I'm struggling with this phone for couple of months, trying to fix it from time to time. Now I feel like there's no hope for it anymore. Tried flashing a lot of custom recoveries for this phone with no success - after turning on the phone and after the Huawei logo I just see fastboot-similar screen with a title 'Error Mode' and with errors: Func NO: 11 (recovery image) and Error NO: 2 (load failed).
I tried TWRP, Elite TWRP and nothing, always stuck at Error mode. I believe this phone is bootaloader and FRP unlocked (you can see in fastboot). I tried extracting recovery, system images from firmware but recovery_ramdisk spits out 'FAILED (remote: partition length get error)' and also I'm not really sure which image should I extract from the update.app.
I'm attaching 3 images - error mode, fastboot mode, images list from the extractor. If anyone has some ideas, I'm happy to hear them.
Error mode:
{
"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"
}
Fastboot mode:
Extractor:
szerbi said:
remote: partition length get error
Click to expand...
Click to collapse
Are you sure your phone is running EMUI 8?
In fastboot mode run commands:
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Related
Hello Folks,
Whenever I reboot my mobile from adb command, it throws below message and not get processed. I tried many times with different varieties but failed. Could you guys help me out here.
{
"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"
}
Thanks in advance for your help.
Make sure you have enabled "allow OEM unlocking" in developer settings. After that go to bootloader and enter the following commands (this will wipe user data)
fastboot oem unlock-go
After entering this command your phone will factory reset.
Now come back to recovery and flash twrp.
fastboot flash recovery twrp.img
fastboot boot twrp.img
StFa2001 said:
Make sure you have enabled "allow OEM unlocking" in developer settings. After that go to bootloader and enter the following commands (this will wipe user data)
fastboot oem unlock-go
After entering this command your phone will factory reset.
Now come back to recovery and flash twrp.
fastboot flash recovery twrp.img
fastboot boot twrp.img
Click to expand...
Click to collapse
Tried that also, but in the command window after executing the command, it says "waiting for devices" and nothing happens after that. OEM unlocking is already allowed in setting.....I also tried by using toolkit available on internet, but in that, my devices is not detected. Tried Kingo Root, but phone get restart every-time when it goes to 90%.
which os do you have?
---------- Post added at 12:32 PM ---------- Previous post was at 12:31 PM ----------
which rom u have installed?
hello, I have a problem with my LG K8 M200E. He suddenly hung in Fastboot mode. I can not do anything. I uploaded the ADB drivers, I tried to upload the file "laf, boot, aboot, recovery" but no results. All the time when I try something in ADB, I get the message "FAILED (remote: unknown command)". Please, help me save him. I can not enter recovery and download mode.
https://i.imgur.com/0NTJhdp.jpg
{
"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"
}
Same problem
Hi did u get ur phone fixed after i have the same problem
hello, I have a problem with my LG v20. He suddenly hung in Fastboot mode. I can not do anything. I uploaded the ADB drivers, I tried to upload the file "laf, boot, aboot, recovery" but no results. All the time when I try something in ADB, I get the message "FAILED (remote: unknown command)". Please, help me save him. I can not enter recovery and download mode.
i had the same problem, the phone for no reason between a day and a night i found it hang on fastboot mode. there is no download mode, i have tried the edl mode, i managed to get the pins and i entered edl successfuly, but i couldnt find the horsefile for the Qualcomm flasher, i tried a different file from other phones that have same SoC but the Qualcomm flasher wouldn't accepted.
thats how far i reached with this phone and i gave up, if anyone interested in going into edl mode i can give you the steps
Does anyone know how to troubleshoot fastboot oem get_unlock_data just hanging and returning nothing?
Aside from not starting with a clean Windows install, I've followed Explorer 4x4's methodology many times but cannot progress. Here's a dump of details that may help:
Windows 8.1
- removed all old and/or non-present devices from Device Manager, leaving:
{
"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"
}
- installed Android Studio
Fastboot:
ADB:
BL:
Code:
MBM-3.0-uefi-ae87908-180903
Baseband:
Code:
M660_04.07.01.46.02R EVERT_APACDSDS_CUST
Product/Variant:
Code:
evert XT1926-5 64GB PVT1
Console [NULL]:
Code:
null
Tools Mode Config:
Code:
DISABLED
Hopefully you have figured this out by now but if not I will help you with your device.
Hello.
Thanks for your offer to help. Unfortunately no the issue is ongoing. Have not unlocked the bootloader.
It seems the 'oem' function(s) in fastboot may be exactly that - down to the OEM to supply and ensure they work. Perhaps so much so that 'fastboot oem' is actually a command sent directly to the phone and if the function called, in this case get_unlock_data does not return anything, it's just black hole.
Anyway, if there's something I can do to absolutely ensure I'm starting from scratch, that might be helpful. I'm thinking something along the lines of that net command in Windows that resets the whole network stack at a low level, but in the context of adb and so forth. I've installed and uninstalled and reinstalled all the bits and pieces so many times, it doesn't seem to be doing the trick.
That or perhaps I could try a Linux live environment? Is there ADB, fastboot binaries for Linux?
Hello!
I have been trying to boot from boot.img/recovery.img with "fastboot boot" command but it doesn't work, so I can't root my phone with magisk.
I have to use "fastboot flash" to root it, and that way I lose the option to do OTA updates.
The issue:
1. I connect the phone to the computer in fastboot mode.
2. I use "fastboot boot patched_boot.img or twrp.img"
3. Phone goes into charging mode.
Things I've tried:
- Different cables
- Different computers
- Latest platform-tools
- Flashed stock ROM from fastboot
I am currently on Android Pie but I have this issue since around June 2018.
{
"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 suggestions?
1. Connect turned on phone to PC
2. adb reboot bootloader
3. Wait for fastboot logo
4. fastboot boot boot.img
5. Should boot after about 30 seconds
[SOLVED] Thank you BlackChimaera
BlackChimaera said:
1. Connect turned on phone to PC
2. adb reboot bootloader
3. Wait for fastboot logo
4. fastboot boot boot.img
5. Should boot after about 30 seconds
Click to expand...
Click to collapse
It worked! Thank you BlackChimaera for your advice.
Glad to hear it ) Been in this situation myself. Not sure what the cause of it.
Reboot to EDL mode from FASTBOOT!
No more Test Point Method needed
Technical Details:
Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the command line and refuses to sent the command to the device. Since FastBoot command protocol is simple and text-based, it is enough to send a packet containing "reboot-edl" text over USB. The simplest way to do that is to patch Windows fastboot.exe file, replacing "reboot-bootloader" text with "reboot-edl". As "reboot-bootloader" string is found in the command line, fastboot.exe sends the same constant string to the device. So if "reboot-bootloader" is replaced with "reboot-edl", you can specify "reboot-edl" in the command line and the same text will be sent to the device.
New Update: Fastboot updated to latest version.
Tutorial:
1. Download the Fastboot_to_EDL from : https://www.mediafire.com/file/yr7csyo64e97vbu/Fastboot_to_EDL.zip/file
2. Extract the zip in your desktop
3. Open the folder and double Click on Reboot.bat
{
"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"
}
4. Reboot your device to Fastboot Mode by pressing
Vol Down + Power button and connect your device with PC and Press Enter.
5. Your Device will be rebooted to EDL!
6. Now flash your Fastboot Rom with Mi Flash Tool to Unbrick your Mi Note 3.
Proof:
saved my ass
thanks a lot ahmed.....
i bricked my phone.. went to flash twrp without unlocking bootloader and it bricked..
this tool saved the phone else mom was gonna whoop my ass..
peace:good: