I don't know what happened, but my Samsung Galaxy tab A always boots back into twrp when I try to boot into the main OS, I had rooted it with cf-auto root and Odin,
then I had used flashify to get twrp version 3.0.2-0, the OS version is 7.1.1 by the way.
I would prefer any methods that involve no pc, but I can still use a computer.
Related
I just got a T-mobile S5 g900T and i want to root it. it's running 4.4.2 and i'm thinking about upgrading to lollipop but im worried i wont be able to root afterwards. What are my root options here?
Motorolaseries said:
I just got a T-mobile S5 g900T and i want to root it. it's running 4.4.2 and i'm thinking about upgrading to lollipop but im worried i wont be able to root afterwards. What are my root options here?
Click to expand...
Click to collapse
You can root on any version of android for this phone:
Just install TWRP with Odin and use TWRP to flash supersu zip. Boot your phone into Odin mode (home, vol down, and power), connect your phone to PC with USB, and install twrp-3.0.0-0-klte-klte.img.tar with Odin (AP button, auto-reboot option disabled). When the status bar is filled, you need to immediately boot into TWRP without rebooting system (this is where you hold down home, vol up, and power). In TWRP, install supersu zip file.
If you reboot to normal android before booting into TWRP and flashing the supersu zip when TWRP is first installed, the operating system will overwrite TWRP with the stock recovery, and you have to try again
What is I flash supersu then it keeps saying set warranty bit kernel
I keep flashing supersu but it keeps saying set warranty bit kernel
Someone knows any methods to root this phone? I already tried Kingo, Genius but no success. Using Odin apparently TWRP don't work on my device. When I go into Recovery Mode, instead of appearing the Recovery Mode by TWRP appears the normal android interface.
I'm having major problems with TWRP, and I need help.
I have a Samsung Galaxy S4 with a properly unlocked bootloader (MDL), rooted, that has had a working version of TWRP 2.8.7.0 and running an older version of Cyanogen.
I'm overhauling the phone, so the first thing I tried to do was to update TWRP.
Since TWRP v2.8.7 supports flashing itself, I booted into recovery and flashed the TWRP update (v3.2.1.0) directly through TWRP. No errors that I saw.
But when I try to boot into recovery, I now get "System Software Not Authorized By AT&T Has Been Found On Your Phone". Fortunately, I can still boot normally - it's only recovery that I'm locked out of.
In trying to fix this, I tried re-flashing TWRP with three different methods:
1. I tried to flash TWRP again through the TWRP app. But I get "Flash Failed".
2. I tried Odin and got "FAIL! (Auth)"
3. I tried flashing v3.2.2.0 using the dd method. This I was able to do without any errors, but I'm still locked out of recovery mode with that same "System Software Not Authorized By AT&T Has Been Found On Your Phone" error.
Help?
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
HippoInWindow said:
Try connect to computer and execute:
adb reboot bootloader
fastboot flash recovery twrp-xxxx-xxx.img
Everything should be good to go.
Note: ALL TWRP settings will be reset.
Click to expand...
Click to collapse
ADB works fine for me, but fastboot does not. It says "waiting for any device". From what I understand, this is a common issue with Samsung phones. I'm using Windows 10, if that helps.
However, I came across a bug report for TWRP here, that reports the exact same problem from 3.0.0.0, and it's still open. That tells me that this may be a general issue with TWRP that they never bothered to fix.
So on a hunch, I tried re-flashing v2.8.7 using the dd method (since that's the only one I can get to work). And SUCCESS! I can now boot into recovery again!
So here's what I need to know:
1. Is there any way to get the latest version of TWRP to work on this phone?
2. Is it safe to flash a current version of LineageOS using this version of TWRP (v2.8.7)?
I'm really wary about that second question, because the last thing I want to do is brick my phone because an old version of TWRP doesn't know how to work with a new version of Lineage/Android. (This phone currently has KitKat on it)
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
HippoInWindow said:
You need Rashr to do this. You can find this app on the Google Play Store which can flash images in your system.
1. This version of TWRP should be able to flash modern LineageOS.
2. Using the above method provided should get you up and running the latest TWRP.
Click to expand...
Click to collapse
I finally found an explanation and solution - it would appear that TWRP 3.x does not have the Loki exploit applied. So nothing 3.0+ will work unless it's been Lokied.
Fortunately, the current versions can be Loki patched, so once that's done, they'll install and work properly. Whew!
Hello, i wanted to install some custom os on my samsung a20e device, so i basically wanted to install twrp. Just to mention, i can unlock bootloader and i know how to root it properly. When i flash twrp with odin, my device just bootloops (i think it's the term) on download mode, and i can't turn it off, i can only restart it. The only way to turn it off is to reflash stock os with odin. Can someone please help me or tell me an alternative ? Thanks.
My phone has screen issue its stuck on logo. I can't flash combination because of the new security Samsung created. I get the message please get approval to use factory binary(PIT)
I have unlocked bootloader and twrp installed, Is there a way to extract the files from the combination rom and create flashable zip to flash that via TWRP?
My Phone is Samsung Galaxy M31S running latest U3 stock rom. Twrp can be installed easily but after the system is booted and If I restart it shut it down I get only official binary are allowed to be flashed. Screen works and is not stuck in twrp but when it boots to system its stuck at first logo/unlocked bootloader screen.
Thanks!
Hello! I have the same problem and the same question.