[Q] ViperMod seems to be gone... how to root? - Eee Pad Transformer Q&A, Help & Troubleshooting

The ViperMod files return a 404 at this time. Not sure if it is a temporary problem, or permanent.
Is there an alternative to root my B60 Transformer running stock ICS? Does anyone have a saved ViperMod file they can share?
Thanks!

I am actually in a bit of a problem and really need this to root. Neither Nacho or Sparky root my tablet through their command line ways, and the Sparky Apk root doesn't work either. I rushed to reset my transformer to stock for a warranty claim I'm finally filing on a screen defect and now I have no recovery, stock .17 software and superuser in the app drawer that I can't get rid of. Pretty good combo if I do say so myself.
And sorry for jacking your thread. just in a bind and hope someone posts her so I notice too.

Ok I'll put this up for a couple of hours not sure if the OP is going to be pissed
but here it is .....Mods if this is not ok please remove
http://www.box.com/s/5662205c7a4af5caf5f6

Thanks! I am sure the OP is just having server issues, as he did not say he intended to remove it for any reason.

Related

From a B07 to a B05...Root?

Purchased an Asus Transformer about 2 weeks ago on Amazon and received a B07...the screen on it ended up having some discoloration on the sides where when something black was playing, you could see white/green discoloration marks near the edge...needless to say, I sent it back to Amazon and they just sent me a B05. Did I get lucky?
Cause I'm looking to root...And apparently I can root this model, but not the last one?
I have Windows 7. There's seems to be several different methods to root this device. I'm running 8.3.2.9.
Is it best to upgrade to Honeycomb 3.2 before you root, or after? Or should I stay with 3.1 Honeycomb...someone let me know and send me some links/files I need to get to root!
Appreciate it mucho!
Simply use the NVFlash method, that's the easiest way to do!
http://forum.xda-developers.com/showthread.php?t=1123429
Do I need to update my firmware or update to HC 3.2 before I NVFlash?
Ultimately what I'm wanting is a rooted Honeycomb 3.2 tablet...
Well, you need to grab an NVFlash package. In this very part of the TF101 forum, you'll find a lot of (actually, 3) ROMs what are rooted, optimized, and fine-tuned. I suggest you to try Prime 1.9, it's really great!
So, all you have to do is to download the NVFlash version of Prime (or any other ROM you want to install), and follow the NVFlash instructions. It will update your TF to 3.2, root it, etc.
You do not need to update to anything, as NVFlash is totally separate from Android - imagine it like a safety switch, what can be flipped if your device gets bricked (=means it won't really switch on due to software problems). It's a separate mode, can not be modified, etc.
Read this
http://forum.xda-developers.com/showthread.php?t=1268458
You should have posted in the Q&A section.
Asking a bloody obvious stupid question to which you require an answer in a DEV section is fail.
sorry to barge in but i am going to get a transformer in a few hours and i am thinking i could easily install custom roms out of the box? also does this work on all models?
CaNsA is right this shouldnt be here.
GTFO
10chars
Moderators are still too slow in here...
Sent from my Transformer TF101 using Tapatalk
TheScPCrew said:
Purchased an Asus Transformer about 2 weeks ago on Amazon and received a B07...the screen on it ended up having some discoloration on the sides where when something black was playing, you could see white/green discoloration marks near the edge...needless to say, I sent it back to Amazon and they just sent me a B05. Did I get lucky?
Cause I'm looking to root...And apparently I can root this model, but not the last one?
I have Windows 7. There's seems to be several different methods to root this device. I'm running 8.3.2.9.
Is it best to upgrade to Honeycomb 3.2 before you root, or after? Or should I stay with 3.1 Honeycomb...someone let me know and send me some links/files I need to get to root!
Appreciate it mucho!
Click to expand...
Click to collapse
Actually you're on a firmware that can still be root using
the old method.
Your choice but NVFlash is probably better.
ADB
http://androidroot.mobi/technical/asus-eee-pad-transformer-tf101-root-cwm-recovery/
NVFlash
http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/
TheScPCrew said:
Do I need to update my firmware or update to HC 3.2 before I NVFlash?
Ultimately what I'm wanting is a rooted Honeycomb 3.2 tablet...
Click to expand...
Click to collapse
No you don't need to upgrade. NVFlash work for all firmware.

TF101 Honeycomb updates

Does anyone know where I might be able to find the latest of the Honeycomb updates? I've got the 8.6.5.13 NVFlash, but I've been searching and haven't been able to find any of the 'Official' updates. It doesn't help that searching XDA for '8.6.5.19' actually searches for '8 6 5 19'. I believe the latest is either 8.6.6.21 or 8.6.5.21? If someone could point me in the direction of the latest (or two latest) oficcial Asus Honeycomb updates, I'd appreciate it.
Hi Subnetmask (255.255.255.0)
Why dont you just use ota from asus? are is your TF rooted and CWM installed?
Otherwise use gnufabio's recovery installer app to install cwm so you can upgrade.
or use nvflash to install ICS????
It looks like he wants to downgrade, or only upgrade to the latest HC and avoid ICS. I'd link you to the download from asus on their site, but of course it's down -_-
When the site is back up it should be on there. If not search for 8.6.6.21 stock rooted tf101 or along those lines.
Thing O Doom said:
It looks like he wants to downgrade, or only upgrade to the latest HC and avoid ICS. I'd link you to the download from asus on their site, but of course it's down -_-
When the site is back up it should be on there. If not search for 8.6.6.21 stock rooted tf101 or along those lines.
Click to expand...
Click to collapse
That's exactly it. I downgraded to 8.6.5.13, but don't want to upgrade it to ICS again just yet... SInce I downgraded it to 8.6.5.13 it hasn't shut down on its own again yet (Big surprise...).
I looked on Asus' web site, and unless there's another section I couldn't find, the only non-ICS download is 8.6.5.13 for the 'CN' SKU. I've searched around Google and unless I"m missing something (always possible) nothing useful has come up yet. Searching here is kinda useless because '8.6.5.13' gets searched as '8 6 5 13' so pretty much any thread with an 8, a 6, a 5 or a 13 gets displayed :/.
I have a copy of Stock 8.6.5.21 (latest HC). I can post it up once I get to my PC.
Probably be a couple of hours.
baseballfanz said:
I have a copy of Stock 8.6.5.21 (latest HC). I can post it up once I get to my PC.
Probably be a couple of hours.
Click to expand...
Click to collapse
That would be awesone. No rush, whenever you have a chance .
Here you go,
http://www.4shared.com/zip/ht-SmZQE/UpdateLauncher_US_epaduser8_6_.html
Awesome. Thanks!
Anyone have 8.6.5.19? I don't know why I'm having so much trouble, but I can't get my TF101 to re-root for the life of me. I've tried on the bare 8.6.5.13 & with 8.6.5.21, with ViperMod, NachoRoot and Razorclaw. .13 is too old and .21 is too new for Razorclaw, Nachroot by it's self didn't seem to work right, and Vipermod, using option 3 didn't seem to work either. The problem with ViperMod was when it came back saying UID should be '0', it was always '2000'. If I cna get .19, I should be able to use Razorclaw, then rootkeeper, and update to .21. Then I just need to make the Asus update prompts go away...
SubnetMask said:
Anyone have 8.6.5.19? I don't know why I'm having so much trouble, but I can't get my TF101 to re-root for the life of me. I've tried on the bare 8.6.5.13 & with 8.6.5.21, with ViperMod, NachoRoot and Razorclaw. .13 is too old and .21 is too new for Razorclaw, Nachroot by it's self didn't seem to work right, and Vipermod, using option 3 didn't seem to work either. The problem with ViperMod was when it came back saying UID should be '0', it was always '2000'. If I cna get .19, I should be able to use Razorclaw, then rootkeeper, and update to .21. Then I just need to make the Asus update prompts go away...
Click to expand...
Click to collapse
I have not seen any 8.6.5.19 (Asus pulled it pretty quick after RazorClaw)
There's a 8.6.6.19 you can use (It's for the TF101G but work on the TF101)
http://forum.xda-developers.com/showthread.php?t=1417006&
baseballfanz said:
I have not seen any 8.6.5.19 (Asus pulled it pretty quick after RazorClaw)
There's a 8.6.6.19 you can use (It's for the TF101G but work on the TF101)
http://forum.xda-developers.com/showthread.php?t=1417006&
Click to expand...
Click to collapse
I saw that thread. The file appears to be for 'WW' SKUs, and MultiUpload appears to not be working. The other problem is if I could DL it, I doube I'd be able to apply 8.6.5.21 once rooted.
Don't know why I'm having so much trouble rooting the thing... I've done it after every release since I got it. I must've just gone stoopid lol. Searching for root give ICS information overload.
SubnetMask said:
I saw that thread. The file appears to be for 'WW' SKUs, and MultiUpload appears to not be working. The other problem is if I could DL it, I doube I'd be able to apply 8.6.5.21 once rooted.
Don't know why I'm having so much trouble rooting the thing... I've done it after every release since I got it. I must've just gone stoopid lol. Searching for root give ICS information overload.
Click to expand...
Click to collapse
This link still work.
http://forum.xda-developers.com/showpost.php?p=21729271&postcount=250
It doesn't matter if it's WW or not. your goal is to get root and after which you can flash the correct version for your region.
If it work and you get root, use OTA Root Keeper to save your root, upgrade to 8.6.5.21 and restore root. Worth a try
Finally got it rooted... After about an hour of searching, I found the method that I had originally used (the 'One Click' root found here). I installed OTA Root keeper, but that didn't work on my upgrade to .21 from .9. I ended up having to re-root, but since the 'One-Click' worked, it wasn't too painful. Using linix to root it is so obscure (to me) I totally forgot about it.
Still, if someone happens to have the 8.6.5.19 update file (Call me wierd, but I'd rather have/use the proper file for my unit rather than the one for the TF101g even though it may work fine), it would be great to get that to add to my 'collection'.

[Q] Root/update question

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

So you are all experts, what about newbies?(Root, Unlock, OTA etc..)

Dear friends,
as i have been hanging out in this forum, i have learnt a lot. But still, i cannot understand the attitude why people treat, reply or explain everything in a way that assumes all of us are android experts.
TF700 is my first android device(have been using Apple before) so I really need to improve-or create- fundamental knowledge. Just for your information, replying messages like; "ok now Unlock the Root system instead OTA .21 and blablablabla?" (btw. i am well aware of the fact that this sentence is totally meaningless)
Whatever, my point is it would be wonderful to have a fundamental knowledge thread, also keeping your great posts too at the same time.
Cheers!!
archonur said:
Dear friends,
as i have been hanging out in this forum, i have learnt a lot. But still, i cannot understand the attitude why people treat, reply or explain everything in a way that assumes all of us are android experts.
TF700 is my first android device(have been using Apple before) so I really need to improve-or create- fundamental knowledge. Just for your information, replying messages like; "ok now Unlock the Root system instead OTA .21 and blablablabla?" (btw. i am well aware of the fact that this sentence is totally meaningless)
Whatever, my point is it would be wonderful to have a fundamental knowledge thread, also keeping your great posts too at the same time.
Cheers!!
Click to expand...
Click to collapse
I am a newbie too -- bought the tf101 a couple of months ago - loved it -- told my husband he could have it - I was buying the 700 ! and was lucky enough to be able to order one (we live in Canada..... Tiger Direct.ca had them)
I have learned a lot from this forum -- glad I found it --- but I won't be "unlocking" anything ! the only thing I know how to "root" are my house plants !!! lol !! we don't even own smart phones yet -- we still have dumb phones !!! but I have my TF700 !!!
You mean sth like this?
seems hard, but it's not.
It seems tough in the beginning for noob, but actually you're going to get it. You should read the "Index" pointing out by d14b0ll0s to gain some basic knowledge and familiar with the terminology then you should be fine. Couple key words I want to point out that you should know. Currently TF700 came with a locked boot loader, meaning you not able to flash (install) custom firmware from our developers. This is a biggest issue at the moment. Sure there're workaround but it's a pain in the as...and unstable(could brick your pad if you not doing it right). When you see numbers like 21,22,26, they are firmware version number. The latest should be 26. OTA stands for "over the air" and we referred to firmware push to our pad by Asus, not manually download and install ourselves. Rooted is a process that you gain access as a administrator on your pad (you have full access to your phone), with rooted privilege you can almost do anything with your pad, like uninstall Asus embed software, do a full backup of your entire OS (operating system), modified system files etc... CWM is a tool you installed on your pad in order to flash (install) custom firmware. So at the minimum you should have root, and in the future when new custom firmware arrived, you can install cwm and used this tool to flash them. Keep in mind that with locked boot loader, you can't flash custom firmware. Finally, once you're rooted or have custom firmware installed, your pad will no longer can accepted OTA firmware (firmware push to your pad by Asus). In this case you need to roll back to stock (re installed factory firmware and no root), before you can do OTA update. Currently, I suggest you should stay on the side line and waiting for the OTA 4.1.1 JB (new Operating System called Jelly Bean, version 4.1.1 will be push to your pad by Asus). After reading this post you should be ready to play... good luck!
Sorry, but I don't get it, what is it about Verizon? Is it because you bought yours from Verizon? Mine comes from ASUS and I believe the OTA updates are from ASUS servers. Is it the US-specific thing that you mentioned?
Yeah... Everything is pretty easy even for people that have no clue what they are doing. My suggestion right now is to root but not unlock. Rooting is as simple as running the .bat file and following on screen directions (assuming you are using Windows). The only thing you need to do after the program is finished is to open up the Superuser app (might be SuperSU) and restart after that for safe measure.
Unlocking does VOID YOUR MANUFACTURERS WARRANTY (and possibly all others you may have purchased). Make sure you know what you want to do with an unlocked device before you do it. Personally, I am waiting for a stable JB build before I unlock. But the choice is ultimately up to you.
d14b0ll0s said:
Sorry, but I don't get it, what is it about Verizon? Is it because you bought yours from Verizon? Mine comes from ASUS and I believe the OTA updates are from ASUS servers. Is it the US-specific thing that you mentioned?
Click to expand...
Click to collapse
Sorry you're right, must not awake yet. ASUS that is. Thanks bro.
Your going to be fine try learning how to build aosp from source in a time limit
Sent from my Galaxy Nexus using xda premium
Skullmonkey said:
Yeah... Everything is pretty easy even for people that have no clue what they are doing. My suggestion right now is to root but not unlock. Rooting is as simple as running the .bat file and following on screen directions (assuming you are using Windows). The only thing you need to do after the program is finished is to open up the Superuser app (might be SuperSU) and restart after that for safe measure.
Unlocking does VOID YOUR MANUFACTURERS WARRANTY (and possibly all others you may have purchased). Make sure you know what you want to do with an unlocked device before you do it. Personally, I am waiting for a stable JB build before I unlock. But the choice is ultimately up to you.
Click to expand...
Click to collapse
I agree with Skullmonkey on this. Until you are ready for really hacking the system, all you really need is to root the system (run the DebugFS) to get "administrator access to your device".
You might want to read what buhohitr wrote several times as there is much to be gleaned from it. If it helps, copy/paste the contents of buhohitr's repsonse to a notepad text document and go through it word-for-word, isolate those that you find questionable or troublesome, then research what those words are. Anything that is "super difficult" you can just post back here in the Q&A section and I'm sure someone will help you in no time.
another noob question: does rooting the device void manufacturing warranty?
It does not. Only unlocking the device does.
Sent from my Transformer Infinity!
So if I root my Infinity...
...which pre-included apps can I get rid of?
Also which preloaded apps are best to bump off if I dare a root?
I have never dabbled with android down in the file system much for fear of doing something irreparable.
Well, to the OP: we already have quite a few 'basic' threads going on here, and no one forces you to embark on the more advanced stuff, do we? Just read up on it, and when you feel like you can make the jump, pick it up little by little. We're not all experts in here, but most of us can follow directions of the gurus really good, and we have the advantage of knowing how to save our butts when the excrement impacts the ventilator. (And most of us learnt it the hard way, by bricking and breaking...)
You should be fine in the regular forums, and as the others have said, stay out of the development sections until you feel secure enough to dabble around with unlocking and so on.
Sent from my ASUS Transformer Pad TF700T
buhohitr said:
Currently, I suggest you should stay on the side line and waiting for the OTA 4.1.1 JB (new Operating System called Jelly Bean, version 4.1.1 will be push to your pad by Asus). After reading this post you should be ready to play... good luck!
Click to expand...
Click to collapse
What's the method for unrooting/reflashing to stock at the moment? I rooted because I wanted to use Titanium Backup right after I got back up to .26. If we haven't figured out how to custom flash roms by the time jellybean comes out, I'll need to go back to stock. I would *hate* to have to lose all my apps, and its possible that titanium backup from 4.0.3 to 4.1.1 might royally screw up the system in doing a restore. So, if that's the case, I guess I'll reflash someway and lose everything? Doh.
spinaldex said:
What's the method for unrooting/reflashing to stock at the moment? I rooted because I wanted to use Titanium Backup right after I got back up to .26. If we haven't figured out how to custom flash roms by the time jellybean comes out, I'll need to go back to stock. I would *hate* to have to lose all my apps, and its possible that titanium backup from 4.0.3 to 4.1.1 might royally screw up the system in doing a restore. So, if that's the case, I guess I'll reflash someway and lose everything? Doh.
Click to expand...
Click to collapse
Anyone figure out a way to go back from root back to stock yet so that when Jelly Bean comes out we can upgrade?
spinaldex said:
Anyone figure out a way to go back from root back to stock yet so that when Jelly Bean comes out we can upgrade?
Click to expand...
Click to collapse
One method to get rid of root would be factory reset (power on while holding both the power and volume down while booting and running a factory reset.) But you could probably temporarily unroot with voodoo ota root keeper and then reroot once you install the upgrade to jelly bean with its root keeper.
Sent from my DROIDX using xda app-developers app
ekalb10 said:
One method to get rid of root would be factory reset (power on while holding both the power and volume down while booting and running a factory reset.) But you could probably temporarily unroot with voodoo ota root keeper and then reroot once you install the upgrade to jelly bean with its root keeper.
Click to expand...
Click to collapse
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
d14b0ll0s said:
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
Click to expand...
Click to collapse
I guess I was just misinformed on the factory reset, sorry if I confused anyone.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
d14b0ll0s said:
That's not true. Funny I've been responding to the same kind of "advice" a few minutes ago in another thread.
Temporarily unrooting through Root Keeper should work, but rooting has prevented updating firmware only for some users. I was rooted and installed updates both manually and through OTA without experiencing any issues. Getting to stock /system partition basically means restoring stock configuration files (like build.prop etc.), removing /system/xbin/su and any copies made by RootKeeper, as well as things that install to /system like BusyBox.
Even if you're rooted you should be able to update firmware manually through stock recovery (power down, power up, hold power and volume down, release, press volume up, etc., with microSD formatted FAT32 and with EP201_768_SDUPDATE on it, it's already in the how-to threads in the general section).
Click to expand...
Click to collapse
+ 1 I have rooted several tablets/phone over the last two years and backed it up using voodoo rootkeeper with ZERO issues updating firmware/OTAS. The only thing that happens after updating is that I loose root, but that's where voodoo OTA rootkeeper comes to play. Only a handful of people have had problems. Some are legit while others have messed/modded their device prior to updates. (like removeing system apps or modding build. Props)
"60% of the time, it works everytime. "
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Unroot it again ??
If there are problems with the tablet and it must be repaired on warranty, then I need to unroot it again.
How do I unroot it again ??
Regards Peder

