So I was craving vanilla android on my HTC One V (CDMA, primoc) so I unlocked the boot loader, rooted it and installed TWRP. I tried AOKP first, but I ended up in what was basically a boot loop (it would boot up into the setup/startup but within about 30 seconds to a minute it would reboot). After digging around a bit I found some information indicating that only AOSP ROMs would work on my phone, I think because I had taken all the OTA updates before installing the ROM. So I tried some AOSP ROMs, but virtually all of them do the same thing. I have been able to get the CodefireX ROM working, but MMS doesn't seem to work with it (I can send texts but don't recieve them). I'd love to be able to install CM9 or 10 but I can't seem to find any AOSP ROMs (other than CFX) that don't put me in a boot loop. Any help would be greatly appreciated!!!
Flash kernel mate
Sent from my One V using xda premium
cybervibin said:
Flash kernel mate
Sent from my One V using xda premium
Click to expand...
Click to collapse
I always flash the boot.img from the ROM zip, that is flashing the kernel isn't it?
The following have support for the PrimoC OTA update:
-RhythmicROM
-x3reme Sense v5
-I have also gotten PACman to work using the CFX kernel (flash the ROM but use the boot.img from CFX)
-demi_fiend is working on a ROM and kernel that is basically a stock ROM (at least that's how I understand it). The kernel is available, but the ROM hasn't been uploaded yet.
Sounds like you have what I had yesterday. Had you already allowed any over-the-air updates?
If so, check out this thread: http://forum.xda-developers.com/showthread.php?t=2018518
Option #2 worked nicely for me.
still fash them sepreately,
for sense based go for titanium
and aosp based fgo for hell boy
cybervibin said:
still fash them sepreately,
for sense based go for titanium
and aosp based fgo for hell boy
Click to expand...
Click to collapse
Please read the op. The poster has a primoc.
Ya I had actually already tried option #2 over there but got this error...
Hboot Version is older!
Update Fail!
Press <POWER> to reboot
Click to expand...
Click to collapse
From what I understand from the responses I got on that thread my main ver was updated with the OTA and the RUU they are using only supports the one previous to it.
The following have support for the PrimoC OTA update:
-RhythmicROM
-x3reme Sense v5
-I have also gotten PACman to work using the CFX kernel (flash the ROM but use the boot.img from CFX)
Click to expand...
Click to collapse
Thanks for the info! I'll give those a try.
tallnproud said:
The following have support for the PrimoC OTA update:
-RhythmicROM
-x3reme Sense v5
-I have also gotten PACman to work using the CFX kernel (flash the ROM but use the boot.img from CFX)
-demi_fiend is working on a ROM and kernel that is basically a stock ROM (at least that's how I understand it). The kernel is available, but the ROM hasn't been uploaded yet.
Click to expand...
Click to collapse
Well RhythmicROM is giving me the same issue as all the others. I might try flashing demi_fiend's kernel and see if that helps...
*EDIT* So I just realized it might be important to mention that every time I do a factory reset with TWRP it fails and says sd-ext can't be wiped. I've been able to wipe everything else though, and was able to get CFX working so I assumed that wasn't the problem.
my bad sorry
Related
Hey guys my buddy asked me to root rom and install a kernel on his one v from virgin mobile. being as i have done this before to multiple phones i was happy to help. i unlocked the bootloader, rooted it. everything was smooth up til there. i did not put a rom on it yet because he urged me to install a kernel so he could overclock his one v. i was aprehensive but i did it anyway. now his phone wont work. im not surprised but i need to fix it. ive tried installing roms to make it work because the backup ive created in twrp wont boot. so im thinking its a kernel problem. no matter what rom i use it will either not boot it will freeze at the screen that says htc and with the red wording below it. or it will boot into the rom and then freeze or run for about 30 sec then restart and it will repeat this until it dies. ive looked everywhere for ways to get it back to stock ive flashe countless roms none work ive flashed many kernels and none work as well. please help. i would like to get it working on a rom with a working kernel but i will put it back to stock if i have to. any help is greatly appreciated. thank you for your time.
You could flash a ruu ....but the problem is you don't have your software number ...or you have to go to another Rom ...which will make the phone boot normally .but don't forget to flash its specific kernel ...if you don't so that the Rom won't boot
What he said. I recommend using the RUU to restore back to stock.
Re-reroot/unlock it, then read more on which kernel to use. You most likely are using the wrong kernel.
What rom are you using currently - ?
What Kernel did you flash - ?
What error do you get with TWRP - ?
ive only been able to get a couple roms to actually boot. the one that is on it now is Amazing Sense. there is no kernel to flash with this rom and no boot.img for it either. i believe it is included. i have decided to RUU and try everything from the beginning. however i cannot find the RUU for HTC One V in the USA on Virgin Mobile. if you could post a link to that i would be very grateful. i dont see any errors on TWRP and i believe it is the stock rom i flashed last. but like i said with the rom im on it is included, so whatever is on there. thanks again for your help guys.
just curios would the sprint ruu work on the virgin mobile one? it may sound dumb but i have seen people use the recovery.img from it. was just wondering if it would brick the device or not. because i still havent found an RUU for virgin mobile one v in the US.
Nazz45 said:
ive only been able to get a couple roms to actually boot. the one that is on it now is Amazing Sense. there is no kernel to flash with this rom and no boot.img for it either. i believe it is included. i have decided to RUU and try everything from the beginning. however i cannot find the RUU for HTC One V in the USA on Virgin Mobile. if you could post a link to that i would be very grateful. i dont see any errors on TWRP and i believe it is the stock rom i flashed last. but like i said with the rom im on it is included, so whatever is on there. thanks again for your help guys.
Click to expand...
Click to collapse
Nazz45 said:
just curios would the sprint ruu work on the virgin mobile one? it may sound dumb but i have seen people use the recovery.img from it. was just wondering if it would brick the device or not. because i still havent found an RUU for virgin mobile one v in the US.
Click to expand...
Click to collapse
Ok. That's good. You use the same ICS kernel with the same ICS roms. No need to keep reflashing. I wouldn't flash a JB rom using a ICS kernel though.
Use this zip - http://androidfiles.org/uploads/index.php?dir=PrimoC/Kernels/ics
1. Extract the Boot.img from that zip and Fastboot flash boot boot.img in Bootloader
2. Wipe everything. Factory Reset, Dalvik, and System.
3. Flash an ICS based rom, Sense, or CM9.
4. Flash this after rom to get wifi working the zip above or below to fix Wifi.
http://androidfiles.org/uploads/index.php?dir=PrimoC/Kernels/ics
Just ran the RUU and it did work everything is back to stock. the sprint RUU worked. i ran into a snag installing the Android SDK it wouldnt recognize that i had my Java JDK. even after messing with my registry it still wouldnt work so i just downloaded the x86 jdk and it worked. its unfortunate cuz now i have a jdk in x64 and x86 and its taking up space on my ssd. oh well i hope it doesnt mess with eclipse. i am now going to unlock the bootloader again and re root it and install probably cm9. thank you for all your help i will post again after i attempt to re unlock reroot and rom. thanks again
Hi
The development of this ROM has been suspended at the moment due to my busy and conflicting schedule. However, fellow developer krabappel2548 is working on an AOSP ROM too. You may like to check out his work on the XDA Forums and on Facebook. I would like to thank all members of the XDA community for your generous assistance and kind support.
I am new to Android development and have recently gotten myself a brand new Xperia S. After browsing through many forums and websites, I have discovered that our Xperia S was once an experimental device of the AOSP. However, I have noticed that there are hardly any AOSP ROMS built for our device. As I'm having a break now, I have some free time on my hands so I thought why not have a go at building an AOSP ROM for our device. So, I present to you XDantheManX Jellybean, a vanilla AOSP ROM for our Xperia S.
Basically, I downloaded the Android sources from the official repository, cloned the Xperia S AOSP repository, included the software binaries for Xperia S from Sony Mobile and built an Android system for our device. I will be uploading my sources onto a GitHub repository for all to contribute in the near future.
WARNING! This is an unstable PRE-ALPHA release. I will not be held responsible if you brick your device.
DOWNLOAD XDantheManX Jellybean 4.2.1 (Unflashable)
DOWNLOAD XDantheManX Jellybean 4.1.1 (Recommended)
DOWNLOAD XDantheManX Jellybean 4.1.1 (Flashable CWM Zip)
Pre-requisites
- Unlocked bootloader. Instructions here.
- Installed fastboot driver for Xperia S if using Windows.
- Android SDK
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Installation instructions
1. Download XDantheManX Jellybean (CWM flashable zip) and flash using CWM Recovery.
2. Flash a CM10 kernel eg. FXP/NOVA of your choice.
Bugs
Report bugs here!
At present, we have issues with compiling the ROM and getting it to boot because:
- Sony's Github device files are in the progress of being modified for Android 4.2
- Therefore, we are unable to create a fully-working 4.1 ROM
- We are also unable to create a fully-working 4.2 ROM as the migration has not been completed.
So, we're stuck somewhere in the middle :/
- Fastboot flashing method is stuck on system.img for 4.1.2
Please post any bugs on this thread and inform me if it is working/not working. PM me if you require any assistance or would like to work together in developing this ROM.
Let's work together to improve this ROM! :highfive:
Hit the Thanks :good: button if this made your day!
Good luck man, it's good to see a AOSP ROM for our device
That is really nice. I look forward to test this on my device soon. Good job man :good:
EDIT: Why such a complicated way of installing this? Can't it be a little bit more user-friendly? Like install ROM with CWM, and maybe flash the kernel with fastboot?
And both links lead to AOSP 4.1.2. No link for JB 4.2.1.
Felimenta97 said:
That is really nice. I look forward to test this on my device soon. Good job man :good:
EDIT: Why such a complicated way of installing this? Can't it be a little bit more user-friendly? Like install ROM with CWM, and maybe flash the kernel with fastboot?
And both links lead to AOSP 4.1.2. No link for JB 4.2.1.
Click to expand...
Click to collapse
Link to JB 4.2.1 fixed!
I'm still quite new to this and am not sure how to create a flashable CWM zip. Could you teach me how please? Thanks.
Thx for supporting XS and this community
I will try it soon
Sent from my Xperia S using xda app-developers app
XDantheManX said:
Link to JB 4.2.1 fixed!
I'm still quite new to this and am not sure how to create a flashable CWM zip. Could you teach me how please? Thanks.
Click to expand...
Click to collapse
I don't know how to do that, sorry
I never did anything with that instalation method, and even being quite a experienced user, I'm scared of that
Try asking help for championswinner (AOKP dev) or Krabappel (KA ROM dev).
XDantheManX said:
Link to JB 4.2.1 fixed!
I'm still quite new to this and am not sure how to create a flashable CWM zip. Could you teach me how please? Thanks.
Click to expand...
Click to collapse
try this - [GUIDE] How to make a cwm recovery flashable zip - http://forum.xda-developers.com/showthread.php?t=1721680
First 4.2.1 for our device...
Thank you so much...
As it is a pre alpha ,i wanted to ask are the basic things working like mobile data ,wifi ,bluetooth, camera etc etc??
Edit:- First Vanilla 4.1.2 for our device as 4.2.1 has some problems....
Sent from my iPhone 6 using Key Lime Pie
ap030993 said:
First 4.2.1 for our device...
Thank you so much...
As it is a pre alpha ,i wanted to ask are the basic things working like mobile data ,wifi ,bluetooth, camera etc etc??
Sent from my iPhone 6 using Key Lime Pie
Click to expand...
Click to collapse
especially the Wi-Fi, the CM10 rom never seems to read the MAC from my telephone and gives it a MAC adress build in the rom itself, since me and my father both had cm10 we had had same MAC, the wifi gives ip's based on MAC so that conflicted a lot. (thus i went back to CM9.1)
does this rom read the actual telephone's MAC adress?
This way of installing is the same as the way in which Sony released the ICS beta for the 2011 line. It's totally safe, don't worry
Update: Receiving error when executing first command in instructions?
fareeed said:
This way of installing is the same as the way in which Sony released the ICS beta for the 2011 line. It's totally safe, don't worry
Click to expand...
Click to collapse
If you say so, I will do it. To go back, the only thing is installing a kernel with a recovery and go back, right? Kinda confused.
Felimenta97 said:
If you say so, I will do it. To go back, the only thing is installing a kernel with a recovery and go back, right? Kinda confused.
Click to expand...
Click to collapse
Doesn't seem to flash throws out errors when trying to execute the first command,
Code:
fastboot flash userdata out/target/product/lt26/userdata.img
Yeah to return just flash kernel with recovery and restore your nandroid or w/e
fareeed said:
Doesn't seem to flash throws out errors when trying to execute the first command,
Code:
fastboot flash userdata out/target/product/lt26/userdata.img
Yeah to return just flash kernel with recovery and restore your nandroid or w/e
Click to expand...
Click to collapse
Ok. And you're saying that the first command line isn't working?
Felimenta97 said:
Ok. And you're saying that the first command line isn't working?
Click to expand...
Click to collapse
Yeah, I think fastboot flash userdata userdata.img may work. Not too sure, best off waiting for the dev to reply I think.
fareeed said:
Yeah, I think fastboot flash userdata userdata.img may work. Not too sure, best off waiting for the dev to reply I think.
Click to expand...
Click to collapse
fareeed said:
This way of installing is the same as the way in which Sony released the ICS beta for the 2011 line. It's totally safe, don't worry
Update: Receiving error when executing first command in instructions?
Click to expand...
Click to collapse
Are you using the 4.1.2 or 4.2.1 build? I would recommend using the 4.1.1 build.
Apologies for my mistake in the instruction. I stated to move the extracted files to the Android SDK Tools folder where fastboot resides. Therefore, since both files reside in the same directory, to flash userdata.img, the code should be:
Code:
fastboot flash userdata userdata.img
Hope the flashing is successful now! :fingers-crossed:
I built this ROM following the instructions on the Sony Xperia S AOSP Github as I have a powerful machine and wanted to develop an AOSP ROM for the community. However, I have yet to test it as I currently have a locked bootloader, having gotten it recently. Nevertheless, I am planning to unlock it in the near future though as software development has always been my passion and the I am planning to use the Xperia S to test and develop more software, such as Firefox OS, which I'm very interested in at the moment.
Do you know if unlocking the bootloader will void my warranty, and to what extent? Thanks.
XDantheManX said:
Are you using the 4.1.2 or 4.2.1 build? I would recommend using the 4.1.1 build.
Apologies for my mistake in the instruction. I stated to move the extracted files to the Android SDK Tools folder where fastboot resides. Therefore, since both files reside in the same directory, to flash userdata.img, the code should be:
Code:
fastboot flash userdata userdata.img
Hope the flashing is successful now! :fingers-crossed:
I built this ROM following the instructions on the Sony Xperia S AOSP Github as I have a powerful machine and wanted to develop an AOSP ROM for the community. However, I have yet to test it as I currently have a locked bootloader, having gotten it recently. Nevertheless, I am planning to unlock it in the near future though as software development has always been my passion and the I am planning to use the Xperia S to test and develop more software, such as Firefox OS, which I'm very interested in at the moment.
Do you know if unlocking the bootloader will void my warranty, and to what extent? Thanks.
Click to expand...
Click to collapse
I will flash 4.2.1 just for a quick try and such.
About unlocking bootloader, the theory is that they still should fix your device if no hardware harm due overclocking or anything like that happened, but most stores don't fix it just because being unlocked. Also it breaks Download Music Info from Walkman and Bravia Engine on Stock ICS (it's a bug).
ERROR while flashing the second part:
If I type "fastboot flashall" it gives me:
"error: neither -p product specified nor ANDROID_PRODUCT_OUT set"
What should I do?
I already flashed userdata.img...
Even after flashing ramdisk.img, the system got stuck on flashing boot.img, so I stopped, tried to flash the dual.elf (dual boot kernel) and failed. I rebooted the phone (Had to do so, fastboot command didn't worked) and I still have dual boot recovery. Restoring backup now. Hope not to have any problems with the userdata.img thing.
Felimenta97 said:
I will flash 4.2.1 just for a quick try and such.
About unlocking bootloader, the theory is that they still should fix your device if no hardware harm due overclocking or anything like that happened, but most stores don't fix it just because being unlocked. Also it breaks Download Music Info from Walkman and Bravia Engine on Stock ICS (it's a bug).
ERROR while flashing the second part:
If I type "fastboot flashall" it gives me:
"error: neither -p product specified nor ANDROID_PRODUCT_OUT set"
What should I do?
I already flashed userdata.img...
Even after flashing ramdisk.img, the system got stuck on flashing boot.img, so I stopped, tried to flash the dual.elf (dual boot kernel) and failed. I rebooted the phone (Had to do so, fastboot command didn't worked) and I still have dual boot recovery. Restoring backup now. Hope not to have any problems with the userdata.img thing.
Click to expand...
Click to collapse
Thanks for testing out the ROM, @Felimenta97! There have been some reported problems with flashing the boot.img for Android 4.2.1 and I was not sure if they have been addressed yet, therefore I did not recommend to flash it. However, Bjorn Andersson, the lead developer on Sony Xperia S AOSP has stated that Sony will be addressing these problems in a future update of their Github repositories. I will then rebuild 4.2.1 again after the update.
userdata.img is flashed as the /data partition on the ROM. Therefore, if you wipe the data partition using your recovery, your phone should be working fine after the restore.
I will be unlocking my bootloader and testing the ROMs soon, during which I will try to address the reported errors. Are you able to get a working BRAVIA Engine/ BRAVA Engine 2 on the stock/custom ROM after unlocking the bootloader? Have you tried flashing 4.1.2? Thanks!
XDantheManX said:
Thanks for testing out the ROM, @Felimenta97! There have been some reported problems with flashing the boot.img for Android 4.2.1 and I was not sure if they have been addressed yet, therefore I did not recommend to flash it. However, Bjorn Andersson, the lead developer on Sony Xperia S AOSP has stated that Sony will be addressing these problems in a future update of their Github repositories. I will then rebuild 4.2.1 again after the update.
userdata.img is flashed as the /data partition on the ROM. Therefore, if you wipe the data partition using your recovery, your phone should be working fine after the restore.
I will be unlocking my bootloader and testing the ROMs soon, during which I will try to address the reported errors. Are you able to get a working BRAVIA Engine/ BRAVA Engine 2 on the stock/custom ROM after unlocking the bootloader? Have you tried flashing 4.1.2? Thanks!
Click to expand...
Click to collapse
I get it, I think... Anyway, I will wait for it then. I didn't tried the 4.1.2 because it isn't exactly what I want. I kinda want to check what is working on 4.2, the new things etc. I have 4.1.2 on PA, so I'm happy with it
But I can try flashing 4.1.2 for testing if you want. Btw, what I have to do with that kernel file?
About BRAVIA, it's a bug related to ICS and bootloader. No one knows how to make it work on Stock ROMs. Some say Bravia is working on PAC (AOSP based) ROM. I'm not sure about it, though.
Felimenta97 said:
I have 4.1.2 on PA, so I'm happy with it
But I can try flashing 4.1.2 for testing if you want. Btw, what I have to do with that kernel file?
About BRAVIA, it's a bug related to ICS and bootloader. No one knows how to make it work on Stock ROMs. Some say Bravia is working on PAC (AOSP based) ROM. I'm not sure about it, though.
Click to expand...
Click to collapse
Thanks @Felimenta97! I would love it if you could test 4.1.2 to check if there are any problems with the flashing.
You may disregard the kernel file. I had included it as it was output when I built the ROM. After further reading, I understand that the kernel has been merged together with ramdisk.img into boot.img so I'm clueless to the file's purpose at the moment too.
Is PA 4.1.2 working well as a ROM for daily use? Thanks for your assistance!
XDantheManX said:
Thanks @Felimenta97! I would love it if you could test 4.1.2 to check if there are any problems with the flashing.
You may disregard the kernel file. I had included it as it was output when I built the ROM. After further reading, I understand that the kernel has been merged together with ramdisk.img into boot.img so I'm clueless to the file's purpose at the moment too.
Is PA 4.1.2 working well as a ROM for daily use? Thanks for your assistance!
Click to expand...
Click to collapse
I'm using it more as a test ROM and backup ROM. I'm the PA, Dark PA and PAC main tester, so...
But yes, PA works fine for me. One of the best AOSP ROMs so far.
I will test it now.
Hey guys, i am trying to flash a kernel on my phone (bricked kernel) i came from 3 different roms and i always get the same problem. After i flash the rom and enter into it and make sure everything works, I go back to fastboot to flash the boot.img of the kernel and then proceed to flashing the kernel module in revcovery. Everything goes well but once I restart my phone just wont proceed pass the htc logo
I am running hboot verson 1.36 as that is the highest i can go with a CID_044 and running CWM 5.8.4.0 Is there something i should be doing or am doing wrong? Please help and thanks
Are you on a JB rom ? If you are, you can't use those kernels. They are for ICS roms only
Mr.Hofs i right like always but if you are on a ics rom you still need to repack your boot.img. You can do that by using nibble.cc. First step is to take the source boot.img and that can be found in rom.zip and you select it when you are on nibble.cc by clicking on source img. Then you need kernels boot.img and that comes with the kernel download in the kernel.zip. When it is all ready they will upload and repack and you will download repackee boot.img. Hope it helps and good luck
Sent from my HTC One X using xda app-developers app
Haha thanks, and i had a similar case a while back and i adviced him to use the 0.6 or 0.5 bricked kernel because I saw some reports in the bricked thread about not booting. It worked for him.
And are you using the right bricked kernel on the right rom. There is one kernel for the aosp roms and there is one for the sense roms
I don't know if i understand (bad english). With repacked kernel will it work? Same case, CM10, 1.36 hboot and CWM 5.8.4.0.
hey guys thanks for all your help i got it to work on an ICS rom but not on a JB rom which is a real bummer cause i really like the JB roms so i guess i just skip flashing kernels and stick with stock Thank you all for your help i really appreciate it
In fact there are no custom kernels for JB yet at all, HTC has to release the source code for it .... but they haven't done that yet ! Till then stock is all we have
How did you get back to the default kernel after flash bricked kernel?
There are 2 ways to go back to the stock kernel
1 ; flash the boot.img from the rom you are using and flash the modules that can be found in the rom.zip
2 ; flash the boot.img from the rom you are using and reflash the rom without a full wipe ( only cache & dalvik cache )
These methods are the ones i know, maybe there is a tool somwhere ... but i don't use tools
Mr Hofs said:
In fact there are no custom kernels for JB yet at all, HTC has to release the source code for it .... but they haven't done that yet ! Till then stock is all we have
Click to expand...
Click to collapse
I just want to make sure I understand...If I currently have Stock JB running on my HOX I cannot use a custom ROM because the source has not been released? I am asking because Ive gone through all the "standard steps" needed to unlock, root, backup, and flash CM10, but I cannot get past the boot screen.
angrymanhands said:
I just want to make sure I understand...If I currently have Stock JB running on my HOX I cannot use a custom ROM because the source has not been released? I am asking because Ive gone through all the "standard steps" needed to unlock, root, backup, and flash CM10, but I cannot get past the boot screen.
Click to expand...
Click to collapse
No custom kernels are not possible. And i mean by that, that there is no sweep to wake functions or other big tweaks like undervolting. Custom roms are no problem ! And to your not booting question : CM10 on a JB hboot needs a modified kernel !
http://db.tt/uDdWaAtH
You need this one ! Then it will boot
Mr Hofs said:
No custom kernels are not possible. And i mean by that, that there is no sweep to wake functions or other big tweaks like undervolting. Custom roms are no problem ! And to your not booting question : CM10 on a JB hboot needs a modified kernel !
http://db.tt/uDdWaAtH
You need this one ! Then it will boot
Click to expand...
Click to collapse
Wow, thanks! I'll check it out as soon as Dropbox let's me download it. It says your account has too much traffic and to check back later.
Sent from my HTC One X using xda premium
---------- Post added at 06:33 PM ---------- Previous post was at 05:38 PM ----------
also i have another few questions. Is the boot.img you are inking to different than the one packaged with the CN10 rom? If I want to go back to my stock nandroid backup do I need to flash the stock boot.img, or will the restoring of the backup take care of that for me? if i do need the boot.img from the stock rom, how do I get that.
angrymanhands said:
Wow, thanks! I'll check it out as soon as Dropbox let's me download it. It says your account has too much traffic and to check back later.
Sent from my HTC One X using xda premium
---------- Post added at 06:33 PM ---------- Previous post was at 05:38 PM ----------
also i have another few questions. Is the boot.img you are inking to different than the one packaged with the CN10 rom? If I want to go back to my stock nandroid backup do I need to flash the stock boot.img, or will the restoring of the backup take care of that for me? if i do need the boot.img from the stock rom, how do I get that.
Click to expand...
Click to collapse
Yeah I got a mail that my links are suspended !!!
But yes its a different boot.img, and if you want to restore the nandroid backup you also need to flash the boot.img from the nandroid backup ! Its located inside the backup folder
Here it is, the CM10 boot for usage with higher hboot versions.
Thanks everyone. One more question... I see the stock boot image in the backup, but it has a different file extension. Do I have to convert it, or do I just rename it to boot.img? Right now it's named boot.emmc.win
Sent from my HTC One X using xda premium
Just flash it like this:
fastboot flash boot boot.emmc.win
Thank you so much for the info.
Sent from my HTC One X using xda premium
If the nandroid backup is done with CWM the kernel will be named boot.img, and when the nandroid backup is done with TWRP recovery its named like the file you have ! :thumbup:
Awh yeah! It worked! You guys are awesome, thank you for your help!!
Sent from my PG41200 using xda premium
OK, another question. I have s-off, I was under the impression that I would not have to manually flash boot images. So I guess my question is why do I have to manually flash the boot images?
Sent from my PG41200 using xda premium
first off, I'd like to give thanks to everyone on this fantastic site, it's been incredible reading tutorials on here and learning a whole lot of tricks. this here is my first thread and before I go off to look for those I owe *thanks to* I have a question am hoping I can get help with.
my HTC One (GSM) is unlocked, has a Custom Recovery (TWRP 2.3.3) and is rooted. I can install custom 4.0.. ROMS (currently running myONEv RC9.5 FX+ by ckpv5). I have however tried several times to install 4.2.2 ROMS that are on here but to no avail. with the little knowledge that I have gained after several attempts, I realise that the 4.2.2 ROMS are not flashing properly as they don't bring on a custom installer like the ROMS that are working.
can somebody please tell me why? should I update my recovery? or is there something I'm missing?
P.S, I can't seem to get a working 2.5.5 TWRP, at the developers website, their download always dies at 99.9%. ALWAYS
my phones details are as follows
PRIMOU PVT SHIP S-ON RL
HBOOT-1.16.0000
RADIO-3831.15.00.19_M
eMMC-boot
Mar 13 2012,20:17:28
4.2.2 ROMS have some bugs so i suggest u try some other ROMS
however if u want 4.2.2 , u can always flash it and USE THE CORRECT KERNEL
BTW, 4.2 ROMS dont bring up a custom installer so its normal
if in ur recovery it says succesful then the rom is flashed properly but check if u have the appropriate kernel
You dont need to update recovery however it is best doing so; your current recovery is just fine
EDIT: use this kernel : http://www.mediafire.com/?y04jyyu2wk2fig3
well..
Sabbit said:
4.2.2 ROMS have some bugs so i suggest u try some other ROMS
however if u want 4.2.2 , u can always flash it and USE THE CORRECT KERNEL
BTW, 4.2 ROMS don't bring up a custom installer so its normal
Click to expand...
Click to collapse
I want 4.2.2 so badly its eating me up :laugh:. will settle for a 4.1.. if I don't get it right. it's just so darn pleasing seeing my ROM much much higher than all my friends.. :laugh: :laugh: :laugh:
thank you for that piece of knowledge about the 4.2.2 ROMS not having installers. I pretty much thought that was the problem. I have been successful in installing the zips but not once have I gotten past the HTC developer warning (recovery boot animation?). I have been using the kernels that are inside the zips, going to try to load PACMAN 4.2.2 with the kernel you just gave me.
one last question, why can't I see the thank you button? is there a number of times am supposed to post before I can use it? am on a PC so am supposed to see everything, right??
lehunch said:
I want 4.2.2 so badly its eating me up :laugh:. will settle for a 4.1.. if I don't get it right. it's just so darn pleasing seeing my ROM much much higher than all my friends.. :laugh: :laugh: :laugh:
thank you for that piece of knowledge about the 4.2.2 ROMS not having installers. I pretty much thought that was the problem. I have been successful in installing the zips but not once have I gotten past the HTC developer warning (recovery boot animation?). I have been using the kernels that are inside the zips, going to try to load PACMAN 4.2.2 with the kernel you just gave me.
one last question, why can't I see the thank you button? is there a number of times am supposed to post before I can use it? am on a PC so am supposed to see everything, right??
Click to expand...
Click to collapse
If your GSM, the latest PACman ROM has issues
u can boot it with the given kernel but u wont get any mobile data connection
if u must try a 4.2 rom then go for Paranoid Android 3
dunno abt the thank u button, didnt happened to me(PC)
maybe you're just signed off?
Sabbit said:
If your GSM, the latest PACman ROM has issues
u can boot it with the given kernel but u wont get any mobile data connection
if u must try a 4.2 rom then go for Paranoid Android 3
dunno abt the thank u button, didnt happened to me(PC)
maybe you're just signed off?
Click to expand...
Click to collapse
PAC won't even install this time round and my backup has gone into a boot loop. gargh *pulls off hair*. off to download the paranoid android, will be back with results. gracias signore for all your help
Whatever info the Sprint techs put into your device in order for it to get service from their network, that information was cleared when I wiped /data/ and /cache/.
Shouldn't that information be saved somewhere safer?
I am now unable to get service. What do?
RUU recovery fixed it.
But will custom ROMs still not be able to get service? Find out soon!
blksith0 said:
RUU recovery fixed it.
But will custom ROMs still not be able to get service? Find out soon!
Click to expand...
Click to collapse
I'm sure you're all eagerly awaiting the results of that test ^
It turns out that NO the custom ROM wiped whatever info allows the phone to place calls, and no updates/actiavtions would fix it. So gg. Don't buy an M9.
blksith0 said:
I'm sure you're all eagerly awaiting the results of that test ^
It turns out that NO the custom ROM wiped whatever info allows the phone to place calls, and no updates/actiavtions would fix it. So gg. Don't buy an M9.
Click to expand...
Click to collapse
That's not correct. As mentioned several times here on xda the boot.img of 3.35.x firmware-based roms is not compatible with 3.y firmware versions where y is not the same as 35. If you're trying to use a non-sense-based custom rom (e.g. CM) you need to flash thicklizard's mono kernel. For sense-based roms you need to re-flash the stock boot.img of your currently installed firmware. After that you can use the chosen rom without problems.
Sent from my HTC One M9 using XDA Labs
So I should first find out what boot.img that ViperROM 5.3.0 uses, and then I should flash that that same boot.img version to my M9?
Do you need S-OFF for changing boot.img?
blksith0 said:
So I should first find out what boot.img that ViperROM 5.3.0 uses, and then I should flash that that same boot.img version to my M9?
Do you need S-OFF for changing boot.img?
Click to expand...
Click to collapse
No and no. Viper is using a boot.img for 3.35.x. You need the boot.img of your stock firmware. You could for example back up the stock boot.img with TWRP before you delete your stock rom and restore it after you flashed the viper rom. However, since the latest viper version is based on an HTC 10 port you still might face issues. Viper 4.3 on the other hand should be working fine since it's based on the HTC One M9. I'd suggest you to ask in the viper thread whether additional steps are needed for getting viper 5.3 to work on your phone.
Edit @blksith0: Sorry, I totally forgot that the viper rom has a special aroma installer with several options for the different branded M9 versions when I wrote this post. Although you might not be using the device on the sprint network you still need to choose the optimisations for sprint. Those options are made for being able to support the different firmware versions and not for the carrier you're actually using. Because of this flashing the stock boot.img shouldn't be needed in case of the viper rom.
Sent from my HTC One M9 using XDA Labs