Database Develop

[Q] Not getting any signal

Hi, I have been reading this forum for 2 days straight trying everything and most of the things helped but now I am stuck.
My problem: I am trying to use the phone on Bell network. No signal, GSM status : Emergency Call Only. When I select Bell from network list it tells me that the SIM does not support the Network. If I put the same SIM in another phone it works and gets network.
My phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.06.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3808mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Preffered Network Type : CDMA/EvDo/GSM/WCDMA/LTE auto
CWM: M7 TWRP Nandroid Backup CID BM___001 1.29.666.5
What I did:
1) Tried the tape method in case SIM card was not making proper contact with phone pins. (Than I realized that was nonesense since the phone was detecting my contacts...)
2) Flashed new firmware (6.06.401.1 came with radios nothing changed)
3) Installed the Bell Mobility Nandroid Backup (still nothing except I can now install the Bell applications from my SIM card)
I am looking for suggestions, ideas and possibly solutions. Any help is welcome!
Finxster

finxster said:
Hi, I have been reading this forum for 2 days straight trying everything and most of the things helped but now I am stuck.
My problem: I am trying to use the phone on Bell network. No signal, GSM status : Emergency Call Only. When I select Bell from network list it tells me that the SIM does not support the Network. If I put the same SIM in another phone it works and gets network.
My phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.06.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3808mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Preffered Network Type : CDMA/EvDo/GSM/WCDMA/LTE auto
CWM: M7 TWRP Nandroid Backup CID BM___001 1.29.666.5
What I did:
1) Tried the tape method in case SIM card was not making proper contact with phone pins. (Than I realized that was nonesense since the phone was detecting my contacts...)
2) Flashed new firmware (6.06.401.1 came with radios nothing changed)
3) Installed the Bell Mobility Nandroid Backup (still nothing except I can now install the Bell applications from my SIM card)
I am looking for suggestions, ideas and possibly solutions. Any help is welcome!
Finxster
Click to expand...
Click to collapse
have you tried another sim in the HTC connected to a GSM network, I have a suspicious feeling you have a GSM phone there and Bell requires a CDMA phone, completely different partition layout.

Seanie280672 said:
have you tried another sim in the HTC connected to a GSM network, I have a suspicious feeling you have a GSM phone there and Bell requires a CDMA phone, completely different partition layout.
Click to expand...
Click to collapse
I tried Rogers SIM and it worked one shot.

finxster said:
I tried Rogers SIM and it worked one shot.
Click to expand...
Click to collapse
also, another thing ive noticed, is the firmware you flashed is a 401 firmware, thats WWE Europe, not 100% sure if that maybe at fault
I believe someone recently had success flashing developer edition firmware and RUU on their device and they were on Bell.
I'll see if I can find the thread, EDIT: http://forum.xda-developers.com/htc-one/help/dpes-developers-edition-canada-t2851008
Its got to worth a try, and easy to do as your s-off.

Seanie280672 said:
also, another thing ive noticed, is the firmware you flashed is a 401 firmware, thats WWE Europe, not 100% sure if that maybe at fault
I believe someone recently had success flashing developer edition firmware and RUU on their device and they were on Bell.
I'll see if I can find the thread, EDIT: http://forum.xda-developers.com/htc-one/help/dpes-developers-edition-canada-t2851008
Its got to worth a try, and easy to do as your s-off.
Click to expand...
Click to collapse
Oh dayum that was fast. I am going to try it now and get back to you with results.
Crossing fingers, toes and everything else....
dam harf to ttpe lije ths...
uncrossing fingers....
BRB
EDIT: Changed CID, MID is the same... downloading firmware
EDIT2: Flashed firmware downloading RUU
sidequestion: the RUU name is RUU M7 UL K44 SENSE55 MR BrightstarUS WWE 4.19.1540.9 Radio 4A.23.3263.28 10.38r.1157.04L Release 353887 Signed 3... wouldn't that also be Europe specific @Seanie280672?
Also, I see my HBOOT is now 1.56...

finxster said:
Oh dayum that was fast. I am going to try it now and get back to you with results.
Crossing fingers, toes and everything else....
dam harf to ttpe lije ths...
uncrossing fingers....
BRB
EDIT: Changed CID, MID is the same... downloading firmware
EDIT2: Flashed firmware downloading RUU
Click to expand...
Click to collapse
be sure to check the MD5 and file size of the RUU before flashing, and if the download is a little slow, you can try this link instead, same RUU:
http://androidruu.com/getdownload.p...8_10.38r.1157.04L_release_353887_signed_3.exe
no, WWE means world wide English.

Seanie280672 said:
be sure to check the MD5 and file size of the RUU before flashing
Click to expand...
Click to collapse
File size is 1.5 gb.... How do I check MD5?

finxster said:
File size is 1.5 gb.... How do I check MD5?
Click to expand...
Click to collapse
MD5 Check http://forum.xda-developers.com/showthread.php?t=1135620
i'll keep my fingers crossed for you :fingers-crossed:

Seanie280672 said:
i'll keep my fingers crossed for you :fingers-crossed:
Click to expand...
Click to collapse
They match!
noob question here... What is the command for fastboot to run an exe?
Nvm... >.> figured it out...

