Related
I lost root after manually updating to 4.1.2 by flashing the zip.
I tried re-rooting but nothing happened and it would just boot back to system.
It is still unlocked though.
Please advise.
fastboot oem unlock, fastboot flash a custom recovery, flash the su binaries,and reboot.
simms22 said:
fastboot oem unlock, fastboot flash a custom recovery, flash the su binaries,and reboot.
Click to expand...
Click to collapse
Thanks but how do I do that?
woshiweili said:
Thanks but how do I do that?
Click to expand...
Click to collapse
You can use WUGs tool kit to root after 4.1.2 update.
For version, just pick custom ROM (JB).
Search for that thread and follow his second....super easy.
Sent from my Nexus 7 using xda app-developers app
tbonezx11 said:
You can use WUGs tool kit to root after 4.1.2 update.
For version, just pick custom ROM (JB).
Search for that thread and follow his second....super easy.
Click to expand...
Click to collapse
Thanks. Yes Wug's toolkit is easy to use. Unfortunately that's one of the first things I tried and didn't work for me.
What ended up working was using Wug's to UNROOT, then unlock and re-root. For some reason that worked. Also fortunately I had a feeling I needed to backup my TWRP backups onto my computer as the Nexus 7 was COMPLETELY wiped after re-unlocking. After this was all done, I moved my backups back to my N7 and restored. Back to 4.1.1 for now. Whew!
didn't work for me either, I could not get ANY custom recovery images to successfully boot on the new bootloader and 4.1.2. Going back to 4.1.1 allowed root again.
Big waste of time going back to stock, locking, unlocking, sideloading 4.1.2 then trying to root.
Had to wipe once more, go back to stock, unlock/lock, root and leave it on 4.1.1
No idea how people are getting custom recoveries to boot on 4.1.2, mine will just restart itself within about 10 seconds of trying to boot an image.
Wug's toolkit makes a folder called ! Ready to flash ...
You will find support su and busy box there....boot to recovery flat the two zips and it roots...
If you did a full wipe they may not be there anymore...
Run the Wug script, when it boots to recovery, install the two zips manually.
Sent from a Buttery-smooth Amaze with xda-developers app
simms22 said:
fastboot oem unlock, fastboot flash a custom recovery, flash the su binaries,and reboot.
Click to expand...
Click to collapse
It was a valiant effort. Can't say you didn't try.
I myself lost root after upgrading to 4.1.2.i just used wugs toolkit and just picked any version for nexus 7 and clicked root.of course better check full driver test first before proceesing.now i am on 4.1.2 and got back with root.
Sent from my Nexus 7 using xda app-developers app
Hi
First of all, this is don't habitual for me since I used to read related post (and more if an update has just arrived) but I just could not find an specific instructions (sorry if I am being too demanding) to go from custom 4.2.1(PA) to stock and finish with rooted 4.2.2, there are a lot of several procedures or recommendations to perform the update :S
well this is what I have planed
- return to stock 4.2.1 (using nexus toolkit)
- download and flash manually the update to 4.2.2 (first try to use the ota update option)
- get root... how??? lol
- restore my apps/data
Since I will return to stock I think I will lose root, that is ok but only if i can root the nexus again, Will I be able to get root on 4.2.2? or I have to root in 4.2.1 and keep it (in some way) at the time I update to 4.2.2
Srryforbad/basicenglish:silly:
Rooting every nexus is the same. Flash/boot a custom recovery and flash supersu.zip. it doesn't matter what OS version its on.
Sent from my Nexus 7 using Tapatalk HD
Pirateghost said:
Rooting every nexus is the same. Flash/boot a custom recovery and flash supersu.zip. it doesn't matter what OS version its on.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
ok, I think I have missing that simple thing...
I don't have to worry about get the bootloader locked again therefore I just have to flash a recovery and SU when I have my N7 on 4.2.2, but...flash from... bootloader I guess, well, I will check that.
Thanks!
Learn the manual way of doing it and don't rely on toolkits. There are many tutorials walking you through the entire process
Sent from my Nexus 7 using Tapatalk HD
SLver said:
ok, I think I have missing that simple thing...
I don't have to worry about get the bootloader locked again therefore I just have to flash a recovery and SU when I have my N7 on 4.2.2, but...flash from... bootloader I guess, well, I will check that.
Thanks!
Click to expand...
Click to collapse
To elaborate on Pirateghost's points...
After flashing the 4.2.2 update... you will lose your recovery (CWM or TWRP)... but getting your recovery back is also part of how you (re)gain root.
As I have posted elsewhere...
Rooting is really simple.
(You will need an unlocked bootloader for this).
Get a custom recovery .img for your device...
Either CWM - http://www.clockworkmod.com/rommanager
...or TWRP - http://www.teamw.in/project/twrp2/103,
...it matters little which...
-----------
fastboot flash it.
-----------
Get Chainfires SU .zip package here http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Flash it using the custom recovery you've just fastboot flashed..
Reboot... and you're rooted.
-----------
...and that's it basically... you have root, a custom recovery from which you can flash ROMs, perform nandroid backups, etc.
But fastboot is the key... learn how to use it, and you will never need to be reliant on anybodies toolkit.
Rgrds,
Ged.
It is what it says on the box....
I accidentally flashed an updated 4.2.2 rom onto my rooted Nexus 4 that was only running 4.2.1
Now, I can't get by the repeated error messages.
In recovery mode have tried to wipe the cache, the dalvik... even tried a full new install of the SU binary.... but can't seem to recover from this error.
Any insight?
I'm only asking this because it's on the script us tech support people have to follow. Did you make a backup?
wipe data(factory reset), then reflash your 4.2.2 nexus 4 rom(and gapps if needed). just flashing the su binaries does nothing for you. i do stuff like this for fun sometimes, its neat seeing all those errors
benderunit9000 said:
I'm only asking this because it's on the script us tech support people have to follow. Did you make a backup?
Click to expand...
Click to collapse
Fair question -
I backed up all my data, yes.
And I had just done a fresh unlocking so I didn't think I needed to - I still had the SU binary in the root directory.
I tried to reflash, still won't boot up in a way I can get at the root directory to put new .zip ROMs on the root, etc.
simms22 said:
wipe data(factory reset), then reflash your 4.2.2 nexus 4 rom(and gapps if needed). just flashing the su binaries does nothing for you. i do stuff like this for fun sometimes, its neat seeing all those errors
Click to expand...
Click to collapse
Did the factory reset. But I don't know how to re-flash with 4.2.2 since it was 4.2.1 originally.
I've downloaded the binary... do I use a similar command ./fastboot .... etc. like I used for flashing the other things?
Robworldwide said:
Fair question -
I backed up all my data, yes.
And I had just done a fresh unlocking so I didn't think I needed to - I still had the SU binary in the root directory.
I tried to reflash, still won't boot up in a way I can get at the root directory to put new .zip ROMs on the root, etc.
Click to expand...
Click to collapse
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
Robworldwide said:
Did the factory reset. But I don't know how to re-flash with 4.2.2 since it was 4.2.1 originally.
I've downloaded the binary... do I use a similar command ./fastboot .... etc. like I used for flashing the other things?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010312
simms22 said:
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
Click to expand...
Click to collapse
Hmmm.
Okay. I'm using clockworkMod Recov 5.8.3.1
I don't see the sideload option, but I'll keep looking.
Robworldwide said:
Hmmm.
Okay. I'm using clockworkMod Recov 5.8.3.1
I don't see the sideload option, but I'll keep looking.
Click to expand...
Click to collapse
cwm should have it, twrp has it for sure.
simms22 said:
there should be an adb sideload option in your custom recovery, you can push a rom to your phone from your computer using adb. you can also reflash the stock image via fastboot. then youll just have to reflash a recovery, then your su binaries or custom rom.
---------- Post added at 09:46 PM ---------- Previous post was at 09:42 PM ----------
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
I've been trying for hours. NO IDEA how to do any of this with a MAC computer.
I at least get to my CDW recovery screen, but I don't have a clue what to do next.
1. Go back to 100% stock using efrant's guide on here
2. Read up on everything so you know what you're doing
3. Try again
EddyOS said:
1. Go back to 100% stock using efrant's guide on here
2. Read up on everything so you know what you're doing
3. Try again
Click to expand...
Click to collapse
For the benefit of those coming after me, who may run into the same problem I did:
I can attest to the wisdom of the above 3 simple steps. It took me several hours to *finally* get this right, but the ABSOLUTE SLAM-DUNK I'VE FINALLY GOT THIS SUSSED PROCESS happened start-to-finish in 20 minutes.
The key step: METICULOUS FOLLOWING EFRANT'S GUIDE.
Do not get sidetracked by other boards or 'short-cuts'.
Just do this... it works, and obviously I learned a lot along the way.
I'm now back to stock, and happily unlocking and rooting, installing custom ROMs just being cognizant of the difficulty if I flash a 4.2.2 ROM on a device that is currently 4.2.1 (which, I believe, is the stock Sprint even now as of April 23).
Thank you to EddyOS and Simms.
what you actually have to do when flashing a ROM with a higher android version than the one you are running? for example I am now on CM10.1, and when Android 5.0 comes out, I need to flash new bootloader and baseband to update to a 5.0 ROM and it will work? Or what?
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
what you actually have to do when flashing a ROM with a higher android version than the one you are running? for example I am now on CM10.1, and when Android 5.0 comes out, I need to flash new bootloader and baseband to update to a 5.0 ROM and it will work? Or what?
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
The key for me was that in addition to flashing the new ROM (I was running 4.2.1 and wanted to put on a custom 4.2.2 ROM) I had to sequentially install the custom ROM then the gapps file while in the same session in recovery mode. Do NOT install just the ROM and then exit recovery mode and reboot! That is how mine got hung up and I had to do a full stock re-install (see Efrant's guide).
As I understand it, this was an issue due to the a change in directory structure or something, so YMMV - this may not apply to future versions of Android.
Robworldwide said:
The key for me was that in addition to flashing the new ROM (I was running 4.2.1 and wanted to put on a custom 4.2.2 ROM) I had to sequentially install the custom ROM then the gapps file while in the same session in recovery mode. Do NOT install just the ROM and then exit recovery mode and reboot! That is how mine got hung up and I had to do a full stock re-install (see Efrant's guide).
As I understand it, this was an issue due to the a change in directory structure or something, so YMMV - this may not apply to future versions of Android.
Click to expand...
Click to collapse
So you didnt actually have to do something special cause I always flash gapps in same session.
And baseband and bootloader, how did you do that? Just flash before installing ROM?
Sent from my Nexus 4 using xda app-developers app
When KLP finally comes out the first thing I will be doing is flashing the complete factory image when released from Google. This will update everything and then using a custom KLP ROM will be a sinch. This is my personal opinion and others may say otherwise but for me it works
EddyOS said:
When KLP finally comes out the first thing I will be doing is flashing the complete factory image when released from Google. This will update everything and then using a custom KLP ROM will be a sinch. This is my personal opinion and others may say otherwise but for me it works
Click to expand...
Click to collapse
Yeah but cant you just install new bootloader and baseband, and then flash a ROM? Much easier imo
Sent from my Nexus 4 using xda app-developers app
I, personally, prefer to flash everything first and then go custom. Dunno why, just do!
EddyOS said:
I, personally, prefer to flash everything first and then go custom. Dunno why, just do!
Click to expand...
Click to collapse
Meh, easier if you just flash stock ROM in CWM first if you want to...
But could someone please answer my question?
Sent from my Nexus 4 using xda app-developers app
hey all,
I'm a complete noob when it comes to rooting
I've been searching online on how to root a nexus 4 using a mac.. every single guide is different, some skip the unlocking bootloader part, some skip other parts, and most guides are just outdated.
I'm running on absolute stock, 4.4.2.
What's the best (and most current) guide out there? I'm interested in rooting my phone mainly so I can get LTE access.. do no care too much for non stock ROMS (not yet at least)
I think this is the easiest for noobs: http://forum.xda-developers.com/showthread.php?t=1999065 . It's a tool that will do all the work for you.
Sent from my Nexus 4 using Tapatalk
update:
I set up adb on my mac and unlocked bootloader, that was easy.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2018179
so now I'm confused about the whole Rom part.. which one do I download? There's a ROMs column, a stock recovery, and stock touch recovery. What are those?
You don't have to install another ROM. You can just download the recovery (CMW for mako touch or non touch) in the post. Also download the su zip tot get root acces.
Sent from my Nexus 4 using Tapatalk
Yuoko5 said:
You don't have to install another ROM. You can just download the recovery (CMW for mako touch or non touch) in the post. Also download the su zip tot get root acces.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ah, so the touch column is all the 'stock' roms. how do I know that it's the latest 4.4.2 stock rom? will be able to do OTA updates after I flash the mako touch?
If you're device is rooted I think you won't be able to install OTA updates from google anymore. But, you can flash these stock roms easily. I'm sure people make flashable zips of every new version of Android. About the columns: ROMs=you can download custom roms (you don't need that); Recovery and recovery touch is basically the same thing. The difference is one recovery can be controlled with the touchscreen and the over with the volume and power button. It's just what you like best.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 02:02 AM ---------- Previous post was at 01:58 AM ----------
beegbear said:
ah, so the touch column is all the 'stock' roms. how do I know that it's the latest 4.4.2 stock rom? will be able to do OTA updates after I flash the mako touch?
Click to expand...
Click to collapse
Get it?
Sent from my Nexus 4 using Tapatalk
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
beegbear said:
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
Click to expand...
Click to collapse
Cwm(clockworkmod recovery) is a side load which helps u to flash different ROMs and zip files. It also helps u to wipe battery stats, partition sd card(not with case of n4)
Factory image is the stock ROM that Google provide that u r having in your nexus 4
Sent from my Nexus 4 using xda app-developers app
beegbear said:
I guess I'm getting some terminology mixed up, it seems that no matter how much I read about this I still can't quite get a grasp of it
What is the definition of CWM (clockwork mod), what exactly does it do?
What is a factory then? (when someone talks about flashing a factory image, I thought that's what CWM is, what's the difference?)
Click to expand...
Click to collapse
And regarding your previous question of OTA updates, You'll have to flash the stock recovery if you're on CWM or TWRP (Team Win Recovery Project - Many people recommend this one, I use it myself) and you shouldn't have made any changes to the system files of your stock ROM.
You will receive the OTA if you have modified anything in system, you just won't be able to flash it. And you can also flash the OTA with TWRP instead of stock recovery. Root does not matter, although it will be lost after you update. Before updating, also make sure you're not using a custom kernel. Kernel: The "thing" that android runs on. It's the heart of the OS, you could say. No kernel, no boot.
Lt.Win said:
And regarding your previous question of OTA updates, You'll have to flash the stock recovery if you're on CWM or TWRP (Team Win Recovery Project - Many people recommend this one, I use it myself) and you shouldn't have made any changes to the system files of your stock ROM.
You will receive the OTA if you have modified anything in system, you just won't be able to flash it. And you can also flash the OTA with TWRP instead of stock recovery. Root does not matter, although it will be lost after you update. Before updating, also make sure you're not using a custom kernel. Kernel: The "thing" that android runs on. It's the heart of the OS, you could say. No kernel, no boot.
Click to expand...
Click to collapse
So let me make sure I'm following this..(sorry, I'm sure you saw such questions countless times before)
CWM (or TWRP) is a custom recovery instead of the stock 'recovery' option that's found in the bootloader. If I choose to go with either CWM or TWRP, how much of an issue is it to flash back to stock recovery? would it be done through ADB the same way the custom recovery was flashed in the first place?
As I understand.. the first thing I should do after unlocking the bootloader (already done) and flashing a custom recovery (not done yet) is to create a backup through the custom recovery. Does that back up the radios as well? If I decide to flash the all in one LTE zip and it doesn't work or what not.. will using that recovery flash back the old radios?
Now to the actual rooting..
so flashing super su is what actually does the root? How would I go about returning to complete stock if I ever need to? (stock recovery, remove root, lock bootloader)
When flashing a different ROM, how come I need to make a backup of my apps? what if I want to start completely fresh? Would I not be able to go to the playstore after flashing a custom rom and downloading everything I need? or there is not going to be a play store after flashing? (that's why GAPPS are needed?)
so I rooted and flashed the hybrid radio, works like charm!
I answered most of my own questions in the post above just by going through the process.
What happens if I decide to factory reset through settings? will CWM stay? will the root stay? will the lte fix stay?
Yes...yes...yes.....you really should take advantage of the countless guides people have written explaining all of your questions.
Sent from my Nexus 4 using XDA Premium 4 mobile app
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Rusty! said:
Your build.prop isn't standard, get the original one, or just use the factory image to update.
Click to expand...
Click to collapse
what i need to install to correct his to the correct build.prop of 4.4.4?
ps. my last 4.4.4 was updated directly OTA..
Just download the 5.0 factory image, remove -w from the flash-all script and it will update you. Less dicking around that way.
inspiron41 said:
I get this error while trying to attempt to update to the latest android 5.0 in twrp...
while installing the new zip file it says:
package expects build fingerprint of google/mantaray/manta: 4.4.4/ktu84p/1227136: user/release-keys or google/mantaray/manta:5.0/LRX21P/1570855:user/release-keys; this device has google/mantaray/manta:4.3/JWR66V/737497:user/release-keys
but my nexus 10 is already on 4.4.4
Click to expand...
Click to collapse
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
CBers said:
Exactly the same here when flashing OTA via TWRP.
The build.prop file hasn't been modified as far as I know.
Where/how to get the file please?
Click to expand...
Click to collapse
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
inspiron41 said:
I found the best way around this is to install the factory nexus 10 lollipop version. It's actually quite easy or even easier than the OTA method. Just make sure you delete the -w from the .bat file to keep all your data. It worked perfectly for me.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
CBers said:
Thanks inspiron41 - I'll give it a go at the weekend.
Which file is the -w in please?
Click to expand...
Click to collapse
Go to this website:
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It has detail instruction and jump down to step 3 regarding to -w
Sent from my Nexus 5 using XDA Free mobile app
I was having the same issue as the OP. So after reading this thread, I've performed the following:
Downloaded Android 5.0 factory image from: https://developers.google.com/android/nexus/images
Followed the instructions at this site, AND MADE SURE TO REMOVE '-w' AS INSTRUCTED, TO PRESERVE DATA: http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
It was pretty easy. I've been waiting about 30 minutes looking at the boot graphic. Hope it turns out OK. But it is easier than playing with the OTA.
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Darnell_Chat_TN said:
After being stuck in a bootloop, I had to factory reset and now all is well.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
[Lemmy] said:
...i've been having the same issue since the 5.0.0 update.
I even had to perform a total wipe to get 5.0.0 onto my N10, and even after that I still have a bad signature on my tablet. Now the problem is back installing 5.0.2 OTA, and I do not want to wipe everything again. So please where is that build.prop file, and how do I fix it? or rather, what the eff has gone wrong here, why, and who's responsible for unbreaking it?
Click to expand...
Click to collapse
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Darnell_Chat_TN said:
Yea, I flashed the 5.0.1 factory image later. Now, I tried to flash the 5.0.2 OTA and it said it saw a 5.0.1 signature and was expecting 5.0.1, or something of that sort. It's basically the same issue all over again... No issues flashing 5.0.2 to my kids' N7s that are 100% stock.
My N10 is unlocked and rooted. There must be something in the customizations that cause this issue.
Click to expand...
Click to collapse
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
[Lemmy] said:
and again, trying to flash the 5.1 OTA and it says there is a 4.4.2 signature so it wont install... but I have re-flashed the stock image several times by now. I just do not get it.
Click to expand...
Click to collapse
Why not just update using the 5.1 factory image? I run unlocked stock/rooted on my N10, and that's the method I always use to update. Would also do it this way on my N5 and now N6. Just fastboot flash all the images from the factory image manually (READ: EXCEPT USERDATA). You can also skip flashing the recovery if you run a custom recovery. However, for the sake of completion, I include flashing the stock recovery. Then I let it boot up normally. Then I'll boot back into the bootloader and flash TWRP and flash SuperSU. Updating this way is easier for me since I don't have to worry about the OTA failing due to customizations I may have made to the system (especially now with the new way Android updates after 5.0).
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
[Lemmy] said:
I've already had to upgrade my tablet by flashing stock for the last three upgrades, and every single time I ended up havnig to wipe the tablet clean and install and configure everything from scratch. I'm still hoping that at some point I wouldn't have to do that anymore...
---------- Post added at 08:57 AM ---------- Previous post was at 08:49 AM ----------
could this all be because my tablet is rooted and has CWM recovery installed?
Click to expand...
Click to collapse
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
charesa39 said:
That's weird. I can't remember the last time I had issues using the stock images, and most people seem to be okay doing it. How are you flashing it? I follow Method 2 from this OP: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I just skip the command that flashes userdata, and it always works. I always flash the new cache image because when I would just erase it, it would be forever stuck in the bootanimation.
Before 5.0, being rooted didn't affect upgrading via OTA. Now, however, any little modification to the system (including being rooted) will cause the OTA to fail everytime. Also using a custom recovery like CWM will cause it to fail. So if you really want to go the OTA route, the least you would have to do is completely unroot (inside the SuperSU app itself) and flash the stock recovery. If you've uninstalled any system apps, you have to reinstall them or it will also fail.
Click to expand...
Click to collapse
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
mj56gt said:
My N10 is with stock ROM 5.0.1 and stock recovery but rooted with unlocked bootloader (and custom launcher). I have two questions:
1) I can unroot it through SuperSU. Do I have to switch back to the stock launcher before trying the OTA installation of 5.1?
2) I remember last time I could gain root by simply installing SuperSU. After flashing the 5.1 factory image, can I still get root this same way, or do I have to install, for example, TWRP and then flash SuperSU?
Thanks!
Click to expand...
Click to collapse
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
charesa39 said:
1) No, you can keep whichever launcher you are using whether it be Trebuchet, Google Now Launcher, Nova, etc. since it's more of just an app and not a system mod.
2) As far as I know (or thought), you've always had to flash SuperSU using a custom recovery unless your ROM already came pre-rooted. In which case, all you would have to do is install SuperSU from the Play Store. But to answer your question, after flashing the factory image, you would have to flash a custom recovery like TWRP and then flash SuperSU using said custom recovery. However, that's not complicated at all. After flashing the factory image, it just takes like another 5 minutes to flash TWRP, boot into it, flash SuperSU, boot into the OS, verify root status, then power off, boot back into the bootloader and flash the stock recovery (if you don't want to keep the custom recovery). While you're at it, after flashing SuperSU, why not flash the Translucent Nav/Status Bar Mod found here: http://forum.xda-developers.com/showthread.php?t=2771708 provided by @hanspampel. He's done a great service for us. It's the easiest and best mod for the stock N10 right now that restores the translucent decor that Google decided to disable on our device. I flashed it on my N10 after upgrading to 5.1 and it works flawlessly. But that's just a suggestion.
Click to expand...
Click to collapse
Thanks a lot for the suggestions! Have a wonderful weekend...
Never mind