[Q] Fully Stock HTC One M7 - One (M7) Q&A, Help & Troubleshooting

So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....

xxshererxx said:
So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....
Click to expand...
Click to collapse
what exactly is happening when you try and unlock the bootloader?

xxshererxx said:
So I have a fully stock HTC One and have spent all night trying to unlock the bootloader. Nothing seems to work I have never rooted this phone, everything I have read makes it seem as if it's impossible. I've tried the adb/fastboot, htcdev, and changing CID methods. Plus I have read of various other ways that already require a root. Which I cannot do seeing how I am still locked and S-ON.
To be honest I'm at the edge and I think I'm just going to give up. I'm on 4.2.2 - hboot 1.54. I was a previous owner of the Thunderbolt which was not a bad phone, I rooted that and everything no questions asked. Although I do remember HTC taking the longest for OTA updates, not a huge fan of HTC.
If anyone has any suggestions on how to unlock the bootloader I will be fine from there. I'm positive I have all the right equipment and prerequisites just not sure if I really am at the end of the road.
Anything useful goes a long way right now.
Thanks.....
Click to expand...
Click to collapse
Is urs the AT&T One? Then the bootloader unlock process is different. If urs is the standard international SIM unlocked, then ideally you should see a splash after you run the bootloader unlock command, which prompts you to unlock the bootloader. Please state what exactly ur issue is when u try to bootloader unlock

I'm with Verizon but it just gives me a 1 line error message doesn't run through anything else or load up anything. I type in "bootloader oem unlock" or whatever after clearly identifying my device is connected with "adb device" and nothing happens. It takes about 0.14 sec and says something along the lines of "[ERRORR] ......" after running again it takes 0.00 sec and says same thing, I can screenshot if you think it would be more helpful.
Please help, I appreciate both responses. Just really want this to work.

xxshererxx said:
I'm with Verizon but it just gives me a 1 line error message doesn't run through anything else or load up anything. I type in "bootloader oem unlock" or whatever after clearly identifying my device is connected with "adb device" and nothing happens. It takes about 0.14 sec and says something along the lines of "[ERRORR] ......" after running again it takes 0.00 sec and says same thing, I can screenshot if you think it would be more helpful.
Please help, I appreciate both responses. Just really want this to work.
Click to expand...
Click to collapse
Hahahaha Verizon is REALLY REALLY BAD when it comes to dev. support. Ideally, you shouldn't be posting this in this forum. Post it on the Verizon forum. But, I can help you.
http://rumrunner.us/downloads-2/
Download the package. Extract the zip and run the 'soju.exe' program. Please read ALL the pre-requisites mentioned in the instructions tab.
P.S. From next time if you're asking for help, please state that you're on Verizon

raghav kapur said:
Hahahaha Verizon is REALLY REALLY BAD when it comes to dev. support. Ideally, you shouldn't be posting this in this forum. Post it on the Verizon forum. But, I can help you.
Download the package. Extract the zip and run the 'soju.exe' program. Please read ALL the pre-requisites mentioned in the instructions tab.
P.S. From next time if you're asking for help, please state that you're on Verizon
Click to expand...
Click to collapse
Worked like a charm, but now I am having trouble with the recovery portion of all this.
I have downloaded and installed the TWRP Manager app and then went to install the recovery and it said my device is not supported, this same problem happened with CWMR.

xxshererxx said:
Worked like a charm, but now I am having trouble with the recovery portion of all this.
I have downloaded and installed the TWRP Manager app and then went to install the recovery and it said my device is not supported, this same problem happened with CWMR.
Click to expand...
Click to collapse
I think you'll find more help here: http://forum.xda-developers.com/verizon-htc-one

Related

[Q] Q: Back to stock?

