Database Info

[Q]htc one s internal sd is 48mb please help

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

The Official RUU of M8 for Windows Phone (Verizon Edition)

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...

[GUIDE] Downgrade firmware 2.1x to 1.5x (S-OFF)

So you want to use the latest custom ROM but you're on 2.1x firmware. That's not an big issue as long as you're S-OFF. If you're not S-OFF download, install and run Sunshine-3.5.8 (or higher when available). Follow instructions and pay the $25,= You'll be S-OFF within 5 minutes and it's really worth the money considering the functionality you get in return.
Now that you're S-OFF it's time to downgrade the firmware. In order to do so you need the right RUU which can be found in this threat. Download the RUU (zip) to your computer.
Within this RUU you'll find the firmware we need but it's encrypted. Now download the RUU_Decryption_Tool.zip and extract it to any folder of your likings. Let's call it c:\RDT\ e.g. The executable in this folder is a command, not a GUI. Copy the RUU to the same folder RDT and rename it to RUU.zip.
Open up a commandprompt (windows-key - cmd.exe) and head to the folder RDT. Now enter RUU_Decryption_Tool RUU.zip You'll be asked what to do in a menu. All you need is to extract the firmware, nothing else! The tool will decrypt the firmware and copy it to a subfolder. Move to the new folder "firmware" and compress all the files within this folder to a ZIP-file called firmware.zip It does not have to be signed since we're S-OFF.
We've got two important files now. The firmware.zip and the RUU file. To be able to use the RUU rename it to 2PQ9IMG.zip and copy it to the root of your SD-card. While we're copying anyway you might want to copy your custom ROM, GAPPS etc. to the SD-card as well!
Copy the firmware.zip to your adb fastboot folder
Boot your device into download mode. It will ask you if you want to install the RUU (2PQ9IMG.zip). Press volume down to pass. Open up a commandprompt and enter the following fastboot command: htc_fastboot flash zip firmware.zip First time will fail but no panic. Your device will reboot and repeat the command by itself. The firmware will be installed, this doesn't take long.
Once finished, reboot your device again into download mode and install the RUU (volume up). When it's done reboot your device and android will show up. Wait until setup screen so that all partitions will work and reboot again to download mode. Now flash the latest TWRP. Open a commandprompt and enter: htc_fastboot flash recovery twrp-3.1.1-0-hiae.img Reboot into recovery mode and do a data wipe. TWRP will ask you to comfirm this by typing "yes". Once done select advanced wipe and wipe the dalvik/cache and system partitions. After this it's business as usual. Flash your custom ROM, SuperSU, GApps etc. and reboot.
done. :good:
I hope this will help out some people. I've done this several times and it's pretty safe. Nevertheless, don't blame be for wrecking your device if something goes wrong!

As I can remember Qc 3.0 support came with an update. If I downgrade to 6.0 will I continue to use Qc 3.0 ?

I tried this like 15 times. S-off. 2.18.617.30. Unlocked. Rooted.
c:\Sam>htc_fastboot flash zip firmware.zip
sending 'zip'... (133925 KB) OKAY
sending time = 6.731 secs
writing 'zip'... (bootloader) HOSD CL#861328
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAIL22 RU_HEADER_ERROR
FAILED (remote: 22 RU_HEADER_ERROR )
Execution time is 9(s)

Trying from this
https://forum.xda-developers.com/showpost.php?p=73489502&postcount=825

thank you succesfully downgraded ...

Nuroxy said:
I tried this like 15 times. S-off. 2.18.617.30. Unlocked. Rooted.
c:\Sam>htc_fastboot flash zip firmware.zip
sending 'zip'... (133925 KB) OKAY
sending time = 6.731 secs
writing 'zip'... (bootloader) HOSD CL#861328
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAIL22 RU_HEADER_ERROR
FAILED (remote: 22 RU_HEADER_ERROR )
Execution time is 9(s)
Click to expand...
Click to collapse
pls zip files into firmware.zip.not firmware folder to zip.:good::good:

hmm may i , just a short question .. why do i need S-OFF ?

solved said:
hmm may i , just a short question .. why do i need S-OFF ?
Click to expand...
Click to collapse
You need s-off to disable signature verification on all partitions since your home-made firmware.zip will not be signed with HTC's key.

