Develop Bugs

[Q] HTC ONE V sim unlock

Is there a way to sim unlock my htc one v?
I've unlocked the bootloader, rooted the device, put it on s-off, installed CyanogenMod Android 4.1.2, kernel version 3.0.16-HELLBOY; i flashed the kernel and rom; i tried to upgrade the ruu but it returned me the error 131 which reffered to some incompatibility ruu, even tho it was the most appropiate one.
another thing i tried was to hack into the mmcblk0p6 and take the un_lock_code but the unlock.sh returned me this error:
[email protected]:/ # IMEI:
[email protected]:/ # UN_Lock_code:
[email protected]:/ # /system/unlock.sh[34]: + + : unexpected 'end of expression'
my radio is 3831.19.00.120. The network is locked on O2, UK. I've tried a lot of things, but nothing worked.
Can you help me guys?
Thanks in advance!

XTZY23 said:
Is there a way to sim unlock my htc one v?
I've unlocked the bootloader, rooted the device, put it on s-off, installed CyanogenMod Android 4.1.2, kernel version 3.0.16-HELLBOY; i flashed the kernel and rom; i tried to upgrade the ruu but it returned me the error 131 which reffered to some incompatibility ruu, even tho it was the most appropiate one.
another thing i tried was to hack into the mmcblk0p6 and take the un_lock_code but the unlock.sh returned me this error:
[email protected]:/ # IMEI:
[email protected]droid:/ # UN_Lock_code:
[email protected]:/ # /system/unlock.sh[34]: + + : unexpected 'end of expression'
my radio is 3831.19.00.120. The network is locked on O2, UK. I've tried a lot of things, but nothing worked.
Can you help me guys?
Thanks in advance!
Click to expand...
Click to collapse
That depends on what fastboot commands your hboot supports. If you have an eng hboot you can remove simlock with fastboot. But I cannot remember the command off hand. Connect up to the pc in fastboot mode and issue the.command fastboot oem h and it will output all the options available. Post them here for us all to learn from please
Sent from my HTC Desire S using Tapatalk

htc one v_commands
heavy_metal_man said:
That depends on what fastboot commands your hboot supports. If you have an eng hboot you can remove simlock with fastboot. But I cannot remember the command off hand. Connect up to the pc in fastboot mode and issue the.command fastboot oem h and it will output all the options available. Post them here for us all to learn from please
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
this is what it returned:
C:\Fastboot>fastboot oem h
...
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) checkKeycardID
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) erase_phone_storage
(bootloader) gotohboot
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readmeid
(bootloader) lock
(bootloader) writesecureflag
(bootloader) readsecureflag
(bootloader) readsimlocktype
(bootloader) clearsimlocktype
(bootloader) readcid
(bootloader) writecid
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) read_sandisk_fw
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Fastboot>

XTZY23 said:
(bootloader) readsimlocktype
(bootloader) clearsimlocktype
(bootloader) readcid
(bootloader) writecid
Click to expand...
Click to collapse
I would use these 2 sets here. First make a nandroid backup, just incase
Then issue these fastboot commands one after another and copy the results.
Fastboot oem readcid
Fastboot oem readsimlocktype
All good? Now first we want to change your cid to super. So issue this command
Fastboot oem writecid 11111111
Fastboot reboot bootloader
Fastboot oem readcid
Your cid should now show up as 11111111, that's 8 1's
All good? Lastly we issue these commands.
Fastboot oem clearsimlocktype
Fastboot reboot
Now just check your simcard and all should be well you can now flash any ruu for any carrier without issue, but always check its compatible with your model type first!
Sent from my HTC Desire S using Tapatalk

fisrt step:
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: O2___001
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Fastboot>fastboot oem readsimlock
type
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
(bootloader) readsimlocktype: SimLockType: 0
OKAY [ 21.759s]
finished. total time: 21.760s
step 2:
C:\Fastboot>fastboot oem writecid 11
111111
...
(bootloader) AMSS is ready
(bootloader) buf_addr:4FC300,buf_size:200,start_sector:1739D
(bootloader) sdcc_init_memory_device done
(bootloader) Finish write sector address 1739D ...
(bootloader) writecid: successfully
OKAY [ 0.691s]
finished. total time: 0.692s
C:Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.151s]
finished. total time: 0.153s
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Fastboot>fastboot oem clearsimloc
ktype
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
OKAY [ 21.758s]
finished. total time: 21.760s
C:\Fastboot>fastboot reboot
rebooting...
finished. total time: 0.155s
C:\Fastboot>

XTZY23 said:
fisrt step:
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: O2___001
OKAY [ 0.003s]
finished. total time: 0.004s
C:\Fastboot>fastboot oem readsimlock
type
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
(bootloader) readsimlocktype: SimLockType: 0
OKAY [ 21.759s]
finished. total time: 21.760s
step 2:
C:\Fastboot>fastboot oem writecid 11
111111
...
(bootloader) AMSS is ready
(bootloader) buf_addr:4FC300,buf_size:200,start_sector:1739D
(bootloader) sdcc_init_memory_device done
(bootloader) Finish write sector address 1739D ...
(bootloader) writecid: successfully
OKAY [ 0.691s]
finished. total time: 0.692s
C:Fastboot>fastboot reboot-bootload
er
rebooting into bootloader...
OKAY [ 0.151s]
finished. total time: 0.153s
C:\Fastboot>fastboot oem readcid
...
(bootloader) cid: 11111111
OKAY [ 0.004s]
finished. total time: 0.005s
C:\Fastboot>fastboot oem clearsimloc
ktype
...
(bootloader) sdcc_init_memory_device done
(bootloader) Wait for AMSS ready
(bootloader) AMSS is ready
OKAY [ 21.758s]
finished. total time: 21.760s
C:\Fastboot>fastboot reboot
rebooting...
finished. total time: 0.155s
C:\Fastboot>
Click to expand...
Click to collapse
Did it simunlock OK?
Sent from my Nexus 7 using Tapatalk

