Heres my info and problem. Thanks in advance for the help!
ROM: jokersax11's cm9 build with gapps
Kernel: (Faux123' 1.45 GHz OC CM9 kernel)
Metods used to flash the rom:
full battery
cache format
delvik format
fastboot wipe (dah whole shabang)
flashed rom
reboot
flased gapps
erase batt. stats
Problems you are experiencing: Alright so I flashed your rom 2 days ago then when the battery was almost out I plugged it in my computer, naturally. The next morning it was at 95% so I decided that I was going to drain my battery all the way before charging it. The problem is that when I plugged it in the wall, the phone started bootlooping but wouldn't get past the M logo (not actually M logo on my phone but you know..). Then I think it overheated because it started giving the message: modem did not power up (2), starting RSD protocol support, battery is too low to flash. Then I let it cool and now its bootlooping agin..
you should never flash a ROM when battery is below 30%.
I guess there was one other thread where the OP encountered the same problem:
http://forum.xda-developers.com/showthread.php?t=1529720
You can try to see if that works.
Make sure you have the latest recovery. I got stuck in boot loop during my first flash due to old version of CWM. Try ROMRACERS CWM. You can serach through!
Related
Hi People, im using a Custom Rom from Noejm.
Two Days ago, i charged my LG P500 with it turned Off. When i wake up, i turned it on, and the Phone just got Stuck on the LG Logo Screen.
I entered in Custom Recovery and Flashed the Rom again. Installed all the Apps etc etc.
So at the end of the day the Battery was minimal and i turned the phone off again and put it in the Charger.
Today i woke up, turned th phone on, and im Stuck at the LG Logo.
What may be causing this?
do a complete wipe before flashing and frmat sd card after keeping a backup then flash hope vrthythng will be fine than,if u dnt want to wipe ur mmc than just wipe all other option in custom recovery and then flash dont install any application fr sm ours and let it settle down properly
Reflash, Re-Wipe...
If after above it still fails, try to do complete wipe again, and then
flash this from recovery http://forum.xda-developers.com/showpost.php?p=11785758&postcount=557
it will make sure to remove the /system
then reflash your rom
I think i know what happened.
I've installed the last Busybox to xbin. And in that day, that happened.
When i flashed the rom again, i've installed again the last Busybox.
This time i have not installed the last one. Lets see if the problem gets resolved.
A strangem problem happened today.
Yestarday I calibrated my baterry stats and left the battery fully discharge, everything ok this morning, I plugged the phone on USB and updated some apps with 3G.
Then my phone booted and I got stucked on a LG boot logo. Only could enter in recovery mode without battery.
Now if I remove usb cable my phone back to LG boot loop.
I didn´t want to install the rom again because I have a lot of apps installed (my last install rom was on saturday and sunday I installed a lot os apps, and didnt backup them yet).
any ideia?
ROM 6.6.1 + Rome 1.3.1 kernel.
If you install ROM a that doesn't wipe the /data partition on install (Most ROMs, all Optimus roms I have seen so fat), only system apps will get reinstalled.
My phone was running at about 60% battery last night, and working fine. It was in my pocket and it vibrated. I was unable to turn it on or reboot it, even after removing the battery. I tried using the battery from my wife's S2 but still no luck. I tried connecting the power supply but it still wouldn't boot so I left it charging overnight.
This morning it alternately flashed a fully green battery and a fully black battery. If I press and hold the power button it starts the boot process - I get past the Samsung splash screen and see the first "Resurrection Remix" splash screen, but then it reverts to displaying the green battery.
Any ideas for how I can revive the phone??
itm said:
My phone was running at about 60% battery last night, and working fine. It was in my pocket and it vibrated. I was unable to turn it on or reboot it, even after removing the battery. I tried using the battery from my wife's S2 but still no luck. I tried connecting the power supply but it still wouldn't boot so I left it charging overnight.
This morning it alternately flashed a fully green battery and a fully black battery. If I press and hold the power button it starts the boot process - I get past the Samsung splash screen and see the first "Resurrection Remix" splash screen, but then it reverts to displaying the green battery.
Any ideas for how I can revive the phone??
Click to expand...
Click to collapse
Ok We cant say its bricked!! Because its booting up but not coming to homescreen rite? Are u able to get into recovery or download mode?? If ur able o then wipe the data cache and dalvik cache, reinstall the ROM again.. If Recovery doesnt shw up.. Then Use ODIN to flash original fw!! Even if u still couldn get it.. Order a USB JIG from Ebay and try getting into DOWNLOAD MODE!! Even after this its still working means ITS BRICKED !!
Start download mode and the flash a new stock firmware . And your phone isnt bricked .!
This is why I always make a backup.
If you can get into download mode you can fix it, if you can't it's a service centre job. Pretty simple really.
Try cleaning charging port..
Sent from my GT-I9100 using XDA
Uh oh...I managed to get into Recovery mode, did a factory reset and kicked off a re-install of the Resurrection Remix ROM from the external SD and it's hung at 50% (for 10 mins now) - at the "Extracting /system..." stage. I daren't interrupt it.
Any ideas???
Yes stop messing
1: If you dint have to save anything, wipe better to full wipe
Flash a stock Rom using Odin, than start again with custom roms.
OR
2: download your custom Rom again and flash, might be corrupt download.
atifsh said:
Yes stop messing
1: If you dint have to save anything, wipe better to full wipe
Flash a stock Rom using Odin, than start again with custom roms.
OR
2: download your custom Rom again and flash, might be corrupt download.
Click to expand...
Click to collapse
So it's OK to interrupt this ROM flash, even though it's stuck at 50%? Should I just hold the power button or remove the battery??
pull the battery
But I say flash stock Rom first, lengthy procedure I know, but safer
OK I decided to reflash RR 2.3, which had been running fine for a couple of weeks previously. Immediately after flashing (which worked OK) the boot process wouldn't complete - it got as far as the RR splash screen then died (screen blank, and needed a long press on the power button to restart).
This happened several times. Eventually I removed and replaced the battery and it finally booted.
Does this sound like a hardware problem? I've noticed that the phone often runs quite warm, but I don't know if that's normal.
You have to flash stock rom, only way to know if there is something wrong with your phone, run it for couple days.
Now to the heat issue, it is due to
1: modem
2: kernel
3: both
At first I tried flashing the ElementalX kernel and my screen didn't turn on. So I waited a day and the htc logo finally showed up and I immediately went into recovery. I already had the Renovate Rom before so I tried installing it as I did a while back. I made a noobie mistake by not realizing that my battery life was at 13 percent. So I tried installing the rom. And its stuck where it says "System Unmounted Already" At the bottom it says its at 20 percent and its installing the rom. However, its already been 2 hours since its been at 20 percent. I currently have the htc one charging but I presume that it wont be solved by just charging it considering that the red light isn't on. Please help me find a solution. To make matters worse I only have a mac laptop.
Alexrt890 said:
At first I tried flashing the ElementalX kernel and my screen didn't turn on. So I waited a day and the htc logo finally showed up and I immediately went into recovery. I already had the Renovate Rom before so I tried installing it as I did a while back. I made a noobie mistake by not realizing that my battery life was at 13 percent. So I tried installing the rom. And its stuck where it says "System Unmounted Already" At the bottom it says its at 20 percent and its installing the rom. However, its already been 2 hours since its been at 20 percent. I currently have the htc one charging but I presume that it wont be solved by just charging it considering that the red light isn't on. Please help me find a solution. To make matters worse I only have a mac laptop.
Click to expand...
Click to collapse
Help would highly be appreciated.
Alexrt890 said:
At first I tried flashing the ElementalX kernel and my screen didn't turn on. So I waited a day and the htc logo finally showed up and I immediately went into recovery. I already had the Renovate Rom before so I tried installing it as I did a while back. I made a noobie mistake by not realizing that my battery life was at 13 percent. So I tried installing the rom. And its stuck where it says "System Unmounted Already" At the bottom it says its at 20 percent and its installing the rom. However, its already been 2 hours since its been at 20 percent. I currently have the htc one charging but I presume that it wont be solved by just charging it considering that the red light isn't on. Please help me find a solution. To make matters worse I only have a mac laptop.
Click to expand...
Click to collapse
I had a flash go bad and get stuck on mine, I just rebooted it into Recovery (power & vol down), did a full wipe, including cache & dalvik cache, and ran the flash again, it worked. Are you not able to get back into recovery?
trjlive said:
I had a flash go bad and get stuck on mine, I just rebooted it into Recovery (power & vol down), did a full wipe, including cache & dalvik cache, and ran the flash again, it worked. Are you not able to get back into recovery?
Click to expand...
Click to collapse
I fixed it. At first I wasn't able to get back into recovery since the phone was turned off and didn't turn on. However, I let the phone stay still for about a day and let the battery die. I than charged it and put it back into recovery as soon as I saw the htc logo.
This is the problem I am having with my Samsung Galaxy Note 3 (SM-N900P). This problem just popped up out of the blue on a stock ROM a few days ago and nothing I have tried has gotten close to fixing the issue
Description:
a) The boot sequence repeats in a loop with no more sound. The phone would reboot at the Sprint splash screen
What I've done so far:
a) Pulled the battery and depleted the capacitors
b) Installed TWRP and did a complete wipe
c) Tried installing a custom ROM to see if the issue persisted. ROMs failed to install as /system was being sketchy (at times it was reporting 0MB for partition and then an actual value after repair). When I managed to get a ROM to install still stuck in the boot loop
d) Used Odin to do a full restore to a stock NC5 ROM. The phone got up to initial configuration page and then rebooted, now only gets to the Samsung splash screen before rebooting
Items that I can get into:
Recovery mode
Download mode
I have a 30 second video of it rebooting but cannot post it currently due to the forum rules
Question:
Is this issue fixable or is it a sign of internal memory failure?
Try an older version of TWRP, i.e. 2.8.5.0
Or, try a different recovery.
I'm not sure that it will work, but it's worth a try.
Good luck!
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
rbeavers said:
Are you doing it this way?
http://forum.xda-developers.com/showthread.php?t=3069667
Click to expand...
Click to collapse
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
SubRyan said:
I didn't notice that but I just installed TWRP 2.8.0.0 through Odin (like a few minutes ago). Phone actually managed to get to the stock recovery image config screen and was working as long as the cable was still attached to the computer.
As soon as I removed the cable it went straight back to the boot loop
Click to expand...
Click to collapse
Here is what you need to do. First pull battery, reinstall. If you can boot into twrp recovery, fine wipe everything i.e. caches, system, data, etc. If you are on a stock recovery do a factory reset. Pull battery, reinstall and boot into download mode.
NOW let's go to work. First use odin to flash stock NC5 tar. Chances are it will bootloop, STOP !!!! don't panic. Just reflash with odin again. The second time it should take. Remember that your device is setting up for first time use. This will take 3-5 minutes, sitting at the Samsung logo. Since didn't list the most important thing which is what OS you where on where the device Borked, or what you where doing with the device when it Borked. I'm going to assume it was on 4.4.4 and you tried to downgrade to 4.4.2 NC5. In which case a bootloop on the first bootup after a downgrade is normal, you have to flash twice to reset the bootloader. For more info click on rom flashing basics in my signature. Enjoy !!!
Problem solved. I started getting suspicious when the phone would boot up with the charging cable attached to the computer today
The issue was an aftermarket Mugen Power battery that developed a fault. Put the stock battery back in and problem resolved
Thanks for the help guys