Related
I just got a TF201. It's my first Android device, so please bear with me for this newbie issue. I wanted to root it so I tried PrimeTime without considering that I was already running version .21. Obviously it screwed up... The worst that happened is seeing a caput droid while trying to load CWM. Don't know what's the deal with that, I guess it just didn't install properly.
The device otherwise still boots fine so I'm left wondering what to do with it. Can someone explain what PrimeTime does exactly, I'd like to know in what state is my TP now...
Is there a risk that an OTA could brick it?
Can I fix CWM and flash a rooted firmware (i.e. Virtuous)?
Can I factory reset everything and lock the bootloader?
Thanks
install touch cwm or twrp and it should be fine, obiesly ota will brick it. Dunno about reseting data.
Sent from my Transformer Prime TF201 using XDA Premium App
vanista said:
I just got a TF201. It's my first Android device, so please bear with me for this newbie issue. I wanted to root it so I tried PrimeTime without considering that I was already running version .21. Obviously it screwed up... The worst that happened is seeing a caput droid while trying to load CWM. Don't know what's the deal with that, I guess it just didn't install properly.
The device otherwise still boots fine so I'm left wondering what to do with it. Can someone explain what PrimeTime does exactly, I'd like to know in what state is my TP now...
Is there a risk that an OTA could brick it?
Can I fix CWM and flash a rooted firmware (i.e. Virtuous)?
Can I factory reset everything and lock the bootloader?
Thanks
Click to expand...
Click to collapse
Another example of what may happen when people don't have patience, not reading everything.
Q: Is there a risk that an OTA could brick it?
Q: Can I fix CWM and flash a rooted firmware (i.e. Virtuous)?
A: Have you used ASUS Unlocker Tool to unlock your bootloader (thus voiding your warranty)? If you did, the awnser is yes for the first 2 questions.
Q: Can I factory reset everything and lock the bootloader?
A: Relocking bootloader isn't possible; You can factory reset everything through Android UI/stock rom only if you didn't install CWM as of yet.
bk201doesntexist said:
Q: Can I factory reset everything and lock the bootloader?
A: Relocking bootloader isn't possible; You can factory reset everything through Android UI/stock rom only if you didn't install CWM as of yet.
Click to expand...
Click to collapse
Thanks for the reply
Can you elaborate, I don't know how far PrimeTime went trying to install CWM. What happens if I reset with CWM present? Can it be cleaned?
vanista said:
Thanks for the reply
Can you elaborate, I don't know how far PrimeTime went trying to install CWM. What happens if I reset with CWM present? Can it be cleaned?
Click to expand...
Click to collapse
I think that if you try to factory reset with CWM installed it will bootloop/brick, I've read it somewhere here on xda.
Again, CWM can only be installed if bootloader has been unlocked. If you didn't and PrimeTime doesn't as well, you cannot have cwm installed.
I believe there was some information laying around about returning to stock, not sure if it's possible to return to stock recovery after flashing cwm.
bk201doesntexist said:
Again, CWM can only be installed if bootloader has been unlocked. If you didn't and PrimeTime doesn't as well, you cannot have cwm installed.
Click to expand...
Click to collapse
My bootloader is unlocked but I'm not rooted, apparently I cannot install CWM from ROM Manager. Is it possible through fastboot? When I try to go into recovery mode I get the laid down dead droid... Is that caused by a faulty CWM or just that I don't have a recovery image anymore?
I modified ViperMODS tool to add Xda user wolf849's method of downgrading a transformer without root, so you can use this http://forum.xda-developers.com/showpost.php?p=25508554&postcount=52 to downgrade to .15 then root, then install OTA rootkeeper then update via ota to .21 again. Or you can just unlock and install cwm if you want to void warranty.
Okay this is just getting more and more confusing. Everywhere I read about CWM and custom ROMs it says you have to be rooted. If that is true then I'm in a dead end because I cannot downgrade to .15 without bricking and I can't properly install CWM either.
I finally found some official doc on fastboot source.android.com/source/building-devices.html , if its accurate you don't even need CWM to flash a custom rom. That seems to be much more reliable. Isn't CWM just a wrapper for what can all be done manually through adb??
Finally found some precise instructions... androidroot.mobi/2012/02/22/introducing-cwm-for-asus-transformer-prime/
Instructions for non-rooted Primes (or those who’d rather use fastboot):
Get fastboot from here, and extract it.
Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
Power off your prime.
Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot”.
Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
Profit!
vanista said:
My bootloader is unlocked but I'm not rooted, apparently I cannot install CWM from ROM Manager. Is it possible through fastboot? When I try to go into recovery mode I get the laid down dead droid... Is that caused by a faulty CWM or just that I don't have a recovery image anymore?
Click to expand...
Click to collapse
you awnsered yourself below
bpear96 said:
I modified ViperMODS tool to add Xda user wolf849's method of downgrading a transformer without root, so you can use this http://forum.xda-developers.com/showpost.php?p=25508554&postcount=52 to downgrade to .15 then root, then install OTA rootkeeper then update via ota to .21 again. Or you can just unlock and install cwm if you want to void warranty.
Click to expand...
Click to collapse
he's unlocked, he can't run an official blob, that method does not work for him
vanista said:
Okay this is just getting more and more confusing. Everywhere I read about CWM and custom ROMs it says you have to be rooted. If that is true then I'm in a dead end because I cannot downgrade to .15 without bricking and I can't properly install CWM either.
I finally found some official doc on fastboot source.android.com/source/building-devices.html , if its accurate you don't even need CWM to flash a custom rom. That seems to be much more reliable. Isn't CWM just a wrapper for what can all be done manually through adb??
Click to expand...
Click to collapse
don't look on source.android.com, aosp doesn't support transformer prime directly, and as you might have noticed, fastboot commands are a bit different for the prime that of galaxy nexus, for example.
why some say you need to be rooted to flash cwm? because they use ROM Manager nice UI to do it, instead of teaching people how to do it without an UI. Rom Manager needs root, as you know.
vanista said:
Finally found some precise instructions... androidroot.mobi/2012/02/22/introducing-cwm-for-asus-transformer-prime/
Instructions for non-rooted Primes (or those who’d rather use fastboot):
Get fastboot from here, and extract it.
Download the blob file (tfp_CWM5_androidroot.blob), and put it in the same folder as where you extracted fastboot.
Power off your prime.
Boot with Volume-down pressed. Wait when you see text appearing. The prime will then allow you to start “fastboot”.
Open up a command-line prompt, and navigate to where you extracted fastboot with “cd”.
Enter the following commandline to flash recovery: fastboot -i 0x0b05 flash recovery tfp_CWM5_androidroot.blob
Profit!
Click to expand...
Click to collapse
exactly, use these steps from androidroot.mobi to flash cwm with fastboot. these are correct, and the only way to flash cwm, if you're unlocked but not rooted.
food for thought: i believe linux+fastboot is way safer than windows+fastboot.
Great! Thanks for the confirmation, quite reassuring, now I know where I'm headed... I'll at least fix my recovery with CWM. From there I don't know, I feel I have to do some more reading before I go ahead and flash any custom rom...
I may not know much on android yet, but I have 10 years experience in linux software dev, with a few pointers like this to get me started I should be able to do anything with this toy soon enough ;-)
Done, just flashed CWM as per the instructions and it works flawlessly. Backing up right now... I'm tempted to go ahead and flash Virtuous.
Done, totally virtuous now ... That was easy Thanks again for the help! Now I only hope I won't regret voiding the warranty
Hey XDA, can we talk? cause im about to cry man tears.
First off you are much better at android then I am, this isn't me trying to sound humble, I suck and the threat of bricking my toys scares me.
Today I found a way to get root access without unlocking my bootloader and I was thrilled, it was easy and it worked! I had root access and then decided I was going to try to install CyanogenMod 10 (latest nightly) and so I installed ROM Manager and downloaded CyanogenMod, when I tried to boot to recovery mode (hold down volume and power, then up volume) I would get the dead android with an exclamation point, every time.
So I decided to unlock my bootloader, I went searching and came across the ASUS official bootloader unlocker and it said the unlocker was for ICS and I have already upgraded the ASUS rom to jellybean, I decided to try the unlock device app anyway and now when I restart the words "this device is unlocked" show in the top left corner, I thought that meant the bootloader is unlocked but when I restart into recovery mode I still get the dead android.
I cant find any information anywhere about how to unlock an ASUS jellybean bootloader and I am only guessing that why I keep getting the dead android.
Anyway, if you can help thats awesome, I am usually the kind of guy that can read and find the answers but **** me if I cant find them anywhere, I was never good at the world of bootloaders, whether PC or Android and I am hoping to find a hand and learn something more here
Thanks
I know its my first time here to post but I have read loads of stuff off this site.
78 people read this already, one of you must be able to point my dumbass in the right direction?
bueller, bueller ...:crying:
Once I get an idea of what I am doing wrong and why I keep getting the dead android, I think I will try to install AndroWook 2.2
ArghMonkey said:
Once I get an idea of what I am doing wrong and why I keep getting the dead android, I think I will try to install AndroWook 2.2
Click to expand...
Click to collapse
You are unlocked but you do not have a custom recovery installed yet.
Go to the TWRP thread and follow the instructions for installing TWRP for the JB bootloader. Do not install CWM.
Make sure you get the correct TWRP for the JB bootloader.
flumpster said:
You are unlocked but you do not have a custom recovery installed yet.
Go to the TWRP thread and follow the instructions for installing TWRP for the JB bootloader. Do not install CWM.
Make sure you get the correct TWRP for the JB bootloader.
Click to expand...
Click to collapse
Sweet, im on it right now
Wow, there are TWRP threads everywhere, several downloads, I even did a search within the transformer prime subthread and cant find one version mentioned for the JB bootloader.
Ill keep looking ...
Lost again.
So I found this
http://teamw.in/project/twrp2/93
But then I read this
"We STRONGLY recommend users enable and backup your device before flashing custom roms/recoveries with nvflash courtesy of AndroidRoot.mobi (this also makes your device essentially "brick-proof") - you need to be on the ICS bootloader to do this, if you have taken the JB OTA from Asus you cannot get nvflash access.
If you have updated to the JB OTA bootloader then you must use the -JB version of the recovery, flashing the non -JB version could potentially permanently brick your device (unless you have nvflash as noted above)."
And have no idea which way I should proceed, should I downgrade? no idea how to do that, I think I read somewhere if I have the official formware updates from ASUS that I can stick it on my microSD and the asus recovery will see it and install the downgrade.
Or should I just go for it, that bricking is a risk but low?
I know I am running jellybean but I still dont have a clue exactly what bootloader I have, I assume there are several versions under jellybean but I cant find any guides to tell me exactly where to find what bootloader version I have.
1: Can anyone tell me how I find exactly which bootloader I am running? I have JB installed (4.1.1)
2: So what version of TWRP do I need to download?
3: How would I install TWRP?
and yes, I am unlocked and rooted, help!
Download TWRP 2.5.0.0 for JB blob from here: http://teamw.in/project/twrp2/93
Rename to twrp.blob
Use command prompt on your computer to flash recovery to tablet using this command: fastboot -i 0x0b05 flash recovery twrp.blob
....................
Follow this thread: http://forum.xda-developers.com/showthread.php?t=2038464
---------- Post added at 12:37 PM ---------- Previous post was at 12:35 PM ----------
ArghMonkey said:
Lost again.
So I found this
http://teamw.in/project/twrp2/93
But then I read this
"We STRONGLY recommend users enable and backup your device before flashing custom roms/recoveries with nvflash courtesy of AndroidRoot.mobi (this also makes your device essentially "brick-proof") - you need to be on the ICS bootloader to do this, if you have taken the JB OTA from Asus you cannot get nvflash access.
If you have updated to the JB OTA bootloader then you must use the -JB version of the recovery, flashing the non -JB version could potentially permanently brick your device (unless you have nvflash as noted above)."
And have no idea which way I should proceed, should I downgrade? no idea how to do that, I think I read somewhere if I have the official formware updates from ASUS that I can stick it on my microSD and the asus recovery will see it and install the downgrade.
Or should I just go for it, that bricking is a risk but low?
I know I am running jellybean but I still dont have a clue exactly what bootloader I have, I assume there are several versions under jellybean but I cant find any guides to tell me exactly where to find what bootloader version I have.
Click to expand...
Click to collapse
You can't use NVFlash because you are on the JB bootloader. You can't downgrade to ICS.
Great links!
Thanks for your help, I will report back once I try this
ArghMonkey said:
Great links!
Thanks for your help, I will report back once I try this
Click to expand...
Click to collapse
Any update? I've had my Prime for over a year. Rooted tonight, looking to unlock the bootloader and flash a custom ROM. Interested to hear the results.
Flash TWRP:
Once unlocked, power it off. Once off power it on by holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install for fastboot. I got all my drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here" (Vista + only or if you installed powertools on 2000/XP)
Click to expand...
Click to collapse
Ok, so I followed your link, I downloaded the Android SDK and when I opened it I see a million things, the Google USB Driver was highlighted so I installed it, are there other drivers im supposed to install before I go to the next step?!
Lavman72 said:
Any update? I've had my Prime for over a year. Rooted tonight, looking to unlock the bootloader and flash a custom ROM. Interested to hear the results.
Click to expand...
Click to collapse
Working on it right now, flashed twrp over, prime is starting up right now *fingers crossed*
and yes! it booted to stock, now to transfer over supersu ...
Awesome TWRP is alive and in charge, now to flash with Androwook!
It aint over but its getting close
ArghMonkey said:
Awesome TWRP is alive and in charge, now to flash with Androwook!
It aint over but its getting close
Click to expand...
Click to collapse
That's great news. Did you follow the steps on this thread?
http://forum.xda-developers.com/showthread.php?t=2038464
Any suggestions or pointers? I've rooted/installed custom roms on many phones, but this one seems to be the most complicated/risky.
Lavman72 said:
That's great news. Did you follow the steps on this thread?
http://forum.xda-developers.com/showthread.php?t=2038464
Any suggestions or pointers? I've rooted/installed custom roms on many phones, but this one seems to be the most complicated/risky.
Click to expand...
Click to collapse
Yup, thats how i did it.
The biggest obstacle is unclear instructions or instructions that assume the reader is not a noob *L*
ArghMonkey said:
Yup, thats how i did it.
The biggest obstacle is unclear instructions or instructions that assume the reader is not a noob *L*
Click to expand...
Click to collapse
Excellent. I'll probably give it a go in the next couple of days. Strange that the Unlock tool works. I've read other posts that state if you are already on JB (which I am) the unlook tool won't work.
Lavman72 said:
Excellent. I'll probably give it a go in the next couple of days. Strange that the Unlock tool works. I've read other posts that state if you are already on JB (which I am) the unlook tool won't work.
Click to expand...
Click to collapse
Everything is totally installed and working great now, Whew, what a relief!
Thanks folks!
ArghMonkey said:
Everything is totally installed and working great now, Whew, what a relief!
Thanks folks!
Click to expand...
Click to collapse
Rooted: Check
Unlocked bootloader: Check
Tired though, and it's late. So I'm going to hold off on the final steps.
I found the following post while doing my daily read thru all the other forums and some people are saying that it has rescued them from wrong TWRP flash and Unrecoverable Bootloader errors.
I would try to do all the other methods available first but if you are completely bricked then you have nothing to lose.
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
flumpster said:
I found the following post while doing my daily read thru all the other forums and some people are saying that it has rescued them from wrong TWRP flash and Unrecoverable Bootloader errors.
I would try to do all the other methods available first but if you are completely bricked then you have nothing to lose.
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Click to expand...
Click to collapse
Flumpster, I was going to start a separate thread to take my brick issues out of your dev thread and saw your thread here. So the option here is to reboot into fastboot, basically wipe everything and then flash the system blob from a stock ROM.
My main question is what if the person is on a TF300T bootloader, in my case 10.6.1.8. Would flashing the latest stock Asus JB ROM over 'system' for the TF200 replace the bootloader as well?
trogdan said:
Flumpster, I was going to start a separate thread to take my brick issues out of your dev thread and saw your thread here. So the option here is to reboot into fastboot, basically wipe everything and then flash the system blob from a stock ROM.
My main question is what if the person is on a TF300T bootloader, in my case 10.6.1.8. Would flashing the latest stock Asus JB ROM over 'system' for the TF200 replace the bootloader as well?
Click to expand...
Click to collapse
To answer myself, yes it does replace the bootloader. The latest ROM on Asus (from last Dec 2012) installs bootloader 1.00e ww_epad-10.4.2.18-20121122 a03
I installed stock TWRP 2.5.0 here for JB based on this thread and was able to get into TWRP and install the Hairybean Upgrade for 2.3, followed by the HB 2.3, and am now booting into the ROM. W00t! Great link in the OP flumpster.
trogdan said:
To answer myself, yes it does replace the bootloader. The latest ROM on Asus (from last Dec 2012) installs bootloader 1.00e ww_epad-10.4.2.18-20121122 a03
I installed stock TWRP 2.5.0 here for JB based on this thread and was able to get into TWRP and install the Hairybean Upgrade for 2.3, followed by the HB 2.3, and am now booting into the ROM. W00t! Great link in the OP flumpster.
Click to expand...
Click to collapse
Ah. I see you have it fixed now.
Ignore the pm I just sent you then.
I have the same issue and i solved it with your link
Can't get in to fastboot?
I just cant get in to fastboot mode.
KingJelle said:
I just cant get in to fastboot mode.
Click to expand...
Click to collapse
adb reboot bootloader
When in recovery.
I just got a used prime and was trying to root/unlock/custom recovery/rom but I think I did something wrong.
This process seems a lot more delicate and volatile than my phone
I installed cwm through the CWM Rom Manager app after unlocking and rooting both of which went smoothly and device booted, and the device was properly rooted. After flashing recovery through CWM Rom Manager app I am ASUS boot screen
The one with "the device is unlocked" in the upper right corner and just sits in that state indefinitely. Can't do anything other than restart and get back to that screen. Any ideas?
hypocritelecteur said:
I just got a used prime and was trying to root/unlock/custom recovery/rom but I think I did something wrong.
This process seems a lot more delicate and volatile than my phone
I installed cwm through the CWM Rom Manager app after unlocking and rooting both of which went smoothly and device booted, and the device was properly rooted. After flashing recovery through CWM Rom Manager app I am ASUS boot screen
The one with "the device is unlocked" in the upper right corner and just sits in that state indefinitely. Can't do anything other than restart and get back to that screen. Any ideas?
Click to expand...
Click to collapse
Unfortunately you never read up on anything before attempting it. There are warnings everywhere on this forum saying not to use cwm on the prime and not to use rom manager and goo manager.
The last official version of cwm on the prime was for the ICS bootloader and if you flash that recovery onto jellybean bootloader then chances are you are going to brick yourself. Rom manager doesn't check what you are on and just installs the ICS version anyway. I reported this to Koush 2 years ago and he did nothing about it.
If you can't get to the bootloader or recovery by holding down volume down and power the same time and you also don't have nvflash backups then I am afraid that you are hard bricked.
There are only 2 options. Either pay Asus to fix it which will cost you more than you paid for it or you buy a motherboard off ebay or one with a smashed screen but still working and swap the motherboard out.
hypocritelecteur said:
Drat. Is there absolutely no chance, no method that might possibly work? No system dumps or backups or anything I can snag from another user to bootstrap my way back to functionality? I admit I jumped the gun here defs. I've been mucking with roms and hacks for android for years and never hard bricked anything and never run into a system this volatile. Didn't realize I was even being reckless! Just a different world I guess. This is however my first tab--are they in general more risky?
Click to expand...
Click to collapse
I know how you feel mate as before getting this tablet I have had numerous android devices and have had lots since and this is by far the easiest to hard brick. With other devices you can mess up but normally there is a method back in (odin etc) but Asus decided to tie it down completely.
The nvflash guys did a great job to make our devices brick proof but you have to make sure that you have your backups first. No one elses backups can be used. They are specific to your motherboard.
You can pick up motherboards quite cheap on ebay and someone here on one of the recent posts even put a tf300 motherboard in there instead as it was a lot cheaper ($50). They are basically the same machines anyway.
Was it unlocked when you got it ? If it was ask the original owner if he ever made nvflash backups.
tf201 maybe bricked
flumpster said:
I know how you feel mate as before getting this tablet I have had numerous android devices and have had lots since and this is by far the easiest to hard brick. With other devices you can mess up but normally there is a method back in (odin etc) but Asus decided to tie it down completely.
The nvflash guys did a great job to make our devices brick proof but you have to make sure that you have your backups first. No one elses backups can be used. They are specific to your motherboard.
You can pick up motherboards quite cheap on ebay and someone here on one of the recent posts even put a tf300 motherboard in there instead as it was a lot cheaper ($50). They are basically the same machines anyway.
Was it unlocked when you got it ? If it was ask the original owner if he ever made nvflash backups.
Click to expand...
Click to collapse
well i tried all these thinks but i can not get into fastboot or into my OS doesn't see my micro sd card also at all it does is go back to the twrp recovery 2.6.3.0 it is wrong file in the twrp recovery all files are empty did i brick my tf201 and is it a paper weight this all it does can't back up or install anything no files and don't see my sd card also need help please
Exterminator77 said:
well i tried all these thinks but i can not get into fastboot or into my OS doesn't see my micro sd card also at all it does is go back to the twrp recovery 2.6.3.0 it is wrong file in the twrp recovery all files are empty did i brick my tf201 and is it a paper weight this all it does can't back up or install anything no files and don't see my sd card also need help please
Click to expand...
Click to collapse
When in TWRP you should have adb access if you have the drivers installed.
Try.
Code:
adb reboot bootloader
to get you back to fastboot.
I managed to install original system blob. But what now? After start I have again four options, but my Prime is not booting into system or recovery. It always hang up on starting screen with ASUS logo or wit a dead robot.
Thank you.
---------- Post added at 09:05 PM ---------- Previous post was at 08:06 PM ----------
ok, now I am totally bricked, I restarted my Prime and it is black, even backlight is dead. It only reacts to power button, when I hold it, it vibrates after a while.
Fastboot or ADB cannot contol it.
Dammit
Did you ever manage to get your system back?
I used ADB to make a backup of my TF201.
I couldn't get ROM manager to flash a new ROM - every time RM restarted the TF201 I simply got the screen The Device is UnLocked together with the graphical menu for Recovery, Android, USB and Wipe and it just sat there and did nothing.
Eventually, I pushed the CWM ZIP into /SDCARD/ renamed it to UPDATE.ZIP then tried rebooting to see if it would treat that like an OTA update - it didn't.
So then I chose the Wipe option. It sat there for ages with nothing happening.
So I then rebooted - now I get the The Device is Unlocked in the top left hand corner, the ASUS logo in the middle and the Powered by NVIDIA`TEGRA` in the bottom right but it does not boot - it is bricked!
My PC no longer sees it in ADB or FASTBOOT so I can't either flash something or restore my carefully taken backup.
It won't boot into anything other than the screen above - so the key combination for Fastboot doesn't work any more.
Prior to all this it was running stock 4.1.1 but was successfully rooted and had been like that for quite some time.
Any ideas?
Kind Regards
Steve
Hi, I have the same problem than the last message. It's impossible!! any ideas please??
Thanks
Vanessa
Hrd Bricked tf201
sdemills said:
Did you ever manage to get your system back?
I used ADB to make a backup of my TF201.
I couldn't get ROM manager to flash a new ROM - every time RM restarted the TF201 I simply got the screen The Device is UnLocked together with the graphical menu for Recovery, Android, USB and Wipe and it just sat there and did nothing.
Eventually, I pushed the CWM ZIP into /SDCARD/ renamed it to UPDATE.ZIP then tried rebooting to see if it would treat that like an OTA update - it didn't.
So then I chose the Wipe option. It sat there for ages with nothing happening.
So I then rebooted - now I get the The Device is Unlocked in the top left hand corner, the ASUS logo in the middle and the Powered by NVIDIA`TEGRA` in the bottom right but it does not boot - it is bricked!
My PC no longer sees it in ADB or FASTBOOT so I can't either flash something or restore my carefully taken backup.
It won't boot into anything other than the screen above - so the key combination for Fastboot doesn't work any more.
Prior to all this it was running stock 4.1.1 but was successfully rooted and had been like that for quite some time.
Any ideas?
Kind Regards
Steve
Click to expand...
Click to collapse
Hi Steve:
Well darn it, I'm another one with a completely bricked tf201. Without going into how I got there, I have the same situation as you... with "The Device is Unlocked" in the upper-left of the screen, "ASUS" in the center and "Powered by Tegra" in the lower right. If I boot with either just the power button, or the power botton and volume down, I get the affore-mentioned screen.
If I boot with power button and volume up, I get a completely black screen. I was very interested in whether you received a reply to your question?
I've noticed that the greater percentage of these questions, as I've described my system, remain unanswered. Not that I am complaining, but I am certainly interested in whether or not there is a remedy as of this date? I am not able to afford sending my tablet to ASUS, so would really appreciate any work arounds I could try.
Cheers man. Hope to hear from you.
Jim
Hi. I would like to protect my device with nvflash before setup first rom.
I read guide about access to nvflash:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean
and
matthill.eu/android/transformer-prime-tf201-jellybean-nvflash
But I am not sure it's valid for my bootloader version. I have TF 201 with Jelly Bean and 10.4.2.18 bootloader. This bootloader comes from officials updates.
I am especially afraid this step: "wheelie / advances / Step 1: Flash AndroidRoot BL". It is can brick my device because of other version of bootloader? In guide is marked version: 10.4.2.15.
I really need help!
Best regards.
Have you read http://forum.xda-developers.com/showthread.php?t=1927818 ?
hp321 said:
Hi. I would like to protect my device with nvflash before setup first rom.
I read guide about access to nvflash:
androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean
and
matthill.eu/android/transformer-prime-tf201-jellybean-nvflash
But I am not sure it's valid for my bootloader version. I have TF 201 with Jelly Bean and 10.4.2.18 bootloader. This bootloader comes from officials updates.
I am especially afraid this step: "wheelie / advances / Step 1: Flash AndroidRoot BL". It is can brick my device because of other version of bootloader? In guide is marked version: 10.4.2.15.
I really need help!
Best regards.
Click to expand...
Click to collapse
You are right to check everything out first :good:. But there is no need to worry about the bootloader as the Flatline process will flash the 10.4.2.15 version. It will also leave behind its own customised version of CWM recovery. Unlike the official version this is compatible with JB bootloader but it is rather clunky and limited so you would do well to replace it with TWRP once you are happy the NVFlash process has gone well.
Restorer said:
You are right to check everything out first :good:. But there is no need to worry about the bootloader as the Flatline process will flash the 10.4.2.15 version. It will also leave behind its own customised version of CWM recovery. Unlike the official version this is compatible with JB bootloader but it is rather clunky and limited so you would do well to replace it with TWRP once you are happy the NVFlash process has gone well.
Click to expand...
Click to collapse
I appreciate your help. So after enabled nvflash my version of bootloader will change? Will I be able after this run my old Android version?
I would like to process this procedure:
matthill.eu/android/transformer-prime-tf201-jellybean-nvflash
My next question is about TWRP. CWM published with nvflash is to limited to setup new rom on my device? It is necessary to setup TWRP on my restore partition? This is not disable nvflash?
hp321 said:
I appreciate your help. So after enabled nvflash my version of bootloader will change? Will I be able after this run my old Android version?
Click to expand...
Click to collapse
Yes, for sure.
I would like to process this procedure:
matthill.eu/android/transformer-prime-tf201-jellybean-nvflash
My next question is about TWRP. CWM published with nvflash is to limited to setup new rom on my device? It is necessary to setup TWRP on my restore partition?
Click to expand...
Click to collapse
The version of CWM flashed by Flatline will continue to work but it was really designed just to be used for the NVFlash process. It is based on an older non-touch version and changing to TWRP would be most people's advice.
This is not disable nvflash?
Click to expand...
Click to collapse
No, APX mode will continue to be available provided you have the correct drivers.
TWRP Recovery freezes when trying to boot to Recovery Kernal
I have a Transformer Prime tf201. I've installed twrp2.6 using fastboot. Everything looked fine. I go the blue progress bar on the prime 100% No errors. When I boot to recovery RCK, it says "Booting Recovery kernal image" and just sits there. I left it over night thinking it may have to think about it for a while but it still just sits there. Any ideas?
Also when I used TWRP Manager. I did a "Wipe Data" and selected cache. It reboots the TF201, says "The device is unlocked." (upper left small letters) shows a ASUS logo in the middle and freezes. Ideas on that?
Thanks for all you guys/gals do...
Restorer said:
Yes, for sure.
The version of CWM flashed by Flatline will continue to work but it was really designed just to be used for the NVFlash process. It is based on an older non-touch version and changing to TWRP would be most people's advice.
No, APX mode will continue to be available provided you have the correct drivers.
Click to expand...
Click to collapse
I think you've answered the question I've spent days searching for. I have stock ASUS 10.4.2.17 rooted and recently unlocked to put nvflash on it. I want to update to 10.4.2.18 but read the update file from the ASUS website flashed through CWM has high risk of bricking the device. I was afraid CWM was mandatory to recover with nvflash, but, sounds like that's not the case. So I can just flash TWRP (which will remove CWM recovery) and then flash the Asus 10.4.2.18 update with TWRP? Secondly, I'm trying to work up the courage to try hairy bean, so I need TWRP for that reason as well.
casey225 said:
I think you've answered the question I've spent days searching for. I have stock ASUS 10.4.2.17 rooted and recently unlocked to put nvflash on it. I want to update to 10.4.2.18 but read the update file from the ASUS website flashed through CWM has high risk of bricking the device. I was afraid CWM was mandatory to recover with nvflash, but, sounds like that's not the case. So I can just flash TWRP (which will remove CWM recovery) and then flash the Asus 10.4.2.18 update with TWRP? Secondly, I'm trying to work up the courage to try hairy bean, so I need TWRP for that reason as well.
Click to expand...
Click to collapse
I would go straight for the HairyBean 2.31 ROM - as you probably read, the first stage of installing that involves flashing TWRP along with a new bootloader anyway . Some of us had trouble getting getting Flatline's CWM to see our external card though - so you may need to flash the normal TWRP first anyway.
Restorer said:
I would go straight for the HairyBean 2.31 ROM - as you probably read, the first stage of installing that involves flashing TWRP along with a new bootloader anyway . Some of us had trouble getting getting Flatline's CWM to see our external card though - so you may need to flash the normal TWRP first anyway.
Click to expand...
Click to collapse
I plan to update to 10.4.2.18 first, do I need to make a new set of nvflash backup files, to prevent bootloader mismatch, after flashing a new recovery (since I haven't seen any that use .17).
casey225 said:
I plan to update to 10.4.2.18 first, do I need to make a new set of nvflash backup files, to prevent bootloader mismatch, after flashing a new recovery (since I haven't seen any that use .17).
Click to expand...
Click to collapse
Once you have your NVFlash backups that's it - you are all set for good.
Not sure what you mean by your second point. Do you mean you intend to update the whole ROM to 10.4.2.18 or just the bootloader? The bootloader 10.4.2.15 flashed by flatliner is still an android 4.1 version so would not be a problem - the dangerous bootloader/recovery mismatch people warn about is JB/ICS. The reason CWM is always the bad guy here is because their official version for the Prime has never been updated beyond ICS - though of course the version included with flatliner is compatible with JB.
Restorer said:
Once you have your NVFlash backups that's it - you are all set for good.
Not sure what you mean by your second point. Do you mean you intend to update the whole ROM to 10.4.2.18 or just the bootloader? The bootloader 10.4.2.15 flashed by flatliner is still an android 4.1 version so would not be a problem - the dangerous bootloader/recovery mismatch people warn about is JB/ICS. The reason CWM is always the bad guy here is because their official version for the Prime has never been updated beyond ICS - though of course the version included with flatliner is compatible with JB.
Click to expand...
Click to collapse
I realized after I posted that it shouldn't be a problem, but I couldn't delete the post. I flashed TWRP 2.6.3.0 successfully, but, when I hit the menu button it says "updating partition details..." I left it overnight and now 10 hours later it was frozen on that screen. I rebooted into recovery and tried to make a backup but it said there wasn't enough space even though it was seeing roughly 10GB (I have 64 GB edition) and the backup was a little over 1GB. When I hit menu, it kept showing me the verbage from the failed backup. Installed Goo manager which seems to function normally. I have rebooted back into recovery and hit menu button and it is updating partition details again. Should I wait even longer, should I try to keep the screen from timing out until it's done? Thanks so much for your help so far!
casey225 said:
I realized after I posted that it shouldn't be a problem, but I couldn't delete the post. I flashed TWRP 2.6.3.0 successfully, but, when I hit the menu button it says "updating partition details..." I left it overnight and now 10 hours later it was frozen on that screen. I rebooted into recovery and tried to make a backup but it said there wasn't enough space even though it was seeing roughly 10GB (I have 64 GB edition) and the backup was a little over 1GB. When I hit menu, it kept showing me the verbage from the failed backup. Installed Goo manager which seems to function normally. I have rebooted back into recovery and hit menu button and it is updating partition details again. Should I wait even longer, should I try to keep the screen from timing out until it's done? Thanks so much for your help so far!
Click to expand...
Click to collapse
So you did use fastboot to flash the recovery image using instructions from the correct section on this page?
Restorer said:
So you did use fastboot to flash the recovery image using instructions from the correct section on this page?
Click to expand...
Click to collapse
I just realized the problem. I went in to set the backup to go to the sd card, the first time I went into recovery, but didn't do the backup at that time. It reverted back to use internal storage and that's why it said there wasn't enough space. Making a backup as we speak...
What happened to the beating your head against the wall icon!
casey225 said:
I just realized the problem. I went in to set the backup to go to the sd card, the first time I went into recovery, but didn't do the backup at that time. It reverted back to use internal storage and that's why it said there wasn't enough space. Making a backup as we speak...
What happened to the beating your head against the wall icon!
Click to expand...
Click to collapse
Here ya go
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi All
I have just installed nvflash and copy files to pc ...just incase i brick it .....i did this when i first install flatline recovery ...now i have installed TWRP and install hairybean v2.3 and the update twrp ...do i need to nvflash it again and get the recovery files ? or will the original ones be fine ?
karl
karlos103 said:
Hi All
I have just installed nvflash and copy files to pc ...just incase i brick it .....i did this when i first install flatline recovery ...now i have installed TWRP and install hairybean v2.3 and the update twrp ...do i need to nvflash it again and get the recovery files ? or will the original ones be fine ?
karl
Click to expand...
Click to collapse
They will be fine.
Restorer said:
They will be fine.
Click to expand...
Click to collapse
That's good to hear
Many thanks
Karl
Easyflasher
This might be a bit off topic but does any one know if easyflasher will work on tf201? It's bricked and can only get APX mode and I don't have a nvflash backup.
Thanks.
Restorer said:
You are right to check everything out first :good:. But there is no need to worry about the bootloader as the Flatline process will flash the 10.4.2.15 version. It will also leave behind its own customised version of CWM recovery. Unlike the official version this is compatible with JB bootloader but it is rather clunky and limited so you would do well to replace it with TWRP once you are happy the NVFlash process has gone well.
Click to expand...
Click to collapse
So that's the JB .img file or the JB .blob file from their site? After doing wheelie step #1, it's not fully an ASUS Bootloader anymore. Or is it enough of an ASUS bootloader that you need to use the JB bootloader .blob one for ASUS?
For doing after nvflash, the teamw.in/project/twrp2/93 page says ICS only - in red - right before an ICS .img file and JB .img file.
I haven't found much more than this thread about what to do on JB after nvflash to get TWRP. :silly:
Arfyness said:
So that's the JB .img file or the JB .blob file from their site? After doing wheelie step #1, it's not fully an ASUS Bootloader anymore. Or is it enough of an ASUS bootloader that you need to use the JB bootloader .blob one for ASUS?
Click to expand...
Click to collapse
Not sure what you are asking here . AFAIK it is pure Asus JB bootloader 10.4.2.15. It is the recovery that you are left with that is a modified, rather basic CWM - CWM never has made an official JB recovery for our device and it is people flashing the ICS version onto their JB bootloaders that has been a major source of hard bricks.
My advice would be to install the latest JB TWRP so you know for sure you have fully compatible JB bootloader/recovery.
For doing after nvflash, the teamw.in/project/twrp2/93 page says ICS only - in red - right before an ICS .img file and JB .img file.
I haven't found much more than this thread about what to do on JB after nvflash to get TWRP. :silly:
Click to expand...
Click to collapse
I don't see the red text you mention. Anyhow, from the TWRP page in your link you are only interested in the section: Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader).. Ignore everything else on that page. Follow the install instructions in that paragraph - click the link to the JB blob files and download the latest blob (NOT img) one from the bottom of the list.
Hey there, everybody! Just got a 201 as a "parts only" tablet... turns out it just needed a trickle charge, so i'm off to the races. Wanted to put KatshMallow on here like I have on my tf300... Finally found out that in order to flash the hairybean stuff (so i can actually flash katshmallow) I needed twrp 2.5.0.0 first. So, upon discovering this, I downloaded the proper twrp image and went to flash the recovery via fastboot.
did 'fastboot devices' to make sure it saw the tablet... all good there.
did the 'flash' command, posted the [sending] and [receiving] steps, all said OK
did the 'adb reboot' command just to get things established and boot into the recovery...
but i don't get a recovery prompt, just a dead android with the 'x'. :/
now i don't even have a recovery module. I downloaded the proper package, but went and downloaded elsewhere just to be sure, and got the same result. I *was* going to ask if someone would post a nandroid from a tf201 that already had katshmallow running and try and establish myself that way, but again, no recovery at all. What do I do from here? anybody happen to know what the last twrp version for the 201 that works with JB 4.1.1? i can try to flash a 2.6.x or 2.7.x if either of those will work.
edit: stock os still running fine, jicyw.
Edit #2: went ahead and rooted with that Chinese apk (forgot the name, but ya'll know the one), then installed rashr, thinking maybe my usb connection was to blame for the bad flash, but i have the same result flashing recovery img with rashr: claims success, but dead andy when trying to open recovery console. Boo!
monogwai said:
Hey there, everybody! Just got a 201 as a "parts only" tablet... turns out it just needed a trickle charge, so i'm off to the races. Wanted to put KatshMallow on here like I have on my tf300... Finally found out that in order to flash the hairybean stuff (so i can actually flash katshmallow) I needed twrp 2.5.0.0 first. So, upon discovering this, I downloaded the proper twrp image and went to flash the recovery via fastboot.
did 'fastboot devices' to make sure it saw the tablet... all good there.
did the 'flash' command, posted the [sending] and [receiving] steps, all said OK
did the 'adb reboot' command just to get things established and boot into the recovery...
but i don't get a recovery prompt, just a dead android with the 'x'. :/
now i don't even have a recovery module. I downloaded the proper package, but went and downloaded elsewhere just to be sure, and got the same result. I *was* going to ask if someone would post a nandroid from a tf201 that already had katshmallow running and try and establish myself that way, but again, no recovery at all. What do I do from here? anybody happen to know what the last twrp version for the 201 that works with JB 4.1.1? i can try to flash a 2.6.x or 2.7.x if either of those will work.
edit: stock os still running fine, jicyw.
Edit #2: went ahead and rooted with that Chinese apk (forgot the name, but ya'll know the one), then installed rashr, thinking maybe my usb connection was to blame for the bad flash, but i have the same result flashing recovery img with rashr: claims success, but dead andy when trying to open recovery console. Boo!
Click to expand...
Click to collapse
come on, peoples... i know someone out there must have some kind of advice. nobody ever responds to anything i post. ya'll are making me feel like i have the xda forums' equivalent of digital herpes. clean bill of health here, folks, I promise! :laugh:
wow, rough crowd. Can't help, sorry. Trying to solve a problem myself :<
Phil
Does the TF201 have it's bootloader unlocked?
NP
So, complete tutorial is here when tab is working : https://forum.xda-developers.com/tr...uide-tutorial-asus-transformer-prime-t3486237
Flashing TF201 is not like TF300.
It is why NVIDIA Download mode is used to backup files.
So, you talk of flashing an apk. How did you do if your tab is down ?
System working ? Download working ? Recovery working ?