Database Info

[Q] Root Help?

{
"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"
}
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 ;( But googled restored contacts, apps & sms

Have a look here for guides: http://forum.xda-developers.com/showthread.php?t=2577043

Help!
Followed guide and when I got to the unlocking bootloader stage it says that my device is not eligble for being unlocked (bootloader) Any HELP!?!?!

SamTenny said:
Followed guide and when I got to the unlocking bootloader stage it says that my device is not eligble for being unlocked (bootloader) Any HELP!?!?!
Click to expand...
Click to collapse
Spam the button their site sucks. Try after a day or two.
If it still doesn't work then this the only solution left.... http://theroot.ninja

SamTenny said:
Followed guide and when I got to the unlocking bootloader stage it says that my device is not eligble for being unlocked (bootloader) Any HELP!?!?!
Click to expand...
Click to collapse
Are you sure you put in the correct value? I thought my xt1032 was not eligible but it was. I typed in the wrong characters.

OK. Thank God
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 ;( But googled restored contacts, apps & sms

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

[LOGO] Remove The Unlocked Bootloader Message

Remove The Unlocked Bootloader Message​
Instruction:
Download the logo.zip
Extract all the files
Reboot to fastboot mode (power + vol down)
Now open cmd and use cd command to go to the directory where you placed the file.
Now Type the command: fastboot flash logo logo.bin
Reboot from the recovery (use vol up to select and vol down to navigate)
Now your bootlogo should be restored back to the normal version
Click to expand...
Click to collapse
screens
{
"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"
}
Hit Thanks If It Helped You!!

Reserved!!

works as advertised. thanks

FunkeeC said:
works as advertised. thanks
Click to expand...
Click to collapse
:good:

I'm an idiot, got it working finally. Even when loading from the platform tools folder it failed. Had to move it to root of C:\ and load like this:
C:\windows\system32>fastboot flash logo C:\logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (460 KB)...
OKAY [ 0.019s]
writing 'logo'...
OKAY [ 0.420s]
finished. total time: 0.440s

SurferNerd6987 said:
I'm an idiot, got it working finally. Even when loading from the platform tools folder it failed. Had to move it to root of C:\ and load like this:
C:\windows\system32>fastboot flash logo C:\logo.bin
target reported max download size of 268435456 bytes
sending 'logo' (460 KB)...
OKAY [ 0.019s]
writing 'logo'...
OKAY [ 0.420s]
finished. total time: 0.440s
Click to expand...
Click to collapse
So now what is u r problem??

Don't have one. It worked. Just a bit of different instruction.

It seems this is a copy of http://forum.xda-developers.com/showpost.php?p=52692225&postcount=2
Please do not copy or repost others' work without permission
Thread closed

Huawei Mate 9 stuck on critical data loss screen!!

The device is not oem unlocked, and it only boots to the screen mentioned, when connected to the PC it appears as a CD unit, with no options at all.
{
"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"
}
When trying to use ADB or FastBoot won't work, also tried to use the Huawei tool and it doesn´t work.
Any ideas on what to do, I really want to obtain all my photos and data back.
Do I have to open the device or is it completely dead?

Could it boot directly to Fastboot - switch off, connect to PC, press and keep pressing Vol- , boot?
And to eRecovery - switch off, connect to charger, press and keep pressing Vol+, boot?
Can you explain which firmware you had (like MHA-L29c432 9.1.0.255(C432E7R1P8) or so)?
Was the Bootloader unlocked - and then, did you have TWRP, Magisk, custom ROM?
What were you doing last (maybe flashing something and what) when it got bricked

zgfg said:
Could it boot directly to Fastboot - switch off, connect to PC, press and keep pressing Vol- , boot?
And to eRecovery - switch off, connect to charger, press and keep pressing Vol+, boot?
Can you explain which firmware you had (like MHA-L29c432 9.1.0.255(C432E7R1P8) or so)?
Was the Bootloader unlocked - and then, did you have TWRP, Magisk, custom ROM?
What were you doing last (maybe flashing something and what) when it got bricked
Click to expand...
Click to collapse
As said on the post the phone was never bootloader unlocked, neither was it changed since i got it. An update came by and when i pressed accept, after 5 min of waititng thats the screen that the phone turns on to.

D.FrostIce said:
As said on the post the phone was never bootloader unlocked, neither was it changed since i got it. An update came by and when i pressed accept, after 5 min of waititng thats the screen that the phone turns on to.
Click to expand...
Click to collapse
Ok, but still what was the firmware you had (and update coming) - since no BL code, you can try to fix it only by DLOAD, and for DLOAD it is important to know what was the firmware (to find and use the same, at least same cust and EMUI version 8, 9 or 9.1)

zgfg said:
Ok, but still what was the firmware you had (and update coming) - since no BL code, you can try to fix it only by DLOAD, and for DLOAD it is important to know what was the firmware (to find and use the same, at least same cust and EMUI version 8, 9 or 9.1)
Click to expand...
Click to collapse
But there is no option at all to recover the data on the device right?

D.FrostIce said:
But there is no option at all to recover the data on the device right?
Click to expand...
Click to collapse
Not, because Internal memory is encrypted and only system can access - you must boot to system.
Try going to Service shop, what they can do
Asked you to try booting to eRecovery, it has an option to (re)Install latest firmware (without Factory reset if you don't force)
TestPoints method should fix the brick, but it would erase everything

zgfg said:
Not, because Internal memory is encrypted and only system can access - you must boot to system.
Try going to Service shop, what they can do
Asked you to try booting to eRecovery, it has an option to (re)Install latest firmware (without Factory reset if you don't force)
TestPoints method should fix the brick, but it would erase everything
Click to expand...
Click to collapse
After several attempts I am now able to enter Fastboot&Recovery mode, what should i do from here?

D.FrostIce said:
After several attempts I am now able to enter Fastboot&Recovery mode, what should i do from here?
Click to expand...
Click to collapse
From eRecovery (this is not Recovery, instructions were above), take Install latest firmware and recovery
If ain't work, read from Fastboot:
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry

same boat here,
MHA-L29c432 9.1.0.255
no oem unlock, got up this morning, phone exactly as described above..
erecovery fails, "in chinese", cannot format data...
below fastboot:
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 0.008s]
finished. total time: 0.010s
C:\Minimal ADB and Fastboot>fastboot oem get-product-model
...
(bootloader) MHA-L29
OKAY [ 0.035s]
finished. total time: 0.038s
C:\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :MHA-L29 9.1.0.252(C432E7R1P8)
OKAY [ 0.041s]
finished. total time: 0.047s
C:\Minimal ADB and Fastboot>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :MHA-L29 9.0.1.158(C432E6R1P8)
OKAY [ 0.042s]
finished. total time: 0.046s
C:\Minimal ADB and Fastboot>fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.035s

In order to try some recovery methods "multtitool for huawei" , tried to use my old, never used unlock code, in order to unlock bootloader, in hope of some progress..
C:\Minimal ADB and Fastboot>fastboot oem unlock QXRFBADKDT677FUE
...
FAILED (status malformed (1 bytes))
finished. total time: 7.644s
C:\Minimal ADB and Fastboot>
it actually shows "phone unlocked":
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.006s]
finished. total time: 0.006s
..but on reboot to next fastboot it does not stick, and I cannot flash any of the system images, or recovery.
Example:
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
Finished. Total time: 2.686s
it behaves very strangely according to me.
other than throwing it in the bin, does anyone have any idea, in order to recover this brick?
or is it time to move on..?

gjergji1 said:
In order to try some recovery methods "multtitool for huawei" , tried to use my old, never used unlock code, in order to unlock bootloader, in hope of some progress..
C:\Minimal ADB and Fastboot>fastboot oem unlock QXRFBADKDT677FUE
...
FAILED (status malformed (1 bytes))
finished. total time: 7.644s
C:\Minimal ADB and Fastboot>
it actually shows "phone unlocked":
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.006s]
finished. total time: 0.006s
..but on reboot to next fastboot it does not stick, and I cannot flash any of the system images, or recovery.
Example:
Writing 'recovery_ramdisk' FAILED (remote: 'flash write failure')
Finished. Total time: 2.686s
it behaves very strangely according to me.
other than throwing it in the bin, does anyone have any idea, in order to recover this brick?
or is it time to move on..?
Click to expand...
Click to collapse
When you successfully unlock (or relock), it notes you that it will reboot and perform Factory reset - it didn't?
Anyway, in Fastboot screen, at the bottom, do you read in RED Phone (=Bootloader) unlocked and FRP unlocked.
Only then it will allow you to flash
If FRP (=OEM) is locked (GREEN), it will not allow you to unlock Bootloader

Phone confirmed dead. Very dissapointed in Huawei.
Moving on..
Purchasing a oneplus 7t...

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.