Related
Hi,
Unlocked my wife's Legend using the HTC-Dev method. Installed CM7 and she was happy... Now she is missing the HTC weather animations and wants to go back to the stock Froyo.
I have the correct RUU for her phone, carrier, and region, extracted from:
RUU_Legend_BellMobility_WWE_2.02.666.3_Radio_47.37.35.09_7.08.35.05_release_130094_signed.exe
First I tried to flash by renaming the rom.zip to LEGEIMG.zip. The bootloader saw it and chewed on it for a while, but the RUU ended up not being applied and the phone booted back into CM. Confusing.
Next attempt: fastboot, with bootloader unlocked.
Code:
[[email protected] ruu]# [B]fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.258s]
finished. total time: 0.258s
[[email protected] ruu]# [B]fastboot oem rebootRUU[/B]
...
OKAY [ 0.017s]
finished. total time: 0.017s
[[email protected] ruu]# [B]fastboot flash zip rom.zip[/B]
sending 'zip' (124420 KB)...
OKAY [ 12.795s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
[B]FAILED (remote: 99 unknown fail)[/B]
finished. total time: 18.643s
Did some more reading, found that RUUs only apply when the bootloader is locked. So I relocked the bootloader with fastboot oem lock and tried again:
Code:
[[email protected] ruu]# [B]fastboot erase cache[/B]
< waiting for device >
erasing 'cache'...
OKAY [ 0.258s]
finished. total time: 0.258s
[[email protected] ruu]# [B]fastboot oem rebootRUU[/B]
...
OKAY [ 0.017s]
finished. total time: 0.017s
[[email protected] ruu]# [B]fastboot flash zip rom.zip[/B]
sending 'zip' (124420 KB)...
OKAY [ 12.874s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
[B]FAILED (remote: 43 main version check fail)[/B]
finished. total time: 44.062s
And trying the LEGEIMG.zip method after relocking:
Code:
Main version is older!
Update Fail!
Do you want to reboot device?
Here are my bootvars:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.0000
(bootloader) version-baseband: 7.13.35.13
(bootloader) version-cpld: None
(bootloader) version-microp: 0816
(bootloader) version-main: 3.30.0.0
(bootloader) serialno: HT05NRA07XX
(bootloader) imei: XXXXX
(bootloader) product: legend
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PB7611000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-39ec9098
(bootloader) hbootpreupdate: 11
Apparently this means that I'm trying to flash an RUU that is older than what is on the device. The problem is, the RUU update that I last applied was the HTCDev one to allow unlocking. So the most recent "full" RUU is older than the HTCDev RUU and I can't seem to downgrade.
Am I missing something? I must be missing something. Please help, or the wife will have one up on me. Can't allow that
Hello,
try this ROM from BlaY0, its an improved stock ROM and you keep root.
When I remember right, there was no version check during installation, you can install it with Clockwork mode Recovery.
alligator_asl said:
Hello,
try this ROM from BlaY0, its an improved stock ROM and you keep root.
Click to expand...
Click to collapse
Thanks, that's an acceptable workaround for now. I ended up going this route. Since CWM 5.X doesn't like "amend" scripting, it took some doing though. :highfive:
If anyone knows of a way to downgrade to a stock RUU after applying the HBOOT 1.02 RUU to the Legend, that would be a help.
I'd suggest if you really need to go back stock froyo it can't be done with hboot 1.02, I have tried various different methods with no success.
I can't remember who, but some where on legend forums (I think in the dev section) there is a method to downgrade back to hboot 1.01, if it works you can do it and flash ruu. I can't confirm if it works or not.
Sent from my Legend using xda app-developers app
ranger4740 said:
I can't remember who, but some where on legend forums (I think in the dev section) there is a method to downgrade back to hboot 1.01, if it works you can do it and flash ruu. I can't confirm if it works or not.
Click to expand...
Click to collapse
Yeah, that sounds right.
So for anyone reading this thread in the future, if you've unlocked your bootloader using HTC-dev you will be unable to return to stock Froyo using an official RUU without first downgrading to HBOOT 1.01 or older.
The HBOOT downgrade process is pretty involved. You need a goldcard and the hack4legend kit. See this thread for details.
And for good measure, here's a thread with someone else working out the same problem we just worked out here... :silly:
At the end of the day, if you ran a nandroid backup of your stock ROM before blowing it away, you won't need all this jazz.
ariaxu said:
Since CWM 5.X doesn't like "amend" scripting, it took some doing though.
Click to expand...
Click to collapse
You can take an older Versin of CWM ( recovery-clockwork-2.5.0.7-legend.zip ), ther are no problems with scripting, a google search brings several results.
If necessary, you lan load the old version of CWM from the new version and then you can flash this ROM !
I rooted my phone this morning, and attempted to install cm10. the screen became inop. so I tried a recovery and it put it into boot loop. I have relocked the phone and tried some RUUs but all come back with bootloader, or signature errors, I have tried fuses method as well to no avail all i end up getting is this:
C:\Users\Downloads>fastboot flash zip RUU.zip
sending 'zip' (659905 KB)...
OKAY [ 27.926s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 106.089s
Boot Screen:
*tampered
*relocked
s on
hboot 2.09
radio 1.12.11.1210
opendsp-v31.1.45.0815
eMMC-boot
Any help would be appreciated
beamer1341 said:
I rooted my phone this morning, and attempted to install cm10. the screen became inop. so I tried a recovery and it put it into boot loop. I have relocked the phone and tried some RUUs but all come back with bootloader, or signature errors, I have tried fuses method as well to no avail all i end up getting is this:
C:\Users\Downloads>fastboot flash zip RUU.zip
sending 'zip' (659905 KB)...
OKAY [ 27.926s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 106.089s
Boot Screen:
*tampered
*relocked
s on
hboot 2.09
radio 1.12.11.1210
opendsp-v31.1.45.0815
eMMC-boot
Any help would be appreciated
Click to expand...
Click to collapse
the remote: 43 main version check fail is due to you using a RUU that is less than the current build you have on your phone.
have you tried this one from unlimited.io?
and try flashing it using these commands:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU.zip
if that fails you can always unlock, reflash TWRP and flash the stock OTA here
rawintellect said:
the remote: 43 main version check fail is due to you using a RUU that is less than the current build you have on your phone.
have you tried this one from unlimited.io?
and try flashing it using these commands:
fastboot erase cache
fastboot oem rebootRU
fastboot flash zip RUU.zip
if that fails you can always unlock, reflash TWRP and flash the stock OTA here
Click to expand...
Click to collapse
C:\Users\Branden\Downloads>fastboot flash zip RUU.zip
sending 'zip' (659905 KB)...
OKAY [ 28.334s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 107.645s
Same error. Gonna have to try unlock
Resolved
Ended up having to run mean bean but its fully operative I think the kernels were messed up.
beamer1341 said:
Ended up having to run mean bean but its fully operative I think the kernels were messed up.
Click to expand...
Click to collapse
how did you resolve this?
sk8dayfuknight said:
how did you resolve this?
Click to expand...
Click to collapse
If you are on the latest OTA 3.16.651.3 you can't run any CM,AOSP,AOKP roms 3.16 had a touch panel drivers update and those roms are based on the 3.15 touch panel drivers
bigdaddy619 said:
If you are on the latest OTA 3.16.651.3 you can't run any CM,AOSP,AOKP roms 3.16 had a touch panel drivers update and those roms are based on the 3.15 touch panel drivers
Click to expand...
Click to collapse
You can run them but your touch screen won't work
Sent from my EVO using xda premium
sk8dayfuknight said:
how did you resolve this?
Click to expand...
Click to collapse
Get s off...
Downgrade tp drivers
Flash cm
Profit? :what::what:
Flowed from my Jewel using Tapatalk 2
Hello,
How do I upgrade my Radio on my DNA. The screenshots shows what I have in my bootloader screen. Please help me. Thanks
Trying to flash
envy270 said:
Hello,
How do I upgrade my Radio on my DNA. The screenshots shows what I have in my bootloader screen. Please help me. Thanks
Click to expand...
Click to collapse
This is what I get when I am trying to flash firmware:
C:\android-sdk-windows\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (33119 KB)...
OKAY [ 2.587s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.799s
I'm fourteen, so ignore any absence of knowledge about any of this. I'm using a stock, non-rooted DNA running android 4.4.2.
So, I've been spending today trying to unlock my DNA's bootloader. I found this nifty program Moonshine, so I decided to use it. On the forum post for the moonshine it told me in order to use it for the DNA I had to flash the 2.06 firmware. This is what it gave me...
c:\Android\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.041s
c:\Android\sdk\platform-tools>fastboot flash zip dna2.06firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (33119 KB)...
OKAY [ 2.664s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 8.543s
So, any help would be appreciated.
In DNA General, there is a thread titled, "Am I too late to root", it has all the info you will need.
Swantexan said:
In DNA General, there is a thread titled, "Am I too late to root", it has all the info you will need.
Click to expand...
Click to collapse
I'll check it out, thanks.
Hi guys, I read thousands of post and didn't found a similar case to mine. This is what happened (sorry for my english, i speak spanish )
I bought my HTC One X+ on eBay believing it was the international version because they sold me unlocked and cleaned, but after flashing a wrong firmware version (thousands of times) I realized that my phone is the AT&T or Telus (evitare_ul) version :crying:
I was so desperate that even I changed the CID (I was S-off). At the beginning had SuperCID, now I have HTC__001 and the worst of all is that I changed the android-info.txt file from these kernels https www androidfilehost (dot) com / ?w=files & flid = 32755 and i flashed.. PUM hboot bricked, I know I'm a fool my fault, i didn't read the warnings.. :crying:
- I trying different RUU for my wrong combination of CID (HTC__001) and modelid: PM631**** and I didn't found.
- I downloaded the source code from htcdev (dot) com / devcenter/ downloads but I don't know what combination i have to do. I need some extra help to build a new firmware for my rare combination of CID, hboot, baseband version and modelid
I need your help please!
I will make a donation through Paypal to the person to help me with this. :fingers-crossed:
Summarize:
Code:
version-bootloader: 1.72.0000
version-baseband: 3.1204.171.33 (for my country we use GSM and UMTS 850/1900 Mhz)
version-main: 1.15.502.9
serialno: HT2BRW302088
product: evitare_ul
platform: HBOOT-T30S
modelid: PM631****
cidnum: HTC__001
battery-status: low
battery-voltage: 3598mV
devpower: 6
partition-layout: None
security: on
build-mode: SHIP
boot-mode: RUU
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Let me know if you need anything else.
Any help would be greatly appreciated.
Thanks!
jcaballero said:
Hi guys, I read thousands of post and didn't found a similar case to mine. This is what happened (sorry for my english, i speak spanish )
I bought my HTC One X+ on eBay believing it was the international version because they sold me unlocked and cleaned, but after flashing a wrong firmware version (thousands of times) I realized that my phone is the AT&T or Telus (evitare_ul) version :crying:
I was so desperate that even I changed the CID (I was S-off). At the beginning had SuperCID, now I have HTC__001 and the worst of all is that I changed the android-info.txt file from those kernel https www androidfilehost (dot) com / ?w=files & flid = 32755 and i flashed.. PUM hboot bricked, I know I'm a fool my fault, i didn't read the warnings.. :crying:
- I trying different RUU for my wrong combination of CID (HTC__001) and modelid: PM631**** and I didn't found.
- I downloaded the source code from htcdev (dot) com / devcenter/ downloads but I don't know what combination i have to do. I need some extra help to build a new firmware for my rare combination of CID, hboot, baseband version and modelid
I need your help please!
I will make a donation through Paypal to the person to help me with this. :fingers-crossed:
Summarize:
Code:
version-bootloader: 1.72.0000
version-baseband: 3.1204.171.33 (for my country we use GSM and UMTS 850/1900 Mhz)
version-main: 1.15.502.9
serialno: HT2BRW302088
product: evitare_ul
platform: HBOOT-T30S
modelid: PM631****
cidnum: HTC__001
battery-status: low
battery-voltage: 3598mV
devpower: 6
partition-layout: None
security: on
build-mode: SHIP
boot-mode: RUU
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Let me know if you need anything else.
Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
Breathe...
first up you need to charge the device, once you've done that grab one of the EVITAREUL the AT&T rom's and recoveries and flash them.
Sorted.
FAILED (remote: 12 signature verify fail)
Thanks for response, I charged my phone and I tried flashing these firmware (from forum.xda-developers com / showthread.php?t=2235248) but i got an error
Code:
C:\adb>fastboot flash zip RUU_EVITARE_UL_JB_45_Cingular_US_1.19.502.1_Odexed.zip
sending 'zip' (609633 KB)...
OKAY [ 77.719s]
writing 'zip'...
(bootloader) signature checking...
[B]FAILED (remote: 12 signature verify fail)[/B]
finished. total time: 104.810s
Code:
C:\adb>fastboot flash zip RUU_EVITARE_UL_JB_45_Telus_WWE_1.20.661.1_Odexed.zip
sending 'zip' (588120 KB)...
OKAY [ 71.639s]
writing 'zip'...
(bootloader) signature checking...
[B]FAILED (remote: 12 signature verify fail)[/B]
finished. total time: 97.739s
Wouldn't it be because my CID is HTC__001 = WWE and mi modelid: PM631****?
Is there a way to change the build.prop from these zip files to match my CID or another info?
Remember: I'm stuck in boot-mode: RUU, can't go to the recovery to unlock and change my CID (like before)
Thanks!:good:
jcaballero said:
Thanks for response, I charged my phone and I tried flashing these firmware (from forum.xda-developers com / showthread.php?t=2235248) but i got an error
Code:
C:\adb>fastboot flash zip RUU_EVITARE_UL_JB_45_Cingular_US_1.19.502.1_Odexed.zip
sending 'zip' (609633 KB)...
OKAY [ 77.719s]
writing 'zip'...
(bootloader) signature checking...
[B]FAILED (remote: 12 signature verify fail)[/B]
finished. total time: 104.810s
Code:
C:\adb>fastboot flash zip RUU_EVITARE_UL_JB_45_Telus_WWE_1.20.661.1_Odexed.zip
sending 'zip' (588120 KB)...
OKAY [ 71.639s]
writing 'zip'...
(bootloader) signature checking...
[B]FAILED (remote: 12 signature verify fail)[/B]
finished. total time: 97.739s
Wouldn't it be because my CID is HTC__001 = WWE and mi modelid: PM631****?
Is there a way to change the build.prop from these zip files to match my CID or another info?
Remember: I'm stuck in boot-mode: RUU, can't go to the recovery to unlock and change my CID (like before)
Thanks!:good:
Click to expand...
Click to collapse
If you can issue fastboot commands, you can issue fastboot flash recovery recovery.img >
Select hboot (ignore the crap that shows up)
Select recovery
You CANNOT flash the modified sense rom's in fastboot as the MD5's or whatever the hboot looks for are wrong, hence the wrong signature.
I tried with two original recovery.img from AT&T, but i get: FAILED (remote: not allowed)
Code:
C:\adb>fastboot flash recovery recovery_signed.img
sending 'recovery' (7500 KB)...
OKAY [ 0.926s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 0.960s
Code:
C:\adb>fastboot flash recovery ATTrecovery.img
sending 'recovery' (8224 KB)...
OKAY [ 1.019s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.040s
I can't flash anything because i'm S-ON, I'm stuck in RUU mode and I think that the only way to revive my phone is with an original RUU.exe (that doesn't exist because i changed my CID) I tried with all these RUU (www androidruu com / ?developer=EvitaRE) and i get the same error about the signature or wrong model.
I don't know if compiling from the source code (www htcdev com / devcenter / downloads) with my requirements would work, but I will pay the person who do that and makes a zip signed or encrypted firmware capable to flash in my phone...
I'm about to buy an used board to replace my f***g bricked HOX+
I don't know what to do. I'm about to give up :crying:
I extracted the rom.zip from this RUU RUU_EVITARE_UL_JB_50_S_Cingular_US_2.15.502.1_Radio_2.21.5517.15_18.27.11.35L_release_341689_signed_0220.exe
Code:
C:\adb>fastboot flash zip rom_01.zip
sending 'zip' (33584 KB)...
OKAY [ 4.109s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) Your memory size = 59640MB, choose rawpt_64g.img
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 6.627s
I want to edit the android-file.txt from the .zip to put my CID HTC_001 (that i changed for fool) but i need to resign or encrypt the zip before flashing again. Is there a tool that do that? I think i'm screwed :crying:
Also, i can't do the same step with this RUU_EVITARE_UL_JB_45_TELUS_WWE_1.15.661.11_Radio_1.09.55.17_18.20.95.55L_release_290307_signed because the zip is corrupted, i downloaded several times
Code:
C:\adb>fastboot flash zip rom.zip
sending 'zip' (669207 KB)...
OKAY [ 81.936s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) time: 4018
(bootloader) rom parsing finish ...
(bootloader) Your memory size = 59640MB, choose rawpt_64g.img
(bootloader) Read zipped android_info fail!
Anyone have the version not corrupted of this RUU? I downloaded the corrupted from www.androidruu.com/?developer=EvitaRE
Thanks!
Are there no other WWE evita ruus you can find? I agree you are probably out of luck, but that would be the only way to fix things that I can think of.
I think, though, you've learned why it's a very bad idea to go back to s-on after modifying your phone. There is no good reason to ever do it, and the risks are large. You changed around a whole bunch of basic settings and firmware, and then locked them down before determining if your phone was stable.
If the ruus don't work, a repair shop with jtag might be able to fix it by flashing the motherboard directly.
Okay, lets just recap.
So you flashed a kernel that was not supported by your model and now the device wont boot. So you tried to flash a ruu, but couldnt find one with your cid. So you changed your cid and re-applied s-on?
So no ruu flash occured?
Just the bad kernel flash?
Then how about this for a plan.
1. htcdev unlock the bootloader.
2. Flash a compatiable custom recovery from your device specific section.
3. Flash a compatiable custom rom for your device, thus making it boot again.
If your hboot has not been damaged ie wrong hboot flashed then a htcdev unlock should work fine. No ruu needed, not that they will work without the mid and cid matching.
Sent from my LG-D802 using Tapatalk
Edited to remove irrelevant data.
Jtag, my last chance
Hi guys, thanks for your help
iElvis, you right, I did things that I didn't know what it was about, I was so desperate.
I'll send my phone to a repair center where use the JTAG. Thanks for the info, I didn't know there was such thing :good:
heavy_metal_man
Yeah, that's the summary of what I did.. but.. I can't go back to the recovery (hboot don't work), i'm stuck in ruu mode (black screen with htc logo), So, I can't unlock de bootloader because I can't go in fastboot mode, I'm S-ON and everything I've tried I get this error: FAILED (remote: not allowed) :crying:
If you know someone (an oriental guy hahaha) that know how to encrypt a modified zip RUU to flash in ruu mode, please let me know
Thanks for everything :good:
Cheers.
jcaballero said:
Hi guys, thanks for your help
iElvis, you right, I did things that I didn't know what it was about, I was so desperate.
I'll send my phone to a repair center where use the JTAG. Thanks for the info, I didn't know there was such thing :good:
heavy_metal_man
Yeah, that's the summary of what I did.. but.. I can't go back to the recovery (hboot don't work), i'm stuck in ruu mode (black screen with htc logo), So, I can't unlock de bootloader because I can't go in fastboot mode, I'm S-ON and everything I've tried I get this error: FAILED (remote: not allowed) :crying:
If you know someone (an oriental guy hahaha) that know how to encrypt a modified zip RUU to flash in ruu mode, please let me know
Thanks for everything :good:
Cheers.
Click to expand...
Click to collapse
Try the command
fastboot reboot-bootloader
To get out of ruu mode.
Sent from my LG-D802 using Tapatalk
heavy_metal_man said:
Try the command
fastboot reboot-bootloader
To get out of ruu mode.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
No man, It brings me back to the ruu mode, i damaged my hboot
Guys, I will try this tool to encrypt the ruu.zip with the modified CID, i'm installing a linux virtual machine.. I will keep you informed...
http://forum.xda-developers.com/showthread.php?t=2199638
Bad news
I re-encrypted a ROM, but I have the same issue about the signature..
"The leading 256 bytes is the signature of the zip file, you'll need to disregard it. There's no way we can sign the zip correctly without HTC's private key"
https://github.com/kmdm/ruuveal/issues/8
Sending to a Jtag repair center...
Cheers