Related
Hi,
I think i messed a little too much with my A501 tablet, and somewhat killed it.
I explain; Yesterday, i treid to flash the ICS leak published on the forum.
Everything worked, except the rom wouldn't lauch.
So, i tried and flashed another HC rom, and that's where the nightmare begins; The tab wouldn't power correctly (stuck on Acer logo), and even recovery access was impossible (stuck on Loading Recovery Kernel Image).
So i tried all the ways i found (from update.zip, to nvflash); but nothing worked for me.
The last one i tried was with this command,which somewhat gave some results:
Code:
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk 0xF******* 0x******** 0x******** 0x******** --sync --go
The Nvflash process could wipe and recreate some partitions, but for some reasons, aborted the process in the middle.
But that's not all, here's the worst part: now, the tab won't boot up AT ALL.
The only thing it does is lighting the power button for some seconds,and turn off just after.
But,during those seconds, APX seems to be usable...but can't fully finish a process,since the tab shuts itself down.
Could someone help me with this? I assume that, if APX is still useable, there could be a way to save it. But what's the order of partitions and commands to have it working about correctly?
Many many thanks in advance for the answers
Ok, my bad, i'm sooooooooooooooooo stupid i'd slap myself: the tab has been powered on all night long...so the fact it was shutting down was only due tu the power source not plugged in
Now, i've followed the instructions for flashing the ICS bootloader provided by Vache, but i'm stuck with a "Magic Value Mismatch"
Needs more investigations
Ok, problem solved; i could reinstall a bootloader and recovery, so now, all i have too do is to flash a new rom.
All is fine now, guess that whiskey and lack of sleep don't do good when flashing
Thanks for all users that have come to this thread
Mods, you can close this thread
anthrax132 said:
All is fine now, guess that whiskey and lack of sleep don't do good when flashing
Click to expand...
Click to collapse
I didn't know there was any other way!
I've had my htc panache (canadian mytouch 4g) for just one day, and it blew its fuse at me. When I went to sleep, it worked fine, but when I woke up, the screen was black and nothing was working. I pulled the battery out and plugged it back in, and now the phone is stuck at the HTC boot screen. I can get into hboot, but some options just don't work, and hangs the phone:
-REBOOT BOOTLOADER (from FASTBOOT menu)
-FACTORY RESET
-IMAGE CRC (hangs on "Calculating... please wait")
-RECOVERY (shows an image of two curved arrows with a regular arrow within, over a tilted cellphone, then the image is reversed, and the screen goes black and the phone vibrates exactly 7 times.)
I tried using the RUU, but my computer won't detect my phone either in hboot or recovery (not that it has the time to detect my phone in recovery). Perhaps I am missing drivers? the device manager shows the phone as a generic "USB Device".
I've tried to get into download mode, but the only other button combination aside from volume down + power that did anything was power + back button, and that brought me to hboot into the fastboot menu.
I tried to update the phone by putting the latest pd15img file from the wiki onto the sd card but after it scans the file, the phone doesn't ask me if I want to update. it just goes back to hboot, and rebooting hboot does the same thing.
How can I get into download mode, anyway?
EDIT: just found hboot drivers. something that works, for once.
Adb maby?
Sent from my LG-P970 using xda premium
wouldn't have been able to use adb if the phone wasn't detected, now was it?
anyway, I found some hboot drivers that seem to work. I'll try the ruu first.
Correct me if I'm wrong, but if I remember correctly the 7 vibrations while trying to enter recovery signifies hardware failure...
Sent from my myTouch 4G using XDA Premium HD app
Ok so... I managed to get the phone charged, and yet RUU still tells me my phone battery is charged at less than 30%, and I can only exit. what gives? Is there a way to bypass that?
(By the way, the hboot drivers I used were from a website called unrEVOked. perhaps these were for another model? where could I get hboot drivers for my phone?)
As for the hardware failure thing, I'm not buying it. at least not yet. If it trully were a hardware failure, the phone wouldn't boot, eh? I can get to hboot and fastboot and fiddle around for a bit, and recovery works for around 10 seconds before it goes blank at me.
So ADB doesn't see my phone but fastboot does. seeing how switching my phone to the fastboot menu installed htc's own drivers right away, I'm not surprised.
Where are the adb drivers for the glacier/panache/mytouch 4g? the only ones I could find are for motorola phones.
EDIT: "C:\sdk-tools>fastboot -p SH16KRM01484 -w
erasing 'userdata'... FAILED (status malformed (1 bytes))
finished. total time: 0.016s"
Try this thread for adb setup:
http://forum.xda-developers.com/showthread.php?t=928370
Also, did you have (flash) a recovery installed? If I remember right, a triangle around a phone when you enter recovery from hboot means you didn't have one installed/flashed. I also remember reading that 7 vibrates mean hardware failure. There are lots of phones that had failed emmc's and would still boot but get stuck at the splash screen. Are you verifying the md5 when downloading ruu?
http://www.htc.com/us/support/htc-mytouch-4g-tmobile/software-updates
That link is to the HTC drivers you're looking for. Once you get it set, you should be able to flash the RUU and I would suggest making sure you have a recovery flashed as well...would help a lot right now if you could at least get there.
Chomanator said:
http://www.htc.com/us/support/htc-mytouch-4g-tmobile/software-updates
That link is to the HTC drivers you're looking for. Once you get it set, you should be able to flash the RUU and I would suggest making sure you have a recovery flashed as well...would help a lot right now if you could at least get there.
Click to expand...
Click to collapse
It's the third driver I download, one was called htcdriver.exe, the second one was the same with a version number, and the third, this one, and none work. nothing happens when I click on them. on the task manager I see the process starting and just quitting for no reason.
I'm starting to think technology as a whole is against me.
I'm gonna try the drivers included with pdanet.
So after getting the right adb drivers...
"C:\sdk-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\sdk-tools>"
nothing.
anyone?
(EDIT: fastboot started working. here's what getvar all gave me: )
C:\sdk-tools>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 0.89.0005
INFOversion-baseband: 26.09.04.26_M
INFOversion-cpld: None
INFOversion-microp: 0429
INFOversion-main: 2.10.1530.1
INFOserialno: SH16KRM01484
INFOimei: 357935045141682
INFOproduct: glacier
INFOplatform: HBOOT-7230
INFOmodelid: PD1510000
INFOcidnum: VIDEO001
INFObattery-status: good
INFObattery-voltage: 4183mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 6a4abc53
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.047s
I'm not sure if this can be helpful or not, but here.
It don't appear to be bricked...try flashing 4ext recovery.
Sent from my HTC Glacier
I tried to flash the phone using one of the pd15img.zip files, but I got the following error: "CID Incorrect!"
Does CID stand for Carrier ID?
So it shows you have s=on and latest gb hboot, so assuming you were running the stock rom. What was the last thing or things you did before plugging out in to go to sleep? Have you tried to select factory reset? If you only had the phone for 1 day, why don't you take it back to where you bought it?
ronin178 said:
So it shows you have s=on and latest gb hboot, so assuming you were running the stock rom. What was the last thing or things you did before plugging out in to go to sleep? Have you tried to select factory reset? If you only had the phone for 1 day, why don't you take it back to where you bought it?
Click to expand...
Click to collapse
Nothing. two hours before I went to sleep, I installed a few games and widgets, and everything went fine. I just quit what I was playing (some 3d racing game), put the phone on charge and went to bed.
Factory reset does nothing (the phone just hangs), and I can't return it because I got the phone from someone else (I doubt he's somehow responsible for this seeing how it's not the kind of defect you can just hide like that) and there was no warranty anymore on the phone, so I can't have it exchanged.
If I really can't do anything with that phone, I'll just sell it for parts on ebay I guess. but for now, I'm not giving up. I'm downloading the videotron ruu again, and will just put the zip file it extracts onto my sd card and rename it accordingly. Hopefully that will work.
I've downloaded the ruu, copied the rom.zip file from the temporary folder into my sd card, renamed it to pd15img.zip, and let it load in hboot. it asked me if I wanted to update, said yes, and it's stuck. I think it IS bricked, after all.
Parsing... [SD ZIP]
[1] BOOTLOADER -Updating
[2] BOOT
[3] RECOVERY
[4] SYSTEM
[5] SPLASH1
[6] USERDATA
[7] TP
[8] TP
[9] RADIO_VZ
[10] RADIO_CUST
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
Update is in progress...
Do not power off the device!
Click to expand...
Click to collapse
It's stuck at where -Updating is, next to BOOTLOADER. I've left it there for 20 minutes now, and it hasn't budged. and I know that bootloaders aren't that big, unless the update is doing something fancy that makes it super slow, so... ****.
Is there a way to switch the phone to download mode? not hboot or recovery, but download mode.
adb just won't detect my phone :c
will somebody tell me how to put that phone into download mode?
Which RUU are you using?
Sent from my myTouch 4G using XDA Premium HD app
My Nexus 4 is in a sorry state and I'm looking for some advice before I RMA, just in case it can be saved. It's very odd.
My N4 was on charge overnight and my alarm went off this morning as normal, Cancelling it crashed the clock app, and when I unlocked the device I was greeted with a cascade of crashing services. So I turned the device off but it will not start and hangs on the Google logo with a padlock icon displayed at the bottom of the screen, The device is not encrupted and the battery is fully charged.
I am running stock 4.2.2 with an unlocked bootloaded and the device _will_ boot to fastboot mode. Selecting the Recovery option displays the Android red warning triangle icon.
So I fired up the Nexus 4 Toolkit and this will let me flash a temporary recovery image. But neither CWM and TWRP can mount /cache, /system, /data or /sd-card, so a factory reset/Dalvik wipe etc will not work. Very odd.
As a last resort I downloaded the official 4.2.2 image but the toolkit cannot flash it and it displays:
Starting Flash Process..
Flashing Bootloader Image..
sending 'bootloader' (2188 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.156s
An Error Occured
I am out of ideas so any suggestions are welcome.
rec71 said:
My Nexus 4 is in a sorry state and I'm looking for some advice before I RMA, just in case it can be saved. It's very odd.
My N4 was on charge overnight and my alarm went off this morning as normal, Cancelling it crashed the clock app, and when I unlocked the device I was greeted with a cascade of crashing services. So I turned the device off but it will not start and hangs on the Google logo with a padlock icon displayed at the bottom of the screen, The device is not encrupted and the battery is fully charged.
I am running stock 4.2.2 with an unlocked bootloaded and the device _will_ boot to fastboot mode. Selecting the Recovery option displays the Android red warning triangle icon.
So I fired up the Nexus 4 Toolkit and this will let me flash a temporary recovery image. But neither CWM and TWRP can mount /cache, /system, /data or /sd-card, so a factory reset/Dalvik wipe etc will not work. Very odd.
As a last resort I downloaded the official 4.2.2 image but the toolkit cannot flash it and it displays:
Starting Flash Process..
Flashing Bootloader Image..
sending 'bootloader' (2188 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.156s
An Error Occured
I am out of ideas so any suggestions are welcome.
Click to expand...
Click to collapse
I suggest you leave it as is and OEM lock it before you send it in. If they see its OEM locked they shouldn't give you a problem with it
brandonc0526 said:
I suggest you leave it as is and OEM lock it before you send it in. If they see its OEM locked they shouldn't give you a problem with it
Click to expand...
Click to collapse
It won't relock.
It's like it's read-only.
rec71 said:
It won't relock.
It's like it's read-only.
Click to expand...
Click to collapse
Hmmm. Try booting into TWRP from the toolkit and flashing a rom. If that doesn't work just try wiping everything and toggling/untoggling all the mounts. I had this issue on my old galaxy S and wiping did the trick, although I had to flash my ROM again
Strange. TWRP asks for a password - is this normal? The device has never had encryption enabled. But if I skip this I still cannot mount or access any part of the storage.
Same error. Have you find any solution?
Hello, did you find any solution? I just had the same exact problem. I wiped it through fastboot but when I try to flash the image, I get the same error
rec71 said:
My Nexus 4 is in a sorry state and I'm looking for some advice before I RMA, just in case it can be saved. It's very odd.
My N4 was on charge overnight and my alarm went off this morning as normal, Cancelling it crashed the clock app, and when I unlocked the device I was greeted with a cascade of crashing services. So I turned the device off but it will not start and hangs on the Google logo with a padlock icon displayed at the bottom of the screen, The device is not encrupted and the battery is fully charged.
I am running stock 4.2.2 with an unlocked bootloaded and the device _will_ boot to fastboot mode. Selecting the Recovery option displays the Android red warning triangle icon.
So I fired up the Nexus 4 Toolkit and this will let me flash a temporary recovery image. But neither CWM and TWRP can mount /cache, /system, /data or /sd-card, so a factory reset/Dalvik wipe etc will not work. Very odd.
As a last resort I downloaded the official 4.2.2 image but the toolkit cannot flash it and it displays:
Starting Flash Process..
Flashing Bootloader Image..
sending 'bootloader' (2188 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.156s
An Error Occured
I am out of ideas so any suggestions are welcome.
Click to expand...
Click to collapse
Don't use a toolkit, use the guide posted in the general section, toolkits are often very faulty as they only tend to work on working devices
Sent from my Nexus 4 using xda app-developers app
Same problem here, tried flashing everything through fastboot,
"fastboot flash recovery recovery-twrp-2.5.0.0-mako.img
sending 'recovery' (7510 KB)...
OKAY [ 0.473s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.479s"
Anything I flash I get the same response.
Any help would be appreciated
This is likely an emmc hardware failure
I've seen something very similar happen a couple of times with people on the one x.
Bootloader magically relocked itself. All partitions only read only. Unable to flash anything or issue lock/unlock commands
Sent from my Nexus 4 using xda app-developers app
highessupremacy said:
Same problem here, tried flashing everything through fastboot,
"fastboot flash recovery recovery-twrp-2.5.0.0-mako.img
sending 'recovery' (7510 KB)...
OKAY [ 0.473s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.479s"
Anything I flash I get the same response.
Any help would be appreciated
Click to expand...
Click to collapse
I'm having the exact same issue. Going to try to warranty it but since it the bootloader can't be relocked I have the feeling I'm screwed.
remote flash write failure
Same issue here.
My phone was unlocked and rooted, with stock firmware. I haven't made any changes to my phone for months since I re-rooted after 4.2.2 was released.
Had some apps crashing yesterday afternoon, not a big deal I thought, I'll just reboot. When I rebooted, the phone got stuck on the nexus boot screen - left it for hours and nothing.
Tried clearing the cache and doing a factory reset, no effect at all. Today, I tried reflashing, erased all the partitions first, but couldn't flash anything. Tried stock firmware first, but also custom recovery partitions and custom boot roms. Nothing.
Same issue here. Can't flash anything, I always get "FAILED (remote: flash write failure)" I also cannot re-lock the bootloader. I guess I will have to send it back for warranty repair to Google/LG?
This is the only thread I could find on this issue, I wonder if some recent app update broke my N4?
nothing to add besides same issue here. I got a google services failed message that I couldn't clear so I turned off my phone and then stuck on X. Haven't even installed a new app or anything in a couple of weeks. I have tried command prompt method and toolkit and both give flash write failure. I have cleared everything via command prompt and same result. Always told you cannot brick a Nexus...
Did you try to connect via adb after fastbooting to CWM (or even on X logo)?
We could compare our kernel logs then, hope it might clarify something...
Had any luck this far? I've got my nexus bootloader unlocked but not rooted, and I fear it will happen to me too.
Same problem here.
I believe I was able to fastboot erase /userdata but every 'flash' command fails. I am able to relock it though so I will try to send it in.
Good thing I kept my Galaxy Nexus and I was able to fit my micro SIM into it
Am I screwed?
Hey guys, another affected Nexus 4 user checking in. Same exact symptoms: was charging, checked something on it, saw a cascade of force closes. Shut it down, then it wouldn't boot past the Google screen. At one point I got it past that to the X screen, but it was stuck there indefinitely (for hours).
I'm running stock 4.2.2 with an unlocked bootloader. Same issues when trying to do anything over fastboot. Had the same idea to flash back to stock with no luck.
So... am I just screwed out of a phone? Or has anyone had luck getting it replaced?
This sounds like an simular issues my LG optimus G had. I would have to flash the misc.img in fastboot to get it to work again due to the misc partition getting corrupt Has anyone tried that yet?
Sent from my HTC One using Tapatalk 4 Beta
Just got off the phone with Google Play support. They had me run through a few tests (boot to fastboot, go into recovery, try booting from there; boot to fastboot, go into recovery, factory reset, reboot). Same thing: stuck on the "x" screen. I mentioned I wasn't rooted, but they didn't ask about the bootloader being unlocked. They went ahead and treated it as a normal in-warranty RMA. They're sending a new Nexus 4, and then I send the defective one back once it arrives.
If you have this issue with a Nexus 4 bought from Google Play, I suggest you call Google Play hardware support at (855) 836-3987. They were super friendly and helpful. While I'm bummed something went wrong with my phone, I'm glad I don't have to buy a new one.
---------- Post added at 09:17 PM ---------- Previous post was at 09:14 PM ----------
XsMagical said:
This sounds like an simular issues my LG optimus G had. I would have to flash the misc.img in fastboot to get it to work again due to the misc partition getting corrupt Has anyone tried that yet?
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
I don't see a misc.img in the stock image from Google for the Nexus 4. But anything else I tried to do via fastboot failed, which I've never had before.
I had the same exact issue experienced with the original poster. The apps were crashing on me like crazy. I was at the dog park. I remember the only app that was being updated at that time was AirDroidv2 just literally like 2 minutes ago before the google apps started to go crazy. I started to shut it down and boot it back up. I got stuck on the "X" screen. after an hour, i went home and tried the toolkit. then i went manual with cmd. all i get is "FAILED (remote: flash write failure)" whenever i attempt to flash it.
after a while, the OS wasn't even booting up. No "google" logo or "X" logo. Only i got was the bootup into fastboot. Now it doesn't even power up unless i connect the usb.
curious, is anyone hearing any rattling sounds in their device and/or red led dot when connecting to usb? I fear it's a bad connection to the battery.
Count me in as one of the unlucky folks as well. I noticed my N4 was auto-updating some apps last night, then later when I went to pick it up I couldn't get the screen to turn on. Held down power until it rebooted, then was stuck at the Google logo and never got any farther. Bootloader mode works, trying to boot into recovery gives a black screen. Tried to re-flash recovery.img from stock but got the same error as others: "FAILED (remote: flash write failure)"
I called Play Support and they were helpful in getting the RMA process started. Unfortunately I expressed some concern about my cracked glass back affecting the return and the CSR mentioned that he'd have to escalate. (As a point of reference, my glass cracked a few months ago). We discussed how common cracked glass backs are with the N4 and how I hoped it wouldn't affect my RMA as the device has been working fine for months. He's waiting to hear back from the specialist before we can move forward.
Really hoping that everything works out.
UPDATE: Warranty claim denied due to the broken glass. Not sure what my next step is. :/
This is how I unbricked my TF300T that had no rom installed and a wrong bootloader/recovery combination. (4.2 bootloader with TWRP recovery JB version). Hope it helps.:good:
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have the same on my TF300t and A700 - but it seems i just managed to get my TF300t back
i tried all fastboot (reflashing recovery, boot, system etc) no dice - especially since writing system was done after 3 secs all the time.
Here how i restored my TF300T JB
download your appropriate lates firmware from Asus (WW, US etc.) and extract the zip twice so you have your blob file
install your device drivers if needed (i used Google SDK ones) (and as a Tip Win8 sucks for Fastboot stuff so try to get Win7 Vista XP for this)
Reset your device with a paperclip/needle (about 2 cm down of your sdcard slot) and hold vol-down to enter fastboot
(the folowing i did at least 10 times already but didn't erase misc)
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\adb\TF300t\blob (this is my path - your's may vary depending where you stored your blob) ((also this was the first time i saw the loading bar while flashing)*
fastboot -i 0x0B05 reboot
* it also took a lot longer as it should:
C:\>fastboot -i 0x0B05 flash system c:\adb\TF300t\blob
erasing 'system'...
OKAY [ 1.695s]
sending 'system' (800935 KB)...
OKAY [133.121s]
writing 'system'...
OKAY [153.973s]
finished. total time: 288.789s
im now setting my tab up to get back to CM (which initially caused this sh1theap due to autoupdate error, same as my A700 got bricked )
hope i could help you out!
cheers
-Buster <----(credits to him) Go to this link ---> http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 because that's the guy that wrote this procedure from above (credits to him) :
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This part was me now -ozkrtech <--- (credits to me)
In addition to that, if you simply can't see your device using the command "adb devices" go check on device manager if you see a device called just "Transformer" with a yellow icon indicating it needs a driver, and manually update driver, select "browse my computer for drivers" and then select let me pick from a list of device drivers on my computer" there you will see a list of like 3 different drivers, one of them says "bootloader" and one of the others says "adb" (i think they self explain) but just in case try with each one of them you can keep on switching drivers until you get your device recognized by the command "adb devices".
You should be asking yourself... whats the right moment to do an "adb devices" command? well my tablet same as -Buster's tablet had the wrong recovery menu flashed (wrong bootloader version) and it just kept booting into the corrupted recovery (in my case TWRP) with the "can't mount anything" and "what's the password" issue. When you get to password screen just hit cancel and try the "adb devices" commando and you'll see it gets recognized with your device serial number.
Once your device gets recognized by "adb devices" command you will proceed to use "adb reboot-bootloader" command and the tablet will reboot into the menu that had 4 options but now have 3 options and its missing the fastboot option (don't panic) in the last bootloader it is auto-fastboot mode when you reach that screen with just 3 options in it now (yeah is the screen with the RCK option) at this point try "fastboot devices" command to see if your device gets recognized same as "adb devices" procedure, it should get recognized with a different serial number (don't know why, maybe that number isn't a serial number), at this time you are SO LUCKY! now you will follow what I posted at the beginning from that other dude ---> (-Buster) or follow his link --- > http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
And you'll have an unbricked tf300t in no time =) (I personally used the stock but newest Asus ROM) 4.2.1 (10.6.1.27.1) and it worked flawlessly.
**NOTE** don't turn off nor reset your device once you have formatted the partitions, no need for that (don't know what happends but it might get really hard bricked) just proceed to flash the stock rom after erasing the partitions.
I'm 100% positive this will work if your device is in same state as ours. (had TWRP for JB) then updated bootloader to version 4.2 and forgot to update twrp to version 4.2 or installed twrp version JB by mistake and lost fastboot and TWRP is asking password.
Hope it helps. Let me know your status and if it worked for you.
So I am in the same boat as I flashed the wrong twrp. My device shows up under adb devices and I can boot into the bootloader using adb reboot-bootloader. However, once there, I can not get the device recognized with fastboot. I have tried messing with the drivers like you suggested but nothing will get it to show up with fastboot. Anybody have advice on where to go from here?
So extra info. The device bootloops into twrp 2.6. The only way I can boot into fastboot mode is with adb reboot-bootloader and I can get into APX. I can also boot directly into my current ROM (Slim beta 3) by selecting android in the bootloader menu. I have tried flashing proper recovery through flashify, which is says was successful, but the wrong twrp never gets overwritten. Rebooting the device will send it back to twrp.
Thanks if anyone can help
Thanks, man! It took a while to find this thread, but this was exactly my problem. The adb driver in windows was the pre-solution to help get back to the fastboot server in the bootloader. Awesome information. Thanks again!
I have tried "adb reboot-bootloader" and then adb devices and fastboot devices and neither will show the tab listed while the tab reaches that screen with just 3 options. I have uninstalled reinstalled drivers, it does show in device manager as Asus Android Composite ADB Interface but when running the command it will not list the tablet. Any suggestions?
Hello!
A few days ago I tried to root my Asus TF300T because before that, I changed the lcd and the touchscreen from FPC-1 to G01 version. So I had to root and update touchscreen's firmware to 02-3011-4820.ekt. I already updated with last firmware from asus.com. First, I installed a TRWP recovery but was useless since the touchscreen doesn't worked. So I tried to rewrite CWM recovery. I reset it and I don't remember exactly if I begun to install or not CWM but when I tried to wipe data (Vol- + Power), the tablet has freezed. After a few minutes I did a hardware reset (pin hole). Since that, the tablet freeze with "Device Unlocked", Asus logo and nVidia. The device was already unlocked. I don't have any backup from it. No fastboot, no adb. Just APX mode. Is it possible to do something with it anymore? I tried BootTools2, extracted bloobs from last version of firmware, tryed to flash them with nvflash and wheelie but vainly. What is the next step? I'm a beginner!
Remember please I cannot go in fastboot recovery menu, only apx. Thank you in advance!
I can not thank you enough!!! my tablet is now working I honestly though it was done for aha THANK YOU!!!
Howdy, folks. I recently bricked my tablet thanks to a bad install of CWM, but following the OP's guide I was successfully able to reflash stock firmware and the device runs fine now.
However, upon reflashing said firmware, it became apparent to me (from reading various threads in the development subforum), that I would need to downgrade to an older firmware version to reflash TWRP. So I did that successfully, but now I am having a problem similar, or perhaps identical, to that of Bionicbowtieguy, in that ADB appears to be broken for my tablet. I have tried uninstalling and reinstalling the Asus usb drivers, in addition to reinstalling/updating all of the ADB software. Fastboot still works fine, but as such I'm unable to root using Motochop's rooting kit (I know there are other methods out there), nor am I able to flash a new recovery. I have also tried repeatedly reflashing the older stock in the hopes that ADB would magically start working again to no avail.
Does anyone have any suggestions to getting ADB to work for my tablet again? I have scoured the web, particularly these forums, for days looking for an answer, but haven't turned anything up yet. Any help would be greatly appreciated.
Gave back 10 years of my life that I lost once I discovered I flashed the wrong TWRP version. Can't thank you enough man.
Kombatant said:
Gave back 10 years of my life that I lost once I discovered I flashed the wrong TWRP version. Can't thank you enough man.
Click to expand...
Click to collapse
Same here!
Thank you OP for making this a topic even if you didn't come up with it you made it a thread that has saved a few people like myself money and headaches. Literally I just stumbled on this thread 10 minutes after I told my wife is be Tablet shipping Black Friday. Thank you sir.
Thank you.
I did this on a hackintosh running OSX since on Win 8.1 fastboot kept crashing.
March of this year I bricked my tablet during that 1 week period where nobody knew that TWRP was broken + fastboot freezing.
I must have tried everything, Maybe that erase misc was the key factor for success.
I was about to sell this for what I could get or send it to asus, now I can use it again!
How are you guys getting your tablet into fastboot mode? I've tried power on with volume down, the reset hole with volume down, and letting the battery die then recharge, then power on with volume down... Nothing. What am I doing wrong?
Sent from my Galaxy Nexus using Tapatalk
Best thread ever!! You are a life saver !!! thank you!!
leris2 said:
Best thread ever!! You are a life saver !!! thank you!!
Click to expand...
Click to collapse
Indeed. You are a god among men. Thank you so much
This worked! I thought I was out of luck. Thanks a lot.
I accidentally flashed an incomparable version of twrp. It would only boot straight into recovery and I couldn't get into recovery. TWRP kept asking for a password even though I never set one up and it wouldn't mount the internal storage or sd card.
I had to follow the instructions at the bottom to intall the drivers so adb and fastboot to work. After that I followed the instructions at the top.
The only thing different I did was skip the "fastboot erase boot" step. I was afraid that would really brick my device if I screwed up (Does this really erase the bootaloader leaving the device with no bootloader?).
Just wondering how long the fastboot window sits displaying < waiting for device > ? All my drivers are ok and I my pad shows up fine as a fastboot device in windows.
Cheers
Fastboot
Bolandk said:
Just wondering how long the fastboot window sits displaying < waiting for device > ? All my drivers are ok and I my pad shows up fine as a fastboot device in windows.
Cheers
Click to expand...
Click to collapse
They do not sit at all they will go right to it. You must not have the right combination yet. Keep trying.
Took me awhile to get the link.
norm883
FIXED!
BY GOD, I have no words for how incredible grateful I am right now! You not only saved my TF300T's life but also a lot of money for me and gave me another lesson of Android insight.
Thanks so much for this!
Let me know if I can return the favor somehow!
Regards,
(a very happy) philleicht
Hi. I think I'm having the same problem as some of the others in this thread.
Background: Tablet is unlocked, JB Rom (Paranoid Android) was installed since March, along with TWRP recovery. In preparation of installing CM11, I used Android Terminal Emulator to install the latest TWRP from a *.blob file, but I found that the latest TWRP is still not CM11-ready...
Setup to Issue: Last night, I decided I wanted to put CM11 on my TF300T. TWRP doesn't have a compatible recovery out for CM11 (install of CM11 rom fails every time), so I reinstalled the paranoid android ROM, and attempted to get the latest recovery from clockworkmod. On cwm's website, they only have choices for "transformer" "transformer prime" and "transformer infinity" which, when downloaded, have tf101, tf201, and tf700 in their filenames. (No tf300, that is)
So... I attempted to install the tf201 recovery (closest to mine, right?) by renaming the file cwm.blob, and using android terminal emulator to install it, the same way I did with TWRP. The first few times I tried and rebooted into recovery... TWRP was still installed... which was weird to me.
The big problem: Ultimately... when I rebooted the tablet, I just see the initial "ASUS" screen with "The Device is UnLocked." in the top-left corner. When I hold the power button to turn it off... it powers back on within a few seconds, and stays at the "ASUS" screen again. It will not stay off... and will not show anything but the "ASUS" splash screen. (With one exception, described later - "the only ray of hope...") If I hold the volume up or down buttons when powering on the device, absolutely nothing different happens. (since it doesn't STAY off... I've tried all kinds of different combinations of pushing/holding the appropriate buttons for when the tablet comes back on) IMPORTANT: I never see the "three icons" as expected when holding the volume button(s). No RCK, USB, etc... when the unit turns back on, it goes to the ASUS screen, and stays there until the battery dies. As a result... I can't get into recovery, fastboot, or APX or whatever in the traditional way.
Pressing the reset button alone, or reset + volume down has the effect of temporarily turning off the unit and then on again, the same as holding the power button to turn it off and letting it turn itself back on again.
The only ray of hope that I have is that *sometimes* if I press reset + volume up with the USB cable connected to a computer... the screen will STAY BLACK, but the "device connected" sound will play on my PC (Win 7 x64) as if I just plugged the tablet into USB on my computer, and I will get a message that it's trying to install an APX device. However, it eventually tells me that the device driver could not be installed. The screen on the tablet stays black in this case... until I reset it, hold the power button, etc.
So... I'm not opposed to (or unfamiliar with) using fastboot or any other command-line app to resurrect my tablet... I just haven't been able to get it into a condition that I can try something like that yet.
Is there any hope for my tablet? Somebody please help me. I'm open to sending a few bucks via paypal or google wallet to anyone that can lead me to a resolution. That would be cheaper than buying a new tablet... not to mention the priceless value of the progress I have in Fieldrunners 2. lol.
Thanks for your time!
~Ryan
same problem reboot back to twrp
well i may be stupid because i can't understand why i have tried a couple of commands and i still get the same problem reset volume down still goes back to twrp and ask for a password can someone please explain this in alittle more detail and what commands i also get the waiting for device in my commands is there another way to push these files into this device tf201 please help is there a way to do something in the twrp recovery like terminal command
I was a fool for flashing wrong recovery!
DrPhant0m said:
Hi. I think I'm having the same problem as some of the others in this thread.
Background: Tablet is unlocked, JB Rom (Paranoid Android) was installed since March, along with TWRP recovery. In preparation of installing CM11, I used Android Terminal Emulator to install the latest TWRP from a *.blob file, but I found that the latest TWRP is still not CM11-ready...
Setup to Issue: Last night, I decided I wanted to put CM11 on my TF300T. TWRP doesn't have a compatible recovery out for CM11 (install of CM11 rom fails every time), so I reinstalled the paranoid android ROM, and attempted to get the latest recovery from clockworkmod. On cwm's website, they only have choices for "transformer" "transformer prime" and "transformer infinity" which, when downloaded, have tf101, tf201, and tf700 in their filenames. (No tf300, that is)
So... I attempted to install the tf201 recovery (closest to mine, right?) by renaming the file cwm.blob, and using android terminal emulator to install it, the same way I did with TWRP. The first few times I tried and rebooted into recovery... TWRP was still installed... which was weird to me.
The big problem: Ultimately... when I rebooted the tablet, I just see the initial "ASUS" screen with "The Device is UnLocked." in the top-left corner. When I hold the power button to turn it off... it powers back on within a few seconds, and stays at the "ASUS" screen again. It will not stay off... and will not show anything but the "ASUS" splash screen. (With one exception, described later - "the only ray of hope...") If I hold the volume up or down buttons when powering on the device, absolutely nothing different happens. (since it doesn't STAY off... I've tried all kinds of different combinations of pushing/holding the appropriate buttons for when the tablet comes back on) IMPORTANT: I never see the "three icons" as expected when holding the volume button(s). No RCK, USB, etc... when the unit turns back on, it goes to the ASUS screen, and stays there until the battery dies. As a result... I can't get into recovery, fastboot, or APX or whatever in the traditional way.
Pressing the reset button alone, or reset + volume down has the effect of temporarily turning off the unit and then on again, the same as holding the power button to turn it off and letting it turn itself back on again.
The only ray of hope that I have is that *sometimes* if I press reset + volume up with the USB cable connected to a computer... the screen will STAY BLACK, but the "device connected" sound will play on my PC (Win 7 x64) as if I just plugged the tablet into USB on my computer, and I will get a message that it's trying to install an APX device. However, it eventually tells me that the device driver could not be installed. The screen on the tablet stays black in this case... until I reset it, hold the power button, etc.
So... I'm not opposed to (or unfamiliar with) using fastboot or any other command-line app to resurrect my tablet... I just haven't been able to get it into a condition that I can try something like that yet.
Is there any hope for my tablet? Somebody please help me. I'm open to sending a few bucks via paypal or google wallet to anyone that can lead me to a resolution. That would be cheaper than buying a new tablet... not to mention the priceless value of the progress I have in Fieldrunners 2. lol.
Thanks for your time!
~Ryan
Click to expand...
Click to collapse
I have exactly this! I hope someone knows the answer for this issue. Else the tablet will learn how to fly!
I tried to push the reset button as described earlier but nothing changes. Not able to go into recovery Just stuck at ASUS in the middle NVidia in the bottomright corner en upperleft corner 'this device is unlocked'
Hey guys,
Been looking around on the forum but couldn't find any info about this.
I recently purchased a Le 3 Pro and was actually working well. I had a few random reboots (I read this was something normal - happened in Snapchat, but after clearing the app cache all was well again).
Anyway, so today at work I noticed the phone just rebooted for no reason, but then it just kept rebooting and rebooting.
I have the stock Chinese rom (it's the X720 vesion by the way) so I have not done any rooting. Was planning to, but thought I'd give stock a run for its money.
So, not I'm stuck with a phone that's stuck in reboot mode.
I can get into fastboot and I tried flashing TWRP into Recovery, and that "seemed" to work (the command came back successful) however when going into recovery mode, it's just the LeEco Recovery and it doesn't do anything. So, I have to power cycle again and then gets stuck in the reboot cycle.
I don't think OEM unlocking was enabled, but seeing I can't get into the OS I can't check. The bootloader was unlocked upon arrival.
I turned the phone off (volume up and down + power button)
Now, I also tried putting the phone into the charger, (it was still at 85%-ish as far as I can remember) however it doesn't seem to be charging. So I'm thinking there may be a hardware issue.
However, maybe a software solution... never know, so if anybody DOES know - highly appreciated
Thx
EDIT: so I've been fiddling around using some guides on this forum... nothing...
C:\Users\Ryan\Desktop\LEMAX2>fastboot devices
403077b2 fastboot
C:\Users\Ryan\Desktop\LEMAX2>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (787 KB)...
OKAY [ 0.048s]
writing 'aboot'...
OKAY [ 0.023s]
finished. total time: 0.079s
C:\Users\Ryan\Desktop\LEMAX2>fastboot oem unlock-go
...
OKAY [ 0.009s]
finished. total time: 0.010s
C:\Users\Ryan\Desktop\LEMAX2>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.092s]
finished. total time: 0.094s
** NOTE --> this was always showing unlocked (even if not doing any of these steps).
C:\Users\Ryan\Desktop\LEMAX2>fastboot flash recovery twrp-3.1.0-0-x2.img
target reported max download size of 536870912 bytes
sending 'recovery' (59348 KB)...
OKAY [ 1.284s]
writing 'recovery'...
OKAY [ 0.407s]
finished. total time: 1.697s
Click to expand...
Click to collapse
This would normally allow me to boot into TWRP recovery. however it just takes me to the Stock Recovery (and does nothing - ie: there is no option to do anything).
Have you tried booting into TWRP instead of flashing it? Try "fastboot boot recovery twrp-3.1.0-0-x2.img"
EDIT: What recovery you are using?
Presterin said:
Have you tried booting into TWRP instead of flashing it? Try "fastboot boot recovery twrp-3.1.0-0-x2.img"
Click to expand...
Click to collapse
Yes, tried that as well. Afterwards I tried:
Fastboot reboot
And also just manually booting into Recovery straight from the Fastboot screen (volume up + power).
Both times it just takes me to the "standard" LeEco Recovery Screen (it just says LeEco, some Chinese text and "Recovery") and doesn't allow me to do anything.
Also, I tried multiple chargers, no sign of the phone being charged at all (no sounds, no on screen display, no LED).
So, basically all I can do is turn it on and watch it reboot over and over again, or go into Fastboot, do some commands (which all seem to do nothing - although I get an "OK" status) or go into the standard LeEco Recovery (even after flashing TWRP into Recovery).
I'm seriously starting to think this is just a Hardware malfunction. However, I've scoured the net and haven't really found a case like mine.
Are you trying to flash Le Max 2 recovery on Le Pro 3? I don't know if it should work, but I would try one from this forum meant for this phone. For example this: https://drive.google.com/file/d/0B7uXK7jfW17nZGRCWmFmZU9NVWs/view (link copied from official LineageOS13 thread)
Presterin said:
Are you trying to flash Le Max 2 recovery on Le Pro 3? I don't know if it should work, but I would try one from this forum meant for this phone. For example this: (link removed) (link copied from official LineageOS13 thread)
Click to expand...
Click to collapse
No. Actually my dad and girlfriend have the Le Max 2 and had to install a new ROM on one of them, hence the LEMAX2 directory (where I'm just centralizing the flash files).
Basically I just want the stock (China) rom for the X720 -as that seemed to be working perfectly for me... for now (well, not now.. but you know what I mean).
I would try clearing all the data from recovery. See if that gets it to "reset".
If that doesn't work you could see about getting a hold of an "update.zip", pushing it to the device and flashing it from the stock recovery to see if it gets it out of the loop.
slgooding said:
I would try clearing all the data from recovery. See if that gets it to "reset".
If that doesn't work you could see about getting a hold of an "update.zip", pushing it to the device and flashing it from the stock recovery to see if it gets it out of the loop.
Click to expand...
Click to collapse
thanks for the answer, would you mind pointing me in the direction of how to "clear the data from recovery"?
Also, I'm not sure if I tried, by ADB doesn't work in Fastboot (to push the zip). At the moment, even in stock recovery I can't do anything.
EDIT: so, home from work. I've had the phone OFF for about 12 hours now. Plugged it in to charger and now I get an LED. Boots up normally, but battery was at 0%. I have no idea what's going on or why it now works, or even why the battery is at 0% (it was at 85% or so when it "crashed" yesterday I believe). Is this a known issue by chance? Or does this seem like a one off type of thing?
Ryanx0r said:
No. Actually my dad and girlfriend have the Le Max 2 and had to install a new ROM on one of them, hence the LEMAX2 directory (where I'm just centralizing the flash files).
Basically I just want the stock (China) rom for the X720 -as that seemed to be working perfectly for me... for now (well, not now.. but you know what I mean).
Click to expand...
Click to collapse
Can't get over "x2" in recovery image file, it points to Le Max 2 recovery.
Ryanx0r said:
thanks for the answer, would you mind pointing me in the direction of how to "clear the data from recovery"?
Also, I'm not sure if I tried, by ADB doesn't work in Fastboot (to push the zip). At the moment, even in stock recovery I can't do anything.
EDIT: so, home from work. I've had the phone OFF for about 12 hours now. Plugged it in to charger and now I get an LED. Boots up normally, but battery was at 0%. I have no idea what's going on or why it now works, or even why the battery is at 0% (it was at 85% or so when it "crashed" yesterday I believe). Is this a known issue by chance? Or does this seem like a one off type of thing?
Click to expand...
Click to collapse
There are some odd issues with this phone and charging. I'm not sure why it would bootloop and then die, only to charge and boot up again finally. Consider yourself fortunate that it works now! I ordered an Anker charger off of amazon and now use that for quick charging instead of the stock charger just in case...
What is the solution for this?
Ryanx0r said:
Yes, tried that as well. Afterwards I tried:
Fastboot reboot
And also just manually booting into Recovery straight from the Fastboot screen (volume up + power).
Both times it just takes me to the "standard" LeEco Recovery Screen (it just says LeEco, some Chinese text and "Recovery") and doesn't allow me to do anything.
Also, I tried multiple chargers, no sign of the phone being charged at all (no sounds, no on screen display, no LED).
So, basically all I can do is turn it on and watch it reboot over and over again, or go into Fastboot, do some commands (which all seem to do nothing - although I get an "OK" status) or go into the standard LeEco Recovery (even after flashing TWRP into Recovery).
I'm seriously starting to think this is just a Hardware malfunction. However, I've scoured the net and haven't really found a case like mine.
Click to expand...
Click to collapse
Can you reply me as soon as possible the solution for the constant reboots.
shivaraju07 said:
Can you reply me as soon as possible the solution for the constant reboots.
Click to expand...
Click to collapse
No solution. It "died" again (and to think I only used it for about 2 days).
I got into contact with the seller on Ali Express, I was told to send it back so they could look into it.
But Ali Express paid me back (while the seller was still looking into the problem). I didn't 'really' want my money back, just wanted the phone and an explanation - however, once I was paid back, the RMA was stopped and I was told to place a new order. Trying to do so, resulted in the seller letting me know that they no longer make the LeEco Pro 3.
So... I just went for OnePlus 5 instead - great phone
Ryanx0r said:
however, once I was paid back, the RMA was stopped and I was told to place a new order. Trying to do so, resulted in the seller letting me know that they no longer make the LeEco Pro 3.
Click to expand...
Click to collapse
I've read that LeEco stopped making phones. What they sell are the remaining stock, that it.
ZeblodS said:
I've read that LeEco stopped making phones. What they sell are the remaining stock, that it.
Click to expand...
Click to collapse
It's a real shame, because they're actually really good phones. My girlfriend has one and is really happy with it. It's the LeMax 2, but still a nice piece of (cheap, but great quality) hardware.
I have leeco le s3. After update Google Play Services, my phone always restarted continuosly when using GPS. Is that same with your issue?
InitialDS said:
I have leeco le s3. After update Google Play Services, my phone always restarted continuosly when using GPS. Is that same with your issue?
Click to expand...
Click to collapse
Have you solved the problem?