I got my Optimus G a few days ago and since then decided to put a custom ROM on so I can get Android 4.3. I've tried two methods, rooting, unlocking, etc. with Stock and then flashing a different rom. As well, I've simply used LGNPST to put TeenyBin on before flashing a custom ROM.
I've tried with several ones, from CyanogenMod to SlimBean to Carbon and a few others. For the majority of them, it boots up correctly after being flashed, but the first time I reboot the phone after this it will never start up. It just freezes at the "Google" screen, or for some ROMs it shows this briefly then turns black. Either way, it never successfully boots up once it's been restarted a single time.
I've tried all the options in the Recovery mode, formatting, wiping, clearing cache/Dalvik cache, etc. But no matter what it still doesn't make it past boot.
I can successfully put back Stock on it with LGNPST, but I want to get 4.3 and I can't find a solution that will continue to work after the phone reboots. Any idea how to solve this?
dabomb18359 said:
I got my Optimus G a few days ago and since then decided to put a custom ROM on so I can get Android 4.3. I've tried two methods, rooting, unlocking, etc. with Stock and then flashing a different rom. As well, I've simply used LGNPST to put TeenyBin on before flashing a custom ROM.
I've tried with several ones, from CyanogenMod to SlimBean to Carbon and a few others. For the majority of them, it boots up correctly after being flashed, but the first time I reboot the phone after this it will never start up. It just freezes at the "Google" screen, or for some ROMs it shows this briefly then turns black. Either way, it never successfully boots up once it's been restarted a single time.
I've tried all the options in the Recovery mode, formatting, wiping, clearing cache/Dalvik cache, etc. But no matter what it still doesn't make it past boot.
I can successfully put back Stock on it with LGNPST, but I want to get 4.3 and I can't find a solution that will continue to work after the phone reboots. Any idea how to solve this?
Click to expand...
Click to collapse
I Had Exactly The Same Problem,I Wiped Internal Storage(I Had Took A Backup First)
Then Flashed Stock 20j Via LGNPST
Then Rooted It And Downloaded FreeGee App And Unlocked Bootloader And Installed Recovery.
And Now I Don't Have That Issue.
Regards,
acervenky,
XPT
acervenky said:
I Had Exactly The Same Problem,I Wiped Internal Storage(I Had Took A Backup First)
Then Flashed Stock 20j Via LGNPST
Then Rooted It And Downloaded FreeGee App And Unlocked Bootloader And Installed Recovery.
And Now I Don't Have That Issue.
Regards,
acervenky,
XPT
Click to expand...
Click to collapse
Thanks for the reply acervenky. I did what you said and got it rooted successfully, but then when I unlocked the Bootloader using FreeGee0.5 it said it worked successfully. However, when I tried rebooting it got stuck on the LG logo and I had no luck getting into the bootloader screen.
Edit: In the past, I followed different guides that would supposedly unlock your phone using the FreeGee app from the Play store, but those didn't work either when I tried them. Generally they would say successful, but even then most of the time it wouldn't work afterwards.
Okay somehow I got it working!
I'm not sure what steps along the way fixed it, but essentially I re-flashed a few times, either 20j stock or TeenyBin [Alt]. Eventually, wiping, formatting, etc. and installing my custom ROM SlimBean worked. The difference was that this time it works now when I reboot, so I don't have a gimp form of 4.3.
Thank you again acervenky, I'm not sure how but installing 20j seems to have done the trick. On the plus side, when I continued to reflash 20j it would always keep my data, allowing me to mess around without having to worry about losing all my settings.
dabomb18359 said:
Okay somehow I got it working!
I'm not sure what steps along the way fixed it, but essentially I re-flashed a few times, either 20j stock or TeenyBin [Alt]. Eventually, wiping, formatting, etc. and installing my custom ROM SlimBean worked. The difference was that this time it works now when I reboot, so I don't have a gimp form of 4.3.
Thank you again acervenky, I'm not sure how but installing 20j seems to have done the trick. On the plus side, when I continued to reflash 20j it would always keep my data, allowing me to mess around without having to worry about losing all my settings.
Click to expand...
Click to collapse
Glad That It Helped,Just Press The Thanks Button Instead Of Replying.
It Means A Lot :highfive:
Regards,
acervenky,
XPT
Related
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
Okay. So. After some trouble with houstonn's latest rom's lately (getting stuck on boot), I decided I'd give one more try for the 4/30 release. Clean wipe, flashed it, flashed minimal apps. Stuck on boot. WOOP WHO CARES?
This time was different - I couldn't access recovery. So I tried like 30 more times to access recovery. Couldn't do it. LGNPST back to the ICS stock bin (11c). Get my OTA update to 4.1.2, rooted with this method http://forum.xda-developers.com/showthread.php?t=2006946. After that, I tried to access recovery mode again. Couldn't do it. So, I was like "what the hell, maybe FreeGee will help." So I continued on to unlock the bootloader with FreeGee and with CWM. Installed quickboot and chose to restart to recovery. SAME THING. Black Screen after LG logo. Can't get into recovery.
Now I'm LGNPSTing back to stock to repeat process. Any ideas on what's going on?
Edit: Running into quite a few problems with LGNPST. Gets stuck at 85% and won't boot even after power cycle.
Edit 2: TeenyBin AltBin let me format my partitions and then the LGNPST worked. Got the OTA. Rooted again, used FreeGee, except this time with TWRP 2.5.0.0. Wouldn't reboot afterwards, so moved on to TeenyBin AltBin again. The phone booted up and everything runs fine. One thing to note: I had some wifi problems when I just TeenyBinAltBin'd and used a restore point for stock 4.1.2 which is why I was so adamant to LGNPST like normal. Still can't flash any of the newer ROMs of houstonn's, but I can others. On the good side, I still have a phone. Hopefully if anyone else has the issue, they can follow this and resolve it.
I've been trying different ROMS and I used SlimROM for awhile until I realized GPS didn't work and my cell connection sucked comapred to TW-based ROMS. Then I tried Hyperdrive which worked at first but every time I would reboot after the first power on after the install, it would stay stuck on the Samsung screen. I reinstalled it time after time (like 6 times) and it would never REboot after the first boot. Every other ROM I've tried installing (Illusion, Synergy, CleanROM) just gets stuck right after the install and they never boot.
I've also noticed that when I try to do a factory wipe after installing anything but SlimROM, I get "error mounting /data" and "error mounting /sdcard/.android_secure".
I've tested installing all of these with the newest verison of TWRP and CWM v6.0.3.2
any ideas?
Factory reset Last option
snowman4839 said:
I've been trying different ROMS and I used SlimROM for awhile until I realized GPS didn't work and my cell connection sucked comapred to TW-based ROMS. Then I tried Hyperdrive which worked at first but every time I would reboot after the first power on after the install, it would stay stuck on the Samsung screen. I reinstalled it time after time (like 6 times) and it would never REboot after the first boot. Every other ROM I've tried installing (Illusion, Synergy, CleanROM) just gets stuck right after the install and they never boot.
I've also noticed that when I try to do a factory wipe after installing anything but SlimROM, I get "error mounting /data" and "error mounting /sdcard/.android_secure".
I've tested installing all of these with the newest verison of TWRP and CWM v6.0.3.2
any ideas?
Click to expand...
Click to collapse
if nothing works, factory-reset but last option.
yeah I just started downloading the stock rom to flash with ODIN in the morning. I just wanted some reason why this would happen so I won't always have have this problem and to know why it only works with some roms over others.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Im having the same problem. I've done a complete ODIN restore to stock like 10 times, while trying Hyperdrive downloaded from 2 sources all with a matching MD5.
I'm on rooted stock right now until someone can figure this out.
I followed the rooting procedure... tried TWRP and Clockwork recoveries... Followed all instructions to the T...
Not sure what else to try... Or what I could be doing wrong... All I can think of now is restoring someones nandroid backup...
Being stuck at the Samsung Galaxy S4 screen sucks...
Zothar said:
Im having the same problem. I've done a complete ODIN restore to stock like 10 times, while trying Hyperdrive downloaded from 2 sources all with a matching MD5.
I'm on rooted stock right now until someone can figure this out.
I followed the rooting procedure... tried TWRP and Clockwork recoveries... Followed all instructions to the T...
Not sure what else to try... Or what I could be doing wrong... All I can think of now is restoring someones nandroid backup...
Being stuck at the Samsung Galaxy S4 screen sucks...
Click to expand...
Click to collapse
I restored to stock using these files http://www.sxtpdevelopers.com/showthread.php?t=237 to flash through ODIN. Rerooted by flashing the older kernel, rooting, installing superSU, then reflashing the newer kernel (normal root procedure). Then I insatlled ROM Manager and gave it root to install CWM recovery. Then I flashed to my same Hyperdrive ROM I was using before and now everything works beautifully. Nothing gets stuck anywhere an no more "cannot mount /data"
Just use that site and restore to stock and everything should work fine.
I'd like to add some confirmation to this. I had similar problems after flashing my first ROM- phone wouldn't reboot a second time, and when I attempted to make nandroids the files would be ridiculously large (~1 TB). I restored to the stock Touchwiz, rerooted normally, and reflashed normally. The strange thing is that I did the rooting and the flashing with the same files I had used the first time, implying something went wrong during the first rooting/flashing process.
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:
I'm using an LS990 that I've had since about when they came out. When Stumproot came out I rooted it, and I had installed the original TWRP Bump when that came out, but I've been running the rom it came with (ZV4 I believe, though I cannot check). Nothing had been unusual until today, when I put the phone in my pocket after using it for normal daily stuff, then when I later took it out it seemed to be in TWRP. I had almost never even booted into it on the G3 other than a very few times when I first installed it (I had been waiting for a CM12 that was stable enough for my liking).
No matter what I do, it seems to be stuck in recovery. I've updated to the latest TWRP (2.8.4.0) and that seemed to take just fine. However, when I try flashing a rom, it just flashes like normal, log says it's great, then....reboot takes me back into recovery. I tried the ZV4 base at first, then the ZV6 base, both with and without wiping all the appropriate partitions, but nothing seems to change. I am getting ready to try non-stock roms, but I thought I'd ask here first to see if anyone has any ideas? Any help much appreciated!
(not worried about my data, I had daily TB backups running which uploaded to Dropbox, so it's all saved, willing to wipe anything and everything)
Click "format data" under the "wipe" section this will wipe EVERYTHING so make sure you have the latest twrp then on your computer save a rom. Wipe the phone via twrp and then plug the phone it and wait for either Adb sideload or mtp. Personally I feel that mtp is the best just because you can move anything to your phone. Then just move the rom you want to the root of the sdcard (Every folder will be gone). Then flash it and hope that fixes it but if it dosent you may need to use the lg flash tool (windows) and flash the zv4 files. This will make you back on zv4 meaning restump root reflash twrp. The whole nine yards, just try the twrp thing first and if that dosen't work then do the flash tool. I am not responsible if you listen to me and your device breaks
bucketachicken said:
I'm using an LS990 that I've had since about when they came out. When Stumproot came out I rooted it, and I had installed the original TWRP Bump when that came out, but I've been running the rom it came with (ZV4 I believe, though I cannot check). Nothing had been unusual until today, when I put the phone in my pocket after using it for normal daily stuff, then when I later took it out it seemed to be in TWRP. I had almost never even booted into it on the G3 other than a very few times when I first installed it (I had been waiting for a CM12 that was stable enough for my liking).
No matter what I do, it seems to be stuck in recovery. I've updated to the latest TWRP (2.8.4.0) and that seemed to take just fine. However, when I try flashing a rom, it just flashes like normal, log says it's great, then....reboot takes me back into recovery. I tried the ZV4 base at first, then the ZV6 base, both with and without wiping all the appropriate partitions, but nothing seems to change. I am getting ready to try non-stock roms, but I thought I'd ask here first to see if anyone has any ideas? Any help much appreciated!
(not worried about my data, I had daily TB backups running which uploaded to Dropbox, so it's all saved, willing to wipe anything and everything)
Click to expand...
Click to collapse
Have you tried this?
http://forum.xda-developers.com/lg-...trying-ota-t2907508/post56061720#post56061720
Thanks, I did get it working. I have no idea how, but my data was all still there, despite wiping several times....but the recovery fix is what worked. I also got that lg flash tool setup so hopefully that will be helpful if I run into future problems. I honestly think after all that mess I may try the CM12 roms now, even if they still have some daily bugs, cause I was almost sad to see it boot back up into the LG stock rom...
Thanks again!
I honestly think after all that mess I may try the CM12 roms now, even if they still have some daily bugs, cause I was almost sad to see it boot back up into the LG stock rom...
Thanks again![/QUOTE]
Here is a cm12 rom that is almost perfic: http://forum.xda-developers.com/sprint-lg-g3/orig-development/cyanogenmod-12-beta-ls990-t2958197
It's the one I use everyday and I have seen almost no bugs