yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] iElvis:
You're correct about regawmod, but there is another way to do it that I saw posted somewhere that would truly relock you, with LOCKED. I can't remember where I saw it, however.

Not that I suggest anyone try it to see, but I've been told (by devs who should know) that you can't go back to s-on via fastboot with a modded hboot. The writesecureflag 3 command runs the same signature check you get at boot with s-on. If it fails, the command doesn't work. I know of at least one person who found this out by accident after trying to go back s-on having forgotten he had a modded hboot.

That being said, one should never go back to s-on unless the phone has been restored to out-of-the-box stock--there are good reasons for this apart from modded hboots.
[One (M7) Original Android Development] Golv:
We can't upgrade PN07IMG from internal card (I tested it), I meant to update with external card connected via usb Y cable. A power supply can be interrupted by pressing and holding power button for 15-17 seconds. As soon as phone starts to reboot, we can run script from computer and flashed through adb. Something like this ...
[One (M7) Original Android Development] iElvis:
I thought of that, actually, but here's the problem with using press-and-hold in place of a battery pull:

I suppose it's worth a shot, but it doesn't seem like you could time it right.
[One (M7) Original Android Development] EtherealRemnant:
I don't hold high regard for this being successful at anything other than bricking phones. It is an interesting theory though. The bootloader freezes if the cable gets disconnected... I had my cable get disconnected on accident one time and hboot froze and I thought I just killed it... It unfroze as soon as I reconnected the cable and I just restarted my fastboot flash.

If HBOOT is loaded into RAM, it is conceivable that HTC has fixed it so that the bootloader freezes if the cable is disconnected rather than restarting the phone - thus preventing a brick AND an eMMC reset.

It could of course be a total fluke that my bootloader froze and resumed though - I don't feel like testing the theory as I quite like my phone.

Sent from my HTC One
[One (M7) Original Android Development] iElvis:
Given how meticulous HTC is about patching these vulnerabilities, this seems like a possibility.

As I keep saying when I stick my head in here, the solution is almost certainly going to be a new exploit, not retreads of old, obvious ones. :D
[One (M7) Original Android Development] EtherealRemnant:
I agree. Unless they slipped up and threw us a bone with the 1.55 hboot. It has happened before. My Inspire I believe?

Sent from my HTC One
[One (M7) Original Android Development] iElvis:
Well, someone had better try it before they see this and fix it. :cool:
[One (M7) Original Android Development] EtherealRemnant:
The War Horse volunteered to try it. We will see.

HTC's developers like to play games with us. It's like a sick sadistic pleasure they enjoy. :P

Sent from my HTC One
[One (M7) Original Android Development] zaphodbeeb:
That works for me because its exactly what I did. I used the RUU to get to 1.44 stock and immediately used writesecure flag 3.so my phone was in "of the box condition" when I did it. Luckily.

I dont think resetting the status to locked is a problem on any boot as far as I can see if you have used revone to s-off, even 1.54. Although I confess I havnt tried it on anything other than 1.44 and 1.54.

Also now I think of it, when I got my phone back from fonefunshop it had also been locked, as well as s-off and super cidded. They didnt do the RUU thing to downgrade the bootloader, rom etc so it must have been locked as a result of their s-off process. It was strange because the device had the same custom rom (and apps), recovery on it as before I sent it.
[One (M7) Original Android Development] skulldreamz:
You can't turn the security flag back on, on a modded hboot. Fastboot oem writesecureflag 3 gives you a success if you are on a stock hboot and if you type the same command on a modded hboot it just fails to write a different hboot which in turn will not brick your phone because the process will not go through in the first place
[One (M7) Original Android Development] horsetastic:
Maybe as it froze there is hope..... If you held the power button down after pulling the y cable it might soft brick on boot. Then you could run an RUU 1.29 of course with old hboot... If the bricking worked and hboot was half written and corrupted it could work.

I'll be updating later on today..... Will let you all know how it goes lol

sent by homing Dragon.....
[One (M7) Original Android Development] AnumEndzeit:
I think you're on to something... Maybe if we held on to the power button at the beginning of boot and waited just before update. Within 10 seconds after holding the power button we press vol up to update and BOOM, no power. Continue with rest of procedure.
[One (M7) Original Android Development] EtherealRemnant:
I would think HTC would have accounted for that one too though. We can't do a battery pull anymore and all they would have to do is freeze hboot and simultaneously overwrite the corrupt hboot with the one in RAM. Ridiculously easy thing to program to be honest, especially given that you have to hold down the power and volume down button for what, 10 seconds before it reboots? That is 8 seconds more than it would take to dump the RAM image to the eMMC and verify it's integrity.

