Database Develop

[HOWTO] Update HBOOT to 1.00 keeping your Legend rooted

CAUTION!! By upgrading HBOOT to 1.00+ you loose the ability to S-OFF your Legend!!!
Preface
Because there are too many ppl without any knowledge spreading false findings and statements I decided to write this HOWTO.
Audience
This HOWTO is primarily ment for those who already have rooted Legends but they recently experienced problems flashing CM's or new Vodafone FroYo boot.img.
Background
HBOOT is like a BIOS in our PCs and to cut a long story short it also contains partition table for phone's internal storage. That means it has info on where exactly certain partition starts and how big it is.
At HTC they decided to partition Legend's internal storage this way:
misc 640 kB
recovery 4,375 MB
boot 2,5 MB
system 240 MB
cache 40 MB
data 185 MB
...but as we found out (first with CM nightly) boot partition was a little short for the boot.img to fit in if we had one or more bad cells (sectors) on it. Eventually we found out that quite some Legend's had bad cell on boot partition and those unfortunate souls that owned such phone were unable to upgrade to Vodafone FroYo rooted ROM too.
I think that HTC also recognized that Legend's boot partition was kinda small so they rearanged partition table in HBOOT 1.00 a bit making boot partition bigger (now it is 3 MB) by shrinking recovery partition a little.
So now we know that some of us actually need HBOOT 1.00 in order to flash FroYo's boot.img without a problem. But how do we keep root then?
Prerequirements
Android SDK (primarily adb)
working USB drivers (for adb to work)
goldcard (in case you are trying to flash ROMs with different CID than your phone has)
ClockWorkMod recovery (if your Legend is already rooted)
Rerequirements
Vodafone FroYo OTA update (actually just firmware.zip from OTA)
Legend rooting tools (just testimage.zip)
Hack 4 Legend v5(just misc1-2.img and flash_image)
VISIONary r13(r14 is out also but i haven't tested it yet)
Instructions
I will split instructions into two parts... for already rooted phones and phones that were already updated with Vodafone OTA thus they lost root.
Already OTA updated with HBOOT 1.00
That one is relatively easy. You could also follow Paul's guide but I like my approach better
Connect your phone to your PC. Second you have to install VISIONary r13 into your phone and do the "temproot" procedure. After a successful "temproot" you should be able to adb shell and then su. Fire up command prompt and issue:
Code:
adb shell
su
...you should have root privileges now (showing #). Next thing is backing up misc partition and replacing it with one from hack4legend-v5.zip. Extract this zip somewhere and fire another command promt there. Now you should upload flash_image binary and misc1-2.img:
Code:
adb push flash_image /data/local/
adb push misc1-2.img /data/local/
...switch back to 1st command prompt and change permission of flash_image_binary:
Code:
chmod 755 /data/local/flash_image
...and backup your current misc partition:
Code:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
Now flash misc1-2.img:
Code:
/data/local/flash_image misc /data/local/misc1-2.img
exit
...and you are set to downgrade retaining HBOOT 1.00.
Unzip r4-legend-root.zip and find testimage.zip in it. Put it on your phone's sdcard renaming it to LEGEIMG.zip. You can then reboot into bootloader issuing:
Code:
adb reboot bootloader
...from command prompt. Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard. Make your sdcard gold and try again. After successful flash and reboot you may remove LEGEIMG.zip from sdcard. Next step is upgrading of rooted FroYo ROM. Put FroYo update ROM zip to your sdcard and install it via ClockworkMod recovery. You may also flash backed up misc partition after that. Still in recovery mode and hooked with your PC switch to command prompt and restore it back:
Code:
adb shell
flash_image misc /sdcard/misc_backup.img
exit
...and reboot.
Rooted Eclair Voda FroYo or CM with HBOOT 0.43
Since you have already rooted phone we can prepare everything before we start. Hook your phone to your PC. Put FroYo ROM update zip to phone's sdcard. Put also misc1-2.img and flash_image from hack4legend-v5.zip and testimage.zip from r4-legend-root there. Extract Vodafone FroYo OTA and put firmware.zip to your phone's sdcard renaming it to LEGEIMG.zip. Reboot into bootloader from command prompt:
Code:
adb reboot bootloader
...bootloader will find LEGEIMG.zip extract it into RAM and check its integrity. If you get CID error at this point you don't have gold card. Make your sdcard gold and retry the procedure.
After successfull flashing of LEGEIMG.zip (firmware.zip from FroYo OTA) you have HBOOT 1.00, new (unrooted) recovery, new (unrooted) boot but old and intact system with superuser.apk and su. Reboot. When system is available, tick "USB debugging" in Settings->Applications->Development. After that you will be able to adb shell into your phone. Fire up some command prompt and issue:
Code:
adb shell
su
...while phone screen is still on. Superuser will pop-up. Grant it. Now make a backup of misc partition:
Code:
cat /dev/mtd/mtd0 > /sdcard/misc_backup.img
...now copy flash_image from sdcard to internal storage, change its permissions, and flash misc1-2.img:
Code:
cp /sdcard/flash_image /data/local/
chmod 755 /data/local/flash_image
/data/local/flash_image misc /sdcard/misc1-2.img
...rename LEGEIMG.zip to firmware.zip and testimage.zip to LEGEIMG.zip:
Code:
mv /sdcard/LEGEIMG.zip /sdcard/firmware.zip
mv /sdcard/testimage.zip /sdcard/LEGEIMG.zip
...exit from adb shell and reboot into bootloader:
Code:
exit
adb reboot bootloader
Phone will reboot, find LEGEIMG.zip and flash it over. You will end up with HBOOT 1.00 and downgraded and rooted recovery. Boot into ClockworkMod recovery and flash Voda FroYo custom update of your choice from your sdcard. You may also want to restore backed up misc partition after updating is done:
Code:
adb shell
flash_image misc /sdcard/misc_backup.img
exit
...and reboot.

Goldcard (no remove, no format, no data loss)
Here are few easy steps on how to make Goldcard without taking it out of your phone but you have to be root (VISIONary temproot is fine).
You will be doing this from command prompt:
Code:
adb shell
su
First you need to find out sdcard's CID:
Code:
cat /sys/class/mmc_host/mmc0/mmc0:*/cid
...copy it into text box on http://hexrev.soaa.me/. Now go to http://psas.revskills.de/?q=goldcard and put in the reversed CID you have got on previous web page. Push goldcard.img to your phone via 2nd command prompt:
Code:
adb push goldcard.img /data/local/
...unmount sdcard via Settings, go back to 1st command prompt and make a backup then make goldcard:
Code:
dd if=/dev/block/mmcblk0 count=1 of=/data/local/sdcard_backup.img
cat /data/local/goldcard.img > /dev/block/mmcblk0
sync
exit
You may also pull that backup to your PC:
Code:
adb pull /data/local/sdcard_backup.img .

BlaY0 said:
Reserved...
Click to expand...
Click to collapse
awosome , I think you must have found some method to crack the SPL? just as desire do ?
waiting

There's actually no cracking of SPL involved...

Hi blay0,
I follow your link to vodafone ota update and appoint me to the website, where is the the link to download it?
Thanks.
Sent from my HTC Legend using Tapatalk

BesFen said:
Hi blay0,
EDITED: I got it, thanks
Click to expand...
Click to collapse

THX
@blay0:
thanks you are great developer.
so if you could temproot automated so you could build pc software to root legend with one click automatically like as wildfire desire ......
thx again

Hmm, I don't understand what are you trying to say???
Sent from my HTC Legend

BlaY0 said:
Hmm, I don't understand what are you trying to say???
Sent from my HTC Legend
Click to expand...
Click to collapse
in htc wildfire rooting process will do Unrevoked 3 for Wildfire
is it possible to automated above process?

VISIONary has an option to "temproot" on every boot.
But I don't see why you would do that if you can root the way I described.
Sent from my HTC Legend

Thanks Blayo ...
@ Blayo
I have some doubts regarding OTAs .. Please check your PM

The primary use of OTA here is just to extract firmware.zip flashing it to upgrade HBOOT. This is not HOWTO for updating the whole system via OTAs.
Sent from my HTC Legend

After flashing firmware.zip, the phone wont boot. Stuck at the HTC logo. What should I do?

Hey guys , im really troubled gettin permission denied on push.
any suggjestions? googled loads of it but nothing related to my issue
Edit: i got root tru visionary yes , it aply's well and su promts for permission so i guess i got root
so was wondering why i keep gettin permission denied on any command in adb
Second EDIT : Nevermind total noobness , forgot i cant push within adb shell.

Hats off to BlaY0 for another amazing work.

rajasyaitan said:
Hats off to BlaY0 for another amazing work.
Click to expand...
Click to collapse
Yes indeed m8 , thanks for your efforts!
Finaly unlocked the Hboot 1.00 running rooted ota froyo
/bow 2 BlaYo.

You're awesome.

Amazing, thanx a million!!
Keeps the Legend running smoothly with custom Froyo Modaco rom.................

I used this guide after my downgrade to Rom 1.31 with HBoot 1.00 and it worked like a charm ! Thank you !

wow You're awesome

[Q] Homemade Fastboot doesn't work for me

I have flashed the 91.2.26001.Retail.en.EU - 4.1.2 homemade fastboots from mattlgroff several times, but I always stuck in a bootloop.
The warning message of the unlocked bootloader is shown, but nothing happens.
I wiped and formatted all partitions with CWM and installed all manually from my gentoo machine with the same commands as in the batch script shown.
What could be the reason, a missing firmware file for my phone or something related? Is there a possibility to look into a log file what's the error?
I switched back to my saved JB (same version) with CWM and all is fine again. I also tried to mix your homemade system.img with my saved boot.img but with no success. Have I missed anything?

Machredsch said:
I have flashed the 91.2.26001.Retail.en.EU - 4.1.2 homemade fastboots from mattlgroff several times, but I always stuck in a bootloop.
The warning message of the unlocked bootloader is shown, but nothing happens.
I wiped and formatted all partitions with CWM and installed all manually from my gentoo machine with the same commands as in the batch script shown.
What could be the reason, a missing firmware file for my phone or something related? Is there a possibility to look into a log file what's the error?
I switched back to my saved JB (same version) with CWM and all is fine again. I also tried to mix your homemade system.img with my saved boot.img but with no success. Have I missed anything?
Click to expand...
Click to collapse
Hello good morning
You can start the process in fastboot mode
Put manually RAZRiRoot2.zip file in the SDCARD
In the PC, need to modify the file *****.bat (EDIT)
delete 2 lines containing the command ADB, skip the file, saving changes
start your phone in fastboot mode and the PC starts the file ****.bat, you just modified.
Once the process is complete, the file RAZRiRoot2.zip flashing in CWMR
(not you format any partition)
Greetings and Luck
Sorry for my bad english
EXAMPLE
adb kill-server > nul
adb start-server > nul
ping 1.1.1.1 -n 1 -w 500 > nul
cls
echo. "Have drivers installed, phone connected, and USB Debugging enabled in Developer Options."
echo. "Also make sure to have a lot of battery power or a factory-style adapter before attempt."
pause
adb wait-for-device push RAZRiRoot2.zip /sdcard/RAZRiRoot2.zip DELETE THIS
adb reboot bootloader DELETE THIS
ping 1.1.1.1 -n 1 -w 1000 > nul
fastboot flash system system.img.ext4
ping 1.1.1.1 -n 1 -w 1000 > nul
fastboot flash boot boot.img
fastboot flash recovery cwm.img
echo. "Select Recovery with Volume Up and flash RAZRiRoot2.zip from internal SD card..."
echo. "Done. If you bootloop then wipe data. "
pause
Click to expand...
Click to collapse

I think you haven't understood what I meant. The homemade ROM isn't working for me, as I said, after flashing. Flashing is well. It absolutely makes no sense to remove commands which let you enter fastboot mode and enter fastboot mode manually then. And there is no difference of starting a batch Script or typing in the same flash commands by hand in a Shell. Starting the bat isnt possible because of using Gentoo Linux, except for running it through my Virtual Machine or converting it to a bash Script. I just wanna know why it doesn't boot the homemade. I installed the root afterwards manually through CWM from sideload so no need for push and also tried via external sd. Root installed always fine too like the flash process.

[Q] First Time Rooter, am I doing this right

These are the steps I am planing on following to root my AT&T Moto X, If you see any mistakes please let me know.
First I need to Get my Moto x to 4.2.2 firmware
Install RSD Lite
Install Moto Drivers
Download 4.2.2 Firmware
Unzip 4.2.2 Firmware
Open Firmware XLM file and delete <step operation="getvar" var="max-download-size" />
Save file and Re-zip Firmware folder
Plug in phone and enable USB debugging, disable Verify apps over USB
Then open Minimal ADB/Fastboot command prompt and type in "adb reboot bootloader"
Run RSD Lite and flash the firmware package I just made.
Let the whole process finish. When phone reboots, wait 5 min and I wont take the OTA
Next i got to root my phone on 4.2.2
Get My phones IP Address
un-zip Rockmymoto
Place the Rockmymoto.jar file and the su file into the Minimal ADB/Fastboot folder
Then push Rockmymoto.jar file and the su file to the SD card
Run Impactor and select "# start telnetd as system on port 2222", then hit start
Run telnet: telnet {phone's ipaddress} 2222
Run the exploit through telnet
The exploit will tell you to use adb to reboot
Wait 5 min run the exploit through telnet for the second time, it will reboot on it's own
Wait 5 min run the exploit through telnet for the third time, it will not reboot
Wait 0-60 seconds, for su to install, then install SuperSu from the market
Now i have to disable Write Protection
Download and extract the MotoWPnomo
run wpbegone.exe as administrator
follow the on-screen prompts
verify with: adb shell getprop ro.boot.write_protect
Using Rsd lite reflash the 4.2.2 Firmware that I had flashed in the first part
At this point its time to Slap My Moto
Unzip SlapMyMoto.zip and place the 5 files (Classes.dex, Install.sh, install-recovery.sh, SlapMyMoto.jar, and su) in the Minimal ADB/Fastboot folder and push the jar file to my internal storage
Over telnet, run Stage1 with this command: dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" and wait 5 min
Run Impactor again and connect over telnet just like in the previous step, then run the same command
Device will reboot, wait 5 min then take the 4.4 OTA
When the phone reboots wait 5 min and finish with adb shell:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
The wait for my device to reboot. And ill be 4.4 rooted on my moto X

:what::what::what:
Just go to fastboot mode and install directly 4.4 ,this one include the OTA update, the phone will reboot.
Ok...go to fastmode again and install/flash TWRP 2.6.3.1 recovery http://forum.xda-developers.com/showthread.php?t=2534850 ok ...now in fastboot mode select "recovery" twrp will start, there is a reboot option, just select "reboot/system" and twrp will ask you if u want to install superSU/root.....select "yes/install super SU" . the phone will reboot.....ready !!! Just go to playstore and update superSU, open superSU and update binaries.
All this process will be ready in 5-8 mins.

omias said:
:what::what::what:
Just go to fastboot mode and install directly 4.4 ,this one include the OTA update, the phone will reboot.
Ok...go to fastmode again and install/flash TWRP 2.6.3.1 recovery http://forum.xda-developers.com/showthread.php?t=2534850 ok ...now in fastboot mode select "recovery" twrp will start, there is a reboot option, just select "reboot/system" and twrp will ask you if u want to install superSU/root.....select "yes/install super SU" . the phone will reboot.....ready !!! Just go to playstore and update superSU
All this process will be ready in 5-8 mins.
Click to expand...
Click to collapse
Isn't this only unlocked bootloader
Sent from my XT1053 using Tapatalk

U need unlocked bootloader the 1st post process is 'tedious' :sly::sly:

[Q] HELP! Can't root after using MotoWPNoMo

Okay all... I had 4.2.2 rooted, write protection off. I tried rooting up to 4.4, didn't go well so I flashed fresh 4.2.2, no root.
Well, I lost root and I'm not sure how to get it back. I've searched the forums for about 3 hours to no avail....
Any help or pointing me in the right direction would be greatly appreciated!

byrdmang2 said:
Okay all... I had 4.2.2 rooted, write protection off. I tried rooting up to 4.4, didn't go well so I flashed fresh 4.2.2, no root.
Well, I lost root and I'm not sure how to get it back. I've searched the forums for about 3 hours to no avail....
Any help or pointing me in the right direction would be greatly appreciated!
Click to expand...
Click to collapse
Start Rant
There is no way you searched the forums for 3 hours the 5th Thread in the Original Android Development is RockMyMoto which is the root for 4.2.2. Also a quick Google Search of Moto X 4.2.2 Root would of given you many guides..
End Rant
Here is the link hope it helps.
http://forum.xda-developers.com/showthread.php?t=2509590
and if you want to root 4.4 check out this guide.
http://forum.xda-developers.com/showthread.php?t=2603358

dray_jr said:
Start Rant
There is no way you searched the forums for 3 hours the 5th Thread in the Original Android Development is RockMyMoto which is the root for 4.2.2. Also a quick Google Search of Moto X 4.2.2 Root would of given you many guides..
End Rant
Here is the link hope it helps.
http://forum.xda-developers.com/showthread.php?t=2509590
and if you want to root 4.4 check out this guide.
http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
That's the thing though... I already HAD 4.2.2 root. I just wanted to root 4.4. I tried the OTA to it, then RSD'd to 4.2.2. But by that point, my write protection was gone, and trying slapmymoto wasn't working either... I'm sorry for being a nuisance and newb, I just want to figure it out and be done!

byrdmang2 said:
That's the thing though... I already HAD 4.2.2 root. I just wanted to root 4.4. I tried the OTA to it, then RSD'd to 4.2.2. But by that point, my write protection was gone, and trying slapmymoto wasn't working either... I'm sorry for being a nuisance and newb, I just want to figure it out and be done!
Click to expand...
Click to collapse
You should still have write protect off even if you flash the stock firmware
run this command and let me know what you get
Code:
adb shell getprop ro.boot.write_protect
If you see "0", that pesky write protection is gone
then we will go from there
but if you have tried rooting you need to give us the error's you got trying to do the 4.4 root so we can see what the issues is and help you find a fix.

Well I have 0.. I've checked that every time I've given this a go. I'm assuming since I've rooted 4.2.2 before AND ran (successfully) motowpnomo, I jump to slapmymoto right?
Well when I do that and run the dalvikvm -cp ... command line, it gives me the line that the system is not write protected (duh), proceed to step 3 attempt the 4.4 ota.. But it doesn't auto reboot like I've read it should. So I've manually done adb reboot, figuring no difference right?
After I'm on 4.4 I try adb reboot bootloader to flash the 4.2.2 recovery.. Does it's business, fastboot reboot.
It's now gotten to the LAST command line with the "echo" command where I get permission denied.. How does that work?

byrdmang2 said:
Well I have 0.. I've checked that every time I've given this a go. I'm assuming since I've rooted 4.2.2 before AND ran (successfully) motowpnomo, I jump to slapmymoto right?
Well when I do that and run the dalvikvm -cp ... command line, it gives me the line that the system is not write protected (duh), proceed to step 3 attempt the 4.4 ota.. But it doesn't auto reboot like I've read it should. So I've manually done adb reboot, figuring no difference right?
After I'm on 4.4 I try adb reboot bootloader to flash the 4.2.2 recovery.. Does it's business, fastboot reboot.
It's now gotten to the LAST command line with the "echo" command where I get permission denied.. How does that work?
Click to expand...
Click to collapse
idk what guide your following but i think it is old.
1. download the correct 4.2.2 CU firmware for your Carrier
2. open the .zip files and extract the files into your folder with ADB and MFastBoot.
3. Boot your phone into the bootloader
4. Run the below commands one by one
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
i recommend wiping your device also but that is up to you
Code:
fastboot erase userdata
fastboot erase cache
Step1)
Unzip SlapMyMoto-1,0.zip and push the jar file to your internal storage
Code:
adb push SlapMyMoto.jar /sdcard/SlapMyMoto.jar
Step2)
Use http://www.cydiaimpactor.com/ to open up a telnet session as system user on port 2222. We covered how to use Impactor and telnet in the RockMyMoto root, I won't be covering it again since this post is going to be long enough already, see here -> http://forum.xda-developers.com/show....php?t=2509590 or http://rootzwiki.com/topic/107098-ro...the-first-ota/
Connecting over telnet, and run Stage1 with this command:
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
When the device tells you to reboot, do this manually with "adb reboot" or your power button. It will not auto reboot on this step
Step3)
Once the device has rebooted, run Impactor again and connect over telnet just like in the previous step, then run the same command
Code:
dalvikvm -cp /sdcard/SlapMyMoto.jar SlapMyMoto
Once the device has rebooted, please take the 4.4 OTA.
Step4)
Now that we are on 4.4, we can finish the process with adb shell:
Code:
adb shell
cp /sdcard/install.sh /data/local/tmp/install.sh
chmod 755 /data/local/tmp/install.sh
echo "/data/local/tmp/install.sh" > /sys/kernel/uevent_helper
Then either wait, or toggle your bluetooth. Once the device reboots, you will have root.
Some times you have to manually reboot your device and also manually install SuperSU from the market place

