[Q] Galaxy S Boot Screen hang meaning? - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi all,
So after I flash a new ROM (MIUI MGv2/RC8vC/MGv1) I always hang at the Galaxy S GT-I9000 screen - the first boot screen.
I am wondering what this means? is it a corrupt file, something wrong with my internal sdcard, ROM not installed properly?
Please help,
Thanks.

some times a wipe from recovery will help and goes back to normal boot
many issues may cause this problem for instance if framework.jar or android.policy.jar or... have some bugs , will happen like that

Hi,
By wipe you mean clearing the formatting system, data, cache, dalvik cache and a factory reset? I ask this because the MIUI roms are not are non-wipe and the instructions recommend you to format those places before install (which I did).

I mean wipe cache partition from recovery. just try it and ley us know if it works

Well I just tried again but it doesn't work because I can't access recovery mode. It hangs at the Galaxy S screen and doesn't move from there so I'm wondering why because if I can't fix the bad install then I can't access the recovery mode and can only flash.

if recovery dont work BUT download mode does,
start the whole process again, flash back to stock froyo with froyo bootloader.
did you come to MIUI from Gingerbread ??

Well i've done the process like 10 times, nearly every single time from froyo (JPU,JS5,Ezbase 2.0) and I also went from 2.1 to 2.2 and then to MIUI. The other times I have tried coming from CM7 as CM7 works.

well i have a similar issue but in my case i just wiped my data thru cwm on darky v8 xxjpy..
now i get boot loops,any idea what should i do??
i know this is not exactly the thread but if i get my answer it'll save me from starting a new one..

When I got bootloops i normally reflashed. If you don't have data it will probably work?
I assume you have data as your on Dark v8 when V9 is out?

i dont understand by have data??
i flashed v9.5 but went back to v 8 few months ago..
today i just wiped/factory reset my phone using cwm and it was succesful but now its bootloops and vibrations..
i never wiped my phone before and only have flashed using cwm,never used odin for flashing roms!!

OH I see, by data i meant personal data that you might want to back up...I'm not to most knowledgeable but I know how to flash roms. I reckon you should try to flash V8 it again if you can enter recovery.

Related

Please help unable to install any rom??

Hey sorry if this has been asked before i couldn't find it anywhere so there is some problem with my phone i don't know what is happening every time i use to install a new Rom it use to install perfectly without any fc's boot loop errors etc, but from past 2 days i don't know why any ROM i try to install (even the one which i use to work perfectly) will not install perfectly there will be fc's boot loop error wont pass the X when i switch on the phone. Please help its driving me crazy
Make sure your wiping old data in recovery.. and if flashed a new kernal or radio could also cause a problem too
ilostchild said:
Make sure your wiping old data in recovery.. and if flashed a new kernal or radio could also cause a problem too
Click to expand...
Click to collapse
yes i did Wipe data/factory reset ,Wipe cache,Wipe Dalvik-cache but just now i discovered that after doing this and still last installed rom has not been wiped its still there wtf what should i do and yes i did install 2.6.34.1_AVS-925mV_BFS_1113Mhz kernel how do i completely wipe everything???
Umm also do wipe sd partition, then do another wipe factory and cache-.. then do a repair sd then try to flash new rom.. this is what i usually do when i install new roms
still no luck i even did clear storage then wiped everything and i dont use app2sd(ext) i dontunderstand what to do i even tried with the clockworkmod's recovery still the same
sorry man, My only guess and idea is try to flash back to a normal kernal, then flash rom.. only thing i can come up with atm, or you can wait and see if some one that comes up with a better solution
where can i find norman kernel or any kernel which can fix this?

[Q] Stuck in Boot animation after installing seeARMS ROM

Hi, I have installed seeARMS ROM and followed his instuction. I have kept the JL2 modem and speedmod kernell (I was already on speedmod). I have tried 2 methods to install. The seeARMS.UGJL2.v0.4.zip with the seearms file and the CWM.
Both install went OK and I even had a congratulations screen. The problem is when the phone reboot it stays on the boot animation and get stuck there. I have tried 2 different boot animation and the same happen.
I have no problem to restore my data since I had backup but I would like to have the seearms ROM. Any idea?
Also a side question, can we get the new CK1 modem with seearms?
Richard
Have you been wiping your phone before flashing the rom? I have been having issues like you describe only when i flashed a rom w/o wiping.
(In CWM Recovery: wipe data/factory reset, wipe cache and advanced -> wipe dalvik cache)
No. I did not wipe. I am not interested in the new ROM if it mean wiping. I made a test by downloading a boot animation app. I trying 2 different boot animation and had the same result. The boot animation play with no sound but I have a vibration during boot and then nothing. Eventually it go back to the animation, vibrate and this repeat until I restore the backup.
I am wondering if tehre is something special about the Bell Canada boot animation?
Can I use the seearms without any boot animation folder?
I don't think it's a problem about the boot ani in particular.
I am not very familiar with the rom, since i have another device. In the seearms rom thread the dev mentioned two versions of the rom, one that requires wiping and one that does not.
So i guess it could be working out to flash the latter w/o wiping. But in my expirience those things rarely work out that way.
There might be incompabilities with the config data left behind by the rom installed before, or other possible issues.
Only way to be sure that those things aren't blocking anything is to wipe the phone and do a clean flash.
Personally i always do it that way. And if i like the rom, and choose to use it, it is always possible to get back all the apps and settings back with titanium backup and/or syncing them back.
But as always before wiping, if you choose to do so, please be sure to have a full nandroid backup, in case you want to go back, or something goes wrong.
I will try the wipe version
What rom were u on before seearms
Sent from my GT-I9000 using XDA Premium App
I was still on stock (froyo 2.2). Actually still on it today
You were right. The wipe version worked fine. I have now to decide to keep it or not...lol
ROM is awasome was worth well the trouble.
Glad it worked out for you - have fun with the rom
Sent from my Desire Z

