[CLOSED] Repair a M7_WLS into a M7_UL - Updated - One (M7) Q&A, Help & Troubleshooting

Hello all!
I've bought a Htc One M7 for Christmas... Chinese problems included. The phone is in pristine condition, but I believe it was completely botched on the sofware side > flashed to a M7_WLS instead of a M7_UL.
What I have :
- A phone with an European IMEI. I do believe the phone is genuinely a HTC M7_UL, since PID is PN07100 (which is european)
- A bootloader that identifies the phone as a M7_WLS (Sprint)
- Radio 1.00.31.0603 (that raised my suspicions)
- S-OFF, HBoot 1.57, SuperCID but locked bootloader (can be unlocked).
- A lousy gift for my mother...
CLOSED/SOLVED : The device was a "real" M7_WLS in a M7-UL body, complete with laser engravings....
- If your bootloader says M7_WLS, it's a sprint device and no amount of flashing can change that.
- Proceeded to restore to stock with S-Off, latest firmware and stock 6.23 rom.
Thanks to everybody who helped me "unlock" that mystery, my mom now has a Nexus 5 lol
What I intend to do:
- Flash a 5.1 firmware (Combo NoBoot No Recovery) for a M7_UL and pray (lol), with the goal of restoring the radio to its correct use
- Go to a RUU if needed
What I need help for :
- Getting either directions, or a sense of feasability, because....
- ...I've lost track of S-OFF, unlocked bootloader, firmware and such. My own M7 was S-off at one time (3 years ago), got back to S-ON with a new hboot trying to update radio... Been stuck since. I don't want to mess this, lock things up, and have to ship the phone back.... My HD2 times are SUCH a long time ago :highfive:
> Basically : updating the radio and the firmware somehow, so I can use LTE bands in Europe and update the phone to a GPE 5.1, and make my mom happy.
Thank you everyone !
Edit: OMG, that HD2 Encyclopedia.... I now understand why I didn't have friends in High School.

RedWave31 said:
Hello all!
I've bought a Htc One M7 for Christmas... Chinese problems included. The phone is in pristine condition, but I believe it was completely botched on the sofware side > flashed to a M7_WLS instead of a M7_UL.
What I have :
- A phone with an European IMEI. I do believe the phone is genuinely a HTC M7_UL, since PID is PN07100 (which is european)
- A bootloader that identifies the phone as a M7_WLS (Sprint)
- Radio 1.00.31.0603 (that raised my suspicions)
- S-OFF, HBoot 1.57, SuperCID but locked bootloader (can be unlocked).
Click to expand...
Click to collapse
If the bootloader is saying M7_WLS then its probably a M7_WLS. You can't trust the PN0710000 MID, it can easliy be changed with S-OFF. Looks more like somebody tried to convert his M7_WLS into a M7_UL which is not possible. You should flash back a Sprint RUU. If you want to confirm what i'm saying dump the MFG partition (mmcblk0p6) and you'll find the original identity of the phone inside of it, most likely MID PN0720000 and CID SPCS_001

alray said:
If the bootloader is saying M7_WLS then its probably a M7_WLS. You can't trust the PN0710000 MID, it can easliy be changed with S-OFF. Looks more like somebody tried to convert his M7_WLS into a M7_UL which is not possible. You should flash back a Sprint RUU. If you want to confirm what i'm saying dump the MFG partition (mmcblk0p6) and you'll find the original identity of the phone inside of it, most likely MID PN0720000 and CID SPCS_001
Click to expand...
Click to collapse
Thanks for this reply.
Unfortunately, I don't have enough knowledge to dump a partition - managed to input the command, but couldn't retrieve the data.
Where I'm at now (tryhard mode enabled):
- Changed MID
- Flashed GPE firmware 5.1 full combo
- Flashed GPE RUU 5.1, ended trying a 4.4, see why next
- Flashed recovery 2.8.7.0 > works, but cannot mount the cache and sdcard unless I fix permissions with SELinux mode
Everything (bootloader, recovery) kinda works, but the Rom won't boot.
Trying to know why : when I flash any RUU, I got two fails at signature checking
- sbl 1-1
- sbl 1-2
I got a white Google logo on black background with a little lock near the HTC logo on the front > I cannot find ANY clue on this one, anywhere on Google, XDA... Damn
- The bootloader also always shows a M7_WLS info, despite MID and CID and stuff being all M7_UL (after all thoses flashes, I get why) > Am I trying too much, not enough, or should it change somehow?
If anyone had a clue, I'd apreciate it.
- I can flash back and forth any firmware or Hboot (M7_UL based) The phone just takes it all, no questions asked ^^
PS : I can send it back, but i'd try at least to put it back in its original shape. Should I flash back a sprint firmware, sprint RUU and call it a day? Since I was previously told flashing a different RUU on a sprint phone would destroy my phone and it didnt....well
Thanks guys !

There is a very easy way to find out if your phone is WLS or WWE. Does it have a sim card slot? WLS is CDMA and doesn't have sim card, so that's a step closer to identifying your phone ?

RedWave31 said:
Thanks for this reply.
Unfortunately, I don't have enough knowledge to dump a partition - managed to input the command, but couldn't retrieve the data.
Click to expand...
Click to collapse
Code:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mfg_backup.img
exit
exit
adb pull /sdcard/mfg_backup.img C:\Wherever\you\want\to\save\it
Where I'm at now (tryhard mode enabled):
- Changed MID
- Flashed GPE firmware 5.1 full combo
- Flashed GPE RUU 5.1, ended trying a 4.4, see why next
- Flashed recovery 2.8.7.0 > works, but cannot mount the cache and sdcard unless I fix permissions with SELinux mode
Everything (bootloader, recovery) kinda works, but the Rom won't boot.
Click to expand...
Click to collapse
You have a WLS and flashing UL RUU, this will obviously not work. Flash a sprint RUU with the sprint MID and CID (PN07200000 SPCS_001) If you need a custom recovery for whatever reason (like dumping your MFG) use a WLS custom recovery.
Trying to know why : when I flash any RUU, I got two fails at signature checking
- sbl 1-1
- sbl 1-2
Click to expand...
Click to collapse
This is not a problem, these item are bypassed.
I got a white Google logo on black background with a little lock near the HTC logo on the front > I cannot find ANY clue on this one, anywhere on Google, XDA... Damn
Click to expand...
Click to collapse
This is the GPE splash screen. That little lock tells you the bootloader status. Open lock = unlocked bootloader
- The bootloader also always shows a M7_WLS info, despite MID and CID and stuff being all M7_UL (after all thoses flashes, I get why)
Click to expand...
Click to collapse
Why? read what iv said in my previous post.... Because its a M7_WLS not a UL.

