Related
This error happens whenever I try to use Fastboot. I don't think it is dependent on the file being flashed, as I have tried a number of recoveries and a few system.img files.
{
"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"
}
How can I fix this? I need a working fastboot to be able to install a ROM and fix my recovery.
Okay, this is solved. I was rooted using the one-click method, but it seems I can't flash anything in fastboot unless my bootloader is unlocked. So I used the command
fastboot oem unlock
Click to expand...
Click to collapse
And now everything works perfectly.
same error is there with my wildfire s..
nothing is working..
it gives error..
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
please help..!!!!
1) You're in the wrong forum.
2) To use fastboot you have to unlock your bootloader with HTCDev tool, and you still won't be able to flash radio/splash/some other partitions.
Jack_R1 said:
1) You're in the wrong forum.
2) To use fastboot you have to unlock your bootloader with HTCDev tool, and you still won't be able to flash radio/splash/some other partitions.
Click to expand...
Click to collapse
i tried unlocking the bootloader.. but after running the RUU, during update something went wrong and a htc logo came up with "!" in all corners..
what do i do now? please help..!!
To unlock the bootloader, you don't need RUU. You should have just used the HTCDev tool.
I don't know what went wrong, soI can't help you. Try looking for help in Wildfire S forum.
Jack_R1 said:
To unlock the bootloader, you don't need RUU. You should have just used the HTCDev tool.
I don't know what went wrong, soI can't help you. Try looking for help in Wildfire S forum.
Click to expand...
Click to collapse
now the things are changed..
the phone booted with the command,
fastboot oem boot
but again when i restart it, its not goin into the bootloader..
Same problem here
sameer.patil291 said:
now the things are changed..
the phone booted with the command,
fastboot oem boot
but again when i restart it, its not goin into the bootloader..
Click to expand...
Click to collapse
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem unlock
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.007s
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem boot
...
(bootloader) [ERR] partition_read::Failed to read page 19840 or it is emp
(bootloader) ty
(bootloader) [ERR] boot image does not exist!!!
FAILED (status read failed (Too many links))
finished. total time: 0.218s
I tried HTCDev and it fail.
Probably Bootloader is gone.
sameer.patil291 said:
same error is there with my wildfire s..
nothing is working..
it gives error..
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
please help..!!!!
Click to expand...
Click to collapse
The Wildfire S needs S-OFF, currently that is not possible on the device because of the advanced security on the bootloader,
Sent from my Nexus One using xda app-developers app
same on my inc s,
since i root install custom rom & need update to ICS so I roll back to stock room
here from my CMD :
C:\android>fastboot flash hboot vivo_downgrade.img
sending 'hboot' (1024 KB)...
OKAY [ 0.421s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.546s
+++++++++++++++++++++++++++++++
C:\android>fastboot flash recovery recovery.img
sending 'recovery' (5386 KB)...
OKAY [ 1.669s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.340s
++++++++++++++++++++++++++++++++++++++
C:\android>fastboot flash boot boot.img
sending 'boot' (3350 KB)...
OKAY [ 1.030s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.451s
++++++++++++++++
need advise and help.
thanks
++++++++++++++++++++++++
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.16.0000
(bootloader) version-baseband: 3805.09.03.27_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.30.707.1
(bootloader) serialno: xxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3794mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d3a3895d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
+++++++++++++++++++++++++++
analog problem
same problem
Is there no solution for this? I have tried everything that I could find on the internet and nothing seems to work. I consistantly get the FAILED <remote: signature verify fail>
And this is what I get when I tried the fastboot oem boot. Getting really frustrated. At the end of my string. Does anyone have any ideas?
... INFOBoot/Recovery signature che
INFOBoot/Recovery signature checking...
INFOsetup_tag addr=0x80400100 cmdline add=0xC02F4554
INFOTAG:Ramdisk OK
INFOTAG:skuid 0x2ED01
INFOTAG:hero panel = 0x2940043
INFOTAG:engineerid = 0x0
INFOTAG: PS ID = 0x0
INFOTAG: Gyro ID = 0x0
INFODevice CID is not super CID
INFOCID is ROGER001
INFOsetting->cid::ROGER001
INFOserial number: HT265W405171
INFOcommandline from head: console=ttyHSL0,115200,n8
INFOcommand line length =718
INFOactive commandline: poweron_status=1 reset_status=0 board_vi
INFOlle.disable_uart3=0 diag.enabled=0 board_ville.debug_uart=0
INFOuserdata_sel=0 androidboot.emmc=true androidboot.pagesize=20
INFO48 skuid=0 ddt=20 ats=0 androidboot.lb=1 td.td=1 td.sf=1 td
INFfs=328 td.prd=1 td.dly=0 td.tmo=300 imc_online_log=0 andr
INFOoidboot.efuse_info=NFSL androidboot.baseband=0.17.31501S.10_
INFO2 androidboot.cid=ROGER001 androidboot.devicerev=3 androidbo
INFOot.batt_poweron=good_battery androidboot.carrier=Rogers andr
INFOoidboot.mid=PJ4011000 androidboot.keycaps=qwerty androidboot
INFO.dq=FAIL androidboot.mode=normal androidboot.serialno=HT265W
INFO405171 androidboot.bootloader=1.13.0000 androidboot.nledhw=0
INFO zygote_oneshot=off kmemleak=off rpm_debug.enable=0 console=
INFOttyHSL0,115200,n8
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=local
INFOaARM_Partion[5].name=cache
INFOaARM_Partion[6].name=userdata
INFOaARM_Partion[7].name=devlog
INFOaARM_Partion[8].name=pdata
INFOaARM_Partion[9].name=fat
INFOaARM_Partion[A].name=extra
INFOaARM_Partion.name=radio
INFOaARM_Partion[C].name=adsp
INFOaARM_Partion[D].name=dsps
INFOaARM_Partion[E].name=wcnss
INFOaARM_Partion[F].name=radio_config
INFOaARM_Partion[10].name=modem_st1
INFOaARM_Partion[11].name=modem_st2
INFOpartition number=18
INFOValid partition num=18
INFOTZ_HTC_SVC_SET_DDR_MPU ret = 0
INFOsmem 90006000 (phy 90006000): TZ_HTC_SVC_UPDATE_SMEM ret = 0
INFOTZ_HTC_SVC_LOG_OPERATOR ret = 0
INFOTZ_HTC_SVC_ENC ret = 0
INFOTZ_HTC_SVC_DISABLE ret = 474079232 (0x1C41E000)
INFOjump_to_kernel: machine_id(3751), tags_addr(0x80400100), ker
INFOnel_addr(0x80408000)
INFO-------------------hboot boot time:198169 msec
FAILED (status read failed (Too many links))
finished. total time: 6.947s
I have a verizon inc 2, unlocked and I want to update the radio. I noticed
2) To use fastboot you have to unlock your bootloader with HTCDev tool, and you still won't be able to flash radio/splash/some other partitions.
Click to expand...
Click to collapse
and have tried putting it on the SD Card and running it thru the bootloader, but it just sits there. the only reason I even want the radio updated was because I saw that I *might* be able to access the 4G signal and use it. otherwise, I would just like to get a ROM of any kind, even stock, working on my phone
I was having this same issue. Can I install TWRP with the bootloader locked?
Jack_R1 said:
1) You're in the wrong forum.
2) To use fastboot you have to unlock your bootloader with HTCDev tool, and you still won't be able to flash radio/splash/some other partitions.
Click to expand...
Click to collapse
I have the same issue in the original thread with my bootloader. ATT HTC one mini I seem to get signature fail When I try flashing a recovery and "connection error" with the RUU. My bootloader is locked Ive tried the RUU with different cables and different ports on my laptop. No luck. SIM Lock says "SD init fail." but the RUU detects the OS version ## ADB detects a device but the RUU wont. PLease help
yumcax said:
Okay, this is solved. I was rooted using the one-click method, but it seems I can't flash anything in fastboot unless my bootloader is unlocked. So I used the command
And now everything works perfectly.
Click to expand...
Click to collapse
With SDK?
https://postimage.org/
i neeed help
i got the same problem after flashing ruu file to my htc evo view 4g tab
(bootloader) [ERR] Command error !!!
OKAY [ 0.005s]
finished. total time: 0.007s
pleeease help
Problem with bootloader
Hello to ALL.
I can not LOCK my bootloader (unlocked by another person).
When tried to fastboot oem lock - always got FAILED.
c:\Android>fastboot oem lock
... INFOLock failed!
FAILED (status read failed (No such file or directory))
HTC 609d (UNLOCKED)
HBOOT-1.03.0001
RADIO-1.02.10.0917
OS-
eMMC-boot
Oct 18 2013,22:38:27.0
By the way, can not flash any files (boot \ recovery or system):
c:\Android>fastboot flash recovery recovery.img
sending 'recovery' (6910 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)
c:\Android>fastboot flash boot boot.img
sending 'boot' (4508 KB)... OKAY
writing 'boot'... FAILED (remote: image update error)
deatails of getvar:
c:\Android>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.03.0001
INFOversion-baseband: 1.02.10.0917
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno: HC3CTMR02037
INFOimei: 355195000000017
INFOmeid:
INFOproduct: cp3dcg
INFOplatform: HBOOT-8x25Q
INFOmodelid: PO4710000
INFOcidnum: HTCCN702
INFObattery-status: good
INFObattery-voltage: 3840mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-a87dbd86
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
Thanks in advance for you assistance.
HTC D516d
Hello to ALL!
When i put (adb \ bootloader) a command "getvar all" fastboot don`t reply me with PHONE INFORMATION:
c:\Android>fastboot getvar all
all:
finished. total time: 0.003s
Now installed ROM from HTC Desire 516 Dual Sim, but seeking for original for my device STOCK - HTC D516d.
Thanks in advance.
The initial situation:
For OS only a dash appears.
The boot loader is unlocked hboot is 1.54.0000, S-ON device is RH
On the device ViperOne running 3.5.0 (4.3)
Now to the problem:
Flashing a recovery is performed, also displayed as OK, but it remains the old (TWRP 2.6.3.3)
Bootloader not lock possible:
(bootloader) Lock successfully ...
(boot loader) mipi display off
(boot loader) mipi_dsi_cmds_tx_ext
(boot loader) pm8921_vreg_disable function, vreg_id = 38
(boot loader) pm8921_vreg_disable function, vreg_id = 1
(boot loader) TZ_HTC_SVC_DISABLE ret = 534 642 044 (0x1FDDFD7C)
(boot loader) Use PSHOLD to reset device.
FAILED (status read failed (Too many links))
finished. total time: 1.139s
Flashing via sideload possible, unfortunately, according to Rome, it passes through or terminates. After the restart, but is ancient Rome it.
Getvar all the following shows:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3893mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Read access possible via fastboot, ADB, token.
What is not possible to change anything on the device.
What are my options, I can do?
If information still needed, just ask.
Thank you
Fooox1 said:
The initial situation:
For OS only a dash appears.
The boot loader is unlocked hboot is 1.54.0000, S-ON device is RH
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
Read access possible via fastboot, ADB, token.
What is not possible to change anything on the device.
What are my options, I can do?
If information still needed, just ask.
Thank you
Click to expand...
Click to collapse
So if I understand correctly, you don't like the fact that firmware version not showing up; so I guess you have a couple of options:
1- (recommended in my opinion) get s-off using rumrunner
2- download this OTA: http://www.htc1guru.com/dld/ota_m7_..._p_release_325133_signedlqk8p6c09r7kmir2-zip/
and extract the "firmware.zip" inside, then flash that in fastboot ruu mode (TWICE in a row)
(you may need to relock bootloader for that)
Thanks for the reply, but unfortunately brings me no further.
1 Runrummer not running my knowledge with 4.3. I have also tried, without success.
2 That's my problem, I can not close the boot loader.
Fooox1 said:
Thanks for the reply, but unfortunately brings me no further.
1 Runrummer not running my knowledge with 4.3. I have also tried, without success.
2 That's my problem, I can not close the boot loader.
Click to expand...
Click to collapse
rumrunner should work just fine, but you're not on 4.3 (firmware); you're hboot 1.54 would imply that you are running a 2.24 firmware, so you need a ROOTED 2.24 ROM with unsecured kernel; try this one: oops, looks like mega is down at the moment
find a 2.24 based ROM, rooted, with unsecured kernel, and rumrunner should work fine. maybe try Maximus 10 or 11: http://llabtoofer.com/category/devices/htc-one/page/2/
However, it is to 4.3 (see photo)
My problem is that the unit will not start a new Rome. Even if the flash goes through, is the old when you start it again. The same happens if I flash a different recovery. What I put on it when the one hanging on the PC is turned on, after the boot gone into recovery.
Fooox1 said:
However, it is to 4.3 (see photo)
My problem is that the unit will not start a new Rome. Even if the flash goes through, is the old when you start it again. The same happens if I flash a different recovery. What I put on it when the one hanging on the PC is turned on, after the boot gone into recovery.
Click to expand...
Click to collapse
1- I understand your current ROM is 4.3, but that has nothing to do with firmware; firmware is <empty>, but hboot is 1.54, so it implies a 2.24 ROM.
2- to get rumrunner to work, you will need a 2.24 RUM
3- can you please boot to bootloader screen and make sure it says UNLOCKED (a screenshot would be nice )
So looking out of the boot loader. The maximum has brought nothing. If flashed, but after booting remains Viper.
As written, also the boot loader can not be closed.
Fooox1 said:
So looking out of the boot loader. The maximum has brought nothing. If flashed, but after booting remains Viper.
As written, also the boot loader can not be closed.
Click to expand...
Click to collapse
keep bootloader UNLOCKED!!
download TWRP 2.6.3.0: http://techerrata.com/browse/twrp2/m7
verify MD5
go to bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery, then flash one of the maximus 10 or 11 roms.
then go for rumrunner.
Result as before. I have the 2.6.3.0 flashed message Ok, fastboot erase cache, message Ok, fastboot reboot-bootloader, One reboots into Rome. When I go into recovery again, because it is the 2.6.3.3. So the one that is already on it.
I flash so not only since yesterday. I have a feeling that he executes everything speaks to fastboot / ADB commands, but it does not implement, for whatever reason.
I have also, over sideload that Guru_Reset_M7_2.24.161.1 flashed. Everything ok, abe after the start again Viper Rome.
Fooox1 said:
Result as before. I have the 2.6.3.0 flashed message Ok, fastboot erase cache, message Ok, fastboot reboot-bootloader, One reboots into Rome. When I go into recovery again, because it is the 2.6.3.3. So the one that is already on it.
I flash so not only since yesterday. I have a feeling that he executes everything speaks to fastboot / ADB commands, but it does not implement, for whatever reason.
I have also, over sideload that Guru_Reset_M7_2.24.161.1 flashed. Everything ok, abe after the start again Viper Rome.
Click to expand...
Click to collapse
sounds too much like a locked bootloader, would you mind copy/paste command prompt, for example:
Code:
C:\ADB2>[B][COLOR="Blue"]fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img[/COLOR][/B]
sending 'recovery' (10570 KB)...
OKAY [ 1.860s]
writing 'recovery'...
OKAY [ 0.768s]
finished. total time: 2.634s
C:\ADB2>[B][COLOR="Blue"]fastboot erase cache[/COLOR][/B]
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.058s
C:\ADB2>[B][COLOR="Blue"]fastboot reboot-bootloader[/COLOR][/B]
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
C:\ADB2>
No problem:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C: \ Windows \ system32> cd ..
C: \ Windows> cd ..
C: \> cd fastboot
C: \ fastboot> fastboot flash recovery recovery.img
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
C: \ fastboot> fastboot erase cache
erasing 'cache' ... OKAY
C: \ fastboot> fastboot reboot-bootloader
rebooting into bootloader ... OKAY
C: \ fastboot>
Oh, do not be surprised, the recovery was only renamed, can be write faster.
Fooox1 said:
No problem:
C: \ fastboot> fastboot flash recovery recovery.img
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
C: \ fastboot> fastboot erase cache
erasing 'cache' ... OKAY
C: \ fastboot> fastboot reboot-bootloader
rebooting into bootloader ... OKAY
C: \ fastboot>
Oh, do not be surprised, the recovery was only renamed, can be write faster.
Click to expand...
Click to collapse
1- yes, i am aware that it can be renamed, though I usually just type the first letter of the filename (for example "o") and then press tab, eg:
Code:
C:\ADB2>fastboot flash recovery o
then press TAB, and:
Code:
C:\ADB2>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
2-
sending 'recovery' (8432 KB) ... OKAY
writing 'recovery' ... OKAY
Click to expand...
Click to collapse
mine gives me a lot more info:
Code:
C:\ADB2>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
sending 'recovery' (10570 KB)...
OKAY [ 1.860s]
writing 'recovery'...
OKAY [ 0.768s]
finished. total time: 2.634s
C:\ADB2>fastboot erase cache
erasing 'cache'...
OKAY [ 0.055s]
finished. total time: 0.058s
C:\ADB2>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.043s]
finished. total time: 0.044s
3- 8432KB
What do you need more accurate. Had actually written anything. The error occurred after the Falshen the Viper Rome. I can do everything in recovery, Wipen, factory reset, etc, everything is executed and confirmed. Unfortunately baer not really. For example, I format the SD, is also displayed as running. But I then go to the File Manager is all still there.
Have also made a backup is running, I want to restore it, is nothing.
Fooox1 said:
What do you need more accurate. Had actually written anything. The error occurred after the Falshen the Viper Rome. I can do everything in recovery, Wipen, factory reset, etc, everything is executed and confirmed. Unfortunately baer not really. For example, I format the SD, is also displayed as running. But I then go to the File Manager is all still there.
Have also made a backup is running, I want to restore it, is nothing.
Click to expand...
Click to collapse
thanks for your kind comments, can i ask one more thing: MD5 of your "recovery.img"
The MD 5 Total:
84F04BFE70C03825689A457009235AD4
Fooox1 said:
The MD 5 Total:
84F04BFE70C03825689A457009235AD4
Click to expand...
Click to collapse
hmm, interesting I now have two versions of 2.6.3.0, one 10570KB and one 8432KB, but both worked fine:
Code:
C:\ADB2>fastboot flash recovery "openrecovery-twrp-2.6.3.0-m7 (2).img"
sending 'recovery' (8432 KB)...
OKAY [ 1.216s]
writing 'recovery'...
OKAY [ 0.675s]
finished. total time: 1.897s
C:\ADB2>fastboot erase cache
erasing 'cache'...
OKAY [ 0.056s]
finished. total time: 0.059s
C:\ADB2>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.052s]
finished. total time: 0.054s
-> bootloader -> recovery and it's there
have you tried using the unlocktocken again? maybe the phone is "semi-locked"
Have it now unlock again with bootloader and TWRP (the 8432 KB) tried to flash :
C: \ fastboot2 > fastboot flash unlocktoken Unlock_code.bin
sending ' unlocktoken ' (0 KB) ...
OKAY [ 0.142s ]
writing ' unlocktoken ' ...
( bootloader ) unlock token check successfully
OKAY [ 0.005s ]
finished . total time: 0.149s
C: \ fastboot2 > fastboot flash recovery recovery- open TWRP - 2.6.3.0 - m7.img
sending ' recovery ' ( 8432 KB) ...
OKAY [ 1.123s ]
writing ' recovery ' ...
OKAY [ 0.777s ]
finished . total time: 1.904s
Ergbnis as before , everything ok, but nothing happens. This is the result , if I want to lock the bootloader again :
C: \ fastboot2 > fastboot oem lock
...
( bootloader ) Lock successfully ...
(boot loader ) mipi display off
(boot loader ) mipi_dsi_cmds_tx_ext
(boot loader ) pm8921_vreg_disable function , vreg_id = 38
(boot loader ) pm8921_vreg_disable function , vreg_id = 1
(boot loader ) TZ_HTC_SVC_DISABLE ret = 534 642 044 ( 0x1FDDFD7C )
(boot loader ) Use PSHOLD to reset device .
FAILED ( status read failed ( Too many links ) )
finished . total time: 1.138s
I have the internal SD card into suspicion. Is there a way to check this or format via fastboot / ADB?
Fooox1 said:
Have it now unlock again with bootloader and TWRP (the 8432 KB) tried to flash :
C: \ fastboot2 > fastboot flash unlocktoken Unlock_code.bin
sending ' unlocktoken ' (0 KB) ...
OKAY [ 0.142s ]
writing ' unlocktoken ' ...
( bootloader ) unlock token check successfully
OKAY [ 0.005s ]
finished . total time: 0.149s
C: \ fastboot2 > fastboot flash recovery recovery- open TWRP - 2.6.3.0 - m7.img
sending ' recovery ' ( 8432 KB) ...
OKAY [ 1.123s ]
writing ' recovery ' ...
OKAY [ 0.777s ]
finished . total time: 1.904s
Ergbnis as before , everything ok, but nothing happens. This is the result , if I want to lock the bootloader again :
C: \ fastboot2 > fastboot oem lock
...
( bootloader ) Lock successfully ...
(boot loader ) mipi display off
(boot loader ) mipi_dsi_cmds_tx_ext
(boot loader ) pm8921_vreg_disable function , vreg_id = 38
(boot loader ) pm8921_vreg_disable function , vreg_id = 1
(boot loader ) TZ_HTC_SVC_DISABLE ret = 534 642 044 ( 0x1FDDFD7C )
(boot loader ) Use PSHOLD to reset device .
FAILED ( status read failed ( Too many links ) )
finished . total time: 1.138s
I have the internal SD card into suspicion. Is there a way to check this or format via fastboot / ADB?
Click to expand...
Click to collapse
1- so i just tried the lock command:
Code:
C:\ADB3>[B]fastboot oem lock[/B]
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (Too many links))
finished. total time: 1.126s
--> it rebooted back to the ROM, i went back to bootloader and sure enough it said RELOCKED
2- "I have the internal SD card into suspicion", we could check the partitions, but I doubt that it has anything to do with it, otherwise you would be experiencing a lot of random reboots.
3- also, have you tried other "tools" that work in custom recovery, such as: http://forum.xda-developers.com/showthread.php?t=1646108
just to see if recovery is working
4- did you flash any "boot.img" (kernel)?
5- have you tried "fastboot oem unlock"
6- have you tried flashing firmware (extracted from signed OTA) in ruu mode as mentioned in post #2?
2 The suspicion arises for me, since deleted, can be moved, but the device is, after rebooting, does not run or crashes. I have already backup, Rom.zip placed on the SD, but after rebooting into recovery they're gone.
3 aromafm-1.91 can be flash, can work with it, but after the restart everything as it was, nothing gets deleted, etc.
4 I have already tried e.g. from Vodafone Rome. As usual, Ok, Ok, but not adopted.
5 At the command fastboot oem unlock:
C: \ fastboot> fastboot oem unlock
... INFO [ERR] Command error!
OKAY
6 I have tried (OTA_M7_UL_JB_50_Vodafone_UK_1.29.161.11-1.28.161.7_release_315813_signedoj2qp335qmm8qjso) unzipped and used the firmware.zip.
Have the One_All-in One_Kit tried using the. But yes you use Flash Factory RUU zip. In this case, however, the device can not connect. About sideload's not the point. Will be transmitted to mobile phones, but the flash stops.
I also tried to flash the RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.16.exe . Device is detected and goes to the black screen (HTC ), of course aborts then , since it is not the correct CID .
Fooox1 said:
3 aromafm-1.91 can be flash, can work with it, but after the restart everything as it was, nothing gets deleted, etc.
Click to expand...
Click to collapse
It almost sounds like a secured kernel, can u post exact details of the ROM you're running, including link.
Did u ever flash a "boot.img" ?
Sent from my HTC One using Tapatalk
Device is stuck in fastboot mode
screen shows
Device is LOCKED: Status code: 0
IMEI : 00000000000
SKU: 00000
Serial number shows values
Date being shown as 01-01-1970
Bootloader logs shows
fastboot reason: failed to initialize partition table
any advise on how to recover from this?
Fastboot erase userdata plus cache
Sent from my Nexus 6 using XDA-Developers mobile app
get error on erase
MacBook-Pro:~ user$ fastboot devices -l
994f3b10 fastboot usb:337641472X
MacBook-Pro:~ user$ fastboot erase cache
erasing 'cache'...
(bootloader) Invalid partition name cache
FAILED (remote failure)
finished. total time: 0.067s
MacBook-Pro:~ user$ fastboot erase userdata
erasing 'userdata'...
(bootloader) Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.066s
MacBook-Pro:~ user$
fastboot flash bootloader. Are you trying to flash N Preview?
reagan1998 said:
fastboot flash bootloader. Are you trying to flash N Preview?
Click to expand...
Click to collapse
my device was running fine with 5.1 and not sure what caused to get into this stuck where its stuck in fastboot boot
i am just trying to flash factory images from https://developers.google.com/android/nexus/images#shamu
Given the suddenness of your problem as well as the symptoms, I believe the internal memory has failed, meaning a service call. However, I hope I'm wrong.
Regardless, flashing factory images won't work because your bootloader is locked. Assuming this is a software issue you may be able to restore the system by sideloading the Android N OTA through recovery. If you can successfully do that, head to Developer Options in the N preview and enable OEM unlock. From there, unlock the bootloader, so you can flash factory images.
Strephon Alkhalikoi said:
Given the suddenness of your problem as well as the symptoms, I believe the internal memory has failed, meaning a service call. However, I hope I'm wrong.
Regardless, flashing factory images won't work because your bootloader is locked. Assuming this is a software issue you may be able to restore the system by sideloading the Android N OTA through recovery. If you can successfully do that, head to Developer Options in the N preview and enable OEM unlock. From there, unlock the bootloader, so you can flash factory images.
Click to expand...
Click to collapse
- I read some threads on sideload, they need device booted with adb access, since mine is stuck in fastboot, i don't have access to device via adb, would side load still work?
- still looking for zip for side load for nexus 6, if you have pointer for it, please let me know
To sideload the Android N OTA, which is the only thing that will help you here, you need to be able to get into recovery and set the recovery to adb sideload mode. If you cannot get into recovery, you definitely have a hardware problem and will need to get the internal storage chip replaced. As for the Android N OTA zip, check in the General subforum. Of course you could also simply do a quick Google search for "Android N OTA Brick" and get to Google's page of OTA zips that way.
Strephon Alkhalikoi said:
To sideload the Android N OTA, which is the only thing that will help you here, you need to be able to get into recovery and set the recovery to adb sideload mode. If you cannot get into recovery, you definitely have a hardware problem and will need to get the internal storage chip replaced. As for the Android N OTA zip, check in the General subforum. Of course you could also simply do a quick Google search for "Android N OTA Brick" and get to Google's page of OTA zips that way.
Click to expand...
Click to collapse
Android N has a new bootloader, so sideloading it will probably make the device not boot into Android.
---------- Post added at 08:24 PM ---------- Previous post was at 08:23 PM ----------
Have you tried flashing a TWRP recovery and maybe flashing a custom ROM to see if it is a storage issue? This phone is not even two years old, it should not be having internal storage issues.
The Android N OTA I'm talking about includes the bootloader, as it is a full system image. Flashing TWRP will not work as the device has a locked bootloader. But since the device apparently has no partitions at all, the exercise I believe is moot. This is a hardware issue.
Run 'fastboot format cache' and 'fastboot format userdata', then run the most holy words in android 'fastboot oem unlock'. Check this: http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783 it really helped me out of a deep hole.
The only way that will work is if the OP enabled OEM Unlocking in Developer Options prior to the device forgetting its partitions. I hope he did, as having the option enabled doesn't affect the ability to get OTAs from Google. If however his device's EMMC chip failed as I believe, it won't help him resolve this issue.
reagan1998 said:
Run 'fastboot format cache' and 'fastboot format userdata', then run the most holy words in android 'fastboot oem unlock'. Check this: http://forum.xda-developers.com/nexus-6/help/solution-stuck-bootloop-locked-t3053783 it really helped me out of a deep hole.
Click to expand...
Click to collapse
apologies for delayed response, i didn't realize there was second page in replies and you guys are still trying to help
here is outout
sh-3.2# fastboot devices
994f3b10 fastboot
sh-3.2# fastboot format cache
Formatting is not supported for filesystem with type ''.
sh-3.2# fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s
sh-3.2# fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-apq8084-71.08(*)
(bootloader) product: shamu
(bootloader) board: shamu
(bootloader) secure: yes
(bootloader) hwrev: 0x83A0
(bootloader) radio: 0x6
(bootloader) emmc: 32GB Sandisk REV=07 PRV=01 TYPE=57
(bootloader) ram: 3072MB Elpida S8 SDRAM DIE=6Gb
(bootloader) cpu: APQ8084 ES1.1
(bootloader) serialno: 994f3b10
(bootloader) cid: 0xFFFF
(bootloader) channelid: 0xDEAD
(bootloader) uid: 7858B30111000000000000000000
(bootloader) unlocked: Not supported
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 8
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sdi.git: sdi.git
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) aboot.git: git=MBM-NG-V71.08-0-g32b8854
(bootloader) qe:
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.040s
sh-3.2#
If it's failing to initialize the partition table, there's nothing you can do here. It needs to go to Motorola for warranty service.
EDIT: How I can tell? The date was set to 1/1/70. That's the beginning date of the Unix clock, which means something got screwed up internally. That plus the lost IMEI and the failure of the device to find its partitions means a bad device.
Sorry to be the bearer of bad news here, but this isn't something software can fix.
Strephon Alkhalikoi said:
If it's failing to initialize the partition table, there's nothing you can do here. It needs to go to Motorola for warranty service.
EDIT: How I can tell? The date was set to 1/1/70. That's the beginning date of the Unix clock, which means something got screwed up internally. That plus the lost IMEI and the failure of the device to find its partitions means a bad device.
Sorry to be the bearer of bad news here, but this isn't something software can fix.
Click to expand...
Click to collapse
Thanks for looking in, warranty must be void since i had open the back cover .
EDIT: Bad advice given.
Strephon Alkhalikoi said:
I would try anyway. The worst that will happen is they will want to charge you.
Click to expand...
Click to collapse
Which is considered fraud and not condoned by xda.
@zelendel: Echh. I'm not looking to get myself or XDA in trouble. I'll edit my post appropriately. Thank you for the reminder.
Strephon Alkhalikoi said:
@zelendel: Echh. I'm not looking to get myself or XDA in trouble. I'll edit my post appropriately. Thank you for the reminder.
Click to expand...
Click to collapse
Not a worry. I know a lot of people advise it but we don't condone it. This is why the disclosure in the OP of every rom thread. We accept what we do might mean killing our device and having to buy a new one. It's a risk of the hobby.
On the Moto X subreddit you might have seen my post on how it came to this. Cant post it here though, because I'm a new user.
So here is the stuff copy pasted:
I'll start from the beginning to list what I did to the phone: Also, yes I'm new to this, so I did some dumdums along the way.
-Did the Moto unlock stuff(worked fine)(thanks tutorial, you didn't tell me this would wipe all my data till the end, I was already done by then)
-Installed TWRP 2.7something (the latest that the TWRP site recommended for this phone, worked fine)
-Used TWRP to install SuperSU/Root the phone(worked fine)
-tried installing cyanogenmod (failed, doesn't boot normally)
-reflashed everything to stock(worked fine, boot android 4.2.2)
-android loads updates, installs, fails to boot (bricked)
Here I am this is what my bootloader looks like:
AP Fastboot Flash Mode (S)
30.BE(*) (sha- blahblah
eMMC: 16gGB blah blah
...
Device is LOCKED. Status Code: 0
Battery OK
Transfer Mode: USB Connected
here comes the menue stuff
...
log looks like this:
downgraded security version
update gpt_main version failed
Failed to hab check for gtp_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
Fastboot reason Invalid CID
USB connected
my fastboot recognizes the device I'm using the mfastboot v2 The Moto X is bought in EU (should be Moto X 1052)
I tried flashing it the same way I did for the reset, the way I did it before, but that doesn't work. I'm not exactly at the setup I actually used to do that with, I'll be able to try it that way again in 3 hours or so, but my setup should be about the same, cept that I'm using a USB3 connection right now instead of a USB2 (I read that ADB is having some problems there, but not that this is the case with fastboot) I've googled for a lot of solutions, non of them worked for me. I don't know what to do anymore.
Some things that might be of interest
mfastboot oem get_unlock_data
results in:
(bootloader) could not get unlock data! [Okay] finished...
Trying:
mfastboot flash partition gpt.bin
results in:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.269s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.174s
bootloader:
downgraded security version
update gpt_mail version failed
preflash validation failed for GPT
I usually get things done with trying around and normally(on other phones) I have no problem making a TWRP backup finding it! and pulling it from the phone so I can reset it within something like 15 mins, but I wasn't able to find where TWRP stored it's backups in this case, and I didn't care very much, not much on the phone to loose.
Anyone know what I could try?
E: Okay, just noticed that the codes in barcodes are different now:
IMEI/MEID: 0000000000000000
SKU: 000000000000
Serial Number: 13a869f1 (that's not the one it should be!!! My serial number should start with TA.... and not contain any lower case letters)
DATE: 01-01-1970
Click to expand...
Click to collapse
One more thing I did(because I found it in this forum) was mfastboot getvar all and got this back:
Code:
version-bootloader: 30BE(*)
version: 0.5
cpu: MSM8960 Pro CS
ram: 2048MB Samsung S4 SDRAM DIE=4Gb
emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
product: ghost
revision-hardware: 0x8300
radio: 0x3
secure: yes
mid: 026b
serialno: 13a869f1
qe:
unlocked: Not supported
iswarrantyvoid: Not supported
max-download-size: 805306368
uid: 2EED8B050C000100000000000000
imei: 000000000000000
meid:
sku: 000000000000000
cid: 0xdead
iccid:
date: 01-01-1970
cust_md5:
reason: Invalid CID
ro.build.date:
ro.build.id:
ro.build.tags:
ro.build.type:
ro.build.user:
ro.build.version.codename:
ro.build.version.incremental:
ro.build.version.release:
ro.mot.build.customerid:
ro.product.name:
ro.build.fingerprint:
ro.build.version.full:
kernel.version:
E: And no, I don't have a problem with the serial number showing here, in the getvar all, because as said in the text quoted from reddit, the stuff there is wrong anyway.
I am seeing the same error. Looking forward to any help to OP and me.
¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down ___
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.
CheckS86 said:
¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down ___
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.
Click to expand...
Click to collapse
did you get the solution ?? I'm in the same situation help
CheckS86 said:
¡ I need help please !
I have a HTC Desire 10 pro (From Aliexpress, yes warranty avoid), it was working fine (more than a year) until a few days ago. One morning I took it and it was off but the notification led was not on despite charging. I tried to turn it on and enter to recovery but it was not responding. I decided to open the phone to remove the battery and verify that it was not damaged. Mysteriously the battery was in good condition, and once I removed it and plugged it back in, the phone responded again when connecting the USB and the charger.
But there is a problem, when the system is going to boot, after showing the HTC logo, the phone turns off together with the notification led and returns to the state in which I found it at first.
I removed and placed the battery again so that it would respond again, but now I entered to recovery to make a reset, but the problem is that the recovery is very outdated, so it does not have the "wipe data" options.
It should be said that i can enter into a "recovery mode" that shows:
"
hTC download mode
*** LOCKED ***
htc_a56dj_pro_dtwl PVT S-ON
LK-1.01.0000(8804eff8)
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-1.18.400.22
Aug 1 2017,13:15:24(929341)
system info
show barcode
reboot to bootloader
reboot to download mode
reboot
power down ___
Security Warranty
If you flash this phone with any ROM
that was not officially released by HTC
you take the risk of
releasing your personal and financial
information to unknown sources.
SD NOT MOUNTED
OTG NOT MOUNTED
FILE NOT FOUND
"
Where the blue txt is the actual menu.
In this "recovery mode" I can't use ADB commands, i only can execute some fastboot commands (PC recognizes my device because of fastboot drivers) as "reboot", but for example:
* I can't use the "erase" command because my current recovery is not supported:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: Partition userdata erase not supported)
finished. total time: 0.022s
"
* Nor I can directly install the TWRP recovery because it tells me:
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 1596000000 bytes
sending 'recovery' (14320 KB)...
OKAY [ 1.507s]
writing 'recovery'...
(bootloader) HOSD CL#929341
FAILED (remote: 9 RU_SECURITY_FAIL recovery and bootloader isn't BL_UNLOCKE)
finished. total time: 2.550s
"
* And I can't use the "oem unlock" command either because it just says:
"
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.062s]
finished. total time: 0.062s
"
Finally "getvar all" command shows this (i think could be useful):
"
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_a56dj_pro_dtwl
(bootloader) version: 1.0
(bootloader) max-download-size: 1596000000
(bootloader) serialno: LC68B1000101
(bootloader) current-slot:
(bootloader) imei: ( here shows IMEI correctly )
(bootloader) version-main: 1.18.400.22
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000(8804eff8)
(bootloader) mid: 2PYA1****
(bootloader) cid: 11111111
all:
finished. total time: 0.061s
"
Well, this is the situation, and i think the solution is:
install the TWRP recovery to do a factory reset and if necessary install a ROM (official or not).
Buuut, to install the recovery I need to activate USB debugging (MANUALLY in the android options) and activate the OEM unlock option to unlock the bootloader, which is impossible for me since the phone "turns off" before starting.
My question is:
How to activate OEM unlock option without having to access to android settings? I mean, with commands in fastboot or in some software.
I have searched a LOT on the internet and I can't find anything about it, all the tutorials have the device fully functional, not like me that my device does not start.
Click to expand...
Click to collapse
did u find the solution? i have the same problem with my note 20 ultra cant start the phone and the OEM is ON (L)
Wow. With a little more time another user (HTC U11+) enters the queue of the mishaps! Any Luck anyone? HTCDev also seem to have given up with no option to login to their website.