Okay, I'm gonna try it again. What I'm seeing for myself as well as everyone else: fastboot camera update > rsd.
Should I root check before taking the ota to make sure everything's in working order? Especially when the times it's supposed to reboot on its own, don't.

byrdmang2 said:
Okay, I'm gonna try it again. What I'm seeing for myself as well as everyone else: fastboot camera update > rsd.
Should I root check before taking the ota to make sure everything's in working order? Especially when the times it's supposed to reboot on its own, don't.
Click to expand...
Click to collapse
nope just flash the 4.2.2 CU firmware and start the slapmymoto guide when u get to the end reboot after it boots up look for SU if not there install and open see if the binaries will install then check root.

Well sir, whatever method(s) I was/were using were obviously wrong or just bad, cause I got the 4.4 root!
I got kinda nervous when I had to manually reboot at the end and wait for supersu to install.
Thank you very much for your assistance! Thanks are in order :good:

byrdmang2 said:
Well sir, whatever method(s) I was/were using were obviously wrong or just bad, cause I got the 4.4 root!
I got kinda nervous when I had to manually reboot at the end and wait for supersu to install.
Thank you very much for your assistance! Thanks are in order :good:
Click to expand...
Click to collapse
glade your up and running

[TUTORIAL] Applying an OTA update with stock + root/custom recovery

