Saving phone from being stuck at ROM boot animation - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi everyone,
I'm using ICS333 ROM.
Yesterday I installed an app (it was XMBC for android), and it gave me an FC. So I restarted hoping that will fix it.
What it did was getting me stuck at ROM boot animation. I managed to reflash the ROM and it worked, but then, downloaded that app again (thought that maybe it did not work because I changed my DPI). I then tried to reflash the ROM again but this time the phone did not boot.
I tried flashing Devil kernel and using the Aroma file manager to delete the app's apk from the folder /data/app but this did not work.
Fourtently I had a nandroid backup which I restored, though I wanted to avoid it because it was somewhat old.
What I wanted to ask is, if there was something else I could have done, so that if it happens again I would be smarter in the future.
Thank you.

I forgot to mention - I also tried accessing safe mode but without success. Has anyone succeeded in going into safe mode in ICS?

Related

[Q] Checking/ Verifying File System Health

My question is this: is there a way to verify that the file system and the overall ROM is operating healthy and without any corruptions/problems?
This is why I ask.
So, to make a long and frustrating story short I am/was running the Ginger Clone 2.2 Final R5 ROM and after disabling the lagfix, I installed the SpeedMod Captivate Kernal.
The installation of the kernal seemed to go just fine, after the initial startup I deleted the "disable-lagfix" folder/file and rebooted the device. However, when the phone restarted it froze on the "Galaxy S I9000" screen and would not boot into recovery mode.
After much profanity and futile ADB "reboot recovery" commands, I flashed the phone back to stock with Odin. When the phone loaded again I rooted and installed ROM manager, then I proceeded to restore the ROM backup that I made prior to flashing the new kernal. The backup loaded successfully, but when I started the phone again, it went into boot-loop at the AT&T screen.
Now at this point I'm really pissed off . I went back into recovery and cleared the partition cache and reinstalled the Ginger Clone Rom, fresh. Thankfully I heard the lady cyborg voice stating that the lagfix was being applied, success . The phone started up just fine, and I was able to reinstate the backup rom that I had created earlier.
So now, I'm left wondering if my file system is operating how it should be, sans kernal flash.
Thanks in advance for any and all help.
Again... I hate to be that guy but you are posting in the wrong forum.
Please read the stickies and the rules before you decide to post.
Sent from my GT-I9000 using XDA App
yogib83 said:
My question is this: is there a way to verify that the file system and the overall ROM is operating healthy and without any corruptions/problems?
This is why I ask.
So, to make a long and frustrating story short I am/was running the Ginger Clone 2.2 Final R5 ROM and after disabling the lagfix, I installed the SpeedMod Captivate Kernal.
The installation of the kernal seemed to go just fine, after the initial startup I deleted the "disable-lagfix" folder/file and rebooted the device. However, when the phone restarted it froze on the "Galaxy S I9000" screen and would not boot into recovery mode.
After much profanity and futile ADB "reboot recovery" commands, I flashed the phone back to stock with Odin. When the phone loaded again I rooted and installed ROM manager, then I proceeded to restore the ROM backup that I made prior to flashing the new kernal. The backup loaded successfully, but when I started the phone again, it went into boot-loop at the AT&T screen.
Now at this point I'm really pissed off . I went back into recovery and cleared the partition cache and reinstalled the Ginger Clone Rom, fresh. Thankfully I heard the lady cyborg voice stating that the lagfix was being applied, success . The phone started up just fine, and I was able to reinstate the backup rom that I had created earlier.
So now, I'm left wondering if my file system is operating how it should be, sans kernal flash.
Thanks in advance for any and all help.
Click to expand...
Click to collapse
Well when you flashed back to stock and then restored your backup it went into a boot loop because the backup does not back up the kernel so the ROM you restored was trying to boot with the stock AT&T kernel...Not going to work. But when you did the fresh install of the ROM it had the kernel so it worked...
try afv or something like that in the market. Its by scary alien and you can verify md5 sum nand backup. i just flashed a new rom but once I get all set up I will come back with the name. Its a free in the market.
Sent from my GT-I9000 using XDA App
jhernand1102 said:
Well when you flashed back to stock and then restored your backup it went into a boot loop because the backup does not back up the kernel so the ROM you restored was trying to boot with the stock AT&T kernel...Not going to work. But when you did the fresh install of the ROM it had the kernel so it worked...
Click to expand...
Click to collapse
Thank you good Sir! That makes perfect sense.
yogib83 said:
Thank you good Sir! That makes perfect sense.
Click to expand...
Click to collapse
No problem Glad to help. Next time if you flash stock after installing ROM manager you can flash the kernel first and then don't boot up just go back into CWM recovery and then restore your backed up ROM and it will work fine.

