I will vouch for getting a new cable too, Asus must give out some shody cables, mine was hardy used.
Sent from my Nexus 7 using XDA Premium HD app
[HOW-TO] Unbrick your Transformer Prime (or not)
- Thread starter Diamondback
- Start date
-
- Tags
- development
I will vouch for getting a new cable too, Asus must give out some shody cables, mine was hardy used.
Sent from my Nexus 7 using XDA Premium HD app
You're ok thanks mate. I don't take donations. Buy yourself a beer out of it and have a drink on me
I'm just glad you got it all sorted. I've seen the same problem with faulty cables many a time and it confused people because it does show up as an unknown device but it just wont do anything.
so is there a way to get us going again from the ASUS logo with the DEVICE IS UNLOCKED at the upper right side yet ? i already tried all i could think of but cant get out of that any help would be appreciated thx................
I'm also stuck at this screen. I neither have fastboot nor ADB. Can't go into the stock recovery no matter what. Now I left it on to drain the batt first and see what I can do.
Any ideas? :crying:
Only APX Mode without NVFlash Blob files - anything possible now?
Dear all members,
Last night while trying to install CWM over TWRP, I messed by the bootloader and now i am left with only APX mode. I did not get the blobs also using the fastboot. Is there any possibility now to get this sorted out in the near future when ASUS decides to provide us with some tools to unlock NVFlash?
Thanks.
Dear all members,
Last night while trying to install CWM over TWRP, I messed by the bootloader and now i am left with only APX mode. I did not get the blobs also using the fastboot. Is there any possibility now to get this sorted out in the near future when ASUS decides to provide us with some tools to unlock NVFlash?
Thanks.
all adb that I find state out of date when I cmd anything to it. got sdk with same results. my prime say error in bootloader. it will fastboot connect, how do I push a bootloader to the prime.
thank you but its not enugt we lookind other way
my EKS partition is dead boot dont continue here how to debug tf201
http://xdaforums.com/showthread.php?t=2178110
my EKS partition is dead boot dont continue here how to debug tf201
http://xdaforums.com/showthread.php?t=2178110
Last edited:
Oops
all adb that I find state out of date when I cmd anything to it. got sdk with same results. my prime say error in bootloader. it will fastboot connect, how do I push a bootloader to the prime.
all adb that I find state out of date when I cmd anything to it. got sdk with same results. my prime say error in bootloader. it will fastboot connect, how do I push a bootloader to the prime.
Try holding the Power button and the Volume Down. When the 1st splash screen comes up, release the Power butten. Then hit the Volume Up.
This should place your Prime in recovery mode -
follow the instructions for using ADB to copy a boot image over to /sdcard, then you just do an "update" from sdcard
Last edited:
Option 1a?
It appears that I have Option 1a. Boots straight to Recovery but then TWRP asks for a password. It appears that TWRP can't mount anything and I can't access any ROMs or backups. I can connect with adb; says device id is 0123456789ABCDEF. When I try to go to adb shell, command shows ~ # <-[6n then exits. I can't enter any commands in adb shell before it exits after 10-15 seconds, back to command prompt.
This all happened when I wanted to flash the latest NRG ROM after being on CM10.1 20130308 UNOFFICIAL tf201. Aroma installer for NRG said I first needed to flash jb 4.2.1 bootloader, and when I tried to do this, was left with this problem. I have seen posts about using adb shell to change to ext4 but I have the same problem as indicated above--shows ~ # <-[6n and then exits before I can enter any commands.
Any suggestions?
It appears that I have Option 1a. Boots straight to Recovery but then TWRP asks for a password. It appears that TWRP can't mount anything and I can't access any ROMs or backups. I can connect with adb; says device id is 0123456789ABCDEF. When I try to go to adb shell, command shows ~ # <-[6n then exits. I can't enter any commands in adb shell before it exits after 10-15 seconds, back to command prompt.
This all happened when I wanted to flash the latest NRG ROM after being on CM10.1 20130308 UNOFFICIAL tf201. Aroma installer for NRG said I first needed to flash jb 4.2.1 bootloader, and when I tried to do this, was left with this problem. I have seen posts about using adb shell to change to ext4 but I have the same problem as indicated above--shows ~ # <-[6n and then exits before I can enter any commands.
Any suggestions?
AW: [HOW-TO] Unbrick your Transformer Prime (or not)
Same Problem here.. Is there a Chance?
Gesendet von meinem Nexus 4 mit Tapatalk 2
Same Problem here.. Is there a Chance?
Gesendet von meinem Nexus 4 mit Tapatalk 2
Same here
0123456789ABCDEF Recovery
for the name of the device and several directories unmountable then unwipable ...
and get stuck on a recovery that is not able to help me.
0123456789ABCDEF Recovery
for the name of the device and several directories unmountable then unwipable ...
and get stuck on a recovery that is not able to help me.
Glad to see I am not the only one... this happened when installing NRG as well.
Any suggestions for someone who tried to install TWRP over cwm?
I am stuck at the asus logo, I've tried a wipe data too and that didn't work
I am stuck at the asus logo, I've tried a wipe data too and that didn't work
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
138Hey guys,
I just wanted to put some information together on how to recover your bricked Prime (if possible).
DISCLAIMER
I am in no way responsible for what you do with your Prime, even when you are following these (my) instructions.
There is always the risk of making it worse and this risk is completely down to you!!!
Currently we know 4 states of bricked Primes whereas 3 are more or less widespread.
- Brick 1a: You unlocked your Prime with ASUS' tool, did some stuff to it (like flashing a custom ROM) and now it always boots into recovery instead of your ROM.
You can't select to boot to fastboot or anything else. No matter what you do it's always the recovery. (happening to many users)
-> Please go to Option 1a
- Brick 1b: You unlocked your Prime with ASUS' tool, did some stuff to it (like flashing a custom ROM) and now once you want to boot your new ROM it shows you the bootanimation but suddenly tells you something about an "unsuccessful encryption" (it's a real android screen, with a touch button etc.)
Once you hit the "Reset" button it restarts but you can't boot the ROM anymore, you are now caught in a CWM loop (much like Brick 1a)
-> Please go to Option 1b
- Brick 2: When booting up your Prime hangs at the splashscreen (the screen with "EeePad" in the middle) and tells you something about an "unrecoverable bootloader error" (happened so far to at least 4 users)
-> Please go to Option 2
- Brick 3: (After messing around with your Prime in recovery it won't boot any ROM anymore, you can however still access fastboot and the recovery)
Update: This particular brick happens due to a bad kernel flash. If you are flashing kernels via the ASUS /staging method, make sure /staging is unmounted before flashing stuff to it, otherwise it WILL faill and brick.
Update 2: It seems we can't use the old fix for this brick anymore. Sometimes it does more bad than good.
->Please go to Option 3
Option 1a
Don't be afraid, your Prime should be recoverable. This is the good news. The bad news is, that you need quite some knowledge of ADB.
To recover your Prime (most likely) you need the following:
- A working ADB setup (please google that if you don't have it, "tutorial setup adb" or something like that should do the trick)
- The USB-Cable to connect the Prime to your PC
- A few minutes time
Now do the following:
- Make sure your Prime is in Recovery mode (CWM)
- Open a cmd line on your pc
- Type: "adb shell"
- You should see a "#" now
- Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
- Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
- Exit the shell and reboot your Prime via CWM
- It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
Option 1b
Good news, this brick should be no problem.
Basically you need to first do Option 1a, but don't reboot the Prime just yet.
- After executing the dd commands, you need to reboot your Prime to the bootloader menu and NOT the ROM itself.
- To do this you need to reboot your device while holding down the Volume_Down key.
- Once the white text in the top left corner appears release the buttons.
- Now don't press anything until you can see a menu with 3 icons, an Android symbol, an USB symbol and a Wipe Data symbol.
- Select the Wipe Data icon with pressing Volume_Down twice. Now press Volume_Up twice to reset the device to factory state.
- WARNING: OF COURSE THIS WILL DELETE ALL YOUR DATA!!!! EVEN THE INTERNAL MEMORY AKA SDCARD!!! CURRENTLY I DON'T KNOW ANY OTHER WAY TO RECOVER FROM THIS BRICK!!!
- After the wipe is done, you should be able to flash a new ROM or boot the existing ROM
Option 2
Sorry, but your Prime is most likely hard bricked.
This can happen if you try to apply a stock blob file after you installed CWM. There is currently no way to recover from this.
Option 3
If you are in this situation (Prime doesn't boot but you can access both recovery and fastboot) please go to #asus-transformer on freenode and ask for help there. We currently don't know if you can recover from this state.
Do not, I repeat, do not try to flash a stock ASUS ROM/blob file.
Doing this you will most likely hard brick your Prime.
We now found a way to un-brick this one too
This one is a bit more risky, so make sure you follow all instructions with a bit of extra care.
Update: It seems the old method for this brick could make things even worse on some Primes.
On some primes this can be easily fixed, however putting this in a guide could do more harm than good.
Troubleshooting
- Problems getting ADB to work in recovery mode? Only seeing something like "Full Android on Emulator" in the device manager instead of your tablet?
Well I have a posible fix for you: Got to this thread and download the drivers. Then override the drivers for the Emulator device manually with the new ones. ADB should work now
--- Read here how to prevent future bricks and other common problems ---
Bits & pieces
You might want to have a look here for a possible solution for some bootloader errors (It's from a TF300):
http://xdaforums.com/showpost.php?p=44244313&postcount=12
Credits:
thx to kmdm for his solution on Brick 1a and Brick 36
Holly Sweet Baby Jesus!!!!!
Thank God!!! *Breaths sigh of relief*
Problem/Issue:
- Was on AOKP Milestone 5.
- Installed TWRP Recovery via fastboot (over CWM).
- Made Backup.
- Installed CM9, played with it for a day or so.
- Wanted to go back to AOKP... Restored TWRP Backup
- Upon Reboot, stuck at boot screen (EEE Pad Screen).
- No recovery, only options were wipe & fastboot
- Flashing either version of recovery yielded no results... still stuck.
Solution:
- Download AKOP Rom zip again to computer. (or which ever particular rom you restored).
- boot into fastboot
- flash recovery via "fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.1.8-tf201.img" <--- CWM Touch Version
- Extract boot.blob from Rom .zip
- flash boot.blob via "fastboot -i 0x0b05 flash boot boot.blob"
- reboot via "fastboot -i 0x0b05 reboot"
BOOTING UP & Recovery Access!!!3
Try instaling these drivers here manually please
http://xdaforums.com/showthread.php?t=1426502
Adb should work fine afterwards2Okay I added a 4th brick to the list. It's a variant of the first Brick and it is recoverable2 - Brick 1a: You unlocked your Prime with ASUS' tool, did some stuff to it (like flashing a custom ROM) and now it always boots into recovery instead of your ROM.
