Stuck in TWRP Boot Loop - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

What I was trying to do: I have a stock 4.4.2 AT&T GS3 that I wanted to root, and then install Cyanogen Mod.
What I did: I flashed Auto-Root with Odin 3.10, restarted and then flashed TWRP 2.8. I then booted to TWRP and attempted to wipe/format the phone but it showed some errors along the way, I think it was something having to do being unable to mount the SD card. I then rebooted into recovery and flashed CM12 and slim Google Apps zip. When it was flashing both I got a string of errors but it said it was successful.
Where I'm at now: When I try turning the phone on (without holding any buttons down) it attempts to boot straight to the TWRP but gets stuck at the blue TeamWin screen. I'm able to get to download mode by holding down the appropriate buttons. I'm wondering if there's anything I can flash from Odin to resolve this.
I also realized I have unbacked up photos on the device, I don't think the format was successful, is there any way to recover those?
Thanks

To recover the pictures, try re-installing TWRP, boot into TWRP, and mount the partitions. Connect the phone to your computer and copy your pictures.

TWRP
I have had this happen before. Try using Odin to flash an older version of TWRP, uncheck reboot after flash and then when it is done, do a battery pull. This has gotten me back into a working TWRP to restore my previous setup. Note: You made need to go back to 2.6. Once you have gotten back up and running flash to the current TWRP with the app.

Related

[Q] Recovery Stuck on Canadian Note 3 SM-9000W8

