Develop Bugs

kindle fire in boot loop. Howto for restoring with fastboot?

I wanted to get 4.2.2 on my fire2, so I went throught the tutorials to root and install twrp recovery which worked great. I downloaded the CM10.1 sgt7 and gapps for the fire 2 in the dev section and proceeded to reboot into recovery. I wiped the system and flashed the rom and gaps, wiped cache/dalvik and hit reboot.
dreaded kindle fire boot loop. The only thing I can think is that the rom DL was corrupted. It really didn't take long to complete the flash in twrp, probably less than 10 seconds. I really should have checked the md5.
OK, so I get a fastboot cable online and it shows up today. I can't seem to locate a tutorial of how to restore with fastboot though... can someone point me to a link?
Thanks,
-J

miatawnt2b said:
I wanted to get 4.2.2 on my fire2, so I went throught the tutorials to root and install twrp recovery which worked great. I downloaded the CM10.1 sgt7 and gapps for the fire 2 in the dev section and proceeded to reboot into recovery. I wiped the system and flashed the rom and gaps, wiped cache/dalvik and hit reboot.
dreaded kindle fire boot loop. The only thing I can think is that the rom DL was corrupted. It really didn't take long to complete the flash in twrp, probably less than 10 seconds. I really should have checked the md5.
OK, so I get a fastboot cable online and it shows up today. I can't seem to locate a tutorial of how to restore with fastboot though... can someone point me to a link?
Thanks,
-J
Click to expand...
Click to collapse
Can you get into recovery?

Always factory reset when flashing a ROM that is completely different from the one already installed, or you will run into a bootloop.

I was able to get it back. Been running 422 for a few months. I had a bad Roman do from what I can tell. I was not able to get to recovery without restoring with a fastboot cable.

twrp wont boot

ok i have a 2nd gen kindle and managed to root and install bootloader but when i select recovery it just hangs on booting? i reflashed an older version of twrp still same thing? (solved)

Wait how did you fix it? I'm having the same problem!
I rooted it using this guide, http://forum.xda-developers.com/show....php?t=2075959, and then I used this guide, http://forum.xda-developers.com/show...light=recovery, to add twrp so I can flash CM. Everything seemed to go well except that I am unable to enter recovery mode. When booting normally it works fine and loads into the kindle OS but obviously, I want to replace that. I have tried searching the forums and trying a few different things but so far nothing has worked.

[Q] Xposed, TWRP, Bootloop, Help!?!?!?!

Hello, this will be my first post here at XDA, and i will be asking for your help guys...
I am experiencing bootloop on my phone.
The thing is I tried to install Xposed Installer using the Automatic method that flashes to the recovery.
It reboots them...
It passed the Galaxy Note II N7100 black screen...
It shows the TWRP logo (The blue one)
AND THEN IT JUST REPEAT AND REPEAT the TWRP logo.
I can boot to Download Mode.
Tried removing the battery and tried to enter recovery again using hardware keys, same thing happens.
What can I do now? Please Help.
Thank You!
P.S. I am running DN3 4.3 Stable using it's stock kernel.

sgtfrnz said:
Hello, this will be my first post here at XDA, and i will be asking for your help guys...
I am experiencing bootloop on my phone.
The thing is I tried to install Xposed Installer using the Automatic method that flashes to the recovery.
It reboots them...
It passed the Galaxy Note II N7100 black screen...
It shows the TWRP logo (The blue one)
AND THEN IT JUST REPEAT AND REPEAT the TWRP logo.
I can boot to Download Mode.
Tried removing the battery and tried to enter recovery again using hardware keys, same thing happens.
What can I do now? Please Help.
Thank You!
P.S. I am running DN3 4.3 Stable using it's stock kernel.
Click to expand...
Click to collapse
Well something was messed up when you flashed xposed installer( i don't know what you mean by automatic method) but do a clean install,since you can get into download mode,grab the twrp img.tar and flash it using pc odin ,then you can access recovery, do all the wipes again by going under "advanced" and reflash your rom.Now to install xposed go to xda thread for it and grab the apk from there (i think it's available on play store as well).You should have no more issues
Twrp