Any htc one a9 device supported
Any htc one a9 device supported
Please emergency ans the question

alray said:
You need s-off to disable signature verification on all partitions since your home-made firmware.zip will not be signed with HTC's key.
Click to expand...
Click to collapse
It's there a way to extract those HTC Keys and Sign the zip with them ? I mean to get the ''certificate.Perm and Key.pk8''.?

HckruxRD said:
It's there a way to extract those HTC Keys and Sign the zip with them ? I mean to get the ''certificate.Perm and Key.pk8''.?
Click to expand...
Click to collapse
The only key that can be extracted from a signed RUU or a signed firmware is the public key present on every phone. The private key used by htc to sign their files is, afaik, impossible to know. I'm pretty sure devs wouldn't waste time on S-OFF if signing your own file was possible...

please help, I kept getting this error about sensor_hub.img
it never flashed successfully

Help please

Hi everyone, could you please help me i have a htc A9 and i face a bootloop . the phone hasn't the usb debugging on and it is S-on, i tried with fastboot to change the ruu but impossible always have failed in cmd prompt
Code:
(bootloader) kernel: lk
(bootloader) product: htc_hiaeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 751200000
(bootloader) serialno: HT5ARBE06603
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 352636071084888
(bootloader) version-main: 2.16.163.4
(bootloader) boot-mode: RUU
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ910000
(bootloader) cid: VODAP203
if someone has an idea i would appreciate coz i'm stuck
I tried to flash a rom using fastboot and i get this error message
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip 2PQ9IMG.zip
target reported max download size of 751200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 278606042 is not a multiple of the block size 4096
sending sparse 'zip' (733590 KB)...
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
OKAY [ 32.033s]
writing 'zip'...
(bootloader) HOSD CL#853511
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_h
(bootloader) RvMuM
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 57.319s
thanks for your help

kabelou said:
Hi everyone, could you please help me i have a htc A9 and i face a bootloop . the phone hasn't the usb debugging on and it is S-on, i tried with fastboot to change the ruu but impossible always have failed in cmd prompt
Code:
(bootloader) kernel: lk
(bootloader) product: htc_hiaeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 751200000
(bootloader) serialno: HT5ARBE06603
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 352636071084888
(bootloader) version-main: 2.16.163.4
(bootloader) boot-mode: RUU
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ910000
(bootloader) cid: VODAP203
if someone has an idea i would appreciate coz i'm stuck
I tried to flash a rom using fastboot and i get this error message
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip 2PQ9IMG.zip
target reported max download size of 751200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 278606042 is not a multiple of the block size 4096
sending sparse 'zip' (733590 KB)...
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
OKAY [ 32.033s]
writing 'zip'...
(bootloader) HOSD CL#853511
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_h
(bootloader) RvMuM
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 57.319s
thanks for your help
Click to expand...
Click to collapse
What ruu version are you trying to flash?
Are you using htc_fastboot.exe or fastboot.exe?

alray said:
What ruu version are you trying to flash?
Are you using htc_fastboot.exe or fastboot.exe?
Click to expand...
Click to collapse
i tried a lot of ruu, an european ruu, vodaphone uk, etc
the htc_fastboot command doesn't work coz it's an old version, i tried to find the newest one but i didn't.
And the fastboot.exe it's the last version in android sdk manager and it's the only thing working...i cannot found ruu with cid vodap203....the phone is from france so if you can help me thanks

kabelou said:
i tried a lot of ruu, an european ruu, vodaphone uk, etc
the htc_fastboot command doesn't work coz it's an old version, i tried to find the newest one but i didn't.
And the fastboot.exe it's the last version in android sdk manager and it's the only thing working...i cannot found ruu with cid vodap203....the phone is from france so if you can help me thanks
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash RUU not fastboot.exe . The only ruu version that will work on your phone is 2.16.163.4 check on easy-firmware.com it's there

alray said:
You must use htc_fastboot.exe to flash RUU not fastboot.exe . The only ruu version that will work on your phone is 2.16.163.4 check on easy-firmware.com it's there
Click to expand...
Click to collapse
Hello Alray,
i tried to download the RUU you said but its not possible becaus i have to pay for it? do you have any access or are you able to download it ? if not no worries and thanks for help!!!.

Flahable zip
Would you like a flashable zip of the htc one a9 boostmobile/sprint stock rom with root?

