Develop Bugs

[Q] Will installing new ROM wipe X-Parts CWM?

Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".
Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks

Artemicion said:
Hi, question: I failed time and again to get CWM working, but finally got it to work using x-parts. However, x-parts is keen to point out that it is not a fully fledged recovery and that "if you wipe the system partition for any reason, it will be gone!".
Does this not mean that if I boot into recovery and install a new ROM (Going for the FXP CM10 one, if it matters), then when I wipe the phone beforehand I'll also wipe my CWM install, thus completely bricking the device? Would appreciate any thoughts, thanks
Click to expand...
Click to collapse
Yes, if you wipe the system partition there will be no more CWM. For CM10, you need to flash a custom kernel for it to work. This custom kernel will usually come with a CWM recovery so it will not be wiped when you flash a new ROM.
僕のLT18iから送られてきた

Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?

Artemicion said:
Thanks. But, to clarify, once I flash new CM10/Jellybean Kernel, my current Gingerbread install will also completely cease to function right? And I'd need to flash back to something earlier to get it to work, if I so desired?
Click to expand...
Click to collapse
Is your bootloader unlocked?
And yes you will have to flash GB ftf using flashtool
Sent from my LT18i

Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.
So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks

Artemicion said:
Yeah, I unlocked the bootloader and rooted it ages ago, but have since neglected actually updating the ROM, decided I can't live in a GB world anymore though.
So, as I understand it, process would be flash a new GB kernel to get CWM > Wipe Everything > Install the relevant ROM and GApps > Done? Does this ROM installation include the update to JB kernel then? Thanks
Click to expand...
Click to collapse
If I am not mistaken the kernel boot img should be inside the ROM zip. Check the ROM zip. Just flash the boot img using fastboot, boot into CWM recovery and flash ROM & gapps.
僕のLT18iから送られてきた

Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:
fastboot -i 0xfce flash boot boot.img
doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks

fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium

Artemicion said:
Ah, ok, well this brings me full circle. Because I'm trying to follow the boot instructions to do so, but:
fastboot -i 0xfce flash boot boot.img
doesn't work. I've taken the boot.img out of the ROM, and put it in the platform-tools folder. But whenever I try this line, it says it can't boot it, and quotes "no error" (no longer at home so can't quote the exact error, but it's something like that). I assumed the problem was me lacking CWM, hence was trying to install that first. Fastboot devices DOES show the device, and both fastboot and adb commands work in a terminal, but I just can't get it to boot into the ROM recovery for Cyanogenmod. Driving my crazy! Thanks
Click to expand...
Click to collapse
You don't need to add -i 0xfce to the command. Just type fastboot flash boot <name of boot image>.img
僕のLT18iから送られてきた

tangosierra_ said:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Thanks, I'll give that a go, not going to be able to try for a few days now, but will. FYI, I took the line of code I was trying directly from the Cyanogenmod wiki for Anzu

tangosierra_ said:
fastboot flash boot boot.img, if I'm not mistaken, is the right command. I use flashtool
Sent from my Xperia Arc S using xda premium
Click to expand...
Click to collapse
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"
I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks

Artemicion said:
Ok, so finally got home to try this, still throwing this out: "error: cannot load 'boot.img': No error"
I've got the right boot.img in my platform-fools folder, the relevant CM build on my SD Root along with GApps. Drivers are definitely installed correctly as fastboot devices shows the device, as do adb command when it's on - anyone got any suggestions? Would be immensely grateful if this confounded problem could be solved. Thanks
Click to expand...
Click to collapse
What is the name of the .img file? It can't have any spaces inside.
僕のLT18iから送られてきた

popthosegaskets said:
What is the name of the .img file? It can't have any spaces inside.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Looks to just be "boot.img" to me, no spaces or anything.

Have you tried flashtool?
Sent from my LT18i using xda premium

