Database Info

[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.

Well I think my tablet is completely unsavable

I tried to use fastboot to install a blob..
It must have frozen or something. It got through sending the blob, then it try to write the system file but it hung overnight and did not finish. I had to try reboot the tablet.
It now does not turn on, go into APX, recovery, or even light up that its charging. The only indication that I get that it has any life left is that when I try turn it on when it is plugged via USB to my PC, my computer makes the noise it does to recognize devices.
Please tell me there's a chance for my tablet.

I don't really think so , if it doesn't show anything i think it's dead, have you tried to acces the bootloader?
(i am not an expert in these things i also didn't brick my tab yet)
Sent from my ASUS Transformer Pad TF300T

I have tried. It did not work.
Are there any tools at all for me to combat this?
Sent from my SAMSUNG-SGH-I317 using xda premium

i think you should send it to asus and see what happens!
Sent from my ASUS Transformer Pad TF300T

I have a warranty from Sams. I am going to attempt a return with them.
What does anyone think my chances of them not figuring out its unlocked if it's hard bricked?
Sent from my SAMSUNG-SGH-I317 using xda premium

sometimes they ask you to pay for a new motherboard (because of unlock) sometimes they just fix it (with an unlocked bootloader) sometimes they fix it and make the bootloader UNunlockable
Sent from my ASUS Transformer Pad TF300T

Thanks for the words. I appreciate it.
Sent from my SAMSUNG-SGH-I317 using xda premium

Liquidmetal6 said:
I tried to use fastboot to install a blob..
It must have frozen or something. It got through sending the blob, then it try to write the system file but it hung overnight and did not finish. I had to try reboot the tablet.
It now does not turn on, go into APX, recovery, or even light up that its charging. The only indication that I get that it has any life left is that when I try turn it on when it is plugged via USB to my PC, my computer makes the noise it does to recognize devices.
Please tell me there's a chance for my tablet.
Click to expand...
Click to collapse
To be honest, it doesn't actually sound like it's off. You shouldn't be getting any response whatsoever if the device is off and dead (on and dead will sometimes net you a malfunctioning device error). If it's still doing that, you can try doing what you would normally do to put the device into fastboot (power + vol. up) "blind." It's worked for me once or twice before, and it's possible it's just your screen that's messed up.
All things considered, given your screen won't come on (so there's no warning about the device being unlocked), so long as Sam's doesn't check with ASUS for your bootloader key status, they won't be able to tell (and likely won't have the know-how to either).

I have had the same thought about sams. However, apparently their warranty does not activate until a year after you purchqse the device, because they pawn if off to Asus. Of course, Asus received the email that I unlocked it and wont do anything about it .
I tried to get it into fast boot and failed but I will mess around with it more since it's not completely dead.
If I flashed a 4.1 blob file and it hung up on writing the system, would the bootloader be 4.2 or 4.1?
It is 4.2 fastboot should have started normally, if it is 4.1 I need to go and do something in the bootloadrr to activate fastboot, correct?
Sent from my GT-N8013 using xda premium

[Q] Need help with a TF300T tablet

hi guys I have a Asus Transformer tablet stuck in a boot loop. when I access the recovery menu it says on the top of the screen.
Android Cardhv-user bootloader <1.00 e> released by "US_epad-10.6.1.27.1-20130711" A03 Key driver not found.. Booting OS
Starting Fastboot USB download protocol
I tried updateing it with that file and it goes thru the update and it still sticks with the boot loop and when I go to recovery the same message appears.
any help would be awesome. please help. it is a stock tablet with nothing never done to it. it just starting doing this out of the blue.

If you've never done anything to it then that must mean your bootloader is locked. I hate to suggest such a thing but you might try wiping your data using the bootloader menu and see if that helps
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

funnel71 said:
If you've never done anything to it then that must mean your bootloader is locked. I hate to suggest such a thing but you might try wiping your data using the bootloader menu and see if that helps
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
tried doing that once and it didn't do anything. to be honest I just want to be able to use the tablet I really don't care about anything save on it so I didn't have a problem wiping it once

extremeconsolemodz said:
tried doing that once and it didn't do anything. to be honest I just want to be able to use the tablet I really don't care about anything save on it so I didn't have a problem wiping it once
Click to expand...
Click to collapse
I tried wiping it again and its the same result

extremeconsolemodz said:
hi guys I have a Asus Transformer tablet stuck in a boot loop. when I access the recovery menu it says on the top of the screen.
Android Cardhv-user bootloader <1.00 e> released by "US_epad-10.6.1.27.1-20130711" A03 Key driver not found.. Booting OS
Starting Fastboot USB download protocol
I tried updateing it with that file and it goes thru the update and it still sticks with the boot loop and when I go to recovery the same message appears.
any help would be awesome. please help. it is a stock tablet with nothing never done to it. it just starting doing this out of the blue.
Click to expand...
Click to collapse
manikkumar20 said:
Dear all users of TF300T.
If you are using Stock ROM (Rooted/Non Rooted) and are bricked or stuck on ASUS boot screen. Then this guide is for you.
As i was using stock ROM (ROOTED) with Locked boot loader without custom recovery and my tf300t was Sofbricked due to wrong configurations at Display Pixel scaling and also reformat did not work for me.!
So i thought to create this guide which may help people out here It worked for me Try your LUCK.
Sorry if i am re posting i did not got any guides out here...
If this helped you please give me a Thumbs up.!
Steps:-
1. Download the latest ROM from ASUS website Which matches your SKU.(Important).
It would look somehing like this (TF300T-TW_epad-10_6_1_15_3-UpdateLauncher . zip)
2. Extract it and rename that file to ( EP201_768_SDUPDATE.zip )
3. Now copy this new renamed file to SDCARD (Root of sd card). Put the SDcard into tablet.
4. Now Press and hold Volume Down + Power for a few seconds. Then you will see the ASUS recovery options.
5. 3 icons will appear: RCK, Android, and Wipe Data. The RCK should be flashing green. Press the UP Volume Key Once.
Now wait for a few minutes. It will flash the ROM.
And wola! Your TF300T will again work fine!!
Any suggestions and comments are most welcomed!
Click to expand...
Click to collapse
What icons show up in the recovery menu?

