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
Related
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.
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.
Hi guys, yesterday my htc one downloaded android 4.4.2 update(4.19.401.11) which is about 308.24 MB. I had TWRP system recovery so i flashed the stock recovery and tried to install the update but after few minutes the progress bar stoped and the green phone logo turned red than i tried to reboot it again show phone is ready to update, i again tried to install and again same happened but this time i left it on that red logo. while in that red logo(maybe warning signal) i left it as it is and after few minutes it rebooted and this time it said new update available to download(the ota update from downloads folder was deleted). I don't know whats going wrong, my current software version in 3.62.401.1( android 4.3 with htc sense 5.5).. I m rooted and also s-off. Please someone help!!
suyash1629 said:
Hi guys, yesterday my htc one downloaded android 4.4.2 update(4.19.401.11) which is about 308.24 MB. I had TWRP system recovery so i flashed the stock recovery and tried to install the update but after few minutes the progress bar stoped and the green phone logo turned red than i tried to reboot it again show phone is ready to update, i again tried to install and again same happened but this time i left it on that red logo. while in that red logo(maybe warning signal) i left it as it is and after few minutes it rebooted and this time it said new update available to download(the ota update from downloads folder was deleted). I don't know whats going wrong, my current software version in 3.62.401.1( android 4.3 with htc sense 5.5).. I m rooted and also s-off. Please someone help!!
Click to expand...
Click to collapse
Try it again and this time when the green logo turns red, hold down volume up and press power button while holding volume up, the recovery log should appear , post the error msg that it shows here (you might have to try pressing volume up, volume down and power button for recovery log to appear, you'll have to get the timing right)
muhammad.uzi1994 said:
Try it again and this time when the green logo turns red, hold down volume up and press power button while holding volume up, the recovery log should appear , post the error msg that it shows here (you might have to try pressing volume up, volume down and power button for recovery log to appear, you'll have to get the timing right)
Click to expand...
Click to collapse
The update is being downloaded again, as soon as it finishes i will do it again and i will try to get the recovery log..
suyash1629 said:
The update is being downloaded again, as soon as it finishes i will do it again and i will try to get the recovery log..
Click to expand...
Click to collapse
Okay
muhammad.uzi1994 said:
Okay
Click to expand...
Click to collapse
Recovery Log:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Warning: No file_contextsVerifying current system...
"/system/framework/core.odex" has unexpected contents.
Installation aborted.
Do you have any idea why is this happening? I tried opening the ota package in my computer, and in there firmware.zip was not opening. It says the compressed folder is invalid.
suyash1629 said:
Recovery Log:
Code:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Warning: No file_contextsVerifying current system...
"/system/framework/core.odex" has unexpected contents.
Installation aborted.
Do you have any idea why is this happening? I tried opening the ota package in my computer, and in there firmware.zip was not opening. It says the compressed folder is invalid.
Click to expand...
Click to collapse
No, mate, I don't know about this error, Maybe @nkk71 knows, better wait to see what he thinks about this . Are you rooted? Have you ever modified your OS by deleting any system apps?
muhammad.uzi1994 said:
No, mate, I don't know about this error, Maybe @nkk71 knows, better wait to see what he thinks about this . Are you rooted? Have you ever modified your OS by deleting any system apps?
Click to expand...
Click to collapse
i m rooted but not modified system apps or deleted them. but this firmware file does not contain "/system/framework/core.odex" and also firmware.zip doesn't open.. i dont think so, rooting effects the update because last time i updated to 4.3 while i was rooted.
suyash1629 said:
i m rooted but not modified system apps or deleted them. but this firmware file does not contain "/system/framework/core.odex" and also firmware.zip doesn't open.. i dont think so, rooting effects the update because last time i updated to 4.3 while i was rooted.
Click to expand...
Click to collapse
I got no ideas about this, you should wait for nkk71 or @alray
suyash1629 said:
i m rooted but not modified system apps or deleted them. but this firmware file does not contain "/system/framework/core.odex" and also firmware.zip doesn't open.. i dont think so, rooting effects the update because last time i updated to 4.3 while i was rooted.
Click to expand...
Click to collapse
1- firmware.zip won't open with Windows Explorer because it's a signed firmware package, this is expected
2- "/system/framework/core.odex" has unexpected contents -> it's either not there or not stock, the OTA will not go through, if all the conditions are not met 100%
nkk71 said:
1- firmware.zip won't open with Windows Explorer because it's a signed firmware package, this is expected
2- "/system/framework/core.odex" has unexpected contents -> it's either not there or not stock, the OTA will not go through, if all the conditions are not met 100%
Click to expand...
Click to collapse
is there any solution for updating?
suyash1629 said:
is there any solution for updating?
Click to expand...
Click to collapse
1- please post a "fastboot getvar all" excluding IMEI and s/n
2- are you using any mods? (such as Xposed)?
3- why stay on stock ROM?
suyash1629 said:
is there any solution for updating?
Click to expand...
Click to collapse
If you're s off, try running an RUU for your cid and mid and then take ota , because somewhere along the way, I think you accidentally modified your system settings
nkk71 said:
1- please post a "fastboot getvar all" excluding IMEI and s/n
2- are you using any mods? (such as Xposed)?
3- why stay on stock ROM?
Click to expand...
Click to collapse
1. "fastboot getvar all" result:
Code:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-OFF
serialno: XXXXXXXXXXXX
imei: XXXXXXXXXXXXXX
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 4002mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
2. never used any mods or exposed framework but its rooted. Last time I restored to factory state using Guru_Reset_M7_2.24.401.1.zip and updated than i s-off using rumrunner_HTC_0.5.0 and locked the bootloader and today i again unlocked the bootloader using adb shell method from the computer(i have done this before too).
3. I dont understand what you mean by this question? i u mean why are you staying on stoke firmware than my answer is i m already using different roms and mods in my galaxy s and galaxy s3, so i thought at-least one phone should be in stock..
muhammad.uzi1994 said:
If you're s off, try running an RUU for your cid and mid and then take ota , because somewhere along the way, I think you accidentally modified your system settings
Click to expand...
Click to collapse
I could do that even earlier than you said but i dont want to factory reset my phone.. can i flash the core.odex of my guru reset? because that file is missing from my phone(i think that missing file is creating the issue)
suyash1629 said:
I could do that even earlier than you said but i dont want to factory reset my phone.. can i flash the core.odex of my guru reset? because that file is missing from my phone(i think that missing file is creating the issue)
Click to expand...
Click to collapse
Two of the guru roms that I tried on my phone were faulty and didn't let me take ota, the solution that worked for me was running a downgrade ruu , it could be that the guru Rom isn't accurate, read this http://forum.xda-developers.com/showthread.php?t=2682363
muhammad.uzi1994 said:
Two of the guru roms that I tried on my phone were faulty and didn't let me take ota, the solution that worked for me was running a downgrade ruu , it could be that the guru Rom isn't accurate, read this http://forum.xda-developers.com/showthread.php?t=2682363
Click to expand...
Click to collapse
But that guru reset has that core.odex and after installing that guru reset i was able to take the ota update to 3.62.401.1(android 4.3)
suyash1629 said:
But that guru reset has that core.odex and after installing that guru reset i was able to take the ota update to 3.62.401.1
Click to expand...
Click to collapse
Then install the guru Rom again, take Ota to 3.xx, then take the next ota to 4.xx. maybe you just modified the system core.odex thing, installing the guru Rom again and retaking ota should work
muhammad.uzi1994 said:
Then install the guru Rom again, take Ota to 3.xx, then take the next ota to 4.xx. maybe you just modified the system core.odex thing, installing the guru Rom again and retaking ota should work
Click to expand...
Click to collapse
Maybe @nkk71 might have some other way to fix this.. if there is nothing i can do than only i will go that way..
suyash1629 said:
But that guru reset has that core.odex and after installing that guru reset i was able to take the ota update to 3.62.401.1(android 4.3)
Click to expand...
Click to collapse
get the missing/changed file from http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
or just dirty flash it without root, then install OTA, and re-root
nkk71 said:
get the missing/changed file from http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
or just dirty flash it without root, then install OTA, and re-root
Click to expand...
Click to collapse
Can i only flash that core.odex file? i dont want to download that huge file because i have slow internet speed. i can transfer that to my website server extract it there any download only core.odex file(doing this will only take few minutes because my website server possibly could download within minutes). or do i have to flash whole guru reset?
hey I want to update my htc one to 4.4 and get rid of twrp.
I´ve unlocked it via htcdev and installed twrp.
i have got s-on
hboot 1.54.0000
CID vodap120 (as far as i know this is still the orginal one)
can I just relock the phone or do i need stock recovery? (hop I´m useing the coreced terms here :/ )
if so can I follow this guide http://forum.xda-developers.com/showthread.php?t=2545227.
I remeber that I had to download some drivers when I unlocked the phone and I dont think that they are still on my computer. could someone send me a link to them?
thanks
joachim (austria)
You don't want to lock the bootloader unless you plan to reflash an RUU. with it unlocked you will just need to reflash to the stock recovery and then do your update. Are you trying to run an ota to 4.4?
Here is a link to drivers: http://forum.xda-developers.com/showthread.php?t=2232799
uuu91 said:
hey I want to update my htc one to 4.4 and get rid of twrp.
I´ve unlocked it via htcdev and installed twrp.
i have got s-on
hboot 1.54.0000
CID vodap120 (as far as i know this is still the orginal one)
can I just relock the phone or do i need stock recovery? (hop I´m useing the coreced terms here :/ )
if so can I follow this guide http://forum.xda-developers.com/showthread.php?t=2545227.
I remeber that I had to download some drivers when I unlocked the phone and I dont think that they are still on my computer. could someone send me a link to them?
thanks
joachim (austria)
Click to expand...
Click to collapse
This tool might be easier to use and quicker for getting the required ADB & Fastboot tools. Here is what is required to receive an OTA update. And yes, you will need your stock recovery installed. However, since you are on a lower hboot, it might be more beneficial to S-OFF first before the 4.4 update. S-OFF gives you more options going forward.
majmoz said:
This tool might be easier to use and quicker for getting the required ADB & Fastboot tools. Here is what is required to receive an OTA update. And yes, you will need your stock recovery installed. However, since you are on a lower hboot, it might be more beneficial to S-OFF first before the 4.4 update. S-OFF gives you more options going forward.
Click to expand...
Click to collapse
I couldn't agree more. the ability to change CID and flash any available RUU while bootloader unlocked is a huge advantage if you like to be adventurous with your devices' software.
first of all thanks for the quick reply
so more detail:
right know I´m getting the information that there has been an update issue.
I´m running on 4.2.2 (the software number is 2.24.161.1(I dont know how important that is or what it actually is)
after clicking on software-updates he told me that I can download 3.63.161.6
yes I want to make an ota update
need to reflash to the stock recovery
Click to expand...
Click to collapse
how do I do that. I need a file for that am i right? Which is the right one for me?
after reflashing stock recovery do i need to do something else.
oh yes i forgot to mention that i have super su. is that a problem?
ps I dont need advantages because I decided that I wont do any changes improvements to my system
uuu91 said:
first of all thanks for the quick reply
so more detail:
right know I´m getting the information that there has been an update issue.
I´m running on 4.2.2 (the software number is 2.24.161.1(I dont know how important that is or what it actually is)
after clicking on software-updates he told me that I can download 3.63.161.6
yes I want to make an ota update
how do I do that. I need a file for that am i right? Which is the right one for me?
after reflashing stock recovery do i need to do something else.
oh yes i forgot to mention that i have super su. is that a problem?
ps I dont need advantages because I decided that I wont do any changes improvements to my system
Click to expand...
Click to collapse
First, read this post about OTA Updates.
Next, you need to download two OTA files from this site. The 2.24.161.1 OTA and the 3.63.161.6 OTA will be used to update your phone.
After downloading the first (2.24 OTA) open up the zip and find the firmware.zip file. Open the firmware.zip and extract the recovery.img file from it. This file is your stock recovery. You flash it like you did your custom recovery by placing it in your ADB/Fastboot folder. Here are the steps:
In bootloader/FASTBOOT USB:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Relock your bootloader with this command in FASTBOOT USB: fastboot oem lock
You can follow the steps in this post on Manually Installing OTAs.
Please read everything at least twice. If you don't understand something then don't hesitate to ask!
uuu91 said:
hey I want to update my htc one to 4.4 and get rid of twrp.
I´ve unlocked it via htcdev and installed twrp.
i have got s-on
hboot 1.54.0000
CID vodap120 (as far as i know this is still the orginal one)
can I just relock the phone or do i need stock recovery? (hop I´m useing the coreced terms here :/ )
if so can I follow this guide http://forum.xda-developers.com/showthread.php?t=2545227.
I remeber that I had to download some drivers when I unlocked the phone and I dont think that they are still on my computer. could someone send me a link to them?
thanks
joachim (austria)
Click to expand...
Click to collapse
much simpler way, as unlocking the bootloader deletes some files required to update, just leave twrp on your phone for the time being, and download this rom ive linked below, if your phone is currently booting up, then just plug it into the computer and move the zip file to your internal storage, then reboot into recovery and install it like you would do with any other rom, during the aroma installer, select wipe data, install stock recovery and install stock radio, upon reboot, you couldn't be anymore stock.
http://www.htc1guru.com/dld/guru_reset_m7_2-24-161-1-zip/
guru reset stock rom 2.24.161.1 Vodafone for the following devices:
modelid: PN0710000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAPE17
cidnum: VODAP405
cidnum: VODAP304
cidnum: VODAPD18
cidnum: VODAP120
cidnum: VODAP110
I´ll follow your guide majmoz
why should i relock bootloader if unlocked doesnt matter?
thank you Seanie280672 but this sounds more complicated to me
i cant download that 2.24.161.1 OTA
error server cannot send any data
now i can.
so lets get started
fuuu
my antivirus tells me that one file in there is a virus.
is this serious?
what shell i do?
Hello, as title says, I need help with going back to stock. I bought this phone super cheap (120€) from some german guy. It works like a charm, but my native language is nowhere so I decided to root and use morelocale2. But when I root I can't update. I already relocked bootloader.
Now I need to pick up right (RUU?), but I just can't understand it.
Radio-4T.27.3218.14
HBOOT-1.57.0000
OS-5.11.401.10
I wondered if I can use http://forum.xda-developers.com/showthread.php?t=2753631 , but it's called firmware so i don't know if it's ota or ruu, or i need to use that stock firmware downwards or am I completely wrong?
Thanks for all responses, cheers
There is no RUU available for your phone version If your phone is S Off then you can flash 4.19.401.9 RUU
If not then you have to restore nandroid backup or flash stock Rom reset according to your software version
yatindroid said:
There is no RUU available for your phone version If your phone is S Off then you can flash 4.19.401.9 RUU
If not then you have to restore nandroid backup or flash stock Rom reset according to your software version
Click to expand...
Click to collapse
Thank you for your reply, I don't think I can restore nandroid backup, because I didn't make any and if If my only choice is to flash stock rom, will you please write me noob friendly tutorial? Thank you.
kajman007 said:
Thank you for your reply, I don't think I can restore nandroid backup, because I didn't make any and if If my only choice is to flash stock rom, will you please write me noob friendly tutorial? Thank you.
Click to expand...
Click to collapse
Check out this site, it has both a stock rom and nandroid. Follow the OP it has the instructions.
majmoz said:
Check out this site, it has both a stock rom and nandroid. Follow the OP it has the instructions.
Click to expand...
Click to collapse
I just can't understand it.. it's too much advanced..I need noob friendly tut.. I don't even know what method should I use. I'm sick of android 4.4.2 it's so slow and lagging..not talking about battery. Please Halp
kajman007 said:
I just can't understand it.. it's too much advanced..I need noob friendly tut.. I don't even know what method should I use. I'm sick of android 4.4.2 it's so slow and lagging..not talking about battery. Please Halp
Click to expand...
Click to collapse
unlock bootloader
flash twrp recovery 2.6.3.3
download and save the zip from method 1 in your adb/fastboot folder
with your phone in recovery, push the zip to your /sdcard either by using adb push or adb sideload
install the zip on your phone using twrp recovery
choose yes to wipe/stock recovery/stock radio
reboot phone
download and install ota
enjoy your phone
and btw there is not much difference between 4.4.2 and 4.4.3, only some security fixes and a crappy file manager.
kajman007 said:
I just can't understand it.. it's too much advanced..I need noob friendly tut.. I don't even know what method should I use. I'm sick of android 4.4.2 it's so slow and lagging..not talking about battery. Please Halp
Click to expand...
Click to collapse
Just what do you want to do? I see you relocked your bootloader. Do you still have a custom recovery installed? Post a fastboot getvar all (except imei and serialno).
majmoz said:
Just what do you want to do? I see you relocked your bootloader. Do you still have a custom recovery installed? Post a fastboot getvar all (except imei and serialno).
Click to expand...
Click to collapse
Yes, I have Cwm.
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.11.401.10
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__102
battery-status: good
battery-voltage: 3817mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
alray said:
unlock bootloader
flash twrp recovery 2.6.3.3
download and save the zip from method 1 in your adb/fastboot folder
with your phone in recovery, push the zip to your /sdcard either by using adb push or adb sideload
install the zip on your phone using twrp recovery
choose yes to wipe/stock recovery/stock radio
reboot phone
download and install ota
enjoy your phone
and btw there is not much difference between 4.4.2 and 4.4.3, only some security fixes and a crappy file manager.
Click to expand...
Click to collapse
I've done it, not sure if it is right, but I still have 4.4.2. Tried to install new update, but my phone was reset and android is still on 4.4.2.. any suggestions? (I didnt watch the installation - I don't want to any more My phone just got like factory reset?)
kajman007 said:
I've done it, not sure if it is right, but I still have 4.4.2. Tried to install new update, but my phone was reset and android is still on 4.4.2.. any suggestions? (I didnt watch the installation - I don't want to any more My phone just got like factory reset?)
Click to expand...
Click to collapse
search for ota and install it
alray said:
search for ota and install it
Click to expand...
Click to collapse
So I can't install updates right from the phone? I have to download OTA from internet and I'll be installing it like installing zip from sd card. Am I right?
kajman007 said:
So I can't install updates right from the phone? I have to download OTA from internet and I'll be installing it like installing zip from sd card. Am I right?
Click to expand...
Click to collapse
settings ---> about ---> software updates
kajman007 said:
So I can't install updates right from the phone? I have to download OTA from internet and I'll be installing it like installing zip from sd card. Am I right?
Click to expand...
Click to collapse
You should be able to download the OTA from the phone. However, you may have some missing files that the OTA will be looking to update. In the post where you got the ROM towards the bottom is a preload file zip. If you need them this is where you can get them to complete the update.
majmoz said:
You should be able to download the OTA from the phone. However, you may have some missing files that the OTA will be looking to update. In the post where you got the ROM towards the bottom is a preload file zip. If you need them this is where you can get them to complete the update.
Click to expand...
Click to collapse
I don't think I'm missing some files. I didn't install the aroma zip with TWRP, I installed them with CWM. Successful. But when I tried to install software update, my phone reset, I didn't watch the installation, but when phone booted, it had setup screen on it. I'm currently downloading a 4.4.3 OTA so we'll see.
EDIT: Downloaded OTA, put in sdcard, trying to boot into recovery, phone automatically boot to ota install, instead of green, it's red and after a while back to android. Im hopeless guys, I think i'll live with 4.2.2 and let someone more experienced and more skilled let this do.
kajman007 said:
I don't think I'm missing some files. I didn't install the aroma zip with TWRP, I installed them with CWM. Successful. But when I tried to install software update, my phone reset, I didn't watch the installation, but when phone booted, it had setup screen on it. I'm currently downloading a 4.4.3 OTA so we'll see.
EDIT: Downloaded OTA, put in sdcard, trying to boot into recovery, phone automatically boot to ota install, instead of green, it's red and after a while back to android. Im hopeless guys, I think i'll live with 4.2.2 and let someone more experienced and more skilled let this do.
Click to expand...
Click to collapse
you can not apply ota manually from stock recovery with s-on. go in settings --> about --> software update
First time you did, your phone performed a factory reset right? This happen sometimes when re-installing stock recovery. just apply the ota again from settings --> about --> software updates.
then if you get a red triangle with an exclamation mark inside, hold vol+ and press power then release both and you should see some text in yellow. post the text if it fail.
alray said:
you can not apply ota manually from stock recovery with s-on. go in settings --> about --> software update
First time you did, your phone performed a factory reset right? This happen sometimes when re-installing stock recovery. just apply the ota again from settings --> about --> software updates.
then if you get a red triangle with an exclamation mark inside, hold vol+ and press power then release both and you should see some text in yellow. post the text if it fail.
Click to expand...
Click to collapse
Tried to update again and SUCCESS! You've got my big thanks