Preamble
As the title suggests, I had a Nexus 5 running stock Android 5.0, with root and TWRP, and wanted to update to Android 5.0.1 (without losing all my data, of course). I couldn't find any guides for my particular circumstances, so after working out how to do it myself, I thought I'd share my method.
Note: This guide is not for the uninitiated. Be prepared to Google something for yourself if you don't understand it.
Prerequisites
Before starting this guide, you should have:
A Nexus 5 that running stock Android. The presence of root/Xposed/custom recovery (maybe custom kernels?) shouldn't be relevant, but I can't vouch for the efficacy of this guide if you've done something obscure to your install.
Android SDK tools, specifically the ADB and fastboot binaries. Additional USB drivers may be required on Windows.
The factory image for the Android version you are currently running.
1. Uninstall root and other /system modifications
If you have rooted your Android, and/or installed BusyBox, Xposed or other modifications to /system, you will need to uninstall these modifications. Failing to do so will cause the OTA to complain that there's something funky going on in your /system partition.
You may be able to manually uninstall each of these modifications, but this was not enough for my install – doing a ‘Full unroot’ in SuperSU still left behind files in /system. The easiest way to uninstall all /system modifications is to reflash the /system partition.
Extract the Nexus 5 factory image (e.g. hammerhead-lrx21o-factory-01315e08.tgz), yielding a directory with files such as flash-all.bat and image-hammerhead-XXXXXX.zip. Do not use the flash-all script, as this will unnecessarily wipe all data on the device.
Extract the image-hammerhead-XXXXXX.zip file, specifically the system.img file.
Open a command prompt/terminal window.
Connect the phone to the computer with a USB cable.
Boot the phone into the bootloader.
Method 1: Power down the phone, then hold VolUp + VolDn + Power until the phone boots into the bootloader.
Method 2: From the terminal, run adb reboot bootloader while the phone is still powered on.
From the terminal, run fastboot flash system /path/to/system.img.
2. Uninstall any custom recovery
Custom recoveries don't seem to support OTA updates, making it necessary to uninstall the custom recovery by reflashing the stock recovery.
Extract the recovery.img file from the factory image, as in Part 1.
Open a command prompt/terminal window, connect the phone to the computer, and boot into the bootloader, as in Part 1.
From the terminal, run fastboot flash recovery /path/to/recovery.img.
Optional: Reflash boot.img and/or cache.img
Some users have reported that reflashing system.img was not sufficient, and that reflashing boot.img and/or cache.img was also necessary. I did not have this problem, but if you do:
Extract the boot.img and/or cache.img files from the factory image, as in Part 1.
Open a command prompt/terminal window, connect the phone to the computer, and boot into the bootloader, as in Part 1.
From the terminal, run fastboot flash boot /path/to/boot.img.
From the terminal, run fastboot flash cache /path/to/cache.img.
3. Apply the OTA update
The simple part. In the bootloader, use the VolUp/VolDn buttons to select ‘Start’, then press the Power button, to reboot into Android. Follow the system update instructions to install the OTA update.
4. Reflash the custom recovery and re-root
Also self-explanatory.

