yashsingh1/xdaforums huggingface dataset:
[One (M7) Android Development] limcc:
I am trying to find the stock Recovery before flashing the custom CWM/TWRP. because the Singapore 4.2.2 OTA will NOT update on my Revone S-off/unlocked M7. I didn't backup the stock recovery cause no info was found on the web, I don't suppose after flashing custom recovery can backup stock since its already custom flashed(not sure, need help). I tried with quite a number of so called stock M7 recovery before the OTA update. The process will always hang at ~1/4 progress bar then error with a exclamation mark inside red triangle. I had to flash back to RUU before it will start the update. I still have S-Off/unlocked bootloader now.

So, I think its the (not so)stock recovery that prevented the update base on the experience I have of >10 hours of trying. of course, I could be wrong, but I still can't find a way to back up the stock recovery. upon checking the downloaded OTA, I found the firmware.zip isn't encrypted! unlike the RUU.

My question is: is this the stock recovery and can I use it to flash back incase I need to claim warranty? expert please take a look and let me know please. see below for firmware.zip link.

Can't post link yet, join the 2 lines together

mega.co.nz/

#!Ddx2iS4Q!PqkuTWF6HwJL4NcMRvxwsD-IozgA8ttpC8gQUT5ukcw

OTA_M7_UL_JB_50_S_hTC_Asia_WWE_2.24.707.1-1.29.707.16_R_P_release_325138_signed firmware.zip (40.2 MB)
[One (M7) Android Development] descenpet:
i was looking if asian wwe(707) firmware is any different from wwe(401) yesterday. it seemed like recovery is different. so i'm assuming old version would be different too, maybe that's why ota with downloaded recovery didn't work for you.

yes that zip contain stock recovery from 2.24.707.1.
[One (M7) Android Development] limcc:
Glad to hear that, thanks. ;)
[One (M7) Android Development] DeSaint2:
Just go to bootloader and do

Fastboot boot recovery (recovery name).img

and it will just boot to the custom recovery. Then do a backup of recovery and it will backup stock recovery
[One (M7) Android Development] descenpet:
fastboot boot doesn't work on 1.54 bootloaders :p
[One (M7) Android Development] Magpir:
HTC_Asia_WWE_2.24.707.1 Firmware

can someone modify the above file and post it here to flash as a custom file

i tried in 7zip to delete the boot.img and recovery.img and zip it back it says operation not allowed

so how do modify it to be like the custom ones i posted earlier?

thanks.
[One (M7) Android Development] zeekabal:
which RUU to flash

hi,

i updated the firmware to version-main: 2.24.401.1 while i still have the stock ROM 4.1.2 and i am facing problem with wifi which not able to find wireless networks and not able to mount the sdcard,

please can someone tell me which RUU i should be flashing in order to fix my problems. i tried 2 RUUs so far and each time it fails saying phone not compatible.

the below is my phone information,

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__203

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.54.0000

(bootloader) version-baseband: 4A.17.3250.14

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.24.401.1

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

(bootloader) serialno: FA35VW903684

(bootloader) imei: 354436058421189

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: HTC__203

(bootloader) battery-status: good

(bootloader) battery-voltage: 3956mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-d16dc66985

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0
[One (M7) Android Development] descenpet:
you have to extract and rezip.
[One (M7) Android Development] Magpir:
ok i done the zip...
[One (M7) Android Development] descenpet:
RUUs likely failed because your bootloader is on higher version.

if no RUU works, the only way to make your phone work is to unlock and install a 4.2 rom.

