Hi Guys,
I've skimmed around this forum for the last few days and gone through some of the posts regarding getting JB on my TF201 and after a couple of days using it and being really unsatisfied with it I've decided I really want to downgrade back to ICS.
I've searched but the scenarios regarding downgrades don't really seem to match my own circumstances. My device isn't unlocked, was rooted through "DebugfsRoot" and then updated to JB using the guides from the forums.
I've attempted putting "WW_epad-user-9.4.2.28" on the root of my MicroSD card to use the "!" triangle method. JB does recognise this as an attempt to downgrade and warns me approriately about losing everything on the tablet which isn't an issue. The downgrade seems to proceed, Andy whirs away and various progress bars complete. Upon rebooting though there is no change to the device whatsoever and JB is still on there.
I've tried copying the blob from that zip onto the device itself and using Terminal Emulator to force the tablet to downgrade to that on the next reboot. The same process happens and there's no change to the tablet upon rebooting.
Has anyone tried this successfully yet? Or will I perhaps have to attempt unlocking the device to get a new ROM on there? I don't know if I'm overlooking something simple but any help would be greatly appreciated!
Lolatron said:
Hi Guys,
I've skimmed around this forum for the last few days and gone through some of the posts regarding getting JB on my TF201 and after a couple of days using it and being really unsatisfied with it I've decided I really want to downgrade back to ICS.
I've searched but the scenarios regarding downgrades don't really seem to match my own circumstances. My device isn't unlocked, was rooted through "DebugfsRoot" and then updated to JB using the guides from the forums.
I've attempted putting "WW_epad-user-9.4.2.28" on the root of my MicroSD card to use the "!" triangle method. JB does recognise this as an attempt to downgrade and warns me approriately about losing everything on the tablet which isn't an issue. The downgrade seems to proceed, Andy whirs away and various progress bars complete. Upon rebooting though there is no change to the device whatsoever and JB is still on there.
I've tried copying the blob from that zip onto the device itself and using Terminal Emulator to force the tablet to downgrade to that on the next reboot. The same process happens and there's no change to the tablet upon rebooting.
Has anyone tried this successfully yet? Or will I perhaps have to attempt unlocking the device to get a new ROM on there? I don't know if I'm overlooking something simple but any help would be greatly appreciated!
Click to expand...
Click to collapse
I've had the same experience and it's very frustrating. My devices is even unlocked and that doesn't help.
@skaforey
if your device is unlocked you should be able to change the recovery system and then use the new recovery to load any image you want onto the device.
@Lolatron
yeah, I've been reading and trying various things the last few days too, but it seems there is no way to downgrade from JB back to ICS with a locked device.
There are a few things I enjoy on JB (like the fixed IO problems of the dock that make the sdcard slot finally useable), but I'm really missing my root acess that got wiped with JB. I'll probably unlock it if we can't find a way to regain root in the next few weeks.
Root access wasn't an issue for me, even after numerous wipes and resets I've kept that and have carried on as normal.
For me it's sluggishness (after a factory reset) on the launcher, huge frame rate drops on games, my Chrome bookmarks no longer syncing and absolutely horrible touch screen keyboard response. Overall it's a huge step down from the previous update, it's just a poor user experience.
Sent from my GT-I9100 using xda app-developers app
dopef1sh said:
@skaforey
if your device is unlocked you should be able to change the recovery system and then use the new recovery to load any image you want onto the device.
@Lolatron
yeah, I've been reading and trying various things the last few days too, but it seems there is no way to downgrade from JB back to ICS with a locked device.
There are a few things I enjoy on JB (like the fixed IO problems of the dock that make the sdcard slot finally useable), but I'm really missing my root acess that got wiped with JB. I'll probably unlock it if we can't find a way to regain root in the next few weeks.
Click to expand...
Click to collapse
You cant revert back to the ICS bootloader once you have flashed the newer JB bootloader, unless of course you have done your NVFlash backups.
Danny-B- said:
You cant revert back to the ICS bootloader once you have flashed the newer JB bootloader, unless of course you have done your NVFlash backups.
Click to expand...
Click to collapse
Awww man, I feel foolish for not knowing what NVFlash is... safe to assume I haven't done that! Ahh well... hopefully time might bring a solution along, gotta put up with this for the time being then. Thanks for the info!
Related
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
Hey guys,
Bit of an Android noob here but I am quite tech savvy. I am gonna root my Prime and install Androwook on it but first I would just like to go over some things. I have had a look around at a lot of guides and that and have figured to do this I need to unlock the bootloader using ASUS' own app fro their support, then I need to install CWM on it through the unlocked bootloader and then I can backup and install new ROMS. But which point is the root, I can't seem to find a clear answer or is it a whole new step all together? And also could you please guide me if this is completely wrong because I am paranoid about my Prime and would hate to end up with it bricked. Sorry if this is sort of in the wrong area or a bit of a repeated question, just paranoid!
Thanks,
I saw your post completely randomly, but I think I have your answer. Rooting your device can be done at any point by either unlockroot.com or DoomLord's toolkit somewhere on the site. It has no effect on installing roms/unlocking bootloaders. It simply gives you more control over a device. I hope I understood your question and helped. Good luck
Sent from my Sony Xperia Neo using xda app-developers app
Ok, thanks, that clears a lot up. I will check that out. I didn't know it was that easy. Could I also ask, which part of the process risks the device been bricked?
mdemons12 said:
Ok, thanks, that clears a lot up. I will check that out. I didn't know it was that easy. Could I also ask, which part of the process risks the device been bricked?
Click to expand...
Click to collapse
Well unlocking the bootloader SHOULD be safe if yu're unlocking by offficial means. What can damage your device is flashing the wrong files. So be REALLY careful with what you flash on your device and always double-check the tutorials in the given thread
if i remember correctly, they said you need root was to install cwm onto your system
the rooting process is very easy anyways
http://forum.xda-developers.com/showthread.php?t=1706588
for the unlocking use the asus official one (This will void ALL warranties so if you brick your prime, well then GG)
and as above post says, most things should be very save so long as you follow to the dot.
when it says DO NOT POWER THE SYSTEM DOWN, just follow what it says and don't power things down, you should be fine
download things that are for you ONLY don't go to other threads trying to install iOS onto your prime (not that its possible.... that i know of)
just read it make sure you understand you won't brick anything~
Yes well I plan on putting the Androwook rom on which seems pretty darn stable. If ASUS comes out with a JB rom for the Prime and I was on the Androwook ROM, would it still be possible to update?
mdemons12 said:
Yes well I plan on putting the Androwook rom on which seems pretty darn stable. If ASUS comes out with a JB rom for the Prime and I was on the Androwook ROM, would it still be possible to update?
Click to expand...
Click to collapse
yes the devs will be able to put jelly bean on the prime if we get the official update :fingers-crossed:
mdemons12 said:
Yes well I plan on putting the Androwook rom on which seems pretty darn stable. If ASUS comes out with a JB rom for the Prime and I was on the Androwook ROM, would it still be possible to update?
Click to expand...
Click to collapse
It is worth noting that you probably don't need to go through the root process if you are installing a custom ROM. Many (most?) custom roms grant super-user permissions by default.
well it does say in the requirements of Androwook that it requires a root.
one suggestion though, use TWRP as your recovery mode. quite handy...
mdemons12 said:
well it does say in the requirements of Androwook that it requires a root.
Click to expand...
Click to collapse
The reason you root your device is to gain superuser permissions. Most OEM versions of Android don't give you SU permissions because it is possible you could mess up your device by deleting systems files or changing hidden settings. However most custom ROMs give you superuser permissions by default.
After unlocking your Prime, I would recommend installing TWRP using the fastboot method, so that you don't need to install root first. Then you can backup your stock and flash AndroWook from TWRP. AndroWook is already rooted, so you won't need to worry about adding extra steps for root.
~Azrael's Kiss~
OK, thanks for the replies. I think I will wait a little and test the device for any major problems before I root and unlock because I don't want to have to send it back for an RMA.
So from what I have read around I need to:
1. Unlock bootloader using the ASUS tool
2. Install CWM or similar and backup my current ROM although I have seen trouble with installing 2.1 with CWM so I think I might use TWRP
3. Install Androwook 2.1 and from what I have read skip some things like bravia engine, sd wipe sqlite vacuum and add sio io scheduler.
There seem to be so many options with the installer which makes it a bit confusing but first up I think I will use the 1.6GHz Kernel or something and keep it mainly stock.
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 am running Android version 4.0.3, Build number IML74.K.US_epad_9.4.2.28-20120525.
I don't recall how I rooted, but it was an easy one step process.
Now I am in the position where I'd like to get all the firmware and JB updates for my device, but I cannot with a rooted device.
I have read different methods, one involving Rootkeeper and others involving restoring the device back to factory after a backup, getting all the updates somehow, and then re-rooting somehow and restoring the backup from Titanium.
Have also read about people loading the firmware files on a microSD card and going from there. I've had nothing but trouble with my microSD slot. Last time the card got stuck in there and I had to use tweezers and a lot of care to get the card out.
So I guess my question really is, for someone with my situation, what is the simplest way to achieve what i want to do? Where can I find a procedure and the files to go with it, including the update files and a way to do a JB root. If an external storage card is required, can the SD slot in the keyboard dock be used?
Any help is appreciated since I cannot find an exact answer to this question. Thank you.
Elizabeth K.
eklisiewicz said:
I am running Android version 4.0.3, Build number IML74.K.US_epad_9.4.2.28-20120525.
I don't recall how I rooted, but it was an easy one step process.
Now I am in the position where I'd like to get all the firmware and JB updates for my device, but I cannot with a rooted device.
I have read different methods, one involving Rootkeeper and others involving restoring the device back to factory after a backup, getting all the updates somehow, and then re-rooting somehow and restoring the backup from Titanium.
Have also read about people loading the firmware files on a microSD card and going from there. I've had nothing but trouble with my microSD slot. Last time the card got stuck in there and I had to use tweezers and a lot of care to get the card out.
So I guess my question really is, for someone with my situation, what is the simplest way to achieve what i want to do? Where can I find a procedure and the files to go with it, including the update files and a way to do a JB root. If an external storage card is required, can the SD slot in the keyboard dock be used?
Any help is appreciated since I cannot find an exact answer to this question. Thank you.
Elizabeth K.
Click to expand...
Click to collapse
Are you on a locked or unlocked Bootloader?
jimgb17 said:
Are you on a locked or unlocked Bootloader?
Click to expand...
Click to collapse
I never did anything to unlock it, so I suspect it is locked.
I read somewhere that if you boot up while pressing the Vol Down button, it will tell whether it is locked or unlocked (Two vs three icons). I tried this, but i saw no indicators displayed other than "Wipe Data" and "Android" and then the Linux prompts on the upper left of the screen. So it booted normally otherwise. Perhaps I should try it again to see if I missed something.
Yes, my bootloader is definitely locked. When I did the volume down boot up, I saw two icons in the center of the screen.
Sent from my Transformer Prime TF201 using Tapatalk 2
Is it possible to remove jellybean from tf201 and reinstall ics. I want to unlock and root my device and after days and days of reading cannot find a way to root my device or to reinstall ica
You don't need to go to ICS. I unlocked and rooted and installed the latest Energy Rom using Urkel's fresh root on JB.
However, got to warn you that one of my 2 Primes got bricked just by installing a recovery...
kapebretoner said:
Is it possible to remove jellybean from tf201 and reinstall ics. I want to unlock and root my device and after days and days of reading cannot find a way to root my device or to reinstall ica
Click to expand...
Click to collapse
The short answer to this question is no. You may not return to ICS. You can unlock and gain root. If your prime is already on jellybean via Asus update do not attempt to install cwm or twrp for ICS or you will permanently brick like garret
Root Possible???
whycali said:
The short answer to this question is no. You may not return to ICS. You can unlock and gain root. If your prime is already on jellybean via Asus update do not attempt to install cwm or twrp for ICS or you will permanently brick like garret
Click to expand...
Click to collapse
I have unlocked my prime, but I would like to root and maybe install cwm if possible.
kapebretoner said:
I have unlocked my prime, but I would like to root and maybe install cwm if possible.
Click to expand...
Click to collapse
Guess I didnt say this plainly enough, if your prime is running ASUS official jellybean version 4.1.1 you will permanently brick (turn it into a $500 paperweight) if you install cwm. To go further there is absolutely no benefit from install cwm on the tf201 ever.
whycali said:
The short answer to this question is no. You may not return to ICS. You can unlock and gain root. If your prime is already on jellybean via Asus update do not attempt to install cwm or twrp for ICS or you will permanently brick like garret
Click to expand...
Click to collapse
You misunderstood what I said. I didn't install anything for ICS. And only One of my Two Primes got bricked. And it booted just fine 2-3 times, the TWRP on this specific Prime wouldn't run for some reason when I went to the Recovery menu. So then I pressed "wipe data" , nothing happened, I rebooted and it bricked.
From what I've seen, it just happens sometimes. I've never seen such weird devices.
Garret said:
You misunderstood what I said. I didn't install anything for ICS. And only One of my Two Primes got bricked. And it booted just fine 2-3 times, the TWRP on this specific Prime wouldn't run for some reason when I went to the Recovery menu. So then I pressed "wipe data" , nothing happened, I rebooted and it bricked.
From what I've seen, it just happens sometimes. I've never seen such weird devices.
Click to expand...
Click to collapse
I didnt misunderstand you, I read your post yesterday. I was just using your brick as an example of what can happen with a bad recovery. From what I have read the reason your prime is bricked is that your recovery is attempting to boot but cant. In most cases its because the recovery needs the correct bootloader version. When you put the wrong recovery for your bootloader you get a permanent wait. It would be nice if there was a timeout for this that caused it to just boot to the os but there is not. Smarter people than me feel free to set me straight if this is not the case.
Couldn't you just flash an ICS ROM using TWRP?
Also, go for Urkel's fresh start. There's no need to go back to ICS, just to get root.
Sent from my myTouch_4G_Slide using xda premium
whycali said:
I didnt misunderstand you, I read your post yesterday. I was just using your brick as an example of what can happen with a bad recovery. From what I have read the reason your prime is bricked is that your recovery is attempting to boot but cant. In most cases its because the recovery needs the correct bootloader version. When you put the wrong recovery for your bootloader you get a permanent wait. It would be nice if there was a timeout for this that caused it to just boot to the os but there is not. Smarter people than me feel free to set me straight if this is not the case.
Click to expand...
Click to collapse
It was the correct bootloader version. For some reason sometimes even though Urkel's fresh root tells you the recovery got installed successfully, it actually does NOT. My Prime still booted fine though until I pressed "Wipe data"...grrr
I searched a lot around the net and many people had the same problem as me. The only answer I found was RMA.
Garret said:
It was the correct bootloader version. For some reason sometimes even though Urkel's fresh root tells you the recovery got installed successfully, it actually does NOT. My Prime still booted fine though until I pressed "Wipe data"...grrr
I searched a lot around the net and many people had the same problem as me. The only answer I found was RMA.
Click to expand...
Click to collapse
well as I said "in most cases". you found another way to bork yours. Guess I wont be using Urkel to do anything to my prime.
I doubt it was Urkel's fresh root that caused the problem. That specific Prime just didn't want to accept the damn TWRP. I have no idea why.
From what I've read, the damn Primes and Asus are to blame. Tons of bricks. If only they gave us the tools we to un-brick them...we could flash from APX mode and the damn things would be unbrickable.