Bricked Mate 9. Plz help - Huawei Mate 9 Questions & Answers

I deleted my bootloader. Whatever rom I flash it's just went into bootloop and when it boot the second time it boot into Huawei erecovery. My model is mha L29 cc636. I used to run on Android 8.0. Plzzz help

Try typing "fastboot oem relock (your phone's unlock code)" but this method will factory reset your device.

okizen said:
Try typing "fastboot oem relock (your phone's unlock code)" but this method will factory reset your device.
Click to expand...
Click to collapse
Fastboot won't work since I deleted my bootloader. I couldn't get into fastboot mode.

hmm.....I didn't;t know you could delete the bootloader.

If your phone still goes to eRecovery, then you couldn't have deleted your bootloader. (Fastboot is the stage 2 boot loader, which loads the various other partitions for startup, boot or kernel + ramdisk for normal, recovery or kernel + recovery_ramdisk for recovery, and erecovery or erecovery_kernel + erecovery_ramdisk for eRecovery.)
In any case:
Power off
Hold volume down while plugging into computer.
That should start up fastboot.

Related

How to resolve boot loop problem on android PumpKinx 10.1" tablet

I've android PumpKinx 10.1 tablet with 5.1 Lollipop android os.
I did take backup of its stock recovery image.
Since there is no custom recovery image for this device I tried to flash it with twrp recovery image. But after running below command, device goes into bootloop. I've tried many methods but no success.
fastboot flash:raw boot twrp.img
Any help would be highly appreciated. Thanks in advance.
maybe u have locked bootloader. First turn on oem unlock in developer options, then reboot in bootloader and type
Code:
fastboot oem unlock
Then confirm acion in the tablet whit volume up, then the bootloader now is unlocked.
Note: The tablet get soft reset. Make backup first.
Then try flash the recovery
xdedeone said:
maybe u have locked bootloader. First turn on oem unlock in developer options, then reboot in bootloader and type
Code:
fastboot oem unlock
Then confirm acion in the tablet whit volume up, then the bootloader now is unlocked.
Note: The tablet get soft reset. Make backup first.
Then try flash the recovery
Click to expand...
Click to collapse
Do you understand boot loop or not? First of all fastboot is already unlocked otherwise how I will be able to run above command and since my device is in boot loop then how can I go to developer option?
chitrang200889 said:
I've android PumpKinx 10.1 tablet with 5.1 Lollipop android os.
I did take backup of its stock recovery image.
Since there is no custom recovery image for this device I tried to flash it with twrp recovery image. But after running below command, device goes into bootloop. I've tried many methods but no success.
fastboot flash:raw boot twrp.img
Click to expand...
Click to collapse
Just send them an email asking for stock firmware with flash tool, along with the purchase bill..
Or if it still has warranty, just go to the service center and say something like you over-charged the phone a complete night & since then it's not working and claim warranty..
Have you tried to wipe the cache partition or even factory reset???

Can't unlock bootloader - boot to OS

Ehy guys im having some trouble with my OPO.
First of all i can't boot to the OS, it just stuck in bootloop, and recovery is not accessible, but i can use fastboot.
Ive already used the MSM8974 tool, but after the flash the device is still stuck in bootloop.
I can't even unlock the bootloader, if i try the fastboot command "fastboot oem unlock" it just reboot and nothing happens.
Do you have some advice to exit this situation?? Ty for the replies

Nexus 5 Bootloop, Bootloader locked, No recovery, No root, No Emergency Mode...Help!!

