yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] LTKred:
i didnt know it was possible to backup the other partitions? doesnt a nandroid just backup data/system/recovery/cache etc?

i'm talking about the secure partitions (i'm guessing they're the secure ones anyways lol), the ones only an RUU flashes like the sbl1, sbl2, rpm, tz etc.

and yeah that nandroid backup is for my phone, i already have that downloaded, but i was looking specifically for an RUU because i want to make sure the partition table is completely stock, not just the data, system and recovery ones. :)

cheers
[One (M7) Original Android Development] donmarkoni:
It's possible. Yes, you are right, my apologies. I meant to write it, but I'm multitasking, so it slipped me. :p You need to find someone with backup of those partitions and use it to restore.

Sorry again, but if anything, it's comforting to know that you are of those people who know stuff and read and learn. There is still hope for humankind. :D

Cheers!
[One (M7) Original Android Development] LTKred:
haha thanks yeah, I've read more pages and posts on here than anything else ive read in my life lol. I dont know a lot, but i at least know enough to usually be pretty careful about messing with certain things :D

Hey, about those other partition backups. My brother has the exact same phone as me (we bought them literally on the same day at the same store lol) do you know how i would go about making a complete full backup of all partitions required to return to S-ON? I only know how to do a general nandroid backup :confused:
[One (M7) Original Android Development] donmarkoni:
I'm gonna make a batch file for partition backup, just wait a little... ;)
[One (M7) Original Android Development] skulldreamz:
Nice idea bro, I can't say I remember seeing someone making a system dump batch...
[One (M7) Original Android Development] TabascoJoe:
If I use revone -l will that lock the bootloader, or just make the message disappear? Since I have s-off locking the bootloader should not prevent me from installing roms and recoverys, or do I still need the bootloader unlocked?

I like to have s-off no messages on the boatloader and still full control of the phone
[One (M7) Original Android Development] PillowMetal:
Yes, you can be S-OFF LOCKED and still flash recovery (through fastboot own rebootRUU) and then anything else after that.

Also, revone -l isn't cosmetic, it actually locks the bootloader.
[One (M7) Original Android Development] iElvis:
S-off basically makes all other security meaningless. Your bootloader is "locked" but not really locked, at least not in the sense of being out of the box locked. You can still do pretty much everything, just certain ways of doing it are closed.
[One (M7) Original Android Development] runganwt:
I think I did mention "Everything back to Stock" Do I? And Firmware as well since GE Firmware is 3.06.1700.1 My meaning of "Firmware could be anything" mean you need to go back to other version that lower than 3.06. It's 2.24.401 or 2.24.707 or 1.29 or 1.27 is doesn't matter if you can flash it under SuperCID. If you have 2.24 version, you can tell them that you got OTA (if your country have one unless you need to really go with the same version you phone come with).

Mostly RUU come with Firmware (All drivers), Recovery, Radio, Kernel and ROM.

If you run Nandroid backup to get back to stock, that's mean you run it under Custom Recovery, you need to flash stock recovery unless you can find firmware that have stock recovery and Radio in it. Stock Nandroid should bring back your Kernel and ROM. All should back to stock when you still S-off then you write back your CID/MID

Double check and S-on.
[One (M7) Original Android Development] cschmitt:
I posted one over in the GPe conversion thread a month or so back, to grab a full dump of the first GPe's.

edit: Backup script is attached.
[One (M7) Original Android Development] bullfrog527:
Hi all, I have a sprint htcONE with the 1.44 hBOOT dated July 5. I'm getting error 2 after the ./revone -P step.

What do I need to do next?

Thanks in advance
[One (M7) Original Android Development] Becool0130:
Is it possible to do s-off with Android Revolution GOOGLE EDITION? I keep getting error =1?

Any tips would be greatly appreciated! Thanks
[One (M7) Original Android Development] skulldreamz:
You all who are getting errors stop using a PC/Mac if your new to this. Google how to s-off htc one without PC. You will save yourself a headache and have s-off in 2 minutes. If your 1.44 hboot allows it or you get lucky like me, bit that's a whole nother story

