[Q] Bricked TF101 - Eee Pad Transformer Q&A, Help & Troubleshooting

Hi,
It would seem that I have inadvertantly bricked my TF101 during the process of trying to root, and install TWRP in order to put on KatKiss. I used Baidu Root to root which appeared to have completed successfully and then tried using CWM (I now know about the incompatibility issues concerning CWM and the TF101) to install the rom. Now, in its current state, the TF101 does not turn on at all. I have tried many guides but the problem I am having which I attribute to the many unsuccessful attempts is that for example, using EasyFlasher, the APX device would disconnect itself. I have tried to restore the device by reflashing the stock rom (WW) using both SBKv1 (wheelie crashes during the process every time, and then the device would disconnect), and SBKv2 (after clicking OK on the APX prompt box, the device disconnects). I have also tried using nvflash and Prime without any success. My device is a B70, and was running Android 3.2 (Honeycomb?).
Please let me know if there is any more clarification or information required that I have missed out on.
Thank you all in advanced for any help or suggestions,
- Tone

Related

[Q] bricked transformer - help please

Hi, I know there are many threads with this particular problem, I did my research and I find this kinda strange (Iam also desperate...)
Long story:
Ive been swapping between official ROM and customs like a madman and Ive always rooted using this method (downgrade, then vipermod), but this time I accidentaly tried to enter recovery at first boot and since then Iam stucked at "EEE Pad" logo with half full progress bar.
tl;dr summary:
no adb
C10 transformer, sbkv2
no recovery
on boot w/ volume down it says 8.6.6 - the one Ive downgraded to; It also says "checking for ota recovery"
sucessful APX mode connect, universal drivers
When using standard nvflash ROM the process is terminated with "write error" message and disconnects the transformer - sbk2 problem, so Ive tried EasyFlasher which utilizes Wheelie for B70+ devices and the exact same thing happens (well, console and GUI says that everything is OK, but when the nvflash is getting ready the device gets disconnected too). There are many people saying in the thread that Wheelie helped them with basically the same problem...
Now Iam downloading linux to try Wheelie manually.
Any ideas how to fix this or I can pretty much toss my transformer out of the window?
Thanks for replies.
nevermind, Iam an idiot - did not realised that I actually have TF101G so sbkv3 and no nvflash for me
so, do you know if there is any "nvlash-for-sbkv3" project in progress?

ASUS TF300TG not detect USB Cable for data but charge is ok

hi 2 all
ASUS TF300TG stick in asus logo after rooting and not detect USB Cable for data by computer and just charge is ok.
no fastboot no recovery...no Power+VolDown...plz help to solve this
pc_helper said:
hi 2 all
ASUS TF300TG stick in asus logo after rooting and not detect USB Cable for data by computer and just charge is ok.
no fastboot no recovery...no Power+VolDown...plz help to solve this
Click to expand...
Click to collapse
It will be good to tell more about your root.
How do you root ?
Which guide have you use ?
Which version of your TG ? before the root?
etc, more infos will be good for a good help
ASUS tf300t fix root permissions error
this was the best place i could think to post this.
I can see that you are somewhat versed with my series of tablet so im hoping maybe you can help me.
I previously had rooted my device and did so pretty easily (fastboot flash CWM-Touch, root-signed.zip) yadda yadda.
Then I deciced i wanted to install CM 9.1(stable)[or so it said]
Downloaded the build onto sd card, wiped my caches and data and all that...CWM install .zip,(good), reboot, stuck at inital cold-boot screen with ASUS and TEGRA powered by NVIDIA logos.
Found a solution to that problem @ transformerforums.com- did a fastboot: flash system blob w/original JB OTA build (took forever, i even thought it froze my computer) i had to download from the asus support site and got the tablet up and running again....BUT, and this is the kicker, no root. I tried using CWM-touch to reinstall root-signed.zip, successful. Hit reboot and CWM popped up with your user su binary may be damaged. Repair? yes. Reboots fine, but then i tried to access a program that needed root, ERROR! IS DEVICE ROOTED? pops up... I checked my /system/xbin/su. still there but couldnt do anything with it...
ANY SUGGESTIONS TO HELP WOULD BE AWESOME. This isn't the first device ive cracked so im not exactly new but dont know enough about this to try fix anymore than what ive done and ive searched the forums over for the past four days and cant find anyone or anything that is similar to whatim experiencing...
please help.
Sincerely, SIK
P.S.-DONT USE CWM-TOUCH V6.0.3 ON THIS TABLET. YOU CANT MAKE RECOVERIES!!! IT SAYS IT DOES BUT DOESNT BUILD ANYTHING!
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
TF300TG
philos64 said:
It will be good to tell more about your root.
How do you root ?
Which guide have you use ?
Which version of your TG ? before the root?
etc, more infos will be good for a good help
Click to expand...
Click to collapse
i dont know about root version,just i know that user attempt to root this device but not success,i am good about installing Official rom or custom rom on asus tf300tg but just problem is USB for data mode not define by cumputer & not working for fastboot & just work for charging,plz help