[Q] Stuck in Boot animation after installing seeARMS ROM

Hi, I have installed seeARMS ROM and followed his instuction. I have kept the JL2 modem and speedmod kernell (I was already on speedmod). I have tried 2 methods to install. The seeARMS.UGJL2.v0.4.zip with the seearms file and the CWM.
Both install went OK and I even had a congratulations screen. The problem is when the phone reboot it stays on the boot animation and get stuck there. I have tried 2 different boot animation and the same happen.
I have no problem to restore my data since I had backup but I would like to have the seearms ROM. Any idea?
Also a side question, can we get the new CK1 modem with seearms?
Richard
Have you been wiping your phone before flashing the rom? I have been having issues like you describe only when i flashed a rom w/o wiping.
(In CWM Recovery: wipe data/factory reset, wipe cache and advanced -> wipe dalvik cache)
No. I did not wipe. I am not interested in the new ROM if it mean wiping. I made a test by downloading a boot animation app. I trying 2 different boot animation and had the same result. The boot animation play with no sound but I have a vibration during boot and then nothing. Eventually it go back to the animation, vibrate and this repeat until I restore the backup.
I am wondering if tehre is something special about the Bell Canada boot animation?
Can I use the seearms without any boot animation folder?
I don't think it's a problem about the boot ani in particular.
I am not very familiar with the rom, since i have another device. In the seearms rom thread the dev mentioned two versions of the rom, one that requires wiping and one that does not.
So i guess it could be working out to flash the latter w/o wiping. But in my expirience those things rarely work out that way.
There might be incompabilities with the config data left behind by the rom installed before, or other possible issues.
Only way to be sure that those things aren't blocking anything is to wipe the phone and do a clean flash.
Personally i always do it that way. And if i like the rom, and choose to use it, it is always possible to get back all the apps and settings back with titanium backup and/or syncing them back.
But as always before wiping, if you choose to do so, please be sure to have a full nandroid backup, in case you want to go back, or something goes wrong.
I will try the wipe version
What rom were u on before seearms
Sent from my GT-I9000 using XDA Premium App
I was still on stock (froyo 2.2). Actually still on it today
You were right. The wipe version worked fine. I have now to decide to keep it or not...lol
ROM is awasome was worth well the trouble.
Glad it worked out for you - have fun with the rom
Sent from my Desire Z

Upgrade to ICS stuck in boot loop...

Trying to install the Cynogen ICS ROM, and when installing the .zip, it loads the Samsung flash screen with Cynogen, then get the green guy and loads of text for about half a second, then it just reboots. Over and over for about 10 mins. WHat went wrong? What should I do?
It happend the same to me.
I just removed the battery and put it back, entered in CWM and reinstalled the ROM.
Good luck!
I somehow got into a recovery mode, but with the assumption it would all go wrong again, tried to install the .zip Darky rom instead, went through the process and said it worked but then it just went back to the Cynogen loop problem!? I just tried a Restore instead, but I haven't rebooted yet, should I wipe everything again, and try the ICM .zip again?
Yep, just go with the whipe. I hope you did a backup.
OK turns out the Restore failed, so now trying to reinstall ICS .zip again. fingers crossed!
yep backed it up, not that its seems to have helped.
Well now it's stuck in the Galaxy S bootscreen...
that really sucks....did you deactivated the lagfix before running the rom?
If the problem persists you have to run a basic ROM using ODIN.
Yes deactivated the lagfixI can't get into recovery or anything now, except download mode.
Download mode is all you need to run a ROM with Odin.
I recommend Amestris, it is a good ROM, good battery life but the thread in not complete, there are some files missing...for now.
I've put some older ROM on I had, then tried to install ICS again but now when I use Clockwork, and select the file it goes to recovery but I can't select any zip files, just reboot back to this awful old ROM!
I had same issue when I installed ics, what I did that worked was pull battery and go back into cwm, reflashed ics zip and it fully installed that time. Had same experience when flashing cm7 before.
Not getting anywhere with this. I get an option to install zip from sdcard which is where the update is (an where the darky update also is which worked), but there is an option to update from internal SD, which is not where the file is. Is it in the wrong place?
I think you would be best to use Odin 1.3 to flash DarkyROM Ficeto JVT base rom.
are you sure those files are still on your sd card?
The reason you need to pull the battery and reflash the ICS rom a few times is because Samsung ROM (most) have a different partition layout to CM7 based roms (which the ICS port is one).
GL.

