yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] EtherealRemnant:
From my suggested "Naked Driver" which I personally use in lieu of any SDK, HTC, or other drivers without issue - even on Windows 8 64-bit.

"Universal Naked Driver 0.72

** HTC One Added (HTC phones are pretty much future proof with my driver)

** Google Nexus 4 Added

** Google Nexus 10 Added

** Google Nexus Q Added

** Google Nexus S Added

32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!

MD5: 30D25BC073F010CA01178CD6E2C5E4FA

I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?"
[One (M7) Original Android Development] ne[m]o:
I can't seem to install the drivers.

following:

http://xdaforums.com/showthread.php?t=2139767

after removing my htc drivers. it doesn't display the HTC one on my adb interface devices.

Also as you can tell on my shell it doesn't seem to detect my phone when I type in adb devices
[One (M7) Original Android Development] EtherealRemnant:
You didn't click "Have Disk" and browse to the driver folder from the look of it.

Go ahead and reinstall the HTC drivers if you would like to but use the driver only package - http://www.mediafire.com/download/eqrqb44r3ot18g1/HTCDriver_4.2.0.001.exe

Remember to unplug your phone before installing them...
[One (M7) Original Android Development] ne[m]o:
Hey thanks for still being here. Greatly appreciate it.

I uninstalled all drivers prior. There was only HTC driver installer, and HTC sync manager on the program list. no SDK or anything else listed. After uninstalling those two programs, I unplugged the phone and installed the HTC driver from you link provided.

Plugged in the phone (it is in hboot screen). Computer detected it and the bubble that said searching for drivers popped up. It then said drivers installed and called it My HTC.

I opened up adb and typed adb devices and still won't list it for some reason. I need it to detect my device if I want to push the nandroid file right?

Thank again man. and everyone else.
[One (M7) Original Android Development] zounduser:
Which ruu do i need to downgrade to? Htc one att version. Thanks
[One (M7) Original Android Development] EtherealRemnant:
adb won't work in hboot. Go into CWM and you should see it installing drivers again.
[One (M7) Original Android Development] ne[m]o:
you are right. booted into recovery. it installed drivers again.

typed in adb devices. it detects it. Should I do the push now?
[One (M7) Original Android Development] EtherealRemnant:
Yep, push it on through and then restore it! :)

---------- Post added at 08:50 PM ---------- Previous post was at 08:47 PM ----------

Should be this guy. http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
[One (M7) Original Android Development] ne[m]o:
It says fail to copy. Refer to picture. Why is that? Am I mis typing something wrong?
[One (M7) Original Android Development] mugetsu666:
Great job, just s-off my tmobile us One. I'm s-off locked & no more tampered!

Team-Noctural.com /androidtechy.com /droidnow.com
[One (M7) Original Android Development] :No-Frost::
Is there a way now to remove the red text wen turning on the device??.
[One (M7) Original Android Development] dirtbikerr450:
Not yet soon though
[One (M7) Original Android Development] fatrix1:
I just got s-off without a computer. I only used rootexplorer and terminal emulator in my phone.
[One (M7) Original Android Development] Adolfopacheco:
Is everyone one the Dev Edition having problems when changing the CID to 1s?
[One (M7) Original Android Development] motumbo:
Worked at first try using terminal emulator on my AT&T HTC one. Not even need to use my laptop! Thanks a lot guys.
[One (M7) Original Android Development] ThePhoneGeek:
Someone earlier was having problems with it so I left mine as BS_US001.

MG
[One (M7) Original Android Development] Skizzy034:
S-Off achieved AT&T One 32GB - cid 11111111

Thank you so much for this!! Worked like a charm!
[One (M7) Original Android Development] letmeputdatipin:
Any chance we can get SIM unlocked? I know the moonshine ver. S-off has SIM unlocked! Just wondering since I've already used revone for s-off.
[One (M7) Original Android Development] Skizzy034:
Anyone try it on the DNA yet? My buddy has a DNA with the 2.06 software so he can't unlock. Hopefully this works for it.

EDIT: Moonshine is out already for the DNA?!

It's out for the One too

LMAO looks like I'm a little late.
[One (M7) Original Android Development] il Duce:
From terminal emulator

I'm s-off

Amazeballs

Thanks y'all

I'll send some money when I get to a pc

Lmfao that was killer!
[One (M7) Original Android Development] wzu7:
now i unlocked + s-off ..

