A friend sent me his KF HD that was bootlooping. He's had it forever running a custom rom. I was able to repair and get Lineage 14.1 loaded with Nano GAPPS. All was working fine until I attempted to flash SuperSU.zip in TWRP.
Current situation -
- bootloop on KF orange logo (will NOT continue on to blue TWRP version of logo)
- able to access fastboot with factory cable
- fastboot commands work correctly
- KFFirstAide won't fix it (manually ran the various menu items since the dropbox links are all no longer working)
- KF Java Utility (with the bootloop fix buttons) won't work
- KFHD SRT (tried 3 versions) all run, but won't fix
- pretty much scoured all of these forums for any fixes - boot images, recovery images all load correctly
Things I've noticed - formatting of partitions fail, and it almost looks like they are corrupt in some instance and have lost their type (example EXT4 for userdata)
He doesn't have a backup of his stock partitions before he originally rooted and loaded a custom ROM.
Is there anyplace I can download stock partitions to re-load one at a time until I can figure out which one is borked? Anyone else have any other ideas? PLEASE don't just respond with 'try KFFirstAide'. Been there, done that, doesn't work.
Related
Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app
SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.
SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.
Hello...just rooted by Kindle Fire HD. I was able to successfully root and boot into recovery. (TWRP) My goal was to install a Jelly Bean ROM. I was able to boot into recovery, got my zip files on the SD card. Took a back up (did not do data due to not enough space) Did a full wipe (both cache) and tried to install the JB zip file. Got an error that it could not open the zip file, so I just thought I'd restore from the back up. Now, when I try to power on, it just goes to the orange (or yellow, color blind) and continues to just loop. I've tried adb, but the loop does not let my PC recognize the tablet in time for me boot into recovery. Tried holding the volume up while powering up and still can't get in. Only thing I do not know (don't think I did) was install the firefirefire bootloader, but like I said, I've been into recovery before. Also, if I remember correctly, debugging is on. Any help would be appreciated.
Sir,
Please wait until mods will move this thread to the device specific forum.
For more replies or questions you must register an account on XDA forums.
Stand by
Good luck
Hi,
I used KFHD SRT 1.3.5 to recover KFHD 7 (2012) from "Red Screen Of Death" successfully and it even updated itself to 7.5.1.
But it again developed RED screen falt within a day. Now even if I use different KFHD SRT versions right from 1.2 to 1.3.5 it is not recovering.
I also tried using bootloader, boot, recovery from Amazon 7.5.1 update.zip However it went till your Kindle cannot boot Reset or Reboot option screen.
Can I get system.img for 7.5.1 ? or is it due to some other fault.
Kindle Android Gurus, Please help
Using fastboot directly or KFHD SRT scripts, I can oem format, erase, flash xloader, bootloader, (Amazon/SRT) boot.img, (Amazon/SRT)recovery.img, (SRT) system.image successfully. but still the device does not boot up. Can expert throw light on this behavior.
How should I go about Is it hardware fault?
Now it has progressed upto TWRP but still no luck
Now I can go into TWRP after using MLO-pvt and u-boot-prod from Stock ROM 7.2.3 and then flashing 2nd Bootloader, TWRP recovery and freedom boot.img
However in mount menu, I am not able to mount data, cache, system partitions. Sometimes if I repair/format these partitions they can be mounted.
However it always say storage cannot be mounted....
Still struggling to get it back working. As stated earlier SRT worked only once and system got upgarded to 7.5.1 but now no version of SRT works.
I might be able to help
In TWRP project Hold down your power button and it should asy slide to unlock slide it then reboot back into recovery and it should work. if not click on wipe in twrp then advanced select everything then wipe then factory wipe then go back to advanced and wipe dalvik cache and cache then hold power button and slide to unlock then reboot back into recovery and try to flash something.
I came across another thread that seemed to help me a bit. Can't find it again. So, hoping someone can point me in the right direction or better yet, give me a magic solution
History - I have a kindle fire - 5th gen. Got it with 5.1.2 which upgraded automatically to 5.1.4. I sideloaded 5.1.2 and it worked just fine. However, I missed the fact that the bootloader is locked on 5.1.2 and tried to flash TWRP. I also blocked OTA updates. (Rootjunky's tool)
Current situation - I am rooted and on 5.1.2. I want to get to Cm 12.1, but I can't get into recovery at all. It is stuck on the "Amazon" logo when I try to get to recovery. It is not the blue logo - I have never seen it, but my logo's not blue. I'm able to boot normally and use the tablet without any issues.
Question - The thread I came across earlier said that a fastboot cable is the only way out. But this person seemed to be at the "blue amazon" logo. Help? Thoughts?
smvsmv said:
I came across another thread that seemed to help me a bit. Can't find it again. So, hoping someone can point me in the right direction or better yet, give me a magic solution
History - I have a kindle fire - 5th gen. Got it with 5.1.2 which upgraded automatically to 5.1.4. I sideloaded 5.1.2 and it worked just fine. However, I missed the fact that the bootloader is locked on 5.1.2 and tried to flash TWRP. I also blocked OTA updates. (Rootjunky's tool)
Current situation - I am rooted and on 5.1.2. I want to get to Cm 12.1, but I can't get into recovery at all. It is stuck on the "Amazon" logo when I try to get to recovery. It is not the blue logo - I have never seen it, but my logo's not blue. I'm able to boot normally and use the tablet without any issues.
Question - The thread I came across earlier said that a fastboot cable is the only way out. But this person seemed to be at the "blue amazon" logo. Help? Thoughts?
Click to expand...
Click to collapse
bootloader was always locked, but 5.0.X allows booting a custom Recovery
if it will not boot to recovery nor rom/system, nothing can be done
fastboot cable doesn't work with 5th gen fires
Sent from my DROID Turbo using XDA Labs
Thanks... When you say "if it will not boot to recovery nor rom/system, nothing can be done", I see a glimmer of hope. The only thing I'm unable to do is boot to recovery. I am still rooted and able to use the tablet fully. There are no issues with that.
Does that help?
smvsmv said:
Thanks... When you say "if it will not boot to recovery nor rom/system, nothing can be done", I see a glimmer of hope. The only thing I'm unable to do is boot to recovery. I am still rooted and able to use the tablet fully. There are no issues with that.
Does that help?
Click to expand...
Click to collapse
Thoughts:
- you can still flash a custom ROM but if something goes wrong during the upgrade you're screwed without a recovery environment.
- recent versions of FlashFire have the ability to preserve and rewrite the recovery environment; not certain if the process works on this device and potential side effects (if any).
- several months ago another contributor claimed to have resurrected the stock recovery environment via adb which created quite a stir at the time. Have not seen much since so I suspect the solution was not generically applicable.
- I'm of the belief that most recovery access issues are actually a booting problem vs a damaged recovery partition. Your situation may be a little different as you attempted to rewrite the recovery partition by flashing TWRP.
oh well.. I'll just wait for you brainy guys to figure a way out. Not messing with the device anymore for now. Thank you!
(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!