Question How to fix Poco F3 stuck in Fastboot? - Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40

I recently installed ArrowOS to my F3 and everything went well. Then I tried returning back to MIUI, flashing it through recovery didn't work so I used the MiFlash tool. Unfortunately I accidentally chose the Erase all and lock option but I exited the application halfway. Now my phone is stuck in fastboot and doesn't turn off, holding down the power button only resets and returns to fastboot. I tried reflashing MIUI both in fastboot and Miflash but both failed. I also checked if my phone was still unlock through MiUNlock and said it was unlocked, though the unlock icon isn't present when the phone is resetted. Is there a way to fix my issue, I'm really concerned if this will permanently break my device and possibly burin in the fastboot logo on my display. Any bit of advice and help is appreciated.

Lol , help you how?
Guess what's wrong ?
What error? Post everything first
Your phone is not locked if you removed it before end

Rstment ^m^ said:
Lol , help you how?
Guess what's wrong ?
What error? Post everything first
Your phone is not locked if you removed it before end
Click to expand...
Click to collapse
I'm stuck in fastboot and restarting does not work since it only goes back to fastboot.

AM3471_ said:
I'm stuck in fastboot and restarting does not work since it only goes back to fastboot.
Click to expand...
Click to collapse
Open mi flash , send error message

Rstment ^m^ said:
Open mi flash , send error message
Click to expand...
Click to collapse
Its just stuck in this step in both keep data and wipe all data.

Looks like usb cable contact issue to me , could even be locked if your halfway is 10min into flash or something... It also happens when you flash consecutively without rebooting
Check pc usb port , plug into usb 2.0 port
Check cable , use original cable
Reboot phone before every flash attempt
If one firmware doesn't work download and try another one ( Only if it spits out crc error : step 7/9 , any other error or lower step like 4/9 re insert usb cable into phone and don't touch it , the phone is losing contact ). Crc error is a real bich , you are on your own figuring that out , don't even bother with guides like removing crc check.
You are failing at the very first step , open mi flash logs from it's dropdown menu and either send screenshot or zip the whole folder and attach it here

1. Make sure ur device is unlocked bootloader
2. Download and extract this file https://t.me/PocoF3ID/494392
3. Double click hentai_go_away.bat it will help you out of fastboot and get you to twrp. From there u can install whatever rom u want.

armuttaqin said:
1. Make sure ur device is unlocked bootloader
2. Download and extract this file https://t.me/PocoF3ID/494392
3. Double click hentai_go_away.bat it will help you out of fastboot and get you to twrp. From there u can install whatever rom u w
Click to expand...
Click to collapse
He already used twrp and messed everything up , it won't work even if he gets into it.

Here are the logs of the Miflash, I used two versions the first being more recent.

AM3471_ said:
Its just stuck in this step in both keep data and wipe all data.
Click to expand...
Click to collapse
Reboot phone by holding power button for 10-15seconds , hold power down as well , don't let it try booting up at all.
Your best bet is to boot it straight into fastboot , not let it fail the boot and enter fastboot by itself

Rstment ^m^ said:
Looks like usb cable contact issue to me , could even be locked if your halfway is 10min into flash or something... It also happens when you flash consecutively without rebooting
Check pc usb port , plug into usb 2.0 port
Check cable , use original cable
Reboot phone before every flash attempt
If one firmware doesn't work download and try another one ( Only if it spits out crc error : step 7/9 , any other error or lower step like 4/9 re insert usb cable into phone and don't touch it , the phone is losing contact ). Crc error is a real bich , you are on your own figuring that out , don't even bother with guides like removing crc check.
You are failing at the very first step , open mi flash logs from it's dropdown menu and either send screenshot or zip the whole folder and attach it here
Click to expand...
Click to collapse
I used two version of Miflash, the first being the newest.

AM3471_ said:
I used two version of Miflash, the first being the newest.
Click to expand...
Click to collapse
Sorry I accidentally resent.

Rstment ^m^ said:
Reboot phone by holding power button for 10-15seconds , hold power down as well , don't let it try booting up at all.
Your best bet is to boot it straight into fastboot , not let it fail the boot and enter fastboot by itself
Click to expand...
Click to collapse
It only boots to fastboot, and trying to shut it off only restarts it to fastboot.

I reflashed miui and this error popped up.

AM3471_ said:
Sorry I accidentally resent.
Click to expand...
Click to collapse
Reboot phone , remove usb cable from phone , rotate it 180° and plug it in again. Don't touch the phone at all after that. Move away from pc table , click start and watch it from distance.
Fastboot commands are not going through correctly from what I've seen in the logs of one folder.
Send screenshot if it errors out again, and logs...
Honestly idk what to tell you , bring the phone under light and inspect the usb port, same with pc port and cable , if all is good keep rebooting the phone and plugging in the cable in and put after every flash.
I had the same issue before , my usb port had water dmg and would act the same way. Flashing fine one time , and other time erroring out in many different ways.

AM3471_ said:
I reflashed miui and this error popped up.View attachment 5509325
Click to expand...
Click to collapse
Send logs for that

This is 100℅ bad connection between phone and pc imo. Somerhing is not quite right , either you have junk in pc/phone/cable ports or there's corrosion covering the pins inside
37216a9f]:err:sending sparse 'super' 3/9 (781964 KB)...
[8:14:35 pm 37216a9f]:err:FAILED (data transfer failure (Unknown error))

Rstment ^m^ said:
Send logs for that
Click to expand...
Click to collapse
This will be my last post for now, I need to get some sleep since its late here, if i dont find any fix tomorrow I'll just send to a repair shop.

