Hi, all! I'm sorry if this is in the wrong section, but I'm having a hard time trying to understand the different forums.
My Samsung Galaxy Ace (S5830) running under a custom ROM The Ultimatum (I've been using this custom firmware for a few weeks now, with no real problems up until now), is bootlooping with no apparent reason. On a rare occasion, most apps on the phone stopped responding and would crash upon opening, and would require a restart before they worked again. Well this happened to me a few hours ago, so I decided to reboot my phone. After coming back to check my phone, I had found it was still booting. This has gone on for several hours now, and I've tried turning it on and off, removing batteries and everything. It's stuck in bootloop. I found this was odd, as I have had no dramas with the firmware I've been using. I have not made ANY recent changes to the phone whatsoever, so I can hardly believe it would be my fault.
Now, my question is; how do I fix this without wiping all data and installing a clean ROM? I have a lot of stuff in the internal storage I can't afford to lose, and it's really important to me. A full wipe of all data would not be ideal. I can access recovery mode.
Thanks in advance, and I apologise if this is in the wrong forum!
You might want to ask to the rom thread for some help or ask in this section,
Galaxy Ace S5830 Q&A, Help & Troubleshooting
Anyway, I will try to help. If your custom recovery is support backup and restore (and advanced restore) your rom (check your custom recovery thread), try to backup your phone rom for now, so you could restore it back when solution not working.
Try to reflash the rom again without wipe data and reboot. If still in bootloop try to wipe data and reboot, see if that phone still bootloop.
If phone is successfully boot, go back to recovery and go to advanced restore, restore only data and then reboot. If still not working, then just full restore back to the phone to state before since I have no idea anymore.
That is the option I only know for now. However, try to ask help on section I link above or the rom thread before try this one, since I only familiar with Galaxy Gio (really similar to Ace) in the past.
I tried what you suggested but no positive results, really. I managed to boot after a full wipe, but restoring data locked it back into a bootloop. I'll try posting it in the other section.
Thanks.
Related
I am trying to flash into this custom ROM http://forum.xda-developers.com/showthread.php?t=1766999 on my ATT galaxy s3... the first times i tried it it hung indefinitely at the updating android applicatoins screen after installing.. I was successfully able to restore from my nandroid fortunately.
The third time, I booted into the OS but it started hanging when i was signing into my google account and never let me open any applications. Then when I reboot it it just hung at the samsung screen forever.
I don't know what im doing wrong, I am clearing data and cache and then flashing from the SD drive then rebooting. Am I the only one having this problem? Should I try another rom and see if that works?
This is my first time flashing a ROM
theraker007 said:
I am trying to flash into this custom ROM http://forum.xda-developers.com/showthread.php?t=1766999 on my ATT galaxy s3... the first times i tried it it hung indefinitely at the updating android applicatoins screen after installing.. I was successfully able to restore from my nandroid fortunately.
The third time, I booted into the OS but it started hanging when i was signing into my google account and never let me open any applications. Then when I reboot it it just hung at the samsung screen forever.
I don't know what im doing wrong, I am clearing data and cache and then flashing from the SD drive then rebooting. Am I the only one having this problem? Should I try another rom and see if that works?
This is my first time flashing a ROM
Click to expand...
Click to collapse
i would restore my nandroid and see if all is well, if so, try a wipe of cache, dalvic cache, and factory reset, then try flashing the rom, if that fails too, try a different rom.
It seems based on the official thread that many users experienced the same problem flashing to 4.0 from stock.. Have to go to 3.0 first and then 4.0 (see the thread I linked, last couple of pages)...
Posting it here in case I wasn't the only one who didn't read the whole thread.
Only recently, from today i have been experiencing stuck on boot screen problems with a rom, i wiped cache and dalvik, even changed kernel but still stuck, so i wiped data and flashed a new rom. I wiped everything, the first boot worked, i installed my apps then i wanted to flash a file so i rebooted, however my device got stuck on boot screen again. It is always stuck on the Galaxy s 2 screen and every rom i use, if i reboot it will get stuck!!! Im not sure what the problem is and im getting very nervous now. Can somebody please help me or at least tell me what is happening? Thank you
I was using the latest NeatRom Lite when the first bootscreen happened, so i switched to Wanam and now same problem, i even tried booting without my sd card, but still cant boot!
Why on earth did you title your topics as nothing more then "Please Help!!!!" ??
Topic titles are supposed to be descriptive (NOT GENERIC) so that people browsing forum can see what topics are about. Your likely to get less page views and hence less likely to get help if you dont use common sense and title topics correctly.
Try a kernel cleaning script.
Try a rom cleaning script.
Try re-stocking via odin.
Hey guys, had a Note for a little while now and was running stock AT&T GB. I tried upgrading to ICS a couple of times using other threads in this forum, but I'd keep getting stuck in a boot loop and had to revert back to stock AT&T GB to recover my device per Da_G's method here: http://forum.xda-developers.com/showthread.php?t=1506330, and it worked fine.
However, I recently tried one more time to upgrade to ICS, failed and reverted back to stock AT&T GB per Da_G's method, and while my phone turns on, it has become sluggish to the point of being absolutely unusable. Screen touches work fine in some cases, and then take forever to register in the same spot later. The on screen keyboard cannot be invoked - it almost always hangs the phone. And the phone randomly reboots.
I did forget to wipe cache and dalvik cache the last time around while doing the install, and that probably caused this problem. But sine then I've wiped both caches and retried flashing, and also reinstalled a stock AT&T radio in case that was the problem, and also reset the flash counter per braway's methode here: http://forum.xda-developers.com/showthread.php?t=1569206, but to no avail...
My Note is pretty much useless at this time, so any light you guys can shed or any other tack you can suggest is going to help me immensely!
Thanks for the help!
Sid.
Wiping caches is not enough. You need to to a full data wipe/factory reset. At this point why not just flash your phone with Odin.
http://www.samsdroid.com/2012/07/i717uclf6-android-404-usa-at-stock-rom.html
This will fully wipe your phone and install the UCLF6 ICS ROM with matching radio.
Agoattamer said:
Wiping caches is not enough. You need to to a full data wipe/factory reset. At this point why not just flash your phone with Odin.
Click to expand...
Click to collapse
Sorry, I didn't mention - I DID do a factory wipe/data reset and I've been flashing the stock GB ROM via ODIN itself. But thanks for the link to the ICS ROM - I'll try installing this and report back.
Okay, I downloaded the UCLF6 ROM from the samsdroid site (took like 3 hours to download!), performed several factory data resets, cache wipes and dalvik cache wipes on my phone, and then flashed the ICS ROM via Odin. Odin showed "Passed", but the phone rebooted into recovery with a message "failed to mount /system" and "failed to mount /data". I then hit "reboot system now" and am stuck at boot loop. Booted back into recovery, got the same message about not being able to mount system and data. Hit "reboot system" again and back to boot loop...
What the heck am I doing wrong???
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
You do have an ATT i717 and not a canadian version? But I think your phone has other issues.
It is an AT&T SGH-i717. I've used it for 6 months now and it worked fine - it just never let me upgrade it to anything beyond GB... and now it is unusable even with GB.
Do you think it might be a hardware issue? Although, how could flashing and reflashing ROMs impact the hardware?
If the odin flashing did not straighten things out then I have to believe that there are other issues.
sid.asu said:
It is an AT&T SGH-i717. I've used it for 6 months now and it worked fine - it just never let me upgrade it to anything beyond GB... and now it is unusable even with GB.
Do you think it might be a hardware issue? Although, how could flashing and reflashing ROMs impact the hardware?
Click to expand...
Click to collapse
Did you try to flash ICS with Samsung Kies? If that doesn't work, your phone may have developed a hardware problem.
i have had the same issues as well, i am unsure if its me or what but everytime i have tried to flash a tmobile rom on my note which should work it slows down to a crawl i cannot even go through the setup process. I have tried via odin and through cwm touch. the next thing i flashed was t879uvlg3 modem and i was wondering if that was the issue and if so what modem should i flash that way i dont have to use kies for recovery cause man..........thats slow. I even made a nandroid backup and it was slow as well so if anyone has had this issue or any ideas please help me
oort cloud said:
Did you try to flash ICS with Samsung Kies? If that doesn't work, your phone may have developed a hardware problem.
Click to expand...
Click to collapse
My problem is that the phone does not stay on long enough for Kies to detect it - it keeps rebooting on GB. Well, guess it's cooked! Thanks for the help!
Hi,
i recently installed CM on my samsung s3 using the installer. All went all. Until after about 2 weeks, the phone was not charging correctly. So i went into the settings and performed a factory reset. No i had not installed or used clockworks to back up my phone. This left my phone in an unusaul state, where there was no home screen, i could not access my apps, although i could access the quick settings tab. Moving on....i followed a guide to try and restore my phones orginal rom using odin. According to odin all was successful, however my phone was stuck in a boot loop and so would not continue into phone. i read up and saw if i installed clockwork i could wipe cache and this might help the phone. so i installed clockwork using odin again. however when i try and access clockwork through the recovery mode, it only loads into odin mode? so i am unable to load clockwork as well i think. I am very new and this and i know i have probably made many mistakes but we learn through our mistakes. So my question is: Could someone please help me get my phone back to its orginal state!? Thankyou very much for anyone that can offer their time and help,
Nick
This May Help You
nick140795 said:
Hi,
i recently installed CM on my samsung s3 using the installer. All went all. Until after about 2 weeks, the phone was not charging correctly. So i went into the settings and performed a factory reset. No i had not installed or used clockworks to back up my phone. This left my phone in an unusaul state, where there was no home screen, i could not access my apps, although i could access the quick settings tab. Moving on....i followed a guide to try and restore my phones orginal rom using odin. According to odin all was successful, however my phone was stuck in a boot loop and so would not continue into phone. i read up and saw if i installed clockwork i could wipe cache and this might help the phone. so i installed clockwork using odin again. however when i try and access clockwork through the recovery mode, it only loads into odin mode? so i am unable to load clockwork as well i think. I am very new and this and i know i have probably made many mistakes but we learn through our mistakes. So my question is: Could someone please help me get my phone back to its orginal state!? Thankyou very much for anyone that can offer their time and help,
Nick
Click to expand...
Click to collapse
This link may help you. fix-s3-to-factory-unroot-stock-recovery-t2323847. Do it at your on risk.
Galaxy S II GT-i9100 was running on OXYGEN for a while (don't even remember the exact version). Now stuck at boot screen (green "flickering OXYGEN" screen, for those who are familiar with this ROM) after a routine battery change. Can boot into recovery fine, but recent backup was done long time ago... so looking for a solution with minimum data loss. Did anybody run into anything like this before?
I'm not sure if the problem is phone or ROM specific, but posting it here first anyway. Could be a general Android problem/solution, I guess...
Would appreciate any advice or references! Can help?
stuck at boot screen, OXYGEN, worked before, broke after a while, GT-i9100
The only things you can try other than a factory reset are:-
*A dirty flash of the rom you're running (unlikely to work, but try it anyway)
*Flash a stock rom with Odin. No, this will not wipe your phone/cause data loss. This has a fair chance of working but you still might end up with bootloop after & need to do a factory reset regardless. In that case, you're losing data; no way around it.
... more details
Thanks for the quick and constructive advice, but after tinkering with it a bit more tonight, it's clear that the problem is with the "data", and not with the "system" or "boot" itself. I can get the phone to boot by recovering only the "'data" part of the previous backup, using the advanced recovery option in the CWM recovery. Also I can back up the "frozen" latest configuration and then restore it to reproduce the problem.
Any additional suggestions/ideas based on this? Could it be, for example, that SMS app or any other app crossed some kind of limit storing its data and cannot initialize anymore? Is there a way to "'repair" the data.tar file from the CWM backup?
Additional details:
CWM-based recovery v5.5.0.4
Android v4.0.4
Oxygen v3-20120501-SNAPSHOT-SGS2
kERNEL V3.0.30...