alray said:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mfg_backup.img
exit
exit
adb pull /sdcard/mfg_backup.img C:\Wherever\you\want\to\save\it
You have a WLS and flashing UL RUU, this will obviously not work.
Click to expand...
Click to collapse
Thanks for all the info, I wish I would have replied earlier : I have a sim card slot. As stated before, can a Sprint CDMA device have one?
Since I don't think so, I now truly believe my phone is a really botched up M7_UL (don't believe it's a M7_U gsm only)
I'm gonna have to figure out why .exe RUU don't work, and why flashing zip decrypted ones don't work either.
Also, if someone has any clue about that M7_WLS showing up despite all the other clues pointing towards an original M7_UL... I've yet to found how this is possible.
Next operation is gonna be trying to install a real .exe GPE RUU, I believe all the flashing and stuff is getting me out of sync firmware numbers (hboot higher than the RUU requirements or so).
They are kinda hard to find (unless from HTC), and I find myself with gigs of Zips and RUU ^^
Will try the M7_U possibility also.
Will dump that partition just to be sure, but since the phone has been tinkered SO MUCH... I don't get it at this point why would someone do that !
> Countdown to christmas...
Thanks guys for your support, it's heartwarming these days

RedWave31 said:
Thanks for all the info, I wish I would have replied earlier : I have a sim card slot. As stated before, can a Sprint CDMA device have one?
Since I don't think so, I now truly believe my phone is a really botched up M7_UL (don't believe it's a M7_U gsm only)
Click to expand...
Click to collapse
The sprint variant also have a sim card, its required for LTE and roaming.
Also, if someone has any clue about that M7_WLS showing up despite all the other clues pointing towards an original M7_UL
Click to expand...
Click to collapse
Like I said earlier, your clues are not telling anything. The phone is S-OFF which means both the MID and CID can be modified to anything easily. If the product name is M7_WLS then its a M7_WLS !!!!!
Next operation is gonna be trying to install a real .exe GPE RUU, I believe all the flashing and stuff is getting me out of sync firmware numbers (hboot higher than the RUU requirements or so).
They are kinda hard to find (unless from HTC), and I find myself with gigs of Zips and RUU ^^
Will try the M7_U possibility also.
Click to expand...
Click to collapse
That will be a lot of wasted time. Write back the Sprint MID and CID and flash the Sprint RUU. Even better, dump the MFG partition first so you are 100% sure what that phone is.
I don't get it at this point why would someone do that !
Click to expand...
Click to collapse
The previous owner probably wanted to flash a M7_UL RUU on his M7_WLS phone without knowing it wasn't possible even after changing the MID and CID to M7_UL.

Related

[Q] where is htc one factory shipped rom?

