Database Info

[Q] What did I do...

Ok... I bought my Transformer about a year ago, rooted it and everything... was doing great, but decided to go back to stock rom, but still wanted to be rooted... ok I had TWRP Recovery on it... I downloaded the newest stock off ASUS site... US_epad_user-9.2.1.27.zip... and put on my SD card... I wiped everything and flashed it like a normal rom... now here is the crap part... I can boot into the rom, and everything is great, but I cant seem to be able to root or anything, when I try Power/VOL Down/VOL UP... I get a standing android for a few seconds then the dead one with a red ! point... I can still use the device, but would really like to get rooted again... HELP... have tried EasyFlasher now, and Brks_rootkit_v8... But doesnt seem to find the device with the dead android.
Thanks for any help

lexknight said:
Ok... I bought my Transformer about a year ago, rooted it and everything... was doing great, but decided to go back to stock rom, but still wanted to be rooted... ok I had TWRP Recovery on it... I downloaded the newest stock off ASUS site... US_epad_user-9.2.1.27.zip... and put on my SD card... I wiped everything and flashed it like a normal rom... now here is the crap part... I can boot into the rom, and everything is great, but I cant seem to be able to root or anything, when I try Power/VOL Down/VOL UP... I get a standing android for a few seconds then the dead one with a red ! point... I can still use the device, but would really like to get rooted again... HELP... have tried EasyFlasher now, and Brks_rootkit_v8... But doesnt seem to find the device with the dead android.
Thanks for any help
Click to expand...
Click to collapse
Go to development thread and look at easyflash, download easyflash and restore your tablet... read the instructions properly...
Sent from my Transformer using xda app-developers app

easyflasher requires APX mode, doesn't matter if it's "a dead droid". Just put it in APX, install the drivers (instructions are in the post) and flash a new firmware, then follow instructions for root (just hit the button in easyflasher). As long as your device is detected in APX, then it'll work.

Stupid me !!!
I was holding Power/Down Vol.... needed to be holding Power/UP Vol... to inter into APX... what a Dummy I feel like... ok... I am back to happy...

[Q] Total device failure: URGENT ASSISTANCE REQUIRED!

I'm quite well up with my Android devices and have enjoyed countless ROMs, modsm, hacks and such for a while now but I have come to a big massive wall and really need help.
I installed RomToolBox on my TF300T which turned out to be the biggest mistake ever. I changed a few settings and had a look around the app when I got a Toast message telling my the system had crashed and was closing. It only gave me the option to click "OK" which upon doing just brought the same message up again and again. I then rebooted by using a pin in the side of the tablet and the device got stuck in a boot loop.
I eventually figured something out and replaced the SystemUI.apk and the Framework-Res.apk in /System/App via ADB and my device booted.
Once booted I noticed my system bar wasn't there and I had no access to the notifications, time etc. I then decided to factory reset so I ran TiBkp and backed up all my Apps + Data and transferred it to my thumbstick.
I proceeded to the settings and ran through the options to wipe and restore to factory settings. After the device rebooted I got the Android on the screen with the Blue loading bar etc. 20 minutes had passed and nothing happened. I decided to Google a few things and ran though the process of trying to sort out the factory restore.
I have tried EVERYTHING and my tablet is now completely screwed.
I have tried everything I can come across, from rebooting into recovery, fastboot and all the rest but noting happens. I've tried the WSG_UnBricker_V1.0.3 and can never get passed "waiting for device". I cant get it to recognise ADB or FASTBOOT and it just sticks on the same factory restore screen.
As I knew it was going to go nowhere, I tried to restart it with a pin and it just gives me the Asus boot screen and then goes straight onto the factory restore screen with no ability to do anything. I cant even turn my device off.
My device was rooted, unlocked, running stock 4.1.1 with all the usual app installed (clockwork etc).
All I can do for now is let the tablet run out of battery and go from there and hope one of you can help.
I will gladly pay for services within the UK if it can be repaired. I obviously can't take it back to the shop. Anyway, enough of that. If you can help, please get in contact.
Thanks,
Dale.

It's a known issue unfortunately if you do a factory reset from the boot loader on a custom recovery.
There should be warnings all over xda about it but I don't think there are. If you can't get the device recognised in fast boot from a PC or you didn't do the nvflash process after unlocking then I'm afraid you probably have a brick.

Not that its much help but if you are bricked like I was, it was quite easy to replace the main board with a used one from Ebay.
No chance you had NV Flash snapshots?
Good luck with it,
Feend

