I have an HTC One M7 Google Play Edition running Jellybean (4.2.2). This lags well behind the current version of android for this version of the phone. Unfortunately, I am unable to receive an OTA update (everytime I check, I get a message stating that my phone is up to date). Is there anything I can do to force an OTA update short of rooting the device and manually installing the updates? I am currently on a BYOD plan with T-Mobile if that matters at all.
nocipher said:
I have an HTC One M7 Google Play Edition running Jellybean (4.2.2). This lags well behind the current version of android for this version of the phone. Unfortunately, I am unable to receive an OTA update (everytime I check, I get a message stating that my phone is up to date). Is there anything I can do to force an OTA update short of rooting the device and manually installing the updates? I am currently on a BYOD plan with T-Mobile if that matters at all.
Click to expand...
Click to collapse
Can you please post the output of "fastboot getvar all" (remove your imei and serialno information before posting).
alray said:
Can you please post the output of "fastboot getvar all" (remove your imei and serialno information before posting).
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.1700.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.176s
nocipher said:
C:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.1700.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4062mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.176s
Click to expand...
Click to collapse
Everything looks good. Is your bootloader locked/unlock/relocked?
You could use a RUU to update your phone, flashing a ruu will wipe everything from the phone, like if it was brand new. Backup your important files before.
If you ever considered S-OFF for your phone, better to do it before updating using rumrunner exploit for free. If you update to the latest version, you will need to use Sunshine s-off which cost 25$.
alray said:
Everything looks good. Is your bootloader locked/unlock/relocked?
You could use a RUU to update your phone, flashing a ruu will wipe everything from the phone, like if it was brand new. Backup your important files before.
If you ever considered S-OFF for your phone, better to do it before updating using rumrunner exploit for free. If you update to the latest version, you will need to use Sunshine s-off which cost 25$.
Click to expand...
Click to collapse
My bootloader is locked. (I pulled the phone out of the unopened box just yesterday).
I tried to get S-OFF using rumrunner so I could update using the HBOOT recovery feature, but there was an issue with my phone not being rooted or something along those lines. Maybe the failure was due to a locked bootloader? (I'm new to all of this.)
If I set my phone to S-OFF, would it be better to just manually apply the updates or use an RUU?
nocipher said:
My bootloader is locked. (I pulled the phone out of the unopened box just yesterday).
I tried to get S-OFF using rumrunner so I could update using the HBOOT recovery feature, but there was an issue with my phone not being rooted or something along those lines. Maybe the failure was due to a locked bootloader? (I'm new to all of this.)
If I set my phone to S-OFF, would it be better to just manually apply the updates or use an RUU?
Click to expand...
Click to collapse
Achieving s-off requires root. Root requires a custom recovery, Custom recovery requires an unlocked bootloader.
Unlocking the bootloader will void your warranty if you have one.
S-OFF is not something everyone needs but its very useful when you have to flash files in case the phone is somehow bricked. If you are not planning to flash custom roms or any other custom files I would recommend staying S-ON. In the worst case, you'll have to pay 25$ for s-off if you really need it later.
better to use the RUU to update the phone imo, much faster than applying all ota updates from your current version. The only downside of using a ruu is that it will wipe your phone data (which shouldn't be a big issue since your phone is 1 day old). Much convenient to update using ota update after so you'll not have to deal with the wipe each time.
alray said:
Achieving s-off requires root. Root requires a custom recovery, Custom recovery requires an unlocked bootloader.
Unlocking the bootloader will void your warranty if you have one.
S-OFF is not something everyone needs but its very useful when you have to flash files in case the phone is somehow bricked. If you are not planning to flash custom roms or any other custom files I would recommend staying S-ON. In the worst case, you'll have to pay 25$ for s-off if you really need it later.
better to use the RUU to update the phone imo, much faster than applying all ota updates from your current version. The only downside of using a ruu is that it will wipe your phone data (which shouldn't be a big issue since your phone is 1 day old). Much convenient to update using ota update after so you'll not have to deal with the wipe each time.
Click to expand...
Click to collapse
I am having trouble finding an RUU for the google play edition. I've been googling and searching the forums for a while now, but most of the RUU's and ROMs I find are for the Sense version. Would the RUU here: http://forum.xda-developers.com/showthread.php?t=2358781 work?
nocipher said:
I am having trouble finding an RUU for the google play edition. I've been googling and searching the forums for a while now, but most of the RUU's and ROMs I find are for the Sense version. Would the RUU here: http://forum.xda-developers.com/showthread.php?t=2358781 work?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B17smFr95pleX29Wamg2c3pRWTQ/view?pli=1
Thanks for the all the help! I used the RUU to update to 5.0.1. That, unfortunately, did not allow an OTA update directly, but I did manage to sideload the 5.1 update via abd.
Related
Hello friends. First of all, I apologize if I am not very clear, but I have little knowledge of English, and to be faster I'll use a translator...
Since about a week ago, my HTC One Developer Edition is showing me errors with WiFi and Bluetooth. These are off steadily even when in use. At first I thought it was a failure of the last installed ROM (ARHD 40.1), but I've tried others such as CM11 without installing any mod and restore my latest nandroid backup, but I have had the same result.
Apart from changing the ROM all I remember doing is to update the firmware, so yesterday I upgraded to the new firmware version to see if solved, but still follows the failure. Do not think it's a hardware failure because the mobile is not second hand, has not suffered any drop and was always working perfectly, so I ask your help and attached the information that shows the phone using fastboot getvar all command if serving them for a diagnosis. Thanks in advance.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3993mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
You are Soff. Why not reflash official dev ruu?
SaHiLzZ said:
You are Soff. Why not reflash official dev ruu?
Click to expand...
Click to collapse
What should I use? Because I see several for Dev Edition on this list:
[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads
[email protected] said:
What should I use? Because I see several for Dev Edition on this list:
[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads
Click to expand...
Click to collapse
Either one will do, they're just slightly different version numbers 1.29.1540.16 and 1.29.1540.3, might as well go for the .16. You'll have to download from here: http://www.htc1guru.com/downloads/ruu-file-downloads/
then you can follow my guide (in my signature), because you need to downgrade hboot to 1.44 separately first, before you can run the RUU. (just the first part about downgrading hboot, the rest of the guide is for people who want to return the phone for warranty)
Also keep S-Off, do NOT go S-On!!!
nkk71 said:
Either one will do, they're just slightly different version numbers 1.29.1540.16 and 1.29.1540.3, might as well go for the .16. You'll have to download from here: http://www.htc1guru.com/downloads/ruu-file-downloads/
then you can follow my guide (in my signature), because you need to downgrade hboot to 1.44 separately first, before you can run the RUU. (just the first part about downgrading hboot, the rest of the guide is for people who want to return the phone for warranty)
Also keep S-Off, do NOT go S-On!!!
Click to expand...
Click to collapse
Well, thank you very much. Be right back after process.
SaHiLzZ said:
You are Soff. Why not reflash official dev ruu?
Click to expand...
Click to collapse
nkk71 said:
Either one will do, they're just slightly different version numbers 1.29.1540.16 and 1.29.1540.3, might as well go for the .16. You'll have to download from here: http://www.htc1guru.com/downloads/ruu-file-downloads/
then you can follow my guide (in my signature), because you need to downgrade hboot to 1.44 separately first, before you can run the RUU. (just the first part about downgrading hboot, the rest of the guide is for people who want to return the phone for warranty)
Also keep S-Off, do NOT go S-On!!!
Click to expand...
Click to collapse
I downgrade to hboot 1.44 and reflash the official ruu (RUU M7 JB UL 50 BrightstarUS WWE 1.29.1540.16), but still blinking on and off wifi and bluetooth.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.16
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3994mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.065s
Time to call HTC for warranty support. No other ideas.
Hey this is off topic but SaHiLzZ, is your name Sahil?
Sent from my HTC_PN071 using Tapatalk
SaHiLzZ said:
Time to call HTC for warranty support. No other ideas.
Click to expand...
Click to collapse
Well, I bought this phone in the United States.... I live in Dominican Republic...
@SaHiLzZ @nkk71 I was using the bluetooth headphones faultlessly for more than 4 hours, and when I get home WiFi even longer, so I know that still work but are turned on and off when it wants ...
[email protected] said:
@SaHiLzZ @nkk71 I was using the bluetooth headphones faultlessly for more than 4 hours, and when I get home WiFi even longer, so I know that still work but are turned on and off when it wants ...
Click to expand...
Click to collapse
did u try changing some of the advanced settings i mentioned?
nkk71 said:
did u try changing some of the advanced settings i mentioned?
Click to expand...
Click to collapse
Yes, but I don't see changes. (Later, I change the "Keep WiFi on during idle" to Always), but just keeps running and then switching off when it want, and when it goes off, just says "activating", infinite loop until I restart.. Same for bluetooth.
SaHiLzZ said:
Time to call HTC for warranty support. No other ideas.
Click to expand...
Click to collapse
@nkk71
Well, without ideas, I sent the phone to HTC America, for guarantee. I had to pay $ 70 shipping because I live in Dominican Republic (No HTC), but after 15 days I received my phone in perfect working (they did not even scratch), and by the way, apparently they changed my camera ... It's not purple! :laugh:
Thanks for all your help friends. :highfive:
I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Nic2112 said:
I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Click to expand...
Click to collapse
post output of "fastboot getvar all"
remove S/N & IMEI before posting
kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Nic2112 said:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Click to expand...
Click to collapse
your previous CID was BM_001, right?
look into nkk71 SuperGUIDE in my signature
kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
kamilmirza said:
your previous CID was BM_001, right?
Click to expand...
Click to collapse
I believe so, yes.
Nic2112 said:
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
Click to expand...
Click to collapse
yes sadly there is only nandroid of BM right now
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Nic2112 said:
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Click to expand...
Click to collapse
yeah maybe that could be the problem
why not try the nandroid and see how it goes?
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Oh Wow, there is a guide for Canadian HTC One, didn't know that!
Are you sure that a Telus RUU will work on a Bell phone? They use different networks I think
SaHiLzZ said:
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Click to expand...
Click to collapse
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
SaHiLzZ said:
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
Click to expand...
Click to collapse
I know how to go back to 1.44, I have done that before.
So what you are saying is that if I have the nandroid installed, and stock recovery from your thread, the phone will detect the OTA? It should install no problem because it will be a standard recovery.
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
SaHiLzZ said:
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
Click to expand...
Click to collapse
Thatk you, one last question before I try this, the OTA, will it replace the radios and firmware as well to Bell's? I guess it depends on what they put in the OTA.
Yes, OTA generally contain new OS, HBOOT, Recovery, and RADIO, practically a full RUU replacement, but not all. IF you are S-ON, you will need to lock bootloader after loading stock recovery, but if you are S-OFF, that doesnt matter, and I will suggest to stay S-OFF!
Please help
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
ginuwine96 said:
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
Click to expand...
Click to collapse
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Not sure what file I need
majmoz said:
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Click to expand...
Click to collapse
This is my phones Info I am not sure what file to use for it ?
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
ginuwine96 said:
This is my phones Info I am not sure what file to use for it ?
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
Click to expand...
Click to collapse
If you're going to follow my guide, you'll need to use CWM method, using this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-bm___001-1-29-666-5-zip/
make sure to have read it once or twice, to be sure you're comfortable with the process
I just bought an HTC One which is unlocked but it shows the O2 bootscreen. I wish to debrand the phone but will that lock the phone? I am not sure how the phone was unlocked by the previous user. Thanks
Klejdi90 said:
I just bought an HTC One which is unlocked but it shows the O2 bootscreen. I wish to debrand the phone but will that lock the phone? I am not sure how the phone was unlocked by the previous user. Thanks
Click to expand...
Click to collapse
No it will not lock the phone, unless you want it locked. Post a fastboot getvar all except remove the imei and serialno and we will be able to direct you how to rebrand your phone.
Klejdi90 said:
I just bought an HTC One which is unlocked but it shows the O2 bootscreen. I wish to debrand the phone but will that lock the phone? I am not sure how the phone was unlocked by the previous user. Thanks
Click to expand...
Click to collapse
Install a custom ROM.
SaHiLzZ said:
Install a custom ROM.
Click to expand...
Click to collapse
I wish to install a stock htc rom with ota can I do this without losing the unlock?
Klejdi90 said:
I wish to install a stock htc rom with ota can I do this without losing the unlock?
Click to expand...
Click to collapse
I dont know if you are talking about sim unlock or bootloader unlock but anyway, both sim and bootloader will stay unlocked even if you flash another rom or if you debrand the phone.
I see
@alray Yeah I mean sim unlock, Can you post a link of a guide to install stock htc rom to debrand. Will I be able to get OTA updates? What steps are needed Unlock bootloader, s-off, change cid custom recovery and install rom? Can you link me to a stock rom with ota for europe or international version. I had a look at the first link in your sig but its kinda confusing.
@nkk71 can you help?
I did a fastboot getvar all and here it is;
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.206.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTXXXXXXXXXX
(bootloader) imei: 35XXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.187s
Klejdi90 said:
@alray Yeah I mean sim unlock, Can you post a link of a guide to install stock htc rom to debrand. Will I be able to get OTA updates? What steps are needed Unlock bootloader, s-off, change cid custom recovery and install rom? Can you link me to a stock rom with ota for europe or international version. I had a look at the first link in your sig but its kinda confusing.
@nkk71 can you help?
I did a fastboot getvar all and here it is;
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.206.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTXXXXXXXXXX
(bootloader) imei: 35XXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.187s
Click to expand...
Click to collapse
If you want a full conversion, you can s-off the phone, change cid to HTC__001 and flash a x.xx.401.x RUU. Your best option to s-off on hboot 1.57 is probably sunshine s-off but its a paid exploit (25 USD) or you can try firewater, its free but it will require more steps and you have like 50% chance it will not work.
or the easier way, if you only want a debranded rom, you could only unlock the bootloader, flash twrp 2.6.3.3 and then flash a rom (like arhd 71.1)
alray said:
If you want a full conversion, you can s-off the phone, change cid to HTC__001 and flash a x.xx.401.x RUU. Your best option to s-off on hboot 1.57 is probably sunshine s-off but its a paid exploit (25 USD) or you can try firewater, its free but it will require more steps and you have like 50% chance it will not work.
or the easier way, if you only want a debranded rom, you could only unlock the bootloader, flash twrp 2.6.3.3 and then flash a rom (like arhd 71.1)
Click to expand...
Click to collapse
@alray Hey I did everything and am now trying to get the right RUU for europe or international. I flashed this : RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe and it seems to be fine except I am still s-off and an for some reason an option while doing the initial wizard called Tell HTC tells me this is a test device so this option will remain on. What is causing this? My device is a test device?! Wrong RUU?
Edit: I am updating the phone but it wont find the latest after every boot it finds the next. Now installing 4.3, it was 4.1.2 to begin with..
Klejdi90 said:
@alray Hey I did everything and am now trying to get the right RUU for europe or international. I flashed this : RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe and it seems to be fine except I am still s-off and an for some reason an option while doing the initial wizard called Tell HTC tells me this is a test device so this option will remain on. What is causing this? My device is a test device?! Wrong RUU?
Edit: I am updating the phone but it wont find the latest after a boot it finds the next? It was 4.1.2 to begin with..
Click to expand...
Click to collapse
Tell HTC/test device is normal. You'll always get this message at the initial setup with s-off phones, don't worry with this.
The ruu will not turn back s-on and thats a good thing. Keep your phone s-off.
alray said:
Tell HTC/test device is normal. You'll always get this message at the initial setup with s-off phones, don't worry with this.
The ruu will not turn back s-on and thats a good thing. Keep your phone s-off.
Click to expand...
Click to collapse
Yeah I thought it was the s-off causing this. Thanks for you reply, gonna install update after update and see if it comes up with the latest. Bit strange it doesn't install the absolute latest, but I guess the final update size would be huge to have all the fixes in previous versions in one.
Klejdi90 said:
Yeah I thought it was the s-off causing this. Thanks for you reply, gonna install update after update and see if it comes up with the latest. Bit strange it doesn't install the absolute latest, but I guess the final update size would be huge to have all the fixes in previous versions in one.
Click to expand...
Click to collapse
updates must be installed incrementally, don't worry you'll eventually be on the latest version.
alray said:
updates must be installed incrementally, don't worry you'll eventually be on the latest version.
Click to expand...
Click to collapse
Yep installed 4.4.3 just now. Thanks for all your help guys :good: Got me a debranded HTC One now. Hated the O2 bootscreen :silly:
Could use a little help with my HTC One M7. Bought it 2nd hand online a few months back, and it came pre-flashed with InsertCoin.
Buuut, updating has become a bit of a hassle for me, especially having to manually update. I'm looking to flash the stock ROM get the OTA up and running again.
I saw the other threads and followed the instructions so I have S-OFF, and I've already removed the "TAMPERED" and "UNLOCKED" from the bootloader. I came across a pretty big hiccup along the way, though.
For some reason, the OS on my bootloader screen is blank. I've tried getting version using ADB, but the version_main is still blank. Here's what I got from ADB:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ************
(bootloader) imei: ************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3760mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.082s
Click to expand...
Click to collapse
So, I've been wondering which RUU I'm supposed to use, because, most of the other posts I've read need me to match my version_main, my radio, CIDnumber, carrier and modelID. Not knowing my version/OS, what RUU should I use?
Note: My phone isn't locked to a carrier. I live outside of the US, (in Asia) but I'm unsure if I'm using the unlocked EU version or the International version.
Thanks in advanced,
-Q
detribdino said:
Could use a little help with my HTC One M7. Bought it 2nd hand online a few months back, and it came pre-flashed with InsertCoin.
Buuut, updating has become a bit of a hassle for me, especially having to manually update. I'm looking to flash the stock ROM get the OTA up and running again.
I saw the other threads and followed the instructions so I have S-OFF, and I've already removed the "TAMPERED" and "UNLOCKED" from the bootloader. I came across a pretty big hiccup along the way, though.
For some reason, the OS on my bootloader screen is blank. I've tried getting version using ADB, but the version_main is still blank. Here's what I got from ADB:
So, I've been wondering which RUU I'm supposed to use, because, most of the other posts I've read need me to match my version_main, my radio, CIDnumber, carrier and modelID. Not knowing my version/OS, what RUU should I use?
Note: My phone isn't locked to a carrier. I live outside of the US, (in Asia) but I'm unsure if I'm using the unlocked EU version or the International version.
Thanks in advanced,
-Q
Click to expand...
Click to collapse
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
then flash the latest WWE ruu (7.19.401.2)
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
RUU according to your info is 7.18.206.2 available at link post above but that's a carrier ruu with many bloatware so flash international ruu 7.19.401.2 instructions given above
i attempted to unlock bootloader on my wife's old HTC M7 (Australian/Vodafone), i was able to unlock the bootloader, but had to do some serious trial and error to get a custom recovery installed, eventually got an older twrp loaded, but the phone just refused to boot into recovery.
i then relocked the bootloader (no S-OFF), and when i try and unlock he bootloader now, the phone attempts to boot into the recovery, and is failing...
i've been trying to find an RUU from somewhere, just to blat the phone back to an old state, and try again.
are there RUUs available anywhere? i dont' care if its not for the local carrier, i just want to get a basic android rom on the thing.
However, im curious if i need to s-off to do this (wasnt the case with my previous HTC)
help!
<<<I NOW KNOW WHAT THE ISSUE WAS, I WAS FLASHING RECOVERY FROM THE HTC M8, NOT M7>>>
any ideas?
gjw00 said:
i then relocked the bootloader (no S-OFF), and when i try and unlock he bootloader now, the phone attempts to boot into the recovery, and is failing...
Click to expand...
Click to collapse
Really bad idea to relock the bootloader with a custom recovery, well you shouldn't relock at all if there is anything "custom" installed on your phone.The process of unlocking bootloader requires the stock recovery. The only way to flash the recovery partition is when the bootloader is unlocked or by flashing a signed firmware.zip or ruu.zip. The firmware.zip or ruu.zip must match your version-main, CID and MID.
i've been trying to find an RUU from somewhere, just to blat the phone back to an old state, and try again.
are there RUUs available anywhere? i dont' care if its not for the local carrier, i just want to get a basic android rom on the thing.
Click to expand...
Click to collapse
Its not working like that. If your phone is S-ON the ruu must be made for your carrier (must match CID and MID, must be same or newer version-main)
post the output of "fastboot getvar all" (remove your imei and serialno)
alray said:
Really bad idea to relock the bootloader with a custom recovery, well you shouldn't relock at all if there is anything "custom" installed on your phone.The process of unlocking bootloader requires the stock recovery. The only way to flash the recovery partition is when the bootloader is unlocked or by flashing a signed firmware.zip or ruu.zip. The firmware.zip or ruu.zip must match your version-main, CID and MID.
Its not working like that. If your phone is S-ON the ruu must be made for your carrier (must match CID and MID, must be same or newer version-main)
post the output of "fastboot getvar all" (remove your imei and serialno)
Click to expand...
Click to collapse
ok, i've been trying with a bunch of RUUs i found on the web, and trying to flash inside RUU (wasnt 100% sure what rebooting to RUU was for actually)
the CID is VODAP021, i will need to check when i get back home to see what the MID is, its not the GPE of the m7, if that helps, you reckon if i find an OTA update, and extract out the ruu.zip, it might blat a stock recovery on? will i need to use htc_fastboot, or just the standard fastboot?
my nexus 5 has finally shat it (small child cracked screen, now screen has crapped itself), just want to get a basic android build onto the m7 in the final few weeks before the new pixel phones are out...
gjw00 said:
ok, i've been trying with a bunch of RUUs i found on the web, and trying to flash inside RUU (wasnt 100% sure what rebooting to RUU was for actually)
the CID is VODAP021, i will need to check when i get back home to see what the MID is, its not the GPE of the m7, if that helps, you reckon if i find an OTA update, and extract out the ruu.zip, it might blat a stock recovery on? will i need to use htc_fastboot, or just the standard fastboot?
my nexus 5 has finally shat it (small child cracked screen, now screen has crapped itself), just want to get a basic android build onto the m7 in the final few weeks before the new pixel phones are out...
Click to expand...
Click to collapse
You can extract a firmware.zip (not an ruu) from an ota update and flash it to restore the stock recovery. You must use the right version. Waiting for your fastboot getvar all.
Sent from my HTC One using XDA Labs
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.980.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
gjw00 said:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.980.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
7.21.980.51 is the latest version for vodap021 and can't find a 7.21.980.51 firmware.zip or ota.zip.
At least there is a 7.21.980.51 ruu on ir-file.com, bad news is that you must register to this website to be able to download (20$ for 30 days)
http://ir-file.com/show.php?token=32375
i can load the phone into the OS btw, i've a feeling that OTA might on the device, you think its' accessible using a non-root browser? i could maybe get the ota zip off the device and try flashing that in RUU?
gjw00 said:
i can load the phone into the OS btw, i've a feeling that OTA might on the device, you think its' accessible using a non-root browser? i could maybe get the ota zip off the device and try flashing that in RUU?
Click to expand...
Click to collapse
Yes, if you can capture the ota this is the best option (because its free). Look in your /download folder, you're looking for a long file name starting with "OTA_M7_UL_L50_SENSE60" and ending with ".zip". Save it on your computer and extract the "firmware.zip" file from it. Then reboot in RUU mode and flash the firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you should be able to unlock again.
it worked! thank you..