Lollipop ROMs will not boot up - Verizon Samsung Galaxy S III

So i've been running stable slimkat 9.0 (4.4.4) on my galaxy s3 and it has been working great. I want to upgrade it to lollipop but I've had trouble flashing any lollipop rom. CM12, AICP, OctOS, PacROM all fail to boot after I flash in recovery. The boot animation starts, and I get the screen that android apps are initializing. After it runs through the apps, the screen blacks out and the phone resets and the cycle continues.
I've had no issues flashing roms beforehand. I can go back to 4.4. and 4.3 ROMs both AOSP and Touchwiz without any problems. I've flashed with both clockwork mod and TWRP and the results are the same. I do a clean factory reset and wipe prior to flashing the rom and 5.1 gapps.
I have no idea why it won't boot up for me. Would appreciate any help!

alphax_0 said:
So i've been running stable slimkat 9.0 (4.4.4) on my galaxy s3 and it has been working great. I want to upgrade it to lollipop but I've had trouble flashing any lollipop rom. CM12, AICP, OctOS, PacROM all fail to boot after I flash in recovery. The boot animation starts, and I get the screen that android apps are initializing. After it runs through the apps, the screen blacks out and the phone resets and the cycle continues.
I've had no issues flashing roms beforehand. I can go back to 4.4. and 4.3 ROMs both AOSP and Touchwiz without any problems. I've flashed with both clockwork mod and TWRP and the results are the same. I do a clean factory reset and wipe prior to flashing the rom and 5.1 gapps.
I have no idea why it won't boot up for me. Would appreciate any help!
Click to expand...
Click to collapse
same problem here bro
sgs3 i9300

i solved mine so if you are still experiencing that hmu i will show you what i did

alphax_0 said:
So i've been running stable slimkat 9.0 (4.4.4) on my galaxy s3 and it has been working great. I want to upgrade it to lollipop but I've had trouble flashing any lollipop rom. CM12, AICP, OctOS, PacROM all fail to boot after I flash in recovery. The boot animation starts, and I get the screen that android apps are initializing. After it runs through the apps, the screen blacks out and the phone resets and the cycle continues.
I've had no issues flashing roms beforehand. I can go back to 4.4. and 4.3 ROMs both AOSP and Touchwiz without any problems. I've flashed with both clockwork mod and TWRP and the results are the same. I do a clean factory reset and wipe prior to flashing the rom and 5.1 gapps.
I have no idea why it won't boot up for me. Would appreciate any help!
Click to expand...
Click to collapse
Are you on the correct firmware? MF1? There is a flashable zip in the CM12.1 thread for it.

Updating the firmware did the trick, thanks! Was running on ML1 up til now. Glad my s3 can still keep up with the times

Related

[Completed] My t999 s3 doesnt want to install cyangenmod

i had cm10 installed but after a few months of problems i decided to upgrade to cm11. After trying to upgrade to twrp 2.8.3 something happened then my cyangen was tripping balls so i went back to stock s3 4.1.3 by flashing with odin. Then i rooted my s3 again using odin. Then i installed rashr and installed twrp 2.8.3. Then i booted into twrp 2.8.3 and before twrp loaded it had the cyanogen logo on it.Then did factory reset and the davik cahce clear thing. Then i proceeded to installed cm11 20141112 snapshotm12 and gapps kk20140606 but when i rebooted my s3 in still goes into the stock andriod what is going on? i tried to install cyanogen mod from a different sd card and i have no luck
eric95204 said:
i had cm10 installed but after a few months of problems i decided to upgrade to cm11. After trying to upgrade to twrp 2.8.3 something happened then my cyangen was tripping balls so i went back to stock s3 4.1.3 by flashing with odin. Then i rooted my s3 again using odin. Then i installed rashr and installed twrp 2.8.3. Then i booted into twrp 2.8.3 and before twrp loaded it had the cyanogen logo on it.Then did factory reset and the davik cahce clear thing. Then i proceeded to installed cm11 20141112 snapshotm12 and gapps kk20140606 but when i rebooted my s3 in still goes into the stock andriod what is going on? i tried to install cyanogen mod from a different sd card and i have no luck
Click to expand...
Click to collapse
Do you mean this unofficial CM11: [ROM][4.4] CM 11 Unofficial - Beta 7 11-22-13 (Discontinued due to new device)?
Or this one: Cyanogenmod CM11?
Please check this thread: T999 UVDMD5 Firmware / Bootloader.
According to this, you might have to update some files (bootloader, modem, etc.) to be able to install newer CM versions.
AFAIK, only CM10 is officially suported for your device: [ROM][OFFICIAL] CyanogenMod 10 Nightly Builds for SGH-T999.
If you have further questions, please ask in the T-Mobile Galaxy S III Q&A, Help & Troubleshooting.
Thread closed and thank you.