Stuck at "touch the android to begin"

This concerns my galaxy note n7000. I had a rooted checkrom v4 working on my note. I tried to install criskelorom v2 and got bootloops. I then tried to go back to stock via odin and flashed stock N7000 KL3 ROM which i had earlier used, I had to go to stock because after bootloop even recovery was not working. now after flashing stock i am getting a strange problem of the phone getting stuck at the welcome to gt-n7000 screen . "touch the android to begin" . nothing is happening after touching the android on the screen although i can change the language etc and even the pull down notification is also working but the phone is stuck at the initial stage. I have a nandroid backup of my initial checkrom in my internal sd card but cannot restore it before installing a rom with root and cwm. Kindly help . Thanks.
I'm having the exact problem. I'm hoping we can create a soft brick sticky thread. I walked away from my phone last night because I was getting frustrated.
My attempts to flash stock ROM via Odin resulted in the "not responding" message in windows. I can get to both CWM and download mode, however any ROM flashed via CWM results in the behavior described by the OP. fortunately I have access to another Samsung phone, so I can double check driver installation (although it worked for flashing previously).
I'm continuing a search through the forums to find some alternate methods for unbricking. Hope someone has an idea.
Thanks!
It seems that the stock roms i was trying to flash were nonwipe ones so i flashed xxla3 which is a wipe rom and was able to boot . I then flashed the earlier kl3 rom over this rom because kl3 is rootable. I then rooted and installed cwm booted into recovery and restored my earlier nandroid backup. I think the situation arises because the nonwipe rom was unable to clear the cache , user data etc
Thank you for the information. I had exactly the same problem. What did you use to root KL3 ?
Just wipe both cash and user data, and reboot.
reboot to recovery mode -> mount and storage -> format system, format cache, format data.
and do a factory reset and wipe cache.
problem should be solved cause that's what i did
Flo1389 said:
Just wipe both cash and user data, and reboot.
Click to expand...
Click to collapse
Thanks
liewkingyan said:
reboot to recovery mode -> mount and storage -> format system, format cache, format data.
And do a factory reset and wipe cache.
Problem should be solved cause that's what i did
Click to expand...
Click to collapse
daaamnnn!!! I'm scared to dead because of this!! Thanks dude!!!, no more **** ass ics
I had an issue like this once or twice.
http://www.youtube.com/watch?v=L5XjF6sPef4
This skips the that screen. then I cleared some things like google framework and it all was peachy
But its not wroking for me

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)

Doesn´t boot... At&t screen then Recovery...

Hi Everyone... I´m having problems whith my old Captivate...
Firts thing is that some time ago, my internal SD card got corrupted and my phone was unable to start, only in recovery but it was impossible to wipe data, cache, dalvik cache, etc...
After that i tried to fix it, flash stock rom, and nothing worked, so i found this thread http://forum.xda-developers.com/showthread.php?t=1447303 and it seems to "work" ...
So i did it, followed all instrutions, and now i´m able to do all wipes and even flash rom´s but i cannot get the phone to start... I flashed ICS Slim rom, but it just gets at&t screen and then it goes to recovery mode, and phone can´t boot... Am i missing something? :/ Like bootloaders o something like that?
caddi234 said:
Hi Everyone... I´m having problems whith my old Captivate...
Firts thing is that some time ago, my internal SD card got corrupted and my phone was unable to start, only in recovery but it was impossible to wipe data, cache, dalvik cache, etc...
After that i tried to fix it, flash stock rom, and nothing worked, so i found this thread http://forum.xda-developers.com/showthread.php?t=1447303 and it seems to "work" ...
So i did it, followed all instrutions, and now i´m able to do all wipes and even flash rom´s but i cannot get the phone to start... I flashed ICS Slim rom, but it just gets at&t screen and then it goes to recovery mode, and phone can´t boot... Am i missing something? :/ Like bootloaders o something like that?
Click to expand...
Click to collapse
Slim Bean is on JB, are you sure you flashed ICS?
If it's JB, you need to flash it twice as it needs to repartition.
Sent from my SGH-I747 using xda app-developers app

Categories

Resources