With me I truly think timing had something to do with it is the only thing I can think of like how the wire trick worked with my vivid...
[One (M7) Original Android Development] zounduser:
Right. Lol. I s-off'd mine using terminal emulator, in a matter of minutes. Also removed tampered. :)
[One (M7) Original Android Development] ZeRo2o9:
thanks i appreciate that especially since it seems like my phone came with that ota when i got it and you were in the same boat. thanks
[One (M7) Original Android Development] EtherealRemnant:
Can a dev hit me with a PM - I'm not a programmer but I disassembled Apple's code and figured out how to get the DVD to boot on a regular PC... And I'm a linux kernel hacker...

If someone can rip the hboots and the partitions that are known to affect security, I will do my best to disassemble... There has to be a code somewhere that makes the 1.44 exploit work again (1.54, lets fix 1.44 first)... I don't read things in terms of 1s and 0s but I can decompile as long as someone gives me the public key... HTC has never successfully locked down a Qualcomm chip... In fact, nobody has.
[One (M7) Original Android Development] skulldreamz:
Finally someone has the correct attitude to do something about the issue instead of *****ing and crying like little school girls. Note that he will achieve s-off because he is not a quitter. When someone tells you something can't be done, nod and smile and then go do it or don't stop trying till you conquer it. I'm living proof whether people want to believe me and a few other people or not. I could care less. What I do care about is the fact that I'm s-off now and have fastboot oem writesecureflag 3 so many damn times I can't even count anymore. Good job the real emenent!
[One (M7) Original Android Development] AlbertoSONIC:
Can i flash a RUU with unlocked bootloader and S-Off? Or i need to run ./revone -l before to install RUU?
[One (M7) Original Android Development] skulldreamz:
Yes you can flash without needing to do anything else... ;)
[One (M7) Original Android Development] bullfrog527:
Yea, I'm using terminal emulator on my device. Here's a copy of what I'm doing.

u0_a224@android:/ $ su

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

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

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

revone v0.2.1

revone failed (error code = 2)

2|root@android:/data/local/tmp #

Thanks

I'm thinking my hBOOT is from July 5 and while it's 1.44 it's locked down.
[One (M7) Original Android Development] AlbertoSONIC:
Hey guys, i've a question... I flashed a 1.28 RUU so revone was deleted during Factory Reset... I'm already S-Off and i want to Lock bootloader and return S-On... To do this, do i need to follow the OP totally (also Prepare and S-Off) or i can do this?

1) adb push revone /data/local/tmp/

2) adb shell

3) cd /data/local/tmp

4) chmod 755 revone

5) ./revone -l

6) fastboot oem writesecureflag 3

If yes, do i need to reboot phone after "chmod 755 revone" or not? And to run "fastboot oem writesecureflag 3" do i need to be in fastboot usb?

And the last question... After these steps, bootloader will show S-On and Locked or S-On and Relocked? Thanks in advance
[One (M7) Original Android Development] BenPope:
No reboot required.

Yes, fastboot requires fastboot.

S-on and Locked, all back to stock. You may want to delete revone before step 6, not sure if you can do it after (well, probably can by obtaining temp root with revone!)
[One (M7) Original Android Development] gampt:
Downgrading from 1.27.531.11 to 1.27.531.8 is now possible. Check this out: http://rootzwiki.com/topic/96098-s-offdowngrade-12753111-to-1275318/ I tried it and it works like a charm. I was able to run revone successfully after downgrading.
[One (M7) Original Android Development] justinaz:
If you have a Tmobile HTC One on 1.27.531.11 follow that link and you will be able to get s-off :) made my month!!
[One (M7) Original Android Development] RuckusDecay:
You guys better not be pulling my chain.
[One (M7) Original Android Development] t.o.m.:
Confirmed. This downgrade method does work. Just completed and ran revone with no issues. :laugh::good:
[One (M7) Original Android Development] zounduser:
For everyone getting revone failed..........make sure it reads only "revone" and not revone.bin!! 9/10 times, this is y revone fails.

Good luck
[One (M7) Original Android Development] jrburkh:
The downgrade is only useful if you are on 1.44 hboot, correct? Still no hope for 1.54?
[One (M7) Original Android Development] RuckusDecay:
Its T-Mobile users if you go to that thread and maybe ask nicely he could probably do one for the at&t guys.

---------- Post added at 09:00 PM ---------- Previous post was at 08:51 PM ----------

