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.

[Q] Boot looping

Hey everybody,
I just started roming my 7310 but so far AOKP B38 is the only ROM I can get to boot. Had some issues with apps uninstalling them self so I wanted to downgrade to a more stable version, most likely Galaxian Soup MileStone 5. I've tried several different ROMs and I always get stuck in a boot loop at the Samsung logo with the exception build 38. Any ideas what my problem might be?
My process is first Odin flash CWM 5.5.0.4 then adb push an updated CWM for the galaxy tabs I downloaded form there forms but have also tried the regular CWM. Then push the ROM and gapp zips, wipe dalvik, factory reset, and then install zip.
Thanks for any help.
Doug

Frugal McMayhem said:
Hey everybody,
I just started roming my 7310 but so far AOKP B38 is the only ROM I can get to boot. Had some issues with apps uninstalling them self so I wanted to downgrade to a more stable version, most likely Galaxian Soup MileStone 5. I've tried several different ROMs and I always get stuck in a boot loop at the Samsung logo with the exception build 38. Any ideas what my problem might be?
My process is first Odin flash CWM 5.5.0.4 then adb push an updated CWM for the galaxy tabs I downloaded form there forms but have also tried the regular CWM. Then push the ROM and gapp zips, wipe dalvik, factory reset, and then install zip.
Thanks for any help.
Doug
Click to expand...
Click to collapse
Always wipe data/factory reset, wipe cache, and also wipe dalvik cache in advanced, aaaaand format /system in mounts and storage. All this before flashing any ROM, unless you ODIN. This is how I always do it. Keep in mind Build 39 has its share of issues, so you're better off using an older build in the meantime.

[Q] No booting after installing CM 7.2

Hello everyone,
I just tried to install the stable version of CM 7.2 (cyanogenmod) and I kind of have a little problem: after rooting the device as described by iProHackr in one of his videos on youtube (Unlock Root 2.4.2 did not work for me), I used the Clockworkmod Rom Manager, downloaded from there the stable version of CM 7.2 and started the installation. The Rom Manager asked me before, if I wish to do wipe the cache and dalvik cache, as well as backup the current os. I selected all options and then the installation started normally.
After some time, the phone rebooted (as part of the installation), but it's stuck at the LG boot logo. I can see the LEDs blinking, but nothing has happened for aprox. 2 hours. The phone does not boot.
What should I do next? Should I reboot in recovery mode and try to repeat the procedure? If yes, how do I boot into recovery mode?
Thanks in advance.

Problem solved. I don't know what the problem was, but I made the same steps one more time, wiped the data and cleared the cache, installed the cm 7.2 again and after a couple of minutes, the phone started successfully.

[Q] Can't install any ROM (Slim Bean, CM10)

I really was checking the whole internet to find the solution for this but I couldn't find it (I'm a begginer so that might be the problem).
Problem is this.
I have a Samsung I9000 with rooted Gingerbread (BOJV9). I have rooted it with the CF-Root-XX_OXA_JVZ-v4.3 KERNEL.
So now my phone has a Kernel version: 2.6.35.7-I9000XWJVZ-CL762604 [email protected] #2.
And the next thing that I wanted was to install the Slim Bean 4.2.2. So I went to the CWM recovery and I have done the wipe of cache, dalvik cache and data/factory reset. everything went ok and fast. then I went to install the Slim Bean and started the install but just when it started, showed on the screen that it is instaling updates, phone just reseted, and Semaphore logo showed up, and was standing there for 10minutes. So I googled and saw that that was some kind of error. So I went CWM recovey and it had a new look because the version changed (from v3 to v6 I think) but I couldnt find data on my external SD card, as if it was deleted, but it was not, the data was there. Then I found this page http://forum.xda-developers.com/showthread.php?t=1494493 and was able to start the phone by flashing it with the original I9000 rom, and then installed the CWM again and then i returned my backup that I made of my phone. Then I started again to install Slim Bean again but this time I got an error at the wipe dalvik cache saying E:unknown volume for path. Now I dont know what could be the problem but please can you help me. Should I first install some other custom rom or should I put the rom files on to the I9000 memory or what. I am really confused
Also the same thing happend when I tried to install CM10. it starts the installation but it restarts after few seconds.
Files that I have used
Slim-I9000-4.2.2.build.3-OFFICIAL.rar
cm-10.0.0-galaxysmtd

Anyone? Help?

Do what you did again till the recovery changes to v6 as you said & then flash the slim bean or any other rom again... it will work.
Good luck

yatharthsims said:
Do what you did again till the recovery changes to v6 as you said & then flash the slim bean or any other rom again... it will work.
Good luck
Click to expand...
Click to collapse
Thank you sir. This helped me. God bless you

CM11 Infinite Boot Loop

Hi,
I have an infinite boot loop when i try to get CM11 on my Z1.
You have to know that :
- I unlock my bootloader with adb and it's work : my bootloader is unlock
- I try ALL nightly honami rom on cyanogen website
- When i turn on CWM I clean reset all cache (wipe, dalvik and wipe data)
- I install the gaps too for 4.4
So after that i try an unofficial CM 10.2 stable version with gaps for 4.3
And get infinite boot again and again... !
I don't see where is the problem ? I wait 20 minutes for each times and roms are put the SD card.
I use adb for unlock my bootloader and i boot the good boot.img for each rom in the shell before the install.
Help please ! Why it's not work ?
Thanks

:up:

Did you ask this to the OP of the Rom which you installed, maybe he know the solution.

I had this issue once on my galaxy s2.
By that time, I used a custom kernel that wasnt optimized for CM. Could it be that you are using a custom, non-CM-supporting kernel?
Also try a factory reset before you install CM

I get this with just about every rom apart from CM11. I'm currently struggling with romaur
Hope you manage to get it sorted

The questions remains . What kernel are you using? Did you do a factory reset before flashing?

You must wipe data,system and caches BEFORE installing a custom ROM