do we still need to change CID (current is HTC_044) ?

what happen if not make changes to it ? pls advise
[One (M7) Original Android Development] bricky23:
This....I have s-off, should I relock the bootloader, or leave it unlocked?
[One (M7) Original Android Development] descenpet:
i'd say leave it unlocked

---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------

cid change is not necessary unless you want to flash other region's RUU/firmware.
[One (M7) Original Android Development] MotoXoom:
Perfect

......even in early stages a complete success on try #1 :)

S-OFF, unlocked, not tampered :)
[One (M7) Original Android Development] ArmedandDangerous:
Been getting this error, not sure what to do next

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.
Success.
revone failed (error code = 2
[One (M7) Original Android Development] poczynek:
Try using Terminal Emulator on your phone.
[One (M7) Original Android Development] billyho7993:
can someone help me please when i try to adb push the revone file it is telling me error: cannot find device i dont know what im doing wrong. i have the drivers installed and the computer reads my phone so im at a loss any help would be appreciated thanks
[One (M7) Original Android Development] david279:
Reboot phone and computer
[One (M7) Original Android Development] scotty1223:
Man you terminal emulator guys are hardcore :D kudos for making it work
[One (M7) Original Android Development] zounduser:
Thanks, but does it have to b a specific RUU? I have the first one that was released. So, lock bootloader, and just run the RUU, correct? Thanks again buddy.
[One (M7) Original Android Development] koax88:
did u put the file in the fastboot folder?push only can detect the file in the folder i think
[One (M7) Original Android Development] EtherealRemnant:
As long as you have the stock RUU, just relock and flash - then you're set.

Sent from my HTC One now Free
[One (M7) Original Android Development] zounduser:
Sweet. Thank u sir.
[One (M7) Original Android Development] ne[m]o:
I definitely have the right folder. It's the same folder I put the firmware.zip in and that pushed right through.

See attached picture. I tried different variations. without .zip with .zip and so forth.
[One (M7) Original Android Development] EtherealRemnant:
Give me a minute... I'm going to test this on mine. I just did a fast download of the ZIP and I'm going to see if I can make the magic happen... brb

---------- Post added at 09:24 PM ---------- Previous post was at 09:20 PM ----------

Out of curiosity... try rogerbackup.zip.zip
[One (M7) Original Android Development] ne[m]o:
rogerbackup.zip.zip

returns:

No such file or directory

every other failure before returns:

/sdcard/0/.... is a directory
[One (M7) Original Android Development] EtherealRemnant:
Well the failure is because of the slash on the end. However, something is still amiss... give me a few.

---------- Post added at 09:35 PM ---------- Previous post was at 09:32 PM ----------

take out the 0. It writes to /sdcard/clockworkmod.

So type adb push rogerbackup.zip /sdcard/clockworkmod/backup/rogerbackup.zip and it should push it to the backup folder.
[One (M7) Original Android Development] ne[m]o:
Trying that now. Stay tuned. Thanks for everything so far. I really hope it will recover from this nandroid.
[One (M7) Original Android Development] EtherealRemnant:
I'm hoping so too. I had to run a backup while I was in adb shell to find out where CWM was saving the files. I am curious if it is going to work with a zip file though. CWM backups are stored in folders with individual tar files in them - it is no biggie if you have to extract the zip though, I know how to do that through an adb shell.
[One (M7) Original Android Development] ne[m]o:
Okay it pushed through. went to backup and restore, clicked on restore from /sdcard returned: no files found

I know if I look into my sdcard via install zip from sdcard. there is 0 folder first. /sdcard/0/clockworkmod

I'll try pushing it through there and see what happens.

Yeah I always throught that restores were from individual files not the zip.
[One (M7) Original Android Development] EtherealRemnant:
Trust me, CWM is not putting it in the emulated folder, I just did it.

adb shell

cd /sdcard/clockworkmod/backup

mkdir 2013-06-03.23.51.18

unzip -d 2013-06-03.23.51.18 rogerbackup.zip

on the phone restore the nandroid.
[One (M7) Original Android Development] ne[m]o:
okay. than why can't it detect my nandroid when I click backup and restore -> restore from /sdcard

edit: refer to screen shot
[One (M7) Original Android Development] EtherealRemnant:
Follow the instructions I just gave you to unzip the folder. It doesn't recognize zip files.
[One (M7) Original Android Development] ne[m]o:
I typed everything you wrote. The screen shot shoes what it returns.
[One (M7) Original Android Development] EtherealRemnant:
Here is where it saved my backup I initiated (which is still going - now I remember why I hated CWM so much) and not that /data/media is the same as /sdcard
[One (M7) Original Android Development] EtherealRemnant:
See if it shows up and will restore... I'm slightly worried you might have a corrupt download from the error.
[One (M7) Original Android Development] ne[m]o:
it sees it but, md5 error.

Should I redownload it? it will take 1.5hrs. Internet here in Canada isn't the best.

gives me unzip: crc error

edit: refer to screenshot for error
[One (M7) Original Android Development] EtherealRemnant:
Go to www.winmd5.com and download WinMD5, you can run it right from the zip. Put the nandroid zip in there and get its MD5 - it should match this: 1af173ca5f55c7501ef4089694f7f967

If it doesn't, you will have to download the file again.

If it does, you will have to push it again.

adb shell

cd /sdcard/clockworkmod/backup

rm -rf *

exit

adb push rogerbackup.zip /sdcard/clockworkmod/backup/rogerbackup.zip

adb shell

cd /sdcard/clockworkmod/backup

mkdir 2013-06-03.23.51.18

unzip -d 2013-06-03.23.51.18 rogerbackup.zip

if it corrupts on the transfer again, use a different USB port.
[One (M7) Original Android Development] ne[m]o:
The md5 matches and is the same

when I type in mkdir... it says file exist

so I try to unzip it it says it can't open rogerbackup.zip [.zip]

I attached the screenshot so you can see what I typed in. I don't know much about adb as you can tell.
[One (M7) Original Android Development] EtherealRemnant:
You missed the space on the rm command.

It is rm -rf * not rm -rf*

rm removes, the -rf removes folders as well, and the asterisk (*) means all.

You also don't have to cd to the 2013* folder. I removed that, realizing my mistake.

run rm -rf 2013* while in the backup directory (run the command ls (lowercase l, not capital i) to make sure you are in the right folder so you don't trash the whole thing) and then pick up at the mkdir command and it will work this time. There is no space between 2013 and the * either.
[One (M7) Original Android Development] ne[m]o:
Running the push right now. Here is what I have in my adb so far: see attached picture
[One (M7) Original Android Development] EtherealRemnant:
Looks good. Since you did the rm -rf * command, you'd have to push it again anyway.

Then do these:

adb shell

cd /sdcard/clockworkmod/backup

mkdir 2013-06-03.23.51.18

unzip -d 2013-06-03.23.51.18 rogerbackup.zip

Hopefully it isn't corrupt this time. If it is, rm -rf * and choose a new port, push it again and do those four commands. Hopefully it works this time though.
[One (M7) Original Android Development] ne[m]o:
same issue. Might be port. I will try another port. Do you have to sleep soon? We can pick this up tmr.

See attached.
[One (M7) Original Android Development] ne[m]o:
ah ****. I typed rml -rf * without the cd /sdcard... command first. now it's returning. error. See attached.
[One (M7) Original Android Development] EtherealRemnant:
Alright, let's try something else. I'm going to send you a PM... I'll help you over TeamViewer.
[One (M7) Original Android Development] zounduser:
Just wanted to report back. I'm good to go. Successfully downgraded to the may build of hboot 1.44 and this, and everything else including supercid, hboot customizer, and splash was a breeze. Just like I remembered. :) thanks again for the help. Much appreciated.
[One (M7) Original Android Development] horsetastic:
Just wanted to say (OT) that I've been checking back here every now and then to see what's going on and every time I do I see more posts with you trying to get this issue resolved. If more people here were like you so many more people would get sorted out when they're stuck. Even though non of your help has been for me or even helped me in any way I still want to say thank you for being helpful and taking your time to troubleshoot and guide.

Honestly man, it's awesome to see :)

Sent from my cybernetic organism.....
[One (M7) Original Android Development] EtherealRemnant:
No problem man, glad that it all worked out. Enjoy! :)

Thanks man. I try to be helpful as much as I can. Unfortunately, I believe in this case there is no hope. I'm pretty sure the eMMC is fried. Anything written to it isn't persisting after a reboot and things that are transferred to it get corrupted in the transfer.

I sure as hell learned a lot today though. Much more than I ever intended to learn, that's for sure. I just wish I could have fixed it for him but I ran through everything I could think of including flashing the stock recovery, re-locking, then unlocking to repair the ability to even mount the data partition by a system wipe from the bootloader. All of it to no avail. I probably should have taken it to PMs or another thread in hindsight - then again, maybe others learned things too. *shrug*

I ran out of ideas. Pretty limited with S-ON and no RUU. Even the OTA is just a firmware update.
[One (M7) Original Android Development] horsetastic:
Ahh man.... Couldn't he even flash the firmware.zip in RUU mode Or did you try that one already? That may fix any deeper issues....
[One (M7) Original Android Development] jerronchua55:
Hi all, I'm currently experiencing error code -6 after using "./revone -P" command. I'm running 4th May version of hboot 1.44 and tried "./revone -P" on 4.1.2, 4.2.2 and 4.3 roms (all sense based roms), in which 4.1.2 and 4.2.2 gave me error code -6 and 4.3 gave me error code -1.

I was on S-OFF before, but i used writesecureflag 3 command to get my device back on S-ON only to realise that my warranty is still valid on S-OFF, and now I'm having problems getting back on S-OFF again.

I read somewhere that once you S-OFF and get back on S-ON, you will not be able to get back to S-OFF again. Is this true?

Here's my getvar all info:

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.44.0000

(bootloader) version-baseband: 4A.17.3250.14

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.24.707.1

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

(bootloader) serialno: HT367xxxxxx

(bootloader) imei: 3558590xxxxxx

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0714000

(bootloader) cidnum: HTC__044

(bootloader) battery-status: good

(bootloader) battery-voltage: 4248mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

getvar:all FAILED (status read failed (Too many links)) <- (failed? does this actually mean something is wrong with my bootloader?)

finished. total time: 0.050s
[One (M7) Original Android Development] RuckusDecay:
It seems you keep getting stuck on bootloop if this is the case just simulated a battery pulled. Let it boot back up.
[One (M7) Original Android Development] EtherealRemnant:
It's not a boot loop unfortunately. Nothing is persistent on the phone after a reboot. Using ls -l in the recovery shows roughly 20MB of data on the whole phone. It freezes as soon as hboot is done, no boot loop. We restored the stock firmware.zip, tried to flash ROMs in both TWRP and CWM, tried to restore a CWM Nandroid of the stock software, nothing persisted except for the recovery image and the firmware. I ran out of ideas. It has to be a hardware failure.

Sent from my HTC One now Free

---------- Post added at 11:54 AM ---------- Previous post was at 11:53 AM ----------

Download the stock RUU and run it. Easiest way to get the phone back to the state that revone will work again.

Sent from my HTC One now Free
[One (M7) Original Android Development] zaphodbeeb:
I had s-off via jcard, ran an ruu to get back to 1.44, did the s-on thing and then successfully used revone to s-off again (and relock etc), so in answer to your question, it is possible to s-on then s-off using revone. To my knowledge revone only works on 1.44 stock. Were you rooted on 1.44 stock? I could not get revone to do its magic until I was rooted and typed in su before running the -P command.

I used RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe to get me to stock.
[One (M7) Original Android Development] elvelozpotosino:
cant s-off

hboot 1.44.0000

jul 5 2013

i keep getting the error 6 after ./revone -P I tried over 60 times, on 4.3 and now on 4.1.2 and i just cant get it to work.. my hboot is version 1.44.0000 dated jul 5 2013... is that the problem????
[One (M7) Original Android Development] Theshawty:
Jul 5 is the problem. It's too new and likely patched. Don't take my word for it though.
[One (M7) Original Android Development] RuleOfSines:
You might be able to downgrade to a pre July 5 hboot and then S-Off. I had to do that with my ATT HTC One. Instructions are lying around here somewhere.

You do however have to use the HTC Dev unlocker to do it I believe if you haven't already unlocked the phone, so you will have a record there if you are concerned about that.
[One (M7) Original Android Development] jerronchua55:
Correct me if I'm wrong, but isn't it impossible to downgrade my rom to the stock one through RUU if I'm S-ON?
[One (M7) Original Android Development] EtherealRemnant:
Not if you are on the 1.44 hboot. You can't downgrade the hboot but you can flash a RUU with the same version number no problem.

The thing with revone is that it is always best to run it on as stock of a system as possible to make sure that you account for any possible issues that may arise.

You do, however, need to run fastboot oem lock from the bootloader (fastboot USB) in order to flash a RUU if you are S-ON.
[One (M7) Original Android Development] jerronchua55:
I've given it a go but I got error 140 on the RUU. I've created a thread regarding my RUU downgrade problems :http://xdaforums.com/showthread.php?t=2478735, it seems like I'm unable to run RUU because although I have a stock rom with the same version number as my RUU (1.29.707.3), but my firmware is of a newer version (2.24.707.1), and thus the error?

Btw, I've gotten my stock 1.29.707.3 rom from a TWRP backup, would there be any difference between the rom from the RUU compared to from the TWRP backup?
[One (M7) Original Android Development] EtherealRemnant:
Try it is all that I can say. If you have an exploitable bootloader then returning to the stock ROM should work but the firmware mismatch may pose an issue. It is worth a try either way.

Sent from my HTC One now Free
[One (M7) Original Android Development] horsetastic:
You should read the s-off guide in my signature. It states that this doesn't work. Also my downgrade thread answers more questions.

Edit. Just noticed your hboot version. You need to edit your mainver to a lower one then the RUU should work.

Also try flashing 1.29 firmware.zip via RUU mode.
[One (M7) Original Android Development] exocetdj:
Damn you were up early hahaha! :eek:
[One (M7) Original Android Development] horsetastic:
Quarter to 7 in the morning isn't early when you've got a 4 month old, a 3 year old and you've got to get to work (30 mins away) for 8:30 haha.... If anything it's not early enough lol!!
[One (M7) Original Android Development] exocetdj:
with a 5 year old and 8 month old I know hhow u feel hahahahaah :)

