Database Develop

[Q] Galaxy S Boot Screen hang meaning?

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.

Nandroid backup of rooted stock ROM

I've made a nandroid backup of my rooted stock Rom with cyanogen recovery and flashed Modacos FR15 wich worked retty good for me. But after some testing i wanted to change back to my stock Rom. After doing backup of the Modaco I wiped and restored the stock rom backup which refused to boot. I restored the modaco Rom which worked perfect. Any ideas what the reason could be? BTW md5 check before restore was all fine and no errors on restore.
Sent from my LG-P990 using XDA App

Did you wipe everything? Also Dalvik cache? It worked for me tho, what kind of version are you using for CWM?

CWM is 3.0.2.8 (latest version which i installed via ROM Manager) - as I said - other backups of CM Nightly and Modaco FR15 worked without probs. But I made 2 Backups of my rooted Stock ROM v10c which refuse to boot after restore :/
Wiped all except Dalvik - I thought Dalvik gets wiped when doing Wipe Data / Factory Reset ... but I will try again with wiping Dalvik too.

I tried again to restore this time with dalvik wipe - but no change - boot hangs at the LG logo with the grey/blue loading-bar, the bar is moving some seconds and then stops and nothing happens. :/

try to press power+vol down to reset the phone to factory default. see if it can help...

I've had similar problem.
phone wont boot.
Only way I found out, you can see here:
http://android.modaco.com/content/l...rom-release-v10b-dated-1300166062-15-03-2011/
but you will loose everything what is on your phone

The reason it won't work, is because MCR converts the file system to ext4 (which CM7 can cope with). To revert to stock, you need ext3 - either
1. Use this to convert back to ext3 and immediately restore the backup (don't reboot or it will go fubar) http://android.modaco.com/content/l...3-for-converting-your-device-er-back-to-ext3/
2. Use nvflash to restore the stock 10b, then flash Clockwork, and then restore your backup.
The choice is yours .

Stuck at Boot

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

[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:

Weird CWM behaviour

Hello!
Before I want to go on to CWM I want to tell you what happened before.
Yesterday I flashed TWRP recovery which resulted in a really bad situation. I was stuck in recovery. If I pressed reboot it went straigt to recovery again, even if I pulled out the battery. So flashed the stock firmware via the KDZ flashing method and everything worked again.
Then I rooted again, installed CWM, installed CM, installed all my apps (TB backup on PC was quite old),....
So all in all it was a big amount of work and it took me a few hours.
Then everything was working again as it should and I updated all my TB backups and then I wanted to make a Nandroid backup so that I wouldnt have to do all that flashing and installing again.
So I went to recovery--> backup and restore --> backup
But it didnt finish. It always stopped with this error: Error while meaking a backup image of /system!
So i thought maybe I should install everything again, which i did. (I had already made a TB backup of all my apps, so i thought this woulb be done fast)
Well, went to recovery again, did a factory reset, wiped dalvik cache and even formated /system. Then I installed the latest CM + GAPPS and rebooted.
And the first thing i recognized was that the screen popped where it says "android is upgrading". And I wondered even more when I realized that all my apps where stille there. So obviously the factory reset and also format /system didnt work properly.
If I format /system and dont install any ROM then the device doesnt boot (which i guess is the normal behaviour). But what I want to say is that the format works there but if I flash CM afterwards all my apps are still there (despite the fact that i also did a factory reset).
All in all the phone does work normal now, but I'm not able to make a Nandroid backup and I'm really wondering why.
(I also reflashed CWM recovery but that didnt change anything)
I would be glad if s1 could help me.
PS: Could the solution be to flash stock again via KDZ and then do everything from the beginning?

Never heard of anything like this before.
Did you flash the recovery as a .IMG or through Rom manager (I would suggest to flash it with Rom manager).
Try this and report back (maybe your recovery image is damaged or smth.)
Sent from my LG-P880

I have no idea what caused this crazy behavoiur of CWM, but I started over again with flashing kdz and now everything is fine

Maybe your SD card is full. Try deleting a few files from your SD and then do the backup.
Sent from my GT-I9070 using xda premium

I dont have any external sd card and on phone memory there were more than 10GB free space