[Q] Trying to downgrade to stock after HTC-Dev unlock... - Legend Q&A, Help & Troubleshooting

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 !

Related

[Q] facepalm s-off problem

I believe I did all the steps correctly but it did not seem to work. May have not done the 'immediate' step quickly enough (fastboot oem boot)? Anyway, i tried it a few more times again without success. I seemed to not be able to write the 3 files equired at the end specifically #2 + 3. Now it says it can't find my fastboot flash zip (I renamed mine soff.zip) but it is there...Thought I would give it and me space for a while before I try again. Anyone with any suggestions?
The soffbin3 is the file inside the zip... You need to pull that file out and flash that the p830000000-dna.zip is the one you leave alone
Sent from my Nexus 7 using XDA Premium HD app
.torrented said:
The soffbin3 is the file inside the zip... You need to pull that file out and flash that the p830000000-dna.zip is the one you leave alone
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Pretty sure I extracted that but will double check, thanks..
rootntootn said:
Pretty sure I extracted that but will double check, thanks..
Click to expand...
Click to collapse
Posting command file here as it did not work again...... I put the zip file and extracted in my working directory not the phone,is that correct? just occured to me that it may need to be on phone sd card anyway below is what got spit out, any help appreciated.
C:\adt-bundle-windows-x86\sdk\platform-tools>adb reboot bootloader
adb server is out of date. killing...
* daemon started successfully *
C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.049s
C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot flash zip soff.zip
sending 'zip' (36905 KB)...
OKAY [ 3.370s]
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: 3.595s
C:\adt-bundle-windows-x86\sdk\platform-tools>fastboot oem boot
...
(bootloader) monarudo_vibrate_device_time(): vibrate 200(ms)...
(bootloader) Boot/Recovery signature checking...
(bootloader) TZ_HTC_SVC_HASH ret = 0
(bootloader) setup_tag addr=0x80600100 cmdline add=0x003147C8
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:skuid 0x32401
(bootloader) TAG:hero panel = 0x94005B
(bootloader) TAG:engineerid = 0x0
(bootloader) TAG: PS ID = 0x0
(bootloader) TAG: Gyro ID = 0x1
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::22222222
(bootloader) serial number: FA2BAS504674
(bootloader) commandline from head: console=ttyHSL0,115200,n8 androidboot
(bootloader) .hardware=dlx user_debug=31
(bootloader) command line length =796
(bootloader) active commandline: poweron_status=1 reset_status=0 board_mo
(bootloader) narudo.disable_uart3=0 diag.enabled=0 board_monarudo.debug_u
(bootloader) art=0 userdata_sel=0 androidboot.emmc=true androidboot.pages
(bootloader) ize=2048 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.td=1 td.s
(bootloader) f=1 td.ofs=328 td.prd=1 td.dly=0 td.tmo=300 hlog.ofs=628 un.
(bootloader) ofs=694 imc_online_log=0 androidboot.efuse_info=SNSL androi
(bootloader) dboot.baseband=1.00.00.1023_3 androidboot.cid=22222222 andro
(bootloader) idboot.devicerev=3 androidboot.batt_poweron=good_battery and
(bootloader) roidboot.carrier=COM
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=local
(bootloader) aARM_Partion[5].name=cache
(bootloader) aARM_Partion[6].name=userdata
(bootloader) aARM_Partion[7].name=devlog
(bootloader) aARM_Partion[8].name=pdata
(bootloader) aARM_Partion[9].name=extra
(bootloader) aARM_Partion[A].name=radio
(bootloader) aARM_Partion.name=adsp
(bootloader) aARM_Partion[C].name=dsps
(bootloader) aARM_Partion[D].name=radio_config
(bootloader) aARM_Partion[E].name=modem_st1
(bootloader) aARM_Partion[F].name=modem_st2
(bootloader) aARM_Partion[10].name=cdma_record
(bootloader) aARM_Partion[11].name=reserve
(bootloader) partition number=18
(bootloader) Valid partition num=18
(bootloader) setting_get_bootmode() = 9
(bootloader) smem 8CF04000 (phy 8CF04000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) TZ_HTC_SVC_DISABLE ret = 205643776 (0xC41E000)
(bootloader) jump_to_kernel: machine_id(4060), tags_addr(0x80600100), ker
(bootloader) nel_addr(0x80608000)
(bootloader) -------------------hboot boot time:156503 msec
FAILED (status read failed (Too many links))
finished. total time: 2.904s
C:\adt-bundle-windows-x86\sdk\platform-tools>
I already see what's wrong..
When you
fastboot flash zip P8300000-DNA.ZIP
you flash that not the soffbin3 file the soffbin3 is for later
Sent from my HTC6435LVW using XDA Premium HD app
.torrented said:
I already see what's wrong..
When you
fastboot flash zip P8300000-DNA.ZIP
you flash that not the soffbin3 file the soffbin3 is for later
Sent from my HTC6435LVW using XDA Premium HD app
Click to expand...
Click to collapse
I did do that, It looks like I didn't because I renamed my P8300000-DNA.ZIP file to soff.zip so I wouldn't have to type all those characters.
rootntootn said:
I did do that, It looks like I didn't because I renamed my P8300000-DNA.ZIP file to soff.zip so I wouldn't have to type all those characters.
Click to expand...
Click to collapse
try putting it back to its orig name and then when your in cmd prmpt just type the P and press tab it will fill the rest in (i dont know the exact name so if i were you i would look it up)
if that doesnt work do a data factory reset in recovery and wipe both caches
.torrented said:
try putting it back to its orig name and then when your in cmd prmpt just type the P and press tab it will fill the rest in (i dont know the exact name so if i were you i would look it up)
if that doesnt work do a data factory reset in recovery and wipe both caches
Click to expand...
Click to collapse
I downloaded the file again and used the original name and still a no go gets the remote 99 unknown fail below
sending 'zip' (36905 KB)...
OKAY [ 3.370s]
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: 3.595s
Is it possible I need stock kernal first?
rootntootn said:
I downloaded the file again and used the original name and still a no go gets the remote 99 unknown fail below
sending 'zip' (36905 KB)...
OKAY [ 3.370s]
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: 3.595s
Is it possible I need stock kernal first?
Click to expand...
Click to collapse
The remote 99 for me and for .torrented the night it was released meant that we had to start over, he restored a nandroid backup from before the process and I just wiped and installed the rom clean.
Mine was because I goofed and ran the flash zip command line twice after the error 92 I ran it one more time because I misinterpreted the message.
So I ended up wiping and reflashing the rom, going into settings/developer options and enabling USB debugging, and doing the process correctly and it worked right off the bat.
But for me at least once I got that error 99 I couldn't get past it until I started with clean system files from before I began pushing the adb lines after the system reboot.
CharliesTheMan said:
The remote 99 for me and for .torrented the night it was released meant that we had to start over, he restored a nandroid backup from before the process and I just wiped and installed the rom clean.
Mine was because I goofed and ran the flash zip command line twice after the error 92 I ran it one more time because I misinterpreted the message.
So I ended up wiping and reflashing the rom, going into settings/developer options and enabling USB debugging, and doing the process correctly and it worked right off the bat.
But for me at least once I got that error 99 I couldn't get past it until I started with clean system files from before I began pushing the adb lines after the system reboot.
Click to expand...
Click to collapse
Thanks! I tried doing factory reset and wiped all cache and that also did not work...will find a backup from earlier and go again, I did do some repeats of commands so this sounds like maybe what I need to do...
rootntootn said:
Thanks! I tried doing factory reset and wiped all cache and that also did not work...will find a backup from earlier and go again, I did do some repeats of commands so this sounds like maybe what I need to do...
Click to expand...
Click to collapse
BINGO! That did it. Thanks for everyones help!!

