Not quite sure what has gone wrong with my tablet but it seems that my recovery partition has been wiped (no recovery) and my boot.img has also gone.
What caused it:
I was installing Ubuntu onto my Prime and I got to the stage where I flash the boot.img. However, fastboot said it was sending the file, then writing the file and reported both "<OKAY>". However, I am not receiving a blue bar as other people say they do, yet I have done before when following the NVFlash guide (yes, I have all my blobs and things backed up).
Anyway, I have tried installing the Universal Driver and it seems to work (shows up in Device Manager). However, any commands that I send to the tablet do not seem to work (fastboot FLASH COMMANDS).
Commands I've entered: fastboot -i 0x0b05 flash boot prime-sdlinux.blob, fastboot -i 0x0b05 flash recovery twrp.blob
Also, "commands such as fastboot -i 0x0b05 erase recovery" result in: erasing 'recovery' ... FAILED (command write failed (Unknown error))
I'm really stuck and it's getting late, not sure what to do. Hope you guys can help me out.
PS: Not sure if this helps but, I cannot turn off the device. It constantly reboots just to hang at the Asus Eee Pad Screen or to hang at the Fastboot screen (when volume_down is held).
EDIT: After troubleshooting some more I have found that uninstalling the naked driver and letting Windows find a driver will actually allow me to send a reboot command (and it'll work). However, any fastboot flash commands do not seem to work. No Progress Bar appears and any commands sent after a flash command do not work (can't reboot after sending a flash command).
Hold the volume up while pressing the power button for about 15 seconds or until it vibrates then release them and it should power off for you.
did you make an nvflash backup?
else try
Code:
downloaded the latest Virtuous Prime ROM.
extract the ZIP file and pull the file called 'blob'
rename the file as boot.blob and move it to the TOOLS folder and open Command Prompt
from the TOOLS folder, type: fastboot -i 0x0b05 flash boot boot.blob
then type: fastboot -i 0x0b05 reboot
this should make you capable to go to recovery again
Open a command prompt; type adb push virtuous_prime.....zip /sdcard/
Wait until you get a confirmation message
Flash the rom like you normally do
Done
found this solution somewhere....
I do have an NVFlash backup, just not with me right now. Will test the above method first. And thanks for the method of turning it off! Although I know it's still on. Just in APX mode.
EDIT: Windows XP (run through VirtualBox on my laptop) seems to pickup my tablet in fastboot devices now. However, I'm still not seeing a progress bar after flashing again, and have the same problems as before (cannot reboot from fastboot). Still doesn't work. I've run fastboot through a native Windows 7 machine and a Windows XP installation on a Mac. Not sure what else I can try if fastboot isn't working.
EDIT2: It seems that I no longer have the error "FAILED (command write failed (Unknown error))" with certain commands.
First, you are in the wrong section, it should be in Q&A.
Second why didn't you try nvflash?
See this: http://forum.xda-developers.com/showpost.php?p=29204285&postcount=228
I believe the reason why fastboot is not working is because you are flashing blobs whilst using AndroidRoot.mobi bootloader.
http://forum.xda-developers.com/showpost.php?p=28875606&postcount=80
I believe you'll have to blobunpack the blob and then flash the raw img files instead.
That actually makes perfect sense! Would have taken me ages to figure out by myself. Thought it was perm-bricked until I got back to my NVFlash backup files. Will try it out.
kokopuphz said:
I believe the reason why fastboot is not working is because you are flashing blobs whilst using AndroidRoot.mobi bootloader.
http://forum.xda-developers.com/showpost.php?p=28875606&postcount=80
I believe you'll have to blobunpack the blob and then flash the raw img files instead.
Click to expand...
Click to collapse
I was in a similar situation until someone pointed me in this direction. Using BlobUnpack on both recovery and boot images gives you boot.LNX.SOS and Recovery.img.SOS (or similar names)
Flashing these solved my issues.
Yea, it worked. Thanks a lot for the help guys. Just takes one extra step to flash something now, kinda annoying, but definitely worth knowing that your tablet is brick-proof.
Related
I have bricked or atleast semi bricked my Folio and i dont know if it can be fixed. It began with damaged internal sd, so i try the format zip but no luck. May device have been like this 3 days now. I NEED HELP, AND YES I HAVE ASKED IN GENERAL SECTION. but i didnt get an answer for days. I need help by someone who can tell me how to set up fastboot. My folio boots i can get to clockwork recovery and i can get in to fastboot mode. I have working ADB on my computer. The install fails when recovery is writing boot.img iget this message: assert failed
write_raw_image("/cache/boot.img", "linux")
E:Error in /sdcard/FolioMod.zip
(Status 7)
It installs system.img fine. So i was thinking i could fastboot boot.img to the device and maybe it boots. So i put Folio in Fastboot mode,insert usb, and update driver, go to command prompt and write fastboot devices all i get is:
? fastboot
Is there anything special i have to keep in mind to setup fastboot for Folio. I used the fastboot that came with SDK. Do i have to add something more to .inf file for fastboot? Do have to use any special fastboot just for Tegra2 devices? Is my fastboot mode damaged? Please i need help i have waited for days in general section not one answer. Hoping on better luck here in the dev section
Are you on Windows or linux?
Normally if adb is working, fastboot should be working too. Just boot your folio into fastboot mode and connect it to your pc. Type 'fastboot devices', if something shows up you are fine (might be just a bunch of ???s).
Otherwise (on win) you need to modify the driver a little. There is a howto around here. I will add a link when I found it.
€: http://www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
But I think if adb is already working, you will be fine. Just make sure you have a recent version of fastboot from the android sdk. Older versions are incompatible with tegra2 based devices.
mblaster said:
Are you on Windows or linux?
Normally if adb is working, fastboot should be working too. Just boot your folio into fastboot mode and connect it to your pc. Type 'fastboot devices', if something shows up you are fine (might be just a bunch of ???s).
Otherwise (on win) you need to modify the driver a little. There is a howto around here. I will add a link when I found it.
€: http://www.addictivetips.com/mobile/enable-adb-usb-drivers-for-nvidia-tegra-based-android-tablets/
But I think if adb is already working, you will be fine. Just make sure you have a recent version of fastboot from the android sdk. Older versions are incompatible with tegra2 based devices.
Click to expand...
Click to collapse
I had entered the part to .inf file but havent done the echo part in command prompt, will try now. Its weird as hell all i get when writing fastboot devices is a ? fastboot. Its a windows Vista 32 im using and SDK 08. And when i enter this echo 0x955 i just get that its the wrong path.
I got fastboot working didnt know it could be ? fastboot when it was connected. I kept getting it so i tryed to send some commands and it got thru. **** so i have had it working for days. I have flashed the boot.img via fastboot and am now trying to do an advanced restore of a nandroid. Will see how it goes. If its not working can i flash system.img and boot.img? Will that work? Well atleast now i can flash standard recovery and send it to toshiba
Probleem Solved Thank you mblaster, you wrote it could look like this when writing fastboot devices: ?????? or atleast something like it so i thought maybe i am connected as my said: ? fastboot . So i tryed some commands and they got thru. So to anyone who tryes to install fastboot try commands. I was waiting for days(dumb, i know). So now im back and kickin, watch out
Moved to proper forum
Guys, i have a slight problem here. I want to install a custom rom on my dell streak. The guide that i am following is from Benny's blog (http://leemn.wordpress.com/2011/02/...from-eclair-2-1-build-6941-to-stephens-1-5-1/)
What I've done:
1. Installed Android SDK (Updated the given updates, as in the screenshot. SCREENSHOT
2. Installed Dell's Windows Drivers from here (ftp://ftp.dell.com/Handheld/R288920.exe)
3. Installed Dell Mobile Sync
4. Downloaded the Fastboot tool from here (http://download143.mediafire.com/pcxqstv8scfg/yd21znuyj14/1.8.1.7-streak-clockworkrecovery.zip) , Renamed the fastboot-windows.exe to fastboot.exe .
5. Downloaded SteakDroid 1.9.0 and renamed it to Update.zip and copied it to the root of my SD card.
6. Downloaded the current version of the baseband as recomended.
7. Made a folder in C drive named Streak and extracted the clockworkrecovery.zip there. Copied the baseband into the same folder as well.
I believe these steps were all correct.
Now however, i am stuck .
8. After my streak is in the FASTBOOT_MODE , waiting for the usb connection, i connected the USB cable to my computer.
9. It said that a new device Android 1.0 has been found.
10. I choose to choose the drivers by my own, and The only drivers that were available is Android ADB interface and Android Composite ADB interface. If i were to click show compatible hardware, then only the Android ADB interface driver would be shown. SCREENSHOT
11. If i were to choose any 2, the drivers would install fine, and FASTBOOT_MODE would show up in my streak.
12. I entered into the commandline (run > cmd) and went to the C:\streak directory. Once i ran the command, fastboot devices, nothing is listed. When i ran the command fastboot reboot, all it says is waiting for device and that is it. SCREENSHOT
I tried this on a second computer, and its the same thing. I believe i should see the "ANDROID BOOTLOADER INTERFACE" driver, to proceed with the flashing. SCREENSHOT
However, i am not seeing such options on both computers, that are running Windows XP SP3.
What should i do?
It happened to me with my XP machine, no matter what I did, bootloader driver wont show up.
Ended up using a win 7 one with no problem installing the driver.
And "fastboot devices" command doesn't work for me no matter what i tried.
I would suggest you try "fastboot -i 0x413c reboot" w/o the quotes. If your streak reboots, that means fastboot it's working and you can go on with the flashing, e.g.
fastboot -i 0x413c flash recovery recovery.img
fastboot -i 0x413c flash dsp1 dsp1.mbn
fastboot -i 0x413c flash amss amss.mbn
etc.
"fastboot devices" wasted hours of my life without realizing fastboot is already working....
PS: one get around of NOT having a win 7 machine is to install pdanet program(google it). It will install the necessary drivers to get you started, just test with "fastboot -i 0x413c reboot" to see if your fastboot is working
PPS: NEVER do any erase with fastboot like fastboot -w or any sort, it will brick it... guarantee
asianftw said:
It happened to me with my XP machine, no matter what I did, bootloader driver wont show up.
Ended up using a win 7 one with no problem installing the driver.
And "fastboot devices" command doesn't work for me no matter what i tried.
I would suggest you try "fastboot -i 0x413c reboot" w/o the quotes. If your streak reboots, that means fastboot it's working and you can go on with the flashing, e.g.
fastboot -i 0x413c flash recovery recovery.img
fastboot -i 0x413c flash dsp1 dsp1.mbn
fastboot -i 0x413c flash amss amss.mbn
etc.
"fastboot devices" wasted hours of my life without realizing fastboot is already working....
PS: one get around of NOT having a win 7 machine is to install pdanet program(google it). It will install the necessary drivers to get you started, just test with "fastboot -i 0x413c reboot" to see if your fastboot is working
PPS: NEVER do any erase with fastboot like fastboot -w or any sort, it will brick it... guarantee
Click to expand...
Click to collapse
I tried installing PDA NET but it still installed with the same ADB drivers.
However, the command "fastboot -i 0x413c reboot" reboots the streak! So i shall try the flash
Edit:
Got everything working as in the steps, right until the update.zip part.
However, i ran into some error.
Here it is:
Steps followed:
Switch off the phone
Boot the phone into recovery mode by holding vol up + vol down + power simultaneously
You will see a black screen with white writing (vol buttons are up/down, camera button is enter/ok)
Select* ”Software upgrade via Update.pkg on SD Card”
You will now be on a black screen with green writing
Select* ”apply sdcard:update.zip”
Scroll* down to “Yes – Install /sdcard/update.zip)
This will load and install the update
Click to expand...
Click to collapse
Mine would say
Fotmatting System
Copying Files...
Creating Symlinks
Creating Some More Symlinks
Last Lot OF Symlinks Being Created
Setting Permissions
Kernel:Installing
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Then it would reboot the device after awhile, and i'll be back to the normal 2.2.2.
This is a screenshot of the error screen: SCREENSHOT
EDIT!! SOLVED MY ISSUE!! ITS FLASHED NOW!!
Quote from someone who guided me on a different forum. Thanks to him!!
1 - u need to install CWM via fastboot
2 - press on 2nd option will bring u to another new menu ...... if it start to install from update , means u failed ..... After installing CWM , DO NOT reboot into your ori 2.2 or else the CWM will get replaced by original recovery . Which means once u install the CWM , key in " -fastboot -0x413c reboot " and hold the 2 volume button while it reboot ..... it will take u to recovery straight after restart
3 - Choose option ( 2 ) which u bring to u to CWM
4 - Select Steven's zip file from there ....option 4 i think , cant remember correctly which is " install zip from sdcard "
Click to expand...
Click to collapse
arvin2212 said:
I tried installing PDA NET but it still installed with the same ADB drivers.
However, the command "fastboot -i 0x413c reboot" reboots the streak! So i shall try the flash
Edit:
Got everything working as in the steps, right until the update.zip part.
However, i ran into some error.
Here it is:
Steps followed:
Mine would say
Fotmatting System
Copying Files...
Creating Symlinks
Creating Some More Symlinks
Last Lot OF Symlinks Being Created
Setting Permissions
Kernel:Installing
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Then it would reboot the device after awhile, and i'll be back to the normal 2.2.2.
This is a screenshot of the error screen: SCREENSHOT
EDIT!! SOLVED MY ISSUE!! ITS FLASHED NOW!!
Quote from someone who guided me on a different forum. Thanks to him!!
Click to expand...
Click to collapse
Glad to hear Clockworkmod works for you!
Clockwork mod working
Yeah, I wasn't able to get the Clockwork mod to work for me, I kept getting a message about "E:can't find MISC:" and it would hang up from there. Would get the same message if I tried to do a nandroid backup also. So I installed Streakmod and my problems were solved. BTW I had to use a Windows XP computer to get my Streak flashed, none of my 3 W7 laptops would act right, pretty sure it was a driver problem but I was able to resolve it on those.
Another question while I am here, anyone know what has to be done to keep the Streak from random reboots????
cdzo72 said:
Yeah, I wasn't able to get the Clockwork mod to work for me, I kept getting a message about "E:can't find MISC:" and it would hang up from there. Would get the same message if I tried to do a nandroid backup also. So I installed Streakmod and my problems were solved. BTW I had to use a Windows XP computer to get my Streak flashed, none of my 3 W7 laptops would act right, pretty sure it was a driver problem but I was able to resolve it on those.
Another question while I am here, anyone know what has to be done to keep the Streak from random reboots????
Click to expand...
Click to collapse
Did you do a full factory reset?
Did you use the clear cache / dalvik cache option from the cwm menu?
I have done all those and have not had any random reboots.
**Just so you know, i've never experienced any random reboots with the streak.
Random reboots
Well I honestly think my problem has more to do with the battery cover than anything else.
Phone wise my streak doesn't lag, doesn't hang up. I can't remember the last time I got some type of error message from having to force close a program, thus taking that into consideration, I would be hard pressed to believe that I have a problem with my installation or maintenance.
I read somewhere about a fix for the battery compartment slide cover, but it's been a week now and I haven't been able to come across it again. Hoping someone else has seen it and can point me there.
cdzo72 said:
Well I honestly think my problem has more to do with the battery cover than anything else.
Phone wise my streak doesn't lag, doesn't hang up. I can't remember the last time I got some type of error message from having to force close a program, thus taking that into consideration, I would be hard pressed to believe that I have a problem with my installation or maintenance.
I read somewhere about a fix for the battery compartment slide cover, but it's been a week now and I haven't been able to come across it again. Hoping someone else has seen it and can point me there.
Click to expand...
Click to collapse
I believe i've read somewhere that the older versions of the streakdroid roms <1.9.1 has the sensors disabled for rebooting once the cover is loose. Try that
I cannot get fastboot to find my TF201. I ran the unlock tool tonight on my stock .21 prime. I have booted into fastboot usb download mode with the Power + Vol Down, wait for RCK to pass, then Vol Down to select fastboot then Vol Up to confirm.
I have tried under my native Ubuntu 11.10 x64 install and Windows 7 x64. Under windows, I removed my already installed SGS2 drives and replaced them with the Naked 0.61 Drivers as found here: [ADB/FB/APX Driver] Universal Naked Driver Beta 0.6.1. I rebooted Windows and tried again to no luck:
Code:
./fastboot devices
or
Code:
fastboot.exe devices
as per respective OS.
Each command just echos an empty line, any tips?
EDIT:
I just went for it anyway and it apparently flashed the recovery
Code:
fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.1.8-tf201.img
but now I am sitting with a completed blue progress bar and am scared to reboot the device.
EDIT 2:
I took a leap and power cycled the device, looks like recovery is in and good to go. Looks like since we need to specify the vendor_id for our devices, the devices command, or anything else for that matter fails to work properly (fastboot reboot, fastboot devices, etc.).
Hope this will help anyone else having issues.
Thanks.
SOLVED fastboot does not find device
Would like to expand your answer!
i am working with asus transformer prime TF201
i had a problem (SOLVED) where fastboot would not find device.
Code:
<waiting for device>
i fixed it by specifying asus vendor id (in this instance i was flashing a new recovery)
Code:
./fastboot -i 0x0b05 flash recovery recovery.img
Hope this helps it took me 2 days to figure that out
PEACE!
Thanks!
I ran into the same issue where the TF201 was not shown as a device.
You saved me from hours of pain!
how ot change vendor id
I'm having the same problem; need to install twrp via fastboot, but windows does not recognize the device. I have 'waiting for device'.
Can anyone explain how to change/specify the vendor id?
EDIT: nevermind, the 0x0b05 is the vendor ID, I already did that but the problem remained. In the end I switched computers and this solved it.
I'm having a somewhat similar problem except I connect my Prime and I see a serial, but it's not the serial of my Prime. I run the command:
fastboot -i 0x050b flash recovery flatline_tf201.img
and I get the message that it copied successfully, but I don't see any blue progress line and when I boot into recovery, I get the triangle; presumably because there is no recovery image.
I've tried it from three different windows systems (2 64bit and 1 32bit) with the same results. I am also unable to connect via ADB.
Any suggestions?
My phone is HTC Desire. Using to enter fastboot to install 4EXT recovery but failed
I can use adb command form cmd.
E:\sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT0ARPL02347 device
But When I restart my phone and enter to FASTBOOT is shows FASTBOOT USB in the screen but nothing happen when I issue command "fastboot devices"
E:\sdk\platform-tools>fastboot devices
E:\sdk\platform-tools>
I am trying to fix my soft-bricked phone that's stuck in a bootloop. Phone was rooted and working fine until I flashed an incompatible TWRP recovery through Flashify and rebooted. I've Googled for weeks and put up a few other related posts here asking for help but haven't gotten much traction. I do have a backup of the stock recovery in .IMG format, as well as a complete Nandroid system image, also in .IMG format.
With those, I figure I should be able to re-flash it and be done, but that would be too simple. ADB debugging was enabled on the phone before it broke, but ADB commands are out since it doesn't make it far enough in the bootloop to connect to my PC. Fastboot works. If I remove the battery from the phone and plug in the USB it boots directly into fastboot. Device manager lists it under Android phone: Android ADB interface, and some fastboot commands work. fastboot devices returns my phones info, and fastboot reboot bootloader will reboot the phone back into fastboot. Anything else however, is a no-go. I've tried fastboot erase recovery, fastboot boot recovery.img, fastboot flash recovery recovery.img, etc.
All either hang (i've waited up to an hour) or give me the error "command write failed (no error)". I've tried Googling the error and haven't found a concrete answer on what it means or how to fix it.
So far I have tried:
Running fastboot from a command window with admin privileges.
Five different USB cables.
Used every USB port on my PC (at least two, if not all of them are USB 2.0. I know fastboot doesn't like 1.0 or 3.0 ports.)
Using the latest version of fastboot.
Tried a slew of different drivers for the phone (at least seven).
Tried using three different OS's (Win 8, Win 8.1, and Ubuntu).
Tried a few different fastboot GUIs just to make sure I was getting the commands right.
All to no avail. The only thing I haven't tried is another PC and that's only because I din't have one. So, bottom line, the only two ways to unbrick the phone without some special piece of hardware are ADB commands or something that relies on ADB connectivity like SP phone tool or QFIL, or by fastboot comands. ADBs out and fastboot won't play nice. At this point i'm tempted to have a round of phone V. blender. Seriously though, i'm out of ideas. If anyone sees anything I haven't thought of please let me know.
Jesseb342 said:
I am trying to fix my soft-bricked phone that's stuck in a bootloop. Phone was rooted and working fine until I flashed an incompatible TWRP recovery through Flashify and rebooted. I've Googled for weeks and put up a few other related posts here asking for help but haven't gotten much traction. I do have a backup of the stock recovery in .IMG format, as well as a complete Nandroid system image, also in .IMG format.
With those, I figure I should be able to re-flash it and be done, but that would be too simple. ADB debugging was enabled on the phone before it broke, but ADB commands are out since it doesn't make it far enough in the bootloop to connect to my PC. Fastboot works. If I remove the battery from the phone and plug in the USB it boots directly into fastboot. Device manager lists it under Android phone: Android ADB interface, and some fastboot commands work. fastboot devices returns my phones info, and fastboot reboot bootloader will reboot the phone back into fastboot. Anything else however, is a no-go. I've tried fastboot erase recovery, fastboot boot recovery.img, fastboot flash recovery recovery.img, etc.
All either hang (i've waited up to an hour) or give me the error "command write failed (no error)". I've tried Googling the error and haven't found a concrete answer on what it means or how to fix it.
So far I have tried:
Running fastboot from a command window with admin privileges.
Five different USB cables.
Used every USB port on my PC (at least two, if not all of them are USB 2.0. I know fastboot doesn't like 1.0 or 3.0 ports.)
Using the latest version of fastboot.
Tried a slew of different drivers for the phone (at least seven).
Tried using three different OS's (Win 8, Win 8.1, and Ubuntu).
Tried a few different fastboot GUIs just to make sure I was getting the commands right.
All to no avail. The only thing I haven't tried is another PC and that's only because I din't have one. So, bottom line, the only two ways to unbrick the phone without some special piece of hardware are ADB commands or something that relies on ADB connectivity like SP phone tool or QFIL, or by fastboot comands. ADBs out and fastboot won't play nice. At this point i'm tempted to have a round of phone V. blender. Seriously though, i'm out of ideas. If anyone sees anything I haven't thought of please let me know.
Click to expand...
Click to collapse
Your computer must not be properly communicating with your device, Have you tried ANY other fastboot commands other then what you mentioned?
Can you provide a screenshot of your fastboot commands failing? Perhaps something else is going on other then what you've provided. You never know.
As mentioned in the post #2, uninstall any drivers you have and install the latest fastboot and adb drivers v1.4.2
(here) and the drivers given by your OEM, followed by a reboot and then type these:
Code:
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot erase customize
Flash the stock boot.img
Code:
fastboot flash boot filename.img
Then boot into your recovery:
Code:
fastboot boot filename.img
Then perform a factory reset from the recovery itself.
Sent from Lord Tywin's athene (xt1643)
tywinlannister said:
As mentioned in the post #2, uninstall any drivers you have and install the latest fastboot and adb drivers v1.4.2
(here) and the drivers given by your OEM, followed by a reboot and then type these:
Code:
fastboot devices
fastboot erase userdata
fastboot erase cache
fastboot erase customize
Flash the stock boot.img
Code:
fastboot flash boot filename.img
Then boot into your recovery:
Code:
fastboot boot filename.img
Then perform a factory reset from the recovery itself.
Sent from Lord Tywin's athene (xt1643)
Click to expand...
Click to collapse
Thanks for the reply. I picked up a new cable today just to be absolutely sure that wasn't the cause of my problems. I've tried several already, but most of those were dollar store cables and iffy at best. No luck though, even with a brand new semi-good quality cable (Duracell) it still doesn't work.
I followed all the above steps. First I made sure the correct OEM drivers were installed. Device manager shows "Android phone: Coolpad Android ADB Interface" when I plug the phone in. I'm not 100% sure that this is the correct driver for my phone, though it is a Coolpad, and I know there is some universality between drivers. I've used both ADB and fastboot commands on my Kindle fire many times with only the generic Google ADB / fastboot driver and never had a problem. Also, the Coolpad driver I found was on a Chinese file sharing website (Baidu) listed under the Coolpad section and was just titled phone driver.rar so i'm guessing it's universal for Coolpads. That, and the fact that the phone does respond to some commands makes me think that the driver isn't the issue either. Next, I followed the posted link and downloaded the latest ADB and fastboot files and installed them. I then moved my recovery.img and my 801es.img (nandroid backup) to the ADB / fastboot folder and opened an admin command window. Here are the results:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
1edf2f7a fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\Program Files (x86)\Minimal ADB and Fastboot>
These would seem to indicate that fastboot is working properly, but upon trying your suggestions I don't get past the second command.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
Then nothing. I've waited 10 minutes and no change. I get similar results trying to erase recovery, boot the recovery.img, and flash the recovery.img.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase recovery
erasing 'recovery'...
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (10240 KB)...
All these net a similar response. Waiting 10 to 15 minutes after each command and still no activity.
I'm stumped.
Just a minor update. I got a second-hand Kindle fire for my son. I thought it was one of the 50 dollar ones they're selling now since it was in plastic behind glass in a locked case and all it said was Kindle fire 7 inch. Dated 1-3-17. For 20 bucks I thought what the heck. Well, upon getting it home and tinkering with it, I quickly discovered it was a Kindle fire 2nd gen from 2012. Still not bad for 20 bucks as the thing was pristine, but I hated the UI. After a little bit of digging, I discovered that you could easily install TWRP, Gapps, and Cyanogenmod 11 on it. All info I found here (surprise surprise, I love this site.) Now that's done and my son loves his tablet. It's just like a proper Android tab.
Anyway, anyone who's tinkered with older Kindle devices knows about fastboot cables (and yes, I did need one, dang bootloops!). I thought I would try the fastboot cable on the stubborn Coolpad. Still no go. So at this point, either the images I have are invalid and I can't get new ones (weeks of Google searches have turned up zip as far as a stock rom for this phone), or the phone is locking me out due to some non-standard security feature. I'm thinking the second. I can understand if the images I have are bad, but that shouldn't affect things like querying the lock status of the bootloader, or trying to erase the boot partition and not getting a response.
I'm out of ideas. If anyone knows anything about this, specifically if this is unique to Coolpads, please let me know. Otherwise, the phone is going to end up in a drawer, probably forever. Thanks.
Jesseb342 said:
I am trying to fix my soft-bricked phone that's stuck in a bootloop. Phone was rooted and working fine until I flashed an incompatible TWRP recovery through Flashify and rebooted. I've Googled for weeks and put up a few other related posts here asking for help but haven't gotten much traction. I do have a backup of the stock recovery in .IMG format, as well as a complete Nandroid system image, also in .IMG format.
With those, I figure I should be able to re-flash it and be done, but that would be too simple. ADB debugging was enabled on the phone before it broke, but ADB commands are out since it doesn't make it far enough in the bootloop to connect to my PC. Fastboot works. If I remove the battery from the phone and plug in the USB it boots directly into fastboot. Device manager lists it under Android phone: Android ADB interface, and some fastboot commands work. fastboot devices returns my phones info, and fastboot reboot bootloader will reboot the phone back into fastboot. Anything else however, is a no-go. I've tried fastboot erase recovery, fastboot boot recovery.img, fastboot flash recovery recovery.img, etc.
All either hang (i've waited up to an hour) or give me the error "command write failed (no error)". I've tried Googling the error and haven't found a concrete answer on what it means or how to fix it.
So far I have tried:
Running fastboot from a command window with admin privileges.
Five different USB cables.
Used every USB port on my PC (at least two, if not all of them are USB 2.0. I know fastboot doesn't like 1.0 or 3.0 ports.)
Using the latest version of fastboot.
Tried a slew of different drivers for the phone (at least seven).
Tried using three different OS's (Win 8, Win 8.1, and Ubuntu).
Tried a few different fastboot GUIs just to make sure I was getting the commands right.
All to no avail. The only thing I haven't tried is another PC and that's only because I din't have one. So, bottom line, the only two ways to unbrick the phone without some special piece of hardware are ADB commands or something that relies on ADB connectivity like SP phone tool or QFIL, or by fastboot comands. ADBs out and fastboot won't play nice. At this point i'm tempted to have a round of phone V. blender. Seriously though, i'm out of ideas. If anyone sees anything I haven't thought of please let me know.
Click to expand...
Click to collapse
First off, the information contained in your post doesn't really gives anybody a clue on how to help you. Phone model, previously working android version, rooted or stock etc. That would be a good place to start
Iamst.ralph said:
First off, the information contained in your post doesn't really gives anybody a clue on how to help you. Phone model, previously working android version, rooted or stock etc. That would be a good place to start
Click to expand...
Click to collapse
The phone is a Yulong Coolpad model 801 ES. I was running stock 4.1.2 JB ROM rooted with Kingroot. Developer options were unlocked and allow ADB debugging was checked. ADB and Fastboot drivers were installed and working properly as I was able to make a backup of my recovery partition and a "Nandroid" image. Note, the Nandroid image wasn't made using a custom recovery, it was made using DFS Evolution phone tools. It said Nandroid backup, and it did generate a file named 801es.img that's roughly 248 mb. I can't tell what partition it is since it has a non-standard header. Every image kitchen I've tried to use tells me bootmagic is missing when it tries to unpack.
The phone was working fine until I flashed an incompatible TWRP recovery. Now I'm stuck in a bootloop. I can get into fastboot mode, but every command I send other than fastboot devices and fastboot reboot ( like fastboot boot recovery.img, fastboot flash recovery recovery.img, fastboot erase recovery, fastboot flashing unlock, ...) just hang. I've waited for over an hour on some and they still didn't complete. I've tried every USB port on my PC, 6 different cables, three different OS's (Win 8, WIn 8.1, and Ubuntu), and a second PC (my laptop) to try and eliminate all possible problems. All that and still no luck. This phone just will not respond to fastboot commands like it should and I have no idea why.
Hopefully that answers all your questions. Maybe you have some ideas.
Your phone is obviously a MTK phone hence fastboot commands get stuck. Search for the firmware of your phone on Google and download it, download Sp flashtool. When you're done downloading, post here
I have similar issues with a Coolpad Defiant 3632A. All commands except for [fastboot devices] and [fastboot getvar] everything else returns - "FAILED (remote: unknown command)".
My fastboot has a Secure Phone text in white at the bottom left of the screen when im in the bootloader. Not long back this was not the case and i'm not sure what is causing it.
GETVAR Results
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version:0.5_emmccid_secureboot
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4082000
(bootloader) variant:MTP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1ff00000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x10dffbe00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x80000000
(bootloader) serialno:1f59cc3d
(bootloader) kernel:lk
(bootloader) product:QC_REFERENCE_PHONE
all:
finished. total time: 0.100s
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!