Hi guys,
I've been having some persistent trouble with my device and have been advised to reflash to see if that fixes my problems. Someone suggested to me on a previous thread that it was possible to do this without erasing all my data and apps and such, but I had always thought that reflashing (following, for example, these instructions) would wipe my phone completely. Am I just completely wrong or is there a different method which avoids wiping the phone.
The exact advice I was given is as follows:
Fastboot flash the images separately. Don't flash the userdata.img. Will keep your data.
Click to expand...
Click to collapse
My confusion is really with the statement "fastboot flash the images separately" - the only image I had thought to flash was a fresh copy of the stock 5.1 ROM I'm running, and surely this would wipe the phone?
Apologies if I'm missing something obvious - I'm still very new to the business of rooting and custom ROMs.
EDIT: Forgot to mention, I'm running stock 5.1 ROM over the latest leankernel (on an N6 of course).
christensen6 said:
Hi guys,
I've been having some persistent trouble with my device and have been advised to reflash to see if that fixes my problems. Someone suggested to me on a previous thread that it was possible to do this without erasing all my data and apps and such, but I had always thought that reflashing (following, for example, these instructions) would wipe my phone completely. Am I just completely wrong or is there a different method which avoids wiping the phone.
The exact advice I was given is as follows:
My confusion is really with the statement "fastboot flash the images separately" - the only image I had thought to flash was a fresh copy of the stock 5.1 ROM I'm running, and surely this would wipe the phone?
Apologies if I'm missing something obvious - I'm still very new to the business of rooting and custom ROMs.
EDIT: Forgot to mention, I'm running stock 5.1 ROM over the latest leankernel (on an N6 of course).
Click to expand...
Click to collapse
The information you were given is correct. You can flash all the images separately, excluding the userdata image, and you won't lose data. You will, have to root again and reflash TWRP.
The_Merovingian said:
The information you were given is correct. You can flash all the images separately, excluding the userdata image, and you won't lose data. You will, have to root again and reflash TWRP.
Click to expand...
Click to collapse
So just to clarify:
From my rooted device (without unrooting first) I could follow the instructions in, for example, the link I posted above to fastboot flash just the stock ROM and end up with a working (but now unrooted) phone with all my data?
I would then have to re-root and install TWRP though, which **would** wipe my data.
Correct?
Sorry to be persistent, I just don't wanna brick my new baby!
christensen6 said:
So just to clarify:
From my rooted device (without unrooting first) I could follow the instructions in, for example, the link I posted above to fastboot flash just the stock ROM and end up with a working (but now unrooted) phone with all my data?
I would then have to re-root and install TWRP though, which **would** wipe my data.
Correct?
Sorry to be persistent, I just don't wanna brick my new baby!
Click to expand...
Click to collapse
I understand your persistence, no need to be sorry. Yes, that is precisely the procedure.
christensen6 said:
So just to clarify:
From my rooted device (without unrooting first) I could follow the instructions in, for example, the link I posted above to fastboot flash just the stock ROM and end up with a working (but now unrooted) phone with all my data?
I would then have to re-root and install TWRP though, which **would** wipe my data.
Correct?
Sorry to be persistent, I just don't wanna brick my new baby!
Click to expand...
Click to collapse
Re-rooting and installing TWRP should not wipe your data (assuming you already have an unlocked bootloader). Also, if you do not fastboot flash the recovery.img file, you will maintain your current recovery. Someone please correct me if I am wrong!
kevinga said:
Re-rooting and installing TWRP should not wipe your data (assuming you already have an unlocked bootloader). Also, if you do not fastboot flash the recovery.img file, you will maintain your current recovery. Someone please correct me if I am wrong!
Click to expand...
Click to collapse
So basically rather than running:
fastboot flash-all
Click to expand...
Click to collapse
I should just run something like:
fastboot flash [<filename>]
Click to expand...
Click to collapse
Where filename will include "boot.img", "cache.img", "system.img" and "radio-shamu....etc.... .img" but NOT bootloader.img or recovery.img or userdata.img" And hopefully all will be well?
EDIT: Particularly unclear as to whether I have to flash the bootloader image first (and then reboot into bootloader) before reflashing the radio, boot, cache and system images, or whether I can leave the bootloader as is (currently unlocked).
EDIT 2: Found a pretty comprehensive guide to my exact problem on reddit for anyone who needs help with this in the future!
christensen6 said:
So basically rather than running:
I should just run something like:
Where filename will include "boot.img", "cache.img", "system.img" and "radio-shamu....etc.... .img" but NOT bootloader.img or recovery.img or userdata.img" And hopefully all will be well?
EDIT: Particularly unclear as to whether I have to flash the bootloader image first (and then reboot into bootloader) before reflashing the radio, boot, cache and system images, or whether I can leave the bootloader as is (currently unlocked).
Click to expand...
Click to collapse
Follow method #2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Excluding the factory reset of course.
Related
Hello friends!
I want to share some information for the beginners here:
While there is the Nexus 4 factory image for KitKat available, there still are non known OTA urls.
But you can flash KitKat anyway AND keep your data (as long as you have an unlocked bootloader):
1. Download the factory image from here:
https://developers.google.com/android/nexus/images?hl=de#occamkrt16o
2. extract ALL the files contained into the same directory where your fastboot.exe is saved, for unpacking I recommend using 7zip
3. boot your phone into bootloader
4. type in the following commands:
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
You're done, KitKat on your Nexus 4, your apps and data still available!
Note: Your phone has to be full stock!!!!
UPDATE:
I'm really sorry for the mistakes I made in this thread.
I corrected them all by now, I think.
To make it more easy for you: You can rename the radio and the bootloader files let's say to radio.img and bootloader.img. Then use the fastboot commands with these new names. So you're a bit more safe not to make spelling errors.
Once again: I am sorry and I hope nobody got stuck due to my mistakes!!!
Some errors here.
random hero said:
fastboot flash bootloader bootloader-mako-makoz10o.img
Click to expand...
Click to collapse
Should be
fastboot flash bootloader bootloader-mako-makoz20i.img
random hero said:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
Click to expand...
Click to collapse
Should be
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84
random hero said:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Skip this if you dont want your custom recovery to be stock again. :good:
random hero said:
Hello friends!
I want to share some information for the beginners here:
While there is the Nexus 4 factory image for KitKat available, there still are non known OTA urls.
But you can flash KitKat anyway AND keep your data (as long as you have an unlocked bootloader):
1. Download the factory image from here:
https://developers.google.com/android/nexus/images?hl=de#occamkrt16o
2. extract ALL the files contained into the same directory where your fastboot.exe is saved, for unpacking I recommend using 7zip
3. boot your phone into bootloader
4. type in the following commands:
fastboot flash bootloader bootloader-mako-makoz10o.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
You're done, KitKat on your Nexus 4, your apps and data still available!
Note: Your phone has to be full stock!!!!
Click to expand...
Click to collapse
If you're making a guide, make sure you give people the correct commands (the numbers of the bootloader and radio are wrong). Not to mention there already is a guide where flashing the update without losing data is explained.
http://forum.xda-developers.com/showthread.php?t=2527142
vanmarek said:
If you're making a guide, make sure you give people the correct commands (the numbers of the bootloader and radio are wrong). Not to mention there already is a guide where flashing the update without losing data is explained.
http://forum.xda-developers.com/showthread.php?t=2527142
Click to expand...
Click to collapse
The numbers of radio & bootloader in Factory image itself are wrong
I am sorry for the two "spelling errors". I corrected them, should be all fine now.
I did not notice that the other guide contains information about flashing KitKat without losing all your data...
sometimes it can be hard to keep an eye on all the threads in every detail...
fastboot flash bootloader bootloader-mako-makoz10i.img still wrong should be 20 instead of 10
Don't really want go threw all that ..
dose somebuy just have image I can flash without having to use the above
I want down load the Image
Boot into Recovery and Flash the Image with Team win Project
Then Reboot
Onknight said:
Don't really want go threw all that ..
dose somebuy just have image I can flash without having to use the above
I want down load the Image
Boot into Recovery and Flash the Image with Team win Project
Then Reboot
Click to expand...
Click to collapse
there are some stock images with root on android develop or orig android develop.
edit: can use dd command to flash images if u have root.
do dd if=/block of/img
like dd if=/dev/block/platform/by-name/system /data/media/0/download/images/zipextracted/system.img
opssemnik said:
fastboot flash bootloader bootloader-mako-makoz10i.img still wrong should be 20 instead of 10
Click to expand...
Click to collapse
Again sorry for that... updated. Thank you!
"I'm really sorry for the mistakes I made in this thread.
I corrected them all by now, I think.
To make it more easy for you: You can rename the radio and the bootloader files let's say to radio.img and bootloader.img. Then use the fastboot commands with these new names. So you're a bit more safe not to make spelling errors."
I thought it was excellent! Anyone who knows what they are doing in the Command Prompt/Terminal understands that they can hit the Tab key to auto-complete the filename. Its up to them to make sure they are accessing their correct folder/file name, not yours!
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
7zip is free, winrar is not.
maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
In my opinion 7Zip looks slightly better and it doesn't spam you with that your trial is over every time you open it.
what to do with a custom rom?
I have PA on my N4 and was wondering what to do to get KitKat? is the procedure similar or different?
Thanks a lot!
maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
7zip is far more friendly towards archives other than rar and zip formats. it's also the only archive app I've found that will allow you to open a flashable zip or apk and replace files inside (like an icon's image file, for example) without having to actually decompile/recompile either the zip or apk (assuming you don't change too much with either file-type)
mad_zack said:
I have PA on my N4 and was wondering what to do to get KitKat? is the procedure similar or different?
Thanks a lot!
Click to expand...
Click to collapse
whether it's a custom or stock rom does not matter. the procedure will be the same either way
Upgrading 4.2>4.3>4.4 was always a piece of cake with Wug toolkit and never had to reinstall any application.
Keeping my settings and applications was important for me.
Sent from my NookColor using Tapatalk 4
how is this method different from if i just removed the -w wipe parameter?
maverickronny said:
how is this method different from if i just removed the -w wipe parameter?
Click to expand...
Click to collapse
the method you refer to will still install the userdata.img file, which will wipe your rom's userdata, as well as anything on your storage partition. The method mentioned in this thread's OP omits the userdata.img file and relies on the user manually wiping the rom data in n custom recovery, therefore wiping only rom data while leaving the storage partition untouched.
Confused as to why people take all these steps when its just unlock>flash recovery>Flash update rom of your choice and done. All these threads on the same thing makes no sense and lets be honest its not that hard to keep up with threads if you search extensively prior to making up a thread which at week three of KitKat you should of thought would be up already.
Not flaming anyone just trying to understand the thought process. Mistakes happen I get it but we got to do better especially with so many people destroying their phones over simple things.... Jus Sayin'
hp420 said:
the method you refer to will still install the userdata.img file, which will wipe your rom's userdata, as well as anything on your storage partition. The method mentioned in this thread's OP omits the userdata.img file and relies on the user manually wiping the rom data in n custom recovery, therefore wiping only rom data while leaving the storage partition untouched.
Click to expand...
Click to collapse
I updated from 4.3 to KRT16O (and later, KRT16S) by omitting the "-w" from the batch file, and I didn't lose a byte of userdata. My bootloader is unlocked, but everything else is stock.
It was so painless, I wonder why I ever bothered waiting for OTAs in the first place.
Hi all, I'm at a loss here as I've tried everything I could think of. I've completely reflashed everything using fastboot to the stock 4.4.2 image, wiped userdata and cache and when I go to install the system update I get an error and it's unsuccessful. What am I missing or doing wrong? Thx
hlaalu said:
Hi all, I'm at a loss here as I've tried everything I could think of. I've completely reflashed everything using fastboot to the stock 4.4.2 image, wiped userdata and cache and when I go to install the system update I get an error and it's unsuccessful. What am I missing or doing wrong? Thx
Click to expand...
Click to collapse
Just use the FXZ instead....
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
@hlaalu : EDIT - WAIT. I assumed you were on the Verizon DEV editon.
On the GSM Unlocked Dev edition??? Don't flash that FXZ!
What device are you on???
samwathegreat said:
Just use the FXZ instead....
http://forum.xda-developers.com/moto-x/general/fxz-moto-x-4-4-4-212-55-26-t2827307
@hlaalu : EDIT - WAIT. I assumed you were on the Verizon DEV editon.
On the GSM Unlocked Dev edition??? Don't flash that FXZ!
What device are you on???
Click to expand...
Click to collapse
I AM on Verizon, thanks for checking. I have no idea what the FXZ is but I'm a little concerned with the big red warning.
hlaalu said:
I AM on Verizon, thanks for checking. I have no idea what the FXZ is but I'm a little concerned with the big red warning.
Click to expand...
Click to collapse
HAHA! Just between you and me -- EVERY FLASHABLE FILE on XDA should have that warning. The problem is that people fail to read or follow instructions. They will flash wrong carrier's roms, attempt to downgrade, etc. Either of which can end up bricking your device - in a heartbeat.
Anyways that FXZ is the FULL factory image -- straight from Motorola, signed with release keys. There's nothing safer. Flashing the FXZ is much safer even than taking the OTA, because it actually replaces (and hence can repair a corrupted/damaged filesystem) all partitions instead of just doing an incremental update (like an OTA).
This particular FXZ is a "keep data" FXZ, meaning it will do the same thing as the OTA - only difference is you will need to re-root afterwards. All your data will still be intact. If you are using Xposed, you will also need to re-install it, but any modules you had installed will keep their respective settings.
Good Luck. That is EXACTLY what you need...
samwathegreat said:
HAHA! Just between you and me -- EVERY FLASHABLE FILE on XDA should have that warning. The problem is that people fail to read or follow instructions. They will flash wrong carrier's roms, attempt to downgrade, etc. Either of which can end up bricking your device - in a heartbeat.
Anyways that FXZ is the FULL factory image -- straight from Motorola, signed with release keys. There's nothing safer. Flashing the FXZ is much safer even than taking the OTA, because it actually replaces (and hence can repair a corrupted/damaged filesystem) all partitions instead of just doing an incremental update (like an OTA).
This particular FXZ is a "keep data" FXZ, meaning it will do the same thing as the OTA - only difference is you will need to re-root afterwards. All your data will still be intact. If you are using Xposed, you will also need to re-install it, but any modules you had installed will keep their respective settings.
Good Luck. That is EXACTLY what you need...
Click to expand...
Click to collapse
Thanks I'll give that a shot. Too bad I didn't see this earlier, all my data has been wiped...repeatedly lol. Custom recovery will still be flashed using fastboot after FXZ?
hlaalu said:
Thanks I'll give that a shot. Too bad I didn't see this earlier, all my data has been wiped...repeatedly lol. Custom recovery will still be flashed using fastboot after FXZ?
Click to expand...
Click to collapse
Precisely. After successfully booted to android (and you verify all is well), go back to bootloader, and:
fastboot flash twrpfilename.img
(get the latest version here: http://techerrata.com/browse/twrp2/ghost )
Then immediately after flashing it, type:
fastboot reboot-bootloader
then VOL DOWN to Recovery, and VOL UP to enter it. Once in, click exit. It will offer to root for you.....
(you MUST enter into TWRP immediately after flashing it [before booting into android again] -- if you don't it won't "stick" and will revert to stock recovery. As long as you immediately boot into TWRP after flashing it, it will "stick" forever....or until you flash something else to recovery. It is unknown why this happens, but the solution is easy enough....)
Up and running again, thanks a bunch for all the help!
Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash the OTA LRX21O (I'm on LNX07M) in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
RandoTheKing said:
Yesterday I recieved my phone and I unlocked the bootloader as well as rooted using CF. Today I tried to flash LRX21O in TWRP but I'm getting the error "Package expects build fingerprint of google/shamu/shamu:5.0/LNX07M/1543455: user/release-keys or google/shamu/shamu : 5.0/LRX210/1570415 : user/release-keys; this device has Android/aosp_shamu/shamu:5.0LRX21M/dees_troy11191312:userdebug/test-keys"
What the heck does this mean? I also tried flashing back to stock recovery but it just ended up with an android image with "error" below it. I'm assuming it ran into the same problem. Do I need to wipe and start all over??
Click to expand...
Click to collapse
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
akellar said:
You can't install the OTA if you rooted. You'll probably need to just install the factory images via fastboot.
Click to expand...
Click to collapse
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
RandoTheKing said:
I thought you could always just flash them manually? When did this change? No point in rooting if I'm going to stay stock, it seems.
Click to expand...
Click to collapse
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
well what will you do for future updates? Full wipe?
RandoTheKing said:
well what will you do for future updates? Full wipe?
Click to expand...
Click to collapse
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Dr Faustus said:
5.0 essentially makes it break OTA when you root/modify anything. This has been known for a bit now (which is why I downloaded the update before I did any rooting/unlocking on my device).
Click to expand...
Click to collapse
jj14 said:
http://www.androidpolice.com/2014/1...e-means-update-will-fail-system-modified-way/
not really - you can just flash the "old" stock system image file and then install the update (or just flash the "new" system file)
Click to expand...
Click to collapse
Any instructions on how to do that? I'm assuming I can still get the update that way
RandoTheKing said:
Any instructions on how to do that? I'm assuming I can still get the update that way
Click to expand...
Click to collapse
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Edit - flash the cache.img instead of just erasing cache
I had trouble flashing the factory image initially. I kept getting an error so I used this method and it worked perfectly. Hope it helps. http://www.ibtimes.co.uk/how-fix-er...roid-5-0-factory-images-nexus-devices-1474865
So i am root and have done a bit of work on my Nexus 6 (changing system sounds, setting it up and a few other things) If i want to install LRX21O, what is the step by step to do that and after i install it if i do a Nandroid Backup, can i restore the backup on LRX21O? I am currently on LNX07M.
I am curious as well. Also do you happen to have a link to the file to just update.?
EDIT... Found it. Will flash when home
Sent from my Nexus 6 using XDA Free mobile app
jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
Click to expand...
Click to collapse
Should that be `fastboot format cache`?
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
Actually, you should just flash the cache.img
jj14 said:
It should be the same as the "back to stock" process
Download new (or old) factory images
Unzip and extract the IMG files
Take nandroid backup on phone
Reboot to recovery
Connect to PC (assuming drivers are installed)
Use fastboot to flash the necessary images
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot erase cache
You don't reboot into recovery if you are using fas boot. You boot into boot loader at least that's how I've done it on every Nexus that I've had.
Edit - flash the cache.img instead of just erasing cache
Click to expand...
Click to collapse
jm77 said:
Should that be `fastboot format cache`?
Click to expand...
Click to collapse
You can use both commands to first format, then flash the new one it doesn't really matter. I've used both methods
jj14 said:
Actually, you should just flash the cache.img
Click to expand...
Click to collapse
Is there a way to sideload the 5.1 update (downloaded from the google images page) without losing the CF root AND not losing any of my system settings and configurations?
Thanks in advance.
LordGrahf said:
Is there a way to sideload the 5.1 update (downloaded from the google images page) without losing the CF root AND not losing any of my system settings and configurations?
Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
Edit after rereading this http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I would prob also do the reboot step after radio flash.
Maybe what your lookin for. If rooting is lost simply redo the cf root process and flash your custom recovery via fastboot. Most importantly this route will prevent data loss. I am going this route but will still backup because its safer and more responsible.
Without a modified img, and using the google provided stuff, you can't keep root. Just re-root, it's not hard.
Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
3. If I'm not losing my installed apps, what would happen to my root-required apps? For example I HAVE LMT pie control installed and configured. Would reinstalling root make it work as before without the need to reinstall and reconfigure LMT?
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
5. What is the minimal set of the update's images can I use to get this update? Like I think I should probably skip the user.img if I don't want my user settings to be wiped out, correct? What other images should I skip in order to not wipe out apps, apps settings, and system settings.
Thank you very much
LordGrahf said:
Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
3. If I'm not losing my installed apps, what would happen to my root-required apps? For example I HAVE LMT pie control installed and configured. Would reinstalling root make it work as before without the need to reinstall and reconfigure LMT?
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
5. What is the minimal set of the update's images can I use to get this update? Like I think I should probably skip the user.img if I don't want my user settings to be wiped out, correct? What other images should I skip in order to not wipe out apps, apps settings, and system settings.
Thank you very much
Click to expand...
Click to collapse
If doing the fastboot way like I linked (I have not read through the procedure for sideload, so I don't know)
1) no
2) no if you only flash some of the IMG files. For your purpose it seems (I'm also assuming you don't have custom kernel) these are the ones to not lose data. Make sure you follow the links in how to flash this correctly with the appropriate order and spots where to fastboot reboot.
Bootloader image
Radio image
Boot image (kernel)
Cache image
System image
Recovery image
Then reroot with the cf zip like before then reinstall the su app.
4) no we flash the new stock recovery too
5) minimal, to not overwrite the user data, above. Yup we skip the user data image
LordGrahf said:
Thanks guys. Few questions:
1. Do I need to unroot before sideloading the update?
2. Would I loose my currently installed and configured apps?
Click to expand...
Click to collapse
No.
LordGrahf said:
3. If I'm not losing my installed apps, what would happen to my root-required apps?
Click to expand...
Click to collapse
You'll have to install su since it was deleted by system.img but that's all. Note that last time I looked CF-Auto still said it was 5.0.1 but ...
LordGrahf said:
4. I'm still using stock recovery, would that affect what I'm trying to do in any way?
Click to expand...
Click to collapse
If you install a current TWRP it will install super-su for you when you request a reboot.
LordGrahf said:
5. What is the minimal set of the update's images can I use to get this update?
Click to expand...
Click to collapse
Everything except user.img. You can read or run flash-base to get the Google suggested initial ordering.
MunkinDrunky said:
http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
Edit after rereading this http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008 I would prob also do the reboot step after radio flash.
Maybe what your lookin for. If rooting is lost simply redo the cf root process and flash your custom recovery via fastboot. Most importantly this route will prevent data loss. I am going this route but will still backup because its safer and more responsible.
Click to expand...
Click to collapse
I flashed the bootloader, but the command to flash the radio (fastboot flash radio radio-shamu-d4.0-9625-02.95.img) failed
Any idea?
Nikos2k said:
I flashed the bootloader, but the command to flash the radio (fastboot flash radio radio-shamu-d4.0-9625-02.95.img) failed
Any idea?
Click to expand...
Click to collapse
I don't really know. I usually just follow instructions. Did you fastboot reboot after flashing bootloader?
MunkinDrunky said:
I don't really know. I usually just follow instructions. Did you fastboot reboot after flashing bootloader?
Click to expand...
Click to collapse
Yes, I rebooted the boot loader (and it indeed showed the new boot loader version after the reboot)
After the fail message of the radio flash command, I rebooted to the system, it works, and from the baseband number in settings/about, it seems that the new radio has been flashed (besides the fail message)
Nikos2k said:
Yes, I rebooted the boot loader (and it indeed showed the new boot loader version after the reboot)
After the fail message of the radio flash command, I rebooted to the system, it works, and from the baseband number in settings/about, it seems that the new radio has been flashed (besides the fail message)
Click to expand...
Click to collapse
hmm yeah i really dont know why that happend. I guess as long as the new radio shows up as you say then it worked. I will actually be doing this shortly, since i am now at a computer
Just updated to 5.1
for those who will read later and more importantly in my same position.
I was on 5.0.1 BL unlocked, custom recovery+root, custom kernel- -wanting to go to->>5.1, root+custom recovery (cause flashing kernels is trivial) without any data loss (basically don't flash the userdata image) (also you could have left out the radio, I guess if you don't want newest radio, and the boot if you want to just keep your kernel--**not 100% about these two though)
I flashed via fastboot the: bootloader (then fastboot reboot-bootloader), the radio (then fastboot reboot-bootloader), then the boot (updated stock kernel), cache, system. Done, exit command prompt, then while in fastboot menu go into TWRP, whereby I choose system reboot and TWRP RE-ROOTS for me! Now I just kernel shop again
Thanks a lot gents. I followed the directions and upgraded/rerouted and none of my apps/settings got wiped. Yay!!
Can someone verify I'm on the latest versions for all components from my screenshot?
Thanks!
I also updated my Nexus 6 with 5.0.1, unlock and root, to 5.1 without losing data. I just had to re-root it afterwards.
I used Wugfresh Nexus root toolkit.
In short I used "Flash stock + unroot", in which I selected "Enable no-wipe" and "force-flash".
After this I rerooted the device from within NRT.
Worked like a charm!
---------- Post added at 03:23 PM ---------- Previous post was at 03:13 PM ----------
LordGrahf said:
Thanks a lot gents. I followed the directions and upgraded/rerouted and none of my apps/settings got wiped. Yay!!
Can someone verify I'm on the latest versions for all components from my screenshot?
Thanks!
Click to expand...
Click to collapse
That's all the latest versions yes...
My nexus 6 is unlocked and is running stock 5.0.1, rooted. . It has twrp and is decrypted.
I tried to sideload the 5.1 ota but it doesnt work.
I tried flashing the new 5.1 factory image but that doesnt work.
I'm tired of all this now, I just want my phone running stock 5.1 , locked , encrypted ,unrooted so I can just get ota next time from Google whenever they send it out.
Any guidance on what I need to do would be appreciated.
Use Wug's Nexus Root Toolkit :good:
Edit : Now I'm currently "Optimising app..." loop.
I tried using tge NRT to flash it back to stock but it didn't work.
I would first make a TWRP backup, then I would flash the boot image (decrypted if you want and make sure its the new one), system, radio and then reboot. I flashed everything fine while keeping twrp on my phone but I didn't like not having a custom ROM plus it was a little laggy so I restored a TWRP backup. My phone did bootloop for a while but eventually it booted 5.1. I would be careful since 5.1 seems to be having some issues in general.
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
Quote:
Originally Posted by baudi11
Same thing happened to me. Here's what I did.
1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.
2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"
3. Click "Flash stock plus unroot"
4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.
5. Follow the toolkit instructions from there.
This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
Click to expand...
Click to collapse
It worked for me after that. Now I'm booted in 5.1
When I try to flash the factory images directly from Google I get the following errors even though the MD5 checks out.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
Press any key to exit...
celeriL said:
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
It worked for me after that. Now I'm booted in 5.1
Click to expand...
Click to collapse
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Giuseppe1010 said:
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Click to expand...
Click to collapse
Glad to help!
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
HaHaa. Tried and true. Always works.
prdog1 said:
HaHaa. Tried and true. Always works.
Click to expand...
Click to collapse
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I totally agree. Have done successful manual flash when tool kits failed. Seen on Nexus 6 already.Saved my soft brick with manual flash when tool kit failed.
Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
rootSU said:
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
Click to expand...
Click to collapse
Thats how I feel because its so easy my wife could do it and she doesn't know anything about flashing. Toolkits are good for non Nexus devices, I just don't see a point when we need to learn things the correct way first.
I hope the bugs get sorted out so people don't hard brick their phones anyone
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
kingofkings11 said:
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
Click to expand...
Click to collapse
You could simply not update the bootloader. Bare minimum requirements is update system and boot (kernel). if you want to learn more about fastboot, go to general > All in one guide > Question 28.
If you do not update the bootloader, you'll never get an OTA but it doesn't seem like you're wanting that anyway.
In regards to data, yes it could cause a problem if you're using a custom rom. You can use fastboot erase data command. This also wipes your /sdcard though.