Hmm, maybe yes maybe not
It passed the sim network locked screen, but now it says "no network available" and when im making a call, it says "mobile network unavailable" \
I REINSTALLED THE RUU i was trying to install it in the first place and it worked. so thanks for your help
PS: the new challenge is this error: mobile network unavailable because it is disconnected
************update***************
1.last night i put s-on on my phone...but
2.even on s-off i could not unlock the bootloader after installing the RUU_PRIMO_U_ICS_40A_HTC_Europe_2.22.401.1_Radio_20.76.30.0835U_3831.19.00.120_release_273801_signed
3. no bootloader unlock->no root->no s-off->no simlock
4. the message header is ****Relocked**** and the error the i receive when i try to unlock the bootloader again is:
C:\Fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.640s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.650s
***********fixed this one*************
HTC ONE toolkit 2.0-Squabbi-- saved me fro a lot o work! great thanks to squabbi!

XTZY23 said:
It passed the sim network locked screen, but now it says "no network available" and when im making a call, it says "mobile network unavailable" \
I REINSTALLED THE RUU i was trying to install it in the first place and it worked. so thanks for your help
PS: the new challenge is this error: mobile network unavailable because it is disconnected
Click to expand...
Click to collapse
http://www.sieempi.eu/blog/2011/09/22/universal-sim-unlock-for-s-offed-htc-devices-536 ok give this a bash pal. will hopefully fix the issue.

GSM problem/hardware problem
thanks heavy_metal_man for replies!
the config.dat file worked, partially i think, returning only one error: Open Cid file failed.
as i could see my phone does not react to find any mobile network available, even tho my phone is "reading" the simcard now. i can see contacts, messages, etc.
ps: i don't have the back cover. would that be the problem?

XTZY23 said:
thanks heavy_metal_man for replies!
the config.dat file worked, partially i think, returning only one error: Open Cid file failed.
as i could see my phone does not react to find any mobile network available, even tho my phone is "reading" the simcard now. i can see contacts, messages, etc.
ps: i don't have the back cover. would that be the problem?
Click to expand...
Click to collapse
The back cover for these kinds of phones usually have "antenna boosting" pads. My htc sensation gets no signal without the back cover on.
For anyone else I would recommend trying the linked website solution from sieempi before fastboot commands
Sent from my Nexus 7 using Tapatalk

[Q] HTC ONE X Hang after Update

ENDEAVORU XE SHIP S-OFF RL
CID-11111111
HBOOT-1.12.0000
CPLD-None
MICROP-None
RADIO-2.1204.135.20
eMMC- bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
June 28 2012, 11:31:28
Hi guys can somebody help me.. please
my phone stuck at HTC ONE logo
how can i fix this isssue...
after updating through internet it keeps on reboot again and again
i dont know how to fix this..
please help me.. tnx

chingkit09 said:
ENDEAVORU XE SHIP S-OFF RL
CID-11111111
HBOOT-1.12.0000
CPLD-None
MICROP-None
RADIO-2.1204.135.20
eMMC- bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM PATH: OFF
June 28 2012, 11:31:28
Hi guys can somebody help me.. please
my phone stuck at HTC ONE logo
how can i fix this isssue...
after updating through internet it keeps on reboot again and again
i dont know how to fix this..
please help me.. tnx
Click to expand...
Click to collapse
Search in the thread have many answare for ENDEAVORU XE it is different from ENDEAVORU PVT try to flash the higher firmware.zip manually

Hi
how can i fix this.. i dont know where i download..
im so stress in this problem.
please someone guide me how to fix this issue.
please please please

chingkit09 said:
how can i fix this.. i dont know where i download..
im so stress in this problem.
please someone guide me how to fix this issue.
please please please
Click to expand...
Click to collapse
ok download latest OTA 4.18,401,4 forom HERE
after read this
How to flash?
(bootloader needs to be relocked)
Re-lock your bootloader (this will most probably wipe content of your device)
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)
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.

chingkit09 said:
how can i fix this.. i dont know where i download..
im so stress in this problem.
please someone guide me how to fix this issue.
please please please
Click to expand...
Click to collapse
after this..
the correct installing of custom rom is.
to unlock and to flash the recovery CWM 5.8.4.0
den install the rom. One_X_4.18.401.3_odexed
is this correct?
can u guide me.. please..
thank you thant

Thant said:
ok download latest OTA 4.18,401,4 forom HERE
after read this
How to flash?
(bootloader needs to be relocked)
Re-lock your bootloader (this will most probably wipe content of your device)
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)
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.
Click to expand...
Click to collapse
after this..
the correct installing of custom rom is.
to unlock and to flash the recovery CWM 5.8.4.0
den install the rom. One_X_4.18.401.3_odexed
is this correct?
can u guide me.. please..
thank you thant
sorry for the wrong quote.

after the command i did
C:\fastboot>fastboot flash zip Firmware.zip
sending 'zip' (12377 KB)... OKAY [ 1.779s]
writing 'zip'... INFOCan not find [android-info.txt] in zipped
image!
FAILED (remote: 24 parsing android-info fail)
finished. total time: 5.417s
C:\fastboot>fastboot flash zip Firmware.zip
sending 'zip' (12377 KB)... FAILED (remote: (00030003))
finished. total time: 0.001s
what will i do?
please help me fix this.. huhuhuhu

