Related
My first rom is LGP920-V08i-APR25-2011. I upgraded it with V10b_00.kdz. However the O3D turned off after booting. If I connect with USB cable, it is working well. but battery level is zero. if I disconnect the cable, it turned off. It is impossible to charge. The level is zero and blinking. So I upgrade it with V10d with rom manager. However the result is same. I didn't back up my phone at first time Is there any solution?? Help me...
Did you try removing the battery for a while and then putting it back in?
Take out the battery and clean the contacts carefully by scraping with a penknife or similar. Do this to the phone connectors too. Sounds like bad/dirty contacts to me.
Sent from my LG-P920 using XDA App
I have another battery. the result is same. If I work in the ClockworkMod Recovery, the battery works well. This problem is about system....
So, the battery charges when you are in clockwork recovery?
I can work in clockwork recovery without USB cable just with battery. That means lg rom system can not recognize the battery in S/W. actually battery is no problem.
You could try wiping your Dalvik Cache (just to be sure) and wiping your Battery Stats through Clockworkmod, maybe it helps.
I can wiped Dalvik Cache However it is impossible to wipe my Battery Stats through Clockworkmod. The result is same.... Do you have another idea to solve the problem??
Why my O3D can not wipe Battery Stats in the Clockworkmod? If I do this, there is no massage and retune to advanced menu. Every options except Wipe Battery Stats work very well... why?????
Nobody knows how to solve this problem?? Pls help me. Thanks
Are u using the original wall charger? LG charger that is. I have plenty phones that won't charge on computer USB when completely dead or even with aftermarket wall chargers. Also some phones are actually smart enough to tell if u are not using an OEM spec charger.
Sent from my MB860 using XDA App
Thanks for your reply. I tested my battery in my friend's O3D. And it works very well. I
think I have to use another rom/firmware...
I decided to wait Cyanogenmod on O3D. Thanks everyone...
Good luck . Let me know what happens if u try the old rom or did u already.
Sent from my MB860 using XDA App
Im having the same problem...The battery is full but it says 0% and and closes itself after booting if not connected to USB or power source.
anyone found a way to fix this? I'm having the same problem
zweetz32 said:
anyone found a way to fix this? I'm having the same problem
Click to expand...
Click to collapse
Me too!, same problem with a ROM KingMod
I set my phone for Stock & Recovery firm, unrooted. Nothing doing! I give up, nobody knows how to solve this problem. I'm totally frustrated with it.
Ratzenberger said:
I set my phone for Stock & Recovery firm, unrooted. Nothing doing! I give up, nobody knows how to solve this problem. I'm totally frustrated with it.
Click to expand...
Click to collapse
Hey man.... i posted in other topic and i don´t think anybody tried.... try to get the batterystats.bin file with someone who has a normal file. Try to put it in the right directory, it sounds stupid, but perhaps it can work, tell me later!!!
Using Root Explorer: data>system>batterystats.bin see if the file is there and if not, put there a normal one
jhonnyjhonny said:
Hey man.... i posted in other topic and i don´t think anybody tried.... try to get the batterystats.bin file with someone who has a normal file. Try to put it in the right directory, it sounds stupid, but perhaps it can work, tell me later!!!
Using Root Explorer: data>system>batterystats.bin see if the file is there and if not, put there a normal one
Click to expand...
Click to collapse
I tried it today, did not work. I tried also deleting the file, and restart the device, nothing!
I think this problem occurs with some specific versions of this model (not for sale), like mine. I don t believe that I spent $ 600 a paperweight: (
Hello to everyone and respect to all you developers for your hard work!
as you can see i'm noob but i'll try not to be too noobish.
here's the situation.. now, i have hephappy's CM9 bluepill rom installed in my lg p500 and it works just perfect (i mean it,just perfect),
and before that i have flashed custom rom's couple of times with success but once when i tried to boot into emergency mode (vol down+back+power) after that i couldn't get rid of that yellow message every time i restarted or turn on my phone till today.
so, now i'm living with that issue,but it bothers me,i can't understand why yellow emergency screen is showing EVERY time i reboot my mobile.
then i find out that the only way to avoid that is pulling battery out and wait for at least 5 minutes and then switch on (then it's ok - LG logo and blah blah).
but when i try to turn it on for less than 5 mins, emergeny mode will be showing everytime i switched mobile on.
so, i don't have a clue or answer what it could be. i tried to flash stock firmware through KDZ and actually everything seems ok and everything works just fine but that yellow screen still spy on me.
as i said, everything works perfect but when battery is drained or i wanna reboot my mobile i have emergency mode shown,so i must repeat above procedure with pulling out battery for 5 mins everytime.
i hope i didn't complicate this
Try to change RADIO (BASEBAND),maybe it might help you!
Sent from my LG-P500 using xda premium
totalka said:
Hello to everyone and respect to all you developers for your hard work!
as you can see i'm noob but i'll try not to be too noobish.
here's the situation.. now, i have hephappy's CM9 bluepill rom installed in my lg p500 and it works just perfect (i mean it,just perfect),
and before that i have flashed custom rom's couple of times with success but once when i tried to boot into emergency mode (vol down+back+power) after that i couldn't get rid of that yellow message every time i restarted or turn on my phone till today.
so, now i'm living with that issue,but it bothers me,i can't understand why yellow emergency screen is showing EVERY time i reboot my mobile.
then i find out that the only way to avoid that is pulling battery out and wait for at least 5 minutes and then switch on (then it's ok - LG logo and blah blah).
but when i try to turn it on for less than 5 mins, emergeny mode will be showing everytime i switched mobile on.
so, i don't have a clue or answer what it could be. i tried to flash stock firmware through KDZ and actually everything seems ok and everything works just fine but that yellow screen still spy on me.
as i said, everything works perfect but when battery is drained or i wanna reboot my mobile i have emergency mode shown,so i must repeat above procedure with pulling out battery for 5 mins everytime.
i hope i didn't complicate this
Click to expand...
Click to collapse
your not noobish. you post in the right place.
I have like no idea what you are expierencing. have you tried booting to recovery?
-DarkKnight- said:
your not noobish. you post in the right place.
I have like no idea what you are expierencing. have you tried booting to recovery?
Click to expand...
Click to collapse
yes pal. everything i can remember including booting into recovery with clockworkmod, wiping all data,cache,update with kdz,then root,flash new rom...and everytime everything goes like a glowe,everything is stable,with no errors.
i suppose i'm one of the luckiest lg p500 users when it's about good,stable device,which could be overclocked or tweaked without kernel panic,errors, etc (i heard that differences between same devices can vary).
BUT after all that i have that same issue with yellow emergency mode.
finally, i suppose that yellow screen is the price i must pay at the cost of good stability and great performance
did you try flashing gb stock rom by lgmdp?
totalka said:
yes pal. everything i can remember including booting into recovery with clockworkmod, wiping all data,cache,update with kdz,then root,flash new rom...and everytime everything goes like a glowe,everything is stable,with no errors.
i suppose i'm one of the luckiest lg p500 users when it's about good,stable device,which could be overclocked or tweaked without kernel panic,errors, etc (i heard that differences between same devices can vary).
BUT after all that i have that same issue with yellow emergency mode.
finally, i suppose that yellow screen is the price i must pay at the cost of good stability and great performance
Click to expand...
Click to collapse
If you can get into yellow screen your ok
Last resort use kdz just don't take out battery or disconnect and you should be fine
Sent from the My Little Pony Official App
@dhruv:
I heard about lgmdp,but i didn't found myself interested enough to try it
Because i actualy didn't had any issues excep that yellow screen.so you think it could be helpful?
@darkknight:
It is the only way i can avoid yellow screen by pulling out battery for 5 mins.
I know that my prob is unusal but now i have a lot of apps installed linked with link2sd,so i should find some way to safely backup all that stuff and try to do smtg.
Sent from my LG-P500 using xda app-developers app
totalka said:
yes pal. everything i can remember including booting into recovery with clockworkmod, wiping all data,cache,update with kdz,then root,flash new rom...and everytime everything goes like a glowe,everything is stable,with no errors.
i suppose i'm one of the luckiest lg p500 users when it's about good,stable device,which could be overclocked or tweaked without kernel panic,errors, etc (i heard that differences between same devices can vary).
BUT after all that i have that same issue with yellow emergency mode.
finally, i suppose that yellow screen is the price i must pay at the cost of good stability and great performance
Click to expand...
Click to collapse
I didnt get the method of flashing rom.. what you said above!!
You root again after updating from kdz.. you have gone wrong somewhere thats why you
get emergency mode everytime you restart.
I would suggest.. clear all the links.. make a nandroid backup. Dont use kdz as its not
required. Go into recovery.. clean everything (specially boot) and flash any rom and see if the problem persists.
which rom and which recovery maybe you can try and change the recovery. I wont reccomend kdz because i flashed it 10-12 times but after that i bricked my phone 2 times while flashing with kdz.
Here it is..
I had official gingerbread used when i found out that cm9 ics was out.then i have wait for stable cm9 rom,till hephappy's premature version.
So,i decided to flash premature,so here is a short procedure..
I don't have exact rooting/flashing guide link right now but i found it on xda forums for p500.
Downloaded short fuse,adb,etc and root via usb & command prompt..everything was ok,device sucesfully rooted,i got superuser.
Next step i installed rom manager from google play and follow flash instructions from xda including nandroid backup,booting to recovery,wiping data,dalvik,battery,everything that could be wiped..then installed premature,gapps,everything goes just fine.
I have been using premature till bluepill cames out.
just before flashing new rom i decided to hard reset via vol up+home+power, but i accidently entered into emergency mode by pressing vol down+back+power instead and after that yellow showing i have issue with it.
Downloaded then stock ginger rom from xda sites (20g),installed via kdz,everything flows fine,rooted againg with same procedure,flashed bluepill rom too with same procedure and still having that yellow emergency mode issue.
I think i made it much more clear
Sent from my LG-P500 using xda app-developers app
I flashed a Jellybean touchwiz rom for Verizon GS3, and went to reboot and now nothing, zero zip nada. No charging led light, no way to get into recovery and no response.
Anything I can do?
what happens when you do vol up + home+power button?
Absolutely nothing. I tried to get back into the recovery to see if I could restore my backup and nope.
did you try leave it pluged in for 30mins ?
does it vibrate once when you try to turn it on?
No vibrating and no sign of life at all. Even when plugged into my computer, I was going to try the unbrick guide but it listed that I should be able to get into the recovery still.
NickTheMajin said:
No vibrating and no sign of life at all. Even when plugged into my computer, I was going to try the unbrick guide but it listed that I should be able to get into the recovery still.
Click to expand...
Click to collapse
leave it plugged in for a while to make sure its not drained battery
do you have a usb jig?
I don't have a USB jig but this is possibly good news. I removed the battery and SD card and plugged it into my computer and it tried to install drivers (failed but tried) and the led light comes on red.
if your gettin led now you more then likely need to let it charge
It doesn't give me the led with the battery in
Plug it into a wall charger for at least 30 or even better if you can get a battery from someone.
Sent from my sexy white Eclipsed galaxy S3
I think its gone still nothing.
red led means qualcomm download mode. sounds dead to me
Yeah, haha. I saw it and mentally prepared myself for it. Literally just got the phone today so Verizon had no qualms with just sending me a new phone. Guess I'm reactivating my Rezound in the meantime. Thanks for the help guys.
you know
I am surprised. That also happened to me the first time i flashed that very same rom (touchwiz) with twrp . I have done this so many times , i literarily can flash a rom on the way to work .
I was in shock , i still dont know how the heck can i flash a rom and brick .
I plugged mine into windows and i got the device manager driver error from hell . and my phone never came back up again
I stayed away form twrp and touchwiz and i still cant possibly comprehend how a simple rom flash can brick my phone .
Which ROM did you flash?
Sent from my SCH-I535 using xda premium
you could probably send it to get Jtag'ed for around $60 if your warranty is invalid (ie used device)
You just hard bricked it. I did the same thing. Check here - post 5 shows the same symptoms :http://forum.xda-developers.com/showthread.php?t=1770341
And here: http://forum.xda-developers.com/showthread.php?t=1791721
I was pushing a copy of root66 that I hadn't md5'd. Took a JTAG to bring me back (twice) .
Sent from my SCH-I535 using xda app-developers app
So, in the future, md5 checksum absolutely everything since I'm assuming now that that is why this happened? (Since I made doubly sure I was flashing a rom for my phone).
If you still have the file you downloaded, you can check it. That would answer that question. If it checks out fine, then we have to look elsewhere for the problem.
BTW, MobileTechVideos.com can bring you back - based on my experience with them, I highly recommend.
Sent from my SCH-I535 using xda app-developers app
Please share exactly what you did so others can benefit from your unfortunate experience.
What ROM did you flash?
Did you use ODIN or a recovery?
If recovery, which one - CWM or TWRP?
Was there any unusual condition you can think of ... low battery, USB connected to computer or to charger, etc?
Hi, i have been looking for answers on the forum, and i learn new things but not how to fix this or what is causing it.
I have buyed i997 from a reseller. He sayd it doesnt work because it have bootloop, but i thinks that is not too much problem getting it working again, so i started searching for the pc drivers n software, then i find here in the forum the stock rom with and without root, i tested them both with odin and the bootloop stills present. I wipe cache and do a factory reset but it keep bootlooping, then think maybe if i update to latest AT&T rom, but no luck.Sometimes the phone just start and theres no bootloop but its very rare and most of the time when i get to the lock screen or setup manager suddently a gapps or something crash and my phome freezes and reboot. I flashed the carbon-jb-v1.6 and suddently it worked fine, no more bootloop and everything smooth,no crashes etc.. then i installed Facebook app and when i was ttyping a message the phone froze up and then restarts, and the bootloop came again, and im stuck on it, and when i pass it, which is very rare, i start typing info in the startup manager and the phone freezes and reboot.. I wipe/format cache, dalvik, factory reset, formated system and data before and after flashing the carbon rom again and it keeps bootlooping. Somebody have similar problems or know how to fix it?
Thanks
P.d. sorry for my bad english.
jakov.90 said:
Hi, i have been looking for answers on the forum, and i learn new things but not how to fix this or what is causing it.
I have buyed i997 from a reseller. He sayd it doesnt work because it have bootloop, but i thinks that is not too much problem getting it working again, so i started searching for the pc drivers n software, then i find here in the forum the stock rom with and without root, i tested them both with odin and the bootloop stills present. I wipe cache and do a factory reset but it keep bootlooping, then think maybe if i update to latest AT&T rom, but no luck.Sometimes the phone just start and theres no bootloop but its very rare and most of the time when i get to the lock screen or setup manager suddently a gapps or something crash and my phome freezes and reboot. I flashed the carbon-jb-v1.6 and suddently it worked fine, no more bootloop and everything smooth,no crashes etc.. then i installed Facebook app and when i was ttyping a message the phone froze up and then restarts, and the bootloop came again, and im stuck on it, and when i pass it, which is very rare, i start typing info in the startup manager and the phone freezes and reboot.. I wipe/format cache, dalvik, factory reset, formated system and data before and after flashing the carbon rom again and it keeps bootlooping. Somebody have similar problems or know how to fix it?
Thanks
P.d. sorry for my bad english.
Click to expand...
Click to collapse
the most inexpensive solution:
http://forum.xda-developers.com/showthread.php?t=1912599
qkster said:
the most inexpensive solution:
http://forum.xda-developers.com/showthread.php?t=1912599
Click to expand...
Click to collapse
Thanks man, but you think it can be the power button? When i unplug the battery and put it again the phone doesnt turn on or something, and when it boot up when i lock the screen with the power button it works fine. I set the cpu governor to conservative and since yesterday i didnt have any problem, but sometimes the phone reboots when typing, i think its someting with the processor or when the phone have little ram or something.
Thanks.
jakov.90 said:
Thanks man, but you think it can be the power button? When i unplug the battery and put it again the phone doesnt turn on or something, and when it boot up when i lock the screen with the power button it works fine. I set the cpu governor to conservative and since yesterday i didnt have any problem, but sometimes the phone reboots when typing, i think its someting with the processor or when the phone have little ram or something.
Thanks.
Click to expand...
Click to collapse
If you ran the phone on complete stock GB or FROYO and you are getting boot loops, it may be a hardware issue.
One of the few things that will give you boot loop with the samsung logo while using the phone is the power button.
Either way, it's no big deal to open it and clean it up to see if the problem goes away.
qkster said:
If you ran the phone on complete stock GB or FROYO and you are getting boot loops, it may be a hardware issue.
One of the few things that will give you boot loop with the samsung logo while using the phone is the power button.
Either way, it's no big deal to open it and clean it up to see if the problem goes away.
Click to expand...
Click to collapse
Thanks bud, I will try cleaning the button. Also I want to ask, is there something to log everything when the phone start? Or something to test the hardware functionality?
Thank you for your time
post number #112
http://forum.xda-developers.com/showthread.php?t=1437548&page=13
qkster said:
post number #112
http://forum.xda-developers.com/showthread.php?t=1437548&page=13
Click to expand...
Click to collapse
Thank you, the post its the number #122
jakov.90 said:
Thanks bud, I will try cleaning the button. Also I want to ask, is there something to log everything when the phone start? Or something to test the hardware functionality?
Thank you for your time
Click to expand...
Click to collapse
Bootlog Uptime will keep a record of all boots from an Android OS perspective ... It will also track crashes... It won't track events outside of a complete restart (i.e. power button bootloops.. But those are pretty obvious when they occur)
For hardware testing, try Z Device Test... That won't tell you about the buttons though... If your screen turns on without pressing power button or from any other standard event (like receiving a text or a phone call), or the phone restarts by itself, time to get cleaning..
Sent from my SAMSUNG-SGH-I997 using xda premium
Zen Arcade said:
Bootlog Uptime will keep a record of all boots from an Android OS perspective ... It will also track crashes... It won't track events outside of a complete restart (i.e. power button bootloops.. But those are pretty obvious when they occur)
For hardware testing, try Z Device Test... That won't tell you about the buttons though... If your screen turns on without pressing power button or from any other standard event (like receiving a text or a phone call), or the phone restarts by itself, time to get cleaning..
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Hey thanks, that was very useful.. i risky miself to do a stock flrom flashing with pit checking the Nand erase all option in Odin 3.07, and the random reboots are gone :laugh:. Now i have one question, Do i need an special kernel for JB 4.2.2? i plan to flash the Carbon-jb-v1.6 rom but i dont know if i need another kernel
I'm glad to hear you solved your issue.
For JB, use the kernel provided with the rom.
Sent from my SAMSUNG-SGH-I997 using xda premium
I have the cricket model. Sometime last night my phone started rebooting on every ROM and kernel. Nothing I do will get it to stop. It doesn't happen in TWRP and that's it. I thought maybe it was a battery issue as I haven't been able to fully charge it because of this issue but that's not helping either. I've been trying to use the upgrade tool but in this state the computer never even recognizes the phone and I can't even get that far, plus it reboots even when in download mode. I'm about to call cricket and see if they can just send me a new one since I've only had it a week but is there anything I can do? Does anyone have a boot IMG for complete stock 60450 ?!? EDIT: Got the tool to recognize phone and start process but what do ya know phone reboots even deep into download mode. It just always wants to restart to the system for some reason, except for when on twrp. UPDATE:EDIT: Turns out the reason the upgrade app wasn't working is because i didn't have enough space for the update to download on the PC . I didn't realize because the app never stated why it was restarting my phone or disconnecting so I just assumed it was related to why my phone kept restarting on all ROMs. Wow lol I feel so damn stupid for not thinking of this 2 days ago. Its installing now and hopefully this fixes my reboot issues. Thanks to everybody here for helping and answering my 1000 question's on every post. Really appreciate it.
it looks like motherboard is gone. I hope you can return it when you have custom rom installed.
DallasCZ said:
it looks like motherboard is gone. I hope you can return it when you have custom rom installed.
Click to expand...
Click to collapse
I've had the phone for one week lol. Motherboard is gone? Could something be messed up in build prop somewhere? I did try to use a DPI changer app on stock rom once or maybe xposed? I've done a lot of flashing since I got it trying to find the perfect setup. I just noticed that the USB cable it came with is crap so now that I'm using a different one I'm hoping that low discalobrated battery was the issue. Charging it up proper and gonna see what happens after. Also for some strange reason the Flyme OS ROM is the only one that doesent seem to want to restart as often. It still does but it lasts a lot longer before doing so , why idk lol.
turn off the phone, charge it fully and then run the upgrade tool to go back to stock.
Odesláno z mého 6045X pomocí Tapatalk
DallasCZ said:
turn off the phone, charge it fully and then run the upgrade tool to go back to stock.
Odesláno z mého 6045X pomocí Tapatalk
Click to expand...
Click to collapse
I wasnt previously able to corectly charge becauss when i would turn the phone off to charge it wpuld power up instead of gking to the charging acreen. I think the USB cable that came with the phone might have been faulty and I just didn't notice it somehow. Now that I've charged the phone to 50% Flyme is up and running without a reboot, although running quite hot....which could also be the issue. Maybe the metal on the USB tip got toasted. That would explain my reboots in download mode but it doesent explain why the phone never once rebooted on me while in twrp and why it would reboot even while not being charged and had like 30%. Gonna charge it up to 100 and try the tool again.
carnivalrejectq said:
I wasnt previously able to corectly charge becauss when i would turn the phone off to charge it wpuld power up instead of gking to the charging acreen. I think the USB cable that came with the phone might have been faulty and I just didn't notice it somehow. Now that I've charged the phone to 50% Flyme is up and running without a reboot, although running quite hot....which could also be the issue. Maybe the metal on the USB tip got toasted. That would explain my reboots in download mode but it doesent explain why the phone never once rebooted on me while in twrp and why it would reboot even while not being charged and had like 30%. Gonna charge it up to 100 and try the tool again.
Click to expand...
Click to collapse
if you can boot to flyme, and got no reboots in TWRP i suggest you flash from TWRP your previously mad ebackup..if you dont have any, just flash stock kernel or look here in threads, there was a thread and it contains TWRP backup of stock rom..if you find TWRP backup of your STOCK 6045O then flash it from TWRP, and if you dont observe nay reboots, it was due to the kernel. IF it still reboots send it to warranty repair.
DallasCZ said:
if you can boot to flyme, and got no reboots in TWRP i suggest you flash from TWRP your previously mad ebackup..if you dont have any, just flash stock kernel or look here in threads, there was a thread and it contains TWRP backup of stock rom..if you find TWRP backup of your STOCK 6045O then flash it from TWRP, and if you dont observe nay reboots, it was due to the kernel. IF it still reboots send it to warranty repair.
Click to expand...
Click to collapse
Well I'm back on CM now with no reboots. I guess my USB cable just sucked and my battery calibration was off so the battery was showing more than it actually had and probably causing instability. However, I still can't get the tool to work. It just reboots at around 22% exiting me out of download mode. BTW I've searched and scowled almost every thread and I can't find a stock kernel. There's the arde one but I thought that was just his custom kernel for stock. And the twrp back up I definitely can't find. I seen the thread but there was no link.
carnivalrejectq said:
Well I'm back on CM now with no reboots. I guess my USB cable just sucked and my battery calibration was off so the battery was showing more than it actually had and probably causing instability. However, I still can't get the tool to work. It just reboots at around 22% exiting me out of download mode. BTW I've searched and scowled almost every thread and I can't find a stock kernel. There's the arde one but I thought that was just his custom kernel for stock. And the twrp back up I definitely can't find. I seen the thread but there was no link.
Click to expand...
Click to collapse
If it was the USB cable why is mobile upgrade tool rebooting the device at 22%? It makes no sense. It could be the pins on the usb socket on the phone or i dont know.
You should ask someone with the 6045O device to send you the boot.img (aka kernel) of stock 6045O.
DallasCZ said:
If it was the USB cable why is mobile upgrade tool rebooting the device at 22%? It makes no sense. It could be the pins on the usb socket on the phone or i dont know.
You should ask someone with the 6045O device to send you the boot.img (aka kernel) of stock 6045O.
Click to expand...
Click to collapse
Well I first noticed my cable was funky when I loaded up Flyme it kept making an unplug sound and I thought it was just the ROM glitching out but I changed the cable and it stopped. About the tool......I have a Windows tablet that it's only USB connection is one of those mini USB to full adapters and it's a little loose. I have zero problems with it plugging my phone into it for file transfer or for adb, it's all fine there so idk why it would be causing an issue with the tool, last time I tried it k specifically made sure all connections were sturdy and didn't move the whole time and it still rebooted. I noticed somebody in one of the threads said his device did the same thing though and that's why he couldn't use the tool as well......nobody ever replied to him lol
Ahh I spoke to soon. Restored my stock, because that's what I prefer for even at OC it still doesent make the phone nearly as hot as CM ROMs and the restarts came right back even with a decent charged battery. I'm back on CM again though and its not happening. Doesent make much sense because before the restarts were happening across all ROMs. It can't be the kernel in my stock restore as I had used it a bunch of times before with no issues...... Though it is saved on my external SD..... But so is the cm build I'm using. Idk whats going on here. Just wanna return the phone to full stock and call it a day lol. Edit: spoke to soon again lol. There goes CM rebooting, although it took way longer than stock to do so.