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] HTC One Bootlooping after Google Edition ARHD 6.0 installation

At this time I am pretty much hopeless... Seriously, nothing works, but if a miracle happens and I get my HTC One back to life it will be thanks to you guys.
So... This is my story:
Today I was using my HTC One M7_UL like any other day, I had Android OneDroid BETA 15 (a CyanogenMod with a few tweaks) installed and I got bored of it, so I decided to flash a Google Edition ROM. Came to the forum and looked for the thread with most replies on "Custom Android HTC One ROMs" and found the winner of the Google Edition ones, the ARHD 6.0 Google Edition. Fine, I thought, let's flash this [email protected]%#. So I started by downloading the latest version (roughly 550 MB) and connecting my HTC One to my Windows 8.1 Pro computer. The HTC drivers don't work with my 8.1 Pro Windows but since I only needed it to send the .zip file to my Internal Storage I gave it a shot. Copied everything, disconnected and proceeded to my recovery (TWRP) where I Wiped it up and flashed ARHD 6.0 GE. After installing, still on the recovery, restored the phone to factory presets and rebooted it. A Google logo appeared and some Nexus-like balls started to spin, some weird sh%t. Until there, everything absolutely fine, but it stood there with the balls spinning for 3~4 minutes and I thought it was normal because it was the first boot after flashing the new ROM. Got to Language Settings on the Android Welcome screen but then it quickly turned black and reeboted. HTC Logo appeared for roughly 1 second and it got black and rebooted again, this time starting back up but when I got to the Language setup it would do the same thing, over and over again.
So I started looking into it and didn't find many answers, then I decided to try and flash another Google Edition ROM, SkyDragon, but as I am a COMPLETE NOOB in this rooting and wobbly wobbly thingies I had no idea how I would get the .zip file to the Internal Storage, since the HTC One HAS NO SD CARD!!! I researched a bit and found sth called ADB Sideloading, which I am certain you know what it is, but the thing is, since my computer doesn't quite work with HTC Drivers I had to use my sister's PC, with Windows 7 and HTC One All-in-One kit. I could access my bootloader and recovery despite of the bootloop, which I think is a good thing, so I put it to fastboot mode, connected the cable to her computer and on the phone it changed from "fastboot" in red to "fastboot usb" in red also, so I thought, oh ok, it will work now. But when I tried ADB commands or tried any of the commands on the All-in-One thing it would just say "NO DEVICES FOUND" or something among those lines.
Anyway, if someone got this far I already thank you for trying to help but I am pretty certain I got a bricked device. I don't even now what to do, should I try to ADB Sideload this other ROM or should I try a Sense ROM, cuz I read somewhere that Google Edition ROMs only work when migrating from Sense ROMs, and if I am supposed to flash a Sense ROM how would I do so? Please try to be as simple as possible, I don't know much and I am pretty noob, anyways, thank you so much, and I hope you can help me!
(Also, before this bootloop it was S-OFF and now it shows as S-ON)
Waiting for a response,
John B.

You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.

