Develop Bugs

[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!

[Q] Stuck in recovery mode bootloop!

Hello everyone,
This is what is happening to me. I was trying to flash Miroslav's Cyanogenmod 11 RC2 with Philz Touch 6.07.9, but none of the recomended methods worked for me, I just got stuck on lg logo bootloop - I really want this rom but it is hard as f**k to flash -. So I tried to go back to CM 10.2.1 and got the "Status 7" error. Very frustrated, I finally used my stock recovery image and it worked fine.
From this point, i was recovering my apps and data using titanium back up and when it finished, a notification asked if I wanted the official system update. I refused it and proceded to reboot. Now the phone boots instantly to recovery mode and show the purple screen of Philz touch. First I wiped cache and dalvik and got the same bootloop. Then I wiped cache, dalvik and factory reset and got the same bootloop. Finally, I formated system, factory reset, wiped cache, wiped dalvik and flashed again my recovery image, and got again the recovery mode bootloop.
Any Ideas? Thank you for your help.
Best regards.
EDIT: I must clarify that when I flash my recovery image, it ALWAYS get suck on a part that says something like "installing android security". I have to press power button 10 seconds to restart but it boots normaly in the stock rom.

chortiman said:
Hello everyone,
This is what is happening to me. I was trying to flash Miroslav's Cyanogenmod 11 RC2 with Philz Touch 6.07.9, but none of the recomended methods worked for me, I just got stuck on lg logo bootloop - I really want this rom but it is hard as f**k to flash -. So I tried to go back to CM 10.2.1 and got the "Status 7" error. Very frustrated, I finally used my stock recovery image and it worked fine.
From this point, i was recovering my apps and data using titanium back up and when it finished, a notification asked if I wanted the official system update. I refused it and proceded to reboot. Now the phone boots instantly to recovery mode and show the purple screen of Philz touch. First I wiped cache and dalvik and got the same bootloop. Then I wiped cache, dalvik and factory reset and got the same bootloop. Finally, I formated system, factory reset, wiped cache, wiped dalvik and flashed again my recovery image, and got again the recovery mode bootloop.
Any Ideas? Thank you for your help.
Best regards.
EDIT: I must clarify that when I flash my recovery image, it ALWAYS get suck on a part that says something like "installing android security". I have to press power button 10 seconds to restart but it boots normaly in the stock rom.
Click to expand...
Click to collapse
When in vain , unbrick your phone again using unbricking guide and use CWM , not all guide is working for the same type of phone . No need to wipe system clean cache watevr **** you were told unless recommended by developer and just factory reset then flash the rom

Mr.201 said:
When in vain , unbrick your phone again using unbricking guide and use CWM , not all guide is working for the same type of phone . No need to wipe system clean cache watevr **** you were told unless recommended by developer and just factory reset then flash the rom
Click to expand...
Click to collapse
Thanks for the answer and the advice about factory reset. Yes, I had to unbrick my phone and by the way, still could not install miroslav's cm11 RC3 using Philz touch 6.19.3.
But I have another issue: I successfully got back to CM 10.2.1 but after I restored my apps using Titanium Backup, I rebooted the phone and got stuck on CM logo for half hour. I wiped dalvik and got the same result. Then wiped cache and dalvik and still stuck. What should I do? Flash again the rom? The restored data is from CM 10.2.1 so I don't see any problem....

chortiman said:
Thanks for the answer and the advice about factory reset. Yes, I had to unbrick my phone and by the way, still could not install miroslav's cm11 RC3 using Philz touch 6.19.3.
But I have another issue: I successfully got back to CM 10.2.1 but after I restored my apps using Titanium Backup, I rebooted the phone and got stuck on CM logo for half hour. I wiped dalvik and got the same result. Then wiped cache and dalvik and still stuck. What should I do? Flash again the rom? The restored data is from CM 10.2.1 so I don't see any problem....
Click to expand...
Click to collapse
check again what you restore, user apps will have no problem to restore but system apps will cause incompatibility to the rom and crash it

Mr.201 said:
check again what you restore, user apps will have no problem to restore but system apps will cause incompatibility to the rom and crash it
Click to expand...
Click to collapse
The phone is good now, I restored the stock rom and from there I flashed CM 10.2.1 just making a factory reset. Plus I flashed adreno drivers and gapps. Once it booted, I restored my apps without sistem data and now the phone works properly.
Thank you Mr.201

chortiman said:
The phone is good now, I restored the stock rom and from there I flashed CM 10.2.1 just making a factory reset. Plus I flashed adreno drivers and gapps. Once it booted, I restored my apps without sistem data and now the phone works properly.
Thank you Mr.201
Click to expand...
Click to collapse
Glad it worked, make sure you untick 'system' in filter in titanium backup so that you can only see your user apps .

[Q] G2 Stuck on CM Spash Screen Loop

Hey All,
Here's a basic synopsis of my issue: I just flashed CyanogenMod on my Sprint LG G2. Now when it boots - or attempts to - it hangs on the CyanogenMod Splash Screen with the spinning cyan arrow.
Here's some more detail:
I've been trying for a few days to get this to work, and I'm finally stumped. I learned the hard way about the LS980ZVA radio and how it's not compatible with non-ZVA ROMs, and whatnot, and I've restored my phone using a .tot 3 times. This most recent time I used the LS980ZV8.tot to enable me to flash CM.
Here's what I did:
Restored phone to LS980ZV8 using LG Flash Tools
Rooted using ioroot
Checked Root
Installed FreeGee Free
Used FreeGee to install CWM 6.0.7.4
Rebooted to recovery
Made a backup
Copied backup to PC
Copied CM-11-20140708-SNAPSHOT-M8-ls980.zip to root of internal storage
Flashed said CM-11.zip from 'sdcard' (It was in sdcard/0/ for some reason)
Rebooted
Got stuck at CM screen.
Did some research on Google
Went back into CWM
Cleared cache
Reflashed CM-11.zip from sdcard
Rebooted System
Stuck at CM screen.
Posted on xda-developers
Any ideas? I can't figure this out for the life of me. I've read something about flashing the boot.img from fastboot, but I can't figure out how to get into the fastboot on the LG G2, and besides that was for an HTC. If you need more info, let me know.
=====Phone Details=====
Carrier: Sprint
Model: LG-LS980
Software: LS980ZV8
Recovery: CWM 6.0.7.4
Rooted: Yes, with ioroot
ROM: Attempted to flash CyanogenMod (cm-11-20140708-SNAPSHOT-M8-ls980.zip)

official.xian said:
Hey All,
Here's a basic synopsis of my issue: I just flashed CyanogenMod on my Sprint LG G2. Now when it boots - or attempts to - it hangs on the CyanogenMod Splash Screen with the spinning cyan arrow.
Here's some more detail:
I've been trying for a few days to get this to work, and I'm finally stumped. I learned the hard way about the LS980ZVA radio and how it's not compatible with non-ZVA ROMs, and whatnot, and I've restored my phone using a .tot 3 times. This most recent time I used the LS980ZV8.tot to enable me to flash CM.
Here's what I did:
Restored phone to LS980ZV8 using LG Flash Tools
Rooted using ioroot
Checked Root
Installed FreeGee Free
Used FreeGee to install CWM 6.0.7.4
Rebooted to recovery
Made a backup
Copied backup to PC
Copied CM-11-20140708-SNAPSHOT-M8-ls980.zip to root of internal storage
Flashed said CM-11.zip from 'sdcard' (It was in sdcard/0/ for some reason)
Rebooted
Got stuck at CM screen.
Did some research on Google
Went back into CWM
Cleared cache
Reflashed CM-11.zip from sdcard
Rebooted System
Stuck at CM screen.
Posted on xda-developers
Any ideas? I can't figure this out for the life of me. I've read something about flashing the boot.img from fastboot, but I can't figure out how to get into the fastboot on the LG G2, and besides that was for an HTC. If you need more info, let me know.
=====Phone Details=====
Carrier: Sprint
Model: LG-LS980
Software: LS980ZV8
Recovery: CWM 6.0.7.4
Rooted: Yes, with ioroot
ROM: Attempted to flash CyanogenMod (cm-11-20140708-SNAPSHOT-M8-ls980.zip)
Click to expand...
Click to collapse
Did you do a full wipe? I would recommend TWRP recovery over CWM. I've used both, but for this phone I prefer TWRP. There are numerous threads with details on how to install it. If you prefer CWM make sure to factory reset/ wipe data, wipe cache, wipe dalvik cache, then flash your rom. Manually shut down your phone then reboot. I've flashed cyanogen Roms on several different phones and they can be finicky. if you choose TWRP then you would do wipe-advanced wipe- check boot, system, data, dalvik, everything except Internal storage. In same recovery session flash your CM rom. Hope this helps. Oh and I would recommend making a backup in TWRP as well if you choose it.

shouldbeshroomin said:
Did you do a full wipe? I would recommend TWRP recovery over CWM. I've used both, but for this phone I prefer TWRP. There are numerous threads with details on how to install it. If you prefer CWM make sure to factory reset/ wipe data, wipe cache, wipe dalvik cache, then flash your rom. Manually shut down your phone then reboot. I've flashed cyanogen Roms on several different phones and they can be finicky. if you choose TWRP then you would do wipe-advanced wipe- check boot, system, data, dalvik, everything except Internal storage. In same recovery session flash your CM rom. Hope this helps. Oh and I would recommend making a backup in TWRP as well if you choose it.
Click to expand...
Click to collapse
No I didn't do a full wipe. I'll take your advice and flash TWRP. I've been out of the Android scene for a couple years and I've had more experience with CWM, didn't know how well recommended TWRP was. I'll flash TWRP, make a new Nandroid, then follow your instructions. Thanks. I'll report back.

shouldbeshroomin said:
Did you do a full wipe? I would recommend TWRP recovery over CWM. I've used both, but for this phone I prefer TWRP. There are numerous threads with details on how to install it. If you prefer CWM make sure to factory reset/ wipe data, wipe cache, wipe dalvik cache, then flash your rom. Manually shut down your phone then reboot. I've flashed cyanogen Roms on several different phones and they can be finicky. if you choose TWRP then you would do wipe-advanced wipe- check boot, system, data, dalvik, everything except Internal storage. In same recovery session flash your CM rom. Hope this helps. Oh and I would recommend making a backup in TWRP as well if you choose it.
Click to expand...
Click to collapse
Awesome!! Thanks so much!! I got TWRP and wiped as you said, then I flashed the CM. It worked!! Thanks!

official.xian said:
Awesome!! Thanks so much!! I got TWRP and wiped as you said, then I flashed the CM. It worked!! Thanks!
Click to expand...
Click to collapse
You are most welcome

[Q] HELP. HTC One X Stuck in bootloop. Almost all famous solutions tried out

So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?

anoopknayak said:
So I wanted to go to Lollipop and I happened to flash the twrp recovery for new layout(as i was getting boot loop when flashing the rom with cwm recovery)
The things i tried until now.
1. Installed twrp and formatted it to get the new layout. Wiped everything, system, cache, data, dalvik cache
2. It was supporting MTP so i transferred the roms to the device being in recovery. Installed CM 12 + gapps for lollipop.
3. Rebooted to bootloader again. flashed boot.img, and did fastboot erase cache.
4. Rebooted again and stuck at CM boot logo.
I wiped the cache, dalvik cache(actually did a factory reset in the twrp recovery) and tried installing Resurrection Remix. Again flashed the relevant boot.img too. But the same result..
Did i destroy my phone?
Click to expand...
Click to collapse
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there

dado323 said:
can you enter in recovery ?
wipe dalik,chace,chace,data then go to,mount select system,chace,data,2gb extra data ,and disabel mtp
if your phone dot show up just leave it on select partions to mount ,unplug cable then plug it back,go to device manager btw and see will it show there
Click to expand...
Click to collapse
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing

anoopknayak said:
Yes I can enter recovery. But again I just cant get any lollipop ROM's working. I dont know whether i have to restore to kitkat(i really dont want too..
I dont get it.. Wipe dalvik cache, cache, data and then disable mtp and then enable mtp.. I mean at the end what does this do?
And in the meanwhile did you mean HTC Sync Manager for device manager. FYI I use a mac(if this helps to get into the problem). And i had flashed kitkat roms from the same without a hiccup but lollipop is failing
Click to expand...
Click to collapse
its hard to explain with recovery you can mount ur sdcard and put another room and install ,the easy way its to start from the begin and install clear CM12 and you will get out from bootloop that help me i was in bootloop like 3920489208420984920 times hahaha

anoopknayak
Have you solve the bootloop issue? I am having the same problem on my International One X
thanks

Probably both of you encountered the same problem as me.
If you are S-on, you have to flash rom and kernel separately. Also, if you try to revert any changes with twrp you have to flash kernel you were using during creation of backup, and then restore backup.
In other words: your current kernel is incompatible with rom.

Mwys
Yes i am S-ON. Can you tell me what the steps are to flash the kernel? I do not have a backup.
What is did was flash New Layout TWRP, did a complete wipe, then copied the ROM and G-Apps zips to the phone, installed them and then flashed boot.img.
Thanks for the help

Yup I also tried the same. but no luck. I tried to revert back to kitkat(by installing cwm, format the storage, sideloaded the ROM and gapps, flashed the boot.img) and still again in bootloop.
Sorry for the delay. I was a lot too busy with work.