Database Develop

[q] s-off what rom??

Hello XDA-Users,
I have a Question for what I can't find any awnswer...
I have an International HTC One with CID T-MOB101, HBOOT 1.55 and I want to S-OFF.
I already unlocked via HTCDev and flashed a custom Rom.
But with rumrunners S-OFF method it failes every time.. I used many various custom roms, but with no it works.
I can't go back to really stock to try it then, because for this I need S-OFF...
Sometimes it poures 8 times and write then, I have to wait 30 seconds, pray, (...) and try it again. When I tried it again it fails again...
Another time it says you have to flash an other Rom or something else.
So I don't know what Rom to try for getting S-Off..
If someone knows how to fix it, or what Rom to try, write me please.
Please help me
Thanks.

I am having the exact same issue!
My Bootloader Info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.22.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.111.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 3997mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I tried the rumrunner tool on 4 different PCs, each of them with Windows 7 Ultimate x86 or x64 and always on USB 2.0 port without any Hubs or something like that. The phone was always directly connected to an USB 2.0 port. I also tried different usb cables.
I always ran soju.exe as Administrator and accepted every Superuser request.
ROMs I tried it with: Stock Android 4.3 Sense 5.5, Android Revolution HD 41.0 and ViperOne 3.5.0
I even used an Ubuntu 13.10 Live CD but it never worked.
My bootloader is of course unlocked, TWRP 2.6.3.3 is installed and the phone is/was rooted on every rom I tried.
I attached the linux terminal log and the windows cmd log.
EDIT: I used the latest rumrunner v0.5.0.

Yep
We have exactly the same issues...
I'm trying now on Viper One 4.0.1, the new One.. Hope it works :fingers-crossed:
But I don't know why this doesn't work...

judufu said:
We have exactly the same issues...
I'm trying now on Viper One 4.0.1, the new One.. Hope it works :fingers-crossed:
But I don't know why this doesn't work...
Click to expand...
Click to collapse
try flashing this 4.3 sense 5.0 rom
http://www.scottsroms.com/downloads.php?do=file&id=466
and here's an even older one 4.1.2 you may try
http://www.scottsroms.com/downloads.php?do=file&id=442

Does it work for you?

judufu said:
Does it work for you?
Click to expand...
Click to collapse
I have had s-off since revone was released

Ok, I'll test it at the morning.
Thanks, hope it works

judufu said:
Ok, I'll test it at the morning.
Thanks, hope it works
Click to expand...
Click to collapse
you might want to read this
http://forum.xda-developers.com/showthread.php?t=2487888&page=55

reprekuc malay
If I understood this correctly the rumrunner s-off developers gave out a rumrunner version that works, but just for testing?

TheHellSite said:
If I understood this correctly the rumrunner s-off developers gave out a rumrunner version that works, but just for testing?
Click to expand...
Click to collapse
How do you mean it ??

judufu said:
How do you mean it ??
Click to expand...
Click to collapse
he's referring to this post that was removed
Originally Posted by maspro View Post
Woohoo, I'm a happy person right now.
I made a partition dump of my phone according to this guide: http://forum.xda-developers.com/showthread.php?t=2488772 and provided some additional information about my specific configuration and send it to the Rumrunner devs to see if it was possible to add support for S-OFF. After some emailing back and forth the last couple of days, I agreed to accept the risks and be a test case to see if it was possible to S-OFF my device, since my firmware was to new to make use of the existing exploits Rumrunner 0.5.0 is using. So we had a remote session together..... and a couple of minutes later my phone was S-OFF.
Don't ask me what the devs did, I looked at the adb screen, saw lots of commands and screen output flying around, but for the most part didn't understand it... Anyway my phone is still alive and I'm S-OFF.
Thx devs and I also made a donation (1HE93648R1560915F)!
Click to expand...
Click to collapse

At least we now know that the rumrunner devs have a working exploit for the latest firmware and hboot version.
We just need to wait for them to release an updated version of their tool.