BenPope said:
You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.
Click to expand...
Click to collapse
Yeah I am unlocked and untempered.
Here is my fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(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: 4309mV
(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.077s
And I am ABSOLUTELY SURE that before all of this it was S-OFF, ABSOLUTELY!

BenPope said:
You need TWRP 2.6.33 or newer.
You need to be S-Off.
You need to have wiped cache and dalvik and probably a full format (except sdcard) wouldn't go amiss before installing. It sounds to me like it wasn't wiped properly.
The device doesn't S-On on its own, you probably did it with the toolkit or something.
ADB doesn't work in fastboot mode, fastboot mode is for fastboot command, such as flashing recovery.
Are you still unlocked?
Give us the output of
fastboot getvar all
Without IMEI and Serial Number.
Click to expand...
Click to collapse
Also my TWRP is 2.6.3.3 so I should be good about that right?

Jvov said:
Also my TWRP is 2.6.3.3 so I should be good about that right?
Click to expand...
Click to collapse
Yes, but as far as I know, you need to be S-Off for GPE KitKat ROMs.
Do you really have no version-main?
If your hboot is 1.44 and dated prior to June, you should be able to use revone to S-Off, but you'll need a booting ROM of Android 4.2.2.

BenPope said:
Yes, but as far as I know, you need to be S-Off for GPE KitKat ROMs.
Do you really have no version-main?
If your hboot is 1.44 and dated prior to June, you should be able to use revone to S-Off, but you'll need a booting ROM of Android 4.2.2.
Click to expand...
Click to collapse
Can you explain exactly how can I do that?

Just flash back to another ROM for the moment that has root then use rumrunner to get S-OFF then flash ARHD GPE again. You'll be fine then.
Sent from my One using XDA Premium 4 mobile app

Also don't do a reset after flashing the rom. It will boot loop every time.
Bat cave One

zelendel said:
Also don't do a reset after flashing the rom. It will boot loop every time.
Bat cave One
Click to expand...
Click to collapse
Solved, thanks to all!

[Q] SOFT BRICKED HTC ONE. Tried Everything!!!

Hi there. This is my first thread in your great site. I have Installed custom roms hundreds of times on various handsets. Yesterday I purchased an HTC One and decided to stick a custom rom on there straight away.
Now I have a problem.....The only thing I can do is get into bootloader and recovery, I can get that far, what I cant do is install any kind of rom to get my phone working. It seems all my data has been wiped, cant mount usb using cwm or twrp so cant just stick a rom on there and flash it. Can't sideload using ADB, pretty much cant get any kind of rom on there at all. I tried using an RUU.exe to return to stock but that fails also (it stays at 5% 'headers' and goes no further)
I have literally been through every search option on google and tried every method I have found for the last 12-13 hours trying to get this solved and i'm now starting to think I have genuinelly done something terrible to my phone and that it is unrecoverable.
My final hope is that one of you genius wizardy type of guys that seem to frequent these forums could help. Im getting desperate now
EDIT: I think I flashed a rom for the M8 version like a fricking noob. Does this mean my phone is knacked?

terrypmarshall said:
Hi there. This is my first thread in your great site. I have Installed custom roms hundreds of times on various handsets. Yesterday I purchased an HTC One and decided to stick a custom rom on there straight away.
Now I have a problem.....The only thing I can do is get into bootloader and recovery, I can get that far, what I cant do is install any kind of rom to get my phone working. It seems all my data has been wiped, cant mount usb using cwm or twrp so cant just stick a rom on there and flash it. Can't sideload using ADB, pretty much cant get any kind of rom on there at all. I tried using an RUU.exe to return to stock but that fails also (it stays at 5% 'headers' and goes no further)
I have literally been through every search option on google and tried every method I have found for the last 12-13 hours trying to get this solved and i'm now starting to think I have genuinelly done something terrible to my phone and that it is unrecoverable.
My final hope is that one of you genius wizardy type of guys that seem to frequent these forums could help. Im getting desperate now [/B]
EDIT: I think I flashed a rom for the M8 version like a fricking noob. Does this mean my phone is knacked?
Click to expand...
Click to collapse
Why not start with
1- a "fastboot getvar all" (excluding IMEI and s/n),
2- what recovery you have (name and version number)
3- what were you trying to flash? link please

nkk71 said:
Why not start with
1- a "fastboot getvar all" (excluding IMEI and s/n),
2- what recovery you have (name and version number)
3- what were you trying to flash? link please
Click to expand...
Click to collapse
Yeah that would help wouldnt it sorry. im using TWRP 2.7.1.1
I was tring to flash HD revolution rom but it seems i downloaded and used the M8 version

(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4336mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11

terrypmarshall said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) hbootpreupdate: 11
Click to expand...
Click to collapse
1- edit your post and remove IMEI,
2- use TWRP 2.6.3.3 or 2.6.3.4 (maybe 2.7.1.1 works, I haven't tested, but 2.7.0.0 does not)
3- ARHD 71.1 (m7_u/ul) is here http://forum.xda-developers.com/showthread.php?t=2183023

nkk71 said:
1- edit your post and remove IMEI,
2- use TWRP 2.6.3.3 or 2.6.3.4 (maybe 2.7.1.1 works, I haven't tested, but 2.7.0.0 does not)
3- ARHD 71.1 (m7_u/ul) is here http://forum.xda-developers.com/showthread.php?t=2183023
Click to expand...
Click to collapse
yep did that but had to wait the 5 mins b4 i could remove the imei lol.
I actually tried your fix here http://forum.xda-developers.com/showthread.php?t=2739126&page=2 just incase.
gonna try TWRP 2.6 now and see if i get any movement......
thank you for your help so far

terrypmarshall said:
yep did that but had to wait the 5 mins b4 i could remove the imei lol.
I actually tried your fix here http://forum.xda-developers.com/showthread.php?t=2739126&page=2 just incase.
gonna try TWRP 2.6 now and see if i get any movement......
thank you for your help so far
Click to expand...
Click to collapse
i'm checking the updater-script on the M8 version for possible damage...
EDIT: twrp 2.6.3.3 or .4

ok installed twrp 2.6.3.3 and still no luck in mounting storage via usb. I know the \sdcard\ section of the phone is empty through looking at file manager. I dont know if this has anything to do with it. In bootloader my OS listing is blank, like there is nothing there. I have used your fix for the Active Cmdline Overflow just incase it was that as i figured this kind of falls into that category.
At the moment, I have d/l an old RUU.exe for jellybean after relocking my phone and that is currently installing although it is stuck on 7% ''Checking Header'' and has been for a while now. I dont expect it to move on any further.
One word.....gutted, wish I had left it alone now ffs

terrypmarshall said:
ok installed twrp 2.6.3.3 and still no luck in mounting storage via usb. I know the \sdcard\ section of the phone is empty through looking at file manager. I dont know if this has anything to do with it. In bootloader my OS listing is blank, like there is nothing there. I have used your fix for the Active Cmdline Overflow just incase it was that as i figured this kind of falls into that category.
At the moment, I have d/l an old RUU.exe for jellybean after relocking my phone and that is currently installing although it is stuck on 7% ''Checking Header'' and has been for a while now. I dont expect it to move on any further.
One word.....gutted, wish I had left it alone now ffs
Click to expand...
Click to collapse
you need to chill and relax, you are now rushing things (aka panic mode), and you are going to get into trouble if you continue, let me when you are calm and relaxed.
apologies if that sounds not nice of me, but random flashing (including fixing something that doesn't need fixing), is not a good way to go.
I checked the updater-script of ARHD 7.0 for M8 and it probably hasn't touched any sensitive partitions on the m7
Take a break and come back, in a while, i'll post back

nkk71 said:
you need to chill and relax, you are now rushing things (aka panic mode), and you are going to get into trouble if you continue, let me when you are calm and relaxed.
apologies if that sounds not nice of me, but random flashing (including fixing something that doesn't need fixing), is not a good way to go.
I checked the updater-script of ARHD 7.0 for M8 and it probably hasn't touched any sensitive partitions on the m7
Take a break and come back, in a while, i'll post back
Click to expand...
Click to collapse
lol, yeah your right was in panic mode. I'm cool though, not touching it again until you tell me to hehehe. Im calm and relaxed. Just need reassurance that there will be a slim chance it can be fixed.
Let me know what you think when your ready mate, I appreciate the help a lot

terrypmarshall said:
lol, yeah your right was in panic mode. I'm cool though, not touching it again until you tell me to hehehe. Im calm and relaxed. Just need reassurance that there will be a slim chance it can be fixed.
Let me know what you think when your ready mate, I appreciate the help a lot
Click to expand...
Click to collapse
gimme 20 mins... kids want some attention before bed :laugh:

interesting side note though......When I plugged into usb and turned phone on, it is trying to download the drivers for HTC One_M8.......
fails, and also MTP USB Device driver download fails

terrypmarshall said:
interesting side note though......When I plugged into usb and turned phone on, it is trying to download the drivers for HTC One_M8.......
fails, and also MTP USB Device driver download fails
Click to expand...
Click to collapse
are you trying to boot the M8 ROM?? why??
so go back to TWRP 2.6.3.3 or 2.6.3.4 and completely format your phone:
To completely format the relevant partitions, you do the following in TWRP:
1) "Format Data", that will format /data and internal storage
2) Advanced Wipe -> /system and /cache, that will format /system and /cache
3) reboot to recovery
then follow the instruction here (though you should already be familiar with the FAQ sticky ) section 'D' to get the ROM onto your phone and install it: http://forum.xda-developers.com/showthread.php?p=53270352&postcount=21

nkk71 said:
are you trying to boot the M8 ROM?? why??
so go back to TWRP 2.6.3.3 or 2.6.3.4 and completely format your phone:
To completely format the relevant partitions, you do the following in TWRP:
1) "Format Data", that will format /data and internal storage
2) Advanced Wipe -> /system and /cache, that will format /system and /cache
3) reboot to recovery
then follow the instruction here (though you should already be familiar with the FAQ sticky ) section 'D' to get the ROM onto your phone and install it: http://forum.xda-developers.com/showthread.php?p=53270352&postcount=21
Click to expand...
Click to collapse
lol, no wasnt intentionally trying to boot the M8 rom, it was trying to do it itself. After the format data steps etc, I now have my system stuff back to normal (no longer states 0MB) couldn't mount with usb using recovery so cant drag and drop rom and install that way so currently trying to install using adb sideload.
If this works i will give you more kids rofl

