So i'm very new to root and i'm kicking myself for doing what I did and i'm really hoping someone can help me out. So long story short in titanium backup I turned all my launchers even the default one into user applications, and now its stuck in an endless boot. And please be noob friendly as possible I almost know nothing about android and barley successfully rooted in the first place. Thanks
(Kindle Fire HD 2012 Model)
Did you install twrp or cwm yet? (Recovery) if not you will probably need a fast boot cable and then reinstall the ROM. Very different routes.
Sent from my XT907 using XDA Free mobile app
Boot Loop
Hello...Just rooted my KF HD and am now stuck in a boot loop. I was able to obtain root and boot into recovery. I was taking a back up before installing a Jelly Bean ROM. When I tried to take the back up, said there was not enough memory, so I did a backup without data. I did a full wipe, cache and davlik cache and when I tried to install the ROM zip file, got a message it could not open the zip. So, I restored from my back up and now all I get is the regular Kindle FIre logo over and over. I tried to connect via adb, but it does not stay on long enough for me to send any commands, my PC does not recognize it. Any help or suggestions? Just wanted to put a good stable ROM on it so the kids can have sometime more reliable than what Amazon provided. Any help is appreciated.
BTW...if I remember correctly, my serial number started with D025. Thanks.
Related
Hi guys, I have bricked my nook hd+ and I hope to get some advice, thank you.
I had the problem where i was only able to boot to cwm recovery, I managed to solve it by using a stock backup, combined with flashing a 2.1 stock rooted rom as i had problems recovering the data partition.
After I did all that(I should have really stopped when I got it working) I tried to install cwm recovery by using the bootable sd card as i lost my custom recovery for some reason. However, I was not able to after rebooting 20+ times. I previously bought two nooks, my other nook had no problems but this particular device had to be rebooted 20-30 times before it worked the other time. Being the genius I am, I then tried to flash recovery using various apps since I still had root..one of the programs flashed and restarted my nook hd+ and I can only boot to the "nook" screen now. Holding power and the n button only restarts the tablet.
I guess my only way out is if i could somehow get adb to work? I know its a long shot but I have been trying for the past 1 hour and have not been able to do anything. My computer manages to recognize the tablet as "Blaze_Tablet" and i am unable to change the drivers. Anyway i was hoping if someone could give me an idea of what i could do or if i should give up on the device as it is unrecoverable. I would appreciate any response at all, thank you good people of xda!
I somehow managed to get fastboot working and flashed custom recovery and managed to restore from backup of stock :victory:
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 guys. I appreciate in advance any help you can bring to this thread.
Please be aware (for my amount of messages) that i'm still a newbie. So, please don't brag or dismiss any opinions or suggestions just because... Instead, try to share your magnificent knowledge and solutions to the following problem:
I have a rooted Kindle Fire HD 7", with second bootloader and TWRP recovery. I was running a 4.2.2 version of Paranoid Android without any problem. I often update ROM's and twerks for the tablet and my SGS3, so i'm pretty much capable of solving many of problems i've faced before, but right now i'm stucked in a bootloop without knowing what to do.
I tried to update my recovery TRWP from 2.4.x version to a 2.6.x version of it (to be able to flash KK 4.4 on KFHD), i've downloaded .img from TWRP web page and flashed via "Flashify" (which i read is the 2nd easiest way to do it), but when i rebooted the device, it got into a bootloop (?). It shows Kindle Fire, first in normal letters color set white-orange, then second color set white-blue, and after it is shown a new icon that says "FASTBOOT kindle fire" in orange... And that's pretty much it. It doesn't moves forward and i can't access recovery mode by pressing power button as usual.
Do you have any ideas of what to do in this scenario? If yes, please share. If don't, thank you anyway for reading the thread.
guillemedina11 said:
Hello guys. I appreciate in advance any help you can bring to this thread.
Please be aware (for my amount of messages) that i'm still a newbie. So, please don't brag or dismiss any opinions or suggestions just because... Instead, try to share your magnificent knowledge and solutions to the following problem:
I have a rooted Kindle Fire HD 7", with second bootloader and TWRP recovery. I was running a 4.2.2 version of Paranoid Android without any problem. I often update ROM's and twerks for the tablet and my SGS3, so i'm pretty much capable of solving many of problems i've faced before, but right now i'm stucked in a bootloop without knowing what to do.
I tried to update my recovery TRWP from 2.4.x version to a 2.6.x version of it (to be able to flash KK 4.4 on KFHD), i've downloaded .img from TWRP web page and flashed via "Flashify" (which i read is the 2nd easiest way to do it), but when i rebooted the device, it got into a bootloop (?). It shows Kindle Fire, first in normal letters color set white-orange, then second color set white-blue, and after it is shown a new icon that says "FASTBOOT kindle fire" in orange... And that's pretty much it. It doesn't moves forward and i can't access recovery mode by pressing power button as usual.
Do you have any ideas of what to do in this scenario? If yes, please share. If don't, thank you anyway for reading the thread.
Click to expand...
Click to collapse
You can't just use anything when modding. TWRP has to come from Hashcode's thread because he modifies them for the Kindles`s. The other thing is the KFHD7 uses FireFlash. You can try flashing a Nandroid backup in TWRP or you will need a fastest cord and factory reset.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
guillemedina11 said:
Hello guys. I appreciate in advance any help you can bring to this thread.
Please be aware (for my amount of messages) that i'm still a newbie. So, please don't brag or dismiss any opinions or suggestions just because... Instead, try to share your magnificent knowledge and solutions to the following problem:
I have a rooted Kindle Fire HD 7", with second bootloader and TWRP recovery. I was running a 4.2.2 version of Paranoid Android without any problem. I often update ROM's and twerks for the tablet and my SGS3, so i'm pretty much capable of solving many of problems i've faced before, but right now i'm stucked in a bootloop without knowing what to do.
I tried to update my recovery TRWP from 2.4.x version to a 2.6.x version of it (to be able to flash KK 4.4 on KFHD), i've downloaded .img from TWRP web page and flashed via "Flashify" (which i read is the 2nd easiest way to do it), but when i rebooted the device, it got into a bootloop (?). It shows Kindle Fire, first in normal letters color set white-orange, then second color set white-blue, and after it is shown a new icon that says "FASTBOOT kindle fire" in orange... And that's pretty much it. It doesn't moves forward and i can't access recovery mode by pressing power button as usual.
Do you have any ideas of what to do in this scenario? If yes, please share. If don't, thank you anyway for reading the thread.
Click to expand...
Click to collapse
You should have used FireFlash or direct ADB. For now,you can try to restore a Nandroid backup and get the TWRP 2.6.3.1 image from Hashcode's thread. And use FireFlash this time!!
I can't help but notice that he said "twerks" in his original post :silly:
Sent from my 2013 Kindle Fire HD with Tapatalk
LinearEquation said:
You can't just use anything when modding. TWRP has to come from Hashcode's thread because he modifies them for the Kindles`s. The other thing is the KFHD7 uses FireFlash. You can try flashing a Nandroid backup in TWRP or you will need a fastest cord and factory reset.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you so very much for your helpful comment.
As i said in the first post, for any reason a can't access twrp recovery by pressing power button right after booting the device. I think a might need the fastboot cable.
Question: Original factory cable doesn't work in this case? y've noticed that i was triying to plug it to the pc with my samsung cable. does it make any real difference (Just comparing factory kindle cable and samsung cable)?.
guillemedina11 said:
Thank you so very much for your helpful comment.
As i said in the first post, for any reason a can't access twrp recovery by pressing power button right after booting the device. I think a might need the fastboot cable.
Question: Original factory cable doesn't work in this case? y've noticed that i was triying to plug it to the pc with my samsung cable. does it make any real difference (Just comparing factory kindle cable and samsung cable)?.
Click to expand...
Click to collapse
yes there's a different in KFHD factory cable and samsung cable cause factory cable are made specially for KFHD and its support good speed then samsung cable/
qoute: lol i am a newbie
A factory cable (also known as a fast boot cable) is not the cable that came with your kindle it is a cable you have to make or order.
On the micro USB side it shorts pin one and pin four.
When this cable is plugged in your kindle will boot to a screen that says fast boot and stay there. In this special mode we can use commands from a PC to change the kindles settings.
Sent from my XT907 using xda app-developers app
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
So i wanted to install CyanogenMod on my kindle fire 2, because the os amazon provides is horrible. Before i could install any roms, i had to root and install a custom recovery. I found a one-click way to do it here, and it must have failed, but the device was still on, so i manually restarted it. When it booted up, it briefly showed the kindle bootlogo, then switched to a solid red/orange full screen. I would really like help fixing this. Please help. (BTW, i do have root access.)
copycat114 said:
So i wanted to install CyanogenMod on my kindle fire 2, because the os amazon provides is horrible. Before i could install any roms, i had to root and install a custom recovery. I found a one-click way to do it here, and it must have failed, but the device was still on, so i manually restarted it. When it booted up, it briefly showed the kindle bootlogo, then switched to a solid red/orange full screen. I would really like help fixing this. Please help. (BTW, i do have root access.)
Click to expand...
Click to collapse
the TweezerMod forum says that it's only useful for the older bootloader. Go ahead and download and flash the bootloader file from Hash's thread here as directed. You really should get a factory cable if you don't already have one, as you'll need one to get into fastboot to flash the bootloader. After this, reboot and try to get into TWRP. If it works, TweezerMod mostly worked. If not, you'll need to do the entire flashing process manually.
Sent from my Amazon Jem using XDA Labs