So I know XDA is full of answers to this one, but it seems everyone either has some snarky comment like, "they won't check' or whatever. There are also some ok answers and tuts but some of it's confusing and a lot of the threads go off topic. So i'd like to ask, how do i get my phone back to stock? i have to mail my device back in for a warranty exchange as the speakers and camera stopped working suddenly.
My device is stock rooted, odex rom w/ TWRP. unlocked bootloader. Super CID and S-off. Tampered message gone in boot loader. My laptop runs Windows 8, which I'm having an issue getting the HTC manager to stay open for some reason, even after an uninstall/ reinstall of the manager and drivers. The drivers themselves seemed to have installed fine as my device is recognized as "my HTC" though when in fastboot, my comp will tell me the device is unrecognized. Using the stock usb plug that came with my phone and I've plugged in to both usb 3.0 and 2.0 ports. And yes, I do have ADB in the root of my computer, though I'm wondering if i need a different type of ADB since this is the one i used with windows 7 a while back..or does it matter?
I'd like to get things back to stock as much as possible and would be very appreciative. Thanks!
If you know there are answers why not use the search function and find them? There is a thorough guide made by mike1986 so I suggest you find that and go from there...
whitetiger_0603 said:
So I know XDA is full of answers to this one, but it seems everyone either has some snarky comment like, "they won't check' or whatever. There are also some ok answers and tuts but some of it's confusing and a lot of the threads go off topic. So i'd like to ask, how do i get my phone back to stock? i have to mail my device back in for a warranty exchange as the speakers and camera stopped working suddenly.
My device is stock rooted, odex rom w/ TWRP. unlocked bootloader. Super CID and S-off. Tampered message gone in boot loader. My laptop runs Windows 8, which I'm having an issue getting the HTC manager to stay open for some reason, even after an uninstall/ reinstall of the manager and drivers. The drivers themselves seemed to have installed fine as my device is recognized as "my HTC" though when in fastboot, my comp will tell me the device is unrecognized. Using the stock usb plug that came with my phone and I've plugged in to both usb 3.0 and 2.0 ports. And yes, I do have ADB in the root of my computer, though I'm wondering if i need a different type of ADB since this is the one i used with windows 7 a while back..or does it matter?
I'd like to get things back to stock as much as possible and would be very appreciative. Thanks!
Click to expand...
Click to collapse
Open android-sdk and click on sdk manager and update adb to the latest version.
Here is a thread to undo s-off and lock your bootloader http://forum.xda-developers.com/showthread.php?t=2314582, firstly change cid http://forum.xda-developers.com/showthread.php?t=2317536.
gee2012 said:
Open android-sdk and click on sdk manager and update adb to the latest version.
Here is a thread to undo s-off and lock your bootloader http://forum.xda-developers.com/showthread.php?t=2314582, firstly change cid http://forum.xda-developers.com/showthread.php?t=2317536.
Click to expand...
Click to collapse
Thank you very much.
Edit: so I downloaded Android sdk to this comp but something isn't working right? Should i have gotten the one in the "other platforms" list? The one i downloaded didn't say it's was Windows 8 compatible, however the DL in the other list is not OS specific, just says it's for Widows 32 or 64 bit.
EddyOS said:
If you know there are answers why not use the search function and find them? There is a thorough guide made by mike1986 so I suggest you find that and go from there...
Click to expand...
Click to collapse
Why are you talking? This is a troubleshooting forum. Not a "go ahead and ask a question and maybe we'll be nice about giving you an answer forum".
whitetiger_0603 said:
Why are you talking? This is a troubleshooting forum. Not a "go ahead and ask a question and maybe we'll be nice about giving you an answer forum".
Click to expand...
Click to collapse
I'm afraid you're wrong. Rule 1 from the forum Rules:
"1. Search before posting.
Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news"
http://forum.xda-developers.com/announcement.php?a=81
Basically, search first. Chances are it has already been asked and answered - as proven in gee2012's post...
Reading your OP would indicate you know the answer is out there but can't be bothered to search - hence my first reply
EddyOS said:
I'm afraid you're wrong. Rule 1 from the forum Rules:
"1. Search before posting.
Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news"
http://forum.xda-developers.com/announcement.php?a=81
Basically, search first. Chances are it has already been asked and answered - as proven in gee2012's post...
Reading your OP would indicate you know the answer is out there but can't be bothered to search - hence my first reply
Click to expand...
Click to collapse
Learn to read an comprehend. Obviously when I said I know i can search, then gave an indication of what was found, then that means I did search, and of course, that's what i found. But instead, you prefer to go the route that i also indicated, and chose to be snarky and rude, rather than just no answer the question at all. But thank you very much for wasting your time and mine by being as such.
Easy method: flash RUU and use revone to relock and
fastboot oem writesecureflag 3
More tricky
adb getvar version-main
Post answer here.
whitetiger_0603 said:
Learn to read an comprehend. Obviously when I said I know i can search, then gave an indication of what was found, then that means I did search, and of course, that's what i found. But instead, you prefer to go the route that i also indicated, and chose to be snarky and rude, rather than just no answer the question at all. But thank you very much for wasting your time and mine by being as such.
Click to expand...
Click to collapse
Thing is, though, I did answer your question. mike1986 has a thorough guide on how to go back to stock so searching for that would've given you the answers you required

[Q] HTC One... Soft brick?