Great
TheHellSite said:
At least we now know that the rumrunner devs have a working exploit for the latest firmware and hboot version.
We just need to wait for them to release an updated version of their tool.
Click to expand...
Click to collapse
Oh beatiful, when this is like you say...
Wait and hope for the best
Thanks.

TheHellSite said:
At least we now know that the rumrunner devs have a working exploit for the latest firmware and hboot version.
We just need to wait for them to release an updated version of their tool.
Click to expand...
Click to collapse
Am i in the same boat as you? i'm Three (H3G_001) International.
Im getting the same problems as what you described earlier.

Just boot your device into bootloader and then run this command in terminal/cmd "fastboot getvar all".
If the following 3 lines match yours, you very likely are in the same situation.
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.22.3263.03
(bootloader) version-main: 3.63.111.3

This it says on my device:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4082mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I think some data are nonrelevant for S-Offing, but for completeness.
Hope there are something usefull data for the further process...

[Q] Back to Stock for Bell HTC One

I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.

Nic2112 said:
I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Click to expand...
Click to collapse
post output of "fastboot getvar all"
remove S/N & IMEI before posting

kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s

Nic2112 said:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Click to expand...
Click to collapse
your previous CID was BM_001, right?
look into nkk71 SuperGUIDE in my signature

kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)

kamilmirza said:
your previous CID was BM_001, right?
Click to expand...
Click to collapse
I believe so, yes.

Nic2112 said:
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
Click to expand...
Click to collapse
yes sadly there is only nandroid of BM right now

I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.

Nic2112 said:
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Click to expand...
Click to collapse
yeah maybe that could be the problem
why not try the nandroid and see how it goes?

Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.

Oh Wow, there is a guide for Canadian HTC One, didn't know that!
Are you sure that a Telus RUU will work on a Bell phone? They use different networks I think
SaHiLzZ said:
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Click to expand...
Click to collapse

As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.

SaHiLzZ said:
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
Click to expand...
Click to collapse
I know how to go back to 1.44, I have done that before.
So what you are saying is that if I have the nandroid installed, and stock recovery from your thread, the phone will detect the OTA? It should install no problem because it will be a standard recovery.

Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.

SaHiLzZ said:
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
Click to expand...
Click to collapse
Thatk you, one last question before I try this, the OTA, will it replace the radios and firmware as well to Bell's? I guess it depends on what they put in the OTA.

Yes, OTA generally contain new OS, HBOOT, Recovery, and RADIO, practically a full RUU replacement, but not all. IF you are S-ON, you will need to lock bootloader after loading stock recovery, but if you are S-OFF, that doesnt matter, and I will suggest to stay S-OFF!

Please help
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched

ginuwine96 said:
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
Click to expand...
Click to collapse
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.

Not sure what file I need
majmoz said:
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Click to expand...
Click to collapse
This is my phones Info I am not sure what file to use for it ?
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s

ginuwine96 said:
This is my phones Info I am not sure what file to use for it ?
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
Click to expand...
Click to collapse
If you're going to follow my guide, you'll need to use CWM method, using this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-bm___001-1-29-666-5-zip/
make sure to have read it once or twice, to be sure you're comfortable with the process

[Q] Why is my phone confused?

When I try to flash any ROM that has M7SPR in the title, I get an error saying that my phone is the M7. But I have sprint and I am trying to get M7SPR becuase M7 ROM's make me lose data.
Background data:
M7_WLS
SuperCID
S-OFF
MID 20000
Basically my questions are:
1. What would cause my M7SPR to think it is a M7?
2. Is there a workaround to keep LTE with GSM ROMs?
3. If there is no workaround for the #2, how do I get my phone to flash M7SPR ROMs again where I can keep my at least my sprint data intact?

