Today my son came to me with a Xiaomi Mi A3, it was in fastboot mode so I thought to press volume down key and power key, but it went straight back to fastboot mode. I asked him what he had done and he told me he had tried to root his phone. I went to my laptop and installed adb and looked at it and somehow he had locked everything, bootloader and critical. Is there any way I can fix this?
Zelyr said:
Today my son came to me with a Xiaomi Mi A3, it was in fastboot mode so I thought to press volume down key and power key, but it went straight back to fastboot mode. I asked him what he had done and he told me he had tried to root his phone. I went to my laptop and installed adb and looked at it and somehow he had locked everything, bootloader and critical. Is there any way I can fix this?
Click to expand...
Click to collapse
Requirements :
adb drivers installed
Mi Flash Tool
Your device's fastboot rom
Procedure :
Put your phone in fastboot mode
Connect your phone with pc
Make sure adb drivers are installed
Open Mi flash tool application in your pc
Select the fastboot rom folder of your device
Choose "clean all" option from the bottom - DO NOT CHOOSE "CLEAN ALL AND LOCK"
And click flash
Here's a video for visual reference (sorry it's in hindi) - https://youtu.be/rJePUW8Xczw
Hope you make it, Best of luck !
And by the way, after that I think you should install a custom rom like Pixel Experience or EvolutionX because default stock android kinda sucks.
Mukesh Sharma 36 said:
Requirements :
adb drivers installed
Mi Flash Tool
Your device's fastboot rom
Procedure :
Put your phone in fastboot mode
Connect your phone with pc
Make sure adb drivers are installed
Open Mi flash tool application in your pc
Select the fastboot rom folder of your device
Choose "clean all" option from the bottom - DO NOT CHOOSE "CLEAN ALL AND LOCK"
And click flash
Here's a video for visual reference (sorry it's in hindi) -
Hope you make it, Best of luck !
And by the way, after that I think you should install a custom rom like Pixel Experience or EvolutionX because default stock android kinda sucks.
Click to expand...
Click to collapse
I've been using Pixel Experience, but there have been a lot of random rebooting that have made me flash A10 stock again.
If you happen to use EvolutionX, are you having reboot issues or anything like that?
Thank you, preliminary!
fetaiharbin said:
I've been using Pixel Experience, but there have been a lot of random rebooting that have made me flash A10 stock again.
If you happen to use EvolutionX, are you having reboot issues or anything like that?
Thank you, preliminary!
Click to expand...
Click to collapse
Yes I'm using EvolutionX and I don't see any random reboots.
Mukesh Sharma 36 said:
Requirements :
adb drivers installed
Mi Flash Tool
Your device's fastboot rom
Procedure :
Put your phone in fastboot mode
Connect your phone with pc
Make sure adb drivers are installed
Open Mi flash tool application in your pc
Select the fastboot rom folder of your device
Choose "clean all" option from the bottom - DO NOT CHOOSE "CLEAN ALL AND LOCK"
And click flash
Here's a video for visual reference (sorry it's in hindi) - (url)
Hope you make it, Best of luck !
And by the way, after that I think you should install a custom rom like Pixel Experience or EvolutionX because default stock android kinda sucks.
Click to expand...
Click to collapse
The bootloader is locked though, so is the critical.
D:\Desktop\ADB>fastboot flashing unlock
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.004s
D:\Desktop\ADB>fastboot flashing unlock_critical
...
FAILED (remote: Flashing Unlock is not allowed
)
finished. total time: 0.003s
OEM-device info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.008s]
finished. total time: 0.010s
You need to use EDL mode, for which you need an authorized Mi Account - either use one of the paid online services or visit a service center.
Related
hey there!
i need some help here please!
i was trying to unlock my bootloader (using this guide) and it went all fine till step 17 (command "fastboot oem unlock-go"), it said i got no permission for unlocking. and now i'm stuck here. the only thing that works is fastboot mode. from there i can switch to adb using the reboot-to-edl-patch, but then i'm stuck again. device-manager shows device as usual (ports COM & LPT) and the red light is blinking, but command "adb devices" replies an empty list. tried "adb kill-server", replugging phone, rebooting computer, still the same.
so what can i do now?
thanks for helping!
Hi. You can install a fastboot rom in edl-mode with mi flash. I recomend a developer rom for this action. Then you can try the unofficial unlock from the start, but i recomend the official unlock.
Odatosz said:
Hi. You can install a fastboot rom in edl-mode with mi flash. I recomend a developer rom for this action. Then you can try the unofficial unlock from the start, but i recomend the official unlock.
Click to expand...
Click to collapse
sorry, forgot to say that miflash does not show the device after i selected the rom. i need to do something before i can flash via edl-mode. but what?
Make sure that you have the correct drivers installed on a 64bit machine, with driver signature off. And you cant get adb device list from there, so thats normal. Try to install the 7.1.8 fastboot rom that should work.
Well even m in a same situation.... as u said ur mobile is giving u red led blinks.. ..
And in device Manger ur fone is showed as Qualcomm 900E instead of 9008 and that's the reason adb couldn't list ur device
All u need to do is do a Google search - xiaomi deep flash cable
shetty_chadda said:
Well even m in a same situation.... as u said ur mobile is giving u red led blinks.. ..
And in device Manger ur fone is showed as Qualcomm 900E instead of 9008 and that's the reason adb couldn't list ur device
All u need to do is do a Google search - xiaomi deep flash cable
Click to expand...
Click to collapse
phone is showed as showed as Qualcomm 9008, and meanwhile i'm able to flash fastboot-rom again. still can't unlock though
AnF replies: FAILED: <remote: oem unlock is not allowed>
finished. total time: 0.016s
drivers are installed correctly, i'm working in signature-off-mode.
tried 7.1.8 rom, can't unlock that either..
maybe a stupid question, but anyway: phone had miui version 8 before i started trying to unlock.. is something wrong with that?
thanks for helping!
no1dev said:
phone is showed as showed as Qualcomm 9008, and meanwhile i'm able to flash fastboot-rom again. still can't unlock though
AnF replies: FAILED: <remote: oem unlock is not allowed>
finished. total time: 0.016s
drivers are installed correctly, i'm working in signature-off-mode.
tried 7.1.8 rom, can't unlock that either..
maybe a stupid question, but anyway: phone had miui version 8 before i started trying to unlock.. is something wrong with that?
thanks for helping!
Click to expand...
Click to collapse
There is no problem with miui 8. You just have to follow the steps from this post: [Tips and Tutorials] Redmi Note 3 [ SnapDragon ] - Unlock the BEAST in Seconds!!! . Just google it, because i cant post links here... Make a efs partition backup before you proceed! With a bad flash you can lose your IMEI like lots on the forum did... I would say to unlock your phone with the official unlock. Good luck!
no1dev said:
phone is showed as showed as Qualcomm 9008, and meanwhile i'm able to flash fastboot-rom again. still can't unlock though
AnF replies: FAILED: <remote: oem unlock is not allowed>
finished. total time: 0.016s
drivers are installed correctly, i'm working in signature-off-mode.
tried 7.1.8 rom, can't unlock that either..
maybe a stupid question, but anyway: phone had miui version 8 before i started trying to unlock.. is something wrong with that?
thanks for helping!
Click to expand...
Click to collapse
Odatosz said:
There is no problem with miui 8. You just have to follow the steps from this post: [Tips and Tutorials] Redmi Note 3 [ SnapDragon ] - Unlock the BEAST in Seconds!!! . Just google it, because i cant post links here...
Click to expand...
Click to collapse
en.miui.com/thread-253680-1-1.html
abihary said:
en.miui.com/thread-253680-1-1.html
Click to expand...
Click to collapse
There you go. Don't forget to read my edit from the other post!
Odatosz said:
There you go. Don't forget to read my edit from the other post!
Click to expand...
Click to collapse
tried that, but no success in unlocking. same reply as mentoined above (FAILED: <remote: oem unlock is not allowed>)
is there any other rom i could try to flash? not to unlock the bootloader afterwards, but to just unbrick my phone?
I would recomend to install a global developer rom for now. And unlock your bootloader with the official method.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
Just install a developer ROM like you did before. Then you can decide what to do next. I would recommend to unlock your bootloader officially if you want custom ROMs on your phone.
good news: i finally managed to unbrick it!
flashing the fastboot 7.1.8 rom, and then flashing the original emmc_appsboot.mbn file via fastboot:
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot reboot
during reboot holding volume-up + power and starting mi pc suite
..and suddenly it's unbricked!
so happy right now!
Glad to hear that.
no1dev said:
hey there!
i need some help here please!
i was trying to unlock my bootloader (using this guide) and it went all fine till step 17 (command "fastboot oem unlock-go"), it said i got no permission for unlocking. and now i'm stuck here. the only thing that works is fastboot mode. from there i can switch to adb using the reboot-to-edl-patch, but then i'm stuck again. device-manager shows device as usual (ports COM & LPT) and the red light is blinking, but command "adb devices" replies an empty list. tried "adb kill-server", replugging phone, rebooting computer, still the same.
so what can i do now?
thanks for helping!
Click to expand...
Click to collapse
The solution is here:
download the required files from the given link: [50mb]
https://mega.nz/#!1NhDTQoR!cP7vrchwswOfj3oHQ5saZ2d0JkcmunEn5pqyOcpZDoE
INSTRUCTIONS: [redmi note 3]
1. Get into fastboot mode. Charge the phone first. Hold the power button and the volume down button simultaenously.
2. If you can open your current rom, open developer options by clicking on the build no several times in the about phone menu in settings. and select allow oem unlocking and usb debugging.
3. if not leave it... go on and connect your phone to the PC while in fastboot mode.
BUT, before that: open Command prompt on your PC. (search it on the search box). right click on it and open it in administrator mode.
type in: bcdedit /set testsigning on
hit enter and restart your pc
(this is imp.)
4. open the zip file and extract the contents. open the boot edl mode folder and click the edl.bat file. allow it to run.
5. now screen will turn black, do not disturb it. Now flash the twrp by running flash twrp.bat from the 'flash TWRP' folder.
6. Now go to Unlock folder and run the unlock bootloader.bat file.
your phone will boot into the TWRP recovery mode automatically.
if it opens in chineese you select every tab and find the globe icon.
if the globe icon is found on any of the tab select it and change the language to ENGLISH.
wipe your system from the wipe tab:
Now download the latest CM13 SNAPSHOT BUILD ROM FOR YOUR REDMI:
https://download.cyanogenmod.org/get/kenzo-snapshot.zip
and GAPPS:
http://opengapps.org/?api=6.0&variant=mini
do select the arm 64 version and mini one.
download from your pc and copy it to micro sd card. enter this card into you phone and go to mount in twrp.
mount the micro sd card storage.
select the zip file on the micro sd card from the install tab on twrp and flash it.
now go back and flash open gapps zip file.
now REBOOT to system. everything will work fine....
I need serius help.... i dont know what the hell happens, i tryed to go in recovery mode while using a custom rom, and then the phone rebooted and keep doing that for ever. I cant boot the phone, i cant go to recovery mode, only thing i can do is going to fastboot mode... but then i'm stuck!
I tryed to:
-fastboot oem unlock > oem unlock is disabled
-fastboot oem device-info > Device tampered: true
Device unlocked: false
Charger screen enabled: false
Display panel:
console_enabled: 0
exec_console_unconsole: 0
-fastboot flash recovery recovery.img > Device not unlocked cannot flash or erase.
-fastboot boot recovery.img > Device not unlocked cannot boot.
-fastboot upgrade stockrom(oss3.1.4).zip >archive does not contain 'android-info.txt' , 'android-product.txt'(this last command im not even sure is right i just tryed).
-fastboot continue > again boot loop
it vibrates and then black screen, and again and again.
-fastboot flash:raw boot recovery.img > Device not unlocked cannot flash or erase.
-fastboot reboot > same as fastboot continue....
I need a way to unlock this ******* OEM or to boot into the system again to unlock it.. I mean i didnt do anything to the phone to broke like this! i was using the dirty unicorn v11.0 rom, pressed the power buttom, selected reboot recovery, and then this happend...
The only relevant thing that could also **** this that i know, is that this night i was using the phone, forgot it on and wake up finding the phone HOT as ****, i mean i couldn't even touch the front screen more that 2-3 sec, i turned it immediately off and tryed to cool it, maybe the heat ****** something up i dont know anymore...
Please someone can tell me how to fix this...
Try this:
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108/
I saw that guide but i get stuck at the step 5, i downloaded the drivers and recovery tool.
Put them in a folder in the desktop, then tryed how they say to press only the volume up while pluging in the phone, and here i think i did that but the name of the driver is not qualcomm-HS USB Diagnostics, but "RELINK-HS QDloader" or something like that.
Now here i get stucked... i dont know how to use the drivers that i downloaded also if i try to change it to RELINK-HS QDloader to RELINK-HS QDloader which is simular to what they say I get the error 10 and when i open the tool it doesn't show any devices.
Mc_Markx said:
I saw that guide but i get stuck at the step 5, i downloaded the drivers and recovery tool.
Put them in a folder in the desktop, then tryed how they say to press only the volume up while pluging in the phone, and here i think i did that but the name of the driver is not qualcomm-HS USB Diagnostics, but "TELKET-HS Qport 9000" or something like that.
Now here i get stucked... i dont know how to use the drivers that i downloaded also if i try to change it to TELKET-HS Qport 9000 to TELKET-HS Diagnostics 9000 which is simular to what they say I get the error 10 and when i open the tool it doesn't show any devices.
Click to expand...
Click to collapse
Install this drivers and check if not works it will be good if you provide some more info about the device like model number and stock ROM oxygen or h2os.
http://www.androidbrick.com/download/qdloader-hs-usb-driver/
Ok i did it, i installed the qualcomm driver, installed it for the phone, but now i have a new problem, the device doesnt show in the msm tool
Big big update, i really really really really feel so much better now!!!!! I want to thanks you to suggest to try this thing again! It worked, man really you saved me!
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.
Hi all,
I recently splurged on a Lenovo K5 Pro which was released in October '18. It seems to be fine overall. Specs are nice with 4gb RAm 64gb ROM, and has android 8.1 with a ZUI 5 skin. This is my issue: I've run into a problem with unlocking the bootloader. I can toggle the 'OEM Unlock' in the dev settings all day, but when putting it into the bootloader and running 'fastboot flashing unlock' , I'm met with 'Flashing unlock is not allowed'.
fastboot flashing get_unlock_ability returns 0, no matter the state of the OEM Unlocking toggle, and 'oem device-info' returns the below:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
OKAY [ 0.010s]
finished. total time: 0.015s
Honestly, I'm kind of stumped. There aren't any forums on this pretty much anywhere given that its new, and 4pda only has discussions surrounding the potential of such a phone. I've seen pixel users run into this, but the issue is resolved with removing screenlocks. So far, no luck for me.
Let me know if you have this phone and have done any development on it. It seems to have quite a lot of potential. Thanks.
edit:
So I'm still unable to unlock the bootloader, but I've successfully rooted the L38041. I'll include the steps below. Please note, I'm only relating how I did this. There are probably more efficient methods, but, for me, this worked. I'm not responsible if you hardbrick your device.
Requirements:
a. Latest QPST from qpstflash (sorry, can't post links yet)
b. Magisk Manager
c. Stock L38041 rom. I used the global version from FirmwareX. Make sure it has ROW in the title, not CN, otherwise it'll be the Chinese ROM.
d. ADB and Fastboot
Steps
1. Download and extract the ROM to your PC.
2. Copy the boot.img file from the extracted folder to your device storage.
3. Open magisk manager on your device and install via 'patch stock boot image'. Navigate to where you put the stock boot.img and select it.
4. Take the patched_boot.img, rename it back to boot.img, and put it back in the extracted ROM folder on your PC. Make sure you've backed up your stock boot. because you'll be replacing it with the patched.
5. Install the QPST package on your PC and run QFIL. Select Flat build, then navigate the programmer path to your ROM folder. Select the prog_emmc_ufs_firehose_Sdm660_ddr.elf as your programmer path. Next, load XMLs RawProgram0.xml and patch0.xml.
6. At this point, attach your adb enabled device via usb and run the adb command "adb reboot edl." This will put your device into emergency download mode, in which you will be able to use QFIL . QFIL should go from 'No Port' to 'Qualcomm HS-USB QDLoader 9008'. Immediately after you see this pop up, select 'Download'. This will completely reset your device.
7. If flashing was successful, wait a bit then boot your device. You should see a little warning complaining that the software has been altered. Wait a little bit more. You can install magisk manager at this point if it didn't show up after the flash. Reboot the device again.
8. Et voila, you should have a rooted device now. Due to the locked bootloader, you still can't (or at least I couldn't) use a custom recovery, were there even one available.
Note: if you get a sahara error in the flashing process, it's probably because you waited too long to hit download.
Hope this helps for those of you with issues.
zui.com/iunlock
KiiKeEp said:
zui.com/iunlock
Click to expand...
Click to collapse
Doesn't work for me. It says IMEI1 is incorrect. Also tried to register the device at Lenovo.com but then it says serial number is invalid.
//
hello this mssg goes out to anyone who orderd thier Lenovo K5 Pro from the aliexpress seller "Lenovo official store" if zui dot com gives you headache mail the seller with that there is a problem and they will fix it for you( i guess). because after i mailed them and i tried again on de zui website my SN and EMEI combo where accapted. and i now got the unlock. its a sn image. if i get it working i highly suggest that people follow the tutorial with twrp since for a lot of people that would be easier. anyway thank you for this solution.
Also maybe you have to wait 7 days before you can unlock your bootloader because tht would be the time it takes for lenovo to process your SN EMEI combination and therefor after 7 days zui can get you your unlock code.
Good Evening,
I have an Android Phone REDMI 6A from the licensed distributor in Indonesia.
The warranty for my phone already expired and I'm tried to Root my REDMI 6A.
I'm searching for the step to Root and here what I get:
1. I need to click 7 times in about to open developer option
2. Allow the USB Debugging
3. Do the unlock bootloader with Mi Unlock (I'm already success and when I'm reboot in below screen there is a text "unlocked"). But it's weird when I see another thread that say for the unlock we need permission from Xiaomi that needs xx days to unlocked legally. But in my case I don't need to wait for xx days.
4. The next step for root is I need to flash with Mi Flash Tools and here is the nightmare when I'm follow the steps and in the steps stated not tell to choose "clean all". In my case the choose for Mi Flash is default in "Clean and Lock" that you can see in the right down below from Mi Flash Tools App.
5. That's it. Flash is done with the option "Clean and Lock" the phone is reboot and Ohh my Goshhh..... the Phone is not working and screen display to Mi Recovery with error "MIUI Versions can't be installed in this device"
From what I read in many threads the situation I'm in is :
1. Flash wrong ROM that makes my Phones Bricked and the protection from Xiaomi is on
2. The bootloader that Unlocked now is Locked and that makes the USB Debugging off too
I'm already do this:
1. Used the SP Flash Tools v 5.1924 with information for SP Flash tool:
a. Download Agent : MTK_AllInOne_DA.bin or MTK_AllInOne_DA_4-19_-signed.bin
b. Scatter Loading files : MT6765_Android_scatter.txt from many ROM Fastboot (Global, China and Rusia)
c. auth_sv5.auth
2. Test in SP Flash Tools "Download" and click the download and then I'm hold volume + in my phone (the battery is disconnected) and then connect the phone use USB cable.
When I'm see the device manager Mediatek USB Port is appear but in SP Flash get error BROM error status_brom_cmd_send_da_fail (0xC0060005)
3. Test the "Format" option in SP Flash Tools with option "Manual Format Flash" and change the data needs from the scatter.txt:
a. Begin Address : 0x5588000
b. Format Length : 0x100000
3. Used Minimal ADB and Fastboot and use command:
a. ADB devices : not work --> I think it's because the usb debugging off. Before when I'm try this when my phone still on this command list the
detail of my devices
b. Fastboot devices : It's work when I can go to fastboot screen (it depends on luck when I'm try the SP Flash tools and I will modified it with
Volume - & Power before connect to PC with usb cable)
c. Fastboot oem device-info : not work
d. Fastboot unlock OEM : not work
e. Fastboot reboot : work but still stuck at Mi Recovery
4. Used Mi Phone Assistant (condition in Mi Recovery choose Connect with Mi Phone) and do the flash ROM used Global, China, and Rusia ROM and still not work.
It works for miui_HM6AGlobal_V11.0.7.0.PCBMIXM_755e2b7216_9.0 and in progress to 100 % but after reboot will stuck to Mi Recovery again.
5. Try Mi Unlock but it's not working
6. When I get to Fastboot sceen by luck I try this too:
a. Used Mi Flash 2017.4.25 with option "Clean All" used ROM (Global, China, Rusia) for flash. Click refresh and the devices is appear and when
click Flash (after fill the path ROM) it's error
b. Used ADB to know the status of my devices (locked bootloader, etc) with command fastboot oem device-info but error
I read if the condition is like this, I'm must flash it to original ROM or China Version. But please tell me how I do that?
I'm already searching and download many ROM (fastboot and recovery) but when used in Mi Phone Assistant to flash ROM it's still not working.
Please tell me if there is some way to restore my REDMI 6A to normal condition (no need for root first).
The condition I'm in now:
1. I have a Mi Account
2. Sometimes by luck I can get to Fastboot screen
Kindly appreciate if you can solve this problem.
Looks like you wiped or formatted your entire phone. I've been in this situation before (RIP my Lenovo A7000a). But i have some experience with SP flash tool.
1. Go to options and go to the download section, and enable USB checksum and storage checksum
2. Load the scatter file
3. Give a checkmark on everything from preloader to userdata
4. Format the phone on the format section(optional but recommended)
5. Then click the download button on download section (important: make sure you haven't plugged your phone)
6. Plug your phone to your PC
7. Wait until the flashing process is done
8. After the flashing process is done you're you will prompted with a green checkmark image
9. Done. It should boot and work properly
---------- Post added at 10:38 AM ---------- Previous post was at 10:18 AM ----------
There's a list of SP flash tool errors and how to solve it here. Maybe it will help you https://forum.hovatek.com/thread-439.html
Hello, If your bootloader is Unlocked, You can go to fastboot & type this command
fastboot erase recovery
fastboot flash recovery twrpname.img
Replace twrp name with name of custom recovery.
Now type : fastboot reboot recovery
Now it will boot in twrp , install any custom ROM from there.
PS: Already told, requires a Unlocked BL