The file name is PDM_W8_WL_BLUE_00_VERIZON WWE_1.06.605.02_Radio_1.00.50.0806_release.zip. It actually comes from a Chinese forum, the original link is here.:laugh:
It was claimed to be official RUU. And the download link is here. Password of the link is w8xm, which is needed before showing the file. It's a cloud storage link from China. I don't know if it can be downloaded outside China. May need VPN?
Anyway, hope it could help to port WP to the Android version M8.
sea-monsters said:
The file name is PDM_W8_WL_BLUE_00_VERIZON WWE_1.06.605.02_Radio_1.00.50.0806_release.zip. It actually comes from a Chinese forum, the original link is here.:laugh:
It was claimed to be official RUU. And the download link is here. Password of the link is w8xm, which is needed before showing the file. It's a cloud storage link from China. I don't know if it can be downloaded outside China. May need VPN?
Anyway, hope it could help to port WP to the Android version M8.
Click to expand...
Click to collapse
reload to Download PDM_W8_WL_BLUE_00_VERIZON WWE_1.06.605.02_Radio_1.00.50.0806_release.zip from FileFactory.com
need time to take look :laugh:
release from Chinese forum at http://bbs.gfan.com/android-7623915-1-1.html
mwang said:
reload to Download PDM_W8_WL_BLUE_00_VERIZON WWE_1.06.605.02_Radio_1.00.50.0806_release.zip from FileFactory.com
need time to take look :laugh:
release from Chinese forum at http://bbs.gfan.com/android-7623915-1-1.html
Click to expand...
Click to collapse
I wonder what it would take to flash it to a AT&T M8? I have a spare one, but really don't want to make a paperweight with it. :silly:
Well to flash any RUU that's not with what came with the phone, you would need to be s-off and have supercid. The file in question is in zip form, it wouldn't run the same way as one that's in exe form.
You would have to flash that type of file in rebootRUU mode in fast boot.
Oditius said:
I wonder what it would take to flash it to a AT&T M8? I have a spare one, but really don't want to make a paperweight with it. :silly:
Click to expand...
Click to collapse
Well flash it and let us know[emoji4]
RUU/NBH Contents
I don't usually dig this deep on roms so I am out of my typical bubble. That said, I am a developer, so this is the kind of thing I do every day.
I downloaded and extracted the RUU file. It contains an *.nbh file and a *.crc file.
I tried NBHExtract (from here), and it failed with an invalid format error.
As did NBHImageTool (from here).
I also found this link about the binary format of NBH files, and looking at it with a hex editor I don't think the described format matches the file contents.
On the other hand, I do see a reference to VZW__001 in the top of the file, as well as a WWE
These tools seem to be from an older generation of hardware. Perhaps the NBH format has been updated, or perhaps these are protected via encryption in some way.
Anyway, that's as far as I got into looking at this file.
---------- Post added 3rd September 2014 at 12:18 AM ---------- Previous post was 2nd September 2014 at 11:56 PM ----------
I also noticed that the NBH file has what appears to be a model number in the header:
06.605.02 0P6B21000
Searching 0P6B21000, got me to this Chinese/(Japanese? idk) blog page:
blogofmobile-com/article/19906
and on the blog page, you can clearly see in the wifi cert image that 0P6B21000 is the model number of the HTC Product HTC6995LVW, which the the M8...
So, that's some kind of legitimacy.
and then I found this post about that number being used as the codename for the global version of the M8:
www-thewincentral-com/2014/08/19/global-version-of-htc-w8-htc-m8-windows-may-have-been-spotted-in-adduplex-database/
Since I cant post external links yet, I bet you can see where those dashes should look a lot more like dots.
Tried to flash...
I locked my bootloader and tried to flash this puppy... Why not.
No joy though:
Code:
C:\Temp\adb>adb reboot bootloader
C:\Temp\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.021s]
finished. total time: 0.022s
C:\Temp\adb>fastboot devices
HT438SF00530 fastboot
C:\Temp\adb>fastboot flash zip RUU.zip
target reported max download size of 1830711296 bytes
sending 'zip' (850337 KB)...
OKAY [ 24.645s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 25.064s
android-info fail... what is that.
Anyway, a fastboot reboot got me back to android. No harm, no foul.
0D0A said:
I locked my bootloader and tried to flash this puppy... Why not.
No joy though:
Code:
C:\Temp\adb>adb reboot bootloader
C:\Temp\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.021s]
finished. total time: 0.022s
C:\Temp\adb>fastboot devices
HT438SF00530 fastboot
C:\Temp\adb>fastboot flash zip RUU.zip
target reported max download size of 1830711296 bytes
sending 'zip' (850337 KB)...
OKAY [ 24.645s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 25.064s
android-info fail... what is that.
Anyway, a fastboot reboot got me back to android. No harm, no fowl.
Click to expand...
Click to collapse
Its reading the android info text file inside the ruu. If you are s-off you can change the model id and cid even, to your current cid and mid.
Hope this helps!
squabbi said:
Its reading the android info text file inside the ruu. If you are s-off you can change the model id and cid even, to your current cid and mid.
Hope this helps!
Click to expand...
Click to collapse
Well what do you know, my MID is
Code:
C:\Temp\adb>fastboot getvar mid
mid: 0P6B20000
finished. total time: 0.004s
and the rom clearly wants it to be 21000...
Thanks!
---------- Post added at 02:27 AM ---------- Previous post was at 01:49 AM ----------
Code:
C:\Temp\adb>fastboot getvar mid
mid: 0P6B21000
finished. total time: 0.003s
C:\Temp\adb>fastboot flash zip RUU.zip
target reported max download size of 1830711296 bytes
sending 'zip' (850337 KB)...
OKAY [ 24.634s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 24.643s
I locked my bootloader, perhaps I shouldn't have.
0D0A said:
Well what do you know, my MID is
Code:
C:\Temp\adb>fastboot getvar mid
mid: 0P6B20000
finished. total time: 0.004s
and the rom clearly wants it to be 21000...
Thanks!
---------- Post added at 02:27 AM ---------- Previous post was at 01:49 AM ----------
Code:
C:\Temp\adb>fastboot getvar mid
mid: 0P6B21000
finished. total time: 0.003s
C:\Temp\adb>fastboot flash zip RUU.zip
target reported max download size of 1830711296 bytes
sending 'zip' (850337 KB)...
OKAY [ 24.634s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 24.643s
I locked my bootloader, perhaps I shouldn't have.
Click to expand...
Click to collapse
Yeah! Haha. As long as you still have S-Off you should be good. But if you dont want to go through the HTCDev unlock method you can do the adb method by scotty1223, you'll just need root for that. (and s-off)
0D0A said:
I don't usually dig this deep on roms so I am out of my typical bubble. That said, I am a developer, so this is the kind of thing I do every day.
I downloaded and extracted the RUU file. It contains an *.nbh file and a *.crc file.
I tried NBHExtract (from here), and it failed with an invalid format error.
As did NBHImageTool (from here).
I also found this link about the binary format of NBH files, and looking at it with a hex editor I don't think the described format matches the file contents.
On the other hand, I do see a reference to VZW__001 in the top of the file, as well as a WWE
These tools seem to be from an older generation of hardware. Perhaps the NBH format has been updated, or perhaps these are protected via encryption in some way.
Anyway, that's as far as I got into looking at this file.
---------- Post added 3rd September 2014 at 12:18 AM ---------- Previous post was 2nd September 2014 at 11:56 PM ----------
I also noticed that the NBH file has what appears to be a model number in the header:
06.605.02 0P6B21000
Searching 0P6B21000, got me to this Chinese/(Japanese? idk) blog page:
blogofmobile-com/article/19906
and on the blog page, you can clearly see in the wifi cert image that 0P6B21000 is the model number of the HTC Product HTC6995LVW, which the the M8...
So, that's some kind of legitimacy.
and then I found this post about that number being used as the codename for the global version of the M8:
www-thewincentral-com/2014/08/19/global-version-of-htc-w8-htc-m8-windows-may-have-been-spotted-in-adduplex-database/
Since I cant post external links yet, I bet you can see where those dashes should look a lot more like dots.
Click to expand...
Click to collapse
no tools on xda will help , the rom is encrypted , and the decrypt key should be in the phone
So flashing that file failed. :crying: I was going to try it today and see. Oh well, guess that saves me the time. Spent a while yesterday getting it reunlocked (Tried installing drivers that I downloaded off an instructional video on youtube. Should have known it was trouble when it said "not for this computer" when I installed it.) But my computer did recognize it, but adb didn't see it. So I d/l the one on HTC and all went well. So my spare M8 is ready to try something else that turns up.
It was always going to be doubtful, but thanks for trying! It's a start :good:
I tried many things. I even flashed back to stock, and then tried to re-flash the rom.
I can't get past this message:
Code:
C:\Temp\adb>fastboot flash zip RUU.zip
target reported max download size of 1830711296 bytes
sending 'zip' (850337 KB)...
OKAY [ 23.429s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
[B]FAILED (remote: 24 parsing android-info fail)[/B]
finished. total time: 23.614s
After looking at the NBH longer in a hex editor, there are several sections of readable strings, so I don't believe the file is encrypted after all. If it is, only some sections/blocks of it are.
For the record I tried combinations of Locked and Unlocked bootloader, regular CID and Super CID.
I wonder if the Windows device has the same CID as the android device. Perhaps it is different and we need to set it to something new.
Now I am starting to wonder if the windows system can be "flashed" with the android bootloader.
0D0A said:
I tried many things. I even flashed back to stock, and then tried to re-flash the rom.
I can't get past this message:
Code:
C:\Temp\adb>fastboot flash zip RUU.zip
target reported max download size of 1830711296 bytes
sending 'zip' (850337 KB)...
OKAY [ 23.429s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
[B]FAILED (remote: 24 parsing android-info fail)[/B]
finished. total time: 23.614s
After looking at the NBH longer in a hex editor, there are several sections of readable strings, so I don't believe the file is encrypted after all. If it is, only some sections/blocks of it are.
For the record I tried combinations of Locked and Unlocked bootloader, regular CID and Super CID.
I wonder if the Windows device has the same CID as the android device. Perhaps it is different and we need to set it to something new.
Now I am starting to wonder if the windows system can be "flashed" with the android bootloader.
Click to expand...
Click to collapse
Have you tried changing your mid and cid to suit the zip?
squabbi said:
Have you tried changing your mid and cid to suit the zip?
Click to expand...
Click to collapse
Yep. I changed my MID and CID to match what is in the first 200 bytes of the nbh file. No joy.
From what I can see, you need to make a proper file called "android-info" and put it in the zip file. If it is expecting it in the nbh itself, you need to modify the name to whatever the equivalent of "Android-info" is. Happy flashing!
There's no android-info.txt in the zip, because it's not an Android RUU. The bootloader won't parse the zip without it. Unless you add it in, all the attempts at flashing it will surely fail.
squabbi said:
Have you tried changing your mid and cid to suit the zip?
Click to expand...
Click to collapse
c:\miniadb_m8>adb shell
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x32\x00\x31\x00\ x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit
MID = 2100 then
try again
joeblack2k said:
c:\miniadb_m8>adb shell
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x32\x00\x31\x00\ x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit
MID = 2100 then
try again
Click to expand...
Click to collapse
Yep. Tried that, repeatedly...
Related
Hi there.
I've got an unbranded htc sensation device (manufactured for india). lat week i updated to cm9, and accidentally got a 1.29 hboot. after that I tried to flash the stock ICS for my pyramid. so, the situation is:
cid HTC__038
hboot version 1.29.0000
radio 11.24A.3504.31_m
openadsp v05.6.0.2226.00.0418
pyramid pvt ship s-on locked.
working adb, fastboot connection
i've got no working rom on the device, stuck in fastboot-loop.
there is no possibility to use revolutionary s-off because of hboot version 1.29, and because the non-working system (cannot put in debug mode)
i tried to flash the lastest 3.33 firmware, bit it still uses a previous version of hboot. (something messed up with signature check fail)
i cannot flash a non-official rom befause s-on.
do i have any possible steps to make my phone working with ics+sense?
all the answers will be "thanked" & btw sorry for my bad english
palomatE said:
Hi there.
I've got an unbranded htc sensation device (manufactured for india). lat week i updated to cm9, and accidentally got a 1.29 hboot. after that I tried to flash the stock ICS for my pyramid. so, the situation is:
cid HTC__038
hboot version 1.29.0000
radio 11.24A.3504.31_m
openadsp v05.6.0.2226.00.0418
pyramid pvt ship s-on locked.
working adb, fastboot connection
i've got no working rom on the device, stuck in fastboot-loop.
there is no possibility to use revolutionary s-off because of hboot version 1.29, and because the non-working system (cannot put in debug mode)
i tried to flash the lastest 3.33 firmware, bit it still uses a previous version of hboot. (something messed up with signature check fail)
i cannot flash a non-official rom befause s-on.
do i have any possible steps to make my phone working with ics+sense?
all the answers will be "thanked" & btw sorry for my bad english
Click to expand...
Click to collapse
Unlock via htcdev unlock then flash 4EXT recovery and enable smartflash then flash a ROM
flashing issue
Jonny said:
Unlock via htcdev unlock then flash 4EXT recovery and enable smartflash then flash a ROM
Click to expand...
Click to collapse
I've got the Unlock_code.bin, flashed with fastboot (fastboot flash unlocktoken Unlock_code.bin), and nothing happens, i mean no prompt is hiven for me to choose neither yes or no. command line says
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.152s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.009s]
finished. total time: 0.162s
Click to expand...
Click to collapse
bootloader is still locked.
is it supported for hboot v1.29?
palomatE said:
I've got the Unlock_code.bin, flashed with fastboot (fastboot flash unlocktoken Unlock_code.bin), and nothing happens, i mean no prompt is hiven for me to choose neither yes or no. command line says
bootloader is still locked.
is it supported for hboot v1.29?
Click to expand...
Click to collapse
Hi,
Yes, 1.29 is supported.
Keep trying.
Sometimes ,it takes more than one go to work.
still no success
malybru said:
Hi,
Yes, 1.29 is supported.
Keep trying.
Sometimes ,it takes more than one go to work.
Click to expand...
Click to collapse
after a few attempts, i've got the following four different responses:
Code:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.152s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.162s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... FAILED (remote: loading custom splash failed)
finished. total time: 0.001s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.069s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.079s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.151s]
writing 'unlocktoken'... OKAY [ 0.008s]
finished. total time: 0.160s
palomatE said:
after a few attempts, i've got the following four different responses:
Code:
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.152s]
writing 'unlocktoken'... INFOunlock token check successfully
OKAY [ 0.008s]
finished. total time: 0.162s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... FAILED (remote: loading custom splash failed)
finished. total time: 0.001s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.069s]
writing 'unlocktoken'... FAILED (remote: unlock token check failed)
finished. total time: 0.079s
C:\Android>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY [ 0.151s]
writing 'unlocktoken'... OKAY [ 0.008s]
finished. total time: 0.160s
Click to expand...
Click to collapse
fastboot reboot-bootloader
and then check the bootloader status
still locked
ganeshp said:
fastboot reboot-bootloader
and then check the bootloader status
Click to expand...
Click to collapse
I actually did this, with the same results. Is it a possible way if modify the partitions by a partitioning software running on pc, and manually edit the partitions' files, changing them to the correct ones, came from the official rom.zip file? I think (dont hit me if i was wrong), this way I can bypass all the s-on and locked bootloader stuff, maybe I can downgrade from hboot 1.29 without wire tricks, and install the stock ICS for pyramid.
what about the PG58IMG stuff? I can modify the removable sd card's files, so i can insert PG58IMG things to root, the phone is actually reads it. what if I somehow inject the Unlock_code.bin into some kind of PG58IMG, and apply this way the unlocking?
could be anything of these upper is working?
palomatE said:
I actually did this, with the same results. Is it a possible way if modify the partitions by a partitioning software running on pc, and manually edit the partitions' files, changing them to the correct ones, came from the official rom.zip file? I think (dont hit me if i was wrong), this way I can bypass all the s-on and locked bootloader stuff, maybe I can downgrade from hboot 1.29 without wire tricks, and install the stock ICS for pyramid.
what about the PG58IMG stuff? I can modify the removable sd card's files, so i can insert PG58IMG things to root, the phone is actually reads it. what if I somehow inject the Unlock_code.bin into some kind of PG58IMG, and apply this way the unlocking?
could be anything of these upper is working?
Click to expand...
Click to collapse
Nope can't/won't work
We could try one thing... Try changing cid
fastboot oem writecid HTC__001
Then ignore errors and reboot
fastboot reboot-bootloader
And check cid again
fastboot getvar cid
If it changed then you can very well flash European unbranded ruu and then boot to a working rom
If it not worked.. Then send a PM to FOOTBALL and ask for Indian ruu.. He might charge some minimal amount based on the scarcity of the ruu.. But if you got proper Indian ruu then you will come out of the boot loop fine
Sent from my Nexus 7 using xda premium
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
You have working adb when in boot loop?
Then you can try my temp-root and then jb SOFF process.. Link in my signature
Have slim chances of working.. But worth a try
Sent from my Nexus 7 using xda premium
ganeshp said:
Nope can't/won't work
We could try one thing... Try changing cid
fastboot oem writecid HTC__001
Then ignore errors and reboot
fastboot reboot-bootloader
And check cid again
fastboot getvar cid
If it changed then you can very well flash European unbranded ruu and then boot to a working rom
If it not worked.. Then send a PM to FOOTBALL and ask for Indian ruu.. He might charge some minimal amount based on the scarcity of the ruu.. But if you got proper Indian ruu then you will come out of the boot loop fine
Sent from my Nexus 7 using xda premium
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
You have working adb when in boot loop?
Then you can try my temp-root and then jb SOFF process.. Link in my signature
Have slim chances of working.. But worth a try
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
cid change is done, now it's HTC_001.
i tried to flash RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed's rom.zip from the temp, renamed to PG58IMG, copied to sdcard's root.
phone said: "lower hboot version"
is there any stock htc ROM with hboot 1.29?
if no, is it a possible way to change the zip to contain a 1.29 hboot version?
edit: i've got no bootloop, but at power-on I'm suddenly passed to fastboot screen without any boot process
but fastboot usb connection is always working, fastboot devices responses are always positive.
palomatE said:
cid change is done, now it's HTC_001.
i tried to flash RUU-Pyramid-ICS-hTC-Europe-3.33.401.53-Radio-11.76A.3504.00U-11.24A.3504.31-M-release-280871-signed's rom.zip from the temp, renamed to PG58IMG, copied to sdcard's root.
phone said: "lower hboot version"
is there any stock htc ROM with hboot 1.29?
if no, is it a possible way to change the zip to contain a 1.29 hboot version?
Click to expand...
Click to collapse
Awesome... That will solve our issue now
Do this copy the New PG58IMG zip file to your fastboot folder
And try these commands one by one
fastboot erase cache (if failed ignore it)
fastboot oem rebootRUU (black screen with silver HTC)
fastboot flash zip PG58IMG.zip (if failed stop there and don't do any thing else and simply paste back the output here)
fastboot reboot
Done
Edit: if the fail at third step is.. Something like.."Hboot pre update... Please flush the rom immediately again"] then repeat the third step again. (i.e this one fastboot flash zip PG58IMG.zip)
Sent from my Nexus 7 using xda premium
---------- Post added at 10:22 PM ---------- Previous post was at 10:12 PM ----------
palomatE said:
edit: i've got no bootloop, but at power-on I'm suddenly passed to fastboot screen without any boot process
but fastboot usb connection is always working, fastboot devices responses are always positive.
Click to expand...
Click to collapse
Now that we have successful cid change adb change is not required
Sent from my Nexus 7 using xda premium
ganeshp said:
Awesome... That will solve our issue now
Do this copy the New PG58IMG zip file to your fastboot folder
And try these commands one by one
fastboot erase cache (if failed ignore it)
fastboot oem rebootRUU (black screen with silver HTC)
fastboot flash zip PG58IMG.zip (if failed stop there and don't do any thing else and simply paste back the output here)
fastboot reboot
Done
Edit: if the fail at third step is.. Something like.."Hboot pre update... Please flush the rom immediately again"] then repeat the third step again. (i.e this one fastboot flash zip PG58IMG.zip)
Sent from my Nexus 7 using xda premium
---------- Post added at 10:22 PM ---------- Previous post was at 10:12 PM ----------
Now that we have successful cid change adb change is not required
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
faced into error again here is the output:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 3.121s]
finished. total time: 3.121s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.267s]
finished. total time: 3.267s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (436283 KB)... OKAY [ 58.448s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 129.037s
C:\Android>fastboot flash zip PG58IMG.zip - here i didn't hit enter
palomatE said:
faced into error again here is the output:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 3.121s]
finished. total time: 3.121s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.267s]
finished. total time: 3.267s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (436283 KB)... OKAY [ 58.448s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOchecking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 129.037s
C:\Android>fastboot flash zip PG58IMG.zip - here i didn't hit enter
Click to expand...
Click to collapse
hit enter ..if it fails again
reboot to bootloader using this command
fastboot reboot-bootloader
then can you give me the output of this command ?
fastboot getvar all (post everything except IMEI and serial number )
ganeshp said:
hit enter ..if it fails again
reboot to bootloader using this command
fastboot reboot-bootloader
then can you give me the output of this command ?
fastboot getvar all (post everything except IMEI and serial number )
Click to expand...
Click to collapse
i've made several attempts, all of them came out with the same results as I posted previously.
getvar results are the following:
Code:
C:\Android>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.29.0000
INFOversion-baseband: 11.24A.3504.31_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.33.401.106
INFOserialno: *** sent you via PM ***
INFOimei: *** sent you via PM ***
INFOproduct: pyramid
INFOplatform: HBOOT-8260
INFOmodelid: PG5813000
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 4064mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 705f86f6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.494s
hope this might help :angel:
hmm this has some weird combination (modelid indicates that the phone is normal sensation ..but firmware version says that the phone is xe!!!) ..but lets see
download the XE version of the same RUU you've downloaded earlier (will have LE in its Name) and get the rom.zip and flash the rom.zip manually using the fastboot commands ive given you earlier
ganeshp said:
hmm this has some weird combination (modelid indicates that the phone is normal sensation ..but firmware version says that the phone is xe!!!) ..but lets see
download the XE version of the same RUU you've downloaded earlier (will have LE in its Name) and get the rom.zip and flash the rom.zip manually using the fastboot commands ive given you earlier
Click to expand...
Click to collapse
i made the steps as you said with the LE version, the output is the following:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 1.654s]
finished. total time: 1.655s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.266s]
finished. total time: 3.266s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (433649 KB)... OKAY [ 58.937s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 128.859s
the image I tried to flash is the following:
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed
is it possible to change the modelid to XE (however the device itself is a plain sensation, maybe I can flash an XE version, then i might have a working system, this way somehow make an s-off or unlock to install a custom rom for plain sensation, and finally flash the stock ics kernel for the plain device?
palomatE said:
i made the steps as you said with the LE version, the output is the following:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 1.654s]
finished. total time: 1.655s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.266s]
finished. total time: 3.266s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (433649 KB)... OKAY [ 58.937s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 128.859s
the image I tried to flash is the following:
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed
is it possible to change the modelid to XE (however the device itself is a plain sensation, maybe I can flash an XE version, then i might have a working system, this way somehow make an s-off or unlock to install a custom rom for plain sensation, and finally flash the stock ics kernel for the plain device?
Click to expand...
Click to collapse
To change MID you need S-OFF. The RUU checks MID so if the 3.33.401.153 RUU fails try the 3.33.401.53 one
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
palomatE said:
i made the steps as you said with the LE version, the output is the following:
Code:
C:\Android>fastboot erase cache
< waiting for device >
erasing 'cache'... OKAY [ 1.654s]
finished. total time: 1.655s
C:\Android>fastboot oem rebootRUU
... INFOStart Verify: 3
INFOStart Verify: 3
INFOerase sector 130560 ~ 131071 (512)
OKAY [ 3.266s]
finished. total time: 3.266s
C:\Android>fastboot flash zip PG58IMG.zip
sending 'zip' (433649 KB)... OKAY [ 58.937s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 128.859s
the image I tried to flash is the following:
RUU_PYRAMID_LE_ICS_35_S_HTC_Europe_3.33.401.153_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_281004_signed
is it possible to change the modelid to XE (however the device itself is a plain sensation, maybe I can flash an XE version, then i might have a working system, this way somehow make an s-off or unlock to install a custom rom for plain sensation, and finally flash the stock ics kernel for the plain device?
Click to expand...
Click to collapse
Ahh as suspected
What happened is you have somehow flashed sensation xe hboot and rest of them have normal sensation counterparts...
I need you to do something now... Download the universal 3.33 firmware from kohr-ah firmware thread in sensation development section..
Then extract the zip
Open android-info.txt file and replace version-main with 3.33.401.53
And save it
Also you have the rom.zip of the normal sensation 3.33.401.53 right.. Get the hboot.nb0 (the name will be big but the extension remains same) and replace the hboot.nb0 present in the firmware zip with this one..
Then remake the firmware.. PG58IMG.zip
Then try to flash this... Obviously it will fail.. But if that replaces the hboot you are having then all is well
So after the above exercise.. You need to try flashing normal sensation rom.zip again
Hopefully it works
Sent from my HTC Sensation using xda premium
so i had to give back the phone to its owner, if the main htc service fails im goin to do the rest you suggested me. anyway i want to say thanks to all of you guys out there, i'll be back for more info, in case of fail. have a nice day
Sent from my GT-I9000 using xda app-developers app
I installed the maximus rom for htc one s,i installed the firmware for it,flashed the rom,i did everything but i went to recovery and it said 48mb storage.When i was using the rom i mounted it from the android its self and deleted the os(I was panicking). I read online and it said u have to install the recovery from the install package . So i installed the recovery file and got it back to normal. Today i panicked and put it on s-on. Then i tried adb side loading a rom and i couldn't figure it out so i went to fastboot usb and i did "fastboot flash zip Energyrom.zip" it didn't work and said failed so i went back to recovery and it is 48 mb again.I reflashed the recovery but that didn't work . What do i do i need my phone fixed asap. Please respond if you know the fix to the problem. (Im only 12 pleease help me). Thanks in advanced
Whats your hboot and what's your radio?
Sent from my HTC One S
my radio hboot is 2.16.0000
My radio is 1.20.50.05.16
How did you get the phone S-ON again? ?
I had the same issue as you for me it helped to install the TWRP 2.6.10 and then i made a sideload.
With any other Recovery your storage stays at 48mb you have to have this version of the TWRP recovery.
I will post some quotes as soon as the search function is avalible again.
EDIT: follow this guide:
http://forum.xda-developers.com/showthread.php?p=45621060
I used the all in one tool kit and i ran the command to s-on, I tried to flash the recover from the install package but it still says 48mb.
Edit: i tried the link u sent but when i try to flash the firmware this comes up
Edit:By the way i have no os installed on my htc one s. And does this mean its bricked ?
C:\Users\Dragon\Downloads\One_S_All-In-One_Kit_v4.0\One_S_All-In-One_Kit_v\Data>
fastboot flash zip firmware.zip
sending 'zip' (36985 KB)...
OKAY [ 2.634s]
writing 'zip'...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.751s
C:\Users\Dragon\Downloads\One_S_All-In-One_Kit_v4.0\One_S_All-In-One_Kit_v\Data>
fastboot flash zip firmware.zip
sending 'zip' (36985 KB)...
OKAY [ 2.625s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.891s
cyberusman said:
I used the all in one tool kit and i ran the command to s-on, I tried to flash the recover from the install package but it still says 48mb.
Edit: i tried the link u sent but when i try to flash the firmware this comes up
Edit:By the way i have no os installed on my htc one s. And does this mean its bricked ?
C:\Users\Dragon\Downloads\One_S_All-In-One_Kit_v4.0\One_S_All-In-One_Kit_v\Data>
fastboot flash zip firmware.zip
sending 'zip' (36985 KB)...
OKAY [ 2.634s]
writing 'zip'...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.751s
C:\Users\Dragon\Downloads\One_S_All-In-One_Kit_v4.0\One_S_All-In-One_Kit_v\Data>
fastboot flash zip firmware.zip
sending 'zip' (36985 KB)...
OKAY [ 2.625s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.891s
Click to expand...
Click to collapse
Did you tried to flash it or did you flashed it? Its necessary to have it on your device with 2.16 HBOOT! Have you an working ADB on your computer? If not download it (http://developer.android.com/sdk/index.html).
Its much better than any toolkit. Error 99 just shows up because your SDK/ADB is outdated thats why its not working.
So first of all install the newest version of AndroidSDK (link above) then write back.
miniAndroidian said:
Did you tried to flash it or did you flashed it? Its necessary to have it on your device with 2.16 HBOOT! Have you an working ADB on your computer? If not download it (http://developer.android.com/sdk/index.html).
Its much better than any toolkit. Error 99 just shows up because your SDK/ADB is outdated thats why its not working.
So first of all install the newest version of AndroidSDK (link above) then write back.
Click to expand...
Click to collapse
I was using the files from the toolkit but i had a older vs of fastboot/adb on my pc (About a week old) this is what came up
C:\Users\Dragon\Downloads\adt-bundle-windows-x86_64-20130917\adt-bundle-windows-
x86_64-20130917\sdk\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.075s]
finished. total time: 0.075s
C:\Users\Dragon\Downloads\adt-bundle-windows-x86_64-20130917\adt-bundle-windows-
x86_64-20130917\sdk\platform-tools>fastboot flash zip firmware.zip
sending 'zip' (36985 KB)...
OKAY [ 2.548s]
writing 'zip'...
FAILED (remote: 92 supercid! please flush image again immediately)
finished. total time: 2.645s
C:\Users\Dragon\Downloads\adt-bundle-windows-x86_64-20130917\adt-bundle-windows-
x86_64-20130917\sdk\platform-tools>fastboot flash zip firmware.zip
< waiting for device >
sending 'zip' (36985 KB)...
OKAY [ 2.547s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 2.801s
C:\Users\Dragon\Downloads\adt-bundle-windows-x86_64-20130917\adt-bundle-windows-
x86_64-20130917\sdk\platform-tools>fastboot flash zip TWRP_2.6.1.0_ville_4.2.2.z
ip
sending 'zip' (8835 KB)...
OKAY [ 0.997s]
writing 'zip'...
(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[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,12
(bootloader) [RUU]UZ,recovery,23
(bootloader) [RUU]UZ,recovery,35
(bootloader) [RUU]UZ,recovery,46
(bootloader) [RUU]UZ,recovery,57
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,86
(bootloader) [RUU]UZ,recovery,99
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,100
(bootloader) ..... OK
OKAY [ 4.294s]
finished. total time: 5.292s
EDIT: OMG THANK YOU IT WORKED MY SDCARD IS 12GB THANK YOU..... But How do you adbs side load i cant figure it out please help me
cyberusman said:
EDIT: OMG THANK YOU IT WORKED MY SDCARD IS 12GB THANK YOU..... But How do you adbs side load i cant figure it out please help me
Click to expand...
Click to collapse
Sideload works just as i described in another post:
http://forum.xda-developers.com/showpost.php?p=45798359&postcount=825
Just open up TWRP and choose the sideload option and then just follow the link above (type the commands in the ADB to sideload the ROM, the you just click on install .zip and choose the "sideload.zip" but remember you have to have S-OFF again after Flashing MaximusHD)
If i helped you you can alway click the thanks button, i really appreciate this
miniAndroidian said:
Sideload works just as i described in another post:
http://forum.xda-developers.com/showpost.php?p=45798359&postcount=825
Just open up TWRP and choose the sideload option and then just follow the link above (type the commands in the ADB to sideload the ROM, the you just click on install .zip and choose the "sideload.zip" but remember you have to have S-OFF again after Flashing MaximusHD)
If i helped you you can alway click the thanks button, i really appreciate this
Click to expand...
Click to collapse
OMG IF I COULD I WOULD THANK YOU X1000 XD. Im Going to try to adb side load7
Edit: I did not make a nandroid backup before flashing a rom so do you know how to get my phone back to stock ?
My carier is Fido(Owned by rogers) So i can use the rogers ruu for ti but i don't know any compatible roms for the ruu
I Go on every day at 3:00 pm Eastern Time. Im going to try to side load the rom tomorrow
Edit: Also is there any way i can go back to how my recovery was ( With out sideloading ) So i can mount and flash instead ? Because im going to get a rom compatible with hboot 2.16 then put s-off again then im going to find out how to downgrade it back to normal. My only question is how do i install a ruu And which rom should i install it on.... Im going to get the rogers ruu for my htc one s.
cyberusman said:
I Go on every day at 3:00 pm Eastern Time. Im going to try to side load the rom tomorrow
Edit: Also is there any way i can go back to how my recovery was ( With out sideloading ) So i can mount and flash instead ? Because im going to get a rom compatible with hboot 2.16 then put s-off again then im going to find out how to downgrade it back to normal. My only question is how do i install a ruu And which rom should i install it on.... Im going to get the rogers ruu for my htc one s.
Click to expand...
Click to collapse
1st of all only the maximushd ROM is compatible with the 2.16 hboot and not any other ROM yet. So you have to downgrade your hboot first. (i dont know exactly how it works but im sure you'll get help in this forum if you ask for it )
2nd: The right RUU for your One S depends on where you live for example (europe or "WWE" for world wide, or north america,) then you have to choose the right carrier for your phone but only if its carrier branded if not then take a non branded ruu.
Then you have to choose the version of the RUU for e.g. 4.1.1 for the latest one.
The right RUU for me would be the "OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip" one
3rd you cant simply flash a RUU via recovery. A RUU is an .exe file for your pc and your phone has to be connected to your pc to flash it. If the RUU setup shows errors, like "hboot is too new/unknown" you have to downgrade your hboot manually before flashing a RUU.
Hi do you know any roms that are compatible withh hboot 2.16 that DONT need s-off because im going to s-off from that rom then downgrade my hboot so i cant run viper one s
Can u please help me find a rom that is compatible with hboot 2.16 and u dont need s-off ?
cyberusman said:
Can u please help me find a rom that is compatible with hboot 2.16 and u dont need s-off ?
Click to expand...
Click to collapse
According to this thread, the Magiorom is compatible with 2.16 and S-ON. Give it a shot.
http://forum.xda-developers.com/showthread.php?t=2470503
tsphan said:
According to this thread, the Magiorom is compatible with 2.16 and S-ON. Give it a shot.
http://forum.xda-developers.com/showthread.php?t=2470503
Click to expand...
Click to collapse
So any version of the magio Rom?
EDIT: I wont be able to flash the rom today because i need to go to seep
Hi, I need help flashing my device back to stock. I tried following this guide. http://forum.xda-developers.com/showthread.php?t=2542219&highlight=sparsechunk But I keep experiencing so many errors.
The following is the error that I get when I do the command for sparsechunk. It keeps returning FAILED. Can someone please help me out with this?
C:\Users\xxxxxxx\Desktop\US_retail_XT1034_14.10.0Q3.X-84-16_CFC.xml\US_retail_XT1
034_14.10.0Q3.X-84-16_CFC.xml>fastboot flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.048s
C:\Users\xxxxxx\Desktop\US_retail_XT1034_14.10.0Q3.X-84-16_CFC.xml\US_retail_XT1
034_14.10.0Q3.X-84-16_CFC.xml>fastboot flash system system.img_sparsechunk1
target reported max download size of 536870912 bytes
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.029s
Have you unlocked your bootloader, as 2 of the lines you have posted say, bootloader permission denied.
Sent from my Moto G using xda app-developers app
Ever happened to me the error in the first file system. But others continued running normally and had no problems.
Do your sparsechunk images start from 1 or from 0 ?
Same issue
mokkami said:
Do your sparsechunk images start from 1 or from 0 ?
Click to expand...
Click to collapse
Having the exact same problem
going to try and place all the files in a separate folder and start over
---------- Post added at 03:44 PM ---------- Previous post was at 03:18 PM ----------
Xcarab said:
Having the exact same problem
going to try and place all the files in a separate folder and start over
Click to expand...
Click to collapse
I fixed my problem.. this is what you should try.
1. Download the stock rom.. perfect for your phone and carrier.
2. Follow teh step by step but when you reach the sparcechuck.. go to teh folder where you unzipped the files from the rom and make sure the names match...
That is how i fixed mine
I have no problem, i wanted to help.
But that what you said was exactly that what i was talking about
But don't rename the file. Just change the fastboot command from 0 to 1 or the other way round.
There are some firmwares which start from 1 others start from 0.
So depending on your firmware you have to start with
fastboot flash system system.img_sparsechunk1
or with
fastboot flash system system.img_sparsechunk0
And as you said youl'll find that out if you look into the folder of the extracted ZIP file.
A friend brought a HTC One Mini in a very unusual situation to me. The phone bootloader is "Locked" and "S-ON". It only boots to fastboot usb mode only. The battery is still ok because I checked with a script that is used to charge in that mode when the battery is low; at least it still has about 3870mV, and the minimum is around 3680mV. The problem is that:
1. When I try to unlock so I can flash a custom TWRP recovery the unlock spalsh screen does not appear, although the unlock command says sucessful.
C:\fastboot-win>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.154s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.006s]
finished. total time: 0.161s
Click to expand...
Click to collapse
2. I downloaded this stock file OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_HK_3.10.708.4-2.12.708.3_release_351634.zip because it matches the OS version showing on the fastboot screen on the phone. When I try to flash it from fastboot I get this error:
C:\fastboot-win>fastboot flash zip OTA_M4_UL_K44_SENSE55_MR_hTC_Asia_HK_3.10.708.4-2.12.708.3_release_351634.zip
sending 'zip' (346477 KB)...
OKAY [ 16.826s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 49.466s
Click to expand...
Click to collapse
Can anyone please render any help? I can follow any instructions to the letter, just that I have never come across this kind of issue before.
Thanks in advance.
Here's my issue. Some time back I installed TWRP in order to install the Pixel Launcher as a system app. When Nougat came out I tried to install the ota. No go. So I installed a stock recovery and relocked the bootloader. Still no luck. I've tried every way possible to install Nougat: ruu.exe, from sd card, flash through adb. Nothing.
I think my stock recovery is problematic. When I try and get into it through the bootloader I get the dreaded red triangle with exclamation mark. So I've tried two ways of extracting the recovery.img from the Nougat update. I've used process monitor and the trick of looking in %temp% after starting the ruu.exe. I get the correct size zip, but when I unzip, whether through 7zip or winzip, I just get a series of 22 smaller zips and have no idea where in all those the recovery image is hiding.
Anyone have any ideas what I'm doing wrong or where I can download the nougat recovery image for sprint?
revcp said:
Here's my issue. Some time back I installed TWRP in order to install the Pixel Launcher as a system app. When Nougat came out I tried to install the ota. No go. So I installed a stock recovery and relocked the bootloader. Still no luck. I've tried every way possible to install Nougat: ruu.exe, from sd card, flash through adb. Nothing.
I think my stock recovery is problematic. When I try and get into it through the bootloader I get the dreaded red triangle with exclamation mark. So I've tried two ways of extracting the recovery.img from the Nougat update. I've used process monitor and the trick of looking in %temp% after starting the ruu.exe. I get the correct size zip, but when I unzip, whether through 7zip or winzip, I just get a series of 22 smaller zips and have no idea where in all those the recovery image is hiding.
Anyone have any ideas what I'm doing wrong or where I can download the nougat recovery image for sprint?
Click to expand...
Click to collapse
The recovery isn't related to anything in the RUU process, it doesn't matter what version you have. If you want to upgrade from marshmallow to Nougat using a RUU you'll first need to update the firmware so your phone can read HTC's new digital signature, without doing that you'll always get signature errors when flashing the ruu. You can find the sprint RUU and firmware in my RUU collection thread (general section).
FYI, ruu are encrypted. You can't simply unzip these files. You need to decrypt using the correct decryption key.
Thank you. It's been a while since I've dived down into a phone. Is there a step by step on how to update the firmware?
So, tried to update the firmware. Here's the result (after doing the "fastboot oem rebootRUU" step):
D:\Android\platform-tools>htc_fastboot flash zip firmware2.18.651.2.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
sending 'zip' (99604 KB)...
OKAY [ 4.927s]
writing 'zip'...
(bootloader) HOSD CL#747079
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8 RU_SIGNATURE_FAIL )
finished. total time: 19.760s
htc_fastboot finished. total time: 19.925s
And now trying the .zip on root of sd method I get this after executing command:
8 RU_SIGNATURE_FAIL
8 RU_SIGNATURE_FAIL
FAIL8 RU_SIGNATURE_FAIL
revcp said:
So, tried to update the firmware. Here's the result (after doing the "fastboot oem rebootRUU" step):
D:\Android\platform-tools>htc_fastboot flash zip firmware2.18.651.2.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target reported max download size of 800000000 bytes
sending 'zip' (99604 KB)...
OKAY [ 4.927s]
writing 'zip'...
(bootloader) HOSD CL#747079
(bootloader) GPT is up-to-dated. [17408]
(bootloader) Perform pre-update
(bootloader) ERR ZIP signature checking failed...
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 8
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 8
(bootloader) [email protected]
FAILED (remote: 8 RU_SIGNATURE_FAIL )
finished. total time: 19.760s
htc_fastboot finished. total time: 19.925s
Click to expand...
Click to collapse
Sorry I thought your phone was S-OFF, this firmware package is decrypted so it can't be flashed on a S-ON phone. If you can find the 2.18.651.2 ota zip file, you can extract the signed firmware from it. (signed version can be flashed with S-ON). You should be able to get the ota file from your phone by selecting "download and install later". Once downloaded you can transfer the ota from your phone to your computer and extract the firmware.zip file from it using winrar / 7zip.
There's another thing I don't understand about this.
The FAQ directions in https://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344 say to " rename the RUU zip file '2PQ9IMG.zip'". But there is no RUU zip file. There is RUU.EXE and the firmware zip file.
revcp said:
There's another thing I don't understand about this.
The FAQ directions in https://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344 say to " rename the RUU zip file '2PQ9IMG.zip'". But there is no RUU zip file. There is RUU.EXE and the firmware zip file.
Click to expand...
Click to collapse
These instructions are for flashing ruu in zip format. how to flash.exe ruu explained just below.
.zip ruu can be extracted from the .exe version if needed (on some pc, a .exe ruu can be problematic, e.g. you double click the file to launch the process and nothing happen...)
---------- Post added at 11:54 AM ---------- Previous post was at 11:51 AM ----------
Btw if you can share your firmware.zip extracted from the OTA it would be really nice for other Sprint users in the same situation. I wasn't able to find the Sprint ota zip file anywhere yet.
alray said:
Sorry I thought your phone was S-OFF, this firmware package is decrypted so it can't be flashed on a S-ON phone. If you can find the 2.18.651.2 ota zip file, you can extract the signed firmware from it. (signed version can be flashed with S-ON). You should be able to get the ota file from your phone by selecting "download and install later". Once downloaded you can transfer the ota from your phone to your computer and extract the firmware.zip file from it using winrar / 7zip.
Click to expand...
Click to collapse
That's what I need! Thanks! Any idea where the dl is saved on the phone? I should have noted that I was s-on. Sorry.
revcp said:
That's what I need! Thanks! Any idea where the dl is saved on the phone? I should have noted that I was s-on. Sorry.
Click to expand...
Click to collapse
For the M9 it was in data/data/com.htc.updater/files I guess it should be similar for the A9. Maybe someone else could confirm this...
Well, I'm dead in the water. I've tried every way possible to dl the ota, but when I go to /android/data/com/htc.updater/files there is nothing there. A 2.18.651.2 ota zip file is nowhere to be found. If anyone has that for spring I would love to get my hands on it.