Develop Bugs

Jelly Bean OTA downloads but fails to install

I got the notification that JB is ready to download, it downloaded fine and I clicked on Restart & Install. After restarting, the "working" Android icon becomes a 'lying down' Android with a red warning side on top. There is not other info. After a minute the phone restarts and boots back into 4.0.4.
My GNexus is running a rooted stock 4.0.4 firmware, yakju, build numer IMM76I, baseband I9250XXK6, kernel 3.0.8-gda6252b
I'm thinking that something is failing validation at the beginning... is there a way to force install it? Do I need to flash it manually? I'd hate to re-install everything. Other than root, I'm really not interested in any other mods.
Any help is appreciated.

you need to be on xxla2 radio and primela03 bootloader

IINexusII said:
you need to be on xxla2 radio and primela03 bootloader
Click to expand...
Click to collapse
Thanks for the quick reply... how do I get that? I thought what I had was stock and it should be upgradable.

download this and extract it: https://dl.google.com/dl/android/aosp/yakju-imm76i-factory-8001e72f.tgz
use this thread and download the fastboot files if you dont have them already and use the commands for windows to flash just the bootloader and radio: http://forum.xda-developers.com/showthread.php?t=1366806
for the fastboot commands use this:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxla02.img
then restart and wait for the ota update again and it should work

Worked like a charm! Thanks a lot. Tasting some sweet Jelly Bean right now