else you will have to wait till 2.24 RUU comes.
[One (M7) Android Development] zeekabal:
but how to install a 4.2 ROM? i am not able to mount the sdcard and hence not able to copy the 4.2 ROM and install it via recovery :(

can maybe flash again the old firmware 1.29.401.16 (with bootloader version 1.44.0000) ? if so, can you please tell me where i can find this firmware? i am not able to find it
[One (M7) Android Development] descenpet:
if RUU doesn't work, old signed zip might not work too. i don't have any link too. if you want to try, download a 1.29 OTA.zip and get firmware.zip from it.

about 4.2 rom. you can always adb sideload/push in recovery even is you can't mount sd in android.
[One (M7) Android Development] zeekabal:
thanks a lot for the hints you are giving, could you please tell me how push the ROM with adb ? im helpless :( what are the commands i should fire?

thanks
[One (M7) Android Development] Magpir:
currently i am on S-off and latest firmware

if i want to flash a 1.29 RUU, whats the procedure like?
[One (M7) Android Development] DeSaint2:
Seriously? Have you tried it? I haven't done it since I first rooted unlocked and went s-off.
[One (M7) Android Development] descenpet:
if your bootloader is still locked, you should unlock first and install custom recovery.

then boot into recovery and make sure your pc can detect your phone properly(adb devices command should show your serial number)

if you want to push, use "adb push rom.zip /data/media/0/" then you should be able to flash it as it is already on sd card.

if you want to sideload, start sideload mode in recovery first, then use "adb sideload rom.zip". it will automatically start flashing once the transfer is finished.
[One (M7) Android Development] DeSaint2:
If it is an exe connect phone to pc and go into bootloader abd start the Ruu with administrative rights. If it's a flashable zip I believe you go to Ruu mode and do the fastboot flash zip command.
[One (M7) Android Development] descenpet:
seriously. i have tried it myself and many people have confirmed as well. :p
[One (M7) Android Development] DeSaint2:
Adb push Rom.zip /data/media I believe is where it goes.
[One (M7) Android Development] Magpir:
someone here mentioned that the firmware is a higher version so the ruu will not work.

will it have any chance of bricking the device?
[One (M7) Android Development] DeSaint2:
You should be able to Ruu to a higher firmware version. It's only when you're s-on that you can't downgrade firmware.
[One (M7) Android Development] zeekabal:
still not able to push it i am getting the following,

C:\android>adb push revolution.zip /data/media/0/

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

error: device not found

what is sideload mode?
[One (M7) Android Development] Magpir:
i mean the ruu if its 1.29, it means it is are a lower firmware version right?

so lower firmware version works with S-off right?
[One (M7) Android Development] descenpet:
it should go through when you are s-off. im not sure if supercid is needed.

---------- Post added at 03:44 AM ---------- Previous post was at 03:41 AM ----------

like i said, your computer need to detect your phone properly and have driver installed. if you type adb devices it should list your serial number with "recovery" beside it.

you can push/sideload after that.
[One (M7) Android Development] Magpir:
I am already super CID, but this doesnt matter right

So to go back to older stock everything, i just run the RUU?

thats all?

is there else i anything i should do?
[One (M7) Android Development] descenpet:
yes. it should work.

my ruu decided to fail on me when i did though. not sure if it is related or just by chance.

it sent me to failed ruu mode(ruu mode with !s at corners). and i can run ruu from there again and it went through.
[One (M7) Android Development] DeSaint2:
A Ruu will return hboot, firmware recovery Rom and kernel all back to stock. The only thing it doesn't do is relock bootloader or return to s-on.

With s-off you can go back and forth from new to old firmware.
[One (M7) Android Development] zeekabal:
thats all what i am getting when i use the push command,

C:\android>adb devices

adb server is out of date. killing...

* daemon started successfully *

List of devices attached

FA35VW903684 device

C:\android>adb push revolution.zip /data/media/0/

adb server is out of date. killing...

* daemon started successfully *

failed to copy 'revolution.zip' to '/data/media/0/': Permission denied

:(:(
[One (M7) Android Development] DeSaint2:
Run the command line as administrator. Sometimes fixes those things
[One (M7) Android Development] descenpet:
you have to do it while in recovery.
[One (M7) Android Development] Johnny424:
So as long as we are s-off we do not need to relock the bootloader and can start the firmware update? Or is it reccomended to relock

Also I have an att HTC one, I am s-off with super-cid..cid_111111..could anyone help me determine which firmware I would need to flash?
[One (M7) Android Development] zeekabal:
now i am not even able to have a recovery :( it seems with all the tries i can only see a stock recovery.

i have tried to do the following just to have a recovery installed

lock bootloader

flash firmware

unlock again

root using "fastboot-windows.exe boot boot.superboot.img" r1r1-htcone-superboot

then i tried to flash CWM recovery and twrp recovery both say that flashing is successful but when i reboot into bootloader and browse into recovery i get this screen showing the htc one with a sync symbol in the middle!

i could be able to flash the same recoveries before! why i am not able to do it now :(:(

this is really a pain :(
[One (M7) Android Development] descenpet:
you don't have to relock.

you can flash any 2.24. they are more or less the same. just show different number.

---------- Post added at 08:26 AM ---------- Previous post was at 08:24 AM ----------

that phone pic with sync like logo is stock recovery. just fastboot flash the recovery.
[One (M7) Android Development] c5satellite2:
Stop posting IMEI and SN!

Unless you WANT your phone cloned of course.

Please go back and edit your post!
[One (M7) Android Development] zeekabal:
thats what i am doing, i am flashing the recovery with fastboot boot recovery.img, but when i reboot the phone and go into recovery, it takes me to the stock recovery. i tried for CWM aand twrp recoveries :(
[One (M7) Android Development] descenpet:
fastboot boot is not the command to flash the recovery

fastboot flash recovery is the command to flash it.
[One (M7) Android Development] zeekabal:
finally one step ahead!! thank you very much!

now i am getting the following error

List of devices attached

FA35VW903684 recovery

C:\android>adb push revolution.zip /data/media/0/

adb server is out of date. killing...

* daemon started successfully *

failed to copy 'revolution.zip' to '/data/media/0/': Is a directory
[One (M7) Android Development] descenpet:
hmm.. maybe because you don't have 0 in /data/media.

which recovery are you using btw?
[One (M7) Android Development] zeekabal:
Latest CWM recovery..
[One (M7) Android Development] descenpet:
then just try pushing it to /data/media/ instead of /data/media/0/
[One (M7) Android Development] zeekabal:
Wuhuuuuuuuuuuuuuu!! I could finally copy and install the ROM using sideload !! wifi and sdcard is working properly!! finally I am starting to roam my new phone!!

cant get enough of thanking you!!
[One (M7) Android Development] nkgangew:
Hey guys, don't normally post, but I'm kinda worried here. I'm S off and have SuperCID and I just flashed the 2.24 firmware. When I use adb to run getvar all, it shows the radio I should be on, it says that my firmware is 2.24 now, BUT it's says my hboot is still 1.44, Not 1.5. Is this going to be an issue now or down the road?
[One (M7) Android Development] Magpir:
i beleive this happens on the 2.24.709.1 custom frmware zip

try flahing the 2.24.401.1 custom firmwarezip
[One (M7) Android Development] Johnny424:
For some reason I am getting stuck after entering the command "fastboot oem rebootRUU"

Hboot selections like reboot and recovery become unresponsive and I can't select anything. The command output doesn't say anything either and after about 5 mins I force reboot back to android..have tried several times but I cant seem to make it past this step.. anyone else have this issue?
[One (M7) Android Development] Magpir:
try changing usb ports or use a different computer to flash
[One (M7) Android Development] Reiki13:
Hello,

I just flash 2.24 firmware and reboot... it's ok but now adb not detect my One...

- I can't use "revone" for re-unlock in shell.

- I can't use recovery.

- I try to change USB port and update drivers, not work.

- I try to unlock in fastboot but "fastboot flash unlocktoken Unlock_code.bin" not work

If you have a tips for me, you make me glad ^^
[One (M7) Android Development] angusc:
Go back to HTCDEV site and re do the unlike process.

Sent with desire from My One
[One (M7) Android Development] Reiki13:
Thank, i try this and is ok but old firmware reborn... my phone is still 2.17 and 2.24 is erased :/
[One (M7) Android Development] Qoon3x:
I Just flashed 2.24.401.12, but now my wifi and storage are not working anymore..

Any ideas? reflashing the frimware doesn't help.
[One (M7) Android Development] DeSaint2:
Try a different Rom. Or reflash the one you have just wipe system and dirty flash.
[One (M7) Android Development] angusc:
[MENTION=4404229]GCbard[/MENTION],

lol.

What is your current configuration?

Can you bout in to bootloader then fastboot and connect USB. Run command:

fastboot getvar all

Post your output minus the iemi and serial number.

Sent with desire from My One
[One (M7) Android Development] Qoon3x:
That was what i was trying to do, but how can I flash a new rom if i can't punt the zip file on my storage? is it possible to flash the rom via fastboot?
[One (M7) Android Development] Reiki13:
I tryed with HBoot 1.44 but is not work... i can't unlock :/
[One (M7) Android Development] GCbard:
I have not received the phone yet. I am trying to gather what information I can first. I will receive it in a few weeks.
[One (M7) Android Development] DeSaint2:
In recovery use adb push or sideload
[One (M7) Android Development] tiho5:
I think this guy has to flash the boot.img he had prior to flashing the firmware.

The firmware replaced his original boot.img and he still has the old modules and that's why his Wi-Fi simply don't work

Edit: fastboot flash boot boot.img
[One (M7) Android Development] Qoon3x:
Where can i find the original boot.img? I was on the stock version before this.
[One (M7) Android Development] rilxous:
Experienced unresponsive touchscreen about middle of screen after flashing the 2.24 firmware. Anyone had same problem?
[One (M7) Android Development] tiho5:
Sorry, I am on my mobile XDA and didn't follow the conversation properly.

But in this case then the boot.img from the FW must be different from the previous stock boot.img which you were using as you were using anolder base up to updating it.

If you have a NAND backup the boot.img you were using is in it and you can extract it from there.

Or you can look for a stock boot.img for the base you are on.

Or you can download the FW you were on up to now and only take (extract) the boot.img from that one.
[One (M7) Android Development] GCbard:
I read in the op that upgrading the firmware upgrades the hboot? I do not have my ONE yet. But it will be the 64 gig ATT version. Can someone tell me which hboot version will end up on it once the latest firmware is flashed?

Also, I still do not understand why it is important to update to the latest firmware before flashing custom roms. All custom roms have a boot.img, so any boot.img will be replaced when flashing a custom rom. In addition wouldn't the firmware just be changed what ever the firmware version of the ROM is? It is my understanding that ROMs are based on firmware so which ever ROM you flash will contain a firmware that will overwrite the precedent firmware.

I just want to understand this before going ahead and rooting. I understand unlocking bootloader, rooting and setting s-off, it is just this idea of updating firmware before flashing custom roms that confuses me.
[One (M7) Android Development] ilal2ielli:
ROM and firmware are separate entities.

ROM is the phone operating system. Firmware is low level drivers.

Upgrading firmware is not necessary, but recommended so that the fixes/updates to drivers are used. For example, updated firmware gives latest radio, usually with optimized performance. Another thing the 2.xx firmwares update is the touch panel firmware, leading to better touch recognition, especially for capacitive buttons.

2.xx firmwares include 1.54 hboot.

Flashing custom firmware before ROM is recommended so that the proper kernel (boot.img is part of kernel) included with ROM is not overwritten by firmware's stock kernel. Although you can just reflash custom ROM over firmware again to have ROM's kernel, but firmware before ROM saves you time and an unnecessary flash.

Best steps to update firmware and ROM are:

1. Obtain S-off using revone. Root can be done first on stock ROM if you prefer to have a stock backup.

2. Unlock bootloader using revone.

3. Flash custom firmware. (Easier if you change to superCID)

4. Flash custom recovery.

5. Flash custom ROM.
[One (M7) Android Development] GCbard:
Thanks for your response.

If I change to superCID which firmware would I use? I am probably to flash sense based Android Roms as well as pure google to give them a try.

Any tutorial you recommend for changing to SuperCID would be appreciated.

Also, I was planning on using revone to activate S-off after unlocking bootloader and rooting via the methods drecribed by qbking77 on youtube. He uses the htcdev site for unlocking the bootloader. THat means i will already have a custom recovery since I will need recovery to flash supersu to get root rights.

Also, after upgrading the firmware you say I will have hboot version 1.54. Revone only works with hboot 1.44. Since I will have activated S-off before upgrading the firmware I assume that the phone will still be set to S-off and i will not need to use Revone again since it is incapable with hboot version 1.44

I am sorry if my questions are too much. Like I said, I am a genex owner and these steps were not required in rooting and flashing custom ROms.

Thanks
[One (M7) Android Development] ilal2ielli:
The newest firmware is 2.24.401.1 for WWE (World Wide English) phones, which AT&T phones are closest to in specification.

Flashing to superCID happens in bootloader, all you need to do is run the command:

fastboot oem writecid 11111111

AT&T CID is CWS__001 if you need to change back. (Two underscores)

Guides I have used:

Revone thread for revone s-off instructions.

mike1986's thread for rooting stock ROM.

Vomer's guide in mike1986's Android Revolution HD thread for firmware flashing (also has a custom firmware file that removes boot and recovery so that those don't get overwritten if you already have custom boot and recovery installed). mike1986's firmware flashing guide is also useful, but does not take into account s-off and supeeCID. With s-off and superCID, no need to relock bootloader to flash firmware.

Any custom ROM's thread for their ROM install instructions.
[One (M7) Android Development] GCbard:
so if I understand correctly if I have S-off and SuperCID I can go ahead and flash the firmware without relocking the phone, but if i do not have superCID and S-off I need to relock the bootloader.

Also, if I do not use the custom firmware with the boot and recovery removed, I will have to of course reflash the recovery. But what about the boot version? Will it stay at 1.54 and therefore render Revone incompatible if I decide to use it again?
[One (M7) Android Development] descenpet:
is you have s-off and supercid, you can flash WWE firmware, relocking is not needed.

if you don't have s-off and supercid, you can only flash official firmware, which AT&T haven't release yet. and yes you will need to relock if you decide to wait for it.

if you use the signed 2.24 firmware, you will have to reflash boot.img from your rom and your custom recovery.

if you use custom 2.24, you don't need to reflash those. but hboot will be 1.54. if you want to stay on 1.44, remove hboot image from the zip before you flash it.
[One (M7) Android Development] GCbard:
Is there any advantage in having hboot 1.54 over 1.44?
[One (M7) Android Development] descenpet:
not really. some stay on 1.44 without any issue i heard. you can get it to 1.54 anytime if you happen to have any issue so feel free to stay on 1.44 if you want to.
[One (M7) Android Development] GCbard:
Thanks. But upgrading the hboot will lose me the ability to use revone. But with s-off already set I might not need it anymore. If that a correct statement?
[One (M7) Android Development] descenpet:
Theoretically yes. Except if you want to return your phone and want to make it locked. But you can downgrade hboot when you want to do that.
[One (M7) Android Development] GCbard:
so I am processing all this information that i am getting from you and other forums i posted in and this is how i would put it together.

1. take new ATT HTC ONE out of box.

2. use instructions via qbking77 youtube video to unlock bootloader and load custom recovery (http://www.youtube.com/watch?v=QU7vi388dMk)

3. use instructions via qbking77 youtube video to root via flashing supersu through recovery. (http://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtu.be)

4. Achieve S-off via instructions for revone via qbking77 youtube video to activate s-off (http://www.youtube.com/watch?v=J4BWxtjaamM). this is based on xda forum by member ieftm at http://xdaforums.com/showthread.php?t=2314582

5. Change to SuperCID via xda thread instruction (http://xdaforums.com/showthread.php?t=2317536)

6. flash a custom firmware via fastboot instructions from this thread. Since I will receive an ATT phone I can find the closest updated firmware under WWE (for my case it should be firmware version 2.24.401.1).

7. reflash custom recovery via fastboot.

8. reboot phone into just-reflashed-recovery to flash desired custom rom and kernel.

does that seem right?

In addition I should find that I still have S-off and that I will not be able to use revone again since my bootloader will be upgraded to hboot version 1.54 and revone is only compatible with version 1.44.

Am i missing anything?
[One (M7) Android Development] descenpet:
revone should work on stock 4.1.2 rom so you can even skip 2 and 3. if you already did it, there is no harm too.