cmendonc2 said:
What icons show up in the recovery menu?
Click to expand...
Click to collapse
there is a RCK, Android, wipe data
but I have tried this guide and it went thru and said it was updating and such and after everything was done i had the same result. anyway u can please email me the one i should be using ifthat is the case?

Did you try downgrading to an older firmware to see if that works?
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button

The screen that you're looking at is not the recovery menu but the bootloader menu. Are you certain that your bootloader is unlocked? If you don't know we start the tablet and look into the upper left hand corner and it will tell you unlock if it is
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2

It's locked. And yes I tried reinstalling4.0 on it due to the sticker on the tablet saying it was 4.0 and it didn't work. Then I seen the message that it said it was missing a driver so I searched for that en file and then updated it with that and it does the same thing. If ur curious what message I mean look at my first post

[Q] Stuck on ASUS logo

Hello everybody,
I hope that someone can give me some advise to get my tf300t up and running again. I wanted to install cm10.2 but I wanted to install CWM first.
I unlocked my device first with the unlock app v8 from asus.
I tried to install CWM the first time but it did not work.
I went back into recovery mode but I wasn't paying attention and pressed wipe userdata
Now my tf300t only shows the ASUS logo and the text that the device is unlocked. I can't get back in recovery mode anymore. Is there a way the restore it back to default?
I hope that someone can help me out.
Thank you in advance for your time and effort.
Regards
Burner1977

burner1977 said:
Hello everybody,
I hope that someone can give me some advise to get my tf300t up and running again. I wanted to install cm10.2 but I wanted to install CWM first.
I unlocked my device first with the unlock app v8 from asus.
I tried to install CWM the first time but it did not work.
I went back into recovery mode but I wasn't paying attention and pressed wipe userdata
Now my tf300t only shows the ASUS logo and the text that the device is unlocked. I can't get back in recovery mode anymore. Is there a way the restore it back to default?
I hope that someone can help me out.
Thank you in advance for your time and effort.
Regards
Burner1977
Click to expand...
Click to collapse
Can you get to the menu with the recovery options, boot android, USB, and wipe data? You can use fastboot from there.

cmendonc2 said:
Can you get to the menu with the recovery options, boot android, USB, and wipe data? You can use fastboot from there.
Click to expand...
Click to collapse
thank you for your response. No I can't get in there. any suggestions?
thx for your advise

burner1977 said:
thank you for your response. No I can't get in there. any suggestions?
thx for your advise
Click to expand...
Click to collapse
If you cant get into there, you cant really use fastboot. Unless you made NvFlash Backups beforehand, I don't think there is much else you can do, since the recovery isn't working either.

cmendonc2 said:
If you cant get into there, you cant really use fastboot. Unless you made NvFlash Backups beforehand, I don't think there is much else you can do, since the recovery isn't working either.
Click to expand...
Click to collapse
I stupidly made no backups so what you are saying is that it is done.

burner1977 said:
I stupidly made no backups so what you are saying is that it is done.
Click to expand...
Click to collapse
I've spent a lot of time searching and it seems like that's it...
I'm on Asus screen, I can reboot it by either holding down pwr button until it reboots, or using reset switch with a paperclip. vol - does nothing, just reboots to asus screen...computer sees nothing. vol + goes into APX mode (blank screen)...computer detects with correct drivers. I've tried draining battery completely...disconnecting battery for a few days...same result.
If I had to speculate...maybe at some point someone will figure out how to use another's backup files and push them to the device in APX mode.
I've looked into replacing the motherboard...and have seen some for as low as 50$ on ebay. Personally, swapping them would be easy...but some may not have the caviler attitude with hardware swapping. Just gotta get the wife to agree to spend the $.
I'd die for a free fix, the kids really miss playing with the thing

coppervines said:
I've spent a lot of time searching and it seems like that's it...
I'm on Asus screen, I can reboot it by either holding down pwr button until it reboots, or using reset switch with a paperclip. vol - does nothing, just reboots to asus screen...computer sees nothing. vol + goes into APX mode (blank screen)...computer detects with correct drivers. I've tried draining battery completely...disconnecting battery for a few days...same result.
If I had to speculate...maybe at some point someone will figure out how to use another's backup files and push them to the device in APX mode.
I've looked into replacing the motherboard...and have seen some for as low as 50$ on ebay. Personally, swapping them would be easy...but some may not have the caviler attitude with hardware swapping. Just gotta get the wife to agree to spend the $.
I'd die for a free fix, the kids really miss playing with the thing
Click to expand...
Click to collapse
I'm on the same boat, this morning I was trying to install CyanogenMod following the instructions and wipped the tablet... I only have APX connection now with no backups...

[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