I have installed CyanogenMod10 and want to return to the the original factory image. All my attempts have failed.
I receive the mesage "Hboot Version is older!" then " Update Fail!"
I have extracted the RUU ROM.zip file and tried to upload manually but all my attempts fails.
Any help how to proceed will be appreciated
Moved to Q&A. Please ask all questions there.
romah1 said:
I have installed CyanogenMod10 and want to return to the the original factory image. All my attempts have failed.
I receive the mesage "Hboot Version is older!" then " Update Fail!"
I have extracted the RUU ROM.zip file and tried to upload manually but all my attempts fails.
Any help how to proceed will be appreciated
Click to expand...
Click to collapse
That is possile if the RUU is older than the one currently on your phone. If this is not the case, try to flash the RUU via the program and from hboot.
Ken-Shi_Kun said:
That is possile if the RUU is older than the one currently on your phone. If this is not the case, try to flash the RUU via the program and from hboot.
Click to expand...
Click to collapse
Obviously , since I have Cyanogenmod 10 installed the RUU version is older. CM10 is somehow preventing the RUU to execute correctly,
I have tried to run the RUU with Hboot but it didn't recognized the phone.
your backup is older than the bootloader version now you have .
Sent from my HTC T320e using xda premium
romah1 said:
Obviously , since I have Cyanogenmod 10 installed the RUU version is older. CM10 is somehow preventing the RUU to execute correctly,
I have tried to run the RUU with Hboot but it didn't recognized the phone.
Click to expand...
Click to collapse
Sorry I will be clearer. The ruu has two thing before start. It evaluates your cid and hboot version. If you had (my example here) a 2.22 stock and you want to flash the ruu of the 2.02 version it will not work because the hboot in your phone is newer. This is a security measurement for you not to be able to downgrade your os.
Even more, ruu needs stock recovery, stock kernel, and the phone to be either "locked" or "relocked". And more, if you has custom is on the phone that time, the ruu will only work from fastboot usb mode.
It is a joke tough that in these phones unlock and custom os is easily achivable, while going back to stock is like a pain in the ass.
Sent from my CM10 One V
Related
I've restored successfully using RRU a couple of times using UK TMO images but I'm no longer able to.
What I did was RRU an image and then OTA update to a version which is unavailable as a RRU. It's currently bricked I just see the pink circle although I can get to the bootloader via power-back (although not via power-vol down oddly).
I think the RRU isn't allowing downgrade now. Is there anyway of either forcing the Windows RRU updater to ignore version or flash more directly?
Enter recovery and flash a stock rooted Rom then ruu it
Or enter fastboot plug phone in then run ruu as administrator
Sent from my HTC Desire using XDA Premium App
I lost recovery it just goes to the pink circle. I only have bootloader.
And I can't run RUU on any of the available UK T-Mobile images without error.
gruntling said:
I lost recovery it just goes to the pink circle. I only have bootloader.
And I can't run RUU on any of the available UK T-Mobile images without error.
Click to expand...
Click to collapse
Hmm. If you have s-off, can you try to flash recovery via fastboot, then wipe everything and flash rom of choice? Never done that but I think my logic is good?
What is long hex code for goldcard?
I think the issue with my failing RUU update is that I have 2.12.110.4 and there isn't a RUU for T-Mobile for that version -- the last is 1.12.110.4 and RUU gives error "error 140 bootloader version error".
I've tried the OTA update as a PB99IMG.ZIP via fastboot but that doesn't work. I assume the ZIPs are signed and I can't mix the RUU extracted rom and OTA.
I think my best option is a goldcard but I don't have access to read the long hex CID from the phone.
I can see cid::T-MOB005 from fastboot.exe oem boot. Is there any way of translating that to the long hex code?
gruntling said:
I think the issue with my failing RUU update is that I have 2.12.110.4 and there isn't a RUU for T-Mobile for that version -- the last is 1.12.110.4 and RUU gives error "error 140 bootloader version error".
I've tried the OTA update as a PB99IMG.ZIP via fastboot but that doesn't work. I assume the ZIPs are signed and I can't mix the RUU extracted rom and OTA.
I think my best option is a goldcard but I don't have access to read the long hex CID from the phone.
I can see cid::T-MOB005 from fastboot.exe oem boot. Is there any way of translating that to the long hex code?
Click to expand...
Click to collapse
This may help I think:
http://forum.xda-developers.com/archive/index.php/t-921398.html
I have the latest OTA update and using ruu file was able to downgrade to an earlier version of GB which I guess was the leaked one. I tried to go back an earlier ruu (RUU_Vivo_W_VERIZON_WWE_1.34.605.3_Radio_0.99.01.02 25_2_NV_VZW1.92_release_181303_signed) but it gave me an error about the bootloader.I have not had S-Off or root done to the phone and is just stock.
I would like to go back to the original ruu/image that was shipped with the DINC2. In worst case I will just apply the latest ruu that is the same as the latest ota.
Any suggestions?
thx
just rename any RUU to PG32IMG.zip and put onr oot of sd card and flash in hboot. since it's signed HTC you don't need root.
Were you able to do this successfully?
Sent from my ADR6350 using XDA App
andybones said:
just rename any RUU to PG32IMG.zip and put onr oot of sd card and flash in hboot. since it's signed HTC you don't need root.
Click to expand...
Click to collapse
In HBOOT I see the message saying its Loading pg32img.zip then after awhile it says it is checking pg32img.zip and then returns back to the Main screen where you can choose fastboot, recovery etc.
After booting phone backup, I attempted again to run the ruu form from windows pc and got this error "ERROR[140]:BOOTLOADER VERSION ERROR"
Hi,
I'm trying to restore from custom rom to stock rom.
My phone is CID ORANG216 and I'm using xx.xx.65.xx RUU releases.
I have 2 relevant files:
The RUU exe - RUU_ENDEAVOR_U_ICS_40_S_Orange_CH-Generic_2.17.65.2_Radio_2.1204.135.20_release_275590_signed.exe
OTA UPDATE for the device - OTA_ENDEAVOR_U_JB_45_S_Orange_CH-Generic_3.16.65.2-2.17.65.2_release_296426gf2xgpisn8xs0fti
After flashing the stock recovery, boot_signed.img, rebootRUU, the RUU update fails because of version failure, I suspect that the HBOOT version is the trouble maker.
My phone is unlocked with S-ON with HBOOT 1.36 and the HBOOT in the RUU is 1.12 .
Due to S-ON I cant change the hboot.
I can't seem to find a workaround for it and install the RUU.
Any ideas??
I even thought about compiling the latest JB release from htcdev development center and flash it...
hanochg said:
Hi,
I'm trying to restore from custom rom to stock rom.
My phone is CID ORANG216 and I'm using xx.xx.65.xx RUU releases.
I have 2 relevant files:
The RUU exe - RUU_ENDEAVOR_U_ICS_40_S_Orange_CH-Generic_2.17.65.2_Radio_2.1204.135.20_release_275590_signed.exe
OTA UPDATE for the device - OTA_ENDEAVOR_U_JB_45_S_Orange_CH-Generic_3.16.65.2-2.17.65.2_release_296426gf2xgpisn8xs0fti
After flashing the stock recovery, boot_signed.img, rebootRUU, the RUU update fails because of version failure, I suspect that the HBOOT version is the trouble maker.
My phone is unlocked with S-ON with HBOOT 1.36 and the HBOOT in the RUU is 1.12 .
Due to S-ON I cant change the hboot.
I can't seem to find a workaround for it and install the RUU.
Any ideas??
I even thought about compiling the latest JB release from htcdev development center and flash it...
Click to expand...
Click to collapse
You need to relock the bootloader to use install RUU . It has nothing to do with hboot . Just take note that you have to use the RUU that is on the same build or higher .
chaun1308 said:
You need to relock the bootloader to use install RUU . It has nothing to do with hboot . Just take note that you have to use the RUU that is on the same build or higher .
Click to expand...
Click to collapse
doesn't work... I'm getting "Error [140]: BOOTLOADER VERSION ERROR"
The only RUU exe available is the one i mentioned and its old
I don't know how to use the OTA file without the original stock rom already installed...
if it helps anything the command "fastboot getvar version-main" on my device gives:
version-main: 3.16.65.2
hanochg said:
doesn't work... I'm getting "Error [140]: BOOTLOADER VERSION ERROR"
The only RUU exe available is the one i mentioned and its old
I don't know how to use the OTA file without the original stock rom already installed...
if it helps anything the command "fastboot getvar version-main" on my device gives:
version-main: 3.16.65.2
Click to expand...
Click to collapse
Like I mentioned . You have to look for the version that's the same with yours or higher to use the RUU . I guess you can't go back to stock until you find the RUU of your version or higher . Maybe you could try a stock ROM nand backup ?
Here are stock backups
http://forum.xda-developers.com/showthread.php?t=1975140
Thanks for the help
my version or CID is not there, any other resource for nands?
Just lock your bootloader using fastboot oem lock and run this RUU with admin privileges..
http://bugsylawson.com/files/file/4...2-radio-51204163r30-release-296363-signedexe/
What error do you get when you do this?
twelve cdrtutt
vin4yak said:
Just lock your bootloader using fastboot oem lock and run this RUU with admin privileges..
ht tp://bugsylawson.com/files/file/412-ruu-endeavor-u-jb-45-s-orange-ch-generic-316652-radio-51204163r30-release-296363-signedexe/
What error do you get when you do this?
Click to expand...
Click to collapse
OMG that's the file I've been looking for 2 days!!!!
worked like a charm, you're my hero for the day! :victory:
hanochg said:
OMG that's the file I've been looking for 2 days!!!!
worked like a charm, you're my hero for the day! :victory:
Click to expand...
Click to collapse
Great!!
can someone put a valid link for that ruu.the site is offline now and i can't finde a valid link to download.
only1 said:
can someone put a valid link for that ruu.the site is offline now and i can't finde a valid link to download.
Click to expand...
Click to collapse
uploaded it again:
h ttp://we.tl/Spg5YhElwV
hanochg said:
uploaded it again:
h ttp://we.tl/Spg5YhElwV
Click to expand...
Click to collapse
worked perfect.thx man you're the best!!!
so, people told me that i can get stock kernel within any custom roms, but where can i get the modules? and can any one tell me some kernels which feature the battery saver? im not asking which is the best since its against the rules, just give me some and ill try them myelf, thanks alot
SilverTattoo said:
so, people told me that i can get stock kernel within any custom roms, but where can i get the modules? and can any one tell me some kernels which feature the battery saver? im not asking which is the best since its against the rules, just give me some and ill try them myelf, thanks alot
Click to expand...
Click to collapse
I don't think your questions relate to the subject here.
Anyway, custom roms are based on the stock rom and most of the times include a file called firmware.zip, look it up in the costum_rom.zip file.
hboot updates are tricky on this device and for upgrading it (from ICS to JB supported hboot) you need a special firmware built for your specific htc one x model (look at the manuals for more instructions).
For the battery saving, I think it depends on the rom you install and not the kernel (or maybe both because they come together?), check out for old posts about that issue, I'm sure its not the first time someone asks about it.
hope it helps
Hello! hopefully someone can help me I stand
I commented:
I have a Verizon One with hboot 1.54, yesterday I managed to unlock the bootloader and make S-off, then I take on the task of putting the HTC_304 cid (Spain) and try to load an official stock RUU rom but always gave me Error 158 , then switch to Super-CID but I continued to set the same mistake and then make the decision to install recovery and change to HBOOT 1.44, I download the latest methyl Revolution and by recovery, made the installation complete without errors, but me no system load.
The bootloader and fastboot also enter without problem and recovery, but I can not enter recovery to sd, tells me that he can not mount and went back to try to load the rom by RUU but I always get the same error (158).
Hopefully someone can help me and do not know what else to do
Well, you need to use only Verizon firmwares for this device. You can't load an ruu from another device. It won't match up and therefore either not work or worse, brick your phone.
Sent from my SCH-I535 using Tapatalk 4
If I've helped, please hit the thanks button
tylerlawhon said:
Well, you need to use only Verizon firmwares for this device. You can't load an ruu from another device. It won't match up and therefore either not work or worse, brick your phone.
Sent from my SCH-I535 using Tapatalk 4
If I've helped, please hit the thanks button
Click to expand...
Click to collapse
then to have put the Super-Cid and 1.44 hboot not give me the freedom to put a European rom?
to be so I have to go back to hboot 1.54 and install an official RUU from Verizon?
The only way I can think is metiante cmd roms charge with all-in-one, through the RUU, but I always get this error.
ak074 said:
what RUU are you trying to use and where did you get it?
Click to expand...
Click to collapse
I've been trying to get this
http://forum.xda-developers.com/show....php?t=2485319 (Deodexed Full ROM version: 1.10.605.10)
I do it with the application all-in-one and the factory ruu flash zip option, correct?
maybe try with the new hboot posted by rumrunner?
I believe it is ENG hboot
Once superCID you should be able to flash any RUU..
are you doing it using FastbootRUU??
Hi people, this is my first time posting on a forum. I've always fixed my problem by googling them but now i failed.
I fixed the problem mentioned in the title and now i'm back to the original problem.
I followed a guide on the web to root my HTC 10. What i did was unlocking the bootloader and then flashing TWRP and till then things went good.
Then i tried to root it by flashing superSU and after that my phone went in bootloop and i found out i didnt have a system image anymore.
I tried to flash the RUU with my cid but i got the following error "RU_MAIN_VER_FAIL...".
This is my situation:
-i can access download, recovery and bootloader
-I've TWRP installed and my internal storage is blank, it only has an empty TWRP folder.
-My external memory has the following folders: Android, TWRP, .android_secure, LOST.DIR
What is my problem? I even tried to restore a TWRP backup without succeeding from https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Please help me!!
rorou said:
Hi people, this is my first time posting on a forum. I've always fixed my problem by googling them but now i failed.
I fixed the problem mentioned in the title and now i'm back to the original problem.
I followed a guide on the web to root my HTC 10. What i did was unlocking the bootloader and then flashing TWRP and till then things went good.
Then i tried to root it by flashing superSU and after that my phone went in bootloop and i found out i didnt have a system image anymore.
I tried to flash the RUU with my cid but i got the following error "RU_MAIN_VER_FAIL...".
This is my situation:
-i can access download, recovery and bootloader
-I've TWRP installed and my internal storage is blank, it only has an empty TWRP folder.
-My external memory has the following folders: Android, TWRP, .android_secure, LOST.DIR
What is my problem? I even tried to restore a TWRP backup without succeeding from https://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
Please help me!!
Click to expand...
Click to collapse
Grab an ruu that is at least at the same version you are, or flash a custom rom from twrp
Tarima said:
Grab an ruu that is at least at the same version you are, or flash a custom rom from twrp
Click to expand...
Click to collapse
thank you for your reply! i tried already a ruu solution with the version of my cid but it didnt workout. You're saying i need to install a custom rom and then revert back to stock?
rorou said:
thank you for your reply! i tried already a ruu solution with the version of my cid but it didnt workout. You're saying i need to install a custom rom and then revert back to stock?
Click to expand...
Click to collapse
No I meant you can flash a custom rom instead of stock. If you want stock you'll have to run a stock ruu. What's your current software number and which ruu are you trying to run?
Tarima said:
No I meant you can flash a custom rom instead of stock. If you want stock you'll have to run a stock ruu. What's your current software number and which ruu are you trying to run?
Click to expand...
Click to collapse
I've used this ruu 1.90.401.5 that has same mid and cid as my phone. And before wiping my internaL storage i had nougat, 7.0 i think. This ruu thing is really twisting my mind, never heard about it before today... maybe that's because i got in trouble. I've installed viper and the phone seems to work now but i have my doubts on whether to keep it or not. I'll try this so rom for a week, i want to see if it has battery or overheating issues.
But in case i wanted to go back to stock, i dont know what went wrong and why the ruu i've picked failed to install even if it had the same cid and mid.
rorou said:
I've used this ruu 1.90.401.5 that has same mid and cid as my phone. And before wiping my internaL storage i had nougat, 7.0 i think. This ruu thing is really twisting my mind, never heard about it before today... maybe that's because i got in trouble. I've installed viper and the phone seems to work now but i have my doubts on whether to keep it or not. I'll try this so rom for a week, i want to see if it has battery or overheating issues.
But in case i wanted to go back to stock, i dont know what went wrong and why the ruu i've picked failed to install even if it had the same cid and mid.
Click to expand...
Click to collapse
If you had Nougat before, that means your firmware version is 2.x.x.x. This is newer than the ruu you're trying to flash. You can only run an ruu that is at the same version as or above your current firmware version, and you cannot downgrade. That's what I mean by "run an ruu that's the same version as your phone."
Get your software info by doing fastboot getvar all from download mode. Then find an ruu that is for your CID/mid and at the same or higher version that you have. That'll take you to stock.
Tarima said:
If you had Nougat before, that means your firmware version is 2.x.x.x. This is newer than the ruu you're trying to flash. You can only run an ruu that is at the same version as or above your current firmware version, and you cannot downgrade. That's what I mean by "run an ruu that's the same version as your phone."
Get your software info by doing fastboot getvar all from download mode. Then find an ruu that is for your CID/mid and at the same or higher version that you have. That'll take you to stock.
Click to expand...
Click to collapse
That explains everything! thank you so much!!!