Hi!
I've been trying custom ROMs on my old phone and want to revert to stock. Despite this concerning a very old phone, I think my question is probably pretty universal, so here goes.
I have a HTC One (M7). I've tried lots of different custom ROMs and now I want to revert to stock. I finally did this using Guru Restore (elsewhere on this forum). However, with flags set for TAMPERED and RELOCKED and S=ON, I am stuck at the most ancient version of the OS. OTA updates wor't work, probably because of the flags. No way to get S=OFF since the options are all no go (revone won't work with this bootloader and I can't fork out $25 for Sunshine). So to be simple and clear, I am 100% stuck with these flags now. Also to make it even trickier, I have a pretty rare/obscure cid in ORANG001. So what are my options for being stock but not the oldest software imaginable?
RUUs: I assume they are the .exe files, since the second 'u' stands for utility. None will work on my phone, either because of the flags, or because none match my obscure cid. So the .exe's are out. Period. Question 1: Unless... does a RUU being 'unsigned' mean it should load anyway?
.zip files: My understanding is that these are the same code as the RUUs above(?), but I'd install them with (eg) TWRP rather than via Windows. So Question 2: If I install a .zip RUU with TWRP, will it ignore a mismatched cid and succeeed anyway? Question 3: I guess a stock RUU installed with TWRP requires no Gapps?
Nandroids: Same question really. Question 4. If I try to restore from a Nandroid that came from a device with a different cid, will it fail, or will it succeed?
Anything else that might help me get a somewhat more contemporary version of Android and Sense onto the phone?
Thank you for your patience and advice & guidence - in anticipation!
Cheers.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34PW913714
(bootloader) imei: 354436054211972
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4315mV
(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
Related
I recently acquired an HTC One SV from Boost mobile to try to fix. The previous owner ran a tool meant for a different phone to try to root the device. When I received it, it was stuck at the HTC splash boot screen with a message on the bottom saying that this is for development purposes only. I have tried going into the bootloader and flashing every image that I could find of boot, recovery, and radio. I found images that were supposedly stock and it still does not boot.
Suggestions say to take and flash a RUU to the device. The only official RUU for the region (OTA_K2_CL_JB_45_S_Sprint_WWE_Boost_2.06.653.5-1.11.653.1_release_3244713ijuyqp8g1s0xuaw.zip) I could find does not flash with an error #12. I then tried to find a method to turn the device to S-off but cannot find anything that can be done when not booted into ICS. Does anyone know a way to turn the phone to S-Off within just the fastboot OR does anyone have a backup that will fit my phone using CWM or TWRP as I can boot into them. I also ran into issues with links not working such as the system.img file located in http://forum.xda-developers.com/showthread.php?t=2292432
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.01.0000
(bootloader) version-baseband: 1.12.50.0115
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *********
(bootloader) imei: **********
(bootloader) product: k2_cl
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8011000
(bootloader) cidnum: SPCS_003
(bootloader) battery-status: good
(bootloader) battery-voltage: 4281mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
all: Done!
Thank you for the help!!!
Hey everyone, I'm having an issue unlocking my bootloader after updating the firmware.
When preparing to install the newest version of Android Revolution HD I thought it'd be a good time to update my firmware before switching to the KitKat based ROM. I used the firmware and instructions from here: http://forum.xda-developers.com/showthread.php?t=2182823
All went well until I tried to unlock the bootloader. I can complete all the steps through sending the Unlock_code.bin to the phone, which is successfully sent via fastboot, but I never get the notice on the phone to unlock. Nothing happens.
I believe my best course of action is to flash an RUU but I can't find any that are 4.06.1540.2 or higher at the moment and with S-ON and a locked bootloader, I can't load anything earlier.
If anyone has any insights I'd be most gracious, I'm currently without a phone and have to lug around a Galaxy Tab 3 for mobile connectivity.
Here's my getvar:
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-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: 4283mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
More info
I'll also note that I've tried two different computers, three different cables, and I've probably tried at least 20 different Unlock_code.bins.
I'm really at a loss here, I can flash both 4.06.1540.2 and 4.06.1540.3 to the device from Mike's firmware link; the device has no problems communicating via fastboot. It's just not asking me if I want to unlock after a successful code transfer.
So flashing a rom went wrong somewhere, and I've probably dug myself a deeper hole trying to fix it of course. I can get to bootloader, and I can also get to CWM and/or twrp recovery, however sideloading always fails. Here's a snapshot of where I am now after mucking around too much.
Looking for some help on what steps I need to take to get my baby working again.
boot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4202mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
simplydroid said:
Looking for some help on what steps I need to take to get my baby working again.
Click to expand...
Click to collapse
Not sure if this will work for you or not, with the S-ON thing, but try this:
http://www.htc1guru.com/dld/ruu_m7_...3_10-38m-1157-04_release_336982_signed_2-exe/
This is the RUU for the latest (current) T-Mobile update. It should wipe and return your device to 100% stock.
Normally RUU's will not work with S-ON, but I believe that's only for "downgrading"and not for flashing the current version. Should work. Can't hurt to try.
Download it, reboot into fastboot, and run the RUU. It'll take a while, but should work.
PhoenixPath said:
Download it, reboot into fastboot, and run the RUU. It'll take a while, but should work.
Click to expand...
Click to collapse
That got me going, thanked.
So I was an idiot and wrote S-On to my phone before I was finished flashing the RUU. I have tried firewater (obtained with Wayback Machine) and rumrunner, and both failed. I am on an old version of AHRD and HBoot 1.56. Every time I try to flash the latest RUU (6.10.531.10) from htc.com, it fails with Error 155 after trying to check the signature. I have also tried extracting the rom.zip and flashing that, but I get the same result (fails after trying to check signature).
I have tried S-OFFing with every method I've found. Using Arch Linux, using Windows, using old ROMs, new ROMs, AOSP, Sense, making sure I always use an unsecured kernel, etc. firewater deletes itself every time I try to run it, and rumrunner fails after 8 tries. I don't want to spend $25 on SunShine, so I'm looking for every alternative.
Phone info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [removed]
(bootloader) imei: [removed]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(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
iwasaperson said:
So I was an idiot and wrote S-On to my phone before I was finished flashing the RUU. I have tried firewater (obtained with Wayback Machine) and rumrunner, and both failed. I am on an old version of AHRD and HBoot 1.56. Every time I try to flash the latest RUU (6.10.531.10) from htc.com, it fails with Error 155 after trying to check the signature. I have also tried extracting the rom.zip and flashing that, but I get the same result (fails after trying to check signature).
I have tried S-OFFing with every method I've found. Using Arch Linux, using Windows, using old ROMs, new ROMs, AOSP, Sense, making sure I always use an unsecured kernel, etc. firewater deletes itself every time I try to run it, and rumrunner fails after 8 tries. I don't want to spend $25 on SunShine, so I'm looking for every alternative.
Phone info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [removed]
(bootloader) imei: [removed]
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4293mV
(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
Click to expand...
Click to collapse
You might try an older RUU 5.14.531.1 first before the newer RUUs.
As far as obtaining S-OFF, with your hboot Sunshine is your best option.
I've tried several zip files and RUUs with no success. I have an old ATT phone which I unlocked. I'm trying to get to Marshmellow.
Any help would be appreciated.
It looks like this:
c:\Users\Dan\Downloads>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: deleted
(bootloader) imei: deleted
(bootloader) imei2: Not Support
(bootloader) meid: deleted
(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: RUU
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
The correct RUUs are in my Index thread, under the "RUU" section: https://forum.xda-developers.com/showthread.php?t=2751432
Take note of the red text, since you are updating to MM, you will need to flash MM firmware.zip in fastbootRUU mode, before the RUU will install properly.
If the bootloader is unlocked, you will also need to relock it to RUU, with command: fastboot oem lock
daneboy55 said:
I've tried several zip files and RUUs with no success.
Click to expand...
Click to collapse
For this statement to be useful in any way, we need specific details. If you don't list the file names or version numbers of the zip files or RUUs, then we have no idea what you tried. Also, you should list error messages or other specific results instead of just saying 'no success". The error messages will usually tell you why it failed. May or may not be AT&T RUUs, may have failed due to unlocked bootloader, etc.
Also don't know what you mean "several zip files". Are they zip format RUUs, or something else?
I got TWRP running. I then found a zip file using my cidnum. It is SkyDragon-M8ul-M8vzw-EYEul_v1.6.0_MM.zip. It failed the zip file check, but I installed anyway. It seems to be working fine thus far. Thanks for your response.