Fixing Boot loop on Samsung Galaxy S+ (GT-I9001) - Android Q&A, Help & Troubleshooting

Hello everyone. This is my first thread on this XDA and I hope if somebody could help me. First of all, I know this phone was released in 2011 and it is considered old and outdated but I could really aprreciate help. I checked many threads and Youtube guides (I considered only those with good rating) and spent total of approximately of 16 or more hours in order to fix this but none of them were good for my case.
So here's the problem. Problem appeared about 20 months ago. First, I installed CM 11 on phone and everything was working fine except for the front camera. Then I tried flashing back to Stock ROM which I've downloaded from SamMobile. I used Odin for both times. After process was over, my problem appeared. Every time I turned on the phone it didn't get past Samsung Galaxy S+ logo. So I figured out it was Boot loop and that it can be fixed. I just couldn't find the working way.
Here are things I've tried: 1) Flashing Stock ROM via Odin without wiping cache first
2) Flashing CM 12 via Odin without wiping cache first
3) Flashing CWM Recovery via Odin, wiping cache and then flashing Stock ROM via Odin
4) Putting phone in Download mode, connecting it to PC and running Kies (Kies couldn't connect the phone because device wasn't responding)
From above mentioned only number 3 partially worked. CWM installed correctly but after I flashed Stock ROM I got same Boot loop problem again.

Related

[Q] TWRP bootloop

While I did find a similar posts, they were for different devices. I also tryed to search o different sites for similar problems to no avial.
What Happened: After backing up system data and app data then removing Foxhound ROM with factory reset, and installing UltimaROM i came to find that the modem did not install correctly result in no connection to my cell network. I booted into TWRP recovery to try and do a re-install of the ROM only to find that TWRP was restarting itself every 3 seconds or so. I attempted to restart the device which i found to result in a TWRP bootloop that i cannot get out of, it constantly is booting into recovery mode and i cannot get it restart the OS.
What I've tried: Since i can get into download mode i decided to attempt to re-install TWRP using Samsung Galaxy S3 Toolkit but since i do not have USB debugging on i cannot do that. I'm mainly looking for a fix before i go and claim it on the warranty saying update went bad or something. If people need more information I will try to provide it as best i can.
Summery if i confused people is that TWRP is in a bootloop, i am unable to get to the OS, but i still have download mode available.
I fixed it but not how I would have liked to. I ended up losing all data due to flashing stock ROM using ODIN. I would still much appreciate a alternative method that does not involve loss of data though just for future reference, that is if anyone knows a alternative method.
Sent from my GT-I9300 using xda app-developers app
could've tried reflashing TWRP or any other recovery through odin
I have an LG Optimus Q (LGL55c) with twrp loop. I was trying to go back to stock rom, instead I deleted all the system files in twrp when it was working...Then I rebooted back into recovery and get the loop. Does this mean I completely bricked my phone? I tried using adb, adb shell doesn't work. It does find the device. Even tried the LG update with no sucess Any ideas or suggestions?
I just read the forum title, I thought this was for the Optimus Q not the Samsung S3. Sorry mods
Temasek unofficial cm12 5.02
I was running this rom when my power button shorted and I got it replaced but then I tried to do a complete wipe and clean flash but since then it has been twrp bootlooping, tried to flash the latest recovery through Odin but still doesn't work also tried stock firmware flash but says binary not available.
This is my secondary device and I've not been in touch with Odin for a while. Any help will be appreciated.
Thanks
Download latest firnware from sammobile.com and flash it with Odin, as described on sammobile: does Odin finish with '1 succeeded'?
I'm in a very similar situation, but with my Samsung Galaxy Note 2 (N7105). It's rooted, and I am, or was using TWRP 2.7.0.2. ROM is CyanogenMod 12, 5.0.2 Lollipop.
I did a factory reset from INSIDE Android, and chose to wipe internal memory. Phone did the reset and wipe, rebooted into TWRP instead of Android, and now I have TWRP boot loop.
I posted more about it here: http://forum.xda-developers.com/showpost.php?p=60247503&postcount=3671
I have the Problem toooo!
What must i do Now!
with my S3 is the same!!!
For posterity:
With an old (2014?) version of TWRP and a custom ROM, I tried reverting to factory settings. That caused the phone to reboot TWRP, and the screen would flash every couple of seconds. I flashed a stock recovery image I found on Google, and when it restarted again, the wipe was completed successfully. My intention was to wipe all user data anyways so I can't say if this method might save it.

[Q] SGT-P7500 3G Doesn't boot anymore -err:0x4

This morning as took my tablet the screen did not switch on, i tried to reboot then it stuck on bootanimation, then i tried to wipe; it still stuck on
bootanimation. Next I tried a complete wipe and installed a new Rom --> same Problem only goes to the bootanimation.
Then I tried to flash with odin, it tells me "complete write operation failed" and err:0x4. Nvflash isn't working too. So what can I do. I was on CM 10.1 nightly before, and evertything worked very well till this morning. I still can go to Download mode but twrp is not working anymore.
Thanks in advance in sorry about my poor english.
Regards.
Maybe the last edit will give you a hint:
http://forum.xda-developers.com/showthread.php?t=1276873
@dvb127 This morning the same happend to my Tablet. Could you find a way to fix it?
I have been running a CM-Version of january and switched to nightlies a couple of days ago. I can't remember anything else I changed
What I tried: flashed a new version of CWM (6.0.3.2) via ODIN and installed the january & newest CM via CWM. Both worked fine.
Still the same problem. When I boot the tablet it reboots several times and gets stuck in the CM bootanimation. Factoryreset and wiping /data causes a reboot.
NetZwerg said:
@dvb127 This morning the same happend to my Tablet. Could you find a way to fix it?
I have been running a CM-Version of january and switched to nightlies a couple of days ago. I can't remember anything else I changed
What I tried: flashed a new version of CWM (6.0.3.2) via ODIN and installed the january & newest CM via CWM. Both worked fine.
Still the same problem. When I boot the tablet it reboots several times and gets stuck in the CM bootanimation. Factoryreset and wiping /data causes a reboot.
Click to expand...
Click to collapse
I flashed a Stock Rom with Odin first, i had to too this in a win XP PC, because it didn't work in win8, rooted again, now I'm in cm again without any pproblems.
Hey, thanks a lot - worked for me as well

