Develop Bugs

Stuck on Bootanimation

Installed gederom, kept wiping, caches, dalviks, flash, reboot, always go past TWRP and into that boot animation - robot with CM9 near it.
Never goes past this point.
What am I to do?

Factory Reset flash the ROM again followed by gapps. should be fine then

yeah wipe all just dont wipe your sd card flash rom flash gaps if needed and go to mount and make sure there are no checks in the boxes of system and data if so uncheck them then reboot

acmys said:
Installed gederom, kept wiping, caches, dalviks, flash, reboot, always go past TWRP and into that boot animation - robot with CM9 near it.
Never goes past this point.
What am I to do?
Click to expand...
Click to collapse
Did you charge full your KF battery?

[Q] roms do not make it past cyanogen mod screen

Kindle first generation:
- rooted and has twrp v2.3.1.1 working (seemingly) fine.
- copied and verified md5 checksum for all roms
- wiped system clearing previous rom
- performed factory reset creating new partitions
- cleared cache and dalvik
- flashed FIREFIREFIRE bootloader v1.4a(current)
- flashed gedeROM which uses cyanogenmod 9 (26-6-2012 recentish...)
- system reboot
- does not leave the cyanogenmod 9 load screen.... (-_-) [waited 30 minutes each time]
THE PROBLEM
- No matter which rom I verify or flash they all hang at the rom loading screen.
- have tried this same process with several diffrent roms including
-AlienDroidV7.0.zip
-gedeROM-KFire-CM9-26-6-2012.zip
-cm-9-20120711 (snapshot)
-jb-kfire-hashcode-10-10.zip
I have used the same procedure for all roms to no avail. Could there be something wrong with TWRP and that it isnt flashing the roms correctly?
(It returns saying that they were all sucessful)
Any help would be epic

Flash this zip in recovery to revert to the older twrp that one your using is broken http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 do a full wipe including the system minus the external storage/sdcard reflash your rom and gapps you should be fine.

Thepooch said:
Flash this zip in recovery to revert to the older twrp that one your using is broken http://forum.xda-developers.com/showpost.php?p=30780737&postcount=180 do a full wipe including the system minus the external storage/sdcard reflash your rom and gapps you should be fine.
Click to expand...
Click to collapse
Thanks!!!
I was having the *exact* same problem as the OP and reflashing the old recovery fixed it. Can't believe the current version is broken like this.
Further searching suggests that also checking "use rm -rf" for the formatting method under settings will solve the problem.

That's why I use the oldest. It has less bugs.

THANKS!
Any idea why the current release of TWRP has so many issues?

I am having the same problem as the OP. I rooted my Fire last summer and updated with various builds of the CM10/SGT7 for the Kindle Fire [Linaro] since then without any problems. I've been using the 1127 build and updated to the 1211 version. Now it just hangs at the CyanogenMod animation screen.
I've tried restoring with a backup that was made following the update to 1127, without success. Same with trying to reflash 1127 and even the 1105 builds, which worked well previously.
When I launch KFU on my Windows 7 machine, it sees my Fire intermittently. Mostly, KFU reports the Fire to be offline and unknown boot status.
TWRP is 2.2.2.1 and all the rest is from KFU 0.96
Any suggestions?

Did you wipe system and factory reset before installing?
"That's a special kind of stupid. The kind that makes me laugh."

I have the same problem as TrojanDAd. I was on stock 6.3.1 and rooted using KFU 0.9.6. It installed FFF 1.4a and TWRP 2.2.2.1. I have tried to install different roms from TWRP including Jandycane, Hashcode's latest AOSP JB rom, Hashcode's Unofficial CM10.1 rom, and two roms from twa_priv. Each time I flash a rom I do factory reset, wipe data, flash rom, flash GApps, wipe cache + Dalvik. When I reboot, it hangs at boot logo. I could post logcat if it would help but the errors are different for each rom and there are alot of errors.

soupmagnet said:
Did you wipe system and factory reset before installing?
"That's a special kind of stupid. The kind that makes me laugh."
Click to expand...
Click to collapse
No, I just did a dirty flash. I wiped the cache and Dalvik during the flash, but that was it.

Well crap... in that case, I'll make my own thread.

selyb said:
Well crap... in that case, I'll make my own thread.
Click to expand...
Click to collapse
It turns out that the "Mount Data" and "Mount System" boxes were checked. I unchecked them, wiped everything and then it finally booted to the lock screen.
Thanks to all on the selyb thread!

[Resolved!] Update to 4.3+ ROM freezes on boot