Guess what!! no more excuses now downgrade dam it. lol j/k man yeah yay finally :D:cool:
[One (M7) Original Android Development] Theshawty:
Oh how I wish for an s-off method for 1.54. *rant* :p
[One (M7) Original Android Development] LTKred:
Thanks man thats great =D does the phone need to be rooted or anything? or just have usb debugging enabled? also once ive pulled all of this from the other handset, how do i put it back onto mine? thanks
[One (M7) Original Android Development] Spartn:
just asked on IRC #revolutionary channel if there is anything new about hboot1.54 for HTC M7, of course i was kicked out, but with the result "no" :(
[One (M7) Original Android Development] irrelephant:
Worked like a charm! #****sAndGiggles :victory:
[One (M7) Original Android Development] EtherealRemnant:
While I am highly appreciative of the downgrade... It is obviously an HTC leak. It wouldn't work if it wasn't signed. S-ON doesn't allow unsigned flashes - and this RUU doesn't have any tricks - it is the software that the phone launched with - signed by HTC. Don't look the gift horse in the mouth...

As for those that are getting the file deleted message using the HTC browser, use Chrome in desktop view - I know some of us use LTE as our sole connection...

Realize though that you are downgrading the radio too. .11 made significant upgrades to radio function - you will have to flash the radio to get the benefits back.

---------- Post added at 05:15 AM ---------- Previous post was at 04:21 AM ----------

One last thing...

DON'T S-ON FOR ANY REASON BUT WARRANTY. YOU CAN CHANGE YOUR CID/MID, AND EVEN GO TO 1.54 - AND DOWNGRADE. Don't be stupid an S-ON. And write down EVERY change you make... Especially your MID and CID... and if you ***HAVE*** to go back to S-ON, if you don't know how to do it properly, ask somebody. Once you are S-OFF, you can seriously mess up your phone. If you go S-ON and you haven't done things in the proper order... you are essentially screwed.

I'm using Helium right now to back up... I'll let you all know how that goes...I have used TiBu since the Hero.

And further - if the latest version doesn't work, use .2.0...
[One (M7) Original Android Development] Jonny:
No downgrade for 1.54 and above because you get signature errors, believe me, this was the first thing I tried when I got the phone - downgrade trick is not new, its just changing the main version in android_info.txt
[One (M7) Original Android Development] EtherealRemnant:
That is false. The bootloader prevents flashing an unsigned image... Without a direct exploit, "android_info.txt" is worthless.

The story changes if you are S-OFF. But you can downgrade from 1.54 to 1.44 with a simple fastboot flash... If you know something that I don't know, please let us all know... because if you are S-ON and you made a "downgrade trick" actually work, there is a pretty serious bounty for anyone who can get 1.54 down to 1.44 - and have the 1.44 be the one dated before July...
[One (M7) Original Android Development] horsetastic:
I concur with the above..... Just pondering...... Wonder if it could be possible to somehow downgrade from 1.54 hboot to the patched 1.44 hboot, then again to the unpatched 1.44.... Though saying that it'll still fail on hboot version check..... if we could somehow find a way to shroud that check..... hmmmmmm
[One (M7) Original Android Development] sjaak1234:
I just got the Japanese HTC One from AU and as they don't allow to unlock the bootloader by using htcdev I want to use Revone. If I use Revone to get S-off, can I just follow any of the other guides to install CWM and load/backup new roms from there?

Btw I noticed that the link in the first post still points to the old file.
[One (M7) Original Android Development] Jonny:
I meant the downgrade trick posted recently on rootzwiki - the only file changed was android_info.txt which had an updated mainversion so that the RUU didn't error. I did a diff between the 2 extracted RUU files and this was all I found different.
[One (M7) Original Android Development] Gerton:
Yes u can
[One (M7) Original Android Development] sjaak1234:
I'm getting some errors

C:\android\platform-tools>adb push revone /data/local/tmp/
3229 KB/s (648208 bytes in 0.196s)