Should this work for all Galaxy Nexi?
IINexusII said:
download this and extract it: https://dl.google.com/dl/android/aosp/yakju-imm76i-factory-8001e72f.tgz
use this thread and download the fastboot files if you dont have them already and use the commands for windows to flash just the bootloader and radio: http://forum.xda-developers.com/showthread.php?t=1366806
for the fastboot commands use this:
fastboot flash bootloader bootloader-maguro-primela03.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxla02.img
then restart and wait for the ota update again and it should work
Click to expand...
Click to collapse
Thanks for this, should this also work for International GSM Galaxy Nexus in Australia? Just not sure if those radios are ok.
My full story incase it matters...
Unlocked bootloader and rooted (did not replace recovery image)
added a custom boot animation
received ICS OTA updates (Lost root but didn't care)
Cleared Data on Google Service Frameworks to encourage JB update
Recieved 4.1 update but same problem as OP describes with dead robot
I have stock 4.0.4 firmware, yakju, build numer IMM76I, baseband I9250XXLA2, kernel 3.0.8-gda6252b
Thanks for any help.

Can't boot in recovery or ROM

Hey
I was following this tutorial:
http://forum.xda-developers.com/showthread.php?t=1525100
And everything worked well untill the part I had to boot into recovery mode.
I couldn't get into it and decided to skip that part and just flash the boot.img from the ROM
http://forum.xda-developers.com/showthread.php?t=1778202
I flashed everything succesful without any errors but now my phone won't boot, it just gives me a black screen and can't get into recovery.
My bootloader is unlocked and I can still get into it.
I was thinking about flashing the stock RUU or another ROM, but is this possible?
Now I can't use my desire hd .. need some help with it.
EDIT:
I'm S-ON and unlocked bootloader.
I just tried to flash CWM and it flashed succesfully but still couldn't boot into recovery..

That tutorial is for the Desire S. What RUU did you use?

bananagranola said:
That tutorial is for the Desire S. What RUU did you use?
Click to expand...
Click to collapse
I didn't use RUU yet, I was thinking about it..

...OK, I'm confused. Exactly what have you done?

bananagranola said:
...OK, I'm confused. Exactly what have you done?
Click to expand...
Click to collapse
First I unlocked the bootloader.
Then I moved the ROM's zip file to the SD card.
I flashed the 4EXT Recovery after that.
I couldn't boot into recovery so I flashed the ROM's boot.img
Then I couldn't boot my phone in normal mode
After that I flashed CWM but it also didn't work..
Then I used fastboot erase cache and after that I tried fastboot oem rebootRUU
that's all I did untill now

What did you have on your phone to begin with, stock? What ROM zip did you get the boot.img from? How did you flash recovery? Which image?

bananagranola said:
What did you have on your phone to begin with, stock? What ROM zip did you get the boot.img from? How did you flash recovery? Which image?
Click to expand...
Click to collapse
I had stock rom on my phone, didn't make a backup.
http://forum.xda-developers.com/showthread.php?t=2335496 is the rom I tried to put on my phone, that is where the boot.img is from.
And I flashed recovery with
fastboot flash recovery recovery.img
btw, i dont have a file PD98IMG
EDIT:
I tried booting into recovery with the command fastboot boot recovery.img
but it is stuck on the HTC screen

OK, you've flashed a JB AOSP boot.img on a Froyo/GB Sense ROM. No wonder it's not booting. Again, where did you get the recovery image from? You need to flash a working recovery from fastboot (fastboot flash recovery recovery.img), flash the ROM from recovery, and flash the matching boot.img from fastboot (fastboot flash boot boot.img).

bananagranola said:
OK, you've flashed a JB AOSP boot.img on a Froyo/GB Sense ROM. No wonder it's not booting. Again, where did you get the recovery image from? You need to flash a working recovery from fastboot (fastboot flash recovery recovery.img), flash the ROM from recovery, and flash the matching boot.img from fastboot (fastboot flash boot boot.img).
Click to expand...
Click to collapse
I just googled the CWM Recover img...
Can you link me to a working recovery img? and to a ROM that is running android 4.0 or higher and is easier to flash?
thanks man!

SmikkelMikkel said:
I just googled the CWM Recover img...
Can you link me to a working recovery img? and to a ROM that is running android 4.0 or higher and is easier to flash?
thanks man!
Click to expand...
Click to collapse
Recoveries are device specific. http://www.clockworkmod.com/rommanager. ROMs are all flashed the same way if you are S-On with an unlocked bootloader.

bananagranola said:
Recoveries are device specific. http://www.clockworkmod.com/rommanager. ROMs are all flashed the same way if you are S-On with an unlocked bootloader.
Click to expand...
Click to collapse
Well thanks, I fixed it myself but still thank you for your help.
You sent me in the right direction !

[Q] Need help updating to Hboot 1.72

Hello all,
The name of this post says it all really, I am trying to update to Hboot 1.72 but I have no idea how This may be difficult as I have a new computer, and don't have any of the old folder I used to do this before so I will have to start from scratch again I have the Android SDK, so I can take any files needed from there, but apart from that I literally have nothing. Also, I am a complete novice with all this stuff so you may need to "dumb down" your answers a bit Thanks in advance.
Current:
Hboot: 1.32.0000
CID: HTC_001
CWM: 5.8.4.0

TheBlaaaaah said:
Hello all,
The name of this post says it all really, I am trying to update to Hboot 1.72 but I have no idea how This may be difficult as I have a new computer, and don't have any of the old folder I used to do this before so I will have to start from scratch again I have the Android SDK, so I can take any files needed from there, but apart from that I literally have nothing. Also, I am a complete novice with all this stuff so you may need to "dumb down" your answers a bit Thanks in advance.
Current:
Hboot: 1.32.0000
CID: HTC_001
CWM: 5.8.4.0
Click to expand...
Click to collapse
Read THIS for the simple method.

Since you are HTC__001 you'll get the ota soon you just need to be on stock rom, kernel and recovery and you are good to go

desmond1303 said:
Since you are HTC__001 you'll get the ota soon you just need to be on stock rom, kernel and recovery and you are good to go
Click to expand...
Click to collapse
The reason I'm trying to do this is because I'm on CyanogenMod 10.1 and the 10.2 update (Android 4.3) requires the newer hboot, so how would I go about doing this myself (step by step)?
Also Tigerlight, I'm fairly confident that JB FW doesn't let you use non Sense based ROM's afterwards, and to be honest I prefer doing things like this myself rather than letting software do it for you

Well...
You should be able to have CM 1.2 on 1.39...
But you Will have to wait for the firmware zip to be uploaded here http://forum.xda-developers.com/showthread.php?t=1957376
in order to be able to update it manually... You could download the OTA files and extract that firmware.zip yourself and than find a tutorial on how to flash a firmware.zip... there are plenty of them out here

TheBlaaaaah said:
The reason I'm trying to do this is because I'm on CyanogenMod 10.1 and the 10.2 update (Android 4.3) requires the newer hboot, so how would I go about doing this myself (step by step)?
Also Tigerlight, I'm fairly confident that JB FW doesn't let you use non Sense based ROM's afterwards, and to be honest I prefer doing things like this myself rather than letting software do it for you
Click to expand...
Click to collapse
JBFW flasher upgrades hboot, which has nothing whatsoever to do with what Sense or AOSP ROM you flash afterward so long as that hboot is compatible.
And why on earth type all the instructions manually when the tools exist.
And the 1.72 hboot firmware has been uploaded HERE.

Tigerlight said:
JBFW flasher upgrades hboot, which has nothing whatsoever to do with what Sense or AOSP ROM you flash afterward so long as that hboot is compatible.
And why on earth type all the instructions manually when the tools exist.
And the 1.72 hboot firmware has been uploaded HERE.
Click to expand...
Click to collapse
Ok, may have been a bit wrong there..... :silly: Still, I like to learn how to do this sort of thing so that if anything ever goes wrong I have the knowledge to fix it. Once I have the firmware, what do I need to do?

Just downloaded JBFW out of interest, and when you go to update it says this: After upgrade you will not be able to - Install a fully functional Non-Sense ROM, so I was right that I can't use that software, and anyway wouldn't want to tbph Anyone know how to manually update hboot given that I have no files from when I rooted anymore? :laugh:

Once you have the firmware.zip file you have to
1:relock the bootloader
Fastboot oem lock
2: boot into ruu mode
Fastboot oem rebootRUU
3: flash the firmware.zip
Fastboot flash zip firmware.zip
Maybe needed twice (only if the command returns an error)
Then unlock the bootloader and flash a custom recovery. Preferably repacked twrp, or philz touch recovery.
Then full wipe the phone in recovery and install the rom.zip and fastboot flash the boot.img.
That sums it up pretty much

Mr Hofs said:
Once you have the firmware.zip file you have to
1:relock the bootloader
Fastboot oem lock
2: boot into ruu mode
Fastboot oem rebootRUU
3: flash the firmware.zip
Fastboot flash zip firmware.zip
Maybe needed twice (only if the command returns an error)
Then unlock the bootloader and flash a custom recovery. Preferably repacked twrp, or philz touch recovery.
Then full wipe the phone in recovery and install the rom.zip and fastboot flash the boot.img.
That sums it up pretty much
Click to expand...
Click to collapse
Thanks Mr Hofs,
Already found out about 20 mins ago: you actually responded to someone else a while back and I used those instructions. I may have messed up quite a lot though: forgot to put the CM 10.2 zip on the phone before hand and now the phone is acting really weird..... I'll let you know if I need help but I have a few ideas first
Thanks again, I appreciate the help.

help

my friend has just brought a one x and it came already rooted and with cm10 on it, he was thinking of changing software, what do i need know about this phone as i am the owner of an arc so no nothing of HTCs. can get on bootloader and into recovery but do not know if kernel has been changed or not and which software we are safe to use. any help would be greatly appreciated. thanks

eddrowe said:
my friend has just brought a one x and it came already rooted and with cm10 on it, he was thinking of changing software, what do i need know about this phone as i am the owner of an arc so no nothing of HTCs. can get on bootloader and into recovery but do not know if kernel has been changed or not and which software we are safe to use. any help would be greatly appreciated. thanks
Click to expand...
Click to collapse
the best thing if to start over, in my opinion... put the rom you like on sdcard (change recovery if needed) and flash it following the instructions in the rom OP (remember to flash the boot.img from the zip otherwise it won't boot)... it's plenty of guides here, just look around

lukes91 said:
the best thing if to start over, in my opinion... put the rom you like on sdcard (change recovery if needed) and flash it following the instructions in the rom OP (remember to flash the boot.img from the zip otherwise it won't boot)... it's plenty of guides here, just look around
Click to expand...
Click to collapse
kernel says on phone its 2.6.39.4-cyanogenmod inkyghost? is that a custom one? can this be changed easily?

eddrowe said:
kernel says on phone its 2.6.39.4-cyanogenmod inkyghost? is that a custom one? can this be changed easily?
Click to expand...
Click to collapse
if you flash a new rom or another kernel the current one will be overwritten...

lukes91 said:
if you flash a new rom or another kernel the current one will be overwritten...
Click to expand...
Click to collapse
i know yeah but thats not the stock kernel is it? do i need no anything about bootloaders with these fones i can get on the bootloader menu so i imagine its unlocked is there a way of finding that out?
do htcs flash in a different way to sony phones as like i sed i never used a htc phone or flashed one b4

eddrowe said:
i know yeah but thats not the stock kernel is it? do i need no anything about bootloaders with these fones i can get on the bootloader menu so i imagine its unlocked is there a way of finding that out?
do htcs flash in a different way to sony phones as like i sed i never used a htc phone or flashed one b4
Click to expand...
Click to collapse
no, it's not htc stock kernel... to find out if the phone is unlocked enter the bootloader and look if the top flag is "unlocked" or "relocked"...
i never flashed a sony device, so i can't tell for sure...
in htc you have to flash the boot.img from rom zip via fastboot and then the rom zip via recovery...

Because you already have CM on your device that means your device is bootloader unlocked
I have rooted and flashed my sisters Xperia which is to similar to ARC , so here are couple of points you need to know before start flashing ROMs and kernels
1-On HOX we have an hboot which is like a bios for a PC which mostly its s-on
2-hboot will not allow you to flash any ROM in a single flash because its will not allow you to flash the boot.img file of it's kernel
3-so when flashing any ROM or kernel you need to flash ROM zip file from recovery then you need to extract boot.img file from ROM zip on your PC and boot into bootloader to push the extracted boot.img from your PC using this fastboot command every time "fastboot flash boot boot.img" if you are using Linux you may have to start your command with sudo
So for flashing here on HOX it's same for ROMs as for kernels
To change recovery for HOX it's nearly as same as flashing boot.img
For recovery you need to get into bootloader to flash the needed recovery.img using fastboot command "fastboot flash recovery recovery.img"
And after each fastboot command you need to place this command order "fastboot erase cache" to prevent boot loops
Sent from my Nexus 7 using Tapatalk

Need help with S-On HTC One M9...

I have an international stock HTC One M9. CID is: HTC__621 and firmware version: 210.709.1 - I've already found the stock recovery for 210.709.1 - I'm looking to install a custom ROM, but I may want to go back to stock later on. I found a TWRP stock backup for 210.709.1, but because I am S-ON, will I not have to manually flash the boot.img? I used winrar to look into the TWRP backup, and I could not find a boot.img. So, my question is: if I flash the TWRP backup using TWRP, will the boot.img automatically get flashed?

You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .

mrbtree98 said:
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
Click to expand...
Click to collapse
Should I rename this to: "boot.img"? And then, use command: " fastboot flash boot boot.img"?

mrbtree98 said:
You will have to flash the boot.img manually. The boot image is there it should be called boot.emmc.win .
Click to expand...
Click to collapse
There's no "boot.emmc.win" within the archive? I can't find it...

arif9m9 said:
Should I rename this to: "boot.img"? And then, use command: " fastboot flash boot boot.img"?
Click to expand...
Click to collapse
Some weeks ago I was told that all newer phones than the HTC One M7 are able to flash boot images with TWRP even if they are S-ON. (I wasn't able to verify that since my phone is S-OFF.) So there should be no need to rename and manually flash the boot image if it's already inside the backup.
arif9m9 said:
There's no "boot.emmc.win" within the archive? I can't find it...
Click to expand...
Click to collapse
You can find the needed boot image in my signature.

Flippy498 said:
You can find the needed boot image in my signature.
Click to expand...
Click to collapse
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?

arif9m9 said:
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
Click to expand...
Click to collapse
If you use the backup from my signature you only need to follow the instructions on the first page of my google sheet to get back to stock.
Be warned: Since Android 5.1 you should only relock the bootloader if you are completely sure that your phone is able to boot to system and that you ticked the new option that allows a bootloader unlock (can be found in the developers options). Many users already got stuck with a non-booting phone that cannot be re-unlocked because they didn't fulfill these requirements. (Sidenote: If you only want to get back to stock to install new OTAs you don't need to relock your bootloader.)
Besides I read that some people stated that the AOSP roms of the M9 messed up their LTE reception (so that LTE was even unusable on other custom roms or stock rom). I don't know whether this problem is already fixed. Some weeks passed since I read about that problem so I suggest you to read the corresponding threads before you start flashing.

arif9m9 said:
Thanks. I downloaded: "boot_2.10.709.1.img" from your signature. Do I just flash it in fastboot like this: fastboot flash boot boot_2.10.709.1.img"? Is it okay if I rename it to just: boot.img?
My M9 is completely stock, right now. I'm intending to: unlock the bootloader, flash TWRP recovery, and finally, install an ASOP ROM.
When attempting to go back to stock, I'm going to: boot into TWRP, wipe everything except for SD card, flash the 2.10.709.1 TWRP stock backup, boot into fastboot and flash the command: "fastboot flash boot boot_2.10.709.1.img", flash the stock 2.10.709.1 recovery, and finally, relock the bootloader. Will all these steps be correct for an attempt to go back to stock?
Click to expand...
Click to collapse
There is no need to flash the boot.img separately on this phone.
As noted DO NOT RELOCK unless you have ticked that "allow oem unlocking" option first. I cannot stress this enough.
Also, no AOSP rom currently has a working camera.

iElvis said:
There is no need to flash the boot.img separately on this phone.
As noted DO NOT RELOCK unless you have ticked that "allow oem unlocking" option first. I cannot stress this enough.
Also, no AOSP rom currently has a working camera.
Click to expand...
Click to collapse
My phone is S-ON, won't I have to flash the boot.img via fastboot?

arif9m9 said:
My phone is S-ON, won't I have to flash the boot.img via fastboot?
Click to expand...
Click to collapse
Flippy498 said:
Some weeks ago I was told that all newer phones than the HTC One M7 are able to flash boot images with TWRP even if they are S-ON.
Click to expand...
Click to collapse
iElvis said:
There is no need to flash the boot.img separately on this phone.
Click to expand...
Click to collapse
No, it's not needed. The only exceptions are backups that don't contain a boot image (like mine for example). That's why I created the google sheet with the instructions.

Flippy498 said:
No, it's not needed.
Click to expand...
Click to collapse
But, when installing custom ROMS, I'll definitely have to use the fastboot command to flash the boot image, right?

arif9m9 said:
But, when installing custom ROMS, I'll definitely have to use the fastboot command to flash the boot image, right?
Click to expand...
Click to collapse
No.

Flippy498 said:
No.
Click to expand...
Click to collapse
But, I'm S-ON....

arif9m9 said:
But, I'm S-ON....
Click to expand...
Click to collapse
It hasn't been an S-on restriction since the M7.

iElvis said:
It hasn't been an S-on restriction since the M7.
Click to expand...
Click to collapse
Does that mean I can flash RUUs even if I'm S-ON?

arif9m9 said:
Does that mean I can flash RUUs even if I'm S-ON?
Click to expand...
Click to collapse
For your CID/MID, yes.

iElvis said:
For your CID/MID, yes.
Click to expand...
Click to collapse
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?

arif9m9 said:
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
Click to expand...
Click to collapse
It depends. If you have a current RUU for your phone (i.e., you don't need to downgrade), you can run it S-on, as that's what it's for.
But if you need to downgrade because the only RUU is an earlier version, yes you do need s-off.
S-off also allows you to go back to LOCKED instead of RELOCKED.

iElvis said:
It depends. If you have a current RUU for your phone (i.e., you don't need to downgrade), you can run it S-on, as that's what it's for.
But if you need to downgrade because the only RUU is an earlier version, yes you do need s-off.
S-off also allows you to go back to LOCKED instead of RELOCKED.
Click to expand...
Click to collapse
When going back to stock, at which stage should I relock my bootloader?

arif9m9 said:
But, all the 'Returning to stock' guides
for the M9 state S-OFF is obligatory?
Click to expand...
Click to collapse
Because if you follow these guides your phone will state "locked" instead of "relocked" at the end. And that is only possible with S-OFF. Besides with S-ON you can only use RUUs with the same firmware version as your phone (or newer RUUs)*.
*Actually downgrades seem to be possible, too, but as far as I know only if the two first numbers of the firmware versions before and after the downgrade are the same. Like from 1.32.xxx.15 to 1.32.xxx.8 but not from 1.40 versions to 1.32 versions or from 2.xx versions to lower versions.
Edit: Looks like I didn't type fast enough.