Hello, my realme 3 pro is stuck in bootloop, I am able to go into fastboot, but unable to write anything using it.
How it happened:
I was installing magisk using the magisk app. I rebooted my phone from the magisk app and the phone got stuck on android screen.
What I have tried:
I used vol up + power button then volume down + power button to go into fastboot. On my PC using fastboot devices I can see my device but whenever I try to execute any command such as
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
It says sending 'recovery' (32056 KB) but takes about a minute before saying FAILED (Write to device failed (no link)).
Can anyone please help me.
Thank You
im facing the same problm .
I fixed the issue be using adb on an older computer with usb 2.0 you can try the same
tell me the complete process
i ve deleted my realme vender and other data files in twrp now im stuck on bootloop of realme 3 pro...
but twrp recovery is loading..
how to fix that please help me
Sparta9000 said:
Hello, my realme 3 pro is stuck in bootloop, I am able to go into fastboot, but unable to write anything using it.
How it happened:
I was installing magisk using the magisk app. I rebooted my phone from the magisk app and the phone got stuck on android screen.
What I have tried:
I used vol up + power button then volume down + power button to go into fastboot. On my PC using fastboot devices I can see my device but whenever I try to execute any command such as
It says sending 'recovery' (32056 KB) but takes about a minute before saying FAILED (Write to device failed (no link)).
Can anyone please help me.
Thank You
Click to expand...
Click to collapse
You should have to install realme ui recovery and vander 3.5gb file from official. Than try official method for installation of twrp ozip supported recovery. And flash any rom and mjsik that you want. In case you accidently delete your vander?
Or
But may be your recovery file is corrupted ?
So I advise you to install twrp from official website .
That will be approx 60mb.
Related
Hey sorry but I am posting this because even after a lot of research I couldn't find a proper solution to this problem....
I am on twrp recovery version 2.1.3 and to upgrade to 2.5.0.0 I used the goo.im app but even after the message showing that recovery was flashed successfully, when I reboot into recovery I still see the 2.1.3 twrp only....
So I tried flashing it with terminal emulator but it didn't work..... This error shows up every time....
failed scanning partitions failed with error : - 1
I tried putting the .img file in the root folder as well but it didn't work.... I tried naming the root of sdcard as storage/emulated/legacy, storage/emulated/0, /sdcard, etc but it keeps on giving this error every single time!
Nowhere could I find a solution for this problem so please please PLEASE! HELP!
:crying: :crying:
flashing recovery the fastboot way
Dwait said:
Hey sorry but I am posting this because even after a lot of research I couldn't find a proper solution to this problem....
I am on twrp recovery version 2.1.3 and to upgrade to 2.5.0.0 I used the goo.im app but even after the message showing that recovery was flashed successfully, when I reboot into recovery I still see the 2.1.3 twrp only....
So I tried flashing it with terminal emulator but it didn't work..... This error shows up every time....
failed scanning partitions failed with error : - 1
I tried putting the .img file in the root folder as well but it didn't work.... I tried naming the root of sdcard as storage/emulated/legacy, storage/emulated/0, /sdcard, etc but it keeps on giving this error every single time!
Nowhere could I find a solution for this problem so please please PLEASE! HELP!
:crying: :crying:
Click to expand...
Click to collapse
Hi,
You may be able to wipe your tears .This worked for me on the Huawei Ascend y300 which was rooted and had its bootloader unlocked first. Since I got a similar error to you using flash_image these steps might work for you too:
disconnect usb cable from phone
Boot into the bootloader mode (usually power and volume down).
reattach usb cable to phone
Download fastboot
get a dos prompt
navigate to the fastboot directory
do these commands followed by pressing enter:
fastboot devices
(your device should be listed)
copy and paste your recovery.img into the fastboot folder in windows.
fastboot flash recovery recovery.img
fastboot reboot.
Now make sure your phone boots normally.
Now power it off. Hold down volume up while pressing power, it should put you in your custom recovery.
Keiichicom.
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
Download and install "minimal adb and fastboot"
Just type on the command line without pressing Enter:
Code:
[COLOR="Blue"][B][I]fastboot [COLOR="Plum"][STRIKE]boot[/STRIKE][/COLOR] recovery.img[/I][/B][/COLOR]
you should place your recovery image file in "minimal adb and fastboot" directory
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds - in my case the phone is restarting)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery command line
Click to expand...
Click to collapse
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
i must extract "flashrec TWRP v2.7.1.2 this file on phone or where? can u explain a
agsao said:
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
Click to expand...
Click to collapse
Please explain me. idont know how to do
prxzero said:
Please explain me. idont know how to do
Click to expand...
Click to collapse
What Is your problem?
Is your phone stuck on logo screen? what were you doing to get the problem??
agsao said:
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
Click to expand...
Click to collapse
Hi..
i just try to install CM12 to this device, with twrp 2.8.6.1 from master lie.
First time its working well, but suddenly this device restarting and stuck on the "lenovo" logo screen.
Every time i presh power button always restarting (like ON-OFF-ON-OFF forever).
when i connectto charger also restarting....
i cant go to twrp using vol- & pwr, when i use minimal adb cannot detected..
Can you help me...
Help
hi.
i try to do something to enable notifications on my lenovo vibe z.
i install new rom from needrom, but it didn't help. So i try to install other one, but i wipe my phone and restart without installed system.
Now when i go to twrp have just flashing teamwin logo, and only when phone is in this mode i can communicate through adb
i have checked many forums and try allot stuff to fix it but nothing works
Please Help!
U are not alone I also in same stage
Is there any one plz help
As long as the hardware is not physically broken, your K910 is unbrickable
http://www.teamsuperluminal.org/unbrick-lenovo-k910/
I followed the guide to revive my K910. You can refer to this forum post in which I documented my experiences:
http://www.teamsuperluminal.org/forums/topic/flash-back-to-lenovo-stock-just-temporarily/
nowbo said:
Is there any one plz help
Click to expand...
Click to collapse
Thanks for your reply
I will apply today. Hope for the best.
Will inform you as soon as this applied..
Have you fixed that problem?
Still at same stage
EcoDan said:
Have you fixed that problem?
Click to expand...
Click to collapse
Hi,
I am still on same stage (Black screen with lenovo logo). Try several ways but can't get out of this. Please help me If any one successful to startup this device or can get on the boot screen where I can do factory reset.
---------- Post added at 07:25 AM ---------- Previous post was at 07:21 AM ----------
wxppro said:
http://www.teamsuperluminal.org/unbrick-lenovo-k910/
I followed the guide to revive my K910. You can refer to this forum post in which I documented my experiences:
http://www.teamsuperluminal.org/forums/topic/flash-back-to-lenovo-stock-just-temporarily/
Click to expand...
Click to collapse
I Try this method but can't get out from that black screen ( Lenovo logo and powered by android)
My device is Lenovo Vibe shot Z90a40. I also try with boot unlock-er but nothing sitll work. So its about 20 days can't use my Lenovo Vibe Shot.
Please help me If you know how to get out of this issue..
Thanks
[/COLOR]
I Try this method but can't get out from that black screen ( Lenovo logo and powered by android)
My device is Lenovo Vibe shot Z90a40. I also try with boot unlock-er but nothing sitll work. So its about 20 days can't use my Lenovo Vibe Shot.
Please help me If you know how to get out of this issue..
Thanks[/QUOTE]
You need to carefully follow each steps in the method - if you short that magic pin and then connect the USB cable (with battery disconnected), your computer will report seeing the device at either COM port 9008 or 9006. Then you can download the factory image to revive the phone. Of course you need to have the right device driver installed. Like I said, as long as the hardware is not broken, this procedure will succeed for sure.
I love you man!
I love you man! I wish you all the happiness and wealth!:victory::victory::victory::angel::angel::highfive::highfive:
Hi,
I'm new here, so please excuse me if I am posting in the wrong category.
So I tried to root my Doogee F7 (not the pro version) using fastboot and TWRP, and it resulted in a sort of bootloop where it says:
Code:
Orange State
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And then it restarts and gives the same message again. This loop has been going on for some time and I can't stop it because the phone has a non-removable battery and I have tried every possible combination of buttons (i.e. Power + Volume Down + Volume Up).
The process I used in my attempt to root was as following:
1. I used
Code:
adb reboot bootloader
to go into fastboot. (I already set up everything like USB debugging and OEM unlocking in the developer options)
2. I then used
Code:
fastboot oem unlock
and pressed Volume Up to unlock the bootloader. All was successful.
3. I then tried to flash TWRP to recovery and I believe this is where everything went wrong. I flashed it using
Code:
fastboot flash recovery recovery.img
and it was successful, according to the command prompt:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery "C:\Users\momen\Downloads\recovery (1).img"
target reported max download size of 134217728 bytes
sending 'recovery' (12832 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.213s]
finished. total time: 0.779s
4. After it finished I used
Code:
fastboot reboot
to reboot the phone and that's when it got stuck.
At the moment I am just letting my battery run out, as I have no other way of turning off the phone, and neither adb nor fastboot is working.
I don't really know if my device was even supported, but I followed the instructions on various websites stating that I should first unlock my bootloader, then flash TWRP, then flash superSU onto it, and my phone would be rooted. I used the latest TWRP image, and I think that was where I went wrong. Is there anything I can do to get my phone to work again?
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
solartediego said:
Hey! i´m sorry for your phone, can you tell me any updates, is it fixed now? what happened? i am about to do the same process to root my Doogee F7 and i´m very worried that my phone gets bricked, so please, i need your recommendations.
I hope everything is alright with your phone.
Click to expand...
Click to collapse
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Hello there. I suggest that you use "fastboot boot recovery.img" than using "fastboot flash" if you are not sure if the custom recovery works (or if you just want to test/try it). In this way, you'll just boot the custom recovery temporarily (and your stock recovery is still in tacked).
For rooting your device, first you'll need a working custom recovery for your device (you used TWRP, very first if it works or compatible with your device).
Insyder28 said:
Ah yes, sorry for not updating. I managed to connect my phone to my PC again using the flash tool and then I could flash the original ROM back onto it. I found the ROM by Googling for a bit tho I dont have a link. Be aware that if you do this, it basically factory resets your phone, locking your bootloader again and all. If you do manage to root your phone please contact me as I still have not managed to do so.
Edit: This process of flashing back your ROM always works as long as your phone powers on, so don't worry too much about bricking your phone. I think I've bricked my phone over 20 times trying to root it, and it worked every single time.
Click to expand...
Click to collapse
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
ciubsy2004 said:
Hi.How you actually managed to connect your phone to PC using flash tool if you were in a bootloop and had no access to fastboot mode or recovery?
Click to expand...
Click to collapse
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
TheBidan said:
Im interested too in your process to flash TWRP again, as i am in the same boot loop than you with a Doogee S60. I´ve waited till the battery ended, but now flash tool doesn´t recognize my phone. If i charge the battery, i get a boot loop again..
Click to expand...
Click to collapse
I have managed to get the flash tool recognizing my phone.Had to keep pressed volume up,if i recall properly(or try volume down) before connecting usb cable to phone with flash tool opened and . It was a while ago though and i can't remember exactly which key was for sure. Hope this helps
Greetings…
W̶i̶l̶l̶ ̶d̶o̶n̶a̶t̶e̶ ̶2̶0̶ ̶U̶S̶D̶ ̶t̶o̶ ̶w̶h̶o̶e̶v̶e̶r̶ ̶c̶a̶n̶ ̶f̶i̶x̶ ̶m̶y̶ ̶p̶h̶o̶n̶e̶ Fixed and contacted both Bordo_Bereli51 and Ante0.
My Huawei Mate 10 got in a bootloop after installing Xposed Framework
It was on Android Oreo 8.0 rooted and bootloader unlocked
Lock state info:
FB LockState: LOCKED
USER LockState: UNLOCKED
Leaving the device to boot normally: HUAWEI logo then reboots.
Vol up+power: eRecovery mode … doesn’t work (wiped data and cache .. tried to download firmware through wifi .. nothing works). ... then tried this method it worked while downloading the firmware .. but after verifying the firmware then installing it when it gets from 0% to 1% it fails and a red exclamation mark appears. :crying:
Vol down + power: fastboot: always get: FAILED (remote: Command not allowed) ). even though the bootloader is supposed to be unlocked. :crying:
Vol up and down: download mode .. on USB: stuck at 5% … without USB connection to computer: nothing happens (a red exclamation mark appears).
The device has an SD card slot: I tried placing the UPDATE.APP in dload folder and pressed both volume buttons but nothing appeared .. did I do something incorrectly?
Here are more info:
product-model: ALP-L29
vendorcountry: hw/meafnaf
build-number: System 8.0.0.38(0310)
fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :ALP-L29 8.0.0.128(C185)
Please help.
thanks in advance
====================
FIXED: Thanks to Bordo_Bereli51 who wrote this post and thanks for Ante0 for recommending DC Pheonix and for taking a lot of his time explaining a lot of things to me privately. contacted both as promised.
How I fixed it (credits to Bordo_Bereli51 for the guide .. I only modified it a bit and added some info from my experience):
1- I purchased a 19 euro -3 days pass for DC Pheonix.
2- Download Firmware Finder and click the "Common Base" tab, then download a FullOTA-MF firmware (all 3 files) which is approved for installation ( I copied the "changelog" link and pasted it in the 6th icon at the top "Firmware Checker" and it returned "Firmware approved for install" I' was not able to repack other non approved firmwares).
3- extract UPDATE.APP from update.zip
4- run DC Phoenix program .. tap the "Standard" button in Update mode .. select "update" and choose the UPDATE.APP you just extracted.
5- let it flash everything successfully then redo step 4 again.
6- Here's the trick before it flashes anything ... as soon as you see "utilizing backdoor" (or something like that) open Task Manager and force close DC Phoenix (it has to be BEFORE flashing anything, otherwise you might get errors like:
"error: exec '/system/bin/sh' failed: No such file or directory"
and AFTER utilizing backdoor (so you can use fastboot commands)
7-Download HWOTA8_Mate10 , place the 3 files you downloaded in step 2 in the "repack" folder, and rename "update_data_full_public.zip" to "update_data_public.zip" and "update_full_*ALP-L29*_hw_*meafnaf*.zip" to "update_all_hw.zip". Then run "repack.bat" and wait for it to finish.
8- run "ota.bat" in "ota" folder.
9- When it flashes the recovery_ramdisk and kernel plug your usb cable out and Reboot to recovery by pressing volume up + power button
10- When the phone is in recovery now ADB works (in case you need to do things manually).
11- When this process also finishes, the command center will tell you to press enter, so it boots to erecovery, which will flash the files.
12- Now your phone is unbricked after the flash.
Do not forget to do factory reset by pressing again at boot: (power + volume up) and selecting (factory reset).
After boot allow (OEM Unlock) under (developer settings) or otherwise the FRP will still be locked but the phone will work.
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Dolev234786 said:
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Click to expand...
Click to collapse
I have the same problem.
Dolev234786 said:
if someone will fix it can u tell me cause i have the same problem
---------- Post added at 06:58 AM ---------- Previous post was at 06:58 AM ----------
wait do u have twrp?
Click to expand...
Click to collapse
No, I don’t have TWRP.
hero3210 said:
No, I don’t have TWRP.
Click to expand...
Click to collapse
What does fastboot mode say, unlocked on both phone and frp?
ante0 said:
What does fastboot mode say, unlocked on both phone and frp?
Click to expand...
Click to collapse
yes both are unlocked
Dolev234786 said:
yes both are unlocked
Click to expand...
Click to collapse
Post input & output when you try to flash using fastboot
ante0 said:
Post input & output when you try to flash using fastboot
Click to expand...
Click to collapse
My device used to be bootloader unlocked
But I always get "FAILED (remote: Command not allowed)" for any fastboot command
I searched here and a lot of people had the same issue and they fixed it by relocking then re-unlocking the bootloader
I tried that .. relocked successfully but now I cannot unlock it again.
This is the current info from info.bat:
Lock state info:
FB LockState: LOCKED
USER LockState: RELOCKED
in fastboot mode it says:
PHONE Relocked
FRP Lock
=====
Input and output of fastboot:
fastboot flash recovery_ramdisk SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'recovery_ramdisk' 1/7 (460797 KB)...
OKAY [ 3.650s]
writing 'recovery_ramdisk' 1/7...
FAILED (remote: Command not allowed)
finished. total time: 3.661s
Thanks for taking time to reply
hero3210 said:
My device used to be bootloader unlocked
But I always get "FAILED (remote: Command not allowed)" for any fastboot command
I searched here and a lot of people had the same issue and they fixed it by relocking then re-unlocking the bootloader
I tried that .. relocked successfully but now I cannot unlock it again.
This is the current info from info.bat:
Lock state info:
FB LockState: LOCKED
USER LockState: RELOCKED
in fastboot mode it says:
PHONE Relocked
FRP Lock
=====
Input and output of fastboot:
fastboot flash recovery_ramdisk SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'recovery_ramdisk' 1/7 (460797 KB)...
OKAY [ 3.650s]
writing 'recovery_ramdisk' 1/7...
FAILED (remote: Command not allowed)
finished. total time: 3.661s
Thanks for taking time to reply
Click to expand...
Click to collapse
You need to enable OEM unlock in Settings-developer options. At least frp needs to say unlock else you won't be able to unlock or flash, at least not for free.
But since you can't boot you're pretty much limited to use dc unlocker/dc phoenix
ante0 said:
You need to enable OEM unlock in Settings-developer options. At least frp needs to say unlock else you won't be able to unlock or flash, at least not for free.
But since you can't boot you're pretty much limited to use dc unlocker/dc phoenix
Click to expand...
Click to collapse
Thanks for the reply
Do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
hero3210 said:
Thanks for the reply
Do you recommend that I use dc unlocker or dc pheonix or FunkyHuawei?
Click to expand...
Click to collapse
Dc phoenix is what you'll need, Mate 10 is not supported in DC Unlocker. (Though DC Unlocker made DC Phoenix)
You'd just want it to flash stock anyway.
And it's cheaper than FunkyHuawei... FH "only" cost 1 credit to flash, but minimum to buy is 5 credits which is $41.
FH is easier though as you'd only need to setup DNS, but it's up to you
HCU/DC Phoenix pass for 3 days is €19, and then you have unlimited usage.
If you need further help you can find me at the telegram group https://t.me/HuaweiMate
as it's easier to do it live than through messages.
There is a "DC Phoenix repair tutorial" if you google it, use Method 1. Basically you just download the firmware update zip you're on now (and hw data zip) from http://pro-teammt.ru/firmware-database/ then extract update.app from it and select it in Phoenix, then extract update.app from hw data zip and select it as customization.
Alternatively you can downgrade to factory build using images from DC Phoenix (the build your phone came with) then update from there when you have a booting phone.
Thank you sooo much man. I really appreciate your help.
What version of Xposed frameworks did you install I have beta 4 working fine on my mate 10 pro.
tokoam said:
What version of Xposed frameworks did you install I have beta 4 working fine on my mate 10 pro.
Click to expand...
Click to collapse
yeah the bootloop was fixed in beta4 (original comment by dev) which wasn't officially released to the channel when I installed it, so I didn't know about it until I got the bootloop.
Anyways, I just managed to fix my issue. I'll post about it now.
ante0 said:
What does fastboot mode say, unlocked on both phone and frp?
Click to expand...
Click to collapse
what would happens if it says unlock on frp? i cant load twrp i have flashed many times but i does not take it.
I bricked my Huawei Mate 10 too
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Carnage! said:
Please help.. I also bricked my Huawei Mate 10 ALP-L29C636...
I installed the EMUI 9.0 on my device using the HWOTA8_Mate10 method which was successful. The EMUI 9.0 ROM was from FirmwareFinder: ROM version ALP-L29C636E2R1P8B108-log (9.0.0.108). I didn't have any issues at all but since Huawei Mate 10's EMUI 9.0 is still in Beta, I decided to switch back to the stable EMUI 8.0.
Here's where the problem started... Since I want to downgrade, I went ahead and downloaded the 3 needed files (update.zip, update_all_hw, update_data_public) from FirmwareFinder: ROM version ALP-L29C636B143 (8.0.0.143). I fired up HWOTA8_Mate10 and started the installation process. The first step was to boot to fast boot and then plug the device, after that, the software asked me to unplug the device and press volume+ and power button but the device won't boot to recovery anymore. The device is now stuck at "Your device is booting now..." I tried rebooting the device but it won't work. Tried to go to eRevovery to wipe cache/factory reset but it will go back to "Your device is booting now..." page. I tried reinstalling the recovery.img via fastboot and tried to boot to recovery mode again but it won't work anymore. I believe my device is now soft bricked . I can still boot to fastboot, I even tried fastboot flash system system.img which was successful but the device still won't boot. Please help how to recover my device. I think I went too far and now I don't know how to fix this issue.
Click to expand...
Click to collapse
Spamming every thread won't help you fix your issue.
Pretoriano80 said:
Spamming every thread won't help you fix your issue.
Click to expand...
Click to collapse
I apologize. I panicked since I don't know what to do. I will continue on the thread which I received a response.
I was using Google experience 10 and twrp 3.2.2.0 but suddenly my device switch off and when try to start it shut off after asus logo, tried twrp it was stuck on teamwin logo , then I try to flash twrp and new rom it push this msg "failed (remote: partition is write protected)"
Please help
No response
It's look like my phone is now useless, no one has any solution, even service center is in brain dead situation
Rahuljha25 said:
It's look like my phone is now useless, no one has any solution, even service center is in brain dead situation
Click to expand...
Click to collapse
Try to ask or find the solution here
https://forum.xda-developers.com/asus-zenfone-max-pro-m1
Rahuljha25 said:
I was using Google experience 10 and twrp 3.2.2.0 but suddenly my device switch off and when try to start it shut off after asus logo, tried twrp it was stuck on teamwin logo , then I try to flash twrp and new rom it push this msg "failed (remote: partition is write protected)"
Please help
Click to expand...
Click to collapse
If you can access the phone by means of ADB, and if you have phone's Stock ROM ( a .ZIP-file ) at your fingertips, then you can try to re-flash phone's stock ROM via ADB's subcommand "sideload"
Code:
adb devices
adb reboot sideload
adb sideload <FULL_PATH_TO_STOCK_ROM_ON_WINDOEWS_PC>
adb reboot
to bring back phone to its original state.