Bootloader loop with Optimizing apps and reboots for CM12.1

I was trying install CM12.1 ROM for Galaxy S3! [Android 5.1] on my existing CM12 [5.0.2]. I followed this article and installed http://galaxys3root.com/galaxy-s3-roms/cm12-1-rom-for-galaxy-s3-android-5-1/.
I did install ROM and GAPPS. Now It is bootloader loop. it is coming all the way to Optimizing apps and reboots again. I think is almost softbrick. I cannot access SD card in my computer to push new ROM or change ROM. What are options I have ?Anything I can do with ODIN? please provide me some steps.
ItsMeSri said:
I was trying install CM12.1 ROM for Galaxy S3! [Android 5.1] on my existing CM12 [5.0.2]. I followed this article and installed http://galaxys3root.com/galaxy-s3-roms/cm12-1-rom-for-galaxy-s3-android-5-1/.
I did install ROM and GAPPS. Now It is bootloader loop. it is coming all the way to Optimizing apps and reboots again. I think is almost softbrick. I cannot access SD card in my computer to push new ROM or change ROM. What are options I have ?Anything I can do with ODIN? please provide me some steps.
Click to expand...
Click to collapse
Before you did that what version of Android was the S3 on?
Sent from my Nexus 5
Today I tried again on CM 12 and 5.0.2 with [ROM][Official]CyanogenMod 12.1 Nightlies for the Verizon Galaxy S3 (d2vzw) and http://wiki.cyanogenmod.org/w/Google_Apps . Still it is the same.
It is on boot loop "Optimizing app.." and then rebooting again. I don't know the solution to fix.
ItsMeSri said:
Today I tried again on CM 12 and 5.0.2 with [ROM][Official]CyanogenMod 12.1 Nightlies for the Verizon Galaxy S3 (d2vzw) and http://wiki.cyanogenmod.org/w/Google_Apps . Still it is the same.
It is on boot loop "Optimizing app.." and then rebooting again. I don't know the solution to fix.
Click to expand...
Click to collapse
As per my question previously, what version of Android were you on prior to flashing LP?
Sent from my Nexus 5
CM12 and 5.0.2
ItsMeSri said:
CM12 and 5.0.2
Click to expand...
Click to collapse
Its very possible 5.1 won't work on the S3. I would never follow some random link. XDA is reputable but other sites very well may not be. I still have my S3 on 4.4. My Nexus runs 5.1 fine but then again it's made to run the newest firmware
Sent from my Nexus 5

[Q] Custom rom in bootloop ?

I have build from source CM12 and when I flashed the ROM it is in an infinite loop in the GOOGLE logo. I have done everything correctly.
I installed a CM12.1 build and there is no problem.
Flashed factory images of 5.0, 5.02 an 5.1.1 and then flashed my build but still it is in loop. No problem when I flash a CM12.1 build.
Can you point out what I did wrong ?
eNVy said:
I have build from source CM12 and when I flashed the ROM it is in an infinite loop in the GOOGLE logo. I have done everything correctly.
I installed a CM12.1 build and there is no problem.
Flashed factory images of 5.0, 5.02 an 5.1.1 and then flashed my build but still it is in loop. No problem when I flash a CM12.1 build.
Can you point out what I did wrong ?
Click to expand...
Click to collapse
If you built from source with no modifications, it should work fine provided that you are installing it on top of the same version of Android. That means if CM12 is 5.0.2 you probably have to install it on top of a fresh install of stock 5.0.2 or some 5.0.2 ROM.
You should also wipe data and dalvik (you probably did seeing as you claim to have done everything correctly).