Like the previous post said I'm not sure what you've done. When xposed framework is installed there is usually an unistall zip created on the internal so card. If you can get recovery find it and flash it
Sent from my GT-N7105 using Tapatalk

The device is now fixed.
So okay, I followed the above instruction to flash a fresh TWRP. It does not work that way, it still has bootloop on the blue teamwin screen, what i've done is flash a .tar Philz specified for my device and then try to boot it. It boot and then it then flashes the pending Xposed script/flashable that I think TWRP can't execute that's why it bootloop. When it CWM successfully flashed it, I boot and wen't to homescreen. Then I now flashed TWRP via odin.
Thanks everyone, my Note 2 has come back to life.

sgtfrnz said:
So okay, I followed the above instruction to flash a fresh TWRP. It does not work that way, it still has bootloop on the blue teamwin screen, what i've done is flash a .tar Philz specified for my device and then try to boot it. It boot and then it then flashes the pending Xposed script/flashable that I think TWRP can't execute that's why it bootloop. When it CWM successfully flashed it, I boot and wen't to homescreen. Then I now flashed TWRP via odin.
Thanks everyone, my Note 2 has come back to life.
Click to expand...
Click to collapse
Boot into Download mode and flash philsz touch recovery 6 and reboot device .. Everything will be ok>