tangosierra_ said:
Have you tried flashtool?
Sent from my LT18i using xda premium
Click to expand...
Click to collapse
No, guess I'll try that next. As I remember, that's what I used to flash in order to root it ages ago. Thanks

help android 4.3 stuck at google screen

Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...

antwong45157 said:
Hey I've been a long time lurker just haven't posted in forums because I haven't made enough posts Lol.
Well my question is in regards to paranoid android 4.3/3.94.
I've seen lots of people with same issue I havent figured out a fix.
Every 4.3 ROM I flash works fine, until reboot then I get stuck at Google screen. Can't backup or restore. Can't even reflash a 4.2.2. I HAVE to do a full wipe SD card and all, then use adB to sideload a rom.. I've flashed the newest primeD04 boot loader or whatever it is. Still the exact same issue.
I have twrp 4.2.2 I believe , maybe 4.2.0. If that helps..
Please help me I need to be on 4.3 .. And have had to do a full wipe more than 5 times Lol...
Click to expand...
Click to collapse
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?

Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?

antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
antwong45157 said:
I'm on toro. Verizon galaxy nexus.
Well to flash a 4.3 ROM.. I went into TWRP.. team in recovery program. Click factory reset, wipe system, cache and davlik.
Then flash 4.3 ROM, gapps and reboot.
After everything loads I try to reboot and I get stuck at Google screen... I have yet to wipe EVERYTHING because I just figured out how to use adb to side load zips.
Gonna try FULL WIPE SD card and everything then flash 4.3 using adb.
I'm on newest boot loader with fk01 and fk02 radios... Are those newest radios ?
Click to expand...
Click to collapse
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload

Woodyy said:
sooo you are on latest bootloader latest radio , allways full wipe and it still does that? try doing a full wipe from CWM recovery and flash it again, btw are you on maguro verizon or sprint?
Click to expand...
Click to collapse
Woodyy said:
Yep those are the latest radios for verizon, i am on maguro, no problems here... but it seams that there are lots of problems on verizon with 4.3 roms.
---------- Post added at 09:33 PM ---------- Previous post was at 09:25 PM ----------
Try to use latest CWM recovery and then full wipe from recovery, reinstall latest flashable bootloader, reboot in recovery again and flash again PA 3.94 and gaps without ADB sideload
Click to expand...
Click to collapse
Going to try to side load first with twrp. If all else fails gonna try cwm recovery

Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*

antwong45157 said:
Tried to side load with adb... No luck. Worked flawlessly until I rebooted then stuck on the Google screen. Please help!
*
*
*
Click to expand...
Click to collapse
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.

Woodyy said:
Ok, i want some info cuz i am allso confused).
1. what rom do you flash with adb sideload PA 3.94?
2. you said you cant flash 4.2.2 anymore?
3. if you use adb sideload you have the android sdk installed
4. if second and third point are true then use adb to wipe everything from the phone and download stock 4.2.2 img and flash from windows adb command prompt.
Click to expand...
Click to collapse
I tried flashing paranoid android 3.94 which is android 4.3 with adb. Hoping it would work different . Nope same result.
I am able to get back on 4.2.2 using adb. I'm on 4.2.2 typing this message . I just need to find out why I can't get on 4.3 with getting stuck at boot screen

This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app

Jewveeski said:
This is probably a silly question , but is your bootloader locked I have the gnex toro and it can get testy at times also try flashing this ROM its what I'm currently on and it works great no issues its stock rooted 4.3 follow the steps in the post
http://rootzwiki.com/topic/36706-ro...stock-android-43-jwr66v-no-bugs/#entry1031982
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I believe my boot loader is unlocked. When. I reboot I see he unlocked lock. But I did flash the new boot loader so maybe I would have to re unlock it? I will try the ROM you posted

Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!

