HY, I'm finding the RRU pro HTC ONE S with CID TIM__401.
My phone is bricked in this situation,
*** TAMPERED ***
*** RELOCKED ***
VLE PUT SHIP S-ON RL
HBOOT-1.06.0000
RADIO-0.16.31501S.17_2
OpenDSP-v21.1.032.0314
eMMC-boot
Mar 15 2012, 23:37:23
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
when I try to using fastboot command the response is:
fastboot flash recovery recovery.img
sending 'recovery' (5742 KB)... OKAY [ 1.040s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.490s
Help me please
Roberto
BOB0660 said:
HY, I'm finding the RRU pro HTC ONE S with CID TIM__401.
My phone is bricked in this situation,
*** TAMPERED ***
*** RELOCKED ***
VLE PUT SHIP S-ON RL
HBOOT-1.06.0000
RADIO-0.16.31501S.17_2
OpenDSP-v21.1.032.0314
eMMC-boot
Mar 15 2012, 23:37:23
FASTBOOT USB
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
when I try to using fastboot command the response is:
fastboot flash recovery recovery.img
sending 'recovery' (5742 KB)... OKAY [ 1.040s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.490s
Help me please
Roberto
Click to expand...
Click to collapse
Well , first of all unlock your bootloader >>> says very clear there >>> *** TAMPERED *** then under that *** RELOCKED *** .
Once you unlocked it ... check this post here >> http://forum.xda-developers.com/showthread.php?t=1543588 and get a rom for your device .
From what says in your post , Mar 15 2012 and versions of HBOOT , Radio , etc ... my guess is that RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S would be fine for you .
I'm not sure if your CID will be a problem to write another recovery image so download that rom version and get from it what you need ( recovery , etc ) . Even so ... i think you should be able to flash TWRP 2.2.0 recovery and use a custom ROM ( TrickDroid 7.0 for example ) .
If need , you can also change your CID to Super CID ... this would alllow ya to write any rom ... check this post for more info >> http://forum.xda-developers.com/showthread.php?t=1671396 .
Yes CID would be a problem, i've changed it to HTC__001 to load the europe ruu...
(I had a tim branded one s too)
Not able to change CID
Alie360 said:
Yes CID would be a problem, i've changed it to HTC__001 to load the europe ruu...
(I had a tim branded one s too)
Click to expand...
Click to collapse
tanks for the info, but i'm not able to change the ID because my cell is not on line.
when i start ADB SHELL it respond ERROR: DEVICE NOT FOUND also some FASTBOOT command give me the same problem.
Sorry for my english
Roberto
BOB0660 said:
tanks for the info, but i'm not able to change the ID because my cell is not on line.
when i start ADB SHELL it respond ERROR: DEVICE NOT FOUND also some FASTBOOT command give me the same problem.
Sorry for my english
Roberto
Click to expand...
Click to collapse
ADB only works if phone is booted or booting and ADB is activated in settings on the phone, and in a custom recovery like CWM.
Fastboot only works in bootloader mode, when it says FASTBOOT just like when you first tried flashing that recovery.img. Test with
Code:
fastboot devices
Your command was correct but it failed because your bootloader was relocked like Equlibryum said. Try unlocking it again with
Code:
fastboot oem unlock
if it doesnt work you have to unlock again. I believe you can van reuse the Unlock_code.bin HTC emailed you the first time e.g.
Code:
fastboot flash unlocktoken Unlock_code.bin
Not sure if you have to be in any special mode to run the RUU, if memory serves me right either just at homescreen on booted phone or in bootloader.
Also you need only fastboot access to change CID.
To use adb you have to enable "debug usb" in developer options (opzioni sviluppatore->debug usb)
Then connect the phone to your pc (it must be on), open cmd and use the command
Code:
adb devices
to see if the phone is effectively connected
Also remember when you change CID you have to request another unlock_code from htcdev
ADB problem
Alie360 said:
To use adb you have to enable "debug usb" in developer options (opzioni sviluppatore->debug usb)
Then connect the phone to your pc (it must be on), open cmd and use the command
Code:
adb devices
to see if the phone is effectively connected
Also remember when you change CID you have to request another unlock_code from htcdev
Click to expand...
Click to collapse
ADB doesn't work, I'm not able to start my ONE S for setting debug usb
>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
Thanks for helpme
Roberto
Then unlock the bootloader, flash a custom recovery and then a custom rom, i sugguest you trickdroid (stable and looks like the stock one).
If you are unconfortable using cmd you should use this: http://forum.xda-developers.com/showthread.php?t=1604677
After that your phone should boot fine.
Then if you want you can change your CID through adb and install the ruu or simply keep trickdroid.
PS: if you want to give thanks, hit the thanks button
also uncheck fastboot under settings/power on phone
and do you have all your drivers/files for fastboot/adb installed in your fastboot.exe folder
make sure you are in that folder in command window for fastboot commands to work and booted into fastboot on phone
as mentioned on adb just be booted in to phone OS
ONE S brick
rugmankc said:
also uncheck fastboot under settings/power on phone
and do you have all your drivers/files for fastboot/adb installed in your fastboot.exe folder
make sure you are in that folder in command window for fastboot commands to work and booted into fastboot on phone
as mentioned on adb just be booted in to phone OS
Click to expand...
Click to collapse
I can't uncheck fastboot under settings/power my phone start only in bootloader and don't go in recovery.
I'm not able to use the ADB or FASTBOOT command because the the device is NOT CONNECT, but the driver and the sofware are correctly installed. I think the only way for resolve in the correct RRU for TIM__401 but is impossible to find it.
bye
Roberto
BOB0660 said:
I can't uncheck fastboot under settings/power my phone start only in bootloader and don't go in recovery.
I'm not able to use the ADB or FASTBOOT command because the the device is NOT CONNECT, but the driver and the sofware are correctly installed. I think the only way for resolve in the correct RRU for TIM__401 but is impossible to find it.
bye
Roberto
Click to expand...
Click to collapse
I believe in order to change your CID you need ADB. got a classic chicken or egg situation here.
I believe the only way you could get this to work is to get fastboot to work. then you could unlock bootloader, and install recovery and rom as they said already. Sometimes you have to try your phone in a different usb port so windows will be forced to reinstall the drivers or you need to delete the drivers from device manager and try again
Can not DO SUPERCID
my htc one s was offical system till i OTA 4.1.1
now HBOOT:2.15 BASEBAND:1.11.50.05.28_10.27.50.08L CID:TIM__401
and UNLOCKED root
but ever I do the supercid the result often still TIM__401
I did cry even 10+
what can I do this?
who can give me some suggestion?
Doggydude said:
get fastboot to work. then you could unlock bootloader, and install recovery and rom as they said already.
Click to expand...
Click to collapse
This is your solution...forget the ruu.
HTC_One_S | S-OFF | Root_Box | Bubba_3.7b_SoftOV
Related
OK I have read the guide on hoe to get cid BUT I have the latest update from t-mobile for the 4G when I run the adb and run it though I get an error message
INFO pyramid_init_sd, SD card power on ok
INFOsdcc_init_memory_device done
INFO[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
INFO[JAVACARD_ERR] SMART_IO.CRD cann't find
OKAY [ 1.125s]
finished. total time: 1.125s
Click to expand...
Click to collapse
When I check the CID it still labels it as T-MOBILE
any ideas on how to fix this
little more detail on what your trying to do? are you trying to get superCID? or you wanting to change back to orginal CID?
Trying to Get superCID
Sent from my HTC Sensation 4G using XDA App
are you fully rooted,have s-off and eng 1.17 hboot?
if you have all those then its simple
simply reboot into fasboot(bootloader)
from cmd window
if you have adb set as environment then you can just type
8.enter the command "fastboot oem writecid 11111111"
9. enter the command "fastboot reboot-bootloader (Wait for it to reboot the bootloader)
10. enter the command "fastboot getvar cid" [it should confirm your CID is 11111111]
11. enter the command "fastboot reboot"
Click to expand...
Click to collapse
if you dont have adb setup in environment then you have to go to the adb directory whever you installed it
eg.
C:\android-sdk\platform-tools\
once in that directory then you can do superCID commands
I have 1.18 hboot
Sent from my HTC Sensation 4G using XDA App
you need the eng boot to do fastboot commands, i suggest you read how to get rooted/or go back to eng boot then do superCID
So I have to re root my phone even though it was rooted after the update? Got a link to this eng boot
Sent from my HTC Sensation 4G using XDA App
thats only if you lost root and dont have root, if you have root, and you still have s-off you can still go back to .17 eng boot
I had this too, what worked for me was:
install android terminal
open terminal
type: getprop cid.ro << this will show you your current cid, back it up.
use 4ext to reboot into bootloader, or adb reboot-bootloader
fastboot cid commands still work
when in bootloader:
open cmd and navigate to your android tools folder, then:
fastboot oem writecid 11111111
fastboot reboot-bootloader
fastboot getvar cid << this should be 11111111 now.
fastboot reboot
Now you can flash any zip file you want.
peewster said:
I had this too, what worked for me was:
install android terminal
open terminal
type: getprop cid.ro << this will show you your current cid, back it up.
Click to expand...
Click to collapse
A small hint: It should say 'getprop ro.cid' and not 'getprop cid.ro'...
Is there any way I can downgrade the hboot from 1.18 to 1.17
Are you s-off if so then yes
Hi
I was trying for root
http://forum.xda-developers.com/showthread.php?t=1583427
but I ended on point 2.
I tried flash all recovery from CWM and from Paul too, but nothing heppend, recovery don't work. It write:
This build is for development purposes only Do not distribute outside of HTC without HTC´s written permission. Failure to comply may lead to
legal action.
and that is all, ONE S not respond, only restart to HBOOT and bootloader. Probably I can't flash CWM.
I have new model :
***UNLOCKED***
VILLEC2 PVT SHIP S-ON RL
HBOOT-2.09.0001
RADIO-16.05.20.16_M2
OpenDSP-v05.6.0.2226.00.0418
eMMC-boot
May 10 2012, 17:19:49
I flashed the kernel with program "One_S_All-In-One_Kit_v1.0" and I just stayed in HBOOT, system isn't work.
When I was trying flash original "RUU_VILLEC2_U_ICS_40_HTC_Europe_1.11.401.109_Radio_16.12.20.02U_16.05.20.16_M2_release_263131_signed.exe"
it reported error 155 -it means little memory in internal storage, and nothing heppend
When I was trying flash ramdisk with fastboot, it wrote:
c:\Program Files\Android\android-sdk\platform-tools>fastboot boot ramdisk.img
creating boot image...
creating boot image - 307200 bytes
downloading 'boot.img'...
OKAY [ 0.240s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 0.257s
I have worked on it for two day
Please, HELP me! Thx
**Sorry for my english**
error 155 can mean several things.
Try to run the RUU from fastboot, That usually clears up the 155 error
If not, let us know and we will find some other solution.
If you think, launched the phone in fastboot and on PC run RUU so it's the same, error 155.
ICS doesn't work so device stay in HBOOT and fastboot.
Have you relocked the bootloader before running the RUU ??
RUU's wont work unless bootloader is locked, To lock it open a command window, navigate to the location of all your adb / fastboot files and type:
fastboot oem lock
Then run the RUU again
I do it but fastboot in PC wrote:
c:\Program Files\Android\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = 268303736 (0xFFDFD78)
FAILED (status read failed (Too many links))
finished. total time: 0.936s
And on phone is:
*** RELOCKED ***
*** Security Warning ***
flash ruu rom instaled ok THANKS YOU i am happy
and one question: how i made bad under root my device?
i need make root my phone. not like made bad think my device
thx
unlock bootloader, Flash CWM in fastboot https://dl.dropbox.com/u/69014495/cwmrecovery.img
Boot into recovery and flash root package twice https://dl.dropbox.com/u/69014495/CWN-SuperSU-v0.87.zip
Then all done you are rooted, Enjoy flashing some customs ROMs
so all make for guide but device show error after flash cwmrecovery.img under fastboot adb
writhing this:
This build is for development purposes only Do not distribute outside of HTC without HTC´s written permission. Failure to comply may lead to legal action.
what next?
ICS is running
recovery not running
This way works?
http://forum.xda-developers.com/showthread.php?t=1577831
I have tried does not work
thx
Hey guys,
It was freaking hard to unlock the bootloader and S-OFF my htc sensation. But I was successful in doing it. I've using this guide http://forum.xda-developers.com/showthread.php?t=1870233.
When I first unlocked snesation, I S-OFFed it but then the bootloader showed LOCKED again, even though the guide says it should say Unlocked. (I unlocked it correctly the first time). So I Unlocked it again... i found no other way.. Then it showed Unlocked.
As of now, it shows...
-Firmware-3.33-
Pyramid PVT SHIP S-OFF RL
HBOOT-1.27.1100
eMMC-BOOT
JAN 13 2012,17:33:34
Click to expand...
Click to collapse
Now in the 3rd and 4th step it asks to use the HTC Sensation All in one ToolKit. The main problem comes here. It doesnt read my device even though I installed the drivers. Below is a detail.
While using the 4EXT recovery from the toolkit.
daemon not running. starting it now port 5037
daemon started successfully
error: device not found
Click to expand...
Click to collapse
Additional info:
I used adb and fastboot through Mac while I'm using HTC Toolkit from Windows. If thats the prob how to I fix it?
I've tried a lot! I put 5 hours on this but failed!
Help would be seriously appreciated!!!
Are you trying to flash recovery? Do you have adb fastboot setup on your PC? You can flash recovery via fastboot from your PC.
Sent from my HTC Sensation Z710e
MrJukeHardbane said:
Are you trying to flash recovery? Do you have adb fastboot setup on your PC? You can flash recovery via fastboot from your PC.
Click to expand...
Click to collapse
Yes, I'm trying to flash a recovery to flash a custom ROM.
ADB fastboot is setup.
Could you send me a good guide for flashing via fastboot. I'll try it and update you. Should I just put the recovery file in to the fastboot folder and use the fastboot command?
pulsar91 said:
Yes, I'm trying to flash a recovery to flash a custom ROM.
ADB fastboot is setup.
Could you send me a good guide for flashing via fastboot. I'll try it and update you. Should I just put the recovery file in to the fastboot folder and use the fastboot command?
Click to expand...
Click to collapse
Yes, put the recovery.img in the same folder as fastboot folder, boot ur phone into fastboot then plug in ur phone to computer and it should say FASTBOOT USB. Then in the fastboot folder, hold shift - right click - open command window here. Then type -
fastboot flash recovery recovery.img
You now should have recovery installed
jmcclue said:
Yes, put the recovery.img in the same folder as fastboot folder, boot ur phone into fastboot then plug in ur phone to computer and it should say FASTBOOT USB. Then in the fastboot folder, hold shift - right click - open command window here. Then type -
fastboot flash recovery recovery.img
You now should have recovery installed
Click to expand...
Click to collapse
Hey,
I did this and it seems like it worked . Here's the output..
Mannans-MacBook-Pro:Android Mannan$ ./fastboot flash recovery recovery.img
sending 'recovery' (4618 KB)...
OKAY [ 1.150s]
writing 'recovery'...
OKAY [ 9.050s]
finished. total time: 10.199s
Click to expand...
Click to collapse
Now, how do I root through this method?
pulsar91 said:
Hey,
I did this and it seems like it worked . Here's the output..
Now, how do I root through this method?
Click to expand...
Click to collapse
You're S-off I guess? You're already rooted as root is a prerequisite for S-off. Download app root checker from play store and check your root status. It should say rooted.
Sent from my HTC Sensation Z710e
SOLVED!!
THANKS GUYS!!!!
It was rooted and the recovery from fastboot worked!!!
Im on CM 10!
THANKS AGAIN!!!
jmcclue said:
Yes, put the recovery.img in the same folder as fastboot folder, boot ur phone into fastboot then plug in ur phone to computer and it should say FASTBOOT USB. Then in the fastboot folder, hold shift - right click - open command window here. Then type -
fastboot flash recovery recovery.img
You now should have recovery installed
Click to expand...
Click to collapse
Sorry - the command window says: "waiting for device"
What can I do?
revierbiker said:
Sorry - the command window says: "waiting for device"
What can I do?
Click to expand...
Click to collapse
did you select fastboot in the hboot screen?
did you enable usb debugging mode from settings?
do you have htc drivers installed?
It all started yesterday where i was trying to update (InsertCoin) which for some reason made my phone shut down mid-way through the installation process...
I had to reboot my phone back into recovery to wipe system/cache/data to reinstall...For some reason this wiped/damaged everything but the bootloader ofc.
(Bye go all my pictures, whatsapp conversations etc...)
This made me not being able to boot into my recovery aswell
I still can't get back into my recovery, and i've tried flashing the recovery over and over again via fastboot flash recovery twrp.img
When i try to flash the recovery, it succeeds but when i try to boot into it, it blinks the splash screen with odd intervals, i dont know if this means that its trying over and over again...I'm sort of desperate here...any help?
sidenote here: I'm in linux
you should've updated firmware to hboot 2.22 needed for IC, then you need to install the latest recovery 2.7.1.1 from twrp website
twrp here: http://techerrata.com/browse/twrp2/m4ul
new firmware here :http://forum.xda-developers.com/showthread.php?t=2759131
I have not updated it, will go and do that now,
Code:
[email protected]:/media/leon/*censor*/Android/ROMS/Millium$ sudo fastboot flash zip firmware.zip
[sudo] password for leon:
target reported max download size of 800227328 bytes
sending 'zip' (19549 KB)...
OKAY [ 2.466s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 4.305s
Right.....!?
I really don't want to reboot to bootloader at the moment...since the update failed...
Apparently i am S-ON and therefor need to obtain s-off, but i don't have an android system installed..how
s-off required to flash firmware or if s-on, bootloader needs to be re-locked, sorry i assumed you knew that! maybe create a signature giving details of your device for future, it does help.
If you are S-ON ---> Re-lock your bootloader (this will most probably wipe content of your device)
If you are S-OFF ---> no need to re-lock the bootloader.
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet or in case it's S-ON)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
Code:
FAILED (remote: 12 signature verify fail)
This ahappens when flashing the firmware
*edit: I have fixed that, but i cannot flash the 2.22 included y you because it has a different modelid, presumably because my m4 isn't the at&t variant.
Will this work?
`leon said:
Code:
FAILED (remote: 12 signature verify fail)
This ahappens when flashing the firmware
Click to expand...
Click to collapse
not work ?? ok, then you will need to s-off the device, unlock first,you need SUPERCID also
Braddison said:
not work ?? ok, then you will need to s-off the device, unlock first
Click to expand...
Click to collapse
It did, sorry, didnt edit the post quick enough
`leon said:
Code:
FAILED (remote: 12 signature verify fail)
*edit: I have fixed that, but i cannot flash the 2.22 included y you because it has a different modelid, presumably because my m4 isn't the at&t variant.
Will this work?
Click to expand...
Click to collapse
no that firmware will not update everything that is required, use the firmware zip in the link i gave previously.
you need to change your cid to supercid,,,,very simple to do
Enter the command "fastboot oem readcid". Make a note of your original CID.
enter the command "fastboot oem writecid 11111111" make sure it is 8 ones (1)
enter the command "fastboot read cid" [it should confirm your CID is 11111111]
Braddison said:
no that firmware will not update everything that is required, use the firmware zip in the link i gave previously.
you need to change your cid to supercid,,,,very simple to do
Enter the command "fastboot oem readcid". Make a note of your original CID.
enter the command "fastboot oem writecid 11111111" make sure it is 8 ones (1)
enter the command "fastboot read cid" [it should confirm your CID is 11111111]
Click to expand...
Click to collapse
Yeah, i just tried that 5 minutes ago, though...:
Code:
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
Gosh...my device doesn't like me..
oh, wait, don't i have to unlock bootloader?
i'll try that now
OMG IM IN RECOVERY
cant seem to do anything with my data partition, same goes for internal storage
well you've done everything that i done when i tried out Insertcoin rom for a few days and never had any of your issues. so not sure whats going on.
- unlocked bootloader
- get s-off
- get supercid
- update firmware
- get latest twrp recoverry
- install Insert Coin
use the fix miniwhooper posted on her firmware thread ....Flash stock recovery and factory reset from boot loader. It will fix you /data partition.. then flash custom recovery and it should be fixed
`leon said:
Yeah, i just tried that 5 minutes ago, though...:
Code:
(bootloader) [JAVACARD_ERR] SD/USBDISK Init error
Gosh...my device doesn't like me..
oh, wait, don't i have to unlock bootloader?
i'll try that now
OMG IM IN RECOVERY
cant seem to do anything with my data partition, same goes for internal storage
Click to expand...
Click to collapse
Make sure you are in the folder your rom zip is located.
Run the command...
adb push filename.zip /sdcard
Wait around 10 minutes as it will not give you progress
go back to TWRP main page and install, choose SDcard and the zip file you just uploaded should be there.
hello @AnGrY sCoTsMaN
i have the exact same problem but i flashed cm.12.1 cant boot in recovery or flash anything using adb
hboot os 2.22 it says unlocked but it seems not
can you please help me out
Edit: problem solved without doing anything
HBOOT 2.16 Installation guide
Requirements before installing
Back up your files, your SD Card will be WIPED!
Charge your phone to AT LEAST 30%
Your bootloader MUST be unlocked
You NEED to be S-OFF or else it won't work
You need basic knowledge of Fastboot commands
Windows 10/8/7/Vista/XP: You need drivers installed
Windows 8.1: You need drivers installed AND update kb2967917 from Microsoft
Linux: You need "51-android.rules" or "99-android.rules" configured
Mac: Nothing needed that I know of
I am NOT responsible if you break your phone
This guide will be from a Windows point of view
Installation Guide
Download the HBOOT 2.16 firmware file from here: Download from Mega.co.nz
Place it in your adb and fastboot folder. For example C:\Users\(Your Username)\Fastboot
Now open a Command Prompt window and then type in:
Code:
cd C:\(Location of your Fastboot folder)
Now take your phone and connect it to your computer (with USB Debugging ON) and type in:
Code:
adb reboot bootloader
Once you are in the bootloader and it displays "Fastboot USB", type in:
Code:
fastboot oem rebootRUU
Once your computer recognizes your phone type in:
Code:
fastboot flash zip Firmware_4.06.401.1.zip
If you changed the file name make sure to type in the name of it instead of the one above
You will then get an error:
Code:
"FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
Don't worry, this is normal. DO NOT unplug your phone. Simply type in once again:
Code:
fastboot flash zip Firmware_4.06.401.1.zip
If you changed the file name make sure to type in the name of it instead of the one above
Then wait until the Command window says "finished" and type in:
Code:
fastboot reboot-bootloader
Next we need to download TWRP recovery. You can download it from MDMower's website and MAKE SURE to get TWRP for "/data/media storage (HBOOT 2.16.0000)" and TWRP 2.8.0.1 or above.
Now we must go back to the command window with your phone still plugged in displaying "Fastboot USB" on the screen
Then we type:
Code:
cd C:\Users\(Your Username)\Downloads
or if the TWRP Recovery file isn't in the above location just direct it to the folder its stored in
Now we type:
Code:
fastboot flash recovery twrp-2.8.x.x-ville-dm.img
just replace the "x" with the numbers on the file. e.g. - 2.8.0.1
Once it flashed successfully press the power button and use the volume buttons to scroll down to recovery and to boot into it, simply press the power button
Now go into "Mounts" and select Enable MTP if it isn't already.
Now copy a ROM of your choice (That supports HBOOT 2.16) and flash it. If MTP doesn't work, simply sideload the ROM
That's it, now you just reboot after installing your ROM.
Hope this helps anybody having difficulty with HBOOT 2.16
Getting a different error when flashing.
c:\adb>fastboot flash zip Firmware_4.06.401.1.zip
sending 'zip' (46472 KB)...
OKAY [ 2.598s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 4.304s
urlyisis said:
Getting a different error when flashing.
c:\adb>fastboot flash zip Firmware_4.06.401.1.zip
sending 'zip' (46472 KB)...
OKAY [ 2.598s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 4.304s
Click to expand...
Click to collapse
You need to change your cid
To change it go into bootloader, then fastboot, connect it to your computer and type
Code:
fastboot oem writecid 11111111
that is eight 1s
If that didnt work then type instead
Code:
fastboot oem writecid HTC__001
that is 2 underscores after HTC
I get this:
Code:
Z:\One_S_All-In-One_Kit_v1.1\Data>fastboot flash zip Firmware_4.06.401.1.zip
sending 'zip' (46472 KB)... OKAY [ 6.507s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 8.020s
No matter how often I attempt it. Redownloaded the zip to make sure it is not corrupt...
Any pointer?
Ah, damn, because I followed the instructions to the end despite the HBOOT not flashing I can also now not access recovery anymore. It seems the new version of recovery was properly flashed, but as it relies on higher HBOOT I can't get into it anymore. It is still in HBOOT 1.03.
Can anyone help me to get this phone ready for Cyanogenmod?
I was able to load the hboot, but now the bootloader is locked again and I can't flash the recovery.
FAILED (remote: not allowed)
Walter_White said:
I get this:
Code:
Z:\One_S_All-In-One_Kit_v1.1\Data>fastboot flash zip Firmware_4.06.401.1.zip
sending 'zip' (46472 KB)... OKAY [ 6.507s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 8.020s
No matter how often I attempt it. Redownloaded the zip to make sure it is not corrupt...
Any pointer?
Ah, damn, because I followed the instructions to the end despite the HBOOT not flashing I can also now not access recovery anymore. It seems the new version of recovery was properly flashed, but as it relies on higher HBOOT I can't get into it anymore. It is still in HBOOT 1.03.
Can anyone help me to get this phone ready for Cyanogenmod?
Click to expand...
Click to collapse
Get s-off change your cid to HTC__001 as shown above and run this ruu, then follow the instructions above
urlyisis said:
I was able to load the hboot, but now the bootloader is locked again and I can't flash the recovery.
FAILED (remote: not allowed)
Click to expand...
Click to collapse
It looks like your s-on
UPDATE: I had to unlock the bootloader via the HTC unlock. RESOLVED
dd98 said:
It looks like your s-on
Click to expand...
Click to collapse
Actually, the bootloader shows the following.
***** Tampered ******
Locked
VLE PVT SHIP S-OFF RL
CID-HTC__001
HBOOT-2.16.000
dd98 said:
HBOOT 2.16 Installation guide
Requirements before installing
Back up your files, your SD Card will be WIPED!
Charge your phone to AT LEAST 30%
Your bootloader MUST be unlocked
You NEED to be S-OFF or else it won't work
You need basic knowledge of Fastboot commands
Windows 10/8/7/Vista/XP: You need drivers installed
Windows 8.1: You need drivers installed AND update kb2967917 from Microsoft
Linux: You need "51-android.rules" or "99-android.rules" configured
Mac: Nothing needed that I know of
I am NOT responsible if you break your phone
This guide will be from a Windows point of view
Installation Guide
Download the HBOOT 2.16 firmware file from here: Download from Mega.co.nz
Place it in your adb and fastboot folder. For example C:\Users\(Your Username)\Fastboot
Now open a Command Prompt window and then type in:
Code:
cd C:\(Location of your Fastboot folder)
Now take your phone and connect it to your computer (with USB Debugging ON) and type in:
Code:
adb reboot bootloader
Once you are in the bootloader and it displays "Fastboot USB", type in:
Code:
fastboot oem rebootRUU
Once your computer recognizes your phone type in:
Code:
fastboot flash zip Firmware_4.06.401.1.zip
If you changed the file name make sure to type in the name of it instead of the one above
You will then get an error:
Code:
"FAILED (remote: 90 hboot pre-update! please flush image again immediately)"
Don't worry, this is normal. DO NOT unplug your phone. Simply type in once again:
Code:
fastboot flash zip Firmware_4.06.401.1.zip
If you changed the file name make sure to type in the name of it instead of the one above
Then wait until the Command window says "finished" and type in:
Code:
fastboot reboot-bootloader
Next we need to download TWRP recovery. You can download it from MDMower's website and MAKE SURE to get TWRP for "/data/media storage (HBOOT 2.16.0000)" and TWRP 2.8.0.1 or above.
Now we must go back to the command window with your phone still plugged in displaying "Fastboot USB" on the screen
Then we type:
Code:
cd C:\Users\(Your Username)\Downloads
or if the TWRP Recovery file isn't in the above location just direct it to the folder its stored in
Now we type:
Code:
fastboot flash recovery twrp-2.8.x.x-ville-dm.img
just replace the "x" with the numbers on the file. e.g. - 2.8.0.1
Once it flashed successfully press the power button and use the volume buttons to scroll down to recovery and to boot into it, simply press the power button
Now go into "Mounts" and select Enable MTP if it isn't already.
Now copy a ROM of your choice (That supports HBOOT 2.16) and flash it. If MTP doesn't work, simply sideload the ROM
That's it, now you just reboot after installing your ROM.
Hope this helps anybody having difficulty with HBOOT 2.16
Click to expand...
Click to collapse
Whatever which recover i choose, my internal storage was always 48mb, i can not push rom, can not sideload rom,
ad346544521 said:
Whatever which recover i choose, my internal storage was always 48mb, i can not push rom, can not sideload rom,
Click to expand...
Click to collapse
You need the hboot 2.16 specific recovery, you can download it here
Never mind, I found what I needed...
Hi, do you have the firmware for t-mobile to downgrade to 2.15? I tried https://mega.co.nz/#!s54F3YqK!QrNjMlieIG65jsaGWS8eXDdLc5FcYM7IEmqTk_pHbFA but doesnt work. I think because is not for tmobile. I cant downloade the full RUU because the download always fails and my internet is so slow.
EDIT: I dont need it anymore, a friend download the file for me. Just a question. in hboot 2.16, gave me more space for my data, i like that, there is no way to make old roms to work on hboot 2.16?
Cannot get this method to work. I'm unlocked and S-OFF. But whenever I try to flash the firmware*.zip I get the message
FAILED (remote: not allowed)
I'm about ready to give up on HBoot 2.16.
confused on twrp for hboot 2.16
Hi thanks a lot for this very clear tuto that help me successfully upgrade to hboot 2.16 without any error issue. everything followed attentively and step by step .
However i am a littlee confused at the step bellow.
When i reached the download section of specified url , concerning TWRP , there is only twrp 2.7 concerning hboot 2.16
But in the tuto you talk about twrp 2.8.. or above. So please can you clarify me on this ?
Thanks
dd98 said:
HBOOT 2.16 Installation guide
[*]Next we need to download TWRP recovery. You can download it from ......and MAKE SURE to get TWRP for "/data/media storage (HBOOT 2.16.0000)" and TWRP 2.8.0.1 or above.
Click to expand...
Click to collapse
delacosta4526 said:
Hi thanks a lot for this very clear tuto that help me successfully upgrade to hboot 2.16 without any error issue. everything followed attentively and step by step .
However i am a littlee confused at the step bellow.
When i reached the download section of specified url , concerning TWRP , there is only twrp 2.7 concerning hboot 2.16
But in the tuto you talk about twrp 2.8.. or above. So please can you clarify me on this ?
Thanks
Click to expand...
Click to collapse
Sorry, this is an old tutorial. Go to this link, download the latest file and flash it in fastboot mode by typing: fastboot flash recovery twrp-2.8.x.x.img (or whatever the file name is)
thanks..but
dd98 said:
Sorry, this is an old tutorial. Go to link, download the latest file and flash it in fastboot mode by typing: fastboot flash recovery twrp-2.8.x.x.img (or whatever the file name is)
Click to expand...
Click to collapse
thanks that is what i did.
But i though this would have help fix wifi, bluetooth not working since stock rom before i flash with "LIBERTY ROM - The Sixth Element" (that did not fix the problem)
Did you anything that can help ? My phone is Htc one s (actually : hboot 2.16 , TWRP 2.8.0.5, radio 1.20, unlocked, s-off, rooted, and with LIBERTY ROM - The Sixth Element" .
delacosta4526 said:
thanks that is what i did.
But i though this would have help fix wifi, bluetooth not working since stock rom before i flash with "LIBERTY ROM - The Sixth Element" (that did not fix the problem)
Did you anything that can help ? My phone is Htc one s (actually : hboot 2.16 , TWRP 2.8.0.5, radio 1.20, unlocked, s-off, rooted, and with LIBERTY ROM - The Sixth Element" .
Click to expand...
Click to collapse
No the recovery version will NEVER affect anything that does/doesn't work on the rom. Since you are using Liberty rom, make sure you are using the 4.4.2 version because the 4.4.3 version is very buggy
of course
dd98 said:
No the recovery version will NEVER affect anything that does/doesn't work on the rom. Since you are using Liberty rom, make sure you are using the 4.4.2 version because the 4.4.3 version is very buggy
Click to expand...
Click to collapse
Yes surely . i am using 4.4.2. I have carefully read i lot of things including that.
Thanks
Guys can someone please help me?
I am on Windows 10 desperately trying to find a solution on the ''WAITING DEVICE'' response after I type
fastboot oem rebootRUU
I have tried installing a bunch of drivers , driver updates on device manager etc with no luck.
The device is just not responding.
Thanks
File Offline
Unfortunately the HBoot 2.16 file is offline. Can someone please reupload it?
Thank you!