Database Develop

[HOW 2] Downgrade software version (before OTA)

This tutorial will help you downgrade back to software version '1.22.605.0' this software version is based on the shipped ROM before the OTA.
1) download: http://shipped-roms.com/shipped/Inc...dio_1.00.03.04.06_release_161493_NoDriver.exe
2)Run the RUU.
NOTE: you do not need your device to extract the ROM.zip from the RUU (Radio Update Utility)
Click to expand...
Click to collapse
A. after step number 2 you will see an image like this:
3) now go to your start menu and click on RUN in the textfield type %temp% and click ok. "you should see"
4) search threw all the folders that start off something like this {D3D2296B-5E22-46DB-BEF4-D7235D4BB485} inside this folder will be another folder with many stuff inside SCROLL DOWN till you see the ROM.zip
5) just drag and drop the ROM.zip onto your desktop like so:
6) renmae the rom.zip to PB31IMG.zip place it on the root of your SDCARD and boot into your hboot (power off the device then while holding the volume down + power will boot you into hboot)
7) the device will load the PB31IMG.zip and tell you if you want to update just volume up for yes, and when prompted to reboot just volume up for yes on your device and your DONE!!!
Hope this helps anyone...!!
ID*

do you have to be connected to htc sync in order to do this or can you just download the file to your pc desktop and connect your incredible via the usb than run the file.
what is RUU exactly, if it is an application where do I download it from

slumpey326 said:
do you have to be connected to htc sync in order to do this or can you just download the file to your pc desktop and connect your incredible via the usb than run the file.
what is RUU exactly, if it is an application where do I download it from
Click to expand...
Click to collapse
you do not need htc sync to extract the rom.zip
(RUU = Radio Update Utility)
this is mainly a how to extract the images from the rom.zip inside a RUU nothing more

ZOMG WILL THIS HALP ME HAS ROOT???????????????????????
Sorry, had to. =P Thanks for the guide!

Thanks
Thanks. Worked perfectly.

When I'm in the hboot menu the phone is saying that there is either no image or its the wrong image. What gives?

You probaly renamed it as
<filename>.zip.zip
Usally Windows dont Turn ON Extension in Browsers

Nope. I know better than that.

So are devs working on rooting pre-OTA, OTA, or both (meaning whichever works best)?
EDIT: I'm just wondering if that's why we have this instruction set posted. I guess if pre-OTA is rooted everyone will want to downgrade.

I don't understand the point of this, although it may be due to the fact I'm a android noob. I went into the recovery menu (I had already applied the OTA update) and selected "clear storage". That wiped my phone and sent me back to pre OTA state. I'm pretty sure of this because the next time I turned on my phone It started bugging me about an exchange update. What's the point of going through this complicated procedure?

i really dont understand the point of this????

suzook said:
i really dont understand the point of this????
Click to expand...
Click to collapse
Title says it all... if a hack for root is found in the updated bootloader everyone who wants root will be able to downgrade to be able to apply the hack is pretty much all this is for

suzook said:
i really dont understand the point of this????
Click to expand...
Click to collapse
Some of us are seeing the 1x for network speed a lot more, or for the first time after the update. This would revert us back to not seeing 1x.

But why do all of this when clear storage does the same thing with less hassle

psmafia said:
But why do all of this when clear storage does the same thing with less hassle
Click to expand...
Click to collapse
I don't think clear storage takes you back to pre-OTA... you have to do that manually, im sure.

RLKirk said:
I don't think clear storage takes you back to pre-OTA... you have to do that manually, im sure.
Click to expand...
Click to collapse
Definitely not. If you want to go to pre-OTA you need to follow this method.

If clear storage got me to pre-OTA i wouldn't still be fighting with this.
Seriously does anyone have any insight into why the heck this isn't working for me?
It's saying:
SD Checking....
Loading [pb31diag.zip]
no image!
Loading [pb31diag.nbl]
no image or wrong image!
Loading [pb31img.zip]
no image!
Loading [pb31img.nbl]
no image or wrong image!
then kicks me back to the hboot screen.
I'd really like to get my reliable 3g back.

