yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] EtherealRemnant:
It really looks like the exploit is still patched somehow. I would run the RUU again, this time after using fastboot oem rebootRUU - seg fault means motochopper is patched. Something didn't downgrade.

Sent from my HTC One
[One (M7) Original Android Development] ImagioX1:
Maybe I should clarify. It was a firmware zip with everything except system, recovery, and boot.img. Maybe I should try the full Ruu and see what happens.

Sent from my HTC One using Xparent Red Tapatalk 2
[One (M7) Original Android Development] EtherealRemnant:
That's why it isn't working. You have to run the full RUU. You have a frankenphone right now.

Sent from my HTC One
[One (M7) Original Android Development] horsetastic:
If you're s-off you can just 'dd' the recovery.img to p34....
[One (M7) Original Android Development] ImagioX1:
I'm not familiar with 'dd'ing as you call it. Could you point me to some good directions on how to use this please....

It just seems funny there's no way to unlock the bootloader when your s-off except through the official HTC site.

Sent from my HTC One using Xparent Red Tapatalk 2
[One (M7) Original Android Development] EtherealRemnant:
I wouldn't recommend dd. One mistake with it and you've got a brick.

And you can unlock without HTC Dev, you just didn't downgrade properly. There's a big difference. Revone was made for a specific environment. HTC patched it. The remedy is to downgrade. The whole thing takes less than an hour including the backup and restore. You can even backup your apps using the Helium app. No root required.

Sent from my HTC One
[One (M7) Original Android Development] horsetastic:
surely you should be able to fastboot flash recovery without unlocking bootloader when you're S-OFF anyway..... very strange....
[One (M7) Original Android Development] Black-FR:
The easiest way is, to Flash the recovery in the RUU mode.

Using a custom Firmware.ZIP.

At sneakyghost's Thread you will find the instruction, how to flash in RUU mode and you find there also alot custom ZIP's.

Fastboot flashing does Not work, with a locked Bootloader.

Gesendet von meinem HTC One mit Tapatalk 4
[One (M7) Original Android Development] Theshawty:
Yes, you can flash the recovery as a zipped image file with an Android info txt from the rebootRUU mode. No need to unlock the bootloader at all then.

>> Sent from the abyss <<
[One (M7) Original Android Development] ImagioX1:
Thanks guys I'm going to give this a shot and report back some time later.

Sent from my HTC One using Xparent Red Tapatalk 2
[One (M7) Original Android Development] EtherealRemnant:
Then why bootloader unlock at all? Lol

Sent from my HTC One
[One (M7) Original Android Development] ImagioX1:
Lol my question!

Btw does the zip you flash in RUU mode have to be signed?

Sent from my HTC One using Xparent Red Tapatalk 2
[One (M7) Original Android Development] EtherealRemnant:
No. You're S-OFF. Nothing has to be signed.

Sent from my HTC One now Free
[One (M7) Original Android Development] Theshawty:
When you're S-OFF, there's no need to unlock the bootloader at all. RebootRUU is past the regular fastboot mode and is used by the RUU utilities and service shops.

Because when you're S-OFF, the security is off and no security and signature checks are made.

>> Sent from the abyss
[One (M7) Original Android Development] EtherealRemnant:
Makes sense. I could have sworn you couldn't run a custom recovery without the bootloader unlocked beforehand but that was older HTC devices.

I'm going to leave mine alone though. It is just fine the way it is. Lol!

Sent from my HTC One now Free
[One (M7) Original Android Development] Theshawty:
With the bootloader unlock on the One and onwards, S-OFF isn't even needed for the end user as we have write access to the system, boot, radio and recovery directly from fastboot and the recovery.

I want S-OFF though so I can flash firmwares etc.

>> Sent from the abyss <<
[One (M7) Original Android Development] PillowMetal:
Yes you can flash custom recovery with a locked bootloader, you package up the file as "recovery.img" along with an "android.txt" in a zip file and flash it from "fastboot oem rebootRUU". I am fully custom and have never unlocked my bootloader.

Can't use fastboot flash recovery recovery.img...

Yes, you need the full RUU including those excluded images (especially boot,img)

Correct, but fastboot oem rebootRUU followed by fastboot flash zip recovery.zip does - so does flashing from the bootloader using a powered USB-OTG cable and a PN07IMG.zip file which is even easier and more portable.

True