[Q] Bootloop Problem

Need your help guys. I'm currently on the Superbean Rom and it had been working brilliantly... until i screwed it up. Recently downloaded the new google keyboard and moved it to system/app and set permissions and all. But it has put my phone into an endless bootloop. Is there any way I can remove this app without having to do a wipe? Also i'm using Philz recovery.
Try flashing the same ROM again without a wipe and see if that helps.

Installed Xposed Framework zip, soft-bricked phone :(

Hey guys,
I know I know, I was stupid to try to get this working but I tried and failed. Now I'm just looking to get my old phone back and just leave it at being rooted (with custom recovery installed) and a custom rom. All 3 of these I had successfully done before I installed the framework zip which is where the problems arose.
I'll give you as much information as possible:
Phone: SM-G935F (UK version and on EE network)
Rooted with: CF-Auto-Root-hero2lte-hero2ltexx-smg935f
Custom Recovery flashed: twrp-3.0.2-2-hero2lte.img.tar
Other things flashed: UPDATE-SuperSU-v2.76-20160630161323.zip
no-verity-opt-encrypt.zip
Custom Rom flashed: KryxxOS-R1.3-G935F.zip
All of these were working and I should have stopped here but with the new Pokemon craze I really wanted Xposed installed to use the modules for it however massively regret it. I wish to get back to this point.
Zip used for Xposed: xposed-v86-sdk23-arm64.zip
Phone initially wouldn't do anything apart from show a battery (not charging (grey icon with lightening in it)) icon when connected to power. And it would ONLY do something when booting into download mode allowing me to go into it. It seemed the custom recovery was no longer working. I then tried everything, flashing back all Stock firmware for my model using ODIN and correct files for my phone (G935FXXU1APF2_G935FEVR1APE2_EVR), that didn't work. Even when installing only AP, all 4 using first HOME_CSC in the CSC and then using all 4 using the CSC file in the CSC. Then I tried using Smart Switch's recovery system, this failed also. Then I remembered hmmm, I can try to reflash my custom recovery using Odin. That WORKED. I thought great now I can do something and sure enough I could wipe my phone and access my files on my phone again when rebooted. After the reboot I tried just re-flashing the SU, the no-verify and the custom ROM thinking it would take me back. It still didn't boot. Black screen nothing. The last thing I attempted was to flash the Xposed Framework uninstaller and used this zip : xposed-uninstaller-20150831-arm64. I didn't know what this asci files were so I didn't flash them? After flashing the uninstaller, I again flashed SU, no-verify and the custom ROM. Nothing. Still nothing. However...whilst I was typing this, because my phone was connected to my PC and not stuck in DL mode or anything, it's now randomly come up with a battery charge. 3% so far but I want to wait until its higher before I risk trying to turn it on. Could it have been a dead battery all along whilst trying to fix?
I'd appreciate your help even if its to clarify that the battery seems to be the problem. I'll keep you posted with it throughout the night but if it gets sorted tonight it means I don't have to go into the city tomorrow to buy a fix. Thanks to all who post. Ask if you need anymore information.
Chris
hey, how did things go now, is it back to normal... rooted with TWRP and your custom ROM of choice ?
nexiros said:
Hey guys,
Chris
Click to expand...
Click to collapse
lol i know this is an old post but damn what a mess you are. you did just everything wrong. :laugh::laugh: hope everything is back working now

Categories

Resources