I am on Liquid Smooth 2.9 (4.2.2) and using TWRP 2.6.3.0 phone is an i747m 32GB model. I tried upgrading to LS2.10 which is 4.3. Installed ROM OK but after first reboot phone froze on the Samsung logo. It wouldn't even get the the boot animation. I tried several methods of flashing as requested but to no avail. Today I tried the latest nightly of Carbon ROM which is 4.3.1 and encountered the same issue. I tried rebooting after flashing GAPPS and it just froze at the Samsung logo without going to boot animation. I did flash the latest bootloader in between while trying to diagnose as well.
Does anyone have any suggestions or similar situations? I would really like to upgrade to a 4.3 ROM but seem to have hit a hurdle...
Thanks in advance.

So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.

Galloway said:
So I've had a little time to try some other things. I've verified the MD5sum of all files trying to flash. All are good. I've tried installing the latest nightly of Carbon ROM after doing a full wipe of all internal. I haven't formatted my external yet. Flashed ROM and phone boots fine. I've tried flashing GAPPS both during initial flash, after initial flash and not at all. In every case the phone boots fine after the initial flash and functions perfectly. It will not boot a second time at all. In all cases so far on reboot it just stays on the Samsung logo screen and I've left it for about a half hour just to make sure it isn't that I'm not waiting long enough. I hold the power button for 8 seconds and then boot into recovery. I've tried doing a factory reset and rebooting. No go. I've tried refreshing the ROM and it still won't boot after. I haven't taken a logcat yet as I just haven't had time but I'm really confused why multiple ROM's. I've currently restored back to 4.2.2 liquidsmooth 2.9.
I'm really hoping someone has a suggestion or that they've come across this before.
Click to expand...
Click to collapse
When you flash the ROM, are you wiping dalvik cache as well as wiping all data/ factory reset and cache?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?

gluk1470 said:
I have the same, CM10.2, Quantum. First boot is ok. but after reboot phone freeze on samsung logo and recovery TWRP 2.6.3.0 needs password. I cant make any wipes, cant restore backup - needs password. Update last bootloader, before flashing made wipe /system /data /cache /dalvik, after - wipe /cache /dalvik /data againe - nothing, second boot only logo,
Could some one tell me, what I do wrong?
Click to expand...
Click to collapse
At least it's not just me....unfortunately I don't have much time lately so I haven't been able to try experimenting. I noticed you are using TWRP as well....I may try flashing CWM if I get a sec and see if the results are the same. Also if the same happens and I have enough time I'll try and grab a logcat. If I don't have time it's called wipe and restore from a backup.
And yes Dalvik + cache are always wiped anytime I flash anything as a minimum. With this issue I have been doing an entire internal format. I have tried just wiping cache and Dalvik when it occurs as well as fixing permissions but still doesn't boot. Wish I had more time latrely to narrow it down.

Yes, its work. I flashed stock ROM 4.1.2, then root device, flash CWM 6.0.2.3 (no touch) and flash Quantum 2.20. But I think, problem not in recovery or device. Problem in Titanium Backup, I used it to restore some system apps and accounts, now I restored only call log and SMS.

I have now tried flashing with TWRP and pulling SD card before initial boot to eliminate an SD card issue. I've set to not install backups from Google as precaution. Still the same result of frozen at Samsung logo.
I've then flashed the newest CWM non-touch and wiped all with flash. The result was even worse. This time it wouldn't even boot the first time for initial setup it just hangs at the Samsung logo.
This is starting to get frustrating just due to the fact of me not having a huge amount of time to dedicate to isolating the issue. I need to get a logcat but I am not usually near a computer to ADB to it when it is not booting. If I have time this weekend I'll try and get a logcat to post up.

CWM broke it real good! LOL! Anyways I couldn't even get my backups to restore. I tried taking a logcat while it was frozen but was not able to get an ADB connection in order to even get a logcat. I managed to push a fresh copy of Liquidsmooth 2.9 to the SD card and install it. Then flashed TWRP back. Then restored my back up. What a tedious task to still be scratching my head as to why multiple 4.3 ROM's won't boot on the second boot after flashing...

It's been resolved! As per an awesome person on Carbon's G+ thread don't flash the ROM from external SD .Only flash it from internal storage!

Stuck in boot loop after flashing CM7

Hi all, hoping this is a stupidly simple fix. I wanted to update to latest stable CM7 and so downloaded and flashed it from CWRecovery,
I also ran the factory reset, and cleared the cache.
When I boot, it shows the blue loading screen, then comes to the "Welcome to ADR6300" and reverts to the CyanogenMod7 loading screen..
Then, it keeps bouncing back and forth between these two screens until I pull the battery...

You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.

