Updating to newest CyanogenMod nightlies bricks phone - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

It's not a hard perma brick. I can get back into TWRP recovery and reflash from my latest backup and my phone boots up and works just fine. But this started last night. I downloaded and flashed the update like normal. Phone rebooted, showed the Samsung logo, then came the Galaxy S3 splash screen with the little blue guy. And it never went away. Phone froze like that. I figured maybe it was just a random one time bug. So I reflashed my latest backup and waited. Tonight there was another nightly. So I downloaded it, made a new backup, installed, same thing. I even did a complete factory data reset.
Idk what's up. Right now my phone works fine but it's gonna suck if I'm unable to flash new roms.

According to this it's supposedly fixed.
http://review.cyanogenmod.org/#/c/49972/

Related

soft brick but!!!!!

hopefully someone can help me. I have a verizon nexus, bootloader is unluck and rooted and has a recovery. Im not new to flashing Ive flash every rom there is for the nexus. last night i backed up my rom before flashing the axi0m av9 i was running av6 prior, once it was done installing i rebooted, the Google black screen showed and then on the next screen the phone went back to the Google black screen and it kept doing it.
pulled the battery out went into recovery, wiped everything and tried again, same thing. tried to restore and after a min it told me incomplete restore not successful. i tried loading another rom that has work in the previous and same thing soft bricked, tried loading another restore a and no luck. all have been going to soft brick. it has a full charged i did wipe everything before all installs. can someone please help me

[Q] Jellybomb start up problems

The problem only happens when I reboot or turn on the phone. When it boots up, I get multiple results. A: It boots up normally (not a problem) B: When it gets to the samsung screen, it freaks out and reboots itself again and again. It's like it's struggling to boot up. One time it got to the gs 3, but then it looped back. C: This just happened today. I booted up and it went pass the samsung screen but when it got to the gs 3 screen, the screen turned a faint pink and it stayed on that screen.
This just happened right after version 8. I know 10 was messed up but on 9 and 11, this problem persisted. Also,I don't think the issue is the phone, since I don't have this problem on other Roms. If I'm wrong please let me know .
Any suggestions, advice, help, etc is welcomed.
Please... i really need help.
I suggest you start over, this will remove any corruption and gremlins you have klinging to your phone..
http://forum.xda-developers.com/showthread.php?t=1904099.. Then re root and flash anew.
Naddict said:
I suggest you start over, this will remove any corruption and gremlins you have klinging to your phone..
http://forum.xda-developers.com/showthread.php?t=1904099.. Then re root and flash anew.
Click to expand...
Click to collapse
I unrooted, went back to stock, it did a factory reset so no bugs should have been alive. I re-rooted, made a backup, did a factory reset and wiped dalvik, then I flashed the rom zip and rebooted. It gets stuck on the Gs III screen. I waited like 5 minutes and it didn't move. My battery was at 50% so I just put it on the charger and tried to boot up and it went through to the set up screen for gmail.Just to see if it was coincedental, I did another reboot but this time it got stuck again. It sounds like a system problem but i'm not sure.Like i said earlier, this only happens on Jellybomb.
Any other ideas?
Edit: I've tried switching recoveries but it doesn't fix it.
Sigh.

Startup seems broken - CWM Working

[Samsung Galaxy Note II N7100]
((EDIT: Suddenly, after leaving it turned off for about 15 minutes, it works. It just powered up IN THE PACMAN ROM! Still no clue what happened though, Would like to find out for the future))
Hello there,
My device was working fine yesterday, however today I re-rooted after an update. This went well and all was working fine, until I decided to try my first ROM, the PACMan ROM. I flashed with CWM6 (Following a tutorial, using Odin) which seemed to work fine until I actually tried to use it. I went to reboot my phone, and when it started up, it was (graphically) glitching, with the Samsung Galaxy Note II logo twitching around the screen, and a strange set of brown, thick-ish bars moving around the bottom half. Following a few seconds of this, the device shut off.
Following this I discovered that I could get it to stay on and boot-up successfully if I held down the home button (Not sure if relevant), however I still wanted to get down to the bottom of the issue. Following some research, I decided to try and flash a different download of CWM 6 for my phone again. This time it worked, and I went straight to factory reset then install the 'Gapps' and ROM file. There were no unexpected errors in this installation, however when the phone restarted, the same glitch occurred, only without a way past it.
I have since tried patching with the other CWM file that didn't work to see if perhaps I could use my phone again, but this didn't work. Similarly, I've used the working CWM to do a factory reset without installing any ROMs, and the booting still didn't work.
Please help I don't wan't to risk doing further damage, and would be perfectly happy going back to regular jellybean.
Thanks in advance!
Regards,
Thomas
TL;DR My Galaxy Note I N7100's boot is after flashing

How I fixed my “stuck at Samsung" issue

