Hello XDA, I have been looking around and I didn't see much stuff on AT&T HTC One M8,
I am hoping this thread will be of use for some of you.
THIS IS FOR ADVANCED USERS ONLY
I AM NOT RESPONSIBLE FOR YOUR PHONE
YOU ARE DOING THIS AT YOUR OWN RISK
YOU HAVE BEEN WARNED
Stock Backups
1.12.502.18
1.58.502.1
MAKE SURE YOU DO A FACTORY RESET AFTER RESTORING
Stock Recoveries
1.12.502.18
1.58.502.1
OTAs
1.12.502.18_to_1.58.502.1_UPDATE
Radio
radio_1.16.21331931.LA11G_20.31A.4145.02L
Other Thoughts..
As of 8/23/2014 I still receive the 1.12.502.18 to 1.58.502.1 OTA Update..
If this helped you in anyway please..
DONATE
Thanks
MLIGN said:
Hello XDA, I have been looking around and I didn't see much stuff on AT&T HTC One M8,
I am hoping this thread will be of use for some of you.
THIS IS FOR ADVANCED USERS ONLY
I AM NOT RESPONSIBLE FOR YOUR PHONE
YOU ARE DOING THIS AT YOUR OWN RISK
YOU HAVE BEEN WARNED
Stock Backups
1.12.502.18
1.58.502.1
MAKE SURE YOU DO A FACTORY RESET AFTER RESTORING
Stock Recoveries
1.12.502.18
1.58.502.1
OTAs
1.12.502.18_to_1.58.502.1_UPDATE
Radio
radio_1.16.21331931.LA11G_20.31A.4145.02L
Other Thoughts..
As of 8/23/2014 I still receive the 1.12.502.18 to 1.58.502.1 OTA Update..
If this helped you in anyway please..
DONATE
Click to expand...
Click to collapse
could you please post the latest OTA 2.23 with android 4.4.3 thanks
Nobody has it, run the ruu its safer and it appears to not have the [email protected] drain that they pulled the update because of
JEANRIVERA said:
could you please post the latest OTA 2.23 with android 4.4.3 thanks
Click to expand...
Click to collapse
JEANRIVERA said:
could you please post the latest OTA 2.23 with android 4.4.3 thanks
Click to expand...
Click to collapse
I haven't been running the AT&T version of this phone for the past week..
I also heard that they pulled the OTA..
As soon as it is back. I'll go back to AT&T to get the OTA, Radio, and Stock Backup for you all!
Which restore is the 4.4.2? My cousins phone is stuck rebooting, so I reset it and its stuck on boot.
AT&T stock recovery 2.23.502.3
For those that might need it, here is the stock recovery from the 2.23 RUU. If anyone is interested, I could also add to this post exactly how I get the recovery. It took me about 2 hours to get all the info together that I needed in order to pull it off.
Steps to extract stock recovery:
1. Flash stock RUU.
2. Boot into TWRP. Don't flash TWRP to phone, but boot into it running on computer. Do this by using the command "fastboot boot recovery.img". Same steps as flashing a new recovery, but in this case you just boot the phone into this version of recovery. You can use the instructions at the link below, just replace flash with boot.
http://teamw.in/project/twrp2/225
3. Root phone by installing SuperSU. Flash the SuperSU.zip from your booted recovery.
4. Reboot phone and update SuperSU from the play store.
5. Connect phone to computer and use ADB to copy recovery partition to img file on phone. I used the guide at this page:
http://forum.xda-developers.com/showthread.php?t=2450045
For the AT&T M8 the block you need to dump is mmcblk0p43
So the command will be this:
adb shell
su
dd if=/dev/block/mmcblk0p43 of=/sdcard/recovery.img
Is the 1.58.502.1 stock backup without root?
Answerd my own question by flashing it,no root witch is cool cause all I would have to do to receive ota is flash the stock recovery alongside. Thank you for this ,I used it to go back to stock and use SunShine to S-OFF
Sent from my SM-T700 using Tapatalk
how do you actually use these to get back to stock?
ive had a botched attempt at updating the firmware and installing venomone.
i tried installing these via the all in one kit but it didnt work, it had me try relocking my bootloader and still didnt work.
so now im stuck with a relocked bootloader, and cant figure out how to get back to stock =/
The_Zodiac said:
how do you actually use these to get back to stock?
ive had a botched attempt at updating the firmware and installing venomone.
i tried installing these via the all in one kit but it didnt work, it had me try relocking my bootloader and still didnt work.
so now im stuck with a relocked bootloader, and cant figure out how to get back to stock =/
Click to expand...
Click to collapse
Download zip file and extract it with root explorer of choice
:navigate to extract location and open the extracted folder,once in that folder you should open the next folder and copy the numbered folder over to your TWRP/backup folder as if it was a backup you made.
Or start searching how to RUU back to stock with adb/fastboot
Sent from my SM-T700 using Tapatalk
jball said:
Download zip file and extract it with root explorer of choice
:navigate to extract location and open the extracted folder,once in that folder you should open the next folder and copy the numbered folder over to your TWRP/backup folder as if it was a backup you made.
Or start searching how to RUU back to stock with adb/fastboot
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
yeah ended up finding the RUU to get back to stock, now my problem is i cant re unlock my bootloader
(Thread here http://forum.xda-developers.com/att-htc-one-m8/help/help-getting-to-stock-att-m8-t2912921)
thanks for helping man
With the OP permission I could make a video of how to use the stock backup from downloading of the file to executing the flashing for a more visual learning
Sent from my SM-T700 using Tapatalk
---------- Post added at 09:25 AM ---------- Previous post was at 09:22 AM ----------
The_Zodiac said:
yeah ended up finding the RUU to get back to stock, now my problem is i cant re unlock my bootloader
(Thread here http://forum.xda-developers.com/att-htc-one-m8/help/help-getting-to-stock-att-m8-t2912921)
thanks for helping man
Click to expand...
Click to collapse
Are you still using the tool kit ?
Try your original key and use the adb/fastboot method .or how about posting the steps you've taken in attempts at unlocking your bootloader this time
Sent from my SM-T700 using Tapatalk
jball said:
With the OP permission I could make a video of how to use the stock backup from downloading of the file to executing the flashing for a more visual learning
Sent from my SM-T700 using Tapatalk
---------- Post added at 09:25 AM ---------- Previous post was at 09:22 AM ----------
Are you still using the tool kit ?
Try your original key and use the adb/fastboot method .or how about posting the steps you've taken in attempts at unlocking your bootloader this time
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
was able to get it to work with a new unlock.bin from htd.dev
Great work. Helpful!
Thanks
I am currently on CM11 and want to get back to stock and update to latest firmware. I will need to flash both the backup and recovery 1.12.502.18 and then ota update. Then I can reflash a custom recovery again. Is that correct?
Here is my info
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *REMOVED
(bootloader) imei: *REMOVED
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
MLIGN said:
Hello XDA, I have been looking around and I didn't see much stuff on AT&T HTC One M8,
I am hoping this thread will be of use for some of you.
THIS IS FOR ADVANCED USERS ONLY
I AM NOT RESPONSIBLE FOR YOUR PHONE
YOU ARE DOING THIS AT YOUR OWN RISK
YOU HAVE BEEN WARNED
Stock Backups
1.12.502.18
1.58.502.1
MAKE SURE YOU DO A FACTORY RESET AFTER RESTORING
Stock Recoveries
1.12.502.18
1.58.502.1
OTAs
1.12.502.18_to_1.58.502.1_UPDATE
Radio
radio_1.16.21331931.LA11G_20.31A.4145.02L
Other Thoughts..
As of 8/23/2014 I still receive the 1.12.502.18 to 1.58.502.1 OTA Update..
If this helped you in anyway please..
DONATE
Click to expand...
Click to collapse
how about earlier hboots ,to downgrade
mws1986 said:
I am currently on CM11 and want to get back to stock and update to latest firmware. I will need to flash both the backup and recovery 1.12.502.18 and then ota update. Then I can reflash a custom recovery again. Is that correct?
Here is my info
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *REMOVED
(bootloader) imei: *REMOVED
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Did you ever figure it out? I'm on the same boat and need to update my firmware. I have the same info as you, s-on, same bootloader version, same radio, etc. That's what I was thinking of doing. Flash stock rom, flash recovery, get ota, then flash twrp recovery again. I'm on att as well.
Gilbertinho said:
Did you ever figure it out? I'm on the same boat and need to update my firmware. I have the same info as you, s-on, same bootloader version, same radio, etc. That's what I was thinking of doing. Flash stock rom, flash recovery, get ota, then flash twrp recovery again. I'm on att as well.
Click to expand...
Click to collapse
That probably isn't going to do what you want. OTA will only update you to Android 4.4.2 and hboot 3.16, which is what you've already got.
What version firmware are you trying to update to. Or asked another way, what ROM are you trying to run? The issue is a bit complicated now, as the current custom ROMs are split on firmware 3.x or 4.x (neither of which are "officially" released by AT&T yet).
redpoint73 said:
That probably isn't going to do what you want. OTA will only update you to Android 4.4.2 and hboot 3.16, which is what you've already got.
What version firmware are you trying to update to. Or asked another way, what ROM are you trying to run? The issue is a bit complicated now, as the current custom ROMs are split on firmware 3.x or 4.x (neither of which are "officially" released by AT&T yet).
Click to expand...
Click to collapse
I am currently running ViperOneM8 1.8 and am trying to run ViperOneM8 2.5.0 which requires you to have the 4.4.3 base firmware. From my understanding AT&T released this OTA. The newer roms require 4.4.4 which AT&T has yet to release. I am not trying to update to 4.4.4 since that requires S-OFF, which I dont want to/don't know how to do. Thanks for the reply by the way!
Related
LOOKS LIKE S-OFF FOR 1.54 HAS HAPPENED. NO NEED TO DOWNGRADE CHECK THE POST HERE
MODS Lock This One Up!!!
I was about to give up on s-off since I got the OTA update but there is hope.
I got s-off doing the following:
1.) Unlock your device via HTCDev
2.) Download and flash CWM Recovery
3.) Flash the stock nandroid for your phone...
a. TWRP Nandroid AT&T Thanks JEANRIVERA
b. TWRP Nandroid AT&T Thanks JEANRIVERA
c. TWRP Nandroid AT&T Thanks cschmittIf any one has other links to other devices let me know... I think this will work on all of the variants.:laugh:
Please note that this nandroid was made with TWRP and may need to be restored with TWRP.
On a side note... The original nandroid that I had linked was also created with TWRP and as I was unable to locate the restore function in my TWRP I did restore with CWM.
4.) then relock your device
Code:
fastboot oem lock
5.) grab 1847-ruu-m7-ul-jb-50-cingular-12650212.exe here and run it... Thanks cschmitt
6.) goto the tutorial here... and follow the directions...
This has worked for me... and I hope this will help someone else. All the information came from other people, I just happened to put it in the right order.
If this did not work for you there are New instructions here... Thanks domohan
IT IS IMPORTANT TO DO ALL THE STEPS IN ORDER...
I take no responsibility for anything you do with this information.
If I forgot to mention your name specifically... I'm Sorry and Thanks!
If I helped you hit the thank you button.
I see, new hboot. Downgrading it is then. Interesting that they haven't forced htc to shut off the unlocking service.
worked as advertised
Thanks a lot. A process for sure but worked for me following the ATT OTA update to .15. Although, I went on to follow the guide at wonderhowto dot com for installing the ASOP Google Edition. Thanks again.
Yeah that was the update that got me ... I am really glad that it worked for someone else... :laugh:
I am having trouble flashing the nandroid. I have tried to both flash the zip as well as unpack it and try to do a restore. Any thoughts?
---------- Post added at 06:33 PM ---------- Previous post was at 05:38 PM ----------
Ok, I actually flashed this one http://forum.xda-developers.com/showthread.php?t=2252959
Then ran the .12 RUU and am now S-OFF. Thanks for this!
well i am glad you got that working... The way i did the nandroid was by extracting the zip to clockworkmod\backups ... then choosing restore... I had TWRP but could not find the restore Nandroid option.
The only way I see this actually working is that the RUU just checks the HBOOT version, and not the build date. Otherwise, the .12 RUU would fail to install because the OTA HBOOT has a newer build date.
If this is true, then all AT&T users better get S-OFF now (if they know what S-OFF does). I have a feeling the 4.2.2 update will come out with a newer HBOOT with a higher number. Then surely, any 4.1.2 RUU will not work.
In any case, it seems to be working for those of us who weren't paying attention and downloaded the OTA... But the message is still S-OFF now while you can, 'cause they will patch the thing eventually.
I was getting Error = -6 codes and this method worked perfectly for me! Thanks so much!
This did not work for my situation...
I had S-OFF, set my CID to 11111111 and installed the latest GE rom. I decided to go back to stock, and made the mistake of S locking without knowing that I could not go back on HBOOT 1.54. Now I'm S-ON with CID 11111111, HBOOT 1.54 and Radio 4A.18
I tried this fix... I get stuck on the RUU, it show sending... but after about 5min it errors out...
Is there any hope for my situation?
This was what in my RUU log...
<T171817><DEBUG><OUT>sending 'zip'... (1029872 KB) FAILED (data transfer failure (Too many links))</OUT>
i used this and it worked flawlessly for me, great looking out man. im now s-off with tampered removed
TabascoJoe said:
This did not work for my situation...
I had S-OFF, set my CID to 11111111 and installed the latest GE rom. I decided to go back to stock, and made the mistake of S locking without knowing that I could not go back on HBOOT 1.54. Now I'm S-ON with CID 11111111, HBOOT 1.54 and Radio 4A.18
I tried this fix... I get stuck on the RUU, it show sending... but after about 5min it errors out...
Is there any hope for my situation?
This was what in my RUU log...
<T171817><DEBUG><OUT>sending 'zip'... (1029872 KB) FAILED (data transfer failure (Too many links))</OUT>
Click to expand...
Click to collapse
I'm not totally sure...
1.) do you have unlock from htcdev?
2.) can you flash a recovery?
a. if so there is hope to get back to at least a working phone till a new exploit for 1.54 is found.
b. Are you sure you re-locked your phone...
Code:
fastboot oem lock
c. SUPER CID - (allows you to flash ANY ROM to the device regardless of the carrier. Just click RUU.EXE) So make sure the phone is locked and flash an older RUU. Then revone and you should be good to go my friend.
let me know if this works!
...and remember to hit the thank you button!
INeFFeCTiVE said:
I'm not totally sure...
1.) do you have unlock from htcdev?
2.) can you flash a recovery?
a. if so there is hope to get back to at least a working phone till a new exploit for 1.54 is found.
b. Are you sure you re-locked your phone...
Code:
fastboot oem lock
c. SUPER CID - (allows you to flash ANY ROM to the device regardless of the carrier. Just click RUU.EXE) So make sure the phone is locked and flash an older RUU. Then revone and you should be good to go my friend.
let me know if this works!
...and remember to hit the thank you button!
Click to expand...
Click to collapse
I have a working phone. I have an unlock from htcdev. i have locked it, i can flash roms and recovery in twrp.
Its when I try an RUU it get suck on sending.... and errors out
Could it be my Main Version? I used misc tool to try to get back to 1.26.502.10, but can never get it to write the last digit correctly. Here is my getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.010
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 3999mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I guess I was wrong on being SuperCID. Using the misctool what should I change my main version to, and how?
Thanks
Here are the steps I did to unlock bootloader, root and acquire s-off:
I went back to fully stock unrooted s-on to get the OTA just to b on the safe side. This is where I knew the update screwed up the current s-off method so I unlocked the bootloader using HTCDev. Then proceed to root and pushed the revone file to the appropriate folder location. I followed all the commands from revone up to where u Chmod 755 revone. After that since I already had root, I simply type su then proceeded with the s-off and unlock command. Removed tampered label and voila!!! Back in business with latest software.
Sent from my HTC One using xda premium
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
I think what happened was the new update screwed up the motochopper temp root exploit and that's y I think u can't s-off with the updated software. But there is always a way...
Sent from my HTC One using xda premium
TabascoJoe said:
I have a working phone. I have an unlock from htcdev. i have locked it, i can flash roms and recovery in twrp.
Its when I try an RUU it get suck on sending.... and errors out
Could it be my Main Version? I used misc tool to try to get back to 1.26.502.10, but can never get it to write the last digit correctly. Here is my getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.010
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 3999mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I guess I was wrong on being SuperCID. Using the misctool what should I change my main version to, and how?
Thanks
Click to expand...
Click to collapse
You can't use the AT&T RUU because your HBOOT is higher than the one in the RUU. S-ON is preventing any older HBOOT to be flashed.
Hi guys, will this work on T-Mobile HTC ONE? I updated not knowing they blocked from s-off.
Thanx,
Vinny
It would certainly be worth a try. The hardware is the same, so I don't see why not... as long as your boot loader is 1.44.00000 (not sure on the amount of zero's) this should work.
I'm pretty sure there are nandroid images for TMO out there so give it a try.
vinny.1967 said:
Hi guys, will this work on T-Mobile HTC ONE? I updated not knowing they blocked from s-off.
Thanx,
Vinny
Click to expand...
Click to collapse
let me know if it's work with you
me_rashad said:
let me know if it's work with you
Click to expand...
Click to collapse
Hey me_rashad, it's a no go. I also flash tmobile nand still no go. from what i research on difference forum is because tmobile update did a patch to the 1.44 HBoot so i guess we have to wait till revone or monshine dev find the way.
vinny.1967 said:
Hey me_rashad, it's a no go. I also flash tmobile nand still no go. from what i research on difference forum is because tmobile update did a patch to the 1.44 HBoot so i guess we have to wait till revone or monshine dev find the way.
Click to expand...
Click to collapse
I did get the OTA too and having the same pesky error -6. The bootloader version still says 1.44.0000, how do we know if its patched or not? Shouldn't the version number increase? What is your version?
Ok, so somehow I've managed to screw this phone up royally. Any help would be greatly appreciated.
I just switched to Android from iPhone and I think I tried too much too fast.
I successfully followed the guide to convert my AT&T HTC One to a Google Play Edition. I got S-OFF and changed the CID to GOOGL001 and successfully got 4.4 up and running.
I'd been using that for a few months and decided I wanted to try the HTC Sense Stock Software 4.3 (being new to android I just kind of wanted to try it myself in addition to stock android) I've been through a ton of steps and attempts now that I won't bore you with, but here's where I'm at now:
I'm stuck in a bootloop. My phone will load to welcome and ask for a language and then reboots about 2 seconds later.
I can successfully get into fastboot and run commands against the device. If I flash a recovery, it seems to work for one or two boots and then it will crash and restart until I flash it again (tried with TWRP and CWM)
I am currently Tampered Unlocked but can perform fastboot oem lock and unlock. I have S-ON, HBOOT 1.54 and Radio 4T.
My goal is to go back to stock for this device with 4.3 and Sense, but since I stupidly did S-ON before I changed the CID I'm not able to run the RUU exe and since my phone is in a bootloop I don't know how to get root access to run rumrunner to S-OFF.
I've been researching and trying stuff for several days now with no luck and this forum seems to have the best advice of most that I've seen. Can anyone help? Thanks so much for your time!
I had a similar experience in which I completely removed android OS from the phone If u flash the HTC with TWRP and you are able to successfully enter the recovery... TWRP has under advance button and option called adb sideload.
basically download the Google edition that successfully ran your device and place it under the adb.exe folder.
Steps
On the phone
Access recoverty TWRP
go to advance
Click on adb sideload
Swipe to activate adb sideload
Connect phone to computer.
On computer
Go to run and enter cmd press enter
go to the folder where you have the adb.exe
and the command that you enter is adb sideload «filename.zip» press enter and let it work
Sent from my HTC One using xda app-developers app
TopoX84 said:
I had a similar experience in which I completely removed android OS from the phone If u flash the HTC with TWRP and you are able to successfully enter the recovery... TWRP has under advance button and option called adb sideload.
basically download the Google edition that successfully ran your device and place it under the adb.exe folder.
Steps
On the phone
Access recoverty TWRP
go to advance
Click on adb sideload
Swipe to activate adb sideload
Connect phone to computer.
On computer
Go to run and enter cmd press enter
go to the folder where you have the adb.exe
and the command that you enter is adb sideload «filename.zip» press enter and let it work
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply and info! Ok, took your advice and flashed TWRP 2.6.3.3 to recovery. (I can only boot to recovery when I'm unlocked, not sure if that matters or not)
I'm trying to send RUU-HTC_One_GE-4.4.2-3.62.1700.1.zip (Is that the correct file I should be using)
The sideload gets to 100% but then instantly fails when it tries to run on the device:
ADB Sideload Complete
Failed
Updating partition details...
E: Unable to mount '/cache
E: Unable to mount '/cache
E: Unable to mount '/cache
Starting ADB sideload feature...
Cancelling ADB sideload...
Starting ADB sideload feature
Installing '/data/media/0/sideload.zip...
Checking for MD5 file...
Skipping Md5 check: no MD5 file found.
I've tried a few different versions with similar results (same file pre rooted) and same thing happens.
Any thoughts on what I could be doing wrong (because I'm sure that it's me that's the problem here. )
Give this a try... At the bottom of the op thread it says if adb sideload fails....
http://forum.xda-developers.com/showthread.php?t=2318497
If the link above didn't work you might want to try pushing the Rom to the phone via adb push...
See link below.
http://forum.xda-developers.com/showpost.php?p=43674827&postcount=5
Sent from my HTC One using xda app-developers app
I'm able to push the zip file ok, but when I try to do "install zip" it fails again. I get error flashing zip Updating Partition Detials
Is there anyway for me to achieve s-off from where I am now? If I change my CID back to the AT&T HTC one and then relock and s-on I would be able to use the stock ruu exe, correct?
I would look for a stock Rom GPE since you changed the CID and your s-on
I would look for a 4.3 or 4.4 stock Rom... Make sure also that TWRP is the latest . And try again both steps above. if that doesn't work my inclination would be to flash the Rom via fastboot.
try using this ROM, when i had the issues with my HTC i used it to sideload or push and it worked flawlessly.
http://forum.xda-developers.com/showthread.php?t=2460035
CtrlAltDave said:
Is there anyway for me to achieve s-off from where I am now? If I change my CID back to the AT&T HTC one and then relock and s-on I would be able to use the stock ruu exe, correct?
Click to expand...
Click to collapse
You are correct to what you said unfortunately the only way for you to perform a s-off based on the information given is using rumrunner in which you need your device to boot completely to the OS
Sent from my HTC One using xda app-developers app
no reason to post one after other where i can edit using the computer
Thanks for all of your help and patience with me. I think this phone hates me. I get error flashing with every zip I throw at the phone. I get error flashing zip in TWRP and Installation aborted with CWM. Tried with 4.3 and 4.4 stock GPE rom. Same results if I sideload or push. I also get an error when i try to fastboot flash the same roms. 99 unknown fail when bootloader unlocked and 12 signature verify fail if bootloader locked. Both of these are using fastboot oem rebootRUU and then fastboot flash zip rom.zip.
I pasted my getvar all below thinking that might help. I noticed my version-main is blank as well. Could that be causing any problems?
C:\Users\dfarrar\Desktop>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
I'm beyond frustrated at this point because I've spent so much time trying to get this working and I'm at a loss. That's what I get for messing around before I learned enough I guess. Thanks again for helping me out. I owe you!
here is mine...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*******
(bootloader) imei: *************
(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: 3756mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
the problem as i see it might be the cidnum and modelid, if you get a rom with both config it might be able to flash
CtrlAltDave said:
Thanks for all of your help and patience with me. I think this phone hates me. I get error flashing with every zip I throw at the phone. I get error flashing zip in TWRP and Installation aborted with CWM. Tried with 4.3 and 4.4 stock GPE rom. Same results if I sideload or push. I also get an error when i try to fastboot flash the same roms. 99 unknown fail when bootloader unlocked and 12 signature verify fail if bootloader locked. Both of these are using fastboot oem rebootRUU and then fastboot flash zip rom.zip.
I pasted my getvar all below thinking that might help. I noticed my version-main is blank as well. Could that be causing any problems?
C:\Users\dfarrar\Desktop>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ************
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
I'm beyond frustrated at this point because I've spent so much time trying to get this working and I'm at a loss. That's what I get for messing around before I learned enough I guess. Thanks again for helping me out. I owe you!
Click to expand...
Click to collapse
try this rom out .... RUU-HTC_One_GE-2.14.1700.15
http://forum.xda-developers.com/showthread.php?t=2358781&page=112
http://forum.xda-developers.com/showthread.php?t=2570785&page=3
Same errors with that rom. Won't work through adb push with twrm or cwm. Won't work with sideload and won't work fastboot flash zip. Could I have permanently broken this thing?
CtrlAltDave said:
Same errors with that rom. Won't work through adb push with twrm or cwm. Won't work with sideload and won't work fastboot flash zip. Could I have permanently broken this thing?
Click to expand...
Click to collapse
no it's not broken ...
Flash this stock recovery and also change your CID back to AT&T
fastboot oem writecid CWS__001
then
http://d-h.st/2Lr
fastboot flash recovery recovery_signed.img
Next boot into stock recovery / factory reset
this is done from the bootloader using the volume up/down to navigate and Power button to select. After you choose recovery you have to push vol up and power to see the factory reset option.
When it's done reflash TWRP recovery and try and sideload a new Rom
I recommend >> Download - ARHD 31.6
Would he be able to change back to the AT&T cod having s-on??? As far as I know you can only change with s-on only when you have supercid in place
Sent from my HTC One using xda app-developers app
TopoX84 said:
Would he be able to change back to the AT&T cod having s-on??? As far as I know you can only change with s-on only when you have supercid in place
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
yeah your right he need to get back s-off also after he gets ARHD 31.6 running
ARHD did the trick! For some reason none of the stock GPE roms would load but this one worked flawlessly. I was able to sideload and install, get supersu and then use rumrunner to get back to s-off. Plus this rom gives me everything that I wanted. I can keep kitkat and still get sense and zoe and whatnot. Never mind going back to stock, I think I'll stick with this for a while and try it out. Thanks so much for your help everyone!
To be in the safe side you might want to consider changing the cid to supercid...
Sent from my HTC One using xda app-developers app
CtrlAltDave said:
ARHD did the trick! For some reason none of the stock GPE roms would load but this one worked flawlessly. I was able to sideload and install, get supersu and then use rumrunner to get back to s-off. Plus this rom gives me everything that I wanted. I can keep kitkat and still get sense and zoe and whatnot. Never mind going back to stock, I think I'll stick with this for a while and try it out. Thanks so much for your help everyone!
Click to expand...
Click to collapse
Good to here it all worked out for you
and remember STAY S-OFF
SuperCID and S-Off for life. Thanks again!
Thanks All
Don't know if any of you will check back on this ancient post, but I read around for a long time and this totally ended up working for me. So belated thanks.
This is my first thread here on XDA so bare with me guys. I'm going to try to add all the important details to help you help me... yeah. Anyways, on with my problem. I recently converted my AT&T HTC One with sense to a GPE. Back on sense I was on 4.3, made a backup with TWRP and currently have it saved on my computer. Once I was one the google play edition, I updated to 4.4, just in case that matters.
The phone has S-OFF and has an unlocked bootloader. Not Rooted nor does it has a custom recovery.
My question is, how do I go back to HTC Sense ? Can I install a TWRP and drag & drop the backup & restore ? Or will installing a custom recovery brick the phone ?
Bootloader screen details:
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.58.1700.5
Click to expand...
Click to collapse
The rest doesn't really matter
Can I install A Custom Recovery and drag the backup from TWRP to my phone and restore back to sense ?
Any help is much appreciated ! :good:
Extra Info After Using The Command "fastboot getvar all"
C:\Users\Windows Master\Desktop\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.58.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34YW910578
(bootloader) imei: Rather Not Post
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4336mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.075s
Click to expand...
Click to collapse
Tony Deavila said:
This is my first thread here on XDA so bare with me guys. I'm going to try to add all the important details to help you help me... yeah. Anyways, on with my problem. I recently converted my AT&T HTC One with sense to a GPE. Back on sense I was on 4.3, made a backup with TWRP and currently have it saved on my computer. Once I was one the google play edition, I updated to 4.4, just in case that matters.
The phone has S-OFF and has an unlocked bootloader. Not Rooted nor does it has a custom recovery.
My question is, how do I go back to HTC Sense ? Can I install a TWRP and drag & drop the backup & restore ? Or will installing a custom recovery brick the phone ?
Bootloader screen details:
The rest doesn't really matter
Can I install A Custom Recovery and drag the backup from TWRP to my phone and restore back to sense ?
Any help is much appreciated ! :good:
Extra Info After Using The Command "fastboot getvar all"
Click to expand...
Click to collapse
Installing a custom recovery won't brick your phone. You'll just have to move the TWRP recovery to your internal SD card from your computer, install TWRP then restore from within TWRP. If you wanted the latest Sense version of Android, you could look at flashing ARHD 51.0 running on 4.4.2 instead of going back to 4.3, but that's up to you. Ask if you need anymore information.
Gpe to sense
i bought a google edition htc m8, so i wanted to get it back to sense aswell as i prefer the usability of it + the phone was made to run on that software
this took me hour to work out and hours of research on xda and other websites, so here im trying to simplify everything into one post, so people can get back to sense
so first of course root your phone if u have a google edition, if you converted to GPE from sense you will already be rooted and you can start the process (with TWRP installed)
i did it successfully but it was a huge process as there are limited resources atm to help me do it, as to why i am posting this
1. first i downloaded HTC one m8 all in one toollink)
http://forum.xda-developers.com/showthread.php?t=2699065
once you download this program you will be able to put the phone into bootloader, with this program you wont have to use comand prompt on windows to change the cid in bootloader.
2. you need to change the phones cid from goog to CID-11111111, of the m8 all in one toolkit it enters it in for you and writes it straight to your phone.
3. once you do this you need to download -
Flash 1.54 Image- http://forum.xda-developers.com/show...68&postcount=3
NOW YOU NEED TO USE COMAND PROMPT- TEST PHONE WITH - FASTBOOT DEVICES- SHOULD GET A NUMBER CODE IF YOUR PHONE IS CONNECTED PROPERLY
1.FIRST ENTER fastboot oem rebootRUU
THEN- fastboot flash zip (whatever you name it).zip REDO IT TWICE 1ST WILL FAIL )- THEN SUCCESSFUL
-Boot back into Bootloader
-Boot into Recovery
-then in twrp (MUST)
-Wipe Data, Factory Reset, Advanced Wipe-Wipe System, Data, Cache
-Reboot Recovery
-Restore or Flash a Sense Rom
(i have been pretty brief in my explanation, everything you need is there for the tricky parts, but if you have problems with toolkit or anything else look it up on xda) but this post will cut down the process time!
thanks. i am not resposible for any faults or problems with your phone but if you do it correctly all should be good :good:
I'm in a pickle, and have been working at it all night to try to get my phone back to at least working order.
Here's what happened so far:
Phone is an ATT model HTC One m8 converted to GPe via RUU. CID was changed to GOOGLE's to received ota updates.
OTA update installed, and I noticed it said something about the firmware. When it finally booted, I didn't have any cellular signal.
Fast forward to 5 hours of trying to recover from it and even flashing the original GPE RUU, I still don't have a baseband.
Here's what I have tried:
RUU of 5.0.1. No signal.
RUU of Sense rom. (Wouldn't boot, so hard to use nandroid backup). No signal.
Flashing radios. Tried ATT and GPE. No luck.
All of these report Baseband is unknown. Worked fine @ 4.4.4. before the update today.
Here's what fastboot shows:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.00
(bootloader) version-baseband: 1.16.213319
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxx3014 (It does show a full IMEI just hiding some of it)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any help would be greatly appreciated. Ive searched all over and haven't found a solution.
EDIT: Forgot to mention that I am currently at stock sense rom (4.4.2) and it doesn't report a baseband. Fastboot shows an IMEI though.
lordpelvis said:
RUU of Sense rom. (Wouldn't boot, so hard to use nandroid backup). No signal.
Click to expand...
Click to collapse
The RUU completes properly, but phone doesn't boot? Or are there any errors?
Not sure how nandroid figures in here. RUU will re-install stock recovery, so a nandroid will do you no good; unless you install custom recovery again.
If in fact the RUU and radio flashes are running to completion (but still no signal), that would not bode well. You might have a radio brick, or something like that.
What Sense RUU did you run, and what GPE RUU did you run (please link it).
And to confirm, you are trying to use this device on AT&T's network?
redpoint73 said:
The RUU completes properly, but phone doesn't boot? Or are there any errors?
Not sure how nandroid figures in here. RUU will re-install stock recovery, so a nandroid will do you no good; unless you install custom recovery again.
If in fact the RUU and radio flashes are running to completion (but still no signal), that would not bode well. You might have a radio brick, or something like that.
What Sense RUU did you run, and what GPE RUU did you run (please link it).
And to confirm, you are trying to use this device on AT&T's network?
Click to expand...
Click to collapse
Yes. Trying to use on ATT network. It doesn't even detect whether a sim is in it or not.
GPE Thread I followed: http://forum.xda-developers.com/showthread.php?t=2708651
I ran the Sense RUU from here: http://www.droidviews.com/restore-att-htc-one-m8-stock-firmware/
Phone does boot, wifi works but there is no baseband or IMEI in the software on either GPE or Sense. I flashed the RUU then flashed custom recovery to do the restore. Sense booted fine but still didn't have any cellular connection. Fastboot shows a baseband and IMEI though.
lordpelvis said:
I ran the Sense RUU from here: http://www.droidviews.com/restore-att-htc-one-m8-stock-firmware/
Click to expand...
Click to collapse
Try these also:
http://forum.xda-developers.com/att-htc-one-m8/general/htc-one-m8-ruu-m8ul-4-4-3-t2860423
http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
So its still not clear, the Sense RUU ran to completion, with no errors? If so, again it doesn't sound good.
Yes no errors. It was fine on 4.4.4 GPE. Could the OTA update have burned up the radio? Going to try 4.4.3 now.
lordpelvis said:
It was fine on 4.4.4 GPE. Could the OTA update have burned up the radio? Going to try 4.4.3 now.
Click to expand...
Click to collapse
OTA typically updates radio, so its possible.
redpoint73 said:
OTA typically updates radio, so its possible.
Click to expand...
Click to collapse
Still no dice on the 4.4.3 RUU. No errors. Phone boots but sticks at the HTC green logo. I can swipe down from the top and see there's no service but nothing else is happening. It will randomly reboot as well.
EDIT: Phone finally finished welcome wizard. Still random reboots and no baseband.
Looks like a trip to ATT is looking more and more likely.
Any other suggestions? Ideas?
Try WNC's Dev Edition 3.28 firmware package: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
At this point, I'm just thinking of anything that will flash the radio, that hasn't already been tried.
redpoint73 said:
Try WNC's Dev Edition 3.28 firmware package: http://forum.xda-developers.com/att-htc-one-m8/development/att-4-4-3-2-22-1540-3-debloated-sense-6-t2837365
At this point, I'm just thinking of anything that will flash the radio, that hasn't already been tried.
Click to expand...
Click to collapse
What's weird is fastboot getvar all reports an IMEI but the roms don't see it.
Still no lock. All roms don't see the IMEI.
lordpelvis said:
Still no lock. All roms don't see the IMEI.
Click to expand...
Click to collapse
how do you fix your phone after all?
I didnt. Warranty replaced.
M8 briccked after try to flash skydragon v3.1 on htc.one m8 with hboot 3.61 and S-ON
It now stuck on htc logo,it was purchased from usa ,if i revert back.now to stock rom,it ll get locked my device again?
I live in gulf country.now for a visit,help me guys.
more details,help me please asap
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.084s
c:\adb>fastboot oem readcid
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.000s]
finished. total time: 0.000s
c:\adb>fastboot oem readcid
...
FAILED command write failed (unknown error)
Finished.
Help me guys
Try access to bootloader and use other ROM maybe CM12
gato06 said:
Try access to bootloader and use other ROM maybe CM12
Click to expand...
Click to collapse
CM12 will only flash with hboot 3.19.
---------- Post added at 09:02 AM ---------- Previous post was at 08:57 AM ----------
abraarukuk said:
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
Click to expand...
Click to collapse
Your firmware (hboot, radio, etc.) is quite old (corresponds to Android 4.4.2). I don't know what Android version SD v3.1 corresponds to (what firmware it supports). But if there is any mismatch (example, if SD v3.1 only support Android 4.4.3 firmware or higher) than the ROM won't boot (or take so long to boot with no boot animation, making you think its stuck).
Also, depending on what version TWRP you are using, newer versions TWRP also won't work with your old firmware (wont flash ROMs properly - will seem to flash OK but ROM won't boot).
So you may have one of the above problems, mostly stemming from extremely outdated firmware. My advice would be to relock the bootloader, and use the latest AT&T RUU to update to current Lollipop (which will also update firmware). Then you can flash current TWRP 2.8.7 and flash nearly any M8 ROMs you want.
RUUs are linked on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Another thing, this thread belongs in the Q&A Help forum section. I'll ask the mods to move it.
redpoint73 said:
cm12 will only flash with hboot 3.19.
---------- post added at 09:02 am ---------- previous post was at 08:57 am ----------
your firmware (hboot, radio, etc.) is quite old (corresponds to android 4.4.2). I don't know what android version sd v3.1 corresponds to (what firmware it supports). But if there is any mismatch (example, if sd v3.1 only support android 4.4.3 firmware or higher) than the rom won't boot (or take so long to boot with no boot animation, making you think its stuck).
Also, depending on what version twrp you are using, newer versions twrp also won't work with your old firmware (wont flash roms properly - will seem to flash ok but rom won't boot).
So you may have one of the above problems, mostly stemming from extremely outdated firmware. My advice would be to relock the bootloader, and use the latest at&t ruu to update to current lollipop (which will also update firmware). Then you can flash current twrp 2.8.7 and flash nearly any m8 roms you want.
Ruus are linked on my index thread: http://forum.xda-developers.com/showthread.php?t=2751432
another thing, this thread belongs in the q&a help forum section. I'll ask the mods to move it.
Click to expand...
Click to collapse
twrp v 2.7.0.2
I NEED TO GIVE LIFE TO MY htc M8
Ruu i tried which said not compatible,unknown error i add screenshot
abraarukuk said:
Ruu i tried which said not compatible,unknown error i add screenshot
Click to expand...
Click to collapse
There are 2 Lollipop RUUs linked on my Index: 4.28.502.1 and 4.28.502.2
Try both, and see if either works.
Not sure why you are getting unknown error (believe this is Error 155). You relocked the bootloader, as I mentioned; and verified on the bootloader screen it says RELOCKED?
As long as the bootloader is RELOCKED, you have the right CID and MID, so I don't see a reason why the RUU won't work.
How can i relock bootloader?
If i relock again i have to pay money to unlock at and t for use orher carriers?
thank you bro,i am trying now as you said
Thank you so much redpoint brother,its upgraded now
i done everything u said now hboot is 3.19 thank u genious
abraarukuk said:
How can i relock bootloader?
If i relock again i have to pay money to unlock at and t for use orher carriers?
Click to expand...
Click to collapse
Relocking the bootloader has nothing to do with SIM unlock (which determines what carrier you can use).
So no, relocking the bootloader will not affect SIM unlock.
You can simply unlock the bootloader again via HTCDev.com, in order to re-install TWRP, flash custom ROMs, etc.
---------- Post added at 10:23 AM ---------- Previous post was at 10:21 AM ----------
abraarukuk said:
i done everything u said now hboot is 3.19 thank u genious
Click to expand...
Click to collapse
You are quite welcome.
Glad you sorted it out.
I didn't see your posts above, otherwise I would have responded earlier.