[Q] Bootloop after flashing CWM Touch, DL Mode working only

Hi there,
I got my SGS3 on Friday, it took two hours until I got bored and rooted it.
First everything was fine, I was using CWM (installed via ROM Manager) and tried some ROMS.
Today, when I wanted to flash CWM Touch via ROM Manager, the phone rebooted and since then in stuck in a boot loop.
There was no error during the process, according to ROM Manager the recovery was properly flashed. All I can do is entering the Download Mode.
I tried to flash two different stock images via ODIN3 (v3.07) but the phone keeps rebooting, even when i try to repartition it using "GT-I9300_mx_20120329.pit". I can boot the phone into recovery, I can see the recovery for a short moment and then the phone reboots. I made it to flash CWM 6.0.3.1 via ODIN, and when booting into recovery then I can see that it worked, but after a second the phone reboots.
Currently I'm downloading a 3-part/3-files factory image, hoping this can help. According to what I've read on the forums so far I don't think it will change anything, but who knows... Any other suggestions?
Greetz
// j_dee
rom manager is not supported on all the phones. probably that should have damaged your phone. hope you get your phone working. good luck :good:
I was using CWM (installed via ROM Manager)
Remove rom manager .
CWM says
Not compatible with ROM Manager !
That is if you recover from damaged pit .
jje
Hey guys,
thanks so far... According to the CWM homepage the SGS3 is supported, in fact there's current even a newer CWM version available for SGS3 than for GNEX.
Fortunatly I just made it to un-soft-brick the device:
- Removed the battery for a few minutes, then placed it back in the phone (for some reason the phone often booted as soon as the battery was back in its place, so I had to be quick).
- Tried to reboot into recovery again, holding "Vol+"+"Home"+"Power" until the recovery showed up, and the phone rebooted.
- Kept on holding "Vol+"+"Home"+"Power" until recovery showed up again, for some reason the phone didn't reboot this time, and then I released all buttons.
- Thanks to ODIN I could now use CWM 6.0.3.1 to flash S4 Revolution (by Elegant Team) from my internal storage, rebooted the phone and it worked. All my data was still in place, so it seems all my attempts to flash the stock images via ODIN did not succeed, save for the stock recovery.
Crap, I was really afraid of having my brand-new SGS3 hard-bricked only a few days after delivery. With my HTC Desire HD it took me almost 6 months to cause the first almost-brick.
There's only one thing I can image with ms SGS3 that might have affected the CWM / ROM Manager flash - I was running a S4-ported ROM ("S4 Revolution"), because this makes "TriangleAway" recognize it as "I9500" phone, so I cannot reset the counter at the moment.
But ROM Manager always showed "GT-I9300"... So in the end I've no clue what has happened so far.
Greetz
// j_dee
don't use rom manager

[Q] Samsung XCover 2 always boots in recovery

Hello!
I have a Samsung XCover 2 (GT-S7710) and I've tried to flash a CM-Rom for quite a while, but without success. At some point my phone stopped to boot a single rom I installed. It automatically starts into CWM Recovery, even with my backup (made with cwm). I thought cwm could be the bad guy and I flashed the Stock Rom with Odin, but same problem here. In Odin everything is fine but again it starts in recovery automatically.
I've read that the bootloader could be the problem and you need to flash it with Odin, but I don't know which one to take, since all treads were about other phones.
Does anyone know which bootloader I have to take or if there is another solution?
Greetings!

Samsung s3 gti9300 briked

Hello everybody
My samsung galaxy s3 gti-9300 past away a few weeks ago.
Everything was working fine the last 3 years (with the official rom, and only a few programs installed) till one day (few weeks ago) random services stared to crash and also some restarts occurred.
I did some restores but nothing changed. After that I started installing custom roms using clockworkmod v6. Every rom continued the problem with random services crashing for a day or two and then the phone restarted in a boot loop.
After three roms tested now clockworkmod cannot install a new rom. It cannot mount cache / recovery dir and also it cannot format it. I've also reinstalled clockworkmod but nothing changed. At first I was using an older version of clockworkmod and then I installed the v6. Other than that clockworkmod is still running fine.
Odin also fails to install anything to the phone. I' ve tested a lot of odin's versions. At the beginning odin was able to install the clockworkmod but now (after the rom's testing) it cannot install anything (pit, bootloader,rom) although the phone enters downloading mode.
Any ideas?
Download stock firmware from sammobile.com flash it via odin
Sureshtuty said:
Download stock firmware from sammobile.com flash it via odin
Click to expand...
Click to collapse
I've tried that (via odin/ pda button) but odin fails after NAND step......
[email protected] said:
I've tried that (via odin/ pda button) but odin fails after NAND step......
Click to expand...
Click to collapse
I still have the same problem. Any help??

Categories

Resources