Someone posted another one of these files, one with HBOOT .79 I believe. If you update hboot, then you can't downgrade then right?

TNS201 said:
Someone posted another one of these files, one with HBOOT .79 I believe. If you update hboot, then you can't downgrade then right?
Click to expand...
Click to collapse
False. HBOOT .77 and .79 are 'inter-flashable'. It goes both ways.

Well both ROM.zip have different Version details so i suspect that Downgrading from 0.79 to 0.77 SPL is Possible
0.77
ModelID: PB3120000
CIDNUM: VZW__001
MainVer: 1.22.605.0
HbootPreUpdate: 11
0.79
ModelID: PB3120000
CIDNUM: VZW__001
MainVer: 1.22.605.2
HbootPreUpdate: 13

[Q] No working ROM, recovery, or RUU...

Hello all,
I have a Sprint HTC Hero that I may have utterly destroyed.
It will not boot normally or into recovery (stays at white HTC screen for hours)
So I have a bad ROM and a messed up recovery partition...
I've tried various RUUs and all of them end of with the same Error 131 Customer ID Error.
I've tried putting HERCIMG.zip directly onto the sdcard and running HBOOT - It finds the file, but I get the same (similar?) error: CID Incorrect! Update Fail!
Alas, this phone is S-ON...
My last resort is trying to recreate a goldcard:
I put the original SD card into another device and found the CID with this command:
cat /sys/class/mmc_host/mmc0/mmc0:*/cid
However, I am not sure if I have done this correctly... the SD card will mount as a Removable Device, but when I try RUU or HBOOT from /sdcard/ it gives the exact same error.
When connected through USB, adb does not pick up the device, but fastboot does...
I'm on Windows 7 x64.
Thanks in advance for any helps and suggestions!
*another interesting note: It has no touch panel...

krazeeazndude said:
Hello all,
I have a Sprint HTC Hero that I may have utterly destroyed.
It will not boot normally or into recovery (stays at white HTC screen for hours)
So I have a bad ROM and a messed up recovery partition...
I've tried various RUUs and all of them end of with the same Error 131 Customer ID Error.
I've tried putting HERCIMG.zip directly onto the sdcard and running HBOOT - It finds the file, but I get the same (similar?) error: CID Incorrect! Update Fail!
Alas, this phone is S-ON...
My last resort is trying to recreate a goldcard:
I put the original SD card into another device and found the CID with this command:
cat /sys/class/mmc_host/mmc0/mmc0:*/cid
However, I am not sure if I have done this correctly... the SD card will mount as a Removable Device, but when I try RUU or HBOOT from /sdcard/ it gives the exact same error.
When connected through USB, adb does not pick up the device, but fastboot does...
I'm on Windows 7 x64.
Thanks in advance for any helps and suggestions!
*another interesting note: It has no touch panel...
Click to expand...
Click to collapse
Ok, so you mount your sd card, THEN try to RUU? If that's what you're doing, don't mount the SD. Also, try running the RUU.exe, if fastboot sees the phone it should work (note the .exe, not .zip). Report back.

il Duce said:
Ok, so you mount your sd card, THEN try to RUU? If that's what you're doing, don't mount the SD. Also, try running the RUU.exe, if fastboot sees the phone it should work (note the .exe, not .zip). Report back.
Click to expand...
Click to collapse
No, I have no way of mounting... It will only go into bootloader (HBOOT/FASTBOOT).
When I try to RUU, it's through FASTBOOT USB.

krazeeazndude said:
No, I have no way of mounting... It will only go into bootloader (HBOOT/FASTBOOT).
When I try to RUU, it's through FASTBOOT USB.
Click to expand...
Click to collapse
Are you running the .exe from htc? Or trying to flash a .zip?

il Duce said:
Are you running the .exe from htc? Or trying to flash a .zip?
Click to expand...
Click to collapse
.exe from htc. I can't flash a zip from recovery because I have no recovery.
I've tried fastboot flash zip, but it says remote not allowed
All the RUUs detect the phone and can reboot it, but when it tries to update the image, I get the Customer ID error...

