Database Users

Lost root after 4.1.2

I was running stock 4.1.1 rooted with NO cwm and I accepted the OTA undate two days ago. Now, I have SU still installed but nothing can obtain root permissions. I used Wugz toolkit to reflash su binaries through TWRP a few times and still no dice. Any thoughts?

Trickee360 said:
I was running stock 4.1.1 rooted with NO cwm and I accepted the OTA undate two days ago. Now, I have SU still installed but nothing can obtain root permissions. I used Wugz toolkit to reflash su binaries through TWRP a few times and still no dice. Any thoughts?
Click to expand...
Click to collapse
Here you go. Just follow the directions. It works fine for 4.1.2.
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/

veeman said:
Here you go. Just follow the directions. It works fine for 4.1.2.
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
Click to expand...
Click to collapse
Welp, I've never actually used adb to push anything manually myself, but now is as good as time as any to try it. The link to CWM on that page is dead. Where else can I get it?

Trickee360 said:
Welp, I've never actually used adb to push anything manually myself, but now is as good as time as any to try it. The link to CWM on that page is dead. Where else can I get it?
Click to expand...
Click to collapse
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.

veeman said:
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
got it. thanks much

Will only boot to stock recovery
veeman said:
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(

jphilli85 said:
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
Click to expand...
Click to collapse
You can just root again and you will have root access.

I lost root too, so I just opened wugtoolkit and hit root. no unlock needed so no loss of programs either.

jphilli85 said:
Every time I reboot into recovery from the bootloader after flashing any recovery (except stock), it fails to boot into recovery. What happens is it shows the Google/Unlocked screen for a couple seconds, goes black (this is where it should enter recovery), but then shows the Google screen again and boots normally. I have tried this with two CWM recoveries and a TWRP recovery, both plugged into a computer and not. when flashing recovery it says OKAY. It seems as if something has gotten corrupted.
Before updating to 4.1.2 everything was working. To get the 4.1.2 update to install, I had to revert back to stock recovery and also revert back to the stock wallet app. Now 'su' is still a command, but it does not do what it is supposed to and no apps have root.
:'(
Click to expand...
Click to collapse
Any news about this. I stay in the same problem.

Here's my experience:
Stock ROM, rooted, custom kernel.
Got the notification for the 4.1.2 OTA update, so I did a nandroid backup in TWRP. Then I flashed back to the stock recovery and boot.img.
I was thinking that I might lose root, based on other's problems. Looked into installing Root Keeper by Voodoo. In the description it said the same feature is built into SuperSU. Problem was it's built into the paid version, which I didn't have (discovered this after it was too late). Installed 4.1.2 OTA. I lost root. My bootloader was updated to 3.41. I also was not able to flash a recovery. Fastboot flash would not work, Wugs toolkit didn't work. Tried several methods. After reading several threads that have been pretty active for the last few days, here's what finally worked for me. Found it in another thread, which I can't find at the moment.
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the JRO03D factory image
fastboot flash recovery TWRP img
fastboot reboot-bootloader
TWRP recovery started up :laugh:.
flashed SuperSU to re-root, it was sucessful.
updated busybox binaries.
installed OTA rootkeeper, so hopefully this won't happen again.
I'm not really sure I want to try flashing the 3.41 bootloader.
What a pain in the A.
Now it's time to flash faux kernel.

jayyo said:
Here's my experience:
Stock ROM, rooted, custom kernel.
Got the notification for the 4.1.2 OTA update, so I did a nandroid backup in TWRP. Then I flashed back to the stock recovery and boot.img.
I was thinking that I might lose root, based on other's problems. Looked into installing Root Keeper by Voodoo. In the description it said the same feature is built into SuperSU. Problem was it's built into the paid version, which I didn't have (discovered this after it was too late). Installed 4.1.2 OTA. I lost root. My bootloader was updated to 3.41. I also was not able to flash a recovery. Fastboot flash would not work, Wugs toolkit didn't work. Tried several methods. After reading several threads that have been pretty active for the last few days, here's what finally worked for me. Found it in another thread, which I can't find at the moment.
adb reboot bootloader
fastboot flash bootloader bootloader-grouper-3.34.img from the JRO03D factory image
fastboot flash recovery TWRP img
fastboot reboot-bootloader
TWRP recovery started up :laugh:.
flashed SuperSU to re-root, it was sucessful.
updated busybox binaries.
installed OTA rootkeeper, so hopefully this won't happen again.
I'm not really sure I want to try flashing the 3.41 bootloader.
What a pain in the A.
Now it's time to flash faux kernel.
Click to expand...
Click to collapse
So, the bootloader 3.41 is the problem?

Southmad said:
So, the bootloader 3.41 is the problem?
Click to expand...
Click to collapse
For some people, yes. No idea why.

veeman said:
http://www.clockworkmod.com/rommanager
You can download the Touch Recovery on the right side for Google Nexus 7 version. But make sure when you put in
Code:
fastboot flash recovery recovery-clockwork-touch-6.0.1.0-grouper.img
for step 5. instead of what they put.
Click to expand...
Click to collapse
Would that image work ok for Galaxy s3? Or there is no difference at all, just matter the 4.1.2 android version?
Cuz i updated my device throught Kies (cuzz from the device itself it didnt allow, stating that the image has been modifyied :angel: ) and after that even with the persistent mode on Super SU the root is gone

[Q] Nexus 7 (4.1.2) can't root

Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message

IAmNice said:
usb debugging on? Have you checked that?
Click to expand...
Click to collapse
Hi. Yes mam (usb debugging on) have a look to the attachment.
Toolkit me boot into fastboot then reboot then for something to fastboot loaded and back to android and trying to upload the files but nothing superuser is not recorded because of (read-only file system).
have a look on the attachment is there to see everything ...

yep same issue here - problem with the forum regs is unless you have enough posts you can't actually address the issue to the appropriate person can you? Anyway, able to unlock but then is unable to root and rest due to a permissions problem. have tried as administrator but of coure this doesn't make any difference.

NexusTropers said:
Hi I have a Nexus 7 version (4.1.2 OTA).
I wanted to ask what the deal is or what I'm doing wrong. I purchased the full version of Nexus ToolKit 7. According to the instructions I made the unlocked bootloader and I wanted to root but each attempt failed.
I do not know what I could do wrong when root is fully automated.
PS: I also tried to reflash Stock Rom (4.1.2)
I enclose a picture attachments with an error message
Click to expand...
Click to collapse
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.

try:
http://forum.xda-developers.com/showthread.php?t=1796109

comminus said:
You can try flashing CWM recovery and installing Superuser from there.
Download Superuser and copy it to your /sdcard
Flash CWM recovery
Install Superuser from CWM
????
Profit.
Click to expand...
Click to collapse
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.

bazabaza said:
Thanks comminus - but I think that if we could do this then we wouldn't be using the tool kit.
Click to expand...
Click to collapse
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.

comminus said:
Why not try before you give up? Nothing I suggested is even remotely challenging.
With your tablet booted normally plug it in to your computer and copy the superuser zip in my previous post to the Download directory on your Nexus 7 from Windows.
Judging by the first provided screenshot I can see that option 6 in that toolkit is for flashing recovery. Why not try that?
As far as how to install the zip from ClockworkMod (CWM), there are literally hundreds of threads and YouTube videos that will show you what to do. The better option is to spend a few minutes (literately. It only takes a few minutes.) to learn some basic fastboot commands. If you're willing to learn there are many people who will help.
Click to expand...
Click to collapse
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.

NexusTropers said:
Thx you for your post
But in the Nexus7 ToolKit can be done but is ClockworkMod must first rename (recovery restore files) but with da only when I have ROOT.
Click to expand...
Click to collapse
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
NexusTropers said:
And why unnecessary to install CWM and resolve other problems I'll eat a connection. If "simply" can I ROOT who create me rich enough.
Click to expand...
Click to collapse
I'm not really sure what you're trying to say...

I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.

comminus said:
Choose #1 in your first screenshot.
After you install CWM make sure you boot recovery before a standard boot. On rebooting from CWM it will say something like "ROM may flash stock recovery on boot." and prompt with yes or no. Choose yes - this renames /system/recovery-from-boot.p and prevents the ROM from restoring stock recovery.
I'm not really sure what you're trying to say...
Click to expand...
Click to collapse
1. THX u i try it.
2. AH sorry translator make crazy text.
homerbrew said:
I tried quite a few times to root my Nexus 7 with the Nexus 7 toolkit, it hung every time when it was supposed to be installing SuperSU and BusyBox. Every time the last message I saw was "adbd already running as root", and it would just hang there. Everything else appeared to work properly. The only tool I was able to successfully use (more than once) was the Nexus Root Toolkit from Wugfresh http://forum.xda-developers.com/showthread.php?t=1766475. You may want to try that tool.
Click to expand...
Click to collapse
Oki THX u i try this tool...

I'm also having this same problem but here's my story:
Using the Nexus 1.5.4 Toolkit, I Unrooted + Flashed jzo54k, success. I locked OEM, success. I unlocked again, success. Then I ran the root process again, and it keeps freezing at the android recovery screen. Following the prompt in the toolkit, I walked away for a few hours hoping time would resolve the issue.
If you're wondering why I unlocked + rooted, and decided to unroot, lock, unlock, and root again, its because I'm super-noob to anything android related after version 1.5, I wanted to learn the processes after I found out I was having troubles with certian things after my Nexus 7 updated from 4.1 to 4.1.2

I am having the same issue as you. 4.1.2 is not rooting for me. I can't install CWM or TWRP because it needs to rename recovery files, and to do that you need to be rooted. If I boot in recovery I always get stock

Having the same issue with a stock 4.1.2. I can unlock no problem but I cannot get it rooted. Everything appears to have worked, but it is not rooted. If I revert back to 4.1.1 I can unlock, root, etc. without issue. I was able to root 4.1.1 and use the root keeper app to then update to 4.1.2 and I was rooted still. However, it would not let me install CWM or anything. ROM Manager says it was installed, but booting to recovery always too me to stock.
Any ideas?

Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app

MetalMadness said:
Can you point me into the direction to downgrading?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I used Nexus Root Toolkit v1.5.4 and selected the "Flash Stock + Unroot" option. When prompted I choose the default 4.1.1 option and away it went.

To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.

hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!

hundred_miles_high said:
To root my 32Gb on 4.1.2 I had to unlock the boot loader, flash the boot loader back to version 3.34, and then I successfully rooted using the nexus 7 toolkit.
Click to expand...
Click to collapse
Indy1204 said:
Winner winner! I was just reading THIS which is exactly what you suggested. I just tried this and can confirm that it did work.
Thanks!
Click to expand...
Click to collapse
Thanks. I did this earlier and it didnt work, but I checked boot instead of flash
FLASH THE OLDER BOOTLOADER DON'T BOOT IT!!!

Recovery won't flash

I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4

Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.

SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4

T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps

Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4

T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.

Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4

T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.

OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.

Problem Recovery

Suddenly my recovery has stopped working whenever i want to go to recovery is shows me that image with a dead android robot.
Is there any way to flash TWRP again without ADB because i can't get it working,
I tryed twrp manager but it needs root and i lost it.

RootNightmareX said:
Suddenly my recovery has stopped working whenever i want to go to recovery is shows me that image with a dead android robot.
Is there any way to flash TWRP again without ADB because i can't get it working,
I tryed twrp manager but it needs root and i lost it.
Click to expand...
Click to collapse
Try using a toolkit.. for example wugsfresh nexus root toolkit! There's an option to flash the last twrp version..

RootNightmareX said:
Suddenly my recovery has stopped working whenever i want to go to recovery is shows me that image with a dead android robot.
Is there any way to flash TWRP again without ADB because i can't get it working,
I tryed twrp manager but it needs root and i lost it.
Click to expand...
Click to collapse
Without root you would need ADB to flash it...
Your recovery will get over-ridden on each boot unless you rename/delete /system/recovery-from-boot.p to recovery-from-boot.bak or something.
You will need to use fastboot to flash recovery again, then boot TWRP and go into the file manager and rename the file I mentioned above. Sorry, no way to flash recovery without working adb or root.

acejavelin said:
Without root you would need ADB to flash it...
Your recovery will get over-ridden on each boot unless you rename/delete /system/recovery-from-boot.p to recovery-from-boot.bak or something.
You will need to use fastboot to flash recovery again, then boot TWRP and go into the file manager and rename the file I mentioned above. Sorry, no way to flash recovery without working adb or root.
Click to expand...
Click to collapse
I solved with an easy root based on adb program
I rooted the phone and reflashed with twrp from play store. Is there anything I must delete now ?
But whatcould have caused this problem. I was using art clean flashed this morning..... It Never happened for me on any device this problem its first time

RootNightmareX said:
I solved with an easy root based on adb program
I rooted the phone and reflashed with twrp from play store. Is there anything I must delete now ?
But whatcould have caused this problem. I was using art clean flashed this morning..... It Never happened for me on any device this problem its first time
Click to expand...
Click to collapse
You must rename/delete the file I mentioned above if it is a stock ROM, otherwise it reflash the stock recovery on the next boot.
Sent from my Nexus 4 using Tapatalk

acejavelin said:
You must rename/delete the file I mentioned above if it is a stock ROM, otherwise it reflash the stock recovery on the next boot.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I rebooted and still I have twrp. Should I still search the file n delete it?

RootNightmareX said:
I rebooted and still I have twrp. Should I still search the file n delete it?
Click to expand...
Click to collapse
It flashes it on boot, so the next time it might be gone. Most AIO tools take care of it for you.
Your call I guess, is the file there?
Sent from my Nexus 4 using Tapatalk

acejavelin said:
It flashes it on boot, so the next time it might be gone. Most AIO tools take care of it for you.
Your call I guess, is the file there?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I have that recovery bak file. What should i do with it ?

RootNightmareX said:
I have that recovery bak file. What should i do with it ?
Click to expand...
Click to collapse
Personally, I just added a .bak extension to the file, but you could delete it. The nice part about keeping it is if you are basically stock and want to get an OTA, you can just take off the .bak extension, reboot, have stock recovery back, then take the OTA... but I haven't been stock for some time, and returning to stock is fairly simple anyway.

acejavelin said:
Personally, I just added a .bak extension to the file, but you could delete it. The nice part about keeping it is if you are basically stock and want to get an OTA, you can just take off the .bak extension, reboot, have stock recovery back, then take the OTA... but I haven't been stock for some time, and returning to stock is fairly simple anyway.
Click to expand...
Click to collapse
That image can actually lock bootloader back too ?

No, just reflash recovery... It can't relock boot loader, that doesn't have to be locked to take an OTA.
Sent from my Nexus 4 using Tapatalk

RootNightmareX said:
I solved with an easy root based on adb program
I rooted the phone and reflashed with twrp from play store. Is there anything I must delete now ?
But whatcould have caused this problem. I was using art clean flashed this morning..... It Never happened for me on any device this problem its first time
Click to expand...
Click to collapse
what program did you use to root?
Sent from my Nexus 4 using xda app-developers app

Issue updating to Android 5.0

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