Yeah, I wasn't thinking at all. I ran my update check, got excited and just did it. It wasn't until after the fact that I really realized what I might have done.
Well, here's everything that happened/is happening.
I was trying to root my pad and get cwm. The pad was running stock 3.1 at the time this.
Well, after a bit of reading and looking around, I decided the easiest way would be to use the batch script located here: http://forum.xda-developers.com/showthread.php?t=1185104
After setting everything up, I ran the script. My tablet was rooted, I could gain superuser access, and busybox was installed as well...however, I could not get into recovery. At all.
In the zip for the rootkit there are two versions of recovery.img, one to use if the other doesn't work...
Well they both didn't work.
So I play around on my tablet for a while and read about 3.2, check my updates and see that I can get the 3.2 update. I do it, install it.
Stupid.
Now the pad is stuck on the Eee Pad screen with the Asus and nVidia Tegra logo.
I can get into APX mode as well as make the tablet attempt to boot into recovery (though it just hangs on "Booting recovery kernel image").
Can't even turn it all the way off, it just hangs.
I tried downloading the v5 (now v6) script from the above thread, and used all of the options included within, including the 3.2 root & recovery. To no avail.
Seems pretty grim.
My phone is a Samsung Epic which I've rooted, flashed roms, upgraded/downgraded Android... With the phone there's a program to completely unroot and flash back to stock. Is there something like that with tablets?
I might've dived into rooting my tablet before reading enough, I read a significant amount before I did anything to my phone, but I convinced myself the prior experience would make this easy. Obviously not the case.
So...any help would be hugely appreciated. Even if it's just telling me that there's not really anything I can do, because I'll be able to take it back for another (though that can be complicated and is preferably avoided).
since you can get to apx mode try nvflash with stockrom to 8.4.4.5 by following these instructions.
http://tabletroms.com/forums/showthread.php?1071-Factory-3.1-NVFlash-Recovery-Roms&p=9968
You'll then need to upgrade to 8.4.4.11 then to 8.6.5.6 before attempting to root using the v5 beta batch root script http://forum.xda-developers.com/showthread.php?t=1185104
That should get you out of trouble. good luck.
IMHO the problem is the recovery.
The ota updates rely on the stock recovery image for doing its dirty work; for what you wrote, it seems that you have installed cwm...
In the batch script hit "5" to reinstall stock boot+recovery us images.
If this won't work, try the woonie's hint.
Hope this helps.
woonie said:
since you can get to apx mode try nvflash with stockrom to 8.4.4.5 by following these instructions.
http://tabletroms.com/forums/showthread.php?1071-Factory-3.1-NVFlash-Recovery-Roms&p=9968
You'll then need to upgrade to 8.4.4.11 then to 8.6.5.6 before attempting to root using the v5 beta batch root script http://forum.xda-developers.com/showthread.php?t=1185104
That should get you out of trouble. good luck.
Click to expand...
Click to collapse
Woonie is correct, I did this to myself last week. After using NVFlash to get back to stock 8.4.4.5, do not let the pad restore settings from your gmail account. Wait for that until after you have it upgraded to 8.6.5.6 and rooted it again to sync up to your account.
http://forum.xda-developers.com/showthread.php?t=1192072&page=2
I follow jhanford's post and get this done.
Hi all,
I have a Transformer Prime and unfortunately I used the "official" unlock (APK) supplied by ASUS. Now I got the message "The divice is unlocked" when it boots up but I am not able to use TITANIUM BACKUP and other tools anymore because the viperMOD PrimeTime v4.1(program to unlock) also always fails.
Is there any possibilty to undo the prodedure to get an unlocked device again an then to use viperMOD PrimeTime v4.1???
Any help would be very very appreciated.
Greetings from Germany
Hans
I believes once you unlocked your device bootloader u also need to rooted your device as welll.....Vipermod v4.5 is your best choice and ts easy to do......once u rooted your device those apps you mentioned should work fine.....also boot keeper is important after rooted so in case u need to update your device you can just temp unrooted it and update......after that just go back to root keeper and restore it back on.......always temp unrooted your device before updated it cause i did it and my prime got stuck on recovery for bout a week was going nuts, eventually i got it back stock rom again.....cause i had done a back up previously which safe my life so good luck.
Thx a lot but it fails!
weakenfalls said:
I believes once you unlocked your device bootloader u also need to rooted your device as welll.....Vipermod v4.5 is your best choice and ts easy to do......once u rooted your device those apps you mentioned should work fine.....also boot keeper is important after rooted so in case u need to update your device you can just temp unrooted it and update......after that just go back to root keeper and restore it back on.......always temp unrooted your device before updated it cause i did it and my prime got stuck on recovery for bout a week was going nuts, eventually i got it back stock rom again.....cause i had done a back up previously which safe my life so good luck.
Click to expand...
Click to collapse
Thx for your quick answer. Sorry to say that Vipermod 4.5 does not work (see link to the pic).
Maybe its due that I have Build 9.4.2.21 (the latest).
To see the errorrs pls use this link:
dl.dropbox.com/u/19088805/Root1.png
There seems to be a prob with SYSTEM\BIN\SU (at least). This may be the reason because also SparkyRoot fails. I do not think that is due to the "official" ASUS boot unlocker which I installed (other people had success to root their device WITH Asus boot unlocker). I am rather sure it's because the build number.
Hm, do you have another idea???
Happy Easter from Germany
Hans
Yes your problem is the build. As of now build .21 cannot be rooted (see this thread http://forum.xda-developers.com/showthread.php?p=21007398).
If your device is already unlocked you could install a custom ROM (like VirtuousPrime.21).
Personally, I'm screwed right now. I had my .15 build rooted. And I installed a root keeper. When I upgraded to .21 the root keeper failed to restore my root.
So I thought I'd go the unlock route and install VP.21. But I can not unlock my bootloader. I have a Prime that has a bug where the S/N isn't listed in my tablet. This bug prevents the unlock app from unlocking the bootloader (was also the reason I could never OTA update my firmware). And the Ratchet tool fix for the S/N relies on the same mempodroid exploit as Vipermod that no longer works on .21 build.
Arggg!
Beermiester said:
Yes your problem is the build. As of now build .21 cannot be rooted (see this thread http://forum.xda-developers.com/showthread.php?p=21007398).
If your device is already unlocked you could install a custom ROM (like VirtuousPrime.21).
Personally, I'm screwed right now. I had my .15 build rooted. And I installed a root keeper. When I upgraded to .21 the root keeper failed to restore my root.
So I thought I'd go the unlock route and install VP.21. But I can not unlock my bootloader. I have a Prime that has a bug where the S/N isn't listed in my tablet. This bug prevents the unlock app from unlocking the bootloader (was also the reason I could never OTA update my firmware). And the Ratchet tool fix for the S/N relies on the same mempodroid exploit as Vipermod that no longer works on .21 build.
Arggg!
Click to expand...
Click to collapse
Hi,
thx for your answer. I downloaded Virtual Prime as you suggested. Before that I used Vipermod to install CWM. But during doing that there came an error message: \data\local\cwminstall: su: not found.
It's always the su-messages that drive me crazy!!
Then when shutting down the Prime and rebooting (volume down then volume up) it always fails (the lying android with the red exclamation mark!)
Do you know what went wrong?
BTW: Vipermod states on Option #5 (installing Unlocker and CWM):"Must be rooted". But my Prime ISN'T rooted... that's exactly that that I want to achive :=)
So my main problem is: how to install CWS. It always fails
Would be great if anyone could help me out of this!
all the best and greetings from Germany
Hans
handi1948 said:
Hi,
thx for your answer. I downloaded Virtual Prime as you suggested. Before that I used Vipermod to install CWM. But during doing that there came an error message: \data\local\cwminstall: su: not found.
It's always the su-messages that drive me crazy!!
Then when shutting down the Prime and rebooting (volume down then volume up) it always fails (the lying android with the red exclamation mark!)
Do you know what went wrong?
BTW: Vipermod states on Option #5 (installing Unlocker and CWM):"Must be rooted". But my Prime ISN'T rooted... that's exactly that that I want to achive :=)
So my main problem is: how to install CWS. It always fails
Would be great if anyone could help me out of this!
all the best and greetings from Germany
Hans
Click to expand...
Click to collapse
The problem, I think, is that you're trying to use the "my Prime is rooted" method of installing CWM.
Try the non-rooted instructions found here: h t t p : //androidroot.mobi/2012/02/22/introducing-cwm-for-asus-transformer-prime/
Also, check out the video here for a how to install CWM. h t t p : //transformerprimeroot.com/transformer-prime-recovery/how-to-install-clockworkmod-recovery-5-8-2-0-on-transformer-prime/
When you do a recovery boot of your Prime do you get 3 options? One being a USB symbol? If you have the USB symbol when you do your recovery boot (ie you've unlocked your bootloader), you can flash CWM onto your Prime.
Thank you . . .n now I have ROOT!!!
Beermiester said:
The problem, I think, is that you're trying to use the "my Prime is rooted" method of installing CWM.
Try the non-rooted instructions found here: h t t p : //androidroot.mobi/2012/02/22/introducing-cwm-for-asus-transformer-prime/
Also, check out the video here for a how to install CWM. h t t p : //transformerprimeroot.com/transformer-prime-recovery/how-to-install-clockworkmod-recovery-5-8-2-0-on-transformer-prime/
When you do a recovery boot of your Prime do you get 3 options? One being a USB symbol? If you have the USB symbol when you do your recovery boot (ie you've unlocked your bootloader), you can flash CWM onto your Prime.
Click to expand...
Click to collapse
Hi,
great reply!!! That helped me a lot - espec. the video. Some instructions are unclear (sometimes spoken of "terminal-input" ... I thought a terminal program input on the Prime!!!).
OK I pushed CWM on the Prime, got me a copy of "WW_ROOTED_CWM_Primeval_Stock_9.4.2.21-signed.zip", flashed the ZIP ... and now I have an boot-unlocked device AND I have root. Titium, Root Explorer and all my other "dear friends" work as they are exspected to do :=)
Once again THX A LOT and if you need something I could help: drop me a line!
Hans
I have done a lot of reading her about rooting and updating my TF300. After getting a headspinning amount of information, I'd like someone to verify what I think I know.
I have a TF300, stock ROM, no root, running US .17. I have not received any updates after going to Settings/about tab/update and pressing the update button (I get "no updates found') I have cleared DM and CM client and rebooted several times, but no updates are found. I have tried on several WiFI networks I have access to.
1. I should be able to root using one of several one click methods I have found here, correct?
2. Once rooted and root keeper is installed, I should be able to update to .29 and keep root, correct?
3. A manual update to US .29, once rooted, will cause me to lose root, correct?
4. Will I receive Over The Air update once rooted? If not, how can I update to US .29 without losing root?
5. Is this the best path to take, or is there another path that would be easier for a newb like me (I know just enough about Android to be dangerous)? What I mean by another path is, should I manually update to US .29 and wait for a one click solution to come out later, all the while enjoying the new update.
6. All this is to fix some lag issues I have with all browsers....Tried Stock, Dolphin, Firefox, Opera...all the same. Some FC and others just hang for up to 30 seconds, even in Performance mode (With only one tab open!) So this will "FIX" those lag issues, correct?
Thank you for your time
If you're still on .17, root with sparkyroot, save it with ota rootkeeper, update to .29 (if it isn't there, they've been posted in many places on the forums), and restore root. As for fixing lag issues, it depends on what you do, rooting alone won't change anything, but you can try out the different tweaks available.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Missed a couple of your questions, yes, you will still receive ota updates if you're rooted, as long as you don't unlock the bootloader. This is the easiest way to root too, all you need to do is follow sparkyroot's instructions and back up your root.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
One question always leads to another
Thank you! But of course, I now have just a few more questions.
I do understand rooting alone will not help me with my lag issues. I'm hoping the update to .29 will. I am not a power user, but I would like the option open to me later to install ROMs, hence why I want to root now.
1. I thought I had to unlock bootloader to root. With sparkyroot I do not?
2. Since I have not unlocked bootloader, will rooting alone void my warranty? I thinking not since I should be able to unroot with no trace, correct?
3. I thought, (or read somewhere here, I think) that if I do a MANUAL install, I would lose root and be unable to regain it. If I get an update PUSHED to me by ASUS, Ill be able to regain root with rootkeeper. Is that correct?
I'd like to thank everyone here, by the way, for all the information I have gotten in my 30 days of owning this tablet and lurking here.
Throb1231 said:
Thank you! But of course, I now have just a few more questions.
I do understand rooting alone will not help me with my lag issues. I'm hoping the update to .29 will. I am not a power user, but I would like the option open to me later to install ROMs, hence why I want to root now.
1. I thought I had to unlock bootloader to root. With sparkyroot I do not?
2. Since I have not unlocked bootloader, will rooting alone void my warranty? I thinking not since I should be able to unroot with no trace, correct?
3. I thought, (or read somewhere here, I think) that if I do a MANUAL install, I would lose root and be unable to regain it. If I get an update PUSHED to me by ASUS, Ill be able to regain root with rootkeeper. Is that correct?
I'd like to thank everyone here, by the way, for all the information I have gotten in my 30 days of owning this tablet and lurking here.
Click to expand...
Click to collapse
No need to unlock for root. They are completely unrelated. Just update manually and use THIS THREAD to root .29. There's even a one-click tool like you wanted. Don't forget to press Thanks for miloj.
Oh, and after you've updated to .29 and rooted; don't forget to use OTA rootkeeper to backup root.
If Asus releases a new update it may save your root.
EndlessDissent said:
No need to unlock for root. They are completely unrelated. Just update manually and use THIS THREAD to root .29. There's even a one-click tool like you wanted. Don't forget to press Thanks for miloj.
Click to expand...
Click to collapse
He's still on the .17 software, so no need to do that. Just use the sparkyroot method, backup with rootkeeper and then update.
Edit to add that no, rooting will not void the warranty, just unroot before you need to send it back.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Yeah, he's still on .17, but he's not getting the OTA prompt. He wants to manually upgrade, and you can't restore root after a manual upgrade, so my advice still stands.
Thank you both! Rooted with Sparky root and backed up with OTA rootsaver. Now I have downloaded the .29 update from ASUS webpage and installed. It says I have lost root.
I tried to restore root with OTA and it says SU restored, however it does not show that I have root access. Tring to use Titanium BU also shows I do not have root.
Tried then to go back to Sparkyroot and try again, but to no avail. Do I now have to downgrade back to .17 to gain root because I messed it up, or is there a solution? I was rooted for several hours before the upgrade to .29.
Throb1231 said:
Thank you both! Rooted with Sparky root and backed up with OTA rootsaver. Now I have downloaded the .29 update from ASUS webpage and installed. It says I have lost root.
I tried to restore root with OTA and it says SU restored, however it does not show that I have root access. Tring to use Titanium BU also shows I do not have root.
Tried then to go back to Sparkyroot and try again, but to no avail. Do I now have to downgrade back to .17 to gain root because I messed it up, or is there a solution? I was rooted for several hours before the upgrade to .29.
Click to expand...
Click to collapse
No, you need to go to:
h tt p://forum.xda-developers.c om/showthread.php?t=1704209 (sorry for the chopped up link. I can't post links yet)
and root again.
EndlessDissent said:
Yeah, he's still on .17, but he's not getting the OTA prompt. He wants to manually upgrade, and you can't restore root after a manual upgrade, so my advice still stands.
Click to expand...
Click to collapse
Ah, ok. Didn't realize you couldn't restore if you updated manually.
Yes, it is as I thought. Tried Sparkys and miloj's root program and I can not get root. I ran the program twice from my lap top. Driver's for TF300 show installed in Device manager (Windows 7). ASUS sync was installed in laptop and recognized TF300 but the program was not running during root attempt.
When I run Superuser and attempt to update SU binaries, I get "Failed" when it attempts pathway to write update.
Attempted to restore using OTA rootkeeper but all I get is "SU Restored". Check boxes indicate no root.
Any other ideas?
Confirmed I am on .29 from a MANUAL update.
Tried again from home computer. Ran Sparky and miloj program. I get error stating
"failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk' : not a directory"
Tablet reboots and says I should be rooted but obviously not. Superuser not written to tablet
Throb1231 said:
Tried again from home computer. Ran Sparky and miloj program. I get error stating
"failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk' : not a directory"
Tablet reboots and says I should be rooted but obviously not. Superuser not written to tablet
Click to expand...
Click to collapse
Can you just install Superuser from the market? The su binaries might be there and the app just isn't installing. I may be wrong, not sure how the automated program works, but it can't hurt.
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Throb1231 said:
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Click to expand...
Click to collapse
Try manually doing the code from miloj's thread?
While the instructions in his thread are clear, they are way past my level of expertise. I would not attempt it without someone standing next to me. I have not entered code since the 1980's Compute! magazine days.
Throb1231 said:
While the instructions in his thread are clear, they are way past my level of expertise. I would not attempt it without someone standing next to me. I have not entered code since the 1980's Compute! magazine days.
Click to expand...
Click to collapse
Well, I can't think of anything else, you could just use the downgrade method, that's easy enough. The code really is just copy/paste though.
Throb1231 said:
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Click to expand...
Click to collapse
Your problem is not with the superuser apk.
The actual root is when you write an "su" binary to system and makes it executable (there is some access control stuff in between, but it's what's happening in essence).
So - your trouble is not with the installation nor the messages from superuser.apk - it's with the actual rooting method.
Make absolutely sure your adb drivers are working and that you've got the files "debugfs", "su" and the other debugfs file on top of the .bat file, which is the installation script, in the same directory whilst running the .bat file.
Agreed. I posted this in development.
It was surprisingly more difficult to install the drivers correctly than anticipated.
For those noobs like me, here's a step-by-step for installing the drivers before running the root method.
http://transformerprimeroot.com/tra...all-transformer-prime-usb-drivers-on-windows/
Please note that before using the step-by-step guide above, I also had to put the tf300 in Camera Mount to even get the "“ASUS Android Composite ADB Interface" option to show up in Device Manager.
Once you get this far, you can manually update the driver (found in the sparkym3 "Drivers" folder from the download) via the step-by-step.
Sent from my ASUS Transformer Pad TF300T using XDA
Well guys, I seem to have really done it this time. I was on 4.1.2 (9.16.6) on my HDMaxx and I was having problems gaining my root access. I used Voodoo to keep root and downgraded (while I was still on 4.1.1) back to 4.0.4 and gained root, then updated all the way back up. When I did the update to 4.1.2, I seemed to have some issues with root again. RootChecker said I have root, but all my root apps said otherwise, and I was unable to update SuperUser due to the fact that it was unable to get root access. I went through the post by Dan Rosenberg (http://www.droid-life.com/2013/04/09...r-devices-too/) and it reported nothing but good news. Here's where the stupidity comes in: I didn't boot back up and test to see if the root was working. I was too excited by seeing that I could (finally) unlock my bootloader. I used the motopocalypse tool, and BAM! No recovery, no rom, no nothing. All I have is a screen that says "WARNING BOOTLOADER UNLOCKED" and if I want, I could get into AP Fastboot mode. All other options (recovery, wipe, etc.) just bring me back to the indefinite screen of the unlocked bootloader. Anyone by any chance know what I could have possibly done? Thank you in advance.
(This question was originally posted in development by accident so I moved it to Q&A)
Action123 said:
Well guys, I seem to have really done it this time. I was on 4.1.2 (9.16.6) on my HDMaxx and I was having problems gaining my root access. I used Voodoo to keep root and downgraded (while I was still on 4.1.1) back to 4.0.4 and gained root, then updated all the way back up. When I did the update to 4.1.2, I seemed to have some issues with root again. RootChecker said I have root, but all my root apps said otherwise, and I was unable to update SuperUser due to the fact that it was unable to get root access. I went through the post by Dan Rosenberg (http://www.droid-life.com/2013/04/09...r-devices-too/) and it reported nothing but good news. Here's where the stupidity comes in: I didn't boot back up and test to see if the root was working. I was too excited by seeing that I could (finally) unlock my bootloader. I used the motopocalypse tool, and BAM! No recovery, no rom, no nothing. All I have is a screen that says "WARNING BOOTLOADER UNLOCKED" and if I want, I could get into AP Fastboot mode. All other options (recovery, wipe, etc.) just bring me back to the indefinite screen of the unlocked bootloader. Anyone by any chance know what I could have possibly done? Thank you in advance.
(This question was originally posted in development by accident so I moved it to Q&A)
Click to expand...
Click to collapse
What os are you on on your computer have your drivers been updated etc
As stated in the other thread toy should be able to manually push a custom recovery via adb. Check the other thread for a link.
sent from my xt926 RAZR maxx hd
Action123 said:
Well guys, I seem to have really done it this time. I was on 4.1.2 (9.16.6) on my HDMaxx and I was having problems gaining my root access. I used Voodoo to keep root and downgraded (while I was still on 4.1.1) back to 4.0.4 and gained root, then updated all the way back up. When I did the update to 4.1.2, I seemed to have some issues with root again. RootChecker said I have root, but all my root apps said otherwise, and I was unable to update SuperUser due to the fact that it was unable to get root access. I went through the post by Dan Rosenberg (http://www.droid-life.com/2013/04/09...r-devices-too/) and it reported nothing but good news. Here's where the stupidity comes in: I didn't boot back up and test to see if the root was working. I was too excited by seeing that I could (finally) unlock my bootloader. I used the motopocalypse tool, and BAM! No recovery, no rom, no nothing. All I have is a screen that says "WARNING BOOTLOADER UNLOCKED" and if I want, I could get into AP Fastboot mode. All other options (recovery, wipe, etc.) just bring me back to the indefinite screen of the unlocked bootloader. Anyone by any chance know what I could have possibly done? Thank you in advance.
(This question was originally posted in development by accident so I moved it to Q&A)
Click to expand...
Click to collapse
Tried RSDlite to stock?... since fastboot seems to be the only thing working it may be the easiest route to have a working phone quickly.
Not sure if the Maxx is the same firmware as the XT926's but here's the verizon ones http://sbf.droid-developers.org/vanquish/list.php
and instructions for the HD http://www.andromods.com/tips-trick...-unroot-unbrick-droid-razr-maxx-hd-xt926.html
I don't know if that applies to your phone or situation.