Database Info

TF300T can't startup anymore

Something went wrong while flashing CWM on my TF300T. It showed successful in cmd window on pc, but the statusbar on my pad kept showing 100% but nothing happend (no message or automaticly rebooting). After waiting 10 minutes or so, I turned off the device and restarted it.
Now the device is not started up anymore, keeps stuck on message:
"The Device is Unlocked".
When I try te start it up in Fastboot ( pwr+vol down) the screen get stuck on message:
"The Device is Unlocked.
Android cardhu-user bootloader <2.10 e> released by "ww_epad-9.4.3.29-20120511" A03
Checking for android ota recovery
Booting recovery kernel image"
Now the pad is not starting up the ROM and I can't get in fastboot mode anymore.
The solutions given in other treads about a simular problem, you need to put your pad into USB mode.
But that is not posible anymore.
Is there any other solution for this problem??
Thanks guy's

problem
I also have the same brick .... like it ....

Hello,
me too...
Tablet starts always automatically into CWM recovery.
Fastboot and ADB doesnt work either...
Could it be ADB isnt working because debugging mode isnt activated?
But how can I change without a working android?
Is there someone out there who can help me out of this problem?
Or is RMA the only solution?
But I dont want to send my transformer to asus so they can change the motherboard. Its only a software problem...
Can someone help me? Please

Give it what it is looking for and hope for the best. Stock update ( ww_epad-9.4.3.29-20120511 ) If when plugged into pc you have access to internal sdcard put it there, if not put it on external sdcard and reboot unit. If that does not load update try to get into fastboot as you mention above maybe it will install from there since it tells you ( Checking for android ota recovery ).
Good Luck!
If you downloaded the file from asus you will need to unzip once and still have a zip but slightly different name!

tobdaryl said:
Give it what it is looking for and hope for the best. Stock update ( ww_epad-9.4.3.29-20120511 ) If when plugged into pc you have access to internal sdcard put it there, if not put it on external sdcard and reboot unit. If that does not load update try to get into fastboot as you mention above maybe it will install from there since it tells you ( Checking for android ota recovery ).
Good Luck!
If you downloaded the file from asus you will need to unzip once and still have a zip but slightly different name!
Click to expand...
Click to collapse
Hello tobdaryl,
thanks for your answer!
Unfortunately I dont have access to internal sdcard... also I cant get into fastboot mode...
I think ADB could help, but I cant get ADB to work. I have to activate usb debugging, right?
But how could I do without starting Android?

Droid_1 said:
Hello tobdaryl,
thanks for your answer!
Unfortunately I dont have access to internal sdcard... also I cant get into fastboot mode...
I think ADB could help, but I cant get ADB to work. I have to activate usb debugging, right?
But how could I do without starting Android?
Click to expand...
Click to collapse
place it on external sdcard if you can't access internal. if this works you don't need adb or fastboot. we are trying to let your unit update for you and clear your problem. as far as fastboot I'm only suggesting do as you said about trying to go into fastboot as when you received the message about update.
sounds harder than it is.
place update on external sdcard. reboot, if no love reboot into fastboot as when you received update message. at that point we hope your unit will auto install the update for you.
time is all you might loose.
Good Luck!:good:

tobdaryl said:
place it on external sdcard if you can't access internal. if this works you don't need adb or fastboot. we are trying to let your unit update for you and clear your problem. as far as fastboot I'm only suggesting do as you said about trying to go into fastboot as when you received the message about update.
sounds harder than it is.
place update on external sdcard. reboot, if no love reboot into fastboot as when you received update message. at that point we hope your unit will auto install the update for you.
time is all you might loose.
Good Luck!:good:
Click to expand...
Click to collapse
Hey tobdaryl,
my transformer didnt recognized the external sd...
But I made it out of the cwm loop.
Nonetheless many thanks for your help! :good:

Droid_1 said:
Hey tobdaryl,
my transformer didnt recognized the external sd...
But I made it out of the cwm loop.
Nonetheless many thanks for your help! :good:
Click to expand...
Click to collapse
Great!!!
Could you give quick info how you recovered? Several others are waiting for resolve same problem.

tobdaryl said:
Great!!!
Could you give quick info how you recovered? Several others are waiting for resolve same problem.
Click to expand...
Click to collapse
Sorry, I forgot to post the link
http://forum.xda-developers.com/showthread.php?p=32787029#post32787029

Droid_1 said:
Sorry, I forgot to post the link
http://forum.xda-developers.com/showthread.php?p=32787029#post32787029
Click to expand...
Click to collapse
Thanks for sharing and taking the time to create a thread for others to use.
Good Luck!

