Database Develop

[Q]Softbricked S-On Only have access to fastboot! Help!

Hi guys please Help me!
I tried installing the Google play 4.4 version on HTC one today half way through install I knocked it off my desk and the phone seem to restart and go to a blue screen with lines on it, for split second Google appeared then went back to the blue screen.
I know I havent damaged the phone physically as the phone can still get into revcovery and is still functioning there however I can't seem to find anything to get me to restore back to stock or anything.
Code:
(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:
(bootloader) version-misc: PVT SHIP S-ON
(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: 4197mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Heres the results from HTC One Toolkit, can anyone help me get my phone back up and running?!
Thanks Matt
~edit forgot to mention I panicked original and tried restoring the orignal rom back on so ended up locking the bootloader and trying to install stock

fblade1987 said:
Hi guys please Help me!
I tried installing the Google play 4.4 version on HTC one today half way through install I knocked it off my desk and the phone seem to restart and go to a blue screen with lines on it, for split second Google appeared then went back to the blue screen.
I know I havent damaged the phone physically as the phone can still get into revcovery and is still functioning there however I can't seem to find anything to get me to restore back to stock or anything.
Code:
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FAxxxxxxxxxxxxx
(bootloader) imei: 3xxxxxxxxxxxxxxxxx
(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: 4197mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Heres the results from HTC One Toolkit, can anyone help me get my phone back up and running?!
Thanks Matt
Click to expand...
Click to collapse
First, remove IMEI and s/n from your post, we dont need to see those.
Second, plenty of options for you to get a ROM onto your phone (your bootloader is unlocked, right):
1- OTG cable
2- adb push
3- adb sideload
4- worst case: run an RUU.EXE: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
(need to be locked for that if S-On)
5- use revone to get s-off on hboot 1.44
---------- Post added at 05:59 PM ---------- Previous post was at 05:57 PM ----------
fblade1987 said:
~edit forgot to mention I panicked original and tried restoring the orignal rom back on so ended up locking the bootloader and trying to install stock
Click to expand...
Click to collapse
PANIC = not good, you end up doing stuff you shouldnt!!!
so either unlock bootloader again and follow one of the three options above
or run the RUU.exe I linked
EDIT:
(bootloader) version-main:
Click to expand...
Click to collapse
WTF, where's your firmware?

That is what is scaring me...
I'm about to try the RUU.exe you linked I will report back to you
Thanks in advance Matt

fblade1987 said:
That is what is scaring me...
I'm about to try the RUU.exe you linked I will report back to you
Thanks in advance Matt
Click to expand...
Click to collapse
I'm in the same boat, how'd it go?

I am guessing if the build.prop can't be read, main-ver doesn't show up?

SaHiLzZ said:
I am guessing if the build.prop can't be read, main-ver doesn't show up?
Click to expand...
Click to collapse
mainversion in fastboot getvar reads it directly from the misc partition (mmcblk0p19 on the M7_U/UL), not from build.prop. so even if you have no OS installed whatsoever, it should still show you a version number.

Thats interesting to know, thanks.. That RUU should fix it however

SaHiLzZ said:
Thats interesting to know, thanks.. That RUU should fix it however
Click to expand...
Click to collapse
hey mate, how's it going
there's a tool for the mainversion too; if you're interested: http://forum.xda-developers.com/showthread.php?t=2526154
never used it, so no clue if it's any good. (did have a look at the source code though and it just writes whatever you want (10 digits, if i remember correctly) to the misc partition.)

[Q] I messed it up...

Long story short. I accidently erased my OS so when i turn my phone on it makes it to the HTC quietly different logo and stops. I can get into fastboot and recovery and all of that but i have had zero success at loading a new ROM. Every time i try to flash one or push one or sideload one i get some kind of error so i can't get it on to my phone. Here are my specs:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA34KS903491
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4331mV
(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 originally tried to root it to be able to SIM unlock the phone but i went a little too far. at this point i'd like to just put it back to stock and start over but i will take anything. Any help would be appreciated. I've been searching the internet and forums for about 3 weeks now trying to figure this out.

joshmccormick20 said:
Long story short. I accidently erased my OS so when i turn my phone on it makes it to the HTC quietly different logo and stops. I can get into fastboot and recovery and all of that but i have had zero success at loading a new ROM. Every time i try to flash one or push one or sideload one i get some kind of error so i can't get it on to my phone. Here are my specs:
I originally tried to root it to be able to SIM unlock the phone but i went a little too far. at this point i'd like to just put it back to stock and start over but i will take anything. Any help would be appreciated. I've been searching the internet and forums for about 3 weeks now trying to figure this out.
Click to expand...
Click to collapse
This will get you fixed up try the latest RUU first if it fails go the long route
Any questions post them here

BD619 said:
This will get you fixed up try the latest RUU first if it fails go the long route
Any questions post them here
Click to expand...
Click to collapse
Thank you, i'll give it a shot

joshmccormick20 said:
Thank you, i'll give it a shot
Click to expand...
Click to collapse
Good luck...I'll be around if you have questions.

BD619 said:
Good luck...I'll be around if you have questions.
Click to expand...
Click to collapse
Ok, i downloaded the RUU and it went about half way through then i got ERROR 155 and it says i need to get the correct version of RUU....:crying:

joshmccormick20 said:
Ok, i downloaded the RUU and it went about half way through then i got ERROR 155 and it says i need to get the correct version of RUU....:crying:
Click to expand...
Click to collapse
4.06.651.2? If so you could try some things like different USB Port(USB 2 work best),different cable,different PC...but you may have already updated beyond that meaning you will have to go the long route

BD619 said:
4.06.651.2? If so you could try some things like different USB Port(USB 2 work best),different cable,different PC...but you may have already updated beyond that meaning you will have to go the long route
Click to expand...
Click to collapse
What do you consider the "long route"?

joshmccormick20 said:
What do you consider the "long route"?
Click to expand...
Click to collapse
Follow the steps in the guide
Do it yourself rather then the RUU doing it...same outcome other then you will have a stock rooted rom rather then a factory rom.

BD619 said:
Follow the steps in the guide
Do it yourself rather then the RUU doing it...same outcome other then you will have a stock rooted rom rather then a factory rom.
Click to expand...
Click to collapse
I was afraid you'd say that. Here's my other problem. I can only get ADB to work using Philz touch recovery. And when i try to push the Zip file or anything like that i get some kind of error which doesnt let it complete. I'm sure you've been through this with other people hundreds of times so forgive me. I get a "failed to write data protocol <no status>"

joshmccormick20 said:
I was afraid you'd say that. Here's my other problem. I can only get ADB to work using Philz touch recovery. And when i try to push the Zip file or anything like that i get some kind of error which doesnt let it complete. I'm sure you've been through this with other people hundreds of times so forgive me. I get a "failed to write data protocol <no status>"
Click to expand...
Click to collapse
Did you re-lock your bootloader?

BD619 said:
Did you re-lock your bootloader?
Click to expand...
Click to collapse
I relocked it and then unlocked it again, tried both ways...i'm about to throw it away.

joshmccormick20 said:
I relocked it and then unlocked it again, tried both ways...i'm about to throw it away.
Click to expand...
Click to collapse
Since you are s-on it needs to be locked/re-locked for the ruu or to flash the firmware.
Add me on hangouts the email addy is in my rescue thread.

BD619 said:
Since you are s-on it needs to be locked/re-locked for the ruu or to flash the firmware.
Add me on hangouts the email addy is in my rescue thread.
Click to expand...
Click to collapse
I'm not sure about the hangouts thing, but I did just relock the bootloader again and ran the RUU you told me to and it got almost all of the way done and i got ERROR 152 image update error

joshmccormick20 said:
I'm not sure about the hangouts thing, but I did just relock the bootloader again and ran the RUU you told me to and it got almost all of the way done and i got ERROR 152 image update error
Click to expand...
Click to collapse
You can add a hangout extension to your chrome browser or use google+
https://chrome.google.com/webstore/search/hangout extension?utm_source=chrome-ntp-icon

BD619 said:
You can add a hangout extension to your chrome browser or use google+
https://chrome.google.com/webstore/search/hangout extension?utm_source=chrome-ntp-icon
Click to expand...
Click to collapse
[email protected] i downloaded it

joshmccormick20 said:
Long story short. I accidently erased my OS so when i turn my phone on it makes it to the HTC quietly different logo and stops. I can get into fastboot and recovery and all of that but i have had zero success at loading a new ROM. Every time i try to flash one or push one or sideload one i get some kind of error so i can't get it on to my phone. Here are my specs:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA34KS903491
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4331mV
(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 originally tried to root it to be able to SIM unlock the phone but i went a little too far. at this point i'd like to just put it back to stock and start over but i will take anything. Any help would be appreciated. I've been searching the internet and forums for about 3 weeks now trying to figure this out.
Click to expand...
Click to collapse
My wife got some kind of corrupt file or virus on her phone and I ended up having to wipe EVERYTHING, OS, SDCARD, only thing on phone was bootloader and old version of TWRP, heres how I fixed it and it worked great.... Download the latest TWRP and flash it via fastboot, make sure you have the latest SDK tools on your computer, sideload the rom of your choice, there are instructions on the TWRP website, you should be good to go....

[Q] Returning to stock [SOLVED]

I wanted to experiment a bit with rooting. I guess I wasn't extremely informed. Anyways, I used the Guru reset(I can't post outside links) , and I guess did not have the matching software. My touchscreen does not work, I tried to do the OTA update like suggested but after the restart to install the update it said the update failed. Now my Wi-Fi is stuck "turning on" so I can't try to run the update again. I don't know what to do, and I can't find it. I don't know what else to include so that you can help me but if you have questions I'll answer to the best of my knowledge.

redelmos said:
I wanted to experiment a bit with rooting. I guess I wasn't extremely informed. Anyways, I used the Guru reset(I can't post outside links) , and I guess did not have the matching software. My touchscreen does not work, I tried to do the OTA update like suggested but after the restart to install the update it said the update failed. Now my Wi-Fi is stuck "turning on" so I can't try to run the update again. I don't know what to do, and I can't find it. I don't know what else to include so that you can help me but if you have questions I'll answer to the best of my knowledge.
Click to expand...
Click to collapse
start by posting a "fastboot getvar all" (excluding IMEI and s/n)

nkk71 said:
start by posting a "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT361W903656
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4179mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

redelmos said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
1- edit your post and remove IMEI (that shouldnt be shared publicly)
2- since you are S-On you need to relock your bootloader using fastboot oem lock then you can use this RUU.EXE:
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
note that your bootloader will say RELOCKED not LOCKED, the only way to set it back to LOCKED is if you are S-Off. but the phone will be completely stock after the RUU, so unless you're selling the phone or going for warranty, then RELOCKED shouldnt matter.

nkk71 said:
1- edit your post and remove IMEI (that shouldnt be shared publicly)
2- since you are S-On you need to relock your bootloader using fastboot oem lock then you can use this RUU.EXE:
RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2.exe
note that your bootloader will say RELOCKED not LOCKED, the only way to set it back to LOCKED is if you are S-Off. but the phone will be completely stock after the RUU, so unless you're selling the phone or going for warranty, then RELOCKED shouldnt matter.
Click to expand...
Click to collapse
It worked, Thank you! I've ran multiple RUU exes and I've tried some .zips but all of them were the wrong version I guess. I've been working on this for around 4 days now, and this is a huge load off my mind.

redelmos said:
It worked, Thank you! I've ran multiple RUU exes and I've tried some .zips but all of them were the wrong version I guess. I've been working on this for around 4 days now, and this is a huge load off my mind.
Click to expand...
Click to collapse
if all is good now, can you also edit main thread title to include [SOLVED], thanks

nkk71 said:
if all is good now, can you also edit main thread title to include [SOLVED], thanks
Click to expand...
Click to collapse
I'm not sure how to edit the title.
Edit: Never mind, it was in advanced, but I also don't know how to delete posts or else I would have deleted this.

redelmos said:
I'm not sure how to edit the title.
Click to expand...
Click to collapse
edit the first post -> at the bottom of the edit window, click Go Advanced, and then you can edit main title

[Q] Looking for guidance on restoring my phone; stuck in boot loop

I used O.M.J's RUU but i am still getting ERROR 155 The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again. I'm not sure what I am doing wrong. I do notice that when I'm at the screen that asks me to update my image my current image info is empty.
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:
(bootloader) imei:
(bootloader) meid:
(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

Did you relock the bootloader? Just go through the steps in the post again, or look in the comments for it. I don't own an HTC one but just trying to help

That RUU is too old it won't work use THIS

Error 115 is you didn't lock your bootloader. As seen her in post 15-http://forum.xda-developers.com/showthread.php?t=2250904&page=2
Tell me if anything works!

K03WL3R said:
Did you relock the bootloader? Just go through the steps in the post again, or look in the comments for it. I don't own an HTC one but just trying to help
Click to expand...
Click to collapse
I relocked the bootloader. I just saw a post for Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip but the OP says its for hboot 1.56 and it looks like mine is 1.57 so im a little nervous about trying it.

Kunigaz said:
I relocked the bootloader. I just saw a post for Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip but the OP says its for hboot 1.56 and it looks like mine is 1.57 so im a little nervous about trying it.
Click to expand...
Click to collapse
I would look around, did I get the correct link to what you are using?

K03WL3R said:
I would look around, did I get the correct link to what you are using?
Click to expand...
Click to collapse
The link you posted didnt work

BD619 said:
That RUU is too old it won't work use THIS
Click to expand...
Click to collapse
thank you for the link. which ruu do i use?

Kunigaz said:
The link you posted didnt work
Click to expand...
Click to collapse
Sorry I just found a post about re-locking the bootloader

Kunigaz said:
thank you for the link. which ruu do i use?
Click to expand...
Click to collapse
Follow the guide if you say hboot is1.57 there is no RUU available

BD619 said:
Follow the guide if you say hboot is1.57 there is no RUU available
Click to expand...
Click to collapse
I have been trying to flash the firmware.zip but every time i download the zip file it say invalid file. So i repaired it with zip repair and got cannot open 'firmeware.zip' error. I also tried clearing my cache and browsing data on crome with not luck.

Kunigaz said:
I have been trying to flash the firmware.zip but every time i download the zip file it say invalid file. So i repaired it with zip repair and got cannot open 'firmeware.zip' error. I also tried clearing my cache and browsing data on crome with not luck.
Click to expand...
Click to collapse
I've never had that happen on my android, it has happened on my iPad but try it on a pc or something.

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.