Ive been asked by a friend of mine to fix his nexus 5 that is stuck on a Bootloop, I've opened it up to have a look at the power button and that wasn't the problem, the device has not been rooted, the Bootloader is locked, there is no emergency mode and there is no recovery. I am however able to access fastboot and when I try unlocking via fast boot it does unlock but then requires a full reboot and as I've said before this cannot happen because of the Bootloop.
Any suggestions!?!?!?!
After unlocking the bootloader, does the bootloader relock itself? If it does, the memory chip is damaged and requires a replacement motherboard.
I've had this problem when I corrupted my recovery by using FlashFire and my bootloader was locked. Though I was able to restore my device using Fastboot. I had unlocked my device and instead of flashing the stock recovery when unlocking the bootloader I had flashed the Team Win Recovery Project recovery and when I tried to boot up to TWRP recovery it would stay for a couple of second displaying that it couldn't wipe the data partition and then reboot me back into bootloader mode. I fixed that when trying out the following steps:
1= Download the latest firmware of the device found Here .
2= Boot the device to Fastboot mode (aka Bootloader mode) plug the device in and unlock the bootloader (of coarse confirm when asked by the device).
3= After seeing that the device has stopped wiping data indicated the text "wiping..." in the very bottom of the specifications in the Fastboot Bootloader REBOOT THE DEVICE IN FASTBOOT BOOTLOADER MODE by navigating using Volume buttons to scroll down and highlight the option "Reboot Bootloader" and then pressing the Power button.
4= Using the provided scripts for Windows , Mac and Linux flash the device with the firmware.
VERY IMPORTANT: WHEN YOU SEE THAT IT IS FLASHING "userdata" and after that "cache" HOLD DOWN THE VOLUME DOWN BUTTON THIS WILL FORCE THE DEVICE INTO FASTBOOT BOOTLOADER MODE.
5= When you see that the device is in the Fastboot Bootloader mode scroll down (again using volume buttons) and highlight "Recovery Mode" then boot into Recovery and it should automatically start wiping the ("userdata" partition) Data once more that the bootloader said when it displayed the "wiping..." message after being unlocked.
If not wipe data factory reset the device manually by using the recovery and reboot to the system.
Optional: 6= IF the device has successfully booted up power it back down and lock the bootloader again using the fastboot tool additionally before locking the bootloader you can reset the warranty tamper flags.
This tutorial explains in detail how to flash a firmware to the Nexus 5 and shows how to restore the tamper flags.
I hope that I helped in some way.
audit13 said:
After unlocking the bootloader, does the bootloader relock itself? If it does, the memory chip is damaged and requires a replacement motherboard.
Click to expand...
Click to collapse
Yes after unlocking Bootloader and restarting the device into the Bootloader it relocks and I'm back at square one
The motherboard needs to be changed. I recommend looking for a used Nexus 5 with a smashed screen and a working motherboard as this may easier than trying to find a new motherboard.
jivvak said:
I've had this problem when I corrupted my recovery by using FlashFire and my bootloader was locked. Though I was able to restore my device using Fastboot. I had unlocked my device and instead of flashing the stock recovery when unlocking the bootloader I had flashed the Team Win Recovery Project recovery and when I tried to boot up to TWRP recovery it would stay for a couple of second displaying that it couldn't wipe the data partition and then reboot me back into bootloader mode. I fixed that when trying out the following steps:
1= Download the latest firmware of the device found Here .
2= Boot the device to Fastboot mode (aka Bootloader mode) plug the device in and unlock the bootloader (of coarse confirm when asked by the device).
3= After seeing that the device has stopped wiping data indicated the text "wiping..." in the very bottom of the specifications in the Fastboot Bootloader REBOOT THE DEVICE IN FASTBOOT BOOTLOADER MODE by navigating using Volume buttons to scroll down and highlight the option "Reboot Bootloader" and then pressing the Power button.
4= Using the provided scripts for Windows , Mac and Linux flash the device with the firmware.
VERY IMPORTANT: WHEN YOU SEE THAT IT IS FLASHING "userdata" and after that "cache" HOLD DOWN THE VOLUME DOWN BUTTON THIS WILL FORCE THE DEVICE INTO FASTBOOT BOOTLOADER MODE.
5= When you see that the device is in the Fastboot Bootloader mode scroll down (again using volume buttons) and highlight "Recovery Mode" then boot into Recovery and it should automatically start wiping the ("userdata" partition) Data once more that the bootloader said when it displayed the "wiping..." message after being unlocked.
If not wipe data factory reset the device manually by using the recovery and reboot to the system.
Optional: 6= IF the device has successfully booted up power it back down and lock the bootloader again using the fastboot tool additionally before locking the bootloader you can reset the warranty tamper flags.
This tutorial explains in detail how to flash a firmware to the Nexus 5 and shows how to restore the tamper flags.
I hope that I helped in some way.
Click to expand...
Click to collapse
Thanks for the suggestion but I've tried this already and it doesn't work because when I unlock the bootloader and reboot into the Bootloader it locks itself again making impossible to flash the system image

