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 was trying to flash recovery after i s-off my htc sensation hboot 1.27
i put in command C:\android\android-sdk-windows\sdk\platform-tools>fastboot flash recovery recovery-clockwork-touch-5.8.0.9-pyramid.img
and C:\android\android-sdk-windows\sdk\tools>fastboot flash recovery recovery-clockw
ork-touch-5.8.0.9-pyramid.img
sending 'recovery' (4876 KB)... OKAY [ 1.254s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.571sC:\android\android-sdk-windows\sdk\tools>fastboot flash recovery recovery-clockw
ork-touch-5.8.0.9-pyramid.img
sending 'recovery' (4876 KB)... OKAY [ 1.254s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.571s
i get this error all files are there and is very frustrating as ive researched all over the internet and cant find a solution
hydroponics said:
i was trying to flash recovery after i s-off my htc sensation hboot 1.27
i put in command C:\android\android-sdk-windows\sdk\platform-tools>fastboot flash recovery recovery-clockwork-touch-5.8.0.9-pyramid.img
and C:\android\android-sdk-windows\sdk\tools>fastboot flash recovery recovery-clockw
ork-touch-5.8.0.9-pyramid.img
sending 'recovery' (4876 KB)... OKAY [ 1.254s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.571sC:\android\android-sdk-windows\sdk\tools>fastboot flash recovery recovery-clockw
ork-touch-5.8.0.9-pyramid.img
sending 'recovery' (4876 KB)... OKAY [ 1.254s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.571s
i get this error all files are there and is very frustrating as ive researched all over the internet and cant find a solution
Click to expand...
Click to collapse
Your hboot is still locked.. Until that status is changed you can't use fastboot commands..
Flash juopunutbear hboot or revolutionary hboot
Check firmware thread by kohr-ah in sensation development section... There is a patched hboot zip there (at the end I think).. First flash that and then continue the rest
Sent from my HTC Sensation using xda premium
ganeshp said:
Your hboot is still locked.. Until that status is changed you can't use fastboot commands..
Flash juopunutbear hboot or revolutionary hboot
Check firmware thread by kohr-ah in sensation development section... There is a patched hboot zip there (at the end I think).. First flash that and then continue the rest
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
u unlocked to s-off then its locked again so do i have to unlock again?
Yes mate ull hve to unlock ur bootloader as fastboot commands nly work on unlocked bootloader
Hit the thanx button if I hve helped you
Hello,
I have a Desire S, I think it has been first S-OFF with Alpharev (hboot 6.98-1002), and then a RUU has been patched (14.01.401.2). From now, the phone isn't able to boot anymore, I only have access to fastboot/bootloader
I've tried to flash the official hboot using fastboot flash hboot hboot.img
but it has not been flashed :
sending 'hboot' (1024 KB)...
OKAY [ 0.207s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.028s]
finished. total time: 0.239s
I've tried with ENG HBOOT, also tried by puting PG88IMG.zip on my SD card, fastboot detect it, tried to flash it but again, bypassed.
I'm a bit lost now, maybe someone could help me
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