In all honesty it simply sounded at first to be a permissions issue for SystemUI.apk.
But if you can get to fastboot I would try Reformatting your system partition and flashing another ROM. Then factory reset your data partition.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

sbdags said:
It's a known issue unfortunately if you do a factory reset from the boot loader on a custom recovery.
There should be warnings all over xda about it but I don't think there are. If you can't get the device recognised in fast boot from a PC or you didn't do the nvflash process after unlocking then I'm afraid you probably have a brick.
Click to expand...
Click to collapse
Sorry if I've misinterpreted you, but are you saying that doing a factory reset in CWM can brick your device?
Sent from my R800i using xda app-developers app

UndisputedGuy said:
Sorry if I've misinterpreted you, but are you saying that doing a factory reset in CWM can brick your device?
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.

sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Wow. Thanks a lot for posting this information. I had no idea. Would using the factory reset within CWM or in the settings be dangerous?

sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
So doing this completely hard bricks the device? meaning NO bootloader? It almost seems like the bootloader factory reset is touching the block that holds the recovery. Isnt there source code for this bootloader? Couldnt this be solved?

sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Wow i am very glad i stumbled across this.. there should be a sticky about this or something!! Thanks for the very helpful post
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

I have to agree, I'm REALLY glad I came across this. I'd noted that in a few of the "My tablet is bricked" threads that people had bricked after accidentally clicking something in the bootloader screen and had vowed not to touch anything in the original bootloader.
Thanks for the heads up on this.

sbdags said:
No if you do a factory reset in the boot loader (you know where there are 4 icons on the screen - the 4th one I believe) and you are on a custom recovery then you can brick your device. In fact I know 3 people that have bricked this way now.
Using the factory reset within TWRP for example will not brick your device. It's the bootloader one that is now dangerous.
Click to expand...
Click to collapse
Just a quick question cuz I'm curious... these 3 (or 2 other?) people you know who bricked this way.. were they able to recover? Or was it game over for them?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

markymark567 said:
Just a quick question cuz I'm curious... these 3 (or 2 other?) people you know who bricked this way.. were they able to recover? Or was it game over for them?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Game over

sbdags said:
Game over
Click to expand...
Click to collapse
Did they not have nvflash files? Can nvflash not recover this brick?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

markymark567 said:
Did they not have nvflash files? Can nvflash not recover this brick?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Yes nvflash would have been able to recover. Unfortunately they either didn't know about nvflash before upgrading to jelly bean or they were already on a higher version than nvflash works on when it was released. In all 3 cases they could only get into apx mode. No fast boot and no recovery.
Only fix in this case is to send it back to Asus are able to recover it so we are missing something that Asus have.