[Q] Stuck in Boot animation after flashing cm12.1

I managed to get my xt925 updated to KKBL, and after flashing cm12.1 I'm stuck in the boot animation. I tried flashing several cm11 versions as suggested somewhere else as step inbetween, but most of them resulted in boot loops (right after unlocked bootloader warning) Any Idea how to fix this ?
btw. I'm trying to flash the lastest cm12.1 . unfortunately I did not make a backup uf stock KK rom before starting this. silly me Is there a stock 4.4.2 ROM available to flash with RSDLite ? I Already tried to restart the whole process - but flashing Stock JB won't work after having KK BL
scherliberli said:
I managed to get my xt925 updated to KKBL, and after flashing cm12.1 I'm stuck in the boot animation. I tried flashing several cm11 versions as suggested somewhere else as step inbetween, but most of them resulted in boot loops (right after unlocked bootloader warning) Any Idea how to fix this ?
btw. I'm trying to flash the lastest cm12.1 . unfortunately I did not make a backup uf stock KK rom before starting this. silly me Is there a stock 4.4.2 ROM available to flash with RSDLite ? I Already tried to restart the whole process - but flashing Stock JB won't work after having KK BL
Click to expand...
Click to collapse
Fixed the Issue by flashing Slimrom 4.4.4 as interlude. Now I'm on CM12.1 and bootup process is normal.
Thank you, so much!
scherliberli said:
Fixed the Issue by flashing Slimrom 4.4.4 as interlude. Now I'm on CM12.1 and bootup process is normal.
Click to expand...
Click to collapse
I was with the same problem and a fixed it after read your tip!! thank you very much!!!!
That is what did the trick for me too.
At first cm12.1 wouldn't run on my XT925. Then i flashed SlimROM 4.4.4, booted it up, rebooted into recovery mode (twpr 2.8.6.0), flashed cm12.1, wiped cache and dalvik and then rebooted.
Now it runs stably on cm12.1. Thanks a lot!

Is an up to date bootloader necessery and can it causes bug in CM?

Hi I am currently on the canadian note 4. I am having some difficulty with cyanogenmod 12.1 lately so I wanted to move to CMRemix for better stability. The Installation guide ask the bootloader and the modem to be updated, I am doing that by reverting to an up to date stock rom and then installing CMRemix (Odin did not want flash for some reason.)
What I understand from the bootloader is that it is like the BIOS on a PC. Can my not up to date bootloader be causing the bug on CM 12.1? I am having the bluetooth crash bug and an overall slow system. CM also does not seem to work to well with spotify.
I am not an expert but I have been running custom rom for 3 years on my note 4 and note 2.
Thanks
PhilRattlehead said:
Hi I am currently on the canadian note 4. I am having some difficulty with cyanogenmod 12.1 lately so I wanted to move to CMRemix for better stability. The Installation guide ask the bootloader and the modem to be updated, I am doing that by reverting to an up to date stock rom and then installing CMRemix (Odin did not want flash for some reason.)
What I understand from the bootloader is that it is like the BIOS on a PC. Can my not up to date bootloader be causing the bug on CM 12.1? I am having the bluetooth crash bug and an overall slow system. CM also does not seem to work to well with spotify.
I am not an expert but I have been running custom rom for 3 years on my note 4 and note 2.
Thanks
Click to expand...
Click to collapse
Odin didn't want to flash the stock ROM???
Flash a stock ROM with Odin. Then flash a custom recovery like TWRP. Then do an advanced wipe and wipe cache delvik, system, data. The bluetooth could be unstable on CM12. You can look for a stable ROM and flash that if you're looking for everything to work flawlessly
i7vSa7vi7y said:
Odin didn't want to flash the stock ROM???
Flash a stock ROM with Odin. Then flash a custom recovery like TWRP. Then do an advanced wipe and wipe cache delvik, system, data. The bluetooth could be unstable on CM12. You can look for a stable ROM and flash that if you're looking for everything to work flawlessly
Click to expand...
Click to collapse
I tried flashing the modem and bootloader, not the entire firmware. I ended up installing the stock firmware in the end. I am doing the updates now and will install CMRemix shortly after
I always go stock before I flash a new ROM. Best way unless directed otherwise

Categories

Resources