[Q] TF300t bricked? Bootloop, no adb, no fastboot but APX accesible

Hi everyone, first post here, but I've been reading this forum for some time now.
I've got an asus transformer pad tf300t 3 days ago. Last night, I tried to install cyanogenmod10, I unlocked the device, and installed clockworkmod, everything was fine until I accidentaly entered recovery mode and wipe all data, now the tablet only shows the asus logo and enteres in to a bootloop (I think). I can't enter recovery mode, ADB doesn't recognize it, fastboot neither and I can't even turn it off. I can't enter recovery, it just shows me the asus logo again.
HOWEVER, I waited until the battery drained, connected the usb cable to the tablet (not in the computer) pressed + volume button and without releasing it, connected to pc. Now the computer detects new hardware. I already installed the driver and it says "ASUS TRANSFORMER PRIME APX INTERFACE". Now, i'm not sure if it's the correct driver, but according to hardware administrator, it works fine.
Now, the real cuestion: Is there anything I can do from apx mode to save my tablet? A new bootloader maybe??
Thanks everyone
PS: Sorry for the bad english, It's not my language
from the loop,If you hold the power button for 10s when reboot and immediatly press the volume down button, what you have asus loop or the screen with the 3 icons (RCK ecc) ?
Claudisimo said:
Hi everyone, first post here, but I've been reading this forum for some time now.
I've got an asus transformer pad tf300t 3 days ago. Last night, I tried to install cyanogenmod10, I unlocked the device, and installed clockworkmod, everything was fine until I accidentaly entered recovery mode and wipe all data, now the tablet only shows the asus logo and enteres in to a bootloop (I think). I can't enter recovery mode, ADB doesn't recognize it, fastboot neither and I can't even turn it off. I can't enter recovery, it just shows me the asus logo again.
HOWEVER, I waited until the battery drained, connected the usb cable to the tablet (not in the computer) pressed + volume button and without releasing it, connected to pc. Now the computer detects new hardware. I already installed the driver and it says "ASUS TRANSFORMER PRIME APX INTERFACE". Now, i'm not sure if it's the correct driver, but according to hardware administrator, it works fine.
Now, the real cuestion: Is there anything I can do from apx mode to save my tablet? A new bootloader maybe??
Thanks everyone
PS: Sorry for the bad english, It's not my language
Click to expand...
Click to collapse
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
tobdaryl said:
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
Click to expand...
Click to collapse
Hi.
This procedure can be applied and can solve a same issue if until to brick the tablet I installed Android 4.1.1?
Thank you
tobdaryl said:
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
Click to expand...
Click to collapse
Sadly, the tablet came with Android 4.1.x :S
atoma1972 said:
Hi.
This procedure can be applied and can solve a same issue if until to brick the tablet I installed Android 4.1.1?
Thank you
Click to expand...
Click to collapse
Use of the bootloader information may allow access to recovery, adb, or fastboot. Access to any of the three may allow the ability to recover your tablet.
None of the ways worked for me.... can't access that menu...
Claudisimo said:
None of the ways worked for me.... can't access that menu...
Click to expand...
Click to collapse
If you still have no adb, fastboot, or recovery I don't know how to help.
Same situation
tobdaryl said:
To answer your question about apx, no unless you received your tablet with ICS 4.0 and installed Nvflash.
Check my signature for a guide for apx and bootloader menu. Look below the apx section for the bootloader information. Try each from beginning to end except removing the back and disconnecting the battery. If you complete the list and still have not seen a change start with #1 and try them again and again. It is surprising but as you go through the list things have a way changing.
Good Luck!
Click to expand...
Click to collapse
Hi, I'm in the same situation, only APX accesible, my last rom was 4.2.1, but i have my NVFLASH backup files created with this tool when my device had stock ICS ROM
http://forum.xda-developers.com/showthread.php?t=1894867
Is something or a tutorial that I can do to bring my device alive using NVFLASH?
Thanks
Mynzer said:
Hi, I'm in the same situation, only APX accesible, my last rom was 4.2.1, but i have my NVFLASH backup files created with this tool when my device had stock ICS ROM
http://forum.xda-developers.com/showthread.php?t=1894867
Is something or a tutorial that I can do to bring my device alive using NVFLASH?
Thanks
Click to expand...
Click to collapse
Rayman the dev and op for nvflash suggests this as a first option.
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
Here is the thread where he posted this info.
If you wish you can use blobtools to create your own.
Here is the link.
https://github.com/AndroidRoot/BlobTools
windows precompiled blobtools - http://forum.xda-developers.com/show....php?t=1890912
this way no long downloads
see post #7 for info - http://forum.xda-developers.com/show....php?t=1068548
UI for blobtools - http://forum.xda-developers.com/show....php?t=2012033
Good Luck!
Note: for recovery I suggest twrp(since you'll be in ICS choose one for ICS and TF300T)!
It Work
tobdaryl said:
Rayman the dev and op for nvflash suggests this as a first option.
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 some_ics_recovery.img
Here is the thread where he posted this info.
If you wish you can use blobtools to create your own.
Here is the link.
https://github.com/AndroidRoot/BlobTools
windows precompiled blobtools - http://forum.xda-developers.com/show....php?t=1890912
this way no long downloads
see post #7 for info - http://forum.xda-developers.com/show....php?t=1068548
UI for blobtools - http://forum.xda-developers.com/show....php?t=2012033
Good Luck!
Note: for recovery I suggest twrp(since you'll be in ICS choose one for ICS and TF300T)!
Click to expand...
Click to collapse
Thank you so much, my device comes back from hell, and it's ready to use, the firmware returns to ICS, but I updated again to JB
:good:
Mynzer said:
Thank you so much, my device comes back from hell, and it's ready to use, the firmware returns to ICS, but I updated again to JB
:good:
Click to expand...
Click to collapse
Great! I'm glad I could help.
help...
Mynzer said:
Thank you so much, my device comes back from hell, and it's ready to use, the firmware returns to ICS, but I updated again to JB
:good:
Click to expand...
Click to collapse
Hi Mynzer,
Could you explain here how you do to un brick or avoid bootloop with twrp please ?
Fullpoweradonf said:
Hi Mynzer,
Could you explain here how you do to un brick or avoid bootloop with twrp please ?
Click to expand...
Click to collapse
Of course, my tablet had the bootloop error with TWRP and the new 4.1.2 JB update.
When my device had stock ICS ROM (long time ago), I followed this tutorial, this allow you to create some backup files from your device, which in the future will allow you flash your tablet througth APX mode (more powerfull that fastboot mode) and the NVFLASH utility
http://forum.xda-developers.com/showthread.php?t=1894867
The only isue is that you need a pre-JellyBean bootloader (ICS) in order to make those backup files, if you are in a JB stock ROM (JB-bootloader), you can't make this backup files (Asus block the way that we can backup this files on JB ROMs).
With my backup files, the nvflash tools (from the tutorial above), and the instrutions that post tobdaryl, I manage to restore my tablet to an ICS ROM
If you are interested, there is a online petition (but i don't remember were :silly asking that Asus allows the NVFLASH backup utility on JB-bootloaders. With NVFLASH and ours backup files, we can restore our devices from any type of soft-brick.
In the case that your TF300 had and stock ICS (or you can flash it one), I can assist you in the case that you have troubles making the nvflash backup files with the tutorial
Would be nice if you could use someone else's file to fix a brick. Has anyone tried it.
Mynzer said:
Of course, my tablet had the bootloop error with TWRP and the new 4.1.2 JB update.
When my device had stock ICS ROM (long time ago), I followed this tutorial, this allow you to create some backup files from your device, which in the future will allow you flash your tablet througth APX mode (more powerfull that fastboot mode) and the NVFLASH utility
http://forum.xda-developers.com/showthread.php?t=1894867
The only isue is that you need a pre-JellyBean bootloader (ICS) in order to make those backup files, if you are in a JB stock ROM (JB-bootloader), you can't make this backup files (Asus block the way that we can backup this files on JB ROMs).
With my backup files, the nvflash tools (from the tutorial above), and the instrutions that post tobdaryl, I manage to restore my tablet to an ICS ROM
If you are interested, there is a online petition (but i don't remember were :silly asking that Asus allows the NVFLASH backup utility on JB-bootloaders. With NVFLASH and ours backup files, we can restore our devices from any type of soft-brick.
In the case that your TF300 had and stock ICS (or you can flash it one), I can assist you in the case that you have troubles making the nvflash backup files with the tutorial
Click to expand...
Click to collapse
Could You explain step by step which driver and how do you get up Yours TF300T?
I have the same problem, only recovery starts (TWRP2.5.0.0)
possible brick?...
After downgrade the console from the v. 4.2 to 4.1, following tutorials in this forum, because it would not let me install a Custom Rom (yes the recovery, not the root) I can think of to make a choice Wipe from the Stock 4.1 Recovery and restart WW I stand still Asus logo, white, and trying to restart pushing Recovery again, I go and I follow the fixed logo. I do not recognize the device SDK and have seen many posts and I can not find the solution ... buf! Someone has been the same? ... The strange thing is that lights ...
In case nothing else works (another fix) worked for me!
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps, don't forget to hit thanks button if it works =)
i have an odd question
i have an odd question. i bricked my tab. it's stuck on asus logo and no access to fastboot. just access to apx mode but i haven't nvflash beckup. my question is: did is possible sometime in the future will be able to unbrick my tab. to wait an new solution to arrive, if that is possible, or there no chance for that. can anybody answer to my naive question please
racerocm said:
i have an odd question. i bricked my tab. it's stuck on asus logo and no access to fastboot. just access to apx mode but i haven't nvflash beckup. my question is: did is possible sometime in the future will be able to unbrick my tab. to wait an new solution to arrive, if that is possible, or there no chance for that. can anybody answer to my naive question please
Click to expand...
Click to collapse
If you cannot access to fastboot, IMHO there's nothing you can do. I am in your same boat: no adb and fastboot access, my PC recognize the tablet only in APX mode but with NVflash I cannot do anything because I not have a backup.
Bye
EDIT: I am in this situation after a wrong recovery flash. I flashed a new recovery but I could not load it and I made the (big) mistake to try a wipe from the recovery menu. My Tf300t is now stuck at asus logo and I cannot access to the bootloader anymore. I do not know what to do, is the tablet definitely bricked or there's something I can try before going to ASUS service?
Thanks in advance.
Bye

[Q] Unable to root TF101 on ICS (build IML74K.TW_epad-9.2.1.27-20120615)

I've following multiple post and tried many methods to root this tablet, but unsuccessful. I've followed CM documentation, have used viperMOD Primer Tool v4.5 and couple of other methods. On a couple of blog posts I noticed that locale makes a lot of difference and was advised against flashing - hence afraid of trying any more methods until I fully understand.
From the build number, it appears that the locale is Taiwan (tablet was purchased in Singapore).
Can someone please point me to a definitive way to root this device? I would really like to get CM on it.
Thanks in advance.
Give this a try: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
It uses EasyFlasher (APX mode and NVFlash/Wheelie) to get a custom recovery installed.
Another method is to use PERI to install a custom recovery via ADB: http://forum.xda-developers.com/showthread.php?t=1681155
I have not found any issues with locale vs rooting. The only issue is if you have a TF101G vs a TF101.
No, not able to
frederuco said:
Give this a try: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html
It uses EasyFlasher (APX mode and NVFlash/Wheelie) to get a custom recovery installed.
Another method is to use PERI to install a custom recovery via ADB: http://forum.xda-developers.com/showthread.php?t=1681155
I have not found any issues with locale vs rooting. The only issue is if you have a TF101G vs a TF101.
Click to expand...
Click to collapse
Hi Frederuco, The device is TF101 (12 GB, no 3G), so assume it is NOT tf101G. (dev settings also says this is a TF101). In addition, this seems to be SBK1 since s/n is : B70KAS21xxxxx.
I tried both EasyFlasher and PERI. But when I boot into recovery, the android image seems to fall down and a typical 'Stop' sign appears.
But the device boots just fine in normal mode.
Any clues?
Concoran said:
Hi Frederuco, The device is TF101 (12 GB, no 3G), so assume it is NOT tf101G. (dev settings also says this is a TF101). In addition, this seems to be SBK1 since s/n is : B70KAS21xxxxx.
I tried both EasyFlasher and PERI. But when I boot into recovery, the android image seems to fall down and a typical 'Stop' sign appears.
But the device boots just fine in normal mode.
Any clues?
Click to expand...
Click to collapse
For EasyFlasher, it may be SBK 2. I have a B70k they is SBK 2.
When using EasyFlasher, did any text appear on the TF screen? If it did not, it didn't work properly.
As for PERI, I've not used it so I cannot troubleshoot much there.
SBK2 didn't work with Easy Flasher either
frederuco said:
For EasyFlasher, it may be SBK 2. I have a B70k they is SBK 2.
When using EasyFlasher, did any text appear on the TF screen? If it did not, it didn't work properly.
.
Click to expand...
Click to collapse
I tried both SBK1 and 2.
I can't boot into recovery. It crashes somewhere.
When using Easy Flasher, there was no text on screen.
By the way, how do I boot this device into APX mode? I tried searching, but couldn't find any useful link yet.
Any clues?
First, plug your tablet into your PC via USB. Then hold VOL UP and POWER for about 10-15 seconds. You should hear the new hardware noise from your PC. The TF101 screen will be black. The ONLY way to know it is really in APX is the new hardware found, and that your PC shows an APX device (it may be an unidentified device until you update the driver).
Thank You so much
frederuco said:
First, plug your tablet into your PC via USB. Then hold VOL UP and POWER for about 10-15 seconds. You should hear the new hardware noise from your PC. The TF101 screen will be black. The ONLY way to know it is really in APX is the new hardware found, and that your PC shows an APX device (it may be an unidentified device until you update the driver).
Click to expand...
Click to collapse
Hi Freduruco. Thank you so much for assisting me with it. I am now able to install and boot into TWRP (using SBK2).
Appreciate your help.
SWEET!
Enjoy.

[Completed] How do I fix my boot verified failed error on Acer A500?

I was recently trying to update my Acer Iconia A500 and it appears I made a mistake...I had my tablet rooted and I was using the Acer recovery tool to try to use cwm to update. I was running stock OTA ICS. Acer recovery tool warned that my bootloader should be updated to version 1.03 (Acer recovery tool said I had 0.03.12-ICS). I was trying to update the bootloader and initiated a reboot and I haven't been able to boot since. When I try to boot, I see "boot verified failed...". I've tried several fixes from what I've found searching. The hard reset with power/volume/screen lock does not work and I still see the boot verified failed. I tried copying every version of update.zip I could find to a microsd card and booting by holding power+volume down - same result. If I boot by holding power+volume down+screen lock I get a message saying "bootloader: v.03.12-ICS: Starting Fastboot USB download protocol", but nothing happens. If I plug the tablet into my computer in this state, it makes a noise recognizing a connected device, but I cannot view the drives (drivers are current) - also in this same state if I use the list devices command in adb fastboot no device is displayed.
Any feedback or advice would be greatly appreciated. I'm not experienced and I am simply trying to piece together information from various sources. Normal solutions would be hard reset or booting with update.zip, but neither are working.
XDA Visitor said:
I was recently trying to update my Acer Iconia A500 and it appears I made a mistake...I had my tablet rooted and I was using the Acer recovery tool to try to use cwm to update. I was running stock OTA ICS. Acer recovery tool warned that my bootloader should be updated to version 1.03 (Acer recovery tool said I had 0.03.12-ICS). I was trying to update the bootloader and initiated a reboot and I haven't been able to boot since. When I try to boot, I see "boot verified failed...". I've tried several fixes from what I've found searching. The hard reset with power/volume/screen lock does not work and I still see the boot verified failed. I tried copying every version of update.zip I could find to a microsd card and booting by holding power+volume down - same result. If I boot by holding power+volume down+screen lock I get a message saying "bootloader: v.03.12-ICS: Starting Fastboot USB download protocol", but nothing happens. If I plug the tablet into my computer in this state, it makes a noise recognizing a connected device, but I cannot view the drives (drivers are current) - also in this same state if I use the list devices command in adb fastboot no device is displayed.
Any feedback or advice would be greatly appreciated. I'm not experienced and I am simply trying to piece together information from various sources. Normal solutions would be hard reset or booting with update.zip, but neither are working.
Click to expand...
Click to collapse
Hard/factory reset would have been my first answer too.
Is your issue similar to this one: Boot verified failed after update PLEADE HELP?
Maybe you can unbrick it like described here: [GUIDE] How to unbrick Acer Iconia A500.
And if you need further help, please register on xda and ask in the thread directly.
Good luck !
Thread closed. Thank you!

Categories

Resources