krazeeazndude said:
.exe from htc. I can't flash a zip from recovery because I have no recovery.
I've tried fastboot flash zip, but it says remote not allowed
All the RUUs detect the phone and can reboot it, but when it tries to update the image, I get the Customer ID error...
Click to expand...
Click to collapse
do you get an error number like 110 or 140 or 170, also have you seen this thread: http://forum.xda-developers.com/showthread.php?t=958968

il Duce said:
do you get an error number like 110 or 140 or 170, also have you seen this thread: http://forum.xda-developers.com/showthread.php?t=958968
Click to expand...
Click to collapse
I get error number 131 Customer ID Error.
I have read that thread and I've tried the HERCIMG.zip on page 3... But I shall try again

krazeeazndude said:
I get error number 131 Customer ID Error.
I have read that thread and I've tried the HERCIMG.zip on page 3... But I shall try again
Click to expand...
Click to collapse
Just make ure you're using the correct zip from that thread (sounds like you are) and the correct commands for fastboot usb, which are listed in that OP. I have never heard of error 131, hopefully you can fix it

il Duce said:
Just make ure you're using the correct zip from that thread (sounds like you are) and the correct commands for fastboot usb, which are listed in that OP. I have never heard of error 131, hopefully you can fix it
Click to expand...
Click to collapse
Yea that didn't work...
I get "FAILED (remote: 42 custom id check fail)"
This makes me think I need a different signed HERCIMG.zip
It's unfortunate I can't post replies to that thread because I'm a new user...

Does anyone know how to fix the CID error?

krazeeazndude said:
Does anyone know how to fix the CID error?
Click to expand...
Click to collapse
try google. I did and saw some stuff on there, but since it's not my phone with the issue, and I'm not paid tech support (nobody is on xda) you should go look around, maybe you can find a fix or someone who's had the issue and can help you. If you do get a fix, POST IT HERE WITH DETAIL, and change the thread title by adding the magic word "SOLVED" into it. Best of luck.

krazeeazndude said:
Does anyone know how to fix the CID error?
Click to expand...
Click to collapse
OK this might work, might not, don't get your hopes up. Open up whatever .zip or .exe you were trying and try to find a file called "android-info.txt" then open that and see if there's a line in there that says CIDNUM: ....... and tell me what the number says - Actually just post up all the stuff in there, model, CID, mainver...

il Duce said:
OK this might work, might not, don't get your hopes up. Open up whatever .zip or .exe you were trying and try to find a file called "android-info.txt" then open that and see if there's a line in there that says CIDNUM: ....... and tell me what the number says - Actually just post up all the stuff in there, model, CID, mainver...
Click to expand...
Click to collapse
Here are the contents of that text file from the rom.zip of 'RUU_Hero_C_Sprint_2.27.651.5_R_signed_release.exe'
ModelID: HERO20000
CIDNUM: SPCS_001
MainVer: 2.27.651.5

krazeeazndude said:
Here are the contents of that text file from the rom.zip of 'RUU_Hero_C_Sprint_2.27.651.5_R_signed_release.exe'
ModelID: HERO20000
CIDNUM: SPCS_001
MainVer: 2.27.651.5
Click to expand...
Click to collapse
Well nevermind that looks normal, I was hoping something was missing, and it's not, I revert to my previous post.
sent from a series of tubes.

il Duce said:
Well networking that looks normal, I was hoping something was missing, and it's not, I revert to my previous post.
sent from a series of tubes.
Click to expand...
Click to collapse
So I've tried these RUU versions, and they're all signed, so I'm pretty sure there's nothing missing from them...
1.29.651.1
2.27.651.5
2.27.651.6
2.31.651.7
They're all official Sprint RUUs... Is it possible that my phone is not an official Sprint phone? Back when it was working, it said Sprint on the main menu... but I think the carrier was CredoMobile...

Ruh roh. I hope you can find a credo mobile ruu.
sent from a series of tubes.

Info like that coulda been useful hours ago. You gotta brick dude. I wish you all the best of luck trying but if you've tried all of that to still no avail...... its gonna be rough if possible at all.
®parallel universe®