C:\android\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)...[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
[-] Failed to map memory.
251|shell@android:/data/local/tmp $ ./revone -P
./revone -P
revone v0.2.1

revone failed (error code = 2)
2|shell@android:/data/local/tmp $ exit
exit

C:\android\platform-tools>adb push revone /data/local/tmp/
3314 KB/s (648208 bytes in 0.191s)

C:\android\platform-tools>adb shell
root@android:/ # cd /data/local/tmp
cd /data/local/tmp
root@android:/data/local/tmp # chmod 755 revone
chmod 755 revone
root@android:/data/local/tmp # ./revone -P
./revone -P
revone v0.2.1

revone failed (error code = 2)
2|root@android:/data/local/tmp #

I tried both the normal version and the wlj version, same result on both. I time (using the normal 0.2.1 version) I told me success, I wanted to reboot my phone but it seemed to kinda crash and reboot itself. I tried performing step 5 but that didn't work. I don't remember the error as I didn't save it but now I can't even get to the point of getting root successful.
[One (M7) Original Android Development] t.o.m.:
i received the exact same error after I downgraded my TMO M7 from 1.27.531.11 > 1.27.531.8.

After a complete reboot I did the steps again and it was successful first try. Keep trying, my friend.
[One (M7) Original Android Development] zipsnet:
Yuu did a diff -s between the two RUU's hboot files ?? Tell me which RUU ??? and I double check ?

The downgrade http://rootzwiki.com/topic/96098-s-offdowngrade-12753111-to-1275318/ works, If you like you can extract the rom.zip file and flash it by doing:

adb reboot-bootloader

fastboot oem lock

fastboot oem rebootRUU

fastboot flash zip rom.zip

fastboot flash zip rom.zip ( yes it'll ask you to run the command again)

fastboot reboot

adb push revone /data/local/tmp/

adb shell

cd /data/local/tmp

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

revone v0.2.1

Gaining root access (thanks to Dan's motochopper)...Success.

revone successful - please reboot to continue.

exit

adb reboot

adb shell

cd /data/local/tmp

shell@android:/data/local/tmp $ ./revone -s 0 -u

revone v0.2.1

Gaining root access (thanks to Dan's motochopper)...Success.

revone successful.

exit

adb reboot-bootloader

fastboot oem readcid

...

(bootloader) cid: T-MOB010

OKAY [ 0.009s]

finished. total time: 0.009s

fastboot oem writecid HTC__001

...

(bootloader) Start Verify: 0

OKAY [ 0.044s]

finished. total time: 0.045s

fastboot oem readcid

...

(bootloader) cid: HTC__001

OKAY [ 0.009s]

finished. total time: 0.009s

fastboot oem writecid T-MOB010

...

(bootloader) Start Verify: 0

OKAY [ 0.023s]

finished. total time: 0.023s

fastboot oem readcid

...

(bootloader) cid: T-MOB010

OKAY [ 0.009s]

finished. total time: 0.009s

--Z
[One (M7) Original Android Development] EtherealRemnant:
Okay so apparently someone made an edit, to the same version of hboot, and made a RUU that didn't exist which magically fixed everything.

You say you have run diff with two RUUs... Umm... T-Mobile has never had a RUU... Every other carrier had one.

And if you diffed it... than you would know what partition was messing everything up.

Post the two RUUs or STFU because you are giving false hope.

This zip file is signed. That's HUGE... because the wire short trick won't work anymore - the security on the new Snapdragons is pretty much bullet proof... It is actually stronger than the OMAP...

EDIT: Just to let you know how strong the OMAP4's bootloader was, not only did it have to be tricked into running a separate module... but around 50 phones got fried by triggering the bomb... And they STILL haven't figured out how to SIM Unlock over 2 years after the chip was released.
[One (M7) Original Android Development] sumpf2:
is there any downgrade thread for the international modell? i cant find one and i dont want to "try some things" and brick my phone.. :/
[One (M7) Original Android Development] Jonny:
1. Your talking to a moderator, watch your attitude (particularly the STFU bit).

2. I'm not giving anyone false hope, can you not expressly see where I stated that IT DOES NOT WORK for hboots on different versions, it is however, confirmed to be working by users on rootzwiki on the older tmobile base ending in .11 with hboot 1.44 when downgrading from .11 to .8 - the S-OFF exploit was patched in .11 but not in .8 as far as I'm aware.

Now as for the diff, I diffed with the extracted content of a 1.28 RUU - fair enough its not tmobile RUU but the Europe one, I do however know the layouts of RUU's and how they work so even though a few other files were different, I can safely say those differences are not important, the important change was with the android_into.txt file which instead of a main version of .8 which is what you would expect from the .8 RUU, it has a main version of .11 - therefore initially tricking the RUU as the RUU utility cannot decrypt the rom.zip afaik, this would be the logical explanation as to why the lone android_info.txt file is included outside of the rom.zip archive.

Edit: Note I also say the EXTRACTED CONTENT OF THE RUU, not the extracted content of the rom.zip - I do not think the rom.zip has been modified because it still contains the original htc signature and so is impossible to extract anything from it without using the RUU decrypt tool.

Edit 2: Now, I tried this downgrade method some time ago for 2.24.401.1 (it is not knew to me, I saw someone mention it in the DNA forum a while back I think, don't quote me on that though, it might have been a different forum) and I got error 155, which I thought at the time was just an obvious error due to signatures or something else but following the thread in rootzwiki, it might have been because I had an unlocked bootloader. I will backup my internal storage and try again with a locked bootloader.

Edit 3: No, downgrading with locked bootloader does not work either, you get Error 140: Bootloader version error. As I thought, the only reason why the downgrade trick works for the tmobile base is because they already have hboot 1.44
[One (M7) Original Android Development] Jonny:
http://xdaforums.com/showthread.php?t=2375223

Read it and start weeping.
[One (M7) Original Android Development] zipsnet:
[MENTION=4184142]Jonny[/MENTION] sorry but using your status as moderator to make people respect you only remind me when my kid does something wrong or talk back to me and I say "I'm your dad so watch your mouth (which @ that point is ok to point out who is who)" so what i'm trying to say is , attitudes are not welcome period. As a moderator I think your roll would be to Educate the Uneducated, no disrespect intended ..

-Z
[One (M7) Original Android Development] horsetastic:
To be fair I think he was right to give the guy a gentle nudge and of course mentioning he's a moderator in this instance is perfectly acceptable imho. There was no need for the way which the other guy spoke to him and he needed to be warned.
[One (M7) Original Android Development] zipsnet:
so I would be ok for him to talk to me like that cuz im not a moderator and I can't delete his post or ban him from here? sorry, but in my book, Respect should come first before anything !

-Z

(sure we can always agree to disagree) :)
[One (M7) Original Android Development] Syn Ack:
1 million dollars to the person who provides S-Off for VZW HTC One
[One (M7) Original Android Development] runganwt:
Agreed, If you have different idea(s) about something. Just share it like civilized people, do not need to be rude even others may not make you happy :rolleyes:
[One (M7) Original Android Development] horsetastic:
It's not OK for him to speak to anyone like that. I was merely stating that I don't think the mod abused his entitlement in this instance. The guy needed a gentle reminder and I think pointing out that he was a mod was a good move. Seemed to me to be a gentle "Oi! Watch your mouth!" to me.....
[One (M7) Original Android Development] EtherealRemnant:
I'm only apologizing for 1 - not because you're a mod but because you are a mod, didn't infract me, and I feel bad about the STFU...

So where did this come from and what are we going to do? We have a signed zip. HTC changed their signature after the gold card exploits... But with a bit of assembly on the RUU EXEs and a batch diff, can we not find their public key? The private is in the phone.

I am about to S-OFF... .

Do you at least agree with my assessment that 2.0 works right and 2..1 has some severe issues? 2.0 even works in windows 8.
[One (M7) Original Android Development] zipsnet:
I've seen this movie before ... and the guy got killed at the end trying to escape right ? :cowboy:

-Z
[One (M7) Original Android Development] lomo2002:
Hboot 1.44

hi guys,

I am a litte new in the world of android rooting, unlocking and stuff. I just bought a new ONE, as I wanted to update the ONE with 4.2.2 rom, I read in the forum that S-off is only possible for Hboot 1.44. I checked the bootloader, it says 1.44. So, I did not update to 4.2.2.

My question is, if I use the Revone and S-off my phone, can I still get the official OTA update from HTC. Right now, I am not going to play with roms and stuff, but in the future, when HTC stop supporting the HTC ONE, then I thought, if I have S-off, I can use the roms that are made in XDA.
[One (M7) Original Android Development] Jonny:
Yes you can, as long as you are on the stock ROM, you will be able to receive OTA updates from HTC.
[One (M7) Original Android Development] TabascoJoe:
So now that I'm S-Off I can install any current RUU without fear that I will go S-On again.

My understanding is that currently the only way to S-On again is to run a command in fastboot?

Also should I go to 1.54, any advantage to it with s-off?
[One (M7) Original Android Development] Jonny:
Once you are S-OFF, you won't lose it unless you manually reset the secure flag back to S-ON using the fastboot command.
[One (M7) Original Android Development] m1ket:
I wish i had read this thread before accepting the OTA updates on my new phone, no s-off for me for now :mad:
[One (M7) Original Android Development] EtherealRemnant:
Not going to be an issue for long.