[Q] JB Stock Needs Help

Ok, I got a TF300t for christmas. I couldn't wait, powered it up, and before I even hit the forums I went ahead and applied the JB update. :crying: I know... So here I am, running stock. I'm at the most recent update as of a few days ago. I've been up and down the forum trying to figure out the root situation, and there's all sorts of instructions for different .17, .26, .29, etc. roms. 1st, which number are you looking at for that? My first guess was build number so I guess that puts me at JRO03C.US_epad-10.4.2.20-20121228 (which following the above I'm guessing would get shortened now to 2.20?)
1st Q Is the only way to currently root/TWRP this bad boy to DL the ASUS unlock apk and run it? From what I can see a LOT of people are having issues with it, and it doesn't even unlock NVFlash?! I'm used to Tegra based devices. I had a ViewSonic gTab before this. I've flashed and NVFlashed the hell out of that device so flashing itself doesn't make me uncomfortable, but the thing with that tab was as long as I could get APX, my ass was fine. I'm not so sure about the TF300t If the APK is the only way... sad panda.
2.) The APK voids the warranty right? Not a fan of that idea...what if I have a legit HW issue not caused by flashing? I'm screwed....damn. Is ANYONE working on a way to modify the bootloader without notifying ASUS? Hell, I'll even take some janky way of rerouting my IP traffic and sending back a false positive to unlock my tab.
I can't really think of a 3 right now. I had one earlier...I forgot. Normally I wouldn't post this since I know it's probably topics that have been covered, but there's SO MUCH info on this tablet and it seems to change with each release that ASUS puts out that I'm not sure which methods I can use and what exactly they will do. The gTab may have been stuck in Froyo, but the guys on TeamDRH are awesome and it was SOOOO easy to flash that thing 7 ways from Sunday. I'm really mad at ASUS's implementation....had I known that they screwed over the abilities to flash the tegra platform I'd have looked into a Sammy to at least match up better with my S3.
Any help or advice is appreciated. I'd really like to find a way to root/TWRP w/o voiding warranty. If it can't be done now does anyone at least know if it's being worked on by anyone?
NeoMatrixJR said:
Ok, I got a TF300t for christmas. I couldn't wait, powered it up, and before I even hit the forums I went ahead and applied the JB update. :crying: I know... So here I am, running stock. I'm at the most recent update as of a few days ago. I've been up and down the forum trying to figure out the root situation, and there's all sorts of instructions for different .17, .26, .29, etc. roms. 1st, which number are you looking at for that? My first guess was build number so I guess that puts me at JRO03C.US_epad-10.4.2.20-20121228 (which following the above I'm guessing would get shortened now to 2.20?)
1st Q Is the only way to currently root/TWRP this bad boy to DL the ASUS unlock apk and run it? From what I can see a LOT of people are having issues with it, and it doesn't even unlock NVFlash?! I'm used to Tegra based devices. I had a ViewSonic gTab before this. I've flashed and NVFlashed the hell out of that device so flashing itself doesn't make me uncomfortable, but the thing with that tab was as long as I could get APX, my ass was fine. I'm not so sure about the TF300t If the APK is the only way... sad panda.
Click to expand...
Click to collapse
For unlock your tablet, the only way is to use the UNLOCK TOOL V7
After, once your tablet unlocked without problem
You can just followed this guide : [ROOT/ROM] Root Stock/Deodex Firmware 10.4.2.20 (US/WW) | Insecure kernel !.
It's exactly for you.
2.) The APK voids the warranty right? Not a fan of that idea...what if I have a legit HW issue not caused by flashing? I'm screwed....damn. Is ANYONE working on a way to modify the bootloader without notifying ASUS? Hell, I'll even take some janky way of rerouting my IP traffic and sending back a false positive to unlock my tab.
Click to expand...
Click to collapse
No way by this side...If you use the Unlock tool, you loose your warranty, it's one fact
I can't really think of a 3 right now. I had one earlier...I forgot. Normally I wouldn't post this since I know it's probably topics that have been covered, but there's SO MUCH info on this tablet and it seems to change with each release that ASUS puts out that I'm not sure which methods I can use and what exactly they will do. The gTab may have been stuck in Froyo, but the guys on TeamDRH are awesome and it was SOOOO easy to flash that thing 7 ways from Sunday. I'm really mad at ASUS's implementation....had I known that they screwed over the abilities to flash the tegra platform I'd have looked into a Sammy to at least match up better with my S3.
Any help or advice is appreciated. I'd really like to find a way to root/TWRP w/o voiding warranty. If it can't be done now does anyone at least know if it's being worked on by anyone?
Click to expand...
Click to collapse
And actually and for my part the most functional as recovery is TWRP, but if you want to use CWM, no problem for use it too

Categories

Resources