Sent from my HTC One

---------- Post added at 07:27 PM ---------- Previous post was at 07:23 PM ----------

That actually sounds somewhat plausible with perfect timing.

Sent from my HTC One
[One (M7) Original Android Development] AnumEndzeit:
Thing is, it asks you (when you update from y usb cable) to press vol up to start update. It takes 12 11 sec for you to press and hold power to force shut off the phone. Now, do the math. You need to shut it off at the 5 sec mark after the update. So press and hold power, count to 7 6, start update at that mark, count to 5 and it shuts off. So its not only plausible but very realistic.

EDIT: It actually takes 11 seconds. I just tried it with a timer.
[One (M7) Original Android Development] EtherealRemnant:
Provided that it doesn't hard brick, I completely agree.

Sent from my HTC One
[One (M7) Original Android Development] AnumEndzeit:
Now, we need a person with a y usb cable and an expendable Htc One! :D
[One (M7) Original Android Development] SaHiLzZ:
Gentlemen, hoping someone can chime into this issue: http://xdaforums.com/showthread.php?t=2406407

Javacard is not an option here in North America. (unless you know about someone doing it, kindly let me know).

Just to note that I am unable to use the touch screen, or unlock the bootloader for an unknown reason so far.

But the phone turns on, and goes to a GE edition rom I believe with debugging turned on.

However CID & MID mismatch is creating an issue.

Any thoughts if that gold card idea is still valid? I bought a USB OTG cable, and thinking if I can somehow use that. Looking forward to any thoughts!
[One (M7) Original Android Development] skulldreamz:
I was in that situation a while ago. Its good you have a otg cable because you can use a wireless mouse to control your phone and s-off using terminal emulator. Attach the little USB male end that comes in the package with the wireless mouse to the otg cable & and plug it in your phone and use the mouse to control your phone. Will take a little longer but at least you can s-off using terminal emulator app and flash a ruu.zip. You should flash 1.26.502.12 ruu.zip because I can tell you from experience that works well with moonshine & revone. You can search YouTube how to soff HTC one without PC. Good luck ;)
[One (M7) Original Android Development] SaHiLzZ:
No luck with terminal emulator, as the phone is bootloader locked and not rooted, can't do su, that fails. Also both es file explorer and term emulator fails to find the folder /data/local/tmp

I have been trying revone s-off as moonshine needs the device to be bootloader unlocked, which I don't have. It is on 1.29.666.5 software, so going to do a OTA to 1.29.666.17, see how it goes.

Depending on how it goes perhaps I should do the OTA to 4.3, which is now available on bell devices?

---------- Post added at 01:33 AM ---------- Previous post was at 01:03 AM ----------

After update:

INFOversion: 0.5

INFOversion-bootloader: 1.44.0000

INFOversion-baseband: 4A.18.3263.15

INFOversion-main: 1.29.666.17

INFOversion-misc: PVT SHIP S-ON

INFOproduct: m7_ul

INFOplatform: HBOOT-8064

INFOmodelid: PN0712000

INFOcidnum: BM___001

---no dice with revone though.
[One (M7) Original Android Development] horsetastic:
Read the guide in my signature. This is my best advice

sent by homing Dragon.....

---------- Post added at 07:09 AM ---------- Previous post was at 07:07 AM ----------

I don't have either of these however if I had a y-cable is try it anyway lol.... I'm pretty sure you wouldn't hard brick and could more than likely recover using an RUU or similar...

sent by homing Dragon.....
[One (M7) Original Android Development] EtherealRemnant:
How would it not have the potential to brick if you reboot and have a corrupt hboot? Over the years of owning HTC devices, the most common theme in bricking is screwing up hboot somehow. Well that and shorting out the phone but luckily I have never had to do that.

Sent from my HTC One
[One (M7) Original Android Development] horsetastic:
Well of course it has the potential to brick..... But I don't think it's as risky as it seems. I well want to risk my phone lol..... Worst comes to worst I'll flush the phone down the loo and claim on my contents insurance lol