il Duce said:
Ruh roh. I hope you can find a credo mobile ruu.
sent from a series of tubes.
Click to expand...
Click to collapse
Credo's page links to the HTC page with the Sprint RUUs... so I'm not sure what's going on... Thanks for your help though.

MattCrystal said:
Info like that coulda been useful hours ago. You gotta brick dude. I wish you all the best of luck trying but if you've tried all of that to still no avail...... its gonna be rough if possible at all.
®parallel universe®
Click to expand...
Click to collapse
Well, Credo uses the Sprint Network... so I just figured it's the same phone... it looks identical. And the Credo webpage redirects to HTC's main webpage, with the Sprint RUUs... so it must be the same CDMA phone.
I came here hoping to find out more information than what I could already find on Google. I didn't know what to expect because I've read through many, many threads, and I was beginning to think that the phone is bricked. I appreciate that you have the courage and honesty to tell me that. Thanks.

your not completely bricked if you can boot into fastboot but if none of what duce posted helps I dont know what will. I do wish you luck and please keep us updated. I would like to know the outcome.

Fixing some misconceptions about S-off

Alright, because there is constant stupidity regarding the bootloader security state for HTC devices. I feel that I can clarify and help remove some myths and misconceptions.
Let's start with the most important one:
What is S-off?
S-off is us turning off the security flag stored in the NV RAM of our device. This allows us to flash unsigned files (zips and images) to our device. The difference is stated below of why you need a zip vs an image.
S-off is not root either. Root is just a binary stored in /system and just doesnt get removed if the device has s-off. S-off just means integrity of file system / partitions aren't checked on the device. So this means the two are exclusive of each other from a user standpoint.
HTC IS JUST GOING TO TURN S-ON AND RUIN IT FOR EVERYBODY!
No, they aren't. For a few good reasons, one of which is their own engineers have s-off to begin with.
The @secuflag (S-on/S-off) is there to verify hboots and other various image files on the device to begin with. When we have s-off on a newer device but idiot user decides to turn s-on for whatever reason and we have a modified hboot? The device will brick because you broke its chain of trust. It thought you were friends but you slept with it's girlfriend or whatever. Now if HTC were to suddenly turn s-on, this would break chains of trust for those who used something like Moonshine with a patched hboot. It was their OTA that caused it. They are then held liable for it and they have to fix it under warranty. You know how much that costs them? Imagine giving 1000's of people new phones because you singlehandedly broke them all. Good job dude.
Not only that, they cant turn S-on by just updating images on the device. It's stored in the NV-RAM. They would need an entirely different method than just flashing through recovery.
Next point is:
S-off means you can flash whatever you want using fastboot flash.
Now because s-off processes before gave us patched hboots, we didnt know any better. This is all wrong. fastboot flash barely works on newer phones unless dev unlocked. Now that not all s-off's give a patched hboot it's good to know the following. The only way to install something with a locked bootloader but s-off, is to use flash zip. This means that you dont just "fastboot flash recovery" or boot.img. You need to create a zip with android-info.txt and whatever files your flashing. With the lock placed on devices, unless you htc dev unlock or flash a modified hboot, it wont allow you to flash because the dev unlock is a different part than what flashes the zips.
More info about patched / eng hboots:
Now that we've seen what we lose without a patched hboot, what does it add exactly? Well, a patched or engineering hboot allows you to fastboot flash pretty much every partition on the device with an unsigned image directly (such as fastboot flash hboot hboot.img or fastboot flash splash1 splash1.img) without giving you a not allowed or command error. The reason these are useful is because it saves time. I really dont want to always have to build a zip so I always use patched hboots. They also give you access to more commands as well which I can't remember off the top of my head. These are all commands mainly used by HTC engineers and software testers.
Final point that I can think of (may add more):
That green progress bar needs to be full when fastboot flashing a zip. While it's a pretty green bar and looks very useful...for whatever reason, htc has decided to make it wrongly report progress when in use. This can lead to users freaking out and just leaving their phone in RUU mode for however until someone tells them they're idiots for it. this progress bar means literally nothing and my favorite quote about it is: "Progress bar is like tits on a snake. Interesting but pointless." Ignore the progress bar. If the command line says the zip finished, just fastboot reboot or reboot-bootloader. It will help you finish whatever the heck you're trying to do.