Hey,
I just wanted to say thanks. This totally fixed the problem I was having. I also want to add that after I flashed the system.img, I was getting errors related to "EMMC:/dev/block/platform/msm_sdcc.1/by-name/boot" with a bunch of numbers after. I googled it and found I had to also flash boot.img, and after that, the OTA worked fine. I would assume if anyone else gets errors like this, they should flash whatever img it shows in the error (ie: mine said /by-name/boot so I flashed boot.img).
-BGM

It worked for me

I've always been using a toolkit for my rooting purposes, I have done Full Unroot on SuperSU, but still getting an error when trying to update to 5.0.1
Will flashing stock wipe everything(whatsapp image, camera's,messages, etc etc)on my phone?

azlan96 said:
I've always been using a toolkit for my rooting purposes, I have done Full Unroot on SuperSU, but still getting an error when trying to update to 5.0.1
Will flashing stock wipe everything(whatsapp image, camera's,messages, etc etc)on my phone?
Click to expand...
Click to collapse
I also had problems using ‘Full Unroot’ in SuperSU. It's not actually as ‘full’ as it sounds.
Flashing a full factory image would normally wipe everything, but carefully following this guide will only reset the /system partition, not any user data.

I'd like to say thank you very much! I was looking for this kind of tutorial... I encountered an error while following all the steps because I forgot I had a custom kernel. So I wanted to add that if you have a custom kernel remember to do the same steps as described above for the kernel (return to stock) and then follow the system and recovery steps afterwards.
If you don't like running commands in terminal you can use Nexus Root Toolkit, on advanced, you have all the commands you need available.
Thank you very much RunasSudo

Taiyo85 said:
I'd like to say thank you very much! I was looking for this kind of tutorial... I encountered an error while following all the steps because I forgot I had a custom kernel. So I wanted to add that if you have a custom kernel remember to do the same steps as described above for the kernel (return to stock) and then follow the system and recovery steps afterwards.
If you don't like running commands in terminal you can use Nexus Root Toolkit, on advanced, you have all the commands you need available.
Thank you very much RunasSudo
Click to expand...
Click to collapse
I have my ADB and Fastboot ok as confirmed by nexus root toolkit, but I am not sure on how to use terminal.. I launched command prompt but it doest recognise all the commands..
Tried Flash Stock + Unroot on Nexus Root Toolkit but the software will crash (fastboot.exe has stopped responding)
I am really clueless on what to do next..

azlan96 said:
I have my ADB and Fastboot ok as confirmed by nexus root toolkit, but I am not sure on how to use terminal.. I launched command prompt but it doest recognise all the commands..
Tried Flash Stock + Unroot on Nexus Root Toolkit but the software will crash (fastboot.exe has stopped responding)
I am really clueless on what to do next..
Click to expand...
Click to collapse
Flash Stock + Unroot wipes everything and defeats the purpose of the tutorial made by RunasSudo
First and foremost you should download Android SDK (Tools only) on http://developer.android.com/sdk/index.html and then ask to install the extra: Google USB Driver.
With Nexus Root Toolkit you don't need terminal, click on advanced and you should see options to flash through fastboot the system only, recovery and kernel. It is pretty straighforward and it asks where the .img are in your computer

Thanks! This guide worked.
For Ubuntu users, you need to install adb and fastboot with these commands :
sudo add-apt-repository ppahablet-team/tools && sudo apt-get update (optional)
sudo apt-get install android-tools-adb android-tools-fastboot

Thanks for the great step by step.
As with some of the other posters, re-flashing system.img was not enough for me, I had to also re-flash the boot.img. Once that was done, I had no problems side loading the update and am now running LRX22C.
I only seem to fiddle with adb once a year - when it OTA time comes - and can never seem to remember some of the steps that need to be taken. Reading through some of the other threads, I have a feeling a lot of people who rooted/custom recovery and cant do the OTA are going to be doing complete image re-flashes when this guide makes that completely unecessary.
thanks again,
.d

BananasGoMoo said:
I googled it and found I had to also flash boot.img, and after that, the OTA worked fine.
Click to expand...
Click to collapse
datcon said:
As with some of the other posters, re-flashing system.img was not enough for me, I had to also re-flash the boot.img.
Click to expand...
Click to collapse
Thanks for the feedback! I've added a note about boot.img to the OP.

+1 for flashing boot.img worked perfect after I did that.

I tried with this tutorial. I flashed system and recovery and then restart. Confirm OTA but I get ERROR.
Then I flashed boot as it was described. Now I don't get OTA In About phone, I'm still on 5.0.0, Check for updates now don't find update
Any idea?
UPDATE - UPDATE: After hour now it is here ... super, it works.

This walkthrough was most helpful! Ended up replacing the boot.img as well since I had ElementalX installed. My apps are optimizing as we speak. Thank you!

Worked for me. What a hassle!
Here is a summary of the process for those looking for a less wordy procedure, with a few added steps:
Download Nexus 5 5.0 (LRX21O) file (note: NOT 5.0.1 yet) https://developers.google.com/android/nexus/images
Unzip via 7-zip multiple times in order to get boot.img, recovery.img, system.img
Enable USB debugging: http://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android-5-lollipop.htm
Plug phone into PC > cmd prompt where adb is installed > type "adb devices" to ensure connection is valid (will need to authorize via popup on phone > then "adb devices" should return your device id and "device"; if it says "unauthorized" then look for the popup on your phone)
adb reboot bootloader
Put system.img, recovery.img, and boot.img in same folder as fastboot.exe
Run commands:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot erase cache (this is optional. I didn't have to do it, but you might)
Use Volume Up/Down to select Start > press Power Button to reboot
Update via Settings > About Phone > System Update
Re-flash TWRP recovery:
Get the file from here: http://forum.xda-developers.com/showpost.php?p=57580889&postcount=1
adb reboot bootloader
fastboot flash recovery openrecovery-twrp-2.8.1.0-hammerhead.img

Paul22000 said:
Worked for me. What a hassle!
Here is a summary of the process for those looking for a less wordy procedure, with a few added steps:
1. Download Nexus 5 5.0 (LRX21O) file (note: NOT 5.0.1 yet) https://developers.google.com/android/nexus/images
2. Unzip via 7-zip multiple times in order to get boot.img, recovery.img, system.img
3. Enable USB debugging: http://www.kingoapp.com/root-tutorials/how-to-enable-usb-debugging-mode-on-android-5-lollipop.htm
4. Plug phone into PC > cmd prompt where adb is installed > type "adb devices" to ensure connection is valid (will need to authorize via popup on phone > then "adb devices" should return your device id and "device"; if it says "unauthorized" then look for the popup on your phone)
5. adb reboot bootloader
6. Put system.img, recovery.img, and boot.img in same folder as fastboot.exe
7. Run commands:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
8. Use Volume Up/Down to select Start > press Power Button to reboot
9. Update via Settings > About Phone > System Update
Click to expand...
Click to collapse
Maybe you could add `fastboot erase cache` as stepp 8.

gee2012 said:
Maybe you could add `fastboot erase cache` as stepp 8.
Click to expand...
Click to collapse
I added it to step 7, thanks. :good: I also cleaned up the formatting and added step 10 about re-flashing TWRP.

Loading problem
I flashed system, recovery & boot images strictly following the instructions, restarted the phone. It got stuck in loading where balls in four colors keep running for half an hour. Shall I keep waiting? I think there must be something wrong. Your advises are welcome.

guangy said:
I flashed system, recovery & boot images strictly following the instructions, restarted the phone. It got stuck in loading where balls in four colors keep running for half an hour. Shall I keep waiting? I think there must be something wrong. Your advises are welcome.
Click to expand...
Click to collapse
Try flash the partitions again. If it's still not working, you may need to reflash a factory image.

RunasSudo said:
Try flash the partitions again. If it's still not working, you may need to reflash a factory image.
Click to expand...
Click to collapse
I flashed the cache image as well, then the problem solved. Thanks