I flashed the Netarchy kernal, and everything was fine. However, whenever I reboot the phone, the sd card often doesn't mount. It's very frustrating!
Sometimes it does though. What else can I tell you about the phone (it's brand new )?
it happened to me yestersay when i flashed netarchy kernel, what i did is wiped everything and reflashed rom and kernel and everything works fine now
Heres what i did:
Take out battery,hold power button for 20 seconds. Then put battery in and power on! Had same issue when flashing trinity kernal
Sent from my Nexus S using XDA Premium App
jark99 said:
Heres what i did:
Take out battery,hold power button for 20 seconds. Then put battery in and power on! Had same issue when flashing trinity kernal
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Sadly, didn't work.
Somehow I had gotten it to be recognized, and did the battery thing, and alas, broke it again!
I don't want to have to reflash and reformat, although I suppose if I can get the sdcard to read for another boot, I can do a complete back-up?
cptsmidge said:
Sadly, didn't work.
Somehow I had gotten it to be recognized, and did the battery thing, and alas, broke it again!
I don't want to have to reflash and reformat, although I suppose if I can get the sdcard to read for another boot, I can do a complete back-up?
Click to expand...
Click to collapse
Have you tried flashing different kernals?
Sent from my Nexus S using XDA Premium App
I had similar problems after flashing Netarchy kernal, I mounted and unmounted both /system and /data and it fixed the issue.
This happens when you flash the kernel and then reboot from recovery.
I don't know why this is.
Flash the kernel, then power off. Then turn it on. Voila, SD card.
jonnythan said:
This happens when you flash the kernel and then reboot from recovery.
I don't know why this is.
Flash the kernel, then power off. Then turn it on. Voila, SD card.
Click to expand...
Click to collapse
not true. i always flash and reboot from recovery. 2-10 times a day, every day.
simms22 said:
not true. i always flash and reboot from recovery. 2-10 times a day, every day.
Click to expand...
Click to collapse
You flash netarchy kernels 10 times a day every day?
Regardless, if you don't have the disappearing SD problem it's probably because of your ROM or something. If it doesn't happen to you the thread doesn't concern you anyway.
The fix is to shut down and power up - not reboot - after flashing the kernel.
jonnythan said:
You flash netarchy kernels 10 times a day every day?
Click to expand...
Click to collapse
no, he is trinity tester
Sent from my Nexus S using XDA Premium App
I have just recently begun modding my G2x. I can install ROMs without any problems but I've since been interested in flashing a custom kernel. Information is sort of everywhere and what I do manage to find I am worried about it being out-of-date. Anyway, I flashed cm7.1 (the stable release) and it worked fine until it started fc-ing everything google related (something to do with sync?). I decided to try flashing kernels (wiping caches as instructed) and could never get one to work. I've since flashed the latest cm nightly (201 I think) and tried trinity with it. Still nothing. I've since read that I should let the phone sit for 10-20 minutes but after about 20 minutes it is just a black screen and nothing ever happens. It does get really hot however. Anyway I have tried flashing kernels multiple times and nothing has ever worked, same story every time. Any way somebody could tell me what I'm doing wrong? Tell me what's compatible (as maybe sorta stable) with the ROMs I'm using? HAHA and if it's not asking too much...maybe some links too? Sorry, just very new to this and very eager to learn. I just have a bit of trouble figuring out what's supposed to be compatible and where to find it. THANKS!
Start over fresh, wipe data x 2, wipe system x 2, wipe cache, wipe dalvik cache, flash cm7 nightly, dont reboot yet, wipe cache ONLY, wipe dalvik cache ONLY, flash kernel try faux123 (make sure kernel is for cm7) latest or morfic latest, reboot, enjoy ....
NVIDIA NEVER AGAIN!
fcisco13 said:
Start over fresh, wipe data x 2, wipe system x 2, wipe cache, wipe dalvik cache, flash cm7 nightly, dont reboot yet, wipe cache ONLY, wipe dalvik cache ONLY, flash kernel try faux123 (make sure kernel is for cm7) latest or morfic latest, reboot, enjoy ....
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Thanks will give it a shot in the morning. Too much of a headache all day. Back in a useable state and I want to keep it that way for a bit haha. Will post results.
I still haven't tried to flash a new kernel... that is coming in a bit. I do have a question though... I'm interested in getting my phone in the cleanest state possible before doing anything further. I basically want my external sd cleaned up (I want to just reformat it) before flashing a rom again. What files/directories are absolutely essential to keep? As I said, I want to just wipe it clean but I'm not sure I can do that.
Sent from my LG-P999 using XDA App
So just to be thorough I can safely remove the cwm directory as well? Just delete it all put my rom and kernel zips back and I'm good?
Sent from my LG-P999 using XDA App
Make sure you flashed recovery through nvflash
NVIDIA NEVER AGAIN!
Tried to just flash 0.4.7 and it did the same thing as before. Waited 20 minutes before taking out the battery then tried to boot it again. Waited 20 more minutes and all it ever did both times was get hot. Same results as before.
Sent from my LG-P999 using XDA App
OK that's what I was missing. Needed to be running SV. Anyway it's working now just fine. Muuuch appreciated.
Sent from my LG-P999 using XDA App
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
At this point, i would suggest to do a full wipe (clear data/factory reset, caches and also format system under storage and mounts). Then flash your flavor of CM7 and while still in CWM, flash the kernel of your choice, DON'T REBOOT, but clear cache/dalvik. Reboot, let it sit for a while and you should be good.
Sent from my LG-P999 using xda premium
Luriden said:
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Click to expand...
Click to collapse
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after that you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Instaling custom kernel instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
ratza66 said:
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Click to expand...
Click to collapse
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Make sure you downloaded his CM7 version and not Stock kernel.
Luriden said:
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Click to expand...
Click to collapse
You welcome, I've added info on how to install custom kernel too
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Luriden said:
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Click to expand...
Click to collapse
You can't install custom kernel on nightly release. Use RC 7.2 and yes do the rom recovery and back it up so the next time you can just restore to any rom that works on your phone.
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Luriden said:
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Click to expand...
Click to collapse
I Think you are missing a one step, Wipe Dalvik. Ok let start from the begining,
First restore your phone to stock, let it boot. Root your phone and install CWM. Install CM7.2 RC rom and let it boot. Go back to the CWM and follow this instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
all these steps are important. I was using CM 7.2 RC with Faux's kernel without any problem and it worked flawlessly
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Luriden said:
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Click to expand...
Click to collapse
Follow this guy on YT, you will find everything there
http://www.youtube.com/watch?v=fxMnnarHaOU
Installing CM7 tutorial
http://www.youtube.com/watch?src_vi...id=annotation_334516&feature=iv&v=Cy9on64jAZs
This one is even better
http://www.youtube.com/watch?v=vUaWXM8GwUI
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Luriden said:
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Click to expand...
Click to collapse
No chance. Nothing will be left over when you wipe your phone. Your SD card is only accessed when you tell CWM to do so. Take your phone back to stock. Do it again this time try either a froyo rom or ICS rom. Then go back wipe everything and install CM7. Sometimes you have to take the long way. after flashing my phone a bazzilion time I learned this the hard way when I couldnt load EB ICS anymore. Had to run GB to get to ICS. Try it in reverse or from a step below and it should go through fine. IF it doesn't, you might have to use ICS instead, which may be stuttery, but works damn well.
DupleX01 said:
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
Click to expand...
Click to collapse
I'm wondering why he still has the issue. YOU CLEAN CACHE BEFORE FLASHING KERNEL/ROM UPDATES!!!
Sent from my LG-P999 using xda premium
For God sake, just flash a random ROM to get access to inside your phone.
1. DIAG your phone OFFLINE with v21e baseband (phone will automatically restart)
2. Let it stay for 5mins after that
3. Use your phone for 15mins
4. Root using 1Click
5. Install CWM
6. Install your ideal ROM + GAPPS (if needed) via CWM
7. Reboot
8. Go outside your living room and watch TV for at least 15mins
9. Reboot your phone into CWM and flash your ideal kernel
10. Enjoy!!!
You better know which ROM/kernel to choose from. Period.
How to upgrade/downgrade your baseband? Do some search, please!
Sent from my LG-P999 using xda premium
I'll do a flash of Froyo or ICS and possibly some baseband research tomorrow. Considering my luck getting a simple rom flash to work, I don't feel too comfortable dealing with the baseband.
A friend was brave enough (somehow) to let me root and install CM7 on his phone, he has the same phone as mine. I got CM7 7.2 RC and Faux's DM UV working like a dream on my first try. Tried it on my phone after recovering it, same problem. So it's a problem that exists deeper on my phone, not with my methods.
The NAND restores for GB and Froyo give me MD5 checksum errors, and the stock zipped rom of GB gives me an installation failed error, so I'm thinking a zipped Froyo rom won't work either, but it might be worth a shot.
Tried Weapon and MIUI too. No go. If I don't get stuck at the blue LG logo, then I'm stuck in a loop between the two LG logos or stuck at a flashing black screen. 8/10 times though it's the blue LG, I think the other errors may have actually been me forgetting to wipe my cache when I was flustered.
I'll try ICS, and hopefully won't get to a point where I have problems installing things I used to be able to, since that seems to be the pattern. After that I finally give up.
I FIGURED IT OUT! Well, sort of. For the hell of it, I downloaded CM7 7.1.0.1 through Rom Manager and it installed fine. It downloaded it to my internal SD, so I hooked it up to my PC to copy the 7.2.0 RC1 to my internal SD and tried installing. No go.
So I went on my phone's web browser and redownloaded 7.2.0 RC1 that way directly to the phone. It works. So somehow, roms I copy from my PC to the phone appear to not work, yet apps and kernels still do. I'm running CM7 7.2.0 RC1, downloaded through my phone's web browser, with Faux's DS UV kernel, copied from my computer. After four days, I finally found a workaround, so I'll stick to it. Whatever works, I guess. I can try reinstalling my USB drivers, but I can probably get by with a combination of the phone's web browser and ES File Manager w/ LAN if need be.
I've been stuck on this all day. No idea what to do and it would be awesome if someone could help me out here.
Ok so i was running eagles blood ics and everything was working fine. I decided to check out some gingerbread roms so i backed up my eg ics rom. I wiped, cleared dalvik and battery, and formated system. Then i flashed the eg cm7 rom with harsh kernel. I've flashed roms and kernels many times before so i'm pretty sure that i didnt do anything wrong (atleast to my knowledge)
When i was done flashing everything i rebooted my phone and it was the white LG logo that came up, and then right after it was the blue LG logo and it sent me back to clockwork recovery. I attempted to wipe all and reflash again and it then sent me to recovery again. I tried restoring my backup and tried rebooting and it sent me to recovery again.
I dont know what to do at this point, anyone kind enough to let me know what may have gone wrong? it would be greatly appreciated.
jonslaught said:
I've been stuck on this all day. No idea what to do and it would be awesome if someone could help me out here.
Ok so i was running eagles blood ics and everything was working fine. I decided to check out some gingerbread roms so i backed up my eg ics rom. I wiped, cleared dalvik and battery, and formated system. Then i flashed the eg cm7 rom with harsh kernel. I've flashed roms and kernels many times before so i'm pretty sure that i didnt do anything wrong (atleast to my knowledge)
When i was done flashing everything i rebooted my phone and it was the white LG logo that came up, and then right after it was the blue LG logo and it sent me back to clockwork recovery. I attempted to wipe all and reflash again and it then sent me to recovery again. I tried restoring my backup and tried rebooting and it sent me to recovery again.
I dont know what to do at this point, anyone kind enough to let me know what may have gone wrong? it would be greatly appreciated.
Click to expand...
Click to collapse
You flashed a cm7 rom with harsh kernel? That's your problem. Harsh's kernels are ICS only. Try flashing just the rom, without the Harsh kernel
Mr. Apocalypse said:
You flashed a cm7 rom with harsh kernel? That's your problem. Harsh's kernels are ICS only. Try flashing just the rom, without the Harsh kernel
Click to expand...
Click to collapse
I've wiped everything multiple times and flashed just the eg rom on its own and it still sends me back to recovery. x.x
i'm using g2x nullifier to see if after doing that, then flashing any rom will make it work.
Nothing has worked at this point. Anyone have any other ideas? X.x
Sent from my T-Mobile G2 using xda premium
jonslaught said:
Nothing has worked at this point. Anyone have any other ideas? X.x
Sent from my T-Mobile G2 using xda premium
Click to expand...
Click to collapse
I would a give a shot of this tool:
http://forum.xda-developers.com/showthread.php?t=1590523
It will reorganize all your partitions.
Sent from my LG-P999 using xda premium
jonslaught said:
Nothing has worked at this point. Anyone have any other ideas? X.x
Sent from my T-Mobile G2 using xda premium
Click to expand...
Click to collapse
Try this it should bring your phone back to stock, you will lose root and CWM. Good luck.
http://forum.xda-developers.com/showthread.php?t=1248644
ratza66 said:
Try this it should bring your phone back to stock, you will lose root and CWM. Good luck.
http://forum.xda-developers.com/showthread.php?t=1248644
Click to expand...
Click to collapse
was looking around for some tool like this and couldn't find it x.x
I used it and presto! my g2x is alive and kicking again, thanks alot man
And thanks to everyone else that bothered posting, really helps alot
Recently, my battery levels have gotten stuck at 100%. At the time that this happened, I was using an older version of owain ics so I decided to update to owain domination ics rom. It was fine after installing and everything but once I turned off the phone, my battery levels would get stuck at 100% once rebooted. When I installed this rom, I made sure to wipe data, cache, factory wipe and dalvik wipe and all that stuff. So I decided to use a different rom and I used eagles blood 4.0.4 and I get the same exact problem. Same with Hell fire sandwich 1.8. I have searched this problem of battery percentage getting stuck at 100% before but all the solutions tried (wipe battery stats and calibration) did not work for me. How would I fix this problem of battery levels getting stuck at 100% after reboot?
Sent from my LG-P999 using Tapatalk 2
fursquare said:
Recently, my battery levels have gotten stuck at 100%. At the time that this happened, I was using an older version of owain ics so I decided to update to owain domination ics rom. It was fine after installing and everything but once I turned off the phone, my battery levels would get stuck at 100% once rebooted. When I installed this rom, I made sure to wipe data, cache, factory wipe and dalvik wipe and all that stuff. So I decided to use a different rom and I used eagles blood 4.0.4 and I get the same exact problem. Same with Hell fire sandwich 1.8. I have searched this problem of battery percentage getting stuck at 100% before but all the solutions tried (wipe battery stats and calibration) did not work for me. How would I fix this problem of battery levels getting stuck at 100% after reboot?
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
I know you wiped but try again cache,davlik,batt stats and fix permissions then reboot
Sent from my LG-G2x using Tapatalk 2
Hey thanks for your reply
Unfortunately, it didn't work and the first reboot gave me a 100% battery percentage. I also noticed that when I switched wifi on using owain domination ics rom, my phone went back to that spinning circle bpotloading screen and then it turned on Wi-Fi.
fursquare said:
Hey thanks for your reply
Unfortunately, it didn't work and the first reboot gave me a 100% battery percentage. I also noticed that when I switched wifi on using owain domination ics rom, my phone went back to that spinning circle bpotloading screen and then it turned on Wi-Fi.
Click to expand...
Click to collapse
Which kernel have you been using? Perhaps try another one. Make sure to wipe cache and dalvik first then fix permissions afterwards. As for the wifi reboot thing, that is just a bug in owains rom right now. In sure it'll be fixed soon.
If you're always using airplane mode, that could be why
pandalogical said:
If you're always using airplane mode, that could be why
Click to expand...
Click to collapse
Ohhhh Mann. U are a genius thank you so much. What's the explanation behind this tho
Sent from my LG-P999 using Tapatalk 2