Database Develop

[Q] Custom Rom/Recovery w/o tampered message?

Hello.
I just got my One, upgraded from the One X
I am very skilled regarding rooting, flashing custom roms, recoveries, etc. I just have a quick question.
Is it possible to install custom rom, custom recovery and turn the phone S-OFF - WITHOUT getting the tampered message?
- If no, tell me that
- If yes, read on
Second case: Does this RRU match my M7?
First of all, what have i done myself:
- Unlocked bootloader
- Installed TWRP
- Made a nandroid backup
- Relocked bootloader because i want to flash [ROM] Android Revolution HD 3.2 Google Edition | High Quality & Performance | Android 4.3 Jelly Bean | 2.14.1700.15
- Flashed latest firmware for my phone - 2.24.401.1 (the thread above states that its not needed but recommended)
- Got the TAMPERED message and wants to get rid of that (and return from HBOOT 1.54 to original HBOOT 1.44)
In order to get rid of that message, this guide state i must use "method 2", and as part of that method 2, i must find the correct RRU.
The following is the output of getvar all before firmware update:
(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: 1.29.401.16
(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: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3980mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.043s
Click to expand...
Click to collapse
And this is getvar all after firmware update:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(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: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4010mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
Will this RRU be for my phone: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
- I found it here: http://www.androidruu.com/index.php?developer=M7
I chose it as its the RRU for the M7 Europe model that gets closest to my original main version (1.29.401.16 vs 1.28.401.7), also the radio in that RRU is just a tad older than my own original radio.
Also, is it possible to downgrade like that (im quite certain it is, just want to be sure).
Kind Regards
TwinAdk

Wait, you was in 1.44 hboot and now you're on 1.54?
If yes, you can't get the s-off.
The tools for the S-OFF are working only in 1.44 hboot, and, i if read right, now you have the 1.54 and you can do nothing...

****, you are kidding me, right? And RUU downgrade is not an option? That will downgrade my RUU too.
Aside from S-OFF being down the toilet, are there any other downsides to Hboot 1.54?

TwinAdk said:
****, you are kidding me, right? And RUU downgrade is not an option? That will downgrade my RUU too.
Aside from S-OFF being down the toilet, are there any other downsides to Hboot 1.54?
Click to expand...
Click to collapse
You can't downgrade with any ruu if you don't have the S-OFF...
Nope, but now you can't remove the ****Tampered**** line and you can't get the S-OFF...

Guich said:
You can't downgrade with any ruu if you don't have the S-OFF...
Nope, but now you can't remove the ****Tampered**** line and you can't get the S-OFF...
Click to expand...
Click to collapse
God dammit.. Well, are there any downsides regarding custom roms, to having the 1.54 hboot? Also, is it likely S-OFF will ever be avail. with 1.54?

TwinAdk said:
God dammit.. Well, are there any downsides regarding custom roms, to having the 1.54 hboot? Also, is it likely S-OFF will ever be avail. with 1.54?
Click to expand...
Click to collapse
No, you can flash all rom, kernel, mod, theme that you want.
For the S-OFF, no, devs said that they will work on the tool for the S-OFF when the new update form htc will come with the 1.55 hboot

Guich said:
No, you can flash all rom, kernel, mod, theme that you want.
For the S-OFF, no, devs said that they will work on the tool for the S-OFF when the new update form htc will come with the 1.55 hboot
Click to expand...
Click to collapse
So when 1.55 hboot arrives, work will start for S-OFF for that HBOOT? Any ETA on 1.55?

TwinAdk said:
So when 1.55 hboot arrives, work will start for S-OFF for that HBOOT? Any ETA on 1.55?
Click to expand...
Click to collapse
Atm there are some leaks of android 4.3 and new hboot 1.55, but this isn't the update that we will get.
For the question, yes

Guich said:
Atm there are some leaks of android 4.3 and new hboot 1.55, but this isn't the update that we will get.
For the question, yes
Click to expand...
Click to collapse
Okay, thanks
Now that i booted the phone, my storage is not available and wifi does not turn on (it says enabling, but thats all) - great start! Any idea why?
Ill look into it tomorrow my self, im off to bed now... Guess the One X will be in service for a few more days...
EDIT: Im on a firmware thats NOT for the android version i have, i think thats the problem. I guess ill have to sideload the custom rom running 4.3, and get it running that way.
Freaking hell, no S-OFF!

You relocked your bootloader after the flash of the rom?
If yes, you have to unlock this, reflash the rom and the kernel, and do a wipe of cache and dalvik-cache...

Guich said:
You relocked your bootloader after the flash of the rom?
If yes, you have to unlock this, reflash the rom and the kernel, and do a wipe of cache and dalvik-cache...
Click to expand...
Click to collapse
I cannot flash the rom as my SD is unavail... Is it an option to sideload the ROM?

TwinAdk said:
I cannot flash the rom as my SD is unavail... Is it an option to sideload the ROM?
Click to expand...
Click to collapse
Flash the stock recovery and then do a factory reset in bootloader, this will fix your sd.
After flash a custom recovery and try to use the sideload

Guich said:
Flash the stock recovery and then do a factory reset in bootloader, this will fix your sd.
After flash a custom recovery and try to use the sideload
Click to expand...
Click to collapse
Hello.
I flashed the stock recovery, and factory reset the phone. It rebooted during factory reset (of course), and booted normally afterwards. Wifi and storage did however still not work.. From within android im told that the storage is "Unavailable" (ill post screenshots later) - and from TWRP, i am told that i have "Internal storage" of 28xxx mb available (not sure about the excact size, around 28 gb) - but i cannot mount it and make it available from windows.
I can see the phone in windows, as a HTC media unit, and browse the content (storage -> legacy -> more folders -> root of SD card with folders like "downloaded" etc - default folders). But when i get there i cannot create folders or files, i can only view the content.....?
1. I cannot downgrade with RRU, since im S-ON
2. My Wifi and storage SEEMS broke (i suspect its because i flashed the firmware mentioned earlier, and my android version is not happy with that firmware - someone with more insight are welcome to comment on my guessing here)
3. Sideloading the rom i want to use (based on android 4.3) seems to be the only option - but can i sideload when my SD is not available in recovery?
Starting to worry a bit here
And thank you for all your help so far :good: I didnt get to say that last evening.. Appriciate!
Kind Regards

Hello sir,
first of all, let me say you screwed up already when not researching XDA before doing an update. Since i have done so myself numerous times, let me advise you to make it a habit, when buying a new phone to specifically research downsides of updates before accepting any.
Particularly in the HTC world, it has become a common thing to only gain S-OFF while the phone is in early software states and loose this ability towards later releases. Until now, many HTC phones i have had to deal with, had issues with disabling security on later firmwares.
Then, the storage problem you describe could possibly be related to something i have seen a fair few times. What Guich told you to do is usually the ultimate trick to get it back working. But let me ask this first: were you able to access storage from windows normally before the update? Or could you also face a driver issue?
OK. Guich's comment did not help. You flashed the stock recovery from the firmware you run. Then you ran Factory Reset from within Bootloader? Or from within android? If the latter, try the first...
I will be putting up stock recoveries from different RUU's soon on my thread here: http://forum.xda-developers.com/showthread.php?t=2316726 but you also find them on the forum already by searching. Try different stock recoveries and factory reset from Bootloader.
Then, if that doesn't help, try to run the OTA 2.24 (which already runs on your phone!) again by booting into bootloader, then picking "Fastboot" there (use volume down and up to navigate and power to confirm) and then going to your adb/fastboot with a command window. Oh, connect phone to PC of course
Lets say you have adb and fastboot plus the dll files in C:\Android. Open a CMD window and do "CD C:\Android" to go there.
there, run "fastboot oem rebootRUU" (type exactly as i do here, omit the quotes though).
then, copy and paste the OTA file (obtain HERE) to the same folder (C:\Android).
For easier typing in CMD, rename the OTA to something short and simple like test.zip or whatever.
then go back to your CMD Window and type in "fastboot flash zip test.zip"
Since its the same hboot and firmware in the OTA like you have on phone and since this package is official and signed, your phone ---should--- accept the flash. If not (maybe because you got the wrong model ID or wrong CID) i wouldn't really know how to proceed. But you DID accept that OTA before so it MUST be for your phone or else it wouldn't have flashed in the first place.
If it flashes fine, boot your phone up and check if it fixed everything.
If not, run the check for software update in Settings/Info/ and see if there is already an official OTA for your phone available that brings you past the 2.24. If not, download one of the inofficial OTA's and --- hope --- that you can flash it. Like 3.18 or 3.22. The first is for Asia/Taiwan though and will almost certainly NOT flash on your phone and the second is BrightstarUS and for the DEV edition and will also almost certainly not flash. But its worth a try.
beyond that, i have no more valuable tips. Only thing I would try is to flash CWM and do a clear storage, wipe data, wipe everything there. But be sure to have your nandroid ready if you do that. CWM uses a slightly different formatting method so it could possibly correct issues. In the past, i have read about screwed up SDcards related to CWM formatting more often than those that got screwed up by TWRP though. So its not exactly ideal to play with CWM on a phone that has already issues with its partition. But if i was desperate, i would do it anyway.
If that doesnt help or make it worse, do the very same thing on TWRP, pick the "wipe Data" option which prompts you to type "yes" into an input line. This will once again format your SD with a different method. It could possible correct this problem.
DO NOT attempt to screw around with the SD Partition using tools like MiniTool or EASUS if you can access the sd from them at all!
The SD Card is an EXT4 file system and cannot be formatted with FAT or NTFS from windows. If you do that, the phone wont work at all anymore. The exact parameters to format the partition externally are not known to me and i doubt you can address the partition from within windows at all. Maybe it works under linux...
Sorry. Cant be much help here. If that all doesnt work, just flash stock recovery back and restore your stock nandroid and send it in for repair. Them service dudes will have the right RUU and fix it for you.
[EDIT]
Oh and before i forget: if you can fix it with these tips, you owe me one
You have to flash Team Venom's ViperOne then instead of ARHD! :laugh:

Aroma installer is running now!! So excited to see the result! I sideloaded the zip, via adb sideload Nice short article on it here: http://teamw.in/ADBSideload
Will return with outcome :highfive::fingers-crossed::fingers-crossed::fingers-crossed:
EDIT: Its back! Running custom rom with sd card avail and wifi working! Pew, saved by adb sideload, increddible!

[Q] I've fallen and I can't get up!

I've successfully played with custom roms for years, but I managed to completely corrupt my Sprint HTC One M7 and I'm having a hard time figuring out how to get it back to being a working phone.
It's rooted and unlocked. I think a bad download of a recovery or rom corrupted either the storage or firmware or both.
When I first rooted it, I did have some problems. However, I was able to recover and successfully ran the Revolution ROM for about a month. I wanted to try the Viper ROM and that action (not the ROM itself, of course) put the device into its current bricked state.
I can still flash different recoveries. I can install new ROMs. I've even attempted to flash stock recoveries and run a factory reset to completely reset the phone's partitions. However the phone is unusable. I even have a OTG cable to grab ROMS from a USB stick. TWRP doesn't recognize the internal storage of the phone, but it does recognize the USB stick on the OTG cable. ClockWork can see all of the storage on the phone.
I have tried relocking and running RUUs, but I think I am doing it incorrectly because my phone is still S-ON and if that is the case, you have to find the right version of RUU that is an upgrade rather than a downgrade of the phone. The RUUs always error out. Perhaps someone will be able to provide a correct link as I have screen pictures and Model ID info I can include.
Behavior: As I try to show in the pictures I've attached, I can install customer ROMS or alleged stock ROMS onto the phone. When the process completes, I am presented with the stock lock screen for the M7. When I swipe the screen I am presented with a white HTC screen that is similar to the boot screen, but note there is no other writing. This is not the boot screen. Rather, it is all you get.
If you are tethered to a PC, you can see the storage on your list of drives.
However, after about 90 seconds, the phone auto reboots, and you are in a loop.
The phone is 13 months old, so I don't think I can just relock it and walk into a Sprint store and ask for a replacement.
Moreover, I think this is fixable, I just don't know how quite yet.
Thanks for those pros out there who can help me get out of this mess of my own making.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(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: 4.06.651.9
(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: 4242mV
(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
all: Done!
finished. total time: 0.035s

It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904

There is no RUU for 4.06.651.9.
This guide will get you fixed up use either the 4.06.651.9 or 5.03.651.3 s-on firmware
http://forum.xda-developers.com/showthread.php?t=2503646

twisteddan said:
It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
That RUU won't work it's super old

BD619 said:
That RUU won't work it's super old
Click to expand...
Click to collapse
Oh ok.....Sorry about that.

twisteddan said:
Oh ok.....Sorry about that.
Click to expand...
Click to collapse
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version

BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
The question is, does such an RUU exist?
If it does not, is there a stock or custom ROM Zip that, while not packaged in an RUU, might work? Although if that were the case, the ROM's I've already tried to use might actually work.
Or, should I attempt to S-Off the phone (something I've never done before) in order to try an RUU to work?
Thanks for your initial answers. Sounds like I don't have enough to move forward quite yet.

BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?

bethesdaadk said:
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?
Click to expand...
Click to collapse
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.

BD619 said:
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.
Click to expand...
Click to collapse
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?

bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
I use this one http://forum.xda-developers.com/showthread.php?t=2651035

BD619 said:
I use this one http://forum.xda-developers.com/showthread.php?t=2651035
Click to expand...
Click to collapse
I've tried to parse out your directions to make sure I do this correctly. Can you please check to make sure I'm understanding you correctly?
First step is to flash the firmware:
I've downloaded 4.06.651.9 s-on firmware per your suggestion becuase that's the current version of my phone.
Then I need to rename it to just plain firmware.zip
Then on the phone:
Boot to bootloader and lock the bootloader by typing:
fastboot oem lock
in my ADB/Fastboot dos session.
Then use these commands:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
which will flash the firmware.
Then: If you get this error after the second command (most likely will)
failed 90 hboot pre-update! please flush image again immediately
press the UP Arrow on your keyboard and press enter to issue the command again. Essentially, you are flashing the firmware a second time.
Then, unlock the bootloader again
fastboot flash unlocktoken Unlock_code.bin
Here's the part where I'm a little uncertain. You state:
8a. If you are using the 4.06.651.4 s-on firmware I would suggest you push this Stock Rooted Odexed Rom to your device or it may not boot.
8b. After flashing the 4.06.651.4 rom you will most likely need to flash the latest radio because the 4.06 firmware does not have a radio included find it HERE
Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Also, earlier in the guide, you state:
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Do I need to worry about that since I'm flashing the s-on firmware and not the s-off firmware?
Thanks for your help on this. If I were this careful the first time around, maybe I wouldn't have gotten to this point. Luckily, my old Evo4G is in good condition so I've put it into service while I try and fix the HTC One.

bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
tdhite's 2.7.0.9 worked fine for me?

Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Click to expand...
Click to collapse
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Click to expand...
Click to collapse
This only applies to folks that are s-off.

BD619 said:
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
This only applies to folks that are s-off.
Click to expand...
Click to collapse
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.

bethesdaadk said:
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.
Click to expand...
Click to collapse
Well the 5.03.651.3 firmware and rom are sense 6

BD619 said:
Well the 5.03.651.3 firmware and rom are sense 6
Click to expand...
Click to collapse
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?

bethesdaadk said:
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?
Click to expand...
Click to collapse
Did you remember to flash the radio?

BD619 said:
Did you remember to flash the radio?
Click to expand...
Click to collapse
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.

bethesdaadk said:
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.
Click to expand...
Click to collapse
Nope just flash the radio from recovery

[SOLVED] [Q] HTC Stuck on Boot Screen, here's what I did

Hi everyone,
I've spent the last 6 hours attempting various fixes from forums and I just can't &^%$ing get this.
Here's what I did.
(1) Phone got stuck in a bootloop.
(2) I did a backup in TWRP version 2.6.
(3) Factory reset.
(4) Everything worked again, no bootloop.
(5) Tried to recover from the backup in TWRP, backup failed.
(6) Phone now stuck on the HTC One screen.. won't load a thing.
I really just want things back to normal, as in stock ROM.
Some info about the phone:
S-ON
TWRP ver 2.6
rooted
can access recovery
don't need anything on the phone
I'm looking for a solution to get this phone going again.. any solution. I'd prefer to be on stock ROM. I'd love some help on this. I'm here.

post your fastboot getvar all please

2dayquestion said:
Hi everyone,
I've spent the last 6 hours attempting various fixes from forums and I just can't &^%$ing get this.
Here's what I did.
(1) Phone got stuck in a bootloop.
(2) I did a backup in TWRP version 2.6.
(3) Factory reset.
(4) Everything worked again, no bootloop.
(5) Tried to recover from the backup in TWRP, backup failed.
(6) Phone now stuck on the HTC One screen.. won't load a thing.
I really just want things back to normal, as in stock ROM.
don't need anything on the phone
Click to expand...
Click to collapse
well if you don't need anything on the phone and you previously did a factory reset and the phone stopped boot-looping, why did you restored that faulty backup? just do a factory reset and you'll be good

alray said:
well if you don't need anything on the phone and you previously did a factory reset and the phone stopped boot-looping, why did you restored that faulty backup? just do a factory reset and you'll be good
Click to expand...
Click to collapse
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.

2dayquestion said:
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.
Click to expand...
Click to collapse
post the ouput of fastboot getvar all

Seanie280672 said:
post your fastboot getvar all please
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(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: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3855mV
(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

2dayquestion said:
The backup contained all of the original apps. Thought I could get it rolling again, but no go. Now the phone just won't boot. Stuck on the HTC one screen, even after another factory reset.
Click to expand...
Click to collapse
factory reset again
Install Titanium backup it will restore apps & data from nandroid backup
from HTC One

yatindroid said:
factory reset again
Install Titanium backup it will restore apps & data from nandroid backup
from HTC One
Click to expand...
Click to collapse
The factory reset isn't working. It still hangs. I did the initial backup through TWRP. Will Titanium backup be compatible with that backup?
Now the phone is currently locked, no OS.Should I flash another ROM?

http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match

Seanie280672 said:
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match
Click to expand...
Click to collapse
The OS is set to 1.000.000. I used some **** utility that reset it. I started clicking things... lol
One thing I'm wondering is since this phone is S-ON, will I be able to even flash a ROM? Could that be the reason that the TWRP restore function isn't working? As far as I know... SON would prevent system files from being written.. correct me if I'm wrong
..downloading that file as I write this

Seanie280672 said:
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_351317_signed_2-exe/
Looks like your RUU to return to fully stock
You could do with seeing if you can see this number anywhere in the bootloader 4.19.631.9 usually under os- however, radio's match
Click to expand...
Click to collapse
The phone is the HTC One m7 through Rogers. It was recently asking me for the latest OTA update. The ROM was stock, if that helps.

2dayquestion said:
The phone is the HTC One m7 through Rogers. It was recently asking me for the latest OTA update. The ROM was stock, if that helps.
Click to expand...
Click to collapse
looks like your RUU, like I said, its a Rogers RUU and contains the same radio, your version-main just threw me off a bit, leave your bootloader locked / relocked and plug into your computer in bootloader mode, then run the RUU on your computer, follow the instructions, make sure your battery is 50% or more before running.
regarding your other question, you can flash custom roms whilst s-on, you just have to make sure your bootloader is unlocked, s-on is not there to protect system files, its there to protect you from messing with the HBOOT and radio's etc which will brick the phone if done wrong, you cant brick by flashing rom's.

Seanie280672 said:
looks like your RUU, like I said, its a Rogers RUU and contains the same radio, your version-main just threw me off a bit, leave your bootloader locked / relocked and plug into your computer in bootloader mode, then run the RUU on your computer, follow the instructions, make sure your battery is 50% or more before running.
regarding your other question, you can flash custom roms whilst s-on, you just have to make sure your bootloader is unlocked, s-on is not there to protect system files, its there to protect you from messing with the HBOOT and radio's etc which will brick the phone if done wrong, you cant brick by flashing rom's.
Click to expand...
Click to collapse
Thanks a lot for that link. I found an RUU file about 7 hours ago, but it was in .zip format, not .exe like the link you provided me. This made it damn easy. I relocked the bootloader, installed, now it's all great. Thanks a lot. Can I thumbs up you, or do anything in return?

2dayquestion said:
Thanks a lot for that link. I found an RUU file about 7 hours ago, but it was in .zip format, not .exe like the link you provided me. This made it damn easy. I relocked the bootloader, installed, now it's all great. Thanks a lot. Can I thumbs up you, or do anything in return?
Click to expand...
Click to collapse
Just hit the thanks button a couple of times is plenty.
The Zip would of worked too, you just have to flash it in a special kinda way.
Glad its all working now, could you edit your title in your first post to SOLVED now please.

Seanie280672 said:
Just hit the thanks button a couple of times is plenty.
The Zip would of worked too, you just have to flash it in a special kinda way.
Glad its all working now, could you edit your title in your first post to SOLVED now please.
Click to expand...
Click to collapse
I'm guessing a side-load? I really like the install wizard, the RUU method is pretty ingenious. One quick question for you: It's asking me for a system update, OTA, that's not installing after I download it. I unlocked the bootloader through HTC dev using the binary they e-mail you. Would I have to unroot? Any tips on what I could do?
[edit: for some reason, OTA worked] thanks a lot for your help and especially for that magical link. cheers

2dayquestion said:
I'm guessing a side-load? I really like the install wizard, the RUU method is pretty ingenious. One quick question for you: It's asking me for a system update, OTA, that's not installing after I download it. I unlocked the bootloader through HTC dev using the binary they e-mail you. Would I have to unroot? Any tips on what I could do?
[edit: for some reason, OTA worked] thanks a lot for your help and especially for that magical link. cheers
Click to expand...
Click to collapse
No, you have to put your phone in fastbootRUU mode and then flash the zip from your computer using fastboot commands.
Glad the OTA worked in the end, but in future when installing OTA's just make sure your bootloader is locked / relocked first.

Seanie280672 said:
No, you have to put your phone in fastbootRUU mode and then flash the zip from your computer using fastboot commands.
Glad the OTA worked in the end, but in future when installing OTA's just make sure your bootloader is locked / relocked first.
Click to expand...
Click to collapse
That may have been the issue. Thanks for your time. Another 'thanks' is in order. Cheers

[Q] HTC One Vodafone System Update 6.12.161.5

Last night I got a notification for a System Update to version 6.12.161.5.
Has anyone tried this yet? And any problems found?
With the last two updates over the last 3-4 months I have had major problems:
1. When VodaFone forced the Rich Communication Suite / Service upon us; abysmal battery performance and terrible instability problem with phone frequently crashing on incoming calls and texts - which I 'solved' by Disabling RCS.
2. When VodaFone pushed the next update that greyed out the box to Disable RCS (they appeared to fix the instability and battery drain problem, but now I don't even have the option to disable RCS).
After lots of self-help and web searching I now have a stable phone with decent battery life again, and given those past painful experiences I am somewhat reluctant to blindly update.
Has anyone tried this Update yet, and can you comment after a few days of usage, particuarly on stability and battery usage?
Thanks
David

I had the 6.12.161.5 update a few days ago. Ive just had the 6.12.161.8 download now. Whats the difference?

Pilch2k said:
I had the 6.12.161.5 update a few days ago. Ive just had the 6.12.161.8 download now. Whats the difference?
Click to expand...
Click to collapse
Yeah, I also just had the 6.12.161.8 update. I've still not installed the previous one. I'm planning to wait this one out, after problems in the past. Will wait until some other folks try it first

daveingram said:
Yeah, I also just had the 6.12.161.8 update. I've still not installed the previous one. I'm planning to wait this one out, after problems in the past. Will wait until some other folks try it first
Click to expand...
Click to collapse
To be honest i've not noticed any issues yet, or any changes!

needed Ota file 6.12.161.8
Hi!
Would someone be so nice to post a link to his copy of this OTA? I need it desperately to revive my bricked One m7...
I've tryed anything but to flash this one on my s-on device..
Please help to save an Htc's life!! :cyclops:

Seymour2002 said:
Hi!
Would someone be so nice to post a link to his copy of this OTA? I need it desperately to revive my bricked One m7...
I've tryed anything but to flash this one on my s-on device..
Please help to save an Htc's life!! :cyclops:
Click to expand...
Click to collapse
you can not flash OTA to unbrick a phone. You need to flash the complete rom. And btw, OTA can not be flashed manually with S-ON, it must be initiated from the OS .

Flash firmware from OTA...
alray said:
you can not flash OTA to unbrick a phone. You need to flash the complete rom. And btw, OTA can not be flashed manually with S-ON, it must be initiated from the OS .
Click to expand...
Click to collapse
Well reading this sound like different from what you say... http://forum.xda-developers.com/showthread.php?t=2182823; but probably I'm wrong...
The actual thing is there's no Ruu nor OTA nor Zip for CID VODAP405 around... Or does?

Seymour2002 said:
Well reading this sound like different from what you say... http://forum.xda-developers.com/showthread.php?t=2182823;
Click to expand...
Click to collapse
Dont know what you are referring to.
The actual thing is there's no Ruu nor OTA nor Zip for CID VODAP405 around... Or does?
Click to expand...
Click to collapse
Unfortunately, there is not much files for that CID.
I don't understand what you want to attempt with an OTA file. Firmware included in OTA are not complete, it only contain files to be updated in an incremental way. If you manually flash a firmware from an OTA updates and you do it over the wrong version (currently installed on your phone) this could end with a bricked phone (hardbrick)
Flashing the entire OTA zip file will not help either. OTA files are patches that must be installed over a working rom and proper rom version. It also must be flashed using the "software update" option within the OS (unless the phone is s-off)
what you should do imo, is to start over fresh, flash twrp recovery 2.6.3.3 and flash a "close to stock" rom

Flash firmware from OTA...
First I want to thank for your help...
Then just to explain things, here's my awkward situation:
- I have a working rom but with battery that always stays at 1% no matter what, I get an ota update but I can't update since it says there's not enought battery...
the ota It gets is a 4.19.1540.9 which doesn't match with the follwing:
version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37WW904203
(bootloader) imei: 357864057367987
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP405
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
To finish the cake: recovery doesn't work and bootloader is relocked and doesn't unlock anymore....
Any suggestion?

Seymour2002 said:
First I want to thank for your help...
Then just to explain things, here's my awkward situation:
- I have a working rom but with battery that always stays at 1% no matter what, I get an ota update but I can't update since it says there's not enought battery...
the ota It gets is a 4.19.1540.9 which doesn't match with the follwing:
version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***************
(bootloader) imei: *********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP405
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
To finish the cake: recovery doesn't work and bootloader is relocked and doesn't unlock anymore....
Any suggestion?
Click to expand...
Click to collapse
how did you manage s-on + locked bootloader + no recovery ?
was this phone converted to DE or GPE at one time ?

Flash firmware from OTA...
I actually didn't do anything extraordinary except maybe to have flashed a rom with a different cid which got an update and brought me almost a this situation.
Then I wanted to bring the device to stock, so I flashed the original recovery and relocked the booloader. Nothing else.
I don't know why at the moment there's no way to enter recovery and if I try to unlock the bootloader again I reach the screen where I must agree on the device's screen to unlock, but then It just stuck on htc logo whilw trying to enter recovery..

Seymour2002 said:
I actually didn't do anything extraordinary except maybe to have flashed a rom with a different cid which got an update and brought me almost a this situation.
Then I wanted to bring the device to stock, so I flashed the original recovery and relocked the booloader. Nothing else.
I don't know why at the moment there's no way to enter recovery and if I try to unlock the bootloader again I reach the screen where I must agree on the device's screen to unlock, but then It just stuck on htc logo whilw trying to enter recovery..
Click to expand...
Click to collapse
are you sure your not just going to stock recovery ?
have you done the fastboot erase cache ?
followed by fastboot reboot-bootloader ?
what was the last custom recovery you had on their and what happened to make it gone ? RUU ?

Flash firmware from OTA...
clsA said:
are you sure your not just going to stock recovery ?
have you done the fastboot erase cache ? Yes, several times...
followed by fastboot reboot-bootloader ? Yes....
what was the last custom recovery you had on their and what happened to make it gone ? RUU ?
Click to expand...
Click to collapse
I was usimg twrp recovery, then I'm pretty sure I flashed the stock recovery, I don't know what happened to make it disappear, It just happened! I haven't been able to use any Ruu well since I never found the right one matching my CID., so I always got an error..

Seymour2002 said:
I was usimg twrp recovery, then I'm pretty sure I flashed the stock recovery, I don't know what happened to make it disappear, It just happened! I haven't been able to use any Ruu well since I never found the right one matching my CID., so I always got an error..
Click to expand...
Click to collapse
if you flashed the stock recovery correctly you go to the bootloader choose recovery hit power button
the screen will go black push volume up and tap power again to see the recovery menu, choose format data . factory reset
after it finishes reboot the phone and try again to unlock the bootloader

Flash firmware from OTA...
clsA said:
if you flashed the stock recovery correctly you go to the bootloader choose recovery hit power button
the screen will go black push volume up and tap power again to see the recovery menu, choose format data . factory reset
after it finishes reboot the phone and try again to unlock the bootloader
Click to expand...
Click to collapse
Once I select recovery from the bootloader menu and I press power button the phone reboots the bootloader...

SOLVED! Unbrikked THC ONE M/!!!!!
So thanks to MIke 1986 and his great page link:http://forum.xda-developers.com/showthread.php?t=2182823, I managed to recover my very very hrad brikked phone!!!!!!!!!
Here's what I did:
1- checked all phone's details with fastboot getavar all---> took note of CID - MID - versione OS installed etc.
2- took the OTA update corresponding to the firmware installed and extracted the firmware.zip
3- flashed the firmware.zip via fastboot (fastboot oem rebootRUU - fastboot flash zip firmware.zip [thanks to mike 1986]) ; #Alray: since a phone is S-On there's no risk to flash a wrong firmware and as I did anyone can do it via normal fastboot command with no issue!:angel:
4-In this way I recovered stock recovery and the possibility to unlock the bootloader again!!
5-moved a CWM nand backup to phone sd using sideload push command ( sideload push nandbackupname.zip /sd/cwm/backup/dateof backup - just make a nand backup yourself first to get exact loaction)
6-recovered from nandbackup using proper tool of cwm.
7-enjoyED MY revived device!!!!!! NOT THANKS TO ALRAY....http://cdn4.xda-developers.com/images/icons/icon8.gif

Seymour2002 said:
So thanks to MIke 1986 and his great page link:http://forum.xda-developers.com/showthread.php?t=2182823, I managed to recover my very very hrad brikked phone!!!!!!!!!
Here's what I did:
1- checked all phone's details with fastboot getavar all---> took note of CID - MID - versione OS installed etc.
2- took the OTA update corresponding to the firmware installed and extracted the firmware.zip
3- flashed the firmware.zip via fastboot (fastboot oem rebootRUU - fastboot flash zip firmware.zip [thanks to mike 1986]) ; #Alray: since a phone is S-On there's no risk to flash a wrong firmware and as I did anyone can do it via normal fastboot command with no issue!:angel:
4-In this way I recovered stock recovery and the possibility to unlock the bootloader again!!
5-moved a CWM nand backup to phone sd using sideload push command ( sideload push nandbackupname.zip /sd/cwm/backup/dateof backup - just make a nand backup yourself first to get exact loaction)
6-recovered from nandbackup using proper tool of cwm.
7-enjoyED MY revived device!!!!!! NOT THANKS TO ALRAY....http://cdn4.xda-developers.com/images/icons/icon8.gif
Click to expand...
Click to collapse
Glad you got your phone revived :good:
since a phone is S-On there's no risk to flash a wrong firmware
Click to expand...
Click to collapse
The risk is there, if you flash a firmware patch (ota firmware) over the wrong version (i.e 5.xx.xxx.x over 3.xx.xxx.x), this could brick. Happened many times that's why its mentioned in some threads. There is no risk flashing the same version like you did

[Q] Unable to go STOCK or flash other ROMs, adb shows device as offline

Hello xda members.
I'm having some trouble with my device, I did search around this past week but still didnt success in fixing it, hope someone can point me in the right direction.
So I was S-ON with 4.3 - 4.4 on ViperOne for a long time, most of the things worked fine but my 3G was a bit slow/disconnected from time to time.
I though giving a shot to a Lollipop version Sky Dragon. I downloaded and installed Sky Dragon and used it fine for some months, but then when I wanted to use Android Studio for a project my device was not recognized. I manually run adb devices and it would not show my device (debuggin on), tried some search on google but without success.
I though moving back to ViperOne / ARHD (I really missed SENSE) would solve my problem, so downloaded the rom and tried to install but it would always stuck in "formatting partition" process.
I manually put my device in fastboot and run getvar all which resulted in BLANK version-main, very strange.
I did some search but had only few similar cases, I tried to go to STOCK by re-lockocking bootloader, flashing stock firmware but the RUU.exe would always stop at 5% and show "fastboot_htc.exe has stopped working", again did some research but could not find a solution.
When I try to flash custom firmware through fastboot flash zip I will always get "(bootloader) Read zipped android_info fail FAILED (remote: 99 unknown fail)".
I then found a tool to write a version-main into the emmc and after flashing it in TWRP I got a 1.00.000.0 version-main. Tried all of above again with the same results. My device will be recognised as "offline" in adb devices.
Luckily I have some backups (viperone 4.3 and skydragon) that work fine except that I cant update and cant connect via adb.
I have outputted my getvar all, let me know if you need further info for my case.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxx
(bootloader) imei: xxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3976mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
What can you suggest me?
Thanks a lot guys, and sorry for the long story!

mindxpert said:
Hello xda members.
I'm having some trouble with my device, I did search around this past week but still didnt success in fixing it, hope someone can point me in the right direction.
So I was S-ON with 4.3 - 4.4 on ViperOne for a long time, most of the things worked fine but my 3G was a bit slow/disconnected from time to time.
I though giving a shot to a Lollipop version Sky Dragon. I downloaded and installed Sky Dragon and used it fine for some months, but then when I wanted to use Android Studio for a project my device was not recognized. I manually run adb devices and it would not show my device (debuggin on), tried some search on google but without success.
Click to expand...
Click to collapse
Update your driver to latest HTC drivers
Update you android SDK to latest version
I though moving back to ViperOne / ARHD (I really missed SENSE) would solve my problem, so downloaded the rom and tried to install but it would always stuck in "formatting partition" process.
Click to expand...
Click to collapse
What recovery version is installed on the phone?
I manually put my device in fastboot and run getvar all which resulted in BLANK version-main, very strange.
Click to expand...
Click to collapse
Not really, its a normal issue everyone get when using some twrp versions.
I did some search but had only few similar cases, I tried to go to STOCK by re-lockocking bootloader, flashing stock firmware but the RUU.exe would always stop at 5% and show "fastboot_htc.exe has stopped working", again did some research but could not find a solution.
Click to expand...
Click to collapse
Make sure to uninstall HTC Sync from your computer. Keep the drivers installed but uninstall HTC Sync. You are not giving any info about what ruu you are trying to flash but afaik, there is none you can use for this phone with s-on.
When I try to flash custom firmware through fastboot flash zip I will always get "(bootloader) Read zipped android_info fail FAILED (remote: 99 unknown fail)".
Click to expand...
Click to collapse
You can not flash custom firmware when S-ON...
I then found a tool to write a version-main into the emmc and after flashing it in TWRP I got a 1.00.000.0 version-main. Tried all of above again with the same results. My device will be recognised as "offline" in adb devices.
Click to expand...
Click to collapse
Having the version-main blank is not an issue preventing your phone to work properly, its only an aesthetic issue. The version-main can be restored by flashed the stock firmware back.

alray said:
Update your driver to latest HTC drivers
Update you android SDK to latest version
Click to expand...
Click to collapse
Already have the latest SDK version.
alray said:
What recovery version is installed on the phone?
Click to expand...
Click to collapse
I'm using TWRP 2.8.5.0
alray said:
Make sure to uninstall HTC Sync from your computer. Keep the drivers installed but uninstall HTC Sync. You are not giving any info about what ruu you are trying to flash but afaik, there is none you can use for this phone with s-on.
Click to expand...
Click to collapse
I found from my CID that this might be compatible RUU_M7_UL_K44_SENSE55_MR_Rogers_WWE_4.19.631.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_351317_signed_2.exe
alray said:
You can not flash custom firmware when S-ON...
Click to expand...
Click to collapse
So should I go S-OFF before? I'm not sure if I can downgrade and S-OFF in the current condition.
alray said:
Having the version-main blank is not an issue preventing your phone to work properly, its only an aesthetic issue. The version-main can be restored by flashed the stock firmware back.
Click to expand...
Click to collapse
Thank you for the clarification

mindxpert said:
Already have the latest SDK version.
Click to expand...
Click to collapse
And latest HTC drivers? Your phone should be visible from "my computer" when booted in twrp 2.8.5.0 cause twrp now have mtp support.
Code:
I found from my CID that this might be compatible RUU_M7_UL_K44_SENSE55_MR_Rogers_WWE_4.19.631.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_351317_signed_2.exe
Not with s-on. 4.19.631.9 is a downgrade, you need s-off to downgrade.
So should I go S-OFF before? I'm not sure if I can downgrade and S-OFF in the current condition.
Click to expand...
Click to collapse
You can go s-off using sunshine s-off but it cost 25$ or you can flash other roms by fixing your adb issues.

alray said:
And latest HTC drivers? Your phone should be visible from "my computer" when booted in twrp 2.8.5.0 cause twrp now have mtp support.
Click to expand...
Click to collapse
Yes my device is visible when in recovery.
alray said:
I found from my CID that this might be compatible RUU_M7_UL_K44_SENSE55_MR_Rogers_WWE_4.19.631.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_351317_signed_2.exe
Not with s-on. 4.19.631.9 is a downgrade, you need s-off to downgrade.
You can go s-off using sunshine s-off but it cost 25$ or you can flash other roms by fixing your adb issues.
Click to expand...
Click to collapse
I used sunshine to s-off my device. Currently downloading files from your signature post which had a case with my CID and MID to return stock then update firmware/rom,
Thanks, will report back tomorrow.