My m8 has an unlocked bootloader with s-on and i recently just used a nandroid backup which flashed the stock recovery and i updated to newest 5.0 update my phone was with t-mobile but it is factory unlocked now. Whenever I try to flash philz or twrp through fastboot it gives me:
target reported max download size of 1826414592 bytes
sending 'twrp' (16086 KB)...
OKAY [ 1.469s]
writing 'twrp'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.047s
How am i supposed to flash a custom recovery
Are you trying to do it in fastboot oem rebootRUU or just normal fastboot? You should be in the bootloader and just use fastboot flash recovery recovery.img
EddyOS said:
Are you trying to do it in fastboot oem rebootRUU or just normal fastboot? You should be in the bootloader and just use fastboot flash recovery recovery.img
Click to expand...
Click to collapse
I tried both
Related
Hello. I was following a video tutorial named: How To change Hboot + Install Jelly Bean on Your HTC One X - JB on HOX
at the stage where I use flash zip firmware.zip I can not get out of the bootloader. Please can someone guide me on how to recover my phone from this.
******RELOCKED*****
******Security Warning******
ENDEAVOUR PVT SHIP S-ON RL
HBOOT-0.43.0000
CPLD-None
MICROP-None
The commands are below which have lead to this disaster. Please can someone assist me. Thanks.
c:\htc>fastboot-windows.exe flash boot boot.img
sending 'boot' (4974 KB)... OKAY
writing 'boot'... INFOFormat partition LNX done
OKAY
c:\htc>fastboot-windows.exe erase cache
erasing 'cache'... OKAY
c:\htc>fastboot-windows.exe oem lock
... FAILED (command write failed (Unknown error))
c:\htc>fastboot-windows.exe oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
c:\htc>fastboot-windows.exe oem rebootRUU
... INFOSave data from original MSC...
INFOSave data from SIF...
INFOUpdate partition data to SIF partition
INFOoffset = 0
INFOUpdate partition data from original MSC...
INFOoffset = 0
INFO[MSG] OKAY
OKAY
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... OKAY
writing 'zip'... INFOadopting the signature contained in this image...
INFOsignature checking...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... FAILED (remote: (00030003))
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... ^C
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... FAILED (remote: (00120000))
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... OKAY
writing 'zip'... FAILED (remote: not allowed)
c:\htc>fastboot-windows.exe flash zip firmware.zip
sending 'zip' (12875 KB)... FAILED (unknown status code)
I have unlocked my bootloader again (frrom the HTCDEV website). I can now get into recovery. I have restored my backup which i made before.
I then copied an old boot.img from my original rom
c:\htc>fastboot-windows.exe flash boot boot.img
< waiting for device >
sending 'boot' (4290 KB)... OKAY
writing 'boot'... INFOFormat partition LNX done
OKAY
Then thankfully my phone booted ok back to how it was originally.
You can't flash the 1.36 hboot,
coz your hboot is to low, with version 0.43.
The easiest way would be, to flash the 2.17 ruu,
and after that, you could Update your hboot.
Gesendet von meinem HTC One X mit Tapatalk 2
thanks for the reply. so where can i find the 2.17 ruu
Also can you explain a bit on the steps that I need to complete with the 2.17 ruu
uk_network said:
thanks for the reply. so where can i find the 2.17 ruu
Click to expand...
Click to collapse
htcruu.com
Searching would have got you the answer quicker.
BenPope said:
htcruu.com
Searching would have got you the answer quicker.
Click to expand...
Click to collapse
ok thanks. I should add im from the UK. Will this RUU do the job?
tcruu.com/Endeavor/RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
uk_network said:
ok thanks. I should add im from the UK. Will this RUU do the job?
tcruu.com/Endeavor/RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
Click to expand...
Click to collapse
If your phone was destined for the UK, yeah.
fastboot get version-main
Will tell you which ROM you had originally, so the 401 needs to match.
I can't get that command to work with my fastboot.
c:\htc>fastboot-windows.exe fastboot get version-main
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
The same also happens if i type.
c:\htc>fastboot-windows.exe get version-main
Sorry
fastboot getvar version-main
BenPope said:
Sorry
fastboot getvar version-main
Click to expand...
Click to collapse
For him it's 'fastboot-windows.exe getvar version-main'
version-main: 1.26.206.2
c:\htc>fastboot-windows.exe getvar version-main
version-main: 1.26.206.2
When I check on htcruu.com/?dir=Endeavor
I can find:
RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed.exe
This has matching 206 version.
But this doesn't have 2.17 as mentioned previously.
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_sined.exe
Any ideas on which one to choose?
The one that matches. Hopefully you'll get OTA updates to 2.17.206.x
RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.120 4.90.13_release_251230_signed.exe
I do notice in the title that it says 02_UK im not on 02 im on three.co.uk would this be an issue? if so its the only RUU that has 206 in the title. Also Is this the only way to update hboot versioin?
Thanks to all who are contributing and for your continued support in this matter. I had a shock when I almost originally bricked my one x.
Well where did you get the phone from?
That's the right RUU.
You can update the firmware by locking it, flashing the updated firmware and unlocking it. Either way your phone is gonna get wiped.
I bought the phone from ebay.co.uk from the UK
I am a little confused by this picture it says 1.29.401.11
Should i go ahead with the upgrade?
When i origianly did the below command i got a different version.
fastboot-windows.exe getvar version-main
version-main: 1.26.206.2
There is a discrepancy between 401 and 206 or does this not matter? or can i now use this ruu??
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
And to confirm the next step, after this update i will need to relock the boot loader and then perform the update and then unlock it.
fastboot-windows.exe oem lock
fastboot-windows.exe oem rebootRUU
fastboot-windows.exe flash zip firmware.zip
then perform the unlock from the htcdev site.
Hey guys, dont know really where else to post this, but i need help upgrading my hboot.
Im currently on hboot 1.12 S-ON, cid VODAPO21
i tried flashing 1.36 firmware and it didnt work, gave an error remote:not allowed
i assume i need to go up in increments.
Trouble is , not sure which ones i should flash first and also where to find it. Ive downloaded RUU for my cid versions 1.26 and 1.29...not sure if you can extract the firmware from them, or how its done. Tried opening it in winrar/7-zip and could open em.
Still not there yet.
Still no luck I am afraid. I have tried both of the below RUU's and receive the error in the attached screenshot.
The RUU's that I have tried both give the same error. They are:
RUU_ENDEAVOR_U_ICS_40_O2_UK_1.26.206.2_Radio_1.1204.90.13_release_251230_signed
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed
Thanks so much to the person who can help get me upgraded to Jelly Bean.
Anyone ?? Im still wanting to update to jellybean and can't yet. Can someone please help me out this this.
You did getvar version main and it said you have a '206 ROM, if a new enough RUU can't be found, you'll have to flash a backup. If you don't have one, check the backups thread for somebody else's. It has to be '206.
BenPope said:
You did getvar version main and it said you have a '206 ROM, if a new enough RUU can't be found, you'll have to flash a backup. If you don't have one, check the backups thread for somebody else's. It has to be '206.
Click to expand...
Click to collapse
I have a backup of my stock rom. But i rooted it and then backed it up. Would this work?
hey guys
i got a problem with my phone & recovery
i have a galaxy nexus gsm
and i wanna flash a 4.4.4 android on my nexus
but i can't switch to recovery because i can't flash it
when i'm in bootloader and i wanna flash the recovery
( in cmd ) i got this eror :
Code:
C:\Users\Orel>cd\
C:\>cd galaxynexusrootnew
C:\GalaxyNexusRootNew>fastboot flash recovery openrecovery.img
sending 'recovery' (13586 KB)...
OKAY [ 1.288s]
writing 'recovery'...
FAILED (remote: Write Fail)
finished. total time: 1.337s
recovery file : openrecovery-twrp-2.7.1.1-hammerhead.img
and i also tried this : openrecovery-twrp-2.7.1.0-maguro.img
sucessfully flashed but when in bootloader i choose Recovery mode , it reboots and bootloader came up
Oracle_Eldorado said:
hey guys
i got a problem with my phone & recovery
i have a galaxy nexus gsm
and i wanna flash a 4.4.4 android on my nexus
but i can't switch to recovery because i can't flash it
when i'm in bootloader and i wanna flash the recovery
( in cmd ) i got this eror :
Code:
C:\Users\Orel>cd\
C:\>cd galaxynexusrootnew
C:\GalaxyNexusRootNew>fastboot flash recovery openrecovery.img
sending 'recovery' (13586 KB)...
OKAY [ 1.288s]
writing 'recovery'...
FAILED (remote: Write Fail)
finished. total time: 1.337s
recovery file : openrecovery-twrp-2.7.1.1-hammerhead.img
and i also tried this : openrecovery-twrp-2.7.1.0-maguro.img
sucessfully flashed but when in bootloader i choose Recovery mode , it reboots and bootloader came up
Click to expand...
Click to collapse
YOU CANNOT USE Another device's recovery. "openrecovery-twrp-2.7.1.1-hammerhead.img" is for Nexus 5 and won't work on Nexus.
Try flashing another recovery WHICH IS for Maguro.
OR if you have toro or toroplus then flash the correct recovery for them.
Hello,
I have a M9 rooted with android 5.0.2.
I downloaded this file:
https://www.androidfilehost.com/?fid=95916177934550733
I compiled the desired kernel into Image.gz and then create boot.img on Ubuntu.
Code:
cp boot_signed.img boot.img
abootimg -u boot.img.test -k Image.gz
I then do in download mode:
Code:
fastboot boot boot.img
I get this error on boot in cmd window:
FAILED (remote: dtb not found)
How can it be fixed?
Did not saw any information about this problem on M9 forum.
Thank you in advance!
adryyandc said:
Hello,
I have a M9 rooted with android 5.0.2.
I downloaded this file:
https://www.androidfilehost.com/?fid=95916177934550733
I compiled the desired kernel into Image.gz and then create boot.img on Ubuntu.
Code:
cp boot_signed.img boot.img
abootimg -u boot.img.test -k Image.gz
I then do in download mode:
Code:
fastboot boot boot.img
I get this error on boot in cmd window:
FAILED (remote: dtb not found)
How can it be fixed?
Did not saw any information about this problem on M9 forum.
Thank you in advance!
Click to expand...
Click to collapse
The file you downloaded is a HTC RUU. To install it you need s-off and a Developer Edition M9
rename it 0PJAIMG.ZIP, place it on ext sd card formatted in FAT32, reboot your hima into DOWNLOAD_MODE, agree and it flashes the phone
clsA said:
The file you downloaded is a HTC RUU. To install it you need s-off and a Developer Edition M9
rename it 0PJAIMG.ZIP, place it on ext sd card formatted in FAT32, reboot your hima into DOWNLOAD_MODE, agree and it flashes the phone
Click to expand...
Click to collapse
Ok, Thank you! Don't really need RUU then.
I will read boot image from device with:
Code:
dd if=/dev/block/mmcblk0p63 of=/sdcard/boot.img
beacause boot is linked with /dev/block/mmcblk0p63
and then replace zImage with my kernel zImage with abootimg.
but remeber you need to be S-Off.
LLegion said:
but remeber you need to be S-Off.
Click to expand...
Click to collapse
I was able to extract boot partition and use abootimg on it to update the kernel successfully (the boot.img has 64 MB.), but
Code:
fastboot boot boot.img
does not work.
It says:
Code:
downloading 'boot.img'...
OKAY [ 3.980s]
booting...
and cmd does not return to normal after waiting 30 mins.
Is fastboot boot command deprecated? Could be a driver problem?
adryyandc said:
I was able to extract boot partition and use abootimg on it to update the kernel successfully (the boot.img has 64 MB.), but
Code:
fastboot boot boot.img
does not work.
It says:
Code:
downloading 'boot.img'...
OKAY [ 3.980s]
booting...
and cmd does not return to normal after waiting 30 mins.
Is fastboot boot command deprecated? Could be a driver problem?
Click to expand...
Click to collapse
The M9 uses aboot not hboot .. as far as I know you can't "boot" anything from fastboot
clsA said:
The M9 uses aboot not hboot .. as far as I know you can't "boot" anything from fastboot
Click to expand...
Click to collapse
Thank you!
I give the following commands:
Code:
fastboot flash boot boot.img.test
fastboot reboot
and i get:
Code:
target reported max download size of 800000000 bytes
sending 'boot' (65536 KB)...
OKAY [ 4.850s]
writing 'boot'...
(bootloader) HOSD CL#xxxxxx
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.870s]
finished. total time: 8.720s
but the device will return to fastboot menu.
I want to flash stock image and now i'm stuck.
Code:
fastboot flash boot boot.img
I get the following message:
Code:
target reported max download size of 536870912 bytes
sending 'boot' (65536 KB)...
OKAY [ 2.160s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 2.180s
adryyandc said:
Thank you!
I give the following commands:
Code:
fastboot flash boot boot.img.test
fastboot reboot
and i get:
Code:
target reported max download size of 800000000 bytes
sending 'boot' (65536 KB)...
OKAY [ 4.850s]
writing 'boot'...
(bootloader) HOSD CL#493992
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 3.870s]
finished. total time: 8.720s
but the device will return to fastboot menu.
I want to flash stock image and now i'm stuck.
Code:
fastboot flash boot boot.img
I get the following message:
Code:
target reported max download size of 536870912 bytes
sending 'boot' (65536 KB)...
OKAY [ 2.160s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 2.180s
Click to expand...
Click to collapse
The error message says your not S-OFF
Sent from my HTC One M9 using Tapatalk
clsA said:
The error message says your not S-OFF
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
How can i put the device in S-OFF mode if the device does not boot?
As i could flash a bad kernel in first step it means i had S-OFF previously?
I was able to upload my stock boot.img (the one backed-up) even i had S-ON with:
Code:
fastboot oem rebootRUU
fastboot flash boot boot.img
fastboot reboot
Don't know why in download mode i was not able to do this.
I have build number 1.32.617.6 CL493992 release-keys
Do i really need to be S-OFF to upload only my custom kernels? According to HTC i don't need to because bootloader is unlocked and:
"What is meant by unlocking the bootloader is that certain partitions are unlocked to provide write access. Specifically: boot, system and recovery. "
http://www.htcdev.com/bootloader/about_unlock_process
Answer: Yes, i need too!
Thanks!
I was able to S-OFF the device. Now the problem is that my compiled unmodified kernels from HTC site won't boot. Any ideea why?
Would i be able to convert this device to Developer Edition using AT&T RUU?
Fixed my problem by using right tool to unpack and repack boot image.
I used this one:
https://github.com/xiaolu/mkbootimg_tools
Help
I have a big problem with my HTC ONE M9. I used a custom rom and I tried to get beck to stock rom without any back up of custom or stock rom. I lost everything and I tried more but I couldn't do anything. The situation now is that I stuck in the logo with no recovery mode or bootloader mode. just download mode. S ON, RELOCKED, Software Modified.
I need your help.
elmasry82 said:
I have a big problem with my HTC ONE M9. I used a custom rom and I tried to get beck to stock rom without any back up of custom or stock rom. I lost everything and I tried more but I couldn't do anything. The situation now is that I stuck in the logo with no recovery mode or bootloader mode. just download mode. S ON, RELOCKED, Software Modified.
I need your help.
Click to expand...
Click to collapse
Sorry, can't help you much in this matter! I won't do it for the money anyway.
You could maybe re-flash a stock ROM since you have access to download mode with fastboot flash zip command. Ask a more experienced user!
adryyandc said:
Sorry, can't help you much in this matter! I won't do it for the money anyway.
You could maybe re-flash a stock ROM since you have access to download mode with fastboot flash zip command. Ask a more experienced user!
Click to expand...
Click to collapse
I tried many stock flashes but doesn't work. I don't know the stock flash of my phone. I couldn't reach fastboot. SD card is my only way
I delete my recovery and cant insatall a new recovery :/
Code:
C:\Users\xxx\Desktop\adb>fastboot flash recovery 3.35.617.12_recovery.img
target reported max download size of 800000000 bytes
sending 'recovery' (20716 KB)...
OKAY [ 2.106s]
writing 'recovery'...
(bootloader) HOSD CL#576582
FAILED (remote: 9: SD_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCK)
finished. total time: 3.128s
RUU back to stock ??
Your bootloader is locked...causing the failure...
Tick "allow bootloader unlock" in developer settings.
On your pc go to htcdev website and get your unlock token and push it via fastboot to your device. Then you can flash twrp, make a system backup!!!!! and flash supersu for root.
Beware, you lose ota ability. This is why you MUST make a backup with twrp BEFORE flashing supersu.
There is only one working supersu so choose wisely.
Sent from my HTC One M9 using Tapatalk
I wiped my device and flashed the latest factory image. I am now trying to install TWRP but fastboot returns the following:
Code:
./fastboot flash recovery ./twrp.img
Sending 'recovery' (65536 KB) OKAY [ 1.860s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
The bootloader is unlocked, and I have tried relocking and unlocking it to no effect.
pismosi said:
I wiped my device and flashed the latest factory image. I am now trying to install TWRP but fastboot returns the following:
Code:
./fastboot flash recovery ./twrp.img
Sending 'recovery' (65536 KB) OKAY [ 1.860s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
The bootloader is unlocked, and I have tried relocking and unlocking it to no effect.
Click to expand...
Click to collapse
twrp doesn't work for android 10. please be specific about versions of android and twrp you are using
pismosi said:
I wiped my device and flashed the latest factory image. I am now trying to install TWRP but fastboot returns the following:
Code:
./fastboot flash recovery ./twrp.img
Sending 'recovery' (65536 KB) OKAY [ 1.860s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
The bootloader is unlocked, and I have tried relocking and unlocking it to no effect.
Click to expand...
Click to collapse
As already noted, TWRP has never worked with 10. If you are on 9 then head over to the dedicated TWRP thread and get yourself up to speed.
if on android 9 it would be fastboot boot twrp. img. (if on Pie)
A/B slot devices don't have a dedicated recovery partition. (reason why flashing to recovery didn't work)
Android 10 doesn't have working TWRP yet. ( can't decrypt data or something)