hey guys, recently I have been experiencing a lot of crashes and other weird things.
sometimes the android gapps process or acore process would stop forcing me to reboot my phone.
the strange thing is, sometimes it will behave as if it was a first boot, so it would ask me to enter my details etc.
but after a battery pull and rebooting, it would boot normally.
however, it has also come to my knowledge that when i boot into CWM recovery, half the time it would say
"can't mount cache, etc etc etc" when it boots into it, and i cannot successfully flash on or wipe anything.
so it takes another few reboots to get it to finally work.
im on 2.02 blackrose running CWM 5.0.2.0
any ideas guys? cheers! :3
spazzy1912 said:
hey guys, recently I have been experiencing a lot of crashes and other weird things.
sometimes the android gapps process or acore process would stop forcing me to reboot my phone.
the strange thing is, sometimes it will behave as if it was a first boot, so it would ask me to enter my details etc.
but after a battery pull and rebooting, it would boot normally.
however, it has also come to my knowledge that when i boot into CWM recovery, half the time it would say
"can't mount cache, etc etc etc" when it boots into it, and i cannot successfully flash on or wipe anything.
so it takes another few reboots to get it to finally work.
im on 2.02 blackrose running CWM 5.0.2.0
any ideas guys? cheers! :3
Click to expand...
Click to collapse
My Nexus 7 just did that after I screwed around with everything in fastboot.
Try this:
\Change to 4EXT
Backup
Full wipe
Restore
My Incredible S doesn't see much screwing around any more and its still fine. I only had that problem after changing bootloaders to blackrose, then I wiped and the problem is gone
markj338 said:
My Nexus 7 just did that after I screwed around with everything in fastboot.
Try this:
\Change to 4EXT
Backup
Full wipe
Restore
My Incredible S doesn't see much screwing around any more and its still fine. I only had that problem after changing bootloaders to blackrose, then I wiped and the problem is gone
Click to expand...
Click to collapse
woops, i forgot to mention that i was on 4ext touch before and it still happened :S
it used to happen before, but not as frequently, so that is why i am a bit worried
when i get my pc back ill try reverting back to 1.13 bootloader :S
Related
Hey guys i don't know if anyone of you had the same issue but any info/help could be helpful.
I used to flash my N1 A LOT! but today i have this strange issue. I wiped and flashed rodriguezstyle again for a clean start, but i only got the colorful X with the unlocked symbol at the bottom and then just a black screen. i thought I've done something wrong and flashed again, but with the same results.
i changed my sd and downloaded again the rom but still no luck, did a nandroid restore and the phone was working properly. then i got a bit frustrated. downloaded 2-3 more roms but the result was the same.
i read somewhere that flashing with battery <50% may cause some errors so left the phone off to fully charge and tried again... no luck
then i remembered i upgraded the radio and i downgraded it to the old one, but still the same results and nandroid doesn't work... jeeeesh... back to the new radio and to my nandroid, but its no fun owning a smart-phone if you cannot flash it.
anyone with the same issue or any helpful tips/instructions?
Try this:
When the phone hangs at boot, reboot to recovery, wipe cache and dalvik-cache and reboot from recovery. Does that work?
If not, you'll need to logcat the boot process and post the log somewhere for us to have a look at.
So, assuming adb is working on your computer, plug in via usb, use adb logcat > output.log and reboot the phone. Continue logging for about 60 seconds after the phone stops.
Post the log to www.pastebin.com and then link back here.
hmmmm ok i will post results in abt an hour. thanx!
hmmmm i think i sorted it out... reflashed recovery. propably i messed smthing in there! thanx for your effort!
Hello everyone!
Weird problem here, too.
I was backing up my SD card in view of a format/cleanup....and when I went to boot into recovery, my N1 was stuck on the black screen with the white letters at the bottom "Build : RA-nexus-v1.7.0.1"... The phone actually boots great, it is just not loading the recovery image. Is it possible that part of the flash got corrupted? If so, I'm pretty much done flashing my N1, right???
I'll post a log asap (if it could help any)...
Oh and btw i tried to re-flash Amon-RA's recovery twice already...Superboot said it was successful....but I doubt it...
Well try flashing stock rom! I flashed it through fastboot step by step and it worked. Also check if the rom you try to flash needs ext partition or if apps2sd is enabled
Sent from my Nexus One
Test
Sent from my Nexus One using XDA App
Thanks nica.
I had to flash stock boot and rom to fix it...
Sent from my Nexus One using XDA App
anyone getting anything out of this log?
http://pastebin.com/YDNJK3RF
Wipe and reflash?
nxt said:
Wipe and reflash?
Click to expand...
Click to collapse
done a dozen of times. changed radios reflashed recovery! all!
the nandroid is working fine
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
JoshHart said:
Use a different rom or start from scratch on the one you're trying to use(not your nandroid)
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
i'am trying from scratch. wiped everything tried from the begining. even changed the radio
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
djmcnz said:
Yes - well I have observed these symptoms before.
The kernel is falling over loading the audio drivers.
It's very strange but if you slow the boot process down you can work around the problem and then get the phone to boot. Once it has booted once the problem doesn't tend to reoccur very often. I have only noticed this on a handful of phones although I can reproduce it from time to time.
When "stuck" (it is actually boot-looping as you observe) reboot to recovery using adb or finger-gymnastics and wipe dalvik-cache (or cache for that matter)... but you need only wipe one of them. Reboot the phone from recovery, should boot as normal but may take a loooooong time the first time...
Please report back, I'd be interested in your findings.
Click to expand...
Click to collapse
i will try it later tonight. the part that's bothering me it's that i loaded several kernels on my current nandroid and every single one is working fine! when i flash a new rom though i get this issues...
hmmmmm nop... not working. i flashed, and rebooted. pulled battery and wiped cashe same thing. then nandroid restore, flashed again, restarted, pulled battery and flashed dalvik. same thing...
i think i sorted out the issue... dunno why it happened but i flashed the stock rom part by part via fastboot and it seems that everything is fine now...
I had the same issue. It happened on every single ROM + Radio combination you can think of, including stock everything. Finally gave up and sent my N1 to get repaired. Received it a week ago and it's working again. They also re-locked my bootloader... And now here I am contemplating unlocking it again... but I don't want to go through that experience again.
I'd send it in rooted or not, if you still have the problem going back to stock.
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
bradels said:
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
Click to expand...
Click to collapse
myrobelle said:
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
Click to expand...
Click to collapse
Thats too bad guys,and i m sorry to hear that news.I would like to havean answer but i dont...
The fact is that since most people in this forum use some custom roms,and all of us think the same,that we can always go back,so it would be great if you give some more details about what happened to you,and mybe why it went wrong,and it would be even better if one of the BIG guys would give some explanation about this...
I already thinking of not updating my rom anymore,dot want to end up in looping too,so lets see if someone will find something.Good luck guys..
By the way,i didnt get it right,CWM recovery cannot load your backup????
I just got an idea,but not sure if or how it would work or not.
Since you can push file with ADB,if soeone made a clean backup with his CWM (o e mail,contacts,setting saved) and send it to you,so that you log in with CWM recovery and flash that ???
Just an idea..maybe stupid dont know...
Its not very clear if youve tried this already but cant you just boot into recovery through adb? or does that not work either?
Hi guys. Yesterday night I was installing a few new apps but the seemed to be stuck installing forever. So I decided to reboot. However, after the reboot, it never goes past the second boot screen.
I know I can just flash to another rom but is there a way to save my data in the instance? I can still get into recovery mode if that helps. Thanks
I've read you can hook up to your pc and mount your sdcard from cwm. Never tried it but if it works you can save your data that way then maybe a master clear/cache or dalvik wipe will help.
Sent from my SAMSUNG-SGH-I897 using XDA App
BumRush said:
Hi guys. Yesterday night I was installing a few new apps but the seemed to be stuck installing forever. So I decided to reboot. However, after the reboot, it never goes past the second boot screen.
I know I can just flash to another rom but is there a way to save my data in the instance? I can still get into recovery mode if that helps. Thanks
Click to expand...
Click to collapse
You can mount USB in recovery and get all your stuff off of your SD that way. You can also nandroid your current ROM in CWM and re-flash it, then restore from backup. As far as saving texts and all that, Idk if you can, but I'm sure someone else does.
Also, you could try clearing dalvik, cache, and then running the kernel cleaning script. It's gotten me out of a few binds before. It might help you to where you wouldn't have to flash again.
Hello, this is my second post here though I visit this forum quite frequently.
I have a p990, and I have encountered a very strange problem with my phone:
Until yesterday, everything was normal, and every couple of weeks or so I installed a new/updated rom via CWM without any problem (usually).
Yesterday I installed the CM7 Kang from Ricardo, and this also worked well. However, when I tried to install my previous rom again (Gueste 3.1, after 3 wipes of course. The reason I didn't go back to a nandroid backup was because of problem in making the last backup) it got stuck on the 2ng LG screen. the buttons are lighted when I touch the screen, but even waiting 30 minutes doesn't change anything.
Since then, I tried to install many different roms (the latest CM7 nightly and some others), and all gave me the same problem. The only things that I've been able to do in order to boot successfully was to revert to an old backup that I had, or to install MIUI, which did work for some reason.
When I tried to install the same version of CM9 again, I always got a boot loop.
Any idea as to what could cause such a strange behavior and how can it be fixed?
Sorry for the long post, I just wanted to give as many details as possible, and I'll be happy to give more details if I can if there are things that I forgot.
Thanks,
Beorn
Beorn1 said:
Hello, this is my second post here though I visit this forum quite frequently.
I have a p990, and I have encountered a very strange problem with my phone:
Until yesterday, everything was normal, and every couple of weeks or so I installed a new/updated rom via CWM without any problem (usually).
Yesterday I installed the CM7 Kang from Ricardo, and this also worked well. However, when I tried to install my previous rom again (Gueste 3.1, after 3 wipes of course. The reason I didn't go back to a nandroid backup was because of problem in making the last backup) it got stuck on the 2ng LG screen. the buttons are lighted when I touch the screen, but even waiting 30 minutes doesn't change anything.
Since then, I tried to install many different roms (the latest CM7 nightly and some others), and all gave me the same problem. The only things that I've been able to do in order to boot successfully was to revert to an old backup that I had, or to install MIUI, which did work for some reason.
When I tried to install the same version of CM9 again, I always got a boot loop.
Any idea as to what could cause such a strange behavior and how can it be fixed?
Sorry for the long post, I just wanted to give as many details as possible, and I'll be happy to give more details if I can if there are things that I forgot.
Thanks,
Beorn
Click to expand...
Click to collapse
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
markop90 said:
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
Click to expand...
Click to collapse
This fixed the same issue for me.
Wiped everything and flashed CM9. Works great (but battery drain is incredible!!!)
Solved!
markop90 said:
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
Click to expand...
Click to collapse
Thanks, I did this, and now I was able to boot again with Gueste 3.1 (I'd rather wait for a bit more stable and mature version of CM9).
Actually, I did this thing twice, and it still didn't help, and in the third time I tried to make a logcat (I'm rather new to this logcat thing), and while trying to boot and make a logcat at the same time it suddenly started workind
I just hope that it will stay good now, and that I won't have this problem again in future flashes...
Thanks!