boot loader

when i boot up my phone in get me to bootloader directly and when i press the press start up it shows me the bootloader is unlocked sign ....
so dose anyone knows whats the wrong with my phone ...
Phone: moto g 2015
recovery : twrp
system : there is no system
22trika said:
when i boot up my phone in get me to bootloader directly and when i press the press start up it shows me the bootloader is unlocked sign ....
so dose anyone knows whats the wrong with my phone ...
Phone: moto g 2015
recovery : twrp
system : there is no system
Click to expand...
Click to collapse
Which part? the going immediately to the bootloader? THat is easy, you tried flashing a ROM and never cleared fb_mode... In the bootloader use fastboot and use this command command:
fastboot oem fb_mode_clear
and it should now boot normally without starting the bootloader each time.
For the bootloader unlock image, flash a logo.bin that is designed to cover it... you can't make it go away any other way even if you relock the bootloader
"system : there is no system"? Well, flash something.

Nexus Stuck on Google Logo

Hello guys, I dont know whats happening with my Nexus 5 right now. Its stuck on Google logo which appears during restarting of the phone.
I have tried everything. I try to go into recovery it dosent work. I tried changing it to CWM from TWRP still it stays TWRP i get errors while flashing .bat files like (error: failure to write). Please help been stuck on this since past 72hours. Any help to resolve this issue is appreciated. Thanks :crying::crying::crying:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
OEM can be locked and unlocked. But the only problem now is i cannot override the previous partitions as there is an error "failed to write" i dont understand why is this happening this is also the reason i cannot get into my recovery as when i enter recovery it gets stuck for some reason.
audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
Also what does flash 4.4 mean? Sorry new to this!
audit13 said:
If the bootloader is unlocked, relock the bootloader and reboot into fastboot mode. If the bootloader unlocks itself, the internal memory is probably damaged. If the bootloader remains locked, unlock it and flash 4.4 using fastboot commands.
Click to expand...
Click to collapse
Also i tried to erase partitions manually but i always got an error as (remote: failed to erase partition)
Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?
audit13 said:
Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?
Click to expand...
Click to collapse
It goes back to unlocked
audit13 said:
Let's start with the bootloader.
Boot into fastboot mode, lock the bootloader, reboot into fastboot mode. Does the bootloader stay "locked" or does it go back to say "unlocked"?
Click to expand...
Click to collapse
Do you have discord or teamspeak or any other apps to chat directly?
NeXussssssssss said:
It goes back to unlocked
Click to expand...
Click to collapse
The internal memory may be damaged.
You might want to try this: https://forum.xda-developers.com/google-nexus-5/general/how-fixed-bricked-nexus-5-corrupted-t2903593
audit13 said:
The internal memory may be damaged.
You might want to try this: https://forum.xda-developers.com/google-nexus-5/general/how-fixed-bricked-nexus-5-corrupted-t2903593
Click to expand...
Click to collapse
I tried the 1st step by overwriting twrp with cwm dint work. Also ADB isnt connected. I tried to but just fastboot works.
I recommend flashing stock 4.4 using fastboot commands.
Stock ROMs are here: https://developers.google.com/android/images
audit13 said:
I recommend flashing stock 4.4 using fastboot commands.
Stock ROMs are here: https://developers.google.com/android/images
Click to expand...
Click to collapse
I tried flashing new roms it says failure to write to cache,boot,recovery everything fails!
There is no way to erase partitions as it fails!
I would say the internal memory is damaged and will require a motherboard change.

Categories

Resources