So I have a VZN Moto X DE and have tried a few times to take the 4.4.4 OTA. It errors out during the system update. To do this, I flashed back the stock recovery and disabled Xposed. My phone is encrypted as it is required for work. I have thought about trying to simply flash the FXZ file in fastboot (I have read of a few people that have had success with this). My question is if my encryption could be causing the error and if it will cause issues trying to flash from fastboot. My understanding is that the encryption should be the /data partition only which I don't think should be touched. Any words of knowledge in this area or wisdom as to why the OTA is failing?
Thanks
I am not sure about the encryption. But are you starting from full stock? Stock recovery and no system apps frozen? Also are you using mfastboot when flashing your system.img?
Trying to flash stock on my brand new (used) N5 awhile back....I bricked it and was VERY lucky to bring it back to life, cause some in my situation didn't. Why? It was encrypted and I didn't know it. Nor did I know the signs that it was, cause I've never used encryption.
So if you ask me....un-encrypt it first!!
My problem was like yours...I couldn't touch the data partition without errors....can't remember if I got as far as system....but somehow I kinda forced it...and boom. Bricked.
Luckily I found a debrick bat file that got it back.
Someone may know how to work around it, but I'd not try to flash it encrypted. I guarantee there's no such bat file to bring the X back to life.
Travisdroidx2 said:
I am not sure about the encryption. But are you starting from full stock? Stock recovery and no system apps frozen? Also are you using mfastboot when flashing your system.img?
Click to expand...
Click to collapse
Thanks Travisdroidx2 - I believe I should be stock. I bought it used with a custom ROM on it. I SBF'ed (or whatever it is called now) it back to stock and installed xposed. I haven't frozen any apps and have the stock recovery. I wasn't using mfastboot, I was trying to use the OTA. I am curious if I can use mfastboot and a system.img with an encrypted phone. Really don't feel like bricking it.
PhilD41 said:
Thanks Travisdroidx2 - I believe I should be stock. I bought it used with a custom ROM on it. I SBF'ed (or whatever it is called now) it back to stock and installed xposed. I haven't frozen any apps and have the stock recovery. I wasn't using mfastboot, I was trying to use the OTA. I am curious if I can use mfastboot and a system.img with an encrypted phone. Really don't feel like bricking it.
Click to expand...
Click to collapse
I have zero experience with encrypted. So I would see if someone can answer that part for you.
I should clarify. I am using fastboot (linux) not mfastboot. I believe that is a windows tool. Thanks Travisdroidx2. This is the first phone i have ever used encryption on as well so it is all new.
PhilD41 said:
I should clarify. I am using fastboot (linux) not mfastboot. I believe that is a windows tool. Thanks Travisdroidx2. This is the first phone i have ever used encryption on as well so it is all new.
Click to expand...
Click to collapse
First, @PhilD41, yes mfastboot is for windows. The Linux variant of fastboot does not have the issues of not being able to flash system.img that Windows users have with the standard fastboot (they HAVE to use mfastboot).
2nd.... Do / Can you use TiBu? If so, why not backup any APPS you must have (and can't re-download from the play store), copy everything from your internal storage to your PC (including the backups you just made in TiBu), then flash the FULL FXZ with the following commands:
fastboot oem fb_mode_set
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
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
This will return you to 100% bone stock. At this point, you can RE-ENCRYPT, re-flash TWRP (which will root for you), and then put everything back the way you want it....
Apologizes if there is some reason I'm missing why you can't / wouldn't do this....
Thanks samwathegreat, I could do that... and I might end up there. The reason I went with stock and xpose'd (besides the fact that it does most everything I need) was to get away with wiping and spending time setting up my phone again. I did that for years on my GNex and still keep a current TiBu / SMS / MMS backup. I was really hoping for a quick flash back to stock recovery and the OTA. Well that didn't work. I figure the next best thing is a fastboot system update without having to mess with my user data. If the answer is to wipe and start over I can.... just won't be for a few weeks with my current schedule.
PhilD41 said:
Thanks samwathegreat, I could do that... and I might end up there. The reason I went with stock and xpose'd (besides the fact that it does most everything I need) was to get away with wiping and spending time setting up my phone again. I did that for years on my GNex and still keep a current TiBu / SMS / MMS backup. I was really hoping for a quick flash back to stock recovery and the OTA. Well that didn't work. I figure the next best thing is a fastboot system update without having to mess with my user data. If the answer is to wipe and start over I can.... just won't be for a few weeks with my current schedule.
Click to expand...
Click to collapse
I understand. I just don't have ANY information that suggests you will be able to manually flash (and preserve userdata) without TOTALLY messing your phone up to all hell, because of the encryption. (wouldn't that suck....)
This is the safe route. The update isn't that big of a deal anyways...
Please update us as to success when you do have the opportunity to get around to this.
I'd probably decrypt first.
Are you properly disabling Xposed? There should be an xposed-recovery-disabler.zip file in the following directory that you should flash.
Sdcard/android/data/de.robv.android.closed.installer/files
You an also just flash the system.img of the OS version you are currently running. It won't mess up your data and all you need to do is install xposed again after you root and everything is back to normal.
Sent from my Dev Edition Moto X
Rooting and unlocking a phone that is used for work purposes, especially when they require device encryption, is asking for trouble.
Schaweet said:
I'd probably decrypt first.
Are you properly disabling Xposed? There should be an xposed-recovery-disabler.zip file in the following directory that you should flash.
Sdcard/android/data/de.robv.android.closed.installer/files
You an also just flash the system.img of the OS version you are currently running. It won't mess up your data and all you need to do is install xposed again after you root and everything is back to normal.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Please tell how you would decrypt? AFAIK (I could certainly be mistaken...) you CAN'T decrypt...you can only "factory reset" to remove encryption...
I'm interested....especially since I would imagine that would have been the first thing the OP would have done....simply "decrypt", then accept the OTA, then re-encrypt...
imnuts said:
Rooting and unlocking a phone that is used for work purposes, especially when they require device encryption, is asking for trouble.
Click to expand...
Click to collapse
Agreed. He appears to be using some Xposed module to "hide root" from the root-detection used by the corporate apps (Exchange, etc. ?)
As far as a nexus goes...you can decrypt by doing a factory reset....only with stock recovery tho.
Or you can format /data.
Either way....all the important stuff you wanted to encrypt is gone.
---------- Post added at 08:17 PM ---------- Previous post was at 08:16 PM ----------
So yes, you can't actually decrypt.....only wipe it out. Lol
That's why hardly anyone uses encryption. That, and it slows the phone down. So I've read....never actually did it.
Actually it isn't that complicated. It is my personal phone. My work went Google for email, calendar, and apps. So with encryption I can sign into my work google account. Not "hide root" required. As for decrypt, that was my understanding as well. It is a one way street that ends in a wipe if you undo it. As for uninstalling xposed, that is possible. I am just using the uninstall button in xposed. If that doesn't do it then I am doing it wrong. I appreciate the conversation and ideas. I may try flashing over the system.img file currently on first and see if that lets me take the OTA. Still need to wait till I have a few hours to dedicate in case something bad happens.
PhilD41 said:
Actually it isn't that complicated. It is my personal phone. My work went Google for email, calendar, and apps. So with encryption I can sign into my work google account. Not "hide root" required. As for decrypt, that was my understanding as well. It is a one way street that ends in a wipe if you undo it. As for uninstalling xposed, that is possible. I am just using the uninstall button in xposed. If that doesn't do it then I am doing it wrong. I appreciate the conversation and ideas. I may try flashing over the system.img file currently on first and see if that lets me take the OTA. Still need to wait till I have a few hours to dedicate in case something bad happens.
Click to expand...
Click to collapse
If you are manually installing the OTA.zip (i.e. you have it on the /SDCard, boot to recovery and try to install), it should tell you WHY it failed. You can then just work the issues out. Not sure if it will work since /sdcard would be encrypted, so I'm not sure if recovery will be able to access it properly or not.
I would back up all your important data from the phone... i.e. stuff you can't "live without" if you lose.
When all else fails... use RSDlite to flash the FXZ, and make sure you erase userdata and cache. You'll be stock, 4.4.4 but have to set everything back up again, install all your apps, etc.
PhilD41 said:
Actually it isn't that complicated. It is my personal phone. My work went Google for email, calendar, and apps. So with encryption I can sign into my work google account. Not "hide root" required. As for decrypt, that was my understanding as well. It is a one way street that ends in a wipe if you undo it. As for uninstalling xposed, that is possible. I am just using the uninstall button in xposed. If that doesn't do it then I am doing it wrong. I appreciate the conversation and ideas. I may try flashing over the system.img file currently on first and see if that lets me take the OTA. Still need to wait till I have a few hours to dedicate in case something bad happens.
Click to expand...
Click to collapse
You'll want to flash this file in recovery to disable xposed (for me uninstall in in the app worked, some say you have to flash the zip)
https://drive.google.com/folder/d/0B89vrGhlDBcENTZvOHhSMlEzU2c/edit
Guys...why are we posting info that's already on page 1 of this thread? The EXACT same info...
samwathegreat said:
Guys...why are we posting info that's already on page 1 of this thread? The EXACT same info...
Click to expand...
Click to collapse
I have mine set to 20 posts per page, so this is still page 1
I must have missed someone else saying that flashing the OTA manually from stock recovery tells you why it failed... (and the OP asked for insights on why it failed, last sentence of the post)
And I'll blame my sinus infection... I'm not thinking clearly
KidJoe said:
I have mine set to 20 posts per page, so this is still page 1
I must have missed someone else saying that flashing the OTA manually from stock recovery tells you why it failed... (and the OP asked for insights on why it failed, last sentence of the post)
And I'll blame my sinus infection... I'm not thinking clearly
Click to expand...
Click to collapse
Correct you are...that detail was never mentioned. ( I miss things too at times -- as you can see )
Anyways glad you can't 'catch' that through the computer LOL - those are just awful!! Hope you're loading up on sudafed, or the like...
Since the OP has limited time and can't risk any possibility of data loss, or the any number of bad things that *could* happen (boot loops?), I really hope he goes with the backup / wipe data / full FXZ method....when he can get around to it. These are the reasons I avoid encryption (though he doesn't appear to have a choice in the matter).
Thanks guys!! I may try to find some time this weekend to play. I don't have data I "can't" loose, just a pain to set up again. I use to wipe, flash, re-install once or twice a week on the GNex. Got it down to a pretty good science. Looks like my OTA was stored in /cache which I might be able to access in recovery. Otherwise, I might just clear it off and run the full stock, again. Right now it is working well enough that I am not looking forward to breaking it. Then again, if it isn't broken you aren't trying hard enough.
Related
So this is a bit of a comedy of errors on my part...
I took the OTA update to lollipop and (foolishly) followed the same method as on KK to get root, putting myself in a bootloop. I got myself out of it by clearing the userdata and the cache.
I went about sorting everything and achieved root using the chainfire method, that was fine and I then went about reinstalling the xposed modules I had before. Foolishly, I didn't double check the status of xposed on Lollipop and consequently put myself back in a bootloop (idiot). I redid what had worked earlier, clearing the userdata and the cache to no avail.
Obviously, the problem was not the same as before and I needed to disable xposed, but in clearing the userdata I not only removed the xposed_disable.zip file to do this and also turned off adb so I can't push it.
The bootloader is fine and I can use fastboot, but can't push anything across. I hadn't replaced the recovery but can boot into twrp. However, I cannot flash it because I cannot push it over using adb.
I can't work out exactly how far I need to go back/what exactly I need to flash in order to put this all back together again.
I would be very grateful for any help that people can give on this.
Seems you need a .19 stock system partition image to get rid of the bootloop. Hope somebody can backup his system after OTA and share his image,otherwise you have to wait for official release or take risk to downgrade.
----------------------------
If you can boot from TWRP, you can try put the Xposed-Disabler-Recovery.zip in an USB SD card(maybe need formatted to particular filesystem like ext4) linked your phone with otg cable,then mount the sdcard and flash the zip file via TWRP.
If you're not worried about going back with a full wipe to KK, you can follow this link here Seeing that you can get your phone into fastboot, it'll work fine.
HAXTREME said:
If you're not worried about going back with a full wipe to KK, you can follow this link here Seeing that you can get your phone into fastboot, it'll work fine.
Click to expand...
Click to collapse
Thank you! This seems to have solved the problem (whatever exactly it was) and the mobile data is fine which was what I was most unsure about.
I'm curious, my device was a XT1092GB (or at least, I believe it was a GB) and now shows as a 'reteu' where I believe it used to show as 'retgb'. This isn't a problem as it all seems to work, but should I be expecting the Lollipop OTA update to come through? I deliberately didn't follow through on the last part of that thread and install 5.0 that way, I didn't want to tempt fate! However, I would like the update if possible and am unsure which way to go about doing it.
Again, many thanks for all the suggestions everyone. This is why android is awesome
Its a stock EU 4.4.4 so the OTA should come through. Even if it doesn't, I'm sure there's a 5.0 retgb firmware doing the rounds on this forum.
HAXTREME said:
Its a stock EU 4.4.4 so the OTA should come through. Even if it doesn't, I'm sure there's a 5.0 retgb firmware doing the rounds on this forum.
Click to expand...
Click to collapse
I guess even if the 5.0 OTA doesn't come through (for the reasons as given here, any following OTA updates should be fine, right?
If not, do you reckon then 5.0 rom given in the link you sent would be appropriate or would this be a better route?
Thanks for the help!
Couldn't find much about this varient just wanted to ask a few questions.
1. Do I treat it like every other google play nexus? Unlock boot loader, flash twrp, boot, backup, reboot, wipe, install ROM? No different partition weirdness?
2. Cm12, are the hotspot checks removed? Fiance is limited data plan I'm not so while out she normally uses my data via hotspot.
3. Cm12 have notification light activated and customizable?
Don't really care about the Sim lock honestly. Been with ATT forever and poor so not leaving the country anytime soon.
Thanks, sorry for repeat questions just didn't get solid answers from things I found.
No partition weirdness. Root as normal. It does have its own boot logo-thing though, which is lame.
Unfortunately I don't know about CM12. Sorry
squattingdonkey said:
No partition weirdness. Root as normal. It does have its own boot logo-thing though, which is lame.
Unfortunately I don't know about CM12. Sorry
Click to expand...
Click to collapse
At least you answered my bricking level question! Thanks!
CM 12 does have working hot spot on AT&T and customizable notification light. And, boot logo is easily removed after root.
Somehow I soft bricked my n6. I unlocked boot loader, installed twrp, went to backup and it couldn't find any partitions. Tried the flash all script from google factory image and that failed as well. Had to flash boot radio recovery etc images each manually to get back to a booting phone. Then installed twrp again and backup and flashing worked.
It was an adventure but I'm good now. Weird not sure why it did that. Must have been an encryption issue.
On the stock ROM you have to tick a box in developer options to enable OEM unlock. I forgot to mention that earlier. That may have been the issue.
ajjames01 said:
On the stock ROM you have to tick a box in developer options to enable OEM unlock. I forgot to mention that earlier. That may have been the issue.
Click to expand...
Click to collapse
Oops yeah that may have been it. I just did the usual fastboot OEM unlock code. Mild panic attack but when I saw I could get to the bootloader I knew I could save it.
I have never done an OTA update as when I first got into Android I was flashing ROMs nearly every week and never waited for updates just flashed a new ROM, however when I got my Nexus 6 I decided to just root and stick with stock.
I woke this morning and the 5.1 update was available but when I download it and select install and reboot it boots into recovery (TWRP) and I can't see where the download is - I presume I am having to flash it myself? So I have to reboot and it says I am up-to-date with 5.0.1 and then an hour later the download is available again and I go through the same process.
Can anyone help, tell me where i am going wrong.
I had same issue after relocking bootloader and this worked for me and hopefully it may work for you. Put phone in fastboot mode.(hold power + volume down) then use fastboot command fastboot -w
How do you define stock if you have TWRP. LOL
Sent from my Nexus 6
DebianDog said:
How do you define stock if you have TWRP. LOL
Sent from my Nexus 6
Click to expand...
Click to collapse
Well OK stock except for the recovery. I presumed you would know what I meant. I will ensure my posts are word prefect next time.
md1008 said:
I had same issue after relocking bootloader and this worked for me and hopefully it may work for you. Put phone in fastboot mode.(hold power + volume down) then use fastboot command fastboot -w
Click to expand...
Click to collapse
Thanks I'll give it a go
Same issue here. Let us know how you make out.
Hate to do a "me too" post, but I've had the exact same experience.
I'll wait to see whether the fastboot -w method works before I do anything else.
I did try to find the (410.4Mb) download on my N6, but I suspect that the failed update must have deleted it, as it's asking me to download it again.
fastboot -w just wiped userdata so needed to do a fresh install and was still at 5.0.1. So just had to install my backup again to get back to where I was this morning.
Ouch! Sorry to hear it (though glad that you had a backup) - thanks for saving the rest of us from trying that particular route.
I'm still looking for a way to get to 5.1.
You can't do an OTA update with a NON-STOCK recovery.
You can however, if your bootloader is unlocked, download the factory image, extract it, and flash the system.img, bootloader.img, radio.img, cache.img etc...use fastboot to flash those.
Or you can fastboot flash the stock recovery, and take the OTA again.
Thanks.
I assume that I can also use Nexus Root Toolkit to "Flash Stock + Unroot" (without wiping the device), then take the OTA update to 5.1, and then use NRT to Root again?
Just doing a full backup at the moment before I start playing!
UPDATE: The above worked fine.
I started with 5.0.1, rooted, unlocked Bootloader
Then, in Nexus Root Toolkit, I used:
1) Backup (using Create Nandroid Backup w/Custom Recovery option)
2) Flash Stock + Unroot (using No Wipe Mode. I also had to enable Force Flash Mode)
Then, on the phone, accept the OTA 5.1 update, which downloaded and installed first time.
Back to NRT, and:
3) Root and also flash Custom Recovery
I ended up with 5.1, rooted, unlocked Bootloader (and all my apps and data were untouched).
Since doing the method recommended in the second post the OTA update hasn't been available on my device?
Have you tried rebooting the phone?
Or going into Settings > About Phone > System Updates > Check for Updates
It's always possible (if unlikely) that Google have stopped the roll-out to fix some of the issues that people have been reporting with SmartLock, etc?
Philip said:
Have you tried rebooting the phone?
Or going into Settings > About Phone > System Updates > Check for Updates
It's always possible (if unlikely) that Google have stopped the roll-out to fix some of the issues that people have been reporting with SmartLock, etc?
Click to expand...
Click to collapse
yes and yes done that too
Philip said:
UPDATE: The above worked fine.
I started with 5.0.1, rooted, unlocked Bootloader
Then, in Nexus Root Toolkit, I used:
1) Backup (using Create Nandroid Backup w/Custom Recovery option)
2) Flash Stock + Unroot (using No Wipe Mode. I also had to enable Force Flash Mode)
Then, on the phone, accept the OTA 5.1 update, which downloaded and installed first time.
Back to NRT, and:
3) Root and also flash Custom Recovery
I ended up with 5.1, rooted, unlocked Bootloader (and all my apps and data were untouched).
Click to expand...
Click to collapse
Why did you take the scenic route? This is by far the longest method to do that.
Instead of flashing stock with nrt, why not just flash stock normally? That way you could have just flashed 5.1 without having to take any OTA...
And further, if you wanted to keep recovery, why not just flash the system and boot image keeping everything else as it is? Then just flash SuperSU from twrp?
2 commands
fastboot flash system system.img
fastboot flash boot boot.img
Boot into recovery and flash root.
Much quicker than the method you used.
rootSU said:
Why did you take the scenic route? This is by far the longest method to do that.
Click to expand...
Click to collapse
Well, my fist step was a backup, which you conveniently left out - you may be happy to update your phone without backing it up first, but I chose not to take that chance.
Apart from that, it's about the same number of steps - I was happy to take 5.1 OTA (which meant that I was certain that it was the correct version for my phone), and Nexus Root Toolkit is a much nicer piece of software to use than fastboot. I know that some people don't like NRT because they feel that it demystifies the black arts of updating and it threatens their voodoo status, but I find it an excellent piece of software and recommend it to you.
In the meantime, while you had to go and find the appropriate system.img and the appropriate boot.img and download them before fastbooting them, these were steps that I was able to avoid whilst enjoying my "scenic" journey.
So you take the high road and I'll take the low road - but I reckon that it took me no longer to update my phone than it took you to update yours!
Philip said:
Well, my fist step was a backup, which you conveniently left out - you may be happy to update your phone without backing it up first, but I chose not to take that chance.
Apart from that, it's about the same number of steps - I was happy to take 5.1 OTA (which meant that I was certain that it was the correct version for my phone), and Nexus Root Toolkit is a much nicer piece of software to use than fastboot. I know that some people don't like NRT because they feel that it demystifies the black arts of updating and it threatens their voodoo status, but I find it an excellent piece of software and recommend it to you.
In the meantime, while you had to go and find the appropriate system.img and the appropriate boot.img and download them before fastbooting them, these were steps that I was able to avoid whilst enjoying my "scenic" journey.
So you take the high road and I'll take the low road - but I reckon that it took me no longer to update my phone than it took you to update yours!
Click to expand...
Click to collapse
It took you loads longer haha.
rootSU said:
It took you loads longer haha.
Click to expand...
Click to collapse
And that bothered you so much that you had to tell the whole world about it? Wow!
Philip said:
And that bothered you so much that you had to tell the whole world about it? Wow!
Click to expand...
Click to collapse
To be honest no. The route you took was so long that I thought you just didn't have a clue about what you were doing so I thought I'd help out and let you know the quicker version... And if anyone reads your post and thinks its the best way to do it, well now they have some contrast.
What bothers me is your attitude however. But I don't care enough to get into an argument with people who would rather waste their time and the people they try to help than listen to constructive criticism.
But yeah, your way is needlessly long so I hope people don't take your lead.
Hey guys. Forgive me for my noobness here, I'm still kind of new to rooting etc. So I've got an Australian nexus 6, running 5.0.1, its rooted, I used the nexus root toolkit, and it installed twrp, I want to update to 5.1, downloaded the update from aosp or whatever and tried to sideload it, I kept getting errors and fails. Both twrp and adb are updated. Now I think from what I've read, after rooting a 5.0 device you can't receive OTAs anymore. I just got the OTA notification, I downloaded it and pressed install, it restarted then booted into twrp and didn't start the update process. I've tried unrooting but it failed. My questions are: can I install the OTA through twrp? Is there a way to bypass twrp to continue the update? Can I factory reset through settings on the phone to go back to stock and then do the update that way? (I've heard its bad to factory reset like that, not sure why or if its true?) Just want 5.1 already! Any help is appreciated, and if possible dumb it down a bit because some terminology still is not known to me
Thanks in advance
ice_cold17 said:
Hey guys. Forgive me for my noobness here, I'm still kind of new to rooting etc. So I've got an Australian nexus 6, running 5.0.1, its rooted, I used the nexus root toolkit, and it installed twrp, I want to update to 5.1, downloaded the update from aosp or whatever and tried to sideload it, I kept getting errors and fails. Both twrp and adb are updated. Now I think from what I've read, after rooting a 5.0 device you can't receive OTAs anymore. I just got the OTA notification, I downloaded it and pressed install, it restarted then booted into twrp and didn't start the update process. I've tried unrooting but it failed. My questions are: can I install the OTA through twrp? Is there a way to bypass twrp to continue the update? Can I factory reset through settings on the phone to go back to stock and then do the update that way? (I've heard its bad to factory reset like that, not sure why or if its true?) Just want 5.1 already! Any help is appreciated, and if possible dumb it down a bit because some terminology still is not known to me
Thanks in advance
Click to expand...
Click to collapse
If you're unlocked, rooted and have TWRP, why not just install custom ROM? Otherwise you can download factory image that you want, unzip and flash images individually via fastboot. Just don't flash user data and you won't loose data.
Just use the toolkit to 100% flash back go stock. It will unroot and reinstall stock recovery. Just remember to always keep USB debugging on and keep that boot loader unlocked. Once your back to the out box state you should be v able to receive ota. Or just use toolkit to flash the new stock image for your device. Ends with I.
Sent from my Nexus 6
I've never flashed files individually. I don't like any of the Roms, I prefer stock android but I like the perks of rooting. Could you give me a step by step on flashing the files individually please
ice_cold17 said:
I've never flashed files individually. I don't like any of the Roms, I prefer stock android but I like the perks of rooting. Could you give me a step by step on flashing the files individually please
Click to expand...
Click to collapse
Look here http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008, method 2.
Awesome thanks, so if I don't flash "user data" I can keep my stuff, will that mess it up in anyway? What about the step that says erase user data, can I skip that then?
ice_cold17 said:
Awesome thanks, so if I don't flash "user data" I can keep my stuff, will that mess it up in anyway? What about the step that says erase user data, can I skip that then?
Click to expand...
Click to collapse
I don`t erase and flash userdata usualy, its good to erase cache and then flash cache cache.img. A data factory reset after the procedure is adviced however for preventing fc`s and such.
So in the end is should wipe anyway? Oh well I was trying to avoid that only as a last resort. It wouldn't even let me unroot through the toolkit for some reason...
I, too, would like to know this. I have looked through many forums and sites to try to find an answer.
My Nexus 6 is:
- bootloader unlocked
- TWRP recovery
- rooted
I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts.
Is there a flashable update.zip that allows the update to 5.1? (I have seen a few, but they usually have encryption disabled - which I believe will cause me to lose my data?)
Would it be easy enough to restore stock recovery and unroot, which would allow me to flash the OTA normally - then just flash TWRP and root again?
How would I go about this?
fubofo said:
I, too, would like to know this. I have looked through many forums and sites to try to find an answer.
My Nexus 6 is:
- bootloader unlocked
- TWRP recovery
- rooted
I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts.
Is there a flashable update.zip that allows the update to 5.1? (I have seen a few, but they usually have encryption disabled - which I believe will cause me to lose my data?)
Would it be easy enough to restore stock recovery and unroot, which would allow me to flash the OTA normally - then just flash TWRP and root again?
How would I go about this?
Click to expand...
Click to collapse
Why not just download the factory image of your choice, then fastboot flash everything but user data. You will keep all your data. Many users go this route. Personally, I like a fresh start that doing a factory reset gives. I backup everything to the cloud and then restore what I need to have on my phone. I mention this because it is recommended to preform a factory reset after installing the images separately. Thus avoiding any boot loops or force closings.
Evolution_Freak said:
Why not just download the factory image of your choice, then fastboot flash everything but user data. You will keep all your data. Many users go this route. Personally, I like a fresh start that doing a factory reset gives. I backup everything to the cloud and then restore what I need to have on my phone. I mention this because it is recommended to preform a factory reset after installing the images separately. Thus avoiding any boot loops or force closings.
Click to expand...
Click to collapse
So do I need to flash all the images?
Can I also leave out the recovery image - or do I flash it and re-flash TWRP after?
Does flashing the OTA (normally) factory reset the device wiping all accounts and setup?
I don't want to perform a factory reset as I use the device for business and have many email accounts, sync accounts, contact accounts and other tweaks that I don't want to have to spend a few days setting up again.
fubofo said:
So do I need to flash all the images?
Can I also leave out the recovery image - or do I flash it and re-flash TWRP after?
Does flashing the OTA (normally) factory reset the device wiping all accounts and setup?
I don't want to perform a factory reset as I use the device for business and have many email accounts, sync accounts, contact accounts and other tweaks that I don't want to have to spend a few days setting up again.
Click to expand...
Click to collapse
I understand, everyone's situation is different. No, an OTA will preserve all your accounts and data. Your best bet in your situation may be to flash stock recovery and remove root. Then you could sideload the OTA. Also, though I don't use or really recommend the use of toolkits, the NRT may have options available for your needs as well. There is a possibility that just removing root and TWRP may still leave traces behind. Enough that the OTA may fail.
Evolution_Freak said:
I understand, everyone's situation is different. No, an OTA will preserve all your accounts and data. Your best bet in your situation may be to flash stock recovery and remove root. Then you could sideload the OTA. Also, though I don't use or really recommend the use of toolkits, the NRT may have options available for your needs as well. There is a possibility that just removing root and TWRP may still leave traces behind. Enough that the OTA may fail.
Click to expand...
Click to collapse
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
fubofo said:
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
Click to expand...
Click to collapse
Relocking the bootloader wipes the device, so you don't want to do that.
What is your ultimate goal? Your absolute ideal situation, once you're updated. Let's learn that and work from there.
fubofo said:
Could you point me to guides for returning to stock recovery and re-locking bootloader?
I can only seem to find many, many guides on how to flash a custom recovery - not the reverse.
Click to expand...
Click to collapse
You don't have to relock your bootloader. That doesn't matter. As for recovery, I believe all you have to do is obtain the proper recovery for the build you are currently running, the fastboot flash it from bootloader.
Look here for more info:
http://forum.xda-developers.com/showthread.php?t=3063857
rootSU said:
Relocking the bootloader wipes the device, so you don't want to do that.
What is your ultimate goal? Your absolute ideal situation, once you're updated. Let's learn that and work from there.
Click to expand...
Click to collapse
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
fubofo said:
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
Click to expand...
Click to collapse
OK, let me ask this, what is your current software? 5.0 or 5.0.1?
fubofo said:
I already stated this in my first post (first page):
"...I would like to update to the latest 5.1 without wiping my device. I don't want to lose my setup and accounts...."
Click to expand...
Click to collapse
No. That is not enough information. That is your IMMEDIATE goal. I need to know what is your ULTIMATE goal?
Right now you're rooted with twrp. In order to give you the best advice I need to know your ultimate goal is. Why are you rooted with twrp? Do you need this in the future? Why are you thinking about locking the bootloader
All this has an affect on what method you use.
rootSU said:
No. That is not enough information. That is your IMMEDIATE goal. I need to know what is your ULTIMATE goal?
Right now you're rooted with twrp. In order to give you the best advice I need to know your ultimate goal is. Why are you rooted with twrp? Do you need this in the future? Why are you thinking about locking the bootloader
All this has an affect on what method you use.
Click to expand...
Click to collapse
Thank you sir for helping!
Evolution_Freak said:
You don't have to relock your bootloader. That doesn't matter. As for recovery, I believe all you have to do is obtain the proper recovery for the build you are currently running, the fastboot flash it from bootloader.
Look here for more info:
http://forum.xda-developers.com/showthread.php?t=3063857
Click to expand...
Click to collapse
Thanks @Evolution_Freak I'll give a shot at flashing just the stock recovery, unrooting and trying the OTA
Usually when a new Android OS version is released, I'll just start over from scratch by manually flashing the seven image files using fastboot. I then install the unencrypt kernel/boot image and also root.
Now that these security updates are coming out every month, is there an easier way in my specific situation to install the update only without having to start from scratch every time like above?
Flash the system image only (if radio is different, flash that too). That won't overwrite your user data/apps
Edit: When flashing the system.img, flash the cache.img as well (to be safe)
Thanks. That is pretty simple. I wish I asked this a long time ago so I could avoided a lot of resetting EVERYTHING up all the time. 2 more clarifications if you don't mind...
1) Would this also work for point releases, like say if a 5.1.2 comes out, or would it be better to reflash everything in that case?
2) No other steps like clear cache or anything? Just flash those 2, reboot, and then I should be good to go?
Toaplan said:
Thanks. That is pretty simple. I wish I asked this a long time ago so I could avoided a lot of resetting EVERYTHING up all the time. 2 more clarifications if you don't mind...
1) Would this also work for point releases, like say if a 5.1.2 comes out, or would it be better to reflash everything in that case?
2) No other steps like clear cache or anything? Just flash those 2, reboot, and then I should be good to go?
Click to expand...
Click to collapse
It should work just fine for point releases. For major releases (like when Android M is released), I will probably flash everything, and wipe everything (including userdata), and start from scratch ! lol!
In theory, it should work find even for major releases, but I'd rather start with a clean slate - especially with the new permissions manager that is being added in this release. I'd rather not take any old incompatible apps thru' - but that's just me
Clearing cache is usually not needed. I've heard of instances where some users get stuck on the Google boot logo for some reason when booting for the first time. If that happens, clearing cache seems to help.
To be safe, it may be a good idea to flash the cache.img too. It takes a few seconds. Better safe than sorry. I'll update my earlier post.
jj14 said:
...
Click to expand...
Click to collapse
Huge thanks. This should make things a lot easier for me.
Is this the system update that just got pushed to my phone? It looks like a small update, like 26MB?
Mine tried to install and failed. My phone is stock, latest official version, never rooted, but the bootloader is unlocked and it is running the no force encrypt kernel, which I believe is probably what is causing the issue?
Only way is to restore completely to stock, take the OTA and then install the no decrypt?
I got the OTA today to upgrade to M from L- (on verizon) where can I Find that system image to flash- I tried sideloading the OTA and it didn't take.
caecusscius said:
I got the OTA today to upgrade to M from L- (on verizon) where can I Find that system image to flash- I tried sideloading the OTA and it didn't take.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
SquireSCA said:
Is this the system update that just got pushed to my phone? It looks like a small update, like 26MB?
Mine tried to install and failed. My phone is stock, latest official version, never rooted, but the bootloader is unlocked and it is running the no force encrypt kernel, which I believe is probably what is causing the issue?
Only way is to restore completely to stock, take the OTA and then install the no decrypt?
Click to expand...
Click to collapse
I believe it's actually both of these things causing the OTA not to take. If anything, anything is changed from stock...no OTA. Bootloader unlocked, kernel, root, even just changing the build.prop (but you need root for that) would cause it to fail. I believe it checks every file and if anything in /system has changed, no OTA.
I've never messed around with the encryption pieces, but I'm wondering if you only flash the system.img (you'd need to re-root) if that would suffice or not as far as the update. You'd be flashing the entire system file instead of only the delta the OTA provides, but it's probably worth looking into.
Hmmm... Well, it takes 15 minutes to just wipe the phone and flash the new ROM with the toolkit, install my apps, copy my files over and set the phone up, so it isn't a big deal, I just want to make sure that I have the right version before I do that...
(LMY48M) That's the one that I want for the VZW N6, right?
I just use helium to backup my apps and everything. Even if I need to wipe it is a pretty easy restore process. I highly recommend helium backup.
hayzooos said:
I believe it's actually both of these things causing the OTA not to take. If anything, anything is changed from stock...no OTA. Bootloader unlocked, kernel, root, even just changing the build.prop (but you need root for that) would cause it to fail. I believe it checks every file and if anything in /system has changed, no OTA.
I've never messed around with the encryption pieces, but I'm wondering if you only flash the system.img (you'd need to re-root) if that would suffice or not as far as the update. You'd be flashing the entire system file instead of only the delta the OTA provides, but it's probably worth looking into.
Click to expand...
Click to collapse
Unlocked bootloader doesn't affect it, the customised kernel does though . But yes, you could just flash the system.img