Exactly, I don't! No TAMPERED, UNLOCKED, OR RELOCKED and never used revone to make it that way. When running revone, only use the "-s 0" parameter.
[One (M7) Original Android Development] ImagioX1:
Thanks for clarifying. I'll report back how it goes. Might not have to run the Ruu after all

Sent from my HTC One using Xparent Red Tapatalk 2
[One (M7) Original Android Development] ne[m]o:
I keep getting cannot detect device when I type in the commands. any help?
[One (M7) Original Android Development] EtherealRemnant:
Drivers. Uninstall HTC Sync if it is installed, uninstall any driver pack for the phone (HTC, PDANet, SDK, etc), reboot, install HTC Sync to get the drivers and just remove HTC Sync. Make sure USB debugging is turned on in development. Make sure fast boot is disabled in power settings. Try different USB ports - adb doesnt like 3.0 ports much.

If it comes down to it, grab a Linux live CD and do it from linux.

Sent from my HTC One now Free
[One (M7) Original Android Development] ne[m]o:
The thing is. I can't boot into my phone. It's stuck on the splash screen. I can access recovery but everything is wiped. So I can't ensure my USB debugging is turned on.

I can't use RUU because 1) I'm on rogers [there isn't a rogers RUU] 2) I need s-off to load another RUU.

I have tried to load GURU Reset via sideload. It worked, but still stuck on boot screen. Then trying it again after installing the adb toolkit. Running the all-in-one toolkit for sideload didn't work anymore. The function no longer worked but just spewlled out a lot stuff instead.

I don't have HTC sync, as far as I can see via control panel->unistall programs.

I'm trying to follow http://xdaforums.com/showthread.php?t=2358738

Stuck on the s-off part. because my adb can't seem to detect/read my phone.

I have a Rogers nandroid backup I want to push to the sd card to recover from, but I don't know how to do that neither.

Thanks if anyone can help.
[One (M7) Original Android Development] EtherealRemnant:
What did you do to get it messed up like that?

And if you hold down power and volume down does it take you to hboot? If it does, plug the USB cable into the computer and it should change to fastboot usb.

Are you bootloader unlocked? If you have TWRP you might be able to sideload a non-aroma ROM (i would just get CM). You'll have to hunt through the options for it because it's been awhile since I used it but I believe it's in advanced.

Sent from my HTC One now Free
[One (M7) Original Android Development] www_igor:
Does revone support hboot 1.55 ?

I have trouble, I need to RUU my HTC One Sprint but I have no RUU 3.xxx and can't downgrade
[One (M7) Original Android Development] EddyOS:
What makes you think it is if 1.54 isn't supported?
[One (M7) Original Android Development] www_igor:
When I am in fastboot mode I see HBOOT 1.55.000... and S-ON

May be there is any other solution
[One (M7) Original Android Development] maarawoe:
What did you installed so you are 1.55? Some OTA???

Odesláno z mého HTC One pomocí Tapatalk 4
[One (M7) Original Android Development] EddyOS:
The 4.3 OTA has 1.55
[One (M7) Original Android Development] exocetdj:
I have heard the guys may be working on hboot 1.55 but it certainly isn't supported yet
[One (M7) Original Android Development] www_igor:
I can test))
[One (M7) Original Android Development] jmkhenka:
Perhaps there is hope.

1.55 hboot on verizon has s-off, perhaps that will help us? Perhaps it will work out of the box with 1.55
[One (M7) Original Android Development] horsetastic:
1.54 hboot on verizon has s-off..... doesn't mean a thing....
[One (M7) Original Android Development] ne[m]o:
when I run adb shell I keep getting.

error: device not found

I have device stuck in bootloop. Should I have it in recovery when I do this or hboot or fastboot usb?

I have unistalled HTC drivers and installed HTC sync

any help plz?
[One (M7) Original Android Development] horsetastic:
Is your bootloader unlocked?

I'm not sure revone will work from recovery. To a point maybe but not completely.... If I were you I'd boot to recovery, facory reset, wipe cache and dalvik cache then sideload another rom.....
[One (M7) Original Android Development] ne[m]o:
Okay so I can't s-off basically.

What am I to do then? Since I need s-off to use RUU. And there isn't a Rogers RUU availble.

My bootloader is unlocked. I can boot to recovery, factory reset, wipe, and sideload, but I still get stuck on boot screen. Any suggestions?
[One (M7) Original Android Development] EtherealRemnant:
You still haven't said what you did to get to this point. We could help you better if we knew how the phone ended up like this.