Nice write-up I added it to the FAQ's thread Q9 Thanks

Very nice thread, thanks

+1 on that green progress bar, when I removed the red writing on the splash screen I saw the progress bar not don't but in command prompt it said finished so I said whatever and just rebooted
Sent from my HTC One using Tapatalk 2

Reminds me of a certain thread I wrote about a year ago
S-OFF explained - by a Developer

Didn't even know that existed.
Sent from my hidden jewel

Question, let's say I have s-off and flash the superuser app and all the required busybox files... Can I use root required apps like titanium backup and wireless tether?
I only ask because I've been hesitatent to root. I just don't want to Dev unlock via HTC and officially void my warranty. The sealed in battery has me extremely paranoid as its generally the first thing I've had to replace with previous HTC devices.
This leads me to the following question, if the response to the first was no... Is there a way to use root apps without using the HTC Dev tool
Please note: I'm not a developer and this was not clear to me in the write up.

You don't need s-off to root.
You do need to root to use apps that require root access.

budeone said:
You don't need s-off to root.
You do need to root to use apps that require root access.
Click to expand...
Click to collapse
You've stated the obvious...but thanks for the response!
I just want to know if we can get root without going through HTC, or if it will be possible in the near future thanks to the s-off development. It's my understanding that you do not need root to get s-off.

bnapy said:
You've stated the obvious...but thanks for the response!
I just want to know if we can get root without going through HTC, or if it will be possible in the near future thanks to the s-off development. It's my understanding that you do not need root to get s-off.
Click to expand...
Click to collapse
I found this link, may answer your question.
http://www.pocketables.com/2012/08/...nlocked-bootloader-in-the-htc-evo-series.html

As described in this thread an Android-info.txt file can be used to fastboot flash update.zip where the contents of the zip are TWRP and the .txt file.
I am S-OFF Locked on 1.31 stock
I want to flash TWRP via the method described above. (Or alternatively the superuser apk)
I have a img file of TWRP.
I need an Android-info.txt file that will work. Where is an example of this file so I can attempt this? Does anyone have a link?

Indirect said:
That green progress bar needs to be full when fastboot flashing a zip. While it's a pretty green bar and looks very useful...for whatever reason, htc has decided to make it wrongly report progress when in use. This can lead to users freaking out and just leaving their phone in RUU mode for however until someone tells them they're idiots for it. this progress bar means literally nothing and my favorite quote about it is: "Progress bar is like tits on a snake. Interesting but pointless." Ignore the progress bar. If the command line says the zip finished, just fastboot reboot or reboot-bootloader. It will help you finish whatever the heck you're trying to do.
Click to expand...
Click to collapse
I don't know about "tits on a snake," but many progress bars I've seen are both uninteresting and pointless. They do generally serve their purpose of keeping impatient/inexperienced users from hammering away at things they don't understand and inadvertently breaking them.

tws101 said:
I need an Android-info.txt file that will work. Where is an example of this file so I can attempt this? Does anyone have a link?
Click to expand...
Click to collapse
Here is the version straight from the 1.31..651.2 OTA firmware.zip. Although you may not need the "btype" or "aareport" lines. I have flashed TWRP in the past without those lines included.

tws101 said:
As described in this thread an Android-info.txt file can be used to fastboot flash update.zip where the contents of the zip are TWRP and the .txt file.
I am S-OFF Locked on 1.31 stock
I want to flash TWRP via the method described above. (Or alternatively the superuser apk)
I have a img file of TWRP.
I need an Android-info.txt file that will work. Where is an example of this file so I can attempt this? Does anyone have a link?
Click to expand...
Click to collapse
PillowMetal said:
Here is the version straight from the 1.31..651.2 OTA firmware.zip. Although you may not need the "btype" or "aareport" lines. I have flashed TWRP in the past without those lines included.
Click to expand...
Click to collapse
Another misconception about S-OFF is that you need a "valid android-info.txt" when flashing from fastboot. When you're S-OFF, the bootloader completely disregards that file. All you need is to make a zip with whatever you want flashed, and then add any android-info.txt file in there. The default one that I include in the plugin template for my Bootloader Customizer is actually completely empty and it works fine as well. As long as there is a file (irregardless of file size) in the zip named android-info.txt, you'll be able to flash it fine, just as long as you ARE S-OFF.

