So I turned off my phone for the night, just to wake up in the morning, turn it back on and it hung on bootscreen. The phone restarted perfectly a few times but for some reason I keep having problems with this ROM. I'm using the compiled Clockwordmod recovery v.3.1.0.1 but I cant get this to work perfectly for a week without problems. Anything I can do to fix it? (Had to restore a previous backup.)
you need to have S OFF to use this kind of rom.
also make sure you do a full wipe including the battery stats
My phone is s-off but thanks for telling me the tip.
TheUndertaker21 said:
also make sure you do a full wipe including the battery stats
Click to expand...
Click to collapse
Randomly wiping battery stats probably isn't a good idea...
OP, really not sure what the issue could be. I'm not very familiar with the ROM and don't know of any known issues.
i have this on my g2 and I have no problems. have you tried reflashing?
This has been happening to me occasionally but mostly when trying to boot into recovery post CWM update.
frankth3frizz said:
i have this on my g2 and I have no problems. have you tried reflashing?
Click to expand...
Click to collapse
Nah, just gave up on it and moved to CM7 nightly.
Related
God do I hate technology sometimes.
Phone was working perfectly, ages ago, I had updated it to JF 1.5, with apps2SD, and everything is working perfectly until today, I restart my phone (not the first time I have done this since last updating my phone), and for some reason it cant go beyond the android flashing screen. Just keeps going.
WTF do I do? I do not want to have to reflash my phone causing me to have to reinstall all my apps, etc. Just too much hassle, I hope it doesnt come to that.
Does anyone have any ideas?
I have tried removing the battery and putting it back, no difference. Maybe I didnt do it for long enough.
Any advice or help would be much appreciated.
wel I thought I may as well reflash with JF 1.5, and have done so, but the phone STILL won't go past the flashing android screen.
Dunno what to do now, I had thought this would definately do the trick.
Any help would be much appreciated.
Use the search bttom.... and WIPE the phone, Wipe the phone and problem solve...
i have almost same problem
except mine goes past android screen then screen goes blank but stays lit up
Don't wipe your phone. Try this first.
Krazyone said:
Figured i would update this with the knowledge i have gained. Erase the EXT2 / 3 partition then wipe. Load the ROM again and reboot. This should let it pass the boot loop. I had the problem this morning with Drizzy's Hero build and now with JAC's I am running tests with.
Click to expand...
Click to collapse
I had the same problem so I did what Krazyone suggested in one of the post. And it solved my problem. It's something to do with your EXT partition be corrupted or something.
EDIT: You will have to either reload your apps or restore them from your backup.
Same problem here & tried as you suggested...
BeenAndroidized said:
Don't wipe your phone. Try this first.
I had the same problem so I did what Krazyone suggested in one of the post. And it solved my problem. It's something to do with your EXT partition be corrupted or something.
EDIT: You will have to either reload your apps or restore them from your backup.
Click to expand...
Click to collapse
I tried that, but phone still wouldn't boot past the android screen. So, will wipe & start anew.
I've been flashing this thing left and right since November (when I got it, teehee). It's been through over 10 Odins and 100 custom rom/kernel flashes. Even so, Odin has never failed me, nor has the ROMs. But lately, my phone has been freezing non stop, I thought I flashed Syndicate Frozen wrong so I reflashed after wiping and it still froze. I changed the kernel prefixes to 1000/200 instead of 1000/100 to see if it's the 100 scale being stupid, but no dice. I decided to flash MidNIGHT rom to see if that would fix the problem and it worked fine, but now another problem arose. My recovery can't find internal or SD storage anymore...I fixed the problem before by booting the phone up, then going into settings > Privacy > factory reset (although that froze the phone and I had to manually pull the battery) but once I rebooted, all was good...but I Odined back to DI18, automatically updated to EC05, then ran the EXT 4 one click root and it was fine, then I flashed Syndicate 1.1 again, froze on me, restored my working version of midNIGHT rom, now it's giving me that internal storage problem again in recovery.
Is my phone about to die??? I took a picture of the recovery error with my brother's phone.
Those aren't big-deal errors - but I've seen them before when I flashed CWM3 and entered it early (I can't tell you exactly what I did). Just Odin again, flash CWM3, let it convert, and restore the backup. You should be fine. But no, your phone is fine.
And, see the SRF thread. The freeze fix has been posted many times.
Perhaps you should try something other than Syndicate for a while...maybe try an RFS based ROM. Sounds like all your problems start with flashing Syndicate.
Stock EC05 RFS with Genocide 0.5a kernel has been rock solid for me and unbelievable battery life.
I'll give it a try, thanks!
I get those same errors when I use reboot recovery to get to CWM3, but when i use the 3 finger method it works fine.
What method did you use to boot to cwm?
Tortel1210 said:
I get those same errors when I use reboot recovery to get to CWM3, but when i use the 3 finger method it works fine.
What method did you use to boot to cwm?
Click to expand...
Click to collapse
It was Quick Boot app.
Overstew said:
It was Quick Boot app.
Click to expand...
Click to collapse
There's your issue.
k0nane said:
There's your issue.
Click to expand...
Click to collapse
Why would that be the issue? It makes that app obsolete then.
Overstew said:
Why would that be the issue? It makes that app obsolete then.
Click to expand...
Click to collapse
Quick boot is a hard reset. Cause of this it causes data corruption. Use the reboot option built into the rom.
If you wanna reboot into recovery after hitting the reboot 3 finger death grip. It will reboot into recovery
Sent from my SPH-D700 using Tapatalk
Overstew said:
Why would that be the issue? It makes that app obsolete then.
Click to expand...
Click to collapse
MysteryEmotionz said:
Quick boot is a hard reset. Cause of this it causes data corruption. Use the reboot option built into the rom.
If you wanna reboot into recovery after hitting the reboot 3 finger death grip. It will reboot into recovery
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Not only that, but something just doesn't set right when you do it - I can't tell you exactly what, but that's definitely the cause right there.
Had both of these same issues as well on SFR 1.1 and also thought my phone was in trouble. Quickboot caused problems in CWM3 and data corruptions, so had to wipe and reflash. Then, like a number of others, I started having the freezing problems on SFR. Unfortunately, hadn't made it through all the pages of issues in the thread (and freezing issue wasn't yet noted in 2nd post when I downloaded the rom), so ended having to do several battery pulls, which caused more data corruption that required wiping and formatting sd card. Since the posted fix is to flash a kernel that is said to break the camcorder, which I use, I decided to flash back to midnight and all is working again.
I don't want this post to be seen as me knocking SFR. The team at ACS does great work and I'm sure the kernel works for most users. Once the freezing issue is resolved, I'll probably try SFR again, because I like their roms. Just wanted to let you know others are having the same issues.
mis3 said:
I don't want this post to be seen as me knocking SFR. The team at ACS does great work and I'm sure the kernel works for most users. Once the freezing issue is resolved, I'll probably try SFR again, because I like their roms. Just wanted to let you know others are having the same issues.
Click to expand...
Click to collapse
It is resolved. Search the thread. Use the posted kernel.
k0nane said:
It is resolved. Search the thread. Use the posted kernel.
Click to expand...
Click to collapse
I'd totally use that fix if my camera worked with it. :S
any kind of quick reset (quickboot or pulling battery with power on) is bad news on a non-journaled ROM.
Overstew said:
I'd totally use that fix if my camera worked with it. :S
Click to expand...
Click to collapse
Try the camera APK from EB13. The camera works, too - only the camcorder doesn't.
k0nane said:
Try the camera APK from EB13. The camera works, too - only the camcorder doesn't.
Click to expand...
Click to collapse
No camcorder is a deal breaker for me (have a 6 year old that loves home movies). Hoping for a new kernel soon.
Sent from my SPH-D700 using XDA App
mis3 said:
No camcorder is a deal breaker for me (have a 6 year old that loves home movies). Hoping for a new kernel soon.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Try the APK from EB13 before you say that.
I thought everyone knew not to use quickboot that's why the roms have reboot in the power options but I'm scared to even use that and never have.
Sent from my SPH-D700 using XDA App
jbadboy2007 said:
I thought everyone knew not to use quickboot that's why the roms have reboot in the power options but I'm scared to even use that and never have.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
midNIGHT rom came with Quickboot.apk, so I assumed it's okay. I'll ditch it right away, though.
not meaning to hijack the thread butttt
is adb reboot acceptable to use on a non journal rom?
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
sorryihaveaids said:
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
Click to expand...
Click to collapse
I've actually been getting random freezes and reboots in TWRP myself, in the last 2 weeks or so, since I've gone flash-crazy. Have you been flashing a lot?
dibblebill said:
I've actually been getting random freezes and reboots in TWRP myself, in the last 2 weeks or so, since I've gone flash-crazy. Have you been flashing a lot?
Click to expand...
Click to collapse
I wouldn't say flash-crazy, but i've tried two different roms in the past two days. It's not really freezing either. It will just start to restore, make it half way through, and reboot. My rom will be restored but none of my data.
sorryihaveaids said:
TWRP 2.5.0.0 reboots my device while performing a restore. It usually happens during the DATA phase. I've tried two different restores and the same thing happens. Thanks
If you need more detail, i'll do my best to provide.
Click to expand...
Click to collapse
Yep, seems to be happening a lot. One suggestion was to revert to 2.4 or even 2.3.3.0. I tried that, and thought the problem was solved, but then it happened again, so I figured what the hell, I'll go back to 2.5.
You're right, it always happens during the data restore, but so far the second attempt at restoring always succeeds, so it's more annoying than anything. I can't recall it ever happening on my phone, though, so I wonder if it's a device issue. Also my phone is running JB 4.1.2 and my N10 is on 4.2.2.
Sent from my Nexus 10 using Tapatalk HD
Ive noticed this problem as well. Hopefully it will be fixed in later releases.
brGabriel said:
Ive noticed this problem as well. Hopefully it will be fixed in later releases.
Click to expand...
Click to collapse
So yesterday I went to flash a new ROM and TWRP froze immediately after doing a Factory Reset Wipe. Nexus kept bootlooping and then getting stuck on the TEAMWIN screen. Was able to get into the bootloader and flash the stock image and unroot through the Nexus Toolkit. I lost all my data though. So my question is, if you can get to bootloader mode and the toolkit recognizes it in bootloader mode, can you recover data without having to do what I did and wipe the device? For future reference sake. God I need to get better about backing up my data on my PC.
Anyone found the solution to this? I am not able to restore my data ( During the resotre in TWRP it goes blackscreen and then just reboots. I've triel like 10 times already..
ky3bmu4 said:
Anyone found the solution to this? I am not able to restore my data ( During the resotre in TWRP it goes blackscreen and then just reboots. I've triel like 10 times already..
Click to expand...
Click to collapse
I had the same issue. Its most likely a corrupt backup and can't be solved. But if you've successfully restored that backup before try reflashing the recovery. Just a tip that somebody else gave me. Use philz cwm touch recovery. It has no issues and more reliable then other recoveries.
Sent from my Nexus 10 using xda app-developers app
abdel12345 said:
I had the same issue. Its most likely a corrupt backup and can't be solved. But if you've successfully restored that backup before try reflashing the recovery. Just a tip that somebody else gave me. Use philz cwm touch recovery. It has no issues and more reliable then other recoveries.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Yes, i'm thinking the same. Maybe it also because the backup was huge (maybe like 4 gb).
But I am not really sure if it is corrupted because the system restores fine and data do not, but it fails in different places, i.e. it may reboot in 30 seconds and may reboot in 2 minutes...
Hi, my phone acted weird today, been running custom room for over couple months without any problem, but then when i resart my phone today it got to the bootload screen and stuck there ever seen. I can able to go into custom recover and did a full wipe but nothing change, could anyone help me out? I have loki also. Using S4 ATT version.
Try wiping cache in your recovery
i did that, always do that after install a new rom, don't know why my phone is soft bricked now...
akahimaro said:
i did that, always do that after install a new rom, don't know why my phone is soft bricked now...
Click to expand...
Click to collapse
if you've done a full wipe and tried either re-flashing your rom or restoring a nandroid and neither was successful, you may need to consider going back to stock via odin and starting over.
i've never seen a phone run on the same rom and kernel settings for months and then just shut down and softbrick without something having been changed recently.
xBeerdroiDx said:
if you've done a full wipe and tried either re-flashing your rom or restoring a nandroid and neither was successful, you may need to consider going back to stock via odin and starting over.
i've never seen a phone run on the same rom and kernel settings for months and then just shut down and softbrick without something having been changed recently.
Click to expand...
Click to collapse
yes, i'm doing that right now, thanks for the tips, i had that happen to my s2 before. Really weird...
Before ODIN'ing back to MDL/MDB...
akahimaro said:
yes, i'm doing that right now, thanks for the tips, i had that happen to my s2 before. Really weird...
Click to expand...
Click to collapse
What recovery image are you running? You are not the only one that had this problem. I am trying to piece this together.
can anyone help me i have a g2 801 t-mobile version and flashed the cloudyflex rom and noticed i didnt have data working so i went to twrp and wiped everything and restored my old stock rom but notice nothing was working no wifi no notification bar and it keeps randomly rebooting and it cant be turned off i have flashed several backups i had stored and none of them work
1stloc said:
can anyone help me i have a g2 801 t-mobile version and flashed the cloudyflex rom and noticed i didnt have data working so i went to twrp and wiped everything and restored my old stock rom but notice nothing was working no wifi no notification bar and it keeps randomly rebooting and it cant be turned off i have flashed several backups i had stored and none of them work
Click to expand...
Click to collapse
I would suggest you to make a clean install of the stock rom!
That should fix the issue!
zacharias99 said:
I would suggest you to make a clean install of the stock rom!
That should fix the issue!
Click to expand...
Click to collapse
I tried and nothing works i even went back to stock using this thread http://forum.xda-developers.com/showthread.php?t=2432476
What recovery were you using and do you have any backups from then or is everything gone?
sp33dsk8 said:
What recovery were you using and do you have any backups from then or is everything gone?
Click to expand...
Click to collapse
the latest twrp....i have backups on my computer but cant transfer them because it keeps rebooting and since i went back to stock i cant root as it does not let cuz of the constant reboot
1stloc said:
the latest twrp....i have backups on my computer but cant transfer them because it keeps rebooting and since i went back to stock i cant root as it does not let cuz of the constant reboot
Click to expand...
Click to collapse
I'd try and get with this guy
"As usual, I'm on #lg-g2 in Freenode as IOMonster, if I'm around I'll be happy to help wherever I can."
http://forum.xda-developers.com/showthread.php?t=2432476
I had the exact same problem! Phone would boot into the rom, or stock and freeze after about a minute and reboot itself constantly. I had the updated version of TWRP and was flashing the new 1/30 Mahdi build and it happened after I did that! I tried flashing stock roms, aosp roms, and eventually did a Flash back to stock method, which non of them worked. I took the phone into T-Mobile and did a warranty replacement, got a new one overnight. Not sure if it is related to Mahdi or not, but it happened after a supposed successful flash.
I tried my TWRP Backups too, and those still restarted on me. Nothing helped me..Tried wiping the sd card, format the whole card, wipe cache, fix perm..
Hopefully you have a warranty or figure it out!
Good luck.
ZetterbergDatsyuk said:
I had the exact same problem! Phone would boot into the rom, or stock and freeze after about a minute and reboot itself constantly. I had the updated version of TWRP and was flashing the new 1/30 Mahdi build and it happened after I did that! I tried flashing stock roms, aosp roms, and eventually did a Flash back to stock method, which non of them worked. I took the phone into T-Mobile and did a warranty replacement, got a new one overnight. Not sure if it is related to Mahdi or not, but it happened after a supposed successful flash.
I tried my TWRP Backups too, and those still restarted on me. Nothing helped me..Tried wiping the sd card, format the whole card, wipe cache, fix perm..
Hopefully you have a warranty or figure it out!
Good luck.
Click to expand...
Click to collapse
Dam no I do not have warranty and I'm on a prepaid plan and bought the phone from swappa sucks the phone is a waste now
Sent from my Nexus 5 using Tapatalk
ZetterbergDatsyuk said:
I had the exact same problem! Phone would boot into the rom, or stock and freeze after about a minute and reboot itself constantly. I had the updated version of TWRP and was flashing the new 1/30 Mahdi build and it happened after I did that! I tried flashing stock roms, aosp roms, and eventually did a Flash back to stock method, which non of them worked. I took the phone into T-Mobile and did a warranty replacement, got a new one overnight. Not sure if it is related to Mahdi or not, but it happened after a supposed successful flash.
I tried my TWRP Backups too, and those still restarted on me. Nothing helped me..Tried wiping the sd card, format the whole card, wipe cache, fix perm..
Hopefully you have a warranty or figure it out!
Good luck.
Click to expand...
Click to collapse
Hey can you tell me how t-mobile insurance works i use to be with sprint and if they couldnt fix it they would send me a new at no cost...my friend has t-mobile insurance can he put his sim card in and they have a look at it and if they do will he be charged anything?
OK learn about adb sideload so you can sibeload a ROM or have you us LG G2 to go back to stock and start all over?
Sent from my LG-LS980 using XDA Premium 4 mobile app
Nicamarcel1 said:
OK learn about adb sideload so you can sibeload a ROM or have you us LG G2 to go back to stock and start all over?
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
ok read my other post as i have gone back to stock and it has not worked
I had the same problem. If you looked for other threads, you would find fix.
Problem is in CPU voltage.
http://forum.xda-developers.com/showthread.php?t=2612243
Wysłane za pomocą LG G2 przez TWRP
1stloc said:
Dam no I do not have warranty and I'm on a prepaid plan and bought the phone from swappa sucks the phone is a waste now
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Should still be under warranty with LG. I'd call their support and give them the serial number to see if it still covered.
As far as the LG Warranty goes, all I did is walk into the store and show them the issue at hand, and he put in a order for a new one sent overnight to me. They send you a prepaid label and a box to ship your old one back(phone only). The new phone I have appears to be brand new, with all the crazy plastic protection on it... not sure if it is a refurbish or not. Didn't cost me a penny, as I have the JUMP w/ protection plan.