Hello There
Just tried to reset the phone from a colleague(forgot his pattern and didnt use his G10 since december 21) and stuck with TFM tool on no command.
Tried every combination with power and volume up but couldn't go further.
With luck after one night of trying the fastboot command on CMD finally found the phone.
First command I tried was fastboot reboot fastboot(found the command somewhere here G10 forum).
The device now wont start in fastboot and start immediately with the AndroidOne logo and afterwards a big red explanation mark with the message:
No Valid operating system could be found.
The device will not boot.
Appreciate any help
Thank you!
Pete
Hey Pete,
I know it's a little late, but I'll put this here just in case you or anyone else needs it later. I got the same error after reset and fixed it by changing the active boot slot.
boot to fastboot
from command prompt/terminal: fastboot getvar current-slot
command will return something like:
current-slot: a
Finished. Total time: 0.002s
In this case you would want to change slot to 'b'
fastboot --set-active=b (if the above says 'current-slot: b', then use --set-active=a here)
fastboot reboot
Then go get a drink or something, this reboot is going to be SLOW.
Dear Experts,
I am having the same error as Pete explained in the beginning, the real problem is I can't get into recovery/fastboot mode by trying different key combinations found in the internet. When I try the combination/ connects usb to PC it shows the error and restart everytime. Even tried to flash stock rom using sp tool but it's not detecting in PC either. Tried a heap of MTK drivers. Tried Test point method. None of these seems to work. Could any super humans among you help me please.
Model - Nokia G10, TA-1334
Thanks in advance..
After a week's research, found the solution and brought back my phone from death. The problem was not the drivers. it was me. Tried the test point method in wrong way, need to set the connection from test point to GND first and then only connect to PC. Also make sure there is at least one program awaiting to be connected (Eg. MTK Client/ MTK Bypass tool).
1. Disable the secure boot.
2. Use SP tool to flash the ROM (Trust me there will be errors. Lots of errors, but it can be sorted with some deep google search).
3. Make sure the test point connected to GND all the time while flashing.
You can do it. Finally, my problem shrinked to the invalid IMEI. will sort it out.
eb60700 said:
After a week's research, found the solution and brought back my phone from death. The problem was not the drivers. it was me. Tried the test point method in wrong way, need to set the connection from test point to GND first and then only connect to PC. Also make sure there is at least one program awaiting to be connected (Eg. MTK Client/ MTK Bypass tool).
1. Disable the secure boot.
2. Use SP tool to flash the ROM (Trust me there will be errors. Lots of errors, but it can be sorted with some deep google search).
3. Make sure the test point connected to GND all the time while flashing.
You can do it. Finally, my problem shrinked to the invalid IMEI. will sort it out.
Click to expand...
Click to collapse
I have the same problem. The phone restarts and I can't put it in fastboot. Could you solve it?
Andrey10 said:
I have the same problem. The phone restarts and I can't put it in fastboot. Could you solve it?
Click to expand...
Click to collapse
You should have back up the firmware before doing anything.
Please try to get the phone in fastboot mode.
I did not make the backup. The combination of buttons to get the phone in fastboot mode does not work for me. All it does is reboot.
Andrey10 said:
I did not make the backup. The combination of buttons to get the phone in fastboot mode does not work for me. All it does is reboot.
Click to expand...
Click to collapse
Have you used SP Flash Tool to reset the device?
eb60700 said:
After a week's research, found the solution and brought back my phone from death. The problem was not the drivers. it was me. Tried the test point method in wrong way, need to set the connection from test point to GND first and then only connect to PC. Also make sure there is at least one program awaiting to be connected (Eg. MTK Client/ MTK Bypass tool).
1. Disable the secure boot.
2. Use SP tool to flash the ROM (Trust me there will be errors. Lots of errors, but it can be sorted with some deep google search).
3. Make sure the test point connected to GND all the time while flashing.
You can do it. Finally, my problem shrinked to the invalid IMEI. will sort it out.
Click to expand...
Click to collapse
hello friend. Did you manage to fix the IMEI by any chance? I have a device that has an invalid IMEI and Serial Number.
I managed to fix the IMEI problem
Related
Some of us are bound to "brick" our Max's at some point, we need a genius that knows the right test points to help us out!
Thanks!
Totally agree. I now manage to boot into EDL and Fastboot, but have a locked bootloader and don't know how to reset the phone
(the only thing I did was an update, then bootloop...)
Help Please..Same with me.
My phone was hardbrick i think.
No download mode, no fastboot mode and my device manager just only recognize as HS-USB Diagnostic 900E
How i can get back to life my phone
Thanks
This should work on Mi Max too:
http://en.miui.com/forum.php?mod=viewthread&tid=310325&extra=page%3D1&mobile=2
Check here: http://en.miui.com/thread-328371-1-1.html
panospc said:
Check here: http://en.miui.com/thread-328371-1-1.html
Click to expand...
Click to collapse
I also posted it here
I am everywhere
How do I put the phone into fastboot mode if it is hard bricked? It won't turn on, I get no responce from phone. When I use method connecting test point to metal cover on mother board of phone usb connects to PC and MiFlash recognizes phone. Try to flash though and I get an error message. No matter what ROM I use, zipped, unzipped or tgz file. Can my phone be unbricked? What am I doing wrong? I have a Mi Max 64GB and am using HELIUM Roms. Please help. I am using this method
http://en.miui.com/thread-328371-1-1.html
Everything is good up to when I click on flash. Then I always get the error message.
Error message is:
The filename, directory name, or volume label is incorrect.(0x8007007b: Open programmer "MPRG*.hex").
I have no clue. Not my first time flashing ROMs or unbricking a phone. It is my first time on a Xiaomi. Only done blackberry and samsung before.
Hello everyone! So... I rooted my ZE551ML when I got it about a month ago and today an update pop-up from Asus shows up. So I said "what could go wrong?" .... How about everything?? Basically, I tried a bunch of different things because I could access via ADB, so I tried to unroot it with a bat file I found with a guide for that, but nothing. Now, I passed from black boot screen with white logo to white boot screen with black logo and I can't connect it with adb nor recovery mode. Is there something I can do to enter recovery? With the normal "volumeUP+power" I get nowhere. Can anybody help?
mikla90 said:
Hello everyone! So... I rooted my ZE551ML when I got it about a month ago and today an update pop-up from Asus shows up. So I said "what could go wrong?" .... How about everything?? Basically, I tried a bunch of different things because I could access via ADB, so I tried to unroot it with a bat file I found with a guide for that, but nothing. Now, I passed from black boot screen with white logo to white boot screen with black logo and I can't connect it with adb nor recovery mode. Is there something I can do to enter recovery? With the normal "volumeUP+power" I get nowhere. Can anybody help?
Click to expand...
Click to collapse
hope you can access fastboot. if yes you can install recovery and ifwi files from fastboot
How do I start fastboot mode? I let it charge all night and my pc does the "device connected/disconnected" sound all of the time, but adb says no device (the drivers are ok, I tried before). I have to say that I tried to flash boot.img, droidboot.img, recovery.img and system.img. Problem is, while I was downloading those files I found 2 other methods for recover it, one was to unroot it and the other to unlock the bootloader.... And I tried. Now, I'm unable to enter recovery.
Edit: I tried this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 and for a short period of time (about a second or 2) I can see another device under the "Intel SOC" in device manager, but xFTSK cannot see the phone, even when it shows up for just a second on device manager.
Edit2: holding power down and plugging in the usb cable allows xFSTK to see my device, I put in the files and begin downloading, everything is going good but then it says
07:24:01 - XFSTK-LOG--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field
And from there it just starts all over again until it fails definetly.
Edit3: I'm trying the hell out of this software. I attach 2 logs to this post with relatives configurations. Still waiting for help.
Using xfstk tool
mikla90 said:
How do I start fastboot mode? I let it charge all night and my pc does the "device connected/disconnected" sound all of the time, but adb says no device (the drivers are ok, I tried before). I have to say that I tried to flash boot.img, droidboot.img, recovery.img and system.img. Problem is, while I was downloading those files I found 2 other methods for recover it, one was to unroot it and the other to unlock the bootloader.... And I tried. Now, I'm unable to enter recovery.
Edit: I tried this guide http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 and for a short period of time (about a second or 2) I can see another device under the "Intel SOC" in device manager, but xFTSK cannot see the phone, even when it shows up for just a second on device manager.
Edit2: holding power down and plugging in the usb cable allows xFSTK to see my device, I put in the files and begin downloading, everything is going good but then it says
07:24:01 - XFSTK-LOG--Windriver Error: 0xC0000011, HC status: The host controller has set the Transaction Error (XactErr) bit in the transfer descriptor's status field
And from there it just starts all over again until it fails definetly.
Edit3: I'm trying the hell out of this software. I attach 2 logs to this post with relatives configurations. Still waiting for help.
Click to expand...
Click to collapse
open Xfstk Tool and click Tab -MRD/AO/BO +MOOR Ao+CRC then go to settings under option menu - enable GP Flag Override Option and Enter value - 0x80000807 and save (OK), then choose files -
FW Dnx - dnx_fwr.bin
IFWI - ifwi.bin
OS IMAGE - droidboot_dnx.img.POS_sign.bin
AND connect phone, press begin and Xfstk tool detect the phone and install the required files and you will able to get Normal Fastboot mode and install the firmware by fastboot / Asus Flash tool / or -SDUPDATE Zip file.
-------------------
Press Thanks Button, If i am helped you
-------------------
In the end, after about 20 times, XFSTK did flash what should have. Now, I'm back in business. I changed nothing, just kept trying.
Hi,
I'm after some advice, how do I place the Moto G5 in Qualcomm mode or EDL mode.
I have entered the bootloader by holding down and turning the phone on, this allows me to use fastboot.
From there I can scroll down to QCOM, but when I press the power button it boots into the normal system instead of EDL mode.
I have also attempted from within fastboot to use:
fastboot oem edl
fastboot oem qcom-on
fastboot reboot emergency
and
fastboot reboot-edl
Although non of these have been sucessful.
I also have access to an EDL cable, although, when I plug the phone in, then flick the switch 10 seconds later, it does not enter EDL mode, it just charges.
The phone sometimes shows as File Storage Linux USB Gadget in device manager, although it is inaccessible, I have updated the laptop to use the qualcomm drivers, although I don't think it will ever recognise it if I can't put the phone into qualcomm mode to begin with.
Any help would be much appreciated.
What are you actually attempting to do?
This mode is generally used to unbrick a device but you have access to the bootloader/fastboot mode and you wouldn't use edl mode to unbrick this device anyway
It's also used on some device to unlock the bootloader but again you wouldn't do that with this device
So without knowing what you are trying to achieve I can't give you any advice
Technically if you start the phone normally then enable usb debugging in dev options then connect phone to PC and in a terminal window where you have adb set up type
adb reboot edl
Not all devices support this mode though and I've no idea if this one does
TheFixItMan said:
What are you actually attempting to do?
This mode is generally used to unbrick a device but you have access to the bootloader/fastboot mode and you wouldn't use edl mode to unbrick this device anyway
It's also used on some device to unlock the bootloader but again you wouldn't do that with this device
So without knowing what you are trying to achieve I can't give you any advice
Technically if you start the phone normally then enable usb debugging in dev options then connect phone to PC and in a terminal window where you have adb set up type
adb reboot edl
Not all devices support this mode though and I've no idea if this one does
Click to expand...
Click to collapse
Without going into too much detail as to why, there are tools I have access to which can be used to take a full back up of the entire memory block of the phone when it is in Qualcomm mode.
I cannot access adb on the device to use "adb reboot edl" so I am limited to either trying to activate Qualcomm using a button combination or via fastboot, unless you can advise another way.
Any help or a point in the right direction would be much appreciated.
jameswstubbs said:
Without going into too much detail as to why, there are tools I have access to which can be used to take a full back up of the entire memory block of the phone when it is in Qualcomm mode.
I cannot access adb on the device to use "adb reboot edl" so I am limited to either trying to activate Qualcomm using a button combination or via fastboot, unless you can advise another way.
Any help or a point in the right direction would be much appreciated.
Click to expand...
Click to collapse
Sounds dodgy to me - sounds like you're trying to access data from a phone that isn't yours so I won't be helping
TheFixItMan said:
Sounds dodgy to me - sounds like your trying to access data from a phone that isn't yours so I won't be helping
Click to expand...
Click to collapse
It's not dodgy, but I fully understand.
Thank you anyway.
try fastboot -i 0x2b4c oem reboot-edl (it's working for LENOVO ZUK Z1 and ZUK Z2)
You can try (if you can/have the TWRP image) to flash TWRP and in reboot options select EDL.
In case the bootloader isn't unlocked you can also use fastboot boot [TWRP image name] to boot directly into TWRP without flashing and then repeat, go into reboot options and select edl.
Not sure if it works for you, if it does let me know that I have helped!
TheFixItMan said:
Sounds dodgy to me - sounds like you're trying to access data from a phone that isn't yours so I won't be helping
Click to expand...
Click to collapse
I need help too. So, I own a Moto G5s plus sanders. I unlocked its bootloader the day I got it. Didn't keep any backup and rooted it. I Also installed dot os based on android 11. But my 4G Volte connection was finicky. So, I decided to use a Volte zip patch. But, anyways I flashed the zip via TWRP and tried to reboot. But the phone didn't turn on after that. After a few minutes to my shock I understood that I hardbricked my mobile. No button combos, nothing worked. Anyways in my desperation I found a YouTube video showing the use of blankflash to revive a phone and lo and behold I used the procedure to again restore my device. It booted to the fastboot interface. But my happiness was short lived. My baseband was unknown at this point and the bootloader was I dunno downgraded to 0.5 inplace of 2.12. But, more importantly the unlock status was lost. I unlocked it again and all went well. I could even flashed TWRP. but then I realised I couldn't upgrade my bootloader. I couldn’t do anything. It's always gives a "security downgrade", "preflash validation failed" and "permission denied" error. I even tried RSA official rescue tool from Lenovo but even it was unsuccessful. It was never unsuccessful before that. Not even with a unlocked bootloader. I researched for days and tried custom ROMs. I flashed stock images. Nothing brought back my baseband and IMEI. When I type "fastboot oem unlock critical" it gives me permission denied error with a message. "Need OEM signed bootloader." I think the blankflash bootloader is the root of all evil. I need to change it and therefore I need to enter the edl mode. I have tried all adb commands and fastboot commands. The phone reboots okay after those commands but never goes into edl mode whatsoever. I am also ready to do a controlled hardbrick of my device to go into the edl mode so that I can use my device again with a proper bootloader and a properly working fastboot. Please help
I was playing normally the phone discharged turned off, and when I connect it only shows the android one screen over and over, the led that shows that it's charging doesn't turns on, I have nothing weird installed, didn't even knew about fastboot or roms, or anything like that until 15 minutes ago, so the fastboot options are not and cannot be activated, does it have a solution? do I just let it be connected for a few hours and try again, or what, i'm a noob on this matters so I don't know what to do. Thanks
maybe try holding vol down and power for 10 or more seconds. it should vibrate. it reboots and shows fastboot icon, you can flash stock rom again, let us know
loop4444 said:
maybe try holding vol down and power for 10 or more seconds. it should vibrate. it reboots and shows fastboot icon, you can flash stock rom again, let us know
Click to expand...
Click to collapse
The fastboot screen shows, but I can't do anything, and if I connect it to my PC after watching somethings like going to CMD and trying some commands the console doesn't even recognize those commands, maybe I have to install something for it to read it? I don't know, if this helps in anyway, I appreciate it.
M4N4GM said:
The fastboot screen shows, but I can't do anything, and if I connect it to my PC after watching somethings like going to CMD and trying some commands the console doesn't even recognize those commands, maybe I have to install something for it to read it? I don't know, if this helps in anyway, I appreciate it.
Click to expand...
Click to collapse
connect phone in fastboot mode and flash stock rom trough MiFlash, but remember to take backup of internal memory. I'll release all except external sd.
pawelik said:
connect phone in fastboot mode and flash stock rom trough MiFlash, but remember to take backup of internal memory. I'll release all except external sd.
Click to expand...
Click to collapse
Can you do the backup even if the phone can't start? does de MiFlash has that option? and thanks i'll try
M4N4GM said:
Can you do the backup even if the phone can't start? does de MiFlash has that option? and thanks i'll try
Click to expand...
Click to collapse
It seems that you didn´t enable USB debugging before, maybe? Did you solve it?
SubwayChamp said:
It seems that you didn´t enable USB debugging before, maybe? Did you solve it?
Click to expand...
Click to collapse
No I didn't enable the USB debugging, and no I haven't been able to do it, the mi flash program needs extra installations but always sends an error message and closes, I really don't know how to do this kind of things, I tried with a program called MiFlash Unlock, but it needs a Xiaomi account connected with the number and I don't have one, I really don't know what to do from here, plus I've read that I need the rom to install and don't know where can I find it and which one is the one that I need to install.
Once again thanks and if someone can help me further than this is appreciated
M4N4GM said:
No I didn't enable the USB debugging, and no I haven't been able to do it, the mi flash program needs extra installations but always sends an error message and closes, I really don't know how to do this kind of things, I tried with a program called MiFlash Unlock, but it needs a Xiaomi account connected with the number and I don't have one, I really don't know what to do from here, plus I've read that I need the rom to install and don't know where can I find it and which one is the one that I need to install.
Once again thanks and if someone can help me further than this is appreciated
Click to expand...
Click to collapse
Anyway you can't do many things although you should have enabled USB debugging atleast you decided to unlock device but fastboot is (almost) useless for device with locked boatloader.
The first thing I do no matter I don't think to root or modify my device is enabling USB debugging just to have more options to recover from an eventual brick.
Now try to do the next before to go to the other option; try to enter to recovery from device off, using volume up + power for some seconds then format/factory reset and let us know what happened.
SubwayChamp said:
Anyway you can't do many things although you should have enabled USB debugging atleast you decided to unlock device but fastboot is (almost) useless for device with locked boatloader.
The first thing I do no matter I don't think to root or modify my device is enabling USB debugging just to have more options to recover from an eventual brick.
Now try to do the next before to go to the other option; try to enter to recovery from device off, using volume up + power for some seconds then format/factory reset and let us know what happened.
Click to expand...
Click to collapse
That option didn't work, volume up + power just tried to start the phone
M4N4GM said:
That option didn't work, volume up + power just tried to start the phone
Click to expand...
Click to collapse
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
SubwayChamp said:
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
Thanks i'll try if it works
SubwayChamp said:
Ok, I supposed it, some partitions get corrupted while device fails to reboot.
Your last solution is using EDL mode, you will find many tutorials on YouTube to put device in this mode using test point method, then flashing the official stock rom through MiFlash tool.
To take in account MiFlash tool doesn´t work while in fastboot mode on devices with locked bootloaders so you have to use it in EDL (Emergency DownLoad) mode, no other workaround known on that. (for this model)
As reference I´ll put the basis of the links that you need to take a look in:
- Test Point method:
https://www.google.com/url?sa=t&rct...=XzknDcBovWw&usg=AOvVaw3gCAHutdqhO0Ukszyz-XJ-
- Drivers for unbrick qualcomm devices:
https://gsmusbdrivers.com/download/qualcomm-hs-usb-qdloader-9008-driver-64-bit-windows/
- Xiaomi Flash Tool:
https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
- Fastboot images, you can use the latest:
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
You should try the official and safer fastboot image.
http://c.mi.com/oc/miuidownload/detail?device=1700353
Little Hill said:
You should try the official and safer fastboot image.
http://c.mi.com/oc/miuidownload/detail?device=1700353
Click to expand...
Click to collapse
Wrongly quoted.
My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP
crazyfox21 said:
My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP
Click to expand...
Click to collapse
Can you get it to stop at fastboot, and stop rebooting over and over? Like, when it first powers down (black screen), before it starts to come back up, hold power and volume down, and boot to the fastboot screen. It should stick. From there you can flash stock ROM.
You might need to only flash stock boot.img, but when that's happened to me, I flashed the whole thing
beachfl said:
Can you get it to stop at fastboot, and stop rebooting over and over? Like, when it first powers down (black screen), before it starts to come back up, hold power and volume down, and boot to the fastboot screen. It should stick. From there you can flash stock ROM.
You might need to only flash stock boot.img, but when that's happened to me, I flashed the whole thing
Click to expand...
Click to collapse
Get some info from youtube it seems this laptop fail to detect/install adb/fastboot driver,, then my Device go to charging mode and ended up bootloop instead of charging. (because if i let the phone itself, without connecting to Laptop. . .it's rock solid on Fastboot mode)
Still try to get other PC/Laptop, seems current available one has a messy Windows. . .
When i execute "fastboot devices" on cmd,, pop-out error api-crt-. . . .- l1.1.0.dll missing
Try installing vc_redist failed to execute MSU
crazyfox21 said:
My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP
Click to expand...
Click to collapse
So Sad, was stuck in the same situation tried 100 of methods but all in vain, in the end had to send my device to customer care center & received after 15 days without charges
I use to flash rom`s when i was younger phones and tablets and never had a brick, I am glad it`s out of my system, Anyway the 8pro works fine for me as a non-gamer as it seem to be very risky to flash.
Good luck getting your problem solved.
crazyfox21 said:
My Redmi Note 8 Pro has bricked after flashing Magisk, confused which method can fix my device
- No Recovery (bootloop even holding volume+)
- Can boot to Fastboot but after connect to PC it's rebooting instead connected on fastboot
can somebody help me ASAP
Click to expand...
Click to collapse
crazyfox21 said:
Get some info from youtube it seems this laptop fail to detect/install adb/fastboot driver,, then my Device go to charging mode and ended up bootloop instead of charging. (because if i let the phone itself, without connecting to Laptop. . .it's rock solid on Fastboot mode)
Still try to get other PC/Laptop, seems current available one has a messy Windows. . .
When i execute "fastboot devices" on cmd,, pop-out error api-crt-. . . .- l1.1.0.dll missing
Try installing vc_redist failed to execute MSU
Click to expand...
Click to collapse
Greetings,
First thing I would do is grab the latest version of ADB/Fastboot, uninstall previous version and reinstall it on your Laptop as Admin, turn off your Anti-virus anti-spyware, optimization program or whatever app you may have running on your Laptop and which could prevent system modification, then run it as Admin. If during installation you are poped with installing more things like MS or google's libraries and such, install them.
You may also try to reboot your phone to fastboot while already being connected to computer which may prevent it to boot to the charging page.
If you manage to get fastboot stable enough when connected and if you have no done already, you may want to proceed with reading the [GUIDE][INFO][PSA] Redmi Note 8 Pro - Megathread + CFW and applying the anti-brick solution before flashing anything else like a recovery again.
Assuming you have not damaged anything else, to recovery from a Magisk installation failure you may only need to flash the boot.img from your exact same Stock image you were on.
If that does not suffice, flashing additionally system and userdata (all data will be lost) should fix it.
Hope this helps,
Good Luck!
PS: I am assuming your bootloader is unlocked right?
[SOLVED]
Sorry for late update. . .
Just like i mention above, cause of laptop that i borrowed so messy. . .its anti-core thing won't allow adb/fastboot connection (that's why, my device suddenly disconected and going to charging mode)
*as soon as i go to nearest net-cafe, i can do fastboot thing (Re-flash stock boot.img and TWRP) and my phone booted up normally ??
Edit : my false because i'm forget to close AVB before flashing Magisk
crazyfox21 said:
[SOLVED]
Sorry for late update. . .
Just like i mention above, cause of laptop that i borrowed so messy. . .its anti-core thing won't allow adb/fastboot connection (that's why, my device suddenly disconected and going to charging mode)
*as soon as i go to nearest net-cafe, i can do fastboot thing (Re-flash stock boot.img and TWRP) and my phone booted up normally ?
Edit : my false because i'm forget to close AVB before flashing Magisk
Click to expand...
Click to collapse
So glad you could fix it and make it work in the end! That's all what matters!
You can now mark your thread as "[SOLVED]" by editing original message tittle
Cheers!