[Q] m7_u HBOOT MOD help? [SOLVED] - One (M7) Q&A, Help & Troubleshooting

Hi, I've been trying to remove the red text from splash screen (I changed the splash to include owner info) for my phone but so far no luck. I've been spending the night searching the forums and it seems that changing the HBOOT would solve my problem. However I can't seem to find one compatible for my phone. Is there any other way for me to do so?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.709.103
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ******************
(bootloader) imei: ********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I would appreciate any help from anyone who can point me to the right direction. (BTW, OTA is 5.12.709.103)
Thanks in advance

I flashed my s-off GSM phone with a full Google Play Edition RUU which contains a really nice black bootloader with a little gray padlock. If you don't want to do that there is a dev thread for installing a custom hboot that you can use to remove the red text. If you cant find it let me know and I'll see if I can find it.

xtalks said:
Hi, I've been trying to remove the red text from splash screen (I changed the splash to include owner info) for my phone but so far no luck. I've been spending the night searching the forums and it seems that changing the HBOOT would solve my problem. However I can't seem to find one compatible for my phone. Is there any other way for me to do so?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.709.103
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ******************
(bootloader) imei: ********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I would appreciate any help from anyone who can point me to the right direction. (BTW, OTA is 5.12.709.103)
Thanks in advance
Click to expand...
Click to collapse
you can flash any modified m7_u firmware which will contain a modified HBOOT to remove red text, due to being s-off, you must change your cid and mid to match the firmware that you want to use first.
NEVER GO S-ON WITH A MODIFIED HBOOT / FIRMWARE, IT WILL LEAD TO AN INSTANT BRICK.

I do have a lot of questions right now:
dougeedug said:
I flashed my s-off GSM phone with a full Google Play Edition RUU which contains a really nice black bootloader with a little gray padlock. If you don't want to do that there is a dev thread for installing a custom hboot that you can use to remove the red text. If you cant find it let me know and I'll see if I can find it.
Click to expand...
Click to collapse
Is this what you're talking about?http://forum.xda-developers.com/showthread.php?t=2391611
I'd prefer the original white bootloader, if that is not asking too much, and I'm having a hard time looking for custom Hboots for my firmware
Seanie280672 said:
you can flash any modified m7_u firmware which will contain a modified HBOOT to remove red text, due to being s-off, you must change your cid and mid to match the firmware that you want to use first.
NEVER GO S-ON WITH A MODIFIED HBOOT / FIRMWARE, IT WILL LEAD TO AN INSTANT BRICK.
Click to expand...
Click to collapse
Do I need to change the CID/MID of my phone or can I just edit android-info.txt? Would this one work? http://forum.xda-developers.com/showthread.php?t=2485651

xtalks said:
Is this what you're talking about?http://forum.xda-developers.com/showthread.php?t=2391611
I'd prefer the original white bootloader, if that is not asking too much, and I'm having a hard time looking for custom Hboot
Click to expand...
Click to collapse
That is the bootloader I am referring to, although I did not install it separately as it was just "part of the package" when running the GPE RUU. I think thishttp://forum.xda-developers.com/showthread.php?t=2485651 may be more what you are looking for, although I have no idea if the specific hboot offered is the one you need.

dougeedug said:
That is the bootloader I am referring to, although I did not install it separately as it was just "part of the package" when running the GPE RUU. I think thishttp://forum.xda-developers.com/showthread.php?t=2485651 may be more what you are looking for, although I have no idea if the specific hboot offered is the one you need.
Click to expand...
Click to collapse
I am actually contemplating on flashing that specific HBOOT right now (check my reply to Sean), but I wouldn't know what to do if it does brick my phone. >_<

It can be a significant risk considering that the bootloader is basically the lowest tier of connectivity users like us have, therefore offering little in the way of options for recovering from a failed attempt.. I suggest reading that whole thread and seeing what has been happening to others. I assume that any attempt to flash a new hboot would fail harmlessly if something did go wrong. The main thing to consider is that no matter what we do to our s-off HTC devices, we have the luxury of bringing the device home to mama with a full RUU flash. If a failed hboot install blocks you from accessing the RUU mode, then you may be well and truly screwed. But all that being said, I have installed a custom hboot once before (I cant even remember why now, perhaps it was pre GPE) and everything went just fine. It goes without saying that you should read the OPs directions over and over until you are sure you have your head all the way around what you are doing before you begin. Also, as the user above offered in quite justified allcaps, you must NEVER EVER try to go back S-on while running a nonstock hboot! This will result in a device recoverable only by jtag service.

