So, multiple strange issues, but starting from the beginning;
Purchased the HTC One from my local provider, the CID for this is BS_US001 ( Brightstar US 001 )
I had gotten an unlock token from HTC and flashed successfully, and also loaded CWM as well, about a week later, I restored the factory using the provided image from HTCDev.com ( PN07IMG_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3 ) This successfully removed the ***TAMPERED*** status, but continued keeping the ***RELOCKED*** ( This isn't a big deal ).
My problem:
When I unlocked the bootloader again, I flash a customer recovery, and get a SUCCESSFUL message, yet, when I restart the bootloader, no ***TAMPERED*** at the top, the phone will not boot into the custom bootloader, however, when I flash into the stock one, it works just fine and shows the phone with the red /_!_\ over it.
Unfortunately at this point, I have been seeing strange issues since, the phone has provided errors similar to "Too many links" when trying to change the SuperCID and when trying to use the moonshine S-OFF, now I can't make any modifications. Any suggestions? I'm stumped after reflashing the RUU.
Let me start off with I think I got lucky. Try this at your own risk. I locked my bootloader and turned my security back on for a TMOUS warranty exchange for the dreaded purple tint in camera. I received my replacement only to find out that in fluorescent lighting the replacement HTC ONE M7 had a greenish tint but only under fluorescent lighting. So I am getting another replacement sent for free. This is where my troubles begin. I decided to unlock my bootloader for my original phone again and root it so I can set everything up again for daily use. I got through all those steps fairly easy. FYI: original phone is on newest TMOUS OTA_M7_UL_K44_SENSE60_MR_TMOUS_5.14.531.1_R-4.19.531.10_release_373019xng22l97gj5szmwv. I then relocked the phone and tried to flash RUU Zip M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2_decrypted.zip in order to achieve s-off again but to no success. Hboot 1.57.000 with S-ON wasn't having any of it I guess.
I unlocked bootloader and relocked bootloader several times trying several different methods to no success. Oh, my recovery was TWRP 2.7.0.0. At some point I realized that if I was going to return this phone I needed to get s-off again to remove tampered flag and actually lock phone instead of relock. I happened to come across a stock rom that I decided to install in hopes of accomplishing S-off. Stock 3.24.531.3 T-Mobile.zip was the rom. Long story. I know. So here is what I did;
Unlocked bootloader
Flashed TWRP and gained root using WinDroid Universal HTC Toolkit
Installed Stock 3.24.531.3 T-Mobile.zip ROM via TWRP
Phone would not fully boot past HTC ONE Animation screen
powered down and powered back on into bootloader
relocked bootloader and rebooted bootloader
unlocked bootloader again
Phone now booted completely into the stock rom I flashed
Proceeded to use firewater for S-off
Didn't work first time
Powered down phone by holding power button and rebooted normally
Tried firewater again and to my luck the SOB worked and I am S-Off again on newest HTC One TMOUS with an older Stock 3.24.531.3 T-Mobile rom
I'm sorry if I have no links to anything I mentioned but I am new to this so I don't really know how to link to other stuff I found on the site. Thanks to all the great people whose tools and rom I used to achieve S-off again.
Prior to doing those steps firewater would not get past the first chugging stage.
If you got the chugging message you were always going to be able to s off it. Firewater isn't worried about the hboot so much as the version of your cpu as to whether the exploit will work on it
Sent from my HTC One using XDA Premium 4 mobile app
It would get to the chugging and sit there for bit then kick the phone back to root command. It didn't matter how many times I tried it would always do the same thing at the same spot. I would then have to reboot the phone and try again but no success. I'm just sharing what I did and worked for me. Clearly the exploit didn't want to work before I did the steps I took. I wouldn't have spent almost 30 hours of reading and trying to fix the problem I caused otherwise. Maybe it was a fluke or dumb luck. I don't know.
Where can I find this stock rom?
Nevermind this did not work.
I have an HTC one m7 801n EUR edition. sometime back I got an error "com.android.htcdialer has stopped unexpectedly" and phone restarted in a loop. My friend installed cyagenmod 11 without taking any backup/stock rom/nandroid and phone started with no netwrok. I tried to recover but failed. Now my bootloader is unlocked but phone is not starting up just cyagenmod logo keeps showing with arrow. Please help me, I just want my phone to work again, thanks
bootloader version- 1.57
version baseband -4T.27. 3218.14
version main - 5.11.401.10
s-on
mid- PN0710000
cid - htc_001
Hello all, I rooted my m7 a few weeks ago. For whatever reason I lost my backup after installing cm12. Now CM 12 is all I can get to work. Sense roms either reboot randomly every min or so (never made it through setup) or bootloop, or won't activate with sprint HFA. I want to ruu, but I've read I need to relock the boot loader and everything I've seen to do that requires s-off.
What do I need to do to get back?
1.61 hboot
Rooted
Unlocked/tampered
S-on
Also, why can't I get any sense rom to run?
cant get s-off with sunshine (what i have been told i need for my hboot vers) while im stuck in cm12...help plzzz
the5ifty said:
Hello all, I rooted my m7 a few weeks ago. For whatever reason I lost my backup after installing cm12. Now CM 12 is all I can get to work. Sense roms either reboot randomly every min or so (never made it through setup) or bootloop, or won't activate with sprint HFA. I want to ruu, but I've read I need to relock the boot loader and everything I've seen to do that requires s-off.
What do I need to do to get back?
1.61 hboot
Rooted
Unlocked/tampered
S-on
Also, why can't I get any sense rom to run?
Click to expand...
Click to collapse
You don't need to be s-off to re-lock or RUU and you must be on a stock rom for Sunshine to work.
new and need help!!!!!
hi new here in need of help i have a
--------------------------------
{Htc m7 sprint}
m7_wls pvt ship
s-on
HBOOT 1.61.000
radio- 1.01.20.1225
open dsp-v35.120.274.0718
os-6.23.651.6
emmc-boot 2048mb
---------------------------------
ok i have rooted lgs and samsungs flashed them and have comptly brick phones to were they wont even turn on.so im not the best but i do have a liitle nolgke of rooting. i do understand what it takes to safely do this. so i now have this htc it all started i needed it sim-unlocked.so i got boot loader lock off and rooted but the twrp i had flashed for it, the touch pad would not work so i put clockwork (6.0.3.3)on it. that seemed to work then my phone was rooted but keep getting binary error so i tried google play way with apks and none of them helped so i flashed update su to recovery then i went to boot back and stuck in a boot loop. so then come to find out my android secure .img is know missing and so i re locked bootloader and tried to flash a couple of the {RUU} i found wich doing all this threw fastboot and not one would past signature and all have failed. im totally dumbed on this and need help to get my phone up and going thank you
Hello all!
I've bought a Htc One M7 for Christmas... Chinese problems included. The phone is in pristine condition, but I believe it was completely botched on the sofware side > flashed to a M7_WLS instead of a M7_UL.
What I have :
- A phone with an European IMEI. I do believe the phone is genuinely a HTC M7_UL, since PID is PN07100 (which is european)
- A bootloader that identifies the phone as a M7_WLS (Sprint)
- Radio 1.00.31.0603 (that raised my suspicions)
- S-OFF, HBoot 1.57, SuperCID but locked bootloader (can be unlocked).
- A lousy gift for my mother...
CLOSED/SOLVED : The device was a "real" M7_WLS in a M7-UL body, complete with laser engravings....
- If your bootloader says M7_WLS, it's a sprint device and no amount of flashing can change that.
- Proceeded to restore to stock with S-Off, latest firmware and stock 6.23 rom.
Thanks to everybody who helped me "unlock" that mystery, my mom now has a Nexus 5 lol
What I intend to do:
- Flash a 5.1 firmware (Combo NoBoot No Recovery) for a M7_UL and pray (lol), with the goal of restoring the radio to its correct use
- Go to a RUU if needed
What I need help for :
- Getting either directions, or a sense of feasability, because....
- ...I've lost track of S-OFF, unlocked bootloader, firmware and such. My own M7 was S-off at one time (3 years ago), got back to S-ON with a new hboot trying to update radio... Been stuck since. I don't want to mess this, lock things up, and have to ship the phone back.... My HD2 times are SUCH a long time ago :highfive:
> Basically : updating the radio and the firmware somehow, so I can use LTE bands in Europe and update the phone to a GPE 5.1, and make my mom happy.
Thank you everyone !
Edit: OMG, that HD2 Encyclopedia.... I now understand why I didn't have friends in High School.
RedWave31 said:
Hello all!
I've bought a Htc One M7 for Christmas... Chinese problems included. The phone is in pristine condition, but I believe it was completely botched on the sofware side > flashed to a M7_WLS instead of a M7_UL.
What I have :
- A phone with an European IMEI. I do believe the phone is genuinely a HTC M7_UL, since PID is PN07100 (which is european)
- A bootloader that identifies the phone as a M7_WLS (Sprint)
- Radio 1.00.31.0603 (that raised my suspicions)
- S-OFF, HBoot 1.57, SuperCID but locked bootloader (can be unlocked).
Click to expand...
Click to collapse
If the bootloader is saying M7_WLS then its probably a M7_WLS. You can't trust the PN0710000 MID, it can easliy be changed with S-OFF. Looks more like somebody tried to convert his M7_WLS into a M7_UL which is not possible. You should flash back a Sprint RUU. If you want to confirm what i'm saying dump the MFG partition (mmcblk0p6) and you'll find the original identity of the phone inside of it, most likely MID PN0720000 and CID SPCS_001
alray said:
If the bootloader is saying M7_WLS then its probably a M7_WLS. You can't trust the PN0710000 MID, it can easliy be changed with S-OFF. Looks more like somebody tried to convert his M7_WLS into a M7_UL which is not possible. You should flash back a Sprint RUU. If you want to confirm what i'm saying dump the MFG partition (mmcblk0p6) and you'll find the original identity of the phone inside of it, most likely MID PN0720000 and CID SPCS_001
Click to expand...
Click to collapse
Thanks for this reply.
Unfortunately, I don't have enough knowledge to dump a partition - managed to input the command, but couldn't retrieve the data.
Where I'm at now (tryhard mode enabled):
- Changed MID
- Flashed GPE firmware 5.1 full combo
- Flashed GPE RUU 5.1, ended trying a 4.4, see why next
- Flashed recovery 2.8.7.0 > works, but cannot mount the cache and sdcard unless I fix permissions with SELinux mode
Everything (bootloader, recovery) kinda works, but the Rom won't boot.
Trying to know why : when I flash any RUU, I got two fails at signature checking
- sbl 1-1
- sbl 1-2
I got a white Google logo on black background with a little lock near the HTC logo on the front > I cannot find ANY clue on this one, anywhere on Google, XDA... Damn
- The bootloader also always shows a M7_WLS info, despite MID and CID and stuff being all M7_UL (after all thoses flashes, I get why) > Am I trying too much, not enough, or should it change somehow?
If anyone had a clue, I'd apreciate it.
- I can flash back and forth any firmware or Hboot (M7_UL based) The phone just takes it all, no questions asked ^^
PS : I can send it back, but i'd try at least to put it back in its original shape. Should I flash back a sprint firmware, sprint RUU and call it a day? Since I was previously told flashing a different RUU on a sprint phone would destroy my phone and it didnt....well
Thanks guys !
There is a very easy way to find out if your phone is WLS or WWE. Does it have a sim card slot? WLS is CDMA and doesn't have sim card, so that's a step closer to identifying your phone ?
RedWave31 said:
Thanks for this reply.
Unfortunately, I don't have enough knowledge to dump a partition - managed to input the command, but couldn't retrieve the data.
Click to expand...
Click to collapse
Code:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mfg_backup.img
exit
exit
adb pull /sdcard/mfg_backup.img C:\Wherever\you\want\to\save\it
Where I'm at now (tryhard mode enabled):
- Changed MID
- Flashed GPE firmware 5.1 full combo
- Flashed GPE RUU 5.1, ended trying a 4.4, see why next
- Flashed recovery 2.8.7.0 > works, but cannot mount the cache and sdcard unless I fix permissions with SELinux mode
Everything (bootloader, recovery) kinda works, but the Rom won't boot.
Click to expand...
Click to collapse
You have a WLS and flashing UL RUU, this will obviously not work. Flash a sprint RUU with the sprint MID and CID (PN07200000 SPCS_001) If you need a custom recovery for whatever reason (like dumping your MFG) use a WLS custom recovery.
Trying to know why : when I flash any RUU, I got two fails at signature checking
- sbl 1-1
- sbl 1-2
Click to expand...
Click to collapse
This is not a problem, these item are bypassed.
I got a white Google logo on black background with a little lock near the HTC logo on the front > I cannot find ANY clue on this one, anywhere on Google, XDA... Damn
Click to expand...
Click to collapse
This is the GPE splash screen. That little lock tells you the bootloader status. Open lock = unlocked bootloader
- The bootloader also always shows a M7_WLS info, despite MID and CID and stuff being all M7_UL (after all thoses flashes, I get why)
Click to expand...
Click to collapse
Why? read what iv said in my previous post.... Because its a M7_WLS not a UL.
alray said:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p6 of=/sdcard/mfg_backup.img
exit
exit
adb pull /sdcard/mfg_backup.img C:\Wherever\you\want\to\save\it
You have a WLS and flashing UL RUU, this will obviously not work.
Click to expand...
Click to collapse
Thanks for all the info, I wish I would have replied earlier : I have a sim card slot. As stated before, can a Sprint CDMA device have one?
Since I don't think so, I now truly believe my phone is a really botched up M7_UL (don't believe it's a M7_U gsm only)
I'm gonna have to figure out why .exe RUU don't work, and why flashing zip decrypted ones don't work either.
Also, if someone has any clue about that M7_WLS showing up despite all the other clues pointing towards an original M7_UL... I've yet to found how this is possible.
Next operation is gonna be trying to install a real .exe GPE RUU, I believe all the flashing and stuff is getting me out of sync firmware numbers (hboot higher than the RUU requirements or so).
They are kinda hard to find (unless from HTC), and I find myself with gigs of Zips and RUU ^^
Will try the M7_U possibility also.
Will dump that partition just to be sure, but since the phone has been tinkered SO MUCH... I don't get it at this point why would someone do that !
> Countdown to christmas...
Thanks guys for your support, it's heartwarming these days
RedWave31 said:
Thanks for all the info, I wish I would have replied earlier : I have a sim card slot. As stated before, can a Sprint CDMA device have one?
Since I don't think so, I now truly believe my phone is a really botched up M7_UL (don't believe it's a M7_U gsm only)
Click to expand...
Click to collapse
The sprint variant also have a sim card, its required for LTE and roaming.
Also, if someone has any clue about that M7_WLS showing up despite all the other clues pointing towards an original M7_UL
Click to expand...
Click to collapse
Like I said earlier, your clues are not telling anything. The phone is S-OFF which means both the MID and CID can be modified to anything easily. If the product name is M7_WLS then its a M7_WLS !!!!!
Next operation is gonna be trying to install a real .exe GPE RUU, I believe all the flashing and stuff is getting me out of sync firmware numbers (hboot higher than the RUU requirements or so).
They are kinda hard to find (unless from HTC), and I find myself with gigs of Zips and RUU ^^
Will try the M7_U possibility also.
Click to expand...
Click to collapse
That will be a lot of wasted time. Write back the Sprint MID and CID and flash the Sprint RUU. Even better, dump the MFG partition first so you are 100% sure what that phone is.
I don't get it at this point why would someone do that !
Click to expand...
Click to collapse
The previous owner probably wanted to flash a M7_UL RUU on his M7_WLS phone without knowing it wasn't possible even after changing the MID and CID to M7_UL.