Database Info

Partition Error. Failed To Unlock Bootloader

{
"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"
}
Any Ideas?
My cmd says this when I type in the command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
error: device not found
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
TA93001LIK fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem unlock _CODE
...
(bootloader) Unlock code = ******************* < Thats Not The Code
(bootloader) Failed to erase partition
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 10.285s
My Device Rebooted Normally But Was Wiped :/

SamTenny said:
Any Ideas?
My cmd says this when I type in the command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
error: device not found
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot devices
TA93001LIK fastboot
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot oem unlock _CODE
...
(bootloader) Unlock code = ******************* < Thats Not The Code
(bootloader) Failed to erase partition
(bootloader) General Unlock failure!
(bootloader) OEM unlock failure!
FAILED (remote failure)
finished. total time: 10.285s
My Device Rebooted Normally But Was Wiped :/
Click to expand...
Click to collapse
can you get to fastboot once more and see the top of the screen for device status?
some users reported those error message but their device get unlocked anyway

Yah! Thats what my 2nd threads about! I got a status code 3! Motorola Support even had no clue. They are going to email me this morning. Probably won't help. Their staff recommended here and motorola forums

HTC E8 DEAD no Os no recovery

{
"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"
}
Hello guys…I need some help with my htc E8 from sprint
My phone is dead no OS , no recovery and stuck at bootloader screen with s-on and is locked bootloader never I unlocked.
Fastboot oem rebootRUU doesn´t work
Fastboot flash unlocktoken doesn’t work
Fastboot flash zip rom.zip doesn’t work because is locked the bootloader I think
When I try flash from hboot with 0PAJIMG.zip error says: device halted due to the largue image update fail.
And every step that I take never do anything…when I try fastboot oem rebootRUU command says: error the command never completed.
I get the rom.zip from the RUU is normal the file has 1.5gb?
Please help me…thanks.​

try to help. give me time. do not upgrade to higher version as it is impossible to downgrade by RUU method. you can simply use ADB commands via USB to unlock bootloader then flash TWRP and use SD card to flash TWRP backup rom. i think this is the easiest method.
Sent from my Nexus 4 using Tapatalk

sallomi said:
try to help. give me time. do not upgrade to higher version as it is impossible to downgrade by RUU method. you can simply use ADB commands via USB to unlock bootloader then flash TWRP and use SD card to flash TWRP backup rom. i think this is the easiest method.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
ok...but I cant unlock the bootloader with the fastboot command .tell me what can I do to unlock througt adb, the phone doesnt start.

sawonch said:
ok...but I cant unlock the bootloader with the fastboot command .tell me what can I do to unlock througt adb, the phone doesnt start.
Click to expand...
Click to collapse
Are you opening a cmd prompt from the folder that includes adb/fastboot ? And are you placing the zips inside the same folder

benny3 said:
Are you opening a cmd prompt from the folder that includes adb/fastboot ? And are you placing the zips inside the same folder
Click to expand...
Click to collapse
of course man...but I cant flash zip file because my device bootloader is locked and when I try to unlock it with fastboot command says: the command never completed and another lines with error...
when tipe cmd fastboot oem rebootRUU here is the succes:
C:\Users\Lidia\Desktop\umbricking project>fastboot oem rebootRUU
...
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Reading block @ 786432
(bootloader) [SD_ERR] sd_read_sector: read sector failed (786432 256)
(bootloader) [ERR] partition_read_emmc(589): error -1
(bootloader) Start Verify: 3
(bootloader) Error: Command never completed
(bootloader) Error: Command timeout error
(bootloader) Error: Command completed with errors
(bootloader) Failed Writing block @ 786432
(bootloader) [SD_ERR] sd_write_sector: write sector failed (786432 256)
OKAY [ 10.285s]
finished. total time: 10.301s
because this error I cant start flashing rom.zip

hardware failure (eMMC problem)

[need help]Try to root pixel 2 but can't unlock the oem lock

