I managed to break the Wifi on my tablet. I had root, accidentally replaced a file I shouldn't have, thought that wiping and flashing the .21 update would work...it didn't. It wouldn't flash because a system file had been modified.
Because I broke the wifi, I can't unlock. I basically am stuck waiting for .21 to be rooted.
Devs, are we close to root? I'm sure you're working on it and I applaud your efforts. Is this firmware super closed off? I'm not asking for an ETA, but maybe more of a status update. Just let me know there is hope
EDIT: I fixed it! I was able to pull an .apk of OTA Voodoo Rootkeep from a previous Titanium Backup file. I installed the app, and it restored root for me! Its possible that I was already still rooted, but without the ability to d/l apps I couldn't do anything about it. Anyway, I'm back with a rooted .21!
I think I had a similar issue....was using wifi tethered to phone...with modded wpa files....Couldn't OTA for .21......no computer/no router to get a wifi connection.
Went to Mickey D's for a free wifi connection....downloaded and installed .15 (for orig files) via SD card.
After that was finished, used OTA to download .21 ...if there are still issues, download it and manually install it via SD card.
Here's instructions to do it via SD card:
http://service.asus.com/TF201_fwupdate
Yeah I had to do that method when I first updated to .21. But then, after .21 I couldn't tether even though the chanelog said ad hoc wifi was supported. So I tried that method again, and broke it. Now I have no root and no wifi.
Waiting for someone to find root for .21 is killing me. lol
Any Devs want to chime in and give us an update on the .21 root process?
http://transformerprimeroot.com/tra...orkmod-recovery-5-8-2-0-on-transformer-prime/
use this. windows didnt work for me, drivers were messed up.
i used the mac method with no drivers required. (same with linux) and it worked flawlessly. pushed CWM using this, then flashed primeval .21 firmware.
stock .21 but with root.
requires unlock
Thanks, but I can't even unlock due to no data connection
I wonder if I could do it with an USB Ethernet dongle?
We definately need some tool to recover from such positions... NVflash or anything. This way its just too risky to temper with files if you're not unlocked imho. I remember about 3-4 cases where people got issues because of trying to improve stuff by editing files like build.prop etc.
Gogo devs, Asus, nVidia... Anyone, give us some tools to be safe
Definitely. I purchased a square trade warranty so that when I unlock I am still covered. However, why should I have to?
I sincerely hope a dev can get us root one .21 at least, and maybe some kind of unlock tool that doesn't report to Asus. And of course, NVFlash
the unlock is just an APK from asus? cant download that and put on SD?
malaeus said:
the unlock is just an APK from asus? cant download that and put on SD?
Click to expand...
Click to collapse
Its simple enough to install, but the app requires a connection with Asus' servers to record the Prime's serial number and then distribute a unique unlock key.
McLiarpants said:
Its simple enough to install, but the app requires a connection with Asus' servers to record the Prime's serial number and then distribute a unique unlock key.
Click to expand...
Click to collapse
Ah was not aware of such communication. Sorry :-(
Have you tried going online with a usb ethernet dongle?
I was going to look into this option, but I was able to fix my wifi!
I pulled Titanium Backup .apk files of my old apps and installed voodoo rootkeeper. it restored root (its possible I never actually lost root, just the ability to d/l apps like root explorer because of broken wifi)! I then loaded my backup of root explorer and copied the correct wpa_supplicant file.
I then immediately unlocked and flashed Virtuous Prime .21. I purchased a square trade warranty with accidental damage protection in case I have any problems with it.
It would be nice to know if I could do that for my unrooted Prime I accidentally upgraded to .21 before rooting. My other Prime is on .21 with root.
I'm sure it is because you had root before, but maybe it's worth a try.
McLiarpants said:
I purchased a square trade warranty with accidental damage protection in case I have any problems with it.
Click to expand...
Click to collapse
Has anyone confirmed that squaretrade considers unlocking and intentionally voiding your warranty "normal use"? I too am getting disheartened waitig for .21 root method. I would love to install custom rom and never have to worry about it again if squaretrade will cover a bricked device. However, I'm afraid if I void my warranty ASUS might decide not to honor the device with warranty issues such as gps dongles, etc.
casey225 said:
Has anyone confirmed that squaretrade considers unlocking and intentionally voiding your warranty "normal use"? I too am getting disheartened waitig for .21 root method. I would love to install custom rom and never have to worry about it again if squaretrade will cover a bricked device. However, I'm afraid if I void my warranty ASUS might decide not to honor the device with warranty issues such as gps dongles, etc.
Click to expand...
Click to collapse
What I've heard from other people is that the warranty says that they don't support intentional hardware or software modifications that would also void the manufacturer's warranty. Such as unlocking or opening the unit. However, if you have the accidental warranty and you drop it after being unlocked, they will fix it or replace it.
So if you have a problem with it after unlocking, it may need an "accident" to happen before you send it into ST.
clouds5 said:
We definately need some tool to recover from such positions... NVflash or anything. This way its just too risky to temper with files if you're not unlocked imho. I remember about 3-4 cases where people got issues because of trying to improve stuff by editing files like build.prop etc.
Gogo devs, Asus, nVidia... Anyone, give us some tools to be safe
Click to expand...
Click to collapse
there is a method to recover from this, grab the full update not the patch one from asus website, put it on a microsd card, and boot recovery
McLiarpants said:
So if you have a problem with it after unlocking, it may need an "accident" to happen before you send it into ST.
Click to expand...
Click to collapse
Understood I would still have to hope that Squaretrade doesn't determine the true problem, otherwise, would be SOL on all fronts. I will try to wait it out for now, but, I think I hear Virtuous Prime calling my name as I type this message.
casey225 said:
Understood I would still have to hope that Squaretrade doesn't determine the true problem, otherwise, would be SOL on all fronts. I will try to wait it out for now, but, I think I hear Virtuous Prime calling my name as I type this message.
Click to expand...
Click to collapse
I am running VP now, but I really like AOKP. The only reason I'm running VP is because Polaris isn't working on AOKP. I know it has some bugs, but I can't work with the lag between hitting a key and the letter showing on the screen in other office apps. I also haven't been willing to pay $15-$30 for an app to see how laggy it is.
lilstevie said:
there is a method to recover from this, grab the full update not the patch one from asus website, put it on a microsd card, and boot recovery
Click to expand...
Click to collapse
The update wont install if any of the system files are modified. It would be nice if it did, but it doesn't, unfortunately.
TB Pro restore with rooted .21 (NOT UNLOCKED)
So I had a thought and I am not sure that this will work. I have a TF101 that was rooted on 9.4.2.17 then upgraded to 9.4.2.21 (without any rootkeeper installed). Still have root but decided to install Voodoo RootKeeper just in case.
I have TB Pro installed and the Dev claims that you can restore to dissimilar hardware. My thought is to restore the APP+DATA+SYSTEM backup to my TF201 that is currently running 9.4.2.21 without root.
Any thoughts on this idea?
Niles
Related
Received a Prime today, brand new. Powered on to 3.2, and almost immediately got the DMClient crash, while still going through the Android Wizard. Continually got it, tried force stopping, clearing cache and data on it, rebooting, etc. Wiped all data both via the bootloader and via settings, immediately came back. Was unable to get an update OTA - crashed immediately.
I downloaded .14 ICS update from ASUS, put it on the internal storage, and it immediately noticed it and offered to upgrade. Did the upgrade, wiped data. Again, during the step where you enter your Google credentials, started getting the DMClient crash. It clearly isn't the result of anything I've installed (since it was happening after a wipe before I was able to install anything!) I know .15 is out there, but updating via the menu is not an option. (Crash, crash, crash, crash.) I haven't seen any other complaints of it happening on a fresh clean install, where it seemed to be impossible to make it stop.
I guess I'm going to root and install .15 either from the dev section, or Virtuous Prime. But has *anyone* else had this happen? I don't understand how it can crash fresh stock install, unless there's some sort of hardware issue causing it. Not that it would be related anyway, but I do have a serial number.
Any help???
skunkiechris said:
Received a Prime today, brand new. Powered on to 3.2, and almost immediately got the DMClient crash, while still going through the Android Wizard. Continually got it, tried force stopping, clearing cache and data on it, rebooting, etc. Wiped all data both via the bootloader and via settings, immediately came back. Was unable to get an update OTA - crashed immediately.
I downloaded .14 ICS update from ASUS, put it on the internal storage, and it immediately noticed it and offered to upgrade. Did the upgrade, wiped data. Again, during the step where you enter your Google credentials, started getting the DMClient crash. It clearly isn't the result of anything I've installed (since it was happening after a wipe before I was able to install anything!) I know .15 is out there, but updating via the menu is not an option. (Crash, crash, crash, crash.) I haven't seen any other complaints of it happening on a fresh clean install, where it seemed to be impossible to make it stop.
I guess I'm going to root and install .15 either from the dev section, or Virtuous Prime. But has *anyone* else had this happen? I don't understand how it can crash fresh stock install, unless there's some sort of hardware issue causing it. Not that it would be related anyway, but I do have a serial number.
Any help???
Click to expand...
Click to collapse
What SKU are you? WW, DE, US, UK?
That really is no good. And it's odd that wipes/manual installs aren't cutting into it, usually the rewrites will help iron things like this out.
Like you said, rooting and trying other (older) updates and such would at least show us if it's consistent regardless of what you do.
Must be s/w issue though, so I'm stumped why you haven't absolved it yet
*EDIT:
And please realize that rooting and unlocking are not the same! You can root and install other updates and still keep your warranty. If you successfully unlock so that you can install Virtuous, you will not have a warranty.
US SKU, sorry about leaving that out. Is there any way a hardware issue could wreak havoc with DMClient? This is really perplexing.
Now that I think about it, though, I'm a bit reluctant to unlock the tablet and cause warranty issues while this is still happening...
EDIT: Hahaha - I realized as I was replying to you that didn't make any sense, and I shouldn't have said unlock!
buxtahuda said:
What SKU are you? WW, DE, US, UK?
That really is no good. And it's odd that wipes/manual installs aren't cutting into it, usually the rewrites will help iron things like this out.
Like you said, rooting and trying other (older) updates and such would at least show us if it's consistent regardless of what you do.
Must be s/w issue though, so I'm stumped why you haven't absolved it yet
*EDIT:
And please realize that rooting and unlocking are not the same! You can root and install other updates and still keep your warranty. If you successfully unlock so that you can install Virtuous, you will not have a warranty.
Click to expand...
Click to collapse
well technically rooting can void warranty also as it states it in there. tampering with root files or software. BUT at least we can unroot. plus hopefully Asus not to much by the books when device is rooted n sent in for warranty work. if anything, I'd remove root from device to be on the safe side n take no chances of them denying me warranty claim for something as simple as that.
but like you said though, if you unlock, kiss your warranty good bye..lmfao
demandarin said:
well technically rooting can void warranty also as it states it in there. tampering with root files or software. BUT at least we can unroot. plus hopefully Asus not to much by the books when device is rooted n sent in for warranty work. if anything, I'd remove root from device to be on the safe side n take no chances of them denying me warranty claim for something as simple as that.
but like you said though, if you unlock, kiss your warranty good bye..lmfao
Click to expand...
Click to collapse
Yeah, I'm not going to unlock until I know what's going on. I figured rooting isn't a big deal since it can always be unrooted. But I'd need to be unlocked to install another ROM, so I guess I don't see where this gets me very far. ACK! Frustrating!
skunkiechris said:
Yeah, I'm not going to unlock until I know what's going on. I figured rooting isn't a big deal since it can always be unrooted. But I'd need to be unlocked to install another ROM, so I guess I don't see where this gets me very far. ACK! Frustrating!
Click to expand...
Click to collapse
Just root. Follow my sig to PrimeTime (Root/Unroot).
Then we (that is, XDA'ers more knowledgeable than I) can get into your system files to see what's going on. You could even just try fixing its permissions and such.
If none of that works, manually blob to another update (also in my sig) and continue testing.
All of this will leave warranty intact so long as you unroot and rewrite any changed system files (probably with a reset/install).
buxtahuda said:
Just root. Follow my sig to PrimeTime (Root/Unroot).
Then we (that is, XDA'ers more knowledgeable than I) can get into your system files to see what's going on. You could even just try fixing its permissions and such.
If none of that works, manually blob to another update (also in my sig) and continue testing.
All of this will leave warranty intact so long as you unroot and rewrite any changed system files (probably with a reset/install).
Click to expand...
Click to collapse
I did root successfully after my first post. Here's what they look like currently:
-rw-r--r-- root root 167247 2012-02-14 08:51 DMClient.apk
-rw-r--r-- root root 668904 2012-02-14 08:51 DMClient.odex
That seems on par with everything else...
Does DMClient do anything other than manage OTA updates? Maybe the solution is just to remove it entirely. I have no problem manually downloading and installing updates, as long as there are no other issues!
skunkiechris said:
Does DMClient do anything other than manage OTA updates? Maybe the solution is just to remove it entirely. I have no problem manually downloading and installing updates, as long as there are no other issues!
Click to expand...
Click to collapse
This formats the internal SD card which makes this route a nuisance. It also requires hooking back up to a PC to re-root.
Again, I've no idea what to look for or what would cause this especially after wiping/resetting (I still wouldn't know otherwise lol ), but hopefully someone will come along who might know or ASUS will answer a support ticket.
i read this:
Once you unlocked the prime and installed CWM, do NOT try to install a super blob from ASUS
BUT Can i do update (OTA) with new software from asus with unlocked bootloader?Does that bricks asus?
djshorty said:
i read this:
Once you unlocked the prime and installed CWM, do NOT try to install a super blob from ASUS
BUT Can i do update (OTA) with new software from asus with unlocked bootloader?Does that bricks asus?
Click to expand...
Click to collapse
NOOOOOOOOOO! Don't install an OTA or try to manually update with a blob - you will DEFINITELY hard brick your Prime. If you want to keep the OTAs don't unlock. Having said that the devs are all very quick at updating their roms when a new OTA comes out. I currently am on Virtuous Prime and it was updated to .21 within 24 hours of Asus releasing it. Same deal with .15.
paddycr said:
NOOOOOOOOOO! Don't install an OTA or try to manually update with a blob - you will DEFINITELY hard brick your Prime. If you want to keep the OTAs don't unlock. Having said that the devs are all very quick at updating their roms when a new OTA comes out. I currently am on Virtuous Prime and it was updated to .21 within 24 hours of Asus releasing it. Same deal with .15.
Click to expand...
Click to collapse
I am only rooted now, not unlocked.
I know that with root i can do OTA, i want to know this.
Thanks for quick answer.
just backup before modifying/deleting/uninstalling anything else, and restore before running update process, or OTA will fail.
Sent from my TF201
How did we establish that the blob method will brick your prime after unlocking? I ask because I have done it multiple times with no adverse effects so far. And from a Linux stand point....it makes no sense why there would be any risk.....
scook9 said:
How did we establish that the blob method will brick your prime after unlocking? I ask because I have done it multiple times with no adverse effects so far. And from a Linux stand point....it makes no sense why there would be any risk.....
Click to expand...
Click to collapse
This is purely a guess but I think people believe that installing a stock blob will tamper with the bootloader or cause the bootloader to "check" for custom firmware.
scook9 said:
How did we establish that the blob method will brick your prime after unlocking? I ask because I have done it multiple times with no adverse effects so far. And from a Linux stand point....it makes no sense why there would be any risk.....
Click to expand...
Click to collapse
Unfortunately, this has been found out the hard way. This forum is littered with examples who have tried to install an Asus update and have hard bricked their TFP. My understanding (which might be wrong ) is that the unlock program installs an token on the bootloader. The token is wiped when the Asus update is applied, which screws the bootloader if you have CWM installed. See post #193 onwards for a discussion by people who actually know what they are talking about:
http://forum.xda-developers.com/showthread.php?t=1514088&page=20
That really did not offer much after reading through it - I actually got hung up and had to reference that thread couple days ago and it saved me
Once you have a custom recovery (CWM) do not try the SD Card update method that Asus outlines on their website. Just a heads up. You will continually boot into CWM and be stuck there. I had to dd zeros into the staging partition before I could boot properly.
Now as for the talk about the bootloader being touched by the blob method....I call BS....the bootloader is the equivalent of the BIOS on a PC, and the blob is only flashing stuff higher level than that (boot/kernel, and system partitions afaik)
If someone has good information contrary to what I am saying I am all ears and willing to learn but so far I am seeing stuff that is absolutely wrong per my own experiences thus far.
scook9 said:
That really did not offer much after reading through it - I actually got hung up and had to reference that thread couple days ago and it saved me
Once you have a custom recovery (CWM) do not try the SD Card update method that Asus outlines on their website. Just a heads up. You will continually boot into CWM and be stuck there. I had to dd zeros into the staging partition before I could boot properly.
Now as for the talk about the bootloader being touched by the blob method....I call BS....the bootloader is the equivalent of the BIOS on a PC, and the blob is only flashing stuff higher level than that (boot/kernel, and system partitions afaik)
If someone has good information contrary to what I am saying I am all ears and willing to learn but so far I am seeing stuff that is absolutely wrong per my own experiences thus far.
Click to expand...
Click to collapse
So you are telling us that you are unlocked and you have flashed an Asus blob without problems? If so, great news - I suggest you report it on the unbricking thread. If not, why don't you give it a whirl and tell us all how it goes
paddycr said:
So you are telling us that you are unlocked and you have flashed an Asus blob without problems? If so, great news - I suggest you report it on the unbricking thread. If not, why don't you give it a whirl and tell us all how it goes
Click to expand...
Click to collapse
I have. I have flashed a blob over stock recovery and over CWM, survived everything so far.....of course - why Asus made this tablet so retarded in the bootloader department is beyond me, I really love how HTC does it with HBOOT. I have also flashed blob, then CWM, then done stuff, then blobbed and also ok
scook9 said:
I have. I have flashed a blob over stock recovery and over CWM, survived everything so far.....of course - why Asus made this tablet so retarded in the bootloader department is beyond me, I really love how HTC does it with HBOOT. I have also flashed blob, then CWM, then done stuff, then blobbed and also ok
Click to expand...
Click to collapse
Cwm 5.5.x.x or 5.8.x.x?
Both
you might be the first, afaik
Sent from my TF201
help with ota after root
I used sparky's root method and everything seemed fine, until I got the ota update notice. from then on i couldn't download or update any app from the market. figured the update was blocking it so tried the update, but it failed, saying kernel image was damaged,and user reset was required, So i rebooted and did the reset. After the reset I tried the ota update again, no go. also still can't download anything from market. I then tried to do recovery and it failed. Please help!!! I'm on ICS .15
Hello everyone!
About a week ago, I went and bought the S3, my first Android phone. The sales guy told me that the phone is sim free but a Samsung's firmware update caused a bug, and that the phone needed to be sim unlocked because of Samsung's error. Needless to say I knew nothing about the phone (or Android).
After a few days of learning about it, I ended up seeing there is a Voodoo app in the file manager, CWM and SuperSU apps in the app drawer.
I came here to check what that was all about.
After reading extensively I now know that the phone is rooted and was sim unlocked with Voodoo app.
I red all about Voodoo and was impressed that it works with the fix, yet another user said this will cause problems in the future, and I already see some users complaining about their phones not working.
My question is, was the sales person lied to me about the Samsung firmware bug? And also, is the Voodoo app + fix is legit, and I can rest my worries aside?
I wouldn't like to have problems and having to wait for some (wonderful and admirable) dev to fix it, every time there is a firmware update.
Thanks in advance, excuse my noobishness.
If its unlocked.....ITS UNLOCKED
reboot, if its still unlocked then you are good. as far as the problems........i dont know of some sort of samsung bug that would f up a phone.
what are you really asking? will your phone all of sudden brick on you and become useless? i dont think so
In fact, there is no Samsung "bug": Samsung has just improve is Lock system which now break voodoo unlock (on purpose or not...)
In theory, it should only relock phones that had been unlock with voodoo app but here is the tricky thing: some shop sell "fake" unlocked phones!
-they took carrier locked phone
-they flash a stock rom
-they change the EFS file in the same way voodoo app would have done
-they sell it as unlocked
the old lock system do not break this and buyers will probably never see the trick but the new lock system just relock the phone and left people with a locked phone even if they think they have bought an unlocked phone
Just look at this post which is an answer to someone who had a relock on an "unlocked" phone with XXBLG8 firmware
Mopral said:
the old lock system do not break this and buyers will probably never see the trick but the new lock system just relock the phone and left people with a locked phone even if they think they have bought an unlocked phone
Click to expand...
Click to collapse
So in fact, from now on, every time I flash an updated rom, I need to pray that samsung didn't (intentionally or not) break the voodoo unlock? Sort of like the Apple's cat and mouse game after the unlocks? Cause I'm not going through that again.
Here is a patch for preventing the sim to be locked after a update http://forum.xda-developers.com/showthread.php?t=1802951, need root and flash with CWM.
gee2012 said:
Here is a patch for preventing the sim to be locked after a update http://forum.xda-developers.com/showthread.php?t=1802951, need root and flash with CWM.
Click to expand...
Click to collapse
Thank you for the reply.
It seems as though the fix is allready applied, the thing that bother me is that
I will need to wait for a fix every time there is an update.
It's just that i'm afraid after owning a locked iphone, that was a nightmare.
Let's say that it is much better and more comfterbale to have an unlocked phone, am i right?
shermenz said:
Thank you for the reply.
It seems as though the fix is allready applied, the thing that bother me is that
I will need to wait for a fix every time there is an update.
It's just that i'm afraid after owning a locked iphone, that was a nightmare.
Let's say that it is much better and more comfterbale to have an unlocked phone, am i right?
Click to expand...
Click to collapse
Go back to the shop and request a original simlock free phone then. if it bothers you that much!
shermenz said:
Hello everyone!
About a week ago, I went and bought the S3, my first Android phone. The sales guy told me that the phone is sim free but a Samsung's firmware update caused a bug, and that the phone needed to be sim unlocked because of Samsung's error. Needless to say I knew nothing about the phone (or Android).
After a few days of learning about it, I ended up seeing there is a Voodoo app in the file manager, CWM and SuperSU apps in the app drawer.
You have bought a second hand phone . Its been used rooted voids warranty and apps installed return it .
jje
Click to expand...
Click to collapse
gee2012 said:
Go back to the shop and request a original simlock free phone then. if it bothers you that much!
Click to expand...
Click to collapse
Well since I'm new to Android I don't know if it should bother me, with Apple it was horrible, my question essentially is should it bother me?
Does sim locked phones Known to cause problems down the road?
Thank you for spendig the time!
shermenz said:
Well since I'm new to Android I don't know if it should bother me, with Apple it was horrible, my question essentially is should it bother me?
Does sim locked phones Known to cause problems down the road?
Thank you for spendig the time!
Click to expand...
Click to collapse
As you are rooted, it is better not to update through Kies or OTA. Kies updates will break root and thus voodoo sim unlock and OTA`s will not be installed as you have a custom recovery. Download future new roms from www.sammobile.com/firmware and flash it with (Mobile) Odin (Pro). See my signature for the procedure. With Mobile Odin Pro you keep root and with pc Odin you will loose root. If in the future you have to send it in for repair warranty can be denied because you are rooted.
Alright so there are a few users who are locked on Jelly Bean and are wanting to take the dive of unlocking and installing a custom rom. So I figured I'd put together this little guide to hopefully help y'all out.
I am not responsible for any damage you do to your device. Following this is your choice.This will void your Asus warranty and you assume all responsibility from here on out.
As long as you follow all directions in this guide your device will not be bricked. It will be unleashed to this beast of a tablets max power
Before you continue make sure you:
1. Have the drivers for your device installed on your computer
2. Have made the upgrade to Jelly Bean
3. Have the USB cable for your Prime
4. Have nerves of steel and the ability to read all and follow instructions in this guide.
Useful Information for total beginners: Some people using this guide may not even entirely understand what they are undertaking. This is not acceptable so it's time for some education. Android is a Linux based operating system (in it's self, not direly important information but it's nice background knowledge) which means that there are certain permissions to users. Having "root" permission is like being an "Administrator" on Windows systems. All devices come without "root" permissions as the total new users can do irreparable damage to their device. This is different than unlocking your boot loader. Unlocking your boot loader (in the Transformer Prime's case) is the act of saying to Asus "I willingly give up my devices warranty in exchange for the ability to totally control my device so I can flash custom software". Unlocking does not automatically give a device root permissions. This can only be obtained through an exploit or by flashing the proper thing after unlocking. Since I'm not perfect at wording (and it's best to educate yourself as much as possible on the subject) there is more info here:
http://www.androidpolice.com/2010/0...top-5-benefits-of-rooting-your-android-phone/
http://www.droidforums.net/forum/ga...53-explain-unlocking-boot-loader-rooting.html
Step 1 Download the Unlock tool here: http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_Prime_TF201/#download (navigate to Downloads, then select the OS as Android, then scroll to utilities and expand the menu. Find the unlock tool and download that. Don't worry about the "For ICS only" disclaimer. This has been confirmed working on Jelly Bean). Install this app on your Prime and run it. Connect to a network before doing so and follow all on-screen directions.
Step 2. By this point the unlock tool has done it's job and when you boot your Prime now has a nice "Your device is unlocked" message in the upper left corner of the screen. The next step is to flash a custom recovery image (TeamWin Recovery Project(TWRP) in this guides case). This may sound complicated but there are multiple easy ways to do this.
Option 1: Go to the TeamWin website and download the needed files as directed on the page and follow the instructions on the website to flash TWRP. (http://teamw.in/project/twrp2/93)
Option 2 (easy option): This option flashes TWRP running a file from your Windows computer. The file attached at the bottom of this guide needs to be downloaded and unzipped to your desktop. Once this is done you power of your Prime and turn it back on while holding the volume down button. Once the tab vibrates release the power button but continue to hold the volume down button.
Once this has been done you will see 4 icons pop up. One is the USB symbol. Navigate to that by pressing the Volume Down button until the icon is highlighted and press volume up to select it (the menu will say use Volume Up to navigate but this is incorrect). This will put your device into fastboot mode. Connect your Prime to your computer via the USB cable and open the folder you extracted earlier. Run the Windows Batch File. This will automatically flash the TeamWin Recovery image for the Jelly Bean bootloader.
Now that you have unlocked and have a custom recovery installed you can begin the flashing. To get into your recovery all you do is power up while holding volume down and select the RCK icon. This boots the recovery image and you'll be able to flash, back up, and restore roms. All threads will have a guide on how to flash the rom in the thread so I won't go into detail. I do suggest however, using a microSDcard to store downloaded roms for flashing as it is safer than internal storage. If you are looking to back up your apps then there's this amazing app called Titanium Backup on the Android Market. It's very powerful and can backup your apps as well as user data.
HELP! Something went wrong and I need help: As with all processes there can be issues that arise. Some are common and others are individual. Let's address some common problems for all you who are still nervous about this:
1. Everything seemed to go fine but my Prime won't boot into TWRP
SOLUTION: This problem comes up for a few reasons and is pretty common. A lot of time it's simply a bad download or you have the wrong files. Check the files you have and make sure they are the right ones. If so then download them again. Sometimes a download just gets corrupted. If neither of these solutions worked either try another method of installing TWRP outlined on their website or post here and either I or another helpful person will do everything possible to help
2. When I tried to flash a custom ROM it won't boot:
SOLUTION: Usually this is an issue specific to the ROM you are flashing. The basic list of problems to eliminate are:
1.Ensure you have a good download
2.Ensure you have the proper boot loader for the ROM (i.e. JB boot loader for Jelly Bean ROMs
3. Try reflashing the rom. Sometimes something just doesn't work and the only way to fix it is to reflash​
Vocab guide for totally new users:
Rom(s): Basically the operating system of your device.
TWRP: Team Win Recovery Project. Started by developers here at XDA and is a powerful recovery tool.
Brick/bricked device: Developer term for saying your device will no longer work due to software/roms and is basically a very, very expensive brick/paper weight.
FAQ: Q: My device is on Jelly Bean but the unlock tool will not work for me no matter what I do. What's wrong?
A: Asus has some issues as a company and certain people are completely unable to unlock their device no matter what. I suggest contacting Asus with your devices S/N and politely ask for an explanation and see if the issue can be resolved. Many users who have used the Asus RMA have still been unable to unlock afterwards.
Other useful links: http://www.youtube.com/watch?v=-pW05Jf87dg&list=UU7YzoWkkb6woYwCnbWLn3ZA&index=22&feature=plcp
Very comprehensive video guide with a full walkthrough to help all with this process. And of course all users can PM me with questions or ask them here.
SuperSU.zip attached is for those who want to root the stock rom. Any custom rom should already be rooted for you.
Good tutorial ..On your way to becoming a recognized contributer
Sent from my LG-P509 using Tapatalk 2
Unfortunately the unlocking tool doesn't work on my TFP, which currently is fully stock 10.4.2.17 and connected to network through wifi.
Tried rebooting, cold booting, waiting, cursing. Might try smashing it against a wall next.
Strange because I've read about many people confirming the tool working on JB. But no luck for me I guess.
DaLongTjeu said:
Unfortunately the unlocking tool doesn't work on my TFP, which currently is fully stock 10.4.2.17 and connected to network through wifi.
Tried rebooting, cold booting, waiting, cursing. Might try smashing it against a wall next.
Strange because I've read about many people confirming the tool working on JB. But no luck for me I guess.
Click to expand...
Click to collapse
The unlock tool doesn't work for about half the people on this forum. There is a separate thread about the whole unlock tool issue. Its useless. Asus refuses to do anything about it. They suggested RMA for some people to fix the unlock issue but when the tablet was returned, it was still locked. Take a look at the thread.
applesuckz said:
The unlock tool doesn't work for about half the people on this forum. There is a separate thread about the whole unlock tool issue. Its useless. Asus refuses to do anything about it. They suggested RMA for some people to fix the unlock issue but when the tablet was returned, it was still locked. Take a look at the thread.
Click to expand...
Click to collapse
I know. There are several threads concerning the unlock tool. My TFP went RMA 2 times, I was unable to unlock after both RMA's. I had root in ICS, but completely lost it after the JB OTA. I was hoping the recent OTA update would change something about the unlocking problems everyone's having, but for me it didn't change a thing.
The OP would be wise not to state that "Don't worry about the "For ICS only" disclaimer. This has been confirmed working on Jelly Bean". For it has be confirmed working on JB by a few user; many of us are unable to unlock even after the latest OTA.
Nothing works for me: reboot, cold boot, factory reset.
I desperately want to installl a custom rom on my TFP to see if that unleashes it's full potential. Right now I own a HTC One X+, which has the same cpu as the TFP but it's many times faster, smoother and less annoying. I still believe the TFP has the potential to be what it was intended to be, but ASUS software isn't going to do that for us.
DaLongTjeu said:
I know. There are several threads concerning the unlock tool. My TFP went RMA 2 times, I was unable to unlock after both RMA's. I had root in ICS, but completely lost it after the JB OTA. I was hoping the recent OTA update would change something about the unlocking problems everyone's having, but for me it didn't change a thing.
The OP would be wise not to state that "Don't worry about the "For ICS only" disclaimer. This has been confirmed working on Jelly Bean". For it has be confirmed working on JB by a few user; many of us are unable to unlock even after the latest OTA.
Nothing works for me: reboot, cold boot, factory reset.
I desperately want to installl a custom rom on my TFP to see if that unleashes it's full potential. Right now I own a HTC One X+, which has the same cpu as the TFP but it's many times faster, smoother and less annoying. I still believe the TFP has the potential to be what it was intended to be, but ASUS software isn't going to do that for us.
Click to expand...
Click to collapse
The issue is not Jelly Bean. The issue is sometimes the servers Asus uses to cross check your serial numbers loses some peoples S/N's. Without a registered S/N the unlock tool will not work. This is the fault of Asus and has been discussed many times. Developers have even decompiled the unlock tool and tried to reverse engineer it to solve this issue to no avail. Please, feel free to do some research if you doubt my answers. Many have spent hours doing so to only find out what they've been told.
McJesus15 said:
The issue is not Jelly Bean. The issue is sometimes the servers Asus uses to cross check your serial numbers loses some peoples S/N's. Without a registered S/N the unlock tool will not work. This is the fault of Asus and has been discussed many times. Developers have even decompiled the unlock tool and tried to reverse engineer it to solve this issue to no avail. Please, feel free to do some research if you doubt my answers. Many have spent hours doing so to only find out what they've been told.
Click to expand...
Click to collapse
I don't doubt your answer, I had never heard about any server-related issues though. Lots of people reported that their Prime's somehow had forgotten their serial numbers, but mine still has it's serial number. Also I registered my S/N online and it's still there, but I don't think that's related in any way. I RMA'd twice, I'm able to get OTA fm updates (possibly a clue that there are no server-side issues with my S/N), but now I'm unable to unlock.
Your guide is great and I really hope it helps many users unlock their Primes so they can get rid of the stock rom and flash a proper one onto their devices. You might want to insert a note though, that even though the unlock tool has been confirmed to work on some JB-primes there's still a chance it won't work (whatever the reason is).
OK let's stop squabbling about semantics here. Fact of the matter is that whoever's able to unlock at this point is quite lucky. The rest of us will just have to wait until ASUS fixes the issues or some whizzkid with too much time on his hands does.
You are a Gem, this finally made the process so much clearer
Shizbazki said:
You are a Gem, this finally made the process so much clearer
Click to expand...
Click to collapse
Thank you feel free to hit the thanks button
Sent from my Zio using xda app-developers app
Hi. I did all the steps you mentioned. In flashing TWRP I chose the 2nd option and everything went great.
The problem appears when I want to go to my recovery (power up holding volume down and then RCK) I get the droid with exclamation mark and nothing happens. Flashing recovery was succesful and I dont have an idea what could went wrong. I'm bit a new user of TF201 so would be grateful if You can help me
EDIT: Ah, I saw now that recovery is not flashing properly, saying sth like InvalidState.
EDIT 2: Ok I handled it myself, thanks again for the guide it was very useful!
Flashed Androwook this morning. Thanks for the painless guide.
Annoyed that nvflash isn't supported on Jelly Bean though. Now that I've flashed, can I get it?
GS_Dan said:
Flashed Androwook this morning. Thanks for the painless guide.
Annoyed that nvflash isn't supported on Jelly Bean though. Now that I've flashed, can I get it?
Click to expand...
Click to collapse
Nvflash is only available to users who did it while on ICS.
Sent from my Zio using xda app-developers app
McJesus15 said:
http://forum.xda-developers.com/showthread.php?t=1998359
Link to my guide thread in the general forum. If anybody has any questions you can PM me or comment there and it'll likely be answered quickly. I'll gladly guide anyone through this process if they need other information.
Click to expand...
Click to collapse
well, I'm unlocked and TWRPed, but what I would really like is root on my stock before flashing AW. So I can install and use TB for the apps...? (I'm on most current updated stock.)
BTW, your lil guide is stupendous. Stupid easy and took minutes. TYVM! I have only vaguely been following the TP forums, stock was fine enough for me, until recently. Was bored of flashing my phone and got the itch today to try something new with the TP. Did a backup, and ready to try some Wookie! Just that lil app issue, cause I'm lazy.
EDIT: correct me if I'm wrong, but after a bit of research (go figure!) it would appear that both Sparky and debugfs won't work on JB/most current stock? Tough sh** for me?
kingdazy said:
well, I'm unlocked and TWRPed, but what I would really like is root on my stock before flashing AW. So I can install and use TB for the apps...? (I'm on most current updated stock.)
BTW, your lil guide is stupendous. Stupid easy and took minutes. TYVM! I have only vaguely been following the TP forums, stock was fine enough for me, until recently. Was bored of flashing my phone and got the itch today to try something new with the TP. Did a backup, and ready to try some Wookie! Just that lil app issue, cause I'm lazy.
EDIT: correct me if I'm wrong, but after a bit of research (go figure!) it would appear that both Sparky and debugfs won't work on JB/most current stock? Tough sh** for me?
Click to expand...
Click to collapse
Once unlocked you can root with a flashable zip. Can't link to one but they're easy to find here on the TFP forum
Sent from my Zio using xda app-developers app
So this would be su.zip (or whatever it's called), and have the following structure?
su.zip
META-INF/
CERT.RSA
CERT.SF
MANIFEST.MF
COM/
GOOGLE/
ANDROID/
update-binary
updater-script
system/
app/
Superuser.apk
bin/
su
I just want to confirm if the file I found is correct or not. Does it need to be for a specific tablet/system? If it was just the app folder and the su binary I wouldn't ask, but the inclusion of metadata has me concerned as I can't seem to find one for the prime specifically.
EDIT: Yup, that's it. I stuck it on the internal storage, went into TWRP, choose "install", navigated to the zip, and it went without a hitch (installed the su binary and superuser app, effectively rooting the system).
Overall, this a good process for people that just want to root without all the hassle of replacing the whole OS.
the unlock tool failed to unlock on my tab... i think its because i did an RMA and asus changed the board inside the device..
GS_Dan said:
Flashed Androwook this morning. Thanks for the painless guide.
Annoyed that nvflash isn't supported on Jelly Bean though. Now that I've flashed, can I get it?
Click to expand...
Click to collapse
What do you think of androwook? Is much better than stock JB?
BashYaBro said:
the unlock tool failed to unlock on my tab... i think its because i did an RMA and asus changed the board inside the device..
Click to expand...
Click to collapse
Try contacting Asus.
sauliiin said:
What do you think of androwook? Is much better than stock JB?
Click to expand...
Click to collapse
Androwook 1.4 turns the prime into the tab it should be. Out scores stock by a lot on benchmarks
Sent from my Zio using xda app-developers app
sauliiin said:
What do you think of androwook? Is much better than stock JB?
Click to expand...
Click to collapse
Very fast, responsive. With the exception of the broken search (there is a fix), and a few other minor issues, I would not hesitate to flash it. Ver 1.5 is right around the corner with several things fixed, and apparently there will be a flashable update from 1.4.
mrwookie6379 said:
Just to give you guys a heads up I will be releasing v1.5 fairly soon to take advantage of the new update that is out but before anyone groans about only having just flashed v1.4 I will release it as an update to those already on v1.4 but also as a full ROM for those who want to skip v1.4 and go straight to v1.5.
Beta 1 for v1.5 was created this PM and is being uploaded for testing now so watch this space.
Click to expand...
Click to collapse
Awesome.
kingdazy said:
Very fast, responsive. With the exception of the broken search (there is a fix), and a few other minor issues, I would not hesitate to flash it. Ver 1.5 is right around the corner with several things fixed, and apparently there will be a flashable update from 1.4.
Awesome.
Click to expand...
Click to collapse
I really ansious about flashing androwook... Just have to found some time!! Thinking about doing it this weekend!
Well.... So do you think really worths the upgrade to Androwwok? I saw that the search bug has a fix, but are there too many other bugs?
And, the performance, is really much better?
Thansk for the answer, friend.
regards
I have just seen the following thread over on the TF300 forums and it is working for them so should work here and on the TF700 also.
http://forum.xda-developers.com/showthread.php?t=2228613
flumpster said:
I have just seen the following thread over on the TF300 forums and it is working for them so should work here and on the TF700 also.
http://forum.xda-developers.com/showthread.php?t=2228613
Click to expand...
Click to collapse
Thanks for bringing this to my attention. I just rooted my TF201 in a few seconds!
For the record, it's one of the units that cannot be unlocked since the mainboard was replaced in an RMA, and I had given up hope of ever having root access. This still won't allow me to install custom roms, of course, but it's a small step in the right direction.
RodneyDekkers said:
Thanks for bringing this to my attention. I just rooted my TF201 in a few seconds!
For the record, it's one of the units that cannot be unlocked since the mainboard was replaced in an RMA, and I had given up hope of ever having root access. This still won't allow me to install custom roms, of course, but it's a small step in the right direction.
Click to expand...
Click to collapse
Glad it helped mate.. I thought a few of the people over here stuck on locked bootloaders would like it
Worked for me too, I have an unlockable bootloader so this is great. Big thanks.
This just made my night. Lost root after my last RMA and can't unlock. THANK YOU!!!
Thank you so much!! I was getting to the point I was almost regretting getting my screen fixed!!!!
Maybe someone can try the Ratchet tool to re-write the serial number?!
Thanks a lot flumpster. I have successfully rooted my TF201 (without unlocking).
Best Regards
Now Rooted although it didn't install busy box which I'm happy without.
Thanks
Weird mine does not seem to want to work, it just sits there blinking after it says it connected to device successfully and it never roots the tablet.
Jesse6749 said:
Weird mine does not seem to want to work, it just sits there blinking after it says it connected to device successfully and it never roots the tablet.
Click to expand...
Click to collapse
Try again bro. there might be connection trouble with the device and pc. Probably adb. You have enabled USB debug right?
Otherwise try on different PC.
I have use Windows 8 and had no trouble rooting the TF201. Also took ota rootkeeper backup.
CRACING said:
Try again bro. there might be connection trouble with the device and pc. Probably adb. You have enabled USB debug right?
Otherwise try on different PC.
I have use Windows 8 and had no trouble rooting the TF201. Also took ota rootkeeper backup.
Click to expand...
Click to collapse
Yeah usb debbuging is enabled, I was just thinking of trying another pc too. Thanks!!
Jesse6749 said:
Yeah usb debbuging is enabled, I was just thinking of trying another pc too. Thanks!!
Click to expand...
Click to collapse
Also make sure you have correct drivers. I had ASUS Sync already installed.
CRACING said:
Also make sure you have correct drivers. I had ASUS Sync already installed.
Click to expand...
Click to collapse
I installed the drivers on my Lenovo X200 and tried again and on that Laptop it worked like a charm.
sahilcc7 said:
Maybe someone can try the Ratchet tool to re-write the serial number?!
Click to expand...
Click to collapse
I tried. Didn't work, but I will take root.
I'm still on ICS since I never dared to upgrade to JB to not loose root.
Since there are a method now, what do I have to do to succesfully upgrade?
Thanks for your help.
netgear
Jesse6749 said:
Weird mine does not seem to want to work, it just sits there blinking after it says it connected to device successfully and it never roots the tablet.
Click to expand...
Click to collapse
Did enable USB debugging in settings /developer?
netgear64 said:
I'm still on ICS since I never dared to upgrade to JB to not loose root.
Since there are a method now, what do I have to do to succesfully upgrade?
Click to expand...
Click to collapse
You will need the JB firmware zip called: US_epad_user_10_4_2_15_UpdateLauncher.zip (Change US for WW or TW depending on your region of firmware). It looks like it is no longer available from Asus website so searching for it will be your only way.
Make sure your TF201 is charged and backup any personal important information first! If you have Voodoo OTA Root Keeper, you can also have it keep a backup of root.
Once you have downloaded it, extract the zip file within that downloaded zip. Do not extract files from the second zip.
Place that extracted zip file on the root of your internal card of TF201. (It might possibly work if you place it on the root of your external card too!) You should see a triangle notification informing you there is an update. Read the notice and proceed once you are happy with everything.
Your TF201 should restart and update to JB.
Once updated, there may be a further notification that there is another update. Apply that too. You can then root with the procedure outlined in this thread.
Hope this helps!
My experience was that I had the JB update and for some reason, I thought I had root saved with Voodoo OTA. Nothing worked and I have waited months like many others for a root solution as our bootloaders were locked. This method roots you in about a minute
Jesse6749 said:
I installed the drivers on my Lenovo X200 and tried again and on that Laptop it worked like a charm.
Click to expand...
Click to collapse
Thats great. Congrats bro. :good:
sstar said:
Did enable USB debugging in settings /developer?
Click to expand...
Click to collapse
He has already rooted. See above.
IconBoy said:
You will need the JB firmware zip called: US_epad_user_10_4_2_15_UpdateLauncher.zip (Change US for WW or TW depending on your region of firmware). It looks like it is no longer available from Asus website so searching for it will be your only way.
Make sure your TF201 is charged and backup any personal important information first! If you have Voodoo OTA Root Keeper, you can also have it keep a backup of root.
Once you have downloaded it, extract the zip file within that downloaded zip. Do not extract files from the second zip.
Place that extracted zip file on the root of your internal card of TF201. (It might possibly work if you place it on the root of your external card too!) You should see a triangle notification informing you there is an update. Read the notice and proceed once you are happy with everything.
Your TF201 should restart and update to JB.
Once updated, there may be a further notification that there is another update. Apply that too. You can then root with the procedure outlined in this thread.
Hope this helps!
My experience was that I had the JB update and for some reason, I thought I had root saved with Voodoo OTA. Nothing worked and I have waited months like many others for a root solution as our bootloaders were locked. This method roots you in about a minute
Click to expand...
Click to collapse
Thank you so much for the help.
I have a german tf201, so I guess i need the ww version of that file. You got any idea where to find that, google didn't bring up anything.
Is it also possible to use the update notification I already have for month now on the tablet?