Boot loop - AT&T Samsung Galaxy S II SGH-I777

So I hate starting a new thread, but after searching for a day I have not been able to fix this issue.
I was running UnNamed v2.1.1 and wanted to update to the newest version. Following the instructions, I booted into CWM, wiped data/factory reset, installed the zip from my sd and rebooted. It worked fine, but I lost all my contacts which were on my SIM card (I was dumb and didn't back them up).
When I had previously updated I still had my contacts so I figured they should still be there. In an effort to find them I booted into CWM mode again and installed CM9 Nightly from my zip card. Again it booted fine, but still no contacts. I decided to go back again to UnNamed (wasn't a fan of CM9) and then I ran into issues.
My phone got stuck in the boot animation screen. I waited 20 min and nothing. Then I followed creepyncrawly's guide for returning to stock. My computer said "PASS" but when it rebooted it said "failed to mount /data (Unknown error: 0)". I turned off the phone and tried again and it seemed to work, but now my phone is still stuck in boot animation screen.
Any ideas how to fix this?

Reflash stock rom through Odin. But I would flash a cwm kernel through Odin, boot into recovery, and flash a rom.
Sent from my SGH-I777 using xda premium

supertwinkey said:
So I hate starting a new thread, but after searching for a day I have not been able to fix this issue.
I was running UnNamed v2.1.1 and wanted to update to the newest version. Following the instructions, I booted into CWM, wiped data/factory reset, installed the zip from my sd and rebooted. It worked fine, but I lost all my contacts which were on my SIM card (I was dumb and didn't back them up).
When I had previously updated I still had my contacts so I figured they should still be there. In an effort to find them I booted into CWM mode again and installed CM9 Nightly from my zip card. Again it booted fine, but still no contacts. I decided to go back again to UnNamed (wasn't a fan of CM9) and then I ran into issues.
My phone got stuck in the boot animation screen. I waited 20 min and nothing. Then I followed creepyncrawly's guide for returning to stock. My computer said "PASS" but when it rebooted it said "failed to mount /data (Unknown error: 0)". I turned off the phone and tried again and it seemed to work, but now my phone is still stuck in boot animation screen.
Any ideas how to fix this?
Click to expand...
Click to collapse
Don't know what is installed with cm9, or if flashing cm9 repartitions, but you can find bootloaders, param.lfs and PIT and complete stock UCKH7 packages in the Download Repository linked in my signature.
Troubleshooting without enough information is only a shot in the dark. I often see problems with param.lfs associated with boot loop. Your error message not being able to mount /data partition suggests PIT. Just some thoughts to start you on the way.

Finally fixed, thanks for the suggestions. After flashing the stock rom in Odin it still wasn't working. I was wiping factory/data before flashing, but for some reason when I wiped after flashing it worked fine.

Related

[Q] Please help newbie with semi-bricked phone

Hi guys, I got a SGS2 just over a week ago, on Bell/Virgin network in Canada. Suffered from the battery drain issue due to being stuck with crappy UGKG2 firmware which my provider still hasn't updated.
I decided to update it myself, and did a ton of research. I successfully got Root tonight by flashing CF-Root-SGS2_ZS-OZS_KG2-v4.1-CWM4 kernel with Odin. In case it matters, I did NOT flash back my stock Kernel, so I still had the insecure kernel installed. From there, I backed up my apps with Titanium.
Went into CWM and selected boot into CWM Recovery. I followed the steps on the wiki, including creating a backup file. My only hint of what I might have done wrong was I originally selected to flash update.zip, and that process failed. I then went to the directory in which cyanogenmod is stored on my SD card, and selected that, then it installed ok. I had downloaded update-cm-7.10-GalaxyS2-signed and that's what I put on the phone. I then also installed the Google Apps.
I then hit reboot, and it only goes to the Samsung screen with the yellow triangle and just hangs there for a few minutes. Not knowing what else to do, I popped the battery out. I have since learned that I can turn it on and off, but it never goes past that screen. Wouldn't go into the recovery or download modes, always that screen. Luckily, I saw somewhere to do the 3 button thing WHILE in that screen, and that works. So I can get to recover, and download modes. So, I think I'm ok. I checked, and it does connect to Odin still.
I just want to know EXACTLY what I should do at this point. I don't want to fully brick it. There are actually two recovery files on the phone... not sure why... Or which one to pick. Should I just flash stock firmware back with Odin? One of my main goals is to get off 2.3.3 so I can have more than 8 hours of battery...
Thanks,
Rob
Boot into tecovery, do a full wipe again. (Wipe data/factory reset, wipe cache partition, advanced>wipe dalvik cache).
Now install CM7 zip twice in a row without reboot. It may take a few minutes for reboot since system is rebuilding dalvik cache. Be patient. After you see the home screen, reboot again.
Sometimes, CM won't install properly with CF root recovery. In that case reboot into download mode, flash codeworkx cwm kernel via ODIN.
http://forum.xda-developers.com/showthread.php?t=1118693
Now reboot into recovery and do full wipe and twice-install !
Ok, working now with the flash twice thing. Well that's weird, would be great if it was in the wiki page...
Thanks!
Rob

Galaxy Player 4.0 Bricked

Hey XDA, I was hoping you could help me out here. I just don't know what to do anymore. So, here goes.
I decided to flash the Terrasilent kernal. All went well during installation. When I booted back into the stock rom after flashing my kernal, I saw that some system apps (gmail and market) were not installed. The icons were there, but they said they weren't installed. Also, all photos, videos, ect were gone. I already had them backed up, so no big deal. So, to try to fix it, I went into Odin and tried to reflash my stock rom through there. Everything worked fine, all was well. That's when I discovered my file system was messed up. Pretty much, it only displays /sdcard/Android, as well as /sdcard/DCIM/, /sdcard/LOST.DIR/ and /sdcard/external_sd/. So, I went ahead and attempted to reflash my kernal (custom kernal, terrasilent if you want to know.) to see if it would fix my ****. **** was not fixed, to say the least. And when Odin said it failed, I flipped out and did the stupidest thing imaginable; I unplugged my USB cable. So, I went and tried to boot up, and got the picture you get when you can't go into recovery, boot up or even download more. A cell phone connecting to a pc picture. So, then I tried following some guides on XDA to fix it, reflashed some stuff, and got close to fixing it. I reflashed my partition table and then tried to flash my terrasilent kernal once more, and it booted up into recovery with no issue. Btw, the kernal installs CWM recovery. But when I tried to reflash my stock rom, it didn't boot up. It said in Odin that it succeded, but in the recovery (which changed back to stock android recovery, I am not sure why) and I got a bunch of errors saying I'm missing all sorts of files. Like, E:failed to mount /cache (invalid argument) or E:copy_kernal_file :: Can't open /cache/recovery/recovery_kernal.log. XDA, please help me. I need this fixed, I can't afford to buy another phone, I'm broke. Help me.
DarkMuffin Inc said:
Hey XDA, I was hoping you could help me out here. I just don't know what to do anymore. So, here goes.
I decided to flash the Terrasilent kernal. All went well during installation. When I booted back into the stock rom after flashing my kernal, I saw that some system apps (gmail and market) were not installed. The icons were there, but they said they weren't installed. Also, all photos, videos, ect were gone. I already had them backed up, so no big deal. So, to try to fix it, I went into Odin and tried to reflash my stock rom through there. Everything worked fine, all was well. That's when I discovered my file system was messed up. Pretty much, it only displays /sdcard/Android, as well as /sdcard/DCIM/, /sdcard/LOST.DIR/ and /sdcard/external_sd/. So, I went ahead and attempted to reflash my kernal (custom kernal, terrasilent if you want to know.) to see if it would fix my ****. **** was not fixed, to say the least. And when Odin said it failed, I flipped out and did the stupidest thing imaginable; I unplugged my USB cable. So, I went and tried to boot up, and got the picture you get when you can't go into recovery, boot up or even download more. A cell phone connecting to a pc picture. So, then I tried following some guides on XDA to fix it, reflashed some stuff, and got close to fixing it. I reflashed my partition table and then tried to flash my terrasilent kernal once more, and it booted up into recovery with no issue. Btw, the kernal installs CWM recovery. But when I tried to reflash my stock rom, it didn't boot up. It said in Odin that it succeded, but in the recovery (which changed back to stock android recovery, I am not sure why) and I got a bunch of errors saying I'm missing all sorts of files. Like, E:failed to mount /cache (invalid argument) or E:copy_kernal_file :: Can't open /cache/recovery/recovery_kernal.log. XDA, please help me. I need this fixed, I can't afford to buy another phone, I'm broke. Help me.
Click to expand...
Click to collapse
I believe what you need to go is go into the android recovery by holding volume up + power. Once you get in there Wipe data/factory reset, and Wipe cache Partition because I believe it's bootlooping.
obscuresword said:
I believe what you need to go is go into the android recovery by holding volume up + power. Once you get in there Wipe data/factory reset, and Wipe cache Partition because I believe it's bootlooping.
Click to expand...
Click to collapse
It didn't work. What do I do now? I tried to flash the Terrasilent kernel over it (which came with CWM) and it gave me the CWM recovery and kernel, but still nothing works. I tried reflashing the rom too but I can't get it to boot, just download mode and recovery loads now.
DarkMuffin Inc said:
It didn't work. What do I do now? I tried to flash the Terrasilent kernel over it (which came with CWM) and it gave me the CWM recovery and kernel, but still nothing works. I tried reflashing the rom too but I can't get it to boot, just download mode and recovery loads now.
Click to expand...
Click to collapse
Well good thing is you're not hardbricked. Have you followed all these steps in this order?
http://forum.xda-developers.com/showpost.php?p=28849870
Do you have the 4.0 stock rom? (Don't use the one I linked since it's for the 5.0). Also did you try wiping the dalvick?
obscuresword said:
Well good thing is you're not hardbricked. Have you followed all these steps in this order?
http://forum.xda-developers.com/showpost.php?p=28849870
Do you have the 4.0 stock rom? (Don't use the one I linked since it's for the 5.0). Also did you try wiping the dalvick?
Click to expand...
Click to collapse
Yes, I followed all those steps perfectly. I have reflashed my stock rom multiple times before. And I have wiped dalvick cache when I was able to get into my CWM recovery a few times to no avail. My pc recognized the device just fine until today. I just flashed my .pit file and the terrasilent kernel through heimdall, and now my device isn't being read through Odin OR Heimdall. It is recognized by my pc but not by those programs. And yes I am in download mode. I also tried flashing back to stock before but the recovery just gave me a bunch of red text errors.
DarkMuffin Inc said:
Yes, I followed all those steps perfectly. I have reflashed my stock rom multiple times before. And I have wiped dalvick cache when I was able to get into my CWM recovery a few times to no avail. My pc recognized the device just fine until today. I just flashed my .pit file and the terrasilent kernel through heimdall, and now my device isn't being read through Odin OR Heimdall. It is recognized by my pc but not by those programs. And yes I am in download mode. I also tried flashing back to stock before but the recovery just gave me a bunch of red text errors.
Click to expand...
Click to collapse
I can't really see the photo, can you type out the error codes lol.

[Q] Bootloop help

well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
cdog1213 said:
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
Click to expand...
Click to collapse
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Jeffjb said:
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Click to expand...
Click to collapse
well I went to go try and boot P.A.C. and my phone just booted normally. So thanks for the help

stuck in bootloop

First off I am on mdk and rooted and up until today have been running hd 10.2. I had been having some weird things happen with twrp 2502 so I went into goo and tried to update to the newest version of twrp. it downloaded and went through with everything and I rebooted into recovery. once I got into recovery it was showing I was still on 2502, but it was asking for a password which I had never seen before. I backed out and tried to boot into my rom again and it got stuck on the samsung custom screen. pulled the battery a few times and still kept getting stuck. went back into recovery and tried to restore a known good backup that I had restored before, but it keeps failing. I had rls12 on my phone so I tried installing it dirty since I cant wipe anything due to the whole password thing in twrp which said it was succesful but still gets stuck on the samsung custom screen. it sits there for about 10 seconds and loops. I tried about 10 more times to get my backup restored and it finally finished and booted into the rom. I left it this way for an hour or so and did some stuff with my phone, tried to update twrp again which did the same thing again and still shows 2502. after the reboot I am back to the same problem of not being able to do anything in twrp except restore or dirty flash, I cant get the usb to mount in twrp so I cant try putting another rom on the phone unless I go and buy a micro sd adapter.
I am in the process of downloading a stock mdk rom to try and flash in odin, but is there anything I can try before I go through with this, or is it pretty much my only option.
after some more research I think I figured out what caused all this. I wiped the data partition with the old version of twrp which screwed it up pretty bad. Apparently the older versions of twrp were known to have this problem. I kept trying to restore, but trying to restore kept failing on the data partition. After about 25 attempts of trying to restore just the data partition I was able to get it to work finally, and then I restored the the others and got it to boot back into the rom. like an idiot I rebooted the phone back into recovery after it finished and had the same problem again. another couple hours wasted trying to restore the data partition and it worked again and this time i was able to get twrp to update and then went back to recovery and formated the data partition again and it seems to have fixed the problem. Now to figure out why hd rls 12 wont install.

Please help with this flusterc*ck of issues

Hi all,
New to this whole rooting and flashing thing. I'm not as good with computers that one can hold in their hand.
Anyways, I'll try to explain this stew of issues that I have
I'm running CW Recovery (6.0.2.3) in conjunction with SlimBean (dtt 4.2.2). One day, in a far away land, my phone prompted me to update Slim. That was all and dandy because I've flashed roms from zip files before. When I tried to do that, the process was aborted and I was given a slew of error numbers that made my brain hurt.
So, I tried to start fresh and clean, like the cilantro that chipotle puts in our burrito bowls. I tried a factory reset using the CW Recovery mode so I can re-root now that jellybean is 4.3. After I wiped the cache and data/factory reset, I rebooted the phone. My phone still boots into Slim and uses clockwork for recovery mode.
Essentially, how do I de-root my phone or factory reset it to the settings that I had from day 1?
UPDATE: I just tried flashing CW Recovery from 6.0.2.3 --> 6.0.4.7. After flashing it, I rebooted my phone into recovery. Now I'm getting a never-ending boot cycle. The samsung logo pops up along with the little blue text "recovery" at the top, then shuts off and repeats that every 3 seconds or so. Methinks I broke it
Thanks
Flash stock ROM via Odin. Download [URL="http://www.sammobile.com l" ] Sammobile [/URL]
Edit: better url
Why download a flight simulator?

Categories

Resources