yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] bjg222:
Ok, so after many tries, I was able to downgrade to the older HBOOT 1.44 (dated March 15, 2013) using the 1.29.1540.3 RUU, but now I'm running into other issues. When I run ./revone -P, I get the following:

Gaining root access (thanks to Dan's motochopper)...[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
...

I've tried Moonshine as well, which tells me to make sure I'm unlocked via HTCDev.com and try again. However, I am unlocked.

I tried following several different guides for downgrading, one of which suggested modifying the misc partition (blk0p19) to change the version number stored there. This, together with locking the bootloader (which was counterintuitive since it's a dev edition I bought unlocked...), which eventually let me run the RUU to downgrade. Though after one failed RUU attempt, I had to modify it again to break out of the constant RUU mode reboot. Somehow, after all's said and done, I messed up recovery, though, and now I can't ever seem to boot into recovery (tried flashing TWRP & CWM, neither will boot). Don't know if the recovery issue's related to the revone/moonshine not working, but it does mean I can't flash a root zip, so I'm trying this unrooted. (which also means I can't get to the misc partition without root access any more). I have re-unlocked the bootloader with an unlock token from HTC.

Suggestions?
[One (M7) Original Android Development] InfinitiGuy:
Have you used 'fastboot boot' to try to boot a custom recovery?
[One (M7) Original Android Development] horsetastic:
Try rooting the phone then running revone with su permissions.

Edit just read the rest properly. If I where you is download the RUU.zip for 1.29 and move it to adb/fastboot folder then plug phone to comp. Open cmd prompt. CD to the folder you have the RUU.zip in then type,

adb reboot oem-78

Wait for it to boot to RUU mode. Then type,

fastboot flash zip RUU.zip

It'll take a while but I think it's worth doing this again just in case something isn't quite right somewhere.
[One (M7) Original Android Development] BuT_TeR:
i am not able to s-off Hboot 1.44 getting error code -6

T-mobile

current ruu is 1.27.531.11

cant find anything lower than this :(

* cant find anything else than this *
[One (M7) Original Android Development] Theshawty:
.11 is why. You need to downgrade to an earlier release as .11 blocks it from working.
[One (M7) Original Android Development] BuT_TeR:
hm.. thought as much ...

where can i get earlier release ?

:crying:cant find any :( :crying:
[One (M7) Original Android Development] Theshawty:
check the tmo htc one section.
[One (M7) Original Android Development] horsetastic:
Read the guide in my signature.... Has a link to tmob downgrade.
[One (M7) Original Android Development] BuT_TeR:
cant find any :( , can you search please? i downloaded this rom from tmobile section and it has broken wifi and no inbuilt file manager.
[One (M7) Original Android Development] bjg222:
Thanks for all the help, finally got it to S-Off! Manually running the RUU failed, but it somehow allowed running the RUU exe to succeed again, restoring the ability to boot into recovery, so I flashed CWM, rooted, and finally got revone to work and give S-Off. Just to double check, installing the 3.22 update shouldn't revert to S-On, right?
[One (M7) Original Android Development] horsetastic:
Glad i could help... Ans no. Never s-on lol
[One (M7) Original Android Development] bjg222:
Awesome, thanks! :)
[One (M7) Original Android Development] Thela7:
It worked just fine

I wanted to share that I could S-OFF in the first try without any problems.

This was my scenery:

M7_UL AT&T

OpenDSP-v26.120.274.0202

Mar 18 2013

[ro.aa.romver]: [1.29.401.16]

[ro.baseband]: [4A.17.3250.14]

[ro.bootloader]: [1.44.0000]

[ro.build.version.release]: [4.1.2]

[ro.cid]: [CWS__001]

[ro.mid]: [PN0712000]

[ro.product.version]: [TrickDroid 5.6.0] (International Mod)

android-tools-adb: Installed: 4.2.2+git20130529-3 Debian Sid/Unstable 64bits

Thanks for your fine tool, Revolutionary!
[One (M7) Original Android Development] zounduser:
I'm currently having problems with the AT&T HTC ONE of a friend's. Completely stock. 1.44 hboot.

1.29 Rom version. I unlocked the bootloader and rooted the stock Rom through twrp.

I keep getting error code 1

Now.....ive done this on 4 other ONES with no problems at all.

Any thoughts guys? I'm downloading the 1.29 ruu right now. Gonna start over I guess. Sigh.....
[One (M7) Original Android Development] crazynarutoman:
Revone Error Code 1

Revone Error Code: 1

CID: GLOBA001

HBOOT: 1.44

Software Version: 1.29.1500.21

Kernel Version: 3.4.10-gd589381

Output:

C:\android-sdk>adb push revone /data/local/tmp

2714 KB/s (648208 bytes in 0.233s)

C:\android-sdk>adb shell

root@m7:/ # cd /data/local/tmp

cd /data/local/tmp

root@m7:/data/local/tmp # chmod 755 revone

chmod 755 revone

root@m7:/data/local/tmp # su

su

root@m7:/data/local/tmp # ./revone -P

./revone -P

revone v0.2.1

revone failed (error code = 1)

1|root@m7:/data/local/tmp #
[One (M7) Original Android Development] horsetastic:
Who knows, I'd always say (as annoying as it is) that what you're doing, downloading the ruu is probably the best way to go....

Just out of interest what is the date of your bootloader? (reboot to bootloader for date)

If in doubt check out my Pre-S-OFF guide in my signature..... Has most common faults and was around them before you start.
[One (M7) Original Android Development] crazynarutoman:
According to my bootloader, the date is July 23 2013, 23:01:49. After reading your S-OFF Guide, I learned that 4.3 ROMs don't work....however this warning wasn't anywhere on all the other S-OFF forums. Not only that, I'm on GE 4.3 haha. So what ROM should I use? Reverting to stock requires a RUU for your specific cid but I haven't seen one around for mine (GLOBA001).

Thanks for your help man.
[One (M7) Original Android Development] horsetastic:
hmm... OK well July means that your 1.44 bootloader 'could' potentially be patched however you could just be falling over on your ROM so first we'll try this....

Have you updated your firmware at all to newer, for example did you need to update anything else in order to get the 4.3 GE ROM you're running to work on your phone?

If you did then I would try downloading and installing Mike's Stock 2.24.401.8 deodexed ROM.... Then try revone again.

If you didn't change anything then if you can try to install a stock 1.29 ROM..... shouldn't matter which really.... Maybe grab one of the stock nandroid backups from Crushalots RUU collection thread.... Then try revone again...

Hopefully one of these should work :)
[One (M7) Original Android Development] crazynarutoman:
Thanks for this man, I love you and this community. For the GE ROM, flashing firmware was recommended by due to the fact that none of the firmwares fit the cid on my phone, I haven't flashed anything. I'll try the stock ROM and revone right now.

---------- Post added at 10:50 AM ---------- Previous post was at 10:41 AM ----------

I'm not sure how I should flash stock ROM...I can't use the .401 method and there isn't a correct RUU for my phone (Wind Canada, cid: GLOBA001). Trying the third method but dunno..
[One (M7) Original Android Development] horsetastic:
OK I have an idea.....

Download this stock ROM.... I know it's not for your CID or MID however you should be able to open the downloaded zip file and edit android-info.txt to match your phone's details..... Oh and dont chose to install radio or recovery during the install.....

I'll double check this but hopefully it'll work.

Let me know how you get on.
[One (M7) Original Android Development] crazynarutoman:
Alright, downloading. Thanks!
[One (M7) Original Android Development] horsetastic:
dont try flashing it until i've had a chance to check it wont do anything we dont want it to though :)

I'm checking out a few other options too. :)
[One (M7) Original Android Development] crazynarutoman:
Haha I haven't flashed it yet. How do I prevent the installation of the radio or recovery? Heading to bed now, will check in morning. Thank you!
[One (M7) Original Android Development] horsetastic:
OK so I don't think flashing this stock is a good idea.... I'm not 100% on it.... I've had an idea and will sort something out if I can.... Hopefully when you wake up there will be a solution for you on here :)
[One (M7) Original Android Development] AnumEndzeit:
Im in the exact same boat as him and used to get 1 error codes until i also got 6. It wont work for him, as i have tried and i have the exact same software/firmware/cid/mid etc. Ive tried everything in this case and the only viable solution now is to wait for beup to release his new exploit.
[One (M7) Original Android Development] horsetastic:
But have you tried everything? ;)
[One (M7) Original Android Development] AnumEndzeit:
Anything within the realms of success, yes. I even claimed my phone for warranty due to the many times i screwed it up.
[One (M7) Original Android Development] horsetastic:
good effort... Did you try flashing stock dev edition software to your phone, changing misc mainver to match it then running moonshine expoloit for the dev edition version..... Yes CID is different but everything else should match....
[One (M7) Original Android Development] AnumEndzeit:
Yep, moonshine refused to work. That was the moment i had to take it in and switch to another.
[One (M7) Original Android Development] horsetastic:
hmmm interesting..... I would assume that the 1.44 hboot is patched but without an ruu or anything we can't downgrade..... well maybe we can.....

---------- Post added at 11:41 AM ---------- Previous post was at 11:36 AM ----------

did you try the BELL software?

oh nips! I've just noticed something I had missed....

Is your MID PN073000?
[One (M7) Original Android Development] AnumEndzeit:
yessir. And mind you, the firmware version on the phone has to be lower than the RUU that is bieng installed. Seeing as there's nothing higher with an unpatched 1.44, its a dead end :|
[One (M7) Original Android Development] horsetastic:
Sorry PN0713000 I think I meant..... Is that right?

There has to be a way man, has to be.....

As weird as this might sound.... Did you try running the T-Mobile downgrade?
[One (M7) Original Android Development] AnumEndzeit:
Yes and yes. That's the first thing i tried because they're the most similar in terms of RUU's. You also cant downgrade using it seeing as my phone's RUU is x.xxxx.1500.21 and TMO's is x.xxxx.1150.08
[One (M7) Original Android Development] horsetastic:
Ahh actually just looked in to it and of course it wont work because if CID.... the RUU shouldn't matter.... If we could get goldcard working then you would be able to use a tmob ruu.zip file (renamed to PN07IMG.zip) in order to bypass the tmob cid check and flash the firmware. As the MID and Mainver match (or can match if you edit mainver) it could/should work.
[One (M7) Original Android Development] AnumEndzeit:
Wouldn't it check the firmware version first before doing that? Also, I would but don't have a USB y cable. Maybe the guy who originally posted this question could use this little bit of info.
[One (M7) Original Android Development] horsetastic:
well goldcard is meant to (if it works) bypass cid check. and as your hboot and MID etc match if we could bypass CID somehow we'd be on to a winner.... But it's a bit speculative tbh...
[One (M7) Original Android Development] Golv:
GoldCard doesn't work on HTC One!

I did make GoldCard with DesireHD (on DHD - GC - working).

I moved PN07IMG.zip (firmware from 3.09.401.1) in sdcard. I deleted following lines in android-info.txt file (I have s-off and cid HTC__A07):

cidnum: 11111111
cidnum: HTC__A07

Then I tried to flash, but got an error: cid incorrect

When I changed my cid to 11111111 (fastboot oem writecid 11111111) - I was able to flash from card with this same file

without problems

.

Conclusion: GoldCard - doesn't work on HTC ONE...
[One (M7) Original Android Development] Spartn:
my did not work either, seems gold doesn't work on HTC ONE
[One (M7) Original Android Development] horsetastic:
OK good to know. :)
[One (M7) Original Android Development] Spartn:
guys have a look http://xdaforums.com/showthread.php?p=46253056&posted=1#post46253056 :) someone could try if it works on our international devices ;)
[One (M7) Original Android Development] exocetdj:
Anyone tried this yet????
[One (M7) Original Android Development] Guich:
At [MENTION=535343]all[/MENTION], this s-off utility by beaups, will work ONLY on a Verizon Device.

