To start off i have an htc one from verizon and i wanted to unlock the bootloader to run custom roms. I used Rumrunner to completely unlock my bootloader and get s-off. well here is where my first problem started, i could not get a custom recovery to flash on my device. Rom manager and Goomanager both said that no version available for my device. after trying multiple version of cwm and twrp i managed to finally get CWM to install on my device. i managed to backup all my data with CWM's device backup and when i tried to install a new rom i could not get it to install i would get an errror because supposedly it wasnt the rom for my device, i made sure it was and tried downloading another rom. After that not working i tried to update my CWM and it managed to remove the version i had and now i cant get into recovery again.
My second problem, along the lines of trying to get this to work, someone on the forums suggested that a person (who was having similar issues with the recovery) to try and adb command to see if the bootloader was actually unlocked, but after doing this it now changed me from S-off to S-on. and i dont want to run rumrunner again to get s-off again because it says on the rumrunner forum that you have to start that program from completely stock and i dont want to risk bricking my device. can anyone help me with either of these problems? any help would be appreciated.
Google androidcentral. It's there.
Sent from my HTC One X using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=2441299
second post should have all the info you need.
basic steps:
-install recovery
-flash superuser or flash a rom
there are a couple of ways to skin the cat
GOO Manager and ROM Manager do not support this phone.
blake1886 said:
To start off i have an htc one from verizon and i wanted to unlock the bootloader to run custom roms. I used Rumrunner to completely unlock my bootloader and get s-off. well here is where my first problem started, i could not get a custom recovery to flash on my device. Rom manager and Goomanager both said that no version available for my device. after trying multiple version of cwm and twrp i managed to finally get CWM to install on my device. i managed to backup all my data with CWM's device backup and when i tried to install a new rom i could not get it to install i would get an errror because supposedly it wasnt the rom for my device, i made sure it was and tried downloading another rom. After that not working i tried to update my CWM and it managed to remove the version i had and now i cant get into recovery again.
My second problem, along the lines of trying to get this to work, someone on the forums suggested that a person (who was having similar issues with the recovery) to try and adb command to see if the bootloader was actually unlocked, but after doing this it now changed me from S-off to S-on. and i dont want to run rumrunner again to get s-off again because it says on the rumrunner forum that you have to start that program from completely stock and i dont want to risk bricking my device. can anyone help me with either of these problems? any help would be appreciated.
Click to expand...
Click to collapse
Hi all !
I have an HTC ONE M8 (obviously) and my phone is actualy S-OFF (sunshine) but my bootloader is Locked (because i flash a zip with bootloader).
I literaly forget that Unlock bootloader with HTC_DEV Wipe DATA !
So I want to know if I can Root / install recovery whitout HTC_DEV Unlock, I'm S-OFF so why I can't use my phone like I want ?
Thank for answer !
And sorry for my bad English I'm a French user of XDA
Take a look here:
http://forum.xda-developers.com/showthread.php?t=2708571
YOU ROCKS !
Google only find the M7 post
But I have not Root acces (Need "Su" in adb shell )
"fastboot boot <insert recovery here>.img" This not working with me
arnaudbond007 said:
YOU ROCKS !
Google only find the M7 post
But I have not Root acces (Need "Su" in adb shell )
"fastboot boot <insert recovery here>.img" This not working with me
Click to expand...
Click to collapse
Are you trying to flash the boot image or the recovery image?
Flash boot.img (or whatever the name of the file is):
Code:
fastboot flash boot boot.img
Flash recovery.img (or whatever the name of the file is):
Code:
fastboot flash recovery recovery.img
The thing is, you need to have an unlocked bootloader to do this. If you don't have root access, and you can't unlock your bootloader via HTC Dev, then I don't know if there's any other way to get it done. (Anyone can correct me if I'm wrong. Thanks!)
I'm trying to BOOT on TWRP without flash it, for just root the ROM
Nobody can help me ?
I just need a way to boot in a recovery.img
arnaudbond007 said:
Nobody can help me ?
I just need a way to boot in a recovery.img
Click to expand...
Click to collapse
If you don't want to flash TWRP or another recovery and keep your stock one, do this:
Download the latest recovery of your choice.
Place the *.img file into your fastboot folder or anywhere you can find it easily; rename it if possible with a simple name, for this example, recovery.img
Put your phone into fastboot mode and connected to your PC.
Open the windows command into your fastboot folder and make sure your devices is recognized by typing "fastboot devices" without quotations.
Once you make sure your phone is connected, type the following: fastboot boot recovery.img
Your device will restart into the TWRP recovery, then install the SuperSu file previously placed into your SDcard or internal memory.
Restart into system and that's all, you'll keep your stock recovery
.
CM17X said:
If you don't want to flash TWRP or another recovery and keep your stock one, do this:
Download the latest recovery of your choice.
Place the *.img file into your fastboot folder or anywhere you can find it easily; rename it if possible with a simple name, for this example, recovery.img
Put your phone into fastboot mode and connected to your PC.
Open the windows command into your fastboot folder and make sure your devices is recognized by typing "fastboot devices" without quotations.
Once you make sure your phone is connected, type the following: fastboot boot recovery.img
Your device will restart into the TWRP recovery, then install the SuperSu file previously placed into your SDcard or internal memory.
Restart into system and that's all, you'll keep your stock recovery
.
Click to expand...
Click to collapse
Thanks but this work only if HTC bootloader is Unlocked; so i Wiped my data to unlock my devices... I just don't understand the benefit of S-Off -> htc bootloader have to be unlocked at all
S-OFF means you can flash older RUU/firmware packages - helpful if the latest RUU isn't available. It also allows you to move from one variation of M8 to another, e.g. Developer Edition to unbranded EU
You can remain locked by flashing a ZIP with just the custom recovery in it via RUU mode - I do this and it works well for the odd time I want to try a custom ROM
arnaudbond007 said:
I just don't understand the benefit of S-Off -> htc bootloader have to be unlocked at all
Click to expand...
Click to collapse
In addition to the benefits mentioned above (and somewhat related), s-off allows access to partitions that are protected with s-on, including radio, hboot, and others. s-off isn't required for root, installing custom recovery or custom ROMs ; but is required for a number of other things.
I find S-OFF working for me only for adaway and now the Battery monitor widget, and also Cerberus App.
Adaway is not working because it can't overwrite the system partition, neither the workarounds worked for me; Cerberus keep crashing anytime i perform a change on the app and Battery monitor widget doesn't install the system app for the same reason: Can't write the partition.
At this point, at least with the M8, i realize there is no joy by just rooting, you need S-OFF or your phone will be the same as unrooted.
CM17X said:
I find S-OFF working for me only for adaway and now the Battery monitor widget, and also Cerberus App.
Adaway is not working because it can't overwrite the system partition, neither the workarounds worked for me; Cerberus keep crashing anytime i perform a change on the app and Battery monitor widget doesn't install the system app for the same reason: Can't write the partition.
At this point, at least with the M8, i realize there is no joy by just rooting, you need S-OFF or your phone will be the same as unrooted.
Click to expand...
Click to collapse
If you are having trouble with the system write protection mod; flashing just about any custom ROM (that supports your firmware) will do the trick.
redpoint73 said:
If you are having trouble with the system write protection mod; flashing just about any custom ROM (that supports your firmware) will do the trick.
Click to expand...
Click to collapse
Sorry dude, but i'm kinda confused now. Which Write protection Mod is out there? can you please link me to it?
And about custom ROM, i'll prefer to give to the Stock firmware a chance before start messing around with ROM's, once i get tire of it i'll change.
Question here is, would S-OFF grant me access to the system partition in order to install apps like the ones i've mentioned above? (Still interested on that Write protection Mod if exist)
CM17X said:
Sorry dude, but i'm kinda confused now. Which Write protection Mod is out there? can you please link me to it?
Question here is, would S-OFF grant me access to the system partition in order to install apps like the ones i've mentioned above? (Still interested on that Write protection Mod if exist)
Click to expand...
Click to collapse
When you mentioned "workarounds" I thought you were referring to the kernel mod to disable system write protection (and that it didn't work for you). But I guess you were referring to some Adaway workaround (that I am not aware of)?
Here is the kernel mod to disable system write protection (s-off is not required for this): http://forum.xda-developers.com/showthread.php?t=2701816
The OP stopped updating it, so no kernel mod for Lollipop in the top post. But if you read near the end of the responses, he says you can get the kernel module from a custom ROM (and a couple LP kernel modules are posted by other users).
redpoint73 said:
When you mentioned "workarounds" I thought you were referring to the kernel mod to disable system write protection (and that it didn't work for you). But I guess you were referring to some Adaway workaround (that I am not aware of)?
Here is the kernel mod to disable system write protection (s-off is not required for this): http://forum.xda-developers.com/showthread.php?t=2701816
The OP stopped updating it, so no kernel mod for Lollipop in the top post. But if you read near the end of the responses, he says you can get the kernel module from a custom ROM (and a couple LP kernel modules are posted by other users).
Click to expand...
Click to collapse
Yes, i was referring to the AdWay workaround which consist on make a symbolic link (Doesn't work at all).
I'll keep away from the Kernels mods for a while as well. I hope S-OFF can give me solutions for that.
I'm S-off, BL-unlocked, and rooted - and I did each in that order. As such, I can pretty much do whatever I please on my phone. (Even if ES File Explorer doesn't believe me and pops up warnings, presumably without trying and failing...) However, when I upgraded to Lollisense, I opted to do an RUU update, since I am always rooted and didn't want to risk it.
I didn't modify the stock software in any way afterwards, beyond rooting the install, and I can assure you that AdAway works fine on my phone. It was one of my first installs. All I can take away from that is that stock firmware disables certain write protections when it sees that the device is S-off.
arnaudbond007 said:
Thanks but this work only if HTC bootloader is Unlocked; so i Wiped my data to unlock my devices... I just don't understand the benefit of S-Off -> htc bootloader have to be unlocked at all
Click to expand...
Click to collapse
Unlocking the bootloader allows access to 4 partitions. S-Off gives access to all 47 partitions.
jshamlet said:
I'm S-off, BL-unlocked, and rooted - and I did each in that order. As such, I can pretty much do whatever I please on my phone. (Even if ES File Explorer doesn't believe me and pops up warnings, presumably without trying and failing...) However, when I upgraded to Lollisense, I opted to do an RUU update, since I am always rooted and didn't want to risk it.
I didn't modify the stock software in any way afterwards, beyond rooting the install, and I can assure you that AdAway works fine on my phone. It was one of my first installs. All I can take away from that is that stock firmware disables certain write protections when it sees that the device is S-off.
Click to expand...
Click to collapse
I believe the system write protection is already disabled by default on stock Developer's Edition (and the only stock ROM to have this feature).
Hi all, I am playing around with an HTC m8 to decide if I should use it as replacement of my Nexus 4 (so far, too big and heavy ).
But well, I unlocked the phone and installed TWRP. All worked fine, but then I flashed supersu and I'm stucked in a boot loop. I am reading a lot of things but I am unsure about what to do now and how to actually root the phone and start installing a different ROM as I don't know what´s the phone model. It says M8_UL in fastboot...
I´m looking at this but not sure if this phone is gpe.
http://forum.xda-developers.com/htc-one-m8/general/root-root-marshmallow-gpe-supersu-t3242210
Any ideas?
Thanks!
1. flash TWRP 3.0.20
2. boot TWRP
3. copy SuperSU v.[2].56 zip to SD card of device in TWRP if on Marshmallow.
4. Flash SuperSu v.[2].56 zip
5. You should boot if you were booting before flashing TWRP.
EDIT: corrected SuperSU version.
spideyngo said:
1. flash TWRP 3.0.20
2. boot TWRP
3. copy SuperSU v.1.56 zip to SD card of device in TWRP if on Marshmallow.
4. Flash SuperSu v.1.56 zip
5. You should boot if you were booting before flashing TWRP.
Click to expand...
Click to collapse
I did that but still stuck in the HTC screen. I flashed 1.56 and I have TWRP 3.0.20 but I'm S-ON, does it matter?
Thanks,
frozst said:
I am reading a lot of things but I am unsure about what to do now and how to actually root the phone and start installing a different ROM
Click to expand...
Click to collapse
You don't need to root in order to install a custom ROM. Once you have TWRP installed, just put a ROM on the phone (download ROM direct to phone, copy to SD card, adb push, etc.), boot into TWRP, and install the ROM (also recommended to backup the stock ROM before flashing a custom ROM, and also do default wipe in TWRP before ROM flash - data, cache and Dalvik).
All custom ROMs are pre-rooted, so you don't need to root separately after flashing a ROM, either. Although, some AOSP based ROMs need root enabled in phone Settings>Developer's Options.
---------- Post added at 11:07 AM ---------- Previous post was at 11:05 AM ----------
frozst said:
I did that but still stuck in the HTC screen. I flashed 1.56 and I have TWRP 3.0.20 but I'm S-ON, does it matter?
Click to expand...
Click to collapse
S-on is fine. I don't know why the previous user stated SuperSU 1.56. That build is ancient, and will definitely not work on Marshmallow. Might be a typo, or they were just thinking of the wrong number (maybe 2.56).
Latest stable version SuperSU 2.76 is recommended for rooting Marshmallow: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
But as already mentioned, you don't need root to flash custom ROMs.
frozst said:
I did that but still stuck in the HTC screen. I flashed 1.56 and I have TWRP 3.0.20 but I'm S-ON, does it matter?
Thanks,
Click to expand...
Click to collapse
EDIT: SuperSU version 2.56. Sorry about that.
I am have an AT&T HTC One M8 on stock Marshmallow. SuperSU 2.76 puts my Marshmallow M8 in a boot loop. You may need to flash a rooted stock ROM to repair booting. S-off not needed, but makes your life easier.
Thanks! the problem was the old SU version, solved now and testing different ROMs. Any recomendations?
spideyngo said:
I am have an AT&T HTC One M8 on stock Marshmallow. SuperSU 2.76 puts my Marshmallow M8 in a boot loop.
Click to expand...
Click to collapse
Hadn't heard that. I wonder if its a known issue experienced by others? If so, I'll fall back to my previous recommendation to use 2.65, which was the former "latest" STABLE version; and no complaints that I am aware of.
Hello, HTC One M9 (Sprint here) I'm stuck in a bootloop too after unlocking the bootloader and installing SU. Tried several version of SuperSU without anyluck. Can anyone help please ?
kbytes said:
Hello, HTC One M9 (Sprint here) I'm stuck in a bootloop too after unlocking the bootloader and installing SU. Tried several version of SuperSU without anyluck. Can anyone help please ?
Click to expand...
Click to collapse
This forum is for the M8, any advice you get may not be correct. Post in the M9 forum.
But what I can say, is if you say "several version" SuperSU is not specific enough (when you post to the correct device forum). Be specific as to what version numbers you tried. Nobody can help, if you don't give the proper info to see what you did wrong. In particular, you need to provide info on what Android version your phone is currently on, what TWRP version, what SuperSU version(s) you tried.
But again, post to the M9 forum, not here.
Stuck on HTC Screen.
I've read through here and see that someone got their M8 off of the HTC start screen. I've installed the SuperSU, and TWRP, the phone restarted and now is stuck on the HTC screen. I am unable to hard reset the phone at all. Its stuck on that screen. Help?
weismanak said:
I've read through here and see that someone got their M8 off of the HTC start screen. I've installed the SuperSU, and TWRP, the phone restarted and now is stuck on the HTC screen. I am unable to hard reset the phone at all. Its stuck on that screen. Help?
Click to expand...
Click to collapse
You probably used an old version TWRP and/or old version SuperSU.
TWRP 3.0.2 and SuperSU 2.76 is recommended.
Hold power+vol up for a minute or so, to force a reboot. Once the screen goes dark to reboot, let go of the buttons, and only hold vol down. Don't let go of vol down, until you are in bootloader. If the phone just gets stuck on the logo screen again, you just got the timing wrong; either didn't start pressing vol down soon enough, or let go too early. Just repeat the process, until you get to bootloader.
From there, restore TWRP backup (which you should always make before attempting to root) and try again, with the proper versions TWRP and SuperSU.
If no TWRP backup, flash proper version TWRP in fastboot, then get proper version SuperSU to the phone (adb push, or put the file on SD card).
Still stuck in boot loop... but different place.
Whew!! OK, so I got past that hurdle (Thank you so much). I'm using the WinDroid Toolkit version 3.1 to unlock the bootloader, flash the TWRP, then flash the SuperSU. The phone is now stuck at the bootloader. If I select "Recovery" it simply comes back to the "Fastboot-usb". I've attached a screen shot (maybe) to demonstrate what I'm seeing on the phone.
*** Software status: Modified ***
*** RELOCKED ***
*** Security Warning ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.19.0.000
[email protected]
Open DSP-v56.2.2-00593-M8974_FO.0126
OS-6.20.502.5
eMMC-boot 2048MB
Apr 14 2016,19:39:46.0
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
Click to expand...
Click to collapse
Thanks for all your help, I'm a noOb to this process. Recent convert from iOS.
weismanak said:
I'm using the WinDroid Toolkit version 3.1 to unlock the bootloader, flash the TWRP, then flash the SuperSU. .
Click to expand...
Click to collapse
Meaning you used the TWRP version and SuperSU version included with the toolkit? If so, that toolkit hasn't been updated in a long time, and likely is not using the versions TWRP and SuperSU that I specified previously.
Additionally, I don't personally recommend using such toolkits. Doing so robs you of a valuable learning experience, and therefore guarantees that you stay a n00b. Also, the toolkits constitute an additional point of failure (even when they are updated) that is not necessary. I've often seen processes fail using the toolkits, when the exact same steps complete just fine if done "manually".
Since it appears you've successfully unlocked the bootloader (can be verified if it says UNLOCKED near the top of the bootloader screen), than I would advise:
1) Manually flash TWRP 3.0.2 with fastboot using the instructions here: https://twrp.me/devices/htconem8gsm.html
2) Download SuperSU 2.76 from here, and put it on SD card (alternately, adb push to phone - but that may be a bit complicated for you).
3) Boot into TWRP, under Install, navigate to the SuperSU 2.76 zip, and flash it.
redpoint73 said:
You don't need to root in order to install a custom ROM. Once you have TWRP installed, just put a ROM on the phone (download ROM direct to phone, copy to SD card, adb push, etc.), boot into TWRP, and install the ROM (also recommended to backup the stock ROM before flashing a custom ROM, and also do default wipe in TWRP before ROM flash - data, cache and Dalvik).
All custom ROMs are pre-rooted, so you don't need to root separately after flashing a ROM, either. Although, some AOSP based ROMs need root enabled in phone Settings>Developer's Options.
---------- Post added at 11:07 AM ---------- Previous post was at 11:05 AM ----------
S-on is fine. I don't know why the previous user stated SuperSU 1.56. That build is ancient, and will definitely not work on Marshmallow. Might be a typo, or they were just thinking of the wrong number (maybe 2.56).
Latest stable version SuperSU 2.76 is recommended for rooting Marshmallow: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip
But as already mentioned, you don't need root to flash custom ROMs.
Click to expand...
Click to collapse
but when checked with root checker, it is showing not rooted. i'm not able to install root apps like flashify, supersu, root explorer. they all say that the phone is not rooted. i'm on mokee 60.1 release running on my redmi 2
ajay vadaparthi said:
but when checked with root checker, it is showing not rooted. i'm not able to install root apps like flashify, supersu, root explorer. they all say that the phone is not rooted. i'm on mokee 60.1 release running on my redmi 2
Click to expand...
Click to collapse
have you flashed the latest supersu.zip ?
does the flashing process ended with success ?
you may try to enable root in developer options and see
also you are in the wrong forum
Sent from my HTC M8 using XDA Labs
Can I re-flash SuperSU over an existing one?
Hi - Long time listener, first time caller!
So, I have a similar issue. After having my HTC M9 for almost 2 years, I decided to take the plunge and get the bootloader unlocked in order for me to update to v7 Nougat (currently on v6 Marshmellow) as Vodafone UK are a little slow in getting the update push out.
I followed a UTube video and all seemed to be going well after I restarted the handset after the bootloader unlock. I then had to enable the Dev Options and enable the USB Debugging in order for me to flash SuperSU 2.46 via TWRP 3.0.2.0.
However, TWRP informed me that the root was successful and to go ahead and reboot. Which I did. But it's now stuck on the HTC One splashscreen and won't proceed any further.
I still have access to TWRP and my PC was able to find the phone when connected with a usb cable (so in a state of softbrick). The FOOLISH thing I now realise, is that I didn't do a back-up of the stock ROM before flashing SuperSU. I've tried to search for a suitable RUU that I can download and get back to stock ROM (and then to unlock the bootloader so I can get v7 Nougat OTA). I'm surprised that there isn't a suitable RUU for my device (details below) and the 2 zips that I have downloaded via XDA simply wouldn't extract for me to get into the tool to flash the stock.
I've decided to go for a custom ROM (one that is with Nougat architecture/feel) if I can't allocate an RUU for my device.
I've come across too many forums and advice that I'm now overloaded with info and not sure which one to follow! Any help would be greatly appreciated as this device is one of the best handsets I've ever had (I've had handsets from early 2000's inc. an iPoo) and need to get it back up and running.
From the bootloader menu these are the details I have:
HTC_HIMA UHL PVT S-ON
LK - 1.0.0.0000
Radio - 01.01_U11440792_96.00.51201G_F
OpenDSP - 15.6.1.0052.8994_1026
OS - 3.35.161.12
Dec 17 2015, 00:40:10 (671447)
MRA58K_Release-Keys
This is a UK Vodafone carrier, model OPJA100 fcc id NM8OPJA100 M9u.
As the title of this thread suggests; can I simply delete the SuperSU v2.46 zip from the root directory, and download / paste SuperSU v2.76 to fix the stuck bootloader screen?
Or, as I have 2 downloads of the RUU.zip file, can I rename one, place it on my external SD card (64gb), go to bootloader and let the device install the stock?
As this device is softbricked, I'm open to suggestions for either stock ROM or custom ROM install.
Thanks in advance.
tigarstyle said:
Hi - Long time listener, first time caller!
So, I have a similar issue. After having my HTC M9 for almost 2 years, I decided to take the plunge and get the bootloader unlocked in order for me to update to v7 Nougat (currently on v6 Marshmellow) as Vodafone UK are a little slow in getting the update push out.
I followed a UTube video and all seemed to be going well after I restarted the handset after the bootloader unlock. I then had to enable the Dev Options and enable the USB Debugging in order for me to flash SuperSU 2.46 via TWRP 3.0.2.0.
However, TWRP informed me that the root was successful and to go ahead and reboot. Which I did. But it's now stuck on the HTC One splashscreen and won't proceed any further.
I still have access to TWRP and my PC was able to find the phone when connected with a usb cable (so in a state of softbrick). The FOOLISH thing I now realise, is that I didn't do a back-up of the stock ROM before flashing SuperSU. I've tried to search for a suitable RUU that I can download and get back to stock ROM (and then to unlock the bootloader so I can get v7 Nougat OTA). I'm surprised that there isn't a suitable RUU for my device (details below) and the 2 zips that I have downloaded via XDA simply wouldn't extract for me to get into the tool to flash the stock.
I've decided to go for a custom ROM (one that is with Nougat architecture/feel) if I can't allocate an RUU for my device.
I've come across too many forums and advice that I'm now overloaded with info and not sure which one to follow! Any help would be greatly appreciated as this device is one of the best handsets I've ever had (I've had handsets from early 2000's inc. an iPoo) and need to get it back up and running.
From the bootloader menu these are the details I have:
HTC_HIMA UHL PVT S-ON
LK - 1.0.0.0000
Radio - 01.01_U11440792_96.00.51201G_F
OpenDSP - 15.6.1.0052.8994_1026
OS - 3.35.161.12
Dec 17 2015, 00:40:10 (671447)
MRA58K_Release-Keys
This is a UK Vodafone carrier, model OPJA100 fcc id NM8OPJA100 M9u.
As the title of this thread suggests; can I simply delete the SuperSU v2.46 zip from the root directory, and download / paste SuperSU v2.76 to fix the stuck bootloader screen?
Or, as I have 2 downloads of the RUU.zip file, can I rename one, place it on my external SD card (64gb), go to bootloader and let the device install the stock?
As this device is softbricked, I'm open to suggestions for either stock ROM or custom ROM install.
Thanks in advance.
Click to expand...
Click to collapse
your first post in the wrong forum this forum for m8 )
if you can flash a rom then flash it,will save the hassle of flashing RUU
and you used an outdated version of supersu ( i don't know if this will fix it but try to flash the latest version on top the older )
you can rename the RUU to 0PJAIMG.zip and put it in the sd card root ( formatted as fat32 or exfat , 3.xx can flash RUU from exfat cards ) then reboot to download mode and follow the instruction
if you have any question ask in the m9 forum as you may get a wrong answer here :silly:
Thanks a lot. I didn't realise this forum was for M8 only, my mistake. I've now posted in the correct forum.
I'll see what they suggest, but I didn't want to flash another SuperSU on top of another in case my phone was hard bricked. I guess I'm lucky that I have a connection with the PC as I can see the internal storage of my device still and I still have access to TWRP.
One thing that the other forums I've read so far didn't mention, is whether or not it matters that I can't extract the RUU.zip file on my PC. I'm I supposed to just place it on the SD Card and let it flash the Stock ROM, or do I need to extract the zip file in order to get to the utility program? Just thought it might be worth sharing for anyone who is on M8 and stuck on the HTC One splashscreen like I am.
tigarstyle said:
I'll see what they suggest, but I didn't want to flash another SuperSU on top of another in case my phone was hard bricked.
Click to expand...
Click to collapse
If the phone was hard bricked, you wouldn't be able to flash anything. The screen wouldn't come on at all. A hard brick means you need to open the phone to repair it (new motherboard or JTAG, at a minimum). You don't have a hard brick.
Do you mean to ask if flashing the proper SuperSU would brick the phone (if its safe to flash)? If that is the question, you best direct it to folks knowledgeable to the M9. On the M8, its fine to flash the newer SuperSU (and the proper fix after flashing obsolete SuperSU). But that doesn't meant the M9 is the same. And following advice meant for another device can possibly damage the device.
tigarstyle said:
One thing that the other forums I've read so far didn't mention, is whether or not it matters that I can't extract the RUU.zip file on my PC. I'm I supposed to just place it on the SD Card and let it flash the Stock ROM, or do I need to extract the zip file in order to get to the utility program?
Click to expand...
Click to collapse
Nowhere in any instructions for flashing RUU.zip will you see anything about extracting files from the RUU.zip.
Therefore, don't do it.
The file is encrypted and signed. Even if you were able to extract anything, you wouldn't be able to flash it with s-on (s-on can't flash unsigned RUU zips).
Excellent, thank you. I was wondering why the zip file wouldn't extract on the PC. I saw videos explaining that in other to get to Stock ROM, you'd do it via the RUU.zip. So when I downloaded the RUU.zip Stock ROM file, I thought I had to extract the zip in order to get to the application, then flash the device.
Thanks for taking the time out to explain in detail...much appreciated.
I rooted my HTC 10 by unlocking bootloader, flashing TWRP , making a backup, and installing SuperSU. I don`t really want root no more, and want to know the best method for un-rooting. Has any one tried the SuperSU full unroot method on this phone? Also I know to install the RUU from HTC is a good option, but in regards to the unlocked bootloader do you have to relock it to install the RUU ? If so can anyone explain why ? Everytime I try to "fastboot oem lock" to relock the bootloader it says "waiting for device" even after verifying that it is connected through "fastboot devices" any ideas ?
Are you using htc's fastboot and not Google's fastboot?
I don't remember locking my bootloader before running the RUU exe.
I didn't lock it when I flashed it from the external SD card.
There are YouTube videos for the latter method.
You dont have to do anything, just flash the RUU and thats it.
You can also unroot without installing an RUU. Just open up SuperSu and click full unroot. I havent tried it myself.
For relocking the bootloader there are several guides.
I had to use the supersu full unroot to get my Snapchat to work, and it worked just fine for me. I'm not an expert, but I chose no when it asked me about doing a system restore and it worked out fine. Best of luck!
I've got a HTC 10 incoming (international model/not US as far as I know), and I'm looking to root and install AdAway once I get it. This will be my first time with HTC, so I just wanted to make sure I've got everything right:
Unlock with htcdev (free, but voids warranty?) or s-off with Sunshine ($25). Does Sunshine s-off require me to unlock the phone with htcdev anyway? Which is more advisable, given I am planning on sticking with stock rom and only wanting AdAway on my device? Are there any other methods to allow flashing TWRP?
Flash TWRP
Make System Image backup with TWRP. Is this still valid when using Sunshine in step 1, or does Sunshine modify the system in some way?
Install Magisk and phh superuser.
Install AdAway
Should I return to stock recovery straight after rooting? Where would I get a compatible stock recovery?
And to install OTA's in the future:
Extract stock recovery img from OTA
Mount system as read-only in TWRP
Restore System Image backup (from original TWRP install procedure). Will this wipe apps/user data?
Fastboot flash stock recovery from step 1
Reboot and install OTA. Do I need to unroot before attempting to install OTA's?
Do I have anything wrong or is there anything I've missed? Anything I should be cautious of? Partial answers, tips, tricks, anything will be appreciated!
Holoryn said:
I've got a HTC 10 incoming (international model/not US as far as I know), and I'm looking to root and install AdAway once I get it. This will be my first time with HTC, so I just wanted to make sure I've got everything right:
Unlock with htcdev (free, but voids warranty?) or s-off with Sunshine ($25). Does Sunshine s-off require me to unlock the phone with htcdev anyway? Which is more advisable, given I am planning on sticking with stock rom and only wanting AdAway on my device? Are there any other methods to allow flashing TWRP?
Flash TWRP
Make System Image backup with TWRP. Is this still valid when using Sunshine in step 1, or does Sunshine modify the system in some way?
Install Magisk and phh superuser.
Install AdAway
Should I return to stock recovery straight after rooting? Where would I get a compatible stock recovery?
And to install OTA's in the future:
Extract stock recovery img from OTA
Mount system as read-only in TWRP
Restore System Image backup (from original TWRP install procedure). Will this wipe apps/user data?
Fastboot flash stock recovery from step 1
Reboot and install OTA. Do I need to unroot before attempting to install OTA's?
Do I have anything wrong or is there anything I've missed? Anything I should be cautious of? Partial answers, tips, tricks, anything will be appreciated!
Click to expand...
Click to collapse
You don't need sunshine for what you want, bootloader unlock is fine.
Sunshine doesn't change the system. Yea always make a backup before changing anything.
No need to reinstall stock recovery after root.
For OTA you need stock image and boot and recovery. Check out one of many "how to take ota" threads for detailed instructions. Restoring system image will not wipe data.
Once you restore system image/boot you will lose root, no need to unroot any further.