Old thread may be old, but it's still relevant.
I just tried to install XPosed as well on my Note II and it did the same thing (mine's AT&T)
Info
Device: Note II
XPosed Version: 2.6.1
Install Method: "Recovery (flash zip automatically)"
Recovery Image: TWRP
Mine exhibited the same behavior as OP's, however after leaving it alone for a while to bootloop recovery as much as it wanted to, I came to my laptop, found this post, grabbed as USB cable, and I was just about to start the process of reflashing recovery when all of a sudden I saw my lock screen.
It took roughly five minutes of bootloop to get it there, but it successfully installed XPosed and my device is running fine.
So, for all the other Googler's out there that landed on this post, leave it alone for a while! See what happens. If it's still bootlooping, like, 30 minutes later, then try reflashing TWRP using ODIN. If that still doesn't work, reflash a new ROM using TWRP.

Stuck at boot loop. White Amazon Logo

Hi guys,
I was in the final step (7) of this gude: http://www.aftvnews.com/start/
Which is installing the latest pre-rooted stock software, (version 51.1.4.1_514013920) After pushing the rom to /sdcard, I rebooted the device so that I could flash it via clockworkmod recovery, but I was not able to select the recovery option with my keyboard. So I decided to re-do the installation of Rbox's kernel boot menu. Now, I'm stuck at a boot loop with just the white Amazon logo showing up. Is my device bricked and is there a way to fix it?

FYI I cannot access clockworkmod recovery. I wish I could, as I would then be able to flash the latest pre-rooted ROM that's in /sdcard
Does anyone know how I can access recovery?

Newbie_from_NJ said:
FYI I cannot access clockworkmod recovery. I wish I could, as I would then be able to flash the latest pre-rooted ROM that's in /sdcard
Does anyone know how I can access recovery?
Click to expand...
Click to collapse
You need cwm 6.0.5.1.4 or higher AND unlocked boot loader or you will brick it. If this is your situation believe me I hope I'm not the bearer of bad news. Hopefully you'll be ok. Good luck!

KLit75 said:
You need cwm 6.0.5.1.4 or higher AND unlocked boot loader or you will brick it. If this is your situation believe me I hope I'm not the bearer of bad news. Hopefully you'll be ok. Good luck!
Click to expand...
Click to collapse
I have all that. Box came with 51.1.1.0_user_511070220. Here are the steps I did:
1. Rooted & install busybox and blocked updates
2. Downgraded to version 51.1.0.2_user_510058520
3. Rooted again
4. Unlocked Bootloader
5. Installed Clockworkmod recovery 6.0.5.1.4a
6. install Pre-Rooted Stock ROM version 51.1.4.0_514006420 updated via Clockworkmod recovery
7. Installed Busybox
8. Installed Kernel Boot menu
9. pushed to sdcard the latest pre-rooted stock software, version 51.1.4.1_514013920
10. Rebooted box, but here is when I realized I could not select recovery option from boot menu using my keyboard.
11. I decided to try and reinstall the boot menu. I followed the same steps I did in #8.
12. Stuck at boot loop with white Amazon Logo.

In hindsight, now that I've reviewed each step, what I should have done was flashed Pre-Rooted Stock ROM version 51.1.4.0_514006420 AGAIN via Clockworkmod recovery in order to properly uninstall the kernel boot menu. Then I should have tried re-installing the kernel boot loader again. Lesson learned.

Newbie_from_NJ said:
I have all that. Box came with 51.1.1.0_user_511070220. Here are the steps I did:
1. Rooted & install busybox and blocked updates
2. Downgraded to version 51.1.0.2_user_510058520
3. Rooted again
4. Unlocked Bootloader
5. Installed Clockworkmod recovery 6.0.5.1.4a
6. install Pre-Rooted Stock ROM version 51.1.4.0_514006420 updated via Clockworkmod recovery
7. Installed Busybox
8. Installed Kernel Boot menu
9. pushed to sdcard the latest pre-rooted stock software, version 51.1.4.1_514013920
10. Rebooted box, but here is when I realized I could not select recovery option from boot menu using my keyboard.
11. I decided to try and reinstall the boot menu. I followed the same steps I did in #8.
12. Stuck at boot loop with white Amazon Logo.
Click to expand...
Click to collapse
Then I don't know...I always double or triple check to make sure but your steps seem correct. Was this a new box? I only say that because I remember that super tedious process and at one point I think I needed to root again. At that point it maybe possible an update could sneak through but that would probably result in losing root--worst case. Not a brick.
It's concerning because you seem to know what you're doing and were cautious during the process.
Hopefully someone else can confirm where you went wrong. If you didn't go wrong then that might be a bigger problem. Everything went smoothly up until it hung at boot?

As they always say, if your in a jam and get "failed" messages when writing to boot or recovery or flashing, do not reboot. keep trying till you get no errors. that said, I thought I was stuck in a boot loop cause I insalled the llama and xbmc launcher and removed the launcher app. I was still able to get through adb but it took like 5 or 6 reboot tries. good luck.

Unable to load temp CWM on Z00AD

I have a Z00AD that has never been rooted and recently I was trying to update the stock via OTA and it got stuck on the logo loading screen.
I then used the guide here (https://www.theandroidsoul.com/how-to-root-asus-zenfone-2-with-cwm-recovery-and-supersu/) to get into temp CWM, which I then used to flash a new stock rom (UL-Z00A-WW-4.21.40.223-user.zip) via extsd .
It flashed successfully (loaded to the launcher) and when I try to get temp CWM again to flash supersu and root the phone, it wont work. After the T4 process is done and it just says completed, press any key to continue, but the phone just stays in fastboot mode forever. I had to turn it off as it got pretty hot.
Help?

Is anybody out there?

Welp, guess not.

3XTR3M1ST said:
I have a Z00AD that has never been rooted and recently I was trying to update the stock via OTA and it got stuck on the logo loading screen.
I then used the guide here (https://www.theandroidsoul.com/how-to-root-asus-zenfone-2-with-cwm-recovery-and-supersu/) to get into temp CWM, which I then used to flash a new stock rom (UL-Z00A-WW-4.21.40.223-user.zip) via extsd .
It flashed successfully (loaded to the launcher) and when I try to get temp CWM again to flash supersu and root the phone, it wont work. After the T4 process is done and it just says completed, press any key to continue, but the phone just stays in fastboot mode forever. I had to turn it off as it got pretty hot.
Help?
Click to expand...
Click to collapse
unlock bootloader first. then download twrp and flash it or boot it