Database Develop

Installing updates on stock rom with unlocked bootloader and root

So, not 12 hours after getting my HTC one a few months ago, I unlocked the bootloader and rooted. I used this method: http://dottech.org/103429/how-to-ro...ader-and-install-clockworkmod-recovery-guide/
I knew I wouldn't get OTA updates, but figured I could flash updates via stock recovery. Apparently I can't. I get an error every time, so essentially I have no options to update. I have also noticed that there are a few little bugs that are quite annoying. So, my question is: Has anyone managed to either unroot and relock the bootloader in order to install updates? Or is there a method I can use to update my One with the latest HTC provided update? I made no changes to the phone aside from unlocking the bootloader and rooting. LOVE, LOVE, LOVE this phone, but as we all know, having the latest update is a huge part of why we make changes to our phone. And with the 4.2.2 update arriving soon, I would really like to have an option of keeping my One always up to date.
Any help would be greatly appreciated.

Yes, after tampering the phone and even flashing the stock recovery gives a red triangle suring flashing ota updates.... I spent 2 days on it...
Get s off.... Flash the appropriate RUU for your phone, and let the OTA install itself by checking software updates in setting- about....
This will definitely work....
Sent from my HTC One using xda premium

Thanks Mathrania, but if you don't mind I have a few questions. 1. Is there any way to get s-off without using an adb shell? If so, can you point me to a link that has the instructions? 2. Where do I find the RUU for m7ul? No idea where to get that. I assume once i find it I can flash it using recovery? Your help appreciated man.
mathrania said:
Yes, after tampering the phone and even flashing the stock recovery gives a red triangle suring flashing ota updates.... I spent 2 days on it...
Get s off.... Flash the appropriate RUU for your phone, and let the OTA install itself by checking software updates in setting- about....
This will definitely work....
Sent from my HTC One using xda premium
Click to expand...
Click to collapse

vijn said:
Thanks Mathrania, but if you don't mind I have a few questions. 1. Is there any way to get s-off without using an adb shell? If so, can you point me to a link that has the instructions? 2. Where do I find the RUU for m7ul? No idea where to get that. I assume once i find it I can flash it using recovery? Your help appreciated man.
Click to expand...
Click to collapse
Yes there is, a saw somewhere... But i need to find it.... The title of the thread is s off without pc or something like that.... But i am outside rightnow.. Once i reach my place, i can point that out.... And why not abd????
Also, do fastboot getvar all, and post the screenshot here, just remove ur IMEI and serial from there(blackout that)... I will tell u about ur ruu too.
Sent from my HTC One using xda premium

Ok, I managed to get s-off using terminal emulator. Much easier. Now, I just gotta find the RUU. To be honest, I am not sure how to do the fastboot getvar all or what you need in a screenshot. Let me know and I'll provide it.
mathrania said:
Yes there is, a saw somewhere... But i need to find it.... The title of the thread is s off without pc or something like that.... But i am outside rightnow.. Once i reach my place, i can point that out.... And why not abd????
Also, do fastboot getvar all, and post the screenshot here, just remove ur IMEI and serial from there(blackout that)... I will tell u about ur ruu too.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse

vijn said:
Ok, I managed to get s-off using terminal emulator. Much easier. Now, I just gotta find the RUU. To be honest, I am not sure how to do the fastboot getvar all or what you need in a screenshot. Let me know and I'll provide it.
Click to expand...
Click to collapse
Boot into bootloader, connect usb cable, slect fastboot..... Now on ur PC, open the folder containing your fastboot files ( hope u have knowledge about that... You can find the fastboot files in the hasoon all in one toolkit as well.... In that folder, Shift + right click... Select open command window here...
Then in command window, type fastboot getvar all.... Copy paste the results to me.
Sent from my HTC One using xda premium

Here it is. Thanks again for your help.
mathrania said:
Boot into bootloader, connect usb cable, slect fastboot..... Now on ur PC, open the folder containing your fastboot files ( hope u have knowledge about that... You can find the fastboot files in the hasoon all in one toolkit as well.... In that folder, Shift + right click... Select open command window here...
Then in command window, type fastboot getvar all.... Copy paste the results to me.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse

delete

Thanks Agry English. Managed to get it done using the emulator method yesterday. Was much simpler. Not a fan of adb shells. Never was very good at cmd. All I need now is the RUU for my version and i should be good to go.
angry english said:
delete
Click to expand...
Click to collapse

vijn said:
Thanks Agry English. Managed to get it done using the emulator method yesterday. Was much simpler. Not a fan of adb shells. Never was very good at cmd. All I need now is the RUU for my version and i should be good to go.
Click to expand...
Click to collapse
yeah i noticed when i read firther down the post, i did mine teh same way, but adb isnt all that bad to be honest, i used it to change the MID, looks daunting but as long as you do exactly was is in the guides it will be fine, no RUU for my version so had to make it something else

well my friend, i tried to find your original RUU, but what I am getting is the link to just an OTA...not the RUU which is required to revert you to stock...anyways..
Did you relock the bootloader??? Relock and try to flash the OTA ...it should work... you can do this while being s-off...no issues...

ALright, so I guess I need to relock the bootloader. I assume this will also mean unrooting? Not entirely sure what the easiest way to relock the bootloader is. Any suggestions?
Now, out of curiosity, is there a root method that I can use after updating that will allow me to continue getting updates without having to go through this every time?
mathrania said:
well my friend, i tried to find your original RUU, but what I am getting is the link to just an OTA...not the RUU which is required to revert you to stock...anyways..
Did you relock the bootloader??? Relock and try to flash the OTA ...it should work... you can do this while being s-off...no issues...
Click to expand...
Click to collapse

vijn said:
ALright, so I guess I need to relock the bootloader. I assume this will also mean unrooting? Not entirely sure what the easiest way to relock the bootloader is. Any suggestions?
Now, out of curiosity, is there a root method that I can use after updating that will allow me to continue getting updates without having to go through this every time?
Click to expand...
Click to collapse
While you are s-off, you can relock you bootloader via a simple command....and to be frank i dont remember it, but you can see that command in S-off Revone Thread...its very simple.....you will have to do that via terminal emulator as you are not an ADB guy ...also unrooting the phone, you can see some vidoe guides out there in the stickies...
but i am not sure, may be relocking itself will take away your root access... just try posting this question in the s-off thread to get an expert answer....

Alright! S-off, bootloader relocked. Gonna try the update. Wish me luck. And thanks so much for your help Math. I'll let everyone know how it went for future reference.
mathrania said:
While you are s-off, you can relock you bootloader via a simple command....and to be frank i dont remember it, but you can see that command in S-off Revone Thread...its very simple.....you will have to do that via terminal emulator as you are not an ADB guy ...also unrooting the phone, you can see some vidoe guides out there in the stickies...
but i am not sure, may be relocking itself will take away your root access... just try posting this question in the s-off thread to get an expert answer....
Click to expand...
Click to collapse

Dammit. Still no luck. I'm getting the same error I used to get even before all this when i try to install an OTA. At first it won't verify the signature, but when i push it via CMW anyway, it starts and hangs on "running bug_fix_1" and that's it. No go. So all, this for nothing. Any chance anyone's come across this issue and has a solution? I'd love to get the update. There are a few bugs that really piss me off.

vijn said:
Dammit. Still no luck. I'm getting the same error I used to get even before all this when i try to install an OTA. At first it won't verify the signature, but when i push it via CMW anyway, it starts and hangs on "running bug_fix_1" and that's it. No go. So all, this for nothing. Any chance anyone's come across this issue and has a solution? I'd love to get the update. There are a few bugs that really piss me off.
Click to expand...
Click to collapse
i heard you saying CWM..... you dont have stock recovery?????

No, I'm using CWM. I assume that's the issue? Not even sure where to get the stock recovery for my firmware. I downloaded one, but I'm not sure it's right and am hesitant about flashing it.
mathrania said:
i heard you saying CWM..... you dont have stock recovery?????
Click to expand...
Click to collapse

vijn said:
No, I'm using CWM. I assume that's the issue? Not even sure where to get the stock recovery for my firmware. I downloaded one, but I'm not sure it's right and am hesitant about flashing it.
Click to expand...
Click to collapse
YOu said you have stock recovery
.... well without stock recovery, forget about the OTA.....
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
mathrania said:
YOu said you have stock recovery
.... well without stock recovery, forget about the OTA.....
Click to expand...
Click to collapse
either find correct RUU, or make a thread asking for recovery for your mobile....

OK, that makes sense. Sorry about the confusion. Not sure why I said stock recovery. Didn't even realize I did until you mentioned it. So, I'll try to flash stock rec and try again, otherwise, I'll just unroot and see if I can factory reset and start over. THanks again for your help.
mathrania said:
YOu said you have stock recovery
.... well without stock recovery, forget about the OTA.....
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
either find correct RUU, or make a thread asking for recovery for your mobile....
Click to expand...
Click to collapse

vijn said:
OK, that makes sense. Sorry about the confusion. Not sure why I said stock recovery. Didn't even realize I did until you mentioned it. So, I'll try to flash stock rec and try again, otherwise, I'll just unroot and see if I can factory reset and start over. THanks again for your help.
Click to expand...
Click to collapse
Factory reset will not give you stock recovery...
Sent from my HTC One using xda premium

Sprint HTC One keeps rebooting after ROM install

I've unlocked bootloader, flashed recovery, and have tried installing several different roms, wiping the cache each time. Each one has heralded the same result though, after boot up after about 10 seconds of being able to use the phone, it will just restart. This has gotten me very frustrated. Any ideas?

Dysnomia said:
I've unlocked bootloader, flashed recovery, and have tried installing several different roms, wiping the cache each time. Each one has heralded the same result though, after boot up after about 10 seconds of being able to use the phone, it will just restart. This has gotten me very frustrated. Any ideas?
Click to expand...
Click to collapse
if you're using twrp, select wipe from main menu>advanced wipe>select dalviccache, cache, data, and system, then flash rom.

Which roms have you installed?
Sent from my HTCONE using Tapatalk 4 Beta

Dysnomia said:
I've unlocked bootloader, flashed recovery, and have tried installing several different roms, wiping the cache each time. Each one has heralded the same result though, after boot up after about 10 seconds of being able to use the phone, it will just restart. This has gotten me very frustrated. Any ideas?
Click to expand...
Click to collapse
krazyflipj said:
Which roms have you installed?
Sent from my HTCONE using Tapatalk 4 Beta
Click to expand...
Click to collapse
This. In particular, the first one you installed, because this sounds suspiciously like what happens when someone flashes a GSM ROM.

Rirere said:
This. In particular, the first one you installed, because this sounds suspiciously like what happens when someone flashes a GSM ROM.
Click to expand...
Click to collapse
I'm having the same problem except I think it's because I flashed the wrong kernel. It was an m7 instead of m7spr kernel. IDK how it even happened but my phone boots up with no signal. I can get to the settings quick enough and noticed baseband says unknown. Tried restoring a sense backup and installing different kernels.
Edit: Actually I flashed a kernel here in the Sprint HTC One forum. It was an aosp rom and an aosp kernel. But still no matter what I do I can't get it to stay booted.

Rirere said:
This. In particular, the first one you installed, because this sounds suspiciously like what happens when someone flashes a GSM ROM.
Click to expand...
Click to collapse
Yes, actually I accidentally downloaded the 4.3 google edition leak rom without realizing it wasnt for the sprint version

insuusvenerati said:
I'm having the same problem except I think it's because I flashed the wrong kernel. It was an m7 instead of m7spr kernel. IDK how it even happened but my phone boots up with no signal. I can get to the settings quick enough and noticed baseband says unknown. Tried restoring a sense backup and installing different kernels.
Edit: Actually I flashed a kernel here in the Sprint HTC One forum. It was an aosp rom and an aosp kernel. But still no matter what I do I can't get it to stay booted.
Click to expand...
Click to collapse
This is exactly the problem I'm having now if I install any other rom

So I relocked the bootloader and tried installing a stock ruu, but I just get an error message, no idea what to do. -_-

Ok, so apparently I need to get S-Off to use the older RUU, but can't seem to get revone working because I cant boot up for more than 15 seconds, can someone help here?

Dysnomia said:
Ok, so apparently I need to get S-Off to use the older RUU, but can't seem to get revone working because I cant boot up for more than 15 seconds, can someone help here?
Click to expand...
Click to collapse
Try this [http://forum.xda-developers.com/showthread.php?t=2251800] It helped my problem. Erased everything from the device but I had it backed up anyway. You do not need s-off but you need to relock your bootloader. It's really easy tho. Google message me or PM me here if you need help.

insuusvenerati said:
Try this [http://forum.xda-developers.com/showthread.php?t=2251800] It helped my problem. Erased everything from the device but I had it backed up anyway. You do not need s-off but you need to relock your bootloader. It's really easy tho. Google message me or PM me here if you need help.
Click to expand...
Click to collapse
already said I can't use that one because I already updated my phone to 1.31.651.2

Dysnomia said:
already said I can't use that one because I already updated my phone to 1.31.651.2
Click to expand...
Click to collapse
im on the same version have you found a solution yet???

Tlalok08 said:
im on the same version have you found a solution yet???
Click to expand...
Click to collapse
if you s-off you can use the .10 ruu (revone s-off method still works moonshine does not)

Aldo101t said:
if you s-off you can use the .10 ruu (revone s-off method still works moonshine does not)
Click to expand...
Click to collapse
i will give that a shot

Tlalok08 said:
im on the same version have you found a solution yet???
Click to expand...
Click to collapse
Ok, I tried flashing another rom, still same results. But, this one revone actually worked with, achieved S-Off and flashed the RUU.

where can i get the revone ??? sorry it this is a dumb question...

Tlalok08 said:
where can i get the revone ??? sorry it this is a dumb question...
Click to expand...
Click to collapse
There is a sticky in this forum that has the info for s off. Also in one of the dev forums there is an all in one tool that makes using revone easy.

Tlalok08 said:
where can i get the revone ??? sorry it this is a dumb question...
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2319412
Or you can use this tool
http://forum.xda-developers.com/showthread.php?t=2236814

Dysnomia said:
Ok, I tried flashing another rom, still same results. But, this one revone actually worked with, achieved S-Off and flashed the RUU.
Click to expand...
Click to collapse
hi,
which rom did you install which allowed you to get revone onto the device?

ya im in the same boat. loaded a rim labeled as a sprint rom, when in aroma, i asked att tmobi or international, i selected international. had this problem ever since. just got my phone maybe 2 days ago. familiar withh rooting and android, fastboot and what not, this is my 4th htc. hero, evo , evo3d and now this please tell me it's not dead. i'm not used to all this no sd card stuff. =[

[Q] Trouble flashing any roms and RUU

I upgraded to 4.06.651.4. HBoot 1.56 Unlocked S-On
Using TWRP 2.6.3.0, I am unable to successfully flash any roms. Everything is successfully installed but all exhibit the same behavior. Boots up and when I unlock the lockscreen, I get the "htcdialer is taking too long" or whatever. No matter what I do there, it will eventually reboot (within 1 minute or so). Tried flashing some aosp roms but they do not fully boot.
Tried locking bootloader and running RUU 3.05.651.6 (which seems to be the latest) but it always fails with an unknown error, which is likely because I'm trying to downgrade firmware? Problem is there doesn't appear to be a 4.06 RUU yet.
Any ideas?

Did you happen to flash a GSM rom that does not have Sprint support?

BD619 said:
Did you happen to flash a GSM rom that does not have Sprint support?
Click to expand...
Click to collapse
No but i did install the wrong recovery image. Installed ATT's somehow. Was able to flash Sprint recovery and things appeared to be ok at that point.

bcaldwell said:
No but i did install the wrong recovery image. Installed ATT's somehow. Was able to flash Sprint recovery and things appeared to be ok at that point.
Click to expand...
Click to collapse
Ok Our device and GSM devices have different mount points that's why you are having issues.
Look HERE to get fixed up
PM or post here if you need help or have questions.

BD619 said:
Ok Our device and GSM devices have different mount points that's why you are having issues.
Look HERE to get fixed up
PM or post here if you need help or have questions.
Click to expand...
Click to collapse
Awesome man. Everything is good again. Thanks.

bcaldwell said:
Awesome man. Everything is good again. Thanks.
Click to expand...
Click to collapse
Good to here enjoy

[Q] [SOLVED] Unlocked/Rooted with S-On want OTA

I would like to install the AT&T OTA of 4.4.2 but have a custom recovery and am unable to upgrade. I am rooted with the stock 4.3 ROM and have the twrp recovery installed. I have S-ON. I've searched around trying to find a way to get this to work but can't seem to figure it out. I've tried looking around for an AT&T 4.3 stock recovery to try and flash it but can't seem to find one. The one from the Dev sticky page is not available for download. Can someone detail the steps I have to perform to get the 4.4.2 OTA from AT&T. Thanks in advance.
[SOLVED]
OK, problem fixed and 4.4.2 installed from OTA. I had relocked the bootloader on my phone so... start from scratch. Steps to resolve
1 - Unlock Bootloader
2 - Get S-Off on device (Makes everything easier). I used Firewater (http://firewater-soff.com)
3 - Flash the AT&T 3.17.502.3 (4.3) RUU from here (http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/). You may need a different one if not on AT&T
4 - Start phone, check for update. Let it download. Cake.
Now off to redo all the settings on my phone. Hope this helps someone else.

You can extract recovery.IMG from the ATT 4.4.2 OTA update if you can't find anything else.
sent from my mobile device

SaHiLzZ said:
You can extract recovery.IMG from the ATT 4.4.2 OTA update if you can't find anything else.
sent from my mobile device
Click to expand...
Click to collapse
Awesome, that's what I wanted to hear. I'm going to give that a shot. Thank you

Stock recoveries here: http://d-h.st/users/guich/?fld_id=29380#files
sent from my mobile device

SaHiLzZ said:
Stock recoveries here: http://d-h.st/users/guich/?fld_id=29380#files
sent from my mobile device
Click to expand...
Click to collapse
I flashed my recovery but recovery now just gets a read triangle with the exclamation

Let the phone download OTA and apply it
sent from my mobile device

SaHiLzZ said:
Let the phone download OTA and apply it
sent from my mobile device
Click to expand...
Click to collapse
Doing now.

It downloaded and attempted to install, then failed half way. Anything else I have to do before I update? Do I have to lock my bootloader again or unroot?
Sent from my HTC One using xda app-developers app

Yea lock bootloader
sent from my mobile device

No dice. Same deal.
Sent from my HTC One using xda app-developers app

Text/Photo of the error?

SaHiLzZ said:
Text/Photo of the error?
Click to expand...
Click to collapse
It doesn't give me an error. The OTA downloads, reboots and gets to a triangle with the green arrows inside and starts installing, then about 25% of the way it stops and goes to a red triangle. I'm thinking the MD5 to one of my files may be failing. I installed an edit to the framework sometime ago to get the hotspot working (that's the only change to the stock rom I've made). It doesn't really give me an error message though.

It could be the issue. You will need to choose one of the few options:
1. Restore a stock ATT OS for the same version you have (4.3) and update again
2. S-OFF (Preferred to avoid future messy bricks) and reinstall old ATT RUU and then upgrade all the way without custom rom/rooting/firmware changes
3. Wait for someone to post a custom rom install of the new ATT 4.4 update and install that.

SaHiLzZ said:
It could be the issue. You will need to choose one of the few options:
1. Restore a stock ATT OS for the same version you have (4.3) and update again
2. S-OFF (Preferred to avoid future messy bricks) and reinstall old ATT RUU and then upgrade all the way without custom rom/rooting/firmware changes
3. Wait for someone to post a custom rom install of the new ATT 4.4 update and install that.
Click to expand...
Click to collapse
Thanks, I appreciate your help. I think I'm gonna go with option 2, depending on how much time I have to do this, or 3 if time is an issue. Just one more question for you. Is firewater the best method to get S-Off or do you recommend a different one?

SMaximus7 said:
Thanks, I appreciate your help. I think I'm gonna go with option 2, depending on how much time I have to do this, or 3 if time is an issue. Just one more question for you. Is firewater the best method to get S-Off or do you recommend a different one?
Click to expand...
Click to collapse
If the ota stops on the second half as you discribe I think you have the wrong stock recovery. Different version than your "version-main"

mb_guy said:
If the ota stops on the second half as you discribe I think you have the wrong stock recovery. Different version than your "version-main"
Click to expand...
Click to collapse
I guess it can't hurt to try and reflash the recovery and retry. I'll give it a try.

SMaximus7 said:
I guess it can't hurt to try and reflash the recovery and retry. I'll give it a try.
Click to expand...
Click to collapse
I had the exact same thing occur, had a newer recovery than "fastboot getvar all"

mb_guy said:
I had the exact same thing occur, had a newer recovery than "fastboot getvar all"
Click to expand...
Click to collapse
It could be because I flashed the recovery that came with the OTA with fastboot and then after SaHiLzZ pointed me in the right direction was able to download the 4.3 recovery but flashed that one with flashify. I bet you the one I did with flashify didn't take. Funny thing is I also relocked my bootloader and now must unlock it again and that will probably wipe my device. What a mess, oh well, I hope that's all it is and at least I'm learning as I go.

SMaximus7 said:
It could be because I flashed the recovery that came with the OTA with fastboot and then after SaHiLzZ pointed me in the right direction was able to download the 4.3 recovery but flashed that one with flashify. I bet you the one I did with flashify didn't take. Funny thing is I also relocked my bootloader and now must unlock it again and that will probably wipe my device. What a mess, oh well, I hope that's all it is and at least I'm learning as I go.
Click to expand...
Click to collapse
Ya, I was lucky, had a nandroid . But you are right the recovery in the ota is too new.

Solved
OK, problem fixed and 4.4.2 installed from OTA. I had relocked the bootloader on my phone so... start from scratch. Steps to resolve
1 - Unlock Bootloader
2 - Get S-Off on device (Makes everything easier). I used Firewater (http://firewater-soff.com)
3 - Flash the AT&T 3.17.502.3 (4.3) RUU from here (http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/). You may need a different one if not on AT&T
4 - Start phone, check for update. Let it download. Cake.
Now off to redo all the settings on my phone. Hope this helps someone else. Thanks everybody for chiming in.

[Q] Unlocking bootloader

Hi all! First of all I'm sorry if this has been asked previously but after 3 hours of searching I was unable to find a straight answer and I have tenths of bookmarks opened...
Right so, just got my "new" (used) phone delivered today. 6 months old, currently running stock 4.4.2 with Sense 6.0 under the GiffGaff network. Straight away I went and tried to flash a new ROM onto it (flashed a few roms previously to my HTC Sensation with no problems). So just the usual routine: fastboot > HTCdev > get token ... and here where the first problem occurred. I couldn't get the token as I was getting the following error:
(bootloader) [ERR] Command error !!!
OKAY [ 0.010s]
finished. total time: 0.010s​Restarting the phone/PC didn't help, changing USB debug on/off also didn't help. Fastboot unlock oem command didn't work either as it gave me the same error. So I went and downloaded the Hasoon2000's AIO tool to see if that will work but again no luck. When hitting the "Get Token ID" I get an error that the phone is offline - . - . So I had a little search on the net and found out that maybe it's due to my HBOOT version which is 1.57 and is S-ON . However I have no idea how to change that nor if it'll actually solve my problem and I don't want to do anything outside the box so that I don't get my phone bricked.
Any ideas what might be wrong/what am I doing wrong/solutions? I'm clueless at the moment and about to run out of patience... Any help is more then welcome

bboybtek said:
(bootloader) [ERR] Command error !!!
OKAY [ 0.010s]
finished. total time: 0.010s​What was the exact command?
Click to expand...
Click to collapse
changing USB debug on/off also didn't help.
Click to expand...
Click to collapse
usb debug doesn't matters in bootloader, only in the OS or in recovery for adb commands.
Fastboot unlock oem command didn't work either
Click to expand...
Click to collapse
this command is blocked, so it will not work.
So I went and downloaded the Hasoon2000's AIO tool
Click to expand...
Click to collapse
Hasoon2000 did a great job with his toolkit, but I recommend (and many others) not using toolkits. use fasboot and adb directly from the command window, much better when you are trying to find what doesnt work. Be sure to have the latest sdk on your computer, and latest htc drivers. Also make sure to use 2.0 usb ports, not 3.0
I get an error that the phone is offline
Click to expand...
Click to collapse
What is the output of "fastboot devices" ?
So I had a little search on the net and found out that maybe it's due to my HBOOT version which is 1.57 and is S-ON
Click to expand...
Click to collapse
not sure about that, I really doubt you can't unlock bootloader because of hboot 1.57.
Any ideas what might be wrong/what am I doing wrong/solutions?
Click to expand...
Click to collapse
follow this guide:

Thanks for the reply mate. I watched the video again but I had no luck. However, thanks to that video I went and downloaded the huge SDK archive from HTC site. Instead of using the small archive with "essential" files for the adb, I used the one from HTC site (it has many more files in adb folder) and guess what, it worked! Now, I'm very happy that I finally unlocked it but my question now is, why didn't it work with just the "essential" files? All tutorials videos/forum posts etc. mentioned just the 4 files and not the big HTC package so if it wasn't for the fact that I was desperate I don't think I would of ever unlock this biatch...

Right, instead of creating a new thread I'm just going to ask here. So I successfully unlocked the device and using this video I tried to root the phone. Everything went smoothly, all successful and so on. However when I downloaded the root checker it gives me a message saying the the device is not properly rooted . I then tried with firewater s-off but no luck here either. I've attached the image of how my cmd looks when trying the firewater method. I really thought it's going to be a bit easier to flash this phone... Any advice here guys?
Edit: I just realised that the phone is still S-ON...how did this happen even tho I successfully installed everything that's required...?
Edit2: Tried the temp-root method with firewater but even this doesn't work. I'm getting an error and fail messages (image attached). I think I've run out of ideas here :/

bboybtek said:
Right, instead of creating a new thread I'm just going to ask here. So I successfully unlocked the device and using this video I tried to root the phone. Everything went smoothly, all successful and so on. However when I downloaded the root checker it gives me a message saying the the device is not properly rooted . I then tried with firewater s-off but no luck here either. I've attached the image of how my cmd looks when trying the firewater method. I really thought it's going to be a bit easier to flash this phone... Any advice here guys?
Edit: I just realised that the phone is still S-ON...how did this happen even tho I successfully installed everything that's required...?
Edit2: Tried the temp-root method with firewater but even this doesn't work. I'm getting an error and fail messages (image attached). I think I've run out of ideas here :/
Click to expand...
Click to collapse
first, why are you trying to s-off? s-off is not required to flash custom roms (except for GPE roms), only an unlocked bootloader and a custom recovery (twrp 2.6.3.3) are needed. You definitively need a fully rooted phone to use firewater and an unsecured kernel would also help. Btw almost all custom roms out here are pre-rooted, so just flash a rom and you'll be fine.
and that video you have linked is very outdated, twrp 2.5.0.0 lol. just flash twrp 2.6.3.3 and then boot in recovery. Quit the recovery and you'll be prompted to install root.
but anyway, is your goal is to flash a custom rom, you don't need to root before, they are all (almost) pre-rooted.

alray said:
first, why are you trying to s-off? s-off is not required to flash custom roms (except for GPE roms), only an unlocked bootloader and a custom recovery (twrp 2.6.3.3) are needed. You definitively need a fully rooted phone to use firewater and an unsecured kernel would also help. Btw almost all custom roms out here are pre-rooted, so just flash a rom and you'll be fine.
and that video you have linked is very outdated, twrp 2.5.0.0 lol. just flash twrp 2.6.3.3 and then boot in recovery. Quit the recovery and you'll be prompted to install root.
but anyway, is your goal is to flash a custom rom, you don't need to root before, they are all (almost) pre-rooted.
Click to expand...
Click to collapse
I got lost a little bit with all the tutorials I found, that's why I thought I need s-off lol. I know the video is a bit old that's why I used twrp 2.7.1.1 with SU 3.2 . I'm planning on installing ViperOne rom so I'm just going to go ahead and try that and hopefully everything will be working. Thanks again for the reply mate

bboybtek said:
I got lost a little bit with all the tutorials I found, that's why I thought I need s-off lol. I know the video is a bit old that's why I used twrp 2.7.1.1 with SU 3.2 . I'm planning on installing ViperOne rom so I'm just going to go ahead and try that and hopefully everything will be working. Thanks again for the reply mate
Click to expand...
Click to collapse
Make a backup using TWRP first..
Also the file you should have used should be SuperSU-2.02.. but if you are going to flash a new rom, point is moot.

SaHiLzZ said:
but if you are going to flash a new rom, point is moot.
Click to expand...
Click to collapse
yeah I've installed a new rom and everything is running perfectly fine! Thanks for the tips chaps!