chingkit09 said:
after the command i did
C:\fastboot>fastboot flash zip Firmware.zip
sending 'zip' (12377 KB)... OKAY [ 1.779s]
writing 'zip'... INFOCan not find [android-info.txt] in zipped
image!
FAILED (remote: 24 parsing android-info fail)
finished. total time: 5.417s
C:\fastboot>fastboot flash zip Firmware.zip
sending 'zip' (12377 KB)... FAILED (remote: (00030003))
finished. total time: 0.001s
what will i do?
please help me fix this.. huhuhuhu
Click to expand...
Click to collapse
Your bootloader must be locked or relocket from this where I see I think it is not= And what happen when you run Fastboot oem rebootRUU the command must be exactly like I write with smal and Capital letters and you must to see black screen with HTC logo and after second flash you will see green line goes up

Thant said:
Your bootloader must be locked or relocket from this where I see I think it is not= And what happen when you run Fastboot oem rebootRUU the command must be exactly like I write with smal and Capital letters and you must to see black screen with HTC logo and after second flash you will see green line goes up
Click to expand...
Click to collapse
C:\fastboot>fastboot getvar all
INFOversion: 0.5a
INFOversion-bootloader: 1.12.0000
INFOversion-baseband: 2.1204.135.20
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.17.707.3
INFOserialno: SH27GW101562
INFOimei: 353426058935339
INFOproduct: endeavoru
INFOplatform: HBOOT-T30S
INFOmodelid: PJ461****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3778mV
INFOdevpower: 33
INFOpartition-layout: None
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: None
INFOhbootpreupdate: 2
INFOgencheckpt: 0
all: Done!
finished. total time: 0.858s
C:\fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.178s
C:\fastboot>fastboot oem lock
... INFODevice was already locked!
OKAY [ 0.017s]
finished. total time: 0.018s
C:\fastboot>fastboot oem lock
... INFODevice was already locked!
OKAY [ 0.018s]
finished. total time: 0.019s
C:\fastboot>fastboot oem rebootRUU
... INFOSave data from original MSC...
INFOSave data from SIF...
INFOUpdate partition data to SIF partition
INFOUpdate partition data from original MSC...
INFO[MSG] OKAY
OKAY [ 0.229s]
finished. total time: 0.230s
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (12377 KB)... OKAY [ 1.786s]
writing 'zip'... INFOCan not find [android-info.txt] in zipped
image!
FAILED (remote: 24 parsing android-info fail)
finished. total time: 5.426s
look this thant..
it is already relocked
huhuhu help me

chingkit09 said:
C:\fastboot>fastboot getvar all
INFOversion: 0.5a
INFOversion-bootloader: 1.12.0000
INFOversion-baseband: 2.1204.135.20
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.17.707.3
INFOserialno: SH27GW101562
INFOimei: 353426058935339
INFOproduct: endeavoru
INFOplatform: HBOOT-T30S
INFOmodelid: PJ461****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3778mV
INFOdevpower: 33
INFOpartition-layout: None
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: None
INFOhbootpreupdate: 2
INFOgencheckpt: 0
all: Done!
finished. total time: 0.858s
C:\fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.178s
C:\fastboot>fastboot oem lock
... INFODevice was already locked!
OKAY [ 0.017s]
finished. total time: 0.018s
C:\fastboot>fastboot oem lock
... INFODevice was already locked!
OKAY [ 0.018s]
finished. total time: 0.019s
C:\fastboot>fastboot oem rebootRUU
... INFOSave data from original MSC...
INFOSave data from SIF...
INFOUpdate partition data to SIF partition
INFOUpdate partition data from original MSC...
INFO[MSG] OKAY
OKAY [ 0.229s]
finished. total time: 0.230s
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (12377 KB)... OKAY [ 1.786s]
writing 'zip'... INFOCan not find [android-info.txt] in zipped
image!
FAILED (remote: 24 parsing android-info fail)
finished. total time: 5.426s
look this thant..
it is already relocked
huhuhu help me
Click to expand...
Click to collapse
are you take the firmware.zip inside the ota archive? or you trying to flash renamed ota to firmware.zip?
or just download this RUU and run as administrator

Thant said:
Your bootloader must be locked or relocket from this where I see I think it is not= And what happen when you run Fastboot oem rebootRUU the command must be exactly like I write with smal and Capital letters and you must to see black screen with HTC logo and after second flash you will see green line goes up
Click to expand...
Click to collapse
Thant said:
are you take the firmware.zip inside the ota archive? or you trying to flash renamed ota to firmware.zip?
or just download this RUU and run as administrator
Click to expand...
Click to collapse
C:\fastboot>fastboot getvar all
INFOversion: 0.5a
INFOversion-bootloader: 1.12.0000
INFOversion-baseband: 2.1204.135.20
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.17.707.3
INFOserialno: SH27GW101562
INFOimei: 353426058935339
INFOproduct: endeavoru
INFOplatform: HBOOT-T30S
INFOmodelid: PJ461****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3742mV
INFOdevpower: 21
INFOpartition-layout: None
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: None
INFOhbootpreupdate: 2
INFOgencheckpt: 0
all: Done!
finished. total time: 0.824s
C:\fastboot>fastboot oem lock
... INFODevice was already locked!
OKAY [ 0.022s]
finished. total time: 0.023s
C:\fastboot>fastboot oem rebootRUU
... INFOSave data from original MSC...
INFOSave data from SIF...
INFOUpdate partition data to SIF partition
INFOUpdate partition data from original MSC...
INFO[MSG] OKAY
OKAY [ 0.227s]
finished. total time: 0.228s
C:\fastboot>fastboot flash zip firmware.zip
sending 'zip' (11685 KB)... OKAY [ 1.688s]
writing 'zip'... INFOshift signature_size for header checking.
.
INFOchecking model ID...
INFOchecking custom ID...
INFOstart image[boot] unzipping & flushing...
INFOFormat partition LNX done
INFO[RUU]WP,boot,100
INFOstart image[recovery] unzipping & flushing...
INFOFormat partition SOS done
INFO[RUU]WP,recovery,100
INFOERASE backup cid
OKAY [ 2.678s]
finished. total time: 4.367s
yehey its all ready done
what is the next step on this?
please help me thant please..
waiting for your reply