I bought pixel 2 a month ago.
It version is
8.0.0 (OPD3.170816.012, Sep 2017, Verizon)
And updated 8.0 to 8.1
8.1.0 (OPM1.171019.019, Feb 2018)
Bootloader: mw8998-002.0067.00
Product Revision: walleye MP1
boot-slot: a
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
fastboot version
fastboot version eac51f2bb6a8-android
-------------------
I turn on the develop mode ,debug mode
OEM lock grayed
TRY to fastboot unlock
C:\Users\User\Downloads\pixel 2root\fastboot>adb devices
List of devices attached
HT7B41A03550 device
C:\Users\User\Downloads\pixel 2root\fastboot>adb reboot bootloader
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.008s
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot oem unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.009s
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.006s]
finished. total time: 0.015s
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot flashing lock_critical
...
FAILED (remote: unknown command)
finished. total time: 0.004s
TRY the recovery mode ,to rollback the 8.0
{
"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"
}
imgur.com/a/2RCVp
i.imgur.com/PhsS42u.jpg
Also TRY this page the apk diidn't work
https://forum.xda-developers.com/pixel-2-xl/how-to/exp-verizon-pixel-pixel-2-xl-potential-t3750795
Somebody know how to root it ,am i miss something ?
please help me ,i am no idea what wrong is it...

am i post in the wrong page ,how to delete post (sorry i am new here
am i post in the wrong page ,how to delete post (sorry i am new here

zavke said:
I bought pixel 2 a month ago.
It version is
8.0.0 (OPD3.170816.012, Sep 2017, Verizon)
And updated 8.0 to 8.1
8.1.0 (OPM1.171019.019, Feb 2018)
Bootloader: mw8998-002.0067.00
Product Revision: walleye MP1
boot-slot: a
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
fastboot version
fastboot version eac51f2bb6a8-android
-------------------
I turn on the develop mode ,debug mode
OEM lock grayed
TRY to fastboot unlock
C:\Users\User\Downloads\pixel 2root\fastboot>adb devices
List of devices attached
HT7B41A03550 device
C:\Users\User\Downloads\pixel 2root\fastboot>adb reboot bootloader
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.008s
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot oem unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.009s
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 0
OKAY [ 0.006s]
finished. total time: 0.015s
C:\Users\User\Downloads\pixel 2root\fastboot>fastboot flashing lock_critical
...
FAILED (remote: unknown command)
finished. total time: 0.004s
TRY the recovery mode ,to rollback the 8.0
imgur.com/a/2RCVp
i.imgur.com/PhsS42u.jpg
Also TRY this page the apk diidn't work
https://forum.xda-developers.com/pixel-2-xl/how-to/exp-verizon-pixel-pixel-2-xl-potential-t3750795
Somebody know how to root it ,am i miss something ?
please help me ,i am no idea what wrong is it...
Click to expand...
Click to collapse
Did you purchase your phone from Google or Verizon? If you purchased it on Verizon, you can no longer unlock the bootloader using the lock_critical command anymore as it has been fixed in this version. Also I do not believe it is possible to roll back to 8.0 but I could be wrong. I haven't had a reason to try.
zavke said:
am i post in the wrong page ,how to delete post (sorry i am new here
Click to expand...
Click to collapse
Should've posted in the questions section.

Try a factory reset. Skip the setup wizard; the OEM Unlock toggle should be available. It was greyed out on mine until I wiped /data.

socal87 said:
Try a factory reset. Skip the setup wizard; the OEM Unlock toggle should be available. It was greyed out on mine until I wiped /data.
Click to expand...
Click to collapse
Can anyone confirm this
Did you have SIM card in? WiFi on? any specifics?

Jmaniac55 said:
Can anyone confirm this
Did you have SIM card in? WiFi on? any specifics?
Click to expand...
Click to collapse
It's been confirmed. Yes, SIM was in, and WiFi was on. I factory reset, and skipped the setup wizard (didn't connect to wifi). Immediately went to Settings > System > About Phone and enabled developer mode, and OEM unlocking was available. It was greyed out before I reset, when I had user data on the device.

socal87 said:
It's been confirmed. Yes, SIM was in, and WiFi was on. I factory reset, and skipped the setup wizard (didn't connect to wifi). Immediately went to Settings > System > About Phone and enabled developer mode, and OEM unlocking was available. It was greyed out before I reset, when I had user data on the device.
Click to expand...
Click to collapse
Nope it sure does not work, tried it and it's still greyed out

Unable to use foastboot commands because device is not being detected.

I have an HTC One m9 that is bricked, but I can unbrick it with fastboot commands to flash the stock rom. I am unable to connect to my device to my laptop with usb for some reason though. When I do "fastboot devices" it shows a list of devices that is empty. when I try to flash anyway, it just says waiting for devices or something like that. Do I need like a special usb driver to connect to my phone via usb? or am I doing something wrong.

Install the HTC USB Driver
HTC One M9 USB Driver for Windows (Official Mobile Driver)
Download the official HTC One M9 USB Driver for your HTC Mobile. We also provide all other HTC Mobile drivers for free.
gsmusbdriver.com

Thank you! Ill post if it worked.

Thank you so much it worked!
{
"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"
}

well connecting to the phone worked, flashing failed.
I am getting many errors here is the log
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
OKAY [ 0.063s]
finished. total time: 0.080s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash zip update.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1934862309 is not a multiple of the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 1934862309 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1934862309 is not a multiple of the block size 4096
OKAY [ 1.033s]
writing 'zip' 1/1...
(bootloader) HOSD CL#894012
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_8
(bootloader) 50laQ
(bootloader) ERR preload central directory info failed (EOCD).
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0)
finished. total time: 2.081s