Don't use it! :)
[One (M7) Original Android Development] exocetdj:
ahhhh crap!!!!! :eek:
[One (M7) Original Android Development] horsetastic:
Not for our phones... yet
[One (M7) Original Android Development] Theshawty:
If ever.... :(

>> Sent from the abyss <<
[One (M7) Original Android Development] exocetdj:
f#ck sh#t b#llocks!!!! :crying::crying::crying::crying::crying:
[One (M7) Original Android Development] ossman:
dude, you said you were going to try this on the international version on the other thread... then you kind of vanished... are you bricked?
[One (M7) Original Android Development] sudeki300:
at least it's another step closer.

[MENTION=4366077]exocetdj[/MENTION] that was a classic quote from the iceman. hopefully he'll do well at ferrari next year (fingers crossed) sorry if off topic.............sudeki300
[One (M7) Original Android Development] crazynarutoman:
After reading through all the comments, it looks like there's no hope atm...thanks for trying thought ><" I'll keep checking the threads, hopefully there'll be a workaround soon.
[One (M7) Original Android Development] Spartn:
tested on mine, did not work at all, phone is ok, still working, i did not check whole thread, i was in hurry, i just posted the link, but it§s really disapointing that it works on 1.54 hboot for verzion and we still don§t have soltuion for our international, now it looks like hboot is not a problem....
[One (M7) Original Android Development] Theshawty:
try flashing the verizon firmware and kernel and see if it boots? :P
[One (M7) Original Android Development] EtherealRemnant:
It seems to be kernel dependent. It may very well need the full Verizon software including the kernel to work.

Sent from my HTC One
[One (M7) Original Android Development] Spartn:
do u have flashable rom.zip which could be used as nandroid backup ..cwm or twrp? i would try :)
[One (M7) Original Android Development] Theshawty:
No i don't. Check vzw forums.

