Hello all,
I've read many forum posts and have had no luck with my current situation, so I made an account and am reaching out to the community for assistance. I had bought a phone off ebay that I used for many months that was S-ON but unlocked--I ran many ROMS that worked on S-ON just fine. However, I've recently decided I'd like to work on an S-off ROM. I went all the way back to stock RUU using the main guide here on XDA (though, my bootloader still said it was "tampered" and "relocked" FWIW). I went back to stock, and took both OTAs to get to 2.06. I tried both the revone.dna (-1 and -2 errors) and moonshine (don't drink and shine after 10 "moonshining" attempts). Does anyone have any advice as to what I need to do to get unlocked again, become S-off, and then allow me to go forward with my own recovery and ROM of choice? I appreciate any help.
Thanks,
Andy
albernhagen said:
Hello all,
I've read many forum posts and have had no luck with my current situation, so I made an account and am reaching out to the community for assistance. I had bought a phone off ebay that I used for many months that was S-ON but unlocked--I ran many ROMS that worked on S-ON just fine. However, I've recently decided I'd like to work on an S-off ROM. I went all the way back to stock RUU using the main guide here on XDA (though, my bootloader still said it was "tampered" and "relocked" FWIW). I went back to stock, and took both OTAs to get to 2.06. I tried both the revone.dna (-1 and -2 errors) and moonshine (don't drink and shine after 10 "moonshining" attempts). Does anyone have any advice as to what I need to do to get unlocked again, become S-off, and then allow me to go forward with my own recovery and ROM of choice? I appreciate any help.
Thanks,
Andy
Click to expand...
Click to collapse
I just got through doing this myself, and had the exact same problem. I successfully got S-Off even when using DigitalDream 2.2 ROM. Here's what I did.
Step 1: Go to this link (http://forum.xda-developers.com/showthread.php?t=2314771) and use the stuff at the very bottom of the first post where it says to download 2.06 firmware and to flash that first. If you can an error when flashing the firmware, don't worry about it. Just do the fastboot reboot-bootloader command then power off the phone completely and turn it back on (as the instructions say.
Step 2: I used the FacePalm method (http://forum.xda-developers.com/showthread.php?t=2155069). I only downloaded the boot.img and firmware. Follow the steps for the FacePalm method. That successfully got me S-Off.
Thanks
Thanks for your response, BoogaBooga. I tried this out, but it seems that I'm out of luck because I'm relocked as opposed to unlocked. Here's what I saw when attempting FacePalm:
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.043s]
finished. total time: 0.044s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot flash zip dna2.06firmware.zip
< waiting for device >
sending 'zip' (33119 KB)...
OKAY [ 2.411s]
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...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,25
(bootloader) [RUU]UZ,boot,38
(bootloader) [RUU]UZ,boot,52
(bootloader) [RUU]UZ,boot,66
(bootloader) [RUU]UZ,boot,79
(bootloader) [RUU]UZ,boot,90
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,51
(bootloader) [RUU]UZ,hboot,100
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,11
(bootloader) [RUU]UZ,recovery,22
(bootloader) [RUU]UZ,recovery,36
(bootloader) [RUU]UZ,recovery,48
(bootloader) [RUU]UZ,recovery,74
(bootloader) [RUU]UZ,recovery,86
(bootloader) [RUU]UZ,recovery,97
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,9
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,27
(bootloader) [RUU]UZ,radio,36
(bootloader) [RUU]UZ,radio,41
(bootloader) [RUU]UZ,radio,50
(bootloader) [RUU]UZ,radio,59
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,73
(bootloader) [RUU]UZ,radio,82
(bootloader) [RUU]UZ,radio,87
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,36
(bootloader) [RUU]WP,radio,73
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [ 17.400s]
finished. total time: 19.810s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.036s]
finished. total time: 0.037s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.039s]
finished. total time: 0.040s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fasboot flash zip PL8320000-DNA.zip
'fasboot' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot flash zip PL8320000-DNA.zip
sending 'zip' (36905 KB)...
OKAY [ 2.680s]
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.814s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot flash zip PL8320000-DNA.zip
sending 'zip' (36905 KB)...
OKAY [ 2.680s]
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.815s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>fastboot boot DNA-rescue.img
downloading 'boot.img'...
OKAY [ 0.813s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.815s
C:\Users\andyb_000\Downloads\adt-bundle-windows-x86_64-20130219\sdk\backup of pl
atform-tools\platform-tools>^A
BoogaBooga said:
I just got through doing this myself, and had the exact same problem. I successfully got S-Off even when using DigitalDream 2.2 ROM. Here's what I did.
Step 1: Go to this link (http://forum.xda-developers.com/showthread.php?t=2314771) and use the stuff at the very bottom of the first post where it says to download 2.06 firmware and to flash that first. If you can an error when flashing the firmware, don't worry about it. Just do the fastboot reboot-bootloader command then power off the phone completely and turn it back on (as the instructions say.
Step 2: I used the FacePalm method (http://forum.xda-developers.com/showthread.php?t=2155069). I only downloaded the boot.img and firmware. Follow the steps for the FacePalm method. That successfully got me S-Off.
Click to expand...
Click to collapse
After I updated to 2.06 (the stock way), I ended up reunlocking using the original unlock key I got from the HTCDEV site. Not exactly sure how you unlocked yours the first time, so I'm not sure if that will help you or not.
BoogaBooga said:
After I updated to 2.06 (the stock way), I ended up reunlocking using the original unlock key I got from the HTCDEV site. Not exactly sure how you unlocked yours the first time, so I'm not sure if that will help you or not.
Click to expand...
Click to collapse
Since I bought the phone already unlocked, I never had the old unlock key. I suppose I can contact the guy I bought it from and see if he still has it. Any other ideas in the meantime?
I'm really not sure. Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2109862
BoogaBooga said:
I'm really not sure. Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2109862
Click to expand...
Click to collapse
I received help from Beaups and got things working. It was a problem with my supercid. We did basically what happens in post #5 here:
http://forum.xda-developers.com/showthread.php?t=2407640
Thanks!
Related
I have followed all of the instructions to a T like 5 times to no avail. Can someone please tell me what I may be doing wrong?
Here is a copy of my command prompt:
C:\Users\Jerry>cd c:\.android
c:\.android>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 48888EEB9889D124D6C72F309EB940E2
(bootloader) 4CF40D0980840AF3DBB8CE4A486C056F
(bootloader) B42CE3D1056CAA6E3BE6884B5A28F120
(bootloader) C3B4E7E9173E3A55070B1A910E2497CD
(bootloader) A10C7FCE2ECE00C595C9DEE4B4D2A0C9
(bootloader) 219FF2E5D0C5019BDD3CA2EE7E28D44B
(bootloader) 875A72786356791FD909F85FE585D75C
(bootloader) 066E93AB9754291B9EC07CF026967276
(bootloader) EFA05F5E63FD78921D794C18CB1FBE22
(bootloader) AA76C231B26418110079C337E1CBA85C
(bootloader) 32549FCB5270D515775DF1DB9EB7C42D
(bootloader) A835495897A09826555C5147F5A7DC51
(bootloader) 059061DBC08128A32501EA28C1C0736F
(bootloader) 1F55865A90703A538D44517E85259D43
(bootloader) D17D85912695F9E8A3F24E3AF917B299
(bootloader) 4DEF2BBCBAB92B36D0D778673321E5CB
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.070s]
finished. total time: 0.070s
c:\.android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.159s
c:\.android>
See the guide/flashing notes in my signature. It'll straighten you out. Stuck at step 13right?
Redownload the bin file, if you noticed it cought it being 0kb of size.
Also ensure that the phone is seen correctly under windows.
Sent from my PG86100 using Tapatalk
That happened to me the bootloader unlock option did not want to come .. i am sure your number software ends with 3 . Or higher what i did i ran the 2.17.651.2 ruu shotter and after that i had no problems . If you run the ruu.shotter you will lose all your data.
Sent from my HTC.EVO.3D.Xda Premium
Amy luck
Sent from my HTC.EVO.3D.Xda Premium
Any luck?
Sent from my HTC.EVO.3D.Xda Premium
darkstar765 said:
I have followed all of the instructions to a T like 5 times to no avail. Can someone please tell me what I may be doing wrong?
Here is a copy of my command prompt:
C:\Users\Jerry>cd c:\.android
c:\.android>fastboot oem get_identifier_token
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 48888EEB9889D124D6C72F309EB940E2
(bootloader) 4CF40D0980840AF3DBB8CE4A486C056F
(bootloader) B42CE3D1056CAA6E3BE6884B5A28F120
(bootloader) C3B4E7E9173E3A55070B1A910E2497CD
(bootloader) A10C7FCE2ECE00C595C9DEE4B4D2A0C9
(bootloader) 219FF2E5D0C5019BDD3CA2EE7E28D44B
(bootloader) 875A72786356791FD909F85FE585D75C
(bootloader) 066E93AB9754291B9EC07CF026967276
(bootloader) EFA05F5E63FD78921D794C18CB1FBE22
(bootloader) AA76C231B26418110079C337E1CBA85C
(bootloader) 32549FCB5270D515775DF1DB9EB7C42D
(bootloader) A835495897A09826555C5147F5A7DC51
(bootloader) 059061DBC08128A32501EA28C1C0736F
(bootloader) 1F55865A90703A538D44517E85259D43
(bootloader) D17D85912695F9E8A3F24E3AF917B299
(bootloader) 4DEF2BBCBAB92B36D0D778673321E5CB
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.070s]
finished. total time: 0.070s
c:\.android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.151s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.007s]
finished. total time: 0.159s
c:\.android>
Click to expand...
Click to collapse
Download and run The 2.08 RUU Then Use the htc Unlock I had the same problem today this works
While trying to get S-Off on about every method I could, and reflashing RUU. I think I bricked it.
What happened was that I attempted to relock the phone. (fastboot oem lock), so I could reflash back to stock.
I'd done this already without any issues. But this time, when I did, it got stuck on booting to the boot loader. It wouldn't boot into recovery nor into the ROM. After about an hour, I finally got it to boot again. However, The only way I could do this was to flash the unlock token.
The issue here is now that when it boots into the fastboot bootloader, it shows some graphical issues and refuse to take the RUU, even when manually flashing it.
D:\One_All-In-One_Kit_v\rumrunner_HTC_0.5.0>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.035s]
finished. total time: 0.035s
D:\One_All-In-One_Kit_v\rumrunner_HTC_0.5.0>fastboot flash zip rom.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1180758 KB)...
OKAY [ 42.850s]
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) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 143.395s
Click to expand...
Click to collapse
I'd done this previosly to revert to stock without issues, not an hour before.
fastboot getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36DW903729
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4267mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.056s
Click to expand...
Click to collapse
The phone is currently on Android 4.4.2, Sense 5.5, stock.
The RUU I'm using is:
RUU_M7_UL_JB43_SENSE50_MR_TMOUS_3.24.531.3_Radio_4A.21.3263.03_10.38m.1157.04_release_336982_signed_2(2)
I have the OTA zip for 4.4.2, as well as the firmware.zip from it.
None of it works, and all errors up with the above error.
And no, I don't have S-Off.
Additionally, when connecting to fasboot USB, it does some screen tearing, distorting the text. I suspect that I've damaged the firmware and the phone is basically a brick. It does boot, but I cannot reflash the RUU.
Hi everyone, I may just lost my nexus 9... :/
I was trying to install the M developer preview on my nexus 9, so I enabled oem unlock from developer settings, then 'adb reboot bootloader', then 'adb fastboot unlock' and after restart:
Code:
Danieles-MacBook-Pro-2:volantis-MPZ44Q myusername$ ./flash-all.sh
target reported max download size of 518205818 bytes
sending 'bootloader' (3085 KB)...
OKAY [ 0.265s]
writing 'bootloader'...
(bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.283s]
finished. total time: 5.548s
rebooting into bootloader...
OKAY [ 0.022s]
finished. total time: 0.022s
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(68411,0xa0ad51d4) malloc: *** mach_vm_map(size=2132963328) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 2130828644 bytes
error: update package missing system.img
I tried to reboot the device and now I can see Google logo, a bit of the startup animation and then it restarts itself again and again...
I cannot even go to the recovery anymore, I'm trying to press and hold Power plus vol up and down but nothing.
Is there a way to fix it? I'm not sure what's happened :/
Thanks,
Daniele
http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
This works for M
Yes thank you!
Sent from my D5803 using XDA Free mobile app
Hi,
I wanted to flash the stock image via fastboot but I keep getting these error
Code:
florian-MS-7788 volantis-mob30p # sh flash-all.sh
target reported max download size of 518205818 bytes
sending 'bootloader' (2898 KB)...
OKAY [ 0.217s]
writing 'bootloader'...
(bootloader) Device State : Unlocked
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[bct] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_preboot_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[mts_prod] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtboot] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[nvtbootwb0] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[tos] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[sp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[gp1] unzipping & flashing...
(bootloader) ...... Successful
(bootloader) start image[pt] unzipping & flashing...
(bootloader) ...... Successful
OKAY [ 5.466s]
finished. total time: 5.683s
rebooting into bootloader...
OKAY [ 0.032s]
finished. total time: 0.182s
target reported max download size of 518205818 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Info: zone aligned segment0 blkaddr: 512
Segmentation fault
It is not the first time I flashed back to stock, so bootloader is unlocked.
If it is important I'm using Linux mint 18
Have you tried flashing the images separately, instead of using the script?
Un zip the archive to get all images.
Flashing the images seperately seems to work as a workaround, but does not solve the error. I also tryed formatting all partitions in twrp.
Thanks
Flo9818 said:
Flashing the images seperately seems to work as a workaround, but does not solve the error. I also tryed formatting all partitions in twrp.
Thanks
Click to expand...
Click to collapse
Are you using the latest fastboot and adb versions, this error was reportedly fixed in 2015?
http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
corkiejp said:
Are you using the latest fastboot and adb versions, this error was reportedly fixed in 2015?
http://www.androidpolice.com/2014/1...-0-factory-images-heres-how-to-get-around-it/
Click to expand...
Click to collapse
I installed fastboot and adb over apt-get fastboot adb from offical repositorys, which should be up to date. I also try installing using nexustools
Update: Fixed. Please delete thread.
Hi guys,
I have an HTC One M8 which was rooted, with TWRP and running CM 12, S-ON. I just wanted to put the stock ROM back on it, I don't care about the flags that says that the software is modified or anything like that.
For that I followed this thread.
Step 1: lock the bootloader. -> this worked. The status is now RELOCKED. ***Software modified***
Trying to flash TWRP doesn't work though, neither is the device listed through adb, bellow what I get in the command prompt.
C:\miniadb_m8> fastboot flash recovery openrecovery-twrp-2.8.4.0-m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (16092 KB)...
OKAY [ 1.740s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.321s
C:\miniadb_m8>adb devices
List of devices attached
C:\miniadb_m8>fastboot devices
xxxx fastboot
I looked up the RUU for my devices based on the information I got back by using fastboot getvar all and came across another post on this forum for my device (HTC__038) and tried flashing that RUU.zip file, bellow the output.
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.013s]
finished. total time: 0.013s
C:\adb>htc_fastboot flash zip RUU.zip
sending 'zip'... (53966 KB) OKAY
sending time = 2.648 secs
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...
FAILED (status read failed (Too many links))
Execution time is 8(s).
I can't get around this, was wondering if someone can point me in the right direction, based on my device info:
C:\miniadb_m8>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxx
(bootloader) imei: xxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any help is appreciated, thanks a lot.
Cheers,
Adrian