itslels said:
Seems like a lot of the time people who are having this stuck at Google screen issue have flashed the new boot loader. Or am I just imagining things?
toro, toro!
Click to expand...
Click to collapse
I had the issue when I tried to go directly from 4.2.2 to a 4.3 custom. The only thing that cleared it up was flashing stock 4.3 from google. After that, no more problems.

Hmm wonder what could be causing it. I did have this issue going from 4.2.2 to 4.3. Every 4.3 ROM I have flashed has booted.
toro, toro!

I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )

antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
i have the same fuking problem , what did you do ?

antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Gz dude enjoy 4.3

antwong45157 said:
I solved my problem after reflashing the new boot loader and a new ROM reboot. Then power off. Battery pull then I wiped cache. I'm not sure exactly what the issue was but now I can load up any 4.3 ROM without a problem )
Click to expand...
Click to collapse
Thanks, I followed this and finally managed to get to 4.3
http://forum.xda-developers.com/showthread.php?t=2389721

Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
EDIT: I did a reboot when I got home and it booted up fine, although I felt like it took longer than on previous versions.

oynoy said:
Oh no... I installed PA 3.94 yesterday and everything seemed great. I didn't have any issues booting the first time (although it took a while), but now I'm afraid to reboot my phone in case it gets stuck at the boot screen like you guys are describing.
Click to expand...
Click to collapse
Gotta be able to reboot your phone brother lol. Give it a shot. If it locks up there is always a way to fix the issue... Good luck. Best wishes

