Hello,
I'm trying to revert my phone to the original state. I's been S-OFFed by revolutionary method, so I flashed eng HBOOT as it was suggested in another threads. Then I tried to flash original rom from RUU. At the beginning it gave me the error 155, so I tried flashing directly from fastboot and everything seemed OK until the end, where it wrote a message about some signature failure.
Here is a part of the flashing log:
Code:
</DEBUG></T185928>
</DEBUG></T185930>
<T185930><DEBUG><CMD>fastboot -s HTxxxxxxxx getvar boot-mode</CMD>
</DEBUG></T185930>
<T185931><DEBUG><OUT>boot-mode: RUU (Hboot&Radio PreUpdate)</OUT>
</DEBUG></T185931>
<T185931><DEBUG><CMD>fastboot -s HTxxxxxxxx flash zip C:\Users\username\AppData\Local\Temp\{8A84FC36-535E-409A-94A3-231D50E85D54}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T185931>
<T190013><DEBUG><OUT>sending 'zip' (253505 KB)... OKAY</OUT>
</DEBUG></T190013>
<T190013><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T190013>
<T190013><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T190013>
<T190050><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T190050>
<T190050><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T190050>
<T190050><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T190050>
<T190050><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T190050>
<T190050><DEBUG><OUT>INFOchecking main version...</OUT>
</DEBUG></T190050>
<T190050><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
</DEBUG></T190050>
<T190103><DEBUG><CMD>adb devices</CMD>
</DEBUG></T190103>
<T190104><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T190104>
<T190104><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T190104>
<T190105><DEBUG><OUT>HTxxxxxxxxfastboot</OUT>
</DEBUG></T190105>
<T190105><DEBUG><CMD>adb devices</CMD>
</DEBUG></T190105>
<T190106><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T190106>
<T190106><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T190106>
<T190108><DEBUG><OUT>HTxxxxxxxx fastboot</OUT>
</DEBUG></T190108>
<T190108><DEBUG><CMD>fastboot -s HTxxxxxxxx getvar boot-mode</CMD>
</DEBUG></T190108>
<T190109><DEBUG><OUT>boot-mode: RUU (Hboot&Radio PreUpdate)</OUT>
</DEBUG></T190109>
<T190109><DEBUG><CMD>fastboot -s HTxxxxxxxx reboot</CMD>
</DEBUG></T190109>
<T190110><DEBUG><OUT>rebooting... </OUT>
</DEBUG></T190110>
<T190110><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T190110>
<T190111><DEBUG><OUT />
Now I've an original rom but it is unable to install OTA update as it ends in fastboot and **security warning**. I also noticed that I have superuser still available in the rom.
Here is an ouput from fastboot getvar all
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 11.10.401.4
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4185mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
I would like to hear some advice, what should I do next to fully revert to stock ROM, unroot and be able to use official updates. Thanks.
You should have flashed MISC partition hack from "downgrade HBOOT" thread before running the RUU.
Your problem is this:
<T190050><DEBUG><OUT>FAILED (remote: 43 main version check fail)</OUT>
RUU didn't like your main version.
So,
should I change the main version using the misc_version utility and then rerun RUU flashing process. If so, what kind of version should I choose or it doesn't matter. Right now i'm using the old ROM 1.28.401.1
I don't want to screw things up, that's why I'm asking.
The misc_version script flashes 1.00.000.0 by default, AFAIK. It's fine. Anything below the version you intend to use is fine.
Thanks a lot for the clarification. After changing the main version, RUU flashing went smoothly and all OTA updates installed without problem.
Related
Can I get a compatible RUU for my Ville C2? I've tried these
RUU_VILLEC2_U_ICS_40_hTC_Asia_WWE_1.11.707.112_Radio_16.12.20.02U_16.05.20.16_M2_release_264458_signed
RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Radio_16.21.20.02U_16.09.20.11_M2_release_286571_signed
but it kept saying CID Check fail ...
Following is the detail about my phone ... Pls help me ...
version: 0.5
version-bootloader: 2.09.0001
version-baseband: 16.05.20.24_M
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: SH261W401960
imei: 352762055675317
product: villec2
platform: HBOOT-8260
modelid: PJ4020000
cidnum: HTC__044
battery-status: good
battery-voltage: 3676mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: f616909f
hbootpreupdate: 11
gencheckpt: 0
It keep show these errors ...
C:\android-sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) Start Verify: 3
OKAY [ 0.150s]
finished. total time: 0.150s
C:\android-sdk\platform-tools>fastboot flash zip rom.zip
sending 'zip' (508987 KB)...
(bootloader) start check_usb: usb_ep0: type=128, request=6
OKAY [ 54.164s]
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...
FAILED (remote: 42 custom id check fail)
finished. total time: 131.563s
Your phone seems branded. You have to get the RUU from the carrier you're on or you have to change your CID (which is not working with the villec2).
S3 RUU
.TanTien said:
RUU_VILLEC2_U_ICS_40_hTC_Asia_WWE_1.11.707.112_Rad io_16.12.20.02U_16.05.20.16_M2_release_264458_sign ed.
Click to expand...
Click to collapse
I tried the HTC_Asia one but when it went to verify my image it didn't show what version I currently had. It was blank. Is that something that I can just ignore and keep going?
Maybe I am not doing it right. ran command: fastboot oem lock
received reply: lock successfully...
TZ_HTC_SVC_DISABLE ret - 268303736 failed (status read failed )Too many Links)
Then I ran the RUU from my PC. Was I suppose to rename it to Rom.zip and run
fastboot oem rebootRUU + fastboot flash zip rom.zip
Super CID
You can try changing CID with this proceure:
http://forum.xda-developers.com/showthread.php?t=1807214
I haven't tried it yet as I haven't found a RUU to need to do it for.
Quills88 said:
You can try changing CID with this proceure:
http://forum.xda-developers.com/showthread.php?t=1807214
I haven't tried it yet as I haven't found a RUU to need to do it for.
Click to expand...
Click to collapse
don't work with s3/villec2
there is no way to do this on s3!
Hello all, I was trying to S-off my phone in order to be able to flash hboot of version 2.15(i guess the most supporting). But stumbled upon a problem - I need a live Android, ie ROM running to S-off. But all I have is fastboot and TWRP 2.3.0(some later won't boot too)
I now don't have any ROM at all, all ROMs I tried won't boot on my hboot. Actually that's the reason I'm trying to upgrade my HBoot. It seems to be a vicious circle, unless I find a ROM which will run on my config
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.16.31501S.17_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: HT23XW411592
(bootloader) imei: 359901041873577
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4180mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
As you can see I gained SuperCID already, did it in recovery as a prerequisite for Facepalm S-Off
Solved
OK, I can confirm that RUU_Ville_U_HTC_Europe_1.47.401.1_Radio_0.15.31501S.13_3_10.08.31501S.04L_release_250115_signed
contains boot.img and system.img files which boot on hboot v1.13
In order to flash that system.img I needed to copy it in recovery to /sdcard,
Code:
mount -o loop
it and manually copy the contents to /system, because flashing with fastboot failed:
Code:
sending 'system' (1048572 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.006s
After rebooting stock will come up
So that's my story cut short:
I was and is S-On
I had HBoot v1.13, upgraded it by RUU flashing firmware.zip from OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip
Now I have HBoot 2.15 and TeamWin Recovery 2.8 .
ZenROM flashes with no problem, but that's still no stock, as the signature of /system is broken.
But in order to get S-Off, which is necessary at least to gain hboot 2.16 for Liberty ROM, I need to get stock ROM.
This is necessary in order for phone to boot with bootloader locked(signature should validate), which is a prereq for Faceplam S-Off(as I understand)
But every RUU I flash says:
Code:
sending 'zip' (534178 KB)...
OKAY [ 21.050s]
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...
(bootloader) checking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 73.893s
And every OTA I try to install in TWRP says I have a CID mismatch , no matter leave I my original (HTC_A07) or SuperCID
Help anyone?
That's my config. I deliberately downed main version, because otherwise during RUU flash I got "invalid main version" instead
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT23XW411592
(bootloader) imei: *****************
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__A07
(bootloader) battery-status: good
(bootloader) battery-voltage: 4203mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
Actually you don't need a stock rom. As far as I know you only need a sense rom. I S-OFFed while I had this rom installed.
Flippy498 said:
Actually you don't need a stock rom. As far as I know you only need a sense rom. I S-OFFed while I had this rom installed.
Click to expand...
Click to collapse
Which S-Off did you use? Rumrunner and firewater didn't work for me
I used facepalm. I know a lot of people here say that it won't work on hboot 2.15 but for me it did work. Don't know why...
Flippy498 said:
I used facepalm. I know a lot of people here say that it won't work on hboot 2.15 but for me it did work. Don't know why...
Click to expand...
Click to collapse
But with facepalm you need to flash PJ4010000.zip (or whatsitsname) in RUU mode(mean you should relock) and when it says "Error: 92 supercid blablablah" you should boot immediately, right?
And you're still with locked bootloader.
And on custom ROM, which means on boot the signature will be checked AND will fail, so it won't boot at all - that's what happens to me...
Tell me I'm wrong, cause otherwise I can't s-off neither I can flash stock...
Well, I SOFFed more than one and a half year ago. But as far as I remember you don't need to relock since you don't want to run a RUU.
Just looked it up. The instructions in the facepalm thread do not mention that you need to relock. Try again to S-OFF without relocking.
Hi, I have problem with my phone which is similar to the one described in this topic.
I have tried to S-off my One SV but I didn't update to the newest version of stock ROM which resulted in an error while running moonshine (it stopped after step 10 saying "Don't drink and moonshine" which was quite funny at first ).
Now the hboot says that the phone is unlocked and tampered.
I have tried flashing a stock rum using RUU exe file but it obviously failed.
Flashing .img files works fine (I have already tried to flash several boot.img's), I have even tried to flash new Venom ROM using TWRP recovery and it flashed fine, but the phone hangs on boot screen.
When I try to flash zip using fastboot it fails:
sending 'zip' (441985 KB)...
OKAY [ 19.654s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 31.754s
When I try to flash anything using PL80IMG.zip method the file is being read (I can see a progress bar) but nothing happens after that.
getvar all output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.01.0000
(bootloader) version-baseband: 0.12.40.00.14_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT32WTP00820
(bootloader) imei: 352803051180587
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3986mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.075s
I would appreciate any help Thanks
Hi,
my phone seems to be stuck in bootloader. Recovery and factory reset don't do anything, just loop back to fastboot. I have fastboot usb working, but no adb connection apparently (adb devices returns empty).
***unlocked***
K2_UL XA SHIP S-ON RL
HBOOT - 2.00
eMMC-boot
jun 13 2013
my fastboot getvar below :
c:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: XA SHIP S-ON
(bootloader) serialno: 123456789012
(bootloader) imei:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010***
(bootloader) cidnum: ORANG202
(bootloader) battery-status: good
(bootloader) battery-voltage: 3706mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.078s
c:\>fastboot getvar commitno-bootloader
commitno-bootloader: dirty-15afa7fc67c51747c2eaca17ce1ac7846d555b6a
c:\>fastboot getvar hbootpreupdate
hbootpreupdate: 11
c:\>fastboot getvar gencheckpt
gencheckpt: 0
fastboot flash recovery returns FAILED (remote: image update error), I've tried many versions of CWM and TWRP. fastboot flash boot with a boot.img I extracted returns the same error.
What can I do from here ? Thank you very much
shameless self bump :fingers-crossed:
did you find a solution, i'm in the same sh*t like you for months
nope, sorry, however i think i found confirmation that i'm f*cked
i found a working RUU, tried to flash it directly from the SD card by renaming it PL80IMG.zip but that could only have worked if i relocked my bootloader, because i'm S-ON. so i ran "fastboot oem lock" and i got the exact same result as this : http://forum.xda-developers.com/showpost.php?p=55525058&postcount=24 (it isn't for the One SV but i'm pretty sure it applies, since i have the exact same red lines)
and apparently it means corrupted hardware/"bad blocks" and i haven't found where to go from there. I suggest you try "fastboot oem lock" and you'll at least know if there's hope?
[edit: i also figured out why it happened : i did a "factory reset" directly from the bootloader instead of doing it from custom recovery, and apparently you should never do that when you're rooted/unlocked... so at least i guess i learned a (f*ing expensive) lesson]