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.
Related
well i have had cyogenmod 3.6.8.1 for awhile and everything works perfectly and smoothly but i just turned off my phone to switch to my new 2400mah battery and when i turned it back on i got past the splash screen but now its stuck at the android boot loop so i thought wait acouple minutes...and well.. no luck. i dont get it...any ideas?
try fixing the ext file system. It could have been messed up if you just took the battery out. If that doesnt work, try wiping and reflashing the ROM. Btw, does it work with the normal battery in?
wipe
if you can get into recovery then u know everything is fine. if u can get the update file for the rom on ur sd then wipe and flash it see wht happens then
Usually these problems can be taken care of with a wipe and a reflash of the ROM. Hopefully you performed a nandroid backup and can restore your settings. If not, there is really no other way but to wipe and reflash and lose your data.
nephron said:
try fixing the ext file system. It could have been messed up if you just took the battery out. If that doesnt work, try wiping and reflashing the ROM. Btw, does it work with the normal battery in?
Click to expand...
Click to collapse
well i shut the phone down properly but i tried what you said anyways... and on the first try it had an error and told me to run it manually..but i tried again and it worked so i rebooted but still no luck. i did a nandroid backup recently...could that possibly have anything to do with it?
and also...when i did the nandroid awhile ago...it got stuck at the boot loop as well...so i did the wipe/update and it worked. and now i turned off my phone for the battery change and this happens....it seems like maybe its something with the rom? idk...i dont see why a nandroid would mess anything up
i suggest to wipe and reflash. That should fix it.
nephron said:
i suggest to wipe and reflash. That should fix it.
Click to expand...
Click to collapse
well yea...i was gonna do that no matter what and that would prob fix it. but this has happened to me before with this rom. i turn it off, everythings fine, then i turn it back on and bam, boot loop. idk. i guess i just should never turn off my phone lol.
imakamasta said:
well yea...i was gonna do that no matter what and that would prob fix it. but this has happened to me before with this rom. i turn it off, everythings fine, then i turn it back on and bam, boot loop. idk. i guess i just should never turn off my phone lol.
Click to expand...
Click to collapse
Set up ADB using the guide in the sticky, and connect your phone through USB
type
Code:
adb logcat
as you boot your phone
see if anything is repeating. if nothing ever shows up, its possible that the battery could be defective
B-man007 said:
Set up ADB using the guide in the sticky, and connect your phone through USB
type
Code:
adb logcat
as you boot your phone
see if anything is repeating. if nothing ever shows up, its possible that the battery could be defective
Click to expand...
Click to collapse
well after wipe/reflash it works....and all...but after restart same thing...im thinking something might be wrong with my ext2 partition...im trying to reformat it via comp and paragon partition manager and it wont let me..it wont even start the reformat...idk
imakamasta said:
well after wipe/reflash it works....and all...but after restart same thing...im thinking something might be wrong with my ext2 partition...im trying to reformat it via comp and paragon partition manager and it wont let me..it wont even start the reformat...idk
Click to expand...
Click to collapse
try this method:
http://forum.xda-developers.com/showthread.php?t=535797&highlight=wipe+ext
But after you install cyans recovery image (or if you already have it installed)
* FSCK for ext filesystems from the menu
if that doesnt work then wipe
I tried to flash a theme update from zip in recovery mode and it messed something up royally. Now when I boot the phone it shows the HTC logo then just goes black and never comes back. I made a Nandroid back up right before I flashed and it said it completed it successfully, but when I go to recovery (volume down + power button) and select nand restore, it says its restoring and then restoring complete but when I reboot it still goes to the black screen. What do i need to do differently? I have never had to restore until now.
I'm on Fresh 2.3.3
Try wiping all data and dalvik and then restoring the nandroid.
doojer said:
Try wiping all data and dalvik and then restoring the nandroid.
Click to expand...
Click to collapse
Just tried that and I'm still getting the black screen after boot.
PMDColeslaw said:
Just tried that and I'm still getting the black screen after boot.
Click to expand...
Click to collapse
Do adb logcat. It might actually be booting without a bootscreen.
HeroMeng said:
Do adb logcat. It might actually be booting without a bootscreen.
Click to expand...
Click to collapse
Can you walk me through that? Sorry I haven't ever heard of it.
EDIT: Ok I let it run for a while and it eventually boots up but the boot screens/sounds never show or play. So I completely wiped the phone and reflashed Fresh 2.3.3... still no boot screens or sounds! I don't know what I could have messed up that complete wipe/flash doesnt get rid of. Any ideas? Also now Titanium is saying that it cant get root access because my phones not rooted properly. What tha?
Bump... Still having this issue. The phone is usable but the boot images and sounds are gone
nobody has mentioned this but maybe you just have a bad Nandroid. maybe something did not copy right or something in the phone internally got deleted during the backup/restore process. i saw on android forums somewhere it happened to some person using an Eris. Cant quite remember how he got it fixed but he ended up fixing it somehow.
t12icky0 said:
nobody has mentioned this but maybe you just have a bad Nandroid. maybe something did not copy right or something in the phone internally got deleted during the backup/restore process. i saw on android forums somewhere it happened to some person using an Eris. Cant quite remember how he got it fixed but he ended up fixing it somehow.
Click to expand...
Click to collapse
Well I thought it might be a bad nandroid too, so I just wiped the phone and flashed fresh without ever restoring the backup and it still has no boot images or sounds. It's the strangest thing. When I flashed the first time to 2.3.3 the re were definately boot images and I flashed from the same file this time.
You might have to just use the RUU and start over from scratch, I had to do that once and it sucked.
Sent from my Hero CDMA using XDA App
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!
My device seems bricked and I have a problem accessing /data.
I'll give you the background...
I'm using cyanogenmod 5.5.0.2 and cyanogenmod 9.
I've been using my device with the these settings for well over a month.
In that time I had some issues with the device shutting down when it was charging, other than that everything has worked flawlessly.
Today it shutdown when I was charging and when I tried to start it, it just showed the Samsung logo then it restarted.
I booted clockwork recovery and I tried several things to get it up and running again.
§ I tried wiping dalvik but that made clockwork freeze (It stops when before the no,no,no,yes,no-list should show)
§ I wiped cache partition, the wipe finished successfully.
§ I tried resetting factory settings with no success (I get the no,no,yes-list. When confirming the device hangs at "formating /data..." )
All I do from clockwork connected to /data and the sd-card freezes the device.
I'm at a complete stop, I have no clue going foreward.
Can anyone help me? That would be much appreciated, and I would love you for it!
Thanks, Jon
I would try to flash the stock rom thru Odin. Get the original honeycomb rom. You can get that at sammobile.com. you'll have to extract the .tar.md5 file out of the zip you'll download. Use 7-zip for that.
Back everything up first and you'll have to rebuild from the stock hc.
Sent from my SGH-I727 using xda app-developers app
Oh god, thanks! It worked.
Or rather, the odin flash failed but somehow that kicked the /data into working mode.
Thanks for you respons <3
Should I put solved tag on the thread?
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