FIX for issue getting stuck on google screen after 4.3 reboot
I don't know if anyone has posted this elsewhere. I had the same problem yesterday - after a lot of playing around this is how I fixed it:
***Note1: you need adb and fastboot.
***Note2: make external backup of things (i.e. photos) you want to keep using adb.
Procedure:
1. Download 4.2.2 image from google (can't post link because of spam prevention rules - you can search for "google developers nexus images")
2. extract files to location of choice
3. Download latest custom recovery image of your choice. I prefer TWRP (latest 2.6)
3. reboot to recovery, do a full factory reset (wipe everything, you will lose all your storage).
4. Reboot to bootloader (from phone off, power plus volume rocker).
5. flash stock image via fastboot (change names and paths acordingly):
Code:
fastboot devices (make sure fastboot can see your device)
adb reboot bootloader
fastboot flash bootloader bootloader-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio /path/to/radio-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot flash radio-cdma /path/to/radio-cdma-toro-<current_ver>.img
fastboot reboot-bootloader
fastboot -w update /path/to/image-mysid-<version>.zip
5. After this last step, the phone should reboot.
6. Go through the phone setup process.
7. power off, and boot to bootloader
8. flash custom recovery:
Code:
fastboot flash recovery /path/to/custom-recovery.img
9 reboot to recovery. TWRP will ask you if you want to root when you reboot to system.
10. Phone rooted and like new!
I think that is all - you can flash your ROM of choice after this!

[Q] 4.4.3 OTA failed after install Qualcomm-optimized Dalvik & Bionic libraries

Hello everyone,
Today my Nexus 7 2013 Wifi received 4.4.3 OTA, but the update failed (I didn't take note the detail error)
My Nexus 7 is running stock ROM 4.4.2, with optimized Dalvik and bionic libraries installed (using 4.4_qc-optimized_bionic.zip and 4.4_qc-optimized_dalvik.zip from thread:
http://forum.xda-developers.com/nexus-4/general/4-4-4-4-x-qualcomm-optimized-dalvik-t2546120
So I tried to use ClockworkMod to install the file df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip
But it failed with error: /system/bin/dalvikvm has unexpected contents
I've tried to revert back the libraries using KOT49E_stock_revert.zip in the above thread.
But the installation of df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip still failed with different error: /system/bin/installd has unexpected contents
Is there anyone encountered the same problem like mine?
Any suggestions? Thanks in advance!

Fastboot flash the system.img from the kot49h factory image and then try the update again.

/system/bin/installd has unexpected contents
meekrawb said:
Fastboot flash the system.img from the kot49h factory image and then try the update again.
Click to expand...
Click to collapse
Thanks for your suggestion! I've tried but still encountered /system/bin/installd has unexpected contents

nct2k said:
Thanks for your suggestion! I've tried but still encountered /system/bin/installd has unexpected contents
Click to expand...
Click to collapse
Are you sure you used the system.img from the 4.4.2 build? Also, how did you flash the system.img file. I recommend using fastboot mode to write it.
I ran into this same problem because I forgot I flashed Dalvik and Bionic. Same error in fact. I flashed the system.img rebooted and went straight back into recovery and pushed the update by ADB and it worked perfectly. Double check everything, because flashing the system.img should correct that error.

sola fide said:
Are you sure you used the system.img from the 4.4.2 build? Also, how did you flash the system.img file. I recommend using fastboot mode to write it.
I ran into this same problem because I forgot I flashed Dalvik and Bionic. Same error in fact. I flashed the system.img rebooted and went straight back into recovery and pushed the update by ADB and it worked perfectly. Double check everything, because flashing the system.img should correct that error.
Click to expand...
Click to collapse
Yes, I used fastboot flash recovery recovery.img (extracted from razor-kot49h-factory-ebb4918e.tgz)
then used adb sideload df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip when the Nexus is in stock recovery mode
I've switched to TWRP (openrecovery-twrp-2.7.1.1-flo.img), same error.
BTW, did you apply the KOT49E_stock_revert.zip before the sideload?

nct2k said:
Yes, I used fastboot flash recovery recovery.img (extracted from razor-kot49h-factory-ebb4918e.tgz)
then used adb sideload df43279bcf6bb6a0ae403249c3e6f314d0a7eb77.signed-razor-KTU84L-from-KOT49H.df43279b.zip when the Nexus is in stock recovery mode
I've switched to TWRP (openrecovery-twrp-2.7.1.1-flo.img), same error.
BTW, did you apply the KOT49E_stock_revert.zip before the sideload?
Click to expand...
Click to collapse
After flashing recovery.img you also need to flash system.img pulled from the same tar file. That's why you're still getting the error. Only flashing the recovery file won't write over what the Dalvik and Bionic files edited.

sola fide said:
After flashing recovery.img you also need to flash system.img pulled from the same tar file. That's why you're still getting the error. Only flashing the recovery file won't write over what the Dalvik and Bionic files edited.
Click to expand...
Click to collapse
In other words - ALL the OTA things can only work on 100% STOCK system. Personally, I used the WUG tool kit to flash a complete NEW, CLEAN, STOCK 4.4.3 (of course that does do a reset of the entire machine)...
You MIGHT be able to put back the stock runtime files that were changed and then do the update so you don't have to go "cold turkey", but my guess is that even that won't allow a update...For the amount of changes, you might just be better off sticking with 4.4.2
Good luck...

My bad, flash system.img is enough, don't need to touch the recovery. Completed the upgrade and all my data retained.
Thanks a lot guys! :laugh:

Is there anyway I can flash the system.img without any PC? I don't have access to any PC now and stuck on this installd error. Can't update to 4.4.3.

Wrong build fingerprint when flashing ota

I've downloaded the ota zip and ready to flash it in twrp. But when I flash it, it shows an error saying my device have wrong build number. I'm very sure that i have kitkat ktu84p but when flashing the ota it says i have the previous jelly bean build which makes my flash unsuccessful. I've also checked build.prop and its also listed there its ktu84p. Whats the problem here and if possible show a solution please

ImjuzCY said:
I've downloaded the ota zip and ready to flash it in twrp. But when I flash it, it shows an error saying my device have wrong build number. I'm very sure that i have kitkat ktu84p but when flashing the ota it says i have the previous jelly bean build which makes my flash unsuccessful. I've also checked build.prop and its also listed there its ktu84p. Whats the problem here and if possible show a solution please
Click to expand...
Click to collapse
See it this thread helps
http://forum.xda-developers.com/nex...-qa/flashing-lollipop-ota-twrp-fails-t2939358

jj14 said:
See it this thread helps
http://forum.xda-developers.com/nex...-qa/flashing-lollipop-ota-twrp-fails-t2939358
Click to expand...
Click to collapse
Thanks for the link. Now i can conclude that the ota doesnt work with custom recoveries. Tried twrp and cwm. Twrp shows jelly bean fingerprints but cwm shows another kitkat fingerprint rather than ktu84p thats suppose to be

ImjuzCY said:
Thanks for the link. Now i can conclude that the ota doesnt work with custom recoveries. Tried twrp and cwm. Twrp shows jelly bean fingerprints but cwm shows another kitkat fingerprint rather than ktu84p thats suppose to be
Click to expand...
Click to collapse
Wonder if you are using an outdated TWRP version. Maybe the newer versions have fixed this

jj14 said:
Wonder if you are using an outdated TWRP version. Maybe the newer versions have fixed this
Click to expand...
Click to collapse
I dont think so cause ive just updated it to 2.8.1.0 which is the newest by now

I tried everything and still get wrong build fingerprint when trying to flash the 5.0
ImjuzCY said:
I dont think so cause ive just updated it to 2.8.1.0 which is the newest by now
Click to expand...
Click to collapse
Hello!
Really want to flash the OTA without a total wipe.
First flashed it from TWRP 2.8.1.0 and got the wrong build finger print says I have Flo:4.3/JSS15Q/779366 and it expects KTU84P/1227136
Then using WugFresh 1.9.4 flashed stock recovery so I could sideload then encountered the whole adb disappearing in recovery - eventually solved that and finally managed to adb sideload saw my screen saying it was installing the update using the stock recovery - YAY! It was short lived as the stock recovery screen told me the exact same thing that TWRP had told me.
I looked at my build.prop and it says my ro.build.fingerprint=google/razor/flo:4.4.4/KTU84P/1227136. user/release-keys
Can someone enlighten me? I've wasted so much time on this I would love some keen insight - PLEASE!!
Thanks for any and all help!
Edbogue

Google changed the way OTAs work in 5.0. You will usually not be able to flash a OTA if your OS is modified. Means no custom recovery or root. You will have to flash your tab back to stock kitkat.
Before it would patch individual file blocks, now it patches the whole system partition as a blob. Read more http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/

Workaround that helped me upgrade
Following the steps below seems to have done the trick for me. My issue was that Android 5.0 updates the system partition all in one go now, rather than each file separately. Following those steps will unroot your device but will allow you to install the OTA updates.
So follow these steps to refresh your current Android version (e.g 4.4.4) then use OTA or adb sideload to update to, for example, 5.0.
This will not wipe user data or the cache.
Download the Factory Image for your current version of android from google (4.4.4 most likely)
Extract each level of compressed files until you get to a .zip file (inside will be boot.img, recovery.img, and system.img)
Move these files to your ADB directory (optional step, makes the commands shorter)
make sure your device is connected with working drivers and is in bootloader mode ( adb reboot bootloader )
perform the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
Finally, (Re)start the system
After this if you want to root and reinstall a custom recovery , follow the normal steps.
I would post my source, but as I only just joined to say what helped me, I'm not allowed to post links I'll just say Google "flashing-a-stock-android-image-without-wiping-user-data" and (as of 19/11/2014) it's the top result.

Please continue here: http://forum.xda-developers.com/nexus-4/help/android-5-0-0-to-5-0-1-update-t2972371#post57515317

Finally finally!!! A fix!
Raingram said:
Download the Factory Image for your current version of android from google (4.4.4 most likely)
Extract each level of compressed files until you get to a .zip file (inside will be boot.img, recovery.img, and system.img)
Move these files to your ADB directory (optional step, makes the commands shorter)
make sure your device is connected with working drivers and is in bootloader mode ( adb reboot bootloader )
perform the following commands:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img
Finally, (Re)start the system
After this if you want to root and reinstall a custom recovery , follow the normal steps.
.
Click to expand...
Click to collapse
Thank you Raingram! This worked perfectly!

[Q] 5.0.1 Rooted to 5.0.2 Without Data Loss

For some reason I'm just not able to Google this answer or find it here on XDA.
I'm on 5.0.1 (LRX22C) and want to go to 5.0.2 (LRX22G). I have downloaded an OTA update capture and tried to adb sideload it.
It failed. After a sec I thought, "duh. I'm rooted with franco kernel installed." I then did the following:
* Used SuperSU to unroot
* Booted to bootloader
* Flashed stock recovery and kernel
* Rebooted to recovery
* Attempted adb sideload again
This still gave a failure message.
The only other post I've seen where anyone is attempting the same suggests to use Nexus Root Tookit. I'm running Xubuntu. I've loaded it through wine but all the files it downloads are failing hash checks (though the app).
Can anyone post how to go from rooted 5.0.1 to 5.0.2 (LRX22G from LRX22C) without loosing user land data? I'd really do not want to flash the recovery image.
Notes: When trying to sideload with latest CWM recovery the script says that I'm on 4.0.4 (I think) and with TWRP it says I'm on 4.3. With stock recovery it gives me an error about the recovery script (7) or something similar.
Thanks,
Mike G.

Make sure you have downloaded the proper OTA for Nexus 7(2013).
Hashcheck fails in Nexus Root Toolkit is common.After Hashfails,there will be a dialog box which contains the steps to do it manually with the Link to the files.Download it & follow the instruction.
I hope this helps

I'm having the exact same problem. I'm attaching what's appearing on TWRP.

All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.

I just used wugfresh's toolbox to do it. A piece of cake. I enjoyed a cup of coffee while I watched being updated.

You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.

yosmokinman said:
All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
So I can just ”fastboot flash system system.img" from the 5.0.2 image and not loose data?
That seems like it would be the easiest. I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Sent from my Nexus 7 using XDA Free mobile app

^Yes. It's a good idea to flash boot as well just to get in the habit of it, it didn't change this time I don't think but I could later. Only flash the bootloader if it's a new version no need otherwise.
I simply ran:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Done, flash su through twrp to get root back.
You probably don't need to format cache but theres no reason not to and it could save you some trouble.

newkydawg said:
You can also use TWRP and dirty flash the stock, rooted rom by Scrolser found here: http://forum.xda-developers.com/nex.../rom-factory-stock-rooted-rom-lrx22g-t3004110 . Simple and fast with no data loss.
Click to expand...
Click to collapse
that worked perfectly for me. thx

mikejr83 said:
I prefer the adb/fastboot commands as NRT hides what it is doing and I like to know what's going on when I "do something" liken push a button.
Click to expand...
Click to collapse
NRT opens a terminal window (a real-time log) and tells you exactly what it's doing while it does its work.

All you need to do is flash the boot and system.img
Then flash su from twrp. It's that easy. No data loss.
Click to expand...
Click to collapse
I have a n7 2013 I have already rooted and installed twrp and SuperSU. I'm currently running 4.4.2 and to update to 5.02. Currently I'm getting the ota update msg for 4.4.3 which I've continued to ignore. With google not messaging me to update to 5.02 makes me think it's required to go to 4.4.3,4.4.4,5,5.02 is that correct? Or can one jump directly to 5.02? I want to keep root and twrp and my existing data I see mentioning of restoring stock recovery first. Why would one do that? What's the point of installing a custom recovery in the first place?
Long time ago I read that ota will work when rooted, but you'll lose root which then can be restored with twrp without losing data. Is that no longer true? Or is it only true of KitKat but not lollipop?