Since you are bootloader unlocked, sideload a stock rooted ROM. I would suggest the AT&T stock rooted ROM since you have Rogers. In TWRP, wipe the whole phone (advanced wipe) if it comes down to it.

Sent from my HTC One now Free
[One (M7) Original Android Development] ne[m]o:
The phone froze on me as I was using google calendar. So I press and held the power button to restart the phone. The phone proceeded to get stuck on the bootloader with the beats audio on it. It also did a couple of screen flashes while it was stuck on this screen.

So I booted into recovery, and re flashed the kernal (thinking it was the kernal issue). That didn't change anything it was still stuck on boot loader. Next I tried to boot into recovery to re-flash the ROM, but it wouldn;t go into recovery. So when I got home, I used HTC AIO and re flashed the recovery. Getting into recovery, doing a full wipe of everything before flashing the ROM. When it booted, it was now stuck on the first boot screen.

After looking at xda and google. It advised me to use a RUU. However, because I was on Rogers. There was no RUU for it, so running the RUU gave me erro 32, signature error. Realized this was the issue because I didn't have s-off. Here I am trying to s-off it.

I can sideload a rom and use aroma to install. However after, reboot it would still be stuck on the first boot screen. Any more details? Any help?
[One (M7) Original Android Development] EtherealRemnant:
Don't use an AROMA ROM. Try to get as close to stock as possible. As I mentioned, an AT&T stock rooted ROM would probably be the best. Also, advanced wipe and make sure to check boot and system so you have a clean slate.

Or do this:

http://androidforums.com/internatio...card-if-your-phone-wont-boot.html#post5933877

Here's the nandroid:

http://bugsylawson.com/files/file/1857-m7-cwm-nandroid-backup-cid-roger001-12963117/

And here is the available OTA:

http://bugsylawson.com/files/file/1...314-release-318662-signedms4ef8qvnqbkudqrzip/

Sent from my HTC One now Free
[One (M7) Original Android Development] ne[m]o:
Thanks for all your help.

I have the nandroid file (the one you provided) I don't know how to push that into my sd card so my recovery can detect it. I also have the OTA, which I used the HTC One AIO to flash the RUU.zip. Does nothing for me.

I just downloaded the "One_2.24.401.8_odexed.zip" and sideloaded it. It does use aroma, everything worked well. Still stuck on boot loader.

I'm downloading the http://xdaforums.com/showthread.php?t=2476204

and going to try that. But it seems the biggest issue is it is still stuck on bootloader. I wish we had removeable sd cards...sigh.
[One (M7) Original Android Development] EtherealRemnant:
Is it boot-looping or freezing?

As for the nandroid, that is what that guide is for. It requires CWM recovery and you adb push it to the proper directory.

Since you are bootloader unlocked and can't run revone, you can't use a RUU because you would have to relock your bootloader and there is no guarantee that you would gain anything from that.

I'm starting to lean towards a failing eMMC at this point. It sucks but it happens.

Sent from my HTC One now Free
[One (M7) Original Android Development] ne[m]o:
It's freezing. Completely stuck on the HTC quietly brilliant part of the screen, with the red warning disclosure at the bottom.

This happens with any type of ROM I put in and successfully flashing it.

As for the nandroid. When I am in the adb console. When I type in adb devices, it gives me list of attached devices and says its in recovery, but the next step when I try to push it, it always returns "error: device not found" but I have HTC Drivers installed, and I have HTC sync installed as well. What is causing this?

I thought having s-off would allow me to run any RUU, and I thought an RUU might be the solution.

I cannot thank you enough for your help in this matter. Should I successfully get out of this, let me buy you a drink.
[One (M7) Original Android Development] EtherealRemnant:
Always remove HTC Sync. Just leave the drivers. It is interesting that you can sideload when adb is broken. You should be able to run adb push if using CWM recovery.

S-OFF would work but you can't obtain S-OFF without a working 4.1.2 install.

The only thing I can think of is decrypting that OTA, relocking your bootloader, and using fastboot to manually flash the firmware.zip

You don't really have any other options right now that I can think of but I would see if someone else chimes in with an idea I'm overlooking. It sounds like you need to reflash your firmware to me. If that fails, I would say that you need to get a new device.

Sent from my HTC One now Free
[One (M7) Original Android Development] ne[m]o:
Okay, I realized I couldn't push it because it was calling from another directory for adb. I am able to push it it now. Just a matter of it not showing on the sdcard directory. I'll get back to you on this.