thant..
how can i install the custom rom
the phone is still stockon HTC one
thant teach me how to fix this please... huhuhuhu

chingkit09 said:
thant..
how can i install the custom rom
the phone is still stockon HTC one
thant teach me how to fix this please... huhuhuhu
Click to expand...
Click to collapse
Now go to htcdev.com and unlock your bootloader after this flash Philz recovery 15.5.9 and mount sd card copy rom sense or AOSP to sd card and flash the boot.img from rom.zip to the phone go in recovery and install rom.zip. If you want to install CM11 you need latest Philz recovery or Latest CWM from CM11 thread. but ont this two recoverys Mount sd card not working first flash Philz 5.15.9 and then copy the rom to the sd card and then if you want to install CM11 flash Philz latest or CWM latest and flash CM11
THIS is latest Philz for One X
THIS is philz 5.15.9
For philz recovery take recovery.img inside from archive
And one more Question now your HBOOT must be 1.72 RIGHT?

Thant said:
Now go to htcdev.com and unlock your bootloader after this flash Philz recovery 15.5.9 and mount sd card copy rom sense or AOSP to sd card and flash the boot.img from rom.zip to the phone go in recovery and install rom.zip. If you want to install CM11 you need latest Philz recovery or Latest CWM from CM11 thread. but ont this two recoverys Mount sd card not working first flash Philz 5.15.9 and then copy the rom to the sd card and then if you want to install CM11 flash Philz latest or CWM latest and flash CM11
THIS is latest Philz for One X
THIS is philz 5.15.9
For philz recovery take recovery.img inside from archive
And one more Question now your HBOOT must be 1.72 RIGHT?
Click to expand...
Click to collapse
where i can find the rom.. huhuhu
thant can i chat you? for fast communication please... huhuhu
my head is going to blow..

chingkit09 said:
where i can find the rom.. huhuhu
thant can i chat you? for fast communication please... huhuhu
my head is going to blow..
Click to expand...
Click to collapse
ROM HERE or HERE the first link is close to stock on second most AOSP and AICP roms and hard modyfied sense roms
But first unlock bootloader and flash philz recovery go in recovery and charge your phone to full
waithing to charge your phone you will check wich ROM you want and download and install it you will see bugs and other think

thant im dead
i dont know what to do.. huhuhu please
can i chat you in yahoo?
please help me.. i dont know what to do.
im so stress and i didn't eat my breakfast,lunch
please help my please..
im so lose
i dont know what to do..
or can we chat on fb? please.

chingkit09 said:
thant im dead
i dont know what to do.. huhuhu please
can i chat you in yahoo?
please help me.. i dont know what to do.
im so stress and i didn't eat my breakfast,lunch
please help my please..
im so lose
i dont know what to do..
or can we chat on fb? please.
Click to expand...
Click to collapse
OK are you unlocked your bootloader via htcdev.com go to the site and take your Unlock_code.bin choice all other supported model on the button unlock bootloader after this fallow the instruction in the site after unlock your bootloader, download philz recovery 5.15.9 take recovery.img from the archive and use this comand to flash it fastboot flash recovery recovery.img after this run fastboot erase cache go in recovery and charge your phone
And one more think I write you on the private I dont use yahoo or facebook and I think you not reading what I write you I must to say something 5 times and after this you will do it. Like @Mr Hofs say READING IS GIFT
Yes you are still on the 1.12 becouse you didnt flash the firmware.zip twice like I write on the 2-3 post up I see your command but I see you runt fastboot flash zip firmware.zip only ane time.

the HBOOT still 1.12.0000
how will i change this? huhuhuhu
super lose..

Thant said:
OK are you unlocked your bootloader via htcdev.com go to the site and take your Unlock_code.bin choice all other supported model on the button unlock bootloader after this fallow the instruction in the site after unlock your bootloader, download philz recovery 5.15.9 take recovery.img from the archive and use this comand to flash it fastboot flash recovery recovery.img after this run fastboot erase cache go in recovery and charge your phone
And one more think I write you on the private I dont use yahoo or facebook and I think you not reading what I write you I must to say something 5 times and after this you will do it. Like @MrHofs say READING IS GIFT
Click to expand...
Click to collapse
already done thant.
now i am in the philZ Touch 5
and the cord is connected how to charger the phone?

And one more think I write you on the private I dont use yahoo or facebook and I think you not reading what I write you I must to say something 5 times and after this you will do it. Like @MrHofs say READING IS GIFT
sorry thant..
how to Like @MrHofs say READING IS GIFT
sorry i dont know

Can't Flash TWRP "Signature Verify Fail"