failed to write data ' protocol fault (no data)
sigh......
oh well, its further than I have gotten all day thanks to you
btw....sorry for double posting all the time mods

you sir are a mod god.....used the push method and its installed the rom.
thank you so much for your help mate, i really do appreciate it. :laugh:

[Q] Please help What should i do before upgrading to lollipop?

Hi guys.
I really trust xda forums and that's why I come here whenever I need help. You always save the day guys and I want to thank you for that.
So a while ago I've unlocked the boot loader, flashed cwm recovery via fast boot and rooted my device. I'm still on a stock Rom though.
Now I want to upgrade to lollipop manually, my plan is to download the official Rom from HTC's website connect my device to the pc with a usb cable then install it on my phone.. From what I understand I should flash back the stock recovery then relock the boot loader and restore the contents of a folder (i don't remember what folder though). Where can I find the stock Rom img file I should flash? (And the folder contents that i'm supposed to restore) also if I relock the boot loader will the upgrade proceed if it still shows "tampered"?
Please guys help what am I supposed to do before upgrading??

monrokhoury said:
Hi guys.
I really trust xda forums and that's why I come here whenever I need help. You ashtrays save the day guys and I want to thank you for that.
So a while ago I've unlocked the boot loader, flashed cwm recovery via fast boot and rooted my device. I'm still on a stock Rom though.
Now I want to upgrade to lollipop manually, my plan is to download the official Rom from HTC's website connect my device to the pc with a usb cable then install it on my phone.. From what I understand I should flash back the stock recovery then relock the boot loader and restore the contents of a folder (i don't remember what folder though). Where can I find the stock Rom img file I should flash? (And the folder contents that i'm supposed to restore) also if I relock the boot loader will the upgrade proceed if it still shows "tampered"?
Please guys help what am I supposed to do before upgrading??
Click to expand...
Click to collapse
You need to restore the preload data. This gets wiped when you unlock the bootloader and it will cause the OTA to fail. Relocking isn't necessary for installing ota's you just need Stock Rom and Recovery. A GuruReset is usually the way to go.
If your talking about flashing the RUU then you will need to relock the bootloader if your s-on but that's it. Missing preload data, rooted rom's and custom recovery will not effect the RUU install. It will just flash stock over the top of it all. Your phone will be wiped though so backup any data you want to keep. :good:
If you need more help finding the correct software post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting

Danny201281 said:
You need to restore the preload data. This gets wiped when you unlock the bootloader and it will cause the OTA to fail. Relocking isn't necessary for installing ota's you just need Stock Rom and Recovery. A GuruReset is usually the way to go.
If your talking about flashing the RUU then you will need to relock the bootloader if your s-on but that's it. Missing preload data, rooted rom's and custom recovery will not effect the RUU install. It will just flash stock over the top of it all. Your phone will be wiped though so backup any data you want to keep. :good:
If you need more help finding the correct software post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting
Click to expand...
Click to collapse
done, here's what that returned:
D:\Program Files\Android>fastboot getvar all
(bootloader) 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.09.401.111
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode:y SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.071s
thanks for helping me find the software. I need to know how to restore the preloade data. I know how to flash the stock recovery but I don't have it. I gotta admit btw that I don't know what ruu is.

monrokhoury said:
done, here's what that returned:
D:\Program Files\Android>fastboot getvar all
(bootloader) 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.09.401.111
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode:y SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.071s
thanks for helping me find the software. I need to know how to restore the preloade data. I know how to flash the stock recovery but I don't have it. I gotta admit btw that I don't know what ruu is.
Click to expand...
Click to collapse
Ok thanks you don't need to worry about an RUU because there isn't one for your Device.
Do you know how to use a nandroid backup? There is a Stock TWRP nandroid and the recovery you need in this thread here http://forum.xda-developers.com/htc-one/development/backup-100-stock-6-09-401-111-twrp-t2992871 :good: you can use this to restore your Device back so you can get OTA updates

Danny201281 said:
Ok thanks you don't need to worry about an RUU because there isn't one for your Device.
Do you know how to use a nandroid backup? There is a Stock TWRP nandroid and the recovery you need in this thread here http://forum.xda-developers.com/htc-one/development/backup-100-stock-6-09-401-111-twrp-t2992871 :good: you can use this to restore your Device back so you can get OTA updates
Click to expand...
Click to collapse
I have cwm recovery on my phone, can I use it to flash the nanodroid backup? or do I have to flash twrp recovery?
and after flashing the nanodroid backup I just have to flash the stock recovery and then upgrade?
which one is the nanodroid backup I need to flash? is it this one:
" TWRP Backup: https://yadi.sk/d/rQzZ9i0CdmstQ "
or this:
"6.09.401.111 Firmware with Hboot 1.57.000 https://yadi.sk/d/n7BAQ8vpdqPSS "
??
and do I need to worry about the radio file in your link?
thanxx for your help man!

Sorry for bothering you too much but I've been thinking, wouldn't it be easier to restore the preloaded data instead of downloading and flashing the backup? Is that possible??
Thanx man

monrokhoury said:
Sorry for bothering you too much but I've been thinking, wouldn't it be easier to restore the preloaded data instead of downloading and flashing the backup? Is that possible??
Thanx man
Click to expand...
Click to collapse
If you can find a download for just the preload data then yes that would be easier. I'll see if I can find something.
Otherwise you want the TWRP backup from that thread and you will need to flash TWRP recovery to restore it. And just to clarify you can't flash the nandroid backup like a normal Rom. You will need to unzip it and copy the folder in to your TWRP backups folder then use the restore option in twrp
The radio file is not such a big issue it will be the same radio you already have anyway.
---------- Post added at 10:35 PM ---------- Previous post was at 10:24 PM ----------
monrokhoury said:
Sorry for bothering you too much but I've been thinking, wouldn't it be easier to restore the preloaded data instead of downloading and flashing the backup? Is that possible??
Thanx man
Click to expand...
Click to collapse
Preload data this is the closest I can find. It may or may not work so try at your own risk.
http://goo.gl/XvLuE0
This is the preload data from 6.09.401.12 which is the lte version of your Device. The preload data may well be the same as the only difference is that 1 device has lte enabled and the other (your Device does not) :good:

Danny201281 said:
If you can find a download for just the preload data then yes that would be easier. I'll see if I can find something.
Otherwise you want the TWRP backup from that thread and you will need to flash TWRP recovery to restore it. And just to clarify you can't flash the nandroid backup like a normal Rom. You will need to unzip it and copy the folder in to your TWRP backups folder then use the restore option in twrp
The radio file is not such a big issue it will be the same radio you already have anyway.
---------- Post added at 10:35 PM ---------- Previous post was at 10:24 PM ----------
Preload data this is the closest I can find. It may or may not work so try at your own risk.
http://goo.gl/XvLuE0
This is the preload data from 6.09.401.12 which is the lte version of your Device. The preload data may well be the same as the only difference is that 1 device has lte enabled and the other (your Device does not) :good:
Click to expand...
Click to collapse
Man, you're the best

monrokhoury said:
Man, you're the best
Click to expand...
Click to collapse
There is no data / preload folder in the backup either, are you sure you need it for this particular device ?
you can download the TWRP backup and extract it then open each individual file, like the system file with winrar, like ive done, this is the system folder from the backup, (see pict below)

Seanie280672 said:
There is no data / preload folder in the backup either, are you sure you need it for this particular device ?
you can download the TWRP backup and extract it then open each individual file, like the system file with winrar, like ive done, this is the system folder from the backup, (see pict below)
Click to expand...
Click to collapse
so this backup won't allow me to restore the preload contents? is there anyway to restore it? or should I forget about ota updates?

monrokhoury said:
so this backup won't allow me to restore the preload contents? is there anyway to restore it? or should I forget about ota updates?
Click to expand...
Click to collapse
no this backup doesnt appear to contain the data/preload contents, but thats why I said have you tried to update ?, is the update available to you yet ? maybe the M7_U is different to the UL and doesnt require this folder, or you could try as Danny stated earlier and use the UL ones he linked you too. :good:

Seanie280672 said:
no this backup doesnt appear to contain the data/preload contents, but thats why I said have you tried to update ?, is the update available to you yet ? maybe the M7_U is different to the UL and doesnt require this folder, or you could try as Danny stated earlier and use the UL ones he linked you too. :good:
Click to expand...
Click to collapse
I want to update manually by downloading the update file from HTC's website and then following these instructions to upgrade:
Performing the ROM Update:
1. Download and save the HTC One™ ROM update to your PC.
2. Connect your device to your PC via the supplied USB cable.
3. If the device is not recognized by the PC, ensure you have HTC Sync Manager installed and then disconnect and reconnect the device from the USB cable.
4. Once the device is properly recognized on the PC, locate the HTC One™ ROM update that you downloaded. Double-click on the file to launch the system update wizard.
5. Follow all of the system update wizard instructions shown on your PC.
6. Once the update is complete, click Finish in the Wizard and the device will reboot.
7. Once the device reboots, the initial setup wizard will appear.
8. Once the initial setup process is complete, the device is ready for use.
I found them here.
Danny said that manually restoring the contents might not work.. if I restore them and then try upgrading can it brick the phone? and how can I restore them anyway?
thaaaanx

monrokhoury said:
I want to update manually by downloading the update file from HTC's website and then following these instructions to upgrade:
Danny said that manually restoring the contents might not work.. if I restore them and then try upgrading can it brick the phone? and how can I restore them anyway?
thaaaanx
Click to expand...
Click to collapse
Not too sure about restoring the contents manually, I have done it myself before, but on a different HTC One SV a couple of years ago in order to update, but I did have a hell of a game doing it, even came down to creating the data and preload folders in system on my phone myself andf setting the correct premissions and then placing each file in there manually, I really wouldnt like to say if it would work for your device or not.
On a different note, which update files have you found, could you supply a link please, and I thought you had to be s-off to manually update regardless ?

Seanie280672 said:
Not too sure about restoring the contents manually, I have done it myself before, but on a different HTC One SV a couple of years ago in order to update, but I did have a hell of a game doing it, even came down to creating the data and preload folders in system on my phone myself andf setting the correct premissions and then placing each file in there manually, I really wouldnt like to say if it would work for your device or not.
On a different note, which update files have you found, could you supply a link please, and I thought you had to be s-off to manually update regardless ?
Click to expand...
Click to collapse
no you don't need to s-off cause you'll be updating using HTC sync manager.
here's a link:
http://www.htc.com/us/support/rom-downloads.html
let's say I'm considering flashing maximushd Rom, I have flashed twrp recovery 2.8.4.0, now I just have to do a full wipe using it and then flash the Rom?

monrokhoury said:
no you don't need to s-off cause you'll be updating using HTC sync manager.
here's a link:
http://www.htc.com/us/support/rom-downloads.html
let's say I'm considering flashing maximushd Rom, I have flashed twrp recovery 2.8.4.0, now I just have to do a full wipe using it and then flash the Rom?
Click to expand...
Click to collapse
There is no lollipop update on that page for your phone, only the dev edition M7, but yes to MHD Rom, and if you get s-off you can flash the matching firmware too.

Seanie280672 said:
There is no lollipop update on that page for your phone, only the dev edition M7, but yes to MHD Rom, and if you get s-off you can flash the matching firmware too.
Click to expand...
Click to collapse
" Unlocked/Developer
Device Name Latest ROM # Details and Instructions Link
HTC One (M8) 4.16.1540.8
View
Download
HTC One 7.17.1540.7
View
Download
HTC One max 3.23.1540.1 N/A
Download"
mine is an unlocked m7.
is switching s-off and flashing the firmware a must? bc some members told me that they just flashed the Rom using twrp recovery and everything went fine.. do you confirm?

monrokhoury said:
" Unlocked/Developer
Device Name Latest ROM # Details and Instructions Link
HTC One (M8) 4.16.1540.8
View
Download
HTC One 7.17.1540.7
View
Download
HTC One max 3.23.1540.1 N/A
Download"
mine is an unlocked m7.
is switching s-off and flashing the firmware a must? bc some members told me that they just flashed the Rom using twrp recovery and everything went fine.. do you confirm?
Click to expand...
Click to collapse
No flashing the firmware isn't required, although it's recommended, you should be ok just to flash the Rom, it's just the same as flashing a custom Rom.
As for unlocked its a different type of unlocked, confusing I know, yours is just network unlocked, that ruu / ota is dev edition, unlocked bootloader and s-off unlocked from the factory, have a look at the version number, the 3rd set of digits is what matters, that's 1540 dev, your output on page 1 states 401 international edition.

Seanie280672 said:
No flashing the firmware isn't required, although it's recommended, you should be ok just to flash the Rom, it's just the same as flashing a custom Rom.
As for unlocked its a different type of unlocked, confusing I know, yours is just network unlocked, that ruu / ota is dev edition, unlocked bootloader and s-off unlocked from the factory, have a look at the version number, the 3rd set of digits is what matters, that's 1540 dev, your output on page 1 states 401 international edition.
Click to expand...
Click to collapse
thanks for explaining that man you're amazing you saved me a lot of time.. I guess I'll download and flash mhd though I gotta ask, why is flashing the firmware recommended?
and is mhd a good Rom in your opinion?
Anyway I made a full nanodroid backup using twrp so that I can roll back if I don't like the results.. that'll work right?
thaaaaanx again

monrokhoury said:
thanks for explaining that man you're amazing you saved me a lot of time.. I guess I'll download and flash mhd though I gotta ask, why is flashing the firmware recommended?
and is mhd a good Rom in your opinion?
Anyway I made a full nanodroid backup using twrp so that I can roll back if I don't like the results.. that'll work right?
thaaaaanx again
Click to expand...
Click to collapse
Nandroid is always recommended and a good idea, I use mhd myself, they are all very much the same at the moment to be honest, the differences between them are very minimal, and matching firmware to the Rom version is always recommended to save a potential problems.
---------- Post added at 09:35 AM ---------- Previous post was at 09:26 AM ----------
Just to add, when the official SIGNED - (that's important) 401 firmware comes out and is available you will be able to flash that, at the moment it's unsigned and will brick your phone. You'll just need to relock your boot loader first as your s-on, then flash it like any other firmware, then re-unlock your bootloader and reflash a custom recovery.

Seanie280672 said:
Nandroid is always recommended and a good idea, I use mhd myself, they are all very much the same at the moment to be honest, the differences between them are very minimal, and matching firmware to the Rom version is always recommended to save a potential problems.
---------- Post added at 09:35 AM ---------- Previous post was at 09:26 AM ----------
Just to add, when the official SIGNED - (that's important) 401 firmware comes out and is available you will be able to flash that, at the moment it's unsigned and will brick your phone. You'll just need to relock your boot loader first as your s-on, then flash it like any other firmware, then re-unlock your bootloader and reflash a custom recovery.
Click to expand...
Click to collapse
I hear you, abd I won't need to restore the preload contents that got quoted when I unlocked the boot loader?

Softbrick Going From CM12.1 to Stock

Hey everyone. I read a lot of posts and tutorials on here (love it) and I've done what I can to try and fix my issue, but I've hit a wall. Even a nudge in the right direction would be amazing. I am working with an AT&T HTC One M7 variant (CWS 001). Here are some relevant settings as to where I am now (below them is the progress of why they are what they are):
HBOOT 1.56
S-ON
Bootloader unlocked
TWRP v2.8.7.0 installed
SuperSU BETA 2.94
Android 4.1.2
Software 1.26.502.15
I recently flashed CM12.1 onto my HTC One M7. Prior to doing so, I did an
Code:
adb backup
(which I now assume I should have done a backup through TWRP?). I wanted to go back to official Android, so I did an
Code:
adb restore
to no avail. This worked for me in the past, so either I'm not sure whether it was wrong to begin with, or something went wrong in general. Either way, that's moot point.
Since that failed, I settled on the method laid out at http://www.htc1guru.com/downloads/stock-rom-downloads/ to restore to stock... Believing that it would restore to stock ROM, remove custom recovery and root, and I would be able to take OTA updates and start fresh-ish.
Long story short, I followed the video and ended up with software version "1.26.502.12" as expected... No touch controls, used a mouse to receive OTA update via WiFi. Somewhere along the process of installing the update, I got a message that it failed, was not able to capture the error, and the device rebooted. As a result of that failure, the software was updated to "1.26.502.15" but the WiFi is now broken... Of course meaning no OTA update. Since the touch controls do not work, I can't use the USB internet pass-through, so my device is relegated to mobile data.
I attempted to relock the bootloader (after affirming that the recovery looked to be stock) and run an RUU to update the phone (also unrooted at this point). I started with the official ROM listed on the HTC website, but I get a 155 error (which, as far as I've been able to find, should not be getting as the bootloader was relocked). I tried an RUU from htc1guru for 1.26.502.15, resulting in the same error. So all I can tell is that something is causing any RUU to fail (would there be logs somewhere?)
At this point I went "eff it, I should be able to get back to CM12.1 at least." So I unlocked the bootloader, installed TWRP v2.8.7.0, and initially installed SuperSU BETA 2.94. TWRP fails each time trying to flash CM12.1 now, however. It now also fails to flash the Guru reset from above.
And that now brings me to today... Basically at a complete loss as to next steps. Clearly I've bungled the whole thing and either taken a misstep or (more likely) a bunch of missteps. My device is successfully rooted, as I was able to download Flashify via the Play Store, open it, and see that it was granted permissions. I'm thinking that my next step might be to try flashing a stock recovery from http://forum.xda-developers.com/showthread.php?t=2545227 via Flashify and seeing if that works.
If it doesn't... Man, I could really use the help! Otherwise, I'm using a Lumia 635 indefinitely...

scirto said:
Hey everyone. I read a lot of posts and tutorials on here (love it) and I've done what I can to try and fix my issue, but I've hit a wall. Even a nudge in the right direction would be amazing. I am working with an AT&T HTC One M7 variant (CWS 001). Here are some relevant settings as to where I am now (below them is the progress of why they are what they are):
HBOOT 1.56
S-ON
Bootloader unlocked
TWRP v2.8.7.0 installed
SuperSU BETA 2.94
Android 4.1.2
Software 1.26.502.15
I recently flashed CM12.1 onto my HTC One M7. Prior to doing so, I did an
Code:
adb backup
(which I now assume I should have done a backup through TWRP?). I wanted to go back to official Android, so I did an
Code:
adb restore
to no avail. This worked for me in the past, so either I'm not sure whether it was wrong to begin with, or something went wrong in general. Either way, that's moot point.
Since that failed, I settled on the method laid out at http://www.htc1guru.com/downloads/stock-rom-downloads/ to restore to stock... Believing that it would restore to stock ROM, remove custom recovery and root, and I would be able to take OTA updates and start fresh-ish.
Long story short, I followed the video and ended up with software version "1.26.502.12" as expected... No touch controls, used a mouse to receive OTA update via WiFi. Somewhere along the process of installing the update, I got a message that it failed, was not able to capture the error, and the device rebooted. As a result of that failure, the software was updated to "1.26.502.15" but the WiFi is now broken... Of course meaning no OTA update. Since the touch controls do not work, I can't use the USB internet pass-through, so my device is relegated to mobile data.
I attempted to relock the bootloader (after affirming that the recovery looked to be stock) and run an RUU to update the phone (also unrooted at this point). I started with the official ROM listed on the HTC website, but I get a 155 error (which, as far as I've been able to find, should not be getting as the bootloader was relocked). I tried an RUU from htc1guru for 1.26.502.15, resulting in the same error. So all I can tell is that something is causing any RUU to fail (would there be logs somewhere?)
At this point I went "eff it, I should be able to get back to CM12.1 at least." So I unlocked the bootloader, installed TWRP v2.8.7.0, and initially installed SuperSU BETA 2.94. TWRP fails each time trying to flash CM12.1 now, however. It now also fails to flash the Guru reset from above.
And that now brings me to today... Basically at a complete loss as to next steps. Clearly I've bungled the whole thing and either taken a misstep or (more likely) a bunch of missteps. My device is successfully rooted, as I was able to download Flashify via the Play Store, open it, and see that it was granted permissions. I'm thinking that my next step might be to try flashing a stock recovery from http://forum.xda-developers.com/showthread.php?t=2545227 via Flashify and seeing if that works.
If it doesn't... Man, I could really use the help! Otherwise, I'm using a Lumia 635 indefinitely...
Click to expand...
Click to collapse
Ignore my last paragraph. I completely misread what that file was providing (stock recovery, duh, of course that's what it's providing. Not what I need).

Also, if this helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT344W907896
(bootloader) imei: 354439054277373
(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: 3849mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

scirto said:
Also, if this helps:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT344W907896
(bootloader) imei: 354439054277373
(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: 3849mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Hey, just picked up your post in the Unbrick thread. So basically your problem started when you tried to take OTA updates with a Stock rom older than your current firmware.
You can't downgrade firmware while s-on. So when the OTA tried to flash the firmware it failed
The simplest way to get you back to a working stock device will be to use an ruu. You can use this one here http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Download it and put it on your pc desktop. Then reboot your device to the bootloader and connect fastboot usb. Because your s-on we need to relock the bootloader or the flash will fail so enter these commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Once the bootloader reboots check it's relocked and in fastboot usb mode then launch the ruu .exe from your desktop. Follow the instructions on your pc. When the flash is complete your device should be back to stock and boot right up.
Then you can take OTA updates safely before unlocking your bootloader again :good:
Sent from my M7 ARHD 84-Kitkat

Danny201281 said:
Hey, just picked up your post in the Unbrick thread. So basically your problem started when you tried to take OTA updates with a Stock rom older than your current firmware.
You can't downgrade firmware while s-on. So when the OTA tried to flash the firmware it failed
The simplest way to get you back to a working stock device will be to use an ruu. You can use this one here http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
Download it and put it on your pc desktop. Then reboot your device to the bootloader and connect fastboot usb. Because your s-on we need to relock the bootloader or the flash will fail so enter these commands.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Once the bootloader reboots check it's relocked and in fastboot usb mode then launch the ruu .exe from your desktop. Follow the instructions on your pc. When the flash is complete your device should be back to stock and boot right up.
Then you can take OTA updates safely before unlocking your bootloader again :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
First off, just want to say thanks for the response! I'll give it a shot with a different RUU, but I do want to mention that I have tried this process (albeit different RUU) and it failed.
So I first tried with the most recent RUU officially provided by HTC. It failed, which led me research to discover that I needed to relock the bootloader (received error code 155). So I relocked the bootloader, tried the same RUU again but received the same error code. So I have tried this with no success so far, but I will try again with the RUU you linked.
Also, I think I found where the logs get dumped from the RUU process so I will link my progress with the output in the event it does fail. Right now, before I try it, I will mention that I am now running software 1.26.502.10 (restored from a nandroid backup), stock recovery, but I am rooted. Does the RUU remove the root, or will it leave it and then I need to unroot to OTA update?
Anyways, more to come shortly...
EDIT: I will also note that my last attempt with an RUU was with my phone starting on the home screen. Not sure if starting in bootloader/fastboot is better or worse or makes no difference? I'll try that too

scirto said:
First off, just want to say thanks for the response! I'll give it a shot with a different RUU, but I do want to mention that I have tried this process (albeit different RUU) and it failed.
So I first tried with the most recent RUU officially provided by HTC. It failed, which led me research to discover that I needed to relock the bootloader (received error code 155). So I relocked the bootloader, tried the same RUU again but received the same error code. So I have tried this with no success so far, but I will try again with the RUU you linked.
Also, I think I found where the logs get dumped from the RUU process so I will link my progress with the output in the event it does fail. Right now, before I try it, I will mention that I am now running software 1.26.502.10 (restored from a nandroid backup), stock recovery, but I am rooted. Does the RUU remove the root, or will it leave it and then I need to unroot to OTA update?
Anyways, more to come shortly...
Click to expand...
Click to collapse
The problem is because your s-on. The way firmware is flashed is very strict with s-on.
You must Relock the bootloader.
You can only use firmware or ruu's that match your MiD and CiD. And they must be signed by HTC.
You can only flash a signed ruu or firmware that is the same as your current version or one update above.
So you see the earlier ruu will fail because it's to old and classed as a downgrade. There for can't be flashed with s-on even while relocked.
The latest ruu is lollipop 7.x.502.xx. So to flash it your device must be on at least 6.x.502.xx. Or the flash will fail. As your device is on 4.x.502.x you need the ruu I linked in my earlier instructions or a 5.x.502.xx which to the best of my knowledge does not exist :good: It should work as long ad you Relock your bootloader. Let me know how it goes
Sent from my SM-T230 using Tapatalk

deleted

Danny201281 said:
The problem is because your s-on. The way firmware is flashed is very strict with s-on.
You must Relock the bootloader.
You can only use firmware or ruu's that match your MiD and CiD. And they must be signed by HTC.
You can only flash a signed ruu or firmware that is the same as your current version or one update above.
So you see the earlier ruu will fail because it's to old and classed as a downgrade. There for can't be flashed with s-on even while relocked.
The latest ruu is lollipop 7.x.502.xx. So to flash it your device must be on at least 6.x.502.xx. Or the flash will fail. As your device is on 4.x.502.x you need the ruu I linked in my earlier instructions or a 5.x.502.xx which to the best of my knowledge does not exist :good: It should work as long ad you Relock your bootloader. Let me know how it goes
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
That all makes sense to me and why I was getting two failed RUU's before... One was too old, one was too new. As I type this, I just got a message saying that the ROM update was successful so let's see how it goes from here... Other than that, it had appeared I was following steps for the RUU's perfectly, hence my confusion!
Touch screen ability is back (I knew the old version I was on would cause issues, as warned by htc1guru) and I'm walking through the device setup now... Will update when I get to the OTA process.
Suffice to say, looking good so far and at the very least grateful to be on a DIFFERENT step than I was before!

scirto said:
That all makes sense to me and why I was getting two failed RUU's before... One was too old, one was too new. As I type this, I just got a message saying that the ROM update was successful so let's see how it goes from here... Other than that, it had appeared I was following steps for the RUU's perfectly, hence my confusion!
Touch screen ability is back (I knew the old version I was on would cause issues, as warned by htc1guru) and I'm walking through the device setup now... Will update when I get to the OTA process.
Suffice to say, looking good so far and at the very least grateful to be on a DIFFERENT step than I was before!
Click to expand...
Click to collapse
Good to know. Glad you got it sorted. At least you can start a fresh if nothing else. :good:
Sent from my M7 ARHD 84-Kitkat

Danny201281 said:
Good to know. Glad you got it sorted. At least you can start a fresh if nothing else. :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Exactly... Might be the software developer in me, but I feel a huge sense of relief as long as I start to see something different happening. OTA is downloading, no root is detected, so the process should complete successfully. Major kudos to you, my friend.

So I was able to accept the OTA update to get up to 4.4.2 and software 5.something.something and am currently updating further... At this point, I think I'm comfortable in saying this issue is resolved. Thanks for the help!!!

scirto said:
So I was able to accept the OTA update to get up to 4.4.2 and software 5.something.something and am currently updating further... At this point, I think I'm comfortable in saying this issue is resolved. Thanks for the help!!!
Click to expand...
Click to collapse
Your Welcome. Enjoy
Sent from my SM-T230 using Tapatalk