Hi,
Another noob question from me.
I recently bought a HTC One. I uploaded a custom ROM (was silly and didn't backup properly). I'd like to have the ability to restore the phone to a complete factory reset. I want the same, exact HTC ROM that the phone originally shipped with, and also no ***TAMPERED***, ***UNLOCKED***. I'll worry about the tampered and unlocked later (locking should be easy - but i want ***LOCKED*** not ***RELOCKED***).
My phone's info:
M7_U PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 15 2013,22:11:42:-1
I keep on running into deadends thinking I've found the factory stock ROM, but when I try to install it, I get errors like 'could not install'...
At some point I relocked the phone and the install went further, but eventually failed with a 'wrong model' error or something. Based on the model info above of my phone can someone point me in the right direction to find the correct ROM?
Thanks so much. I hope soon to be just as much of a contributor as I am an asker...
First of all you cannot get it to state locked it will always say relocked until a s-off is achieved where you will be able to downgrade hboot and second of all download the app below and post the results.
https://play.google.com/store/apps/...sMSwxLDEsIm9yZy50cml0b25zb2Z0LmNpZGdldHRlciJd
daleski75 said:
First of all you cannot get it to state locked it will always say relocked until a s-off is achieved where you will be able to downgrade hboot and second of all download the app below and post the results.
https://play.google.com/store/apps/...sMSwxLDEsIm9yZy50cml0b25zb2Z0LmNpZGdldHRlciJd
Click to expand...
Click to collapse
Thanks...downloaded. A long list of variables with no cut'n'paste...but here is maybe the relevant info:
ro.boot.carrier HTC-Asia-SEA-WWE
ro.boot.cid HTC__044
ro.boot.mid PN0711000
ro.cm.device m7
ro.product.module HTC One
ro.product.name htc_m7
Any other details I can provide?
I think this original RUU should suffice.
http://bugsylawson.com/files/file/1...14325013-1033115001-release-311678-signedexe/

[Q] Help updating HTC 802w

I need your help guys. I can't apply any software updates to my HTC 802w (current version is 4.1.2) as it does not have the option in the Settings. I don't want to deal with the headaches of rooting and custom ROMS, so is there any way I can just download Android 4.2/4.3 (HTC Sense 5.5 would be a bonus) for my phone and install it via the microSD card or something? I am just looking for a simple and straightforward way to update the software for now.
Bumping for replies. Any advice will be greatly appreciated.
My understanding is that the update option is disabled in custom ROMs so people don't mess with their devices. What does your phones bootloader say? When off, press power and vol down together and hold.
Sent from my HTC One using XDA Premium 4 mobile app
hardstuffmuc said:
My understanding is that the update option is disabled in custom ROMs so people don't mess with their devices. What does your phones bootloader say? When off, press power and vol down together and hold.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is what it says:
***LOCKED***
M7DUG PVT SHIP S-OFF RH
CID-11111111
HBOOT - 2.23.0000
RADIO-U2.05.3501.18
OpenDSP- v28.120.274.0320
QSC - 1237.18.19.0520
OS-1.26.707.5
eMMC-boot 2048MB
May 29 2013, 13:06:9.12873
I just want to be able to install the regular 4.2.2 or 4.3 update. I am assuming I can't because I am in Saudi Arabia and my phone is Chinese, and the updates are supposed to be OTA, which is not possible here. Even so, there must be some way to just download the files from somewhere and install them manually, right?
Killfenrir said:
This is what it says:
***LOCKED***
M7DUG PVT SHIP S-OFF RH
CID-11111111
HBOOT - 2.23.0000
RADIO-U2.05.3501.18
OpenDSP- v28.120.274.0320
QSC - 1237.18.19.0520
OS-1.26.707.5
eMMC-boot 2048MB
May 29 2013, 13:06:9.12873
I just want to be able to install the regular 4.2.2 or 4.3 update. I am assuming I can't because I am in Saudi Arabia and my phone is Chinese, and the updates are supposed to be OTA, which is not possible here. Even so, there must be some way to just download the files from somewhere and install them manually, right?
Click to expand...
Click to collapse
don't know where or from whom you got your phone, but here's the situation you are in:
***LOCKED***
M7DUG PVT SHIP S-OFF RH <--- S-Off, only in a very few and rare situation would a phone come S-Off
CID-11111111 <--- SuperCID, somebody did that!!
M7DUG <--- that's the Dual SIM, right? so don't go messing around with M7_U and M7_UL versions, they are DIFFERENT
so to put it mildly, your phone was used by someone before you, and is not "out of the box". and you will not get any OTAs unless you're 100% stock.
nkk71 said:
don't know where or from whom you got your phone, but here's the situation you are in:
***LOCKED***
M7DUG PVT SHIP S-OFF RH <--- S-Off, only in a very few and rare situation would a phone come S-Off
CID-11111111 <--- SuperCID, somebody did that!!
M7DUG <--- that's the Dual SIM, right? so don't go messing around with M7_U and M7_UL versions, they are DIFFERENT
so to put it mildly, your phone was used by someone before you, and is not "out of the box". and you will not get any OTAs unless you're 100% stock.
Click to expand...
Click to collapse
Thanks for the reply. Just a few questions:
1. What do you mean by "SuperCID"? Is it a good thing or a bad thing?
2. Yes, the phone is dual sim, and if what you said is correct, OTAs are out of the question. So if I just want to update my Android 4.1.2 to 4.2.2 (and hopefully HTC Sense as well), what are my options? What about upgrading with RUUs?
3. Yes, I got the impression that my phone was used by someone before me, as even though it has the Chinese bloatware, it does not have HTC Marketplace App or most of the Google apps but strangely has the Play Store app. Weird.
4. How can I "unlock" my phone? Or more specifically, what are the restrictions on a "locked" phone and what are the benefits of unlocking?
Killfenrir said:
Thanks for the reply. Just a few questions:
1. What do you mean by "SuperCID"? Is it a good thing or a bad thing?
2. Yes, the phone is dual sim, and if what you said is correct, OTAs are out of the question. So if I just want to update my Android 4.1.2 to 4.2.2 (and hopefully HTC Sense as well), what are my options? What about upgrading with RUUs?
3. Yes, I got the impression that my phone was used by someone before me, as even though it has the Chinese bloatware, it does not have HTC Marketplace App or most of the Google apps but strangely has the Play Store app. Weird.
4. How can I "unlock" my phone? Or more specifically, what are the restrictions on a "locked" phone and what are the benefits of unlocking?
Click to expand...
Click to collapse
S-Off is a good thing, means you can change pretty much anything on your phone, but it also means you can brick it
I have no idea about the dual sim, so you're going to have to do some searching. I don't know if there are any RUUs out there for "M7DUG", but I think Maximus has a custom ROM for the dual sim,
whatever you do, make sure it's compatible with your device "M7DUG"!!!
nkk71 said:
S-Off is a good thing, means you can change pretty much anything on your phone, but it also means you can brick it
I have no idea about the dual sim, so you're going to have to do some searching. I don't know if there are any RUUs out there for "M7DUG", but I think Maximus has a custom ROM for the dual sim,
whatever you do, make sure it's compatible with your device "M7DUG"!!!
Click to expand...
Click to collapse
I found this post with a collection of RUUs:
http://forum.xda-developers.com/showpost.php?p=43177948&postcount=369
Looks like the right ones. So, if I want to update from Android 4.1.2 to Android 4.2.2 these RUUs, how do I do so (I mean, what is the procedure)? And will the update require me to wipe all of my data or can I keep my data and settings?
Also, what does "locked" real mean for my device and how can I "unlock" my phone?
Killfenrir said:
I found this post with a collection of RUUs:
http://forum.xda-developers.com/showpost.php?p=43177948&postcount=369
Looks like the right ones. So, if I want to update from Android 4.1.2 to Android 4.2.2 these RUUs, how do I do so (I mean, what is the procedure)? And will the update require me to wipe all of my data or can I keep my data and settings?
Also, how can I "unlock" my phone?
Click to expand...
Click to collapse
Good find :good:
I'll look into it tomorrow, have to sign off for tonight.
and yes, it will wipe EVERYTHING off your phone, so back everything up tonight, and I'll get back to you tomorrow, if nobody else answers you
have a good night
Killfenrir said:
I found this post with a collection of RUUs:
http://forum.xda-developers.com/showpost.php?p=43177948&postcount=369
Looks like the right ones. So, if I want to update from Android 4.1.2 to Android 4.2.2 these RUUs, how do I do so (I mean, what is the procedure)? And will the update require me to wipe all of my data or can I keep my data and settings?
Also, what does "locked" real mean for my device and how can I "unlock" my phone?
Click to expand...
Click to collapse
before going on, i need to check a couple of things:
1) a screenshot of Settings -> About -> Software information
2) a screenshot of Settings -> About -> Software information -> More
3) in bootloader/FASTBOOT USB: a "fastboot getvar all" (remove IMEI and serialno)
4) download CIDGetter from Play Store, and tell me which CID it gives you.
please please help
I have brought one HTC one 802w from china. After installing some program it is restarting continuously
Then i tried to install the viper one 3.5 but not my phone is stuch in the unicom logo and cannot install the viperone 3.5. i donot have backup.
the error log is as under.
AROMA INSTALLER version 2.70B6
(c) 2013 by amarullz xda-developers
ROM Name : ViperOne
ROM Version : 3.5.0
ROM Author : Team Venom
Device : HTC One
Start at : Sat Dec 7 15:24:57 2013
===========================================
ViperOne 3.5.0 By Team Venom
Be patient - 1st boot may take a while
===========================================
emmc_umount_partition: umount /cache failed
Extracting tools
Installing Venom Tools
Extracting Build Tools
about to run program [/sbin/busybox] with 3 args
Extract: /temp/fsck.ext4
Extract: /temp/mkfs.ext4
Extract: /temp/tune2fs.ext4
Setting permissions
set_perm: chown of /sdcard/Venom/Tools/VenomCheck.sh to 0 0 failed: No such file or directory
set_perm: chmod of /sdcard/Venom/Tools/VenomCheck.sh to 777 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
End at : Sat Dec 7 15:25:00 2013
similar problem
nkk71 said:
before going on, i need to check a couple of things:
1) a screenshot of Settings -> About -> Software information
2) a screenshot of Settings -> About -> Software information -> More
3) in bootloader/FASTBOOT USB: a "fastboot getvar all" (remove IMEI and serialno)
4) download CIDGetter from Play Store, and tell me which CID it gives you.
Click to expand...
Click to collapse
i have the similar problem, although mine say s-on
*****UNLOCKED******
M7CDUG PVT SHIP S-ON RH
HBOOT-2.23.0000
RADIO-U2.05.3501.18

[SOLVED][Q] Fully backing up before tampering (CID HTC__332) [Conversion to WWE]