anonymouseli said:
Would you like a flashable zip of the htc one a9 boostmobile/sprint stock rom with root?
Click to expand...
Click to collapse
Am glad that you asked this, I know that this is a different thread but I have been looking for a nougat flashable zip, am using HTC One A9 sprint version 1.10.651.1 hiaewhl S-OFF and boot loader unlocked, it's rooted with twrp 2.8.7.0 installed..I just want to grab this opportunity. I need to update my phone to nougat and return to stock.. I saw RUU.exe but I realized that you will flash firmware first before RUU.exe ,I didn't see RUU.zip for hiaewhl and I have not use RUU before..help me out.. I need any rom I can flash through custom recovery.. Is it safe for me to flash custom rom for hiaeul on my hiaewhl being S-OFF and bootloader unlocked? Pls your reply..
Sent from my 2PQ93 using XDA-Developers Legacy app

CAMERON1988 said:
Am glad that you asked this, I know that this is a different thread but I have been looking for a nougat flashable zip, am using HTC One A9 sprint version 1.10.651.1 hiaewhl S-OFF and boot loader unlocked, it's rooted with twrp 2.8.7.0 installed..I just want to grab this opportunity. I need to update my phone to nougat and return to stock.. I saw RUU.exe but I realized that you will flash firmware first before RUU.exe ,I didn't see RUU.zip for hiaewhl and I have not use RUU before..help me out.. I need any rom I can flash through custom recovery.. Is it safe for me to flash custom rom for hiaeul on my hiaewhl being S-OFF and bootloader unlocked? Pls your reply..
Sent from my 2PQ93 using XDA-Developers Legacy app
Click to expand...
Click to collapse
You should be alright ill upload it tomorrow

anonymouseli said:
You should be alright ill upload it tomorrow
Click to expand...
Click to collapse
I will be grateful
Sent from my 2PQ93 using XDA-Developers Legacy app

Stock Rom Rooted
CAMERON1988 said:
I will be grateful
Sent from my 2PQ93 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Okay here is a link to download the rom becuase , i just finish uploading it and its around 4gbs or so.
https://anonfile.com/E1P1E7mdbb/TWRP_zip
Steps to recover
1) First thing you should do is extract the rom, DO NOT FLASH THE ZIP FILE !!! .
2)Delete any old twrp folders in your sd card or phone storage, dont worry it will not affect the recovery itself.
3))Put the twrp folder in your device or sd card, however you can transfer it, its better if its on an sd card(make sure the folder says twrp).
4)Turn off the device and reboot into recovery.
5)Afterwards format the entire phone (Dont use factorey reset, use format data)just make sure you dont delete anything from the sd card.
6) Next go into restore or backup whatever its called and restore the rom from your sdcard, it should automatically detect the folder and if it doesnt try choosing the folder manually.
7) reboot the phone and give it sometime and if doesn't boot up after 20 minutes delete the cache or factory reset.
8) let me know if you got any questions email: [email protected]
---------- Post added at 06:32 PM ---------- Previous post was at 06:30 PM ----------
anonymouseli said:
Okay here is a link to download the rom becuase , i just finish uploading it and its around 4gbs or so.
https://anonfile.com/E1P1E7mdbb/TWRP_zip
Steps to recover
1) First thing you should do is extract the rom, DO NOT FLASH THE ZIP FILE !!! .
2)Delete any old twrp folders in your sd card or phone storage, dont worry it will not affect the recovery itself.
3))Put the twrp folder in your device or sd card, however you can transfer it, its better if its on an sd card(make sure the folder says twrp).
4)Turn off the device and reboot into recovery.
5)Afterwards format the entire phone (Dont use factorey reset, use format data)just make sure you dont delete anything from the sd card.
6) Next go into restore or backup whatever its called and restore the rom from your sdcard, it should automatically detect the folder and if it doesnt try choosing the folder manually.
7) reboot the phone and give it sometime and if doesn't boot up after 20 minutes delete the cache or factory reset.
8) let me know if you got any questions email: [email protected]
Click to expand...
Click to collapse
w.
---------- Post added at 06:32 PM ---------- Previous post was at 06:32 PM ----------
anonymouseli said:
Okay here is a link to download the rom becuase , i just finish uploading it and its around 4gbs or so.
https://anonfile.com/E1P1E7mdbb/TWRP_zip
Steps to recover
1) First thing you should do is extract the rom, DO NOT FLASH THE ZIP FILE !!! .
2)Delete any old twrp folders in your sd card or phone storage, dont worry it will not affect the recovery itself.
3))Put the twrp folder in your device or sd card, however you can transfer it, its better if its on an sd card(make sure the folder says twrp).
4)Turn off the device and reboot into recovery.
5)Afterwards format the entire phone (Dont use factorey reset, use format data)just make sure you dont delete anything from the sd card.
6) Next go into restore or backup whatever its called and restore the rom from your sdcard, it should automatically detect the folder and if it doesnt try choosing the folder manually.
7) reboot the phone and give it sometime and if doesn't boot up after 20 minutes delete the cache or factory reset.
8) let me know if you got any questions email: [email protected]
Click to expand...
Click to collapse
w.