Back story was basically I went to use my phone that was running dicksteele buttnaked and it was frozen so I did a battery pull and that just froze up at Samsung screen and wouldn't let me into twrp. Sorry if this is a bit all over the place but if you are stuck like I was it may offer some help or at least get you thinking that you may not have tried absolutely everything.
@terpin32 got it back up, thanks for the help and all the suggestions from my post and the others I read here. Read all the suggestions for stuck at Samsung posts. Flashed via Odin all the param tz files I could find no luck. Still couldn't get it to boot normally or into recovery. So I flashed twrp via Odin still couldn't get into recovery. So I tried Phillz via Odin and bam got into recovery.
Now the issue was I had no backups via Phillz. So I tried wipes of cache and davlik still no normal reboot. Then I tried to do a full wipe to load a new ROM and the phone locked up and rebooted again. So I got back into recovery and began just trying to flash ROMS since my options were getting more limited.
First tried Buttnaked and it wouldn't boot same thing as before. Went back into Phillz and tried a full wipe for new ROM again. Froze before it finished and rebooted again. So I tried zens 4.3 and it froze on bootup. Tried to full wipe same result. Thought hey I will give a Aosp Rom a go. Dirty unicorns and everything looked like it was going to boot because it didn't freeze but it also never booted and just hung. Back into Phillz and tried a full wipe again and it frikn worked. Now I was getting somewhere. So I flashed twrp back and wiped everything again. Went to my last backup of DickSteeles ButtNaked and it booted back up just like nothing happened. My sound issue I was also having is fixed since my save was before it went goofy.
Not sure if this will help anyone but thought I would share. I do troubleshooting a lot at work and sometimes it's extreme. I came to the realization that I might need a new phone so I tried everything I could think of. My wifi is a little wonky probably because of the tz files I flashed but I will take that over the stuck bootup.

This doesnt quite seem like a boot loop... Help?

So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
ride1226 said:
So my phone has been perfect for over a year. Within the first month of owning it I rooted, installed TWRP, and jumped on CM13. Been updating nightlies all year long once every week or so and enjoying the phone. Its really been perfect. Tonight after work I jump in my car, throw it on my car charger, and drive home. When I get home I notice for some reason I have no cell service (Emergency Call Only) so I reboot. That was the end. The reboot got stuck on the CM boot screen flashing the circle out around the CM face over and over and over. So, I pop the battery, try again, same thing.
Well, being that I have rooted and flashed for years now I figured Id wipe dalvik and cache. Tried that, same thing. Did a full wipe and reinstalled the nightly from my SD card. This time I thought I made progress as it set up all the apps. Then it just hangs on "starting apps" and then it sits there forever. Never boots. Doesnt loop or restart or anything, just says its starting apps.
So, jump on here and find the bootloop issue. My serial is 505x so I was wondering if maybe thats my issue. Decide to download the all in one flash zip from here...
http://forum.xda-developers.com/tmobile-g4/development/stock-h811-20i-images-kdz-flashable-t3308227
and I flash that. Stock rom works without any issue. Fired it up, logged in, no problems. Huh. Do a restart and even though I flashed that file it still shows bootloader unlocked as the LG logo comes up, and boots into TWRP as normal as well. Figured well I flashed a stock rom, lets give CM13 a try again. I download a fresh nightly through my pc and transfer it over via usb so I know its good. Full wipe, flash, reboot, hangs at "starting apps" again.
Now I am lost. The stock rom sucks and my love for this phone is based around what it is with CM installed. Am I missing something here? I really want to get back to CyanogenMod and away from the clunky slow stock rom.
Any input is greatly appreciated. Thank you all.
EDIT: Well went through the Android setup steps after flashing the stock rom so I would have a phone until this was all figured out. Turned out its not working. After setup I am not getting "Process System Isn't Reponding: wait or close" No matter what I do the phone is so slow or laggy I cant use it. Its trying to download my apps and restore my phone from my Google account but it just hangs up. No idea what to do at this point. Is my kernel messed up? Its a totally clean flash. What the heck. 3am, I give up, hopefully someone has insight in the morning. Thank you all.
Click to expand...
Click to collapse
You really have to investigate by adb. Look into the dmesg output and logcat as well. Maybe your sdcard is corrupt or 100 other issues are possible as well. What device do you own? H811? unlocked?
.
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
kunate said:
I have rooted my lg g4 h811 and am trying to flash cm 14, after flashing it through twrp, my phone stuck in bootloop. i try o put it in recovery but it only gives me factory reset option which i did several times but still stuck on bootloop. what should i do?
Click to expand...
Click to collapse
There are several users reporting that the latest cm version bootloop the best option is to start in download mode and Flash with LGUP Stock ROM.
You could also try to boot into Download Mode and then flash the latest twrp and then Boot into Factory Reset Mode again

Categories

Resources