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.
Related
First I'd like to apologise if i'm posting at the wrong place and if i do, feel free to point me in the right direction.
I have an HTC One, branded (Croatian Vipnet).
I then rooted it using this guide http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/ I didn't put a custom ROM on, literally just followed that guide (unlock bootloader > flash TWRP > install SuperSU > done).
So currently running software number 2.24.401.8. I'm looking to unroot (a few reasons, one of which is to install the current update).
Because I left the ROM alone I suppose I should just be able to recover to stock recovery back on, then lock the bootloader then run the update, but I'm struggling to find anything clear on this, or a link to what looks like the right stock recovery.
I'm thinking I don't need the full RUU since I didn't change the ROM.
Earlier, I decided to go full RUU so I did S-Off, removed 'Tampered' sign and 'locked' according to this topic and now i'm reluctant to go with RUU install because a) i can't find the right one (check my fastboot report) and b) I could mess things up bricking my phone.
I would be grateful if someone could shed a little light on this issue and point me in the right direction. I would also appreciate the least invasive method which doesn't include full RUU but if that isn't an option than please help me to pick the right RUU for my phone (having in mind that i'm noob on this).
my fastboot getvar all report:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3980mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
jhercog said:
First I'd like to apologise if i'm posting at the wrong place and if i do, feel free to point me in the right direction.
I have an HTC One, branded (Croatian Vipnet).
I then rooted it using this guide http://htconeroot.com/htc-one-root/how-to-root-htc-one-windowsmaclinux/ I didn't put a custom ROM on, literally just followed that guide (unlock bootloader > flash TWRP > install SuperSU > done).
So currently running software number 2.24.401.8. I'm looking to unroot (a few reasons, one of which is to install the current update).
Because I left the ROM alone I suppose I should just be able to recover to stock recovery back on, then lock the bootloader then run the update, but I'm struggling to find anything clear on this, or a link to what looks like the right stock recovery.
I'm thinking I don't need the full RUU since I didn't change the ROM.
Earlier, I decided to go full RUU so I did S-Off, removed 'Tampered' sign and 'locked' according to this topic and now i'm reluctant to go with RUU install because a) i can't find the right one (check my fastboot report) and b) I could mess things up bricking my phone.
I would be grateful if someone could shed a little light on this issue and point me in the right direction. I would also appreciate the least invasive method which doesn't include full RUU but if that isn't an option than please help me to pick the right RUU for my phone (having in mind that i'm noob on this).
my fastboot getvar all report:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3980mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
Easiest way if your on stock rom is to just flash the stock recovery and install the OTA.
http://forum.xda-developers.com/showthread.php?t=2545227
Your recovery is on that page. Just look down until you find 1.29.401.12 HTC (without Taiwan, Asia and Australia). Flash that and then download the update via the rom
nateboi81 said:
Easiest way if your on stock rom is to just flash the stock recovery and install the OTA.
http://forum.xda-developers.com/showthread.php?t=2545227
Your recovery is on that page. Just look down until you find 1.29.401.12 HTC (without Taiwan, Asia and Australia). Flash that and then download the update via the rom
Click to expand...
Click to collapse
Thank you for your prompt answer
I have one more question before I proceed with the instructions. Does that mean that i should be back on full stock? I.e. claiming back the warranty should be ok?
jhercog said:
Thank you for your prompt answer
I have one more question before I proceed with the instructions. Does that mean that i should be back on full stock? I.e. claiming back the warranty should be ok?
Click to expand...
Click to collapse
Their are many more steps involved in retuning a phone for warranty..
see @nkk71 Superguide here
http://forum.xda-developers.com/showthread.php?t=2541082
Yes what he said. It's important to mention why for example warranty to we can answer as detailed as possible..good luck
Sent from my HTC One using XDA Premium 4 mobile app
@clsA
I just flashed to my stock recovery following your advice and everything went well.
Now i'm going to read Superguide by nkk71 you recommended. Thank you for helping me!
@nateboi81
Yes what he said. It's important to mention why for example warranty to we can answer as detailed as possible..good luck
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No particular reason (for now). However, recently i noticed problems with charging. I plugged the phone into charger and the battery icon played as the phone was charging. When I disconnected the cable, the icon showed the red line as if the battery was on it's bare minimum. I restarted the phone a few times and managed to charge the battery. That got me into thinking about restoring the phone in original state in case of necessary service or RMA.
So far, so good. The phone is charging normally and everything is working as expected but i would like to return it to original state anyway. At least to inform myself how can this be done prior to any failure.
Also, I could sell that thing easier in it's original state.
This was my first time messing with my phones ROM, I am completely new to this, and I bricked my phone. Here is what happened.
I rooted my phone using the guide from htconeroot.com
Everything worked fine.
Then I followed a guide from htconeroot to install android 4.4 kitkat ROM
That is when my phone got stuck in bootloader. I could run recovery with clockworkmod but when i went to the back up file in my sdcard the folder was empty. I tried factory reset and erasing cache to no avail. I finally found a guide by qbking77 called "how to unroot/unbrick the htc one to stock" and have been attempting various RUU versions trying to get it to take. I always get ERROR 155 The ROM Update Utility cannot update your Android phone. After running the RUU I can no longer run recovery with clockworkmod.
I have spent all weekend trying to educate myself and get this fixed but I am lost.
Here is my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 0000000000000
(bootloader) imei:00000000000000000
(bootloader) meid: 0000000000000000
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3808mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you in advance for any advice.
Well the first thing I noticed is you have an m7 wls, this is the spirint version of the HTC one, completely different to the normal version, so stop flashing things before you really do brick your phone, if you can get into the bootloader then your not bricked, yet, if you continue to try and flash wrong things you stand a high chance of messing up your blocks and partitions. Get yourself over to the m7 spirint forums for help.from here, just search for it above in the find your device box.
Seanie280672 said:
Well the first thing I noticed is you have an m7 wls, this is the spirint version of the HTC one, completely different to the normal version, so stop flashing things before you really do brick your phone, if you can get into the bootloader then your not bricked, yet, if you continue to try and flash wrong things you stand a high chance of messing up your blocks and partitions. Get yourself over to the m7 spirint forums for help.from here, just search for it above in the find your device box.
Click to expand...
Click to collapse
Didn't realize they had separate forum for the different service providers. ty.
Kunigaz said:
Didn't realize they had separate forum for the different service providers. ty.
Click to expand...
Click to collapse
Your welcome, not a different service provider, a different phone, it's not a gsm phone.
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!
Hi all, i have a problem with my device - get stuck on "htc" white screen - then reboot after 1 min +-.
Already unlocked bootloader and tried to flash few roms with no success - still got the same problem.
Please tell me what Rom do i need for GSM international device in order to return it to factory state.
I also agree to relock it and using RUU in oreder to fix my problem... just dont no which RUU to use... from ISRAEL
Please help :crying::crying:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 3914mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
So first of all, I assume you have successfully unlocked your bootloader for flashing a ROM, recovery etc. You can check it if you boot into bootloader by pressing vol. up and power button. S-off is required to manually do a firmware upgrade. S-off is gained via many methods. There are many threads in the general or FAQ section ( http://forum.xda-developers.com/showthread.php?t=2488772 ).
I recommend you to read any s-off related thread in general and FAQ. This is also a good information for it: http://forum.xda-developers.com/showthread.php?t=2431515
The newest firmware is http://forum.xda-developers.com/showthread.php?t=2965090 . Also usually there is described how you flash it.
Basically there are 3 kinds of roms you can use: stock CyanogenMod nightlies, Google play edition or sense edition.
I recommended you that u get the supercid, so you can easily switch between ROMs and you have less problems with a ruu (in case you brick something, a ruu is a good alternative to a repair shop. It is a stock nandroid backup). How to supercid is described here: http://forum.xda-developers.com/showthread.php?t=2317536 .
So after you s-offed and firmware upgraded your phone, you have to get the newest twrp recovery. Just Google twrp and go on their site. If you search for your phone you can download the recovery and also read how to flash it.
I used the three different roms:
InsertCoin Sense ROM: http://forum.xda-developers.com/showthread.php?t=2694142
GPE: http://forum.xda-developers.com/showthread.php?t=2963927
CyanogenMod: http://download.cyanogenmod.org/?device=m7
But first, you must answer yourself the question if you want to install custom roms. Now that Lollipop is also out there, there is no basically need for a custom rom. Sure custom roms can give you more features, tweaks and other stuff, but if you don't really need it, you can just go back to full stock device via: http://forum.xda-developers.com/showthread.php?t=2358738
Take the disclaimers serious. Though anyone will help you if he/she can, but if you do something wrong you can just blame yourself. No one will buy you a new phone if you bricked it. You are fully responsible for what you do with your phone. But I can say that if you just read all the links I provided, check everything 3 times or more, it is a pretty easy thing to do all the mind blowing stuff.
If you have any questions, just ask.
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)