[Q] Verizon ROMS stuck at boot....other boot fine? - G2 Q&A, Help & Troubleshooting

So I have a VS980 Verizon G2. I have never had issues flashing in the past. I recently did a complete wipe to install CM12. Rotation was broken so I went back to a debloated Verizon 39A rom that I have never had any issues with. I get to the white Verizon boot screen and sits there forever. I don' t remember it EVER taking this long . I am pretty sure 20 minutes has went by but I always forget to time it.
I can flash the stock 26a KK Verizon ROM and it works fine and only take about 4 minutes to get past the boot screen. I can then do complete wipe and flash 39A radio and CM12 and it boots fine. I then decide to fix rotation and sensors again so I do complete wipe (to include internal storage as I am doing my flashes from USBOTG adapter). Flash stock 39 A ROM (tried debloated and stock both) and Verizon Screen forever.
I even did a restore of the debloated 39A ROM in TWRP and it will actually boot but it sits for ages at the "Android is upgrading.... starting apps" screen and I got tired of waiting more than 10 minutes for it to boot. Why is everything else but stock based Lollipop ROMs working fine?! What is going on with this thing? I have never seen this before.

Related

Phone freezes before OS loads. Help!

I'm having a major issue with my phone. I installed TWRP version ending .2 and been using roms with no issues. I also never had an issue with my GS3 in the past. In any event, I recently tried to install the FREEGS4 rom and it initially loads fine. However, when I rebooted, it froze at the Samsung Galaxy S4 logo screen. I tried formating data and reflash rom. It flashes fine and loads fine initially.. but when I reboot, it freezes at logo screen. I tried to flash another custom MDL rom and it loads fine initially but freezes at reboot.
I tried to ODIN back to stock MDC. It flashes fine but when it auto reboots, it freezes at Samsung Galaxy S4 logo screen. I tried to ODIN back to stock with MDL rom. Same issue.. The only way I can get the OS to load is if I install TWRP and I do a quick flash of a ROM. It will intially load the ROM fine but if I power off or reboot the phone, it will freeze on the Samsung Galaxy S4 Logo screen.
Does anyone what could be causing this and any recommendations on how to fix it?
spydc said:
I'm having a major issue with my phone. I installed TWRP version ending .2 and been using roms with no issues. I also never had an issue with my GS3 in the past. In any event, I recently tried to install the FREEGS4 rom and it initially loads fine. However, when I rebooted, it froze at the Samsung Galaxy S4 logo screen. I tried formating data and reflash rom. It flashes fine and loads fine initially.. but when I reboot, it freezes at logo screen. I tried to flash another custom MDL rom and it loads fine initially but freezes at reboot.
I tried to ODIN back to stock MDC. It flashes fine but when it auto reboots, it freezes at Samsung Galaxy S4 logo screen. I tried to ODIN back to stock with MDL rom. Same issue.. The only way I can get the OS to load is if I install TWRP and I do a quick flash of a ROM. It will intially load the ROM fine but if I power off or reboot the phone, it will freeze on the Samsung Galaxy S4 Logo screen.
Does anyone what could be causing this and any recommendations on how to fix it?
Click to expand...
Click to collapse
Before flashing a new ROM, did you clear dalvik and cache?
Yes. I always do. I even tried formatting data. I also tried odin back to stock rom. I am using the phone now because it boots the first time after flashing a custom rom. I havent rebooted since but as soon as I do, it will freeze and I would need to re flash custom rom. Stock rom freezes too
Sent from my SPH-L720 using xda app-developers app
When you Odin back to stock did you do another factory reset after boot? You need to do 2 factory resets after boot also wipe system when flashing ROMs.
i have the same issue as you.
idk if this fixed it but i went back to the stock recovery and did a factory reset twice rebooted my phone then installed twrp. flashed freegs4 and now my os boots up with no issues.

[Q] Phone will not start after first restart from a fresh flash

I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
schmidty455 said:
I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
Click to expand...
Click to collapse
Omni clearly states that it is an alpha, so you mileage may vary considerably.
Sounds kernel related. Have you tried just reflashing the kernel and seeing if it'll boot after that. Or trying a different kernel?
Thanks for the reply! I actually just fixed the problem on my own. I used Odin to flash a newer version of TWRP and then flashed omni, and it looks like everything is working just fine. I read a few people saying that they were having issues flashing kit kat roms with older versions of recovery, so I figured it was worth a shot.

