Hey guys, as the title states, I'm wondering if there were any working TWRP or CWM's Recoveries for the Sprint Samsung Galaxy S6. I'm on 5.1.1 OI1 rooted.
I've tried TWRP 2.8.6.0 and 2.8.7.0 both the .tar via Odin and the .img via Flashify. Version 2.8.6.0 gets me stuck in a bootloop while Version 2.8.7.0 installs, but it doesn't seem to work. I see the recovery screen, but nothing works, as if the touchscreen is just shut off. I can press the power button, which it then tells me to 'Slide to Unlock', but that doesn't work either, the touchscreen just isn't responding. And if I try rebooting, it just gets caught in a bootloop, same as the other version.
So I was wondering if there were any recoveries in the works right now that I can keep my eye on for future releases.
Thanks!
Step 1: Go to developer options (unlock that if you haven't by tapping on build number) and be SURE that OEM unlocking is set to one. Really, be sure.
Step 2: Flash this via Odin: http://build.twrp.me/twrp/twrp-2.8.7.1-zerofltespr.img.tar
Step 3: Profit! (South Park reference there...)
Related
Hello, this will be my first post here at XDA, and i will be asking for your help guys...
I am experiencing bootloop on my phone.
The thing is I tried to install Xposed Installer using the Automatic method that flashes to the recovery.
It reboots them...
It passed the Galaxy Note II N7100 black screen...
It shows the TWRP logo (The blue one)
AND THEN IT JUST REPEAT AND REPEAT the TWRP logo.
I can boot to Download Mode.
Tried removing the battery and tried to enter recovery again using hardware keys, same thing happens.
What can I do now? Please Help.
Thank You!
P.S. I am running DN3 4.3 Stable using it's stock kernel.
sgtfrnz said:
Hello, this will be my first post here at XDA, and i will be asking for your help guys...
I am experiencing bootloop on my phone.
The thing is I tried to install Xposed Installer using the Automatic method that flashes to the recovery.
It reboots them...
It passed the Galaxy Note II N7100 black screen...
It shows the TWRP logo (The blue one)
AND THEN IT JUST REPEAT AND REPEAT the TWRP logo.
I can boot to Download Mode.
Tried removing the battery and tried to enter recovery again using hardware keys, same thing happens.
What can I do now? Please Help.
Thank You!
P.S. I am running DN3 4.3 Stable using it's stock kernel.
Click to expand...
Click to collapse
Well something was messed up when you flashed xposed installer( i don't know what you mean by automatic method) but do a clean install,since you can get into download mode,grab the twrp img.tar and flash it using pc odin ,then you can access recovery, do all the wipes again by going under "advanced" and reflash your rom.Now to install xposed go to xda thread for it and grab the apk from there (i think it's available on play store as well).You should have no more issues
Twrp
Like the previous post said I'm not sure what you've done. When xposed framework is installed there is usually an unistall zip created on the internal so card. If you can get recovery find it and flash it
Sent from my GT-N7105 using Tapatalk
The device is now fixed.
So okay, I followed the above instruction to flash a fresh TWRP. It does not work that way, it still has bootloop on the blue teamwin screen, what i've done is flash a .tar Philz specified for my device and then try to boot it. It boot and then it then flashes the pending Xposed script/flashable that I think TWRP can't execute that's why it bootloop. When it CWM successfully flashed it, I boot and wen't to homescreen. Then I now flashed TWRP via odin.
Thanks everyone, my Note 2 has come back to life.
sgtfrnz said:
So okay, I followed the above instruction to flash a fresh TWRP. It does not work that way, it still has bootloop on the blue teamwin screen, what i've done is flash a .tar Philz specified for my device and then try to boot it. It boot and then it then flashes the pending Xposed script/flashable that I think TWRP can't execute that's why it bootloop. When it CWM successfully flashed it, I boot and wen't to homescreen. Then I now flashed TWRP via odin.
Thanks everyone, my Note 2 has come back to life.
Click to expand...
Click to collapse
Boot into Download mode and flash philsz touch recovery 6 and reboot device .. Everything will be ok>
Old thread may be old, but it's still relevant.
I just tried to install XPosed as well on my Note II and it did the same thing (mine's AT&T)
Info
Device: Note II
XPosed Version: 2.6.1
Install Method: "Recovery (flash zip automatically)"
Recovery Image: TWRP
Mine exhibited the same behavior as OP's, however after leaving it alone for a while to bootloop recovery as much as it wanted to, I came to my laptop, found this post, grabbed as USB cable, and I was just about to start the process of reflashing recovery when all of a sudden I saw my lock screen.
It took roughly five minutes of bootloop to get it there, but it successfully installed XPosed and my device is running fine.
So, for all the other Googler's out there that landed on this post, leave it alone for a while! See what happens. If it's still bootlooping, like, 30 minutes later, then try reflashing TWRP using ODIN. If that still doesn't work, reflash a new ROM using TWRP.
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.
The events that transpired:
1. Installed stock NF9 via Effortless guide.
2. Booted into stock & all aspects where upgraded to NF9
3. Installed CF-Auto-Root via Odin
4. Installed philz touch 6.12.8
5. Attempted to boot into Recovery and it rebooted itself
6. Installed TWRP included in Effortless guide
7. Booted into TWRP. The recovery was behaving oddly and it took about 10 minutes just to get to the next step.
8. Installed HyperDrive RLS4
9. Booted into HyperDrive
10. Installed ROM Manager and installed the latest CWM Touch
11. SuperSU updated it binaries and I accidentally told it to do it in TWRP/CWM.
Now I am in an eternal bootloop. I have tried to boot into download mode with no success. I have removed the batteries and waited hours (not an exaggeration) and it still attempts to boot into recovery on its own over and over again. Can any give me some more ideas to try to fix this? Thanks!!!
re: boot loop/recovery/rom manager
Jakman85 said:
The events that transpired:
1. Installed stock NF9 via Effortless guide.
2. Booted into stock & all aspects where upgraded to NF9
3. Installed CF-Auto-Root via Odin
4. Installed philz touch 6.12.8
5. Attempted to boot into Recovery and it rebooted itself
6. Installed TWRP included in Effortless guide
7. Booted into TWRP. The recovery was behaving oddly and it took about 10 minutes just to get to the next step.
8. Installed HyperDrive RLS4
9. Booted into HyperDrive
10. Installed ROM Manager and installed the latest CWM Touch
11. SuperSU updated it binaries and I accidentally told it to do it in TWRP/CWM.
Now I am in an eternal bootloop. I have tried to boot into download mode with no success. I have removed the batteries and waited hours (not an exaggeration) and it still attempts to boot into recovery on its own over and over again. Can any give me some more ideas to try to fix this? Thanks!!!
Click to expand...
Click to collapse
Here is a sure way to solve the issue you are having with bootlooping and root.
#1: Odin flash cf-autoroot, here is the direct download link:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.0.1-hltetmo-4.4.img.tar
#2: Odin flash twrp recovery, here is the direct download link:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.0.1-hltetmo-4.4.img.tar
Odin flash the cf-autoroot first.
You were not using the latest official version of twrp recovery, and
you must have used either an old version or a pre-release beta.
Once you are done doing the above you will no longer have bootloop and root issues.
Don't use rom manager for anything in the future if you want to avoid
these kinds of issues. The latest firmwares and custom roms do not play
nicely with rom manager.
Also philz touch recovery is not fully compatible with these newer firmwares and roms.
Good luck!
Misterjunky said:
Here is a sure way to solve the issue you are having with bootlooping and root.
#1: Odin flash cf-autoroot, here is the direct download link:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.0.1-hltetmo-4.4.img.tar
#2: Odin flash twrp recovery, here is the direct download link:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.8.0.1-hltetmo-4.4.img.tar
You were not using the latest official version of twrp recovery, and
you must have used either an old version or a pre-release beta.
Odin flash the cf-autoroot first.
Once you are done you will no longer have any bootloop and root issues.
Don't use rom manager for anything in the future if you want to avoid
these kinds of issues. The latest firmwares and custom roms do not play
nicely with rom manager.
Good luck!
Click to expand...
Click to collapse
Here is the problem: I cannot get into download mode. I have held volume up+home+power and any combination of buttons and it just keeps trying to boot into a broken recovery. I have also plugged it into my computer and it doesnt communicate to it at all (makes sense, since it never boots into anything). I need to be able to reset my bootloader or force the bootloader into download mode.
Try removing the battery and while holding down the three button combo insert battery. With luck it'll go into D/L mode.
Pp.
PanchoPlanet said:
Try removing the battery and while holding down the three button combo insert battery. With luck it'll go into D/L mode.
Pp.
Click to expand...
Click to collapse
I have been trying that all evening! I have been looking up JTAG services and JIGs. I read your comment and said "It can't hurt to give it another go"... and BAM!!! Download Mode! After the 50th time!!! WOOT! Thanks guys!
This is what the Android community is all about.
Your welcome.
Pp.
Hi,
I have an LG Gpad 7.0 v400 tablet which I recently rooted.
I am trying to flash TWRP recovery using Flashify (for root users), but it is not working.
It flashes the file and says to reboot the device to apply the flash, but when it reboots, it stops at the start screen with text in the top left corner saying their is an error with booting up.
Turning the tablet off then on again clears the error, but the recovery isn't there.
I have the correct recovery for the tablet
What do I do now?
I am in the same exact predicament so can anyone help with instructions OT a link on how to flash recovery or how to get into recovery with button combo. I can't figure it out
Hi all, looking for some help here.
I picked up a pair of P607's to install Lineage on.
1. I flashed (via ODIN) the latest Samsung factory build from Sam Mobile (Now running 5.1.1).
2. Grabbed the latest TWRP tar file (twrp-3.1.1-0-lt03ltexx.img.tar)
3. Flashed TWRP via ODIN (AP button, selected the twrp tar, unchecked auto-reboot)
4. Held power button and turned off.
5. Powered back on and Held the [home - vol up - pwr] to boot into recovery to check TWRP.... and..... Recovery Boot Loop.
Odly enough, if I get it back into download mode and just boot it normally, it will boot fine back into the OS (stock rom, not lineage yet)
I can recover back to the factory by re-flashing the stock rom again, so it's recoverable.
I've tried with two different 3.1 TWRP versions now, twrp-3.1.0-0-lt03ltexx.img.tar and twrp-3.1.1-0-lt03ltexx.img.tar, both do the same thing.
Any ideas on this one?
There's definitely some odd issues with TWRP for this device...
3.1.1 Failed
3.1.0 Failed
3.0.2 Worked and boots into TWRP
Would be nice to get the latest TWRP working for this device, anyone interested in logs from the 3.1.0 or 3.1.1 attempts?
how did you get out of the boot loop? i cant seem to get back in to download mode
XnoteX said:
how did you get out of the boot loop? i cant seem to get back in to download mode
Click to expand...
Click to collapse
Today I got the same bootloop problem.
Impossible to enter the Download-Mode.
I removed carefully the Backcover and disconnect the battery plug for some seconds.
On the next start I´m holding down Vol- and entered Download Mode.
With Odin I flashed TWRP 3.0.2.0 (same version like before) and its working again without loosing the installed programs.
I think you can also wait until the battery is empty .....
Hope it helps a bit to recover a great tablet.
sillysuliman said:
There's definitely some odd issues with TWRP for this device...
3.1.1 Failed
3.1.0 Failed
3.0.2 Worked and boots into TWRP
Would be nice to get the latest TWRP working for this device, anyone interested in logs from the 3.1.0 or 3.1.1 attempts?
Click to expand...
Click to collapse
Most ROMs here install fine with 3.0.2. That's what I am using on my 607T.