the problem is this:
Boot loops (g1 screen) occur when ever the battery drains. the only fix is to wipe data/factory reset. The battery has been replaced, and this still happens.
Could it be an outdated radio, an sd card issue, or recovery image issue? I'm rooted and running a old 1.4 cyanogen recovery and a SuperD rom.
Any ideas or suggestions? thanks
umm dunno that one, why not jus update the recovery and and radio
Related
I rooted my phone without any problems then installed another recovery image without an issue. I flashed my phone with new rom image and that also worked fine then I tried to another rom that seem to go well but now my phone is just siting at mytouch initial screen. I can go back into recovery but after flashing rom it still only sits on mytouch screen. How I can fix my phone?
Do you do a wipe before you install the new rom? That might fix the issue.
how do you wipe phone I'm having same problem. phone wont boot into recovery I can go into bootloader
I have been running the kanged builds of CM9 for a while, but it began to get bogged down recently and would freeze up almost daily forcing a hard shutdown and reboot.
Sometime yesterday, it began to boot only into recovery no matter what option I tried in the Cyanoboot menu. From there I tried a factory reset and wipe dalvik to hopefully get back into CM9 and here's where the strangeness really kicked off.
Clockwork (which was running off emmc) would freeze in the middle of the factory reset just like it would when CM9 was running (the graphics would degrade slightly upon inspection of the screen).
So, I grabbed my old sdcard with clockwork recovery on it to boot from sd, and I run into the same problem again. Freezing before a wipe, factory reset, or install from sd can complete.
Now, after each failed attempt in clockwork (sd and emmc) it sticks at a backlit black screen and after a hard shutdown refuses to boot (sd or emmc) for about an hour, only to repeat the madness again.
Does anyone have any ideas what I can try from here or familiar with a similar situation?
My sd clockwork version is 3.2.something and I've also tried 3.0.1.something.
UPDATE: For reasons unknown, my Nook seems to be booting regularly as of this morning. However, I am still unable to get a successful flash out of any rom. The closest I've gotten to success is stuck in a boot loop. I think from here I'll likely be able to figure it out, but just as before...
Any help is welcome and appreciated!
I had the same problem with the black screen when trying to install different roms on mine. I just kept clicking the power button and after a few minutes it would kick back on every time.
There is an entire thread specifically on this
http://forum.xda-developers.com/showthread.php?t=949699
As far as CM9 I can't help you much there. I would just try to install a different rom, and hope that works.
Thanks!
I had seen that thread, but I thought my experience was a different; either way, I've managed past that problem using a method similar to yours.
If this helps any, I have been trying to to 7.2 RC1 for a while as well, but it will not get me any further than the stuck boot screen same as the CM9.
Have you tried to follow the tread on returning it to stock ?? I would reformat and repartition it and return it to stock ... then make sure it runs. After that I would try to reinstall the new roms ...
Just my 2 cents
Tinpau
Having an issue that I cant seem to figure out. I have been using various roms eg Omega V7,S4 Google Edition V16, Fox Hound 1.1 etc. They all install fine, factory reset before and after wiping the various cashes as required. I also format the SD storage to be sure, but once up and running, apps installed, every time I restart the phone or for some reason it freezes it just get stuck at the white Samsung S4 logo.
If i go back in to recovery (TWRP 2.6.0.0) factory reset does nothing to fix this. I have also noticed that sometimes the internal SD shows as 0 Mb, and I have to reformat this to re-install a ROM. (Getting corrupt some how?) Only re-installing the ROM from fresh seems to get my phone up and running again. Until something happens. Any ideas?
I follow all instructions as detailed, and never come across this issue with my S3.
Ok after trying a few things the only thing that seemed to fix the problem was reflashing stock firmware using oden.
I had to reformat the internal storage again as this was acting like it was encrypted, which it was not. Think this problem that caused my phone not to boot when when restarted.
No Idea why it did this but its fixed now.
john81uk said:
Ok after trying a few things the only thing that seemed to fix the problem was reflashing stock firmware using oden.
I had to reformat the internal storage again as this was acting like it was encrypted, which it was not. Think this problem that caused my phone not to boot when when restarted.
No Idea why it did this but its fixed now.
Click to expand...
Click to collapse
same problem. As long as i dont reboot it works fine...first reboot it get stucked....
willhave to reverse to stock then...
too bad i loved GE!!!
So simple and fast!
I am facing weird issue with my Nexus 4.
All of sudden it stopped working. Won't go past X logo. I tried flashing stock images, didn't help. Though to flash backward, went for 4.2.2 JDQ39, it worked but no radio. Did factory reset, cache cleaning and all but no avail. Whenever flashing newer builds then it won't go past X logo and if JDQ39 or older then no radio. Multiple flashes done, no avail.
Tried flashing latest CM nightly as well (August 26), but that's also not booting beyond the logo in hours.
Any suggestions????
contactfornitish said:
I am facing weird issue with my Nexus 4.
All of sudden it stopped working. Won't go past X logo. I tried flashing stock images, didn't help. Though to flash backward, went for 4.2.2 JDQ39, it worked but no radio. Did factory reset, cache cleaning and all but no avail. Whenever flashing newer builds then it won't go past X logo and if JDQ39 or older then no radio. Multiple flashes done, no avail.
Tried flashing latest CM nightly as well (August 26), but that's also not booting beyond the logo in hours.
Any suggestions????
Click to expand...
Click to collapse
doing a system wipe (factory reset) when you update from 4.2 tp 4.3..? also just reminding you 4.3 based roms need new radio and bootloader update.. but that radio also works with 4.2..
Same problem
contactfornitish said:
I am facing weird issue with my Nexus 4.
All of sudden it stopped working. Won't go past X logo. I tried flashing stock images, didn't help. Though to flash backward, went for 4.2.2 JDQ39, it worked but no radio. Did factory reset, cache cleaning and all but no avail. Whenever flashing newer builds then it won't go past X logo and if JDQ39 or older then no radio. Multiple flashes done, no avail.
Tried flashing latest CM nightly as well (August 26), but that's also not booting beyond the logo in hours.
Any suggestions????
Click to expand...
Click to collapse
I am having the same problem, it sucks
the radio doesnt work, i think, because the IMEI is unknown, well at least on my N4
Antonio0 said:
I am having the same problem, it sucks
the radio doesnt work, i think, because the IMEI is unknown, well at least on my N4
Click to expand...
Click to collapse
You are doing something wrong, its pretty hard to brick a nexus. What recovery do you have installed? have you tried using ADB or even a toolkit?
i dont think i have a solution
smoka206 said:
You are doing something wrong, its pretty hard to brick a nexus. What recovery do you have installed? have you tried using ADB or even a toolkit?
Click to expand...
Click to collapse
So I've heard that its hard to brick, but my phone isn't bricked, far from it, because I can use it it boots and everything (I'm on 4.2.2) and I'm replying to you from it now, but I'm on my homes WiFi because the phone doesn't read my Sim card, or at least that what I initially thought, but after some research I found out that its my lack of IMEI that's causing the problem. Even when I go into settings and about phone and look in there, both baseband and IMEI say "unknown" but when I boot into fastboot its a all there.
Regarding your question about adb and toolkits and my recovery
1.) I've tried adb as well as fast boot and wugfreshes toolkit to try and solve the problem
2.)I am completely stock 4.2.2, and that includes the recovery.
PS I used to be rooted and that was it, but after I had gotten stuck in a bootloop I flashed 4.2.2 and that got the phone out of Tue loop but now the IMEI and baseband is 'unknown' rendering my phone essentially an iPod type of device
Antonio0 said:
So I've heard that its hard to brick, but my phone isn't bricked, far from it, because I can use it it boots and everything (I'm on 4.2.2) and I'm replying to you from it now, but I'm on my homes WiFi because the phone doesn't read my Sim card, or at least that what I initially thought, but after some research I found out that its my lack of IMEI that's causing the problem. Even when I go into settings and about phone and look in there, both baseband and IMEI say "unknown" but when I boot into fastboot its a all there.
Regarding your question about adb and toolkits and my recovery
1.) I've tried adb as well as fast boot and wugfreshes toolkit to try and solve the problem
2.)I am completely stock 4.2.2, and that includes the recovery.
PS I used to be rooted and that was it, but after I had gotten stuck in a bootloop I flashed 4.2.2 and that got the phone out of Tue loop but now the IMEI and baseband is 'unknown' rendering my phone essentially an iPod type of device
Click to expand...
Click to collapse
i have the same problem too.. can someone help please??
try this http://forum.xda-developers.com/showthread.php?t=2347060
http://forum.xda-developers.com/showthread.php?t=2453364
Hi Guys,
anyone else experience this weird behavior?
I was on Golden Eye ver from July with MG1 modem (i337m).
I installed Golden Eye v5 with a full format (formatting using TWER - WIPE - Delete Data - YES), then install rom and then KTOONSNE kernal to get wifi working.
The usual wait a few mins and the rom boots and everything working great/fast and stable. However, once you reboot, it will get stuck at the boot logo with the Samsung Galaxy S4 logo. no matter how long i wait it will not boot into the rom.
I have tried:
- reinstalling the kernal
- fixing permissions
- wiping caches
- reinstalling rom
nothing will bring me out of this unless i do a full format of the internal SD again (even restored a nandroid).
anyone experience this? Any suggestions from anyone?
What recovery and version are you using?
intenal security might be broken
iB4STiD confirmed that this is a known issue with TWRP breaking the internal security. Have to flash ADML using odin to fix. I'll have to do some research to see how to do that.
Vince
vkwan said:
Hi Guys,
anyone else experience this weird behavior?
I was on Golden Eye ver from July with MG1 modem (i337m).
I installed Golden Eye v5 with a full format (formatting using TWER - WIPE - Delete Data - YES), then install rom and then KTOONSNE kernal to get wifi working.
The usual wait a few mins and the rom boots and everything working great/fast and stable. However, once you reboot, it will get stuck at the boot logo with the Samsung Galaxy S4 logo. no matter how long i wait it will not boot into the rom.
I have tried:
- reinstalling the kernal
- fixing permissions
- wiping caches
- reinstalling rom
nothing will bring me out of this unless i do a full format of the internal SD again (even restored a nandroid).
anyone experience this? Any suggestions from anyone?
Click to expand...
Click to collapse
Ok, that's why I asked. Twrp 2.6.1.0 should work
ok i'll give it a shot. Thanks for the suggestion.
jd1639 said:
Ok, that's why I asked. Twrp 2.6.1.0 should work
Click to expand...
Click to collapse
*edit* I take that back. I was stuck on team win logo after the reboot was stuck and had to hold the power button until it shut down. Now I can reboot into the rom. Strange but I don't care. It works. Thx jd1639 and iB4STiD
I just upgraded to TWRP 2.6.1.0 and no luck. Same thing full wipe. Install rom and boots fine. But if I reboot again it's stuck on the Samsung galaxy logo. Trying to go back into TWRP to restore a old backup and stuck now on the Teamwin logo
vkwan said:
ok i'll give it a shot. Thanks for the suggestion.
Click to expand...
Click to collapse