[Q] Bootloop after flashing any ROM after 4.4.2 update. How do I fix this?

So I have been running CM11 since January and finally got around to updating to KitKat to see what was new and because CM11 wasn't using the kitkat kernel which I assume is what caused all the SoDs and instabilities in all the ROMs. Well now I'm on stock and I'm suffering horrible battery life in comparison (17 hours with 4 screen on vs 36 hours with 8 screen on). I tried flashing CM11 and it worked but after a day or two I wanted to try a new ROM. Carbon was one that I saw near the top of one of the G2 development forums so I decided to try that. Went through the normal process to flash a ROM and it bootlooped when I rebooted. My backup also boot looped and I had to use some method to go back to 12B since I had no ROM or anything on my phone. Got back to 24A and I tried flashing Malladus to see if a stock based ROM would work and it looped. Restored my backup and tried CM11 and it also looped. Now I'm sitting on stock with Verizon's bloat hogging resources and battery and a phone that won't flash and boot successfully. Is there any way I can fix this? Has anyone seen this before?
TLDR: phone won't flash a ROM without bootlooping since 24A update
Only gonna bump this once but I really hope the right person sees this. Really confused as to why my phone won't properly boot after a clean ROM flash

[Q] Is my G2 dead?

Ive been running CM12 for a long time, but today I noticed I had a few missed calls and my phone hadnt rung. I rebooted the phone and it went into a boot loop. I cleared cache, but still bootlooping, dirty flashed the latest nightlie and then a full wipe - all of which resulted in the boot loop.
I restored my phone using the TOT method, but it would get to the setting up google account/wifi etc and reboot.
I used KDZ to install 30b lollipop ROM this seemed ok until reboot and then it would factory reset, optimise apps every time and be back to the setup screen.
I managed to install KK using KDZ and this seems more stable so used IOROOT and Autorec. I then flashed CM12 and GAPPS again, but it started to boot loop again.
I hadnt done anything to my phone prior to the problems - ie. no new ROMs, kernels or even apps.
Any suggestions or does it sound like something more physically wrong?
I have managed to get Cloudy G2 2.2 working without any problems except it isn't recognising my SIM. Does anyone have any thoughts or is this a dead phone?

Galaxy s5 (g900v) wont start after safestrap prompts

i have been trying to install a good rom on my s5. i know that since i have an 11' toshiba chip, i cant do any major custom roms only stock touchwiz roms. i have 3 or 4 that i have found that actually work on my phone and when i tried a new rom today, it didn't work. so i flashed 4.4.2 again to start from scratch and i went back to my usual stock deodexed rom that is always a for sure rom that works. today when i flashed it, twrp (safestrap) prompts me to either boot normally or to continue. i have had this problem in the past, and whenever it shows that screen, it will never boot up, after the prompt it will just have a black screen for about 5 min. before booting stock recovery. if i boot it up again, safestrap will still prompt me if i want to boot recovery or continue and keep repeating this cycle. last time, it had resolved itself and didnt show up after wiping and reflashing my rom. this time it wont go away and my phone wont boot anything. thanks in advance
as.hs said:
i have been trying to install a good rom on my s5. i know that since i have an 11' toshiba chip, i cant do any major custom roms only stock touchwiz roms. i have 3 or 4 that i have found that actually work on my phone and when i tried a new rom today, it didn't work. so i flashed 4.4.2 again to start from scratch and i went back to my usual stock deodexed rom that is always a for sure rom that works. today when i flashed it, twrp (safestrap) prompts me to either boot normally or to continue. i have had this problem in the past, and whenever it shows that screen, it will never boot up, after the prompt it will just have a black screen for about 5 min. before booting stock recovery. if i boot it up again, safestrap will still prompt me if i want to boot recovery or continue and keep repeating this cycle. last time, it had resolved itself and didnt show up after wiping and reflashing my rom. this time it wont go away and my phone wont boot anything. thanks in advance
Click to expand...
Click to collapse
Find youre phones firmware and put phone into download mode and flash firmware!

Categories

Resources