sbdags said:
Yes nvflash would have been able to recover. Unfortunately they either didn't know about nvflash before upgrading to jelly bean or they were already on a higher version than nvflash works on when it was released. In all 3 cases they could only get into apx mode. No fast boot and no recovery.
Only fix in this case is to send it back to Asus are able to recover it so we are missing something that Asus have.
Click to expand...
Click to collapse
That's a bummer for them but good to know nvflash can fix it. and f*** Asus for locking the jb boot loader to prevent nvflash... Maybe this is a stupid comment but I think they would sell more devices if they didn't do stuff like this... I know when I look into purchasing a device I come here first to make sure there is android development and unbricking procedures. ( I saw nvflash for tf300t and that's pretty much the reason I picked that tablet). Its a bummer that companies like Asus are much more concerned with making money by repairing bricked devices. (Although I do love Asus hardware. I own a tf300t and a nexus 7...its a love hate thing... Damn you Asus)
Sent from my Nexus 7 using xda app-developers app

D.MADROX said:
I'm quite well up with my Android devices and have enjoyed countless ROMs, modsm, hacks and such for a while now but I have come to a big massive wall and really need help.
I installed RomToolBox on my TF300T which turned out to be the biggest mistake ever. I changed a few settings and had a look around the app when I got a Toast message telling my the system had crashed and was closing. It only gave me the option to click "OK" which upon doing just brought the same message up again and again. I then rebooted by using a pin in the side of the tablet and the device got stuck in a boot loop.
I eventually figured something out and replaced the SystemUI.apk and the Framework-Res.apk in /System/App via ADB and my device booted.
Once booted I noticed my system bar wasn't there and I had no access to the notifications, time etc. I then decided to factory reset so I ran TiBkp and backed up all my Apps + Data and transferred it to my thumbstick.
I proceeded to the settings and ran through the options to wipe and restore to factory settings. After the device rebooted I got the Android on the screen with the Blue loading bar etc. 20 minutes had passed and nothing happened. I decided to Google a few things and ran though the process of trying to sort out the factory restore.
I have tried EVERYTHING and my tablet is now completely screwed.
I have tried everything I can come across, from rebooting into recovery, fastboot and all the rest but noting happens. I've tried the WSG_UnBricker_V1.0.3 and can never get passed "waiting for device". I cant get it to recognise ADB or FASTBOOT and it just sticks on the same factory restore screen.
As I knew it was going to go nowhere, I tried to restart it with a pin and it just gives me the Asus boot screen and then goes straight onto the factory restore screen with no ability to do anything. I cant even turn my device off.
My device was rooted, unlocked, running stock 4.1.1 with all the usual app installed (clockwork etc).
All I can do for now is let the tablet run out of battery and go from there and hope one of you can help.
I will gladly pay for services within the UK if it can be repaired. I obviously can't take it back to the shop. Anyway, enough of that. If you can help, please get in contact.
Thanks,
Dale.
Click to expand...
Click to collapse
I have worked with six or seven who used the wipe data on the bootloader; two recovered.
If you have any chance to recover you have to work at it. First apx mode is useless unless you previously flashed Nvflash.
We need adb, fastboot, or recovery working. Here is a thread for your use to get control of your tablet.
You mention rebooting into recovery. Stock, cwm, or twrp?
As you progress through this list the tablets have a way of evolving. This can happen even if you haven't gotten anything to function as you wish. That means you have to do them again; three times may be the charm.
I would like very much to know about your mention of recovery. Can you still get into recovery and which?
How about a current update before you begin using that link.

[Q] Tf300t stuck at bootscreen and can't get into recovery options.

Hey,
My Asus Tf300t has been working perfectly until I wanted to get into recovery mode (RCK) yesterday. It got stuck there and
I tried it another time and it didn't work. After that I let it go and just booted normally, but then it stayed at the "ASUS Inspiring inno.... etc." screen.
Now I can shut my device down by holding the power button, but I cant get it to cold boot or get into recovery options again, it just boots endlessly.
My device has been unlocked and working fine for months.
What can I do?
regards,
Pmobilee

make sure that you are hold the "volume down" button, and hope it puts you back to where you can boot into recovery. Does that tablet boot at all, or just a "bootloop"

Did you have a working recovery before this? Like have you booted your recovery before and know that it was working?
Sent from my Nexus 7 using xda app-developers app

tazzz013 said:
make sure that you are hold the "volume down" button, and hope it puts you back to where you can boot into recovery. Does that tablet boot at all, or just a "bootloop"
Click to expand...
Click to collapse
Yes, I have been into the recovery and know the procedure. And im afraid the boot goes as far as the asus logo.
markymark567 said:
Did you have a working recovery before this? Like have you booted your recovery before and know that it was working?
Yes, recovery booted before. But this all started when I tried to boot recovery again, and it got stuck. Then this infitite boot occurred.
Click to expand...
Click to collapse

and when you tried to boot recovery again what method did you use? did you use the "reboot recovery" option in your recovery or ROM power menu?or did you do it manually?(hold vol- and power then press vol+)?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Hi all. I'm in the exact same situation. Didn't want to make a new thread though.
I rooted my TF300T a few months ago (Oct 2013), and it has been running fine on CyanogenMod 10.2. So I ran the CyanogenMod Update app (Settings > About Tablet > CyanogenMod Updates), then downloaded the LATEST nightly (dated yesterday: Dec 14, so 10.2...141213). I don't know if this is a factor, but I usually pull down the notification bar and tap the "Reboot and Install" option, but I accidentally cleared my notifications, so I went back into CyanogenMod Updates, tapped the installed button for the latest nightly, and tablet started rebooting.
However I cannot get past the boot screen. So recovery is not loading. I used TWRP last time I did this. I Can't turn the tablet off either, at least not until I plugged the USB from my PC to the tablet then tried long pressing the Power button and holding Volume Down. Before plugging USB in it would simply restart and sit on the boot screen again.
I have to leave the house for now, but will attempt to get into Recovery later tonight with same methods as above. Fingers crossed!
EDIT: I remembered, it was 10.2, not 10.1 I was running. So I shouldn't have had any issues going from 10.2 to a newer 10.2.

I'm back home now. I've tried again to get into Recovery, but cannot. I've got the tablet plugged into the PC with the USB, I'm holding Power and Volume Down, but nothing. Instead it seemly turns off, but comes back on and stays on the same boot screen (Asus. Inspiring Innovation, etc...).
And I can't figure out how I was able to turn the damn thing off before either. So I have to leave it on until the power drains. So that sucks!
Is it bricked?

Let's do this together. I recently tried to upgrade to 4.4 from 4.3 and I accidently erased my tablet by manually booting into twrp 2.5 and selecting the 3rd option which is wipe data...so we are in the same boat.
Has your battery drained yet?
Sent from my SAMSUNG-SM-N900A using xda app-developers app

Ideas4ya said:
Let's do this together. I recently tried to upgrade to 4.4 from 4.3 and I accidently erased my tablet by manually booting into twrp 2.5 and selecting the 3rd option which is wipe data...so we are in the same boat.
Has your battery drained yet?
Click to expand...
Click to collapse
Damn, that sucks! Yes, battery has now drained, and yes, let's work this out together. What ROM were you using? Android 4.4 is not out on CyanogenMod for the TF300T, and I will probably stick to CM. But if I have to use something else to get this fixed, I'll do it.

Was any fix found for this? I am now experiencing the same problem after trying to reboot into recovery to upgrade Cyanogen. Any help would be appreciated.

fdbryant3 said:
Was any fix found for this? I am now experiencing the same problem after trying to reboot into recovery to upgrade Cyanogen. Any help would be appreciated.
Click to expand...
Click to collapse
Nope, and after a lot of support and help from the good guys on the Transformer Forums, I've declared this unfixable. If you had a NVIDIA backup, you'd be fine, but without that you're pretty much screwed, sorry to say.

Can you get into bootloader? If so you can do this:
http://forum.xda-developers.com/showthread.php?t=2425581
And it should resolve ANY bad flash/wrong flash issues.

[Q] Only asus bootscreen, no recovery or boot - Is it Bricked?

Good evening all?
Ive unlocked my TF300T a year back and had been running Cyogenmod 10.1 on it for months, all worked fine.
As a recovery i had CWM installed and it worked like a charm as well.
A week ago i saw Cyogenmod 10.2 was out there and i wanted to switch the recovery to TWRP (i installed ver 2.6.x.x) and tried the new Cyogenmod.
It sisnt work so i wanted to switch back to 10.1 and CWM.
I dont exactly know what i did but in the end even the vol down and power button menu doesnt work anymore.
The tab turn on now and shows the Asus start screen but doesnt boot up.
Also when i press vol down and the power button it doesnt load the boot menu where i can install a new recovery and install the old Cyogenmod.
When its powered on i cant even turn of the tab, it keeps turning on for a few minutes in the Asus logo screen and than turn off and on again... till the battery is empty.
Did i brick my tablet ?
Are there any ways i can try to get the original software back?
Any help would be greatly appreciated.
Cheers !
Marty

Same situation with me....i think u have Hard Bricked your Tablet. The only option is Change the motherboard. So u need to send it to Asus..
Sent from my iris504Q using XDA Premium 4 mobile app

Did you update your bootloader to the JB one?

It IS Lupus said:
Did you update your bootloader to the JB one?
Click to expand...
Click to collapse
I think i didn't...
At first i just unlocked the device, installed recovery CWM and after a version (januari 2013) of Cyogenmod 10.1 wich was Android 4.2.2 and kept the Cyogenmod 10.1 up to date every few weeks... Thats all i did till i wanted to install Cyogenmod 10.2 (Android 4.3)
I can't recall updating the bootloader myself, could have been with an Asus update or something but i think i din't do it myself.

CM changed to the updated PITs when Asus updated first.
best solution would be to flash latest stock, boot into it once, flash twrp2 (2.6.0.0 works for me atm) then flash cm10.2
here is my summary
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
hope it helps
and no, i don't think you need to send it in for repair - it sounds more like broken PIT's so mount and boot points are not being recognized anymore.
gl
-Buster

Buster99 said:
CM changed to the updated PITs when Asus updated first.
best solution would be to flash latest stock, boot into it once, flash twrp2 (2.6.0.0 works for me atm) then flash cm10.2
here is my summary
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
hope it helps
and no, i don't think you need to send it in for repair - it sounds more like broken PIT's so mount and boot points are not being recognized anymore.
gl
-Buster
Click to expand...
Click to collapse
Thanks for your reply, how do i get to give fastboot commands when starting with volume down + power doesn't work anymore.
The only thing i have left is volume up + power to boor into APX mode and i cant seem to get the right usb driver for the TF300T
Cheers !

Tablet gets stuck on boot animation
I have a rooted asus tf300t and it will turn on but not get past the boot animation. I have tried to reset it using the bootloader but it will still not work. if anyone has any suggestions, i would like to hear them. i am a complete noob so please try to keep it simple. thanks

Tablet gets stuck on boot animation
I have a rooted asus tf300t and it will turn on but not get past the boot animation. I have tried to reset it using the bootloader but it will still not work. if anyone has any suggestions, i would like to hear them. i am a complete noob so please try to keep it simple. thanks

geronphillips said:
I have a rooted asus tf300t and it will turn on but not get past the boot animation. I have tried to reset it using the bootloader but it will still not work. if anyone has any suggestions, i would like to hear them. i am a complete noob so please try to keep it simple. thanks
Click to expand...
Click to collapse
More details will be needed before someone can help. What had you done right before it acted up? What rom do you have in there ATM? Can you post a picture or tell what's on the initial screen (the one before the boot animation)? Did you try volume down + power? If you did, what did the screen show?

graphdarnell said:
More details will be needed before someone can help. What had you done right before it acted up? What rom do you have in there ATM? Can you post a picture or tell what's on the initial screen (the one before the boot animation)? Did you try volume down + power? If you did, what did the screen show?
Click to expand...
Click to collapse
I rooted my device using the method shown on this page
http://forum.xda-developers.com/showthread.php?t=2228613I
, the ROM is stock and the screen before the animation is normal (white Asus text). I have tried volume down and power and from that screen, I reset my tablet. This didn't solve the issue, before this started, I changed the boot animation and changed fonts. I think it was while restarting after the font change that it stopped booting properly.

geronphillips said:
I rooted my device using the method shown on this page
http://forum.xda-developers.com/showthread.php?t=2228613I
, the ROM is stock and the screen before the animation is normal (white Asus text). I have tried volume down and power and from that screen, I reset my tablet. This didn't solve the issue, before this started, I changed the boot animation and changed fonts. I think it was while restarting after the font change that it stopped booting properly.
Click to expand...
Click to collapse
I gather by "reset my tablet", you meant you cold booted it by selecting the android icon. This being the case, you can always reflash the stock ROM with fastboot. Depending on whether you had 4.1 or 4.2 bootloader - 4.1 has 4 icons including a USB icon which if clicked, will make the tab enter fastboot/download mode; 4.2 will enter that mode automatically as you press volume down+power - you need to choose the right ROM you want to install. The initial screen should tell you which bootloader on the top left corner. 4.1 matches stock Roms commencing with 10.4.x.xx; 4.2 is Roms with 10.6.x.xx
I've flashed a 4.1 ROM (104220) on a tab with 4.2 bootloader by means of an external SD card without problems. However, to be safe, you should flash whatever version you'd had before the incident. If you already have data on the tab that you care to keep, you shouldn't touch the wipe date icon. If you need a link as to what to do, read this one. Good luck.

[Q] Bricked? TF300

Hello,
I ran CM's in-android update utility to update to CM 10.2 last night and it hosed my tablet.
My TF300 gets stuck at the ASUS logo screen. When I power it off it boots right back to the ASUS screen. If I push the VOL UP button twice before it reboots it will stay off.
Can't get it into recovery mode by pressing VOL DOWN and POWER, still gets stuck at ASUS screen.
My computer wont see it; I can't get fastboot to do anything with it, < waiting for device >. This is the same computer that I used fastboot to initially flash clockwork so it is setup correctly. Windows 7 64-bit.
Is it bricked beyond repair? If not how do I proceed?
Thank you
P.S. I'm not sure what other information you may need, and I can't remember some of the specifics. I can't get to that informaiton now due to it not booting.

Hmpf, just finished writing this, applies to you also:
http://forum.xda-developers.com/showthread.php?p=50788393
Sent from my TF300T using Tapatalk

f69m said:
Hmpf, just finished writing this, applies to you also:
http://forum.xda-developers.com/showthread.php?p=50788393
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Neither worked. Still nothing but ASUS Logo boot screen. Want me to move to other thread to consolidate?

epatch said:
Neither worked. Still nothing but ASUS Logo boot screen. Want me to move to other thread to consolidate?
Click to expand...
Click to collapse
Sure, but I am afraid I am out of ideas. Rescue requires either fastboot, recovery/adb or a set of nvflash blobs created before.
Sent from my TF300T using Tapatalk