Database Develop

[Q] Interesting boot loop problem.

2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?

hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?

bradels said:
2 nights ago I thought I would have a go at installing ULTIMATE ROM 3.0. I have flashed many Roms on my Galaxy S before and not had a problem yet. I have ClockworkMod Recovery 2.5.1.0 installed.
However, this time- something went wrong. I don't think the installation completed properly. When I tried to reboot the system (to go back into my previous ROM) I wasn't able to. The Samsung logo appeared before the phone booted back into Recovery mode.
I tried to re-flash my previous working update.zip but had problems. I wasn't able to properly re-flash as the Installation would abort for various reasons. After doing cache clearing and data/factory reset I still had no luck. I resorted to reformatting the sdcard. Still didn't solve the flashing problem.
Throughout the whole time I was able to adb into the phone, browse the file system and I could push files on to it and take files off. But Kies wouldn't recognise the phone and Odin isn't able to complete a transfer to the phone (not sure why).
Today, I am able to successfully flash update.zip files (at least, that's what it looks like) but the phone ALWAYS boots into ClockwordMod recovery.
I am fast running out of ideas. Does anyone have any suggestion?
How can I tell if my ROMs are really 'there' but I can't access them because ClockworkMod is preventing them from booting?
Click to expand...
Click to collapse
myrobelle said:
hmmm... me too.. stuck in a loop, that keeps going back to the CWM recovery menu, and no matter what i do, keeps going back to it... cant even get to the download screen to flash (again).... here i was thinking no matter what happens when installing custom roms, i can always flash to my stable secure rom, but not this time... need some software that can perform surgical operations, any suggestions?
Click to expand...
Click to collapse
Thats too bad guys,and i m sorry to hear that news.I would like to havean answer but i dont...
The fact is that since most people in this forum use some custom roms,and all of us think the same,that we can always go back,so it would be great if you give some more details about what happened to you,and mybe why it went wrong,and it would be even better if one of the BIG guys would give some explanation about this...
I already thinking of not updating my rom anymore,dot want to end up in looping too,so lets see if someone will find something.Good luck guys..
By the way,i didnt get it right,CWM recovery cannot load your backup????

I just got an idea,but not sure if or how it would work or not.
Since you can push file with ADB,if soeone made a clean backup with his CWM (o e mail,contacts,setting saved) and send it to you,so that you log in with CWM recovery and flash that ???
Just an idea..maybe stupid dont know...

Its not very clear if youve tried this already but cant you just boot into recovery through adb? or does that not work either?

Bionic boot looping ice cream sandwich boot animation

My bionic is boot looping the ice cream sandwich boot animation. I had everything running fine and when i did a nandroiod backup all of a sudden it started boot looping. I have followed the directions for the rsd lite fix and also the r3l3as3d root one click fix. Both when ran said that they installed okay and should be fine but when i start it up it is still boot looping. Can someone please help. even after running them I still don't have the stock boot animation I still have the ice cream sandwich and I am still boot looping. I followed all of these direction http://www.droidforums.net/forum/dr...70-r3l3as3droot-43v3r-root-bionic-v2-1-a.html and on the screen it said that they installed okay and should work. and like I said I followed all the direction on this site as well http://rootzwiki.com/topic/4603-fxz-fastboot-recovery/ and it says it worked but after rebooting I find out it did not. can someone please help. I can boot into fast boot (obviously) and the stock recovery but nothing I have tried so far seems to fix this issue and now I am lost and stuck boot looping an ice cream sandwich style boot animation ( which has been working fine for weeks until i just did this last nandroid backup and for some reason after that nothing but boot loops.

Try this fix:
droidforums.net/forum/droid-bionic-hacks/173870-r3l3as3droot-43v3r-root-bionic-v2-1-a.html
It worked for my Bionic when I got stuck in a bootloop. You might try clearing your dalvik cache before you do anything else though.

I have the same issue!!!

If you're looking to wipe down your phone and start from scratch you should really be seeking out the full 700MB FXZ file to use with RSD Lite. That'll bust through any mods you may have put in that have wrecked your phone.

I already did.

nullifier said:
Try this fix:
droidforums.net/forum/droid-bionic-hacks/173870-r3l3as3droot-43v3r-root-bionic-v2-1-a.html
It worked for my Bionic when I got stuck in a bootloop. You might try clearing your dalvik cache before you do anything else though.
Click to expand...
Click to collapse
did you not read my post, I already treid that, and I cant clear davliche cache if i cant get into cwm like I said i can only get into stock recovery.

projektorboy said:
If you're looking to wipe down your phone and start from scratch you should really be seeking out the full 700MB FXZ file to use with RSD Lite. That'll bust through any mods you may have put in that have wrecked your phone.
Click to expand...
Click to collapse
Like I said I already tried the full 700mb FXZ and it did not work!

Htimez2 said:
Like I said I already tried the full 700mb FXZ and it did not work!
Click to expand...
Click to collapse
I had similar issues that seemed to be caused from restoring a nandroid after doing the 5.7 update, however my results were the complete opposite of yours, if you have insurance like most i'd go pay the hundred bucks and act distraught that it's now at the bottom of a lake or river after a canoe capsize.
Also try option 4 vs 1 or vice versa on http://forum.xda-developers.com/showthread.php?t=1279825

Lucky!
I'd rather be stuck in a never ending ICS boot loop than have fully functional GB any day!

Just curious, did you try to perform a factory reset immediately after the fxz? If not, I would do another fxz and when the phone reboots, pull the battery, enter stock recovery and perform a factory reset. Good luck, hope you get it going.

HELP!!
Hey Everyone. I had UNL3ASH3D v1.4 on my bionic, got bored and saw the Shifter base rom and wanted to flash Shift3r ICS blurry v2.3.1....installed shifter base.zip...booted fine...backed up, factory restored, wiped cache, installed Shift3r ICS blurry from sd. Now im in a boot loop =(.
I Held Power and up/down got into the recovery, but it wont access my sd card, and wont boot up a clockwork backup from a while ago. Please help....!

fxz it with rsd lite, u just soft bricked it.
Also i'm almost positive that those themes specifically say for 2.0+ as noted by this warning in in the post "THIS IS THE TH3ORY CR3AM IC3 CR3AM SANDWICH ADD-ON FOR [R3]BLURR3D V2.0PBX", so fxz, forever root, optional on 5.7 upgrade and flash [R3]BLURR3D V2.0PBX base rom re-apply theme

In the end I just had to send it back to Motorola for a new one. I just never mentioned it was rooted so it was still covered under warranty since I technically unrooted it before i sent it back even though it wont stop boot looping. SO I got my new Bionic the other day and I am happy and re-rooted again, and the best part is I didn't have to pay for the insurance replacement phone.

to be or not to be. a question, or a way of living?
I will have to admit that I, at one time, would proceed with the same recourse. But I've been around the block a time or two now, and have come to realize how my actions, large AND small, greatly affect others.
If I do something to VOID my warranty, I own up to it.
Just sayin'

[Q] Stuck on LG screen [Solved]

Hello, this is my second post here though I visit this forum quite frequently.
I have a p990, and I have encountered a very strange problem with my phone:
Until yesterday, everything was normal, and every couple of weeks or so I installed a new/updated rom via CWM without any problem (usually).
Yesterday I installed the CM7 Kang from Ricardo, and this also worked well. However, when I tried to install my previous rom again (Gueste 3.1, after 3 wipes of course. The reason I didn't go back to a nandroid backup was because of problem in making the last backup) it got stuck on the 2ng LG screen. the buttons are lighted when I touch the screen, but even waiting 30 minutes doesn't change anything.
Since then, I tried to install many different roms (the latest CM7 nightly and some others), and all gave me the same problem. The only things that I've been able to do in order to boot successfully was to revert to an old backup that I had, or to install MIUI, which did work for some reason.
When I tried to install the same version of CM9 again, I always got a boot loop.
Any idea as to what could cause such a strange behavior and how can it be fixed?
Sorry for the long post, I just wanted to give as many details as possible, and I'll be happy to give more details if I can if there are things that I forgot.
Thanks,
Beorn

Beorn1 said:
Hello, this is my second post here though I visit this forum quite frequently.
I have a p990, and I have encountered a very strange problem with my phone:
Until yesterday, everything was normal, and every couple of weeks or so I installed a new/updated rom via CWM without any problem (usually).
Yesterday I installed the CM7 Kang from Ricardo, and this also worked well. However, when I tried to install my previous rom again (Gueste 3.1, after 3 wipes of course. The reason I didn't go back to a nandroid backup was because of problem in making the last backup) it got stuck on the 2ng LG screen. the buttons are lighted when I touch the screen, but even waiting 30 minutes doesn't change anything.
Since then, I tried to install many different roms (the latest CM7 nightly and some others), and all gave me the same problem. The only things that I've been able to do in order to boot successfully was to revert to an old backup that I had, or to install MIUI, which did work for some reason.
When I tried to install the same version of CM9 again, I always got a boot loop.
Any idea as to what could cause such a strange behavior and how can it be fixed?
Sorry for the long post, I just wanted to give as many details as possible, and I'll be happy to give more details if I can if there are things that I forgot.
Thanks,
Beorn
Click to expand...
Click to collapse
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops

markop90 said:
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
Click to expand...
Click to collapse
This fixed the same issue for me.
Wiped everything and flashed CM9. Works great (but battery drain is incredible!!!)

Solved!
markop90 said:
Try this: go to recovery > mounts and storage and wipe system, data and cache, and flash your rom.
If wiping system doesn't work neither, catch a logcat when the phone bootloops
Click to expand...
Click to collapse
Thanks, I did this, and now I was able to boot again with Gueste 3.1 (I'd rather wait for a bit more stable and mature version of CM9).
Actually, I did this thing twice, and it still didn't help, and in the third time I tried to make a logcat (I'm rather new to this logcat thing), and while trying to boot and make a logcat at the same time it suddenly started workind
I just hope that it will stay good now, and that I won't have this problem again in future flashes...
Thanks!

Galaxy S plus I9001 problem

Hello. I am currently in hold of a soft-bricked Galaxy S Plus smartphone, and i've been encountering several problems during my 'Rom' expedition. I'm not quite sure if there is any thread out there that presents a similar issue such as mine, and if it is, i couldn't find it, therefore i apologize in advance for any misunderstanding. My smartphone currently won't boot and gets stuck on the Samsung Logo - Along the way i have managed to make the recovery mode work, somewhat, and the download mode works flawlessly.
It all started when i first acquired my Galaxy S plus and stumbled upon an article on how i could simply upgrade my android version to Android 4.0.4 ICS via CyanogenMod 9, aka Ice Cream Sandwich and to be honest, it startled me and i was eager to try it out. After spending a couple of hours into informing myself on this procedure, because yes, i was pretty scared to even consider it. Clockworkmod gave me several headaches during the way, and so did Odin, before i got used to it, but in the end i made a Nadroid backup and i successfully installed the rom and could gladly enjoy my new Ice Cream Sandwich. However, the rom had it's issues(Other than that, it worked amazingly), and some people pointed them out( I'm not the brightest man when it comes to phone performance ), so i decided to look further into it. I found the xda forums, and browsed them for a couple of hours, in search for the perfect rom and decided to try out the CM10. I thought it would be a piece of cake, since the last installation went briefly, but i was oh-so-wrong.
I backed up my Sms, contact history and such, and simply turned on the recovery mode, with the intention of wiping the data and cache -- And boom! Clockworkmod froze and the phone shut down, just for me to realise that it was now impossible to go past the logo. I panicked and spent most of my time into searching for a solution, but there were couple of things which i simply couldn't do! First, the clockworkmod (I used CWM 5 when installing the first rom) wouldn't allow me to wipe the data and cache; Second, odin would simply get stuck when trying to install a stock rom (I tried a couple of gingerbread roms before that); I even let the PC open the whole night, just to let odin do it's work, but it still couldn't work. A stock rom that /worked/, though, was the I9001BUKP2 / CNXKP1 - Romania(Vodafone) Android 2.3.5 which i came across on another forum post. After installing the gingerbread rom, i booted into the recovery mode(original one) and tried wiping the data - But it would only freeze and shut down.
- I must add, that the clockworkmod gives me errors on mount cache (Command) and whenever i try to restore my original firmware(backup) it would just freeze on the data restore. (I had issues with several other roms when using Odin multidownloader, since they simply wouldn't get past the "System.img.ext4")
I honestly don't know if i missed out on anything, and/or if i missed out on any thread that could simply smack the answer right in my face, but once again, i'm sorry. If anyone could provide help to my issues, i would be grateful - Thank you very much !
edit: I have just now tried to install a firmware[ I9001 XEN I9001XXKF8 ], and after odin did it's job, and the SGS+ booted into recovery mode to finish the installation, i have noticed something very interesting - It gets stuck at "Formating /data..." - I can only assume this is perhaps a primary issue.

[Q] Bootloop - Samsung Galaxy S5830 B with CM10.1.6

Hello all
First of all, I'd like to say that I've spent a lot of time searching through XDA and other websites on the internet, and so far I didn't find a solution to my problem, and that's why I'm creating this new thread.
I have a Galaxy Ace S5830B and just flashed Mardon's version of CM10.1.6 ROM in it, following every single step on his guide, using CWM 5.0.2.6.
I made sure that before flashing the new ROM I wiped the whole thing, clearing cache, dalvik cache, formatting /system and doing the factory reset.
I did not manually flash any kernel.
Everything runs smoothly and ok, just like all compliments the ROM gets on his topic, except for when I have to shut the phone down.
Once it is shut down and I'm powering it back on it gets into a boot loop that won't go past the Samsung logo. It means that the Samsung logo goes on, fades off and then it loops back to it, and the Cyanogenmod blue circle loading animation never comes.
It only works when I get back into CWM and hit "reboot system now" . Then it reboots normally.
I'd just like it to act normally, booting normally straight from a powered off state without having to go through CWM everytime I need to switch the phone on. That's because it's my father's phone, and having him getting into CWM every now and then after a battery run off is too risky, you know what I mean.
Any help will be very very much appreciated.
Thank you
Riggs
Sent from my GT-i9300. Forgive some misspelling here and there.

offRiggs said:
Hello all
First of all, I'd like to say that I've spent a lot of time searching through XDA and other websites on the internet, and so far I didn't find a solution to my problem, and that's why I'm creating this new thread.
I have a Galaxy Ace S5830B and just flashed Mardon's version of CM10.1.6 ROM in it, following every single step on his guide, using CWM 5.0.2.6.
I made sure that before flashing the new ROM I wiped the whole thing, clearing cache, dalvik cache, formatting /system and doing the factory reset.
I did not manually flash any kernel.
Everything runs smoothly and ok, just like all compliments the ROM gets on his topic, except for when I have to shut the phone down.
Once it is shut down and I'm powering it back on it gets into a boot loop that won't go past the Samsung logo. It means that the Samsung logo goes on, fades off and then it loops back to it, and the Cyanogenmod blue circle loading animation never comes.
It only works when I get back into CWM and hit "reboot system now" . Then it reboots normally.
I'd just like it to act normally, booting normally straight from a powered off state without having to go through CWM everytime I need to switch the phone on. That's because it's my father's phone, and having him getting into CWM every now and then after a battery run off is too risky, you know what I mean.
Any help will be very very much appreciated.
Thank you
Riggs
Sent from my GT-i9300. Forgive some misspelling here and there.
Click to expand...
Click to collapse
Try doing a factory reset, it might solve it. Do post the result. Hope I Helped

Already did it, also wiping cache and dalvik cache. No solution.
But thank you anyways =)
Sent from my GT-i9300. Forgive some misspelling here and there.

I also noticed this problem on my Ace S5830 and I have no idea why. I thought I was the only one who is having this problem. If anyone knows why, please tell.
Sent from my GT-S5830 using Tapatalk

offRiggs said:
Already did it, also wiping cache and dalvik cache. No solution.
But thank you anyways =)
Sent from my GT-i9300. Forgive some misspelling here and there.
Click to expand...
Click to collapse
When you are using CM10.1 by Mardon, NEVER WIPE DATA/FACTORY RESET!! ...You should fix your problem flashing again the rom
The ROMs are already preconfigured and when you wipe data/factory reset, all those settings will be lost and the device won't be able to boot successfully again

Oh, nice to know that! I'll try it soon, then I'll post the results.
Sent from my GT-i9300. Forgive some misspelling here and there.

offRiggs said:
Oh, nice to know that! I'll try it soon, then I'll post the results.
Sent from my GT-i9300. Forgive some misspelling here and there.
Click to expand...
Click to collapse
Ok, so just follow the correct steps to re-flash CM10.1