Currently on hboot 2.09. I unlocked my bootloader but I seem to be unable to gain root access. I tried using the Universal HTC Toolkit to flash TWRP and flash superuser but that didn't work. I flashed TWRP 6.00 from fastboot since I know that TWRP flashes SuperSU when you reboot from it. Long story short, I still don't have root access. I got an app to check if I had root access and it said I did not. I've gone back into recovery, but whenever I try to reboot from recovery my phone freezes and reboots correctly, but doesn't check for superSU.
Anyone have any idea? Or have a superSU or superuser zip that I could flash so I could gain root?
Not sure about that TWRP version you're using since the most recent version is 2.7.x. At any rate the most recent version of SuperSU can be found in the link below. Download the zip and flash in recovery.
http://forum.xda-developers.com/showthread.php?t=1538053
Sent from my HTC M8
Magnum_Enforcer said:
Not sure about that TWRP version you're using since the most recent version is 2.7.x. At any rate the most recent version of SuperSU can be found in the link below. Download the zip and flash in recovery.
http://forum.xda-developers.com/showthread.php?t=1538053
Sent from my HTC M8
Click to expand...
Click to collapse
Can I use the most recent TWRP even if I'm still on hboot 2.09?
double edit: Thanks for the help!
Yes. You can get it from the TWRP website.
Sent from my HTC M8
I assume now that I'm rooted I can just use the TWRP app? I can't use fastboot commands on my work computer, unfortunately.
You can flash it using the bootloader method. No PC required.
Not sure what app you're referring to. Goo Manager?
Sent from my HTC M8
Related
I was rooted on 2.08 and decided to relock and upgrade to 2.17 OTA. I was able to unlock again and install TWRP custom recovery. I flashed Superuser.zip (3.07) from recovery. But it seems I still don't have root access. Not of the rooted apps work. Tried installing busybox from app on the market but says don't have root. Trying to update binary from Superuser app fails. How do I get root access at this point. Should I flash an older Superuser. Thanks.
Did you flash a rooted ROM? If not, that is likely your problem.
Vdubtx said:
Did you flash a rooted ROM? If not, that is likely your problem.
Click to expand...
Click to collapse
I'm on stock ROM right now. I flashed a different version of superuser which worked. That was my problem. I have root access now.
My HTC one m8 has root access. I was using twrp recovery and stock rom. I wanted to flash a custom rom (tried cyanogen and pan) but twrp never helped me in finding my zip file. Then I tried swapping my recovery from twrp to cwm but that never happened and it got stuck in bootloader mode and then I did factory reset :/. And now everytime I try going into recovery it takes me to the bootloader mode. now I am trying flashing a custom recovery but first turning s_off and I tried firewater but it doesn't work.
What should I do?
It still has root access but s_on and don't know about bootloader on/off and no recovery.
Sent from my HTC one m8 using XDA Free mobile app
Fahad khan lodhi said:
My HTC one m8 has root access. I was using twrp recovery and stock rom. I wanted to flash a custom rom (tried cyanogen and pan) but twrp never helped me in finding my zip file. Then I tried swapping my recovery from twrp to cwm but that never happened and it got stuck in bootloader mode and then I did factory reset :/. And now everytime I try going into recovery it takes me to the bootloader mode. now I am trying flashing a custom recovery but first turning s_off and I tried firewater but it doesn't work.
What should I do?
It still has root access but s_on and don't know about bootloader on/off and no recovery.
Sent from my HTC one m8 using XDA Free mobile app
Click to expand...
Click to collapse
and does your device say unlocked at the top of your bootloader? if not follow this guild http://forum.xda-developers.com/showthread.php?t=2799796 , but use the twrp for you device carrier only
if you did it via recovery you should still be ok
go to your bootloader download this twrp img here http://techerrata.com/file/twrp2/m8/openrecovery-twrp-2.7.1.0-m8.img on your computer (for gsm) int. att (i'm guessing this is the device carrier you have)
ensure you have fastboot tools(adb tools installed)
put the .img in your folder that contains fastboot
open a cmd in that folder on your computer and make sure you put your phone in fastboot mode via your bootloader.
then type on your computer in cmd fastboot flash recovery (name of twrp you downloaded).img
then type fastboot erase cache
you now have twrp installed to get to it now select recovery from bootloader on your phone.
when installing custom roms in twrp you need to go to advanced wipe(select data,cache,delvik cache, and system then swipe the arrow bar beneath)
then press home and press install the go to the location on the sdcard where you put the rom.zip of the custom rom and select it. instalation will begin after completion reboot(done)
It says unlocked at the top but S On.
Shouldn't I turn s off before flashing recovery?
Sent from my unknown using XDA Free mobile app
@Fahad khan lodhi
it won't matter either way.
but just so you know what s-off is
s-off turns security mode off so you can swap out boot splashes and such, if you s-off and super cid you can flash any carrier's firmware,
also allows you to flash a kernel in recovery on older devices(m8 doesn't need s-off to flash kernel)
Can't S-Off unless you can boot. Firewater only works if you can get into the OS and then only for some devices. You should reinstall TWRP and see if you can boot to it then put a rom on an external SD card or use adb to push a rom zip to the internal if you don't have an SD card. Make sure that you fastboot flash the boot.img of whatever rom you are trying due to being S-On. If all that fails, then you will need to find the same or newer RUU from HTC for your carrier to restore the phone to stock and start over.
es0tericcha0s said:
Can't S-Off unless you can boot. Firewater only works if you can get into the OS and then only for some devices. You should reinstall TWRP and see if you can boot to it then put a rom on an external SD card or use adb to push a rom zip to the internal if you don't have an SD card. Make sure that you fastboot flash the boot.img of whatever rom you are trying due to being S-On. If all that fails, then you will need to find the same or newer RUU from HTC for your carrier to restore the phone to stock and start over.
Click to expand...
Click to collapse
Hey thank you very much.
It helped and i flashed latest twrp recovery and then flashed viper one m8 1.8.0 rom but the latest version is 2.4.0 and it says to have that your firmware should be 4.4.3 and i have 4.4.2.
Question is can i flash paranoid android coz that gives me 4.4.4 firmware and then flash latest viper one m8 version or i have to go to stock rom and update it and then flash latest version of viper?
Reply please.
Sent from my HTC One_M8 using XDA Free mobile app
Fahad khan lodhi said:
Hey thank you very much.
It helped and i flashed latest twrp recovery and then flashed viper one m8 1.8.0 rom but the latest version is 2.4.0 and it says to have that your firmware should be 4.4.3 and i have 4.4.2.
Question is can i flash paranoid android coz that gives me 4.4.4 firmware and then flash latest viper one m8 version or i have to go to stock rom and update it and then flash latest version of viper?
Reply please.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
It should still work with the firmware you have. It's recommended but not necessary. And flashing PA would certainly not update your firmware. Firmware in this instance is mostly focused on the radio/baseband version and the touch drivers. These are not included in any kind of custom rom for your phone (nor 99% of android custom roms for anything). Much more important if you were originally on 4.2.2 or 4.3 and trying to run the new Viper. The only way to update firmware while S-On is via RUU or OTA. If you were S-Off then you could flash just the firmware package that has the hboot and stock recovery files removed.
I am wondering if the following method will allow root while keeping OTA:
1) Unlock with HTCDev
2) Only boot into TWRP (not flash it as permanent recovery): Fastboot boot twrp.img
3) Once booted into TWRP, install supersu
Then should OTA updates work, after which you only have to repeat steps 2 & 3?
My intent is to just get root access for apps like WiFi Tether Router.
If you install SU, the OTA will not work. SU modifies the system which will cause an OTA to fail.
Sent from my 831C using XDA Premium 4 mobile app
Besides the reply above...
Someone suggested this in another thread and could not get TWRP to directly boot.
Hi
I've ordered the redmi note 2 and would like to install a custom rom on it when I receive it. Can somebody tell me what the easiest method to root the phone and install TWRP is? There seems to be so many different ways and I'm finding it abit confusing. Also do I need to unlock the bootloader before rooting?
Thanks
Search on Youtube for: How to install recovery Xiaomi Redmi Note 2 and How to root Xiaomi Redmi Note 2
arg357 said:
Hi
I've ordered the redmi note 2 and would like to install a custom rom on it when I receive it. Can somebody tell me what the easiest method to root the phone and install TWRP is? There seems to be so many different ways and I'm finding it abit confusing. Also do I need to unlock the bootloader before rooting?
Thanks
Click to expand...
Click to collapse
Flashed a china dev rom was an easier way without using PC. But first to need to wipe your phone. Then installed flashify to flash twrp.img. With twrp, you can flashed any compatible rom you like.
for the redmi note from the wife who only needed root I used Kingroot
And I wanted root and TWRP so I used Windroid toolkit
thanks for the replies. Windroid seems pretty straightforward, I'll give that a go once I get my phone.
You can flash xiaomi.eu latest ROM and you'll get TWRP 3.0. For root you can flash any SuperSU official zip using TWRP
Gyovany96 said:
You can flash xiaomi.eu latest ROM and you'll get TWRP 3.0. For root you can flash any SuperSU official zip using TWRP
Click to expand...
Click to collapse
you mean this one? http://xiaomi.eu/community/threads/6-2-25.30340/
that says TWRP needs to be installed before that rom can be flashed?
arg357 said:
you mean this one? http://xiaomi.eu/community/threads/6-2-25.30340/
that says TWRP needs to be installed before that rom can be flashed?
Click to expand...
Click to collapse
Yes that one..
"Our ROMs now contains TWRP which will install it automatically and overwrite your MiRecovery (If you still use it)"
"Version 6.2.25 still can be installed via MiRecovery but it will overwrite it to TWRP"
I use xiaomi.eu ROM/Based ROM's because it has my language
ah ok, thanks mate
So I tried updating via updateer with the rom from xiaomi.eu but that failed it said something about the file signature. So I tried the windroid method, the computer picked up the device no problem and it was weorking well. I flashed TWRP and Super SU and completely wiped everything on the phone. Now I'm trying to sideload a rom using windroid, but when I go to the ADB sideload option in TWRP it just stays stuck on "starting ADB sideload feture..." Windroid seems to recognise that the device is in sideload mode but I can't flash anything as it just stays stuck.
Any ideas?
Never mind, my PC picked up the phone while it was in recovery and I was able to just copy the rom file over
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!