Rstment ^m^ said:
This is 100℅ bad connection between phone and pc imo. Somerhing is not quite right , either you have junk in pc/phone/cable ports or there's corrosion covering the pins inside
37216a9f]:err:sending sparse 'super' 3/9 (781964 KB)...
[8:14:35 pm 37216a9f]:err:FAILED (data transfer failure (Unknown error))
Click to expand...
Click to collapse
I'll try using a different PC tomorrow to see what the problem is.

AM3471_ said:
This will be my last post for now, I need to get some sleep since its late here, if i dont find any fix tomorrow I'll just send to a repair shop.
Click to expand...
Click to collapse
That's not the log file for error above... But I found similar one in folders above.
Clean the ports before you sleep... Power off everyrhing , phone pc , remove usb cable from charger and clean them all with cotton - if you have 97℅ or higher alchohol you can soak the cotton in it and clean the ports.
If not just send it back to service... They will prolly replace your motherboard if the flashing fails on their end as well , usb port will only be replaces at the very end of their troubleshooting.

Related

accidentally format bootloader

I accidentally formatted bootloader, and now my device unable to detect,boot or anything. Is there anything I can do of ?
(might try everything to work it out )
Can you boot into the preloader with volume up and power pressed?
flash ROM via FlashTool
BlueFlame4 said:
Can you boot into the preloader with volume up and power pressed?
Click to expand...
Click to collapse
no, i could not
Kittehdispenser said:
no, i could not
Click to expand...
Click to collapse
Sounds like a hard brick, which means your phone is destroyed. What exactly did you do?
BlueFlame4 said:
Sounds like a hard brick, which means your phone is destroyed. What exactly did you do?
Click to expand...
Click to collapse
welp, i tried to install custom rom ( which need to download the rar and paste it into INTERNAL) but i accidentally paste it to my SD card. Then i start to install it.
Then i said it's uninstallable, I just restart my phone and everthing went normal buy my wallpaper screen turns black and unable to read it tho USB ( Just the standby screen shows wallpaper)
Then my brothers came out and said that all you need to do is format it again and reinstall. We tired countless times . But then it have another option which above Format everything but not bootloader and another is Format everything and bootloader.
Then my bro press it and ... It became bricked.
it's still warrantyable so .. I plan to play dumb to the warranty company if I can't fix it.
( even if i play dumb idk what reason I need to come off, if i say yesterday the battery from 70% drop to 0% then it unable to open again )
PS: before this happen my battery happens from 70% drop to 0%, after charged. it's fine
PPS: give me a good excuses to play dumb C::
Wait, wait. How did you format the bootloader? No recovery should have this option! The only possible option to hard brick the P8000 is to pull out the USB cable in the exact moment when the SPFlash Tool writes it. So, can you elaborate a bit more about what you've done? I'm pretty sure you're missing something.
Soft Bricked HTC Desire 616
BlueFlame4 said:
Wait, wait. How did you format the bootloader? No recovery should have this option! The only possible option to hard brick the P8000 is to pull out the USB cable in the exact moment when the SPFlash Tool writes it. So, can you elaborate a bit more about what done? I'm pretty sure you're missing something.
Click to expand...
Click to collapse
Hi,
I did something similar with my HTC Desire 616. I choose "Format All + Download" option with SP Flash Tool. The phone soft bricked. Later I tried "format whole flash (including bootloader)". It's still soft bricked...
Is there a way to revive my phone back??? :crying:
I had the same problem - but it is possible to set the phone to a special bootloader mode called META mode - see this video: https://www.youtube.com/watch?v=A3TmXtOA0IA
To do so you have to open the phone and disconnect the battery. You can find a howto easily on youtube.
Then set up everything to flash the phone (SP-Flashtool, scatter file, etc.) and push the volume down button while connecting the phone to the computer. This switches the phone to META mode, the computer can recognize the phone, installs the preloader driver and finally flashes the phone
Maybe you have to do the procedure twice because on the first connection only the preloader driver will be installed.
This worked for my P8000(B) which I treated with SP-Flash Tool and "Format All + download"
Be aware that you formatted the NVRAM and lost your IMEI's
FrauHofrat said:
P8000(B)
Click to expand...
Click to collapse
What the meaning of (B)? Just asking because i have (W)
Tecno spark 3 pro clone flash file mt6570 android 9.0 firmware
Hi
I need your assistance, please help me find the firmware for the above phone. I recently tried to flash it with a Spark 3 clone firmware i got online but it gives an error STATUS_PARTITION_NOT_FOUND and also i accidentally formatted the bootloader on SP Flash Tool so the phone is a brick, it can't charge, and it can't turn on. I have screenshots of the About section when the phone was working, which contains the phone's features model and build but on opening the back cover of the device, i realized its a clone phone and i cannot determine its real model to get the exact right flash file.
Thanks

[help] ZE551ML crashes, TWRP freezes, no connection in xfstk downloader