>> Sent from the abyss <<
[One (M7) Original Android Development] DeSaint2:
Might be that the partition list is different as well. Sprint has a different partition table then the international.
[One (M7) Original Android Development] horsetastic:
Maybe the kernel will flash and a stock Rom minus firmware could too.... Will see
[One (M7) Original Android Development] EtherealRemnant:
That was my thinking. It is conceivable anyway.

Sent from my HTC One
[One (M7) Original Android Development] horsetastic:
Haha I'm up for anything. I'll have to unlock my bootloader.... Again.... Anyway so if I have to run an RUU.zip to get back from a soft brick then it's not like I'm going to lose anything is it lol....
[One (M7) Original Android Development] hapticc:
Dont worry i think if it will be possible to s-off 1.54 it will be released soon as why would developer negelect huge user base of international htc one
[One (M7) Original Android Development] horsetastic:
Tbh. I think if ours could be done it might have already been so perhaps it's not possible....

Anyway this is OT for this thread now. Should really discuss this is the S-OFF Downgrade etc thread... Link in my Sig. We should keep this thread clean for revone issues etc only.
[One (M7) Original Android Development] Spartn:
tried to flash verizon, stock radio, recovery, boot and it did not work, so something is still there different partition table or kernel.. and verizon s off did not work :(
[One (M7) Original Android Development] electronical:
When i saw this post http://www.xda-developers.com/android/rumrunner-s-off-achieved-on-the-verizon-htc-one/ my heart skipped a beat. I rushed here to see if FINALLY the curse could be lifted off my M7. But it was too good to be true. :(

I'm beginning to think likewise - if it could be done, it would have been done. There are undoubtedly several hundred thousands of international One owners stuck with S-ON. Getting through hboot 1.54 appears to be a really tough programming challenge. Maybe it requires a better and bigger team of developers to get together and have a crack at it. The key is probably understanding what changed from hboot 1.44 and the different layer/s of security in hboot 1.54. This long wait reminds me of the PS3 scene when the latter first launched. I spent 4 long years waiting for the system to be "opened" to developers. Let's hope hboot 1.54 doesn't take that long - a vast majority of us won't be keeping the same smartphone for such a long time! I really hope a solution is found while the One still retains its title of the hottest smartphone of the moment. :fingers-crossed:
[One (M7) Original Android Development] EtherealRemnant:
I don't think we will see anything until 1.55 unfortunately

Sent from my HTC One
[One (M7) Original Android Development] iElvis:
There is no neglect. Don't assume that because there have been no updates that no one was working on it. The reason there's never been a GSM 1.54 s-off method is likely because no one could find a way to do it.

It didn't work because you're s-on, and you can't flash non-stock firmware otherwise.

Flashing verizon firmware on an s-off GSM One would result in a hard brick.
[One (M7) Original Android Development] zounduser:
Ok, I've tried everything. Does this not work on the latest 1.26..15? This sucks big time! Dont know what else I can do. And moonshine will not work either.
[One (M7) Original Android Development] ImagioX1:
Im also having problems. I had hboot 1.44 May build and used revone to s-off my phone. I foolishly locked the bootloader and never flashed a custom recovery or anything. Later on I recieved an ota that upgraded my hboot to 1.44 July build and revone would no longer unlock my bootloader. Kept getting segmentation fault error. So I reflashed the May build of the 1.44 hboot and Im still getting the segmentation fault error. Anyone know how to fix this??
[One (M7) Original Android Development] EtherealRemnant:
Both of you need the RUU to downgrade. AT&T has an official RUU down to .10 (i think that is it) that will restore the original hboot [MENTION=4523921]zounduser[/MENTION] and if it is a T-Mobile version [MENTION=4852379]ImagioX1[/MENTION] (you don't specify and I'm on Tapatalk), search for the .8 downgrade - it's on rootzwiki. You can't touch hboot without S-OFF, it is protected.

Sent from my HTC One
[One (M7) Original Android Development] ImagioX1:
I am s-off and Im on ATT. I have already downgraded my hboot back to the build I orginally s-offed with but revone still will not work..
[One (M7) Original Android Development] EtherealRemnant:
Seg fault is when Motochopper fails. Try su before running revone. If that doesn't work, downgrade your ROM to the stock rooted 4.1.2 ROM and it will work fine. I'm pretty sure it's .9 or .10. You can't S-OFF with 4.3 and most 4.2.2, at least with revone.

Sent from my HTC One
[One (M7) Original Android Development] zounduser:
Ya, I'm wondering y though? The hboot is still 1.44 hmmm....ok. I'll search for it and downgrade on Wednesday when I get my laptop back. Thanks bro. I figured it was due to needing to downgrade, but I figured I was good as long as I didn't have the 1.54 hboot.
[One (M7) Original Android Development] EtherealRemnant:
HTC patched the revone and motochopper exploits but for whatever reason left US devices on 1.44 hboot. I'm guessing because 1.54 is supposed to be 4.2.2 firmware would be a good guess just like 1.55 comes with 4.3.

Sent from my HTC One
[One (M7) Original Android Development] ImagioX1:
My phone is not rooted. I have already ruu-ed down to the March hboot and on the 4.1.2 rom and am still getting segmentation fault error....

Funny thing is it worked the first time. Thats how im s-off
[One (M7) Original Android Development] EtherealRemnant:
This is why everyone says never to S-ON after you S-OFF.

Can you fastboot getvar all and post it here with the serial, IMEI, etc removed? I'm curious if you had changed something when you went S-ON.

Also have you tried a different USB port, hard-rebooted the phone (hold power + volume down until it reboots itself)?

Maybe try Moonshine.

I'm curious what getvar says though.

Sent from my HTC One
[One (M7) Original Android Development] ImagioX1:
As I said before im already s-off. Im trying to unlock my bootloader. I foolishly locked it after I ran revone the first time. I know go ahead and call it stupid cause that's what it was.

(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.1540.3

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

(bootloader) serialno: HT37HW************

(bootloader) imei:

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0712000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 4153mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status read failed (Too many links))
[One (M7) Original Android Development] zounduser:
Makes sense. :) thanks for the replies. I steer away from asking questions, I can usually figure something out on my own. This is a prime example of that. Lol. I'm usually on the other end helping a user out, it's nice to get help for a change. Thank u sir. Will report back Wednesday evening.

