Database Users

[Q] Lost root after verizon update

So I installed the Verizon OTA update and now I seem to have lost root. I was rooted via Z4. Now when I click root, it just vibrates and nothing happens. I cant use rooted apps any more. The Superuser app is still present, though it doesnt do anything. Can I just do the oneclick root over the Z4? I really don't want to ruin the tab. Any help would be appreciated, thanks.
* I am running stock rom.
Thanks

After any ROM update root has to be lost. On new ROMs z4root does not work, that is right. Try to find SuperOneClickv1.7_ShortFuse - it really works with latest updates. Put the package on your C:\ disk. Run executable with administrator rights, otherwise it will not work out. If you have any anti-virus running on PC - stop it before copying the package to disk, otherwise it will immediately kill one of the files in package (this one is not a virus!).
Hope this helps.

qmanager said:
After any ROM update root has to be lost. On new ROMs z4root does not work, that is right. Try to find SuperOneClickv1.7_ShortFuse - it really works with latest updates. Put the package on your C:\ disk. Run executable with administrator rights, otherwise it will not work out. If you have any anti-virus running on PC - stop it before copying the package to disk, otherwise it will immediately kill one of the files in package (this one is not a virus!).
Hope this helps.
Click to expand...
Click to collapse
I also applied that update and lost root. z4root wouldn't work anymore, SuperOneClick did the trick! Thanks for the help!

DRTY said:
I also applied that update and lost root. z4root wouldn't work anymore, SuperOneClick did the trick! Thanks for the help!
Click to expand...
Click to collapse
You are welcome!

Qman, thanks for you help. I did simply run the onerootclick app and it worked perfectly!

Hmm. Turned on USB debugging, ran SuperOneClick as admin but getting stuck as "Waiting for device......"

Soundchasr said:
Hmm. Turned on USB debugging, ran SuperOneClick as admin but getting stuck as "Waiting for device......"
Click to expand...
Click to collapse
Did your PC detect the tab? Are drivers installed? Other people did this trick smoothly.

qmanager said:
Did your PC detect the tab? Are drivers installed? Other people did this trick smoothly.
Click to expand...
Click to collapse
Funny you should mention that. Every other time, my pc would see it immediately. This time it isn't seeing it all.

Soundchasr said:
Funny you should mention that. Every other time, my pc would see it immediately. This time it isn't seeing it all.
Click to expand...
Click to collapse
It is not so funny, many people just are trying rooting without drivers... Please see some details here, it may help probably

Where do I get the drivers and how do I install? I found SuperOneClick1.8ShortFuseDrivers but I'm not sure if that's it and how to install if it is.
Thanks.

It took a while but I finally found the drivers and was able to root successfully. However Titanium backup still says it can't get root access....
EDIT: I had debugging off. Works now.

I have been putting off doing the VGT update for fear of having to reroot or something else going wrong but I got sick of that pop up so I said what the hell and went for it. . . .
And I still have root. . .
But I am running just about stock everything, I have not found or seen any good reason to run a custom rom yet.
Now it there was a way to run CM7 I would love that!! I have that on my Evo and love how fast my phone is.
But to the point. . . Are we all getting the same update? Again I just did it and I have not lost root.

qmanager said:
After any ROM update root has to be lost. On new ROMs z4root does not work, that is right. Try to find SuperOneClickv1.7_ShortFuse - it really works with latest updates. Put the package on your C:\ disk. Run executable with administrator rights, otherwise it will not work out. If you have any anti-virus running on PC - stop it before copying the package to disk, otherwise it will immediately kill one of the files in package (this one is not a virus!).
Hope this helps.
Click to expand...
Click to collapse
THANKS!!!! Worked like a charm.
I was previously rooted with Z4. I installed the "mandatory" Verizon update and of course lost root, Z4 and Superuser no longer worked. Found your post, tried it on my XP SP3 machine with no luck, kept coming up with daemon not running or something like that. Just now tried it on a Vista machine and it worked flawlessly. I did have to reboot for it to work, did not see that mentioned anywhere here, but after a reboot my apps that require rooting are once again working.

