Hi all,
So I'm with EE in the UK, which is the only network to refuse to update the Mate 20 Pro until at least April. I tried to update using this method here which has had some success on the EE forums: https://forum.xda-developers.com/mate-20-pro/how-to/android-emui-10-lya-l29-c432-dload-t4015241
I formatted my USB, plugged it in my the adapter, and it verified and installed the files in the dload folder:
{
"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"
}
However, upon loading now I get stuck at the "Your device is booting" with the option of either powering off, holding power down to enter eRecovery etc. I tried to restore via eRecovery but get a failed error after connecting to any WiFi. I tried to connect to HiSuite but it says the device is not supported.
Fastboot says "PHONE locked, FRP Unlock" so I don't know if I can do anything to restore it.
My best idea is to be able to reflash an original EE image via the USB method again - does anyone know how I can do this? Or is the device permanently bricked?
Thanks
Matt
EDIT: I should point out the error has occurred because I flashed LYA-L29 instead of the LYA-L09 that I am on...
I can connect via ADB/fastboot if that helps...
MattKneale said:
I can connect via ADB/fastboot if that helps...
Click to expand...
Click to collapse
Put the files in the adb/fastboot folder, enable "usb dubugging, open cmd as admin and navigate to the adb folder then type "adb reboot bootloader" then "fastboot flashing unlock" then on your phone press "unlock the bootloader" then after quickly setting up the phone go straight to settings and enable developer mode and usb debugging again then on the pc type "adb reboot bootloader" and finally type "flash-all" wait patiently for the flashing to end.
Good luck !
Related
For clarity, my OS is Lubuntu 17.04 (Zesty)
Due to my phone's apparent obscurity, I'm unable to find any resources pertaining to it, so I've been trying to be as 'manual' as I can by unlocking it through fastboot commands. I really want to unlock my phone's bootloader in order to root it and install a custom recovery and then custom ROM.
However, I've run into an issue. Whenever I run 'fastboot oem unlock', as well as most other fastboot commands, I get stuck at an ellipsis('...') and it stays there until I shut off my phone. Ctrl+C and Ctrl+Z can't close it. So far, I've successfully installed ADB and fastboot tools.
For troubleshooting, I have:
- double checked if my device is listed whenever I run either the 'adb devices' command or the 'fastboot devices' command and it is listed for both
- I've set up my udev rules and adb_usb.ini
- changed usb ports/cables
- rebooted my phone and PC many times
- looked for official and unofficial unlocking instructions (to no avail)
If there is anyway you can help me or guide me to a resource which may be of use to me, please do so. It's been a real struggle having such an obscure phone, but it's what I can afford at the moment.
tl;dr: 'fastboot oem unlock' not working. stuck at ellipsis('...'). device is listed under 'adb devices' and 'fastboot devices' command.
Unfortunately, I can't post outside links yet, so please PM me for a link to my dropbox folder containing my .rules, adb_usb.ini, and CPU-Z information.
{
"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"
}
Bolded for skimmers.
Respect All XDA Developers,
I'm mizan from Bangladesh, i have a problem with my Huawei GR5 mini Device with the Bootloader.
The problem cause........ I am unlock my device bootloader, twrp recovery & root my device, few month letter i need to relock the bootloader, also remove the supersu. that's why i go to the supersu apk and full unroot my phone, then i flash the stock recovery (unfortunately it's may not flashed i don't know). then i go to the bootloader mode & type a command to relock the bootloader then the problem happened.
Please help!!
I have a full partitions backups made with Partitions Backup and Restore App (Root access required). I backup all the partitions, all of them in raw mode. All the files are *.img ready to flash with fastboot.
The problem
1. adb is not recognizing the device
2. fastboot is not recognizing the device
3. I cannot enter TWRP
4. Huawei EMUI 3 buttons (volume up + volume down + on/off button) function doesn't start neither (I'm trying to force the update to B132 ROM)
5. The phone enters directly to Rescue Mode and says
{
"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"
}
6. i can't shutdown my phone when i press the power button it will automatically go to the Rescue Mode again.
So the phone is still working and I got this RESCUE MODE screen but I can't do anything when this screen is displayed.
Any idea? What can I try?
Please, I really need your help, anything you can imagine to try please, let me know!!!
Thanks in advance!!!
Same Problem
Same problem happened to my GR5 mini also. What to do?
Hi all, as the title says, I'm unable to install twrp recovery.
Before proceeding on Android:
- USB debugging enabled
- Bootloader unlocked
- All screen security disabled
Befor proceeding on Windows:
- ADB tools & fastboot downloaded
- Z5C drivers downloaded
- General Google driver downloaded
- TWRP recovery downloaded
First connection pc the phone shows up at portable devices as Xperia Z5 Compact.
{
"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"
}
Opened command prompt -> ADB devices
command prompt -> ADB reboot bootloader
Phone goes into black screen + blue led
Moves from "portable devices" to "other devices" and shows up as S1Boot Fastboot
command prompt -> ADB reboot bootloader
fastboot flash recovery recovery.img -> stuck into "waiting for device"
I tried installing drivers via different methods with no luck.
Any help is much appreciated
PD: Can't post links to pics
Disconnect the device and shut it down.
Wait a few seconds.
Press volume up and hold it and connect usb cable.
Flash recovery.
Would be nice if you give a feedback!
Hello!
I got my mom's phone because it got stuck on the boot screen (honor Powered by android). She was out in the cold for a while, and when she tried to use her smartphone, it had shut down. As she tried to restart it, it got stuck on the boot screen. So she gave it to me hoping to at least get some important data back. I fixed some bricked phones in the past, but this one seems impossible to fix.
I got fastboot working, but the recovery doesn't seem to start no matter how I press PWR and Vol+. Also fastboot reboot recovery gets me no further than a reboot to the boot screen. Since the FRP is locked, I can't flash a recovery image.
The fastboot screen suggest to open HiSuite. But on my Mac it does require HDB to be active. However the windows version aknowledges that a device can do something via fastboot.
But my win10 machine is unable to properly recognize the usb device. Installing USB drivers seems not to help, even manual install in the device manager fails with driver signature disabled. Also a registry fix from this website seems not to help. In the end, I can't get fastboot to work in the commandline nor HiSuite.
At this point I'm out of Ideas. As it stands now, the only way to recover the data is by unsoldering the eMMC .
There are ways to unlock the bootloader, but as far as I know, it requires wiping the storage.
I'm not sure what happened to the phone outside, but it's really strange that there is no recovery available.
Does anyone have ideas on how to proceed?
{
"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"
}
Hey, I had OrangeFox Recovery and tried to install TWRP from within the OrangeFox by flashing it in the recovery parition but somehow the TWRP file was corrupted even though it showed successful but when I restarted my mobile it automatically opens the fastboot mode and now the situation is as follows:
-No recovery installed on the phone
-No Operating System installed on the phone (because I was installing TWRP to install a ROM)
-No USB Debugging enabled because I didn't know that I would fall into this situation
-No matter what combination I do, it takes me to the fastboot mode and doesn't do anything else.
Now I have installed the Mi Flash Tool along with its drivers but it doesn't show my device in the list even the windows make the connected sound but I think because USB debugging is not enabled it doesn't show it in the list of devices to flash to. Please tell me if their is anyway I can get my mobile back to normal (I have the original fastboot rom from official website) but the only problem I guess is the USB debugging.Thanks
{
"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"
}
do you have bootloader unlocked
can you use “fastboot flash twrp.img” or “fastboot boot twrp.img” by any chance in fastboot, if no, what is the error code
LR7875 said:
can you use “fastboot flash twrp.img” or “fastboot boot twrp.img” by any chance in fastboot, if no, what is the error code
Click to expand...
Click to collapse
hey buddy thanks for your help, I had my bootloader unlocked and I did it, I now flashed orangefox recovery using fastboot and I can use the recovery to install the ROM I want, However there is a problem that the last ROM I had was very secure and private rom (Calyxos) which encrypted the data so I am not able to wipe data. Tell me if you have any fix and once again thanks.