What is this firmware method? I can relock and unlock my bootloader just fine using the HTC one AIO. I unistalled the htc sync, my drivers are from HTC drivers only. I'll keep you posted.

EDIT: using TWRP not cw
[One (M7) Original Android Development] EtherealRemnant:
Give me a few to get on the computer and decrypt the OTA for you. I'll post it up here when I'm done along with the instructions okay?

Sent from my HTC One now Free

---------- Post added at 12:16 PM ---------- Previous post was at 11:58 AM ----------

Okay, here is the firmware.zip. Try it without relocking.

Make sure you're in hboot, not recovery.

fastboot oem rebootRUU will take you to the HTC screen, then run

fastboot flash zip firmware.zip

it should fail the first time, run the same command again.

When it is done, fastboot reboot.

Report here what you get when you do this.

http://www.mediafire.com/?b5vq5sy5bjyflb0
[One (M7) Original Android Development] ne[m]o:
Okay I can push the rogers nandroid back-up into the sdcard. But when I hit nacup/restore->restore. It doens't show my nandroid backup. Why?

I will give your firmwave thing a whirl. brb.
[One (M7) Original Android Development] EtherealRemnant:
You need CWM recovery to use that nandroid and you have to restore it to the place that the guide says to restore it to - it doesn't search for them. Annoying, I know.
[One (M7) Original Android Development] ne[m]o:
So I did as you said. here is my results.

Needless to say, after rebooting it is still stuck on the bootscreen with the HTC quietly brilliant. So how effed am I?
[One (M7) Original Android Development] EtherealRemnant:
Error 99 is a good thing. Relock your bootloader and try again.

fastboot oem relock

Sent from my HTC One now Free
[One (M7) Original Android Development] ne[m]o:
I relocked my bootloader, and rebooted into bootloader.

Bootloader now says ***relocked***

tried typing in fastboot oem rebootRUU

gave me this:
[One (M7) Original Android Development] EtherealRemnant:
You typed in "fasboot", not "fastboot"
[One (M7) Original Android Development] ne[m]o:
Holy crap I am an idiot.

Okay I got to work. I unlocked the bootloader again.

It booted back into the first HTC screen and is stuck on that. What now? adb push rom? (the sense 5 deox one?)

Thanks man!!!!! =)))
[One (M7) Original Android Development] EtherealRemnant:
Now that you have working firmware, just flash TWRP (you went back to stock recovery with that firmware package) and then sideload. Fingers crossed that this works now.

EDIT: You didn't run the command a second time. It isn't done.

fastboot flash zip firmware.zip

then after that is done, fastboot flash zip firmware.zip again, then reboot. The first command only prepares the device for hboot flashing.
[One (M7) Original Android Development] ne[m]o:
I flashed the firmware three times. Then booted into bootloader then unlocked the bootloader again. Flashed TWRP. Rebooted into recovery, adb sideload, sideloaded the sense 5 deoxy. rebooted.

Screen now is just the HTC quietly brillant, no red disclaimer. But also stuck on that screen. Any hints? We're so closeee!
[One (M7) Original Android Development] EtherealRemnant:
Okay. First off, slow down.

There is a very specific order that this has to be done.

1) fastboot relock

2) fastboot oem rebootRUU

3) fastboot flash zip firmware.zip

4) fastboot flash zip firmware.zip (confirm it says it was successful, if it errors, note any error and post it here)

5) fastboot reboot

6) Go to the bootloader, verify that recovery is stock recovery by opening it from bootloader. If it isn't, we have a problem. If it is, we can proceed.
[One (M7) Original Android Development] ne[m]o:
Okay, thanks for the details.

I followed up to step 5.

It rebooted into the HTC splash screen without the red warning. I can't seem to get into bootloader. Whether it be by 3 button method or via adb.
[One (M7) Original Android Development] EtherealRemnant:
Hold down volume down and power - the lights at the bottom will start to flash, keep holding until it brings you to the hboot screen. If the buttons don't start flashing after a few seconds, you might need to let the phone die, charge it, remove the charging cable, then boot the device with power and volume down to get into hboot. It may have soft-bricked but hboot should still be functional.

Also try fastboot reboot-bootloader. It may have initialized enough to get to that point.
[One (M7) Original Android Development] ne[m]o:
I pressed and held for volume down and power, the lights do flash. I've been holding it for like 8 mins now.... nothing has happened.