A friend recently gifted me a used One that he had previously unlocked and rooted, but returned to stock. I am attempting to unlock, root, and SIM unlock it. (It is sprint, I want to use it on att)
I do not know a lot about the One, I am not a huge fan of HTC in general as it seems that their phones were always overly complicated to work on.
I successfully unlocked the bootloader and threw clockworkmod recovery on, which is when the problems started. Since then, I was no longer able to boot the phone...
Then, as usual, the tampered message showed in my HBOOT menu.
I installed twrp recovery but that failed to work, so I then realized I had not downloaded the version for Sprint HTC Ones. After downloading the correct version, it does boot into recovery.
However, I cant seem to install any roms (this includes through ADB). It throws the error message "FAILED remote not allowed"
So Im sort of in a bind here, and I thought maybe someone with more knowledge about the One could help me out. Is the sprint version even capable of use on an ATT network, and if so, can someone please tell me how on earth I can fix this thing? I want to make a backup phone for use due to the fact that I'd like to sell my nexus 5 and buy a Oneplus One.
Thanks a ton!
Any help here? I still haven't been able to fix this. I've been trying several different recoverys, roms, etc. I also tried to reboot the phone to RUU but that was no help either. Remote errors..
EvanLovesToast said:
Any help here? I still haven't been able to fix this. I've been trying several different recoverys, roms, etc. I also tried to reboot the phone to RUU but that was no help either. Remote errors..
Click to expand...
Click to collapse
The Sprint HTC One is a CDMA phone and the AT&T is a GSM. They have different radios and partitions. Since it is a Sprint phone, you need to make sure you only put Sprint compatablile software on your phone, if you don't you will end up bricked. You might find more resources to help you at the Sprint HTC One forum. This forum is primarily for the GSM variants. I don't know which RUU you ran but you might want to find out what is really on your phone by running a fastboot getvar all on your phone. It will tell you what hboot, firmware, security, etc. Depending on your status, you can only flash certain RUU's.
Thank you very much for the info. Problem is, I was unable to even try using an RUU because it gives me the error that the phone is not even connected to the computer..
EvanLovesToast said:
Thank you very much for the info. Problem is, I was unable to even try using an RUU because it gives me the error that the phone is not even connected to the computer..
Click to expand...
Click to collapse
Check nkk71's post the first three or four questions may help you out. But like I said, you really need to go to the Sprint forum and post your questions there because what works for one variant may not work for the other variants.

Nexus 6 Motorola Help Needed