This is an ATT version phone I rooted this phone a couple of days ago with TWRP. However, I had to use adb to enter fastboot as it would not go to fastboot using power/volume keys. Actually, it never shows a fastboot screen, even in adb, so it may have been going into fastboot all along and I just could not see it.
So, instead of leaving well enough alone, I RUU'ed (newest ATT version from HTC site) it to try to get fastboot to work normally (it still works, I just can't see it on screen). Now, I can't get rooted again. FWIW, I did make a backup with TWRP before RUU'ed. Regardless, there is nothing on this phone I need to keep, I just want to root it before I start using it.
Any help is greatly appreciated...
Here is my unlock sequence. Note what happens if I try to flash TWRP immediately after unlock. I have to CTRL C and Reboot phone.
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash unlockt
oken unlock_code.bin
target reported max download size of 1826414592 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.110s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.012s]
finished. total time: 0.125s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
Now when I try to flash TWRP, I get :
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recover' (20022 KB)...
OKAY [ 1.884s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.611s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.28.502.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 7f8e91a3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
HT445####### fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot reboot
rebooting...
finished. total time: 0.013s

Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.

Mr Hofs said:
Fastboot flash recover is wrong, it should be :
Fastboot flash recovery < see the Y there.
Click to expand...
Click to collapse
Same Results:
C:\s>fastboot flash recovery twrpm8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (14818 KB)...
OKAY [ 1.438s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.976s
C:\s>
C:\s>fastboot flash recovery twrp30m8
error: cannot load 'twrp30m8'
C:\s>fastboot flash recovery twrp30m8.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.889s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.616s
C:\s>

Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.

Mr Hofs said:
Bad download then, see how the sizes of the file are different when you flash it again. At least the command is correct now. Re-download the recovery file and try again.
Click to expand...
Click to collapse
Already tried that, but tried again. First below is my result before I downloaded new twrp and the second one is my result after I re-downloaded image
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.896s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>fastboot flash recovery twrp.img
target reported max download size of 1826414592 bytes
sending 'recovery' (20022 KB)...
OKAY [ 1.899s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.625s
C:\s>

Try the HTC_fastboot adb package. It's posted several times here on xda.

Mr Hofs said:
Try the HTC_fastboot adb package. It's posted several times here on xda.
Click to expand...
Click to collapse
Still no luck, same error (see below). This worked flawless before I flashed the latest ATT RUU.
Is it possible phone is still not unlocked or would I be getting that far if it was still locked?
Question. This phone is AT&T (more details in getvar above) but at the end of the contract, AT&T sent me code to unlock the SIM. Now, the SIM I am using is on a T-Mobile MVNO (TING). Since they SIM unlocked the phone, would I be able to and would there be any advantage/risk to trying to flash the Stock RUU for HTC unlocked/developer. It is a higher software version than the ATT version I flashed (twice).
C:\FB>htc_fastboot flash recovery twrp.img
sending 'recovery' (20022 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Execution time is 3(s)

Any other ideas? I can't see bootloader screen, but it appears I can access and do all bootloader functions in adb.
I would really like to be able to eliminate locked bootloader as the issue, is there anything else I can flash or try that might let me know if bootloader is still locked. I can get results from getvar and fastboot devices.
I also have an image of the phone saved from TWRP before I flashed the RUU, but seems no way to get that image back. I am not opposed to purchasing S-off if that will for sure help me.

Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html

joikep said:
Try to flash a lower version of TWRP and see if that helps: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img.html
Click to expand...
Click to collapse
Already tried two previous versions

rockfordpi said:
Already tried two previous versions
Click to expand...
Click to collapse
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?

rockfordpi said:
OK, lets try this a different way. IF one were to try to flash TWRP to M8 AND the bootloader was NOT UNLOCKED, what error message would one get?
Would there still be a response from adb getvar and fastboot devices IF the bootloader were locked?
Trying to eliminate potential issues one at a time
Is there a more appropriate forum for me to post the question?
Click to expand...
Click to collapse
OK, we can close this one out. I did want to post my solution, just in case anyone else had a similar error.
Long Story a little bit shorter, on my HTC one M8, the error:
sending 'recovery' (11976 KB)... OKAY
writing 'recovery'... (bootloader) signature checking...
FAILsignature verify fail
FAILED (remote: signature verify fail)
Was due to a locked bootloader. Because, for some reason I can't see the bootloader on my phone, I could not see the lock status, so I was having to do EVERYTHING via ADB. The problem was, when unlocking the bootloader there is screen on the phone that asks you to confirm yes or no if you want to unlock it. I could not see that screen and the instructions I was reading left that out (It was a good assumption that if one was trying to unlock one would know to say YES. LOL). So, I was missing that step. When I found that step, even though I could not see it on screen, I just blindly pushed volume down and then power to select. At that point it unlocked and allowed me to flash twrp 3.0.
Still do not know WHY I can't see the bootloader screen. I wonder if for some reason the colors are off in my bootloader screen and all the words are the same color as the background or it is trying to redirect that output somewhere else.
but at this point I am going to live with it as trying to fix it is what got me in here in the first place.

Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Someone have an idea to help me ?
Many thanks

foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
Click to expand...
Click to collapse
The top post is in regards to getting signature verify fail message when flashing custom recovery. So I don't see how it's the "same problem".
Be careful about saying "same problem" without giving any specific information about your actual problem, or device details. From my experience, I've seen many dozens of times where folks say they have the "same problem" and when prompted for more info, we find there are many many differences.
foosee said:
Hi,
I have the same problem phne always reboot in fastboot menu.
The status is also RELOCKED after fashing stock ROM
RUU_M8_UL_M60_SENSE70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
Click to expand...
Click to collapse
Did the RUU flash successfully, or were there any error messages?
Also, please do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can see more info about the phone.
foosee said:
But I'm not able to user adb : device not found.
Fastboot seems working but not adb
Click to expand...
Click to collapse
This is normal and expected. You can't use adb when in bootloader. And you can't use fastboot and adb simultaneously. Meaning, when one works, the other will not work, by definition.
Fastboot = only works in bootloader fastboot mode
adb = only works within OS, or alternately will work in custom recovery TWRP
If you issue the command fastboot devices, you should find that it works.
It is also not clear what you are trying to use adb to do (what commands?).

Please help my htc 10 is dead

I Tried to flash but always getting error partition failed. Stucked in boot loop. no recovery. only i can get fastboot. below is my getvar.
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA64xxxxxxx
all:
finished. total time: 0.381s
htc_fastboot finished. total time: 0.738s
Press any key to continue . . .

What's your CID and latest ROM version? And what did you try to flash?

Dont know anything here... I dont know what was the ROM version at the time of root... now no information available... what can I do ...

When I try to flash anything via fastboot it says partion not exist
RUU also not working says battery is less than 30% but actually battery is full...

Does charging led turns green..
@Sneakyghost could help

cutecool said:
Does charging led turns green..
@Sneakyghost could help
Click to expand...
Click to collapse
no it doesnt... the battery icon comes up and then boot loop starts again...

Since you're in Qatar, you're probably on the 401 software. Did you get a software update in the last 2-3 weeks?
If not, download this: https://www.androidfilehost.com/?fid=24686681827312455
Relock your bootloader (fastboot oem lock), and flash this RUU (fastboot flash zip "name of zip").
If you got the recent update, then you're likely on 1.95, and you'll have to wait until there's an RUU, or take it to a service center.
This is as much help as I can give. Good luck.

I wouldn't lock the bootloader until you know your device fully boots.

Stephen said:
I wouldn't lock the bootloader until you know your device fully boots.
Click to expand...
Click to collapse
The 401 RUU zip won't flash on unlocked. This has been documented and I have gone through it myself. Do you have any alternate suggestions?
Why wouldn't you lock without a working system? My understanding is that unlocking via HTCdev would still be possible.

I tried dear but its not locking bootloader
here is the message
C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.257s
C:\Android\com>htc_fastboot oem relock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.249s
C:\Android\com>

abidpioneer said:
I Tried to flash but always getting error partition failed. Stucked in boot loop. no recovery. only i can get fastboot. below is my getvar.
(bootloader) version:0.5
(bootloader) ramdump-mode:false
(bootloader) variant:Surf eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0xe000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x61e000000
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xef000000
(bootloader) serialno:FA64xxxxxxx
all:
finished. total time: 0.381s
htc_fastboot finished. total time: 0.738s
Press any key to continue . . .
Click to expand...
Click to collapse
You need to be in download mode then use the getvar all command. All fastboot commands are done in downlaod mode. How are you trying to flash RUU?

I am unable to use download mode..it says download mode failed in red

abidpioneer said:
I am unable to use download mode..it says download mode failed in red
Click to expand...
Click to collapse
You'll need a service center.

Yes. Service center. I don't think it's a brick since there's still a boot process but at this time I also wouldn't know how to force it to flash stuff, since it seems at least one vital partition is broken. So, call it a semi-brick with currently no way out...
Sorry that I can't offer any help here...

abidpioneer said:
I tried dear but its not locking bootloader
here is the message
C:\Android\com>htc_fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.257s
C:\Android\com>htc_fastboot oem relock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
htc_fastboot finished. total time: 0.249s
C:\Android\com>
Click to expand...
Click to collapse
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Sent from my HTC6545LVW using Tapatalk

I will check dear..thanks

dottat said:
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Click to expand...
Click to collapse
What is hosd.. ? Never heard about it...

I tried but its not working... i went to htc service centre they refused to do the job saying its modified they cannot do the job.. WTH is this at htc service centre...

abidpioneer said:
I tried but its not working... i went to htc service centre they refused to do the job saying its modified they cannot do the job.. WTH is this at htc service centre...
Click to expand...
Click to collapse
What happened? Did it flash successfully? Any errors?
Sent from my HTC6545LVW using Tapatalk

dottat said:
Is the correct HTC driver showing in device manager? Are you in white bootloader or download mode?
Your phone is behaving just like one with a mismatched hosd and aboot would. There's a specific way to fix it. That firmware zip you would need to flash aboot and hosd by name/partition. Unzip it and flash using
Htc_fastboot flash hosd hosd.img
Htc_fastboot flash aboot aboot.img
Htc_fastboot reboot-bootloader
Check to see if you have download mode back.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Interesting facts there, mate. Thought you retired. Obviously I'm much more retired than you, considering I never knew HOSD is directly flashable like aboot...
Good to see you around!
(Besides, is it a true story that you retired? People were telling me that...)

Pixel XL bricked, bootloader locked and recovery doesn't work.

Does anyone can help me?
My Pixel XL brick more than a week ago, and I couldn't. I was installing the 8.0.0 official image from the bootloader with fastboot (a "clean install"), apparently there was an error installing the recovery and I didn't realize, so I lock the recovery (with fastboot oem lock and Up Volume key). After that, I restarted the phone and now it doesn't start (it shows only a "Google" splash and it restarts again).
I can't use the recovery mode (to use adb sideload command), try enter to the recovery makes the phone start "bootlooping" too.
I seen another thread explaining my problem, but it has almost a year without activiy (I asked on it to the user if he could solve that this problem but it seems like he doesn't use xda anymore):
https://forum.xda-developers.com/pixel-xl/help/pixel-xl-soft-bricked-unlock-bootloader-t3540772
I live in Uruguay, so I can't RMA.
Summary:
- My phone is bricked.
- I can enter to bootloader, but it's locked.
- I can't enter to recovery mode.
- I can't RMA.
Useful logs:
fastboot getvar all:
Code:
(bootloader) version:0.5
(bootloader) hw-revision:PVT
(bootloader) mid:G-2PW2100
(bootloader) version-main:0.12.999.1
(bootloader) imei:352693081633543
(bootloader) ramdump-mode:false
(bootloader) boot-mode:FASTBOOT
(bootloader) has-slot:radio:yes
(bootloader) has-slot:bootloader:yes
(bootloader) has-slot:reserve5:no
(bootloader) has-slot:devinfo:no
(bootloader) has-slot:fsg:no
(bootloader) has-slot:mfg:no
(bootloader) has-slot:board_info:no
(bootloader) has-slot:reserve4:no
(bootloader) has-slot:metadata:no
(bootloader) has-slot:pg2fs:no
(bootloader) has-slot:pg1fs:no
(bootloader) has-slot:ramdump:no
(bootloader) has-slot:frp:no
(bootloader) has-slot:reserve3:no
(bootloader) has-slot:cdt:no
(bootloader) has-slot:ddr:no
(bootloader) has-slot:modemst2:no
(bootloader) has-slot:modemst1:no
(bootloader) has-slot:fsc:no
(bootloader) has-slot:dip:no
(bootloader) has-slot:dpo:no
(bootloader) has-slot:devinfobak:no
(bootloader) has-slot:sec:no
(bootloader) has-slot:persist:no
(bootloader) has-slot:ssd:no
(bootloader) has-slot:misc:no
(bootloader) has-slot:xbl:yes
(bootloader) has-slot:reserve0:no
(bootloader) has-slot:userdata:no
(bootloader) has-slot:system:yes
(bootloader) has-slot:vendor:yes
(bootloader) has-slot:apdp:yes
(bootloader) has-slot:msadp:yes
(bootloader) has-slot:modem:yes
(bootloader) has-slot:devcfg:yes
(bootloader) has-slot:hosd:yes
(bootloader) has-slot:boot:yes
(bootloader) has-slot:aboot:yes
(bootloader) has-slot:cmnlib64:yes
(bootloader) has-slot:cmnlib32:yes
(bootloader) has-slot:hyp:yes
(bootloader) has-slot:pmic:yes
(bootloader) has-slot:rpm:yes
(bootloader) has-slot:tz:yes
(bootloader) has-slot:keymaster:yes
(bootloader) has-slot:bootlocker:yes
(bootloader) slot-count:2
(bootloader) current-slot:a
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:2
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4240000
(bootloader) variant:US
(bootloader) secure:yes
(bootloader) unlocked:no
(bootloader) version-baseband:8996-012901-1702171013
(bootloader) version-bootloader:8996-012001-1704121145
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x635400000
(bootloader) partition-type:system_b:ext4
(bootloader) partition-size:system_b: 0x80000000
(bootloader) partition-type:system_a:ext4
(bootloader) partition-size:system_a: 0x80000000
(bootloader) partition-type:vendor_b:ext4
(bootloader) partition-size:vendor_b: 0x12c00000
(bootloader) partition-type:vendor_a:ext4
(bootloader) partition-size:vendor_a: 0x12c00000
(bootloader) partition-type:boot_b:raw
(bootloader) partition-size:boot_b: 0x2000000
(bootloader) partition-type:boot_a:raw
(bootloader) partition-size:boot_a: 0x2000000
(bootloader) serialno:HT7370201155
(bootloader) kernel:lk
(bootloader) product:marlin
all:
finished. total time: 2.243s
./flash-all.sh (8.0.0-stock-opr3.170623.007):
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32268 KB)...
OKAY [ 1.076s]
writing 'bootloader_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.175s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.275s
target reported max download size of 536870912 bytes
sending 'radio_a' (57272 KB)...
OKAY [ 1.952s]
writing 'radio_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 2.050s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.150s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
W/ziparchive(10452): Zip: unable to allocate 818872552 bytes at offset 0 : No space left on device
failed to extract 'system_other.img': I/O Error
W/ziparchive(10452): Zip: unable to allocate 263934088 bytes at offset 0 : No space left on device
failed to extract 'vendor.img': I/O Error
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
error: file_write: write: No space left on device
--------------------------------------------
Bootloader Version...: 8996-012001-1704121145
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT7370201155
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
FAILED
Device version-bootloader is '8996-012001-1704121145'.
Update requires '8996-012001-1706221457'.
finished. total time: 0.300s
./flash-all.sh (7.1.2-stock-njh47d):
Code:
target reported max download size of 536870912 bytes
sending 'bootloader_a' (32380 KB)...
OKAY [ 1.088s]
writing 'bootloader_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.187s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.247s
target reported max download size of 536870912 bytes
sending 'radio_a' (57240 KB)...
OKAY [ 1.924s]
writing 'radio_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 2.022s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.250s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
W/ziparchive(10714): Zip: unable to allocate 1721085316 bytes at offset 0 : No space left on device
failed to extract 'system_other.img': I/O Error
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1704121145
Baseband Version.....: 8996-012901-1702171013
Serial Number........: HT7370201155
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.050s]
checking version-baseband...
OKAY [ 0.050s]
sending 'boot_a' (26001 KB)...
OKAY [ 0.951s]
writing 'boot_a'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.401s

zades9 said:
Does anyone can help me?
My Pixel XL brick more than a week ago, and I couldn't. I was installing the 8.0.0 official image from the bootloader with fastboot (a "clean install"), apparently there was an error installing the recovery and I didn't realize, so I lock the recovery (with fastboot oem lock and Up Volume key). After that, I restarted the phone and now it doesn't start (it shows only a "Google" splash and it restarts again).
I can't use the recovery mode (to use adb sideload command), try enter to the recovery makes the phone start "bootlooping" too.
I seen another thread explaining my problem, but it has almost a year without activiy (I asked on it to the user if he could solve that this problem but it seems like he doesn't use xda anymore):
https://forum.xda-developers.com/pixel-xl/help/pixel-xl-soft-bricked-unlock-bootloader-t3540772
I live in Uruguay, so I can't RMA.
Summary:
- My phone is bricked.
- I can enter to bootloader, but it's locked.
- I can't enter to recovery mode.
- I can't RMA.
Click to expand...
Click to collapse
I assume that you have tried fastboot boot with the correct twrp image?

I understand you locked the bootloader, however, maybe the stock images didn't flash correctly to reset the "allow oem unlocking" in the developer options..
If that's the case, try unlocking the bootloader again with "fastboot flashing unlock".

mikefnz said:
I assume that you have tried fastboot boot with the correct twrp image?
Click to expand...
Click to collapse
I get this log:
Code:
[cristian: PixelXL]$ fastboot boot twrp-3.0.2-0-alpha2-fastboot-marlin.img
downloading 'boot.img'...
OKAY [ 0.901s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 1.001s

Pain-N-Panic said:
I understand you locked the bootloader, however, maybe the stock images didn't flash correctly to reset the "allow oem unlocking" in the developer options..
If that's the case, try unlocking the bootloader again with "fastboot flashing unlock".
Click to expand...
Click to collapse
Code:
[cristian: PixelXL]$ fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.043s
[cristian: PixelXL]$ fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s

I have no idea man... hopefully someone a lot more experienced than me comes around with a valid solution.

zades9 said:
Code:
[cristian: PixelXL]$ fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.043s
[cristian: PixelXL]$ fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s
Click to expand...
Click to collapse
I'm no expert but have you tried the Skipsoft Toolkit? https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767
And checked this guide? https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page20

mikefnz said:
I'm no expert but have you tried the Skipsoft Toolkit? https://forum.xda-developers.com/pixel-xl/development/tool-skipsoft-android-toolkit-google-t3482767
And checked this guide? https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478/page20
Click to expand...
Click to collapse
I can't enable Bootloader Unlocking from the developer settings because the device is bricked.

@zades9 I have an idea. Try downloading an OTA image to 8.0 and flashing that from stock recovery if you can access it (twrp might be cool too idk). If it will not let you flash an ota because you're already on 8.... 8.1 is coming out soon lol Is your bootloader messed up somehow? Fastboot flashing unlock_critical unlocks the bootloader but I don't know much about it. Let me rephrase it allows the bootloader to be flashed over.

Yea I'd try:fastboot flashing unlock_critical
Is it possible to switch to the bootloader_b slot and reboot-bootloader... possibly flash the b slot?

comat0se said:
Yea I'd try:fastboot flashing unlock_critical
Is it possible to switch to the bootloader_b slot and reboot-bootloader... possibly flash the b slot?
Click to expand...
Click to collapse
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s

tdct12 said:
@zades9 I have an idea. Try downloading an OTA image to 8.0 and flashing that from stock recovery if you can access it (twrp might be cool too idk). If it will not let you flash an ota because you're already on 8.... 8.1 is coming out soon lol Is your bootloader messed up somehow? Fastboot flashing unlock_critical unlocks the bootloader but I don't know much about it. Let me rephrase it allows the bootloader to be flashed over.
Click to expand...
Click to collapse
For what I know, you can't flash anything if your bootloader is locked.
Code:
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s

I know about 6 months ago in the Nexus 6p forum, someone created a zip that could be flashed in recovery to toggle bootloader unlock in developer settings. It might be worth looking for to see if there's some sort of adb shell script that you could possibly use to toggle that switch. So you didn't boot after flashing factory image before locking? Also be sure to be using the most up to date adb and fastboot tools as that can cause issue too. IDK, I wish you luck!

Bryanx86 said:
I know about 6 months ago in the Nexus 6p forum, someone created a zip that could be flashed in recovery to toggle bootloader unlock in developer settings. It might be worth looking for to see if there's some sort of adb shell script that you could possibly use to toggle that switch. So you didn't boot after flashing factory image before locking? Also be sure to be using the most up to date adb and fastboot tools as that can cause issue too. IDK, I wish you luck!
Click to expand...
Click to collapse
If I could flash something in recovery mode I could flash the stock rom with "adb sideload file.zip", so I would not need unlock bootoader.
And yeah, I didn't boot after locking oem again :/

zades9 said:
For what I know, you can't flash anything if your bootloader is locked.
Code:
[cristian: ~]$ fastboot flashing unlock_critical
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.044s
Click to expand...
Click to collapse
Actually that's not true. You can flash factory ota updates on a locked bootlader from stock recovery, idk about twrp though.

zades9 said:
If I could flash something in recovery mode I could flash the stock rom with "adb sideload file.zip", so I would not need unlock bootoader.
And yeah, I didn't boot after locking oem again :/
Click to expand...
Click to collapse
I wasn't referring to flashing that zip file, but looking inside to see if it's an adb shell script, you have a booting phone with a working bootloader, the recovery is compromised. There has to be a way to get your phone fixed. Only when it's totally dead do you give up hope

Well, while we are grasping at straws, make sure your fastboot is the very latest version. The version I use is marked as
~$ fastboot --version
fastboot version -4022467
I would also give the November image a try.

Crap I bricked mine too! Was on rooted Stock with twrp. Did factory reset (to unroot), then relock bootloader (all done with Skipsoft Toolkit). Thought I'd be in the clear, but now it's just bootlooping a half second Google logo and then black. I can get into the bootloader but nothing else works, not recovery, nothing. Can't flash anything since bootloader is locked now. Tried adb commands like fastboot continue but nothing works... Any updates or ideas on this!?? Device is bricked! I bought mine new on Craigslist so may have some trouble with RMA.... Yikes!

Please let this be a lesson to people to stop locking their bootloader's, or know what the heck they are doing before they do. I'm tired of reading about this across all forums. Whoever is explaining the steps to unlock the bootloader, need to give explicit knowledge on what to do and not do. I honestly wish I could be of more help, but it's a pain to get sorted on devices with regular partitions, so on this device I have no clue. It would be great if you could somehow force it to boot using the alternate slot
To OP, it looks like you're using slot A. Can you try switching to slot B and thing to boot?
fastboot --set-active=_b

dictionary said:
Please let this be a lesson to people to stick locking their bootloader's, or know what the heck they are doing. I'm tired of reading about this across all forums. Whoever is explaining the steps to unlock the bootloader, need to give explicit knowledge on what to do and not do. I honestly wish I could be of more help, but it's a pain to get sorted on devices with regular partitions, so on this device I have no clue. It would be great if you could somehow force it to boot using the alternate slot
To OP, it looks like you're using slot A. Can you try switching to slot B and thing to boot?
fastboot --set-active=_b
Click to expand...
Click to collapse
Code:
C:\Users\cristian>fastboot --set-active=_b
Setting current slot to 'b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.076s
C:\Users\cristian>fastboot --set-active=b
Setting current slot to 'b'...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.292s
I posted my problem on the Pixel User Community, but that thread is dead: https://groups.google.com/a/googlep...forums.com?utm_medium=email&utm_source=footer