[Q] Need help Re-Rooting

A few months ago I tried upgrading the bootloader to Jellybean and somehow things did not work correctly. I really don't remember how exactly I messed it up but at the moment I am stuck with a Unlocked Bootloader and on 10.4.2.9 US firmware unrooted. Any advise on to which root method will work? I had tried a few back when this happened but I kept getting errors. Also now I can't get windows to recognize the device either by using Asus Sync or any other Asus driver I have found.
Thanks

firstly you must install TWRP by fastboot.

Hazard17 said:
firstly you must install TWRP by fastboot.
Click to expand...
Click to collapse
That's the main problem I'm having now, no matter what drivers I install on the computer, Windows does not recognize the tablet. The driver installs correctly but when I plug in the tablet I get an error stating "There is a problem connecting the device to Windows" or something like that.

[Q] Urgent! Stuck at bootloader but cant do anything

Hi u all!
First of all thank you for your time and sorry for my english, I speak spanish.
I have a nexus s i9023. I was using CyanogenMod 11 experimental 24042014.
I was having many problems and decided to downgrade to the stable version 10.1.2
It downloaded ok, installed all the updates, rebooted and then got stuck in the logo screen when booting.
The problem is that my nexus s has a broken the power button, it doesn't work.
As for right now the olny thing I can do is to enter the bootloader screen, but cant move throgh the options with the volume keys, it's like its stuck.
If I plug in the device when in the bootloader (fastboot mode) screen my PC doesn't recognice it, I search in the device manager but it doesn't appear.
If it helps when I plug in the battery the phone starts on in it's on.
Please, any help is appreciated.
Im really sad because I love my nexus.
Thank you!!!

Same here. Any help for us would be great. Thanks.

shd128 said:
Hi u all!
First of all thank you for your time and sorry for my english, I speak spanish.
I have a nexus s i9023. I was using CyanogenMod 11 experimental 24042014.
I was having many problems and decided to downgrade to the stable version 10.1.2
It downloaded ok, installed all the updates, rebooted and then got stuck in the logo screen when booting.
The problem is that my nexus s has a broken the power button, it doesn't work.
As for right now the olny thing I can do is to enter the bootloader screen, but cant move throgh the options with the volume keys, it's like its stuck.
If I plug in the device when in the bootloader (fastboot mode) screen my PC doesn't recognice it, I search in the device manager but it doesn't appear.
If it helps when I plug in the battery the phone starts on in it's on.
Please, any help is appreciated.
Im really sad because I love my nexus.
Thank you!!!
Click to expand...
Click to collapse
kijp15 said:
Same here. Any help for us would be great. Thanks.
Click to expand...
Click to collapse
Seems like a driver issue. Can you try installing the drivers in a different system?
If it goes well, then use install cwm touch recovery from fastboot. You can take backup and flash new ROMs after that.
Try Nexus Root Toolkit to install drivers if you don't have access to a different system.

smit.sanghavi said:
Seems like a driver issue. Can you try installing the drivers in a different system?
If it goes well, then use install cwm touch recovery from fastboot. You can take backup and flash new ROMs after that.
Try Nexus Root Toolkit to install drivers if you don't have access to a different system.
Click to expand...
Click to collapse
Don't I need to have android debugging enabled? If so, I don't think Nexus Root Toolkit will work. I flashed a ROM to my NS4g & I get boot loops. I flashed the wrong Gapps a few months ago.
I was hoping there would be a way to automatically turn android debugging on. I know it may sound dumb & also probably impossible.
Any other tips.
Tell me I'm screwed. Haha.

kijp15 said:
Don't I need to have android debugging enabled? If so, I don't think Nexus Root Toolkit will work. I flashed a ROM to my NS4g & I get boot loops. I flashed the wrong Gapps a few months ago.
I was hoping there would be a way to automatically turn android debugging on. I know it may sound dumb & also probably impossible.
Any other tips.
Tell me I'm screwed. Haha.
Click to expand...
Click to collapse
I disabled USB debugging. Rebooted to bootloader. Fired up 'fastboot devices' on cmd and could see my phone. This tells me that I do not need USB debugging on fastboot.
If you see an unknown device in Device Manager while in fastboot then use Universal Naked Driver to install the drivers. But since you don't, you'll need another PC to do this stuff. Once drivers are installed, you can do a 'fastboot reboot recovery' to get into recovery and fix the the problems. The first thing I advice is to flash a touch recovery. The rest is up to you.