Hello guys,
I recently got my HTC One, and I don't know how or why, but it turned out to be a Mexican version, with CID HTC__332 (in the middle of Europe none the less!). So I updated to Android 4.3 with Sense 5.0 (OTA), and have been waiting for the Sense 5.5 update for more than 2 months now (not to mention KitKat, which I'll probably never get).
Anyway, I got tired of waiting and decided to get superCID and force it to update. But since it's my first time with this phone I'd really hate to mess it up, so please help me if you can:
I've read up on almost everything regarding the process, so I know I need to:
1. unlock the bootloader (with HTC dev site)
2. root the phone (it seems there's no other way but with installing a custom recovery)
3. get s-off with rumrunner (if it works with this weird HTC__332 CID od mine)
4. change to superCID
5. restore stock recovery
6. update with FOTA
Now, what I don't know is what do I do if something goes wrong and the phone won't boot, or goes into a bootloop, or something like that?
I've installed custom ROMs on my old Xperia U20i before, so I always had CWM backups, but even if they failed I could bring back the phone with the SE Update Service. HTC doesn't seem to have such a program... the closest thing I could find were those RUUs, but I'm not sure which one (if any) is for my phone I've also seen lots of stock recoveries around, but I'm not sure which one I'd need to flash for the OTA update to work.
So, looking at the info from my phone below, can you tell me which RUU and stock recovery I need?
Also, and this is the most important, is there a way for me to just back up everything (nandroid) including my stock recovery, with just an unlocked bootloader*, so I have a failsafe?
(* as I understand it, rooting requires a custom recovery, so I loose the stock one)
Here's the info from my phone, please ask if you need more:
About:
Code:
Android version: 4.3
HTC Sense version: 5.0
Software number: 3.25.599.2
HTC SDK API level: 5.45
Kernel version: 3.4.10-gd92dcb6, [email protected] # 1, SMP PREEMPT
Baseband version: 4A.20.3263.16_10.38k.1157.04D
Build number: 3.25.599.2 CL259846 release-keys
Bootloader:
Code:
M7_U PVTSHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.25.599.2
eMMC-boot 2048MB
Oct 9 2013, 17:55:59.0
Fastboot:
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main: 3.25.599.2
version-misc: PVT SHIP S-ON
serialno: HT386W90****
imei: ****************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 3935mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e0349bfc
hbootpreupdate: 11
gencheckpt: 0
Please don't tell me I'm stuck with this version and that I'll have to risk it, I love this phone too much to brick it
mbinic said:
Hello guys,
I recently got my HTC One, and I don't know how or why, but it turned out to be a Mexican version, with CID HTC__332 (in the middle of Europe none the less!). So I updated to Android 4.3 with Sense 5.0 (OTA), and have been waiting for the Sense 5.5 update for more than 2 months now (not to mention KitKat, which I'll probably never get).
Anyway, I got tired of waiting and decided to get superCID and force it to update. But since it's my first time with this phone I'd really hate to mess it up, so please help me if you can:
I've read up on almost everything regarding the process, so I know I need to:
1. unlock the bootloader (with HTC dev site)
2. root the phone (it seems there's no other way but with installing a custom recovery)
3. get s-off with rumrunner (if it works with this weird HTC__332 CID od mine)
4. change to superCID
5. restore stock recovery
6. update with FOTA
Now, what I don't know is what do I do if something goes wrong and the phone won't boot, or goes into a bootloop, or something like that?
I've installed custom ROMs on my old Xperia U20i before, so I always had CWM backups, but even if they failed I could bring back the phone with the SE Update Service. HTC doesn't seem to have such a program... the closest thing I could find were those RUUs, but I'm not sure which one (if any) is for my phone I've also seen lots of stock recoveries around, but I'm not sure which one I'd need to flash for the OTA update to work.
So, looking at the info from my phone below, can you tell me which RUU and stock recovery I need?
Also, and this is the most important, is there a way for me to just back up everything (nandroid) including my stock recovery, with just an unlocked bootloader*, so I have a failsafe?
(* as I understand it, rooting requires a custom recovery, so I loose the stock one)
Here's the info from my phone, please ask if you need more:
About:
Code:
Android version: 4.3
HTC Sense version: 5.0
Software number: 3.25.599.2
HTC SDK API level: 5.45
Kernel version: 3.4.10-gd92dcb6, [email protected] # 1, SMP PREEMPT
Baseband version: 4A.20.3263.16_10.38k.1157.04D
Build number: 3.25.599.2 CL259846 release-keys
Bootloader:
Code:
M7_U PVTSHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.25.599.2
eMMC-boot 2048MB
Oct 9 2013, 17:55:59.0
Fastboot:
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.20.3263.16
version-cpld: None
version-microp: None
version-main: 3.25.599.2
version-misc: PVT SHIP S-ON
serialno: HT386W90****
imei: ****************
meid: 00000000000000
product: m7_u
platform: HBOOT-8064
modelid: PN0711000
cidnum: HTC__332
battery-status: good
battery-voltage: 3935mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e0349bfc
hbootpreupdate: 11
gencheckpt: 0
Please don't tell me I'm stuck with this version and that I'll have to risk it, I love this phone too much to brick it
Click to expand...
Click to collapse
I just went through this a couple days ago with someone
go here and read pages 2-5 and see if you understand or still have questions read it all before moving on
http://forum.xda-developers.com/showthread.php?t=2593387&page=2
Thanks for your answer clsA!
I don't know how I missed that thread, I've been searching for HTC__332 and that damned version number all over :$
So, having read that, I'd say I'll first need to:
1. unlock my bootloader
2. root (and flash a custom recovery, TWRP 2.6.3.3)
* 2.5 create nandroid backup
* 2.5.5 get files for rumrunner version for this software
3. install ARHD (31.6, http://forum.xda-developers.com/showthread.php?t=2183023)
4. get s-off with rumrunner (0.50)
And after that's all done, come back, re-read and do the more-likely-to-cause-a-heartattack-part, right?
Just a couple more questions before I try and do this:
1. There's no stock recovery image available for my phone, so after flashing the custom recovery I won't be able to go back to stock recovery and receive ota updates (if they ever even come)?
2. Will rumrunner work with ARHD 41.0? Or, will ARHD 41.0 install and run normally on my phone? In case I can't finish the process correctly, it would be comforting to know I can still have the latest and greatest software on my phone
mbinic said:
Thanks for your answer clsA!
I don't know how I missed that thread, I've been searching for HTC__332 and that damned version number all over :$
So, having read that, I'd say I'll first need to:
1. unlock my bootloader
2. root (and flash a custom recovery, TWRP 2.6.3.3)
* 2.5 create nandroid backup
* 2.5.5 get files for rumrunner version for this software
3. install ARHD (31.6, http://forum.xda-developers.com/showthread.php?t=2183023)
4. get s-off with rumrunner (0.50)
And after that's all done, come back, re-read and do the more-likely-to-cause-a-heartattack-part, right?
Just a couple more questions before I try and do this:
1. There's no stock recovery image available for my phone, so after flashing the custom recovery I won't be able to go back to stock recovery and receive ota updates (if they ever even come)?
2. Will rumrunner work with ARHD 41.0? Or, will ARHD 41.0 install and run normally on my phone? In case I can't finish the process correctly, it would be comforting to know I can still have the latest and greatest software on my phone
Click to expand...
Click to collapse
yes after the conversion to .401 you will have a EU device and can update and flash all the new roms as they come out.
make note of the 2 links posted about changing your MID / CID their important steps in the whole process
http://forum.xda-developers.com/showthread.php?t=2535365
this guide by @nkk71 is a good source of information your just doing a few things differently
http://forum.xda-developers.com/showthread.php?t=2541082
OK, so part one is going mostly smoothly for now - unlocked bootloader, flashed TWRP, backed up (uploading for sharing) + saved partitions for rumrunner if I end up needing them (also uploading), had a few bootloops but managed to get ARHD 31.6 running. Now onto rumrunner...
I got S-OFF with rumrunner in the first try! Now to re-read and change CID and MID (4:40 AM, fingers crossed, heart pounding)
I'm sorry for this, but some of the posts are confusing and a bit contradictory, so I need to confirm this:
1. set super CID with
Code:
fastboot oem writecid 11111111
Is that the correct CID? Is that the correct number of 1s (8? from http://forum.xda-developers.com/showthread.php?t=2317536)?
2.set MID with MID_Change_TOOL_v.1.01 (from http://forum.xda-developers.com/showthread.php?t=2535365)
3. Now what, do I:
3.1 run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
OR
3.2 downgrade to HBOOT 1.44 with (from http://forum.xda-developers.com/showthread.php?t=2541082):
If you’re on hboot which is above 1.44, then first thing is to downgrade that:
so download this: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
Click to expand...
Click to collapse
and then run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
I'm a bit scared, so please bare with me, and if this is completely wrong please point me in the right direction.
Also, will I have a relocked-untampered-S-ON device after running the RUU, or will that part be left as it is (unlocked-tampered-S-OFF)? I don't think I'll need to be S-OFF after this, and don't mind the red texts in fastboot, so is there anything else I'll need to do after the RUUinstall, or just go and get the FOTA update?
mbinic said:
I'm sorry for this, but some of the posts are confusing and a bit contradictory, so I need to confirm this:
1. set super CID with
Code:
fastboot oem writecid 11111111
Is that the correct CID? Is that the correct number of 1s (8? from http://forum.xda-developers.com/showthread.php?t=2317536)?
2.set MID with MID_Change_TOOL_v.1.01 (from http://forum.xda-developers.com/showthread.php?t=2535365)
3. Now what, do I:
3.1 run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
OR
3.2 downgrade to HBOOT 1.44 with (from http://forum.xda-developers.com/showthread.php?t=2541082):
and then run RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe?
I'm a bit scared, so please bare with me, and if this is completely wrong please point me in the right direction.
Also, will I have a relocked-untampered-S-ON device after running the RUU, or will that part be left as it is (unlocked-tampered-S-OFF)? I don't think I'll need to be S-OFF after this, and don't mind the red texts in fastboot, so is there anything else I'll need to do after the RUUinstall, or just go and get the FOTA update?
Click to expand...
Click to collapse
Almost
1- change you MID to PN071000 using the tool
2- with SuperCID you cannot receive OTAs, so you need to change CID to European unbranded, there are several (this will affect the country/language options): http://forum.xda-developers.com/showpost.php?p=48195855&postcount=98 (instructions are also in that post)
so for example, if you wanted Eastern European languages you would need to set CID to HTC__032
3- since you're on hboot 1.55, you need to downgrade that separately to 1.44
4- you can leave the phone UNLOCKED, and even TAMPERED, but if you prefer to set them LOCKED and remove TAMPERED you can follow my guide.
5- run the RUU you mentioned
6- KEEP S-OFF!!
OTAs will not be affected by unlocked bootloader, or S-Off
let me know if you need more details
Ok, so the correct order is:
1. change MID
2. change CID
3. downgrade HBOOT
4. run RUU
Thanks!
mbinic said:
Ok, so the correct order is:
1. change MID
2. change CID
3. downgrade HBOOT
4. run RUU
Thanks!
Click to expand...
Click to collapse
yep, that works!
don't want to confuse you , but 1 2 and 3 can be run in any order, most important is to do run the ruu as last step, once the ruu has completed you should immediately receive OTAs.
remember, stay S-Off, consider it your "get out of jail" card, in case you ever want to change something again.
Thanks again I'll try it in a couple of hours and report my progress.
Edit:
OK, got CID HTC__032 and changed MID successfully. AROMA hung at 0.00%, but a restart helped like it was described in the post. Now onto HBOOT and RUU.
Edit 2:
Installed HBOOT 1.44 and the Guru Bootloader reset - removed tampered and set locked (why not ). Running RUU in a few minutes...
So, everything went smoothly, the OTA is slowly installing, and I am now a proud owner of an Eastern European model! B)
I learned a lot in the process, certainly read a lot, and I am very grateful to the people who wrote the posts, and especially to those who helped me here!
Guys, if we ever meet, the beer is on me! Until then, PM me, I can at least buy you one from here Maybe I can also help out somehow, being that I'm a programmer as well.
Anyway, after the OTA updates are done and I set everything up, I'll probably be reinstalling TWRP and going to ARHD 41, but first I'll see what else is out there
mbinic said:
So, everything went smoothly, the OTA is slowly installing, and I am now a proud owner of an Eastern European model! B)
I learned a lot in the process, certainly read a lot, and I am very grateful to the people who wrote the posts, and especially to those who helped me here!
Guys, if we ever meet, the beer is on me! Until then, PM me, I can at least buy you one from here Maybe I can also help out somehow, being that I'm a programmer as well.
Anyway, after the OTA updates are done and I set everything up, I'll probably be reinstalling TWRP and going to ARHD 41, but first I'll see what else is out there
Click to expand...
Click to collapse
Congrats mate
Can you also edit main thread title to include [SOLVED], thanks
Done
The OTA install is done as well, but unfortunately the latest one I got was JB 4.3 with Sense 5.5 (3.62.401.1), no KitKat. I tried changing CID to HTC__001, but still no KitKat updates.
I'll probably now install ARHD 41.0, newest MaximusHD or Elegancia, but they mention upgrading the firmware. Should I try that, upgrade the firmware that is? Will I be able to go back later with HBOOT 1.44 and the RUU I already used, or will that option be gone (or is it already)?
Sorry for more questions, but I wouldn't want to mess everything up at the very end
mbinic said:
Done
The OTA install is done as well, but unfortunately the latest one I got was JB 4.3 with Sense 5.5 (3.62.401.1), no KitKat. I tried changing CID to HTC__001, but still no KitKat updates.
I'll probably now install ARHD 41.0, newest MaximusHD or Elegancia, but they mention upgrading the firmware. Should I try that, upgrade the firmware that is? Will I be able to go back later with HBOOT 1.44 and the RUU I already used, or will that option be gone (or is it already)?
Sorry for more questions, but I wouldn't want to mess everything up at the very end
Click to expand...
Click to collapse
4.4 (hopefully 4.4.2) not out yet for most, only US Dev Edition, and has a few "bad habits" for the rest of the world... no need to change CIDs, it'll come soon enough....
ARHD 41.0 and MaximusHD are based on the US Dev Edition, not the WWE edition.
I just figured that out from the version number, sorry. So, no firmware flashing for now, I'll just go ahead with the ROM, but first a TWRP backup, just in case. Thanks again!
my htc
mbinic said:
I just figured that out from the version number, sorry. So, no firmware flashing for now, I'll just go ahead with the ROM, but first a TWRP backup, just in case. Thanks again!
Click to expand...
Click to collapse
hi friends first my english is not so good so excuse me i a have some mistakes, then i want to say i was reading your experience, i got the same version of htc one HTC_332 this is the cid for latin america this is what htc supports tell me by email, ok i got a little questions maybe u can help me
1)this process works on my version of htc correctly?
2)my phone update via ota to 4.3 and sense 5.0 and i want know if u recomend to me do this process or wait for ota update for 4.4 kitkat and sense 5.5 ( i know htc is not the best company giving updates)
3) is high the risk of brick? is some way to restore if something fails in process?
PS 1: i'm really newbie in this or noob i was reading to grown my knows and i want a opinion of someone with more experience.
PS 2: is ironic but this htc_332 i buyed in florida and is factory unlocked, bad luck mine uh??
for last i want to thanks for the time you take to anwer me
Hello edulaffont,
edulaffont said:
1)this process works on my version of htc correctly?
2)my phone update via ota to 4.3 and sense 5.0 and i want know if u recomend to me do this process or wait for ota update for 4.4 kitkat and sense 5.5 ( i know htc is not the best company giving updates)
3) is high the risk of brick? is some way to restore if something fails in process?
PS 1: i'm really newbie in this or noob i was reading to grown my knows and i want a opinion of someone with more experience.
PS 2: is ironic but this htc_332 i buyed in florida and is factory unlocked, bad luck mine uh??
Click to expand...
Click to collapse
1) As you can see from this thread, I went through this process without any problems. When I was done converting and updated to 4.3 with Sense 5.5 I decided to go with ARHD 41, and last night installed new firmware and ARHD 51, also without any problems.
2) I would recommend you convert your phone to WWE, but that decision, as well as the risk, is on you. I got tired of waiting and didn't think HTC would update this CID, so I tried it and am very happy with how it turned out. I can't thank enough the guys that helped me here!
(btw guys, those beers are getting warm, pm me your paypals if you've got 'em)
3) I'm not really sure about this one, but I went ahead and backed up everything I could before I started it. I think it'll go well if you follow the instructions here
first
mbinic said:
Hello edulaffont,
1) As you can see from this thread, I went through this process without any problems. When I was done converting and updated to 4.3 with Sense 5.5 I decided to go with ARHD 41, and last night installed new firmware and ARHD 51, also without any problems.
2) I would recommend you convert your phone to WWE, but that decision, as well as the risk, is on you. I got tired of waiting and didn't think HTC would update this CID, so I tried it and am very happy with how it turned out. I can't thank enough the guys that helped me here!
(btw guys, those beers are getting warm, pm me your paypals if you've got 'em)
3) I'm not really sure about this one, but I went ahead and backed up everything I could before I started it. I think it'll go well if you follow the instructions here
Click to expand...
Click to collapse
First thanks for fast reply and help, how i said my phone esas updated to 4.3 with sense 5.0 the same day i buyed it, by the way This was about 1 week ago, i see is better change Cid What do yo recomend by the way how do u change the firmware?,thanks in advance and excuse my poor english
edulaffont said:
First thanks for fast reply and help, how i said my phone esas updated to 4.3 with sense 5.0 the same day i buyed it, by the way This was about 1 week ago, i see is better change Cid What do yo recomend by the way how do u change the firmware?,thanks in advance and excuse my poor english
Click to expand...
Click to collapse
I also got that update as soon as I bought the phone, some time in October/November I think, it's old.
I didn't change the firmware when I was converting to WWE, a .401 version wasn't out yet.
I did change it last night though, and installed ARHD 51 (it gives me more options than stock) and everything went smoothly (I even did a dirty flash).
Anyway, I recommend you stick to the original instructions (use old ARHD for rumrunner), and when you're done converting to WWE, ran the RUU and everything works you can choose wheter you want to get the OTAs and stay stock (KitKat 4.4.2 OTA for WWE just came out, with new firmware), or root and install any ROM you wish