regaw_leinad said:
As long as there is a file (irregardless of file size) in the zip named android-info.txt, you'll be able to flash it fine, just as long as you ARE S-OFF.
Click to expand...
Click to collapse
That's good to know, and thanks for the bootloader customizer, I have been using it for years, as well as your "rebooter" which is very convenient. Glad to see you in the One forums!

regaw_leinad said:
As long as there is a file (irregardless of file size) in the zip named android-info.txt, you'll be able to flash it fine, just as long as you ARE S-OFF.
Click to expand...
Click to collapse
Just to follow up, I discovered that at least with the Sprint HTC One, you need the following three lines at a minimum when flashing from rebootRUU or you will get an error stating:
FAILED (remote: 24 parsing android-info fail)
Code:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
So it looks like S-OFF validation of android_info.txt has stiffened up since the EVO 4G LTE days.

PillowMetal said:
Just to follow up, I discovered that at least with the Sprint HTC One, you need the following three lines at a minimum when flashing from rebootRUU or you will get an error stating:
FAILED (remote: 24 parsing android-info fail)
Code:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
So it looks like S-OFF validation of android_info.txt has stiffened up since the EVO 4G LTE days.
Click to expand...
Click to collapse
Ah, you don't have a bootloader that allows fastboot flashing? That must be why. If you were flashing straight from the hboot, you don't need it. Didn't realize you guys had to use RUU mode.

regaw_leinad said:
Didn't realize you guys had to use RUU mode.
Click to expand...
Click to collapse
I would LOVE to be able to flash from hboot, it was so convenient and didn't require a computer. But alas, no SD Card on the Sprint variant, so no hboot flashing.
It has been said that we can use USB-OTG to perform the hboot flashing, but I have yet to get a known compatible and working USB drive to be recognized or even looked at when starting up the bootloader, although the drive works fine when rebooted to system or even recovery. It just doesn't search for external mounts like the old EVO 4G LTE hboot did on startup.
There's a thread for the small number of us who care and wan't to do this, but can't...
http://forum.xda-developers.com/showthread.php?t=2320252
And specifically, my experiences trying to get it to work.
http://forum.xda-developers.com/showpost.php?p=44444102&postcount=9
http://forum.xda-developers.com/showpost.php?p=44494480&postcount=11
Any insight or things you can share regarding this would be greatly appreciated.

PillowMetal said:
I would LOVE to be able to flash from hboot, it was so convenient and didn't require a computer. But alas, no SD Card on the Sprint variant, so no hboot flashing.
It has been said that we can use USB-OTG to perform the hboot flashing, but I have yet to get a known compatible and working USB drive to be recognized or even looked at when starting up the bootloader, although the drive works fine when rebooted to system or even recovery. It just doesn't search for external mounts like the old EVO 4G LTE hboot did on startup.
There's a thread for the small number of us who care and wan't to do this, but can't...
http://forum.xda-developers.com/showthread.php?t=2320252
And specifically, my experiences trying to get it to work.
http://forum.xda-developers.com/showpost.php?p=44444102&postcount=9
http://forum.xda-developers.com/showpost.php?p=44494480&postcount=11
Any insight or things you can share regarding this would be greatly appreciated.
Click to expand...
Click to collapse
You know, it might depend on the type of drive, and it might depend on the file system your drive is formatted to. I have 0 experience using USB-OTG, so I'm probably not the best one to ask unfortunately But if you do get it working, be sure to make a guide or something! Try playing around with different formatting of your drive possibly

regaw_leinad said:
You know, it might depend on the type of drive, and it might depend on the file system your drive is formatted to. I have 0 experience using USB-OTG, so I'm probably not the best one to ask unfortunately But if you do get it working, be sure to make a guide or something! Try playing around with different formatting of your drive possibly
Click to expand...
Click to collapse
Ah, never thought of trying different formatting, there are different allocation unit sizes I could use... thanks! I will definitely make a guide if I get this resolved because it is driving me crazy, so I'm sure there are others too.

