Related
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?
i had network problems (3g stopped working, don't know why), and had an old version of doc's. so i figured i'd install the new version after a wipe, see if that'd fix it.
just to be safe, i went in recovery (clockwork) and restored an earlier backup. it worked, but still no internet. upon remembering that this was the backup i made just after installing docs, i went back to my previous backup, stock rom, i think 2.1.
this is where stuff went wrong. i hadn't disabled the lagfix (forgot which one, i remember i had ext4 as filesystem), and now, no matter what i do, my phone won't go past the boot screen. big lettering galaxy s, smaller gt-i9000 and at the bottom samsung, you know the one.
i tried everything i could imagine. wipe data/factory reset, wipe cache partition, re-restore to the oldest backup. only then did i remember the lagfix and remove it. retried all of those, still no dice.
i can get into recovery mode, both clockwork and 2e, and i can get into download mode.
when i connect my phone to my pc, it doesn't notice. when selecting mount in clockwork, it mounts, and shows the two drives in my computer, but when i try to open one of the drives, i get nothing.
i installed docs rom a while back, and have wiped my pc since then, so i have no files from that. i have installed the android sdk, but don't know how to use it, let alone how to use it with a phone that doesn't show.
all i want is to get back to stock, for now. try again from there.
can i? or have i ruined my phone?
edit:
wow... take about relief.
i used odin to flash xxjpu, 2.2.1, and it seems to have worked!
in case anyone else is stuck on a boot screen, download mode with odin means you're safe.
anyone with more sense than i showed in my stupidity, sorry for adding another semi useless topic.
Ok, I might have bricked my phone. I had the cm7/Aosp gingerbread mod. But I didn't have apps2sd enabled. So I downloaded rom manager, flashed the newest version of clockwork recovery, and rebooted to recovery, where I partitioned for apps 2 sd with a size of 256 mb and 128mb swap-space . I then factory reset, and formatted Boot, cache, data, everything. After that I went to mount as Usb, and I copied the Rom, gapps, and a battery icon mod back to the phone. But the phone didn't recognize any installable packages on my sd after I un-mounted, so I shut my Hero off in hopes it would when I turned it back on p) . When I turned the Hero on, it went to a Usb-fastboot mode, and I couldn't get it to turn off so I removed the battery from the back of my phone, then put it back in. Now my phone won't turn on at all. Does anybody know what I did wrong and can I fix it?
http://androidcommunity.com/forums/f60/how-to-apps2sd-for-droid-34800/
http://forum.xda-developers.com/showthread.php?t=666420
not sure if this will help but maybe you can find some info there
Hopefully that squared you away. But for future question, please post it in the general or question section. This area is specifically for devs and their projects.
oohaylima said:
Hopefully that squared you away. But for future question, please post it in the general or question section. This area is specifically for devs and their projects.
Click to expand...
Click to collapse
Alright sorry, I think I meant to post it there but then kinda freaked out >.<
spleef said:
http://androidcommunity.com/forums/f60/how-to-apps2sd-for-droid-34800/
http://forum.xda-developers.com/showthread.php?t=666420
not sure if this will help but maybe you can find some info there
Click to expand...
Click to collapse
Thanks Spleef, but I was wondering how to get my phone to turn on again as it seems to have just quit on me
Whenever a ROM doesn't boot up properly, boot loop, freeze, etc, I usually have to pull the battery out. Then when I restart it, I hold down the Volume Down and Power buttons at the same time to boot into recovery. Try doing this while the phone is plugged into your wall charger and see if that helps.
Also, I'm not 100% on how to get the apps2sd working, but I had a question about which version of Clockwork you were using. I thought with CM7 Gingerbread we were supposed to use version 3.0.0.5 of Clockwork. I know there is a new version, 2.5.1.7 I think, that shows up in ROM Manager. Unless something has changed, I don't think it will work with CM7.
I'm still pretty new to this, so hopefully someone else will chime in here for you.
Good luck.
i did the same thing one time you gota wipe everything again i mean even the sd card and extthen take ur sd card adapter and put rom gapps any extras on ur sd card then put it back into ur phone then flash it in the order of rom,gapps,extras,and kernel last if u are using one hope this helps
p.s this was using CWM 2.5.0.1
This just happened to me the other day, except I was trying to use firerats partition mod. See if it will boot by holding volume down or up while powering on. It worked for me, but I had to ruu back to stock and had reroot with z4root.apk
Sent from my HTC Hero CDMA using XDA App
Ok anytime you do a factory reset from the phone you most likely will loose root. And leave your phone charged over night it should come back on. And your swap is to big IMO. For apps to sd try a 28 or 32 swap and 512 partition. Then upgrade you ext from ext2 to ext3. And you were supposed to wipe everything before you flashed the apps to sd file. As in wipe everything data,cache,dev-cache and ext. Then flash your rom,google-apps,and kernel last. Boot up sign into your account and let it sync. Then boot to recovery and flash the apps2sd zip. After that you should install your apps. And I think you should ruu and reroot. Sounds like you lost root when you did factory reset from with in the phone. Just my opinion. Hope it helps good luck.
Something.About.Me.U.Dont.Like.
Its.Cool.I.Understand.AWAH
Before I startת I tried to find this problem also search on Google and here but could not find any information about this problem.
This night I did not put the device to a charger because he had already 90% battery, so I left it disconnected,in the morning I got up I saw the phone is turn off, I tried to turn the phone light up and the ATT screen turn on,
I went and when I came back after 10 minutes I saw that the phone is still stuck on the "Galaxy S" screen.
I removed battery, changed, and it's still stuck.
I'm running version CM7.1,
The phone can get into the recovery menu.
Can anyone help me?
I do not understand in the android system and I don't have any backups of my pictuers...
Any chance to save the phone?
update: I search for a solution, and found on the CWM the option of "Mount USB storage" and I copied my pictures to my computer...
so now my new question is how can I get the phone to turn on again? only format and install new rom?
I can use CM7.2 zip file and install via the recovery menu?
you can go to cwmr and can do a data wipe which will uninstall all your apps and data but will not touch your sdcards
You won't lose your pictures on the sd card. If you are still stuck, try wiping dalvik cache from recovery
Sent from my ICS Samsung Captivate
I have a similar problem. Like eidoll32, I did not plug in my cappy and when I went to turn it on the next day, I was only able to get a boot loop at the AT&T screen. Currently, I cannot get into recovery, but only download mode.
I originally rooted the phone with the Galaxy_One_Click_Root tool, and installed CyanogenMod 7.1 for the captivate, when CM7.2 went to RC1, I flashed that from CWM, doing a full wipe. Later I wanted to try ICS, so I flashed AOKP - captivatemtd - M5 b30, doing a full wipe (twice).
That's where I was when this happened, and where I am now.
Let me start by saying,this isn't my first rodeo,i've been rooting since the beginning of the G1,but this one has me stumped.
Ive got a Moto Atrix HD, rooted and bootloader unlocked running Batakangs Deodexed stock. It started feeling kinda laggy so I decided to jump into recovery (CWM 6) and delete the Devlik cache Battery stats etc. basically everything but user data so I didn't have to start from scratch. Ive done it in the past and it speed things up considerably with no ill side effects. So I did it thins time and immediately got the "unable to access recovery log/command" error. So I decided to reboot recovery and try it again and the same error came up as soon as it booted into it. I decided to just use rsd and do a complete fresh stock att install,but it wouldn't go to fastboot and rsd didn't see the phone neither did adb.So I tried a full wipe. Didn't work. So idecided to do a rom reinstall and see if that fixed it.nothing. So I tried another wipe and this time it wouldn't boot back into recovery,stays stuck on the first boot screen. I even went through the trouble to remove the back and unscrew the battery and do a battery pull with no luck. During all this I had RSD pulled up and it never saw the phone to give me something to work with. Im kinda stumped on this one,i can normally figure it out without issues,searched here and I didn't see anyone with the same issue exactly. Im open for ideas. Thanks
Updatek so I managed to get PhilzTouch recovery installed,and got Carbon installed. But still getting the error in recovery.Its finally booting at least tho....Finally got to use MythTools to reinstall the recovery and all is fixed..
TabascoTX said:
Let me start by saying,this isn't my first rodeo,i've been rooting since the beginning of the G1,but this one has me stumped.
Ive got a Moto Atrix HD, rooted and bootloader unlocked running Batakangs Deodexed stock. It started feeling kinda laggy so I decided to jump into recovery (CWM 6) and delete the Devlik cache Battery stats etc. basically everything but user data so I didn't have to start from scratch. Ive done it in the past and it speed things up considerably with no ill side effects. So I did it thins time and immediately got the "unable to access recovery log/command" error. So I decided to reboot recovery and try it again and the same error came up as soon as it booted into it. I decided to just use rsd and do a complete fresh stock att install,but it wouldn't go to fastboot and rsd didn't see the phone neither did adb.So I tried a full wipe. Didn't work. So idecided to do a rom reinstall and see if that fixed it.nothing. So I tried another wipe and this time it wouldn't boot back into recovery,stays stuck on the first boot screen. I even went through the trouble to remove the back and unscrew the battery and do a battery pull with no luck. During all this I had RSD pulled up and it never saw the phone to give me something to work with. Im kinda stumped on this one,i can normally figure it out without issues,searched here and I didn't see anyone with the same issue exactly. Im open for ideas. Thanks
Updatek so I managed to get PhilzTouch recovery installed,and got Carbon installed. But still getting the error in recovery.Its finally booting at least tho....Finally got to use MythTools to reinstall the recovery and all is fixed..
Click to expand...
Click to collapse
I just jumped in and read your post. unfortunately, I had no chance to reply to you after I read the last line But it's nice to know my tools is helpful.