Hello all,
I'm stuck in different guides on what to do next.
Problem: Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13.
Also had charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
Tried:
- Factory reset in TWRP -> didn't work (the occasion I did get into CM13 it showed the setup again, so the reset actually went through, but loops still exist).
- When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
- When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
- Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC.
-> Problem: Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
- Another problem: When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.
So now im a bit stuck on what to try next to solve everything and get myself back into CM13. CM13 has ran since Feb '16 and have been a happy user since then until now.
Thanks for reading!
The simplest solution may be to flash back to stock and start over. If the phone doesn't behave properly on a stock ROM, there could be a hardware problem.
Hi there , in TWRP select reboot then power off .
Enter bootloader via buttons after 10 seconds being off !
Enter bootloader - power and vol + , when in bootloader if on LP -- flash raw with AFT (asus flash tool )
If any probs with above , you might have to fastboot flash stock recovery and boot to recovery if/and a , try raw if on LP with AFT or b, sideload stock firmware you flashed stock recovery for.
audit13 said:
The simplest solution may be to flash back to stock and start over. If the phone doesn't behave properly on a stock ROM, there could be a hardware problem.
Click to expand...
Click to collapse
timbernot said:
Hi there , in TWRP select reboot then power off .
Enter bootloader via buttons after 10 seconds being off !
Enter bootloader - power and vol + , when in bootloader if on LP -- flash raw with AFT (asus flash tool )
If any probs with above , you might have to fastboot flash stock recovery and boot to recovery if/and a , try raw if on LP with AFT or b, sideload stock firmware you flashed stock recovery for.
Click to expand...
Click to collapse
Thank you for your answers! Last hours been trying to flash the stock ROM back. However, when getting into bootloader, adb devices and fastboot devices don't show the device. Or it even freezes and gets into reboot loops again. So this is why I'm stuck, nothing seems to be working from all the guides and things I'm reading.
So precisely:
- Power off bootlooping device by holding power button
- Power on by holding PWR + VOL UP
- When vibrating: release PWR keep holding VOL UP
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
So what can I try to make connection?
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
@j4y_ha .................in bootloader
Type >
................................................. fastboot devices
What ifwi version number in bootloader ?
timbernot said:
- Now i'm in bootloader?
- Connect USB cable to computer
- type adb devices, shows nothing.
@j4y_ha .................in bootloader
Type >
................................................. fastboot devices
What ifwi version number in bootloader ?
Click to expand...
Click to collapse
The bootloader in shows the following:
IFWI version: 0094.0173
SERIAL_NUMBER = F8AZFG0152** (couldn't read the last 2 digits as the device rebooted again). Also sometimes the SN shows 012345689ABCDEF.
I've much trouble keeping the device in bootloader. Last tryings it keeps shutting down after couple of seconds in the menu.
EDIT:
So far the device seems to stay in bootloader mode now. I can cycle through the options normal boot, recovery etc. Below the screen it shows Continue the fastboot process in blue text. I've inserted the USB cable but have been unable to get "fastboot devices" to show any device. ASUS Flashtool also doesn't do anything.
I'm going to try to find a micro SD adapter so I can try flashing stock rom in TWRP from the phone itself (would that be something that could work or is this phone fubar?)
@j4y_ha
Do not attempt to flash stock rom in TWRP ! You will brick !
Flash a custom rom in TWRP only- not one with a mm bl version
You have LP
PLEASE
Follow my first reply to you
timbernot said:
@j4y_ha
Do not attempt to flash stock rom in TWRP ! You will brick !
Flash a custom rom in TWRP only- not one with a mm bl version
You have LP
PLEASE
Follow my first reply to you
Click to expand...
Click to collapse
Thank you for your support! Will try again.
I have MM not LP.
I don't understand your reply correctly I think so here is what I think you say?:
I should obtain LP rom for ZE551ML
Next, enter bootloader via buttons PWR & VOL UP after 10 seconds being off !
When in the bootloader, - power and vol + (short press or long?) , when in bootloader ->
I connect USB to computer, flash the file using AFT if I make connection. -- flash raw (raw = LP ROM from ASUS) with AFT (asus flash tool )
Thanks again for your help
j4y_ha said:
Thank you for your support! Will try again.
I have MM not LP.
Thanks again for your help
Click to expand...
Click to collapse
IFWI version: 0094.0173 is LP, NOT M
follow my first reply:good:
---------- Post added at 06:39 PM ---------- Previous post was at 06:37 PM ----------
No1
Hi there , in TWRP select reboot then power off .
---------- Post added at 06:40 PM ---------- Previous post was at 06:39 PM ----------
no2
Enter bootloader via buttons after 10 seconds being off !
no3
When in bootloader you are on LP -- flash raw with AFT (asus flash tool )
@timbernot I'm unable to make connection. Fastboot also most of the times freezes and goes to black screen. What could I possibly try now?
Sorry I thought CM13 was MM but then I'm on LP still haha :good:
j4y_ha said:
@timbernot I'm unable to make connection. Fastboot also most of the times freezes and goes to black screen. What could I possibly try now?
Sorry I thought CM13 was MM but then I'm on LP still haha :good:
Click to expand...
Click to collapse
I'm taking wild guess here that you got wrong TWRP recovery installed somehow or something from M causing all these problems , when you get into bootloader again..Scroll to and select reboot bootloader and fastboot flash stock recovery for LP version you was on .
Then , I guess your problems will be over , where you will be able to flash raw in bootloader or in stock recovery , adb side load the firmware
Thanks for your quick anwer. Will try to get through it haha :good:
DUDEE
that's not a problem.. THAT's like 20 different problems... I bricked the living crap out of my zen the day I bought it (because me = smartypants did not know that the MM boot unlocker is nonexistent so I just tried to root and update from my head using older techniques) and... the XTS tool thingy fixed it..
Don't get me wrong, i want to help but this is the problem that I feel little frustrated with..
Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13. ## (but it boots sometimes and goes into TWRP, so you have an easy fix to just revert to stock lollipop... why haven't you done that? You sound like you know what most of this stuff does...
Charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
## how do you connect this battery issue to your occasional bootloop? Check hardware or firmware and definitely use different threads.. there's no way these are all part of the "same problem"...
When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
## Same answer as above - this is unrelated to #2 and unrelated to #1 - is your TWRP the correct one? I mean... did you just maybe flash TWRP version 4000 Modified Alpha for Google Glass??? LOL
When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
## Is D2W there? "DoubleTap2Wake" ? Are you sure you have a good touch? (this maybe 20% sounds related to your TWRP touch going crazy..)
Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
## There's this awesome invention called DRIVERS... and we're lucky in this case (cuz I bricked an hour after I bought it) because Intel PC + Intel Phone = Yay... There is even.... a very specific "INTEL ASUS WINDOWS DRIVER" file... from the INTEL AND ASUS WEBSITE... or maybe your USB CABLE is f**? My point is... another unrelated issue where it sounds like you've not even tried it properly before complaining.. I like helping people. I don't like when people refuse to try or they skip the actual study-notes to do it... I used the EXACT same guide to unbrick and it worked in 2 mins... I'm on a 2007 Laptop which overheats if I use 4 tabs... how am I able to follow the exact same guide on a brand new "FULLY BRICKED" phone... it literally would vibrate after trying power button for 5 mins and be stuck in a "blank black screen" for hours and hours... No twrp no nothing.. and I did it - why didn't you? Same guide man...
When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.)
## Try again. Sometimes people accidentally hit power to early.. or whatever.. It's not a MK2 Fatality.. don't force yourself to get it exact.. Let the menu pop up... just wait a second and scroll up/down just to see if that works... then scroll to Boot-Recov and gently hit power+vUp.. should be fine.. otherwise just .. literally try 10 times.. it WILL work.
Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC
## Nope.. TWRP is like Bret Hart. It isn't unstable. Not for LP not MM not for N. Not for Stock Not for CM Not for AOSP. You *wanted* to do what you should have done right at the beginning but you didn't get that done properly (see below)
Essentially you have 8 different unrelated issues (and the biggest one is not reading guides, not trying hard enough and just thinking that people like me sit around and get paid for this)... and want ans in one place w/o just doing the simple thing of going back to everything stock...?? *it's just annoying cuz people who want to help will feel like.... others don't even try simply because we exist and have desire to help...* - I am not trying to offend you but I hope you get my pov.
Do This EXACTLY
#Buy a cable. Borrow a cable. Whatever you do be 1000000% sure the USB Cable is fine
#Install Intel Asus Android drivers from official EXE (google it... don't add new post for that link)
AND THEN
Follow the same Unbrick guide word for word *but* just pay close attention to these:-
IntelSeC Driver + device detected even if OFF (start>devman>showall>intelsec
In the official unbrick utility make sure you're on the second tab at the bottom
In settings check that your device flag is 0x08..... whatever instead of the default 0x000
Back in the *second tab at the bottom* (i don't remember exact name but it's in the guide) -- put the right files (mentioned in guide) in the right boxes.. (mentioned in guide) and remember you ONLY need the DVFWthingy... + TOKENthingy + IFWthingy
Plug the Zen in... hear the "da-dumm" sound... keep looking at the Unbrick tool.. and the moment you see Device Detected = 1 you hit install/start...
AFTER that is fully done *(and if you fail don't post just repeat from scratch)... I don't personally recommend Asus Flash tool it was acting dodgy for me but instead grab the RAW Stock... Rename it to zip.. open it and grab the img files and fastboot flash the fastboot droidboot.img + splashscreen splash.img + boot boot.img + recovery recovery.img
If you've followed all that from the guide and double checked what I've put up there.. you should be fine if you just fastboot reboot bootloader... and go into stock recovery... install zip/update and put your stock OS in there..
Done.
Just please take my advice and don't skim through guides, don't think you don't need to read something, don't click stuff without double checking every line from guide, print it out on PAPER if you need to.... but please don't post like this... and don't use different guides or you will be stuck (as your heading stated..)
Forget everything you knew. Close all other tabs and use this guide thoroughly for Reference:-
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
j4y_ha said:
Hello all,
I'm stuck in different guides on what to do next.
Problem: Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13.
Also had charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
Tried:
- Factory reset in TWRP -> didn't work (the occasion I did get into CM13 it showed the setup again, so the reset actually went through, but loops still exist).
- When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
- When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
- Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC.
-> Problem: Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
- Another problem: When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.
So now im a bit stuck on what to try next to solve everything and get myself back into CM13. CM13 has ran since Feb '16 and have been a happy user since then until now.
Thanks for reading!
Click to expand...
Click to collapse
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Thank you for your thourough answer Ryankabir! Much appreciated. My answers are below. I will try your suggestions soon.
ryankabir said:
DUDEE
that's not a problem.. THAT's like 20 different problems... I bricked the living crap out of my zen the day I bought it (because me = smartypants did not know that the MM boot unlocker is nonexistent so I just tried to root and update from my head using older techniques) and... the XTS tool thingy fixed it..
Don't get me wrong, i want to help but this is the problem that I feel little frustrated with..
Zenfone2 doesn't boot most of the times (either looping after the white ASUS screen) or rebooting during loading of CM13. ## (but it boots sometimes and goes into TWRP, so you have an easy fix to just revert to stock lollipop... why haven't you done that? You sound like you know what most of this stuff does...
Click to expand...
Click to collapse
Yes I do know what I can do with it, but it just so complicating as there are different factors like the loops, not being able to get connections with USB. I mean, it is not totally bricked since sometimes I can get into TWRP or bootloader.
ryankabir said:
Charging problem, so I unplugged the battery from the back and put it back. This seemed to solve the charging problem. But problems above still persist. Thinking it may have corrupted some memory.
## how do you connect this battery issue to your occasional bootloop? Check hardware or firmware and definitely use different threads.. there's no way these are all part of the "same problem"...
Click to expand...
Click to collapse
Well, since the phone worked fine before the battery issue, there is some sort of link between the issues I would think. Maybe I've broken some hardware during the battery removal or did the booting into charging mode and on/off continously corrupt some memory leaving me with weird crashes & loops.
ryankabir said:
When in TWRP, after pressing randomly some buttons and go back to mainscreen, the touchscreen stops responding too and reboots
## Same answer as above - this is unrelated to #2 and unrelated to #1 - is your TWRP the correct one? I mean... did you just maybe flash TWRP version 4000 Modified Alpha for Google Glass??? LOL
Click to expand...
Click to collapse
Although I'm not sure if I have the correct TWRP, it did flash CM13 correctly back in FEB 2016 and haven't found a need to update it ever since as it worked fine during the occasional update...
ryankabir said:
When in CM13, after letting the phone sleep for a bit (2 mins roughly) - it doesn't wake up from power button. Have to press long and boot again.
## Is D2W there? "DoubleTap2Wake" ? Are you sure you have a good touch? (this maybe 20% sounds related to your TWRP touch going crazy..)
Click to expand...
Click to collapse
No, D2W is not there. The phone is totally unresponsive to the power button as well as D2W. When in TWRP the touchscreen functions fine until it freezes at some random moment.
ryankabir said:
Cannot get XFSTK to detect the device (Windows says: USB device not recognized or something like that).
## There's this awesome invention called DRIVERS... and we're lucky in this case (cuz I bricked an hour after I bought it) because Intel PC + Intel Phone = Yay... There is even.... a very specific "INTEL ASUS WINDOWS DRIVER" file... from the INTEL AND ASUS WEBSITE... or maybe your USB CABLE is f**? My point is... another unrelated issue where it sounds like you've not even tried it properly before complaining.. I like helping people. I don't like when people refuse to try or they skip the actual study-notes to do it... I used the EXACT same guide to unbrick and it worked in 2 mins... I'm on a 2007 Laptop which overheats if I use 4 tabs... how am I able to follow the exact same guide on a brand new "FULLY BRICKED" phone... it literally would vibrate after trying power button for 5 mins and be stuck in a "blank black screen" for hours and hours... No twrp no nothing.. and I did it - why didn't you? Same guide man...
Click to expand...
Click to collapse
Yes I know what drivers are :good: - I've tried IntelSoc, Intel ASUS etc... all drivers that are somewhere mentioned I have installed. Before the charging problem I was able to connect the phone and access files fine as well.
ryankabir said:
When the USB cable is inserted into the device, it sometimes looks like the power+vol up combination doesn't do anything when booting (either the screen stays black or it tries to boot into CM13 and fail.)
## Try again. Sometimes people accidentally hit power to early.. or whatever.. It's not a MK2 Fatality.. don't force yourself to get it exact.. Let the menu pop up... just wait a second and scroll up/down just to see if that works... then scroll to Boot-Recov and gently hit power+vUp.. should be fine.. otherwise just .. literally try 10 times.. it WILL work.
Click to expand...
Click to collapse
Thanks, will try more!
ryankabir said:
Since TWRP seems so unstable, I wanted to reflash everything using the Unbrick guide via PC
## Nope.. TWRP is like Bret Hart. It isn't unstable. Not for LP not MM not for N. Not for Stock Not for CM Not for AOSP. You *wanted* to do what you should have done right at the beginning but you didn't get that done properly (see below)
Click to expand...
Click to collapse
TWRP is indeed fine and stable! However, it freezes and reboots my phone so in my particular situation it is currently not stable. Therefore the need to completely wipe the phone and start from fresh.
ryankabir said:
Essentially you have 8 different unrelated issues (and the biggest one is not reading guides, not trying hard enough and just thinking that people like me sit around and get paid for this)... and want ans in one place w/o just doing the simple thing of going back to everything stock...?? *it's just annoying cuz people who want to help will feel like.... others don't even try simply because we exist and have desire to help...* - I am not trying to offend you but I hope you get my pov.
Click to expand...
Click to collapse
Appreciate your POV. I know how it feels like if people ask for help for something they could have read easily somewhere. I'm thankfull for all the guides that people have written on here! I'm asking for help because in my situation the guides are not working and would like to have a full clean wipe of my phone and fix all possible software issues before trowing away the phone because of hardware fault.
ryankabir said:
Do This EXACTLY
#Buy a cable. Borrow a cable. Whatever you do be 1000000% sure the USB Cable is fine
#Install Intel Asus Android drivers from official EXE (google it... don't add new post for that link)
AND THEN
Follow the same Unbrick guide word for word *but* just pay close attention to these:-
IntelSeC Driver + device detected even if OFF (start>devman>showall>intelsec
In the official unbrick utility make sure you're on the second tab at the bottom
In settings check that your device flag is 0x08..... whatever instead of the default 0x000
Back in the *second tab at the bottom* (i don't remember exact name but it's in the guide) -- put the right files (mentioned in guide) in the right boxes.. (mentioned in guide) and remember you ONLY need the DVFWthingy... + TOKENthingy + IFWthingy
Plug the Zen in... hear the "da-dumm" sound... keep looking at the Unbrick tool.. and the moment you see Device Detected = 1 you hit install/start...
AFTER that is fully done *(and if you fail don't post just repeat from scratch)... I don't personally recommend Asus Flash tool it was acting dodgy for me but instead grab the RAW Stock... Rename it to zip.. open it and grab the img files and fastboot flash the fastboot droidboot.img + splashscreen splash.img + boot boot.img + recovery recovery.img
If you've followed all that from the guide and double checked what I've put up there.. you should be fine if you just fastboot reboot bootloader... and go into stock recovery... install zip/update and put your stock OS in there..
Done.
Just please take my advice and don't skim through guides, don't think you don't need to read something, don't click stuff without double checking every line from guide, print it out on PAPER if you need to.... but please don't post like this... and don't use different guides or you will be stuck (as your heading stated..)
Forget everything you knew. Close all other tabs and use this guide thoroughly for Reference:-
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
Click to expand...
Click to collapse
Thanks for the suggestion and will try this!
timbernot said:
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Click to expand...
Click to collapse
I've tried your guide but I still have been unable to get a connection with ASUS Flashtool. The phone does keep itself relatively stable in bootloader (don't know what fixed it) - I am able to cycle through normalboot, recovery options etc without it crashing. The bootloader shows "Continue the fastboot process". I have tried different drivers, while rebooting between install/uninstall of drivers.
Thanks again all for the help
@j4y_ha
Goodluck
timbernot said:
@j4y_ha
Goodluck
Click to expand...
Click to collapse
Right m8 , we gonna fix your phone .
Do not stray from this guide.
Stick to it and you will be more the wiser when you have finished .
1 boot to boot loader ...scroll to 'power off ' and select it.
2 Connect your phone to wall charger ...let it charge till full.
When that's done , we ready for next step
timbernot said:
Wow @ryankabir
one step at a time hey
xFSTK is used to bring temp bootloader to hard bricked devices .
He has stock LP bootloader and all avenues to repair should be explored first
If anyone needs to unbrick , there is a thread in my signature below ,shows how to go from complete brick , to restoring serial number and into system within 15mins
Click to expand...
Click to collapse
Just a bit curious what the smileys in line 1 and 2 actually meant.. any hidden snarkasm these?
As for the LP stock BL he has.. after reading through the various (and really insane bugs)... I do not agree with your suggestion to explore all avenues to repair... - and my reasoning for that is... because he got stuck and paralleled different guides... i can understand the urge to have one full fix instead of going all from empty... but i'm basically thinking that if he has put in CM13 then that guide has one Unblock BL (via MMBL) - we can't be sure which one he used (downgrade to LP, unlock then upgrade etc)... + tinkering with TWRP again was it the same twrp thats with CM13.. no way to be certain
So essentially he could be fixing it al but we often totally overlook TX " RR... becausee his type has ben Mania
Cons:
Cant really tell what v BL he has.. and maybe you can try all fixes menrion
£ not a nassuve breakast
I'll try a pros/cons thing...
Pro
Th XT tool as we both said phenoenal (including prerequisites), I am assuming your footer contains the same line I pasted?
Also with his touch screen and semi-sleep state etc - could cause someone to get a permanent bootloop
There could be other mods / zips which simply outwrite each other ldurng etcs.. Now the way you're suggesting... lets say I do that.. how which one touches which sys etc would just
Con
There is defin
Mmbl came about around July 16, he run cm 13 Feb 16.
.173 or .177 is unlocked or locked LP Boot loader.
xFSTK is to gain temp Boot loader.
He gets recognised in fastboot.
He can flash stock recovery .
He can sideload .
.
.
But
Can he ?
That's not sn ide btw
Well I'm not gonna dig too deep into the twrp touch issues (there could be conflicting drivers or even something weird i noticed in twrp302 anything below 20% batt (or if batstats corrupt) then the touch goes craycray.. so lets ignore that..
this thread is getting too heavy i won't have time - so - you can always backup ur data partition so no worries there.. nothing to lose..
one problem at a time.. as I said in first post my phone was bricked much worse i had mismatched fastdroidboot and bootimg and after pressing power on maybe 4-5 times.. it would only turn on once.. sometimes on and immediately off... sometimes on stuck on logo.. sometimes on and no logo but screen is black (corrupt splash)..
so lets just try to go baaaaaack to the futureeeeeee ... Ok I found the script I made (after 8 hours of trying EVERY combination from different guides I just took individual components and made my own.. ) -
I'm writing this in a hurry so please use my first reply to get the XFTS Ubrick Guide for the Files + get the LOLLIPOP One Click BL Unlock + Lollipop Raw image... Their Guide wants you to use Asus Flash but that program failed me every time... so I have got a differnt way to do it..
I'm copying this directly from my own script (so you can change if any paths/names different)... but do not change the order or sequence
Using OneClick (keep the unlock1234 files saved separately for later use)...
If you have these unlocked I just say do it again anyway - no harm...
Unlock Bootloader for LP Stock (even if you have MM you must downgrade by this same method)
Code:
#flash old droidboot for LP stock Bootloader
fastboot flash fastboot droidboot_2_20_40_197.img
fastboot reboot-bootloader
# must run reboot bootloader once with this droidboot before continuing - dn't skip this
# unlock bootloader (use files provided inside oneclick tool but instead of using their script, manually do it - more reliable)
fastboot oem start_partitioning
fastboot flash /tmp/start.sh tools/unlock1
fastboot flash /tmp/recovery.launcher tools/unlock2
fastboot flash /system/bin/logcat tools/unlock3
fastboot flash /tmp/unlock tools/unlock4
fastboot oem stop_partitioning
#if you get failed/error at oem stop - reboot to Bootloader (VOLUP+Power long press -
Release power at Asus Logo or long vibration) and re-do the last step
#if all done so far
fastboot reboot-bootloader
#white Asus logo means unlocked loader
fastboot flash recovery twrp3.img
reboot-bootloader
#toggle Up to choose Recovery - quick tap VOLUP+Power
#twrp will start
install Custom_MM_Rom.zip
#likely it will fail giving IFW 7 error - (intentionally did NOT put MM BL here), so
install Asus_MM_WW_420_184.zip (stock on stock only)
#let it be fully done, verify working MM stock OS
#check if it works - *sign* test your touch screen quickly and in dev tools Keep Debugging ENabled
#then power off - or if you have more options directly choose reboot
#during reboot vibration hit VOLUP+P to Fastboot
####RE-DO Entire first half again
fastboot flash fastboot droidboot_2_20_40_184.img
fastboot reboot-bootloader
# must run once with this droidboot before continuing
# unlock bootloader
fastboot oem start_partitioning
fastboot flash /tmp/start.sh tools/unlock1
fastboot flash /tmp/recovery.launcher tools/unlock2
fastboot flash /system/bin/logcat tools/unlock3
fastboot flash /tmp/unlock tools/unlock4
fastboot oem stop_partitioning
fastboot reboot-bootloader
#now only flash certain MM files (the rest should already be there from stock upgrade) - if you have different MM Img (if they release new one in future - all readers just need to ensure the TOKEN DNX IfW matching)
${FASTBOOTBINARY} flash splashscreen tools/splashscreen_551.img
fastboot flash token tools/bom-token_ze551ml_4_21_40_134.bin
fastboot flash dnx dnx_ze551ml_4_21_40_134.bin
fastboot flash ifwi ifwi_ze551ml_4_21_40_134.bin
fastboot flash fastboot droidboot_4_21_40_134.img
fastboot reboot-bootloader
#should now see black splashscreen + little red error msg for 2 seconds
#entering twrp again by toggling Recovery-> VOLUP+P
install superuser.zip
wipe cache + data
install yourcustomROM.zip
ryankabir said:
Just a bit curious what the smileys in line 1 and 2 actually meant.. any hidden snarkasm these?
As for the LP stock BL he has.. after reading through the various (and really insane bugs)... I do not agree with your suggestion to explore all avenues to repair... - and my reasoning for that is... because he got stuck and paralleled different guides... i can understand the urge to have one full fix instead of going all from empty... but i'm basically thinking that if he has put in CM13 then that guide has one Unblock BL (via MMBL) - we can't be sure which one he used (downgrade to LP, unlock then upgrade etc)... + tinkering with TWRP again was it the same twrp thats with CM13.. no way to be certain
So essentially he could be fixing it al but we often totally overlook TX " RR... becausee his type has ben Mania
Cons:
Cant really tell what v BL he has.. and maybe you can try all fixes menrion
£ not a nassuve breakast
I'll try a pros/cons thing...
Pro
Th XT tool as we both said phenoenal (including prerequisites), I am assuming your footer contains the same line I pasted?
Also with his touch screen and semi-sleep state etc - could cause someone to get a permanent bootloop
There could be other mods / zips which simply outwrite each other ldurng etcs.. Now the way you're suggesting... lets say I do that.. how which one touches which sys etc would just
Con
There is defin
Click to expand...
Click to collapse

[GUIDE] QDLoader 9008 fix | EDL Mode fix

Hi everyone,
If your phone does not react on any of yours actions. You may have the same problem. This is an instruction how to fix it.
If you have a last version of Windows 10 you can easily check if it is your case (You will have "Qualcomm HS-USB QDLoader 9008" device at your Windows devices' list.
How to Fix:
1. Download Drivers Qualcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip and install it.
2. Download firmware link1 or link2
3. Install the driver
4. Unpack a firmware archive
5. Power off your phone by pressing Voice Down + Power Buttons (If your phone would be in this state too long the script would not works).
6. Start update_image_EDL.bat script - it will recreate all of the partitions
7. After the script will finish you will see the bootloader
8. Start script flashall_AFT.cmd - it will install firmware to the new partitions
9. Download fresh official firmware from asus site and put the archive at your memory card.
10. Start bootloader
11. Go to a standard recovery mode and install this firmware form the card
12. restart and repeat 10-11 (it will install software at the second state)
13. The problem is fixed. Congratulations!
Common problems:
Exception: System.DLLNotFoundException: DLL "QMSL_MSVC10R.dll": Module was not found. (HRESULT: 0x8007007E) can not be loaded.
Solution: You need to install Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package MFC. Thanks to Genim
can you please update the post with the links to the software? thanks
admirdante said:
can you please update the post with the links to the software? thanks
Click to expand...
Click to collapse
I tried, but this was my first message, so I could not manage to do it (I need at least 10 messages). However, I report it to a moderator teams. I hope they will do it for me.
Hi OP,
I have edited the links into first post for you. Enjoy.
Jerry
Forum Moderator
Thank you so much OP. You saved my phone. It's been in Edl mode for about 2 months. Now it's up and running again.
Guys if I can add one thing to the OP post .. Make sure you plug the phone in and let it charge for awhile before attempting. Once you get to the fastboot mode it will not allow you to continue if your battery is too low. I understand that you can't tell what percentage the battery is but just let it charge for 2 hours and then do the whole process. I had to stop when I got to the fastboot stuff. And then continue after 2 hours on the charge.
st3wart said:
Thank you so much OP..
Click to expand...
Click to collapse
You are welcome. It took some time, so I decided to publish it.
st3wart said:
I understand that you can't tell what percentage the battery is but just let it charge for 2 hours and then do the whole process.
Click to expand...
Click to collapse
In fact I can. I intentionally bricked my phone 3 times to write the simplest possible tutorial (my first solution was too long, because I could not understand why the problem was fixed).
I could not implement this solution when I had 6 per cent of battery, but it worked ok when I had 11 per cent. I can guess, that if it more than 10% - it is ok to implement this tutorial.
st3wart said:
Thank you so much OP. You saved my phone.
Click to expand...
Click to collapse
I'm glad it worked for you! I made it into FastBoot Mode, but when I select Recovery, it puts me back into FastBootMode.
Am I missing something or did something not work properly? Don't know how to flash the official firmware now.
In fastboot mode... Go to the extracted files and double click on the flashall_aft file and sit back and wait until it finishes.
st3wart said:
In fastboot mode... Go to the extracted files and double click on the flashall_aft file and sit back and wait until it finishes.
Click to expand...
Click to collapse
I did click it. It opened and closed cmd too fast for me to read though.
That's what it did when my battery was low... Go plug your phone in with the original charger for an hour and then go directly to your PC and plug it in and double click that file and it should do it's job.
Also check to make sure your antivirus isn't blocking the file. Mine blocked access to it for whatever reason.
I did click it. It opened and closed cmd too fast for me to read though.
Click to expand...
Click to collapse
It looks like st3wart's answer is correct. I faced the same behavior when my phone had 6 per cent of battery. This problem was fixed as soon as my phone had 11 per cent of the battery. Thus you should try to charge it before starting the script.
Furthermore, if you would still face this problem you can copy files fastboot_.log and test1.txt and share all of logs with us (or just find the error by yourself).
error from fastboot_.log:
"Writing 'partition:0'...
FAILED (remote: Warning: battery's capacity is very low)"
I did charge it for 2+ hrs with the original charger though. When I unplug it, turn it off and back on again it gives a low battery error. When I plug it back in, it goes straight back into FastBootMode.
But it seems to not charge the battery for some reason.
I did charge it for 2+ hrs with the original charger though.
Click to expand...
Click to collapse
Did you charge it in EDL mode?
For some reasons it did not work for me either. I just booted to bootloader, then power-off the phone and saw the animation of charging. You can also try to flash TWRP (using their instructions) and charge your phone in this mode.
If it does not work - please check your charger.
goldman1993 said:
Did you charge it in EDL mode?
Click to expand...
Click to collapse
As soon as I charge the phone, the FastBoot screen comes up. When I select power off, it comes right back into FastBootMode. Is there a way to force shut down so i can charge it?
Also tried installing twrp, but when I select RecoveryMode it puts me back into FastBootMode again.
When I select power off, it comes right back into FastBootMode. Is there a way to force shut down so i can charge it?
Click to expand...
Click to collapse
It is a bit abnormal behavior. I'm not sure, why it happens, to be honest. Have you tried to use different cable or charger (I'm not sure what is the reason, so I would try to change something)?
Genim said:
As soon as I charge the phone, the FastBoot screen comes up. When I select power off, it comes right back into FastBootMode. Is there a way to force shut down so i can charge it?
Also tried installing twrp, but when I select RecoveryMode it puts me back into FastBootMode again.
Click to expand...
Click to collapse
Press power button for long time to power off.
Then try flashing every image of that link:
https://forum.xda-developers.com/ze...ne-6-proton-kernel-v1-0-t3963948/post80405617
goldman1993 said:
Have you tried to use different cable or charger?
Click to expand...
Click to collapse
I have.
I unplugged the phone and let the battery run comepletely empty until the phone shut off.
Then I plugged it back in and it charged for a minute (could see the charging symbol).
It then turned itself back on into FastBoot and stopped charging again.
---------- Post added at 07:29 PM ---------- Previous post was at 07:29 PM ----------
EMJI79 said:
try flashing every image of that link
Click to expand...
Click to collapse
I did flash them, but for some images it gave me the following error:
FAILED (remote: 'Error flashing partition : volume full')
Genim said:
I did flash them, but for some images it gave me the following error:
FAILED (remote: 'Error flashing partition : volume full')
Click to expand...
Click to collapse
Not good...
Then I plugged it back in and it charged for a minute (could see the charging symbol).
It then turned itself back on into FastBoot and stopped charging again.
Click to expand...
Click to collapse
Well, we can try to brick it one more time (put it into EDL mode). Then you can try to power it up in this state and unbrick it one more time.
Firstly you need to load to bootloader and write
.\fastboot.exe --set-active=b
Then you need to reboot your phone.
I believe, that you would not successfully load to bootloader (IT would be the same EDL mode), so you can try to charge it in this state or try tutorial one more time. (After a 30 minutes of your charging process you can try tutorial one more time).
goldman1993 said:
.\fastboot.exe --set-active=b
Click to expand...
Click to collapse
I ran that command and it bricked the phone again.
But I did wait too long before running the script. I'm getting an Sahara error.
How should I proceed? Can I just run that line again?

[HELP] Bricked Begonia [SOLVED]

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!

Question No valid operation system could be found on G10

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

Categories

Resources