[Q] Nandroid download

Can someone please tell me if this nandroid download is supposed to have a .exe file? Verizon RUU Zip 1.10.605.10 Posted or can someone tell me where to get a nandroid for my htc one m7?

sydneygriffin62 said:
Can someone please tell me if this nandroid download is supposed to have a .exe file? Verizon RUU Zip 1.10.605.10 Posted or can someone tell me where to get a nandroid for my htc one m7?
Click to expand...
Click to collapse
First, that file is a RUU zip file not a nandroid backup. Unless your OS is the same as that file or you are S-OFF you can not run that file.
Second, you might have better luck finding a nandroid for your phone in the Verizon HTC One forum because they are setup for that phone. There are some key differences between the Verizon phones and the GSM phones.
Third, you will need to provide more information about your phone and what you are searching for before anyone can help you. Generally a fastboot getvar all will provide a lot of the information.

htc one stock rom
majmoz said:
First, that file is a RUU zip file not a nandroid backup. Unless your OS is the same as that file or you are S-OFF you can not run that file.
Second, you might have better luck finding a nandroid for your phone in the Verizon HTC One forum because they are setup for that phone. There are some key differences between the Verizon phones and the GSM phones.
Third, you will need to provide more information about your phone and what you are searching for before anyone can help you. Generally a fastboot getvar all will provide a lot of the information.
Click to expand...
Click to collapse
Yes I am s off with twrp recovery and viper one 6.2
CID- VZW__001
OS- 1.10.605.10
I want to keep TWRP and S-Off but go back to stock please help I was told this was bricking some phone's
http://www.htc1guru.com/dld/ruu-zip-m7_wl_jb_50_vzw_1-10-605-10_decrypted-zip/

sydneygriffin62 said:
Yes I am s off with twrp recovery and viper one 6.2
CID- VZW__001
OS- 1.10.605.10
I want to keep TWRP and S-Off but go back to stock please help I was told this was bricking some phone's
http://www.htc1guru.com/dld/ruu-zip-m7_wl_jb_50_vzw_1-10-605-10_decrypted-zip/
Click to expand...
Click to collapse
that file will work use the instructions at the bottom of this page
http://www.htc1guru.com/downloads/ruu-zip-downloads/
their is also a newer RUU here it flashes the same way
http://flyhalf205.com/getdownload.php?file=RUU/m7vzw/PN07IMG_M7_WL_JB_50_VZW_2.10.605.1_DECRYPT.zip

[RECOVERY-EU-Ver] PhilzTouch_Recovery for 64Bit HTC Desire 510 (msm8916)

Here you have philz touch recovery ported from YUREKA . Its full working and I prefer this one instead to CWM, because it´s more modded.
Put the zip in the root of your microsd, boot into bootloader and Update will automatically start
DeviceTree : https://github.com/joker2910/android_device_htc_a11ul
EDIT : Attached new , fresh compiled Recovery + my device_tree, used for compiling Philz recovery

greeneyes2910 said:
Here you have philz touch recovery ported from YUREKA . Its full working and I prefer this one instead to CWM, because it´s more modded.
Put the zip in the root of your microsd, boot into bootloader and Update will automatically start
Click to expand...
Click to collapse
You're doing a fantastic job. Keep up the good work! ?
Sent from my 0PCV1 using XDA Free mobile app

Thanks for recovery,working perfect on my phone

