Stuck at Boot - Galaxy S I9000 Q&A, Help & Troubleshooting

So today my phone was on and everything was fine, then while I was charging it, went away from it a few minutes then came back it was on the boot menu. It now can not get past the boot menu ever.
I have ClockWork Mod recovery installed, and CM7.1 stable.
I did a "backup" via the ClockWork Mod Recovery of the system.
I am also quite tempted to get the CM9 RC2 installed. But screw it if it any kind of unstable. CM7.1 stable is unstable enough.
What should I do? I would prefer it if I did not lose all my stuff (like app notes etc).
Can I like just put my phone into Download Mode, place the CM9 RC2 on the root folder, then do the good old
cyanogenmodWiki Full Update Guide method via recovery
without losing anything?

tottycs said:
So today my phone was on and everything was fine, then while I was charging it, went away from it a few minutes then came back it was on the boot menu. It now can not get past the boot menu ever.
I have ClockWork Mod recovery installed, and CM7.1 stable.
I did a "backup" via the ClockWork Mod Recovery of the system.
I am also quite tempted to get the CM9 RC2 installed. But screw it if it any kind of unstable. CM7.1 stable is unstable enough.
What should I do? I would prefer it if I did not lose all my stuff (like app notes etc).
Can I like just put my phone into Download Mode, place the CM9 RC2 on the root folder, then do the good old
cyanogenmodWiki Full Update Guide method via recovery
without losing anything?
Click to expand...
Click to collapse
If you have done a "backup" from CWM before the failure just restore that.
From CWM menu try to do a dalvic and cache clean up. also clear init.d and nstool settings and try to reboot
If you want to be more adventurus and loose your contacts, sms, settings...and other stuff from CWM do full wipe and cache and dalvic and then install your favorite rom.

I tried to installthe Gnexus port rom jr03l 4.1.1 rc 10. I was on TAJB'S Jellybean rom with devil kernel. I tried to install the rom as per the instructions given. I did a nandroid backup of the current rom before attempting to do so. The flash failed as the phone rebooted into recovery after a few minutes. I tried to restore from my nandroid backup. That failed too and it came up with a message of "no free space". I rebooted the phone and the phone automatically tried to flash the gnexus port rom again. It failed rebooted and got stuck on the devil kernel screen.
After about 20 mins, i took the battery out and rebooted into recovery. I really dont know where to go from here. I need to backup my efs folder too somehow.
I have a flash zip of the gnexus port rom, the tajb rom and a cm9 nightly in my internal sd card. I also have a nandroid backup of my cm9 rom.
Any help will be greatlyy appreciated!!!
Please help me.

Hey
Just flash any firmware (Official is preferred)..root it and do a restore of the backup u have..
Done

Hey do a factory reset then try to restore your backup
Sent from my Awesome I9000 using Slim Bean

Related

Upgrade to ICS stuck in boot loop...

Trying to install the Cynogen ICS ROM, and when installing the .zip, it loads the Samsung flash screen with Cynogen, then get the green guy and loads of text for about half a second, then it just reboots. Over and over for about 10 mins. WHat went wrong? What should I do?
It happend the same to me.
I just removed the battery and put it back, entered in CWM and reinstalled the ROM.
Good luck!
I somehow got into a recovery mode, but with the assumption it would all go wrong again, tried to install the .zip Darky rom instead, went through the process and said it worked but then it just went back to the Cynogen loop problem!? I just tried a Restore instead, but I haven't rebooted yet, should I wipe everything again, and try the ICM .zip again?
Yep, just go with the whipe. I hope you did a backup.
OK turns out the Restore failed, so now trying to reinstall ICS .zip again. fingers crossed!
yep backed it up, not that its seems to have helped.
Well now it's stuck in the Galaxy S bootscreen...
that really sucks....did you deactivated the lagfix before running the rom?
If the problem persists you have to run a basic ROM using ODIN.
Yes deactivated the lagfixI can't get into recovery or anything now, except download mode.
Download mode is all you need to run a ROM with Odin.
I recommend Amestris, it is a good ROM, good battery life but the thread in not complete, there are some files missing...for now.
I've put some older ROM on I had, then tried to install ICS again but now when I use Clockwork, and select the file it goes to recovery but I can't select any zip files, just reboot back to this awful old ROM!
I had same issue when I installed ics, what I did that worked was pull battery and go back into cwm, reflashed ics zip and it fully installed that time. Had same experience when flashing cm7 before.
Not getting anywhere with this. I get an option to install zip from sdcard which is where the update is (an where the darky update also is which worked), but there is an option to update from internal SD, which is not where the file is. Is it in the wrong place?
I think you would be best to use Odin 1.3 to flash DarkyROM Ficeto JVT base rom.
are you sure those files are still on your sd card?
The reason you need to pull the battery and reflash the ICS rom a few times is because Samsung ROM (most) have a different partition layout to CM7 based roms (which the ICS port is one).
GL.