sent by homing Dragon.....
[One (M7) Original Android Development] Spartn:
hmm, this will not work as we got error saying hboot is older version - i believe we will not get to that screen with all these numbers until there is a RUU with hboot 1.54 or something what works and doesn't fail on checking phase

this is first time i have seen this screen and i;ve tried to use many RUU renamed to PN07IMG.ZIP and copied to gold, it did not get to that status

i think the person who did that picture has PN07IMG from dev RUU which matches all conditions, hboot, modelid etc, so no problem to get that status asking if he wants to start update

EDIT: just checked the picture again, the person who did that picture is S-OFF, we S ON have no way to get there (asking to start update) because of many checking, and hboot is worse here ;) and no point to unplug power cord in phase of checking ;) one more thing, right after the phone has transfered the zip from goldcard to the phone, (after loading PN07..zip file) my card reader light goes off, so i think the phone does not use the power cord after that phase, i think it does copy the zip file from card to the phone and the rest goes from there without sd, power and y cable
[One (M7) Original Android Development] kansu_makugen:
Worked fine. Fortunately I made a backup of the device's stock ROM so I could return to stock, S-off and go back to custom.

Thanks a lot!
[One (M7) Original Android Development] horsetastic:
No no you misunderstand I think. We can use a signed firmware with 1.54 hboot inside, rename to PN07IMG.zip and it should work. The hboot needs to start writing then we stop it half way causing it to be corrupt. Then we can use the tool swapping the hboot and misc images inside to ours and downgrade hboot.

sent by homing Dragon.....

---------- Post added at 09:21 AM ---------- Previous post was at 09:09 AM ----------

Oh yeh. May be an issue with me taking the 1.55 plunge. With PM0710000 HTC__001 S-ON device I don't think I can even update it yet.... Unless anyone knows a way?

sent by homing Dragon.....

---------- Post added at 10:14 AM ---------- Previous post was at 09:21 AM ----------

Ok so I decided to start a thread specifically for us trying to find a way round the hboot stuff. Lets leave this thread for troubleshooting and issues relating to revone....

Discussion thread is Located Here!

sent by homing Dragon.....
[One (M7) Original Android Development] HeavyMetalHighVoltage:
It worked perfect for me on the first try with no issues at all. Thank you so much for this guide!!!!
[One (M7) Original Android Development] SaHiLzZ:
Thanks, I did read it, it is quite informative. As this device got into state before 1.54 came out, it is unlikely to be effected by it, also only ATT & TMobile devices got the patched 1.44 HBOOT update, not Canadian ones.

One thing to note is that phone displays GOOGLE when it start to boot up, not HTC, then it shows HTC quitely brilliant screen. Somehow I think it is the GE HBOOT, not HTC HBOOT?

Is that possible?
[One (M7) Original Android Development] horsetastic:
If you flashed GE software then you may just have the GE splash screen somehow. Unless you flashed a GE firmware somehow?

sent by homing Dragon.....
[One (M7) Original Android Development] SaHiLzZ:
Got no idea, bought it like that, screen not working and bootloader locked. Initially the main version was .401., implying a EU based RUU was ran at some point of time. Doesn't explain the Google splash screen though.
[One (M7) Original Android Development] horsetastic:
I think what's happened here is you've bought a phone that's been returned by someone who had s-off and just returned it to stock but missed the splash screen.

sent by homing Dragon.....
[One (M7) Original Android Development] SaHiLzZ:
Possibly, but doesn't explain why revone continues to fail with error code 6.. I have been able to unlock the screen using OTG Mouse..
[One (M7) Original Android Development] horsetastic:
If I were you I'd check my CID MID and Mainver and then download the correct RUU.zip or RUU.exe for my exact phone. A 1.29 RUU. Run it and ensure my software is all what it's meant to be. Revone will work then.

sent by homing Dragon.....
[One (M7) Original Android Development] SaHiLzZ:
Unfortunately no RUU or .zip available for .666.x. =) But thanks for the support.
[One (M7) Original Android Development] iElvis:
You bought it used? I'm willing to bet I know what you got: A phone someone converted to GE, then decided to sell but didn't return to stock configuration correctly before reverting to s-on. I've seen a number of people do this and screw up their phones because they didn't know what they were doing or didn't follow the instructions correctly. Your problems are most likely due to mixed up firmware and MID conflicts (which is also likely why revone is failing).