Is the board name "msm8916" the sufficient compatibility factor to apply this corectly?
(CPU-Z says my board name is msm8916, however
There is nowhere in the CPU-Z reports about "A11UL" - but HBOOT reports it.)
greeneyes2910 said:
Put the zip in the root of your microsd, boot into bootloader and Update will automatically start
Click to expand...
Click to collapse
Is this instruction referring to CWM already installed? (I don't have it yet.)
How to evoke bootloader afterall? When pressed volume down & Power then HBOOT starts but unfortunatelly it reports:
"CID incorrect"
The zip file has been placed in the root of the SD card - as you suggested. What is wrong?

ioy said:
Is the board name "msm8916" the sufficient compatibility factor to apply this corectly?
(CPU-Z says my board name is msm8916, however
There is nowhere in the CPU-Z reports about "A11UL" - but HBOOT reports it.)
Is this instruction referring to CWM already installed? (I don't have it yet.)
How to evoke bootloader afterall? When pressed volume down & Power then HBOOT starts but unfortunatelly it reports:
"CID incorrect"
The zip file has been placed in the root of the SD card - as you suggested. What is wrong?
Click to expand...
Click to collapse
It seems you have not an European 64Bit Desire. So you have to unzip first andy modify the android info to match your cid. Zip again & try then

Working, good job.

greeneyes2910 said:
It seems you have not an European 64Bit Desire. So you have to unzip first andy modify the android info to match your cid. Zip again & try then
Click to expand...
Click to collapse
You probably mean the file android-info.txt with the content:
Code:
modelid: 0PCV20000
cidnum: HTC__001
cidnum: HTC__031
cidnum: HTC__102
cidnum: HTC__Y13
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__M27
cidnum: HTC__A07
cidnum: HTC__002
mainver: 1.51.401.1
btype:1
aareport:1
DelCache:1
hbootpreupdate:13
What to write in? How to find CID of my phone? It is apparently msm8916 as (CPU-Z reports) and "A11UL" (as HBOOT says so), besides TheDreamer kernel works on it.
I've got it from T-Mobile in the European Union country. Where to get CID from within this phone?

or just unzip the file and using fastboot flash it to your phone, which is how I did it. Works a treat.

Burtrum, hope the compatibility's proven sufficently to rely on this version of recovery as working well with my phone after using the "brut force" you suggesting

do you have to be rooted on the 64 BIT first? because i just unlocked my boot loader

ioy said:
Burtrum, hope the compatibility's proven sufficently to rely on this version of recovery as working well with my phone after using the "brut force" you suggesting
Click to expand...
Click to collapse
Lol. If I do have an issue I'll use the same method to put CWM back on there. But that is the method I've used with my Incredible S, HOX and now this phone

It's ok, the "simple CID getter" told me what the CID was and this putted to android-info.txt yielded perfectly working recovery now
Thank you!

Flashed via fastboot, works a charm. Thank you soooo much!! Now we just need some x64 roms! :0)

is anyone able to make a 64bit back up.
im stuck in limbo at the moment with my fone its unlocked rooted and has this recovery on it but no OS due to a mistake i made .

Maybe this Recovery would work well with yet-unexisting modded 64bit ROMs updates.
However HTC has just released update of its stock 64bit ROM (which is reported to work smoother than previous one) and this Recovery doesen't allow for doing the update.
So where to get the 64 bit STOCK recovery back from?
OR maybe you would propose any trick to overcome this obstacle without touching the PhilzTouchRecovery please?
(When manually chosen OTA_xxxxxx.zip it complains about not finding /system/build.prop )

Works great thank you, now all we need is some roms

Beshnazzle said:
now all we need is some roms
Click to expand...
Click to collapse
Yes, we wait for them patientlessly! :-/
And the stock recovery one could extract from OTA_*****.zip update file. It's simple, just unzip.

ioy said:
Yes, we wait for them patientlessly! :-/
Click to expand...
Click to collapse
Well, me and you could team up and try to port a 32 bit on to our one? idk how but i found a tutorial on it

Okay so ive been trying to get the ROM files from my device by using "Clone ROM to update.zip" within Philz CWM but the /system file named "system.ext4.tar" wont extract i get This Message for some reason and i dont know what to do.

Beshnazzle said:
Okay so ive been trying to get the ROM files from my device by using "Clone ROM to update.zip" within Philz CWM but the /system file named "system.ext4.tar" wont extract i get This Message for some reason and i dont know what to do.
Click to expand...
Click to collapse
Hello,
I don't know what that "Clone ROM to update.zip" is, but I can help you to simply extract system.ext4.tar. I don't know how to do it in Windows without Cygwin but if you use that program or Linux you can type:
Code:
tar -xvf system.ext4.tar
in a terminal and it will extract your whole system to the folder you are in. This is a very quick and easy way to obtain /system.