OK thanks a lot, I will download it when I subscribe to a data plan because there's no Wi-Fi here
Sent from my 2PQ93 using XDA-Developers Legacy app

I couldn't download the file as it is failing whenever it gets to 1.97Gb I have tried several times but still the same I have spent almost 7gb but couldn't still get it downloaded..I don't know whether the fault is from the link or not
Sent from my 2PQ93 using XDA-Developers Legacy app

Pixel3 Blueline Slot A is dead

It seems my slot A is dead. No matter what I try I cannot boot to it.
I've tried flash.android.com to flash back to stock, even tried going back to Pie, and back to Q, but still Slot A is dead.
With stock Pie I flashed TWRP and tried flashing custom ROM to both slots, but slot A always fails.
Tried sideloading factory OTA and LineageOS, but it keeps failing.
Tried ./flash-all.sh using a few different ROMs, stock and CalyxOS, but it always fails with the following error.
target reported max download size of 268435456 bytes
sending 'bootloader_a' (8537 KB)...
OKAY [ 0.340s]
writing 'bootloader_a'...
(bootloader) Flashing Pack version b1c1-0.2-6374987
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition cmnlib_a
(bootloader) Flashing partition cmnlib64_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition storsec_a
(bootloader) Flashing partition logfs
OKAY [ 0.279s]
finished. total time: 0.619s
rebooting into bootloader...
OKAY [ 0.060s]
finished. total time: 0.110s
target reported max download size of 268435456 bytes
sending 'radio_a' (71436 KB)...
OKAY [ 2.050s]
writing 'radio_a'...
(bootloader) Flashing Pack version SSD:g845-00107-200409-B-6382632
(bootloader) Flashing partition modem_a
OKAY [ 0.418s]
finished. total time: 2.467s
rebooting into bootloader...
OKAY [ 0.060s]
finished. total time: 0.110s
extracting android-info.txt (0 MB)...
extracting boot.img (64 MB)...
target reported max download size of 268435456 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB)...
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (787 MB)...
archive does not contain 'system.sig'
extracting system_other.img (152 MB)...
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB)...
archive does not contain 'vbmeta.sig'
extracting vendor.img (440 MB)...
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: b1c1-0.2-6374987
Baseband Version.....: g845-00107-200409-B-6382632
Serial Number........: 96KX220PE
--------------------------------------------
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s

When slot A is active and I run fastboot flash boot boot.img for installing LineageOS, it will not boot to recovery, but if I set slot B active and do that then recovery works fine.

Do you have the most recent platform tools, and are you definitely launching the ./flash-all from the platform tools folder and not a path referencing an older version (AKA the version of fastboot and ADB that install from apt)?

sliding_billy said:
Do you have the most recent platform tools, and are you definitely launching the ./flash-all from the platform tools folder and not a path referencing an older version (AKA the version of fastboot and ADB that install from apt)?
Click to expand...
Click to collapse
Can you explain how to do that?
What I am doing is downloading the zip file from developer.google.com under Factory Images. Then I unzip that file open the folder and find the flash-all.sh file, open terminal in that folder and run the file using command ./flash-all.sh
Is there a way to run that file from somewhere other than where it is located?