---------- Post added at 10:59 PM ---------- Previous post was at 10:52 PM ----------

Also, it should b in the OP that these later software versions are not supported. I know that the 1.54 hboot is correctly addressed, but I spent almost a full day, and then some, trying to s-off. Just a suggestion.
[One (M7) Original Android Development] ImagioX1:
LOL I dont generally ask for help either. THIS though has me totally stumped. RUU and all and I still cant unlock my bootloader. 1.44 hboot too.
[One (M7) Original Android Development] EtherealRemnant:
Everything looks good there. Developer Edition MID and software and all.

Since you're already S-OFF you're just running revone -u right?

No problem. We all need help sometimes. :)

Sent from my HTC One
[One (M7) Original Android Development] PillowMetal:
If you are S-OFF, what is it that you need the bootloader unlocked for - you can do anything you want with a locked bootloader when S-OFF.

But if you really do want an unlocked bootloader, what is the date on your 1.44 hboot. It should May 8th or earlier or revone will not be able to work with it. I haven't been following your issues, but did you RUU to get to where you are, because the CID is 11111111. Not sure if revone has a problem with that too. When I first used revone I was as close to stock as possible (and unrooted and locked).
[One (M7) Original Android Development] ImagioX1:
C:\Users\Jlee\Downloads\adt-bundle-windows-x86_64-20130219\adt-bundle-windows-x8

6_64-20130219\sdk\platform-tools>adb shell

shell@android:/ $ cd /data/local/tmp

cd /data/local/tmp

shell@android:/data/local/tmp $ chmod 755 revone

chmod 755 revone

shell@android:/data/local/tmp $ ./revone -P

./revone -P

revone v0.2.1

Gaining root access (thanks to Dan's motochopper)...Segmentation fault (core dum

ped)

139|shell@android:/data/local/tmp $ ./revone -u

./revone -u

revone v0.2.1

Gaining root access (thanks to Dan's motochopper)...Segmentation fault (core dum

ped)

139|shell@android:/data/local/tmp $

[MENTION=2857827]PillowMetal[/MENTION] you cannot flash custom recoveries if you're s-off with a locked bootloader. Also it doesn't work even with the stock cid. My hboot version is March 1.44