okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
dorkydroid said:
okay, i had a slim rom running on my fire (5.1.1) and tried to go to cm12 using flashfire. i made sure that wipe was at the top of the list. it got stuck on installing the new rom, so after 30 minutes i restarted tablet. i got stuck in the cm logo bootloop. i do still have access to the amazon stock recovery. tried to do a data wipe/factory reset. still stuck at logo bootloop. i tried to sideload the amazon stock bin file, but it stops after 5 seconds and says "failed to read command: invalid argument" and goes back to the recovery main menu. if you try to do another sideload, it instantly says "timed out waiting for package. installation aborted" before you even press anything. have to restart device to try sideloading again.
at one point i had it almost install cm12 from a zip file through sideload, but at the very end it gave me a signature verification fail. since i can't boot the phone, i can't turn on usb debugging. sometimes it'll show up in the device manager as mtp but never shows up as fire or android device or any of that. it will show up on adb devices command when its in fastboot, but can't do anything with it from there. i've tried all the different ways in the forums here and rootjunky, but nothing seems to work at all. any ideas if i'm doing something wrong or is this just bricked, regardless of stock recovery?
tried a few commands to see if i could fastboot one of the roms or stock images, but they all tell me its missing the android-info.txt
Click to expand...
Click to collapse
try stock 5.1.2 firmware
otherwise there is no fix that I know of
Sent from my KFFOWI using XDA Labs
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
dorkydroid said:
i started trying to get it going, but got the same results. eventually the battery died and it doesn't want to charge anymore, so hopefully i'm still under warranty. thanks for all the help though, been a reader here for a really long time. just sucks to get a hard brick for the first time. used a droid x for four years straight with a locked bootloader and never came across a problem like this
Click to expand...
Click to collapse
I fear I'm in the same boat. Which version of flash fire were you using?
Any further progress?
Sent from my Nexus 7 using XDA-Developers mobile app
Related
Okay, so I decided to screw around with my HTC One again, and ended up trying the new Cyanogenmod installer. Needless to say, I have screwed my phone up worse than ever and I have no idea how to get it back. It is stuck in bootloader, I can't go into recovery or reboot or even power off. It just keeps rebooting to bootloader. I tried the RUU, but it comes back with an error that the image version isn't correct, and I tried flashing another recovery, but i still can't get into recovery. Right now, I am sitting in my bootloader with nothing to boot into. I can use ADB however, just please help me.
CaRBiiNeZz said:
Okay, so I decided to screw around with my HTC One again, and ended up trying the new Cyanogenmod installer. Needless to say, I have screwed my phone up worse than ever and I have no idea how to get it back. It is stuck in bootloader, I can't go into recovery or reboot or even power off. It just keeps rebooting to bootloader. I tried the RUU, but it comes back with an error that the image version isn't correct, and I tried flashing another recovery, but i still can't get into recovery. Right now, I am sitting in my bootloader with nothing to boot into. I can use ADB however, just please help me.
Click to expand...
Click to collapse
Try, "fastboot erase cache" and then try to go into recovery.
Sent from my HTCONE using Tapatalk
Long story short: Phone won't boot past "Unlocked Bootloader" warning; Recoveries won't stick; Unknown Error & Freezing when trying to Flash System.img
I own an ATT Locked Moto X, but went ahead and unlocked it by purchasing the oem code. No issues there.
I decided to go ahead and try rooting it too, and was able to flash TWRP as my recovery. Still, everything seemed to be looking good, until I tried hard rebooting (to see if root would last). Upon rebooting, I could not get past the warning sign, notifying me that the bootloader was unlocked. I waited, and waited, and restarted again, but all progress stopped there. I would be the first to admit that whatever happened was probably my fault; perhaps I flashed some files in the wrong order, or entered a wrong command into fastboot. I don't know, and frankly don't care. My only question is how to get out of this mess and back to rooting, or at the very least, back to stock ROM now that I'm unlocked.
Booting into recovery only leads to the red triangle over an open android mascot, with the "Android Recovery" title. So clearly TWRP didn't stick; I tried reflashing, but nothing lasts past reboot. Then I tried flashing Philz Touch instead, which, upon exit, notified me that root was not enabled. So I rooted, rebooted, and was finally able to see Philz Tough again, even though I still can't boot normally. That time, both Philz Touch as well as root seemed to have stuck.
With that minor victory I downloaded the latest firmware for my model and tried to flash the components over, thinking I had somehow corrupted the existing OS files, but here's where it gets particularly frustrating. I am able to flash every file except for system.img, even though I am using moto-fastboot, which I understand is a common mistake. I get no specific error code, simply "Unknown Error," upon which the phone is frozen in fastboot. The phone remains unresponsive until I hard reboot [back into fastboot], and see that, once again, Recovery is back to stock. So now I'm baffled. I can't seem to find a way to flash the system file, factory resetting doesn't work, and my recoveries are constantly reverted back to stock. Does anyone have any advice, or suggestions for what I could try next?
You try RSD lite?
Sent from my XT1058 using xda app-developers app
southern87 said:
You try RSD lite?
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
I was already downloading it just as I saw your post, as my last-ditch effort. It also failed, but it gave me "Unknown USB Error," which is all I needed, it seems. I tried a different USB slot on another side of the computer, and lo-and-behold, the flash finished.
I'm not sure what saddens me more, the fact that I pushed off making this post for hours, only to have the solution less than an hour after I do, or the fact that I never thought to try a different USB port... In any case, sorry for the uselessness of this post. I think I'll save rooting for another day though...
First and foremost I am a newb when it comes to rooting. I tried installing the newest Viper Rom on my phone and everything was successful until the phone tried to reboot. It is now stuck in the fastboot/bootloader screen and I cannot go into recovery mode at all. I tried doing a factory reset and it just keeps taking me back to the same screen.
I was running Cynogen MOD 4.4 Rom and everything was working fine. I backed up my phone and wiped my phone before I ran the Viper Rom. I don't know what happened and I'm kind of freaking out. I tried connecting my phone to my computer via USB when I run "fastboot devices" through the command prompt it keeps giving me "waiting on device". I did some research and everywhere kept saying that I needed to install the htc drivers through both htc sync manager and the individual driver files I found on the internet. I did everything possible and it still doesn't seem to recognize it.
I'm currently stuck/lost on what to do hopefully someone here can point me in the right direction. Attached is a screen shot of both my device manager and command prompt. I will continue to look on the internet for any type of answer. Thanks everybody.
(Sorry for starting a new thread I just didn't know where to put it.)
Does your phone boot? Can you get to recovery or bootloader?
Sent from my HTC One using Tapatalk
It boots but it keeps going back to the same screen where it says bootloader, factory reset, fastboot, etc... I had cwm installed but every time I push recovery it takes me back.
kal3l15 said:
It boots but it keeps going back to the same screen where it says bootloader, factory reset, fastboot, etc... I had cwm installed but every time I push recovery it takes me back.
Click to expand...
Click to collapse
Are you sure you selected sprint during setup? Maybe this is your solution http://forum.xda-developers.com/showthread.php?t=2503646
Sent from my HTC One using Tapatalk
I bought a VS980 last week and have been trying to flash a new recovery ever since. It is rooted, but when I try to reboot into recovery, the phone reboots and as soon as the LG splash shows up, the phone turns off. Not reboots, or freezes, or boot-loop, but just turns off. I have followed several different methods of flashing from different articles/guides i have found but all have the same effect. I have done a factory reset twice and tried to start fresh, but have the same result. I have done several options of using ADB Push to flash the recovery and I have tried to use, CWM, TWRP, Flashify, RomToolBox Pro, and GooManager apps to flash into recovery but I always have the same result. Phone reboots, LG Splash shows up for just a second, then the phone turns off.
I am about out of ideas. Please help!
usafmunk said:
I bought a VS980 last week and have been trying to flash a new recovery ever since. It is rooted, but when I try to reboot into recovery, the phone reboots and as soon as the LG splash shows up, the phone turns off. Not reboots, or freezes, or boot-loop, but just turns off. I have followed several different methods of flashing from different articles/guides i have found but all have the same effect. I have done a factory reset twice and tried to start fresh, but have the same result. I have done several options of using ADB Push to flash the recovery and I have tried to use, CWM, TWRP, Flashify, RomToolBox Pro, and GooManager apps to flash into recovery but I always have the same result. Phone reboots, LG Splash shows up for just a second, then the phone turns off.
I am about out of ideas. Please help!
Click to expand...
Click to collapse
Are you running JB or KK?
JB - Download flashify from the market and let it handle flashing the recovery
KK - Follow the directions here, steps 5-8 if you're already rooted and on 24A. - http://forum.xda-developers.com/showthread.php?t=2702958
mjones73 said:
Are you running JB or KK?
JB - Download flashify from the market and let it handle flashing the recovery
KK - Follow the directions here, steps 5-8 if you're already rooted and on 24A. - http://forum.xda-developers.com/showthread.php?t=2702958
Click to expand...
Click to collapse
Thank you so very much. The guide from the link you posted worked. You have just ended a week long battle for me and you have my thanks!
usafmunk said:
Thank you so very much. The guide from the link you posted worked. You have just ended a week long battle for me and you have my thanks!
Click to expand...
Click to collapse
Well I spoke too soon. I followed the guide in from the link, which did in fact allow me to reboot into TWRP, however, the phone seems to have been bricked in the process. I unless I use the hardware keys to reboot into recovery, the phone boots up completely blank. The screen is on, but it is black. I have tried to revert back to stock but I have not been able to. I followed all the directions found here:
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=download+fail
Still no luck.
usafmunk said:
Well I spoke too soon. I followed the guide in from the link, which did in fact allow me to reboot into TWRP, however, the phone seems to have been bricked in the process. I unless I use the hardware keys to reboot into recovery, the phone boots up completely blank. The screen is on, but it is black. I have tried to revert back to stock but I have not been able to. I followed all the directions found here:
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=download+fail
Still no luck.
Click to expand...
Click to collapse
Please can you describe anything that's going wrong? I.e. Can you access downloader mode?, Is your port set to COM41 (Note it does not set it automatically)?, Anything else that would give us an idea where the reverting back to stock process is going wrong?
TheOriginalKyle said:
Please can you describe anything that's going wrong? I.e. Can you access downloader mode?, Is your port set to COM41 (Note it does not set it automatically)?, Anything else that would give us an idea where the reverting back to stock process is going wrong?
Click to expand...
Click to collapse
Sure. I do not know if I am able to reach Fastboot or not. I can get into TWRP Recovery and request Fastboot, as well as hold the Up-Volume buttons on start, but the screen comes on blank after the LG icon goes away.
I can not see the device from my File Explorer in Windows. I have tried to remove each of the 3 devices that appear in my Device Manager and re-install them with the most recent drivers for my phone, which seems to work, but then I still cannot connect to it. The computer recognizes that a device has connected, but I guess I do not know how to transfer files if not through File Explorer or an ADB push.
I have tried to use ADB push but I cannot see any ADB Devices. Within TWRP, I have tried to use ADB Sideload, but the message '//twrp/backups/086c8bd70b935975' not found comes up and so it gets stuck on "starting ADB Sideload feature...."
When I use the "Mount" option in TWRP, Only Data and Cache is selected. I can select System, but I am not able to select USB-OTG
When trying to use the LG Flash Tool (and tried to change every port to 41 for each device I found in Device Manager), it fails with "Model: Unknown"..."device Model is different!"..."Check Phone or DLL!"...."00000000"
I think there were some other things tried too but that is all I can think of at the moment.
usafmunk said:
Sure. I do not know if I am able to reach Fastboot or not. I can get into TWRP Recovery and request Fastboot, as well as hold the Up-Volume buttons on start, but the screen comes on blank after the LG icon goes away.
I can not see the device from my File Explorer in Windows. I have tried to remove each of the 3 devices that appear in my Device Manager and re-install them with the most recent drivers for my phone, which seems to work, but then I still cannot connect to it. The computer recognizes that a device has connected, but I guess I do not know how to transfer files if not through File Explorer or an ADB push.
I have tried to use ADB push but I cannot see any ADB Devices. Within TWRP, I have tried to use ADB Sideload, but the message '//twrp/backups/086c8bd70b935975' not found comes up and so it gets stuck on "starting ADB Sideload feature...."
When I use the "Mount" option in TWRP, Only Data and Cache is selected. I can select System, but I am not able to select USB-OTG
When trying to use the LG Flash Tool (and tried to change every port to 41 for each device I found in Device Manager), it fails with "Model: Unknown"..."device Model is different!"..."Check Phone or DLL!"...."00000000"
I think there were some other things tried too but that is all I can think of at the moment.
Click to expand...
Click to collapse
Well new update: I was able to fix it! The problem was my own ignorance. I was following some Googl'd instructions to get the device into download mode that were incorrect. Once I saw the correct ones, I was able to get into Download Mode and revert to stock from there.
(Keep in mind all of this is happening without a OS on it after the sentence where i decied to format) New to the forums and still noobish at flashing roms and the like. But here is my delima, I had a kindle fire HD that i got years ago and flashed properly with the 2nd boot loader, TWRP ( I think at the time the version was like 2.7.0.0), and Pac-Rom, well wanting to try the Cyanogenmod and other roms, being a complete idiot I decided that I would format the device completely and flash a new rom and gapps because I have just had more success flashing that way. Anyway, I finish and was looking at roms on XDA and noticed that TWRP finially got updated to 3.0 so I assumed that I would finially get mass storage support over usb, like a flash drive. well that didn't end up working still, oh well no biggie i have used ADB a few times to push some roms over. So I find out ADB had a message to the extent of when I did the ADB devices command , the device was unauthorized. So I thought crap something must have gone wrong when I was updating to the new version, so ended up fastbooting into a version of TWRP 2.8.something, and that worked but my device was still unauthorized, so restarted, and now its in some odd boot loop, like the kindle fire logo will only stay up for a few seconds then shut down immediately, and just keep repeating like that, the blue logo won't show up and I cant boot into fastboot or into TWRP.
Does anyone know what went wrong or how to fix it. Huge thanks if you can!