Bricked Asus ME301T - Transformer TF300T Q&A, Help & Troubleshooting

Messed up big time and have surely bricked my device (permanently). Was trying to install Omni ROM on it. (Had it rooted, unlocked it, couldn't enter recovery then, kept getting error. tried to flash TWRP recovery 2.6.3.0 using terminal on tab, reset the tab, and we get where i am now)
Now all i get when i switch on my tab is an ASUS start screen with "The device is unlocked" message on the top left, and it just stays there. Same thing happens when start it with hold power button and volume down key or reset and volume down key. But when i press reset and volume UP key, the pc recognizes the tab, and i can install the driver either as:
1. ADB interface
2. Bootloader interface
3. Composte ADB interface
and the device comes up as an APX.
Tried to follow Buster99's method (of unbricking for TF300T) after the device drivers are installed, but all i get is <waiting for device>
Any hope of recovering it or am i really fckd.

true_lies said:
Messed up big time and have surely bricked my device (permanently). Was trying to install Omni ROM on it. (Had it rooted, unlocked it, couldn't enter recovery then, kept getting error. tried to flash TWRP recovery 2.6.3.0 using terminal on tab, reset the tab, and we get where i am now)
Now all i get when i switch on my tab is an ASUS start screen with "The device is unlocked" message on the top left, and it just stays there. Same thing happens when start it with hold power button and volume down key or reset and volume down key. But when i press reset and volume UP key, the pc recognizes the tab, and i can install the driver either as:
1. ADB interface
2. Bootloader interface
3. Composte ADB interface
and the device comes up as an APX.
Tried to follow Buster99's method (of unbricking for TF300T) after the device drivers are installed, but all i get is <waiting for device>
Any hope of recovering it or am i really fckd.
Click to expand...
Click to collapse
Shoot me an email here [email protected]
Lets see if we can get you fixed up....
Thx Josh

lj50036 said:
Shoot me an email here [email protected]
Lets see if we can get you fixed up....
Thx Josh
Click to expand...
Click to collapse
My ME310T is bricked as well and I am not sure of what to do since using the pin hole to reset does not work.
It kept booting to the ASUS logo and I downloaded software from the ASUS site and put on my SD card and tried to load the new firmware/software. Now I only get a green android on his back with a red brick.
Please help, thanks

My ME310T
Bricked mine last night My ME310T, accidentally did the wipe from the Bootscreen with the RCK ,, now i tried everything i could find , ADB, Nvflash, power+ Vol - ( no go) reset + vol- nogo, only can get it to Vol+ and APX. All i get is the Boot unlocked in upper left , and Asus Innovation.. or blank screen with APX .. Any help would be great ,,,

thsire said:
Bricked mine last night My ME310T, accidentally did the wipe from the Bootscreen with the RCK ,, now i tried everything i could find , ADB, Nvflash, power+ Vol - ( no go) reset + vol- nogo, only can get it to Vol+ and APX. All i get is the Boot unlocked in upper left , and Asus Innovation.. or blank screen with APX .. Any help would be great ,,,
Click to expand...
Click to collapse
When do you get adb ?

lj50036 said:
When do you get adb ?
Click to expand...
Click to collapse
If you mean what do i get? , just hangs with blinking curser ,,,, i think im total bricked only can get APX mode..

thsire said:
If you mean what do i get? , just hangs with blinking curser ,,,, i think im total bricked only can get APX mode..
Click to expand...
Click to collapse
So no bootloader no recovery just APX ?
That is to bad, sorry to here that.
Thx Josh

Omnirom on ME301T,
Hi,
I have a working ME301T with the latest (yesterday!) Omnirom on it, but......
I broke the glass when I was opening the device to replace a broken speaker.
I found (google is my friend) that these broken speakers cause a crash or reboot every now and then, the rubber comes loose, then the winding cause a short circuit when playing music, that crashes the unit.
So if you want to take your speaker and screen, and use our electronics, you have a working unit again.
Send me a PM with an offer if you are interested.
Un saludo from Spain,
Satbeginner

bricked me301t
Im in need of some help i have an unlocked and rooted me301t went to do a factory reset from the stock recovery screen and when it rebooted all i get is the asus screen and your device is unlocked in the upper left corner. Tried to boot into recovery wont do anything except the asus screen . Tried to put firmware on my sd card but dont know the sku because i cant get to it. can anyone help me to recover this thing and get it working again?/ Thanks in advance..
ps running stock 4.2 and stock recovery or was when it worked. LOL

Related

[Q] I need help! My TF got stuck and can't boot into recovery!!!

My Tf got stuck at the logo Eee Pad boot after I tried to restore the old rom, and now it can't do anything except boot and stuck at the logo.
I tried the nvflash unbricking technique from rayman84 : http://forum.xda-developers.com/showthread.php?t=1123429
, but my TF only listed as unknown device when I tried to get to APX mode and it also said,
"This device is disabled because the firmware of the device did not give it the required resources. (Code 29)"
Now I don't know what else to do. Please help! I hope I am not completely bricked the device yet.
Have you tried the button combo to get into recovery?
Press and hold the Vol down + power button.
When prompt, you'll see lines of words at the top left of the screen, push the Vol up button immediately within 5 sec to get into recovery.
Apparently, I didn't know the button combo. Anyways you save my niece's TF. Thanks a bunch
Edit: although the tablet is working now, it still got the message usb unknown device. Do you know how to fix it?
Hi, i don't know if i should post a new thread but my problem is almost the same as bengob3t's one.
I have a brand new TF101 with a B70 Serial number, but i successfully rooted it using the RazorClaw Tool. Then i tried to install clockwork mod followin this topic : http://forum.xda-developers.com/showthread.php?t=1106587
I directly applied the instructions from step 8 (download hashmyfiles etc...) and i rebooted my Eee pad manually step 13
I didn't see any progress bar, but my device is stuck on the Asus screen, and the speakers make stange noises at regular intervals.
I am able to go into recovery though (power + vol down then vol up) but the factory reset doesn't work, and i cant really do anything (at least not anything that i know what it is).
Is my tablet definitely bricked ? If not, how can i bring it back to life ?
I wasn't able to use NVFlash, as i can't seem to go in APX mode. I press power+vol up, i hear the sound usb device connected and immediately after i hear the sound "usb device disconncted"
Nvflash says
"Nvflash started
rcm version 0X4
Command send failed (usb write failed)"
Thanks in advance for your help.
EDIT : When i put the micro sdcard from my phone into the tablet, i am able to mount it. So i will probably be able to flash something from it, but what ? Do i have to flash a recovery ? Directly a custom rom ?
I'm a little lost, but i'll try to give you guys as mush info as i can find.
EDIT2 : I flashed the PRIME rom, everything seems to be back to normal... if you got info on my situation, don't hesitate to fill me in ^^ i'd like to understand what i did wrong, even though i dodged the bullet.
bengob3t said:
Apparently, I didn't know the button combo. Anyways you save my niece's TF. Thanks a bunch
Edit: although the tablet is working now, it still got the message usb unknown device. Do you know how to fix it?
Click to expand...
Click to collapse
Do you have the correct driver installed? Do you have Asus sync install on your PC?
hmm.. I'm not sure. I downloaded the unbricked tool nvflash file, and the tool already had usb driver inside it. Is that the driver you were talking about? I never were able to get to the point where I need to point the APX to where the driver located because it always said unknown driver the whole time.

Broken CWM

I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
If you can boot to OS - you can use fastboot to flash any recovery.. or flash TWRP from goomanager.
upd: sry..don't see about "stuck".
abe_cedar said:
I have flashed the CWM from TF201 by accident. Now the tablet is stuck in that CWM mode. I can't connect to usb using adb mode. Power+volume down does not work anymore. Any way I can reflash the correct CWM?
THanks
Click to expand...
Click to collapse
I have made the same mistake. Although I can get the device to fastboot USB mode. I have tried to use CWM with the restore I made before I put in Cyanogenmod 9, as well as putting on the Cyanogenmod experimental #2 for TF300. No error messages at all and it wipes data and cash without any problems.
But I get locked on the Asus boot screen and it does not continue ie I am stuck as well.
I have as well tried to use the TWRP 2.1.5. I get the Teamwin loggo screen, it wipes all the data and verifies all the filesystems and reboots. Still stuck.
Is the device bricked ?
upd:The TF300 can not be shutoff either. When you hold the power button the screen goes black, but after ~5 s the device is starting again and is still stuck on the Asus bootup screen.
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
cheedear said:
if you reboot it holding vol down and power, can you get back into the boot menu, to reselect fastboot?
if holding the power button doesn't switch it off, what happens if you leave it to run out of batteries then do this?
then you can flash the correct recovery.img
Click to expand...
Click to collapse
Yes, I can get access to the fastboot and I have already tried to flash with the recovery.img. I have as well let the battery run out and tried it once more with the same result.
Still stuck on the asus bootup screen.
power
Hare,
I have same problem.tab cannot power off. Just reboots into cwm.
I was thinking to drain bat. Thanks for sharing that info.
There are a lot of topics about people who broke their devices with TF201's recovery.
Afaik, no one recovered it. Send to Asus.
So the device is bricked then :'(.
Thanks for clearing it up.
Sent from my GT-I9100 using XDA
RMA..
Guillaume,
Thanks for clarification.
I have read that ASUS wants 700USD for replacing/reflashing the bootloader. That was for the tf201. Any way to nvflash it back to factory? I don't believe that they have to change the MB.
I have no warranty left, but I don't want to be gouged by them either.
Any thoughts, info?
Hi,
I've do the same mistake, but I can use adb.
Do youhave any news about our problem?
Thanks
Midyr
unable to power off
My issue is that I have the CWM for the tf201. I did the update from the CWM app in Android. Bad idea. So now the tab does not power off s.t. I can get into the power+vol down mode. Adb does not work since I cannot ( don't know how) to make it go into the usb debugging mode. I have tried several things none of which have worked. Still stuck.
I wanted some feedback for a RMA from ASUS, posted it here but sor far no answers.
Not sure if it would really work, but on my Evo, I don't have to completely power off the phone to do the recovery sequence. I can do it during a normal reboot. There is a point just before the device starts booting again where it is technically "off", and if I hold volume down (don't even have to hold power on my Evo; volume down seems to be the only necessary button) starting at this point, the phone will boot into the bootloader.
So, next time the device reboots, just start holding volume down (possibly power also, just in case) at the "off" point.

[Q] HELP>>>>>>>Bricked my TF300T

Hi All..
My TF300 is unlocked. I installed the new JB and then I was trying to install CWM. I used fastboot to push it to the device. When I rebooted, holding down the volume button, It came up to the menu with RCK, USB, etc. I selected wipe data by accident. It sat there for a while saying it was going to wipe and go into the boot loader. After a while I shut it off thinking it was hung. Now when I power on the device I get only the ASUS startup screen. Volume up or down don't affect the mode. It just says "The Device is Unlocked" at the top, and the static ASUS logo in the middle. When I plug in the USB to my Windows 7 computer I get nothing in the device listing. I can't even fully turn the device off. Holding power for a few seconds, it goes off, and then it comes right back on by itself.
I think I'm totally bricked, right? It won't even go into APX mode it appears.
thanks ...
arch.fadi said:
Hi All..
My TF300 is unlocked. I installed the new JB and then I was trying to install CWM. I used fastboot to push it to the device. When I rebooted, holding down the volume button, It came up to the menu with RCK, USB, etc. I selected wipe data by accident. It sat there for a while saying it was going to wipe and go into the boot loader. After a while I shut it off thinking it was hung. Now when I power on the device I get only the ASUS startup screen. Volume up or down don't affect the mode. It just says "The Device is Unlocked" at the top, and the static ASUS logo in the middle. When I plug in the USB to my Windows 7 computer I get nothing in the device listing. I can't even fully turn the device off. Holding power for a few seconds, it goes off, and then it comes right back on by itself.
I think I'm totally bricked, right? It won't even go into APX mode it appears.
thanks ...
Click to expand...
Click to collapse
When you hold down the power button to turn it off, as soon as the screen goes off, let go of the power button and hold the VOL up button. Wait a second or so and then let go of the VOL button. The tablet should go into APX mode. It can be quite hard to time it right, but the tablets screen should stay blank, without rebooting.
thanks for ur care
i forget to update the post ...sorry
.....i do that and my pc show apx driver but fastboot did not work ....
how can i use fastboot again to install bolb again ?????????
thanks in advance
chappie1970 said:
When you hold down the power button to turn it off, as soon as the screen goes off, let go of the power button and hold the VOL up button. Wait a second or so and then let go of the VOL button. The tablet should go into APX mode. It can be quite hard to time it right, but the tablets screen should stay blank, without rebooting.
Click to expand...
Click to collapse
thanks for ur care
i forget to update the post ...sorry
.....i do that and my pc show apx driver but fastboot did not work ....
how can i use fastboot again to install bolb again ?????????
thanks in advance
ME Too and hundreds of Others
arch.fadi said:
thanks for ur care
i forget to update the post ...sorry
.....i do that and my pc show apx driver but fastboot did not work ....
how can i use fastboot again to install bolb again ?????????
thanks in advance
Click to expand...
Click to collapse
I've been searching the web for two weeks - nobody has a solution !
I've tried everthing.
Asus has a way to reset the OS as several owners have sent their unlocked "Bricked" tablets to their service center.
Last repair I read online stated that Asus returned their TF300T with the latest version of JB installed.
Asus would be Wise to post a solution - Imagine the goodwill that would generate.
Many thanks...
Q:did asus change mother board?
Or it kind of software fixed
I read about SKB..... What sbk?

Super bricked

I hope I can save it but after 4 hours of trying and reading I can't seem to do it.
I was running an unlocked tf300 with cleanrom. I wanted to update to the newest version of cleanrom and have my tablet on that and ready for school for next term. I downloaded cleanrom on laptop and put it on my micro sd. Went and grabbed the tablet and tried using rom manager to install from sd and backup the os that was on it. Didn't work. So booted into the fastboot spot (vol down and power) and decided i should wipe data since i was there. Went over to that and pushed vol up (once). Let it sit for like 45 minutes and was still on the same screen. Thought to myself well it must be done. Shut off the tablet to restart it.
This is where the problem came up. Now i'm stuck on asus logo. The VD+P doesn't do anything but reboot into the asus logo. The VU+P will put it into a black screen and windows sees it as Asus transformer Prime APX interface. But adb can't see the device. Just device manager. typing fastboot -i 0x0b05 thing just says <waiting for device>
Every post i've read seems to tell people to just push VD+P but if i could do that and get to recovery i wouldn't be doing this. I can't put a blob file into the root sd of the tablet because I can't see the tablet.
Any help would be greatly appreciated.
Maybe this link can help.
http://forum.xda-developers.com/showthread.php?t=2034866
Device manager already sees it as transformer prime apx thing though. So i assume by getting it into APX mode doing the VU+P method it is in apx? or is that not mean it's actually in apx?
bigworm82 said:
Device manager already sees it as transformer prime apx thing though. So i assume by getting it into APX mode doing the VU+P method it is in apx? or is that not mean it's actually in apx?
Click to expand...
Click to collapse
Apx mode is not going to do you any good. The previous link also provides info on blootloader " recovery " mode.
Try the universal naked drivers from this link and try fastboot again.
http://forum.xda-developers.com/showthread.php?t=1766220
If that does not work leave off ' -i 0x0b05 ' in fastboot -i 0x0b05 command and try again.
tobdaryl said:
Apx mode is not going to do you any good. The previous link also provides info on blootloader " recovery " mode.
Try the universal naked drivers from this link and try fastboot again.
http://forum.xda-developers.com/showthread.php?t=1766220
If that does not work leave off ' -i 0x0b05 ' in fastboot -i 0x0b05 command and try again.
Click to expand...
Click to collapse
Already installed the naked drivers and that's when the computer recognized it in the device manager portion as the asus prime apx interface thing. It still just says <waiting for device> in everything i try on fastboot.
bigworm82 said:
Already installed the naked drivers and that's when the computer recognized it in the device manager portion as the asus prime apx interface thing. It still just says <waiting for device> in everything i try on fastboot.
Click to expand...
Click to collapse
Are you in fastboot mode or apx when you give the commands?
tobdaryl said:
Are you in fastboot mode or apx when you give the commands?
Click to expand...
Click to collapse
i just go into cmd and go to the folder i put fastboot and all in and type fastboot..... so on.. what should i do?
bigworm82 said:
i just go into cmd and go to the folder i put fastboot and all in and type fastboot..... so on.. what should i do?
Click to expand...
Click to collapse
I know you previously said you couldn't get into recovery-bootloader menu but that is what we have to accomplish. Apx mode on this unit is only good if you previously installed nvflash and had all of the proper backup files.
The first link I provided provides 9 ways to get into bootloader menu and from there either fastboot mode (usb symbol) or recovery (RCK). I know some may not work but we only need one.
tobdaryl said:
I know you previously said you couldn't get into recovery-bootloader menu but that is what we have to accomplish. Apx mode on this unit is only good if you previously installed nvflash and had all of the proper backup files.
The first link I provided provides 9 ways to get into bootloader menu and from there either fastboot mode (usb symbol) or recovery (RCK). I know some may not work but we only need one.
Click to expand...
Click to collapse
I'm confused the first link is to get into APX mode from how i read it on the page. Am i wrong? I have no issues getting into this mode.
bigworm82 said:
I'm confused the first link is to get into APX mode from how i read it on the page. Am i wrong? I have no issues getting into this mode.
Click to expand...
Click to collapse
apx or bootloader menu-recovery.
To use this guide to enter the bootloader menu just use volume down everywhere it says volume up. Everything else is the same.
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard) reset is located about 25mm or 1in below the sdcard
try this one.
tobdaryl said:
apx or bootloader menu-recovery.
4. with unit powered on hold volume down and press reset with paperclip - (don't press hard)
reset is located about 25mm or 1in below the sdcard
try this one.
To use this guide to enter the bootloader menu just use volume down everywhere it says volume up. Everything else is the same.
Click to expand...
Click to collapse
nope just back to asus logo
bigworm82 said:
nope just back to asus logo
Click to expand...
Click to collapse
use cmd(terminal) in same directory as fastboot
adb reboot then immediately hold volume down
if no help then
adb reboot bootloader - no need for volume on this one
tobdaryl said:
use cmd(terminal) in same directory as fastboot
adb reboot then immediately hold volume down
if no help then
adb reboot bootloader - no need for volume on this one
Click to expand...
Click to collapse
Device not found.
bigworm82 said:
Device not found.
Click to expand...
Click to collapse
Force power off by holding power a few seconds.
Plug power cord into tab with the other end of the power cord not plugged into anything. Hold volume down and plug other end of power cord into pc. This done without pressing power again after it is powered off. Easier to do than describe.
tobdaryl said:
Force power off by holding power a few seconds.
Plug power cord into tab with the other end of the power cord not plugged into anything. Hold volume down and plug other end of power cord into pc. This done without pressing power again after it is powered off. Easier to do than describe.
Click to expand...
Click to collapse
The Problem lies in holding the volume down button. No matter how i turn it on. either plugging it in while holding power down, reset button, letting it die and then plugging it in and turning it on....it just goes into the asus logo screen .
bigworm82 said:
The Problem lies in holding the volume down button. No matter how i turn it on. either plugging it in while holding power down, reset button, letting it die and then plugging it in and turning it on....it just goes into the asus logo screen .
Click to expand...
Click to collapse
I'm sorry, I did understand that from the beginning but the only things that can save you is get into that menu or recovery or your tab accepts a fastboot or adb command. That is the reason you keep getting pushed into that direction.
My best guesses are out. Sometimes redoing something you have already done twice works.
My experience and all I have read rom manager has issues on this tab. Also many who wiped data from the bootloader- recovery menu reach this same point when they reboot.
Some have recovered by just doing each thing again and again and suddenly something works.
Yeah i fear i'm just going to have to call ASUS . sad panda. i keep trying different methods of doing the VD+P method but it just won't get into recovery.
bigworm82 said:
Yeah i fear i'm just going to have to call ASUS . sad panda. i keep trying different methods of doing the VD+P method but it just won't get into recovery.
Click to expand...
Click to collapse
I'm sorry but I am afraid you are correct. If unable to use adb, fastboot, or get into recovery there aren't any other options. Sorry if I pushed more than I should but I wanted to see a more positive result than calling Asus.
Good Luck!
tobdaryl said:
I'm sorry but I am afraid you are correct. If unable to use adb, fastboot, or get into recovery there aren't any other options. Sorry if I pushed more than I should but I wanted to see a more positive result than calling Asus.
Good Luck!
Click to expand...
Click to collapse
I appreciate the attempts though . I really didn't want to have to call them lol.
bigworm82 said:
I appreciate the attempts though . I really didn't want to have to call them lol.
Click to expand...
Click to collapse
If you explain you were having issues with your tab and used wipe data hoping to correct the problem. Now when you turn on it just stays on the asus logo maybe they will repair it without cost.
If you go into detail you probably won't get lucky.

[Q] No Fastboot No Recovery .. Is it dead ?

While i was trying to install the latest official rom to my device (The new Padfone Infinity A86 T004) it is bricked, Now i am facing a very bad (miserable) situation.
When turning on the device it shows me the ASUS logo and in top of the screen a message says : ERROR: Can not boot Invalid boot image!!
And my big problem is that i can't access any of ADB, recovery mode or even fastboot. the phone is undetectable by my PC at all.
I don't know how to force fastboot ... if i can reach the beautiful fastboot mode i will be able to handle the next steps in the fixing journey.
I have red that as long as the device shows something it means that it is not totally bricked .. but how to get out of this situation?
Any suggestions ?
Sorry my englsih is´nt good.
So you can´t broken your phone with OTA Updates
You can delet all files and sysfile and the asus isn´t broken.
you just need patience.
make sure you have the correct driver
turn off your phone,
press vloume up and power, so the phone stay with boot logo, so you are in the fastboot mode.
there you can use my exploit btw the howto downgrade A86, but the downgrade dosent works.
so unzip the newest rom .zip out of asus page....
copy the boot.img and recovery.img in your minimal fast adb folder
so you can:
c:\ADB>fastboot -w ( really wipe all partions and data of your phone!)
c:\ADB\fastboot flash boot boot.img
c:\ADB>fastboot flash recovery recovery.img
copy the complete OTA Update Zip on your phone (internal sd or external is matter)
reboot phone and install the zip out of recovery.
there may be errors come to the first, if that should be the case
then repeat the case up to 3 times
I hope you can read and understand it .
if you need further assistance , please contact me at any time , like even on my homepage lange23.de
BerayekZ said:
While i was trying to install the latest official rom to my device (The new Padfone Infinity A86 T004) it is bricked, Now i am facing a very bad (miserable) situation.
When turning on the device it shows me the ASUS logo and in top of the screen a message says : ERROR: Can not boot Invalid boot image!!
And my big problem is that i can't access any of ADB, recovery mode or even fastboot. the phone is undetectable by my PC at all.
I don't know how to force fastboot ... if i can reach the beautiful fastboot mode i will be able to handle the next steps in the fixing journey.
I have red that as long as the device shows something it means that it is not totally bricked .. but how to get out of this situation?
Any suggestions ?
Click to expand...
Click to collapse
Thank you for your help.
The issue is that the phone now is not detected by the pc at all , i can not access the fast boot ...
Do you really pressed Volume up and Power at the same time, if startet???
If the phone during normal start at the stops bootlogo that's not fastboot!!!
Turn really off an than hold volume up an press Powerbutton, hold it up to boot logo.
then you are really in fastboot mode!
BerayekZ said:
Thank you for your help.
The issue is that the phone now is not detected by the pc at all , i can not access the fast boot ...
Click to expand...
Click to collapse
after turning off
when i press volume up + power button the phone vibrates and the asus logo displayed. then i release power button and keep pressing volume up button => and after 1 second an error appears ERROR: Can not load Invalid boot image!!
when pressing power button + volume down button a menu appears with two options 1.Enter recovery mode and 2.Exit update mode.
when choosing option 1 , the menu disappeared and the asus logo appears without the previous error message.
when choosing option 2 , the the menu disappeared and the asus logo appears and the previous error message.
all these cases the phone didn't go to fastboot mode and never detected by the pc.
when i press volume up + power button the phone vibrates and the asus logo displayed. then i release power button and keep pressing volume up button don´t keep pressing volume up,
fasboot mode only power & up, until the logo. Pressing this two to logo and then left them. the logo sty tuned in display so you re in fastboot
if you pressing up too jump in question menü,
if you pressing at startup power & down jumped directly into question menü, but this menü is wrong for you. you need only fastboot nothing more
BerayekZ said:
after turning off
when i press volume up + power button the phone vibrates and the asus logo displayed. then i release power button and keep pressing volume up button => and after 1 second an error appears ERROR: Can not load Invalid boot image!!
when pressing power button + volume down button a menu appears with two options 1.Enter recovery mode and 2.Exit update mode.
when choosing option 1 , the menu disappeared and the asus logo appears without the previous error message.
when choosing option 2 , the the menu disappeared and the asus logo appears and the previous error message.
all these cases the phone didn't go to fastboot mode and never detected by the pc.
Click to expand...
Click to collapse
keep pressing on volume up button is not jumping in question menü, but shows logo + error message (can not load invalid boot image)
also pressing them to logo then releasing also shows logo + the error message.
i am also uploading a video to youtube to verify..
https://youtu.be/uw4Esyppq_c
and without recovery its right?
And with error message and logo your pc find nothing new unkown devices?
CMCC Composite ADB Interface?
?
BerayekZ said:
https://youtu.be/uw4Esyppq_c
Click to expand...
Click to collapse
Yes, no recovery
And yes PC does not find any new devices
I can not understand it...
I once the boot.img deleted in the phone and also get such error message .
but my systems find an Android device and i can use the fastboot
Any way , a good news that the phone was only few days out of its package and i managed to return it back to the seller and will send to me a new one.
But i am really disappointed with ASUS not to make any unlock tool for the new padfone infinity.
Once, i believed that as long as there is no physical damage in the phone, there will be always a way around to fix it by fastboot. but it discovered that it is not correct and the fast boot itself can be damaged..
Any way thank you so much the only man helped me here sinus23.
I got this problem too
Me too
I got this problem
guys you got to do this , i am having yureka plus5510a no fastboot no recovery
bros no recovery no fastboot boot loop tried all combination not charging nothing what you think you guys are genius give me some let me tell you the whole thing how i ended here .. its all started with the king root(worst decision ) i wanted to flash twrp in my yu yureka plus 5510a no idead what " A" stands for then i used flashify from playstore and downloaded the twrp by the official twrp and flashed it with the flashify and boom boot stuck with no recovery some how removing battery and connecting the phone goes to the charging disp from where i did enable the fast boot but cmd was not able to identify adb devices nor the flashboot commands were working so i did same with win 10 powershell but nothing no devices , so i decided to use a method of ygdp , much hopes with this used ***** 5.1.153.00.P0.160604.8675_I02.def.CPB ******* dont know where the log file is but it was showing old bootloader error downloading and error and error and terminated at 2 % , then this one of your thread by unziping the official files and clicking on flash-all.bat file which he provided img(1) "some trials your phone will be all right " i tried with some "waiting devices error " message but then it just started something happened oem unlock blah_blah and then successful , tried to boot again but this time phone was automatically jumping into fastboot mode , then i finally tried one last time in that power shell thing by typing using cmd and applied fastboot code , even no devices was showing in powershell ,, but then i used some different code something like "fastboot ix902 recovery " and i was able to install a real old twrp recovery.. phone was showing the cyanogen loading ....but later after 1 hour i felt its stuck = + = but luckily recovery was working but but dont know why the buttons setup used to go in fastboot mode was now taking me in recovery,, and fastboot was no longer acessable , i was fine with it so i downloaded latest recovery from your respected thread file named as " twrp-3.0.2-0-20160604-UNOFFICIAL-tomato.img " i wanted to install nougat aosp so i thought its a nice idea to update the recovery first i. so i did the normal recovery update from the recovery it self , and now i guess that recovery was so old , the new one was kinda mindblower for the older one and booom no recovery , no fastboot , tried all the combination and came up with this one volume+ vol- and power shown img (2) same as boot logo but a small "official" tag
pls help i know this post dont suits your professional level , right now i havent slept from kinda like three days cause of exams and this sarcasm of being in trouble.. like my every devices is rooted o in onyx m in tab 2 , it frustating pls help ........i will edit this and make it more polite but if you are one who can solve this .. i am ready to donate man. cause u deserve it , it will gonna be learning experience with you i will be totally into the reply and pls dont scream for drivers i did installed coolpad driver adb drivers everything required i feel yureka is a real fake company their parts isnt distinguishable i did al the steps nicely and cleanly except the (kingroot ) and pls dont brag about the old threads , they didnt helped me much.. and probably why my phone is kinda dead

Categories

Resources