Database Develop

[Q] Constant Boot Loops when trying to install new ROMs

I have CWM 4.00.15 installed and I tried to install Ryyu's Rom (Wipe) by putting it on the SD card and rebooting into recovery, then selecting the zip file and hitting apply. When the installation tried to update my kernel, it just froze and rebooted. I was then stuck on a boot loop between the Galaxy S screen and the CyanogenMod boot screen. I know that Ryyu's did not install correctly because the CyanogenMod boot screen was still there. I had to use 3 button recovery and erase cache, davlik cache and user data before trying to install AOSP Essence, but same problem happened. Installation dies and phone keeps rebooting in loops. Finally, gave up and went back to CyanogenMod Nightly and it worked.
Why can't I seem to install any other ROMs besides Cyanogen? I know I am doing something wrong, but not sure what. Any advice/help appreciated. Thanks.

Have you tried starting from a clean install?
Try starting with a stock rom and then to activate Cwm flash a modded Kernel.

Br1g0 said:
Have you tried starting from a clean install?
Try starting with a stock rom and then to activate Cwm flash a modded Kernel.
Click to expand...
Click to collapse
Hi,
this is what I initially did to get Cyanogen on:
1. Used Superoneclick root to root phone
2. Check that 3 button recovery and download mode works. Recovery version was 3e, so installed superlagfix from android market. This automatically installed ClockworkMod Recovery as well.
3. Use CWM and flashed recovery for Samsung Galaxy S i9000
4. Reboot into recovery and select the CyanogenMod zip file and click apply to install.
To install subsequent ROMs, I just put the zip file on my SD card, reboot into recovery and repeat step 4 above, after clearing cache and user data. It is after that I get stuck on boot loops.
I did do a Nandroid backup before my initial Cyanogen install so I can go back and restore it, but it would be Froyo.

when coming from CM / MIUI - Samsung based ROM
you MUST flash a 3 file firmware with pit and re-partition.
Cyanogen and MIUI use different partitions than samsung ROMs so this is why you are having issues.

Ok, just managed to flash Darky's EE 10.2 using Odin. Not sure if Odin is the ideal way, but it worked. Really enjoying Darky's. Thanks folks!

