Hi i have an HTC 10 Verizon
My phone has Unlocked Bootloader and S-Off
Can i change CID and MID to developer and Run the Developer Ruu?
Many people talk me that its imposible and if i will try my phone will go Bricked
Please help me
sure can, only drawback is that you have no VOLTE/Advanced Calling/Wifi Calling if you use a verizon sim. Also is a PITA to go back to verizon and have all of the features working again.
Instructions for converting VZW HTC 10 to US Unlocked
thank @andybones and @dottat
1. if you have advanced calling turned on for Verizon, I would recommend turning it off before continuing. In case you want to get back to Verizon, its a PITA to get VOLTE/advanced calling/wifi calling going again
2. reboot to download mode
3. open cmd prompt, and send fastboot oem writecid BS_US001
4. send fastboot reboot-bootloader
5. go back to download mode
6. verify your CID has changed, MID does not need to be changed, as the models are the same.
7. Download this RUU, and run it. I know its not the latest or nougat, but this is the only one I could get to install without giving me an error 150. You can try other US unlocked RUUs but I know this one works.
http://dl3.htc.com.s3.amazonaws.com...WL_M60_SENSE80GP_NA_Gen_Unlock_1.80.617.1.exe
8. Run the RUU, when successfully installed, reboot, and setup the phone. You wont have working Verizon radio at this point however (if you are using a Verizon based sim)
9. Using wifi, take OTAs until you hit nougat (this will take an hour or 2) so make sure you have time set aside to not have a phone to use.
10 Download the radio from this link, it is the latest radio from Verizon 1.85.605.8 (non nougat firmware) , unzip it, and put the image in your adb/fastboot directory
https://www.androidfilehost.com/?fid=313042859668276381
11. Once on nougat, reboot to bootloader. Open a command prompt and enter fastboot flash radio xxxxxxx.img (the x's denote the name of the img file inside of the zip above). Once successful, enter fastboot reboot and reboot to nougat.
12. Once in nougat, open dialer and enter *#*#4636#*#* and set the radio drop-down to LTE/CDMA.
13. At this point, you should see Verizon Wireless in the top left corner, and have working LTE/3g/1x. Note that once again, there will be no VOLTE/ADVANCED CALLING/WIFI CALLING and it is a PITA to get back down to VZW 1.85.605.8 and get all of this to work (not impossible, a PITA though)
14. Flash TWRP and supersu and whatever else you want at this point
aer0zer0 said:
Instructions for converting VZW HTC 10 to US Unlocked
thank @andybones and @dottat
1. if you have advanced calling turned on for Verizon, I would recommend turning it off before continuing. In case you want to get back to Verizon, its a PITA to get VOLTE/advanced calling/wifi calling going again
2. reboot to download mode
3. open cmd prompt, and send fastboot oem writecid BS_US001
4. send fastboot reboot-bootloader
5. go back to download mode
6. verify your CID has changed, MID does not need to be changed, as the models are the same.
7. Download this RUU, and run it. I know its not the latest or nougat, but this is the only one I could get to install without giving me an error 150. You can try other US unlocked RUUs but I know this one works.
http://dl3.htc.com.s3.amazonaws.com...WL_M60_SENSE80GP_NA_Gen_Unlock_1.80.617.1.exe
8. Run the RUU, when successfully installed, reboot, and setup the phone. You wont have working Verizon radio at this point however (if you are using a Verizon based sim)
9. Using wifi, take OTAs until you hit nougat (this will take an hour or 2) so make sure you have time set aside to not have a phone to use.
10 Download the radio from this link, it is the latest radio from Verizon 1.85.605.8 (non nougat firmware) , unzip it, and put the image in your adb/fastboot directory
https://www.androidfilehost.com/?fid=313042859668276381
11. Once on nougat, reboot to bootloader. Open a command prompt and enter fastboot flash radio xxxxxxx.img (the x's denote the name of the img file inside of the zip above). Once successful, enter fastboot reboot and reboot to nougat.
12. Once in nougat, open dialer and enter *#*#4636#*#* and set the radio drop-down to LTE/CDMA.
13. At this point, you should see Verizon Wireless in the top left corner, and have working LTE/3g/1x. Note that once again, there will be no VOLTE/ADVANCED CALLING/WIFI CALLING and it is a PITA to get back down to VZW 1.85.605.8 and get all of this to work (not impossible, a PITA though)
14. Flash TWRP and supersu and whatever else you want at this point
Click to expand...
Click to collapse
Could you also have a VZW radio zip package that can be stored on your SD card so one can just accept every OTA while on US unlocked and then after booting, move the radio zip to root of SD card and flash it via download mode?
And just repeat every OTA and use the newer VZW radio when available?
Sent from my HTC6545LVW using Tapatalk
richii0207 said:
Could you also have a VZW radio zip package that can be stored on your SD card so one can just accept every OTA while on US unlocked and then after booting, move the radio zip to root of SD card and flash it via download mode?
And just repeat every OTA and use the newer VZW radio when available?
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
I suppose its possible, however from the verizon end of things, where our current firmware sits at 1.85, the only us unlocked RUU i could get to flash was the 1.80 without getting an error. then there are something like 4 OTA's to take until you hit nougat. what i didnt try, was going right from 1.80 to 2.28 directly via RUU once i got US unlocked on the phone. That might even work.
However, until we get a TWRP flashable radio in a zip (im not a smart man), the radio has to be flashed via fastboot, so storing it on the externalSD doesnt do any good. With TWRP in good working order by captain and friends, that might be a more feasible possibility.
Ok, so I've got the latest FW working on nougat with verizon a bit simpler... Convert to us unlocked CID, Flash latest US unlocked firmware, flash the radio.img you linked, and flash whatever nougat rom you want. Manually select verizon APN under mobile settings, use *#*#4636#*#* and change to LTE/WCDMA/GSM/CDMA auto and toggle radio.
zylent said:
Ok, so I've got the latest FW working on nougat with verizon a bit simpler... Convert to us unlocked CID, Flash latest US unlocked firmware, flash the radio.img you linked, and flash whatever nougat rom you want. Manually select verizon APN under mobile settings, use *#*#4636#*#* and change to LTE/WCDMA/GSM/CDMA auto and toggle radio.
Click to expand...
Click to collapse
Basically the same thing I just typed, I spelled everything out in an easy to comprehend fashion....
richii0207 said:
Could you also have a VZW radio zip package that can be stored on your SD card so one can just accept every OTA while on US unlocked and then after booting, move the radio zip to root of SD card and flash it via download mode?
And just repeat every OTA and use the newer VZW radio when available?
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
aer0zer0 said:
I suppose its possible, however from the verizon end of things, where our current firmware sits at 1.85, the only us unlocked RUU i could get to flash was the 1.80 without getting an error. then there are something like 4 OTA's to take until you hit nougat. what i didnt try, was going right from 1.80 to 2.28 directly via RUU once i got US unlocked on the phone. That might even work.
However, until we get a TWRP flashable radio in a zip (im not a smart man), the radio has to be flashed via fastboot, so storing it on the externalSD doesnt do any good. With TWRP in good working order by captain and friends, that might be a more feasible possibility.
Click to expand...
Click to collapse
It may be possible to make a .zip to rename to 2PS6IMG.zip and will flash just Verizon 1.85x radio.img
aer0zer0 said:
sure can, only drawback is that you have no VOLTE/Advanced Calling/Wifi Calling if you use a verizon sim. Also is a PITA to go back to verizon and have all of the features working again.
Click to expand...
Click to collapse
Actually I went ahead and followed your guide except for flashing the Verizon radio since I'm using my phone on Metro PCS and after taking 5 OTAs I can confirm that I have WiFi calling and VOLTE located under the dialer settings. Just thought you like to know and thanks for the guide!
asj2583 said:
Actually I went ahead and followed your guide except for flashing the Verizon radio since I'm using my phone on Metro PCS and after taking 5 OTAs I can confirm that I have WiFi calling and VOLTE located under the dialer settings. Just thought you like to know and thanks for the guide!
Click to expand...
Click to collapse
That's great, if I could ever live somewhere, not in a gorge like I do now, I'd be on straight talk att. Now that your on nougat, you can just use the latest ruu's now since your there.
aer0zer0 said:
That's great, if I could ever live somewhere, not in a gorge like I do now, I'd be on straight talk att. Now that your on nougat, you can just use the latest ruu's now since your there.
Click to expand...
Click to collapse
I had a question and im sorry if this isnt the correct post to post this on but since i used sunshine to unlock my bootloader and s-off, changed cid and now running us unlocked firmware do i still have to unlock my bootloader thru the htc dev site cause im getting the htc screen with the red text when i flash twrp and then it reboots the phone and doesnt boot twrp. Already tried different images and same results....
Update: I went ahead and unlocked thru htc dev and reflashed twrp and that seemed to do the trick! Funny thing is that when i flashed the unlock token from htc dev i didnt get the normal screen asking if i want to unlock bootloader!
asj2583 said:
I had a question and im sorry if this isnt the correct post to post this on but since i used sunshine to unlock my bootloader and s-off, changed cid and now running us unlocked firmware do i still have to unlock my bootloader thru the htc dev site cause im getting the htc screen with the red text when i flash twrp and then it reboots the phone and doesnt boot twrp. Already tried different images and same results....
Update: I went ahead and unlocked thru htc dev and reflashed twrp and that seemed to do the trick! Funny thing is that when i flashed the unlock token from htc dev i didnt get the normal screen asking if i want to unlock bootloader!
Click to expand...
Click to collapse
Hmm, thats odd, i thought you were already bootloader unlocked and SOFF...there should have been no need to re-unlock via token. I assume you went to the TWRP thread and downloaded 3.0.3.0 TWRP unoffical from there. I have heard of MD5 not matching up and causing that issue.
aer0zer0 said:
10 Download the radio from this link, it is the latest radio from Verizon 1.85.605.8 (non nougat firmware) , unzip it, and put the image in your adb/fastboot directory
https://www.androidfilehost.com/?fid=313042859668276381
11. Once on nougat, reboot to bootloader. Open a command prompt and enter fastboot flash radio xxxxxxx.img (the x's denote the name of the img file inside of the zip above). Once successful, enter fastboot reboot and reboot to nougat.
12. Once in nougat, open dialer and enter *#*#4636#*#* and set the radio drop-down to LTE/CDMA.
13. At this point, you should see Verizon Wireless in the top left corner, and have working LTE/3g/1x. Note that once again, there will be no VOLTE/ADVANCED CALLING/WIFI CALLING and it is a PITA to get back down to VZW 1.85.605.8 and get all of this to work (not impossible, a PITA though)
14. Flash TWRP and supersu and whatever else you want at this point
Click to expand...
Click to collapse
this steps are need to use it with another carrier?
sorry for my bad english.
Correct. If you just plan on using it purely as unlocked.
aer0zer0 said:
Correct. If you just plan on using it purely as unlocked.
Click to expand...
Click to collapse
sorry i dont understand you
the last step are for verizon sims only?
chaddr18 said:
sorry i dont understand you
the last step are for verizon sims only?
Click to expand...
Click to collapse
Correct
aer0zer0 said:
Correct
Click to expand...
Click to collapse
thanks but i find out that that i have oem unlock Turn Off! and there is not oem unlock option in developer mode
chaddr18 said:
thanks but i find out that that i have oem unlock Turn Off! and there is not oem unlock option in developer mode
Click to expand...
Click to collapse
I'm not following your problem?? If your already bootloader unlocked, you don't need to do it again
aer0zer0 said:
I'm not following your problem?? If your already bootloader unlocked, you don't need to do it again
Click to expand...
Click to collapse
i cant unlock bootloader i dont have oem unlock option
aer0zer0 said:
I'm not following your problem?? If your already bootloader unlocked, you don't need to do it again
Click to expand...
Click to collapse
Are you already SOFF?
Related
Hello all, I used the htc unlock method, but I am not able to flash a different radio version.
Does anyone know how to do that?
(Just booting into bootloader does not do the trick like it would normal unlock methods)
Thanks.
Anyone?
Sent from my PG86100 using XDA App
have you tried the commands
adb reboot bootloader
fastboot boot recovery.img
and flashing the radios from fastboot? or FlashimageGUI (which probably will not work for radios)
I have been wondering this myself. I have not heard of any methods that have come up to allow this recently. Same thing goes for splash images as I havent seen any method for those.
I have an idea of how it may be possible though. Perhaps someone else with a bit more knowledge can chime in to let us know if it is possible or not.
Anyhow.
Being officially unlocked I don't believe that ROOT is an issue like it is on an unofficial method. I know typically you would NOT accept an OTA to prevent the loss of ROOT. However, being an officially unlocked device, I am not sure if it matters.
I know that when I unlocked my device I had to manually unlock it, then I installed my recovery, then I simply flashed SU to it. My thought is that you can take the OTA. If the OTA doesn't work, you may have to re-lock the device, then run the OTA. But I believe the OTA would be safe. Once OTA completed, then flash your unlock token again, put recovery back on, then flash SU again.
Or I believe you could also wait for the new RUU instead of an OTA. Put on stock ROM, re-lock, run RUU, re-unlock, install recovery, flash SU.
The problem is that you may not be able to flash back to the previous radio once you are done.
Any thoughts on this?
UPDATE: I recently (like two minutes ago) learned that an RUU will not update a radio. I was under the impression that they did. Since it will not, I guess the RUU method will not work. Still curious about the OTA method though.
From the HTCDev Q and A:
HTCDev said:
Why is my security still on (S-On) after I have unlocked my bootloader?
Your device is shipped with Security on (S-ON) to protect your system software configuration (such as the bootloader, radio, boot, recovery, system and others). After you have unlocked the bootloader, however, you will have lifted the restrictions on boot, recovery and system. This means you can customize boot, recovery and system images on your phone as you desire. You can easily see that you have successfully unlocked the bootloader by looking at the top of the screen when entering the bootloader screen. Security is left on to protect things like the radio, and SIM lock.
Click to expand...
Click to collapse
yousefak said:
From the HTCDev Q and A:
Click to expand...
Click to collapse
Well, yeah. The S stays on to protect the radio.
But the S would be on regardless if you never rooted to begin with, but an OTA would allow the radio to update. So, my thought is that you can potentially take an OTA with the HTC unlock method and get the new radio.
If it were me, I would save my titanium file to my PC (just as a precaution), I would re-lock my device using fastboot oem lock, then I would run the RUU that matches my current software version. This would return me to stock/unrooted. At this point you should be able to accept an OTA. The OTA updates your radio/software/etc. Once you update, flash the unlock token again, then flash the superuser binary back onto the phone. Now, this would be contingent that HTC doesn't go back on their word and they dont push an OTA that prevents you from unlocking the phone.
Now, Ill admit I am not a developer, so I am not an expert, but it is my understanding that once it is unlocked putting root on the phone is pretty straight forward. You don't have to come up with a root method such as revolutionary, etc. It should simply allow Superuser because it is unlocked. If this is not the case, then Ill admit that my thought process is flawed. However, if it is the case, then why not return to stock, take an OTA, unlock, re-root, use titanium? Like I said, may not be able to return to previous radio, but why would you anyhow?
mildlydisturbed said:
have you tried the commands
adb reboot bootloader
fastboot boot recovery.img
and flashing the radios from fastboot?
Click to expand...
Click to collapse
Can someone tell me how exactly to accomplish the above?
I ran these commands and the it said "Installing update..." but the radio remains the same.
Thanks again.
I am trying to unroot my htc amaze from telus canada. I have followed the instructions using the all-in-one kit, and when I went to relock my bootloader, I got stuck in the fastboot screen, and when I tried to reboot, it kept getting me back to the same screen. I was able to unlock the bootloader again, and now when I try to access wi-fi, it says error under the wi-fi button in settings!
how do I fix this?
gnarkilljboy said:
I am trying to unroot my htc amaze from telus canada. I have followed the instructions using the all-in-one kit, and when I went to relock my bootloader, I got stuck in the fastboot screen, and when I tried to reboot, it kept getting me back to the same screen. I was able to unlock the bootloader again, and now when I try to access wi-fi, it says error under the wi-fi button in settings!
how do I fix this?
Click to expand...
Click to collapse
If you have a back up, restore it, but your best call is to download the stock zip file, place it on your sd card root, rename it PH85IMG and boot into the bootloader, should ask you if you wanna update, just say yes and let it restore everything to stock, then relock the bootloader, though locking the bootloader isn't exactly necessary.
Ok, where do I find the stock rom? also, now when I slide the cirle to unlock my phone, a windows pops up saying sorry, HTC Sense has stopped unexpectedly, would you like to tell htc?
gnarkilljboy said:
Ok, where do I find the stock rom? also, now when I slide the cirle to unlock my phone, a windows pops up saying sorry, HTC Sense has stopped unexpectedly, would you like to tell htc?
Click to expand...
Click to collapse
Here is the stock file: http://d-h.st/qah
After installing that, everything will be fine.
Thank you...will do after I nap. Just to make sure, what is the root dir?
gnarkilljboy said:
Thank you...will do after I nap. Just to make sure, what is the root dir?
Click to expand...
Click to collapse
Just put it directly on the sd card, not in any folders, rename the file to PH85IMG.
Thanks for all the help. ok, so I have done that, and rebooted into bootloader. It shows a bar at the side that looks like it is installing somehing, or loading, then I reboot back to my phone, and I am still getting the same error.
gnarkilljboy said:
Thanks for all the help. ok, so I have done that, and rebooted into bootloader. It shows a bar at the side that looks like it is installing somehing, or loading, then I reboot back to my phone, and I am still getting the same error.
Click to expand...
Click to collapse
After the bar loads it just goes back into the phone? No option to install update?
No, there is no option to install. It just goes back to the main fastboot screen. I changed it to a zip file, because it was an exe file, and it didn't see it. The reason I want to unroot is to update to ics!
*frustrated.
If Dark Nightmare gave you an RUU for T-Mobile then it won't work. Be sure its a Telus RUU. Otherwise you need to do a lot more leg work.
Edit...NVM he gave you the right link. Is you phone originally a Telus Phone?
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Lol I pay attention.
The question is, did you try the ICS leak by any chance?
Yes, it's a telus phone. I have not tried the ics yet, but that's what I want to install! Lol is there a link for the leaked ics?
Do you think it might be because I used Debloater and Debloater Remover? (was just following the instructions). no matter what I do, I keep getting that error.
Ok, so, I was able to fix that error that kept popping up!
Couple of quick questions before this one is locked up:
Do I need to re-root my phone, if I followed all those steps in the all in one tool kit?
And
Can someone post a link here on how I can install the latest version of ICS on my phone?
Thanks for all the help!
gnarkilljboy said:
Ok, so, I was able to fix that error that kept popping up!
Couple of quick questions before this one is locked up:
Do I need to re-root my phone, if I followed all those steps in the all in one tool kit?
And
Can someone post a link here on how I can install the latest version of ICS on my phone?
Thanks for all the help!
Click to expand...
Click to collapse
Unless you S-Off, there's no way you're upgrading to ICS until Telus release their version.
I am also a Telus Amaze user.
In this order, you need to:
1)Unlock your bootloader from HTCdev
2) Use Juopunutbear's S-off hack.
3) Flash the T-mobile RUU
4) Flash the ICS rom
5) Insert your SIM, connect to telus under mobile networks, and enter Telus' APN settings.
Be aware though, I can't seem to get MMS to send properly. Anyone have any ideas?
steamdnt said:
I am also a Telus Amaze user.
In this order, you need to:
1)Unlock your bootloader from HTCdev
2) Use Juopunutbear's S-off hack.
3) Flash the T-mobile RUU
4) Flash the ICS rom
5) Insert your SIM, connect to telus under mobile networks, and enter Telus' APN settings.
Be aware though, I can't seem to get MMS to send properly. Anyone have any ideas?
Click to expand...
Click to collapse
Did you remember to supercid before flashing the tmobile rom? And check the apn settings thread for the apn settings just in case they were incorrect, though in my experience the carrier pushes the settings no matter what device you're using.
I did Super-Cid the device. At least, I wrote 11111111 to CID.
APN is also correct, I set it up manually and my data connection and texting work just fine.
Could this be at all related to Telus using HSPA, while the TMOUS rom only has options to select WCDMA or GSM?
Thanks for the info on installing ICS. I think I will do it once we find out how to get mms working.
Don't hold your breath on the T-mobile version. I'm waiting for the Telus OTA so I can rip it apart and figure out what is going on.
In addition, anyone know of any risks for the few of us Telus users that are running the TMOUS rom? It shouldn't detect Telus' OTA, right?
Tmo using HSPA+ as well, the network set ups are practically the same, Try checking your mms settings in the app itself.
I've had a lot of trouble upgrading to KitKat. After attempting to flash different image files for stock recovery/boot/system, I found it impossible to completely unroot the phone using the instructions posted because the phone kept re-rooting itself. Finally, I S-offed, wrote superCID, used the Telus RUU, applied the OTA downloaded to the phone, changed the CID back to GLOBA001 (my carrier is WindMobile). And finally! I know I relocked and unlocked the bootloader somewhere in the process, but I can't quite remember when.
Now, before I even think of re-rooting the phone or installing a custom recovery, I'd like to create a backup of the stock boot, recovery, and system. I tried running
Code:
fastboot boot openrecovery-twrp-2.7.1.1-zaracl.img
using the special KitKat TWRP. There's a message about boot.img being downloaded successfully but the phone reboots to a black screen.
I know that TWRP 2.7.1.0 downloaded from their website worked fine on my phone before I ran the RUU . So I'm not sure that the new TWRP is incompatible with my phone.
If I wanted to use adb instead, I'd need to root the phone before being able to pull the stock recovery, boot, and system images using adb shell. If I have to resort to rooting, is there any way to do so without flashing a custom recovery first? If there is, I might be able to unroot the phone afterward and make it stick. (Delete the supersu apk and su binary, right?)
I remember that the first time my phone attempted to download and apply the OTA automatically, my phone wiped itself. It was a lot of hard work to get it back to a usable state, but it was my own fault for not having a proper backup. I'd like to avoid making that mistake again, and have a stock backup handy on my computer in case there are carrier updates for my phone in the future.
To re-iterate, possible to back up stock everything without root? If not, possible to root without installing custom recovery?
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
Locking the bootloader won't do anything, it's only unlocking using the htcdev token that causes the data wipe. So if you haven't unlocked using the htcdev method since running the RUU you will still have the 2 - 3 apps.
I don't know if the /data/preload/ folder is a requirement for a successful OTA update or not but I checked inside my OTA zip for my phone and it does include the 3 items stored there for the VM variant.
The unlock was AFTER the RUU. I ran the RUU, then used the OTA to upgrade to KitKat, then unlocked the bootloader again. However, I didn't notice any apps disappearing and the OTA zip for Wind also has a /data/preload folder.
*Shrugs* Seems good enough to me. TWRP, here I come!
needing wind stock stuck with wind awsy amd wont connect
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
jayjsteez said:
I have an unlocked desire 601 it finds only wind away I'm trying to get a backup of the stock Rom to flash it does anyone k ow if there any around or even a back up I can use to try to get my phone working on wind home
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2804427
needing help for s-off
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
---------- Post added at 11:29 PM ---------- Previous post was at 11:16 PM ----------
EveKnight75 said:
I had already re-locked the bootloader using the HTCdev method after the upgrade and before starting the thread. Do you think the potential loss of apps would cause any future OTAs to fail? If so, I don't mind re-doing the RUU (no important data on the phone right now). If not, I'll proceed with flashing TWRP.
Thanks for the tip on the alternate unlock method. I'll use that method the next time I need to re-unlock the bootloader.
Click to expand...
Click to collapse
hey i have unlocked desire 601 but only says wind away and wont connect ive knoticed the wind version is the same as the other versions but im wondering do i need the wind rom in order for it to pick up the wind home i cant seem to find anywhere online the wind rom and everytime i try to s-off it saysfailed and ive followed everything is there any insite you could give me to help me with this issue if its fixable again my phone says wind away but wont connect to it and i need to get it working as its my only device and carrier i use thx
-Duir- said:
You can no longer boot into a custom recovery, you have to actually flash it.
As far as having the stock recovery and boot, those are actually inside the OTA so you can pull it from there.
Since you'll have the stock recovery already, you can flash TWRP and use that to backup boot and system.
When you need to go stock, just use TWRP to restore your backup and then manually flash the stock recovery.
Since you made the device S-OFF, I recommend that if you need to lock/unlock the bootloader that you use the commands in this thread versus using the htcdev method as that wipes the /data/preload/ folder (as part of its normal /data wipe) which includes a few stock apps.
Click to expand...
Click to collapse
I don't understand how you can pull the stock recovery from the OTA. I thought OTA's are immediately installed, instead of stored untill you want to install it? So, how do you backup the stock recovery?
It is saved until you want to install. When it go finishes Downloading, just choose install later. And you will be able to copy it into other storage devices and extract files and what not. I'm not sure if it stores in internal or external I'm 80% sure external sd if you have one.
Sent from my HTC0P4E1 using XDA Free mobile app
I have an at&t branded phone. I recently switched to T-Mobile and would like to get T-Mobile ROM installed on it.
I started with a phone which was NOT rooted, had stock AT&T rom.
I have done the following so far:
*
Unlocked my boot loader - worked flawlessly
Installed TWRP - worked flawlessy
Attempted to install Super SU - I think it worked
Attempted to install a T-Mobile ROM - Getting a "Error flashing zip" error
I download official T-Mobile ROM installer from HTC website. I let the installer run until I saw "Rom.zip" in the temp folder.
A website on google told me that i can use this file to flash my phone. I did have some doubts about this file as I am able to unzip only half the file's contents using winrar. But anyways, I went ahead and used this ROM file.
I rebooted my phone in Recovery mode (TWRP). I clicked on Install and selected rom.zip from my SD Card. When I attempt to install rom.zip, I received following messages:
Installing '/external_sd/tmobile_rom.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Error flashing zip 'external_sd/tmobile_rom.zip'
Updating partition details...
....done
I tried a few different ROM's I found on the internet with the same error message.
So now I am stuck with no OS on the phone. I can only go to bootloader or TWRP.
If someone can suggest a more appropriate ROM file, I can give that a try.
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
I have s-on. Yes, I want the full T-Mobile firmware...mixing up my terms as I am new to this.
Since I don't have an OS right now, I will first try to restore to AT&T firmware by using the stock RUU on htc website. If that's successful, I will proceed with rest of the steps.
redpoint73 said:
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
Click to expand...
Click to collapse
So I was able to get back to AT&T firmware using below steps:
booted my phone to boot fastboot mode
I re-locked my bootloader using following command: fastboot oem lock
I download the AT&T HTC One M8 Stock RUU
Ran the installation until my firmware was flashed again
I am just so happy to have a phone that works now. I will continue soon with the rest of your instructions to get T-Mobile firmware.
redpoint73 said:
S-on or s-off?
I don't think you just want the T-Mob ROM, I think you also want the T-Mobile firmware, including the T-Mob radios. At least, that would probably be my recommendation.
That being the case, the best way to do that is probably run the entire T-Mobile RUU (not just the ROM.zip). But that would also require you to change to the T-Mob CID and MID.
S-off is required for that (which is why I asked) so if you are still s-on, you will need to get the phone up and running again (AT&T RUU may be the easiest way - relock bootloader first) than run sunshine s-off.
So in short, what I would suggest:
1) If s-on, get an OS back on the phone, so you can boot normally
2) (again, if still s-on) run sunshine to get s-off
3) Change to T-Mobile CID and MID
4) Run T-Mobile RUU
5) Beer
This gets your phone to a stock T-Mobile software state. Essentially a T-Mobile M8, in everything except the stupid AT&T planet logo on the back of the phone. This means you will even get any future OTAs meant of the T-Mobile M8.
I'm gathering from your post this is what you want (stock T-Mob setup). If not, you need to specify what exactly you are trying to do.
Click to expand...
Click to collapse
After spending few hours, I have successfully installed T-Mobile firmware on my AT&T M8.
I pretty much followed your instructions. For anyone else looking to this this, here are the complete instructions.
Unlocked boot loader
Installed TWRP recovery
Installed Super User
Changed to T-Mobile CID
Changed to T-Mobile MID
Used sunshine to get Security Off (paid $25)
Ran official HTC M8 T-Mobile RUU
And now I am enjoying a beer
Thanks redpoint73 for your helpful reply.
deepak528 said:
Unlocked boot loader
Installed TWRP recovery
Installed Super User
Changed to T-Mobile CID
Changed to T-Mobile MID
Used sunshine to get Security Off (paid $25)
Ran official HTC M8 T-Mobile RUU
Click to expand...
Click to collapse
I think this is slightly out of sequence. You need to s-off before changing CID and MID. CID and MID cannot be modified with s-on.
wouldnt a simple rom without the firmware provide wifi calling?
PunishedSnake said:
wouldnt a simple rom without the firmware provide wifi calling?
Click to expand...
Click to collapse
Yes. But this thread is from last May, when I think having the 3G AWS band was more of an issue than it is now.
redpoint73 said:
Yes. But this thread is from last May, when I think having the 3G AWS band was more of an issue than it is now.
Click to expand...
Click to collapse
Agreed
Software up to date issue
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
Android version 5.0.2
HTC Sense Version 6.0
Software Number 4.28.502.1
HTC SDK API Level
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
I believe this phone was originally purchased from ATT on May of 2016 if it makes any difference , figured I post it. since it could be a newer version of HTC M8.
Also is there a way to back up my current stock rom, without Rooting phone ? Thanks for all your help.
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
My responses below in red font:
ELEVO said:
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
That is correct, the AT&t version (and most US versions) can only OTA update if connected to the proper branded carrier (AT&T in this case). Therefore, the RUU is your best option to update.
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
You can. But you need to flash the 6.20.502.5 firmware first, before you can flash the RUU. See instructions to flash the firmware here: https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
Then run the RUU. Keep in mind, that RUU will wipe the phone. So backup your data to an off-phone location (cloud, computer, etc.) before RUU.
Also is there a way to back up my current stock rom, without Rooting phone ? The current Lollipop ROM? No, there will be no way to revert to LP by official means, once you RUU to Marshmallow. I doubt you will find the need or desire to "downgrade" to obsolete LP version. If for some reason you did want to, there are options, but would require unlocking the bootloader (to install custom recovery and flash a Lollipop ROM), or s-off (which would allow you to "downgrade" by RUU - which is not allowed with s-on).
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
You are misunderstanding a couple things:
1) s-off is not a setting in Developer Options. s-off can only be obtained with sunshine app ($25)
2) You don't need s-off to root this device. Simply unlock the bootloader, install TWRP, and flash SuperSU to root
Click to expand...
Click to collapse
Detailed
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
Thanks for the detailed reply, really helpful and greatly appreciated :good:
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device? or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Again, my responses in red font:
ELEVO said:
Thanks for the detailed reply, really helpful and greatly appreciated :good:
You're welcome. Always happy to help!
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device?
You can't flash the Dev Edition RUU with s-on. Even though the versions are very similar (same model ID - MID) the two versions have different carrier ID (CID). Wrong carrier ID will make the Dev Ed RUU fail, by definition. And the only way to change CID is with s-off. Further, its not really necessary to flash the Dev Ed RUU (and not worth spending money of s-off) to accomplish what you want (see more below)
or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Its correct that the AT&T stock ROM disables tethering. Flashing most custom ROMs (or the Dev Ed ROM) will enable tethering - as well as remove annoying AT&T branding and bloat apps. Flashing the Dev Ed RUU is not necessary to accomplish this.
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
You need to relock the bootloader in order to flash firmware and RUU (command: fastboot oem lock). Once the RUU is complete, the phone will be on a fully stock "factory" image. So you will be unrooted. You will also be back to stock recovery (no longer have TWRP installed). From there, what you want to do:
1) Unlock the bootloader again. Either use the same unlock bin code you used to unlock BL before. Or get a new code from HTCDev.com
2) Flash TWRP back to the phone with fastboot. TWRP 3.0.2 is recommended for compatibility with MM firmware.
3) Flash the desired custom ROM. The custom ROM will be rooted (if you flash the Dev Ed ROM, you can select root in the AROMA installer).
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Always good to make backups. Although be aware, that RUU will wipe the phone, including internal storage. So if you picked internal storage as your backup location, you'll want to move/copy to another location (removable SD is okay, otherwise to computer or cloud).
Also note that restoring app data (as well as call logs, SMS) using Titanium, after RUU or ROM flash should be okay. But don't restore any system data, as this can cause problems.
Click to expand...
Click to collapse
redpoint73 said:
Again, my responses in red font:
Click to expand...
Click to collapse
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Bricked ?
ELEVO said:
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Click to expand...
Click to collapse
I think i may have bricked my phone? I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Phone would not reboot into anything but dark screen. even when i restarted it with power button. the only thing that worked for me, was Holding Down Power/Volume and quickly hit the volume down button before device would vibrate to reboot, that took me into recovery. Below is what i see in Recovery.
Phone now has new software
***RELOCKED***
m8_UL_CA PVT SHIP S-ON
HBOOT-3.1.0.0000
RADIO-4.0 [email protected]
OpenDSP-V56.2.2-00593-M8974_FO.0126
0S-6.20.502.5
eMMC-boot 2048MB
APR 14 2016,19:39:46.0
HBOOT
<Vol UP> to previous item
<Vol Down> to next item
<Power> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
I was able to run and "IMAGE CRC" via boot loader. it gave me alot of numbers after calculating. not sure if that is a good sign ?
Things I've tried in Recovery.
1. Recovery goes back to black screen.
2. SHOW BARCODE Works- 3 bar codes showed up.
3. Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
4. Tried to do a factory reset and tries to do it, then a black phone pops up on screen with green arrow sgoing in circles for like 10 seconds. then reboots to dark screen.
Please Help :crying: Thanks
Can anyone help me with this? I bought the phone with me on vacation and now using an HTC Developer Edition that the button down doesn't work and Volume down button us sunk in But at least i have my phone with all my contacts and apps , For now ?
I would like to know if i can unbrick my other HTC . Thanks.
Late in responding, as I was on work travel myself, and not on XDA for over a week.
ELEVO said:
I think i may have bricked my phone?
Click to expand...
Click to collapse
It's basically impossible for you to do anything with an s-on M8 that will actually brick it. That is the good thing about s-on.
ELEVO said:
I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Click to expand...
Click to collapse
I think you only flashed the firmware.zip and not the RUU. Based on the condition here, and your other thread you created here: https://forum.xda-developers.com/htc-one-m8/help/htc-one-e-m8-fastboot-issues-t3757628
I clearly described above to flash the firmware.zip then the RUU. They are 2 completely different things. Firmware is about 80 MB and only contains hboot, radio, and a few other things. RUU is a full image that is 1.5 GB.
No boot after flashing signed firmware is normal, as it expects the RUU to be run afterwards.
ELEVO said:
Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
Click to expand...
Click to collapse
adb doesn't work in fastboot mode. Only fastboot commands will work in fastboot mode. You can only use adb when booted to OS (not an option for you, obviously) or alternately in custom recovery TWRP. So what you describe (adb not working) is normal and expected.
However, fastboot is enough to get the phone working from the described condition.