Device always booting into TWRP 2.6.30 - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I wanted to share my somewhat scary experience and how I resolved it.
It started when one day I wanted to flash an updated rom using TWRP so I rebooted into recovery and TWRP all of a sudden asked for a password.
To resolve the issue I had to ODIN an older version of TWRP, fix permissions and then reinstall 2.6.30.
This got me back into TWRP and I thought all was resolved.
I then proceeded proceeded to wipe everything and even format to ensure the device was clean. I flashed the rom w/o issue and it booted up fine. After I got it all running nicely I rebooted into TWRP to make a backup. The backup was successful.
I then rebooted to system (after backup completed) and the my phone froze on the loading screen. I pulled the battery and restarted the phone and it booted into recovery mode.
I thought maybe there was a permissions issue to I did a fix permissions and rebooted to system via TWRP. Phone still froze when booting. I pulled the battery again and again it powered up into recovery mode again. I decided to wipe everything again and install an older backup that was proven to be good (which I restored previously w/o issue). It restored and rebooted fine. Then I turned off the phone and turned it back on and the damn phone booted into recovery again @#[email protected]# Rebooting to system in TWRP causes the phone to freeze, Cold booting the device boots it into recovery. So I was essentially stuck once I installed anything if I ever had to reboot the phone.
The only solution that worked was to take the stock image (included stock recovery) and root.zip and flash that to the phone. After flashing it I had to go into the stock recovery as the phone still didn't boot properly. I didn't pay much attention but the stock recovery brought up a number of errors but I was able to chose an option (sorry I don't recall what) to fix them.
After it was fixed the phone booted up w/o issue and also rebooted w/o issue. All appeared to be back to normal.
So I went and flashed TWRP again through ODIN and restored my backup and all is back to normal.
As an FYI .. I grabbed the stock image from here :
http://forum.xda-developers.com/showthread.php?t=2363882

Related

[Q] Bricked I747M :(

My I747M started acting strange and failing on installs from the play store. It had twrp 2.6.0.0 and cm10.2 on it.
I ran a nand restore and it didnt fix the issue, so I rebooted into twrp recovery mode and went to wipe everything except external sd since thats where my downloads are. It started then the phone rebooted instantly.
Now all i can get is it will boot to download mode, but oden never shows that its writing anything to the phone, the % stays at zero, if i unhook the usb cable it just says it couldn't detect the phone no matter how long I wait. kies does the exact same thing.
If I try to boot back into recovery mode in twrp it just shows the twrp screen then resets. If I try a normal boot it resets at the cm boot screen just before the animation screen.
is it bricked for good?
Update: I downloaded twrp and flashed using odin. thats the only thing that will flash in download mode, from twrp I can flash a rom and it boots up and the phone works.
In download mode kies see's but cant connect to my phone for a factory restore. odin see's and can flash but flashing anything other than the recovery just hangs.
In twrp when I try to restore a nandroid backup of rooted 4.1.2 touchwiz it just crashes and reboots the phone and I start with the original post issues.

Stuck in TWRP Boot Loop

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.

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

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.

Idle phone spontaneously booted into twrp recovery

I have MIUI_XiaomiEU_Stable_10.3.4.0_FIXED installed for a few month. The phone was working but was occasionally restarting spontaneously.
I had this problem also on stock rom.
Today the phone rebooted into twrp recovery and will not boot into system again.
When turned on it boots to twrp. I can als manually get it to boot to fastmode.
I can properly boot to system after I boot into fastboot and do "fastboot boot twrp-3.3.1-dees_troy-daisy.img" .
Any advice on how to fix it ?
What go corrupted ?
Can I fix it by flashing twrp-3.3.1-dees_troy-daisy.img ?
p.s I had the same problem 6 weeks ago. I wiped everything and flashed stock rom using Miflash. I want to avoid it and keep my data if possible.
I'm not sure what's causing the issue, as it might be ROM related, because you said yourself that you had spontaneous reboots on MIUI. But I believe the TWRP you are using might be part of the issue. You should use Offain's version of TWRP found here: https://androidfilehost.com/?a=show&w=files&flid=291011
Use the latest version to avoid bugs. Somehow the 'official' version of TWRP doesn't work properly. Cheers.

Categories

Resources