Hi - apologies first of all if this is covered elsewhere in the forums.
I purchased a brand new Nexus 6 directly from Motorola this week as they had slashed the price down to just £309 for the 64gb. It arrived Monday. I turned it on, signed into my network etc. it starting updating apps. Then it said that Android 5.1.1. was available so I downloaded it and proceeded to install. About halfway through the installation it crashed. My phone is now stuck on continually booting up and saying 'optimising xxx apps'. After a bit of research, I found that this was a common problem as 5.1.1. was trying to update and some apps were incompatible. So I read many forums and booted into Recovery mode, wiped the cache, wiped data and did a factory reset, but it still won't work.
I called Motorola who told me that they have had many of their Nexus 6s do this and all they could do was to refund me the phone as they now are out of stock.
Further research led me to read about 'flashing' the phone so I downloaded Wugfresh but I cannot get into the phone to enable me to debug. After many hours today I have come to the conclusion that I am never going to be able to use my new phone which I am gutted about.
My question is, is there anyway to flash the phone without enabling debugging because I cannot get into the main menu because all if does is just keep optimizing apps?
Many thanks for reading and any assistance would be greatly appreciated.
bacon_roll said:
Hi - apologies first of all if this is covered elsewhere in the forums.
I purchased a brand new Nexus 6 directly from Motorola this week as they had slashed the price down to just £309 for the 64gb. It arrived Monday. I turned it on, signed into my network etc. it starting updating apps. Then it said that Android 5.1.1. was available so I downloaded it and proceeded to install. About halfway through the installation it crashed. My phone is now stuck on continually booting up and saying 'optimising xxx apps'. After a bit of research, I found that this was a common problem as 5.1.1. was trying to update and some apps were incompatible. So I read many forums and booted into Recovery mode, wiped the cache, wiped data and did a factory reset, but it still won't work.
I called Motorola who told me that they have had many of their Nexus 6s do this and all they could do was to refund me the phone as they now are out of stock.
Further research led me to read about 'flashing' the phone so I downloaded Wugfresh but I cannot get into the phone to enable me to debug. After many hours today I have come to the conclusion that I am never going to be able to use my new phone which I am gutted about.
My question is, is there anyway to flash the phone without enabling debugging because I cannot get into the main menu because all if does is just keep optimizing apps?
Many thanks for reading and any assistance would be greatly appreciated.
Click to expand...
Click to collapse
You could try and flash a flash a factory image via fastboot...
draa2711 said:
You could try and flash a flash a factory image via fastboot...
Click to expand...
Click to collapse
No, he can't try, he has his bootloader locked.
OP, this thread is a classic case of why the first thing anyone should do with this device, even if not planning to root or otherwise modify it, is to enable developer options in settings and enable both USB Debugging and OEM Unlocking. Without both enabled there's no way to resolve your problem, and unfortunately you'll need to contact Motorola and arrange a return, since they are out of stock.
Once you get your money back, look on Swappa for a used device. You may be able to get a device that way at a lower price than what Motorola offers.
Strephon Alkhalikoi said:
OP, this thread is a classic case of why the first thing anyone should do with this device, even if not planning to root or otherwise modify it, is to enable developer options in settings and enable both USB Debugging and OEM Unlocking. Without both enabled there's no way to resolve your problem, and unfortunately you'll need to contact Motorola and arrange a return, since they are out of stock.
Once you get your money back, look on Swappa for a used device. You may be able to get a device that way at a lower price than what Motorola offers.
Click to expand...
Click to collapse
Thanks for your advice, but I had no idea, probably like so many others who aren't as clued up on Android that USB Debugging even existed. I just bought a phone that I wanted that now is no good to me having never been able to use it because of a bug in 5.1.1. I am returning to Motorola for refund.
Without wanting to raise false hopes, there is a thread in this forum where the OP says he recovered his device even though the bootloader was locked (he was certain of it, he said...), other people replying that this was impossible, and yet they eventually seemed to accept that it might be. My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
I'll see if I can find the thread for reference, but in the meantime does anyone recognise the thread I mean?
bacon_roll, since I'm vegetarian I shouldn't be helping you but have you tried Wugfresh's option of "Phone is bricked/bootlooping"? I think all it does is to reboot the device into bootloader anyway, but I think this might be worth a go if you haven't already tried it. You did mention that you've booted into recovery, but you don't mention bootloader mode.
draa2711 said:
You could try and flash a flash a factory image via fastboot...
Click to expand...
Click to collapse
Thanks. As per my post, I can't because the phone is locked.
dahawthorne said:
My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
Click to expand...
Click to collapse
You could check in the About Phone menu to see what version you're on.
Both Android 5.x and Android 6.x have an OEM Unlocking toggle in Development Options. I know because I followed my own advice given above in my previous post in order to flash the latest Android 6.0.1 ROM to the device, and then checked Developer Options afterward.
dahawthorne said:
Without wanting to raise false hopes, there is a thread in this forum where the OP says he recovered his device even though the bootloader was locked (he was certain of it, he said...), other people replying that this was impossible, and yet they eventually seemed to accept that it might be. My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
I'll see if I can find the thread for reference, but in the meantime does anyone recognise the thread I mean?
bacon_roll, since I'm vegetarian I shouldn't be helping you but have you tried Wugfresh's option of "Phone is bricked/bootlooping"? I think all it does is to reboot the device into bootloader anyway, but I think this might be worth a go if you haven't already tried it. You did mention that you've booted into recovery, but you don't mention bootloader mode.
Click to expand...
Click to collapse
Hi - please get my hopes up, I really want to keep this phone if I can
Without sounding like a complete nerd, what is the difference between recovery and bootloader mode?
When I scroll through the options with both arrows pressed and power button, I have START, RESTART BOOTLOADER, RECOVERY MODE, POWER OFF, FACTORY, BARCODES, BP TOOLS, QCOM & BOOTLOADER LOGS
I have done factory wipe/cache/restart bootloader etc.
How do I boot into bootloader mode please.
Thank you.
Overly simplistic reply here, but it should be enough to answer the question.
The bootloader prepares the system for booting. Once it's done its work it hands off control of the system to Android's kernel. Recovery is a mini operating system used to initiate low level functions such as wiping the on-board storage. The screen you describe I believe is the bootloader interface, hence why you have a "Restart Bootloader" option instead of "Start Bootloader".
You can probably save some serious money by returning and buying off swappa really. I just broke my N6 and couldn't find one in stock but, used swappa to find one around $260 that was only used for 2 weeks.
If you already have Wugfresh's Nexus Root Toolkit installed, use the "Install & test drivers" button to make sure that you have all your drivers installed properly. If all is ok, although I know this won't be popular advice, then start with the "My device is soft-bricked", then try the "Unlock" button and then "Flash stock" button. If the phone is already a paperweight then I don't believe it can possibly do any more harm, and you might even hit it lucky...
If none of this works, grab Motorola's refund offer with both hands...
Strephon Alkhalikoi said:
Overly simplistic reply here, but it should be enough to answer the question.
The bootloader prepares the system for booting. Once it's done its work it hands off control of the system to Android's kernel. Recovery is a mini operating system used to initiate low level functions such as wiping the on-board storage. The screen you describe I believe is the bootloader interface, hence why you have a "Restart Bootloader" option instead of "Start Bootloader".
Click to expand...
Click to collapse
Ok thank you.
I downloaded and installed Wugfresh, followed all the instructions. It won't work once it goes to flash because it can't see my phone connected. My PC recognises it as Nexus 6 but on the 'bootloader' screen at the bottom, it says Connect USB Data Cable, even though the phone says Battery OK (Charging). I tried to install latest USB drivers but apparently the latest are installed.
I am giving up now as I don't believe I can try anything else. Just strange that Wugfresh won't see the phone, yet my PC does.
Thanks.
Oh well...
You did try the Wugfresh "Test drivers"? It has a really helpful walkthrough on deleting and installing drivers. I'd give it a go before you give up.
dahawthorne said:
Oh well...
You did try the Wugfresh "Test drivers"? It has a really helpful walkthrough on deleting and installing drivers. I'd give it a go before you give up.
Click to expand...
Click to collapse
Ok I don't often use this phrase because I think it's very over rated but O M G - IT WORKED!!
I followed the driver guide in Wugfresh as you suggested, downloaded the CORRECT drivers, flashed it, unlocked bootloader, enabled usb debugging (just in case ) and then restored it then finally relocked the bootloader. It worked flawlessly and after setting up it is now 6.0.1 with the 1 Jan 2016 security patch applied - OTA.
I can't think you enough for your suggestion and advice, I really appreciate it and glad that I persevered with it.
Have a great weekend.
Thanks.
Bacon_Roll (vegetarian version)
That is absolutely fantastic news. I'm almost as pleased as you are. Remote assistance across the ether - you can't beat it with a big stick...
But as your attorney I advise you to go back into bootloader, check the connection (fastboot devices) and unlock again (fastboot oem unlock). This will wipe your device, but I reckon in the last 25 minutes you won't have been able to install much.
There are so many threads on this forum where people have been told "You're stuffed" because they have a problem and have a locked bootloader. Just this afternoon in another thread I read, literally in capital letters "DON'T RELOCK YOUR BOOTLOADER" for this very reason - without it you don't have recourse to the recovery tools you may one day need.
(P.S. Another person whose thread I followed also managed to get a result with NRT after all else had failed. I suggested to him that he might like to thank the developer, Doug Cohen/Wugfresh, more tangibly by donating a few dollars, which you can do through Paypal on his website. After all, he just saved your £300 phone... ).
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
dahawthorne said:
That is absolutely fantastic news. I'm almost as pleased as you are. Remote assistance across the ether - you can't beat it with a big stick...
But as your attorney I advise you to go back into bootloader, check the connection (fastboot devices) and unlock again (fastboot oem unlock). This will wipe your device, but I reckon in the last 25 minutes you won't have been able to install much.
There are so many threads on this forum where people have been told "You're stuffed" because they have a problem and have a locked bootloader. Just this afternoon in another thread I read, literally in capital letters "DON'T RELOCK YOUR BOOTLOADER" for this very reason - without it you don't have recourse to the recovery tools you may one day need.
(P.S. Another person whose thread I followed also managed to get a result with NRT after all else had failed. I suggested to him that he might like to thank the developer, Doug Cohen/Wugfresh, more tangibly by donating a few dollars, which you can do through Paypal on his website. After all, he just saved your £300 phone... ).
Click to expand...
Click to collapse
Understood! I will take your advice on both counts but I was going to donate anyway as it really is a fantastic tool.
Thanks again
Strephon Alkhalikoi said:
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
Click to expand...
Click to collapse
Thanks for your help over the thread Strephon - much appreciated.
Strephon Alkhalikoi said:
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
Click to expand...
Click to collapse
FFS, it's not a magic wand, people! It can't do anything that fastboot and adb can't. Don't start a religion here instead teaching people to do stuff with their phones, Christ!
Some people were lucky enogh that their phones came with 5.0, and some early 5.0s didn't check yet for the Enable OEM Unlocking switch. You could have typed fastboot OEM unlock and achieved the same.