Anyhoo, im toying with the idea of sending my phone to fonefunshop as desperate for s off lol! (see what i did there to get back on topic?? hahahaha) :eek::silly::D:good::p;):):angel:

---------- Post added at 11:04 AM ---------- Previous post was at 11:02 AM ----------

wonder if [MENTION=4647967]Guich[/MENTION] knows any more about work done by revone team and hboot 1.54/55?????
[One (M7) Original Android Development] horsetastic:
Haha, are you also wishing you'd made more of the mornings you had before kids? lol....

and yes, I'm also beginning to ponder sending mine off.... But still hoping and hoping....

I've not heard anything for a while.... Gone a little quiet. Though there seem to be a few new people appearing asking if they can downgrade lol....
[One (M7) Original Android Development] exocetdj:
Defo mate but wouldn't change it for the world!!!! :)

lmao!!! thats what got me to pledge another $10 :)

If noobs keep doing that I think my donation is going to be rather large! :eek::cool::silly::D
[One (M7) Original Android Development] Guich:
No news atm...

And, however, if you can see the first page of this thread, the team wasn't present a lot :)

But check the bounty thread for the s-off by fuses and beaups, probably will be out soon :)
[One (M7) Original Android Development] exocetdj:
Lovely stuff matey :) thanks, im watching every s off thread like a hawk
[One (M7) Original Android Development] Guich:
I don't have this problem :D

I'm already s-offed :p :p
[One (M7) Original Android Development] exocetdj:
Lucky boy!

My hboot was 1.54 out of the box so yeah "i'm having fun" hahahahaha :highfive::D
[One (M7) Original Android Development] nkk71:
Hi guys,

(Maybe you already know, but anyhow) So it looks like revone, is not only dependant on ROM version but also on firmware.

I have S-Off, so I've been messing around a bit with different ROMs to see if we could get [MENTION=4347696]jerronchua55[/MENTION] to achieve S-Off

1- I kept firmware 2.24.401.1, but downgraded hboot to 1.44 May 2013 edition

2- tried with ARHD 13.3 (4.2.2) -> error code -6

3- tried with GPe (4.2.2) -> error code -6 (though I'm pretty sure I read some guy did get S-Off on GPe)

4- tried with ARHD 19.4 (4.1.2) -> error code -6 (that's the ROM I was on when it worked for me first time!)

5- tried odexed 1.29.401.13 -> that wouldn't even boot up

I'll try a few more permutations to see if I can get anywhere, and post back. Any suggestions which permutations, I should try?
[One (M7) Original Android Development] ImagioX1:
Well guys I got custom Rom up and running by flashing recovery through ruu mode like tall said. Still locked and everythings lovely. Thanks for talks help.

Sent from my HTC One using Xparent Red Tapatalk 2