[Q] [i9000] Stuck in boot loop on GB, Encryption Unsuccessful on ICS - Galaxy S I9000 Q&A, Help & Troubleshooting

After having to restart my SGS I9000 more and more often, I decided to have a go with cyanogenmod. I installed v9 fine, and it booted properly. However after I restarted it (I can't remember why), I got the Encryption Unsuccessful screen...
I tried the various fixes to this, including swaping the sd card / emmc - no luck. So I decided to flash back to stock GB. When I tried that, I just get it stuck in a boot loop (cycle of Galaxy S screen for ~ 5s, then blank for ~5secs). When I tried CM7, it just sits there spinning the boot screen.
I've tried various options, and just get stuck at either boot loop, or encryption unsuccessful.
In the recovery manager I always get 'can't mount /data' or similar - but can normally manually format /data.
I don't have any trouble getting in to d/l mode, or recovery mode, and have been using Heimdall to flash updates.
I'm thinking I have some hardware problem - I can't understand why I just can't get it to boot anything...
Any suggestions on what I can try? When searching for options, I normally see 'Flash it back to stock' but that isn't working for me...
(Before I had all this trouble, my phone would often boot loop about 5 to 10 times before finally booting.)

rerrnated the
Did you Try flashing Sock ROM ( 3 files) with Odin ? Do this .

Yes, I have tried that - same result as with Heimdall - just boot loops

Related

[Q] [SOLVED (by myself)]Did I just trash my phone?

So I flashed a recovery from terminal emulator, pressed reboot to recovery, the phone showed blank black screen, shut down and it kept on doing this for a loooong time.
After that I tried download mode, but it's stuck at setup connection. Any things I can still try before JIG/JTAG?
EDIT: The panic was bigger than the problem. Pulled out SIM, SD card, tried to boot it, it displayed a logo showing that there is a problem with the connection to the PC, then I booted to download mode and flashed a 4 package ROM, as it can override the boot thingy. So it's all good now.

Samsung logo boot loop, totally stuck

Hey guys, my phone got totally stuck on a Samsung logo (neverending loop).
Yesterday I let my bro play an Angry Birds on my phone. After a while I took my phone back and to my surprise it wasn't responding. Mobile was turned on (connected to the charger) but all I could see was a black screen. I tried restarting my phone by removing battery but it didn't help at all. I got stuck at Cyanogen Mod logo everytime. Since I haven't updated my firmware in a while I decided to intstall the newest version of CM (KitKat 4.4.4 from novafusion.pl) using Odin app. After a successful installation my phone still didn't boot up, I was getting stuck on a blue CM logo. After this I wanted to wipe my cache/dalvik cache but I wasn't able to get into recovery mode (getting stuck on a TeamWin screen). Reinstalling TWRP and installing ClockWork recovery didn't have any effect. I wiped my phone using .tar file found on this forums, tried reinstalling my ROM recovery many times, tried installing param file (don't even know what's that) and resetting three button combination using Benzonat0r's mod. None of these things seemed to have any impact. I'm still not able to get into recovery neither boot my phone up - Samsung logo bootloop. What am I supposed to do to unbrick my phone?
On a side note my knowledge about Android phones is tiny so please consider this. Also forgive me my poor grammar, not a native English speaker here.
Guskax said:
Hey guys, my phone got totally stuck on a Samsung logo (neverending loop).
Yesterday I let my bro play an Angry Birds on my phone. After a while I took my phone back and to my surprise it wasn't responding. Mobile was turned on (connected to the charger) but all I could see was a black screen. I tried restarting my phone by removing battery but it didn't help at all. I got stuck at Cyanogen Mod logo everytime. Since I haven't updated my firmware in a while I decided to intstall the newest version of CM (KitKat 4.4.4 from novafusion.pl) using Odin app. After a successful installation my phone still didn't boot up, I was getting stuck on a blue CM logo. After this I wanted to wipe my cache/dalvik cache but I wasn't able to get into recovery mode (getting stuck on a TeamWin screen). Reinstalling TWRP and installing ClockWork recovery didn't have any effect. I wiped my phone using .tar file found on this forums, tried reinstalling my ROM recovery many times, tried installing param file (don't even know what's that) and resetting three button combination using Benzonat0r's mod. None of these things seemed to have any impact. I'm still not able to get into recovery neither boot my phone up - Samsung logo bootloop. What am I supposed to do to unbrick my phone?
On a side note my knowledge about Android phones is tiny so please consider this. Also forgive me my poor grammar, not a native English speaker here.
Click to expand...
Click to collapse
Download This rom "I8190 серв. укр.rar" from here
Unpack .rar and open Odin.
Select the goldenxx.pit to [PIT]
Select CODE_I8190XXAMA2_809600_REV00_user_low_ship.tar.md 5 to [PDA]
Select CSC_QXE_I8190QXEAMA1_20130109.163004_REV00_user_lo w_ship.tar.md5 to [CSC]
Put your phone in download-mode and connect it to computer.
Hit [Start] when device is detected by Odin.
You will end up with a "La'Fleur" branded phone, but no worries!
Just go to download mode again and flash a custom recovery and after that a ROM of your choice.
The three button combo will still work!!
This is not my work, give my friend @tyson a thanks for that!
I tried installing stock recovery and ROM. After completed installation I finally managed to pass Samsung screen. I got to the something like Android installation screen and my phone suddenly shut down. Now it's totally bricked, I can't turn it on nor get into the download mode. Charging progress doesn't show up while phone is plugged in neither. Any help?
moonryder said:
Download This rom "I8190 серв. укр.rar" from
Unpack .rar and open Odin.
Select the goldenxx.pit to [PIT]
Select CODE_I8190XXAMA2_809600_REV00_user_low_ship.tar.md 5 to [PDA]
Select CSC_QXE_I8190QXEAMA1_20130109.163004_REV00_user_lo w_ship.tar.md5 to [CSC]
Put your phone in download-mode and connect it to computer.
Hit [Start] when device is detected by Odin.
You will end up with a "La'Fleur" branded phone, but no worries!
Just go to download mode again and flash a custom recovery and after that a ROM of your choice.
The three button combo will still work!!
This is not my work, give my friend @tyson a thanks for that!
Click to expand...
Click to collapse
Hey dude, I wish I saw your reply earlier. If my phone wasn't bricked now I'd give it a shot.

[Q] Milestone 1 - can't boot after the installation

Hi guys, I'll try to explain my problem:
My Milestone has been running the rom "cm-7.2.4e-umts_sholes" since two years without issues... until a few days ago: aleatory restarts and freezes. Yesterday, I turned it on and was stuck on "M" logo. Several restarts later, it shows the "2ndBoot - Kernel Restart in progress" logo and nothing else.
I tried to reflash the rom and encountered some issues:
Bootloader 90.73, I flashed the vulnerable recovery "vulnerable_recovery_only_RAMDLD90_78.sbf" and enter in recovery stock. When I tried to run the "OpenRecovery_2ndbootOR_v1_2" the OR doesn't start at all. Black screen, restarts and recovery stock again. Only the "OpenRecovery_v1_46_SHOLS_inkl_ext_mmcfix_parted_update" does the trick and starts the OR with red letters. After all the obligatory wipes, applied update from "cm-7.2.4e-umts_sholes" and then reboot system. And the same "M" stuck or "2ndboot" stuck screen. I tried wipes again, but no results.
So, I tried to go back to an earlier version and installed "SHLA_U2_02.02.0_USASHLSPERARLA017.0R_USASHLSPERARLAT_P037_A015_HWp2a_1FF" with RDSLite. It boots up Android BUT the touchscreen not works at all, even with several reboots. Tried to reflash Cyanogenmod from here, but the same issues above listed appears.
I really going crazy with this... Did I make some mistake at any point? Must I reflash the bootloader 90.73 if I found it? (besides all the webs containing all the .sbf's and bootloaders appears to be offline by now).
Any solution/advice you can give me please?
Thanks in advance and sorry my english, isn't my first language.

[Q] Possible partition corruption?

Here's the deal, I have a sprout8 device (the Indonesian Nexian Journey One) running stock 6.0 with some xposed mods installed on it. Suddenly the device shuts down and when I try to boot it up it only goes halfway through the bootanimation when it shuts down again. I wasn't too worried as I thought it was just a conflicting system issue and I also thought it was time to re-flash fresh stock 6.0 to freshen up my phone anyway. So I went ahead and did it.
Here's where the problems start to show up, I had a hard time booting to recovery through the power + volume up combination. The phone suddenly shuts down on its own as it boots up. I tried it a few times and finally got to recovery. After that, as I flashed stock 6.0 the phone shut down again. I thought it was an issue with my recovery so I tried wiping everything through fastboot and re-flashed recovery through fastboot aswell. From there I tried again to flash stock 6.0 through recovery and again, the phone shut down. I tried a different ROM thinking it was a ROM issue but still got the same results.
After hours of trying to flash a ROM through recovery (retrying over and over as it suddenly shut down while flashing), I finally got a ROM installed. Then I rebooted my phone, but again it freezes halfway through the bootanimation (literally freezing the bootanimation) and refused to do anything. I took off the battery and booted up the phone countless tries trying to get it to boot up. When it finally booted up, I filled in all the Google startup credentials and finally got started on a fresh stock 6.0. However, I tried to restore my previous application data through Android's application recovery on startup but everytime the device installs a new application it would freeze up and shut down. This happened countless times. Then the phone, once again, shut down and could not start the ROM. It would freeze up on the bootanimation.
Then things started to get weird, when the phone turns on it should show the "Nexian" logo in all its glory before going to bootanimation. But here the screen gets all distorted and shows these weird horizontal (and sometimes vertical) lines. Nothing's wrong with my phone screen so I assume it is a system error. From here on, the phone refused to boot. It just shows the Nexian logo and restarts over and over. The same thing happens even after I re-flashed both my recovery and ROM. I even tried using SP Flash Tool to re-flash stock but still the same results.
Now, the device wouldn't even turn on. But when I connect it using USB to a Windows computer, it still gets detected through device manager as an ordinary MediaTek device.
I'm assuming now that it may be a problem with the /system parition where we install our ROMs in. The partition may be (partially) corrupt. Seeing as the device could still boot the ROM a few hours ago but freezing upon updates to the stated partition.
If you guys have any other ideas/solutions I'm all ears.

Nook HD (hummingbird) stuck in boot loop after botched ROM install

Several times, I tried (and failed) at installing CM on my Nook HD. It went through all of the motions of installing the ROM (no errors, nothing), but when I rebooted, it went straight back to stock with "Hi, welcome to your NOOK."
I thought maybe my version of CWM was too old. I finally found a newer version (6.0.4.9, I think). I flashed TWRP first and then tried to flash CM. This time it crashed in the middle of the installation! Now, it won't boot at all. It just shows the Nook logo, then goes to the Cyanoboot screen, then goes black, then back to Cyanoboot, and so on. It won't boot from the SD card, either. I tried holding N and power to get into TWRP, which was allegedly installed, but that doesn't work, either.
Every web page that I could find discussing the issue of bootloops says, "First, boot into recovery..."
So, what do I do if I can't boot into recovery? Or is there a way I haven't tried yet?
Okay, I was able to restore. I inserted a bootable SD card and held down the N key and the power button. It takes a few times to get it right. So, now I'm back to stock.

Categories

Resources