Help for a noob

Hello, firstable congratulations to everyone to made an awesome forum, page, etc...
Im from Mexico and I have a HTC one M8 Sprint and I use it on GSM band
a guy sold me with a program named teamwin this program appears when I try to install the new version
I already have the 4.4.3 android version, 6.0 sense and 2.16.651.4 sofware version
and my doubt is can I make any modd to my celphone? I guess that's sounds pretty obviously but I'm new on the topic
I remember I can modd a sony ericsson telephones (like w600) but now Im so noob on the celphone topics.
I like learn new things and I only asking for your help, maybe if you can help me I appreciate that
All the links you can give me will be readed 100% for sure.:good:
So greetings for everyone and again please help me to get this cellphone a new life :laugh:
Hold down power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons and only hold vol down. Don't let go, until you see a white screen with various info on it. This it the bootloader. If the phone simply reboots to OS or Safe Mode, you just had bad timing of the button combo. Repeat the process until you see the bootloader screen.
On the bootloader screen, does it say RELOCKED, UNLOCKED, or LOCKED near the top?
Does it say Software modified, or official?
Does it say s-off or s-on?
redpoint73 said:
Hold down power and vol up for several seconds to force a reboot. The moment the screen goes dark to reboot, let go of those buttons and only hold vol down. Don't let go, until you see a white screen with various info on it. This it the bootloader. If the phone simply reboots to OS or Safe Mode, you just had bad timing of the button combo. Repeat the process until you see the bootloader screen.
On the bootloader screen, does it say RELOCKED, UNLOCKED, or LOCKED near the top?
Does it say Software modified, or official?
Does it say s-off or s-on?
Click to expand...
Click to collapse
It says
Tampered
Unlocked
S-ON
About the OS I don't know, the phone already has SuperU app, also I don't know how it works
Erbat said:
It says
Tampered
Unlocked
S-ON
About the OS I don't know, the phone already has SuperU app, also I don't know how it works
Click to expand...
Click to collapse
You need to update the firmware, to do much of any mods (like current ROMs).
You can do so by either:
1) Finding the proper stock nandroid and stock recovery, then OTA update to latest version.
2) Relock the bootloader, and use latest Sprint RUU (will wipe the phone).
redpoint73 said:
You need to update the firmware, to do much of any mods (like current ROMs).
You can do so by either:
1) Finding the proper stock nandroid and stock recovery, then OTA update to latest version.
2) Relock the bootloader, and use latest Sprint RUU (will wipe the phone).
Click to expand...
Click to collapse
I'm a bit affraid because I don't know if after to do that my phone still works
It's sprint and I use it here in mexico with movistar so I need something else to do this proccedure? I also searching the topics you told me here in the forum
Erbat said:
I'm a bit affraid because I don't know if after to do that my phone still works
Click to expand...
Click to collapse
In your first post, you ask about doing mods. Now you are saying you are afraid to. So I have no idea what your comfort level, what you are willing to accomplish, etc.
As long as you are willing to learn, put in some time reading and understanding, and follow instructions carefully, there isn't much to be afraid of. Any mods to the phone involve some risk. But the risk of permanent damage (a true "brick") are minimal. The worst that is likely to happen, is the phone fails to boot, and you may need to troubleshoot for an hour to 2 to get it back running. But that happens to just about anyone that mods phones, at some time or other. Its just part of the game.
But in the phone's current condition, something needs to be done by you, in order to update the phone in any way; whether it be by official means (RUU or OTA) or custom ROM. Otherwise, it will be stuck on Android 4.4.3 as it is now.
Erbat said:
It's sprint and I use it here in mexico with movistar so I need something else to do this proccedure?
Click to expand...
Click to collapse
Not sure what you are asking, are you wondering if any additional hardware is needed? You will need a computer for either method I stated, plus the sync cable that came with the phone (or other charge/data cable). PC is required for Method #2.
Yes for sure Im reading the past days about the topic and the fears I guess its for my phone became to an expensive brick, but I want to do this, I sent you a PM and I read your answer sorry for do that.
And finally about the last quote, I mean the M8 its originally sprint (on the starts screen says) so I want to know if its possible make the unblock totally to use on any company of the world or the country (Mexico) above than GSM, maybe 3G or in the best way 4G
Erbat said:
And finally about the last quote, I mean the M8 its originally sprint (on the starts screen says) so I want to know if its possible make the unblock totally to use on any company of the world or the country (Mexico) above than GSM, maybe 3G or in the best way 4G
Click to expand...
Click to collapse
So it sounds like you already using the phone on Movistar, just not with 3G or 4G?
There is a mod to unlock bands, which seems to work on your Sprint CDMA version (from what I understand). But it requires s-off ($25 by sunshine app) and is a slightly more complicated mod: http://forum.xda-developers.com/htc-one-m8/general/unlock-bands-qualcomm-device-phone-t2880239
So if you are unsure about doing what I've previously described; the mod to unlock bands is definitely the next level beyond that. Mods done with s-off are more risky, and can actually brick the phone (render it permanently unusable).
Whatever you do, do NOT try to flash another carrier/region versions radio, firmware, RUU, etc. in an attempt to change the band support. You may see some recommendations to that effect. But this does NOT work on the Sprint version, and will probably BRICK your phone.
Sorry I think I don't give my idea correctly, my English is not good.
I wonder if you can make my htc have the most updated software and if it is possible to use other phone network than the GSM because since I buyed (used) has the same software, the same HTC Sense and I could only use the internet GSM mobile network
My phone is
m8_WHL PVT SHIP S-ON *Unlocked*
So I would like to write the correct idea because your help it's usefull for me
really I appreciate your help and therefore not want to lose by confusion or my bad english
then I hope this time to let me know if this is better for your
I'm trying to do my best
Erbat said:
Sorry I think I don't give my idea correctly, my English is not good.
I wonder if you can make my htc have the most updated software and if it is possible to use other phone network than the GSM because since I buyed (used) has the same software, the same HTC Sense and I could only use the internet GSM mobile network
Click to expand...
Click to collapse
Updating the software is a completely separate matter from the phone's band support (3G and LTE bands the phone is compatible with).
I already told you how to update the software, in Post #4 above.
To see if the phone will work with your carrier's 3G or LTE network, you first need to know what 3G and 4G band (or bands) they use for each. Can't really do anything without that basic info. Either research online, or call your carrier and ask them. This is something you should have done before buying the phone; as changing to the proper band support is not always possible.
redpoint73 said:
To see if the phone will work with your carrier's 3G or LTE network, you first need to know what 3G and 4G band (or bands) they use for each. Can't really do anything without that basic info. Either research online, or call your carrier and ask them. This is something you should have done before buying the phone; as changing to the proper band support is not always possible.
Click to expand...
Click to collapse
The band works on 850/1900, while 4G LTE conection use band 4 - LTE AWS frecuency of 1700 MHz and 2100 MHz.
I work today on the software ( the most important for me )
Erbat said:
The band works on 850/1900, while 4G LTE conection use band 4 - LTE AWS frecuency of 1700 MHz and 2100 MHz.
Click to expand...
Click to collapse
Sprint M8 supports 3G bands 850 and 1900.
Are you sure you entered your carrier's APN info correctly?
Did you try the SIM card in another phone, to make sure the SIM works for 3G?
redpoint73 said:
Sprint M8 supports 3G bands 850 and 1900.
Are you sure you entered your carrier's APN info correctly?
Did you try the SIM card in another phone, to make sure the SIM works for 3G?
Click to expand...
Click to collapse
yes I use the right APN settings but when I bought the guy who sold it to me also told me it was unblock for any company here in Mexico but the problem is that you could not upgrade because when the file is downloaded and is installed, the phone enters into recovery mode and can not be or I do not know if it's my mistake, you can not install at all
He say that if I upgrade or modify the phone I can lose part of the unblock of the phonel and it became unusable here in Mexico
I screwed a lot
I don't know what I did wrong on the process of re-stock the phone and now don't start.
only shows the white screen with HTC green logo.
I rememberd when I try to wipe I check all the options and "I swipe to wipe" later when the phone will be reboot
shows me a message about the superU and I install (because already has it)
I was scared and search about this and only found a way to enter on bootloader and says this
*Tampered*
*Relocked*
Well, 6 hours later I have this now:
*Tampered*
**Unlocked**
m8_WHL PVT SHIP S-ON
HBOOT-3.18.0.0000
OS-2.16.651.4
eMMC-boot 2048MB
but when I unlock the bootloader (here's the tutorial of bootloader http://www.htcdev.com/bootloader)
I see the recovery mode once but when I try to do the next step (http://forum.xda-developers.com/showthread.php?t=2755657)
I can not start the recovery mode and I don't do any of progression
Also I can see an message saying me the phone hasn't any OS file so I guess that's the reason I can make it start, only turn on and shows the same white screen with HTC logo, I can entered to Bootloader and FASTBOOT but when I select recovery the phone returns to HBOOT and when I turn off and later turn on happen the same (entered directly to HBOOT screen)
Im a bit concerned about that I hope you can teach me how
*Edited now I can enter to recovery I relocked and unlocked again and I can enter again to recovery and bootloader, please help me to put the files of OS
maybe with a SD card?
Return to stock
Hi Erbat,
first of all it would be nice to get an overview of your device and its versions, you can do this by doing the fastboot command "fastboot getvar all"
The most important version wich you already have is your OS 2.16.651.4, everything what you try to flash to your device if you want to return to stock should match this number or it will mostly fail.
So at this point forget about the Guide with official OTA updates and root access, because its for 4.16.401.10 and you should mainly focus on returning to stock without root to get new updates (easier)
I dont know how much knowledge you already have but just to mention:
Every OS with 2.16.651.4 is for your Sprint version, this means all of the files without 651 will lead in the wrong direction.
Later when you use a RUU ("official" files to return to stock firmware) or a nandroid backup (stock backup created by other users), the files and backups you will find have to match exactly to your OS Version 2.16.651.4 to work.
So at the moment you should focus on returning your device back to stock firmware and OS first, after that you can recieve official OTA updates from HTC :good:
The tutorials/threads you should focus on are mainly these two:
[GUIDE][S-ON] Restore your (European) HTC One M8 back to stock
[tutorial] How to get back on stock with TWRP Stock Nandroid Backups
Edit: You can't use your recovery, because if i understood this right you got TWRP (a custom recovery) before and might have corrupted/deleted it, simply flash the newest version of TWRP 2.8.7.0 with the fastboot command "fastboot flash recovery *NAME-OF_RECOVERY*.img"
TWRP: http://teamw.in/project/twrp2/225/
(If i got anything wrong pls correct me ^^)
KODEC.4 said:
Hi Erbat,
first of all it would be nice to get the an overview of your device and its versions, you can do this by doing the fastboot command "fastboot getvar all"
The most important version wich you already have is your OS 2.16.651.4, everything what you try to flash to your device if you want to return to stock should match this number or it will mostly fail.
So at this point forget about the Guide with official OTA updates and root access, because its for 4.16.401.10 and you should mainly focus on returning to stock without root to get new updates (easier)
I dont know how much knowledge you already have but just to mention:
Every OS with 2.16.651.4 is for your Sprint version, this means all of the files without 651 will lead in the wrong direction.
Later when you use a RUU ("official" files to return to stock firmware) or a nandroid backup (stock backup created by other users), the files and backups you will find have to match exactly to your OS Version 2.16.651.4 to work.
So at the moment you should focus on returning your device back to stock firmware and OS first, after that you can recieve official OTA updates from HTC :good:
The tutorials/threads you should focus on are mainly these two:
[GUIDE][S-ON] Restore your (European) HTC One M8 back to stock
[tutorial] How to get back on stock with TWRP Stock Nandroid Backups
Edit: You can't use your recovery, because if i understood this right you got TWRP (a custom recovery) before and might have corrupted/deleted it, simply flash the newest version of TWRP 2.8.7.0 with the fastboot command "fastboot flash recovery *NAME-OF_RECOVERY*.img"
TWRP: http://teamw.in/project/twrp2/225/
(If i got anything wrong pls correct me ^^)
Click to expand...
Click to collapse
OK I will try to do those things you've post here.
So tonight before I went to sleep the recovery says I don't have OS installed, that's so confusing because I don't know how install it again, I'm pretty noob so I (if you can do it) explain me a lot to do.
Yesterday already learn to use fastboot and the files and those things to do on the computer, I like to learn and more if is for recover my phone :laugh:
Erbat said:
OK I will try to do those things you've post here.
So tonight before I went to sleep the recovery says I don't have OS installed, that's so confusing because I don't know how install it again, I'm pretty noob so I (if you can do it) explain me a lot to do.
Yesterday already learn to use fastboot and the files and those things to do on the computer, I like to learn and more if is for recover my phone :laugh:
Click to expand...
Click to collapse
I know it looks pretty bad for a "noob" if he got no OS on his device and it won't boot anymore, but don't worry as long as you get your phone into fastboot mode you can fix everyting :fingers-crossed:
KODEC.4 said:
I know it looks pretty bad for a "noob" if he got no OS on his device and it won't boot anymore, but don't worry as long as you get your phone into fastboot mode you can fix everyting :fingers-crossed:
Click to expand...
Click to collapse
I can't do anything on cmd, my phone hasn't battery today and when I try to do fastboot getvar all say wating for your device and yesterday obviously don't say this
I need wait to 30%? I guess I have readed this before
Charge it up, restart everything (pc) and try again. You can use "fastboot devices" wich will list all devices connected in fastboot mode (ofc you must choose fastboot in bootloader menu first)
Next could be that you have HTC sync active witch might block something -> uninstall HTC sync
Otherwise you might have driver problems, if so, uninstall htc drivers and sync and reinstall HTC sync to get new drivers. -> uninstall sync only again (maybe reboot)
If all this does not work search for specific fastboot drivers for the M8 and try it with them
Erbat said:
I don't know what I did wrong on the process of re-stock the phone and now don't start.
only shows the white screen with HTC green logo.
I rememberd when I try to wipe I check all the options and "I swipe to wipe" later when the phone will be reboot
Click to expand...
Click to collapse
You should never wipe any of the partitions in the TWRP "Advanced" menu, unless you know exactly that they mean, and what the result will be (those options are called "Advanced" for good reason!). Even if the phone was properly working before, what you did was to wipe the OS (system partition) and make it stop working!
Further, you wiped any backup files and personal data that may have been on internal storage or the removable SD.
Simple rule when modding the phone: Do not experiment or make up your own solutions (will almost always fail and possibly make matter worse); and only do exactly what is directed to you from the proper guides, reputable "helpers", etc.
---------- Post added at 10:30 AM ---------- Previous post was at 10:27 AM ----------
Erbat said:
I screwed a lot
I don't know what I did wrong on the process of re-stock the phone and now don't start.
Click to expand...
Click to collapse
Can't help you, if you don't tell us exactly what you did: step by step, in specific detail, with links to the files you are trying to use, exact file names, etc.
If you don't tell us what you did, we can't see what you did wrong.
---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------
Erbat said:
I see the recovery mode once but when I try to do the next step (http://forum.xda-developers.com/showthread.php?t=2755657)
Click to expand...
Click to collapse
This guide has nothing to do with returning to stock, and is not for your version of the M8.
Nothing good can come of this; for what you are trying to do.
If you didn't know what you were doing, you should have stopped and asked. Learning and reading is good (and I applaud the effort), but don't do anything unless you are sure about it. In your case particular (due to your lack of knowledge/experience) I'd recommend not do anything unless we specifically direct you to. You seem to be going down the wrong roads, and just want to make sure we mitigate that now.
---------- Post added at 10:39 AM ---------- Previous post was at 10:32 AM ----------
Erbat said:
I can't do anything on cmd, my phone hasn't battery today and when I try to do fastboot getvar all say wating for your device and yesterday obviously don't say this
I need wait to 30%? I guess I have readed this before
Click to expand...
Click to collapse
The phone needs to be powered on, and in bootloader-fastboot mode for any fastboot commands to work.
Charge the phone for a few hours, and try again.
We need to get fastboot working, to move forward at all.

TWRP/Root on locked BL device?

i went to unlock my bootloader this morning but when i tried i got a "command not allowed" message from fastboot, i checked and for some reason its bootloader unlock status says a big fat "NO" (not sure why as the phone came direct from sony)
anyway ive managed to get temp root via the method in the huge thread here (well i got it once so far) but i cant seem to find much info aside from backup of DRM keys, there may well be info in teh main thread but its some 1000+ posts long and a lot to slog through in the hope of finding a sliver of info so i figured id ask what there is i can do at this point?
all i really want is to be able to install viper audio, i dont really care what rom its running, i was planning on l16 but im happy with anything that works, any help would be appreciated

Categories

Resources