Thanks all. Followed this guide (http://forum.xda-developers.com/showthread.php?t=2365506) with my fingers crossed and all was well.

xtalks said:
Thanks all. Followed this guide (http://forum.xda-developers.com/showthread.php?t=2365506) with my fingers crossed and all was well.
Click to expand...
Click to collapse
Edit your thread title with a [SOLVED] tag and I will pay you for it by hitting your thanks button!

Related

[Q] Need Mac help going from GE back to stock

So I was able to completely convert my AT&T One to a GE phone per the thread over at http://forum.xda-developers.com/showthread.php?t=2358781.
I find out afterwards that my bottom mic does not work on phone calls, not sure how long it's been this way since I normally use bluetooth. The back mic works for speakerphone but that won't do me any good. Now I want to get back to stock to see if the mic comes back to life and in case I have to take it back to AT&T.
I've managed to maneuver my way around the terminal in Mac OSX to flash custom roms and such. I'm S-off and have super CID. The part I'm stuck at is finding a RUU zip to revert back to stock. Most of the links I've found are dead or are for the exe that will run in windows only.
This is the readout of my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.1700.15
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4282mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-21fde4b846
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I can't even seem to flash the developer RUU without an error, and I'm wondering if it might have do do with the MID. Need some pointing in the right direction, thanks!
when you converted did you back up your stock HBOOT?
if so you can put it back,
then run the AT&T RUU
OR conversely it has been discovered that if you flash the 2.17 firmware found in this post
http://forum.xda-developers.com/showpost.php?p=42556698&postcount=24958
you can then flash a downgraded RUU.
sent luditr
gunnyman said:
when you converted did you back up your stock HBOOT?
if so you can put it back,
then run the AT&T RUU
OR conversely it has been discovered that if you flash the 2.17 firmware found in this post
http://forum.xda-developers.com/showpost.php?p=42556698&postcount=24958
you can then flash a downgraded RUU.
Click to expand...
Click to collapse
Thanks gunny, I was hoping you'd answer since you use a mac also. I did not back up my HBOOT, but I believe I have the stock one that someone else uploaded. I'll give the firmware and downgrade a shot. Do you happen to know where to find the zip and not exe for the stock AT&T One?
acquiredhate said:
Thanks gunny, I was hoping you'd answer since you use a mac also. I did not back up my HBOOT, but I believe I have the stock one that someone else uploaded. I'll give the firmware and downgrade a shot. Do you happen to know where to find the zip and not exe for the stock AT&T One?
Click to expand...
Click to collapse
I'm afraid I don't.
I use vmware and an old copy of windows XP when I need an RUU.
If you don't have VMware Virtualbox is free and will also work

HTC One Developer Edition: WiFi and Bluetooth fail

Hello friends. First of all, I apologize if I am not very clear, but I have little knowledge of English, and to be faster I'll use a translator...
Since about a week ago, my HTC One Developer Edition is showing me errors with WiFi and Bluetooth. These are off steadily even when in use. At first I thought it was a failure of the last installed ROM (ARHD 40.1), but I've tried others such as CM11 without installing any mod and restore my latest nandroid backup, but I have had the same result.
Apart from changing the ROM all I remember doing is to update the firmware, so yesterday I upgraded to the new firmware version to see if solved, but still follows the failure. Do not think it's a hardware failure because the mobile is not second hand, has not suffered any drop and was always working perfectly, so I ask your help and attached the information that shows the phone using fastboot getvar all command if serving them for a diagnosis. Thanks in advance.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3993mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
You are Soff. Why not reflash official dev ruu?
SaHiLzZ said:
You are Soff. Why not reflash official dev ruu?
Click to expand...
Click to collapse
What should I use? Because I see several for Dev Edition on this list:
[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads
[email protected] said:
What should I use? Because I see several for Dev Edition on this list:
[COLLECTION] HTC M7 RUU, OTA, and Stock Nandroid Downloads
Click to expand...
Click to collapse
Either one will do, they're just slightly different version numbers 1.29.1540.16 and 1.29.1540.3, might as well go for the .16. You'll have to download from here: http://www.htc1guru.com/downloads/ruu-file-downloads/
then you can follow my guide (in my signature), because you need to downgrade hboot to 1.44 separately first, before you can run the RUU. (just the first part about downgrading hboot, the rest of the guide is for people who want to return the phone for warranty)
Also keep S-Off, do NOT go S-On!!!
nkk71 said:
Either one will do, they're just slightly different version numbers 1.29.1540.16 and 1.29.1540.3, might as well go for the .16. You'll have to download from here: http://www.htc1guru.com/downloads/ruu-file-downloads/
then you can follow my guide (in my signature), because you need to downgrade hboot to 1.44 separately first, before you can run the RUU. (just the first part about downgrading hboot, the rest of the guide is for people who want to return the phone for warranty)
Also keep S-Off, do NOT go S-On!!!
Click to expand...
Click to collapse
Well, thank you very much. Be right back after process.
SaHiLzZ said:
You are Soff. Why not reflash official dev ruu?
Click to expand...
Click to collapse
nkk71 said:
Either one will do, they're just slightly different version numbers 1.29.1540.16 and 1.29.1540.3, might as well go for the .16. You'll have to download from here: http://www.htc1guru.com/downloads/ruu-file-downloads/
then you can follow my guide (in my signature), because you need to downgrade hboot to 1.44 separately first, before you can run the RUU. (just the first part about downgrading hboot, the rest of the guide is for people who want to return the phone for warranty)
Also keep S-Off, do NOT go S-On!!!
Click to expand...
Click to collapse
I downgrade to hboot 1.44 and reflash the official ruu (RUU M7 JB UL 50 BrightstarUS WWE 1.29.1540.16), but still blinking on and off wifi and bluetooth.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.16
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3994mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.065s
Time to call HTC for warranty support. No other ideas.
Hey this is off topic but SaHiLzZ, is your name Sahil?
Sent from my HTC_PN071 using Tapatalk
SaHiLzZ said:
Time to call HTC for warranty support. No other ideas.
Click to expand...
Click to collapse
Well, I bought this phone in the United States.... I live in Dominican Republic...
@SaHiLzZ @nkk71 I was using the bluetooth headphones faultlessly for more than 4 hours, and when I get home WiFi even longer, so I know that still work but are turned on and off when it wants ...
[email protected] said:
@SaHiLzZ @nkk71 I was using the bluetooth headphones faultlessly for more than 4 hours, and when I get home WiFi even longer, so I know that still work but are turned on and off when it wants ...
Click to expand...
Click to collapse
did u try changing some of the advanced settings i mentioned?
nkk71 said:
did u try changing some of the advanced settings i mentioned?
Click to expand...
Click to collapse
Yes, but I don't see changes. (Later, I change the "Keep WiFi on during idle" to Always), but just keeps running and then switching off when it want, and when it goes off, just says "activating", infinite loop until I restart.. Same for bluetooth.
SaHiLzZ said:
Time to call HTC for warranty support. No other ideas.
Click to expand...
Click to collapse
@nkk71
Well, without ideas, I sent the phone to HTC America, for guarantee. I had to pay $ 70 shipping because I live in Dominican Republic (No HTC), but after 15 days I received my phone in perfect working (they did not even scratch), and by the way, apparently they changed my camera ... It's not purple! :laugh:
Thanks for all your help friends. :highfive:

Need help to get S-off. tried all possible

Hi everyone! I have a problem, I tried to make S-off with all available here on the site, and it did not work out (rumrunner hanging on pounding ........ and firewater is also something same on bottle 1). Bootloader is in state tampered.
Here is my data
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.51 (this version was set by misctool, (before there was 4.19.401.8) I thought that perhaps i can flash older firmware tht can make rumrunner to work)
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3AGW901978
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I do not know what else can help make S-off, probably tried all possible methods. Maybe, someone also went through this agony with S-off
I would also add that I tried to restore the firmware using Guru_Reset_M7_2.24.401.8 and then OTA update but it only caused permanent bootloot
pankozin said:
Hi everyone! I have a problem, I tried to make S-off with all available here on the site, and it did not work out (rumrunner hanging on pounding ........ and firewater is also something same on bottle 1). Bootloader is in state tampered.
Here is my data
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.51 (this version was set by misctool, (before there was 4.19.401.8) I thought that perhaps i can flash older firmware tht can make rumrunner to work)
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3AGW901978
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I do not know what else can help make S-off, probably tried all possible methods. Maybe, someone also went through this agony with S-off
I would also add that I tried to restore the firmware using Guru_Reset_M7_2.24.401.8 and then OTA update but it only caused permanent bootloot
Click to expand...
Click to collapse
There is already a thread discussing about s-off on hboot 1.56 here
you'll probably find an answer there.
Afaik you'll need a rooted rom + an unsecured kernel to achieve s-off.
alray said:
There is already a thread discussing about s-off on hboot 1.56 here
you'll probably find an answer there.
Afaik you'll need a rooted rom + an unsecured kernel to achieve s-off.
Click to expand...
Click to collapse
I tried 5 different roms. dont know about kernels, i think this roms have unsecured kernels. but mb i need to install it separately??? I read this thred u suggested, but it didnt help. Now im on ARHD 62.0. what kernel should i try?
I really literally read all posts over internet but nothing helped. Or i dont understand something about this process. so i created a thread for it
pankozin said:
I tried 5 different roms. dont know about kernels, i think this roms have unsecured kernels. but mb i need to install it separately??? I read this thred u suggested, but it didnt help. Now im on ARHD 62.0. what kernel should i try?
I really literally read all posts over internet but nothing helped. Or i dont understand something about this process. so i created a thread for it
Click to expand...
Click to collapse
arhd already comes with the required kernel. have tried arhd 53?
alray said:
arhd already comes with the required kernel. have tried arhd 53?
Click to expand...
Click to collapse
I tried 53 and 31.6. just dont know what can i do more. I feel like i changed something crucial in firmware or something so now nothing works (
pankozin said:
I tried 53 and 31.6. just dont know what can i do more. I feel like i changed something crucial in firmware or something so now nothing works (
Click to expand...
Click to collapse
s-off is hard to achieve on hboot 1.56 and doesn't work for everyone. Maybe you could just wait for a better s-off solution for 1.56.
alray said:
s-off is hard to achieve on hboot 1.56 and doesn't work for everyone. Maybe you could just wait for a better s-off solution for 1.56.
Click to expand...
Click to collapse
Where can i find firmware to flash in S-ON state? i heard tht signed one may suite.
alray said:
s-off is hard to achieve on hboot 1.56 and doesn't work for everyone. Maybe you could just wait for a better s-off solution for 1.56.
Click to expand...
Click to collapse
Hey i got this problem when using rumrunner "adbd can not run as root in production builds"

Please help!!!

I have tried the latest rom for htc that was recommended from xda. was told to unlock bootloader push rom to device. then relock device the open twrp and install rom but this will not work because the bootloader is locked.
I am running out of ideas. I have spent nearly 5 days, day and night to revive my m7. followed every tutorial and all instructions thoroughly only to come to the same point. rom not installed.
here is the current status
tampered, unlocked, s-on
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.980.35
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA426W918414
(bootloader) imei: 355859056825508
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4323mV
(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
would be great just to get it back to normal.
Thanks .
howelldog said:
I have tried the latest rom for htc that was recommended from xda. was told to unlock bootloader push rom to device. then relock device the open twrp and install rom but this will not work because the bootloader is locked.
I am running out of ideas. I have spent nearly 5 days, day and night to revive my m7. followed every tutorial and all instructions thoroughly only to come to the same point. rom not installed.
here is the current status
tampered, unlocked, s-on
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.980.35
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA426W918414
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4323mV
(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
would be great just to get it back to normal.
Thanks .
Click to expand...
Click to collapse
Please just post in one thread only! Remove the IMEI information from getvar information.
There appears to be a RUU for your device here:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
See 7.19.980.5
However your current version main is 7.21.980.35 so I'm not sure it will flash since the device has a newer version already installed. Scroll to the bottom of the page and read the instructions for "How to downgrade with S-ON" and change the current version main to 7.19.980.5 then flash the RUU.
Hope this works for you
mb_guy said:
Please just post in one thread only!
There appears to be a RUU for your device here:
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
See 7.19.980.5
However your current version main is 7.21.980.35 so I'm not sure it will flash since the device has a newer version already installed. Scroll to the bottom of the page and read the instructions for "How to downgrade with S-ON" and change the current version main to 7.19.980.5 then flash the RUU.
Hope this works for you
Click to expand...
Click to collapse
^^+1, this should get the phone back to stock without any problem.
@mb_guy This is real mess now lol, he posted at 3 different places, one member telling him to unlock and flash a custom rom (which is ok), another member telling him to flash the wrong RUU without even looking at his getvar and us now telling him to do something different here. Hope he now understand why he shouldn't create 2 threads for the same issues and post in a 3rd one... : Contradictory advice and confusion :crying:
A BIG thank you
I would like to thank the team and their members for helping me Restore my HTC back to normal. It was a very frustrating and time consuming process for a novice phone hacker. but managed to get everything back to normal from this last thread response, and managed to unlock, root and s-off as well, which was the process i was trying to achieve in thew first place. I now have backed up my phone system and kept a copy of the working ROM.
I am sorry for any issues that I may have caused by creating a new forum thread, I didn't realise this was bad online etiquette. It was purely because I was not getting the right responses from the existing threads, and mostly because I am not that familiar with how forums work.
Thanks again and keep up the good work.
Shane.
howelldog said:
I would like to thank the team and their members for helping me Restore my HTC back to normal. It was a very frustrating and time consuming process for a novice phone hacker. but managed to get everything back to normal from this last thread response, and managed to unlock, root and s-off as well, which was the process i was trying to achieve in thew first place. I now have backed up my phone system and kept a copy of the working ROM.
Click to expand...
Click to collapse
Glad you got it sorted :good:
I am sorry for any issues that I may have caused by creating a new forum thread, I didn't realise this was bad online etiquette. It was purely because I was not getting the right responses from the existing threads, and mostly because I am not that familiar with how forums work.
Click to expand...
Click to collapse
No problem mate, in the future just remember you can edit your thread title and all your posts if you don't get the right answer or if you have more info to add. You can also bump your thread once a day if you don't get any answer. :good:
alray said:
^^+1, this should get the phone back to stock without any problem.
@mb_guy This is real mess now lol, he posted at 3 different places, one member telling him to unlock and flash a custom rom (which is ok), another member telling him to flash the wrong RUU without even looking at his getvar and us now telling him to do something different here. Hope he now understand why he shouldn't create 2 threads for the same issues and post in a 3rd one... : Contradictory advice and confusion :crying:
Click to expand...
Click to collapse
Hi
Just wondering if this ruu that i have installed in this post will accept software updates? I am rooted and s-off. will the update affect the current status?
howelldog said:
Hi
Just wondering if this ruu that i have installed in this post will accept software updates? I am rooted and s-off. will the update affect the current status?
Click to expand...
Click to collapse
Yes but root might be a problem. Lot of ppl ended with softbricked phone after installing a Lollipop ota update over a rooted stock rom. Backup your files first, then try to update. If that doesn't work you can always re-flash the RUU and take all ota updates before rooting.

No ROM, No Recovery, Relocked, Tampered, Security Warning

I've been searching around for a solution to fix my device with all of my attempts failing. I have a HTC One M7 from Telus (Newfoundland, Canada) which is about 3 years old. It's in great condition and has been well taken care of. I had been using CM 12.1 and TWRP right up until a few days ago. My intentions were to bring my phone back to factory settings without any root capabilities as the newest update for Pokémon Go requires you to have an un-rooted device. Obviously my efforts to go back to factory settings were in vain as now my phone is basically one step away from being bricked. I can load up the bootloader just fine and acheive fastboot without any problems although anything beyond there fails everytime (ie. enter recovery mode).
I'm able to do stuff with it using ADB tools via my pc so not all hope is lost just yet. Could anyone provide step by step instructions on how to get the phone back to an untampered state as well as links to the files i'll need to do so? I have yet to find any ROM's for a TELUS M7 as well as the default recovery tools. I keep seeing links to utilities which apparently are a basic one-click-fix though none of them have worked thusfar (my most recent one is called "RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2.exe" which seems to work right up until it gets to the HEADER portion where it doesn't move past 5%)
I've since bought a new phone which is an extreme pain to use as, in my opinion, it's a huge downgrade from what i've been using (LG-K121)
Any and all help is muchly appreciated [:=
kayohbe said:
I've been searching around for a solution to fix my device with all of my attempts failing. I have a HTC One M7 from Telus (Newfoundland, Canada) which is about 3 years old. It's in great condition and has been well taken care of. I had been using CM 12.1 and TWRP right up until a few days ago. My intentions were to bring my phone back to factory settings without any root capabilities as the newest update for Pokémon Go requires you to have an un-rooted device. Obviously my efforts to go back to factory settings were in vain as now my phone is basically one step away from being bricked. I can load up the bootloader just fine and acheive fastboot without any problems although anything beyond there fails everytime (ie. enter recovery mode).
I'm able to do stuff with it using ADB tools via my pc so not all hope is lost just yet. Could anyone provide step by step instructions on how to get the phone back to an untampered state as well as links to the files i'll need to do so? I have yet to find any ROM's for a TELUS M7 as well as the default recovery tools. I keep seeing links to utilities which apparently are a basic one-click-fix though none of them have worked thusfar (my most recent one is called "RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2.exe" which seems to work right up until it gets to the HEADER portion where it doesn't move past 5%)
I've since bought a new phone which is an extreme pain to use as, in my opinion, it's a huge downgrade from what i've been using (LG-K121)
Any and all help is muchly appreciated [:=
Click to expand...
Click to collapse
Please, post the output of "fastboot getvar all" (don't post your imei and serialno).
Sent from my HTC One using XDA Labs
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.127s
I recognize this is my own mistake as a result of being short sighted and not careful enough with my actions. Also, i'm willing to take any amount of time necessary to learn whatever skills may be required to resolve this issue (how to utilize certain tools properly, specific programming languages etc.)
kayohbe 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:
(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: PN0712000
(bootloader) cidnum: TELUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4266mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.127s
Click to expand...
Click to collapse
When a phone is S-ON you can only flash a RUU that is same or newer version than your actual version. Unfortunately your version-main is blank (this is bug caused by an old twrp version) so we can't exactly know the version it was running. The 1.61 hboot version and CID/MID suggest a 7.17.661.?? version. The newest RUU version available is 7.17.661.7
Try to flash it (from this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944)
Use instruction provided at post #1 of that thread to flash the RUU ****make sure to use the fastboot version provided in that thread***.
If your phone was running a newer bersion than that (i.e 7.17.661.52) the RUU won't flash and we'll have to try something else.
Btw did you already relocked your bootloader? If no make sure to reflash the stock recovery over twrp before re-locking.
alray said:
When a phone is S-ON you can only flash a RUU that is same or newer version than your actual version. Unfortunately your version-main is blank (this is bug caused by an old twrp version) so we can't exactly know the version it was running. The 1.61 hboot version and CID/MID suggest a 7.17.661.?? version. The newest RUU version available is 7.17.661.7
Try to flash it (from this thread: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944)
Use instruction provided at post #1 of that thread to flash the RUU ****make sure to use the fastboot version provided in that thread***.
If your phone was running a newer bersion than that (i.e 7.17.661.52) the RUU won't flash and we'll have to try something else.
Btw did you already relocked your bootloader? If no make sure to reflash the stock recovery over twrp before re-locking.
Click to expand...
Click to collapse
Alrighty, just to reiterate before I get into it, you suggested I choose the 7.17.661.7 version correct?
kayohbe said:
Alrighty, just to reiterate before I get into it, you suggested I choose the 7.17.661.7 version correct?
Click to expand...
Click to collapse
Yep try this version first and if it's not working we'll try something else. You'll have to relock your bootloader before flashing the ruu, male sure to flash the stock recovery (linked above) before relocking.
Sent from my HTC One using XDA Labs
alray said:
Yep try this version first and if it's not working we'll try something else. You'll have to relock your bootloader before flashing the ruu, male sure to flash the stock recovery (linked above) before relocking.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
My Bootloader has already been Relocked, should I be doing something else to get a working recovery on there before I begin flashing the RUU?
kayohbe said:
My Bootloader has already been Relocked, should I be doing something else to get a working recovery on there before I begin flashing the RUU?
Click to expand...
Click to collapse
No its to late, try the RUU.
Seems good [:=
Just finished the process & everything seems to be working just fine - i'm in the middle of the "optimizing apps 189 of 251" (das a lotta bloat lol) stage right now.
Any suggestions on what should be done next?
Also - thank you so friggen much for your help & I apologize for being so noob in these matters
kayohbe said:
Just finished the process & everything seems to be working just fine - i'm in the middle of the "optimizing apps 189 of 251" (das a lotta bloat lol) stage right now.
Any suggestions on what should be done next?
Also - thank you so friggen much for your help & I apologize for being so noob in these matters
Click to expand...
Click to collapse
no problem. Update your phone to the latest version before unlocking and rooting. The latest one is .52
One final question - is there a default recovery on there now that everything is set up and running properly or will I need to dig up a factory recovery, achieve S-OFF & flash it on there?
kayohbe said:
One final question - is there a default recovery on there now that everything is set up and running properly or will I need to dig up a factory recovery, achieve S-OFF & flash it on there?
Click to expand...
Click to collapse
When flashing a RUU, the stock recovery is installed on the phone. The stock recovery is very limited, it can be used to install ota updates, clear cache and factory reset. If you want to make a backup of your whole phone you'll need to unlock your bootloader and flash a custom recovery (preferably TWRP).
alray said:
When flashing a RUU, the stock recovery is installed on the phone. The stock recovery is very limited, it can be used to install ota updates, clear cache and factory reset. If you want to make a backup of your whole phone you'll need to unlock your bootloader and flash a custom recovery (preferably TWRP).
Click to expand...
Click to collapse
My only issue with going back to custom ROM's (which I waaay prefer over stock as stock ROM's are super limited in so many ways) is I will be prevented from playing Pokémon Go as Niantic have recently disallowed such operating systems from running their app altogether. I don't care for using apps which would be considered 'cheating' or 'exploiting' but with a custom ROM i'd be completely forced to stop playing it no matter how I choose to do so (yes it's silly that i'm basing my decision around that one simple game which isn't even all that great as far as Pokémon games go but it's what I do to pass time during my work breaks 6 nights a week).
Until a fail-safe workaround is made for this tiny issue, i'm stuck with Official 5.0.2 (blek!) and Sense - at the very least I can use a custom Launcher but that's about all I can do.
kayohbe said:
My only issue with going back to custom ROM's (which I waaay prefer over stock as stock ROM's are super limited in so many ways) is I will be prevented from playing Pokémon Go as Niantic have recently disallowed such operating systems from running their app altogether. I don't care for using apps which would be considered 'cheating' or 'exploiting' but with a custom ROM i'd be completely forced to stop playing it no matter how I choose to do so (yes it's silly that i'm basing my decision around that one simple game which isn't even all that great as far as Pokémon games go but it's what I do to pass time during my work breaks 6 nights a week).
Until a fail-safe workaround is made for this tiny issue, i'm stuck with Official 5.0.2 (blek!) and Sense - at the very least I can use a custom Launcher but that's about all I can do.
Click to expand...
Click to collapse
I played the game for 2-3 days at launch and it was easy to spoof a fake gps location to cheat. To do that I also had to hide the fact the I was using "mock location" from the developer options using an Xposed module or the game would detect it. I guess its also really easy to hide the fact the you are using a custom rom/root from pokémon go using the same method... Not tried but im sure it can be done.
I assume it was easy prior to the current update - they've cracked down on 'spoof players' about a week or so ago
Help for HTC - M7
Dear Sir
my phone stuck @HTC logo. not booting icant install new OS.
still S-On please help me to solve mobile software issue.
ready for the payment. if your solution success.
=-============================================
(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.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3AVW904592
(bootloader) imei: 359405054090020
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3952mV
(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
i dont know whether i downloded file corect or not
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed
need step by step instruction
1191 said:
Dear Sir
my phone stuck @HTC logo. not booting icant install new OS.
still S-On please help me to solve mobile software issue.
ready for the payment. if your solution success.
=-============================================
(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.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3AVW904592
(bootloader) imei: 359405054090020
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3952mV
(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
i dont know whether i downloded file corect or not
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_458803_signed
need step by step instruction
Click to expand...
Click to collapse
Yes you've download the right file.
Instructions how to flash: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
(see post #1)

Categories

Resources