The ZIP you pass to fastboot is corrupted: at least its Central Directory part - located at ZIP's end - can't be read.

so I need to find a different zip that works then.

TWRP only shows a black screen

After installing TWRP all I get is a black screen. Any idea why? Here is what I did so far:
Bootloader unlocked:​I have unlocked the bootloader as described
Bash:
>fastboot oem unlock 0xXXXXXXXXXXXX
OKAY [123.312s]
Finished. Total time: 123.312s
And the bootloader shows as unlocked in the developer settings:
{
"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"
}
Reboot to Bootloader:​I rebooted into the bootloader using adb:
Bash:
>adb devices
List of devices attached
CB512E83J6 device
>adb reboot bootloader
>fastboot devices
CB512E83J6 fastboot
Flash TWRP​I tried to flash both TWRP 3.5.2 and TWRP 3.4.0. I also rename the files twrp.img and recovery.img as suggested in some of the instruction. But that didn't make any difference.
Bash:
>fastboot --verbose flash recovery twrp-3.5.2_9-0-maple.img
fastboot: verbose: Do flash recovery twrp-3.5.2_9-0-maple.img
fastboot: verbose: target reported max-download-size of 536870912 bytes
Sending 'recovery' (33596 KB) OKAY [ 0.855s]
Writing 'recovery' OKAY [ 0.318s]
Finished. Total time: 1.178s
Boot recovery​Using fastboot​First I tried to boot the recovery using fastboot but that booted Android instead:
Code:
>fastboot --verbose reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.001s
Using ADB​From there I tried to adb to boot into recovery. That too booted Android instead:
Code:
>adb reboot recovery
Using Volume down + Power Button
Last I tried the Volume down + Power Button until the first vibration, then releasing the Power Button. That at least resulted in green LED suggesting that the recovery was indeed booted. But the screen is all black and fastboot won't report the device ID.
Bash:
>fastboot --verbose devices -l
???????????? fastboot usb:339869696X
I order to return to Android I have to first boot into the bootloader. If I just reboot the system I will reboot into the revovery again.
Code:
>fastboot reboot bootloader
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.001s
Any ideas what else I can try?
Is there an alternative recovery ROM I could try?
All I want is to root the phone and the recovery is only on step into that direction. Which begs the question: Can I root without recovery?

Update:​I'm one step further: It's necessary to unplug the USB cable and reboot pressing Volume down + Power Button. That's interesting and I should have tried it earlier.