Related
So I wanted to return to stock, but now all I have access to is fast boot, with no OS on my device and it's no rooted, unlocked or anything. What do I do!?
You will need to flash back to the factory Google Image through fastboot. Check out the unroot guide to get the image and how to flash.
Remember to root and flash CWM afterwards.
Edit: Guess you don't need root or CWM if you want stock.
Sent from my Galaxy Nexus using XDA App
NewMossie said:
You will need to flash back to the factory Google Image through fastboot. Check out the unroot guide to get the image and how to flash.
Remember to root and flash CWM afterwards.
Edit: Guess you don't need root or CWM if you want stock.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
I tried that, for some reason I can't get it to work. Maybe the instructions are not clear. I'd REALLY appreciate if you can clarify them for me!
Here's what you do.
1. Extract the Google images to your fastboot.exe directory. You should have:
- bootloader-maguro-primekk15.img
- radio-maguro-i9250xxkk6.img
- image-yakju-icl53f.zip
2. Boot into bootloader and THEN plug in your phone
3. Run "fastboot devices" to make sure fastboot reads the phone
4. Type the following commands to flash all 3 images. Be sure to check your phone and wait for each command to finish.
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip
BrandonPrice31 said:
So I wanted to return to stock, but now all I have access to is fast boot, with no OS on my device and it's no rooted, unlocked or anything. What do I do!?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=21308202&postcount=251
Do I have to relock my bootloader and remove CwM recovery to get the OTA updates ?
Relock, no. But you can't have Cwm recovery, and your rom have to be completely stock.
Swiftkey'ed on my CM9 Galaxy Nexus
Herman76 said:
Relock, no. But you can't have Cwm recovery, and your rom have to be completely stock.
Swiftkey'ed on my CM9 Galaxy Nexus
Click to expand...
Click to collapse
So I'm on JellyBean but with the XXLA2 radio. Can the OTA include and replace my radio? I'm debating whether I flash the new radio now or just wait for the OTA.
Memnoch30 said:
So I'm on JellyBean but with the XXLA2 radio. Can the OTA include and replace my radio? I'm debating whether I flash the new radio now or just wait for the OTA.
Click to expand...
Click to collapse
In order for you to get OTA updates, all these images on your device need to match: boot, system, radio, bootloader, recovery. So to get future OTA updates to install, if you are running JB and the JB stock kernel, you need to be running the XXLF1 radio and the LC03 bootloader, and the recovery that came with JB.
efrant said:
In order for you to get OTA updates, all these images on your device need to match: boot, system, radio, bootloader, recovery. So to get future OTA updates to install, if you are running JB and the JB stock kernel, you need to be running the XXLF1 radio and the LC01 bootloader, and the recovery that came with JB.
Click to expand...
Click to collapse
Everything is stock on my phone including the recovery. So I'll flash the new radio then. After I run fastboot flash radio whateverfile.img do I have to reboot to bootloader again or just fastboot reboot and that's it?
Also, I don't see an LC01 bootloader on the JB thread. I'm still on PRIMELA03.
efrant said:
In order for you to get OTA updates, all these images on your device need to match: boot, system, radio, bootloader, recovery. So to get future OTA updates to install, if you are running JB and the JB stock kernel, you need to be running the XXLF1 radio and the LC01 bootloader, and the recovery that came with JB.
Click to expand...
Click to collapse
The only thing that I have flashed so far is Koush's JB ROM...does this mean I have to go ahead and flash everything else? Where do I get these files?
gadgetluva said:
The only thing that I have flashed so far is Koush's JB ROM...does this mean I have to go ahead and flash everything else? Where do I get these files?
Click to expand...
Click to collapse
The files are here:
http://forum.xda-developers.com/showthread.php?t=1737899
Memnoch30 said:
The files are here:
http://forum.xda-developers.com/showthread.php?t=1737899
Click to expand...
Click to collapse
So to confirm, thus far I have flashed the stock Jellybean ROM. Is there a separate kernel that needs to be flashed, or was that taken care of by flashing the JB ROM?
I see that I need the new radio XXLF1, which I'll flash tonight. I see that efrant has listed two versions here: http://forum.xda-developers.com/showpost.php?p=27984443&postcount=1097; if I go through fastboot and temporarily flash CWM through fastboot boot cwm.img, which version should I use? I assume I would then use the CWM version? Otherwise, I would use fastboot flash radio xxx.img for the non-CWM file?
Is the PRIMELC03 - Source: takju JRN84D update bootloader the correct one? I don't see the LC01 that efrant mentioned in his post above? And I would flash using fastboot hboot xxx.img?
Last dumb question: After flashing the JB update, I still have the stock recovery...this doesn't change, correct? In other words, I can leave it as is and now that I have the stock ROM, Radio, Bootloader and left the recovery alone, I should be 100% updated to have OTAs again?
gadgetluva said:
So to confirm, thus far I have flashed the stock Jellybean ROM. Is there a separate kernel that needs to be flashed, or was that taken care of by flashing the JB ROM?
I see that I need the new radio XXLF1, which I'll flash tonight. I see that efrant has listed two versions here: http://forum.xda-developers.com/showpost.php?p=27984443&postcount=1097; if I go through fastboot and temporarily flash CWM through fastboot boot cwm.img, which version should I use? I assume I would then use the CWM version?
Is the PRIMELC03 - Source: takju JRN84D update bootloader the correct one? I don't see the LC01 that efrant mentioned in his post above? And I would flash the same way?
Click to expand...
Click to collapse
Sorry, typo. Lc03
Sent from my Galaxy Nexus using Tapatalk 2
Ok, thanks. I apologize for being so cautious, but I really want to understand how to do everything from fastboot as opposed to flashing through CWM. I would prefer to keep a stock recovery and stock files for now.
Could someone confirm that the following is correct?
1. Flash new radio: Download the .zip and EXTRACT into folder that contains fastboot.exe
Run Command:
fastboot flash radio xxlf1.img
2. Flash new bootloader: download the .zip and EXTRACT into folder.
Run Command:
fastboot hboot LC03.img
3. Stock recovery is kept in place after flashing JB ROM (red exclamation mark with Android on his back)?
4. Stock Kernel was flashed over with the JB ROM as well?
gadgetluva said:
Ok, thanks. I apologize for being so cautious, but I really want to understand how to do everything from fastboot as opposed to flashing through CWM. I would prefer to keep a stock recovery and stock files for now.
Could someone confirm that the following is correct?
1. Flash new radio: Download the .zip and EXTRACT into folder that contains fastboot.exe
Run Command:
fastboot flash radio xxlf1.img
2. Flash new bootloader: download the .zip and EXTRACT into folder.
Run Command:
fastboot hboot LC03.img
3. Stock recovery is kept in place after flashing JB ROM (red exclamation mark with Android on his back)?
4. Stock Kernel was flashed over with the JB ROM as well?
Click to expand...
Click to collapse
Not quite. (I bet you are coming from an HTC device, right? )
Download the XXLF1 radio and rename the image xxlf1.img (for simplicity);
Download the LC03 bootloader and rename the image to lc03.img;
(Yes, they have to be in the same directory as fastboot.)
Reboot into fastboot mode and type:
fastboot flash bootloader lc03.img
fastboot reboot-bootloader
fastboot flash radio xxlf1.img
fastboot reboot-bootloader
fastboot reboot
For your points 3 and 4: yes and yes
efrant said:
Not quite. (I bet you are coming from an HTC device, right? )
Download the XXLF1 radio and rename the image xxlf1.img (for simplicity);
Download the LC03 bootloader and rename the image to lc03.img;
(Yes, they have to be in the same directory as fastboot.)
Reboot into fastboot mode and type:
fastboot flash bootloader lc03.img
fastboot reboot-bootloader
fastboot flash radio xxlf1.img
fastboot reboot-bootloader
fastboot reboot
For your points 3 and 4: yes and yes
Click to expand...
Click to collapse
Thanks efrant!
Memnoch30 said:
Thanks efrant!
Click to expand...
Click to collapse
No problem. I had already laid out a simple step-by-step here to flash Jelly Bean...
efrant said:
No problem. I had already laid out a simple step-by-step here to flash Jelly Bean...
Click to expand...
Click to collapse
Cool I already have JB. Fastboot is still the recommended way, right? At least in my N1, NS days it was supposed to make sure files were flashed successfully whereas CWM couldn't verify it. It just flashed files and you'd find out after a reboot. Is that still the case?
Memnoch30 said:
Cool I already have JB. Fastboot is still the recommended way, right? At least in my N1, NS days it was supposed to make sure files were flashed successfully whereas CWM couldn't verify it. It just flashed files and you'd find out after a reboot. Is that still the case?
Click to expand...
Click to collapse
That was certainly true for the N1. Samsung devices are a little different, and not as easy to brick. I guess you are "safer" with fastboot, but it doesn't make much if a difference on Samsung.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Not quite. (I bet you are coming from an HTC device, right? )
Download the XXLF1 radio and rename the image xxlf1.img (for simplicity);
Download the LC03 bootloader and rename the image to lc03.img;
(Yes, they have to be in the same directory as fastboot.)
Reboot into fastboot mode and type:
fastboot flash bootloader lc03.img
fastboot reboot-bootloader
fastboot flash radio xxlf1.img
fastboot reboot-bootloader
fastboot reboot
For your points 3 and 4: yes and yes
Click to expand...
Click to collapse
Thanks so much. I knew how to do things through CWM, but wanted to learn how to do it all through fastboot on my computer so I fully understand what it is that I'm doing. I appreciate the step by step, you're a huge help to this community and I thank you for that.
---------- Post added at 12:51 PM ---------- Previous post was at 12:49 PM ----------
Memnoch30 said:
Cool I already have JB. Fastboot is still the recommended way, right? At least in my N1, NS days it was supposed to make sure files were flashed successfully whereas CWM couldn't verify it. It just flashed files and you'd find out after a reboot. Is that still the case?
Click to expand...
Click to collapse
It seems like you and I had the exact same questions! Good thing efrant was around to help us out!
Yup, did both now and everything looks good. Thanks again efrant!
Buying a galaxy nexus tomorrow wanted to know how tell if the boot loader us unlock. Can anyone trek me how?
Sent from my ADR6425LVW using xda premium
If it's a new one, it's locked. If it's used you'll know because you will see an icon of an unlocked padlock at the bottom of the screen.
edit: the padlock only shows up when you turn it on.
edit2: like this http://androidallies.com/wp-content/uploads/2011/12/unlocked-nexus2.jpg
Out of curiosity, what is the fastboot command to flash the actual ROM img?
Ok im nexus user but my sister gave me her old DHD to give it to my father but i can't root that $#$!#$ device...im on 3.13.163.3 software no root no s-off (whatever this is) and im not sure what version i have to download from htcdev to downgrade to hboot2.....anyone can help???
Ok i manage to unlock the bootloader with upgrading hboot....i dont have sdcard can i remove soff without one???so i can normally flash roms??cause i flash "RandomROMv101" i also fastboot flash the boot.img after that....but i didnt manage to boot to rom....it takes me to twrp!!!
If your bootloader is S-On unlocked, you need to flash the boot.img from fastboot each time you flash a ROM.
bananagranola said:
If your bootloader is S-On unlocked, you need to flash the boot.img from fastboot each time you flash a ROM.
Click to expand...
Click to collapse
On fastboot is show a purple line sais unlock something...but one line bellow sais sON...can i s-off it without sdcard??
Why do you want S-Off?
bananagranola said:
Why do you want S-Off?
Click to expand...
Click to collapse
To be able to flash boot without flasthboot....i cant flash nothing now...for 4.1 roms i need to flash something else??i flash them through twrp after that i flash boot.img through fastboot but it send me straight to recovery
pikachukaki said:
To be able to flash boot without flasthboot....i cant flash nothing now...for 4.1 roms i need to flash something else??i flash them through twrp after that i flash boot.img through fastboot but it send me straight to recovery
Click to expand...
Click to collapse
What version of TWRP are you running? What ROM are you trying to flash? Are you full wiping? How are you flashing the boot.img? Are there any error messages?
bananagranola said:
What version of TWRP are you running? What ROM are you trying to flash? Are you full wiping? How are you flashing the boot.img? Are there any error messages?
Click to expand...
Click to collapse
This happent to me for the 1st time...but it needed format system too....not sure maybe it isnt inside the update-script file!!!now its all good....so whats exacly soff is doing??i didnt need to flash boot with fastboot
pikachukaki said:
This happent to me for the 1st time...but it needed format system too....not sure maybe it isnt inside the update-script file!!!now its all good....so whats exacly soff is doing??i didnt need to flash boot with fastboot
Click to expand...
Click to collapse
I have no idea what you're saying.
bananagranola said:
I have no idea what you're saying.
Click to expand...
Click to collapse
I had to wipe system too...i only making factory reset that didnt wipe system...all roms i have used wipe system through update-script...anyway now its all good...but why i didnt need to flash boot.img through fastboot?
look here http://forum.xda-developers.com/showthread.php?t=2367322
Is it ok to flash a ROM after i have unlocked my bootloader and rooted or do I absolutely have to have S-Off first? I have looked around and searched and googled first and found no answer to this question. Any help is greatly appreciated!
PS4AndroidHacker said:
Is it ok to flash a ROM after i have unlocked my bootloader and rooted or do I absolutely have to have S-Off first? I have looked around and searched and googled first and found no answer to this question. Any help is greatly appreciated!
Click to expand...
Click to collapse
you can flash a rom with only bootloader unlocked here follow this guide : http://forum.xda-developers.com/showthread.php?t=1435228
PS4AndroidHacker said:
Is it ok to flash a ROM after i have unlocked my bootloader and rooted or do I absolutely have to have S-Off first? I have looked around and searched and googled first and found no answer to this question. Any help is greatly appreciated!
Click to expand...
Click to collapse
You can flash a rom without being s-off but you need to manually flash the boot.img file.
check this thread for info: http://forum.xda-developers.com/showthread.php?t=1421255
Has anybody tried fastbooting the recovery img into the phone's memory?
Like this:
adb reboot bootloader
fastboot boot recovery-clockwork-5.0.2.0-vivow.img
brettbee said:
Has anybody tried fastbooting the recovery img into the phone's memory?
Like this:
adb reboot bootloader
fastboot boot recovery-clockwork-5.0.2.0-vivow.img
Click to expand...
Click to collapse
All that will do is boot you into recovery .
If you use fastboot , the command would be like
"Fastboot flash recovery <name of recovery.img>"
Sent from my Galaxy Nexus using Tapatalk
brettbee said:
Has anybody tried fastbooting the recovery img into the phone's memory?
Like this:
adb reboot bootloader
fastboot boot recovery-clockwork-5.0.2.0-vivow.img
Click to expand...
Click to collapse
bsmitty83 said:
All that will do is boot you into recovery .
If you use fastboot , the command would be like
"Fastboot flash recovery <name of recovery.img>"
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I had read somewhere that if you boot into recovery in the phone's memory instead of from the partition, the recovery will be able to write to the boot partition - so no need to flash the boot.img separately.
I haven't tested this myself, though.
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.