If you have a nonstandard CID/MID configuration + s-on, there may be no way to fix it, unfortunately, at least until you can find an s-off exploit.
[One (M7) Original Android Development] horsetastic:
Just noticed your mainver is showing as 1.29.401.12.... Is this the case? If so you need to do this.

Be rooted first.

Download android terminal emulator if you haven't got it already.

Download Hex Editor too

Open terminal emulator and type..

su

Then type

dd if=dev/block/mmcblk0p19 of=sdcard/misc.img

Open misc.img in hex editor. Edit the number from 1.29.401.12 to 1.29.666.5

Make sure you add an extra dot to the end of the number in place of the 2. But bot a typed dot. It should match the code of the other dots. (hope this makes sense)

And before anyone tells you that you can use a tool to write new misc version it won't work properly because the version number you have is too long.

Save the misc.img

Go to terminal and type

dd if=sdcard/misc.img of=dec/block/mmcblk0p19

Then reboot to bootloader and it should show 1.29.666.5 mainver.

Now try running the ota update again. It should work.

You don't need a locked bootloader for ota to work.... Just stock recovery etc
[One (M7) Original Android Development] SaHiLzZ:
I updated it already, after OTA update:

INFOversion: 0.5

INFOversion-bootloader: 1.44.0000

INFOversion-baseband: 4A.18.3263.15

INFOversion-main: 1.29.666.17

INFOversion-misc: PVT SHIP S-ON

INFOproduct: m7_ul

INFOplatform: HBOOT-8064

INFOmodelid: PN0712000

INFOcidnum: BM___001

---no dice with revone though.

http://xdaforums.com/showthread.php?t=2406407
[One (M7) Original Android Development] horsetastic:
I see.... Have you run revone with root permissions?

su

./revone -P

?

Otherwise just try and try again.
[One (M7) Original Android Development] SaHiLzZ:
No, the device is not rooted, and i can't unlock the bootloader to root it, because the Unlock bootloader for Yes/No screen doesn't show up for some reason. Attributing it to the same touch screen issue.
[One (M7) Original Android Development] horsetastic:
Oh.... This isn't good news.... Is there a firmware.zip you could flash? You need to fix your bootloader issue....
[One (M7) Original Android Development] iElvis:
He can only flash signed firmware, and with his MID/CID problems, that will cause the flash to fail.
[One (M7) Original Android Development] EtherealRemnant:
Since revone is managing to gain root couldn't he just download and run motochopper to obtain root? Revone may still fail but it would allow an attempt with su as The War Horse suggested.

Sent from my HTC One
[One (M7) Original Android Development] Flasher8:
guys,

refer below info :

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.54.0000

(bootloader) version-baseband: 4A.18.3263.15

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 3.17.401.2

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: HT353W901269

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0714000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 4308mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-d16dc66985

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

can i downgrade to my original build which is Asia_WWE_1.29.707.3 for warranty purposed ? Currently i'm using latest insert coin rom, would like to lock my bootloader and s-on back for warranty, is it possible ?

any guide would appreciated.
[One (M7) Original Android Development] iElvis:
You're s-off; you can flash whatever you want.

But I strongly recommend not going back to s-on. First, it's not necessary since some units ship s-off, so it doesn't mean you modded your phone. Second, they are likely to upgrade you and leave you unable to get s-off when you get it back.
[One (M7) Original Android Development] EtherealRemnant:
Change CID back to your original CID, restore stock recovery, flash stock RUU or a stock non-rooted ROM. Leave S-OFF alone and lock the bootloader with revone.

Sent from my HTC One
[One (M7) Original Android Development] SaHiLzZ:
I can try motochopper, sure, but:

Motochopper failure:
[One (M7) Original Android Development] EtherealRemnant:
Damn. Well it was worth a try. I figured it was rooting since it wasn't showing a seg fault.

Have you tried the .2.0 version of revone? I had better luck with it than 0.2.1
[One (M7) Original Android Development] SaHiLzZ:
When i run the 0.2 first linked in OP, it says 0.2.1. Anyone has it?
[One (M7) Original Android Development] EtherealRemnant:
I might. I will have to look through my computer later.

Sent from my HTC One
[One (M7) Original Android Development] iElvis:
I thought they took it down.
[One (M7) Original Android Development] horsetastic:
Post 2 mate
[One (M7) Original Android Development] Golv:
You can try Kingo Android root .