The Lepricon said:
Can you explain how to do that?
What I am doing is downloading the zip file from developer.google.com under Factory Images. Then I unzip that file open the folder and find the flash-all.sh file, open terminal in that folder and run the file using command ./flash-all.sh
Is there a way to run that file from somewhere other than where it is located?
Click to expand...
Click to collapse
Extract the .zip directly into your platform tools folder and then with that folder open right click and open terminal from the folder. That is easier than changing your terminal path and should result in the ./ running directly from that place. Again, be sure you are running the current platform tools.

Hi, I'm not sure if you wrongly wrote the file extension, but shouldn't you run the flash-all.bat instead of the flash-all.sh?

Vanschtezla said:
Hi, I'm not sure if you wrongly wrote the file extension, but shouldn't you run the flash-all.bat instead of the flash-all.sh?
Click to expand...
Click to collapse
Clearly, he is not using Windows (the ./ command in the OP) so .bat file is not relevant.

sliding_billy said:
Clearly, he is not using Windows (the ./ command in the OP) so .bat file is not relevant.
Click to expand...
Click to collapse
I see. Thanks for clarifying that.

I'm running Ubuntu. I also tried Windows and ran the .bat file and got pretty well the same result.
@ sliding_billy I've been pretty busy the last couple days so haven't tried your advice yet. Hoping to get a chance tonight after work.

The Lepricon said:
I'm running Ubuntu. I also tried Windows and ran the .bat file and got pretty well the same result.
@ sliding_billy I've been pretty busy the last couple days so haven't tried your advice yet. Hoping to get a chance tonight after work.
Click to expand...
Click to collapse
One other thing... Have you tried a factory reset from recovery?

sliding_billy said:
One other thing... Have you tried a factory reset from recovery?
Click to expand...
Click to collapse
I believe I have. I'll try that tonight

Ok, so tonight I have tried the following:
Factory reset from recovery - that may have helped. I could then boot to both slots. slot a had lineage, slot b had factory image
unzipped factory image to latest platform tools folder and ran flash-all.sh - still getting same error and still had 2 different ROMs on slots
flashed using flash.android.com from chrome, then set other slot active and flashed again - tried this a few times. whichever slot I have active when I do this boots fine, but the other slot will not boot
So, to summarize, I now have both slots working, but only the slot I flash will boot. So, if I flash slot a, then it will boot, but slot b will not, and vice versa. And, yes I am flashing same ROM to both slots. And, flash-all.sh does not flash to either slot. It just gives met the error I posted in the OP.
Does anyone know why I am getting the error when running flash-all.sh?

The Lepricon said:
Ok, so tonight I have tried the following:
Factory reset from recovery - that may have helped. I could then boot to both slots. slot a had lineage, slot b had factory image
unzipped factory image to latest platform tools folder and ran flash-all.sh - still getting same error and still had 2 different ROMs on slots
flashed using flash.android.com from chrome, then set other slot active and flashed again - tried this a few times. whichever slot I have active when I do this boots fine, but the other slot will not boot
So, to summarize, I now have both slots working, but only the slot I flash will boot. So, if I flash slot a, then it will boot, but slot b will not, and vice versa. And, yes I am flashing same ROM to both slots. And, flash-all.sh does not flash to either slot. It just gives met the error I posted in the OP.
Does anyone know why I am getting the error when running flash-all.sh?
Click to expand...
Click to collapse
I still haven't seen that you are running the current planform tools, so that is my first suggestion. My second one is to sideload the OTA twice (including full boot after of course) so that it will install on both slots and swap. I suspect that you will then have it truly back to normal and can then do a flash-all including the -w to completely wipe.

I downloaded platform-tools_r30.0.4-linux.zip from developer.android.com yesterday and that is what I was using. And it was not working right. So, last night I downloaded it to my Windows machine and tried from there with the same results, only running flash-all.bat.
Late last night I tried your advice of sideloading factory OTA on both slots and that fixed it. Now I can boot to both slots just fine.
Thank you for all your help, sliding_billy

The Lepricon said:
I downloaded platform-tools_r30.0.4-linux.zip from developer.android.com yesterday and that is what I was using. And it was not working right. So, last night I downloaded it to my Windows machine and tried from there with the same results, only running flash-all.bat.
Late last night I tried your advice of sideloading factory OTA on both slots and that fixed it. Now I can boot to both slots just fine.
Thank you for all your help, sliding_billy
Click to expand...
Click to collapse
Great news, and you are quite welcome.