magni08 said:
When I try to flash any ROM that has M7SPR in the title, I get an error saying that my phone is the M7. But I have sprint and I am trying to get M7SPR becuase M7 ROM's make me lose data.
Background data:
M7_WLS
SuperCID
S-OFF
MID 20000
Basically my questions are:
1. What would cause my M7SPR to think it is a M7?
2. Is there a workaround to keep LTE with GSM ROMs?
3. If there is no workaround for the #2, how do I get my phone to flash M7SPR ROMs again where I can keep my at least my sprint data intact?
Click to expand...
Click to collapse
How are you flashing gsm Roms on this phone. They have different partitions.
I think you dun goofed your partitions. Try RUUing to the latest Sprint firmware and never flash a GSM ROM again.

I flashed a stock sprint RUU then while in bootloader, reflashed twrp 2.8, then flashed slimkat m7spr, now if I went back into twrp and tried to flash any other m7spr rom, I get a failure saying that this device is an m7 and this rom is for m7spr...

magni08 said:
I flashed a stock sprint RUU then while in bootloader, reflashed twrp 2.8, then flashed slimkat m7spr, now if I went back into twrp and tried to flash any other m7spr rom, I get a failure saying that this device is an m7 and this rom is for m7spr...
Click to expand...
Click to collapse
fastboot getvar all
Post results here.
Remove serial number and imei.
Also, if you want a response, remember to quote.

sauprankul said:
fastboot getvar all
Post results here.
Remove serial number and imei.
Also, if you want a response, remember to quote.
Click to expand...
Click to collapse
c:\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.5555
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.651.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ------------------
(bootloader) imei: ---------------------
(bootloader) meid:-----------------
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
There you go, thank you for the advice regarding the response time and quoting.

magni08 said:
(bootloader) version-bootloader: 1.56.5555
(bootloader) version-baseband: 1.00.20.1108
(bootloader) version-main: 4.06.651.4
(bootloader) cidnum: 11111111
Click to expand...
Click to collapse
Your boot loader is outdated. Current is 1.57. Baseband is off, supposed to be 1.29(edit: I pulled this number from my butt, I meant 1.01) i think. Version is supposed to be 5.05. CID - set it to the default sprint, if that's not it.

sauprankul said:
Your boot loader is outdated. Current is 1.57. Baseband is off, supposed to be 1.29 i think. Version is supposed to be 5.05. CID - set it to the default sprint, if that's not it.
Click to expand...
Click to collapse
Have you got a url for the baseband? This is the only one I could find for this specific phone; http://forum.xda-developers.com/showthread.php?t=2406330 and they seem to be slightly outdated.

magni08 said:
Have you got a url for the baseband? This is the only one I could find for this specific phone; http://forum.xda-developers.com/showthread.php?t=2406330 and they seem to be slightly outdated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2795856

sauprankul said:
http://forum.xda-developers.com/showthread.php?t=2795856
Click to expand...
Click to collapse
I just flashed that RUU and the radio is still 1.01.20

magni08 said:
I just flashed that RUU and the radio is still 1.01.20
Click to expand...
Click to collapse
Still? It was 1.00.2 before the RUU.
Also did you change your cid?

magni08 said:
I just flashed that RUU and the radio is still 1.01.20
Click to expand...
Click to collapse
latest baseband is 1.01.20.0904_2
why would you super cid a sprint phone, it's pointless, because you can't flash GSM roms on a cdma phone,period.

sauprankul said:
Still? It was 1.00.2 before the RUU.
Also did you change your cid?
Click to expand...
Click to collapse
I guess i might have overlooked it, since it was 1.xx.2 looking quickly I thought it was no change. I have not changed the cid. From what I was reading that is considered supercid, which is supposed to bypass carrier specific ROMs. Making it much more difficult to brick.