It's work without unlocking bootloader.
[One (M7) Original Android Development] SaHiLzZ:
Yes, and it says 0.2.1 when I run it.

Tried, no go.. =(
[One (M7) Original Android Development] horsetastic:
That's right. You need to rename the file to revone
[One (M7) Original Android Development] EtherealRemnant:
No, they are both links to .2.1

I am searching my computer for the .2.0 binary right now.

Sent from my HTC One
[One (M7) Original Android Development] horsetastic:
You don't want 2.0 anyway. It's not as accurate as 2.1....
[One (M7) Original Android Development] EtherealRemnant:
It worked better for me than .2.1 did. I kept on getting -1 with 2.1 and 2.0 went first try. I'm just grasping at straws trying to help recover that seriously jacked up phone that's all.

Sent from my HTC One
[One (M7) Original Android Development] SaHiLzZ:
And I appreciate that greatly. I had given up on it until recently saw the chatter about goldcard, thought it may help, but apparently not..
[One (M7) Original Android Development] EtherealRemnant:
Goldcard would at least let you bypass CID checks and flash a full RUU.

I'm assuming you already tried the BM OTA zip to see if it would fix the hboot issue. If there was a BM RUU it would be an easy fix since your MID and CID match a BM One.

Sent from my HTC One
[One (M7) Original Android Development] horsetastic:
2.0 gives false positives so might have just seemed to work better...

I have no idea how we can help this chap.... But there has to be a way.

There has to be a way to recover bootloader......
[One (M7) Original Android Development] EtherealRemnant:
Well it succeeded in S-OFF the first run when I went through the .11 to .8 downgrade procedure while 0.2.1 kept failing.

Unfortunately, all of the copies I have appear to be 0.2.1 (I didn't do it with this laptop the second time) but it was a long shot anyway..
[One (M7) Original Android Development] SaHiLzZ:
After bell OTA update: . all numbers look code, mid cid match as well

INFOversion: 0.5

INFOversion-bootloader: 1.44.0000

INFOversion-baseband: 4A.18.3263.15

INFOversion-main: 1.29.666.17

INFOversion-misc: PVT SHIP S-ON

INFOproduct: m7_ul

INFOplatform: HBOOT-8064

INFOmodelid: PN0712000

INFOcidnum: BM___001
[One (M7) Original Android Development] EtherealRemnant:
I think you're stuck until if/when a RUU comes out. I was going to suggest trying to flash the signed zip but I doubt it would make any real difference.
[One (M7) Original Android Development] horsetastic:
Ok so here's revone.bin and revone 2.0 as well as 1.29.666.5 firmware.zip.... Least I hope it is. Can't check on my phone so if someone could check it I would be greatful. Try to flash the firmware.zip by using adb command adb reboot oem-78 to reboot directly to RUU mode then fastboot flash zip firmware.zip (of course you need the firmware.zip in the same folder as your adb files etc)

Hope this works man.

revone.bin

revone-2.0

firmware
[One (M7) Original Android Development] EtherealRemnant:
Is that a signed firmware image or is this just hinging on revone 2.0 working?
[One (M7) Original Android Development] horsetastic:
No it's a signed firmware.zip :) that's why I can't check it on my phone.... Can't open it lol
[One (M7) Original Android Development] EtherealRemnant:
Well that would certainly fix the problem lol. I went looking for that earlier and didn't find it.
[One (M7) Original Android Development] horsetastic:
I'm assuming it's the right one. And of course hopefully it will flash OK.... If it does then fingers crossed we can fix this ****ed up phone!
[One (M7) Original Android Development] Theshawty:
I just thought of something. When and if 4.3 drops.. you think I could flash the European firmware? I don't know what actually differs the European version and the Nordic version, lol, and it seems the Eurpean firmwares thus far have the HTC__Y13 (Nordic) CID in the android info txt.
[One (M7) Original Android Development] :
Does it matter if I forgot to do the chmod 755 revone? I have s off successfully.
[One (M7) Original Android Development] KillerBeaver:
Has anyone tried a similar method to what was used in this thread for downgrading HBOOT by corrupting the HBOOT during an RUU for the same version? I didn't see it listed in The War Horse's Thread abou previously tried downgrade methods.