[Solved]
PonsAsinorem said:
You didn't mention the order of what you did. Assuming you have no valuable data, I would just start over.
Reboot into recovery
Wipe system
Factory reset
Flash ROM
Flash GAPPs (if desired)
Reboot into ROM
Also, ensure you're on the latest CWM, first.
Click to expand...
Click to collapse
Worked perfectly! Thank you!!
Apparently the problem was having the wrong version of GAPPs. I was reinstalling but Wiping system was the step I had skipped!

Flashing any rom results in infinite boot

I have tried the roms below:
Pac-rom
LiquidSmooth
CyanogenMod 12.1
CyanogenMod 11
And the result is it always gets stuck at boot where the boot animation continues infinitely. I have gave it about 30 minutes to boot.
With LiquidSmooth I was able to run logcat, but CM12.1 I am not able to.
I have tried resetting system, data, caches in twrp and using the reset for new rom in philz.
I have tried flashing with both TWRP and Philz.
I am using the latest Philz and TWRP.
The only thing that has worked for me is samsung stock ROM, but I do not like the stock ROM.
Are there SPH-L900 phones you have to do something different?
Is there a way to get boot logs from CM12?
Am I doing something wrong?
See attachment from LiquidSmooth.

After flashing http://forum.xda-developers.com/showthread.php?t=2086769 everything worked.

GRMrGecko said:
After flashing http://forum.xda-developers.com/showthread.php?t=2086769 everything worked.
Click to expand...
Click to collapse
Hi,
I see that you got it working by using that thread, but what exactly did you flash from it? I had it working with CM12.1 but decided to flash the recovery from CM for my phone and it ruined the installation. Tried re-flashing with the latest nightly to get stuck in the CM infinite boot, returned to stock (that worked fine) flashed TWRP and CWM 6.0.4.3 Touch, re-did everything again with both, but cant go past the infinite boot. This happened the last time too, but it started working out of nowhere so I continued patching until I flashed "cm-12.1-20150828-NIGHTLY-l900-recovery.img". Now it doesn't boot again and redoing what I did the last time is not working (Wiping Cache, Dalvik...)
Thanks

Raziel10000 said:
Hi,
I see that you got it working by using that thread, but what exactly did you flash from it? I had it working with CM12.1 but decided to flash the recovery from CM for my phone and it ruined the installation. Tried re-flashing with the latest nightly to get stuck in the CM infinite boot, returned to stock (that worked fine) flashed TWRP and CWM 6.0.4.3 Touch, re-did everything again with both, but cant go past the infinite boot. This happened the last time too, but it started working out of nowhere so I continued patching until I flashed "cm-12.1-20150828-NIGHTLY-l900-recovery.img". Now it doesn't boot again and redoing what I did the last time is not working (Wiping Cache, Dalvik...)
Thanks
Click to expand...
Click to collapse
Followed this guide from some post I found after reading for 8 hours, LOL. Don't remember who it is from... It's for the Cyanide ROM but worked perfect for CM12.1 latest nightly with the latest GAPPs
1.) revert everything to stock
Using Odin3 v3.09 I first flashed this: L900VPUCNE2_L900SPTCNE2_SPR.zip
2.) Reboot and verify it's not bricked, then use ODIN to flash Philz philz_touch_6.15.4-l900.tar.md5
3.) Reboot into Philz recovery and follow these steps exactly
1. Mounts and Storage
Format / system
Format / cache
Format / data
Format / data and /data /media (/sdcard)
(note this isn't the EXTERNAL sdcard, on to which I had loaded the ROM, Shift and gapps)
2. Power Options > reboot recovery
3. Wipe cache partition
4. Advanced > Wipe dalvik cache
5. Wipe data / factory reset > Wipe data / factory reset
6. Wipe data / factory reset > clean and install new ROM
At one point Philz asked me if I wanted to root and I said yes.
3.) Flash (from the external sdcard) the ROM (Tablet style ROM found in OP "5.0.2-RC-7.1-tablet"), Then flash Shift (Shift-LP-4.3 other versions DID NOT WORK), then flash gapps (GApps-5.0.2-20150315-signed NO OTHER VERSION WOULD FLASH, got Error 20 every time) Here's the
After everything was flashed I rebooted and got stuck at boot animation AGAIN, so I rebooted into recovery and wiped cache. Just cache, not dalvik or user data, rebooted, and it worked.
Installed Netflix from appstore, when I logged in to netflix it asked me to update google play services (I've seen it do this on other devices as well). Updated google play services and went back to Netflix, chose a random show and tapped on it, stuck at "loading" screen. Rebooted phone, tried netflix again and it works.
This was a tough one! But it's working now and I've saved all these files in one place incase it bricks again. Now to install the Note 3/4 style faux-stitched-leather back cover I got off Amazon.
Thanks all!