Flash back the original soju firmware back onto your device by first using "nexus s root toolkit v.1.8.2 by wugfresh". It may take a little of your time downloading the roms and installing the drivers but trust me it should be working and your phone will boot into stock android 4.1.2. You can then root your device and install custom recovery as normal. Anything do pm me :laugh: ps, click the bricked option one the software is loaded up and remember to connect your device only and remove other phones from your computer

Fastboot not working

Need some help here. Long story short, tablet fell and broke digitizer. 6+ months later finally replaced it but new one wouldnt work. Updated touch screen driver and it works. ADB works but fastboot does not. Used factory ROM to reset device to see if it helps. It doesn't. In device manager it shows ASUS android bootloader interface with no !. Downloaded ASUS pc suite for the drivers still no go. Bootloader reads:
key drivers not found... booting OS
android cardhu-user bootloader <1.00 e> released by "US_epad-10.6.1.27.5-20130902" A03
Starting fastboot USB download protocol
When i try fastboot devices, it returns nothing. if i try any fastboot commands it hangs on waiting for device. Any help? Thanks.

i have the same problem, waiting for any suggestion/help. If you figure out the problem please let me know

Well still no luck so far. I ahave even tried downgrading to 10.4.2.20 and no dice.

hmm maybe try to reinstall USB drivers on your computer, try different USB cable / port on computer

I believe it has something to do with the drivers. I have noticed ADB only works when i have ASUS PC Sync program running in the background on the PC. If I uninstall it or close the app ADB stops working. I have tried using the naked universal drivers and the stand alone ASUS drivers that are on here and neither of them seem to work for me either in fastboot or ADB. If only i could remember how i use to do it, but i have been away from ASUS products for over a year now..

All right, so i figured out what was going on with my fastboot and it was such a simple thing. After nothing else was working that i could find online i did find one command line that made me think of something and it worked. I looked at my ADB version vis the adb version command. I was on version 1.09. I thought it was a bit out of date but should work since it worked with my tf300 before the screen broke and it sat on a self and with my tf700 before it was stolen, heck it still worked now with my HTC One M8. But i deleted my adb and fastboot folder, installed android SDK and the newest platform tools and tried it. It works!!! So in the end i just needed to update my ADB and fastboot files. I hope this helps some other people with this issue since i saw a lot of post about it and a few solutions but here is a new possible solution.

need bootloop help please

So far I always found answers to all my questions here without ever asking. This forum is awsome! Thanks to everyone here doing good work!
My problem: I have the European version of the Honor View 10. I opened bootloader, I installed the Magisk correctly with the 15.4 version, worked all fine. (thank you topjohnwu)
Then MY mistake ... I wanted to install Xposed Installer. I was not concentrated that moment and took the wrong version! From my other Honor phone (android 6.0, version 89, arm64). Absolutely stupid!
Phone restarted ... bootloop ... and goes into eRecovery. I tried everything I could there, clear dalvik cache, factory reset. > no change!
Then I thought ok, connect to PC, safe mode ... adb ... but no success. adb devices brings no result. PC does not find my phone anymore. I hoped I could get into my phone by connecting with PC, but it seems I am unable. So I can not help myself this way.
Next try was to force the phone to update with SD card. I only found asian update software, but I already did not care. I want to save my phone. Update starts, but after 5% it stops, update fail.
Now I hope that someone here can help. I have no idea what else I could do. Best regards, Markus

mark_at said:
So far I always found answers to all my questions here without ever asking. This forum is awsome! Thanks to everyone here doing good work!
My problem: I have the European version of the Honor View 10. I opened bootloader, I installed the Magisk correctly with the 15.4 version, worked all fine. (thank you topjohnwu)
Then MY mistake ... I wanted to install Xposed Installer. I was not concentrated that moment and took the wrong version! From my other Honor phone (android 6.0, version 89, arm64). Absolutely stupid!
Phone restarted ... bootloop ... and goes into eRecovery. I tried everything I could there, clear dalvik cache, factory reset. > no change!
Then I thought ok, connect to PC, safe mode ... adb ... but no success. adb devices brings no result. PC does not find my phone anymore. I hoped I could get into my phone by connecting with PC, but it seems I am unable. So I can not help myself this way.
Next try was to force the phone to update with SD card. I only found asian update software, but I already did not care. I want to save my phone. Update starts, but after 5% it stops, update fail.
Now I hope that someone here can help. I have no idea what else I could do. Best regards, Markus
Click to expand...
Click to collapse
Did you already try ro flash ramdisk and system sith stock images via fastboot?