LG optimus 2x bootloop after failed cyanogen mod

Hello!
Today, i decided to install cyanogemmod on my 2x. So i downloaded ROM manager and downloaded cyanogenmod. everything went fine until i was going to boot for the first time. I got into a bootloop. so i tried taking out the battery and all that stuff but it still would't work. So i tried to recover the phone. I recovered it to a month old backup (I could not find the one i made in ROM manager before i installed cyanogenmod) The recovery went fine. But, when i rebooted it got into a loop on the lg logo! (the one without the loading bar) it would just load the lg logo, be there for like 10sec, then it would do the same. I tried recovering one more time, but it didn't work. The same thing happend. What should i do? :S Should i wipe data/factory reset?
EDIT: My phone was on android 2.3.4 before i download cyanogenmod.
BTW before i installed cyanogenmod, i forgot to clear cache and data. I was in a hurry so i did't notice the screen popping up, I automatically pressed "ok" without selecting anything.
Thanks for the help
- Kashif
Different partitions... Look for something called backtoext3 in the dev section (or somewhere else) The problem is that when you flash a custom rom like CM you convert your filesystem to EXT4, while stock is EXT3.
So basically what you have to do is:
1) Reboot into recovery
2) Wipe everything
3) Flash Backtoext3 zip
4) Restore Nandroid.
This should work. this will take you back to stock.
So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)
kashi169 said:
So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)
Click to expand...
Click to collapse
Yes
Flashing backtoext3 is just flashing the zip file you put on the sd card. (and then install zip from SD ) an then restore your nandroid stock backup and you're back on stock.
But you said you wanted to try CM right? In that case, wipe everything (factory reset/data + cache + dalvik) and then flash the CM7 rom and you have CM! Don't worry about backtoext3, your partitions are already on EXT4, because of your prior CM flash.
Ohh! Thanks Can you send the files for cm (2.3.4)? I've found some, but im not sure if my phone is compitable with them :S im really afraid to mess something up again
My. Signature. (CM7 temasek's KANG = the best CM7 at the moment )
I did everything and i got into a bootloop at the skating andriod screen again
OK, restored my phone back... Now it wont connect to the network and the battery has a question mark inside it. It also says the battery level is 999% heelp
Nvm, got my phone back to normal still dont understand why cm wont work...
You need cwm5 to flash cm.
I have a G2x, which is basically the same phone. But anyway, I would recommend nvflashing CWM and not getting it from ROM Manager.
CWM 5.0.2.0 will do just fine, but it is indeed old...
Anyway, are you sure you waited long enough on the CM boot screen? The first boot might take a couple of minutes. (4 or 5)

[Q] unable to restore from CWM

So I got following problem:
I was on Slim 3.2, did a cwm backup and wanted to upgrade to 3.3.
Probably it was a bad download or something, because I got stuck at the boot animation.
After I wanted to restore my backup I didnt even get into recovery, so I did a clean install with odin on 2.3.6.
Then I flashed cm9 to try restoring my data again, same problem.
I tried to restore my data several times, from cm9, from slim 3.2, but every time I get stuck on boot animation. Once I even let it sit for 40 minutes.
While restoring everything seems fine. Checking MD5 sums, erasing boot before restore, restoring boot image, system, data, datadata.
But then it says that .android_secure.img wasn't found, so it just skipped that and completed the restoration.
Reboot and stuck on boot anim.
Anyway to fix that? I'd be really gratefull if I got my app data back
flash darky xxjvu-re through odin heres a video showing a guide it not jvu its 10.2 re,same thing this will restore your phone ie get it working again
http://www.youtube.com/user/puggereduk
What to do when I got Darkys Rom on my phone?
Darky install the latest kernel, and then restore..
I think your problem is solved
Flashed Darky with Odin, flashed semaphore1.0 to get a more recent cwm and then restored my backup.
Now, every time I start my phone I get to cwm. If I choose reboot I get into cwm again.
What do now?

Samsung i9000 Recovery help!

Hi guys
Recently I installed CM10 jelly bean coming from CM9, everything worked well untill i realised that I didnt do a back up for my apps.
I had done a nandroid back up before coming to CM10, so i decided to go back to cm9 and get my apps back. This came up with an error.
So i thought it didnt work because i was on cm10, i downloaded cm9 again and installed it.
Nandroid back up worked, but now phone will not turn on samsung galaxy s screen just flashes.
I cant get into recovery only download.
Please help!
Hey
No issues...just downgrade to 2.3.6 using odin (Link Given Below) & root it..
Then flash CM9..reboot..
after the first boot goto CWM using the 3-button combo and restore from your nandroid backup..
Done..
Before flashing stock rom, download the newest Semaphore kernel and flash it using Odin (only PDA file, repartition NOT ticked). It may boot properly or at least it will get you to CWM
Cool123454 said:
Hi guys
Recently I installed CM10 jelly bean coming from CM9, everything worked well untill i realised that I didnt do a back up for my apps.
I had done a nandroid back up before coming to CM10, so i decided to go back to cm9 and get my apps back. This came up with an error.
So i thought it didnt work because i was on cm10, i downloaded cm9 again and installed it.
Nandroid back up worked, but now phone will not turn on samsung galaxy s screen just flashes.
I cant get into recovery only download.
Please help!
Click to expand...
Click to collapse
I had same issue when I flash JB Rom in first time.
When I feel ICS is better than JB(in this moment,I know JB will keeping improve).
FYR,my way as below to back to ICS and everything is come back.
1. In to recovery
2.do a 3wipe
3.falsh cm9(what you want),when flash completed reboot system.
4.Into desktop and run untill system is satble.
5.reboot phone to recovery
6.make a nadroid backup now
7.reboot phone.
8.reboot to recovery
9. restore previous backup data
final get a beer to celebration .
4.
Thanks guys solved it

[SOLVED] Am I bricked? PLEASE help me :(

Hi guys. I'm quite a noob, but have a good experience on flashing without be bricked (CM9, CM10, Crash, Paranoid...), but I have a problem.
I will explain to you step-by-step what I've done with my Note, so I wish some of you could help me.
1) I was running JB Crash ROM with PhilZ kernel.
2) Some apps got Force Close too often, so I went on Rom Manager and, after a look into the "Fix permissions" description ("It will fix some force closes" or something like that), I decided to give it a try and I tapped on it.
3) After that, my homescreen became unusable, because "TouchWiz Home" got EVERY TIME force closed without reason. Everything else worked fine, so I deciced to boot into CWM recovery to restore a nandroid backup of the same ROM.
4) Instead of tapping "restore", I tapped "backup" (my fault) and it started without possibility of get back. I got something like 200 Mb of free space, so in every case it will never have had success. My Note stucked at this point, so I decided to reboot manually (vol up+home+power) into recovery. Finally I tried to "restore" but I get this message: "ERROR WHILE RESTORING /SYSTEM".
5) I tried to reboot my Note, but it stucks at "Samsung Galaxy Note GT-N7000" screen without going on.
The good news is that it can go without problems into recovery and into download mode. What can I do? Flashing from CWM, for example, CM9 can fix this?
Please help me thanks!
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
friedje said:
1. Boot into CWM
2. Wipe data, dalvik and cache
3. Format system
4. Reflash your ROM
Don't use rom manager it's not compatible ....
Click to expand...
Click to collapse
After formatting /system, can I try to restore my nandroid backup? Or I have to necessary reflash my ROM? In that case, it's the same thing make it via CWM or via ODIN PC? I'm still on PhilZ recovery, which is safe I guess!
Anyway, thanks for your help
Via CWM or Odin, depends if you have your rom in the zip or the md5.tar format.
I would reflash to be clean. It's a bit more work in restoring your apps and data
afterwards, but at least you don't restore any messed up files.
if you can still access CMW and Download Mode then you probably are not brick... try fresh install through pc odin.. safe method no need to worry about bricking by fullwiping on unsafe kernel or raising triagle or binary counter whatsoever.. if you wanna play safe then PC ODIN and after that you can root your rom
Thank you guys, now I'm on stock ICS flashed via PC Odin and everything works fine I knew I was 99% not-bricked (still recovery and download mode avaiable), but I was a little scared too.
Thank you again!
glad you solved it.. :good:

Categories

Resources