finxster said:
They match!
noob question here... What is the command for fastboot to run an exe?
Click to expand...
Click to collapse
there isn't one.
plug your phone into the computer and make sure it says fastboot USB on the screen, then double click the RUU.exe file and it will launch, follow the on screen instructions, flashing takes quite a while, about 10 mins I think mine took, and at points it will look like its stuck, not very reassuring I know, it got stuck at 5% for me and then suddenly jumped to 95%, then seemed to sit there forever until it finally completed.
EDIT: is your Bell sim still in the phone ?

@Seanie280672 Yep bell sim still in phone. Installing now

finxster said:
@Seanie280672 Yep bell sim still in phone. Installing now
Click to expand...
Click to collapse
good, because during set-up it should detect your sim and ask you to select your operator, im hoping Bell is in the list.

Seanie280672 said:
good, because during set-up it should detect your sim and ask you to select your operator, im hoping Bell is in the list.
Click to expand...
Click to collapse
It prepared installation and when I agreed and clicked next... it closed... I was running it as admin....

finxster said:
It prepared installation and when I agreed and clicked next... it closed... I was running it as admin....
Click to expand...
Click to collapse
damn, I had that problem once, its not the RUU at fault, its your computer, this is how I fixed it, its a bit long winded and you have to restart your computer after each installation, you need to install all of them one at a time, or you can try another computer if you have one available.
http://forums.androidcentral.com/ht...tall-4-3-ruu-windows-7-8-1-a.html#post3466555

I want to take a minute and thank you @Seanie280672!!! I am going to go ahead and try it... I do however have another pc next to me so I will try running the RUU from that one in the meanwhile.

finxster said:
I want to take a minute and thank you @Seanie280672!!! I am going to go ahead and try it... I do however have another pc next to me so I will try running the RUU from that one in the meanwhile.
Click to expand...
Click to collapse
your welcome, but don't thank me yet, its not worked yet, im just sharing my knowledge which ive learned from others on this great forum.

Seanie280672 said:
damn, I had that problem once, its not the RUU at fault, its your computer, this is how I fixed it, its a bit long winded and you have to restart your computer after each installation, you need to install all of them one at a time, or you can try another computer if you have one available.
http://forums.androidcentral.com/ht...tall-4-3-ruu-windows-7-8-1-a.html#post3466555
Click to expand...
Click to collapse
So, I got it to run on my main PC but there is a dialog box that makes me skip all the steps... will try on the laptop
Same on my laptop... ARUWizard Click here to next dialog... and I can't do anything else... clicking ok until the program is killed

finxster said:
So, I got it to run on my main PC but there is a dialog box that makes me skip all the steps... will try on the laptop
Same on my laptop... ARUWizard Click here to next dialog... and I can't do anything else... clicking ok until the program is killed
Click to expand...
Click to collapse
ive never seen that error before, but this would maybe explain it: http://www.solvusoft.com/en/files/e...windows/htc/rom-update-utility/aruwizard-exe/

http://forum.xda-developers.com/showthread.php?t=2666090
He has the same issue, however I am in bootloader fastboot usb mode... and still nothing... should I try RUU mode?
@Seanie280672

finxster said:
http://forum.xda-developers.com/showthread.php?t=2666090
He has the same issue, however I am in bootloader fastboot usb mode... and still nothing... should I try RUU mode?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=50739768&postcount=4

[Q] One M7 GPE 5.0.1 No IMEI, Baseband

Hi everyone,
So, I upgraded my wifes M7 to a 4.4.4 GPE ROM from a Rogers stock ROM. I unlocked the bootloader from HTCDev and then got S-OFF with firewater. All went swimmingly, until we got the two OTAs for Lollipop. About 4 days ago, the service went out on the phone. In settings, there is no IMEI or Baseband listed, they both say unknown. I checked in fastboot with the getvar all command and the IMEI is there. I tried flashing the radio from the 5.0.1 OTA file, but it says "command rejected" to which it SOUNDS like my S-OFF isn't there anymore, even though the getvar and fastboot screen show it S-OFF.
Here is the getvar output:
C:\Users\Jeff>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: H**************
(bootloader) imei: 3************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3848mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.114s
So, where do I go from here... It's pretty coincidental that this happened RIGHT around the time that the M7s had the audio bug, but this doesn't sound like the same issue. I think reflashing the radio would work, but it keeps kicking me back, and I've read around here and am unsure of how to re-SOFF the phone. Any help would be appreciated. My wife is not beyond putting the Rogers RUU back on and just waiting for an official GTC update to Lollipop... if that's easier.
Thanks everyone.

First of all try to wipe all phone(full stock reset) and install android gpe 5.0.1 in recovery(you can find it on forum easy) than write me and say if you still have wrong baseband and imei(also probably your phone is not abble to read simcard numbers?)

If fastboot displays the proper imei, best guesses sounds like there is something wrong with the rom or radio that is causing it to report the incorrect imei.
If you have a custom recovery installed (since it appears you are s-off) you could just backup that current rom, wipe/factory reset it to see if it works and if it was something that borked up during the update.
If it still reports the incorrect imei after factory reset, try flashing some known working rom (cm11, omni, etc) and see if everything's working fine in there. Restore your backup after you are done.
That would confirm it's a software-related issue and you can proceed from there.

