Due to the massive inconvenience/time this has caused me, having little experience initially with android devices and coupled with the fact Telstra Australia will not release an RUU to make things easy, I thought I would document my method for those currently on hboot 1.5x+ who are wanting to roll their device back to complete stock. This process is specifically for people who want a Telstra branded rom for warranty and does require sunshine if you have hboot 1.57. This is for the HTC one M7 although I suspect the process is the same on the M8..
This method was performed in Windows 7 as Windows 8 seems to have issue with fastboot commands. If you have a different carrier, are performing this on Mac or plan to use a Nandroid please see nkk71’s superguide for more details. Unfortunately the only 2 Telstra Nandroids I could find both failed for me.
*Please make sure fastboot is unchecked and usb debugging is turned on in developer options
I have packaged all of the tools needed including the RUU.zip I used in the link below. The Guru files are hosted separately.
http://1drv.ms/1AVZvMF
The Guru files are hosted here, you will need both of these.
Stock Rom – Guru Reset
http://www.htc1guru.com/dld/guru_res...-24-841-1-zip/ - download
http://www.htc1guru.com/downloads/stock-rom-downloads/ - info
Bootloader to remove tamper/lock bootloader
http://www.htc1guru.com/dld/guru_boo...reset_1-0-zip/ - download
http://forum.xda-developers.com/show....php?t=2527194 - info
1. S-off must be achieved. If you have it already you are in luck, proceed. This table shows what you can or cannot achieve with S-off for reference. Cannot remember exactly where I found this. Please message me with username so I can provide props if known.
Methods:
a) If you’re on hboot 1.44 use revone -
http://forum.xda-developers.com/show....php?t=2314582
http://revolutionary.io/
b) If you are hboot 1.54/1.55 you can attempt rumrunner
http://forum.xda-developers.com/show....php?t=2488772
http://rumrunner.us/
c) If you are in hboot 1.56/1.57 you will need sunshine for usd as I did. As far as I am aware there is currently no way around it. However I am very happy with this application and support. Firewater is discontinued.
http://theroot.ninja/
2. Reboot into bootloader/fastboot usb and perform getvar
fastboot getvar all
Note the following:
version-bootloader: 1.57.0000– hboot version
cidnum: TELST001 - CID
modelid: PN0714000 – MID
version-main: 5.11.841.9 – firmware
All Telstra devices should have a modelid of PN0714000. If for some reason you do not have this MID see nkk71’s superguide for different MID/CID RUUs and download a different version.
BOOT LOOP
The firmware will be reset to a 1.29.x base when you flash the RUU which is fine for OTA updates. If you have previously experienced boot loop it is because the firmware coming out in the OTA updates is lower than the firmware already installed on your device. Firmware can only be upgraded not downgraded by OTAs.
3. Provided your MID is PN0714000 proceed to change your CID to match RUU CID. The CID associated with the RUU provided is HTC__044
fastboot oem writecid HTC__044
fastboot reboot-bootloader
*confirm CID is now HTC__044 – see bootloader or getvar
4. Flash the RUU.
fastboot oem rebootRUU (silver htc will appear)
fastboot flash ruu.zip (it will report failed flush, repeat command)
fastboot flash ruu.zip (success)
fastboot reboot-bootloader
*bootloader should now read hboot 1.44
5. Change CID back to stock (TELST001)
fastboot oem writecid TELST001
fastboot reboot-bootloader
6. Mount and Launch TWRP custom recovery
fastboot boot openrecovery-twrp-2.8.4.0-m7
7. Once in TWRP your phone become available as a mass storage device. Run an ADB command to check the phone is being recognized in windows and then push the guru reset rom to the device.
adb devices
adb push Guru_Reset_M7_2.24.841.1.zip /data/media
If your device does not display a serial number executing an adb devices command you will need to install the drivers in device manager, it is likely an unrecognized device post RUU flash. See nk771s FAQ for instructions.
8. In TWRP recovery hit install, navigate to the data/media folder and select the Guru_Reset_M7_2.24.841.1.zip
Run through the installer and select the options as seen in this video
https://www.youtube.com/watch?v=Gqfly8XVw6w
When complete hit – do not add root and reboot the device. If it gives option to wipe cache, do so.
9. Boot your phone as normal into the now stock 4.2.2 Rom, set up wireless and install the first two small OTA updates to confirm they are working. If successful uncheck fastboot/enable usb debugging again and reboot phone back into boot loader with adb command.
abd reboot bootloader
10. In fastboot USB mount/launch TWRP recovery then adb push the Guru Boot Loader tool to the device.
fastboot boot openrecovery-twrp-2.8.4.0-m7
adb push Guru_Bootloader_Reset_1.0.zip /data/media
11. Hit Install, Navigate to the folder and launch Guru_Bootloader_Reset_1.0.zip. Run through the wizard and select remove tamper and lock function then wipe cache. Video here for clarification.
https://www.youtube.com/watch?v=yimzmt23E6Q
12. Reboot the phone a few times into bootloader to make sure lock/tamper does not return
fastboot reboot-bootloader
If unlocked/tamper returns or the installer fails you may have to use the manual method, exercise caution. See nk771's FAQ for instructions.
13. Set S-on
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Fastboot into bootloader a few times to make sure everything is fine before proceeding to final OTA updates.
14. Boot phone normally and proceed to do all of the remaining OTA updates to bring your software/firmware up to latest version. Sometimes the phone will boot into stock recovery mode first time after S-on, just reboot it, it will come good.
If you would prefer to use a Nandroid backup (although I am not sure why), start from step 7 and restore it via TWRP or CWM (depending on the backup type) in place of Guru Reset. After this is complete you can proceed with the remaining steps.
This all came about from Telstra being unwilling to repair my purple haze issue (which is clearly a sensor/camera module hardware defect) while having my bootloader unlocked/tampered. The purple haze issue occurred when my device was factory locked. I understand unlocking the boot loader voids warranty but this issue is hardware related which happens on stock software/firmware. I find it a little dishonest that HTC/Telstra want to charge me to have my unit replaced/repaired when it's a known hardware defect unless I am willing to go back through the process of making this device look like it's stock. I hope this can help some of the Telstra customers in the same position as RUU/Nandroids are almost non existent. Thank god for guru! ;)
This method was performed in Windows 7 as Windows 8 seems to have issue with fastboot commands. If you have a different carrier, are performing this on Mac or plan to use a Nandroid please see nkk71’s superguide for more details. Unfortunately the only 2 Telstra Nandroids I could find both failed for me.
*Please make sure fastboot is unchecked and usb debugging is turned on in developer options
I have packaged all of the tools needed including the RUU.zip I used in the link below. The Guru files are hosted separately.
http://1drv.ms/1AVZvMF
The Guru files are hosted here, you will need both of these.
Stock Rom – Guru Reset
http://www.htc1guru.com/dld/guru_res...-24-841-1-zip/ - download
http://www.htc1guru.com/downloads/stock-rom-downloads/ - info
Bootloader to remove tamper/lock bootloader
http://www.htc1guru.com/dld/guru_boo...reset_1-0-zip/ - download
http://forum.xda-developers.com/show....php?t=2527194 - info
1. S-off must be achieved. If you have it already you are in luck, proceed. This table shows what you can or cannot achieve with S-off for reference. Cannot remember exactly where I found this. Please message me with username so I can provide props if known.
Methods:
a) If you’re on hboot 1.44 use revone -
http://forum.xda-developers.com/show....php?t=2314582
http://revolutionary.io/
b) If you are hboot 1.54/1.55 you can attempt rumrunner
http://forum.xda-developers.com/show....php?t=2488772
http://rumrunner.us/
c) If you are in hboot 1.56/1.57 you will need sunshine for usd as I did. As far as I am aware there is currently no way around it. However I am very happy with this application and support. Firewater is discontinued.
http://theroot.ninja/
2. Reboot into bootloader/fastboot usb and perform getvar
fastboot getvar all
Note the following:
version-bootloader: 1.57.0000– hboot version
cidnum: TELST001 - CID
modelid: PN0714000 – MID
version-main: 5.11.841.9 – firmware
All Telstra devices should have a modelid of PN0714000. If for some reason you do not have this MID see nkk71’s superguide for different MID/CID RUUs and download a different version.
BOOT LOOP
The firmware will be reset to a 1.29.x base when you flash the RUU which is fine for OTA updates. If you have previously experienced boot loop it is because the firmware coming out in the OTA updates is lower than the firmware already installed on your device. Firmware can only be upgraded not downgraded by OTAs.
3. Provided your MID is PN0714000 proceed to change your CID to match RUU CID. The CID associated with the RUU provided is HTC__044
fastboot oem writecid HTC__044
fastboot reboot-bootloader
*confirm CID is now HTC__044 – see bootloader or getvar
4. Flash the RUU.
fastboot oem rebootRUU (silver htc will appear)
fastboot flash ruu.zip (it will report failed flush, repeat command)
fastboot flash ruu.zip (success)
fastboot reboot-bootloader
*bootloader should now read hboot 1.44
5. Change CID back to stock (TELST001)
fastboot oem writecid TELST001
fastboot reboot-bootloader
6. Mount and Launch TWRP custom recovery
fastboot boot openrecovery-twrp-2.8.4.0-m7
7. Once in TWRP your phone become available as a mass storage device. Run an ADB command to check the phone is being recognized in windows and then push the guru reset rom to the device.
adb devices
adb push Guru_Reset_M7_2.24.841.1.zip /data/media
If your device does not display a serial number executing an adb devices command you will need to install the drivers in device manager, it is likely an unrecognized device post RUU flash. See nk771s FAQ for instructions.
8. In TWRP recovery hit install, navigate to the data/media folder and select the Guru_Reset_M7_2.24.841.1.zip
Run through the installer and select the options as seen in this video
https://www.youtube.com/watch?v=Gqfly8XVw6w
When complete hit – do not add root and reboot the device. If it gives option to wipe cache, do so.
9. Boot your phone as normal into the now stock 4.2.2 Rom, set up wireless and install the first two small OTA updates to confirm they are working. If successful uncheck fastboot/enable usb debugging again and reboot phone back into boot loader with adb command.
abd reboot bootloader
10. In fastboot USB mount/launch TWRP recovery then adb push the Guru Boot Loader tool to the device.
fastboot boot openrecovery-twrp-2.8.4.0-m7
adb push Guru_Bootloader_Reset_1.0.zip /data/media
11. Hit Install, Navigate to the folder and launch Guru_Bootloader_Reset_1.0.zip. Run through the wizard and select remove tamper and lock function then wipe cache. Video here for clarification.
https://www.youtube.com/watch?v=yimzmt23E6Q
12. Reboot the phone a few times into bootloader to make sure lock/tamper does not return
fastboot reboot-bootloader
If unlocked/tamper returns or the installer fails you may have to use the manual method, exercise caution. See nk771's FAQ for instructions.
13. Set S-on
fastboot oem writesecureflag 3
fastboot reboot-bootloader
Fastboot into bootloader a few times to make sure everything is fine before proceeding to final OTA updates.
14. Boot phone normally and proceed to do all of the remaining OTA updates to bring your software/firmware up to latest version. Sometimes the phone will boot into stock recovery mode first time after S-on, just reboot it, it will come good.
If you would prefer to use a Nandroid backup (although I am not sure why), start from step 7 and restore it via TWRP or CWM (depending on the backup type) in place of Guru Reset. After this is complete you can proceed with the remaining steps.
This all came about from Telstra being unwilling to repair my purple haze issue (which is clearly a sensor/camera module hardware defect) while having my bootloader unlocked/tampered. The purple haze issue occurred when my device was factory locked. I understand unlocking the boot loader voids warranty but this issue is hardware related which happens on stock software/firmware. I find it a little dishonest that HTC/Telstra want to charge me to have my unit replaced/repaired when it's a known hardware defect unless I am willing to go back through the process of making this device look like it's stock. I hope this can help some of the Telstra customers in the same position as RUU/Nandroids are almost non existent. Thank god for guru! ;)
Aucun commentaire:
Enregistrer un commentaire