How to update firmware (adsp, recovery, radio, ...)
This affects your hardware, do it in case it is really needed.
Reminder: If you decided to do this, it is your choice.
Take no responsibility for the cases when device will not survive at next boot.
!! SPL (bootloader) should be locked.
If it is unlocked, you can re-lock with command:
fastboot oem lock
1. Get to bootloader.
adb reboot bootloader
or
by pressing vol"-" and power keys/
2. fastboot oem rebootRUU
this will bring you to updater mode
3. Flash firmware that you have extracted from OTA zip file
fastboot flash zip firmware.zip
(the firmware.zip file is the one extracted from OTA zip update)
sending 'zip' (27589 KB)...
OKAY [ 3.558s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 13.210s
!!! This to be done quickly !!!
4. Issue again command:
fastboot flash zip firmware.zip
< waiting for device >
sending 'zip' (27589 KB)...
OKAY [ 3.556s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,12
(bootloader) [RUU]UZ,adsp,25
(bootloader) [RUU]UZ,adsp,37
(bootloader) [RUU]UZ,adsp,50
(bootloader) [RUU]UZ,adsp,62
(bootloader) [RUU]UZ,adsp,75
(bootloader) [RUU]UZ,adsp,90
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,11
(bootloader) [RUU]UZ,boot,24
(bootloader) [RUU]UZ,boot,34
(bootloader) [RUU]UZ,boot,48
(bootloader) [RUU]UZ,boot,60
(bootloader) [RUU]UZ,boot,73
(bootloader) [RUU]UZ,boot,87
(bootloader) [RUU]UZ,boot,99
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,99
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,10
(bootloader) [RUU]UZ,recovery,23
(bootloader) [RUU]UZ,recovery,33
(bootloader) [RUU]UZ,recovery,44
(bootloader) [RUU]UZ,recovery,55
(bootloader) [RUU]UZ,recovery,73
(bootloader) [RUU]UZ,recovery,83
(bootloader) [RUU]UZ,recovery,95
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1,0
(bootloader) [RUU]UZ,sbl1,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) signature checking...
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,9
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,27
(bootloader) [RUU]UZ,radio,36
(bootloader) [RUU]UZ,radio,45
(bootloader) [RUU]UZ,radio,50
(bootloader) [RUU]UZ,radio,59
(bootloader) [RUU]UZ,radio,68
(bootloader) [RUU]UZ,radio,77
(bootloader) [RUU]UZ,radio,86
(bootloader) [RUU]UZ,radio,91
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,72
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
(bootloader) ...... Successful
OKAY [ 26.203s]
finished. total time: 29.762s
Main components of your firmware upgraded.
Normally, after this you remain in RUU mode.
Reboot to bootloader.
Unlock bootloader (if needed).
Flash custom recovery (if needed).
Reboot.
Is this can be used to update hboot of those Cid's which had not received any update?
Is equal to update OTA? So, Is it make a complete rom update like OTA?
bilal_liberty said:
Is this can be used to update hboot of those Cid's which had not received any update?
Click to expand...
Click to collapse
I did the same thing to upgrade 4.0.3 to 4.0.4 using RUU.So yes
bilal_liberty said:
Is this can be used to update hboot of those Cid's which had not received any update?
Click to expand...
Click to collapse
2 things.
-if you mean to flash ota zip unmodified file on the same principal, the answer is no. You can't.
- however, after flashing firmware, you can still flashing new OTA zip file, relevant for your device.In fact I think any..
Not directly, you will need to make some changes to updater script which is located in OTA zip file. You also need to exclude firmware.zip from original OTA file.
I think there is a mention abt this in a forum.
This type of flashing can be done with 3rd party recovery tool, like twrp. Meaning that signature of original OTA zip file fwill not be verified. Because by modifying original ota zip we break the signature of the file that was initially done with htc certificate.
I guess next question that is expected - is it possible to flash any firmware, for s3 type device. For example Asia for Europe or one operator to another. I have no clear answer on this one at the moment. Normally, firmware is linked to the model of device (read hardware). it not linked to country or cid. In addition, when you flash firmware, pre-boot spl checks only signature of the image you flash.
Of course, it is easy to try, but be careful, if you destroy spl, it is not so easy to recover.
The method above could be interesting for people, who likes to install custom roms, but not on the "level" with required spl (bootloader).
Good luck. But be careful.
istnag said:
Is equal to update OTA? So, Is it make a complete rom update like OTA?
Click to expand...
Click to collapse
Not quite. It does update of the firmware only. But as it was mentioned before. It is easy to flash system from OTA zip file.
Keep in mind, when we speak about flashing system, OTA shall be for your device, because it will check device's cid, although will not check signature (twrp recovery).
I believe that is the way to update,because my CID is the rom.zip. I don't want to unlock the bl, so I need to wait...
Or can I flash the system.img anyway?
Sent from my HTC One S using xda app-developers app
istnag said:
I believe that is the way to update,because my CID is the rom.zip. I don't want to unlock the bl, so I need to wait...
Or can I flash the system.img anyway?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
You want to update system, but don't want to unlock bootloader.
For the moment it is ruu or ota. Ota is when you receive update directly to device.
Ruu JB 4.1.1 for s3 type devices is unlikely. for s4 devices you can get ruu though.
Is JB 4.1.1 Update Process is working on Stock rom..?
Restore to stock JB
Hi,
My Mobile has following specification
Phone: HTC One S (VILLE C2)
Android Version: 4.1.1
HTC Sense: 4+
Software number: Tricdroid 6
Kernel version: 3.4.10 (by Flar2)
Baseband version: 16.22.20.03U_16.11.20.24_M
Build number: 3.19.720.100 CL157254 release-keys
HBOOT: 3.01.0000
Recovery: TWRP v2.4.0.0
I am running with custom rom.I have My OTA file for JB for my device CID.
Can u Guide me how to update to stock using OTA zip file from custom rom for JB.
Thanks In advance
sgmistry said:
Hi,
My Mobile has following specification
Phone: HTC One S (VILLE C2)
Android Version: 4.1.1
HTC Sense: 4+
Software number: Tricdroid 6
Kernel version: 3.4.10 (by Flar2)
Baseband version: 16.22.20.03U_16.11.20.24_M
Build number: 3.19.720.100 CL157254 release-keys
HBOOT: 3.01.0000
Recovery: TWRP v2.4.0.0
I am running with custom rom.I have My OTA file for JB for my device CID.
Can u Guide me how to update to stock using OTA zip file from custom rom for JB.
Thanks In advance
Click to expand...
Click to collapse
sgmistry:
here is instruction.
http://forum.xda-developers.com/showpost.php?p=37511931&postcount=47
gl.
htc one s hboot 3.01 ruu
fdp24 said:
sgmistry:
here is instruction.
http://forum.xda-developers.com/showpost.php?p=37511931&postcount=47
gl.
Click to expand...
Click to collapse
htc one s
cid htc_038
hboot 3.01.0000
ruuuuu please
try this
sgmistry said:
Hi,
My Mobile has following specification
Phone: HTC One S (VILLE C2)
Android Version: 4.1.1
HTC Sense: 4+
Software number: Tricdroid 6
Kernel version: 3.4.10 (by Flar2)
Baseband version: 16.22.20.03U_16.11.20.24_M
Build number: 3.19.720.100 CL157254 release-keys
HBOOT: 3.01.0000
Recovery: TWRP v2.4.0.0
I am running with custom rom.I have My OTA file for JB for my device CID.
Can u Guide me how to update to stock using OTA zip file from custom rom for JB.
Thanks In advance
Click to expand...
Click to collapse
instruction from this link works for me.
Code:
http://forum.xda-developers.com/showthread.php?t=2164783
perhaps also works for you.
NoobPro said:
htc one s
cid htc_038
hboot 3.01.0000
ruuuuu please
Click to expand...
Click to collapse
It is unlikely to find JB 4.1.1. ruu for htc one S (S3).
but you can get the OTA for your CID:
http://yadi.sk/d/ST46JsL82yazY
you need to make some modifications to the zip file, before will be able to flash it on your device.
it is in forum concerning how to flash OTA.
http://forum.xda-developers.com/showpost.php?p=37511931&postcount=47
gl.
fdp24 said:
It is unlikely to find JB 4.1.1. ruu for htc one S (S3).
but you can get the OTA for your CID:
http://yadi.sk/d/ST46JsL82yazY
you need to make some modifications to the zip file, before will be able to flash it on your device.
it is in forum concerning how to flash OTA.
http://forum.xda-developers.com/showpost.php?p=37511931&postcount=47
gl.
Click to expand...
Click to collapse
but i have no os installed on my phone
will this work even then
Yes it should
bilal_liberty said:
Yes it should
Click to expand...
Click to collapse
i guess ill give it a try
but can i find a ruu to get back to 4.0.4(stock) from hboot 3.01.0000
is it even there ????
---------- Post added at 09:22 PM ---------- Previous post was at 08:26 PM ----------
bilal_liberty said:
Yes it should
Click to expand...
Click to collapse
while doing so what if the progress bar stops at around 90 percent
it wil not stop at 90%
U cannot downgrade through RUU; u can install any ics custom rom through twrp and it will work
bilal_liberty said:
it wil not stop at 90%
U cannot downgrade through RUU; u can install any ics custom rom through twrp and it will work
Click to expand...
Click to collapse
dude it does i tried it more then ten times
NoobPro said:
dude it does i tried it more then ten times
Click to expand...
Click to collapse
explain exactly what is happening.
and pls. put the details of your device in a signature, to know what are we talking abt.
Related
Hi.
It seems to me that i have a problem.
Tried to install S5 t-mobile stock for One XL firmware update. Has S-OFF and SuperCID.
I followed the instructions below and my doesn't boot anymore. ( with button too ).
Is there anything i can do ?
Thanks a lot.
Installing the Firmware (Warning: You MUST be S-OFF and Super CID to flash this!)
Reboot to bootloader
Run: fastboot oem rebootRUU
Run: fastboot flash zip <PathToFirmware.zip>
Run the previous command AGAIN
Reboot: fastboot reboot
STDOUT
steamy Downloads # fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.064s]
finished. total time: 0.064s
steamy Downloads # fastboot flash zip firmware_3.17.111.1_0.24a.32.45.03_10.129.32.34a.zip
sending 'zip' (20161 KB)...
OKAY [ 2.276s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 3.909s
steamy Downloads # fastboot flash zip firmware_3.17.111.1_0.24a.32.45.03_10.129.32.34a.zip
< waiting for device >
sending 'zip' (20161 KB)...
OKAY [ 2.273s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,12
(bootloader) [RUU]UZ,adsp,25
(bootloader) [RUU]UZ,adsp,36
(bootloader) [RUU]UZ,adsp,49
(bootloader) [RUU]UZ,adsp,60
(bootloader) [RUU]UZ,adsp,72
(bootloader) [RUU]UZ,adsp,85
(bootloader) [RUU]UZ,adsp,96
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ..... OK
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) [RUU]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ..... OK
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ..... OK
(bootloader) start image[wcnss] unzipping & flushing...
(bootloader) [RUU]UZ,wcnss,0
(bootloader) [RUU]UZ,wcnss,20
(bootloader) [RUU]UZ,wcnss,51
(bootloader) [RUU]UZ,wcnss,71
(bootloader) [RUU]UZ,wcnss,91
(bootloader) [RUU]UZ,wcnss,100
(bootloader) [RUU]WP,wcnss,0
(bootloader) [RUU]WP,wcnss,100
(bootloader) ..... OK
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,6
(bootloader) [RUU]UZ,radio,12
(bootloader) [RUU]UZ,radio,17
(bootloader) [RUU]UZ,radio,24
(bootloader) [RUU]UZ,radio,30
(bootloader) [RUU]UZ,radio,35
(bootloader) [RUU]UZ,radio,42
(bootloader) [RUU]UZ,radio,48
(bootloader) [RUU]UZ,radio,54
(bootloader) [RUU]UZ,radio,60
(bootloader) [RUU]UZ,radio,66
(bootloader) [RUU]UZ,radio,71
(bootloader) [RUU]UZ,radio,77
(bootloader) [RUU]UZ,radio,84
(bootloader) [RUU]UZ,radio,89
(bootloader) [RUU]UZ,radio,95
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,47
(bootloader) [RUU]WP,radio,95
(bootloader) [RUU]WP,radio,100
(bootloader) ..... OK
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
(bootloader) ..... OK
OKAY [ 24.802s]
finished. total time: 27.076s
steamy Downloads #
steamy Downloads # fastboot reboot
rebooting...
finished. total time: 0.056s
does the phone turn on at all ? what happens when you connect it to the computer?
Vcek said:
does the phone turn on at all ? what happens when you connect it to the computer?
Click to expand...
Click to collapse
Nothing at all. Just peace of plastic with buttons
Turge responded in the last thread and told you to try the unbrick evita method. There's a good chance you'll be able to recover that way. I almost forgot that thread existed.
http://forum.xda-developers.com/showthread.php?t=1966850
Sent from my HTC One XL using xda app-developers app
exad said:
Turge responded and in the last thread and told you to try the unbrick evita method. There's a good chance you'll be able to recover that way. I almost forgot that thread existed.
http://forum.xda-developers.com/showthread.php?t=1966850
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Thanks a lot. I think the method will help.
In my dmesg i see something mentioned in your link.
[660942.299059] usb 1-2: Product: QHSUSB_DLOAD
[660942.299068] usb 1-2: Manufacturer: Qualcomm CDMA Technologies MSM
[660942.300725] qcserial 1-2:1.0: Qualcomm USB modem converter detected
[660942.301335] usb 1-2: Qualcomm USB modem converter now attached to ttyUSB0
If you can get past enumeration of the partitions, it's recoverable. Step 3 I think?..
Should list off a whole buttload partitions
Sent from my HTC One XL using xda app-developers app
exad said:
If you can get past enumeration of the partitions, it's recoverable. Step 3 I think?..
Should list off a whole buttload partitions
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Unfortunately ls /dev/sd* shows nothing except my laptop partitions
You spammed like a mofo? There's a time window to catch them
Sent from my HTC One XL using xda app-developers app
exad said:
You spammed like a mofo? There's a time window to catch them
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
steamy udev # while true ; do ls -la /dev/sd* ; done > /tmp/listing
steamy udev # grep -v sda /tmp/listing
steamy udev #
Looks like "i'm dead". Have to go to htc service.
For those of you worried that these will brick your phone, I have tested this on my own personal phone and the files were hex edited by me. The screenshots below are from my phone's bootloader screen, and before+after hex editing. Thank you herwegan for providing the hboot hex editing tutorial. All the darkboot firmwares now include the latest Google bootloader. See the last attachment.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\DeathAngel74>cd c:/sdk
c:\sdk>adb reboot bootloader
c:\sdk>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.050s]
finished. total time: 0.050s
c:\sdk>fastboot flash zip hboot.zip
target reported max download size of 1526722560 bytes
sending 'zip' (602 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,50
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.220s]
finished. total time: 2.470s
C:\sdk>fastboot reboot
C:\sdk>
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\DeathAngel74>cd c:/sdk
c:\sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.14.531.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3864mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
c:\sdk>
AT&T added:
5.12.502.2 No red warning:
https://drive.google.com/file/d/0B007JgCLgXQLU1hCUUhzb3BNQlk/edit?usp=sharing
Darkboot 5.12.502.2:
https://drive.google.com/file/d/0B007JgCLgXQLd3N1cFFRdUd3M1U/edit?usp=sharing
___________________________________________________________________________________
New Google Play Edition added from: 5d068c2397c0533ca0b61ea262615dc2a379dbd4.OTA_M7_UL_K44_STOCK_UI_MR_Google_WWE_4.07.1700.4-3.62.1700.1_KTU84L.H4_release_377648, thanks to EthanFirst for the link. The date changed from 11/21/2013 to 5/16/2014 after I updated.
4.07.1700.4 hboot only( If you just want to upgrade the bootloader and not flash full firmware. )
https://drive.google.com/file/d/0B007JgCLgXQLdFJ6SVZjLXIwd3c/edit?usp=sharing
rename the zip to hboot.zip
fastboot oem rebootRUU
fastboot flash zip hboot.zip
fastboot reboot
4.07.1700.4 full darkboot firmware:
https://drive.google.com/file/d/0B007JgCLgXQLSkdNUmVqXzhLdFE/edit?usp=sharing
____________________________________________________________________________________
US Developer Edition:
Dark bootloader 5.11.1540.9
https://drive.google.com/file/d/0B007JgCLgXQLR3FzZS1sSVc1SXc/edit?usp=sharing
5.11.1540.9 no red warning
https://drive.google.com/file/d/0B007JgCLgXQLNUFsS3BMaXk5WGM/edit?usp=sharing
Europe/International:
Dark bootloader 5.11.401.10
https://drive.google.com/file/d/0B007JgCLgXQLM2lubnFxQlluU1U/edit?usp=sharing
5.11.401.10 no red warning
https://drive.google.com/file/d/0B007JgCLgXQLakFaaUFBM2dlY2c/edit?usp=sharing
Asia - Malaysia/Singapore:
5.12.707.3 no red warning
https://drive.google.com/file/d/0B007JgCLgXQLZVBhTzc0SEdyWWM/edit?usp=sharing
Darkboot 5.12.707.3
https://drive.google.com/file/d/0B007JgCLgXQLZ3dqdHYzV1VTNDQ/edit?usp=sharing
Asia - India
5.12.707.104 Dark bootloader:
https://drive.google.com/file/d/0B007JgCLgXQLaXc3ZUpXeW5RSmM/edit?usp=sharing
5.12.707.104 w/red warning removed
https://drive.google.com/file/d/0B007JgCLgXQLYlZXbGo1UVRwWWs/edit?usp=sharing
T-Mobile US:
TMOUS darkboot 5.14.531.1:
https://drive.google.com/file/d/0B007JgCLgXQLVlgtVGtxU0NNc3M/edit?usp=sharing
TMOUS 5.14.531.1 red warning removed
https://drive.google.com/file/d/0B007JgCLgXQLQllZdEdPUG1tMFk/edit?usp=sharing
6.07.1540.1 Darkbootloader added: Thanks Seyaru and Vomer
https://drive.google.com/file/d/0B007JgCLgXQLRnUwUVlkT1hJNGs/edit?usp=sharing
6.09.401.5-Darkboot-MOD-NOWIPE added
https://drive.google.com/file/d/0B007JgCLgXQLNExuZnltVkpCcUk/edit?usp=sharing
For those of you using the darkboot firmwares, check out the dark bootsplash screens as well . Flash the zip in recovery. Enjoy!
Disclaimer:
I know these files are safe to flash, but I just have to say it.....Flash at your own risk, I will not be held responsible for bricks......
Can someone else comnfirm that this is safe to flash? You know, no bootloops or anything.
Thanks in advance.
Sent from my HTC One using XDA Premium 4 mobile app
I can, the pic is of my personal phone, as long as the usual steps are followed.
ANDR01DN00B said:
Can someone else comnfirm that this is safe to flash? You know, no bootloops or anything.
Thanks in advance.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
flashed with no issues
Couple more questions: Will this s-on my device if I am s-off, and this will work on a GSM device, (M7_UL) since the firmware was most likely pulled from a European M7.
Thanks again.
Sent from my HTC One using XDA Premium 4 mobile app
ANDR01DN00B said:
Couple more questions: Will this s-on my device if I am s-off, and this will work on a GSM device, (M7_UL) since the firmware was most likely pulled from a European M7.
Thanks again.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did flash in ul and still soff. Firmware doesn't make s on
Sent from my HTC One using XDA Premium HD app
hey guys, is this firmware safe? heard in another thread a lot of people got their devices bricked with modded firmware.. hope this one is good?
It will not s-on a s-off'd device. It will work on an M7UL, I know because I flashed this on my phone before I posted this here. I think this was originally pulled from Brightstar WWE 5.11.1540.9, but I'm not sure...
Edit:
OTA_M7_UL_K44_SENSE60_MR_BrightstarUS_WWE_5.11.1540.9-4.19.1540.9_P_release_370042lrklkigfk5j4biku.zip
Lol thanks everyone got it working looks better than I thought it would :good::good:
why the date in bootloader is november,2013..in my bootloader having firmware 4.19... shows feb,2014
any extra features why i should flash it..performance/stability/signal etc ?
anyway thanks.
Hi DeathAngel66669!
Please make a FW without darkboot.
hunkyycbz said:
why the date in bootloader is november,2013..in my bootloader having firmware 4.19... shows feb,2014
Click to expand...
Click to collapse
The bootloader is from the Google Edition Rom, which is 1.54, released in nov 2013. It contains hboot 1.54 from 3.58.1700.5 Google Edition firmware.
dtbinh said:
Hi DeathAngel66669!
Please make a FW without darkboot.
Click to expand...
Click to collapse
You can find it here: http://www.androidfilehost.com/?fid=23487008491964056
It isn't made by me, unzip it and remove recovery.img if you don't want twrp 2.7, and rezip the other files.
wzu7 said:
any extra features why i should flash it..performance/stability/signal etc ?
anyway thanks.
Click to expand...
Click to collapse
So far the phone seems snappier and the signal is a little better, but its only the first day.....
DeathAngel66669 said:
You can find it here: http://www.androidfilehost.com/?fid=23487008491964056
It isn't made by me, unzip it and remove recovery.img if you don't want twrp 2.7, and rezip the other files.
Click to expand...
Click to collapse
This FW contains hboot with red text.
Could you make FW without red text?
just flashed on my t-mobile m7,looks great thanks.
confirmed no brick,no wipe. A1
I also just flash this firmware and everything is alright
cheers ))))
dtbinh said:
This FW contains hboot with red text.
Could you make FW without red text?
Click to expand...
Click to collapse
This is the link to the original, unmodified 1.57.0000 hboot.
http://www.androidfilehost.com/?fid=23487008491964070
Firmware updated successfully (HTC M7_UL , SuperCID, Original CID is HTC_001) I noticed my hboot was downgraded to 1.54 though? Or is 1.54 the latest for the black hboot?
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1540.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3859mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Hi fellow tweakers!
I've bin a proud owner of a HTC One SV a year and half now.
I've installed a custom rom right away because of the extra bloatware and such.
(S-Off K2_U Europe)
Through the months ive flashed a few roms like Blue Donkey & Saturn roms.
Never had any problems or what so ever, nice and clean installs
Since a few weeks i saw a awesome Sense5 based rom, and you probably know which one i mean:
ViperSV from Team Venom.
Simply amazing, with exactly the tweaks i needed and a clean nice rom.
Even ROM Producers (rom developers w/e) like Old.Splatterhand said it was simply the best thing ever what happened to the OneSV.
I immediatly started flashing!
Now the part which you all came here for:
Robotic call sound with in- and outgoing calls..
They can hear my voice, but when i here theires, it sounds like a sasquatch or whatever
I offcourse started searching in the main thread about this issue
I saw a few with the same problem.
A few ppl (among team venom) stated it could be the firmware. (bug from updating to 4.2.2)
Ive been throwing myself in the index thread for a few hours with no succes.
How i flashed the ViperSV Rom:
0) Started from Saturn III - HTC One SV | Jelly Bean 4.1.2 (All in one edition)
1) Reboot Recovery
2) Check MD5 -> Flashed ViperSV using TWRP 2.7
3) Flashed the boot.img sep.
4) Full Wipe including dalvik cache
What i did to solve the robotic voice issue:
1) Used other firmware:
RUU_K2_U_ICS_40_HTC_Europe_1.17.401.3_Radio_0.12.4 0.00.14_2_10.49.40.11L_release_302178_signed.exe
-Got stuck by sending ROM image to the OneSV
2) Tried every kernel for K2_U in the index thread.
http://forum.xda-developers.com/showthread.php?t=2655793
-Issue persists.
3) Other ROMS which had no use offcourse.
I've been looking for a exact answer a few weeks now, and i've tried different orders during flashing *.img files etc.
Feel like am stuck in a vicious circle bwohh.
And i know iam missing a certain part.. that's the most ignorant feeling ever when you're working in the IT business .. :x
XDA you rule!
This is for sure the firmware (missing files for 4.2.2).
You have said you are S-off, with k2u, yes?
Then download this file: http://d-h.st/tAc
And flash it this way:
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
Or rename it to PL80IMG.zip, copy the zip to your sdcard, boot into bootloader and confirm to flash.
After that, your phone should be good to go for ViperSV!
old.splatterhand said:
After that, your phone should be good to go for ViperSV!
Click to expand...
Click to collapse
Thanks for your time!
So weird..
With the first method with 'fastboot flash zip firmware.zip' i get:
error: cannot open 'firmware.zip'
Click to expand...
Click to collapse
Second method:
1) rename firmware.zip to PL80IMG.zip.
2) Reboot the phone into Bootloader.
3) I see that it cant load the zipfile 'no image'
When i try to flash the zipfile manually i also gives a error
' error flashing zip'
Then we need more information about your phone model, please!
Connect your phone with fastboot and type into the cmd:
Code:
fastboot getvar all
Put the output here (except your IMEI & Serial number)
old.splatterhand said:
Then we need more information about your phone model, please!
Click to expand...
Click to collapse
Thanks for the quick help man!
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.15.40a.00.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -------------------------------
(bootloader) imei: --------------------------------
(bootloader) product: k2_u
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8013000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4092mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.070s
Click to expand...
Click to collapse
Hm, only thing i see is your different Cid.
So try the same steps with Supercid.
You can get SuperCid with fastboot cmd:
Code:
fastboot oem writecid 11111111
old.splatterhand said:
Hm, only thing i see is your different Cid.
So try the same steps with Supercid.
You can get SuperCid with fastboot cmd:
Code:
fastboot oem writecid 11111111
Click to expand...
Click to collapse
Bootloader changed from HTC__E11 to:
(bootloader) cidnum: 11111111
Click to expand...
Click to collapse
Rebooted, and repeated same steps.
At fastboot flash zip firmware.zip :
error: cannot open 'firmware.zip'
Click to expand...
Click to collapse
Issue persists
Is it normal, that the phones screen keeps showingthe HTC logo ? during this process ?
Seems like its stuck, shouldnt it start the RUU ?
PL80IMG.zip also? Is your bootloader locked?
Make a backup from your important data and try to flash the RUU.
old.splatterhand said:
PL80IMG.zip also? Is your bootloader locked?
Make a backup from your important data and try to flash the RUU.
Click to expand...
Click to collapse
PL80IMG.zip gives same error.
The phone is stuck on the black HTC screen during this process (fastboot oem rebootRUU).
Is this normal ?
Quick way to check the bootloader is unlocked ?
I'ive unlocked it before with my previous rom.
** Update.
In the meantime i've unlocked my bootloader.
Its unlocked succesfully
sending 'unlocktoken' (0 KB)...
OKAY [ 0.135s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.005s]
finished. total time: 0.141s
Click to expand...
Click to collapse
Only the disclaimer screen does not appear. (the phone is still in fastboot usb)
But when my phone is booted into bootloader i see ***TAMPERED *** and *** UNLOCKED ***
Does that means that its already unlocked ?
Also, when i give the command:
fastboot oem rebootruu
Click to expand...
Click to collapse
it gets stuck at a black screen with HTC txt logo.
When doing the reboot ruu method that HTC logo is normal. You just need to be patient while it proceeds. When done just reboot. Sometimes these steps will result in errors. They don't always work on the first try for some reason. There are cases known where individuals will have to attempt multiple times before the process works. I personally do not know the cause for this, but it has been recognized in the XDA community as a minor hiccup. Regardless lol, just keep on.
Sent from my C525c using Tapatalk
Your phone is unlocked now, then try the PL80IMG.zip way again.
Make sure that you are in bootloader mode & your file is on the external sdcard.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Beside what Modding.MyMind told us, i see no other reason, why it should not work.
You are S-Off, bootloader unlocked, SuperCID, modelid is ok.
mike1986. has also made a nice guide about flashing firmware.zip. He made it for HTC One M8, but for One SV its the same.
Maybe i missed some steps, so please check it out here
(Only read the FAQ & How to flash, do not use any download/file from there!!!)
Modding.MyMind said:
Regardless lol, just keep on.
Click to expand...
Click to collapse
old.splatterhand said:
Your phone is unlocked now, then try the PL80IMG.zip way again.
Make sure that you are in bootloader mode & your file is on the external sdcard.
Beside what Modding.MyMind told us, i see no other reason, why it should not work.
You are S-Off, bootloader unlocked, SuperCID, modelid is ok.
Click to expand...
Click to collapse
Both, really thanks for your time and effort!
When into Bootloader its loading the PL80IMG.zip.
when its done its highlighted on HBOOT and says:
'press power to reboot'
Click to expand...
Click to collapse
fastboot flash zip firmware.zip:
c:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash zip firm
ware.zip
sending 'zip' (34426 KB)...
OKAY [ 2.388s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping for pre-update...
(bootloader) start image[sbl2] flushing...
(bootloader) [RUU]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping for pre-update...
(bootloader) start image[sbl3] flushing...
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping for pre-update...
(bootloader) start image[rpm] flushing...
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping for pre-update...
(bootloader) start image[tz] flushing...
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 6.951s
Click to expand...
Click to collapse
I will reset my phone.
reinstall viperSV
flash sep firmware.zip
and check again
only the order confuses me sometimes :/
Repeat the same commands immediately again and you should be fine!
old.splatterhand said:
Repeat the same commands immediately again and you should be fine!
Click to expand...
Click to collapse
Since the beginning i've had problems with the firmware.zip:
I couldnt and still cannot move the ZIP to my SDcard:
I get an error message saying:
CANNOT COPY ITEM: 'The device has either stopped responding or has been disconnected'
and i tried redownloading it and such.
( i can move other zip files, only this one i can't,also renaming the zip file doesnt help)
i've unpacked it, and when i try rezipipng it:
The archive is corrupt .. :/
Only when i rename it to PL80IMG, it will copy to my sd card.. very strange..
When it was finally on the sdcard ive renamed it to firmware.zip.
Only that one seems to fail.
Could you reupload a new one ?
Iam guessing this could be a weird multiplecause problem :/
** UPDATE ***
After a few rename and rezip actions i finally can flash the firmware.zip:
c:\adt-bundle-windows-x86_64-20140321\sdk\platform-tools>fastboot flash zip ol
r.zip
sending 'zip' (34426 KB)...
OKAY [ 2.266s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,16
(bootloader) [RUU]UZ,adsp,26
(bootloader) [RUU]UZ,adsp,37
(bootloader) [RUU]UZ,adsp,49
(bootloader) [RUU]UZ,adsp,60
(bootloader) [RUU]UZ,adsp,71
(bootloader) [RUU]UZ,adsp,83
(bootloader) [RUU]UZ,adsp,94
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) start image[boot] unzipping & flushing...
(bootloader) [RUU]UZ,boot,0
(bootloader) [RUU]UZ,boot,12
(bootloader) [RUU]UZ,boot,25
(bootloader) [RUU]UZ,boot,37
(bootloader) [RUU]UZ,boot,50
(bootloader) [RUU]UZ,boot,62
(bootloader) [RUU]UZ,boot,73
(bootloader) [RUU]UZ,boot,83
(bootloader) [RUU]UZ,boot,95
(bootloader) [RUU]UZ,boot,100
(bootloader) [RUU]WP,boot,0
(bootloader) [RUU]WP,boot,99
(bootloader) [RUU]WP,boot,100
(bootloader) ...... Successful
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,61
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) start image[recovery] unzipping & flushing...
(bootloader) [RUU]UZ,recovery,0
(bootloader) [RUU]UZ,recovery,12
(bootloader) [RUU]UZ,recovery,22
(bootloader) [RUU]UZ,recovery,34
(bootloader) [RUU]UZ,recovery,45
(bootloader) [RUU]UZ,recovery,57
(bootloader) [RUU]UZ,recovery,72
(bootloader) [RUU]UZ,recovery,84
(bootloader) [RUU]UZ,recovery,96
(bootloader) [RUU]UZ,recovery,100
(bootloader) [RUU]WP,recovery,0
(bootloader) [RUU]WP,recovery,99
(bootloader) [RUU]WP,recovery,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) [RUU]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ...... Successful
(bootloader) [RUU]UZ,radio,6
(bootloader) [RUU]UZ,radio,12
(bootloader) [RUU]UZ,radio,18
(bootloader) [RUU]UZ,radio,25
(bootloader) [RUU]UZ,radio,31
(bootloader) [RUU]UZ,radio,38
(bootloader) [RUU]UZ,radio,44
(bootloader) [RUU]UZ,radio,50
(bootloader) [RUU]UZ,radio,56
(bootloader) [RUU]UZ,radio,63
(bootloader) [RUU]UZ,radio,69
(bootloader) [RUU]UZ,radio,75
(bootloader) [RUU]UZ,radio,82
(bootloader) [RUU]UZ,radio,88
(bootloader) [RUU]UZ,radio,94
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,50
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
OKAY [102.422s]
finished. total time: 104.687s
Click to expand...
Click to collapse
Looks good!
Allthough the green progressbar on the screen is still on 95%
I'll wait a few minutes.
If nothing happens i will fastboot reboot it.
*** Problem fixed! ***
Thanks!
I had so much problems trying to find the right firmware.
Then when i was so close, problems while copying the solution to my sd
Now finally after a few tries in the right order... perfect!
Extract it directly from the OTA update:
http://fotadl.htc.com/OTA_K2_U_JB422_SENSE50_MR_HTC_Europe_3.11.401.106-2.14.401.107_release_339145qf6n2sk971fk7x3k.zip
TGN said:
Allthough the green progressbar on the screen is still on 95%
I'll wait a few minutes.
Click to expand...
Click to collapse
Should be normal. 100% is the reboot action.
*** Problem fixed! ***
Click to expand...
Click to collapse
Nice
Can someone write a small guide how to solve robotic issue? I will include in ViperSV OP so future members experiencing this problem can solve it
xpirt
xpirt said:
Can someone write a small guide how to solve robotic issue? I will include in ViperSV OP so future members experiencing this problem can solve it
xpirt
Click to expand...
Click to collapse
Flash the rom with your guide.
Then flash seperatly the firmware files for the radio:
http://d-h.st/tAc
1) put the files in your fastboot folder
2) Run the following commands while in fastboot:
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Then flash the rom you like with 4.2.2!
TGN said:
Flash the rom with your guide.
Then flash seperatly the firmware files for the radio:
http://d-h.st/tAc
1) put the files in your fastboot folder
2) Run the following commands while in fastboot:
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Then flash the rom you like with 4.2.2!
Click to expand...
Click to collapse
Appreciated Will put it as soon as I'm home.
xpirt
I have the same problem, but in my case it seems to be a hardware related issue.
Can someone upload a sample of this distorted voice call? (just to be sure it's hardware related in my case)
So that's my story cut short:
I was and is S-On
I had HBoot v1.13, upgraded it by RUU flashing firmware.zip from OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip
Now I have HBoot 2.15 and TeamWin Recovery 2.8 .
ZenROM flashes with no problem, but that's still no stock, as the signature of /system is broken.
But in order to get S-Off, which is necessary at least to gain hboot 2.16 for Liberty ROM, I need to get stock ROM.
This is necessary in order for phone to boot with bootloader locked(signature should validate), which is a prereq for Faceplam S-Off(as I understand)
But every RUU I flash says:
Code:
sending 'zip' (534178 KB)...
OKAY [ 21.050s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 73.893s
And every OTA I try to install in TWRP says I have a CID mismatch , no matter leave I my original (HTC_A07) or SuperCID
Help anyone?
That's my config. I deliberately downed main version, because otherwise during RUU flash I got "invalid main version" instead
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT23XW411592
(bootloader) imei: *****************
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__A07
(bootloader) battery-status: good
(bootloader) battery-voltage: 4203mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
Actually you don't need a stock rom. As far as I know you only need a sense rom. I S-OFFed while I had this rom installed.
Flippy498 said:
Actually you don't need a stock rom. As far as I know you only need a sense rom. I S-OFFed while I had this rom installed.
Click to expand...
Click to collapse
Which S-Off did you use? Rumrunner and firewater didn't work for me
I used facepalm. I know a lot of people here say that it won't work on hboot 2.15 but for me it did work. Don't know why...
Flippy498 said:
I used facepalm. I know a lot of people here say that it won't work on hboot 2.15 but for me it did work. Don't know why...
Click to expand...
Click to collapse
But with facepalm you need to flash PJ4010000.zip (or whatsitsname) in RUU mode(mean you should relock) and when it says "Error: 92 supercid blablablah" you should boot immediately, right?
And you're still with locked bootloader.
And on custom ROM, which means on boot the signature will be checked AND will fail, so it won't boot at all - that's what happens to me...
Tell me I'm wrong, cause otherwise I can't s-off neither I can flash stock...
Well, I SOFFed more than one and a half year ago. But as far as I remember you don't need to relock since you don't want to run a RUU.
Just looked it up. The instructions in the facepalm thread do not mention that you need to relock. Try again to S-OFF without relocking.
Modified Firmware Without The Red Developer's WarningPlease make sure you understand EVERY STEP before trying to flash a new firmware. I AM NOT RESPONSIBLE FOR ANYTHING GOING WRONG OR ACCIDENTAL BRICKS!
This firmware is WITHOUT the development warning overlay:
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.
This is the custom version firmware with modified HBOOT to remove the red warning.
*** This will NOT wipe your SD partition ***
But please make a back up before flashing for safety.
Requirements for flashing: S-OFF
If you do not know how to flash a Firmware or it is your first time, follow Vomer's Guide for detailed instructions.
If you do know what you are doing, here is a reminder of the commands:
Code:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip C:\adb\Firmware_File_Name.zip
fastboot flash zip C:\adb\Firmware_File_Name.zip (repeat)
fastboot reboot
DOWNLOAD LINKS: (Show appreciation and hit the THANKS below)
Latest:
fw_7.19.401.2-NoRed_NoWipe
Older Versions:
fw_7.15.401.1_NoWipe_NoRed
fw_6.09.401.12-NoWipe_NoRed
fw_6.09.401.11_custom_nored
fw_6.09.401.10_custom_nored
HTC M9 Firmware without Red Warning
* I am not adding any new FW for M7. If there is a new release and you can provide the custom-FW I can modify the red warning out for you per request and post it here.
fw_7.19.401.51 can be found here
Credits:
@vomer for his amazing guide.
Thanks a lot! Its what I have been looking for
Sent from my HTC One using XDA Free mobile app
I'm getting the following:
C:\HTC One Toolkit - Squabbi - 3.1.2>fastboot flash zip fw_6.09.401.11_custom_nored.zip
target reported max download size of 1526722560 bytes
sending 'zip' (29585 KB)...
OKAY [ 2.500s]
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: 3.014s
Click to expand...
Click to collapse
I'm running ARHD 83.1. This is what I have:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.161.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3861mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Do I need to change my CID? If yes, to what?
Can I also flash on 4.4?
Cheers Tobi
Sent from my One using XDA Free mobile app
Is this any different from this release?
Works great, thanks.
---------- Post added at 10:30 AM ---------- Previous post was at 10:29 AM ----------
polys643 said:
Do I need to change my CID? If yes, to what?
Click to expand...
Click to collapse
Either add your CID to the android-info.txt or switch to supercid.
I also got FAILED (remote: 99 unknown fail)
but it stil shows FW 6.09.401.11 CL366813...so I guess it didn't fail...
dep
Thank you for grabbing this.
I've tried a couple of times and it fails at:
C:\adb>fastboot flash zip c:\adb\firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (29585 KB)...
OKAY [ 2.449s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 2.870s
My details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3930mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.265s
Any ideas?
**Edit**
I checked on my phone and the firmware is still 5.28.605.2
I don't know why it's blank above?
Seems to have worked fine for me after changing cid to 11111111.
Thanks a bunch!
Can you also make it dark?
Toda
after fastboot reboot i get stuck at oem rebootRUU screen.
I mean the sliver htc logo screen now what I have to do
plz help
MY device is s-off and supercid
Hi, a new version is available:
(@LlabTooFeR) HTC One M7 receives maintenance update. ROM Version is 6.09.401.12 (193.94mb). Main changes related to NFC module. Where can download this new fw?
kreatik said:
Hi, a new version is available:
(@LlabTooFeR) HTC One M7 receives maintenance update. ROM Version is 6.09.401.12 (193.94mb). Main changes related to NFC module. Where can download this new fw?
Click to expand...
Click to collapse
You can find it here http://forum.xda-developers.com/showthread.php?t=2316726 , there is a NO WIPE version but the person who provides the firmwares does not remove the red text nor does he do a Dark version..... Myself, I am going to wait for a Dark version that has the red text removed...
apaquette420 said:
You can find it here http://forum.xda-developers.com/showthread.php?t=2316726 , there is a NO WIPE version but the person who provides the firmwares does not remove the red text nor does he do a Dark version..... Myself, I am going to wait for a Dark version that has the red text removed...
Click to expand...
Click to collapse
Thanks
Successfully flashed with insertcoin-m7_4.0.5!
C:\sdk>fastboot flash zip fw_6.09.401.12-NoWipe_NoRed.zip
..................................................................................
C:\sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA387W.......
(bootloader) imei: ..............
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
C:\sdk>fastboot reboot
rebooting...
finished. total time: 0.031s
tks
I've just updated. Everything went fine.
The main change between de .11 and .12 is radio's? Or is it just NFC?
Confirm -Working fine
C:\>fastboot flash zip C:\fw_6.09.401.12-NoWipe
_NoRed.zip
target reported max download size of 1514139648 bytes
sending 'zip' (29302 KB)...
OKAY [ 2.347s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 3.958s
C:\>fastboot flash zip C:\fw_6.09.401.12-NoWipe
_NoRed.zip
< waiting for device >
target reported max download size of 1514139648 bytes
sending 'zip' (29302 KB)...
OKAY [ 2.360s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[adsp] unzipping & flushing...
(bootloader) [RUU]UZ,adsp,0
(bootloader) [RUU]UZ,adsp,15
(bootloader) [RUU]UZ,adsp,27
(bootloader) [RUU]UZ,adsp,37
(bootloader) [RUU]UZ,adsp,49
(bootloader) [RUU]UZ,adsp,60
(bootloader) [RUU]UZ,adsp,72
(bootloader) [RUU]UZ,adsp,82
(bootloader) [RUU]UZ,adsp,94
(bootloader) [RUU]UZ,adsp,100
(bootloader) [RUU]WP,adsp,0
(bootloader) [RUU]WP,adsp,100
(bootloader) ...... Successful
(bootloader) start image[cir] unzipping & flushing...
(bootloader) [RUU]UZ,cir,0
(bootloader) [RUU]UZ,cir,100
(bootloader) ...... Successful
(bootloader) start image[pg2fs_spcustom] unzipping & flushing...
(bootloader) [RUU]UZ,pg2fs_spcustom,0
(bootloader) [RUU]UZ,pg2fs_spcustom,22
(bootloader) [RUU]UZ,pg2fs_spcustom,48
(bootloader) [RUU]UZ,pg2fs_spcustom,70
(bootloader) [RUU]UZ,pg2fs_spcustom,97
(bootloader) [RUU]UZ,pg2fs_spcustom,100
(bootloader) ...... Successful
(bootloader) start image[rpm] unzipping & flushing...
(bootloader) [RUU]UZ,rpm,0
(bootloader) [RUU]UZ,rpm,100
(bootloader) [RUU]WP,rpm,0
(bootloader) [RUU]WP,rpm,100
(bootloader) ...... Successful
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-3,0
(bootloader) [RUU]UZ,sbl1-3,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-3,0
(bootloader) [RUU]WP,sbl1-3,100
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) [RUU]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ..... Bypassed
(bootloader) start image[tp] unzipping & flushing...
(bootloader) [RUU]UZ,tp,0
(bootloader) [RUU]UZ,tp,100
(bootloader) ...... Successful
(bootloader) start image[tz] unzipping & flushing...
(bootloader) [RUU]UZ,tz,0
(bootloader) [RUU]UZ,tz,100
(bootloader) [RUU]WP,tz,0
(bootloader) [RUU]WP,tz,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,5
(bootloader) [RUU]UZ,radio,11
(bootloader) [RUU]UZ,radio,17
(bootloader) [RUU]UZ,radio,23
(bootloader) [RUU]UZ,radio,29
(bootloader) [RUU]UZ,radio,34
(bootloader) [RUU]UZ,radio,40
(bootloader) [RUU]UZ,radio,46
(bootloader) [RUU]UZ,radio,52
(bootloader) [RUU]UZ,radio,58
(bootloader) [RUU]UZ,radio,63
(bootloader) [RUU]UZ,radio,69
(bootloader) [RUU]UZ,radio,75
(bootloader) [RUU]UZ,radio,80
(bootloader) [RUU]UZ,radio,86
(bootloader) [RUU]UZ,radio,92
(bootloader) [RUU]UZ,radio,98
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,23
(bootloader) [RUU]WP,radio,46
(bootloader) [RUU]WP,radio,69
(bootloader) [RUU]WP,radio,92
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
(bootloader) ...... Successful
OKAY [ 54.556s]
finished. total time: 56.916s
C:\Users\Gecata>fastboot reboot
rebooting...
finished. total time: 0.047s
3DDude said:
I've just updated. Everything went fine.
The main change between de .11 and .12 is radio's? Or is it just NFC?
Click to expand...
Click to collapse
Radio not changed - see attached screenshots.
NFC - may be, I'm not sure!
Is that not because of your rom and the version itself?
See on both screens you have 6.09.401.5 as build number
Or will the new radio versions be detected in android - when you flash the firmware?
Or is that just the radio thats in your rom?
Working very well. Thanks a lot
---------- Post added at 02:23 PM ---------- Previous post was at 01:56 PM ----------
gecata said:
Radio not changed - see attached screenshots.
NFC - may be, I'm not sure!
Click to expand...
Click to collapse
Yes, the Radio has not been changed since 6.09.401.5
If something is working well, there is no reason to change....