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
Related
Hey guys,
apart from my Un-Bricking-Thread I wanted to start a Thread dealing with how to prevent a brick in the first place.
--- Already bricked your Prime? Read on here, maybe you can recover it ---
In the last days I learned quite a few things about the TFP, its CWM and how to work with it. I also hard bricked my Prime so I certainly know what I am talking about
Unfortunately ASUS didn't fully unlock our Bootloader. We still can't use NVFLASH for low level flashs.
This also means that we can't recover some things we could with NVFLASH access (like a broken bootloader).
So lets start with the things you better not do:
DON'T
Once you unlocked the prime and installed CWM, do NOT try to install a super blob from ASUS (that is a blob file from one of the 'full' updates from their site)
It seems that doing so totally bricks your Prime with no chance of recovery... (happened at least twice so far)
Don't flash kernels like you used to flash (with write_raw_image to /boot). This does not work on the Prime. More on how to do it later.
Don't rely on your newly created ROM to work, ALWAYS have a backup of a working ROM on your sdcard (or a zip of a working ROM)
Currently we can't mount the USB-Storage from inside CWM, so transferring files to the Prime while being in recovery is not as easy for many not so advanced users.
Always make sure you have all files you need before rebooting to recovery.
DO
Kernel flashing: There seem to be two methods on how to flash a new kernel. One is safer but needs a bit more work, and the other is rather unsafe but okay when you (or the ROM dev) know what needs to be done.
Flash your boot.img via fastboot. This is usually rather safe (as safe as fastboot can be) but needs you to have a working fastboot environment. Update: It seems kernel flashing via fastboot does not work at all. Fastboot doesn't give you an error but it doesn't update the kernel either...
Flash your kernel via the /staging partition. In order to use this method you first need to pack your boot.img into a blob file.
Then you need put the data from the blob file to the /staging partition.
Once you reboot the kernel gets automatically installed.
Please be aware that you can flash almost everything like this, even the bootloader.
So if you screw up packing the blob file, you could easily brick your Prime.
The advantage of this method is that the user doesn't need to do anything, but you really need to take care of what you are doing.
Also make sure that the /staging partition is ALWAYS unmounted before flashing anything to it. Otherwise this will result in a Brick 3.
Always make a backup of your current ROM before flashing anything else. As stated earlier, we currently have no access to the sdcard in recovery, so transferring files to Prime is not as easy in recovery mode.
So I hope I can find some more topics in the future, but for now that's it
Diamondback said:
DON'T
Once you unlocked the prime and installed CWM, do NOT try to install a super blob from ASUS (that is a blob file from one of the 'full' updates from their site) It seems that doing so totally bricks your Prime with no chance of recovery... (happened at least twice so far)
Click to expand...
Click to collapse
But but but how can I has update?! I want Update! RWAR!
Thanks, thanks, bump, and thanks again! Due to the current state of our device's development (especially with an early build of CWM), misinformation floating around, etc. this is invaluable! Now I know what "staging" is and what its use is. Well done - keep up the great work
Sent from my Transformer Prime TF201 using xda premium
mtotho said:
But but but how can I has update?! I want Update!
Click to expand...
Click to collapse
Use custom ROMs. We currently don't really know if it ALWAYS bricks your Prime. We just know that two updates bricked two primes
I think nobody wants to try
Diamondback said:
Use custom ROMs. We currently don't really know if it ALWAYS bricks your Prime. We just know that two updated bricked two primes
I think nobody wants to try
Click to expand...
Click to collapse
Yea I am just kidding. I knoweth better plus I like custom roms (and I am very flash happy)
I won't be happy until we get some sort of nightly rom that I can flash daily
thanks diamondback this prob saved me lots of time and the almost $700 i have in my device+dock
Sent from my Transformer Prime TF201 using xda premium
Will be possible to use NVFLASH anytime? Have we to look for a dev or is Asus that must upgrade its apk?
Thanks Diamondback for making this. This needs to become a sticky immediately. To many people are blindly unlocking then get mad when they find out they can't do OTA updates. Or people installing CMW without even unlocking and blaming others issues on that when they found out device should've been unlocked first..lmfao
Unlock tool release=operation sabotage for those who don't know any better or ignorant or lazy to research first. QnA section had several people with semi or hard bricked primes. Primes are dying off left n right..lol
Diamondback said:
Unfortunately ASUS didn't fully unlock our Bootloader.
Click to expand...
Click to collapse
So you download their software, run it to completely void your warranty (they've already denied support on one unrelated hardware issues that I know of), and you STILL don't have full access?
WTF!?!?!!?
Not being able to use NVFlash has completely put me off, for me NVFlash was the ultimate aim for unlocking the bootloader ... pretty **** !
(unhappy smiley)
Diamondback, I'm so sorry to hear that you bricked your Prime! Any luck getting unbricked yet?
Thank you so much for posting this invaluable guide. You are generous beyond words, to go to this effort to save other users from the lessons you had to learn the hard way. There aren't enough thanks in the world.
If we can at least ATM use fastboot that's a good thing. A good thing for fastboot is you can first do-
fastboot boot boot.img and it will boot the kernel the first time, basically so you can test it before it writes the .img
then you can fastboot flash boot.img to write the image. It'll work for now, sucks that any non-dev who just wants to flash a kernel has to set up fastboot
Edit- girluvsdroid- just saw you were in wilmington- me too.
This was very helpful.
BUMP!
Reading is fundamental! Lol I don't know how many times I've just glanced over post, just to get the newest firmware, and kernals, just to end up on the verg of a bricked device. Thanks.
What ?
So If I UnlockBootLoader
I cant OTA Anymore ? Seriously
AndyMclamb said:
What ?
So If I UnlockBootLoader
I cant OTA Anymore ? Seriously
Click to expand...
Click to collapse
But why would you unlock if you were not going to install custom roms (that have the latest OTA built in) anyway?
Diamondback said:
Flash your boot.img via fastboot. This is usually rather safe (as safe as fastboot can be) but needs you to have a working fastboot environment.
Click to expand...
Click to collapse
Hmm.. Does not seem to work for me. Built a kernel, switched in fastboot mode. Then:
Code:
$ sudo ./fastboot -i 0x0b05 boot zImage blob.LNX-ramdisk.cpio.gz
creating boot image...
creating boot image - 4214784 bytes
downloading 'boot.img'...
OKAY [ 0.748s]
booting...
FAILED (remote: ()
finished. total time: 0.749s
Prime displays: Failed to process command boot error(0x120000)
Any advice?
saturn_de said:
Hmm.. Does not seem to work for me. Built a kernel, switched in fastboot mode. Then:
Code:
$ sudo ./fastboot -i 0x0b05 boot zImage blob.LNX-ramdisk.cpio.gz
creating boot image...
creating boot image - 4214784 bytes
downloading 'boot.img'...
OKAY [ 0.748s]
booting...
FAILED (remote: ()
finished. total time: 0.749s
Prime displays: Failed to process command boot error(0x120000)
Any advice?
Click to expand...
Click to collapse
Yes. fastboot boot does not work at all.And we also found out that kernel flashing via fastboot does not work either.
You have to flash your kernels via a custom made blob ;-)
Gesendet von meinem Desire HD mit Tapatalk
Prime Stuck in CWM boot loop hell.
I have a Prime that is stuck in a CWM Recovery boot loop.
Brick 1a
All thanks (sincerely) to Viperboy and his ViperMOD PrimeTime 4.5, I had my Prime rooted, boot loader unlocked and loaded with ClockworkMOD Recovery 5.5.0.4.
I used CWM to create a backup, wipe the data/factory, cache partition and Dalvik cache, rebooted the system (from CWM menu) just to verify that the unit was really wiped back to setup, powered down the unit, rebooted into CWM Recovery (using Power while holding Vol.Down, wait for small/white text, Vol.Up) and Restored using the previously created Backup.
I rebooted Android from CWM menu and my Prime was restored.
Everything was great, but not for long.
The next time that I booted into CWM recovery I selected “Reboot System Now”.
It went dark, displayed the ASUS splash screen, went dark and went back into CWM.
I am stuck in that loop.
I have tried all the suggested fixes I can find but all methods are useless because:
1. I can’t acquire an ADB connection because Windows doesn’t identify the bricked Prime correctly and won’t install the USB drivers. Device Manager sees “Full Android as Emulator”.
2. I can’t boot into the boot loader to use Fastboot because I never see the option to choose it. It boots or reboots directly into CWM after “Booting Recovery Kernel Image”, ever while holding the Vol.Down button.
I have repeatedly tried installing and uninstalling the drivers by installing and uninstalling the Asus Sync and Asus Android USB Drivers. I have repeatedly tried to install the drivers via the Device Manager. No good. I’ve installed and uninstalled Android SDK Tools repeatedly.
Is there a way out of this? I hope I'm not efed.
Thank you in advance for any help.
Temporalmind said:
I have a Prime that is stuck in a CWM Recovery boot loop.
Brick 1a
[..]
I apologize for the length of this post. I hope I’m not efed.
Click to expand...
Click to collapse
Please try to manually installing these drivers here
http://forum.xda-developers.com/showthread.php?t=1426502
Adb should be working afterwards
Universal Naked Driver works great!
Ok, you saved me and my precious.
Your drivers were exactly what I needed.
After installing them in Device manager I was able to achieve a “ASUS Android Composite ADB Interface” connection.
Following the “How to Unbrick your Transformer Prime (or not)”, Option 1a and restoring I’m up and running.
Thank you!
Then, I deliberately caused the boot looping condition again to see if I could figure out how I got there.
There is an app that I think comes preinstalled on the Prime called ”Transformer Recovery Boot”. The icon is labeled "Recovery". This is the app that took me into the Brick 1a the first time and I duplicated it the next time I used it.
Then I was able to ADB my way back to civilization, again.
Thought I’d pass that on incase it helps to determine why the unlocked Prime seems to be so susceptible to bricking.
Again, Thank You!
My TF201 is unlocked and I've manually updated it to the JB build from Asus. After running this I noticed that I've lost root and my recovery is broken. Is there a good method to go about fixing this yet?
MeepZero said:
My TF201 is unlocked and I've manually updated it to the JB build from Asus. After running this I noticed that I've lost root and my recovery is broken. Is there a good method to go about fixing this yet?
Click to expand...
Click to collapse
Few months ago I flashed AndroWook to my Prime. I didn't have access to a computer and cable, but I had coveted to have JB so I decided to skip the steps with NVFlash, because I did not read thoroughly the instruction and I thought that the NVFlash is a plain backup but in modern way
The true is that I lost my unlocket bootloader, because JB installation fix bootloader and lock it again
Official ICS bootloader unlocker not works with devices JB based and ASUS haven't updated this for working with JB :/
Today I know why the NVFlash was so much important. So sad, but really story... You have the same problem. I'm sorry...
gucman said:
Few months ago I flashed AndroWook to my Prime. I didn't have access to a computer and cable, but I had coveted to have JB so I decided to skip the steps with NVFlash, because I did not read thoroughly the instruction and I thought that the NVFlash is a plain backup but in modern way
The true is that I lost my unlocket bootloader, because JB installation fix bootloader and lock it again
Official ICS bootloader unlocker not works with devices JB based and ASUS haven't updated this for working with JB :/
Today I know why the NVFlash was so much important. So sad, but really story... You have the same problem. I'm sorry...
Click to expand...
Click to collapse
I have no idea what you did but you cannot relock the bootloader once you have unlocked. The only way this ever happens is if you return it for RMA and they swtich out the motherboard.
Just because it might not say unlocked bootloader in the top left anymore does not mean it has relocked.
If you have installed Androwook rom at some point and have not sent it in for RMA at any time since your device is still unlocked mate.
If you are talking about losing recovery that happens when you upgrade the bootloader and then have to flash a new recovery thru fastboot that matches the bootlader you are now on.
Maybe I should rephrase my question. If my recovery is broken, and I don't have root, is it possible to either fix recovery OR repair my root access?
MeepZero said:
Maybe I should rephrase my question. If my recovery is broken, and I don't have root, is it possible to either fix recovery OR repair my root access?
Click to expand...
Click to collapse
Yes there is mate..
Please make sure that you are definitely on the JB bootloader before proceeding. You can check this by looking at the tegra logo when you switch the machine on. If it is down the bottom right it is jellybean if it is bottom center it is ICS.
Once you are sure you are on the JB bootloader go to this post http://forum.xda-developers.com/showpost.php?p=26595675&postcount=2 and follow the Install Instructions for TWRP.
@flumpster:
I have the string "device is unlocked" in top left corner and it's the cause I didn't send it to ASUS for RMA.
General problem is that i can't get recovery and fastboot.
gucman said:
@flumpster:
I have the string "device is unlocked" in top left corner and it's the cause I didn't send it to ASUS for RMA.
General problem is that i can't get recovery and fastboot.
Click to expand...
Click to collapse
First thing you need to do is get yourself into fastboot mode.. Power off the device and then hold the volume down and power button the same time for 10 seconds until you get a load of icons on your screen. Press volume down to go over to the USB icon ( fastboot ) and then press volume up.
At this point it will say starting fastboot protocol and freeze. This is normal. You now have to look in your device manager to see if you have the drivers installed. If you have any devices in there with exclamation marks by them then install naked drivers from the dev thread.
Once that is done you can do the same as what I just said to the guy above to get a new recovery on there.. Make sure you are on JB bootloader the same as I said to him tho.
flumpster said:
Yes there is mate..
Please make sure that you are definitely on the JB bootloader before proceeding. You can check this by looking at the tegra logo when you switch the machine on. If it is down the bottom right it is jellybean if it is bottom center it is ICS.
Once you are sure you are on the JB bootloader go to this post http://forum.xda-developers.com/showpost.php?p=26595675&postcount=2 and follow the Install Instructions for TWRP.
Click to expand...
Click to collapse
It looks like I'm on the JB bootloader then. I'll take a look at this later tonight and see if I can get this thing fixed
I'm 100% sure that I'm on the JB bootloader. I know how to get fastboot But it stucks on "Starting Fastboot USB download protocol". And i could waiting to over and obver. Probably to the next end of world
I reinstalled the naked drivers few times before I noticed that I should disable driver signature enforcement, because I'm on Win 8. I did these and actually I have installed it correctly. I bought the new cable recently. I thought that it's whats wrong with my wire. No success...
But I never saw that topic about AndroWook TWRP for JB earlier and I am taking to work! I hope this help
gucman said:
I'm 100% sure that I'm on the JB bootloader. I know how to get fastboot But it stucks on "Starting Fastboot USB download protocol". And i could waiting to over and obver. Probably to the next end of world
I reinstalled the naked drivers few times before I noticed that I should disable driver signature enforcement, because I'm on Win 8. I did these and actually I have installed it correctly. I bought the new cable recently. I thought that it's whats wrong with my wire. No success...
But I never saw that topic about AndroWook TWRP for JB earlier and I am taking to work! I hope this help
Click to expand...
Click to collapse
The starting fastboot protocol and not going anywhere is completely normal mate. That is how fastboot works. You could wait all day and it will not change.
Your problem is more windows 8 with its driver verification issues. I don't have windows 8 but if you get really stuck and can't get them installed I know that WhyCali in the team has it installed and he can help you.
You are definately not locked tho
It works!
You're my god bro :highfive:
I watched the .bat file from your package and I deduced that I should have to use fastboot with "-i 0x0B05" flag.
Thank You again
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.
Hey guys, if this is in the wrong section feel free to move it. For whatever reason there still isn't a sub-section for the Pantech Flex...
Anyways, long story short, I had some issues with the stock setup and so I used the built-in Reset option under Settings -> Backup & Reset..
This resulted in a soft-brick of sorts, I can't get past the AT&T logo screen, and since it had just been reset, USB Debugging is NOT enabled.. *sigh*
So, I'm trying to use Fastboot to flash/boot CWM so I can recover from this little predicament (I hadn't successfully flashed CWM yet).. but on 99% of Fastboot commands, I get the following error:
Code:
C:\> fastboot flash recovery cwm.img
sending 'recovery' (8076 KB)...
OKAY [ 0.608s]
writing 'recovery'...
FAILED (remote: Not Support !!)
finished. total time: 0.608s
Which leads me to believe I need to unlock some things.. and upon looking around (the VERY limited information for this device...) I found a few suggestions of using "fastboot oem unlock", however it gives the same "FAILED (remote: Not Support !!)" command..
Anyone know anything that may help? Thanks guys!
You probably should be able to get out of trouble with this thread: http://forum.xda-developers.com/showthread.php?t=2472487
Ur lucky its soft brick!
Mine got super hard bricked.....
There are many ways to solve soft brick....
Just go cwm and flash a right rom for u.....
If u dont have cwm feel free to search in the forum......
Sent from my iPad mini using Tapatalk HD
Thy Boss said:
Ur lucky its soft brick!
Mine got super hard bricked.....
There are many ways to solve soft brick....
Just go cwm and flash a right rom for u.....
If u dont have cwm feel free to search in the forum......
Sent from my iPad mini using Tapatalk HD
Click to expand...
Click to collapse
OP stated that they have not had any luck getting CWM to work.
And to OP - sorry! I just double checked the instructions I linked to, but realized you need adb working for the method if you are already on JB. Please let me know if you are ICS or JB and I'll see if I can't give you better direction...
es0tericcha0s said:
OP stated that they have not had any luck getting CWM to work.
And to OP - sorry! I just double checked the instructions I linked to, but realized you need adb working for the method if you are already on JB. Please let me know if you are ICS or JB and I'll see if I can't give you better direction...
Click to expand...
Click to collapse
Sadly yes, I'm already on JB.. My apologies for the slow reply, didn't get notifications like I thought I had set.
Also, I've gotten it to boot up, but the launcher seems to have been erased and so I get a black screen. Status bar still appears but I can't pull it down to access settings. Navigation buttons respond to input but are still useless without a launcher.
On another note, I've tried flashing a few zips via stock recovery's adb sideload mode, everything from cwm to an entire (stock and otherwise) rom, even just a launcher since that should be all I need, but every time I tried to sideload, it would get to 49% and suddenly "Installation Aborted!" Not sure why that doesn't work... *sigh*
FalloutState said:
Sadly yes, I'm already on JB.. My apologies for the slow reply, didn't get notifications like I thought I had set.
Also, I've gotten it to boot up, but the launcher seems to have been erased and so I get a black screen. Status bar still appears but I can't pull it down to access settings. Navigation buttons respond to input but are still useless without a launcher.
On another note, I've tried flashing a few zips via stock recovery's adb sideload mode, everything from cwm to an entire (stock and otherwise) rom, even just a launcher since that should be all I need, but every time I tried to sideload, it would get to 49% and suddenly "Installation Aborted!" Not sure why that doesn't work... *sigh*
Click to expand...
Click to collapse
Got yourself a tricky one here.
http://forum.xda-developers.com/showpost.php?p=37320624&postcount=88
Use that modded stock recovery to have proper adb access in recovery, and do: adb install launcher.apk (non /system version with that command, and launcher.apk can be named anythingyouwant.apk)
I kind of think that isn't going to be enough though.
If that doesn't work, it might be worth trying to fastboot boot a version of CWM, have the rom you need on the SD card and use that to flash. CWM won't stay, but if you boot and all is well, that can be re-added easily. Let's get the easy option out of the way first though.
es0tericcha0s said:
Got yourself a tricky one here.
http://forum.xda-developers.com/showpost.php?p=37320624&postcount=88
Use that modded stock recovery to have proper adb access in recovery, and do: adb install launcher.apk (non /system version with that command, and launcher.apk can be named anythingyouwant.apk)
I kind of think that isn't going to be enough though.
If that doesn't work, it might be worth trying to fastboot boot a version of CWM, have the rom you need on the SD card and use that to flash. CWM won't stay, but if you boot and all is well, that can be re-added easily. Let's get the easy option out of the way first though.
Click to expand...
Click to collapse
I saw that first link while searching for solutions, however that dropbox link is dead. @timmythanoob, do you still have this file available?
As far as your second idea of using "fastboot boot xxx.img" or whatever have you, the issue with that is that the "boot" command is one of the Fastboot commands I mentioned in the OP that gives the "Remote: Not Support!!" error, which from what I can find is an issue with "aboot" in the JB update...
If I can get ahold of timmythanoob's recovery image with ADB access, then even if adb install'ing a launcher doesn't work, I could still have WAY more options to work with and I'm confident that with full ADB access I could restore the device to working order... IF someone can get me that recovery w/ adb :|
EDIT: Actually I don't think even timmythanoob's recovery image will work since I don't have access to the "fastboot boot" command... I really think my only options are PDL mode and sideloading a zip in recovery. PDL won't work because of the lack of PDL's for our device (and Pantech refusing to give me one), and sideloading a zip in recovery, for whatever reason, always seems to fail with an Installation Aborted... -_-
Anyone have any ideas?
Sorry, a lot of the info for this phone is mixed and matched between instructions for ICS and JB. So, basically, it seems you are boned. Only way to properly get fastboot to work would be to downgrade the aboot, which you can't do because you have to be rooted and booted while on JB to do so. Same thing with CWM on JB. Have to be rooted and booted. :/ Sorry man.
Last resort I can see would be trying to flash the JB OTA zip via stock recovery:
http://forum.xda-developers.com/showpost.php?p=46025559&postcount=164
But even that guy who obviously knows these devices a bit better than we do says it probably wouldn't work for someone in your situation a bit later in that thread:
http://forum.xda-developers.com/showpost.php?p=46209691&postcount=174
But that's pretty much your last option at this stage other than sending it into Pantech so they can use their firmware flashing tool since they won't share it with anyone.
I tried that JB OTA, didn't work. 49% and then Installation Aborted. I was going to send it to Pantech but I imagine they won't help since thanks to my recovery attempts, in the bootloader screen it shows as being rooted and tampered with.
Sucks man. One of the downsides of their being so many different devices out there. Only so many developers to go around and that combined with little to no support from Pantech... :/
I'm going to claim OP resurrection rights and bring this back up in hopes that someone can help. Anyone know anything?
Sent from my YP-G1 using Tapatalk
First off, I am learning everything on the fly, so keep this in mind if my question sounds stupid. It's my wife's Prime and it just wouldn't boot one day.The best I can tell it had JB 4.1.1 and it is locked. I can access the bootloader with 4 options. There are no longer any recovery options on the TF201 itself. I am trying to flash a recovery from fastboot, but when it goes to write I get a failed message-invalid state error even though the blue bar goes to full on the tablet. I assume that the reason I am unable to flash the tablet is because it is locked and at this point there is no way to unlock it. I just need someone to confirm my assumption that the device is permanently bricked so I can stop the hours of research and return to a normal life. Thanks for any help.
ghiotom said:
First off, I am learning everything on the fly, so keep this in mind if my question sounds stupid. It's my wife's Prime and it just wouldn't boot one day.The best I can tell it had JB 4.1.1 and it is locked. I can access the bootloader with 4 options. There are no longer any recovery options on the TF201 itself. I am trying to flash a recovery from fastboot, but when it goes to write I get a failed message-invalid state error even though the blue bar goes to full on the tablet. I assume that the reason I am unable to flash the tablet is because it is locked and at this point there is no way to unlock it. I just need someone to confirm my assumption that the device is permanently bricked so I can stop the hours of research and return to a normal life. Thanks for any help.
Click to expand...
Click to collapse
No not possible with out unlocking - you can flash the stock asus blob which is signed and it will update your recovery back to stock but that is it.
I'm not sure what you're saying. You said it can't be flashed if the bootloader is locked, then you say I can flash a stock Asus blob.
ghiotom said:
I'm not sure what you're saying. You said it can't be flashed if the bootloader is locked, then you say I can flash a stock Asus blob.
Click to expand...
Click to collapse
Yes exactly that. You can't flash anything customised on an locked boot loader.
I didn't mention that I also tried to install the stock Asus firmware from their website using both the Fastboot method as well as a microSD card, but neither method worked. You're saying that flashing the stock firmware should work.The fact that it didn't, leads me to believe that there is probably something wrong on a hardware level and a motherboard replacement is the only option.
ghiotom said:
I didn't mention that I also tried to install the stock Asus firmware from their website using both the Fastboot method as well as a microSD card, but neither method worked. You're saying that flashing the stock firmware should work.The fact that it didn't, leads me to believe that there is probably something wrong on a hardware level and a motherboard replacement is the only option.
Click to expand...
Click to collapse
Not sure you can fastboot flash it no but you can certainly unzip it, rename it to whatever they said to and drop it on the microsd, go to bootloader, hit rck and it should flash it. You can only do this with Asus signed files.