I have a real frustrating problem with my Canadian Rogers Note 3. I'm rooted and running CM11, but I was looking for a ROM that might be more stable than the nightly builds. I wanted to try a TW-based ROM so I downloaded BobCat, JediElite, and FireNote ROMs.
I copied the ROMs to the SD card, booted into CWM Recovery and tried flashing one of them (don't remember which). The installation seemed to go fine, no error messages or warnings. But when I finished and rebooted the phone just stopped at the Note 3 boot screen. No boot animation, no loading, nothing.
I went back to CWM Recovery, tried the other two ROMs, and got the exact same results. Then I tried flashing the stock Rogers Note 3 ROM. CWM refused to flash it and spat out some garbage about a corrupt zip file (re-downloaded it with the same results). I eventually gave up and restored the CM11 image I'd backed up.
At this point I began to reason maybe CWM wasn't suited to installing TW ROMs, so I decided I needed TWRP instead. Goog.Im and TWRP manager both refused to install TWRP however. So I dropped the TWRP Recovery zip on my SD card and tried flashing it using CWM.
Here’s where it gets really freaky. When my phone rebooted I got a "recovery booting" message, but the recovery never loaded. The screen just froze at the Note 3 logo. If I pulled the battery the phone would again display "recovery booting" and sit there endlessly. The only way I could break the cycle was booting to Download Mode, then exiting so it enters a normal ROM boot.
I let the phone boot up fully and then opened ROM Manager. It showed TWO recoveries installed, one CWM and one TWRP, apparently side by side. Is this even possible???
So anyway, I went back to playing around between ROM Manger, Goo.Im, and TWRP Manger, trying to re-flash it to either CWM or TWRP, but not both. Nothing worked; every time I tried booting to recovery the system would hang at the “recovery booting” message.
I eventually tired of this and decided to get out Odin. I flashed TWRP Recovery successfully (according to Odin), but it still won’t launch. I then tried flashing CWM Recovery with the same results.
So completely out of options, I tried flashing the stock Samsung Recovery. It boots just fine. So I try again flashing the custom recoveries, but they still refuse to launch. Each time I have to reinstall Samsung Recovery.
And that’s where I am currently: I have a (badly) working CM11 nightly ROM on my phone. I have the stock Samsung Recovery installed. I’m afraid to try flashing any zips using Samsung Recovery because my backup image was created using CWM, and if I can’t get CWM recovery to work I won’t be able to restore the backup.
Have I broken some law of the universe by trying to go from CWM to TWRP? Would TWRP work better with TouchWiz ROMs? And can I even install TouchWiz ROMs after hacking my phone to CM11 nightlies? Lastly, how can I get this $#@& Samsung Recovery off my beautiful phone and install a working custom recovery?

Recovery Fail!

So two days ago I thought about installing Vision X rom on my Note 3 (T Mobile).
I downloaded the ROM and then backed up my current ROM (nandroid). I had Phillz touch recovery then.
Then I thought about going to TWRP and thus I downloaded the latest zip for my phone and flashed it via Phillz upon trying to reboot into recovery it got stuck in the screen "Rebooting Recovery...".
When I restarted it would still try to reboot into recovery and get stuck. I got out of that by going into download mode and then selecting "Restart Phone".
After that I looked for solutions and upon failing to find any I thought about going back to stock and starting from ground zero. I managed to flash the latest stock using Odin however I forgot to do a factory reset before hand.
When I tried to do a factory reset in my, now stock, phone it failed and then got stuck trying to get into recovery. It would flash "Rebooting Recovery..." then restart and flash that in a loop.
I have lost my root as well in the process and trying to root using Odin and CF-Root just get's me back in the recovery boot loop. I can use the phone OK however this is not a stable situation.
I'm sure I've made some serious errors in the tinkering and would like to get my recovery back. I really love Custom Roms. Any kind and knowledgeable souls out there to help me in my cause?
kaif15 said:
So two days ago I thought about installing Vision X rom on my Note 3 (T Mobile).
I downloaded the ROM and then backed up my current ROM (nandroid). I had Phillz touch recovery then.
Then I thought about going to TWRP and thus I downloaded the latest zip for my phone and flashed it via Phillz upon trying to reboot into recovery it got stuck in the screen "Rebooting Recovery...".
When I restarted it would still try to reboot into recovery and get stuck. I got out of that by going into download mode and then selecting "Restart Phone".
After that I looked for solutions and upon failing to find any I thought about going back to stock and starting from ground zero. I managed to flash the latest stock using Odin however I forgot to do a factory reset before hand.
When I tried to do a factory reset in my, now stock, phone it failed and then got stuck trying to get into recovery. It would flash "Rebooting Recovery..." then restart and flash that in a loop.
I have lost my root as well in the process and trying to root using Odin and CF-Root just get's me back in the recovery boot loop. I can use the phone OK however this is not a stable situation.
I'm sure I've made some serious errors in the tinkering and would like to get my recovery back. I really love Custom Roms. Any kind and knowledgeable souls out there to help me in my cause?
Click to expand...
Click to collapse
Go to the Playstore and download TWRP Coordinator and then
use it to install the latest TWRP recovery for your phone.
Once you can get back into TWRP recovery you need to flash
the cf-autoroot for your phone. Be sure you flash the CORRECT
version of cf-autoroot for your phone's model.
Good luck!
Misterjunky said:
Go to the Playstore and download TWRP Coordinator and then
use it to install the latest TWRP recovery for your phone.
Once you can get back into TWRP recovery you need to flash
the cf-autoroot for your phone. Be sure you flash the CORRECT
version of cf-autoroot for your phone's model.
Good luck!
Click to expand...
Click to collapse
The app is constantly crashing!
It would start for a second then close. I tried the TWRP manager as well with the same result.
I've lost root access when I Odined back to stock, won't I need root access to install new recoveries?
Sounds like you flashed the stock 4.4 firmware and now need recovery to root. Flash this TWRP file using Odin http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.7.0.1-hltetmo-4.4.img.tar
Once you flash it, you need to boot into recovery to install supersu to root.
Switch off the Galaxy Note 3 (remove the battery and reinsert if needed)
Next, press and hold simultaneously Volume Up, Home and Power.Release the buttons when the screen flickers and wait for the TWRP menu.
Select Reboot, then System and install Supersu for root.
Once booted, open Supersu to update it and grant permission.
Hope this helps. Good luck.

My phone won't wipe nor flash a new rom/recovery

Hi there. Here I have my t989 with stable cm11 by Sultanxda and twrp 2.7.0.0 installed.
Everything was fine until I wanted to try 5.0.1.
I got into twrp and did the usual wipe and install ParanoidAndroid 5.0. It failed.
Ok stuff happens so I just went restore my backup no big deal.
Now when I reboot back my phone looks as it were before BUT it reboots after 2-3 minutes in every time it boots back up.
So I thought the power button has problem but soon I figured it is not because my phone won't self reboot in recovery and download mode.
I went back to twrp and try to wipe it clean and install cm11 instead of restoring to my previous backup.
Wipe says successful, install says successful, reboot system. And only to find myself still in my old Rom and nothing was wiped.
All my apps are still there blahblahblah. I tried to update my twrp through twrp manager but phone reboot before it finishes installing.
I grab my odiin and try to update recovery there. Odin says success. Goes to recovery only to find its still in 2.7.0.0
Download a stock .tar and flash it with Odin. Odin says success, boot up and still in my old cm11 rom...
Now I went out of option but ask for help. I have done flashing for 3 years with this phone and I have never gotten this problem before.
Please Help

S.O.S Galaxy S3 Boot-Up Fails (Recovery Mode BOOTLOOP)

Ok guys im in some really deap ****. This is what happend
I was trying to flash my SGH-T999 with cm-2xxxxxxNIGHTLY-d2lte to get the 4.4.4kitkat upgrade. Rooting with clockworkmod using Odin V1.85 was succesfull. I got into recovery mode, wiped data factory, /cache, and /delvik cache/ and i went on to install zip from sdcard. The installation failed, tried severals times and it still fails. And when i try switching it on, it boots with the SAMSUNG Logo and goes back off, then comes back on again with a "Recovery Booting" written on the top left hand corner of the screen, and then it boots into recovery mode. When i hit Reboot System, it does same thing. I have tried downloading the recovery but my SD-Card slot seems to be damage of which the recovery needs to be put on, and more so i cant detect if the memory card i install is ready or not.
Flash twrp to the phone. Cwm has not been updated for a while.
A few months ago I flashed TWRP 2.8.7.0 using Heimdall just fine, no problems. Now I've been trying to flash the latest TWRP 3.0.2, I can't seem to get it to boot, the flash is successful. Then I reflash the older version, and it's not booting into recovery. I'm not too familiar with Samsung phones, but I've been doing this for a long time on my Moto X 2014 using ADB/Fastboot, without issues.
I was able to return to stock firmware using Odin.

Soft brick that won't quit

Was trying to update the supersu binary by installing the updated zip in recovery. On reboot it was stuck in a boot loop. First off nothing else worked, then fastboot worked and then 10 mins later twrp recovery started working. I tried to restore a backed up image but still got boot loop. Then tried to flash a rom I had on sdcard - still boot loopy. Tried to go the miflash tool root but couldn't get it to find the phone despite it appearing in explorer. Copied stock miui zip onto sc card from pc and installed but still same problem. Standard dalvik/cache wipe before and after each install. Now I'm struggling to get recovery up.
Help - haven't managed to totally brick something despite many years of tinkering. :/
PS. I can still get fastboot up. Now when I try to get recovery up the screen goes black and I have to reboot.

Categories

Resources