HELP! - Stuck booting to Recovery after trying to flash CM10 :(

Hi,
I flashed my GT-i9000 (Firmware was Gingerbread BUJVY) using CF Root (CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.tar) through ODIN.
All worked fine and I was able to boot into Recovery using the regular Volume Up+Home+Power.
I then proceeded to flash CM10 nightly (23/9/12) (from my external Micro SD card) by wiping data, wiping cache and wiping Dalvik Cache.
I then navigated to the zip file for CM10 and run it. It started ok then qiuckly the phone rebooted and rebooted into a newer version of CWM (6.0.1.4).
From here I cannot do anything at all!! It won't recognise my Micro SD now to even run the installation again
I'm hoping someone may be able to help, I would really appreciate it!
TIA!

zim_zimmer said:
It started ok then qiuckly the phone rebooted and rebooted into a newer version of CWM (6.0.1.4). From here I cannot do anything at all!! It won't recognise my Micro SD now to even run the installation again
Click to expand...
Click to collapse
Do you know what version is your Firmware? is it 2.3.3 or 2.3.6?, IF its 2.3.3 your boot loader needs to be updated to 2.3.6 for you use , If its already 2.3.6, than you should be able to use CWM recovery to reinstall the CM 10 from your SD card. (But by doing this you may lose your IMEI as you should do a progressive upgrade , like from GB 2.3.6>ICS CM9>JB) or flash a semaphore JB kernel
Easiest way out would be for you to use a JVU ROM to recover, safe your EFS, than proceed to CM 9 and than to CM 10...
you can get a rescue kit or JVU+CFRoot from My Android Collections and or a solution from My Android Solutions

Hi there,
I was on Gingerbread 2.3.6 before I ran the above.
I have gotten a bit further than the above. I managed to mount the phone as a USB whilst in CWM and put the CM10 zip file on the actual phone memory. I then wiped data/cache/dalvik and rerun the install. It installed but didn’t reboot itself, so I rebooted manually and then the Cyanogenmod logo started up and it booted into CM10. Looked ok apart from the Home Button didn’t work!!
Do you think I should still run the above??
Rooting this phone and flashing ROMS is more difficult than my Galaxy S3!!
Cheers

zim_zimmer said:
Looked ok apart from the Home Button didn’t work!!
Do you think I should still run the above??
Click to expand...
Click to collapse
Since you are already on CM 10, you need to solve your home button problem, try doing a wipe in recovery, if fails, flash again the CM 10

Hmmm, it didn’t work.
What I’ve done since though is try to flash another ROM.
I’ve flashed the ‘xBean’ ROM with success, however, I did encounter the exact same problem when flashing the ROM as mentioned above
I wiped data/cache/dalvik and run the install for xBean. It stopped after the first install attempt and rebooted itself, however it just brought me back to the CWM screen (although this time different from the CM CWM).
So I wiped data/cache/dalvik, then run the install again. This time it went through the full install but again (like with CM) it didn’t rebooted automatically. I manually rebooted and then the xBean logo came up and booted in.
This time the home button is working, and pretty much everything else is too by the looks of it. So far so good!
I guess my question would be, why does the ‘ghost installs’ keep happening???

Phone won't boot, can't transfer files

I was helping my friend flash a ROM, he downloaded CM10.1 put it on his internal SD card he went into recovery and wiped data and cache afterwards he flashed the ROM and during that his installation aborted! he completed the same process a few times and still same thing. we decided to give up and just reboot, but the thing is now he's stuck on the Galaxy ace logo screen! so we went back to recovery and tried again.. same thing... again. we can't even transfer files since we can't boot up the phone!
Any suggestions? I'm really desperate..
EDIT: He used odin to get back to stock, It's all good!

Go to Recovery
Then go to mounts and storage menu.
then select mount USB
and then Transfer the required files
this way you can Transfer files via USB by recovery
And use CWM Recovery 5.0.2.6
ROM doesn't get flashed if you are using CWM Recovery 4
enjoy

O2x bootloop after unlocking boot loader

Hello everyone
So I have fully rooted phone which I've been using for a long time with CM10.1, I just wanted to flash cwm from 6.0.3.1 to same version with cwm touch support but I couldn't because of many errors in ADB and other programs like All in one tool kit and others. So again, I got an error that I couldn't flash a new cwm, I don't know why but I thought of unlocking boot loader again.... that was really stupid, why I had to do that I don't know I thought the errors would go away... but now I have some crappy old lg logo which I had a year ago like I just bought a phone, now I cant get past or even see CM boot logo, just the red old lg logo. So I guess that's what is called boot loop? Its not first time I got this problem and fixed it somehow, but now I don't know what to do because I cant even get into cwm, the only way to get in there is to flash cwm again and if I power off my phone the combinations of cwm doesn't work, so that's why I need to flash again so that it could launch cwm automatically. Did I messed up my boot partitions or something ?
Things I have:
6.0.1.5 cwm from nv flasher
CM10.1 a new nightly in my phones internal memory (I install them like 2 times a week through cwm without problems) which I thought could fix everything by installing a rom with not messed up system files (I've put it into phone before this problem occurred)
but I cant install any zip from sdcard like I did every time before because it sais E:Cant mount /sdcard/ (WHAT???)
I don't have any backups -_-
internal and external memory which are both full and cant access in cwm by pressing mount usb storage, it doesn't work..... So it means I cant make a backup in cwm.
Things I want to do:
Get back to phones previous state. I think its possible because its not like I have erased the data, I just messed up boot partitions, yes ?
I also don't want to loose my data on sdcard/emmc or what ever its called. (on my phone both internal/external memories are called sdcard). Ofcourse if there is a way to somehow make a backup without cwm then Its okay if loose my data, then I can do a factory reset.
Maybe I cant install zip from sdcard because this cwm is bad? Will a newer version also say that I cant mount sdcard (I never had this problem in any cwm's that I have used).
I hope someone can suggest me something . If I wrote something not clear or haven't said some details, tell me I'll try to explain.
!EDIT: Ok I've managed to fix that lol.
Things that I've done:
used All in one kit option called "flash stock rom" (even if I have already a custom rom, not stock ) then installed older cwm, it was version 5 it had a good working "mount usb storage" so my pc recognized the phone and I placed new CM rom into my sdcard (external). So after I flashed the rom, installed cwm5, I fixed permissions just in case, then deleted cache partition and dalvik cache, then installed that CM rom, somehow it still had an old boot logo and was still stuck in boot loop, then again after I used All in one kit and flashed stock rom I saw my new lg logo (black and white, not the broken one with red lg circle) so I just normally booted up phone from cwm and I have everything back without any data loss.

[solved] Just another Bootloop - but this time with other complications

Dear all,
after rooting a cyanogen my Samsung SIII mini (GT-I8190N) went into a bootloop. Unfortunately, my home button is defect so I cant access the custom recovery (at least I have no idea how).
I can access download mode using an USB jig and I tried to flash multiple combinations of firmwares - but nothing helps.
The furtherst I got was with slimKat, with showed me for half a second a dialog which launcher I want to use, before it rebooted. CM 12 always "optimizes apps" and reboots after it finishes the last. Stock does only show the boot animation in a constant loop.
I tried repartitioning in ODIN and even NAND Erase all... but with no success.
My flash counter is already at 32
Does anyone have still some ideas? Can I factory reset the phone from ODIN? Can I somehow boot into recovery from ODIN?
Best,
Jan

gebauer said:
Dear all,
after rooting a cyanogen my Samsung SIII mini (GT-I8190N) went into a bootloop. Unfortunately, my home button is defect so I cant access the custom recovery (at least I have no idea how).
I can access download mode using an USB jig and I tried to flash multiple combinations of firmwares - but nothing helps.
The furtherst I got was with slimKat, with showed me for half a second a dialog which launcher I want to use, before it rebooted. CM 12 always "optimizes apps" and reboots after it finishes the last. Stock does only show the boot animation in a constant loop.
I tried repartitioning in ODIN and even NAND Erase all... but with no success.
My flash counter is already at 32
Does anyone have still some ideas? Can I factory reset the phone from ODIN? Can I somehow boot into recovery from ODIN?
Best,
Jan
Click to expand...
Click to collapse
I suspect that your device is boot-looping on custom ROMs because there is incompatible stuff on your /data partition. The data partition needs to be wiped and you can't really do that with ODIN. You need to find a custom recovery that allows you to flash using ODIN and that is compatible with the custom ROM you are trying to flash. You also need to wipe /data (format it) before your first boot. You will loose all your info, even the stuff that was in your internal sd but the device should boot.
BUT:
I note that you said your HOME button is not working and that is required to manually boot into recovery. Additionally, with out a booting ROM you can not issue the "adb reboot recovery" command which would do it for you. There is a trick that I have learned but I only know how to do it with "heimdall" in the Ubuntu Terminal.
Basically it's like this: If you flash a recovery directly into the kernel partition, then when you try to boot normally, you will boot recovery instead. Then flashing a ROM normally (in recovery) will restore a normal kernel into the kernel partition.
The partitions for the kernel and recovery on this device are typically kernel and kernel2 respectively.
kernel -> kernel
recovery -> kernel2
So:
recovery -> kernel ( Will boot recovery on a normal boot ).
I hope I have explained this well enough. You are going to have to do some learning if you want to get this working. Good luck.
P.S. If you are thinking of asking follow questions, don't, Google it instead.
Heimdall: http://glassechidna.com.au/heimdall/

Meticulus said:
Basically it's like this: If you flash a recovery directly into the kernel partition, then when you try to boot normally, you will boot recovery instead. Then flashing a ROM normally (in recovery) will restore a normal kernel into the kernel partition.
Click to expand...
Click to collapse
Dear Meticulus,
thanks a lot for your help. I was away for the week-end; thus the late reply.
With your help it took me only an hour to get my smartphone working again. The main tipps, which helped me was the Heimdal tool, which I wasn't aware off and the possibility to flash the recovery directly into the kernel...
It worked like a treat. The smartphone booted into TWRP directly, which finally gave my access to wipe the data partition.
It took a couple of trials before I was able to flash an android image back to the kernel/system but this also worked nicely.
So thanks again and this brick is solved :good:
Jan