I tried fastboot reboot-bootloader and it just displays:

<waiting for device>
[One (M7) Original Android Development] EtherealRemnant:
Ctrl-C that and try adb reboot bootloader.

Its obviously still alive, just not responding. The good news is that white screen will kill the battery with the quickness. Try holding just the power button and see if that does anything. Basically just toy with it - if all else fails, you have no choice but to let it die and try to bring it back up.

I'm hoping that I wasn't right about the eMMC failing. It is rare but it does happen. The fact you're running a signed hboot made for your device is very telling that something isn't functioning properly. That said if you can't get it up, you do have a case for warranty since if its bricked they won't bother doing diag on it and will just flash it.
[One (M7) Original Android Development] Theshawty:
press and hold the volume down and power while holding your phone under a light source.
[One (M7) Original Android Development] EtherealRemnant:
Didn't know about that trick.
[One (M7) Original Android Development] ne[m]o:
that worked.

It booted into bootloader. Then clicked recovery.

it booted into this black screen with a green ! sign and kind of recycle sign thing. Then it rebooted itself back into the HTC quietly brillant screen (no red warning).
[One (M7) Original Android Development] EtherealRemnant:
Good. You're stock. Do the light trick again and then follow this.

Now we need this file -> http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-roger001-1-29-631-17-2013-06-03-zip/

We need this recovery -> http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.3-m7ul.img

Once you have both, unlock your bootloader.

Now:

1) rename recovery-clockwork-touch-6.0.4.3-m7ul.img to recovery.img

2) fastboot flash recovery recovery.img

3) fastboot reboot-bootloader

4) open recovery from bootloader

5) adb push nandroidname /sdcard/clockworkmod/backup/nandroidname/ (replace nandroidname with the name of the extracted nandroid - I would shorten it if it is a long name to avoid any errors)

6) restore nandroid

7) reboot and pray.
[One (M7) Original Android Development] ne[m]o:
Thanks man. It's going to take an hour to download the "rogers file".

Okay advice if step 7 doesn't work?

got to step 4.

for step 5, do I need my phone to be in recovery mode? or hboot?
[One (M7) Original Android Development] EtherealRemnant:
Recovery. CWM activates ADB when it is opened and will allow you to push the image.

So CWM is now coming up on the device? If so, try adb reboot bootloader and it should take you back to hboot. If it does, power down until you are ready to restore the nandroid. I picked that one specifically because it goes with the firmware package you flashed. It should be a fully stock system after that is restored which is the ideal for troubleshooting purposes.

If step 7 fails, someone else might have to chime in or you may have no recourse but to replace it. It is official firmware and the matching nandroid of that firmware. There aren't any other variables to take into account.

EDIT: Once the device is powered down, when you turn it back on, make sure to hold down power and volume down so you don't get stuck at the HTC screen again.
[One (M7) Original Android Development] ne[m]o:
I can get into CWM. thanks.

I typed: adb reboot bootloader

it said daemon started successfully. Then < error: device not found >

The last time I pushed the nandroid zip file into the phone, I couldn't recover it from recovery. Is that going to happen now? Now that I am in CWM recovery, I clicked sdcard, there is only folder:

/sdcard/0/clockworkmod/ there is no backup part. Is that okay, that the folder doens't exist? Do I need to extract the nandroid zip before pushing it in?

When I type in adb devices it doens't even show the devices attached anymore, unlike last time.
[One (M7) Original Android Development] EtherealRemnant:
Okay uninstall ALL adb drivers (SDK, HTC Sync, PDANet, etc) and use this -> http://xdaforums.com/showthread.php?t=2263822

See if adb works after that.

As for the folder, it will create it automatically since it doesn't currently exist.

I'm going to flash CWM to my phone temporarily so I can help you directly.

EDIT: When I opened up CWM, I typed adb devices and it shows mine. I also pushed and it created the folders that weren't there.
[One (M7) Original Android Development] DeSaint2:
Did you make sure your sdk was up to date? If not that might cause some issues.
[One (M7) Original Android Development] EtherealRemnant:
It is easier just to remove everything and use the generic driver, especially with the broad range of support it has.
[One (M7) Original Android Development] DeSaint2:
I'm talking about the android sdk(which is generic for all adb and fastboot). The driver is needed for connection to the phone but does not provide adb and fastboot instructions.