magni08 said:
I guess i might have overlooked it, since it was 1.xx.2 looking quickly I thought it was no change. I have not changed the cid. From what I was reading that is considered supercid, which is supposed to bypass carrier specific ROMs. Making it much more difficult to brick.
Click to expand...
Click to collapse
Would you considering trying to change back to SPCS_001? (I think that's the right one)
I'm pretty sure changing CID doesn't allow you to flash GSM roms. Super CID only applies to GSM phones.

sauprankul said:
Would you considering trying to change back to SPCS_001? (I think that's the right one)
I'm pretty sure changing CID doesn't allow you to flash GSM roms. Super CID only applies to GSM phones.
Click to expand...
Click to collapse
Can anyone confirm that SPCS__001 is the correct cid for sprint m7? I am down to try it, but I want to be sure that's all.
I do appreciate your help as well!

magni08 said:
Can anyone confirm that SPCS__001 is the correct cid for sprint m7? I am down to try it, but I want to be sure that's all.
I do appreciate your help as well!
Click to expand...
Click to collapse
Here is my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.05.651.2
(bootloader) version-misc: PVT SHIP S-ON <<note that this is actually S-OFF, I have a custom HBOOT
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) meid: ****
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001 //here is the CID
(bootloader) battery-status: good
(bootloader) battery-voltage: 3748mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

sauprankul said:
Here is my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0904_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.05.651.2
(bootloader) version-misc: PVT SHIP S-ON <<note that this is actually S-OFF, I have a custom HBOOT
(bootloader) serialno: ****
(bootloader) imei: ****
(bootloader) meid: ****
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001 //here is the CID
(bootloader) battery-status: good
(bootloader) battery-voltage: 3748mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I put my cid back to SPCS_001 and tried another M7SPR rom (http://forum.xda-developers.com/spr...t/5-0-lollipop-unofficial-cm12-m7spr-t2943941 this one specifically) and I get the same message:
This package is for device: m7spr, m7wls: this device is m7.
I also just tried the aokp (http://forum.xda-developers.com/showthread.php?t=2268789) same thing...
This is the only rom (http://forum.xda-developers.com/spr...ock-rooted-5-05-651-2odex-11-15-2014-t2941907) that actually works, rather frustrating.

magni08 said:
I put my cid back to SPCS_001 and tried another M7SPR rom (http://forum.xda-developers.com/spr...t/5-0-lollipop-unofficial-cm12-m7spr-t2943941 this one specifically) and I get the same message:
This package is for device: m7spr, m7wls: this device is m7.
I also just tried the aokp (http://forum.xda-developers.com/showthread.php?t=2268789) same thing...
This is the only rom (http://forum.xda-developers.com/spr...ock-rooted-5-05-651-2odex-11-15-2014-t2941907) that actually works, rather frustrating.
Click to expand...
Click to collapse
@BD619 any idea how this catch meachanism works? Like, what does it read? Seems like everything is set back to default for this one.
Actually did you run the RUU.exe (as opposed to flashing the firmware)? Or try to flash the latest stock ROM (4.4.3, 6.09)?

sauprankul said:
@BD619 any idea how this catch meachanism works? Like, what does it read? Seems like everything is set back to default for this one.
Actually did you run the RUU.exe (as opposed to flashing the firmware)? Or try to flash the latest stock ROM (4.4.3, 6.09)?
Click to expand...
Click to collapse
Sounds like the OP flashed the wrong recovery.
I would suggest run the RUU and start fresh.
OP you posted this in post 1 MID 20000 can you explain what that means?

BD619 said:
Sounds like the OP flashed the wrong recovery.
I would suggest run the RUU and start fresh.
OP you posted this in post 1 MID 20000 can you explain what that means?
Click to expand...
Click to collapse
The recovery is the latest from the twrp team straight from their site. I did try and revert back from 2.8 to 2.6 but it hung up at the htc loading recovery screen. From that hangup I reflashed the 2.8 I was using just to get something moving. I will look into the changing twrp and try something from there.
The MID 20000 is a reference to; modelid: PN0720000 to indicate that I was in fact using the sprint variant of this phone.
Thank you for the assistance.

magni08 said:
The recovery is the latest from the twrp team straight from their site. I did try and revert back from 2.8 to 2.6 but it hung up at the htc loading recovery screen. From that hangup I reflashed the 2.8 I was using just to get something moving. I will look into the changing twrp and try something from there.
The MID 20000 is a reference to; modelid: PN0720000 to indicate that I was in fact using the sprint variant of this phone.
Thank you for the assistance.
Click to expand...
Click to collapse
There is a version of twrp for every variant maybe you flashed one of the other variants by mistake (folks flash the M7_ul version all the time)
Official TWRP
tdhite version of TWRP (try this one first it has been polished a bit more then official)

Need T-Mobile KitKat rom

I need a T-Mobile or international stock rom sense 5.5 KitKat to to flash on my M7. I now have the AT&T unlocked and rooted but I want to make it a fully functional tmobile device with ota updates and mms and stuff (cause as of now mms don't work, but everything else does. It's a well known issue)
So of you could point me in the direction of a stock sense 5.5 KitKat rom I'd be very great full.
PS: I don't want lollipop. I don't like it. Personal preference.

test_subject said:
I need a T-Mobile or international stock rom sense 5.5 KitKat to to flash on my M7. I now have the AT&T unlocked and rooted but I want to make it a fully functional tmobile device with ota updates
Click to expand...
Click to collapse
So you will first need s-off to flash a t-mobile RUU.
(cause as of now mms don't work, but everything else does. It's a well known issue)
Click to expand...
Click to collapse
Is your APN correctly set? Most of the time, MMS issues are only caused by bad APN. Also caused by add blocking apps like AdblockPlus.
So of you could point me in the direction of a stock sense 5.5 KitKat rom I'd be very great full.
Click to expand...
Click to collapse
Post the output of ''fastboot getvar all', don't post your imei / serialno.
Btw may I ask you why do you want to have ota update support if you want to stay on Kitkat?

alray said:
So you will first need s-off to flash a t-mobile RUU.
Is your APN correctly set? Most of the time, MMS issues are only caused by bad APN. Also caused by add blocking apps like AdblockPlus.
Post the output of ''fastboot getvar all', don't post your imei / serialno.
Btw may I ask you why do you want to have ota update support if you want to stay on Kitkat?
Click to expand...
Click to collapse
Ok. Thank you. I have tried as many apn configurations as i could find to fix the mms/group text but nothing works. I dont have ad block either. Here's the output of "fastboot getvar all":
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Angel>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid:
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3823mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
C:\Users\Angel>
and as for the why of wanting otas but wanting to stay on kitkat, I guess it is just for my own sanity, knowing that the rom I have has the capability of recieving an ota is something I'd prefer, but I guess I could settle for a stock rom on the latest kitkat.
Thanks for your help (and sorry i took so long to reply)

test_subject said:
C:\Users\Angel>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: ??
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3823mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
Yep, you'll need s-off if you want to flash a t-mob ruu because you will need to change your AT&T CID to T-Mobile and your MID to PN0710000. Btw why the MID (modelid) line is blank? It should currently be PN0712000...

alray said:
Yep, you'll need s-off if you want to flash a t-mob ruu because you will need to change your AT&T CID to T-Mobile and your MID to PN0710000. Btw why the MID (modelid) line is blank? It should currently be PN0712000...
Click to expand...
Click to collapse
Ok thanks. It's blank because I thought that was one of the things you told me not to post, sorry. So after getting s-off and flashing the t-mobile ruu, will I still be rooted? Also, where might I find a t-mobile ruu for KitKat? Or a similarly stock rom, because I just mainly want to get rid of the AT&T
Thank you

test_subject said:
Ok thanks. It's blank because I thought that was one of the things you told me not to post, sorry. So after getting s-off and flashing the t-mobile ruu, will I still be rooted? Also, where might I find a t-mobile ruu for KitKat? Or a similarly stock rom, because I just mainly want to get rid of the AT&T
Thank you
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/ruu_m7_..._10-33e-1718-01l_release_387953_signed_2-exe/
After flashing a ruu, you will not have root anymore, you'll have to re-flash a custom recovery and supersu binaries.

unfortunately set up wizard has stopped working

Hi, i have recently been trying to root my htc m7, but had problems along the way so tried to do a factory restore with TWRP, it got as far as updating all apps but then gave a message "unfortunately set up wizard has stopped working". and i cant get into any phone settings.
I can get into bootloader and TWRP ( phone is showing tampered and unlocked )
Could do with a little assist cos im quite a noob at this......thanx in advance for any comments

DummySpit said:
Hi, i have recently been trying to root my htc m7, but had problems along the way so tried to do a factory restore with TWRP, it got as far as updating all apps but then gave a message "unfortunately set up wizard has stopped working". and i cant get into any phone settings.
I can get into bootloader and TWRP ( phone is showing tampered and unlocked )
Could do with a little assist cos im quite a noob at this......thanx in advance for any comments
Click to expand...
Click to collapse
Reflash a rom or a ruu. Something on /system got corrupt, a factory reset won't fix anything on /system.
What was the problem with root exactly?
Sent from my HTC One using XDA Labs

alray said:
Reflash a rom or a ruu. Something on /system got corrupt, a factory reset won't fix anything on /system.
What was the problem with root exactly?
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
hi, thanx for reply, when i rooted my m7 everything had gone successfully, but when i did a root checker it came back as "not rooted" so i did a factory restore to start over again but stuck on wizard has stopped working. Do you know which rom i should get for my phone?

DummySpit said:
hi, thanx for reply, when i rooted my m7 everything had gone successfully, but when i did a root checker it came back as "not rooted" so i did a factory restore to start over again but stuck on wizard has stopped working. Do you know which rom i should get for my phone?
Click to expand...
Click to collapse
You want to ruu the stock + root rom or a custom rom? Post the output of "fastboot getvar all" (hide your imei and serialno).
Sent from my HTC One using XDA Labs

alray said:
You want to ruu the stock + root rom or a custom rom? Post the output of "fastboot getvar all" (hide your imei and serialno).
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
(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.25.771.511
(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: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3863mV
(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!
finished. total time: 0.047s
I`m not bothered if its stock or custom....just one that can get my phone back working
I`m happy to go off your recommendation tbh

DummySpit said:
(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.25.771.511
(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: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3863mV
(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!
finished. total time: 0.047s
I`m not bothered if its stock or custom....just one that can get my phone back working
I`m happy to go off your recommendation tbh
Click to expand...
Click to collapse
Are you sure your version-main is really 7.25.771.551?
You could flash the 7.19.771.21 RUU but since your phone is S-ON you'll have to change your version-main.
file at post #2 of this thread, instruction at post #1. version-main downgrade explained at the end of post #2 (how to downgrade with s-on)
Your other option is to flash any custom rom you'd like from twrp. Most roms are pre-rooted btw. ARHD is good one to start with, stable, looks like a stock rom but with many improvements. There are also some good Sense 7 roms like InsertCoin or NewSenSeven.

alray said:
Are you sure your version-main is really 7.25.771.551?
You could flash the 7.19.771.21 RUU but since your phone is S-ON you'll have to change your version-main.
file at post #2 of this thread, instruction at post #1. version-main downgrade explained at the end of post #2 (how to downgrade with s-on)
Your other option is to flash any custom rom you'd like from twrp. Most roms are pre-rooted btw. ARHD is good one to start with, stable, looks like a stock rom but with many improvements. There are also some good Sense 7 roms like InsertCoin or NewSenSeven.
Click to expand...
Click to collapse
Thank you for info, where would i find the stock rom to match my version main, after all, I just wanted to try and "root" the phone in the first place.
If I got it back to original state then maybe i could start over again with proper guidance.
Sorry if I sound like a proper novice............. but i am...........thanks once again.

DummySpit said:
Thank you for info, where would i find the stock rom to match my version main, after all, I just wanted to try and "root" the phone in the first place.
If I got it back to original state then maybe i could start over again with proper guidance.
Sorry if I sound like a proper novice............. but i am...........thanks once again.
Click to expand...
Click to collapse
There is no rom that match your version-main, thats why I suggested that you either change your version-main using the downgrade guide so you can flash the 7.19.771.21 RUU (you'll be able to update back to your current version after) or to flash any custom rom you'd like.

Sorry I understand now, I'll have a shot at downgrading and see how it goes. Thanks for your time and advice.