I ported TWRP using Android kitchen to flash to my device (Coolpad 801es) since there isn't an official version. For some reason, I can't seem to get fastboot to play nice with my phone (see my earlier post) so I used flashify. On reboot i'm stuck in a bootloop. I did have the foresight to back up my stock recovery with flashify and transfer it to my PC first, in case something went wrong. Now, I can't boot into recovery at all and ADB isn't working since the phone isn't being recognized by my PC when I plug it in. I just want to flash the stock recovery back and fix this. I can get into fastboot, and the PC does recognize the phone in fastboot, but when I try any commands it just hangs at waiting for device. I've googled but every solution i've seen for fixing a bootloop tells you to boot into recovery to do so.
Can someone please help me out?
UPDATE:
Upon further research, I discovered the reason fastboot commands weren't working is because my phone apparently isn't whitelisted in the fastboot exe. However, if I type Fastboot followed by -i 0x1ebf the commands seem to work. Using this method, fastboot devices lists my phone and fastboot reboot reboots the phone.
I think i'm on the right track, but when I try "Fastboot -i 0x1ebf flash recovery (path to recovery.img)" the terminal shows "sending 'recovery' (10240kb)..." and nothing else. No progress indicator, and i've waited 10 minutes for it to complete which should be more than enough time to flash a 10 meg file, but there's no change it just sits there. Like I said, I think i'm on the right track but I could REALLY use some help. I can't be the first person on here with this problem. Can someone, anyone, PLEASE help me.
So, more Googling would indicate that either i'm not using the correct USB port, or that my bootloader is locked. I have tried all the USB ports on my PC (front and back) as well as two different cables, no joy. As far as the bootloader being locked, the phone is rooted which I thought meant that the bootloader is unlocked as that is part of the rooting process. I try "Fastboot oem unlock" to check but I just get "failed remote no such command unlock" and there is no OEM option under developer options on this phone. I'm trying to piece this together but I could really use some help.
Related
So I just got my TFP today and already unlocked it with the ASUS tool and have been trying to get CWM on it for the past hour now. I've been following the instructions from here: http://transformerprimeroot.com/tra...orkmod-recovery-5-8-2-0-on-transformer-prime/
Basically I can get to fastboot and select it, but it just sits on "starting fastboot usb download protocol". When I enter in the command to flash CWM (fastboot -i 0x0b05 flash recovery recovery-clockwork-5.8.2.0-tf201.img) I get the message <Waiting for device>. I let it sit for 15 minutes my first try and at least 25 minutes my second try. I tried with keeping the USB cord plugged in the entire time. I'm beyond frustrated. Can anyone help? Did I just get a **** TFP that won't work with fastboot for some reason?
EDIT- Well ****, turns out I didn't have the drivers installed. Kind of embarrassing but I guess that's what I get for abandoning Android for so long. Mods can feel free to delete this.
I also had this problem using fastboot on linux. If on linux you need to be in root for fastboot to work. Also make sure you can see the device to ensure fastboot is working by using
sudo fastboot -i 0x0b05 devices
My phone has banished me from using it for about 3 months now. I repeatedly apologized for upsetting it, and begged of it to allow me back in. But it's a cold machine, which feels no empathy and cares not for my well-intentioned promises of never angering it again.
I understand it's reluctance to believe my words, as this is not the first time I've committed such atrocities. You see, I bricked it doing the same thing once before. Likewise, I was never able to fix it. Instead, I pawned it off to an Android developer in the office and he was able to fix it after a few hours of struggling. I've since moved to a different office on the other side of the country, and he was unable to remember exactly what he did that finally fixed it.
On to the important things:
What happened exactly?
I was installing a ROM (I can't remember which one at this point, it's been a while). Something counterproductive happened during the install, and sent it into a bootloop.
Symptoms?
1. It starts booting as normal. HTC logo for a few seconds, goes black as if it's going to the next screen, then it reboots.
2. This time it has the HTC logo with "Entering Recovery..." in pink above it.
3. I get a very quick (a few milliseconds, tops) glimpse of the CWM loading screen, then it reboots and goes back to step 1.
4. It repeats indefinitely, and would probably do so for eternity.
What can I actually do?
I can get to the bootloader screen, and cycle through the options (Fasboot, Recovery, Factory Reset, Simlock, Image CRC, Show Barcode), and I can drill into each section and see their child options. However anything I try to do, just sends me into the bootloop.
However, it does still say it's Unlocked in the bootloader. It has the "Tampered" and "Unlocked" alerts at the top.
What have I tried?
I've tried more random things than I can possibly recite right now. I even went to the extremes of dual booting Windows 8 on my Macbook, so I could start trying some of the Windows-only suggestions, like using the All-In-One Toolkit. The biggest issue, is that nothing I use can find the device. Not ADB or Fastboot on Mac, not ADB or Fasboot on Windows, and not the All-In-On-Toolkit. The only thing I ever get is "Waiting for device" or "Device not found".
Any help would be much appreciated. Thanks in advance guys!
rvrzl said:
My phone has banished me from using it for about 3 months now. I repeatedly apologized for upsetting it, and begged of it to allow me back in. But it's a cold machine, which feels no empathy and cares not for my well-intentioned promises of never angering it again.
I understand it's reluctance to believe my words, as this is not the first time I've committed such atrocities. You see, I bricked it doing the same thing once before. Likewise, I was never able to fix it. Instead, I pawned it off to an Android developer in the office and he was able to fix it after a few hours of struggling. I've since moved to a different office on the other side of the country, and he was unable to remember exactly what he did that finally fixed it.
On to the important things:
What happened exactly?
I was installing a ROM (I can't remember which one at this point, it's been a while). Something counterproductive happened during the install, and sent it into a bootloop.
Symptoms?
1. It starts booting as normal. HTC logo for a few seconds, goes black as if it's going to the next screen, then it reboots.
2. This time it has the HTC logo with "Entering Recovery..." in pink above it.
3. I get a very quick (a few milliseconds, tops) glimpse of the CWM loading screen, then it reboots and goes back to step 1.
4. It repeats indefinitely, and would probably do so for eternity.
What can I actually do?
I can get to the bootloader screen, and cycle through the options (Fasboot, Recovery, Factory Reset, Simlock, Image CRC, Show Barcode), and I can drill into each section and see their child options. However anything I try to do, just sends me into the bootloop.
However, it does still say it's Unlocked in the bootloader. It has the "Tampered" and "Unlocked" alerts at the top.
What have I tried?
I've tried more random things than I can possibly recite right now. I even went to the extremes of dual booting Windows 8 on my Macbook, so I could start trying some of the Windows-only suggestions, like using the All-In-One Toolkit. The biggest issue, is that nothing I use can find the device. Not ADB or Fastboot on Mac, not ADB or Fasboot on Windows, and not the All-In-On-Toolkit. The only thing I ever get is "Waiting for device" or "Device not found".
Any help would be much appreciated. Thanks in advance guys!
Click to expand...
Click to collapse
Sorry I don't know how drivers work on a Mac.
the procedure from a PC would be
boot to bootloader
choose fastboot
plug in usb to phone
you now see fastboot usb in bootloader
from command prompt type "fastboot erase cache" then fastboot reboot
try to boot phone.
if it fails
reboot to bootloader
reflash recovery
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot
make sure your recovery is named like above and in the same folder as fastboot
clsA said:
Sorry I don't know how drivers work on a Mac.
the procedure from a PC would be
boot to bootloader
choose fastboot
plug in usb to phone
you now see fastboot usb in bootloader
from command prompt type "fastboot erase cache" then fastboot reboot
try to boot phone.
if it fails
reboot to bootloader
reflash recovery
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot
make sure your recovery is named like above and in the same folder as fastboot
Click to expand...
Click to collapse
Thanks for the help clsA
I gave this a try, but like I expected I'm just getting a "waiting for device" message from fastboot.
This time around (in Windows), I did notice that I'm also getting an error about the USB device not being recognized. I don't think it's initializing correctly because Windows says it's malfunctioning. Nothing has happened to the device itself (no bangs, drops, water, etc), and this wasn't a problem until after it was bricked, so I doubt it's hardware related.
Interestingly, under the Device Manager, it is listed under "Android USB Devices" as "My HTC" so it seems to know what it is. My drivers appear to be up to date. Any other suggestions? Thanks again.
rvrzl said:
Thanks for the help clsA
I gave this a try, but like I expected I'm just getting a "waiting for device" message from fastboot.
This time around (in Windows), I did notice that I'm also getting an error about the USB device not being recognized. I don't think it's initializing correctly because Windows says it's malfunctioning. Nothing has happened to the device itself (no bangs, drops, water, etc), and this wasn't a problem until after it was bricked, so I doubt it's hardware related.
Interestingly, under the Device Manager, it is listed under "Android USB Devices" as "My HTC" so it seems to know what it is. My drivers appear to be up to date. Any other suggestions? Thanks again.
Click to expand...
Click to collapse
Install the drivers included in the All in one kit or install HTC sync (not recommended)
Sent from my TouchPad using xda app-developers app
[RESOLVED!]
For anyone else who might be having this problem
1. I was finally able to resolve this by downloading the archive provided by Esau Silva, which (I'm assuming) had updated versions of adb, and fastboot for Mac/OSX: http://esausilva.com/2010/10/02/how-to-set-up-adb-android-debug-bridge-in-mac-osx
2. I booted to the bootloader (power + volume down for 10 seconds), went to the Fastboot option, then plugged my phone into my Macbook; enabling Fastboot USB.
3. I opened terminal, CD'd into the directory containing adb/fastboot, and then ran "./fastboot devices" to see if it recognized my device. Sure enough, with Fastboot USB on and the updated adb, it recognized the device.
4. Then I ran "./fastboot erase cache" which allowed me to boot back into the bootload, and then properly boot into recovery, finally seeing ClockworkMod Recovery again.
5. From CWMR I erased the cache again, erased the dalvik cache, and then did a full wipe/factory reset.
6. Then I booted back into CWMR once again, and chose sideload. Then back on my Macbook I was able to run "./adb devices" to make sure adb could see my HTC One. Once I confirmed it could see it, I ran "./adb sideload nameofrom.zip"
After the sideload was complete, I was back up and running.
Big thanks to clsA who got me Googling fastboot a bit more. Hopefully this helps someone else!
Hey guys I need help. My HTC One is stuck in bootloader mode. I was trying to upgrade to the latest T-Mobile update. I tried downgrading with an RUU and I tired to flash stock recovery. I'm not all too sure what exactly happened, but I have no OS or recovery mode. All I have is bootloader mode. When I try to reboot to OS there is a bootloop. When I try to go into recovery a picture of a phone shows up with a red triangle and exclamation point. When I enter Fastboot in the bootloader it shows up on the phone as Fastboot USB. Although it says Fastboot USB, the phone is not recognized on the computer. When I try to enter fastboot commands, the prompt says "waiting for device" no matter what command I type.
If I could get the computer to recognize the phone, I could flash a recovery and a ROM or run an RUU. But that is only if I could get it to recognize the phone and I can't. I have searched for days and I can't find anything that works.
I have no OS, no recovery mode, and the bootloader isn't recognized on the computer. Please help! any help/advice will be greatly appriciated!
Please and thank you! :good:
amkivb said:
Hey guys I need help. My HTC One is stuck in bootloader mode. I was trying to upgrade to the latest T-Mobile update. I tried downgrading with an RUU and I tired to flash stock recovery. I'm not all too sure what exactly happened, but I have no OS or recovery mode. All I have is bootloader mode. When I try to reboot to OS there is a bootloop. When I try to go into recovery a picture of a phone shows up with a red triangle and exclamation point. When I enter Fastboot in the bootloader it shows up on the phone as Fastboot USB. Although it says Fastboot USB, the phone is not recognized on the computer. When I try to enter fastboot commands, the prompt says "waiting for device" no matter what command I type.
If I could get the computer to recognize the phone, I could flash a recovery and a ROM or run an RUU. But that is only if I could get it to recognize the phone and I can't. I have searched for days and I can't find anything that works.
I have no OS, no recovery mode, and the bootloader isn't recognized on the computer. Please help! any help/advice will be greatly appriciated!
Please and thank you! :good:
Click to expand...
Click to collapse
keep on rebooting until it's seen in the PC. Make sure the driver is installed (or forcible install it if it's an unknown device).
After that, once you're able to see it... re-flash the unlock token (fastboot flase unlocktoken unlock_code.bin). That will get you back into the ROM. At least, that's what did for me:
http://forum.xda-developers.com/showthread.php?t=2665481
But I can't reflash an older RUU at all, so I can't downgrade.
Drashna said:
keep on rebooting until it's seen in the PC. Make sure the driver is installed (or forcible install it if it's an unknown device).
After that, once you're able to see it... re-flash the unlock token (fastboot flase unlocktoken unlock_code.bin). That will get you back into the ROM. At least, that's what did for me:
http://forum.xda-developers.com/showthread.php?t=2665481
But I can't reflash an older RUU at all, so I can't downgrade.
Click to expand...
Click to collapse
I figured it out. All I needed was windows 7 instead of 8 for some reason. After I installed 7 I just ran the 4.3 RUU. Now I have a different problem. Originally this all happened because I was going to upgrade to the new 4.4.2. Now I can't flash stock recovery. I have cwm but I need stock recovery to upgrade to 4.4.2. Since there is no 4.4.2 RUU I don't know what to do now.
Hey guys - while trying to unlock the bootloader on my HDX 7, I flashed the older aboot per instructions and now cant get the HDX to boot. It shows a backlit black screen when attempting to boot, IT IS recognized by the computer, and I have ADB composite drivers installed, so thats what it is seen as in device manager. I can't see the system mounted as a file folder, however, I can get it to semi-respond to fastboot commands. fastboot devices lists the serial number, fastboot reboot will reboot it back to the backlit screen, fastboot -w did its thing and wiped it, fastboot flash boot boot.img seems to flash the boot.img, but it still will not boot. Also, NO adb commands are working, and it is not seen when adb shell or adb devices is executed. Am I totally F*cked, or is there hope that I can somehow flash a recovery via fastboot and get a system img flashed? any help or thoughts would be great.
sunapeelakers said:
Hey guys - while trying to unlock the bootloader on my HDX 7, I flashed the older aboot per instructions and now cant get the HDX to boot. It shows a backlit black screen when attempting to boot, IT IS recognized by the computer, and I have ADB composite drivers installed, so thats what it is seen as in device manager. I can't see the system mounted as a file folder, however, I can get it to semi-respond to fastboot commands. fastboot devices lists the serial number, fastboot reboot will reboot it back to the backlit screen, fastboot -w did its thing and wiped it, fastboot flash boot boot.img seems to flash the boot.img, but it still will not boot. Also, NO adb commands are working, and it is not seen when adb shell or adb devices is executed. Am I totally F*cked, or is there hope that I can somehow flash a recovery via fastboot and get a system img flashed? any help or thoughts would be great.
Click to expand...
Click to collapse
Barring a hardware problem your device is likely recoverable. Sounds like you may have flashed the wrong aboot; verify you're using the appropriate image. Aboot-13 is for the 7" (Thor); aboot-14 for the 8.9" (Apollo).
If that's not the issue you will need to coax the device into 'bulk mode' and rebuild from there. Not hugely difficult if comfortable with Android devices and working at the command prompt. There are random posts describing the process in the unlock thread. I'm not in a position to post links ATM so you'll have to do some digging. Read carefully; details and sequence of operations matter.
Davey126 said:
Barring a hardware problem your device is likely recoverable. Sounds like you may have flashed the wrong aboot; verify you're using the appropriate image. Aboot-13 is for the 7" (Thor); aboot-14 for the 8.9" (Apollo).
If that's not the issue you will need to coax the device into 'bulk mode' and rebuild from there. Not hugely difficult if comfortable with Android devices and working at the command prompt. There are random posts describing the process in the unlock thread. I'm not in a position to post links ATM so you'll have to do some digging. Read carefully; details and sequence of operations matter.
Click to expand...
Click to collapse
I flashed aboot 13, but the device never booted after I flashed that and twrp. I figured I could get into twrp since I had flashed it one step previous, but I cant. So i wiped it using fastboot -w thinking I could get rid of the aboot file, then flashed twrp again using fastboot flash recovery recovery.img, it ran through its thing and seemed to flash successfully, but I still cant boot to anything but a blank black screen. no logos or anything. It does respond to all the fastboot commands, of which I only know enough to be dangerous. I've tried changing the drivers around to get adb working to no avail. It seems to be stuck in fastboot mode, even when i fastboot reboot and quickly unplug it. Just not sure where to go from here - it had 4.5.5.2 on it before all of this.
sunapeelakers said:
I flashed aboot 13, but the device never booted after I flashed that and twrp. I figured I could get into twrp since I had flashed it one step previous, but I cant. So i wiped it using fastboot -w thinking I could get rid of the aboot file, then flashed twrp again using fastboot flash recovery recovery.img, it ran through its thing and seemed to flash successfully, but I still cant boot to anything but a blank black screen. no logos or anything. It does respond to all the fastboot commands, of which I only know enough to be dangerous. I've tried changing the drivers around to get adb working to no avail. It seems to be stuck in fastboot mode, even when i fastboot reboot and quickly unplug it. Just not sure where to go from here - it had 4.5.5.2 on it before all of this.
Click to expand...
Click to collapse
Bulk mode and rebuild.
Davey126 said:
Bulk mode and rebuild.
Click to expand...
Click to collapse
Ok, I executed fastboot -i 0x1949 erase aboot and seemingly put the HDX into bulk mode - I can now see a bunch of disk drives on the computer, and it is now recognized as "other devices" "QHSUSB_BULK" in device manager. I still am unable to execute adb commands at this time.
sunapeelakers said:
Ok, I executed fastboot -i 0x1949 erase aboot and seemingly put the HDX into bulk mode - I can now see a bunch of disk drives on the computer, and it is now recognized as "other devices" "QHSUSB_BULK" in device manager. I still am unable to execute adb commands at this time.
Click to expand...
Click to collapse
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post71430759
Davey126 said:
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post71430759
Click to expand...
Click to collapse
ok sick, I was able to execute those commands for aboot and twrp 3.1.1.1 and get the HDX booted into TWRP. now my issue is that I have nothing to install to get a system image going. Any suggestions on something safe?
Got slimrom installed and running 7.1.2 - awesome! Thanks so much for the help!
Hi to all,
I have a question about my device.
I hope that I have posted this correctly; if not please accept my apologies.
I have a Letv Le 2 Pro X620. This has the MTK CPU (not snapdragon).
The phone had the stock ROM on it with EUI and it got the updates.
In the last update about a month ago, Google Service stopped working; and I therefore wanted to flash a different ROM on to fix that; as well as to finally get rid of the chinese apps which annoyed me.
SO I downloaded a ROM from XDA https://forum.xda-developers.com/le-2/development/rom-lligera-t3538654 (thanks).
The device was unrooted and had the stock recovery.
I used the basic adb and fastboot command prompt applications. I already enabled developer mode in the phone and had also enabled debugging and unlocking boot loader.
In the adb/fastboot I entered the command to unlock "fastboot oem unlock" and "fastboot oem unlock go". IT would confirm and complete and then I went onto flash the recovery.
HERE IS WHERE THINGS DIDNT GO AS EXPECTED.
And I ended up doing this multiple times (i.e oem unlocking, and flashing recovery)
I tried using TWRP twrp-3.2.1-0-s2; and also downloaded a pack "Le2RootMegaPack" which had Letv-X620-Twrp-3.0.2-0 .
IT would complete successfully; but on reboot I would get an error message like "Orange State. Your phone can not be trusted" (this is not the exact message but close to it).
The message only seemed to come once as if I restarted it would disappear.
When I went back to fastboot it would say locked until i did over the fastboot oem unlock command (in other words I had to unlock everytime).
Also when I go to reboot; something about "Lock" would come in the command prompt statuses just before it rebooted.
It seems like the bootloader kept getting locked again.
So I could not boot into TWRP.
I then tried using the "fastboot boot xx.img" command which after several attempts and variations worked.
I flashed the Letv-X620-Twrp-3.0.2-0 and then "fastbook boot" booted from ANOTHER version of TWRP (as it would not boot using that same TWRP).
Then when the phone was about to restart I held up the volume up button and it booted to TWRP.
(That recovery (which I booted from) was from the ROM LeEco+x620+CM13+Rom+v145+by+Kangburra which I also downloaded from XDA.)
However the touch screen wouldnt work and I had to use a USB mouse (using the adaptors/OTG cable) and was able to control the phone in the TWRP.
I wiped the dalvik and cache and loaded the rom and it completed. then it asked to reboot which i did; and then it just wouldnt start.
The present status is that there is nothing on the Phone. I cannot boot to recovery nor to fastboot.
The only reaction I get from the phone is if I plug in a USB cable (charger). I have it plugged into the PC and the PC sound for when a device is plugged in and the sound for when a device is plugged out plays rapidly within 2-3 seconds (ie it connects/disconnects quickly).
The adb/fastboot commands do NOT work. The computer does not include it in devices etc.
I would therefore be grateful if I can have some assistance. I would like the phone to work again (obviously).
Thank you for your time.