Hi everybody !
(Im french Tf300 user , sorry for my bad english =) )
To start:
10 hours ago i did the new JB 4.2 update by fastboot , because my device is unlocked .
After operation done , i reboot the device , but , here , impossible to reboot , just a black screen ,no asus logo or recovery or bootloader menu , nothing .
But my computer recognize the device only in APX , no fastboot ..
So , I was bricked my device or not ?
There are any way to unbrick ?
I must send my device to Asus support ?
Help me , I need my device for school !
Thx
What file did you flash by fastboot, zip or blob? Did you reboot by power or fastboot 0x0B05 reboot? It's looking like unrecoverble brick.
Dirt-diver said:
Hi everybody !
(Im french Tf300 user , sorry for my bad english =) )
To start:
10 hours ago i did the new JB 4.2 update by fastboot , because my device is unlocked .
After operation done , i reboot the device , but , here , impossible to reboot , just a black screen ,no asus logo or recovery or bootloader menu , nothing .
But my computer recognize the device only in APX , no fastboot ..
So , I was bricked my device or not ?
There are any way to unbrick ?
I must send my device to Asus support ?
Help me , I need my device for school !
Thx
Click to expand...
Click to collapse
At this time apx is useless unless you installed nvflash while on ICS.
The three ways to recover are recovery (stock, twrp, or cwm), fastboot, or adb.
You can try adb from your black screen. - adb devices and if you get all zeros or serial # adb is working.
The bootloader is different on 4.2. From left to right; RCK which left without pressing any keys will automatically go into fastboot (watch the screen). Android = boot into system. And last Wipe Data = do not use this.
For how to get into the bootloader see my signature for a link on the options to get into the bootloader.
I forgot pressing up volume on RCK enters recovery.
Good Luck!
I try Adb devices , but , they say :List of attached devices , and nothing other command .
Sometimes in computer , there recognize : "Unknown devices " or APX mode ..
Dirt-diver said:
I try Adb devices , but , they say :List of attached devices , and nothing other command .
Sometimes in computer , there recognize : "Unknown devices " or APX mode ..
Click to expand...
Click to collapse
The Devices command doesn't work with the TF300T in either adb or fastboot. Try to reboot using fastboot; that will confirm that you've got a working connection. Not sure what the precise command parlance is but I've seen it in these forums.
hgoldner said:
The Devices command doesn't work with the TF300T in either adb or fastboot. Try to reboot using fastboot; that will confirm that you've got a working connection. Not sure what the precise command parlance is but I've seen it in these forums.
Click to expand...
Click to collapse
My mileage varies as does many others. Both adb devices and fastboot devices work properly on this tablet if everything is properly installed and configured.
Forget APX at this time it is useless for you!
Thank you for your answer !
I can't reboot to fastboot , because when i try it , there nothing on the screen , only blackscreen , no light no logo nothing..
No light? When are you plugging tablet, is light on power key?
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
Dirt-diver said:
Thank you for your answer !
I can't reboot to fastboot , because when i try it , there nothing on the screen , only blackscreen , no light no logo nothing..
Click to expand...
Click to collapse
Look at my signature and click the link for info to get into the bootloader. At this point it appears your only out.
I try too... but nothing , only way .. back to asus.. i have the warranty i bought the device in january 2013 but i'm unlocked .
Related
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
AdvanceArg said:
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
Click to expand...
Click to collapse
PC operating system?
Drivers for fastboot and adb loaded?
Look at my signature about universal naked drivers.
Also about getting into your bootloader menu.
APX will be useless to restore.
tobdaryl said:
PC operating system?
Drivers for fastboot and adb loaded?
Look at my signature about universal naked drivers.
Also about getting into your bootloader menu.
APX will be useless to restore.
Click to expand...
Click to collapse
W7 x64
Used exactly those naked drivers.
Cant access to bootloader.
AdvanceArg said:
W7 x64
Used exactly those naked drivers.
Cant access to bootloader.
Click to expand...
Click to collapse
Did you actually use the link to attempt the bootloader access?
Did the drivers properly install?
Do you have an sdcard for this tablet?
tobdaryl said:
Did you actually use the link to attempt the bootloader access?
Did the drivers properly install?
Do you have an sdcard for this tablet?
Click to expand...
Click to collapse
i installed ADB Interface Drivers, but i cant Android Bootloader Interface Driver because 'vol down + up + power' doesnt work.
AdvanceArg said:
i installed ADB Interface Drivers, but i cant Android Bootloader Interface Driver because 'vol down + up + power' doesnt work.
Click to expand...
Click to collapse
I'll assume that means all ten methods to get into the bootloader failed.
If the adb drivers installed we may have a chance.
You didn't say about the sdcard.
At the moment are you still stuck in apx or bootlooping.
Sorry but I need a place to begin.
tobdaryl said:
I'll assume that means all ten methods to get into the bootloader failed.
If the adb drivers installed we may have a chance.
You didn't say about the sdcard.
At the moment are you still stuck in apx or bootlooping.
Sorry but I need a place to begin.
Click to expand...
Click to collapse
i have a sd, it doesn't have info [isn't from tf300, it doesnt came with]. When i introduce it into eeepad i can't access the storage from windows.
I can only interact with the tablet when i turn it on with VOLUP + POWER then is when windows ask me for drivers, now i have installed ADB drivers.
sorry for all dude. And thanks.
AdvanceArg said:
i have a sd, it doesn't have info [isn't from tf300, it doesnt came with]. When i introduce it into eeepad i can't access the storage from windows.
I can only interact with the tablet when i turn it on with VOLUP + POWER then is when windows ask me for drivers, now i have installed ADB drivers.
sorry for all dude. And thanks.
Click to expand...
Click to collapse
No problem we just need to get a starting place and have as much in our favor as possible.
I don't believe adb works in apx mode but we'll give it a shot.
No sdcards come with the tablet.
Go into apx mode (volume + power).
Go to your adb folder with cmd and type
adb devices - press return or enter
If it is working we should get your serial number in return.
Now get out of apx mode.
type
adb devices - do not press return yet
watch your unit and when the screen goes black and before it lights(rebooting) now press return
Tell me what is returned each way.
tobdaryl said:
Go into apx mode (volume + power).
Go to your adb folder with cmd and type
adb devices - press return or enter
If it is working we should get your serial number in return.
Now get out of apx mode.
type
adb devices - do not press return yet
watch your unit and when the screen goes black and before it lights(rebooting) now press return
Tell me what is returned each way.
Click to expand...
Click to collapse
No serial. only ''List of devices attached''
Tried with Asus Trasnformer Prime APX Interface [naked drivers] and ADB drivers.
AdvanceArg said:
No serial. only ''List of devices attached''
Tried with Asus Trasnformer Prime APX Interface [naked drivers] and ADB drivers.
Click to expand...
Click to collapse
[FONT=TimesNewRomanPSMT, serif]Download 10.4.2.9 JB from this thread post #3[/FONT]
[FONT=TimesNewRomanPSMT, serif]unzip once and you should still have a zip if you get a blob then do not unzip.[/FONT]
[FONT=TimesNewRomanPSMT, serif]rename to EP201_768_SDUPDATE.zip and copy to sdcard and place sdcard into your tablet.[/FONT]
[FONT=TimesNewRomanPSMT, serif]Power tablet and hope![/FONT]
nothing. Renamed US_epad-user-10.4.2.9 to EP201_768_SDUPDATE.zip, throwed it into sd and turned tablet on. Stuck on ASUS logo.
AdvanceArg said:
nothing. Renamed US_epaduser_10_4_2_9_UpdateLauncher.zip to EP201_768_SDUPDATE.zip, throwed it into sd and turned tablet on. Stuck on ASUS logo.
Click to expand...
Click to collapse
I have some bad news for you.
Without adb or fastboot access I don't know of anything else to be done.
If you could have gotten into the bootloader menu we would have had a chance.
Maybe someone else will read this thread and have more ideas.
I'm sorry.
Good Luck!
same problem here. i have a tf300t and can only access apx interface.
I got into this mess, after by "accident" choosed the "wipe data" option present on the bootleader.
!! adb, fast boot do not work!! "power key + down button" dont do anything!
i'm getting a bit resteless because no matter were i search on the web i can not find anything suitable on how to resolve this issue...
there are some youtube videos that show a solution for tf100. it seems the same problem.
http://www.youtube.com/watch?v=CwvfNIHCYlQ
there is also a tool for tf100, called easy flasher. to bad it does not work for tf300t
http://forum.xda-developers.com/showthread.php?t=1688012
i think it is a question of seaching and waiting. someone will help and get or point to a solution. because if we google for tf300t bricked that are lots and lots of links stating this issue...
what a mess...
AdvanceArg said:
Hi, good people. I have bought a TF300T bricked last week, the old user has stock OS, tried to root and failed.
Now im fighting with that. When i turn on the tablet, it stuck at 'The Device is Unlocked' with Asus n' Nvidia Logo, after a minutes it reset and keeps in a constant loop.
I tried to recovery [vol down etc etc] and no effect, i tried with a few of tutorial and nothing.
I connected the tablet via APX [VOL UP + power]. PC recognized it but i stucked in this. Tried to fastboot and stays in 'waiting device'
Someone with ideas? Thanks frr all and sorry for the inconvenience.
Click to expand...
Click to collapse
Do you see anything after resetting by holding volume down and the power button? If you can get the tablet into fastboot mode you may able to revive it. If you can, ask the previous owner which version stock Android he was running before he tried to root it (it matters!).
This method worked for me!
Link to my thread ---> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps guys. Good luck!
hi
please someone help me :crying::crying::crying:
these steps that i made before i asking for help
1. unpacked and got it with latest firmware 10.4.3.9
2. unlocked with asus official tool from asus support website
3. root by http://forum.xda-developers.com/showthread.php?t=2013792
4. device rooted successful and worked perfect
5. installed titanium backup and restored my apps from nexus 4
6. rebooted and continue work perfect
7. uninstalled asus stock apps and rebooted OK
8. at one moment battery discharged and device turned off
9. after hour of charging device booted and stuck on asus logo
now my problems
1. can't boot in any mode (pwr+vol down just restart device)
2. pc (xp, 7 x64, 7 x86) not recognize device
3. in apx mode (pwr+vol up) device manager see device and with Universal Naked Driver 0.72 seems ok
4. adb and fastboot = device not found
5. wheelie --blob blob.bin
Waiting for device in APX mode...
[=] Chip UID: 0x15d456d1557fa16
[-] Failed to read RCMVERS from blob file.
device one day old, and i too tired to continue read millions of forums with many solutions. all them starting with "fastboot" and fastboot can't see device....
so please anyone help me !!!
or maybe my asus tf300tg already in tablets heaven ?
thanks for any help !
hopes die last !
only thing I can guess if you still have the stock Recovery is trying the reset button on the left side under the external sd slot. But this can make it worth.
What exactly to do with reset button ?
Sent from my Nexus 4 using xda app-developers app
petition
Seems that you got a same problem as many others ( hundreds ) and as me too. If you are not able to access the bootloader but still have access only in APX mode than your device is soft bricked. To recover it is necessary to access the nvflash ( which is restricted by Asus) and rewrite the bootloader. To get access from Asus is posted an open petition here: http://forum.xda-developers.com/showthread.php?t=2119533 . Sign it and pray......
Sorry mate.
rhc94 said:
hi
please someone help me :crying::crying::crying:
these steps that i made before i asking for help
1. unpacked and got it with latest firmware 10.4.3.9
2. unlocked with asus official tool from asus support website
3. root by http://forum.xda-developers.com/showthread.php?t=2013792
4. device rooted successful and worked perfect
5. installed titanium backup and restored my apps from nexus 4
6. rebooted and continue work perfect
7. uninstalled asus stock apps and rebooted OK
8. at one moment battery discharged and device turned off
9. after hour of charging device booted and stuck on asus logo
now my problems
1. can't boot in any mode (pwr+vol down just restart device)
2. pc (xp, 7 x64, 7 x86) not recognize device
3. in apx mode (pwr+vol up) device manager see device and with Universal Naked Driver 0.72 seems ok
4. adb and fastboot = device not found
5. wheelie --blob blob.bin
Waiting for device in APX mode...
[=] Chip UID: 0x15d456d1557fa16
[-] Failed to read RCMVERS from blob file.
device one day old, and i too tired to continue read millions of forums with many solutions. all them starting with "fastboot" and fastboot can't see device....
so please anyone help me !!!
or maybe my asus tf300tg already in tablets heaven ?
thanks for any help !
hopes die last !
Click to expand...
Click to collapse
How did you take a blob.bin????
atoma1972 said:
Seems that you got a same problem as many others ( hundreds ) and as me too. If you are not able to access the bootloader but still have access only in APX mode than your device is soft bricked. To recover it is necessary to access the nvflash ( which is restricted by Asus) and rewrite the bootloader. To get access from Asus is posted an open petition here: http://forum.xda-developers.com/showthread.php?t=2119533 . Sign it and pray......
Sorry mate.
Click to expand...
Click to collapse
yeah m8 same as me from 2 days now your soft briked and nothing else to do but w8t or send it to asus and be charged for the repair.
Sign the petition and maybe wer in luck some day not to far.....
Hi guys,
i have a tricky problem.
I bought a used nexus S, without any hope to recover it.
This is the state at the moment (after installed SDK and drivers).
I think the device is in his standard state (all locked up, never rooted, stock rom)
It boot up and ask for a password to encrypt device (works : volume and emergency call).
If i connect usb, he tries to mount USB storage but he dosen't success.
I connect to pc and pc see an Android ADB device in the devices list.
BUT if i lauch 'adb devices' i dont see anything.
I start it in bootloader mode (Vol Up + Power) ... it starts.
BUT Vol Up and Vol down didn't work. I can only press power and return again in bootloader. (volume work if i normally boot)
In bootloader state i tried 'fastboot devices' and i didn't see any device.
So the state is :
Bootloader i think "broken" (volumes dosen't work and fastboot dosen't see device)
Debug usb disabled (adb don't see my device)
Device encrypted
Any idea ?
I think is a nice problem to let your brain works on :laugh::laugh:
Thanks in advice.
Daniele
Hey guys, there is anybody out there ?
I dont think that no one could try to solve this problem.
Thanks
Do you have the drivers installed onto your PC? You will need to get the adb drivers and fastboot drivers. Download Samsung Kies and that will take care of your ADB drivers. Click here: http://www.mediafire.com/download/5a7gou9droidi53/drivers.rar for your fastboot drivers. Hope this helps.
I've already installed drivers.
But i will give a try to the ones you linked.
Thanks you.
sirhaplo said:
I've already installed drivers.
But i will give a try to the ones you linked.
Thanks you.
Click to expand...
Click to collapse
I'd suggest just booting Linux and doing whatever you need to do in there.
The kernel already supports communicating with the Nexus S, no need to mess with drivers like on Windows.
Hello everyone , i have an issue , i had custom room on my phone. I wanted to install another custom ROM so i cleared cache i think i deleted something that i didnt need to delete when i was using TWRP recovery , after i cleared cached i restarted the phone and now its not booting anywhere not boot loader not recovery nowhere it just stuck on HTC quite brilliant screen (with htc warning message about that it is for developers only version)
please help
I tried pluging in to computer cmd commands fastboot just saying waiting for device , some tool kits also can't get in touch with device
when i power it on computer does have usb sound but i dont see any device in the list , i have feeling that it eject its as soon as it connect to it.
Phone is unlocked rooted ,but its s-on
Please help!!!
lins_nt said:
Hello everyone , i have an issue , i had custom room on my phone. I wanted to install another custom ROM so i cleared cache i think i deleted something that i didnt need to delete when i was using TWRP recovery , after i cleared cached i restarted the phone and now its not booting anywhere not boot loader not recovery nowhere it just stuck on HTC quite brilliant screen (with htc warning message about that it is for developers only version)
please help
I tried pluging in to computer cmd commands fastboot just saying waiting for device , some tool kits also can't get in touch with device
when i power it on computer does have usb sound but i dont see any device in the list , i have feeling that it eject its as soon as it connect to it.
Phone is unlocked rooted ,but its s-on
Please help!!!
Click to expand...
Click to collapse
UPDATE!!!!!!!!!!! when i power phone off computer does see the device via usb port
lins_nt said:
UPDATE!!!!!!!!!!! when i power phone off computer does see the device via usb port
Click to expand...
Click to collapse
You Can delete this post i got it fixed
lins_nt said:
You Can delete this post i got it fixed
Click to expand...
Click to collapse
Please tell my how you fixed ??
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 ...