[Q] RUU back to stock

I'm trying to RUU back to stock DNA on Verizon but it keeps telling me there is an error
it tells me "ERROR [158]: Image error"
am i missing something?
kreep22 said:
I'm trying to RUU back to stock DNA on Verizon but it keeps telling me there is an error
it tells me "ERROR [158]: Image error"
am i missing something?
Click to expand...
Click to collapse
Did you lock the phone again first, if you had previously unlocked/rooted?
GreginNH said:
Did you lock the phone again first, if you had previously unlocked/rooted?
Click to expand...
Click to collapse
yes, it's showing relocked status and it wont let me do anything just takes me to the bootloader no matter what i do
kreep22 said:
yes, it's showing relocked status and it wont let me do anything just takes me to the bootloader no matter what i do
Click to expand...
Click to collapse
Right Click and Run as Admin try that... make sure you are in fastboot usb mode as well or redownload the RUU maybe you got a bad DL
.torrented said:
Right Click and Run as Admin try that... make sure you are in fastboot usb mode as well or redownload the RUU maybe you got a bad DL
Click to expand...
Click to collapse
I tried to Run as Admin and no luck tells me the same error message, i've done it before with the same ruu that i am trying with now but idk what is going on, am i bricked?
kreep22 said:
I tried to Run as Admin and no luck tells me the same error message, i've done it before with the same ruu that i am trying with now but idk what is going on, am i bricked?
Click to expand...
Click to collapse
does your phone boot to android at all? or recovery
.torrented said:
does your phone boot to android at all? or recovery
Click to expand...
Click to collapse
I got it wprking, just re unlocked and rom came back on. Thank u
Sent from my HTC6435LVW using xda app-developers app
kreep22 said:
I got it wprking, just re unlocked and rom came back on. Thank u
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
How did you do it can you please explain?
Tried going back to stock settings
Relocked m errory phone s- off still the ruu wizard keeps giving me error 158? Flashed hboot with no luck. how do I unlock again like I said still s-off
wondering how u unlocked again
chris1569810 said:
How did you do it can you please explain?
Click to expand...
Click to collapse
I'm in the same situation
You flashed the stock hboot with no problems? Which hboot?
Help! I have a similar problem
GreginNH said:
Did you lock the phone again first, if you had previously unlocked/rooted?
Click to expand...
Click to collapse
I used moonshine S-OFF to root my DNA. I dont know how to get back to the stock locked hboot. and i keep getting that error 158.
any recommendations?
madc321 said:
I used moonshine S-OFF to root my DNA. I dont know how to get back to the stock locked hboot. and i keep getting that error 158.
any recommendations?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2293919
finanandroid said:
http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
Thanks but I tried that with no luck. I was able to flash viper venom though. no idea why the bamf rom did not work.
Solution?
So what ended up being the solution for the Error 158 and being stuck at Fastboot? I can't seem to find one that will work. Check my thread in Q & A: http://forum.xda-developers.com/showthread.php?t=2649525
Before running ruu u should boot into fastboot and make u see fastboot usb then start ruu, the error is because ur device can't boot into bootloader to finish with ruu
Sent from my HTC6435LVW using xda app-developers app
jaymazz13 said:
Before running ruu u should boot into fastboot and make u see fastboot usb then start ruu, the error is because ur device can't boot into bootloader to finish with ruu
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I just spent 20 minutes freaking out. I kept getting the 158 error over and over. I fastboot flashed the locked bootloader file and it said RELOCKED, but still errored out.
I was on the ENG hboot at the time and fastboot flashed the vanilla 3.06 hboot and this time the RUU went through.
Hopefully this will help somebody else out.
sasquatch1 said:
I just spent 20 minutes freaking out. I kept getting the 158 error over and over. I fastboot flashed the locked bootloader file and it said RELOCKED, but still errored out.
I was on the ENG hboot at the time and fastboot flashed the vanilla 3.06 hboot and this time the RUU went through.
Hopefully this will help somebody else out.
Click to expand...
Click to collapse
How can I do this if phone was fully stock before recieving an OTA via Verizon and now wont get past white HTC screen?
I am s-on...I cant flash anything...and RUU keeps failing.
---------- Post added at 04:56 PM ---------- Previous post was at 04:51 PM ----------
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA2BPS501936
(bootloader) imei: 990000671822338
(bootloader) meid: 99000067182233
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
DuceTheTruth said:
How can I do this if phone was fully stock before recieving an OTA via Verizon and now wont get past white HTC screen?
I am s-on...I cant flash anything...and RUU keeps failing.
---------- Post added at 04:56 PM ---------- Previous post was at 04:51 PM ----------
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA2BPS501936
(bootloader) imei: 990000671822338
(bootloader) meid: 99000067182233
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
By above post i could understand that your phone is S-On and LOCKED.
If that was the case, How your phone got updated to boot 1.57.0000?
Have you flashed anything (firmware) in fastboot mode?
If yes, You have very less chance to get the phone working unless its JTAGed.
First of all thank you for your reply...
This phone was all stock when I received it in this state...never been rooted ...unlocked or anything....
All I know is that after accepting an OTA update from vzw the phone never booted up fully again...
Now I did try the flashing instructions from .torrented but everything I do fails...
I get "remote 22 loading zip info fail"...
I also get " remote 12 signature verify fail"....
Sent from my SPH-L710 using XDA Free mobile app
---------- Post added at 06:34 PM ---------- Previous post was at 06:19 PM ----------
DuceTheTruth said:
First of all thank you for your reply...
This phone was all stock when I received it in this state...never been rooted ...unlocked or anything....
All I know is that after accepting an OTA update from vzw the phone never booted up fully again...
Now I did try the flashing instructions from .torrented but everything I do fails...
I get "remote 22 loading zip info fail"...
I also get " remote 12 signature verify fail"....
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.073s]
finished. total time: 0.073s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.038s]
finished. total time: 0.039s
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\adb>fastboot flash zip PL83IMG_3.06_Recovery.zip
target reported max download size of 1514139648 bytes
sending 'zip' (11248 KB)...
OKAY [ 1.343s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.451s
C:\adb>fastboot flash zip PL83IMG_1.15_hboot
error: cannot open 'PL83IMG_1.15_hboot'
C:\adb>fastboot flash zip PL83IMG_1.15_hboot.zip
target reported max download size of 1514139648 bytes
sending 'zip' (434 KB)...
OKAY [ 0.202s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.252s
C:\adb>fastboot flash recovery PL83IMG_3.06_Recovery.zip
target reported max download size of 1514139648 bytes
sending 'recovery' (11248 KB)...
OKAY [ 1.364s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.470s

3.16 hboot2.09 In boot loop

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

Help please! I bricked hboot. I changed CID

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

not able to unlock HTC Desire 10 Pro Bootloader :(

Hello guys can you help me, i cant unlock the bootloader of HTC Desire 10 PRO cos the command "fastboot flash unlocktoken Unlock_code.bin" is not working getting this message below again n again. i have checked usb debugging & OEM Unlock options too in Developer options too. i really don't understand why is this happening. Also there is not much help from this device available here on XDA or other sites too.
M:\HTCRoot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.042s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.132s
need help guys..
here is more info if required.... guys plz help
C:\Users\Desktop\platform-tools>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC73XZ9*****
(bootloader) current-slot:
(bootloader) imei: 35**520********
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA10000
(bootloader) cid: HTC__060
all:
finished. total time: 0.037s
Same error here. Tried Desire* and other supported devices from the HTCdev site.
Kindly help which device to choose from dev site.
D:\HTC Desire 10 PRO\ADB-Windows> fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1602400000 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 1.009s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 1.033s
princepavs said:
Hello guys can you help me, i cant unlock the bootloader of HTC Desire 10 PRO cos the command "fastboot flash unlocktoken Unlock_code.bin" is not working getting this message below again n again. i have checked usb debugging & OEM Unlock options too in Developer options too. i really don't understand why is this happening. Also there is not much help from this device available here on XDA or other sites too.
M:\HTCRoot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.042s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/platform/mtk-msdc.0/11230000.msdc
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
FAILED (remote: UnlockToken Verify Fail!!)
finished. total time: 0.132s
need help guys..
Click to expand...
Click to collapse
Are you still able to unlock? I have the same issue too. Stuck here
I don't know if this one helps you too but I was unable to unlock bootloader from bootloader mode and I tried it from download mode. It was successfully done with fastboot.... command. Root? I used Magisk. only problem is it takes 5 minutes to start up every time I reboot.
carlochiefsg said:
Are you still able to unlock? I have the same issue too. Stuck here
Click to expand...
Click to collapse
naaa never worked.. so gave this phone to my dad as he's a normal android user... must say MTK processors r the worst
princepavs said:
naaa never worked.. so gave this phone to my dad as he's a normal android user... must say MTK processors r the worst
Click to expand...
Click to collapse
to be exact HTC MTK processor is the worst, HTC lied about all HTC phones boot loader is unlockable.... BS!

Categories

Resources