Quick background:
Avid Android flasher/user for years, experience with most flagships and usually self-sufficient in my tinkering around with phones.
This phone seems to be the exception to the rule and I have a few questions that are not answered clearly in previous threads that I have read through.
If your objective is to point out any sort of ignorance on my part you can stop reading now, this is purely an educational post that can also hopefully help those who might also have these issues going forward.
Onto the questions.
In the process of unlocking bootloader, performing s-off, rooting and installing a recovery what is the easiest order to those who have done all of this?
Next, I am registered on HTCdev but I am stuck almost immediately when attempting to follow their step-by-step for unlocking my bootloader because it would appear that this years HTC model doesn't have HBOOT or Fastboot in Download mode? I have attached pictures of what I see on my phone when try their first step.
Lastly, it would appear that people are now trying to monetize on things such as S-Off actions so the consistent information and tutorials that once were available are now pretty scattered and hidden by those trying to shill Sunshine, I am not interested in that method whatsoever so please disregard this call for assistance if that is the solution you would be recommending.
Thanks for reading and if anyone is willing to lend some advice it would be greatly appreciated.
The process I went with was as follows:
Unlock bootloader, install custom recovery (then make a backup of system/data/boot), flash supersu, S-Off using Sunshine. While I don't agree with the costs associated with Sunshine, ultimately there has not been any other choices out there to reliably accomplish S-Off so I forked up the cash so I could have the convenience of S-Off. It worked just fine and I've had no issues since. If you'd rather not S-Off and save your money, that is fine. Just make sure you follow the advice from the other threads and take a stock back up before you flash ANYTHING in TWRP that you can restore to and take OTAs to update your firmware. Otherwise, you'll have to wipe your phone with an RUU to update the firmware without S-Off.
When I was using HTC Dev, I selected "other supported devices" or whatever that option is since the M9 was not listed when I unlocked my bootloader. If there is one for the M9 now and it isn't working for you, try selecting other. Also, ensure that you have the correct drivers installed. I would offer more advice on the actual process of unlocking the bootloader but I can't find the threads I was referencing throughout the process and I did all of this about two and a half months ago so I can't remember as much as I like. I hope this helps.
outofluck said:
The process I went with was as follows:
Unlock bootloader, install custom recovery (then make a backup of system/data/boot), flash supersu, S-Off using Sunshine. While I don't agree with the costs associated with Sunshine, ultimately there has not been any other choices out there to reliably accomplish S-Off so I forked up the cash so I could have the convenience of S-Off. It worked just fine and I've had no issues since. If you'd rather not S-Off and save your money, that is fine. Just make sure you follow the advice from the other threads and take a stock back up before you flash ANYTHING in TWRP that you can restore to and take OTAs to update your firmware. Otherwise, you'll have to wipe your phone with an RUU to update the firmware without S-Off.
When I was using HTC Dev, I selected "other supported devices" or whatever that option is since the M9 was not listed when I unlocked my bootloader. If there is one for the M9 now and it isn't working for you, try selecting other. Also, ensure that you have the correct drivers installed. I would offer more advice on the actual process of unlocking the bootloader but I can't find the threads I was referencing throughout the process and I did all of this about two and a half months ago so I can't remember as much as I like. I hope this helps.
Click to expand...
Click to collapse
Thank you so much for the insight.
Did you have the HBOOT and Fastboot issues from the Bootloader/Download mode screens on the phone itself?
williamvito said:
Thank you so much for the insight.
Did you have the HBOOT and Fastboot issues from the Bootloader/Download mode screens on the phone itself?
Click to expand...
Click to collapse
Download mode is our new "Fastboot" mode. Make sure before you go to HTCDev Unlock the bootloader that you access "Developer Settings" on the phone and check the "OEM Unlocking" option which will allow the bootloader to be unlocked without the "Killswitch" firmware blocking it. I'm not sure if HTC just hasn't updated instructions since the "official" start of the Killswitch legislation kicked in OR if they just won't.
Sunshine works amazingly and honestly, if you don't want to show gratitude in the form of a monetary payment (as opposed to a click of the thank you button or empty promise of a donation "on your next pay day") for the work, that's ok, just don't have s-off or find an exploit and bring to the masses for free.
Good luck!
mrrogers1 said:
Download mode is our new "Fastboot" mode. Make sure before you go to HTCDev Unlock the bootloader that you access "Developer Settings" on the phone and check the "OEM Unlocking" option which will allow the bootloader to be unlocked without the "Killswitch" firmware blocking it. I'm not sure if HTC just hasn't updated instructions since the "official" start of the Killswitch legislation kicked in OR if they just won't.
Sunshine works amazingly and honestly, if you don't want to show gratitude in the form of a monetary payment (as opposed to a click of the thank you button or empty promise of a donation "on your next pay day") for the work, that's ok, just don't have s-off or find an exploit and bring to the masses for free.
Good luck!
Click to expand...
Click to collapse
Thanks for the clarification about download mode, it makes a lot more sense now especially since HTC hasn't updated their descriptions.
In regards to sunshine, that seemed like a half-handed way of calling me cheap since I didn't want to pay out a $25 fee and almost a threat if I were to post a free way to achieve S-Off if I found one? I wasn't offended but there seems to be a lack of transparency as to why this option exists and nothing else really, CF-Auto Root for Samsung devices was one of my favorite exploits that I definitely supported over the years but that's only after I had such success with it and not prior to needing such service.
I understand this brands devices have been layered much differently than others with not only rooting as an option but also the unlocking and s-off stuff involved, but the difference between last years support and this years is a pretty wide gap.
This is not a criticism on you at all, but as much as HTC needs the business these days it would also seem as if the remaining development community would also make it as hassle-free as possible to fully enjoy the true potential of the device, instead it just seems like some unnecessary capitalism to take advantage of those who want to appreciate a niche phone, just my opinion.
No, I wasn't calling you cheap at all (and meant no malice or to offend) but it is the only option because no one else has brought an alternative to market. I'd pay jcase and team anyway and again but the fact remains, no one else apparently has the skills (or is willing to) to do it.
At the end of the day, s-off isn't a requirement to root and do the custom rom dance here so no one is forced to s-off for any real reason.
Sent from my 0PJA2 using Tapatalk
All good, my core frustration was really with the conflict of terminology on the HTC side preventing me from starting even step one of the unlock process and the newly realized issue on my end that java was preventing my SDK platform tools from opening, once I get to the point of root I'll decide whether its worth it for myself to go ahead and perform S-Off via Sunshine or go down the rabbit hole to see if I can figure it out on my own. Thanks again for the advice and info.
Related
Well at last, HTC has brought us their method to root HTC Evo 3D & Sensation.. Just register to become a member (dev) and begin rooting your Evo3D. I wanted to show you all what to expect.. and of course there are disclaimers so view screen shots for full details. I have not tried this setup so please give feedback, I do have the phone but it's been rooted by other methods.. just giving fellowship & sharing information. Enjoy!
Go to HTCDev.com to get started.. (This will VOID your warranty, root your phone & give you super human strenghts)
Previous rooting gave phone's the same voided warranty especially servicing in carriers service center, same deal. Revolutionary method also voids warranty so now people have choices.. (Former Sprint Service Mgr)
As informed please give useful feedback if you have used this method so we know where we stand with this and in fact "IF" HTC is helping us out.
Thx to Doomstang for input-
Doomstang said:
Well I think I've finally gotten somewhere...Wireless Tether was just successfully granted Superuser permissions.
This was all done without ever having rooted this phone in the past...so I accepted the OTA update, unlocked with HTC Dev's process, got a working recovery going, and then got Superuser installed.
graffixnyc posted the link to the working recovery so I used that: http://www.multiupload.com/AQ9KV7IME9
Click to expand...
Click to collapse
And Graffixnyc-
graffixnyc said:
This was the version of CWM that booted for me. I flashed through fastboot and also did a nandroid restore just fine. This was the version IEF(from alpharev) gave me on irc
http://www.multiupload.com/AQ9KV7IME9
I was able to get into recovery from selecting recovery from the fastboot method and from doing adb reboot recovery. Sorry for not posting earlier I had finals yesterday and went out after to celebrate
http://www.multiupload.com/AQ9KV7IME9
Click to expand...
Click to collapse
Please make sure all items are installed and up to date.
Google Android SDK zip:
http://developer.android.com/sdk/index.html
Java Runtime Environment:
http://java.com
HTC Sync (Windows Only):
http://www.htc.com/www/help/
Continued "disclosure"
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty. Please note that unlocking your bootloader does not mean that you will be able to unlock the SIM lock. Unlocking your SIM lock is at the discretion of your operator/carrier and is not part of the bootloader unlocking scope.
Our devices have been designed with our hardware and software specifications in mind and unlocking the bootloader will change the software and may cause unexpected side effects. It is impossible for HTC to ensure the proper functioning of your device after this. In the worst case scenario, it is possible that your device may be physically damaged due to overheating or the behavior of your device might be altered including, but not limited to, hearing aid compatibility (HAC) and specific absorption rate (SAR) values.
Some content on your device may also be invalidated and cannot be accessed any more because of invalid DRM security keys. This includes content that you may have purchased through a 3rd party vendor and through HTC. Furthermore, although you will still be able to receive updates to your device via FOTA (“firmware over the air”), we do not guarantee that updating your device via FOTA will not render your device unusable. Please understand that you will not be able to return your device to the original state and going forward your device may not be held covered under the warranty for all claims resulting from the unlocking of the bootloader. HTC bears no responsibility if your device is no longer usable afterwards.
HTC is committed to assisting customers in unlocking bootloaders for HTC devices. However, due to some of our carrier customers concerns, certain models with specific restrictions may not be able to be unlocked. Please refer to our list of supported devices to see if your device is eligible for unlocking the bootloader.
We strongly suggest that you do not unlock the bootloader unless you are confident that you understand the risks involved. This is a technical procedure and the side effects could possibly necessitate repairs to your device not covered under warranty. If you are still interested in unlocking the bootloader, and you understand the consequences both to your device and to your warranty, then you may refer to the following pages where we have provided the unlocking instructions.
If there's an error you will see screen shot below.. with details on what happened.
So maybe I'm confused about what this does ... I went through the process and everything seems to have worked. Bootloader now shows unlocked. I tried to flash a recovery (both clockworkmod and TWRP) and it seems to flash successfully but when I try to run recovery it just reboots the phone after showing the HTC logo for a minute. I was hoping to install the rooted OTA but not sure what to try next...
nabbed said:
No. I'm not confused about the unlock.
I'm worried about a man who makes a guide about unlocking the device he does not have...
Am I wrong to be worried, about a man, who makes a post, about unlocking a device, he does not have?
Has has tested the method?
Click to expand...
Click to collapse
Yooooo. Godzson is a trusted guy and helps many devs in the community. No sense in flamming him when you'll just start pissing off devs here.
Sent from my PG86100 using Tapatalk
Godzson is a trusted member on here. Don't think you have to worry about him. Why would someone take all this time to write up a post with pics and the info just to mess with people? Smh....... Alot of the devs in the 3d community who do roms and themes don't even have the damn 3d. Don't start turning this community into **** by questioning people trying to help.
gthing said:
So maybe I'm confused about what this does ... I went through the process and everything seems to have worked. Bootloader now shows unlocked. I tried to flash a recovery (both clockworkmod and TWRP) and it seems to flash successfully but when I try to run recovery it just reboots the phone after showing the HTC logo for a minute. I was hoping to install the rooted OTA but not sure what to try next...
Click to expand...
Click to collapse
TWRP doesn't work and CWM Is a hit or miss. You should of tried the stock recovery, I think it had one. Wait till a root for the new boot loader I say.
I think the unlocked just gives partial access to the bootloader if I am correct. Your security flag(s-off) is still on.
Sent from my EVO3D(overclocked) via XDA App
Godzson is only posting to what HTC promised, here a unlocker. He is also a trusted member, who provides a substantial amount of information for the community. Please they are also right to say some dev, and do not have this device and do an amazing job developing for it. let's please keep peaceand move forward..
Why waste your time reposting instructions found on htcdev.com? People want to know what happens after you do the method and how it helps put custom software on your phone.
mwalt2 said:
Why waste your time reposting instructions found on htcdev.com? People want to know what happens after you do the method and how it helps put custom software on your phone.
Click to expand...
Click to collapse
Because sometimes people want to see the process without having to DO the process....
Why question it? Just don't read through 2 pages or more of posts if it's offensive to you.
Yo GODZSON, you do know that the little green android guy isn't the only one that's green around here, don't you? LMFAO. Just look at the noobs trying to flame you, and don't even know anything about you, LOL. Yeah, LOL. Like they got room to talk. Keep up the great work buddy.
On a more serious note, does this method actually allow you to root? Cuz I didn't really see anything on HTC's site, or in your post about rooting. Yet the title states rooting with HTC's unlock method. Just a fyi.
Sent from my PG86100 using XDA Premium App
Well sir maybe doing a lil research would benefit the questions. I did assist with 2 threads in Evo3D (screen pics and 3D converting). I placed this for information to the community and for knowledge to those that may want to see what it looks like and have other options of rooting their phone. I do have the device but's its been rooted therefore I havent tried this "Official" method. Would be nice to ask with some manners in XDA you can get suspended, banned, etc for your actions, this is a community to help each other out.
Thanks to all the fellow dev's for the kind words.. to all the noobs with lack of knowledge no worries we're here for you to help out, much love for you.. hey we all started there at one time
Well I think I've finally gotten somewhere...Wireless Tether was just successfully granted Superuser permissions.
This was all done without ever having rooted this phone in the past...so I accepted the OTA update, unlocked with HTC Dev's process, got a working recovery going, and then got Superuser installed.
graffixnyc posted the link to the working recovery so I used that: http://www.multiupload.com/AQ9KV7IME9
this is a joke!
HTC's unlocked bootloader is a joke, it just says "unlocked" but you cannot flash any new recoveries and you get S-ON. Don't try this folks, stay rooted! My 3D is now officially bricked with HTC method, it's not unlocked at all as you can't do anything with it.
zedomax said:
HTC's unlocked bootloader is a joke, it just says "unlocked" but you cannot flash any new recoveries and you get S-ON. Don't try this folks, stay rooted! My 3D is now officially bricked with HTC method, it's not unlocked at all as you can't do anything with it.
Click to expand...
Click to collapse
I'm very sorry to hear yours was bricked but I was able to flash a working recovery (although the first 2 I tried did fail) and gain SU permissions even with S-ON still showing.
thnx
Doomstang said:
I'm very sorry to hear yours was bricked but I was able to flash a working recovery (although the first 2 I tried did fail) and gain SU permissions.
Click to expand...
Click to collapse
Thanks I actually saw your post and trying that now! We will have ROOT!
It does look like things are working for some starting here in one of the other threads.
Great write up
Lol, sorry HTC. We beat you to it.
Sent from my EVO 3D using XDA Premium App
The unlock is terrible, I got it to work on my Dad's phone, but I could only get into clockwork once, TWRP doesn't work, and only a manual flash of clockwork seemed to work, I tried to get in with Rom Manager for him so he could do a backup, and it wouldn't go either, and it didn't want to go back in for me manually either, just boots up.
Oh well, I managed to root it and get a rom installed. So we shall see how everything goes.
It's S-ON still, which is complete crap.
nfollin said:
The unlock is terrible, I got it to work on my Dad's phone, but I could only get into clockwork once, TWRP doesn't work, and only a manual flash of clockwork seemed to work, I tried to get in with Rom Manager for him so he could do a backup, and it wouldn't go either, and it didn't want to go back in for me manually either, just boots up.
Oh well, I managed to root it and get a rom installed. So we shall see how everything goes.
It's S-ON still, which is complete crap.
Click to expand...
Click to collapse
4.0.1.5 failed for me too.
I started with CWM 4.0.1.4.
I clicked update recovery in ROM Manager and it said 4.0.1.5 successfully installed after I granted it SU permissions. Had it reboot into recovery from ROM manager and the phone just restarted...so I manually went to recovery via HBoot and it fails to load and restarts the phone. I guess I'll push that 4.0.1.4 back to it now.
so the bootloader gets unlocked but yet it stays S-on? wtf lol ?
I'm 99.9% sold on the Amaze, I will probably be ordering this weekend.
One niggling doubt is the s-off issue. I see that it hasn't been achieved yet, though you can unlock the bootloader via the HTC.com dev code, and that allows perma-rooting and Custom Roms to be installed.
My questions are:
What would S-off achieve? Would there be more impressive roms that use the space and/or resources from /system or somewhere else that can't be touched without S-off? Is a CM 9 possible for the Amaze without S-off? In the CM forums, the "last" word so far is that it hasn't been included on the official list because "it doesn't even have S-off yet".
Is there a difference warranty-wise? I understand the _possible_ implication of asking HTC for the code, they have you in some database that says you unlocked the bootloader. But as for the device itself, is one undoable and the other not?
I understand that flashing kernels would be harder without s-off because it would have to be done via adb, I think I understood. This is no big deal in itself.
Finally: if you unlock the bootloader via the HTC code, and weeks or months down the road an exploit is found to gain S-Off, are you hosed because you used the code and didn't wait?
I'd like to know so I can make my decision before getting the phone. If it's very disadvantageous to use the code rather than wait for S-off, for one reason or another, then I'd have to decide if I can live with only temp-rooting the device.
I am not going to use it on T-Mobile, I'm in Venezuela and will use it with my carrier here, so the unnecessary bloat will be even more of an annoyance, because on top of it sucking, it won't even work; so it would be important for me to at least root to get rid of it.
I'm sorry if my questions are too expansive, I picked up bits and pieces of information in other posts, but none of them answered these questions clearly. Thank you very much to all those who can help me answer them.
el_ochito said:
I'm 99.9% sold on the Amaze, I will probably be ordering this weekend.
One niggling doubt is the s-off issue. I see that it hasn't been achieved yet, though you can unlock the bootloader via the HTC.com dev code, and that allows perma-rooting and Custom Roms to be installed.
My questions are:
What would S-off achieve? Would there be more impressive roms that use the space and/or resources from /system or somewhere else that can't be touched without S-off? Is a CM 9 possible for the Amaze without S-off? In the CM forums, the "last" word so far is that it hasn't been included on the official list because "it doesn't even have S-off yet".
Is there a difference warranty-wise? I understand the _possible_ implication of asking HTC for the code, they have you in some database that says you unlocked the bootloader. But as for the device itself, is one undoable and the other not?
I understand that flashing kernels would be harder without s-off because it would have to be done via adb, I think I understood. This is no big deal in itself.
Finally: if you unlock the bootloader via the HTC code, and weeks or months down the road an exploit is found to gain S-Off, are you hosed because you used the code and didn't wait?
I'd like to know so I can make my decision before getting the phone. If it's very disadvantageous to use the code rather than wait for S-off, for one reason or another, then I'd have to decide if I can live with only temp-rooting the device.
I am not going to use it on T-Mobile, I'm in Venezuela and will use it with my carrier here, so the unnecessary bloat will be even more of an annoyance, because on top of it sucking, it won't even work; so it would be important for me to at least root to get rid of it.
I'm sorry if my questions are too expansive, I picked up bits and pieces of information in other posts, but none of them answered these questions clearly. Thank you very much to all those who can help me answer them.
Click to expand...
Click to collapse
I don't know where to start with all of your questions but I will do my best.
The difference between S-OFF and Unlocked bootloader is that with S-OFF you can flash anything including a radio and supposedly it would give us the ability to update the kernel by recovery. With an unlocked bootloader we cannot update the radio or kernel but can pretty much change everything else. An unlocked bootloader is required to root your device and remove all the bloat that you don't like. You can temp root the device to remove that bloatware however they will re-appear after a reboot. It has been under some debate if in fact using the unlock_code.bin file provided by htcdev is going to void your warranty if your device would require servicing. If it's vital to know that information then call HTC to inquire before unlocking.
Regarding CM9, it is possible but slightly inconvenient since CM9 would almost certainly require a different kernel and since we cannot flash kernels by recovery it would have to be done in a very certain order. Is it currently in the works? To my understanding, yes! Any idea when you can see it as a download here in the forums? Not at this time. Check back daily because things change frequently!
Thanks a lot for your response, Binary. I see you have an Amaze and have indeed unlocked its bootloader, so I guess the real question would be: when and if s-off is achieved, will you be able to do it even though you've already unlocked the bootloader with the .bin file?
Warranty would be terribly hard for me to take advantage of anyways after the initial check. If I don't RMA the unit, then I'm pretty much gambling on the fact that it will work well no matter what, since sending it back to the US from Venezuela would be a major PITA, so I don't really care much about voiding it.
el_ochito said:
Thanks a lot for your response, Binary. I see you have an Amaze and have indeed unlocked its bootloader, so I guess the real question would be: when and if s-off is achieved, will you be able to do it even though you've already unlocked the bootloader with the .bin file?
Warranty would be terribly hard for me to take advantage of anyways after the initial check. If I don't RMA the unit, then I'm pretty much gambling on the fact that it will work well no matter what, since sending it back to the US from Venezuela would be a major PITA, so I don't really care much about voiding it.
Click to expand...
Click to collapse
There is no reason that having an unlocked bootloader will interfere with being able to obtain s-off in the future because we can always relock the bootloader when (or if) it comes down to it.
Binary100100 said:
I don't know where to start with all of your questions but I will do my best.
The difference between S-OFF and Unlocked bootloader is that with S-OFF you can flash anything including a radio and supposedly it would give us the ability to update the kernel by recovery. With an unlocked bootloader we cannot update the radio or kernel but can pretty much change everything else. An unlocked bootloader is required to root your device and remove all the bloat that you don't like. You can temp root the device to remove that bloatware however they will re-appear after a reboot. It has been under some debate if in fact using the unlock_code.bin file provided by htcdev is going to void your warranty if your device would require servicing. If it's vital to know that information then call HTC to inquire before unlocking.
Regarding CM9, it is possible but slightly inconvenient since CM9 would almost certainly require a different kernel and since we cannot flash kernels by recovery it would have to be done in a very certain order. Is it currently in the works? To my understanding, yes! Any idea when you can see it as a download here in the forums? Not at this time. Check back daily because things change frequently!
Click to expand...
Click to collapse
Your words helped me a lot. I was thinking about the diff between s-on/off and lock.unlock bootloader for long. Thanks so much
This is my primary concern.
Quote from toastcfh in the one x forum TWRP thread. ......
no, USB mount does not work in recovery. It appears to be locked out in recovery mode. the workarounds to get it working are one of two things.
(1) fastboot boot awesomeRecovery.img (this works because fastboot then boots recovery on the boot/temporary partition. So the you're not actually in recovery mode
(2) Offmode (this works because again you're again not technically in recovery mode. It uses the recovery ramdisk, kernel, and binaries but its still not technically recovery.
On that note I've seen suggestions that it's possibly a recovery issue with cwm and twrp. Unfortunately it doesn't appear to be the case. If it were then in CWM u wouldn't have usb when u fastboot boot the recovery or in offmode (fair assumption since both these options use the same kernel, ramdisk and binaries as recovery?). Can it be fix? Not that i know of. It looks to me like a total radio or bootloader lockout from using USB in recovery. Which means on a radio or bootloader level USB is disabled in recovery mode.
On that note I think we should raise the point to HTC that this locking down of the device does not suite our needs.Key points of fail would be as follows.
(1) Can NOT flash the boot partition from recovery. I've personally contacted HTC on this numerous times and they seem to just not care. Responding with "It's a security issue" and so forth. I would love to know how this is a security issue of any sort. Every other Android device has this ability except HTC devices since they started the HTC unlock ordeal. It's utter fail IMHO and HTC should listen to our needs .
(2) Can NOT flash recovery or boot partitions from system. This issue is NOT a deal breaker and isn't so bad when it comes down to the nitty gritty. But since the issue above exists, flashing with applications like htc dumlock and such were our only options. These work around apps cant be used to flash now because of the lockpout from system and it wouldn't be such an issue if HTC didnt lock us out in recovery from flashing boot.
(3) Can NOT flash P*IMG.zips in hboot/bootloader anymore. For the unlocked device running a custom firmware this is a must. Specially when radio updates and such are needed from the OEM. We seen a big use of this on the Sensation when HTC updated the device from Gingerbread to Ice Cream Sandwich. The update required new hboots, radios, and partitioning to actually use. So in that instead of having to flash a RUU Which didn't exist the only choice was to flash a custom P*IMG.zip that included all the radios and images need to run the builds. At this point we can't update those image/partitions without flashing an RUU. This makes no since and doesn't seem to do anything but make things more difficult on the unlocker to customize and modify their device.
(4) If all the conditions above HAVE to exist. Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
(5) WHAT WAS THE POINT OF HTC UNLOCK? I was to reach out and except us as a community. It was to keep us from having to exploit their firmware and look for holes to gain control of a device we rightfully own. WHAT DID HTC UNLOCK DO? It unlocked the devices at first and with each new revision of the unlock it gets more locked down and harder for us to use it as intended. WHAT DOES THAT LEAD TO? It leads to us hoping someone will take the time out of their life and exploit HTC's firmware so we can have access and control of our devices. I mean, it's bad when u have people poking a device with a paperclip to get a device unlocked to avoid a official unlock.
Bottom line; I'm personally fed up with HTC's unlock. It's absolute crap! It does not serve the purpose it was intended and only makes things harder then they were before. As a devoted HTC customer it has me questioning if my next device will be an HTC. With all the other options that would allow me to spend less time trying to gain proper access to my device and more time actually having fun with it, why choose HTC? Everyone else is shying away for these same issues. Everyone with an HTC unlocked device waits for someone to exploit HTC's firmware and give them a proper unlock. Why not just choose a device without the locked down/unlock instead? IDK but HTC needs to step up and listen to us. Every HTC forum with an HTC Unlock is screaming for these issues to be fixed.
My call to HTC is to fix these issue and/or give us proper documentation on flashing firmware to our devices via custom recoveries. The boot flashing lockout is dumb, pointless, and in NO WAY a security threat AT ALL and is nothing more then a CRAP RESPONSE to something that they sould be working to correct, instead of ignoring. In the end its hurting HTC's relations with developers and is ultimately doing the opposite of what it's original intent.
HTC, PLEASE READ AND LISTEN!!!11ONEone
To everyone else, SPREAD THE WORD!!!ONEone
Click to expand...
Click to collapse
This comes straight from toastcfh himself.
I think that if we all send an email to customer support and follow up something may come of this. Copy what toastchf said into an email send it everyone and then follow up until you get someone who cares. Then tell them about all those people who aren't doing this because they are fed up and switching to Samsung devices.
Sent from my EVO 3D S using XDA
you should edit your post to put his Quote in actual [ QUOTE=toastcfh;25407373]....(quoted post text goes here)...[/QUOTE ] tags(just remove the "space" between the first and last bracket...like I have done so below.
toastcfh said:
no, USB mount does not work in recovery. It appears to be locked out in recovery mode. the workarounds to get it working are one of two things.
(1) fastboot boot awesomeRecovery.img (this works because fastboot then boots recovery on the boot/temporary partition. So the you're not actually in recovery mode
(2) Offmode (this works because again you're again not technically in recovery mode. It uses the recovery ramdisk, kernel, and binaries but its still not technically recovery.
On that note I've seen suggestions that it's possibly a recovery issue with cwm and twrp. Unfortunately it doesn't appear to be the case. If it were then in CWM u wouldn't have usb when u fastboot boot the recovery or in offmode (fair assumption since both these options use the same kernel, ramdisk and binaries as recovery?). Can it be fix? Not that i know of. It looks to me like a total radio or bootloader lockout from using USB in recovery. Which means on a radio or bootloader level USB is disabled in recovery mode.
On that note I think we should raise the point to HTC that this locking down of the device does not suite our needs.Key points of fail would be as follows.
(1) Can NOT flash the boot partition from recovery. I've personally contacted HTC on this numerous times and they seem to just not care. Responding with "It's a security issue" and so forth. I would love to know how this is a security issue of any sort. Every other Android device has this ability except HTC devices since they started the HTC unlock ordeal. It's utter fail IMHO and HTC should listen to our needs .
(2) Can NOT flash recovery or boot partitions from system. This issue is NOT a deal breaker and isn't so bad when it comes down to the nitty gritty. But since the issue above exists, flashing with applications like htc dumlock and such were our only options. These work around apps cant be used to flash now because of the lockpout from system and it wouldn't be such an issue if HTC didnt lock us out in recovery from flashing boot.
(3) Can NOT flash P*IMG.zips in hboot/bootloader anymore. For the unlocked device running a custom firmware this is a must. Specially when radio updates and such are needed from the OEM. We seen a big use of this on the Sensation when HTC updated the device from Gingerbread to Ice Cream Sandwich. The update required new hboots, radios, and partitioning to actually use. So in that instead of having to flash a RUU Which didn't exist the only choice was to flash a custom P*IMG.zip that included all the radios and images need to run the builds. At this point we can't update those image/partitions without flashing an RUU. This makes no since and doesn't seem to do anything but make things more difficult on the unlocker to customize and modify their device.
(4) If all the conditions above HAVE to exist. Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
(5) WHAT WAS THE POINT OF HTC UNLOCK? It was to reach out and accept us as a community. It was to keep us from having to exploit their firmware and look for holes to gain control of a device we rightfully own. WHAT DID HTC UNLOCK DO? It unlocked the devices at first and with each new revision of the unlock it gets more locked down and harder for us to use it as intended. WHAT DOES THAT LEAD TO? It leads to us hoping someone will take the time out of their life and exploit HTC's firmware so we can have access and control of our devices. I mean, it's bad when u have people poking a device with a paperclip to get a device unlocked to avoid a official unlock.
Bottom line; I'm personally fed up with HTC's unlock. It's absolute crap! It does not serve the purpose it was intended and only makes things harder then they were before. As a devoted HTC customer it has me questioning if my next device will be an HTC. With all the other options that would allow me to spend less time trying to gain proper access to my device and more time actually having fun with it, why choose HTC? Everyone else is shying away for these same issues. Everyone with an HTC unlocked device waits for someone to exploit HTC's firmware and give them a proper unlock. Why not just choose a device without the locked down/unlock instead? IDK but HTC needs to step up and listen to us. Every HTC forum with an HTC Unlock is screaming for these issues to be fixed.
My call to HTC is to fix these issue and/or give us proper documentation on flashing firmware to our devices via custom recoveries. The boot flashing lockout is dumb, pointless, and in NO WAY a security threat AT ALL and is nothing more then a CRAP RESPONSE to something that they sould be working to correct, instead of ignoring. In the end its hurting HTC's relations with developers and is ultimately doing the opposite of what it's original intent.
HTC, PLEASE READ AND LISTEN!!!11ONEone
To everyone else, SPREAD THE WORD!!!ONEone
This is the future of HTC unlock and each new device it gets worse. Maybe HTC will listen and address these issues, then again maybe we will just need to find another OEM that supports us and does listen.
Click to expand...
Click to collapse
I read this last night. The man is absolutely correct. I am actually going to write a similar one about Asus with Transformer Prime unlock. Reading his post inspired me. Lol. All his points are extremely valid. It seems that there are manufactures who want to lock people out, makes us wait for them for updates and fight the dev community anyway possible. Then, it seems others are the exact opposite. Other manufacturers would rather the devs here fix it and they don't hear from us. The latter of the two is probably smarter. There are issues with every phone but the ones who are more dev friendly don't catch as much crap for it because at least they are fully open and the devs here can try to fix it.
Sent from my Anthrax infected 3D!
If I've helped you in any way... hit the "Thanks" button.
wait so you "thank" me but dont take the little sec to edit your post and fix it? lol
sgt. slaughter said:
wait so you "thank" me but dont take the little sec to edit your post and fix it? lol
Click to expand...
Click to collapse
Lol s off can be good if you know what your doing . But it can be a curse for those that have no idea . Such as you can screw somethin up .
I think htc isn't bad they just don't want a bunch of folks brickin and frying the CPU on a phone and sending it in sayin it was htc fault .. Tellin em fix it when it was a noobs fault.
Sent from my PG86100 using xda premium
sgt. slaughter said:
wait so you "thank" me but dont take the little sec to edit your post and fix it? lol
Click to expand...
Click to collapse
You're a mod, fix it yourself...
Vdubtx said:
You're a mod, fix it yourself...
Click to expand...
Click to collapse
That's not a mods job. Lol..
Sent from my PG86100 using xda premium
Vdubtx said:
You're a mod, fix it yourself...
Click to expand...
Click to collapse
Not Mod of this forum u dork. lol
sgt. slaughter said:
Not Mod of this forum u dork. lol
Click to expand...
Click to collapse
Lol Where is a donky smiley .
Sent from my PG86100 using xda premium
I wanted to return my HTC One to stock, and it took me hours to do so. I had to search for multiple threads, and it was a big hassle and pretty confusing. I am back to stock now, although I am still S-Off. I figured I would compile a thread helping others in similar situations return to stock. This guide will help you return to sense, lock your bootloader, unroot, hide your tampered banner, as well as prevent your device from showing up as relocked. You're device will still remain S-Off after following these steps.
Here are the steps. I am assuming the recovery is device specific, and I wouldn't recommend flashing the recovery.img on any device other than the AT&T M8.
1. Make sure your device is S-Off. If not, download firewater and S-Off your device.
2. Restore a nandroid of the stock Sense ROM, or find a stock ROM to flash. You'll have to dig around; I used a nandroid.
3. Flash SuperSU.zip in recovery on top of the stock Sense ROM. You can find the SuperSU.zip here: http://download.chainfire.eu/396/SuperSU
4. Use adb to flash the stock recovery.img to your device. You can get the recovery files here. http://forum.xda-developers.com/showthread.php?t=2711814 *ONLY FOR THE AT&T MODEL*
5. Boot back up into sense, and follow this guide to remove the tampered banner in recovery. http://forum.xda-developers.com/showthread.php?t=2708565
6. Follow this guide to lock your boot loader and make it say **LOCKED** instead of **RELOCKED**. http://forum.xda-developers.com/showthread.php?t=2708571
7. Boot your device back up, and open SuperSU. Go into settings and find the "full unroot" option and run that. Reboot your device like it suggests.
8. I would factory reset your device in settings or recovery to make sure everything's clean, although this step isn't necessary.
Enjoy Sense! Hope I was able to help some of you guys! ?
Sent from my HTC One_M8 using Tapatalk
supitsronnie said:
I wanted to return my HTC One to stock, and it took me hours to do so. I had to search for multiple threads, and it was a big hassle and pretty confusing. I am back to stock now, although I am still S-Off. I figured I would compile a thread helping others in similar situations return to stock. This guide will help you return to sense, lock your bootloader, unroot, hide your tampered banner, as well as prevent your device from showing up as relocked. You're device will still remain S-Off after following these steps.
Here are the steps. I am assuming the recovery is device specific, and I wouldn't recommend flashing the recovery.img on any device other than the AT&T M8.
1. Restore a nandroid of the stock Sense ROM, or find a stock ROM to flash. You'll have to dig around; I used a nandroid.
2. Flash SuperSU.zip in recovery on top of the stock Sense ROM. You can find the SuperSU.zip here: http://download.chainfire.eu/396/SuperSU
3. Use adb to flash the stock recovery.img to your device. You can get the recovery files here. http://forum.xda-developers.com/showthread.php?t=2711814 *ONLY FOR THE AT&T MODEL*
4. Boot back up into sense, and follow this guide to remove the tampered banner in recovery. http://forum.xda-developers.com/showthread.php?t=2708565
5. Follow this guide to lock your boot loader and make it say **LOCKED** instead of **RELOCKED**. http://forum.xda-developers.com/showthread.php?t=2708571
6. Boot your device back up, and open SuperSU. Go into settings and find the "full unroot" option and run that. Reboot your device like it suggests.
7. I would factory reset your device in settings or recovery to make sure everything's clean, although this step isn't necessary.
Enjoy Sense! Hope I was able to help some of you guys! ?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Do you think these steps could pass with returning it to an AT&T store for exchange?
chrispyutec said:
Do you think these steps could pass with returning it to an AT&T store for exchange?
Click to expand...
Click to collapse
I am not sure. I haven't tried returning to AT&T. The only thing they can get you for is S-Off, but some devices shipped S-Off so I don't know how likely that is to happen. AT&T shouldn't look into it too much. They don't have access to HTCDev so they can't see you've requested an unlock token.
Sent from my HTC One_M8 using Tapatalk
supitsronnie said:
I am not sure. I haven't tried returning to AT&T. The only thing they can get you for is S-Off, but some devices shipped S-Off so I don't know how likely that is to happen. AT&T shouldn't look into it too much. They don't have access to HTCDev so they can't see you've requested an unlock token.
Click to expand...
Click to collapse
I don't know about your AT&T store reps, but I can't think of a single one from a store local to me that would have any clue whatsoever on how to determine if the device was rooted, unlocked, etc.
Also keep in mind that, unless you've personally irritated one of them, THEY (usually) DON'T CARE. They might be required to check certain things by AT&T corporate, but do you really think that a typical sales rep is going actually exert any extra effort whatsoever to check the device?
Take the steps you mentioned. Leave the device S-OFF, but clear the "tampered" flag (as you mentioned) and any type of red warning that happens on the boot animation. Basically, just fix up the extremely obvious stuff that a sales rep couldn't possible ignore. When you go to bring it back, act like you've never heard of "XDA", and if someone asks if the phone was modified, tell them that you changed the default ringtone or something silly like that. (In other words, play dumb.)
Delete
Delete
Sent from my HTC One_M8 using Tapatalk
I was in a store the other day with a friend who needed something done to his account. Beside us was a rep trying to activate an M8 for a customer. She kept running to the back to get different SIM cards and couldn't figure out why they wouldn't fit. She was trying to put them in the SD card slot
And you're worried about them checking bootloader locks and S-Off? :laugh:
To give an example of how "closely" an AT&T store rep examines a phone for exchange/return:
I noticed a couple days ago that the volume button on my own M8 is quite a bit more.. wiggly.... than the AT&T demo M8's in my local store. It doesn't really bother me, but I figured I was still in my "14 days" so I could get a simple exchange for a more perfect volume button.
So, I spent about an hour backing up my device, changing the CID back to CWS__001, switching the firmware back to AT&T stock, switching the recovery back to stock, patching the bootloader to NOT show "unlocked" or "tampered", etc. Basically, when I was done, it was nearly impossible for even a knowledgeable person to know I had "converted" the phone to a dev edition and so on.
I brought the phone to the store and here's what they did to examine it: NOTHING.
They saw that the screen turned on, and that was it. Nothing else. I was extremely disappointed. (Perhaps it relates that I had just factory reset it, so it was sitting at that stupid AT&T welcome screen... perhaps they didn't want to waste time tapping through all the prompts?)
Oh, and I ended up NOT doing the exchange. They brought a new one up, and it had the same wiggly volume button. So, we opened a couple more boxes and all were wiggly. Being that I didn't see any other defect in my existing phone, I decided to keep my known wiggle instead of risking a different different that wiggled just as much, but might also have some other issue.
Take care
Wiggles Gary
where do we find the stock nandroid to use? Does this work to get back to stock to get the latest OTA update?
jdk2 said:
I was in a store the other day with a friend who needed something done to his account. Beside us was a rep trying to activate an M8 for a customer. She kept running to the back to get different SIM cards and couldn't figure out why they wouldn't fit. She was trying to put them in the SD card slot
And you're worried about them checking bootloader locks and S-Off? :laugh:
Click to expand...
Click to collapse
LOL you laugh. My AT&T girl did the same thing. She had the nano sim sideways in the sd card slot and couldn't figure why it wouldn't go in.
drivel2787 said:
where do we find the stock nandroid to use? Does this work to get back to stock to get the latest OTA update?
Click to expand...
Click to collapse
You can find stock nandroid backups here: http://forum.xda-developers.com/showthread.php?t=2701376. Make sure your CID matches! Instructions are in that thread.
Yes, if you follow this method you will receive OTA updates again.
Sent from my HTC One_M8 using Tapatalk
I have to use HTC's free screen replacement program, im rooted, unlocked, and s-off... soooo, i have to do this before sending them my phone right?
JoSway said:
I have to use HTC's free screen replacement program, im rooted, unlocked, and s-off... soooo, i have to do this before sending them my phone right?
Click to expand...
Click to collapse
There was a poster who claimed they told him he was ineligible for the replacement because they had him on record on HTCdev as unlocking his boot loader. Said he needed the dev edition to be able to do that without voiding his warranty. That was just one person though
I got my device 2 days ago and rooted immediately. Then I noticed I was on the old firmware version, so I used your guide to get unroot and back to stock. It worked well. Now I'm updated and rooted again
deleted
garyd9 said:
To give an example of how "closely" an AT&T store rep examines a phone for exchange/return:
I noticed a couple days ago that the volume button on my own M8 is quite a bit more.. wiggly.... than the AT&T demo M8's in my local store. It doesn't really bother me, but I figured I was still in my "14 days" so I could get a simple exchange for a more perfect volume button.
So, I spent about an hour backing up my device, changing the CID back to CWS__001, switching the firmware back to AT&T stock, switching the recovery back to stock, patching the bootloader to NOT show "unlocked" or "tampered", etc. Basically, when I was done, it was nearly impossible for even a knowledgeable person to know I had "converted" the phone to a dev edition and so on.
I brought the phone to the store and here's what they did to examine it: NOTHING.
They saw that the screen turned on, and that was it. Nothing else. I was extremely disappointed. (Perhaps it relates that I had just factory reset it, so it was sitting at that stupid AT&T welcome screen... perhaps they didn't want to waste time tapping through all the prompts?)
Oh, and I ended up NOT doing the exchange. They brought a new one up, and it had the same wiggly volume button. So, we opened a couple more boxes and all were wiggly. Being that I didn't see any other defect in my existing phone, I decided to keep my known wiggle instead of risking a different different that wiggled just as much, but might also have some other issue.
Take care
Wiggles Gary
Click to expand...
Click to collapse
Believe it or not all you have to do is put the stock rom back on the device. You still have a hardware warranty. If say, your speaker is broken that would have occurred regardless of you flashing the ROM. Flashing the rom is not a punishment for you to live with bad hardware... However try to put back to stock if you can.
thank u for helping
Lil Jones said:
Believe it or not all you have to do is put the stock rom back on the device. You still have a hardware warranty. If say, your speaker is broken that would have occurred regardless of you flashing the ROM. Flashing the rom is not a punishment for you to live with bad hardware... However try to put back to stock if you can.
Click to expand...
Click to collapse
AT&T terms clearly state that they have the "right" to void warranty if the software is modified.
In reality, AT&T will not check or care. Its more important to keep you as a monthly account holder, versus the relatively modest price if a refurb phone. I've seen many reports of successful warranty exchanges with unlocked bootloader, root, even having an obviously custom ROM (like CM) installed.
Return to close as stock as possible/feasible to play it safe. But its likely not going to be a deal breaker.
can i be S-Off and do ATT OTA's?
rahtrip said:
can i be S-Off and do ATT OTA's?
Click to expand...
Click to collapse
Sure. But if you've bothered to s-off, why would you want to?
Sent from my HTC One_M8 using XDA Free mobile app
Hello. Thanks in advance for your time and advice.
I've got a brand new HTC One M8, AT&T, firmware says 4.4.2 with no available updates.
I want to create an initial backup. I'm a computer technician, and just dabbling in Android, and it's important for me to make a "clone" of my phone before I proceed to wreck things. (This is a replacement phone, the last one had a hardware issue... I swear... I managed to install ViperOne onto it, for a week before the screen faded to white and died.)
I assume I'll need root access to make a proper backup. I also assume I should use Nandroid. I've not used the app before, but I'm sure I can figure it out. As far as root goes, I previously used Hasoon2000's HTC One 2014 (M8) All-In-One Toolkit, which worked well, as far as I could tell. (It's a visual basic program with scripts to download drivers, register at htcdev, get token id, submit it, unlock bootloader, flash recovery, and lots of nice ADB commands. Is this a good option to use? I hear many people use S-Off, but I don't really see a need... ?
So, I assume I'll need a new token ID from HTC, as the previous one I got corresponds to the old, malfunctioning phone.
After it's unlocked, I'd use the toolkit to grant perm root. That would be a great place to be for now. I plan to wait until the 4.4.4 update is pushed, then worry about installing a new rom.
Am I on the right track?
For the AT&T version (and most the major US carrier versions) we are lucky enough to have RUUs. So really, no need to backup the stock configuration. If you like, grab the RUUs and save them to your computer so you have them ready if and when it is needed.
Nandroid isn't a specific app, its just a generic term for a backup made with recovery. The custom recovery is your choice: TWRP, Clockworkmod, Philz.
Just a personal opinion, I would actually strongly recommend against using the toolkit for a couple reasons: most importantly using the toolkit robs you of an important learning opportunity. Doing the steps "manually" is a key way to learning your way around fastboot/adb. Doing the steps manually isn't that hard, and shortcutting the process with the toolkit really doesn't gain you much. Another key issue, is the toolkit introduces an additional point of failure. In fact, I've seen folks have trouble doing some of the steps with the toolkit; where doing the steps "manually" worked without a hitch. And the toolkit hasn't been updated for a long time, and will install an obsolete version of TWRP recovery, which in itself can cause issues.
If you used the toolkit before, you can certainly use it again. This is likely the path of "least" resistance, the the "easy" way to do things. But I wouldn't necessarily call it the "best" way to do it. If you don't already know your way around adb, I would do the steps manually. Since you have a background in computers, you will probably even find the manual process more enjoyable.
Yes, you would need to unlock the bootloader again via HTCDev.com, as the unlock bin code in based on the phone's unique IMEI.
The process would be as simple as unlocking the bootloader using HTCDev.com (very easy, the website is self-explanatory). Use fastboot to install custom recovery. Then to gain root, just flash SU or SuperSU in recovery. If you need a step-by-step guide, there is an excellent one here: http://forum.xda-developers.com/showthread.php?t=2799796
But also be aware that once the 4.4.4 OTA rolls out, you will need to return to stock recovery, and also restore any system files modifed by root, in order to install the OTA.
Thanks, redpoint73
Exactly the answer I was looking for. The guide looks great. Looks like there's a lot of useful information about reverting to stock, too. I guess I'll have a go at it now, as opposed to waiting for the update. Like you say, it's good to know things. Thanks much.
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
AT&T HTC ONE M8
jball said:
@redpoint73
Now I'm only asking cause I don't know everything. Couldn't those who have S-off just RUU the update once available instead of reverting to complete stock state(no root,no custom recovery, locked Bootlaoder)?
Click to expand...
Click to collapse
Absolutely. In fact S-off is not even required to run an RUU intended for your version (AT&T). If s-on, the added step of relocking the bootloader is all that is needed to run the RUU.
HTC seems to have gotten better about releasing the RUUs promptly. In fact, the previous (ill fated) 4.4.3 update saw the RUU and OTA roll out on the same day. Although this hasn't always been the case. On past devices, the RUUs were not released for weeks (sometimes longer) after the OTA started to roll out. And many folks don't want to wait that long.
Also, relocking the bootloader is not required to OTA, only to RUU.