[Q] About to use the lollipop RUU but have some questions.

Hi there, so I'm looking to flash lollipop to my M7 but first want to verify I've taken the right steps.
Here's my phone's info:
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.00000
RADIO-4A.23.3263.28
OpenDSP-v32.120.274.0909
OS-4.19.631.9
eMMC-boot 2048MB
MID: PN0712000
CID: ROGER001
version-main 4.19.631.9
Now, as far as I'm aware, this is the unlocked edition of the M7. I'm hoping to use this RUU here To flash lollipop onto my phone:
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2.exe (can't post link because I just registered)
My concern is that while my phone is listed as M7_UL (m7_unlocked I gather), the CID reads "Roger001". I currently have used the phone only with Virgin Mobile in Canada (Bell Canada's network) and had no problems, but I just want to make sure this won't mess up my radio or make it unusable with my carrier.
I've also gone ahead and backed up all my data from my phone on my computer, and created a nandroid backup as well (although I'm not sure if I could even use the nandroid if things went poorly, because I think I'll be losing custom recovery right?)
Any advice or links to information I might be missing would be greatly appreciated,
Thanks in advance!
EDIT: Also, forgot to mention, my phone is rooted and the bootloader is unlocked.
DorianG said:
Hi there, so I'm looking to flash lollipop to my M7 but first want to verify I've taken the right steps.
Here's my phone's info:
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.00000
RADIO-4A.23.3263.28
OpenDSP-v32.120.274.0909
OS-4.19.631.9
eMMC-boot 2048MB
MID: PN0712000
CID: ROGER001
version-main 4.19.631.9
Now, as far as I'm aware, this is the unlocked edition of the M7. I'm hoping to use this RUU here To flash lollipop onto my phone:
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2.exe (can't post link because I just registered)
My concern is that while my phone is listed as M7_UL (m7_unlocked I gather), the CID reads "Roger001". I currently have used the phone only with Virgin Mobile in Canada (Bell Canada's network) and had no problems, but I just want to make sure this won't mess up my radio or make it unusable with my carrier.
I've also gone ahead and backed up all my data from my phone on my computer, and created a nandroid backup as well (although I'm not sure if I could even use the nandroid if things went poorly, because I think I'll be losing custom recovery right?)
Any advice or links to information I might be missing would be greatly appreciated,
Thanks in advance!
EDIT: Also, forgot to mention, my phone is rooted and the bootloader is unlocked.
Click to expand...
Click to collapse
Nope it won't work, simply because you are s-on, you require 631 RUUs simple as that, you cannot flash a 1540 RUU, however if you go s-off then you can.
M7 UL mean HTC One model 7 not sure what the u stands for, but the L is with LTE support.
You would need to s-off your phone to change the cid and flash the developer firmware in order to flash the developer 1540 ruu, s-off can only be done using sunshine and will cost $25.
DorianG said:
Hi there, so I'm looking to flash lollipop to my M7 but first want to verify I've taken the right steps.
Here's my phone's info:
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.00000
RADIO-4A.23.3263.28
OpenDSP-v32.120.274.0909
OS-4.19.631.9
eMMC-boot 2048MB
MIDN0712000
CID: ROGER001
version-main 4.19.631.9
Now, as far as I'm aware, this is the unlocked edition of the M7. I'm hoping to use this RUU here To flash lollipop onto my phone:
RUU_M7_UL_L50_SENSE60_MR_BrightstarUS_WWE_7.17.1540.7_Radio_4T.35.3218.16_10.33Q.1718.01L_release_420191_signed_2.exe (can't post link because I just registered)
My concern is that while my phone is listed as M7_UL (m7_unlocked I gather), the CID reads "Roger001". I currently have used the phone only with Virgin Mobile in Canada (Bell Canada's network) and had no problems, but I just want to make sure this won't mess up my radio or make it unusable with my carrier.
I've also gone ahead and backed up all my data from my phone on my computer, and created a nandroid backup as well (although I'm not sure if I could even use the nandroid if things went poorly, because I think I'll be losing custom recovery right?)
Any advice or links to information I might be missing would be greatly appreciated,
Thanks in advance!
EDIT: Also, forgot to mention, my phone is rooted and the bootloader is unlocked.
Click to expand...
Click to collapse
1.56 rumrunner S Off
nothing will stop you just change CID BS_US001 and flash ruu
yatindroid said:
1.56 rumrunner S Off
nothing will stop you just change CID BS_US001 and flash ruu
Click to expand...
Click to collapse
So if I S-Off using rumrunner then change my CID to "BS_US001" I can successfully flash the RUU?
The thought of S-Off scares me slightly, can someone confirm that there's no chance that this method will brick my device, and that I won't have any issues with the radio?
DorianG said:
So if I S-Off using rumrunner then change my CID to "BS_US001" I can successfully flash the RUU?
Click to expand...
Click to collapse
Yes with s-off you'll be able to flash the firmware and then the RUU
The thought of S-Off scares me slightly, can someone confirm that there's no chance that this method will brick my device
Click to expand...
Click to collapse
The procedure to s-off itself is not risky, but when s-off is achieved, you'll always have to be careful what you flash. S-OFF remove protection from crucial partitions on your phone and let you flash anything you want without verification. So if you flash something not compatible with your phone, you can brick it.
and that I won't have any issues with the radio?
Click to expand...
Click to collapse
You'll be fine using dev edition on Canadian carriers. I have personally tested on Fido, Rogers, Telus and Koodo. Should work too on Bell/Virgin.
alray said:
Yes with s-off you'll be able to flash the firmware and then the RUU
The procedure to s-off itself is not risky, but when s-off is achieved, you'll always have to be careful what you flash. S-OFF remove protection from crucial partitions on your phone and let you flash anything you want without verification. So if you flash something not compatible with your phone, you can brick it.
You'll be fine using dev edition on Canadian carriers. I have personally tested on Fido, Rogers, Telus and Koodo. Should work too on Bell/Virgin.
Click to expand...
Click to collapse
Great, thanks! In terms of what's compatible, is it pretty much just using common sense, i.e. not flashing a rom meant for the M8 or some other phone, or are there more things that could make something incompatible that I would need to learn about in the future?
Also, the ROM I posted here and intend to flash, it's for sure compatible? Sorry I know I'm probably being a bit overcautious
DorianG said:
Great, thanks! In terms of what's compatible, is it pretty much just using common sense, i.e. not flashing a rom meant for the M8 or some other phone, or are there more things that could make something incompatible that I would need to learn about in the future?
Also, the ROM I posted here and intend to flash, it's for sure compatible? Sorry I know I'm probably being a bit overcautious
Click to expand...
Click to collapse
Yes its safe to use that ruu on your phone.
TO avoid potential brick, always make sure you flash files for
M7_U or M7_UL variant. Files for other variants (e.g M7WLS will brick your phone)
Do not try to flash roms for other phones. We often see ppl bricking their M7 because they have mistakenly flashed an HTC Droid DNA rom on it.
Check MD5 values on your download to make sure your files are not corrupted before flashing <--- important!
Ask questions if you are not sure of the file you want to flash.
---------- Post added at 06:11 PM ---------- Previous post was at 06:09 PM ----------
and if you want to update your firmware, very important:
use a full firmware package
if using firmware package from ota files, they must be flashed incrementally.
alray said:
Yes with s-off you'll be able to flash the firmware and then the RUU.
Click to expand...
Click to collapse
Sorry, one final question. Do I understand you correctly that I need to first flash a new firmware for my phone before using the RUU? If so where would I find this? I originally thought that the RUU would update the firmware for me.
DorianG said:
Sorry, one final question. Do I understand you correctly that I need to first flash a new firmware for my phone before using the RUU? If so where would I find this? I originally thought that the RUU would update the firmware for me.
Click to expand...
Click to collapse
You normally need to be on 6.xx.xxx.x or 7.xx.xxx.x firmware to use the 7.xx.xxx.x RUU. You can try to use it but im pretty sure the ruu will stop at 5% (checking headers). If so, you must flash the firmware first. You can use the 6.07.1540.2 firmware posted in my thread.

HTC One M7 on Android 5.0.2 Sprint help

Just got an HTC One M7 (in red ) . It's the Sprint variant running stock Android 5.0.2. I just finished unlocking the boot loader through HTCDev. I'd like to make a back up of the stock recovery. How can I do this? Here's the results of fastboot getvar all
Code:
version: 0.5
version-bootloader: 1.61.0000
version-baseband: 1.02.20.0922
version-cpld: None
version-microp: None
version-main: 6.23.651.10
version-misc: PVT SHIP S-ON
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 4309mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e2a13e5
hbootpreupdate: 11
gencheckpt: 0
Also, what's the latest TWRP and Root I can install on it? I searched for those too, but the download links are for older versions of the phone or different variants such as the m7_ul. Are those compatible with the version of the M7 that I have? Never messed around with a Sprint phone before and don't want to mess anything up.
And which would be the method of obtaining s-off for this variant? I did some searching and found outdated information for older versions of the phone. Would I need to s-off if I wanted to replace icons for built it apps, change the color of the dialer, and change bootup & shutdown animations? Or can all that be done with s-on?
Also, is it possible to use this variant on the AT&T or T-Mobile network with LTE?
The5thSurvivor said:
Just got an HTC One M7 (in red ) . It's the Sprint variant running stock Android 5.0.2. I just finished unlocking the boot loader through HTCDev. I'd like to make a back up of the stock recovery. How can I do this?
Click to expand...
Click to collapse
You need the phone already s-off to backup the stock recovery. This is done by downgrading hboot to 1.44 so you can use "fastboot boot recovery.img" to boot a custom recovery without flashing it. Then you can backup the untouched /recovery partition using dd commands from the booted recovery. Otherwise the stock recovery can be extracted from a 6.23.651.10 ruu. Anyway the stock recovery is pretty much useless now that the phone is so old: the only thing it will do that twrp can't is installing htc's ota update (this phone will not receive new update)
Also, what's the latest TWRP
Click to expand...
Click to collapse
https://dl.twrp.me/m7wls/
and Root I can install on it?
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
or different variants such as the m7_ul. Are those compatible with the version of the M7 that I have? Never messed around with a Sprint phone before and don't want to mess anything up.
Click to expand...
Click to collapse
m7_ul files are not compatible with the m7wls unless clearly stated in the thread you are downloading from.
And which would be the method of obtaining s-off for this variant?
Click to expand...
Click to collapse
Sunshine S-OFF
Would I need to s-off if I wanted to replace icons for built it apps, change the color of the dialer, and change bootup & shutdown animations? Or can all that be done with s-on?
Click to expand...
Click to collapse
Looks like you don't understand what S-OFF is for, you should stay away from this until you read and understand what S-OFF is. S-OFF is not required to do anything you have asked.
Also, is it possible to use this variant on the AT&T or T-Mobile network with LTE?
Click to expand...
Click to collapse
No, not with LTE. Frequencies are not compatible.
Sorry for the late reply. I've been in and out of the hospital for the past few weeks.
alray said:
You need the phone already s-off to backup the stock recovery. This is done by downgrading hboot to 1.44 so you can use "fastboot boot recovery.img" to boot a custom recovery without flashing it. Then you can backup the untouched /recovery partition using dd commands from the booted recovery. Otherwise the stock recovery can be extracted from a 6.23.651.10 ruu. Anyway the stock recovery is pretty much useless now that the phone is so old: the only thing it will do that twrp can't is installing htc's ota update (this phone will not receive new update)
Click to expand...
Click to collapse
I see. Yeah, I guess it's not worth the hassle then, especially since there will definitely won't be any new ota updates. I'll just grab it from the ruu as you mention :good:
alray said:
https://dl.twrp.me/m7wls/
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Thanks. I'll be sure to try those as soon as I'm back home.
alray said:
m7_ul files are not compatible with the m7wls unless clearly stated in the thread you are downloading from.
Click to expand...
Click to collapse
Gotcha. Things like make me wish that there weren't so many variants of the same phone.
alray said:
Sunshine S-OFF
Looks like you don't understand what S-OFF is for, you should stay away from this until you read and understand what S-OFF is. S-OFF is not required to do anything you have asked.
Click to expand...
Click to collapse
I see. The only phones that I have mangaed to get s-off on were the two HTC Sensations that my girlfriend and I had. It was a pain in the neck to get it to work, but it worked. From what I remember reading, s-off allows you to write to some write protected system partitions. I thought that would be necessary if I wanted to replace icons for built it apps, change the color of the keyboard & dialer, and other stuff. But if s-off is not needed to do any of that, even better However, I'm surprised that there's no other way to obtain s-off besdies Sunshine. I thought I'd have to do something similar to the Sensation phone.
alray said:
No, not with LTE. Frequencies are not compatible.
Click to expand...
Click to collapse
Dang! Will it at least work with 3G?
The5thSurvivor said:
Sorry for the late reply. I've been in and out of the hospital for the past few weeks.
Click to expand...
Click to collapse
Sorry the hear that, hope everything will be ok
I see. The only phones that I have mangaed to get s-off on were the two HTC Sensations that my girlfriend and I had. It was a pain in the neck to get it to work, but it worked. From what I remember reading, s-off allows you to write to some write protected system partitions. I thought that would be necessary if I wanted to replace icons for built it apps, change the color of the keyboard & dialer, and other stuff. But if s-off is not needed to do any of that, even better However, I'm surprised that there's no other way to obtain s-off besdies Sunshine. I thought I'd have to do something similar to the Sensation phone.
Click to expand...
Click to collapse
It was possible to s-off using other methods than sunshine on older hboot versions but now since 1.57 only Sunshine is working.
Dang! Will it at least work with 3G?
Click to expand...
Click to collapse
Depends your carrier bands but irc yes it's possible
I also have this phone i have unlocked bootloader installed twrp recovery from fastboot and rooted with kingoroot, one thing i would like to know if i can sim unlock it by root explorer and modify some files the phone is running 5.0.2.
Sent from my SM-G532M using Tapatalk
alray said:
Sorry the hear that, hope everything will be ok
Click to expand...
Click to collapse
Thank you. Much appreciated :victory:
alray said:
It was possible to s-off using other methods than sunshine on older hboot versions but now since 1.57 only Sunshine is working.
Click to expand...
Click to collapse
Oh boy, looks like I have version 1.61. I supposed I could try downgrading the hboot. What would happen if I did downgrade and the did the s-off, would I be able to upgrade the hboot version and keep the phone with s-off?
alray said:
Depends your carrier bands but irc yes it's possible
Click to expand...
Click to collapse
Then I guess in my case it would be worth it. If I could use this Sprint variant with either AT&T or T-Mobile, that would be fantastic. Thanks!
alray said:
https://dl.twrp.me/m7wls/
Click to expand...
Click to collapse
I'm not able to flash TWRP. It keeps failing. I tried different versions (twrp-3.2.1-0-m7wls.img, twrp-3.1.1-0-m7wls.img, and twrp-2.8.7.0-m7wls.img) and they all fail. I attached an image. I thought after unlocking the bootloader that I could flash a custom recovery. What did I miss?
The5thSurvivor said:
Oh boy, looks like I have version 1.61. I supposed I could try downgrading the hboot. What would happen if I did downgrade and the did the s-off, would I be able to upgrade the hboot version and keep the phone with s-off?
Click to expand...
Click to collapse
Hboot can't be downgraded when S-ON. Nothing can automatically revert a S-Off phone back to S-On (this include hboot update). The only way to set back S-ON is with the appropriate fastboot command.
The5thSurvivor said:
I'm not able to flash TWRP. It keeps failing. I tried different versions (twrp-3.2.1-0-m7wls.img, twrp-3.1.1-0-m7wls.img, and twrp-2.8.7.0-m7wls.img) and they all fail. I attached an image. I thought after unlocking the bootloader that I could flash a custom recovery. What did I miss?
Click to expand...
Click to collapse
Are you sure your BL is unlocked? There shouldn't be any signature verification on the recovery image when the BL is unlocked...
alray said:
Hboot can't be downgraded when S-ON. Nothing can automatically revert a S-Off phone back to S-On (this include hboot update). The only way to set back S-ON is with the appropriate fastboot command.
Click to expand...
Click to collapse
Will keep that in mind :good:
alray said:
Are you sure your BL is unlocked? There shouldn't be any signature verification on the recovery image when the BL is unlocked...
Click to expand...
Click to collapse
Yep, I went through the whole HTCDev process of unlocking it. I just powered it down to go into the bootloader and take a picture of it. As you can see in the attached image, it says: *** UNLOCKED ***
I didn't have this issue with other HTC phones that I unlocked the bootloader as mentioned in this thread. I was able to flash the TWRP recovery of both AT&T variants of the M8 on the first try without issues. I've yet to try the Sprint M8, but will do so later today.
EDIT: I tried a different USB cable and was able to flash TWRP successfully. I immediately did a nandroid backup. I also installed Magisk Manager as per your suggestion. However, I'm not sure as to how I'm supposed to get a stock boot image dump beforehand with the ".img" extension. I thought the nandroid backup would have that, but the boot file is named boot.emmc.win (16MB in filesize). Can I copy that file and rename it with a ".img" extension?
The5thSurvivor said:
Will keep that in mind :good:
Yep, I went through the whole HTCDev process of unlocking it. I just powered it down to go into the bootloader and take a picture of it. As you can see in the attached image, it says: *** UNLOCKED ***
I didn't have this issue with other HTC phones that I unlocked the bootloader as mentioned in this thread. I was able to flash the TWRP recovery of both AT&T variants of the M8 on the first try without issues. I've yet to try the Sprint M8, but will do so later today.
EDIT: I tried a different USB cable and was able to flash TWRP successfully. I immediately did a nandroid backup. I also installed Magisk Manager as per your suggestion. However, I'm not sure as to how I'm supposed to get a stock boot image dump beforehand with the ".img" extension. I thought the nandroid backup would have that, but the boot file is named boot.emmc.win (16MB in filesize). Can I copy that file and rename it with a ".img" extension?
Click to expand...
Click to collapse
Sorry for the delayed answer.
Glad you've found the problem with the cable :good:
Backbup made with twrp will always have the .emmc.win extension. I'm not sure renaming the file with a .img extension will do the trick, I never tried. Attached is the stock boot.img for your firmware version (6.23.651.10)

Categories

Resources