Tried Factory Reset
So I tried a factory reset from fastboot... no nice. I actually have the stock recovery on the unit so I could receive OTAs from google and not have to jigger around with anything (since it's my wifes phone) ... I THINK I'm S-OFF, but the fact that I couldn't flash a radio.img file in fastboot has me worried that the 5.0.1 update may have partially rescinded it, and I don't want to make things worse by something borking in the middle of a flash.
Would an RUU be the way to go here? Or just try stuffing TWRP onto it and try CM11 ...

if you confirm it's soff, or just even htcdev unlocked (as fastboot would say) you can always flash back stock recovery if you decide to change your mind.
You can extract the recovery img from a working stock rom/ruu, in the meantime flashing twrp/philz opens you for advanced recovery options.
You just flash the recovery in fastboot mode.
fastboot flash recovery twrp-etc.img
fastboot flash recovery nameofstockhtcrecovery.img
As for the radio, not sure what to say. Perhaps try extracting it (from your update file if possible) and flash it from there?

Still no dice
So I flashed TWRP and CM11 ... still no baseband or IMEI. I found a few flashable zips for radio images and still nothing.
I relocked my bootloader, and tried to push a Rogers RUU signed exe, to which I got Error 158 Image Error. No other information is given. I am going down in versions, but as far as I can see, my S-OFF is still in effect.

ssign said:
So I flashed TWRP and CM11 ... still no baseband or IMEI. I found a few flashable zips for radio images and still nothing.
I relocked my bootloader, and tried to push a Rogers RUU signed exe, to which I got Error 158 Image Error. No other information is given. I am going down in versions, but as far as I can see, my S-OFF is still in effect.
Click to expand...
Click to collapse
fastboot oem writecid 11111111
Now you can flash any RUU
Flash your Rogers RUU (after you confirm the md5 matches), and report back :good:

Update: Cannot flash RUU
Hi Again,
So I set SuperCID and tried to reflash the RUU. It got a little further, but hung on the "checking headers" but for almost an hour... so I reset the phone since I had to leave for XMas plans. Now, it gives me an error 155 Image Error when I try to use it. I've seen elsewhere that might need to downgrade my hboot? Since I'm on 1.57.0000? Any ideas about that? Thanks

[Q] Allllrighty then - no touchscreen after firmware flash

So it's been a good few days with my M7 given to me by a friend. I am totally new at the whole custom ROM thing but had no problems with root, unlock, s-off, etc. but took me many hours as I've rarely used Cmd functions. Still have stock 4.1.2 sense 5.0. Time to move forward so ..... downloaded TWRP and ROM Installer, etc. Decided to update firmware next as some ROMs need later and lost touchscreen function. No other issues, boots fine into whatever and recovers into TWERP with full function of touchscreen. Should I flash older firmware or can I loaded newer ROM through TWERP to get back in the game ? need to answer calls and texts at some point soon !

biggerdog said:
So it's been a good few days with my M7 given to me by a friend. I am totally new at the whole custom ROM thing but had no problems with root, unlock, s-off, etc. but took me many hours as I've rarely used Cmd functions. Still have stock 4.1.2 sense 5.0. Time to move forward so ..... downloaded TWRP and ROM Installer, etc. Decided to update firmware next as some ROMs need later and lost touchscreen function. No other issues, boots fine into whatever and recovers into TWERP with full function of touchscreen. Should I flash older firmware or can I loaded newer ROM through TWERP to get back in the game ? need to answer calls and texts at some point soon !
Click to expand...
Click to collapse
If you have Stock 4.1.2 rom and the latest firmware that's almost certainly your problem. But rather than flashing older firmware why not flash a newer rom ?

Danny201281 said:
If you have Stock 4.1.2 rom and the latest firmware that's almost certainly your problem. But rather than flashing older firmware why not flash a newer rom ?
Click to expand...
Click to collapse
Exactly what I was intending to do anyway which was reason for firmware upgrade (guess I put the cart before the horse 1) , can I do this through TWRP ? Do I download said ROM on my laptop and copy to directory on phone then load through TWRP ? Thanks for your help. As i stated , this is all new territory to me ....... any guidance appreciated (or links to assist) thanks.

biggerdog said:
Exactly what I was intending to do anyway which was reason for firmware upgrade (guess I put the cart before the horse 1) , can I do this through TWRP ? Do I download said ROM on my laptop and copy to directory on phone then load through TWRP ? Thanks for your help. As i stated , this is all new territory to me ....... any guidance appreciated (or links to assist) thanks.
Click to expand...
Click to collapse
Can you post the out put of
Code:
fastboot getvar all
Please remove your imei and serial numbers before posting.
What sort of rom are you looking for Stock or Custom?

Danny201281 said:
Can you post the out put of
Code:
fastboot getvar all
Please remove your imei and serial numbers before posting.
What sort of rom are you looking for Stock or Custom?
Click to expand...
Click to collapse
give me few minutes , I have not decided on a rom , just wasn't getting OTA updates from ATT so figured I'd take matters into my own hands ! Kinda wanted sense 6 , other than that , open to suggestions .........

Here we go :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.06.401.1
(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: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s

biggerdog said:
Here we go :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.06.401.1
(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: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4218mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
Click to expand...
Click to collapse
Ok start with this http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_84.0.zip
Android Kitkat 4.4.3 Sense 6
Download the rom and put the file in your fastboot folder on your PC and rename it rom.zip. Boot to TWRP recovery (2.6.3.3 Recommended) and connect your usb cable. Check adb is working with
Code:
adb devices
If you get the expected out put
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push is complete. Factory reset and install the rom from TWRP

Gotta ask a quick question , just curious. I cannot download the rom onto PC then drag to folder on the phone then install through TWRP ? Not questioning method and advice given , just thinking as I have no experience and seems like it would do the same, but I wouldn't know ! I will proceed through command prompt as recommended for now .....

biggerdog said:
Gotta ask a quick question , just curious. I cannot download the rom onto PC then drag to folder on the phone then install through TWRP ? Not questioning method and advice given , just thinking as I have no experience and seems like it would do the same, but I wouldn't know ! I will proceed through command prompt as recommended for now .....
Click to expand...
Click to collapse
Yes with TWRP 2.8.4.0 you can just copy the file to the phone in windows .. no need to push as TWRP supports MTP now

clsA said:
Yes with TWRP 2.8.4.0 you can just copy the file to the phone in windows .. no need to push as TWRP supports MTP now
Click to expand...
Click to collapse
Awesome. As stated, all was well until flashing firmware 6.06.401.1 which may have been too big of a jump for my stock 4.1.2. The flash showed successful and went fine but I've read elsewhere that I should have been "relocked" before flashing , then unlocked after ? I am not seeing this step on all instructions ( I followed this : http://forum.xda-developers.com/showthread.php?t=2485651 ) Also didn't verify model ID (PN0712000) , may need to find a different firmware and re-flash ? Never got errors , just lost touch screen (which sounds common). Thanks all , hittin' the sack as this download from Android Rev is taking forever (need a torrent) ! Goodnight and thanks for feedback to come (something to look forward to in the AM).

biggerdog said:
Awesome. As stated, all was well until flashing firmware 6.06.401.1 which may have been too big of a jump for my stock 4.1.2. The flash showed successful and went fine but I've read elsewhere that I should have been "relocked" before flashing , then unlocked after ? I am not seeing this step on all instructions ( I followed this : http://forum.xda-developers.com/showthread.php?t=2485651 ) Also didn't verify model ID (PN0712000) , may need to find a different firmware and re-flash ? Never got errors , just lost touch screen (which sounds common). Thanks all , hittin' the sack as this download from Android Rev is taking forever (need a torrent) ! Goodnight and thanks for feedback to come (something to look forward to in the AM).
Click to expand...
Click to collapse
Well you could always change your CiD to Dev Edition and flash the Dev Edition firmware. And no you do not need to relock your bootloader to flash firmware, That is only for S-on users. Your phone is s-off :good:
The problem with the touch screen will be the big gap between firmware and rom. think of it like using Window 8 with Windows 95 Drivers

Danny201281 said:
Well you could always change your CiD to Dev Edition and flash the Dev Edition firmware. And no you do not need to relock your bootloader to flash firmware, That is only for S-on users. Your phone is s-off :good:
The problem with the touch screen will be the big gap between firmware and rom. think of it like using Window 8 with Windows 95 Drivers
Click to expand...
Click to collapse
Would you have a "how to" link on the steps to do this that you trust ? I'm sure I could search as well but want to proceed correctly as I'm about there !

biggerdog said:
Would you have a "how to" link on the steps to do this that you trust ? I'm sure I could search as well but want to proceed correctly as I'm about there !
Click to expand...
Click to collapse
look here
http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11

clsA said:
look here
http://forum.xda-developers.com/showpost.php?p=58087799&postcount=11
Click to expand...
Click to collapse
Thanks all - everything up and running. Didn't go developer but may consider if there are any real advantages (I would assume only if running stock, correct ?) Not sure when they'll be releasing Lollipop for this M7 but supposedly soon

HTC One M7 Stock Recovery Backup

Hi Guys
Im new here so I hope I wont mess things up too bad, by posting something in the wrong place or something like that
I have a question about my Htc One M7 and I have been googling all day and either there is no easy solution or I am not able to find it...
So hopefully you can help me
My Htc One is at the moment completely stock. All I did was unlocking the bootloader as described by the htc-dev website.
I want to make a backup of my Stock Recovery, before I flash a custom one.
I tried to use this Guide: http://forum.xda-developers.com/showthread.php?t=2265618 to achieve that.
In step 7/8 it states ("In the Command Prompt type following command: fastboot boot recovery.img (this command might not with newer hboots)") that I should be able to boot a recovery without flashing it. But it also says that it might not work with higher hboots.
It seems that it wont work with my Hboot 1.56
Now my actual question: Is there any way to make a backup of the 100% Stock Recovery?
And please dont give me a link where i can download one, i would like to create a backup myself
If you find anything that is wrong with this post (spelling, location or somthing), please let me know.
Thank you for your help

hahamuntz said:
Hi Guys
Im new here so I hope I wont mess things up too bad, by posting something in the wrong place or something like that
I have a question about my Htc One M7 and I have been googling all day and either there is no easy solution or I am not able to find it...
So hopefully you can help me
My Htc One is at the moment completely stock. All I did was unlocking the bootloader as described by the htc-dev website.
I want to make a backup of my Stock Recovery, before I flash a custom one.
I tried to use this Guide: http://forum.xda-developers.com/showthread.php?t=2265618 to achieve that.
In step 7/8 it states ("In the Command Prompt type following command: fastboot boot recovery.img (this command might not with newer hboots)") that I should be able to boot a recovery without flashing it. But it also says that it might not work with higher hboots.
It seems that it wont work with my Hboot 1.56
Click to expand...
Click to collapse
You can only use the "fastboot boot recovery.img" command on hboot 1.44. So if you absolutely want to backup the stock recovery using this method you'll need s-off in order to downgrade your hboot so you can boot a custom recovery without flashing it to dump the stock one, not very convenient... Stock recovery can be extracted from the ota update zip file of the same version your phone is running, this is the method used by everyone if their stock recovery.img is not already available to download here on xda.
Now my actual question: Is there any way to make a backup of the 100% Stock Recovery?
Click to expand...
Click to collapse
Yes but not convenient at all like said above, I already did it once, just because the ota update zip file was encrypted and so it was impossible to extract the recovery directly from the ota so I had to pull it directly from the phone: http://forum.xda-developers.com/showpost.php?p=54167697&postcount=1095
And please dont give me a link where i can download one, i would like to create a backup myself
Click to expand...
Click to collapse
Can't give you any link to download your recovery anyway since we don't know what firmware version your phone is running.

alray said:
You can only use the "fastboot boot recovery.img" command on hboot 1.44. So if you absolutely want to backup the stock recovery using this method you'll need s-off in order to downgrade your hboot so you can boot a custom recovery without flashing it to dump the stock one, not very convenient... Stock recovery can be extracted from the ota update zip file of the same version your phone is running, this is the method used by everyone if their stock recovery.img is not already available to download here on xda.
Yes but not convenient at all like said above, I already did it once, just because the ota update zip file was encrypted and so it was impossible to extract the recovery directly from the ota so I had to pull it directly from the phone: http://forum.xda-developers.com/showpost.php?p=54167697&postcount=1095
Can't give you any link to download your recovery anyway since we don't know what firmware version your phone is running.
Click to expand...
Click to collapse
Thank you for your quick answer
It doesn't have to be this way, I just want to create my own backup of Stock Rom and Stock Recovery. If their is a way to extract it from an ota update, I would gladly use this method. Do you know a good guide, that explains how to do that? And could I do that with the current version of Android running on the Phone? Update sounds like I would have to update it first?

hahamuntz said:
Thank you for your quick answer
It doesn't have to be this way, I just want to create my own backup of Stock Rom and Stock Recovery. If their is a way to extract it from an ota update, I would gladly use this method. Do you know a good guide, that explains how to do that? And could I do that with the current version of Android running on the Phone? Update sounds like I would have to update it first?
Click to expand...
Click to collapse
To extract the stock recovery from an update update, simply open the zip file, inside you'll find another zip file named "firmware.zip" open that one and extract the recovery.img file.
what is your firmware version? "fastboot getvar version-main"

alray said:
To extract the stock recovery from an update update, simply open the zip file, inside you'll find another zip file named "firmware.zip" open that one and extract the recovery.img file.
what is your firmware version? "fastboot getvar version-main"
Click to expand...
Click to collapse
Im running 4.19.401.11
How do I get the ota.zip file? Is there a way to extract that from my Phone?

hahamuntz said:
Im running 4.19.401.11
How do I get the ota.zip file? Is there a way to extract that from my Phone?
Click to expand...
Click to collapse
You can get the ota zip file when downloading an update and selecting "install later". Once the download is completed, connect your phone to your computer and copy the ota zip file from your download folder to your computer. Once the update is installed, the ota zip file is deleted form the phone so you can't extract the update from the phone since its already installed.
You can find the ota update file for your version (from 4.19.401.9 to 4.19.401.11) here: https://www.androidfilehost.com/?fid=95747613655045071
Or directly download the 4.19.401.11 stock recovery here: https://www.androidfilehost.com/?fid=95864024717070740 which is the same exact recovery installed on your phone.

alray said:
You can get the ota zip file when downloading an update and selecting "install later". Once the download is completed, connect your phone to your computer and copy the ota zip file from your download folder to your computer. Once the update is installed, the ota zip file is deleted form the phone so you can't extract the update from the phone since its already installed.
Click to expand...
Click to collapse
I think i did it. Thank you very much!
there is the firmware folder with 9 .img files in it seems to be right, altough I can't open the zip folder directly (it says error- Folder invalid), but it worked when I extracted the Folder...
The 9 .img files are about 100 MB, is that right?
And could I apply the same update to my second HTC One M7( running a rooted Stock with Android 5.0.2), to get it back to Stock Rom and Recovery?
What do I have to check to make sure they are compatible?

hahamuntz said:
I think i did it. Thank you very much!
there is the firmware folder with 9 .img files in it seems to be right, altough I can't open the zip folder directly (it says error- Folder invalid), but it worked when I extracted the Folder...
The 9 .img files are about 100 MB, is that right?
Click to expand...
Click to collapse
The stock recovery should be around 12MB not 100MB,
And could I apply the same update to my second HTC One M7( running a rooted Stock with Android 5.0.2), to get it back to Stock Rom and Recovery?
What do I have to check to make sure they are compatible?
Click to expand...
Click to collapse
No, this recovery is only for 4.19.401.11 and that update file is for patching 4.19.401.09 to 4.19.401.11 only.

alray said:
The stock recovery should be around 12MB not 100MB, .
Click to expand...
Click to collapse
Sorry i didn't say that well... All of the .img files in this folder together are about 100 MB.
The Recovery itself is only 12 MB, so it seems fine
alray said:
No, this recovery is only for 4.19.401.11 and that update file is for patching 4.19.401.09 to 4.19.401.11 only.
Click to expand...
Click to collapse
Okay, but if I would install the update and make a Nandroid backup of the updated Rom, would I be able to install that Nandroid backup also on the second Phone?
And would I be able to use the recoverybackup I received out of the OTA.zip to restore the first Phone to StockRecovery if I flashed a custom Recovery after I updated?

hahamuntz said:
Sorry i didn't say that well... All of the .img files in this folder together are about 100 MB.
The Recovery itself is only 12 MB, so it seems fine
Click to expand...
Click to collapse
Yes that seems fine.
Okay, but if I would install the update and make a Nandroid backup of the updated Rom, would I be able to install that Nandroid backup also on the second Phone?
If I understand correctly, you'll update phone #1 then make a nandroid backup
And would I be able to use the recoverybackup I received out of the OTA.zip to restore the first Phone to StockRecovery if I flashed a custom Recovery after I updated?
Click to expand...
Click to collapse
I'm not sure if I should answer this one before knowing the details (fastboot getvar all) of the second phone and knowing what is your goal exactly. That might only brings more confusion and there might be easier solution to restore your phone than creating a backup from device A and restoring it to B...
But yes its possible, you want to make sure your recovery version, software version and firmware version match together. E.G You don't want to restore a 4.19.401.11 software backup on a phone running a different firmware version and the recovery version must also match. So if phone B is 7.19.401.22 firmware you want to restore a 7.19.401.22 software and a 7.19.401.22 stock recovery. If you have updated phone A from 4.19.401.11 to 7.19.401.22 and then make a backup of it, you should be fine restoring that backup on phone B. Any mismatch between version will prevent installation of ota updates and in some case you can have drivers issues.

alray said:
I'm not sure if I should answer this one before knowing the details (fastboot getvar all) of the second phone and knowing what is your goal exactly. That might only brings more confusion and there might be easier solution to restore your phone than creating a backup from device A and restoring it to B...
But yes its possible, you want to make sure your recovery version, software version and firmware version match together. E.G You don't want to restore a 4.19.401.11 software backup on a phone running a different firmware version and the recovery version must also match. So if phone B is 7.19.401.22 firmware you want to restore a 7.19.401.22 software and a 7.19.401.22 stock recovery. If you have updated phone A from 4.19.401.11 to 7.19.401.22 and then make a backup of it, you should be fine restoring that backup on phone B. Any mismatch between version will prevent installation of ota updates and in some case you can have drivers issues.
Click to expand...
Click to collapse
First Phone:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(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: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4287mV
(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!
Second Phone:
Code:
(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.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3869mV
(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
all: Done!
What I wanna do is to use the first phone to create my own Backup of ROM and Recovery to get the second phone to the newest Version of stock.
Is this possible with these pair of Phones?
And could you recommend me a good website were I could learn what all these variables mean? an were I could learn more about this topic?

hahamuntz said:
First Phone:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(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: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4287mV
(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!
Second Phone:
Code:
(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.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3869mV
(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
all: Done!
What I wanna do is to use the first phone to create my own Backup of ROM and Recovery to get the second phone to the newest Version of stock.
Click to expand...
Click to collapse
Well the second phone can simply be updated to the latest version by flashing the 7.19.401.22 ruu and then taking one ota update to 7.19.401.30 which is the latest version.
The first phone can also be updated to the latest version by flashing the 7.19.401.2 firmware first and then doing the same thing, flashing the 7.19.401.22 ruu and then taking one ota update to 7.19.401.30. Simple and easy unlike what you are trying to do
And could you recommend me a good website were I could learn what all these variables mean? an were I could learn more about this topic?
Click to expand...
Click to collapse
Here is the essential:
(bootloader) version-bootloader: This is your bootloader version, sometime called hboot
(bootloader) version-baseband: This is your radio version, radio is the software that controls the reception/transmission. Different carriers/region will requires different radio version because of different infrastructures.
(bootloader) version-main: This is your firmware version, the firmware is the code that make possible the interaction between the software and the hardware.
(bootloader) serialno: Serial number of your phone, don't share this number on the forum
(bootloader) imei: IMEI number is a unique number identifier for GSM networks, for example if your phone is declared lost/stolen or linked to unpaid bills, this number will be added to an international blacklist and you won't be able to use your phone on any carrier worldwide. Don't share this number on the forum.
(bootloader) meid: MEID is the same as IMEI but for CDMA phones, on GSM phone you don't have an MEID (only showing 0)
(bootloader) product: This is your product code, M7_UL means its a M7, U = GSM, L= LTE so its a M7 GSM/LTE
(bootloader) modelid: Model ID (MID) is a little like the product code but more specific to your region. For example, PN0710000 = M7_UL Europe. PN0712000 is also a M7_UL but for North America (all Canadian carriers, USA's AT&T, Google Play Edition and US developer edition)
(bootloader) cidnum: CID is the carrier / region ID
(bootloader) security: Security ON/OFF. Read about s-on/s-off here

alray said:
Well the second phone can simply be updated to the latest version by flashing the 7.19.401.22 ruu and then taking one ota update to 7.19.401.30 which is the latest version.
The first phone can also be updated to the latest version by flashing the 7.19.401.2 firmware first and then doing the same thing, flashing the 7.19.401.22 ruu and then taking one ota update to 7.19.401.30. Simple and easy unlike what you are trying to do
Click to expand...
Click to collapse
How would I know if these are compatible?
I would rather not use some download from the Internet because I afraid that somebody messed it up and I won't get the 100% Stock, maybe even an infected one. (Is this even a rational fear? )
That's why I am trying to create all the necessary resources myself, so I can be sure that they are alright. Also I learn much more if I do it step by step instead of just flashing a Rom from the web.
For example how do I check if a Rom is compatible with my device?
alray said:
(bootloader) serialno: Serial number of your phone, don't share this number on the forum
(bootloader) imei: IMEI number is a unique number identifier for GSM networks, for example if your phone is declared lost/stolen or linked to unpaid bills, this number will be added to an international blacklist and you won't be able to use your phone on any carrier worldwide. Don't share this number on the forum.
Click to expand...
Click to collapse
Is the other stuff save to share?

hahamuntz said:
How would I know if these are compatible?
I would rather not use some download from the Internet because I afraid that somebody messed it up and I won't get the 100% Stock, maybe even an infected one. (Is this even a rational fear? )
Click to expand...
Click to collapse
Not really since the RUU are offical (from HTC) and also they are encrypted with HTC private key .The 7.19.401.22 ruu was uploaded by me as you can see here. :good: So there is nothing to fear. Then the 7.19.401.30 ota update will come directly from HTC's servers so again, nothing to fear.
That's why I am trying to create all the necessary resources myself, so I can be sure that they are alright.
Click to expand...
Click to collapse
No offense, but these ruu are probably more reliable than what you are trying to do + easier to achieve your goal.
Also I learn much more if I do it step by step instead of just flashing a Rom from the web.
Click to expand...
Click to collapse
+1 for learning
For example how do I check if a Rom is compatible with my device?
Click to expand...
Click to collapse
First you have a M7_UL (GSM variant) so make sure you are only flashing M7 GSM stuff (rom, recovery, kernel etc). Also read the rom thread to see if you have all the pre-requisite before flashing a rom, for example, lollipop roms requires at least a 7.xx.xxx.x firmware to work correctly so it would work fine on phone B but not on phone A. Another example: CyanogenMod roms requires at least TWRP recovery 2.7.1.1, using anything below that will not work. Thats why you should always read the first post of the thread from the rom you want to flash before proceeding. If you are unsure after reading, better to ask questions instead of (soft) bricking,

So can I flash the 7.19.401.22 from you directly on phone B? And then update over the official server? Then Phone B is completely stock and with the newest version?
If understood the whole s-off/ s-on that you posted, I only can flash the official RUUs on Phone B with s-on?
I think after that I understood everything for now thank you very much!
Do you have a good source where I can read about this whole topic? I need something like an encyclopedia with explanations, that are not completely basic but easy enough for me to understand

hahamuntz said:
So can I flash the 7.19.401.22 from you directly on phone B? And then update over the official server? Then Phone B is completely stock and with the newest version?
Click to expand...
Click to collapse
Yes you can and btw the ruu is not from me, I have uploaded it but its an official RUU from HTC.
If understood the whole s-off/ s-on that you posted, I only can flash the official RUUs on Phone B with s-on?
Click to expand...
Click to collapse
You can also flash the RUU on Phone A but you will need to update its firmware first since its too old to accept the 7.19.401.2 ruu
Do you have a good source where I can read about this whole topic? I need something like an encyclopedia with explanations, that are not completely basic but easy enough for me to understand
Click to expand...
Click to collapse
About what? flashing RUU?
Btw, you'll find instructions how to flash the ruu here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 (see post #1)

I meant to ask if it is correct that I can only Flash official RUUs while on S-On?
I mean something like a collection of Information about all the terms used around flashing and rooting.
At the moment I just google everything I don't understand/know, but I would like to understand it all completely. Is there something like a guide, that doesn't only say " Do this and then do that" but also explains why I should do this and what exactly I am doing.

alray said:
Btw, you'll find instructions how to flash the ruu here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 (see post #1)
Click to expand...
Click to collapse
Thanks, can I flash everything from there that has my CID? Or do I have to look out for something else?
And while I am doing this, could I switch from Sense to the Google Play Edition on Phone B?

hahamuntz said:
Thanks, can I flash everything from there that has my CID? Or do I have to look out for something else?
Click to expand...
Click to collapse
As long as the rom you want to flash is for a M7_UL you should be able to flash it, CID is more important when you want to flash a RUU.
And while I am doing this, could I switch from Sense to the Google Play Edition on Phone B?
Click to expand...
Click to collapse
Using a custom GPE rom yes its possible, using a GPE RUU no because the phone is S-ON and flashing the GPE ruu would requires to change the phone CID/MID (s-off needed)

alray said:
As long as the rom you want to flash is for a M7_UL you should be able to flash it, CID is more important when you want to flash a RUU.
Click to expand...
Click to collapse
So could I flash this Rom, although it says its for Gsm or would I lose my ability to use lte?
(http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927)
Is this even the correct Rom if I want the complete stock gpe? And if flash the unrooted version would I be able to root it in a second step (Easier for me to learn the stuff, then just flashing a rooted Rom)
alray said:
Using a custom GPE rom yes its possible, using a GPE RUU no because the phone is S-ON and flashing the GPE ruu would requires to change the phone CID/MID (s-off needed)
Click to expand...
Click to collapse
I think I understood it wrong... I thought the Ruu is a part of a Rom? Used to verify if it is official or not?
Do you know a collection of Information about all the terms used around flashing and rooting.
At the moment I just google everything I don't understand/know, but I would like to understand it all completely. Is there something like a guide, that doesn't only say " Do this and then do that" but also explains why I should do this and what exactly I am doing.

Failing to Flash / Locate RUU on M7

Hey Guys -
This morning I've spent some time trying to convert my HTC One M7 from AT&T to T-Mobile (both USA) so that I may use a new T-Mobile SIM I have. I already had S-Off, so it looked like a fairly simple process. Unfortunatly, I've hit a roadblock and after searching cannot find the solution. I believe the biggest issue is due to htc1guru.com being down which I do not know if due to the DOS attack in Atlanta or not - Anyways - below is what I've done so far, where i hit the error, and current status of the phone...
Phone's Original State
I should have run a getvar for this first, but copied all info from a pic I took before starting of the bootloader screen
HTC One M7 flashed with ViperOne 9.0.0 on AT&T USA (GSM)
- M7_UL PVT SHIP S-OFF RH
- S-Off / Rooted
- CID: CWS__001
- HBOOT: 1.61.0000
- RADIO: 4M.32.3218.06
- OpenDSP: v35.120.274.0718
- OS: 7.23.502.1
Steps I Followed to Convert Carrier to T-Mobile
I found and used this guide mostly as it seemed to do exactly what I was trying to do
1. Changed CID to "T-MOB010"
2. Flashed "MID_Change_1.01.zip" via TWRP and choose to install Model ID "PN0713000" - Rebooted
3. Skipped step for re-locking bootloader
4. htc1guru.com was offline so had to find RUU elsewhere. So, I finally found and downloaded "RUU_M7_UL_JB_50_TMOUS_1.27.531.11_Radio_4A.17.3250.20_10.40.1150.04_release_324846_signed.exe" from androidruu.com.
5. Executed above EXE, went to %temp%, and copied "rom.zip" out to my adb folder
6. Ran "adb reboot bootloader" then "fastboot oem rebootRUU" to get to silver HTC logo
7. Executed "fastboot flash zip rom.zip" which failed with below error. I tried re-running the string, but got the same results
Current Error
When executing step #7 above
Code:
C:\adb>fastboot flash zip ruu.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1037365 KB)...
OKAY [ 41.799s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 22 loading zip info fail
Please check if you flash part)
finished. total time: 47.542s
Current Phone Status
Below are the current settings for my M7 which I just pulled via "fastboot getvar all" before posting...
Code:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4M.32.3218.06
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.23.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT35ZW914588
(bootloader) imei: 354439051018051
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3864mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 4.782s
The Issue? / Overall
I'm pretty sure that the error is due to the rom.zip not being what I need to flash. I've found plenty of links for the rom/ruu that should work for my situation, but they are all on htc1guru.com. If I power on the phone in it's current state with the (new / never used) T-Mobile SIM in, I am prompted to enter an 8 digit PIN which I assume I would need to call T-Mobile for and activate first. Based on what I'm trying to do, the error, and the above data; what do I need to do? If it is in fact an incorrect rom/ruu file, does anyone have a link to it on another site or can tell me which specific one I need to look for?
Thanks for your help!!!

Try the link on OP for latest Ruu it may help. http://forum.xda-developers.com/showthread.php?p=59353567

Toqeer said:
Try the link on OP for latest Ruu it may help. http://forum.xda-developers.com/showthread.php?p=59353567
Click to expand...
Click to collapse
Thanks - downloading now. So this is obviously an installable one. Do you suggest I try to install it via the EXE / built-in installer, extract the rom.zip and apply using steps above, or does it even matter? I don't care if I loose any data on the phone.
Thanks!

bzowk said:
Hey Guys -
This morning I've spent some time trying to convert my HTC One M7 from AT&T to T-Mobile (both USA) so that I may use a new T-Mobile SIM I have.
Click to expand...
Click to collapse
Converting your phone from AT&T to T-Mobile USA version won't make it work with a T-Mobile SIM card. You have to SIM-Unlock your phone. Even if you flash a T-MOB ruu, your phone will still be locked to AT&T and ask you for an unlock code.

alray said:
Converting your phone from AT&T to T-Mobile USA version won't make it work with a T-Mobile SIM card. You have to SIM-Unlock your phone. Even if you flash a T-MOB ruu, your phone will still be locked to AT&T and ask you for an unlock code.
Click to expand...
Click to collapse
Well crap. What's the process for in the guide I posted a link to in my original post, then? What more do I need to do in order to SIM-Unlock it?

bzowk said:
Thanks - downloading now. So this is obviously an installable one. Do you suggest I try to install it via the EXE / built-in installer, extract the rom.zip and apply using steps above, or does it even matter? I don't care if I loose any data on the phone.
Thanks!
Click to expand...
Click to collapse
Install it via EXE auto installer put your phone in fastboot mode and simply run .exe file on PC.

bzowk said:
Well crap. What's the process for in the guide I posted a link to in my original post, then? What more do I need to do in order to SIM-Unlock it?
Click to expand...
Click to collapse
You don't need to do anything from that guide, you just need to sim-unlock your phone. Its done with an unlock code you can purchase online, sometimes you can get the unlock code for free from the original carrier (at&t in your case). Insert a foreign sim card, boot your phone, it will then ask you to enter the code and once done your phone will be able to work on any network (as long as the frequencies are compatible).
Btw that guide should be named "how to brand/de-brand your M7" and not "How to Get Your HTC One M7 Ready for a Different Mobile Carrier". That guide will obviously not make your phone ready to be used on another carrier if its not telling you to remove the sim-lock... I guess the author was using a carrier unlocked M7 hence why he forgot to tell about sim-unlock in his guide...