ucyifly said:
I did have to reboot for it to work, did not see that mentioned anywhere here, but after a reboot my apps that require rooting are once again working.
Click to expand...
Click to collapse
It is not mentioned because it is considered to be done "by default" - after any system update a tablet must be rebooted...

[XOOM2/XYBOARD][HOW TO] Motorola Xoom 2/Xyboard Everything Root and more!

XOOM2/Xyboard Everything root and more!
From 26/03/2014, I will no longer be updating this post as I no longer have the device and Motorola won't be upgrading the device further. Please instead of sending me PMs, go to the Q&A board or post your comment on this thread.
Note: This method will not work on Windows 8. Only Windows XP, Vista, 7, Linux and Mac OS X is supported.
Root Method - Honeycomb
1. Download the Windows version here, or the Linux/OSX version here.
2. Your Computer must have Motorola Drivers installed before rooting and connect your device with debugging on to your computer via USB. (Mac Users don't need drivers)
3. Extract the zip file from the download link, and run “run.bat” (on Windows) or “run.sh” from a terminal (on Linux/OSX)
4. Your device should reboot a few times during the process, don't worry.
5. Then you should see a finished message on the Root Method Window. At this point your device is safe to be removed from the computer.
7. As you are running Honeycomb if you are reading this then you should be receiving the ICS OTA soon. So lets backup your root so you can restore everything root after the upgrade (saves time). Download OTA Rootkeeper and backup root.
6. Well Done! You have root. Enjoy root and be safe.
Blog Post: Here
Root Method - Ice Cream Sandwich
1. Connect your Xoom2/Xyboard via USB to your Windows PC. Install Motorola Drivers from here.
2. Under Settings > Developer Options > Hit the "Enable USB Debugging" selection.
3. Download the Root Installer from here. (Says for Droid RAZR but also works on Xyboard and Xoom 2]
4. Unzip the download.
Bootstrap/Safestrap[Custom Recovery]
Waring: DO NOT proceed if you are inexperienced. bootstrap is messy and is only needed once we have ROMs cooking. All questions about the recovery ask in the developer thread.
1. Install the Bootstrap APK file.
2. Allow Superuser Powers.
3. Read the instructions which is displayed on the user interface.
5. You will now see a splashscreen after you reboot (before boot animation), here you can decide if you want to enter recovery or continue with boot.
-Method Under Constuction-
Unroot or temporary unroot
Temp Unroot - If you need to unroot for any reason and come back at any time, then install OTA Rootkeeper and then select the option "temp unroot). This will remove root without restarting and you can restore by a touch of a button.
Full remove of Root - If you want to complety remove root all together, if you need to send in your device for repair or trading your device. Install Ginger Unroot and continue with the onscreen instructions. This application has confirmed to work on the Xoom2/Xyboard.​

Doing it right now

Linux version has a wrong link or not uploaded yet

mdcykkk9 said:
Linux version has a wrong link or not uploaded yet
Click to expand...
Click to collapse
Should be working now.

Thx is working now . i just made a donation to his paypal account. i hope for future support for the tablet .

Thanks, is good news. Now we just need that we have updates to fix bugs, and if it can be ics ...
This is worth a donation to continue the work.

édit : error, sorry, it's ok

Working well ! Thank you.
I rooted my Xoom 2 ME bought in France.
But I cannot update to 3.2.2 ???
My build 1.6.0_218.3-MZ607 ,current version 3.2

Would this work for Xoom 1 wi-fi version ?

ouatitw said:
Would this work for Xoom 1 wi-fi version ?
Click to expand...
Click to collapse
This root method should work on all Motorola Devices running honeycomb or gingerbread. Try it out and see if it does
Sent from my Motorola Xoom 2

I did the US ICS update on My UK Xoom so im on 4.03 at the moment - i believe Motorola added some file which prevents me so far from rooting with the current one click programs ? so would it be safe to try this ?

ouatitw said:
I did the US ICS update on My UK Xoom so im on 4.03 at the moment - i believe Motorola added some file which prevents me so far from rooting with the current one click programs ? so would it be safe to try this ?
Click to expand...
Click to collapse
The method is safe to try but Email Dan if you have any issues when rooting.

Thanks a lot Dan Rosenberg,
Suppose i root my device and if i need to use my warranty at later point of time.
Is there is anyway that i can hide Motorola that i have rooted my device.

luke.arran said:
The method is safe to try but Email Dan if you have any issues when rooting.
Click to expand...
Click to collapse
I wouldn't email Dan, I'd post it here... Dan probably has more than enough things going on than to answer all rooting questions on here...
This root method very well may work on the Xoom with ICS, never hurts to try it. I don't see how you can't root with an existing method though, with the Xoom being fully unlockable and all...

Elysian893 said:
I don't see how you can't root with an existing method though, with the Xoom being fully unlockable and all...
Click to expand...
Click to collapse
the thing is that maybe you can, but you might not want to Unlocking wipes all your data, apps, etc and also permanently sets a variable stating that your warranty is gone.
It might, for example, be desireable to create a backup of all your apps and data using titanium backup, which requires root, before unlocking your xoom.

Does this mean that more knowledgeable folks can create custom ROMs now, or does that still require an unlocked bootloader?

Trackz said:
Does this mean that more knowledgeable folks can create custom ROMs now, or does that still require an unlocked bootloader?
Click to expand...
Click to collapse
No, we need to figure out a bootstrap for custom roms. No custom kernels.
Also, the method to fix adb remount is reset every other boot by the kernel, init.rc rebuilds local.prop on reboot as a failsafe and can't be changed without a custom kernel...

Response to luke.arran
luke.arran said:
This root method should work on all Motorola Devices running honeycomb or gingerbread. Try it out and see if it does
Click to expand...
Click to collapse
Just to let you know this does not work on all Xoom models like you say. Here is my thread with my specs in it. I have tried it three times following the directions to a T and it never gets past;
"[*] Initiating Phase 1...
[*] This may take a few minutes, don't mind the buzzing."
I have now let it run for over an hour each time and it never goes any further and my Xoom is still not rooted. It did not even ever reboot on its own. Does anyone have any suggestions? If not I'll just use some threads 1 & 2, I got from a friend.
Thanks, InfiniteImmortal

llama-power said:
Unlocking wipes all your data, apps, etc
Click to expand...
Click to collapse
Not this method. It is supposed to unlock and root motorola devices in 10 minutes without deleting any files. When I read about this on android police I was very excited as I never rooted because I only needed Superuser for my Xoom (never was interested in ROMs) and could never justify scraping everything just for this.
I tested the files here on a windows 7 machine... if I run from command at step 2. I get su permission denied. If I run the batch file I get "failed backup" loop after the device has been detected
tried the portable one click .exe found in "Motofail: Universal Motorola Android Root Tool (Portable)" works perfect on my bionic
obviously fails to remount as it does not include local.prop from step 5. so it's not working on xoom
This is the most awesome root utility I ever came along. It took something like 6 mins to root my phone without losing any files, if I can get it to run on my Xoom this will be just a dream come true!

Update: This root method does not support the Original Xoom. Confirmed by Dan.

[Q] 4.1.2 update enquiry after unlocked, rooted. kernel changed

Hi,
I am new to this forum and android stuff.
Please forgive me if I asked noob question.
I tried to search but got no complete answer.
My condition:
Nexus 7
build number JRO03S
used Nexus root toolkit 1.5.3
to unlock and root
used TWRP to install poitee kernel for usb dac.
Then:
The 4.1.2 updates notification show up
I pressed yes ... accidentally.
Now:
The build number becomes JRO03S
but the Android version is still 4.1.1
Question:
a. How to update to 4.1.2?
b. How to update without wiping any data and apps?
c. Do I have to reinstall the pointee kernel?
d. Will flashing rom ( updating to newer version ) wipe all things?
Sorry for so many questions,
For my situation it is a mixed up that I can't find similar condition on the internet yet.
Please kindly help and advise.
Much Thanks!

Btw,
I done below, no success:
1. quickboot
2. TWRP recovery
3. install nakasi-JZO54K-from-JRO03S.zip (from /sdcard)
4. error --> "Status 7" shown.
Cannot update.
Please Please help....

Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.

There is a modified version of the update that someone made. It doesn't perform the system checks that cause so many peoples devices to fail. If you can't run the update because you changed or deleted a system apk, read this post: http://forum.xda-developers.com/showpost.php?p=32752631&postcount=20
Don't run this if you're just not sure of why your update is failing.

vinny86 said:
Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.
Click to expand...
Click to collapse
Understood and Thanks a lot!!!:good:
that means all in all,
I still have to go through
the route of "Backup all --> Flash Stock & unroot --> Root --> Restore all".
However, considering the latest update seems don't have anything important or useful to me
So I just wait for the next more important update.
and save the drudgery next time.

vinny86 said:
Use the wugs toolkit and go back to fully stock ROM, re lock the bootloader.
Only then will you be able to apply the OTA update.
backup your app data using titanium backup.
Click to expand...
Click to collapse
He doesn't need to lock his bootloader, and he'll still not be able to run the update the natural way as long as he's got twrp or cwm installed. He can flash the factory rom and push the update through using custom recovery though.

Visa Declined said:
There is a modified version of the update that someone made. It doesn't perform the system checks that cause so many peoples devices to fail. If you can't run the update because you changed or deleted a system apk, read this post: http://forum.xda-developers.com/showpost.php?p=32752631&postcount=20
Don't run this if you're just not sure of why your update is failing.
Click to expand...
Click to collapse
Thanks for you advise,:highfive:
it is very kind of you to help.
I think may be the Status 7 error could be caused by the Custom Kernel Installed (poitee)
I better ask him in detail later on.
But mine is JRO03S,
May be it is safer to Return to Stock Rom completely and go for OTA later.
Sadly, This 4.1.2. seems got no very useful component to me,
I solely use it as a second PDA and Music Player with USB DAC.
I will have to wait for better solution then.....

pleaseabcd said:
However, considering the latest update seems don't have anything important or useful to me
Click to expand...
Click to collapse
The latest update allows you to boot into recovery mode without being plugged into usb. Now, if I get stuck in a bootloop, I don't have to look for something to plug my device into to restore. This feature alone is worth whatever hassle one may have to do to update.

Visa Declined said:
The latest update allows you to boot into recovery mode without being plugged into usb. Now, if I get stuck in a bootloop, I don't have to look for something to plug my device into to restore. This feature alone is worth whatever hassle one may have to do to update.
Click to expand...
Click to collapse
O'really.....em...then it is a different story..(Safer for the future...)
Perhaps, I just:
1. use Titanium Backup to back up everything --> copy the "Back up" to PC (just in case)
2. use Wugfresh Nexus Root Toolkit 1.5.4 to Flash Stock n Root
3. if can Flash to 4.1.2 stock rom directly, OK
4. if can't --> flash back to 4.1.1 stock rom (JRO03S) and then OTA
5. Finally, use Titanium backup to restore Everything.
Have to Thank You you guys again!
I know I am a newbie... but I am learning......
Hate to be limited to what I was given......while I can experiment and make mistake to grow up !:laugh:

[Q] Problems with the root after 4.2.2 update

Hello everyone, I am fairly new to rooting, roms and what not. The only other experience I had rooting something was with my old g2x. Anyways, I was reading everywhere that the new 4.2.2 OTA update was available and people had provided urls. I decided I would go ahead and root my nexus 10 while it was on 4.2.1. I followed the instructions with rooting a nexus 10 by using the nexus root toolkit by WugFresh. I followed every instruction (backing up, unlocking, then rooting) without making any mistakes. Everything went fine with the rooting process until i tried to install a paid app. I then went ahead and looked up what the -24 error was. They said to fix it i needed to go into data/data and delete the folders. This is when I realized the my root hadn't worked. The unlock worked but the root didnt. I downloded rootchecker and it said I wasnt rooted. Now I'm attempting to root my nexus 10 again but it keeps saying my adb device is listed as offline. No matter what I do, uninstalling all the usb drivers related to google and such, wiping my nexus 10 etc. I can't get it to root. Some assistance is needed! Anything I can do to root my tablet?

itstommy said:
Hello everyone, I am fairly new to rooting, roms and what not. The only other experience I had rooting something was with my old g2x. Anyways, I was reading everywhere that the new 4.2.2 OTA update was available and people had provided urls. I decided I would go ahead and root my nexus 10 while it was on 4.2.1. I followed the instructions with rooting a nexus 10 by using the nexus root toolkit by WugFresh. I followed every instruction (backing up, unlocking, then rooting) without making any mistakes. Everything went fine with the rooting process until i tried to install a paid app. I then went ahead and looked up what the -24 error was. They said to fix it i needed to go into data/data and delete the folders. This is when I realized the my root hadn't worked. The unlock worked but the root didnt. I downloded rootchecker and it said I wasnt rooted. Now I'm attempting to root my nexus 10 again but it keeps saying my adb device is listed as offline. No matter what I do, uninstalling all the usb drivers related to google and such, wiping my nexus 10 etc. I can't get it to root. Some assistance is needed! Anything I can do to root my tablet?
Click to expand...
Click to collapse
I recommend trying the Nexus 10 Toolkit 1.3.0. I successfully rooted my 4.2.1 N10 with this tool a few days ago (and promptly lost it in the OTA). http://forum.xda-developers.com/showthread.php?t=2001868

nalf38 said:
I recommend trying the Nexus 10 Toolkit 1.3.0. I successfully rooted my 4.2.1 N10 with this tool a few days ago (and promptly lost it in the OTA). http://forum.xda-developers.com/showthread.php?t=2001868
Click to expand...
Click to collapse
Yeah, but the thing is it doesn't recognize the device being plugged in. I don't know what else to do. I've tried using that toolkit (the one click all) and it wont even start.

itstommy said:
Yeah, but the thing is it doesn't recognize the device being plugged in. I don't know what else to do. I've tried using that toolkit (the one click all) and it wont even start.
Click to expand...
Click to collapse
Have you tried the Naked ADB drivers? What Windows OS are you using?

nalf38 said:
Have you tried the Naked ADB drivers? What Windows OS are you using?
Click to expand...
Click to collapse
where did you find the naked drivers? I'm running W7 64 bit. I only installed the drivers that came with pdanet as required by the guide I followed. Now im stuck in an unrooted 4.2.2.

ADB mode offline Both toolkits
nalf38 said:
I recommend trying the Nexus 10 Toolkit 1.3.0. I successfully rooted my 4.2.1 N10 with this tool a few days ago (and promptly lost it in the OTA). http://forum.xda-developers.com/showthread.php?t=2001868
Click to expand...
Click to collapse
I too have the same problem. Been searching for hours trying to find a solution.
I have tried both Wug's and mskips (paid version) toolkits and still the device shows offline.
I have ADB debuging enabled and tried in PTP and MTP modes. Have uninstalled the drivers and tried the PDAnet versions as well as the ones from mskips toolkit.
Both toolkits show that the device is connected, and I have booted to recovery and done the driver install (sees it as a Nexus 4 btw), but it's in offline mode.
My G-Nex works just fine, and I'm no stranger to rooting/custom roms. Not sure if having both devices loaded on this laptop is the issue.
Any help would be appreciated
Thanks
Jim

mrlow999 said:
I too have the same problem. Been searching for hours trying to find a solution.
I have tried both Wug's and mskips (paid version) toolkits and still the device shows offline.
I have ADB debuging enabled and tried in PTP and MTP modes. Have uninstalled the drivers and tried the PDAnet versions as well as the ones from mskips toolkit.
Both toolkits show that the device is connected, and I have booted to recovery and done the driver install (sees it as a Nexus 4 btw), but it's in offline mode.
My G-Nex works just fine, and I'm no stranger to rooting/custom roms. Not sure if having both devices loaded on this laptop is the issue.
Any help would be appreciated
Thanks
Jim
Click to expand...
Click to collapse
You're not researching in the right places. Wug's toolkit 1.6.2 have been confirm by the developer to not be working properly and he states that an update is in the horizon so be patient. Also, if you click on his website he wrote a paragraph about a temporary fix and he gives you a zip file so you can replace the files on the computer. I can assure you it works. If the files are replaced properly your device will show online instead of offline.
Here is his website where he gives you the tools to make it work: http://www.wugfresh.com/nrt/

THANK YOU SO MUCH FOR POSTING THIS. I've been scouring the forums everywhere just trying to fix this when the answer was right under my nose.

Thanks!
RawBott Bigg said:
You're not researching in the right places. Wug's toolkit 1.6.2 have been confirm by the developer to not be working properly and he states that an update is in the horizon so be patient. Also, if you click on his website he wrote a paragraph about a temporary fix and he gives you a zip file so you can replace the files on the computer. I can assure you it works. If the files are replaced properly your device will show online instead of offline.
Click to expand...
Click to collapse
Thanks a bunch! :good:
I did finally get it working late last night using mskips toolkit (donate version). Went without a hitch.
I can't believe I didn't see that. It's easy to miss something when you're frustrated, and not thinking about the right search terms.
The solution I found was it was a permission problem. As soon as I tried to do something with the toolkit, I got a popup on the tablet asking if I wanted to let my laptop control it. As soon as I said yes and always it worked beautifully. Had to do it again when it did the factory reset, but I was ready that time.
It threw me for a loop, never had to do that with my GNex or my OG Droid.
For now, I'll stick with mskips toolkit.
Thanks again.
Jim

[Q] Bricked by Nexus (and I'm not a techie)

Hi everybody.
Okay I'm not a techie. I managed to root my nexus 4 running android 5.0.1 with kingo root. I wanted the OTA 5.1 UPDATE, so unrooted, tried the OTA and it failed.
I've installed minimal adb and fastboot but after various goes I'm no further on. Is my phone ruined?
Under system recovery I'm now showing LMY470. If I try and reboot I just get the google display.
PLEASE - can anybody help (I go on holiday on Sunday and really need my phone!)
Hope somebody can help
Rob

Just flash the factory image with fastboot.
Download the factory image, extract it. In there is a flash-all batch file
Boot into the bootloader and connect your device to the pc
Double click on the flash-all
Note, this will wipe your device.
Sent from my Nexus 5 using XDA Free mobile app

robigouk said:
Hi everybody.
Okay I'm not a techie. I managed to root my nexus 4 running android 5.0.1 with kingo root. I wanted the OTA 5.1 UPDATE, so unrooted, tried the OTA and it failed.
I've installed minimal adb and fastboot but after various goes I'm no further on. Is my phone ruined?
Under system recovery I'm now showing LMY470. If I try and reboot I just get the google display.
PLEASE - can anybody help (I go on holiday on Sunday and really need my phone!)
Hope somebody can help
Rob
Click to expand...
Click to collapse
Your phone is not ruined.... You may need to have to flash the image again. You might want to try using the "Nexus Root Toolkit"
Just search for it It will walk you through the whole process. You might also search for the SkipSoft Android Tool Kit.
I hope that helps Let us know how you get on

Blacksmith5 said:
Your phone is not ruined.... You may need to have to flash the image again. You might want to try using the "Nexus Root Toolkit"
Just search for it It will walk you through the whole process. You might also search for the SkipSoft Android Tool Kit.
I hope that helps Let us know how you get on
Click to expand...
Click to collapse
All done. manged to put no the original 4.3 and then let it do all the OTA stuff. dont' think I'll be rooting again, put me off!

robigouk said:
All done. manged to put no the original 4.3 and then let it do all the OTA stuff. dont' think I'll be rooting again, put me off!
Click to expand...
Click to collapse
When you say you "unrooted", how did you do so? I have found with 5.+ that in order for the OTA to not fail when you have been rooted, requires that you flash the stock images for the current version, as opposed to Factory Resetting, and then you will be able to install the OTA update without it failing. Has to do with out the updater checks the entire partition and not pieces, which is a new method. If one byte of data is out of place on System partition, it OTA fails.