alohahe3000 said:
Did you already try ro flash ramdisk and system sith stock images via fastboot?
Click to expand...
Click to collapse
I would flash anything ... if I could! That is my problem at the moment and I can not solve it.
When I start phone I get into Huawei eRecovery after two tries to boot > does not help!
When I connect to PC > phone gets not detected! (during boot try it gets connected shortly ... but then gets disconnected after some seconds, in between I can not get into phone via PC)
So when I would want to use fastboot .... not possible because of that issue. I tried to connect in fastboot mode ... but no difference. Actually I do not understand why I can not connect to PC anymore!
The only way I can imagine now is flash or update something via SD card. I tried with asian update.zip, but it will only go to 5% .... and then ends.
But to be honest ... I am not very optimistic about finding any solution. I think only some very smart pro from this site might have an idea. But not sure if these guys read questions about bootloops.

mark_at said:
Next try was to force the phone to update with SD card.
Click to expand...
Click to collapse
Try to flash via Fastboot the stock rom... do a full wipe and reboot.
here the link to the stock ROM:
https://mega.nz/#!W9hjiTgZ!_ZGq7V83bkWPF_Ue7_c41wVXNrQ_YjnsQUxRS0_MevU

Taobaibai said:
Try to flash via Fastboot the stock rom... do a full wipe and reboot.
Click to expand...
Click to collapse
Thanks for the link. But how can I flash via fastboot when my phone is not detected from the PC? That is my main problem at the moment!
That is why I wrote about all things I had tried already. And being unable to connect to the computer is really worrying me!
"adb devices" will not find my phone!

mark_at said:
Thanks for the link. But how can I flash via fastboot when my phone is not detected from the PC? That is my main problem at the moment!
That is why I wrote about all things I had tried already. And being unable to connect to the computer is really worrying me!
"adb devices" will not find my phone!
Click to expand...
Click to collapse
You have to boot into fastboot modus. When booting, push power and Volume down button. A white screen appears if device is connected with PC.
Then try "fastboot devices". If your device is displayed, you can flash with "fastboot flash" system image. Stock system.img download link can be found in AOSP thread, second post.

alohahe3000 said:
You have to boot into fastboot modus. When booting, push power and Volume down button. A white screen appears if device is connected with PC.
Then try "fastboot devices". If your device is displayed, you can flash with "fastboot flash" system image.
Click to expand...
Click to collapse
Exactly
alohahe3000 said:
Stock system.img download link can be found in AOSP thread, second post.
Click to expand...
Click to collapse
Or just use my link. I copied it from the AOSP Thread

I managed to get my phone displayed when I entered fastboot devices.
And I managed to flash the img!! Hurra !!
Thank you very very much to everyone here helping me ...
I thought that nothing would work because when I typed "abd devices" nothing happened. But when I typed "fastboot devices" the phone was there.

mark_at said:
I managed to get my phone displayed when I entered fastboot devices.
And I managed to flash the img!! Hurra !!
Thank you very very much to everyone here helping me ...
I thought that nothing would work because when I typed "abd devices" nothing happened. But when I typed "fastboot devices" the phone was there.
Click to expand...
Click to collapse
It wasn't so difficult.
Viel Spaß mit dem Smartphone!!!

one more thing I have to add:
after flashing the system.img from the link above .... I have FRP lock .... that was not before.
does it mean I have to relock my bootloader and then unlock it once again? In some other thread I found that information.

mark_at said:
one more thing I have to add:
after flashing the system.img from the link above .... I have FRP lock .... that was not before.
does it mean I have to relock my bootloader and then unlock it once again? In some other thread I found that information.
Click to expand...
Click to collapse
and now I relocked bootloader .... and guess what? bootloop again ... and I can not unlock it again, because I did not think about enable OEM unlock! It says necessary to unlock FRP before.
I am terribly sorry for being such an idiot!!

mark_at said:
and now I relocked bootloader .... and guess what? bootloop again ... and I can not unlock it again, because I did not think about enable OEM unlock! It says necessary to unlock FRP before.
I am terribly sorry for being such an idiot!!
Click to expand...
Click to collapse
Never ever relock bootloader untill you have a backup plan. We have dload method till emui 7 buut not sure on EMUI 8 so can't suggest you anything at the moment. Someone played with EMUI 8 can guide you through it.

I understand that I was not allowed to relock bootloader! I feel awful and stupid about it ... believe me!

I was able to erase FRP with HCU client from DC Phoenix.
After that I was in phone again
And afterwards I could open the bootloader again.
Halleluja!!
Thanks for everyone's help here ...