http://www.androidauthority.com/community/threads/how-to-root-the-htc-one-m9-5-0-2-windows.18546/
I have not tried it yet, but on the site it says it works for the att variant... I'll try it tomorrow when I get mine...
Sent from my Nexus 5 using XDA Free mobile app
cables2590 said:
http://www.androidauthority.com/community/threads/how-to-root-the-htc-one-m9-5-0-2-windows.18546/
I have not tried it yet, but on the site it says it works for the att variant... I'll try it tomorrow when I get mine...
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Those are good instructions :good:.
Captain_Throwback said:
Those are good instructions :good:.
Click to expand...
Click to collapse
Hey Captain! Had to switch to AT&T for work so I'm here now. I want to root, but I'm sure there will be a bevy of updates in the near future, so I was wondering if you know if the stock AT&T M9 Recovery is available or even RUU?
I tried using those instructions, but there is no fastboot option in when I reboot using the Volume Down / Power button. Trying adb reboot fastboot just reboots the phone.
dratsablive said:
I tried using those instructions, but there is no fastboot option in when I reboot using the Volume Down / Power button. Trying adb reboot fastboot just reboots the phone.
Click to expand...
Click to collapse
Fastboot works in Download mode. That's where you need to be.
OK I can get to download mode with
adb reboot bootloader
fastboot devices returns my device serial number
But when I use fastboot oem get_identifier_token I get an error:
C:\fastboot>fastboot oem get_identifier_token
...
FAILED (remote: unknown command)
finished. total time: 0.004s
When booted into bootloader I get this on the screen:
Software Status Official
LOCKED
S-ON
REBOOT
REBOOT TO BOOTLOADER
BOOT TO DOWNLOAD MODE
BOOT TO RECOVERY MODE
POWER DOWN
OK I was able to get the bootloader unlocked and rooted. My problem was trying to use Windows. When my device was connected, and I tried adb devices, it would list my device 3 times. Therefore I had problems using any adb commands, so I decided to use Fedora Linux.
First time I was using the wrong mode, bootloader, instead of download. Then when I did get to download, I was getting <Waiting for Device> I figured I probably needed to use sudo. Once I did that, the unlock process worked, and was able to install root afterwards.
Now what I need to know, is there a way to easily remove that AT&T tattoo on the back of the phone?
i don't think its possible to get root on the M9 at&t until we get S-OFF
basedboii said:
i don't think its possible to get root on the M9 at&t until we get S-OFF
Click to expand...
Click to collapse
Not true, I have an AT&T M9 and was able to root using the instructions.
I'm rooted and running LeeDroid rom from the international m9 thread.
basedboii said:
i don't think its possible to get root on the M9 at&t until we get S-OFF
Click to expand...
Click to collapse
I'm also AT&T and was able to root with instructions. Why would rooting need S-off??
Sent from my HTC One M9 using XDA Free mobile app
borillako said:
I'm also AT&T and was able to root with instructions. Why would rooting need S-off??
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
It doesn't. We need s-off to change the CID and flash other ruu's, such as the dev edition ruu. I believe we need s-off to completely return to stock(removing the tampered flag).
lyall29 said:
I'm rooted and running LeeDroid rom from the international m9 thread.
Click to expand...
Click to collapse
Does everything work? I've unlocked the bootloader but have not installed twrp out of fear over messing something up and not being able to update / receive necessary future updates.
Sent from my HTC One M9 using Tapatalk
dantegl36 said:
Does everything work? I've unlocked the bootloader but have not installed twrp out of fear over messing something up and not being able to update / receive necessary future updates.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Yes everything appears to be working fine. I haven't had any problems in the week I've had the phone. As long as you flash the newest twrp beta(I'm using 2.8.6.3) and make a backup of your stock system before flashing any mods, then you should be able to return to stock without any problems.
Go here... http://forum.xda-developers.com/showthread.php?t=3066720 and read about specific device issues in post 2. Make sure that you read the entire OP (especially post 2) before asking questions in the thread.
Go here... http://forum.xda-developers.com/showthread.php?t=3066720 and read about specific device issues in post 2. Make sure that you read the entire OP (especially post 2) before asking questions in the thread.[/QUOTE]
Thanks for the link. I read through the first two posts and have a question. Why is it so important to receive OTA update? I thought after rooting, custom recovery,and installed custom rom, you just update (manually flash) the custom rom's new updates as they come out. And the versions of the custom rom is usually based on the new official OTA release anyways no?
mf1tym said:
Go here... http://forum.xda-developers.com/showthread.php?t=3066720 and read about specific device issues in post 2. Make sure that you read the entire OP (especially post 2) before asking questions in the thread.
Click to expand...
Click to collapse
Thanks for the link. I read through the first two posts and have a question. Why is it so important to receive OTA update? I thought after rooting, custom recovery,and installed custom rom, you just update (manually flash) the custom rom's new updates as they come out. And the versions of the custom rom is usually based on the new official OTA release anyways no?[/QUOTE]
I think the OTA file needs to be modified so it can be flashed by a custom recovery.
Related
I have an AT&T HOX+ running stock. It's unlocked via HTC and rooted. I cannot download any OTAs. I learned the hard way that you cannot download OTAs if you have any stock apps disabled so I've re-enabled them. Now it goes through the motions and finds the update, but when I connect to Wifi all I see is a blank message as seen in the attached screenshot.
Nilpo said:
I have an AT&T HOX+ running stock. It's unlocked via HTC and rooted. I cannot download any OTAs. I learned the hard way that you cannot download OTAs if you have any stock apps disabled so I've re-enabled them. Now it goes through the motions and finds the update, but when I connect to Wifi all I see is a blank message as seen in the attached screenshot.
Click to expand...
Click to collapse
Maybe Unroot and try.......
You must first flash the stock recovery and then relock bootloader using the command "fastboot oem lock" in fastboot. The stock recovery.img can be flashed using the fastboot command "fastboot flash recovery recovery.img" where "recovery.img" is replaced with whatever your recovery name is and .img. Make sure you flash the recovery before relocking. Root should not mess up the update although you will lose root after the update. I updated while the device was still rooted!
Sent from my HTC One X+ using xda developers app
[email protected] said:
Maybe Unroot and try.......
Click to expand...
Click to collapse
Is there a way to unroot without losing data? I haven't found one yet.
ryandroid226 said:
You must first flash the stock recovery and then relock bootloader using the command "fastboot oem lock" in fastboot. The stock recovery.img can be flashed using the fastboot command "fastboot flash recovery recovery.img" where "recovery.img" is replaced with whatever your recovery name is and .img. Make sure you flash the recovery before relocking. Root should not mess up the update although you will lose root after the update. I updated while the device was still rooted!
Sent from my HTC One X+ using xda developers app
Click to expand...
Click to collapse
So there's no way to update and run a custom recovery? If I have to relock the bootloader, I can't unlock again without factory wiping.
Why can't HTC just get the bluetooth right from the start? How did they even release a phone when BT doesn't work?
Nilpo said:
Is there a way to unroot without losing data? I haven't found one yet.
Click to expand...
Click to collapse
It's not the unrooting that will cause you to lose any data or other content on your device. It is the re-unlocking of the bootloader or the running of a RUU. AFAIK, there is no way to keep your device contents while you update the radio and hboot. The only option is to backup contents of SD, backup apps using Google or TiBU, and backup sms and call log. I may be wrong but I'm pretty sure this is how it goes. With that being said, it is not mandatory that you upgrade the radio/hboot in order to install a ROM that is sense 5/JB 4.2.2. There are already ROM's out there for AT&T built on this base
Sent from my HTC One X+ using xda developers app
Nilpo said:
Is there a way to unroot without losing data? I haven't found one yet.
Click to expand...
Click to collapse
Yeah u can unroot using SuperSU App itself from the setting choose Full Unroot........
Unintsall all the root Apps too since it unnecessary to have then without root.......
Flash the Stock recovery and relock the bootloader and then check for updates.....:good:
ryandroid226 said:
It's not the unrooting that will cause you to lose any data or other content on your device. It is the re-unlocking of the bootloader or the running of a RUU. AFAIK, there is no way to keep your device contents while you update the radio and hboot. The only option is to backup contents of SD, backup apps using Google or TiBU, and backup sms and call log. I may be wrong but I'm pretty sure this is how it goes. With that being said, it is not mandatory that you upgrade the radio/hboot in order to install a ROM that is sense 5/JB 4.2.2. There are already ROM's out there for AT&T built on this base
Sent from my HTC One X+ using xda developers app
Click to expand...
Click to collapse
If I unroot and install the OTA, and then unlock the bootloader again, with it keep the updated firmware or drop back to factory?
If I'm going through all this trouble, maybe I should be looking at a custom ROM. Any suggestions for a Sense 5 one built on AT&T? I haven't seen one for this phone.
Nilpo said:
If I unroot and install the OTA, and then unlock the bootloader again, with it keep the updated firmware or drop back to factory?
If I'm going through all this trouble, maybe I should be looking at a custom ROM. Any suggestions for a Sense 5 one built on AT&T? I haven't seen one for this phone.
Click to expand...
Click to collapse
The unlocking will wipe ur Storage.....but u ll have the update of 4.2.2..
there are few Custom ROMS with Sense 5 u can go through this Forum
Nilpo said:
If I unroot and install the OTA, and then unlock the bootloader again, with it keep the updated firmware or drop back to factory?
If I'm going through all this trouble, maybe I should be looking at a custom ROM. Any suggestions for a Sense 5 one built on AT&T? I haven't seen one for this phone.
Click to expand...
Click to collapse
If you update via the OTA then your factory firmware WILL be updated. Maybe you can request that a dev make a ROM that is stock and rooted sense5/JB 4.2.2, you might grab the interest of someone.. That way you could have a "stock" image of the ROM and avoid the radio/hboot upgrade. Otherwise, you will just have to go through the update process, wiping your device. IMO, backing everything up is not too painstaking and it is a good practice to do this periodically anyways. Just my .02!
Sent from my HTC One X+ using xda app-developers app
Backing up isn't too difficult on JB. I've done it manually as well as with Helium and other apps throughout the rooting/experimenting process. It's been my experience that those app backups don't restore properly and I'm left starting over anyway. The issues could be app specific, but I honestly don't remember which apps didn't work now.
Of course, I suppose it's all a small price to pay to have a phone that actually works when I connect my BT headset.
Where does one find the stock recovery?
I hope this isn't silly, but I've been running custom recovery forever and I'm blanking as to where to locate/d-load the stock recovery.
thanks!
mrbillishere said:
Where does one find the stock recovery?
I hope this isn't silly, but I've been running custom recovery forever and I'm blanking as to where to locate/d-load the stock recovery.
thanks!
Click to expand...
Click to collapse
Not sill at all. I have an image that I believe is the stock recovery, but how can I be sure?
Nilpo said:
Not sill at all. I have an image that I believe is the stock recovery, but how can I be sure?
Click to expand...
Click to collapse
OK, well after dusting off the cobwebs and reading some threads for the Intl version I learned this... the stock firmware will also contain the radios and stock recovery. So now I'm looking for the correct firmware to match my phone's CID and Modelid. The command to dump these variables out is 'fastboot getvar all'
My AT&T OneX+ reported this:
(bootloader) modelid: PM6310000
(bootloader) cidnum: CWS__001
There's a txt file in the firmware.zip that will contain a list of the applicable CID numbers the firmware can apply to. Evidently since our phones are S-on an entry in the list must correspond to the device's reported CID.
So now I'm searching for an updated firmware.zip
You can find the stock rom here as found in this thread.
Hi All,
I bought this refurbished AT&T unlocked HTC One from eBay. I am with T Mobile.
I already unlocked the bootloader and rooted the phone. Why I did this:
1) I wanted to remove all the AT&T stuff including their update check which doesn't work with T Mobile SIM. (But not able to do it even after uninstalling with Titanium, those just come back on restart)
2) I wanted KitKat (either like an unlocked or international HTC one or the Google Play KitKat)
But I am not sure how to proceed.
I already have downloaded a ROM from this link: htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one
But not sure about S-OFF/ON etc because I am a newbie, this is my second android phone and first rooting.
Can anyone give me step by step instructions to install either a google play kitkat or a pure sense 5.5 kitkat? I would prefer if I can do this just once now and get future updates automatically from google/htc.
Mine is Android 4.3 based Sense 5.0 with all the AT&T stuff. I am in the US.
There is no real difference between AT&T Kitkat and Jellybean on the One. In fact there are a few bugs with Kitkat. Such as the camera and a few others that have been posted.
njaustin123 said:
Hi All,
I bought this refurbished AT&T unlocked HTC One from eBay. I am with T Mobile.
I already unlocked the bootloader and rooted the phone. Why I did this:
1) I wanted to remove all the AT&T stuff including their update check which doesn't work with T Mobile SIM. (But not able to do it even after uninstalling with Titanium, those just come back on restart)
2) I wanted KitKat (either like an unlocked or international HTC one or the Google Play KitKat)
But I am not sure how to proceed.
I already have downloaded a ROM from this link: htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one
But not sure about S-OFF/ON etc because I am a newbie, this is my second android phone and first rooting.
Can anyone give me step by step instructions to install either a google play kitkat or a pure sense 5.5 kitkat? I would prefer if I can do this just once now and get future updates automatically from google/htc.
Mine is Android 4.3 based Sense 5.0 with all the AT&T stuff. I am in the US.
Click to expand...
Click to collapse
You could just try this
http://forum.xda-developers.com/showthread.php?t=2659374
I dont want AT&T again
mb_guy said:
You could just try this
http://forum.xda-developers.com/showthread.php?t=2659374
Click to expand...
Click to collapse
I dont want AT&T again.
njaustin123 said:
I dont want AT&T again.
Click to expand...
Click to collapse
I'd say switch to the Developer Edition rom, it doesn't contain all of the AT&T bloat.
1. Unlock the bootloader here.
2. S-Off via rummrunner or firewater.
3. Change CID to BS_US001 'fastboot oem writecid BS_US001'
4. Install Developer Edition 4.3 RUU, get it here.
5. Take OTA to 4.4.2.
There are guides in the One General and Q&A sections that cover all of this. Do a lot of reading, and then ask questions as needed.
Thanks. Any more Info?
cschmitt said:
I'd say switch to the Developer Edition rom, it doesn't contain all of the AT&T bloat.
1. Unlock the bootloader
2. S-Off via rummrunner or firewater.
3. Change CID to BS_US001 'fastboot oem writecid BS_US001'
4. Install Developer Edition 4.3 RUU, get it
5. Take OTA to 4.4.2.
There are guides in the One General and Q&A sections that cover all of this. Do a lot of reading, and then ask questions as needed.
Click to expand...
Click to collapse
Thanks a lot Schmitt. I think that is exactly what I have to do.
My bootloader is already unlcoked, Also I think I can handle Step 2 and Step3. Could you please pour or point me to more info on Step 4 and 5. Links to discussions here or other links will do. Being a newbie I am totally confused about stock, kernel, RUU etc.
njaustin123 said:
Could you please pour or point me to more info on Step 4 and 5. Links to discussions here or other links will do. Being a newbie I am totally confused about stock, kernel, RUU etc.
Click to expand...
Click to collapse
The RUU is easy, it is a complete software package for the phone that will restore it to the original software of the Developer Edition phones.
For the RUU to work, the CID (carrier id) must be set to BS_US001. This why you'll need to s-off the phone, so that you can change the CID.
Go to http://www.htcdev.com/devcenter/downloads and select 'Brightstar US' as the carrier, then 'Find Files' and download the 'RUU 3.22.1540.1 Developer Edition'. It is an EXE, just run it with the phone connected to the USB port of the computer and it will walk you through the install. After it reboots you will have developer edition 4.3, then update to 4.4.2 by OTA, just check in the Software Update menu in settings on the phone. It will download a file to the phone that will update it.
rumrunner didn't work
cschmitt said:
The RUU is easy, it is a complete software package for the phone that will restore it to the original software of the Developer Edition phones.
For the RUU to work, the CID (carrier id) must be set to BS_US001. This why you'll need to s-off the phone, so that you can change the CID.
.
Click to expand...
Click to collapse
rumrunner gave this error:
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
njaustin123 said:
rumrunner gave this error:
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
Click to expand...
Click to collapse
Flash the ElementalX kernel from here http://forum.xda-developers.com/showthread.php?p=40682393 and try again.
It's unsecured and should make rumrunner successful.
Thanks. It's S-OFF Now
cschmitt said:
Flash the ElementalX kernel from here and try again.
It's unsecured and should make rumrunner successful.
Click to expand...
Click to collapse
Thanks a lot. I did the kernel update and then S-OFF. Will try RUU tonight.
njaustin123 said:
Thanks a lot. I did the kernel update and then S-OFF. Will try RUU tonight.
Click to expand...
Click to collapse
See, this stuff is easy. You'll like the Dev Edition ROM.
In Dev Edition
cschmitt said:
See, this stuff is easy. You'll like the Dev Edition ROM.
Click to expand...
Click to collapse
Thank you again. I installed 4.3 RUU and OTAed to KitKat.
Very much satisfied and happy with it.
Some questions:
My root and custom kernel are gone. Even the TWRP recovery is lost.
Do I need to flash TWRP as recovery again? And install SU and 4.4 ElementalX again for root and getting the kernel? If yes and if I do these, will my future OTAs be blocked?
njaustin123 said:
Thank you again. I installed 4.3 RUU and OTAed to KitKat.
Very much satisfied and happy with it.
Some questions:
My root and custom kernel are gone. Even the TWRP recovery is lost.
Do I need to flash TWRP as recovery again? And install SU and 4.4 ElementalX again for root and getting the kernel? If yes and if I do these, will my future OTAs be blocked?
Click to expand...
Click to collapse
Yes
yes and Yes
you get future OTA by returning to stock first (flashing stock recovery will sometimes be all that's needed)
How do I flash stock recovery?
clsA said:
Yes
yes and Yes
you get future OTA by returning to stock first (flashing stock recovery will sometimes be all that's needed)
Click to expand...
Click to collapse
How do I flash stock recovery? If that alone doesn't work, is a complete installation with RUU the only way?
njaustin123 said:
How do I flash stock recovery? If that alone doesn't work, is a complete installation with RUU the only way?
Click to expand...
Click to collapse
Flash it using fastboot just like you would flash TWRP. The stock recovery can be pulled out of a firmware.zip.
Could not find the recovery image
cschmitt said:
Flash it using fastboot just like you would flash TWRP. The stock recovery can be pulled out of a firmware.zip.
Click to expand...
Click to collapse
I got the notification for 4.19.1540.9 update. I was about to go back to the stock recovery to update this.
But could not unzip the recovery image from the RUU zip
(PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip). It was not unzippable and even after repairing it with zip_repair tool I could not get the recovery image.
Also I downloaded recovery_1.29.1540.16_R.img from another xda post. That didn't work. After giving start update, it was stuck at a red triangle with a warning sign.
njaustin123 said:
I got the notification for 4.19.1540.9 update. I was about to go back to the stock recovery to update this.
But could not unzip the recovery image from the RUU zip
(PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip). It was not unzippable and even after repairing it with zip_repair tool I could not get the recovery image.
Also I downloaded recovery_1.29.1540.16_R.img from another xda post. That didn't work. After giving start update, it was stuck at a red triangle with a warning sign.
Click to expand...
Click to collapse
I think both of those recoveries are too old, you need the one for your currently installed kitkat version.
Any idea where can I get it?
mb_guy said:
I think both of those recoveries are too old, you need the one for your currently installed kitkat version.
Click to expand...
Click to collapse
Any idea where can I get it?
njaustin123 said:
Any idea where can I get it?
Click to expand...
Click to collapse
I can't find the 4.19.1540.x version but I believe any 4.19.x.x version will work.
I think the stock recovery may be in this dark bootloader firmware download .
http://www.htc1guru.com/downloads/firmware-downloads/
Get the 4.19.401.8 download and see if the recovery.img is included.
Best I can come up with for now.
No. That doesn't have it
mb_guy said:
I can't find the 4.19.1540.x version but I believe any 4.19.x.x version will work.
I think the stock recovery may be in this dark bootloader firmware download .
http://www.htc1guru.com/downloads/firmware-downloads/
Get the 4.19.401.8 download and see if the recovery.img is included.
Best I can come up with for now.
Click to expand...
Click to collapse
I just downloaded it and checked, it doesn't have the recovery.img
Ok... so I have unlocked my boot-loader, what do I need to do to root my phone?
I am not S-off yet, do I need to be S-off before root is possible?
Pure+ said:
Ok... so I have unlocked my boot-loader, what do I need to do to root my phone?
Click to expand...
Click to collapse
You don't need S-Off to root. Since you've already unlocked the bootloader, I suggest using this program to flash a custom recovery (ex TWRP or Philz) then select perm root. The application guides you through most of it. If you need more help with the program itself, check the main thread or one of the support links in the program.
Link: http://forum.xda-developers.com/showthread.php?t=2699065
akitten007 said:
You don't need S-Off to root. Since you've already unlocked the bootloader, I suggest using this program to flash a custom recovery (ex TWRP or Philz) then select perm root. If you need more help with the program itself, check the main thread or one of the support links in the program.
Link: http://forum.xda-developers.com/showthread.php?t=2699065
Click to expand...
Click to collapse
That's the tool i used to unlock BL. I just wasn't sure what the exact steps for Root were. Which Recovery is the most stable of the 2? I'm most familiar with TWRP but if the alternate option is more stable then I will go that route.
Pure+ said:
That's the tool i used to unlock BL. I just wasn't sure what the exact steps for Root were. Which Recovery is the most stable of the 2? I'm most familiar with TWRP but if the alternate option is more stable then I will go that route.
Click to expand...
Click to collapse
I usually run with TWRP, but both recoveries are stable. If you look in the roms section, most require Philz recovery so if you want to flash roms I would go with that. And here is a link from the program that shows a step by step process of unlocking and rooting. Just skip the unlocking portion
http://forum.xda-developers.com/showthread.php?t=2066390
akitten007 said:
I usually run with TWRP, but both recoveries are stable. If you look in the roms section, most require Philz recovery so if you want to flash roms I would go with that. And here is a link from the program that shows a step by step process of unlocking and rooting. Just skip the unlocking portion
http://forum.xda-developers.com/showthread.php?t=2066390
Click to expand...
Click to collapse
So I installed TWRP and I'm rooting now. What's the best way to update TWRP to the latest version. It installed 2.7.0.2 and I'd Like to install 2.7.0.4
Pure+ said:
So I installed TWRP and I'm rooting now. What's the best way to update TWRP to the latest version. It installed 2.7.0.2 and I'd Like to install 2.7.0.4
Click to expand...
Click to collapse
Grab the img from the thread here: http://forum.xda-developers.com/showthread.php?t=2695709
Then you need to use fastboot to flash recovery. Hold shift and right click the data folder of the toolkit. Select open command window from here. Then type commands listed below in order.
adb reboot fastboot
fastboot flash recovery recovery.img(rename twrp img to this)
fastboot reboot
akitten007 said:
Grab the img from the thread here: http://forum.xda-developers.com/showthread.php?t=2695709
Then you need to use fastboot to flash recovery. Hold shift and right click the data folder of the toolkit. Select open command window from here. Then type commands listed below in order.
adb reboot fastboot
fastboot flash recovery recovery.img(rename twrp img to this)
fastboot reboot
Click to expand...
Click to collapse
Thanks. I actually just ended up using the toolkit to install for me before i saw this. But next time I'll know lol
akitten007 said:
I usually run with TWRP, but both recoveries are stable. If you look in the roms section, most require Philz recovery so if you want to flash roms I would go with that. And here is a link from the program that shows a step by step process of unlocking and rooting. Just skip the unlocking portion
http://forum.xda-developers.com/showthread.php?t=2066390
Click to expand...
Click to collapse
Hey btw I really appreciate all the help you've provided me. Might not be rooted right now without it. I do have one more question, what are the benefits of S-off?
Pure+ said:
Thanks. I actually just ended up using the toolkit to install for me before i saw this. But next time I'll know lol
Click to expand...
Click to collapse
No problem. Hope I was able to help
---------- Post added at 10:22 AM ---------- Previous post was at 10:19 AM ----------
Pure+ said:
Hey btw I really appreciate all the help you've provided me. Might not be rooted right now without it. I do have one more question, what are the benefits of S-off?
Click to expand...
Click to collapse
S-Off allows write permissions to the firmware, radio, and bootloader partitions. Some roms, like the GPE ones I believe, require S-Off, but most stock sense roms do not. You can also sim unlock with S-Off. Those are the primary uses, but someone feel free to chime in if I missed something. This is my 3rd day with the M8 lol
There's also this: http://forum.xda-developers.com/showthread.php?t=2718626
twrp 2702 from official site is newer that the 2704 unofficial. grab img from official site
fastboot flash recovery twrp.img
IF all your wanting to do is flash roms then no need for s-off...if just learning and are leary of a brick stay safe with s-on....Theres always a chance when messing with partitions that are locked with s-on
S-Off is good for preventing brick in some situations, of course people still manage to brick their phones with s off, but to achieve S-Off you have to be familiar with adb and fastboot commands. If you required the toolkit for root, ie you do not know how to use adb and fastboot commands, I wouldn't recommend doing it until you are familiar with that. There are several guides, take some time to read and you should have a good start.
Sent from my HTC One_M8
My phone is rooted.
andrewnelson said:
My phone is rooted.
Click to expand...
Click to collapse
Did the posts here make that possible? I know I wouldn't be rooted right now without their help.
Sent from my HTC One_M8 using Tapatalk
Now that we have our own specific forum, would it be plausible to get some sort of step-by-step guide on how to go about installing the KitKat OTA if you're rooted? In browsing through the megathread from before, I get the impression that I will need to flash the stock recovery and relock my bootloader, then unlock once again once I've updated, but the thread itself is a bit daunting and the advice is pretty well scattered amid the various conversations there. Can we get some sort of consolidated guide from someone more knowledgeable than myself?
(Thank you in advance, by the way. I know I will be highly appreciative.)
groverXIII said:
Now that we have our own specific forum, would it be plausible to get some sort of step-by-step guide on how to go about installing the KitKat OTA if you're rooted? In browsing through the megathread from before, I get the impression that I will need to flash the stock recovery and relock my bootloader, then unlock once again once I've updated, but the thread itself is a bit daunting and the advice is pretty well scattered amid the various conversations there. Can we get some sort of consolidated guide from someone more knowledgeable than myself?
(Thank you in advance, by the way. I know I will be highly appreciative.)
Click to expand...
Click to collapse
This is what I followed, though you are going to lose data...
TehFlash said:
If you have the different partition layout that was introduced with the KitKat update, and also have the upgraded HBOOT then I guess i'll write up this guide. To get the phone back in proper working order, you need to do this.
1) Make sure you have the HTC drivers installed, and HTC Sync Manager fully uninstalled. ADB/Fastboot and such in working order, etc.
2) Download the KitKat OTA ZIP from Duir's Drive Folder here https://drive.google.com/uc?id=0B-kSF8g8H7KudEFRU1hPMjRObU0&export=download and open it up and take out firmware.zip
3) Get into HBOOT on the phone, and flash that firmware.zip file by running fastboot flash zip firmware.zip and also run fastboot flash update firmware.zip both will say FAIL but for me that worked if that didn't work then relock your device by running fastboot oem lock and then get back to fastboot and run fastboot oem rebootRUU (case-sensitive) and then issue fastboot flash zip firmware.zip and also run fastboot flash update firmware.zip and reboot to fastboot again
4) If you had to relock your device unlock it by getting your Unlock_code.bin from HTCdev and issue this command when you're in fastboot which is fastboot flash unlocktoken Unlock_code.bin
5) download Duir's TWRP recovery built for KitKat which is located here https://drive.google.com/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing grab the openrecovery-twrp-2.7.1.1-zaracl.img and then flash that by issuing fastboot flash recovery openrecovery-twrp-2.7.1.1-zaracl.img
6) Boot up into recovery, and format Data middle button on the right and type in 'Yes' and then wipe everything (you might have to reboot back into recovery again and then wipe everything) The reason to format Data using that button is because of KitKat remapping the partitions
7) Grab the KitKat TWRP backup from here https://docs.google.com/file/d/0B8-7I2_Vt73ldUNPd2c4X0xoQXc/edit
8) while that downloads make a pseudo backup, and then when thats finished mount your SDcard and open up the KitKat TWRP backup on windows and just overwrite all the files in zara_cl442/zara_cl442 and then reboot back into recovery again.
9) Restore the Backup you made and overwrote with the KitKat TWRP backup
10) go into fastboot and go back to Duir's drive located here https://drive.google.com/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing and grab KK_stock_boot.img and then flash that by issuing fastboot flash boot KK_stock_boot.img in a command prompt
11) Reboot into the System and it should work
Click to expand...
Click to collapse
Kit Kat OTA
That seems really complicated and sort of risky. Can't we just restore stock recovery and boot. Relock boot loader. And then install the ota as downloaded.
The_Greatest_Juan said:
That seems really complicated and sort of risky. Can't we just restore stock recovery and boot. Relock boot loader. And then install the ota as downloaded.
Click to expand...
Click to collapse
That's what I was wondering. I'm alright with re-rooting afterward (and after that I'm going S-OFF so I can use Viper4Android).
On a side note, has anyone noticed higher battery consumption with KitKat? My wife (who is unrooted and generally doesn't mess with her phone) updated and her battery died twice yesterday with no real increase in usage.
groverXIII said:
That's what I was wondering. I'm alright with re-rooting afterward (and after that I'm going S-OFF so I can use Viper4Android).
On a side note, has anyone noticed higher battery consumption with KitKat? My wife (who is unrooted and generally doesn't mess with her phone) updated and her battery died twice yesterday with no real increase in usage.
Click to expand...
Click to collapse
Get s-off first then update kk bec if things go wrong during the update u can downgrade hboot. With s-on u cant downgrade hboot. U get stuck and theres no way to fix ur device. Ive seen this happen to somebody
Child's Play said:
Get s-off first then update kk bec if things go wrong during the update u can downgrade hboot. With s-on u cant downgrade hboot. U get stuck and theres no way to fix ur device. Ive seen this happen to somebody
Click to expand...
Click to collapse
Good to know. Got a link to how to get S-OFF that would prevent me from searching through the massive thread?
groverXIII said:
Good to know. Got a link to how to get S-OFF that would prevent me from searching through the massive thread?
Click to expand...
Click to collapse
Read the instructions http://rumrunner.us/instructions/ then download rumrunner 0.5.0 under "htc universal downloads" and run it as administrator
The only thing I changed on my phone was gain root, unlock bootloader and flash Philz Touch cwm recovery. I haven't gotten s-off or changed H-boot. I don't want to change anything else if I don't have to. Is there anyway to get the update. I don't care if I lose root.
The_Greatest_Juan said:
The only thing I changed on my phone was gain root, unlock bootloader and flash Philz Touch cwm recovery. I haven't gotten s-off or changed H-boot. I don't want to change anything else if I don't have to. Is there anyway to get the update. I don't care if I lose root.
Click to expand...
Click to collapse
U should get s-off then flash stock recovery, unroot ur device and relock the bootloader then update kk by tapping "system updates" in settings or run the ruu to get everything back to stock. S-off wont be affected
Child's Play said:
U should get s-off then flash stock recovery, unroot ur device and relock the bootloader then update kk by tapping "system updates" in settings or run the ruu to get everything back to stock. S-off wont be affected
Click to expand...
Click to collapse
Alright I'll try that when I get home and let you know how it goes. Thanks a bunch.
Alright. So it didn't work. It works fine at first but at about 40% through the update it shows a red exclamation mark inside a red triangle on the phone. I unrooted and flashed the stock recovery from the development thread on the new forum. The jelly bean one. And relocked the
Bootloader. Ugh. This is really frustrating. What am I doing wrong? Do I have to get rid of s-off as well. That's fine if I do.
Sent from my HTC0P4E1 using XDA Free mobile app
The_Greatest_Juan said:
Alright. So it didn't work. It works fine at first but at about 40% through the update it shows a red exclamation mark inside a red triangle on the phone. I unrooted and flashed the stock recovery from the development thread on the new forum. The jelly bean one. And relocked the
Bootloader. Ugh. This is really frustrating. What am I doing wrong? Do I have to get rid of s-off as well. That's fine if I do.
Sent from my HTC0P4E1 using XDA Free mobile app
Click to expand...
Click to collapse
Did u delete the hcheck file when u got s-off?
Child's Play said:
Did u delete the hcheck file when u got s-off?
Click to expand...
Click to collapse
So I did not. Can you walk me through that please
Sent from my HTC0P4E1 using XDA Free mobile app
The_Greatest_Juan said:
So I did not. Can you walk me through that please
Sent from my HTC0P4E1 using XDA Free mobile app
Click to expand...
Click to collapse
Ok u didnt. Make sure everything is stock. Im not sure why its stuck at 40%
Child's Play said:
Ok u didnt. Make sure everything is stock. Im not sure why its stuck at 40%
Click to expand...
Click to collapse
So should I just run the RUU
Sent from my HTC0P4E1 using XDA Free mobile app
Some ppl had the same issue. There r instructions in the post. Whats the hboot version? Get into bootloader and tell me
Child's Play said:
Some ppl had the same issue. There r instructions in the post. Whats the hboot version? Get into bootloader and tell me
Click to expand...
Click to collapse
What post? The massive thread before we got a forum? My hboot is 2.22.0000
Sent from my HTC0P4E1 using XDA Free mobile app
The_Greatest_Juan said:
What post? The massive thread before we got a forum? My hboot is 2.22.0000
Sent from my HTC0P4E1 using XDA Free mobile app
Click to expand...
Click to collapse
Yes. U r using kk. We need a guide for ur issue we dont have to look thru all posts. Im gonna post a thread
Child's Play said:
Yes. U r using kk. We need a guide for ur issue we dont have to look thru all posts. Im gonna post a thread
Click to expand...
Click to collapse
Ok so how do I fix it?
Sent from my HTC0P4E1 using XDA Free mobile app
The_Greatest_Juan said:
Ok so how do I fix it?
Sent from my HTC0P4E1 using XDA Free mobile app
Click to expand...
Click to collapse
Im not sure what u need to do. Somebody knows
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Need to wait for hboot to be modded to have that removed
Wonders_Never_Cease said:
Need to wait for hboot to be modded to have that removed
Click to expand...
Click to collapse
Ah okay thanks. Wasnt sure if Hboot was universal or if it was by build.
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Wonders_Never_Cease said:
2.23.503.2 ota? If not s-off cannot flash firmware...if s-off the hboot has been modified already. Link is located in my thread in the at&t m8 section
Click to expand...
Click to collapse
I'm on build 2.22.401.5 running VenomOne rom, S-Off, rooted all the good stuff. Will your hboot mod work for mine?
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Wonders_Never_Cease said:
if on an att device its been discussed many times to use the appropriate firmware for us devices...2.22.1540.3/.4 is latest developer edition device firmware, 2.23.502.3 is latest for att devices...imo use one of those packages @firmware instead of euro.
Click to expand...
Click to collapse
OK and I can just install either one of those hboots over my existing one and it wont brick my phone or is this more to this?
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Wonders_Never_Cease said:
look in the htc one m8 forum since your using a euro firmware for the modified 2.22.401.5 hboot im sure its been done...
Click to expand...
Click to collapse
Found it, thanks man. Gonna mess with it a little later.
CavyS said:
Just updated to the 4.4.3 OTA then rooted flashed TWRP and install Venom One ROM. Now I get that annoying message on boot. My OCD is drving me nuts! found a few tutorials about flashing fastboot, but they all seem pretty old. Not sure if theres an update or an easy to fallow tutorial using adb or an AIO software. Thanks.
Click to expand...
Click to collapse
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
thinkhope said:
Hey Cavy..I got a couple of questions for you, if you don't mind. Were you completely stock after taking the 4.4.3 update? I just received my update a couple of days ago and I'm thinking about taking the plunge and rooting. How did you go about rooting and flashing Venom One? Thanks for your help!
Click to expand...
Click to collapse
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
CavyS said:
Yeah I was completely stock after updating. To root I used the AIO toolkit found here (http://forum.xda-developers.com/showthread.php?t=2699065) Once youre rooted reboot into recovery and make a backup. Then download the ViperOne rom here (http://venomroms.com/htc-one-m8/) copy the zip folder onto your SD or internal storage and reboot into recovery again and flash the ViperOne zip folder.
Click to expand...
Click to collapse
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
redpoint73 said:
You don't need to root if you are going to flash a custom ROM right away. Unlock bootloader, install custom recovery, then put the custom ROM on the phone and flash it.
Click to expand...
Click to collapse
It was just easier for me to fallow a set of instructions going step by step than jumping around just to avoid 1 easy step.
thinkhope said:
So the toolkit still works?? Thought I read somewhere the 4.4.3 patched something. Are you also S-OFF??
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah still works, you might of read that Firewater for some people doesnt work on 4.4.3. For me Firewater worked and I'm S-Off for some people it doesnt and you have to use Sunshine in that case.
thinkhope said:
So the toolkit still works??
Click to expand...
Click to collapse
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
redpoint73 said:
I highly recommend doing it manually and steering clear of toolkits. Using a toolkit robs you of an important learning opportunity, and leaves you with little understanding of the processes. Skills and knowledge that are important when things don't go quite right (which will inevitably happen).
Click to expand...
Click to collapse
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
I agree and that's the route I'm trying to take, however just need a bit more of a solid guide to lean on. I haven't messed around with adb or pushed anything via fastboot since my One X. Don't want to end up with a fancy paper weight.
Click to expand...
Click to collapse
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
redpoint73 said:
If you did it on your One X, its really not any different on the M8. Actually, probably a good deal easier if you had the AT&T One X (EVITA), since that phone required temp root and SuperCID to unlock the bootloader, for the most part.
In short:
-Go to HTCDev.com to unlock the bootloader. The website walks you though step-by-step, so there is really nothing to that part.
- Use adb to flash your recovery of choice (TWRP or CWM)
- Flash SU/SuperSU or flash a custom ROM
-S-off, if you want
- That's it!
Click to expand...
Click to collapse
I definitely did have the evita. Had to alter the cid to make htc dev believe it was a different phone or something like that, if I remember correctly.
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Well, sounds easy enough. I will be attempting later tonight after work. Thanks for all of your help. If it's OK, mind if I PM you if something goes wrong?
Sent from my HTC One_M8 using XDA Free mobile app
thinkhope said:
S-ON really is only if I want to mess with different radios, right? All I want is xposed and and maybe some cm 11 or gpe once Android L is out.
Click to expand...
Click to collapse
S-off is needed to flash radio, hboot, SIM unlock, and some other things. But not for root or to flash ROMs. Pretty much similar to how things were on the EVITA; with the exception that boot.img will flash automatically along with the ROM (not possible on most hboots on the EVITA, and had to be flashed manually with fastboot).
It sounds like you are already on the "official" 2.23 software (Android 4.4.3) by OTA? If so, you don't need to update firmware (radio, hboot, etc.) as the OTA already updated it. Otherwise, s-off is needed to flash the firmware manually; which is pretty much required for any 2.xx Sense based custom ROMs (otherwise there will be serious bugs like very long boot times, broken WiFi, Bluetooth). While s-off is not strictly needed to flash the ROM (it will flash correctly) things just won't run right if firmware is outdated. This is the only reason you would "need" to have s-off for flashing ROMs. AOSP and GPE ROMs won't suffer this issue.
But if you are already on the new OTA, this isn't an issue for flashing any ROM. You can verify by looking at the hboot version and baseband. If you are on hboot 3.18 and baseband 1.19; your firmware is up to date, and won't be an issue for running any ROMs.
thinkhope said:
mind if I PM you if something goes wrong?
Click to expand...
Click to collapse
I actually prefer you just posting to the forums. Either to an existing relevant thread, or start a new one if a relevant one does not already exist.
Couple reasons for this:
- Info given to you can help others reading the forums, and benefit the community as a whole instead of being hidden away in PM
- You can get help from more than just one user. I don't claim to even remotely know everything, and often its helpful to have more than one set of eyes on a problem (especially the tougher ones). And I might not even be online to help.
In particular for the 2nd point: my wife and I are going to be having a baby, with scheduled induction tomorrow (Sept. 5) unless it happens by itself sooner. So I won't be available to help you when that happens, anyway!
In any case, good luck!