NIGHTLY recovery failure - Zuk Z1 Q&A, Help & Troubleshooting

Yesterday I had an update for the newest NIGHTLY Cyanogen ROM, which updated my ZUK Z1 to Cm 13 compatible to android 6.0.1
I had installed a NIGHTLY recovery and ROM on my own 3 months ago and everything was working fine. till yesterday after the update
Google Play was not compatible with my newest rom so i had to find a way to install 6.0 version of Gapps cause during the install i
kept getting a message that system partition had not enough space, which was not true.
I used ADB to re-install the latest NIGHTLY recovery and then BOOM... I got that message that bootimage was incomplete or not signed and my ZUK
bricked... It keeps loop booting and I'm not able to enter any recovery or boot in to bootloader.
Any help here would be greatful....
Thanks in advance Nick

TWRP installed on your Z1?

Monget said:
TWRP installed on your Z1?
Click to expand...
Click to collapse
Call me a noob, but I think I never istalled TWRP... Just the NIGHTLY recovery using ADB and then flashed NIGHTLY ROM via the recovery..
Now I can do nothing. I press power button, phone vibrates I see the ZUK logo, then bootloops forever..

Be optimistic your zuk is not dead.
A adb sideload with Cos 12.1 will be a good start. Download the last rom cos (Yogpas3 (of head) and go in recovery cyanogen, I think you did not flash TWRP

Monget said:
Be optimistic your zuk is not dead.
A adb sideload with Cos 12.1 will be a good start. Download the last rom cos (Yogpas3 (of head) and go in recovery cyanogen, I think you did not flash TWRP
Click to expand...
Click to collapse
I cannot enter recovery mode...
My zuk keeps boot looping forever. It just vibrates and I see the ZUK logo for less than a second. Then the same again

Nikosstamatiou said:
I cannot enter recovery mode...
My zuk keeps boot looping forever. It just vibrates and I see the ZUK logo for less than a second. Then the same again
Click to expand...
Click to collapse
i just managed to enter fastboot mode by pressing both volume + and - and then plugging the usb cable into my phone... Any ideas now?

Nikosstamatiou said:
i just managed to enter fastboot mode by pressing both volume + and - and then plugging the usb cable into my phone... Any ideas now?
Click to expand...
Click to collapse
Try to download this : http://loadbalancing.modaco.com/download.php?file=z1.recovery.testkeys.img
Put in a folder, and try an "fastboot i 0x2b4c boot z1.recovery.testkeys.img"
This requires of course that pilot is properly installed on the PC
Sorry for my bad english dude, i do my best (French)

Monget said:
Try to download this : http: // loadbalancing.modaco.com/download.php?file=z1.recovery.testkeys.img
Put in a folder, and try an "fastboot i 0x2b4c boot z1.recovery.testkeys.img"
This requires of course that pilot is properly installed on the PC
Sorry for my bad english dude, i do my best (French)
Click to expand...
Click to collapse
hehe it's ok friend I'm not english or american so we both cant speak very good english...!!!
well I've tried what you told me. I get the message that device is locked, I then try "fastboot -i 0x2b4c oem unlock"
but it won't let me unlock the device... what do I try next...??

Nikosstamatiou said:
hehe it's ok friend I'm not english or american so we both cant speak very good english...!!!
well I've tried what you told me. I get the message that device is locked, I then try "fastboot -i 0x2b4c oem unlock"
but it won't let me unlock the device... what do I try next...??
Click to expand...
Click to collapse
Hum enter "fastboot -i 0x2b4c oem unlock-go"
Any reaction after this command?

Monget said:
Hum enter "fastboot -i 0x2b4c oem unlock-go"
Any reaction after this command?
Click to expand...
Click to collapse
nope... still not letting me unlock. same with flashing unlock and flashing unlock_critical. Only that when I type these commands it seems to be doing something..
i get the "..." message like it is working on something..

SOLVED
problem finally solved, i guess..!!
I had to use QFIL application, which flashed the ZUI version again on my phone, and then booted a cyanogen recovery and a cyanogen nighlty rom..

What does
fastboot oem device-info
say?
Perhaps it is unlocked, I didn't have a proper UNLOCKED message, but the status shows the Unlocked State.
Otherwise try the original Recoveries / OS from:
https://cyngn.com/support

sirmelkor said:
What does
fastboot oem device-info
say?
Perhaps it is unlocked, I didn't have a proper UNLOCKED message, but the status shows the Unlocked State.
Otherwise try the original Recoveries / OS from:
https://cyngn.com/support
Click to expand...
Click to collapse
I think I solved it..
I had to use QFIL application, which flashed the ZUI version again on my phone, and then booted a TWRP recovery by breadcrust and a Cyannogen nighlty rom..

Nikosstamatiou said:
I think I solved it..
I had to use QFIL application, which flashed the ZUI version again on my phone, and then booted a TWRP recovery by breadcrust and a Cyannogen nighlty rom..
Click to expand...
Click to collapse
I have the same problem ..
What the steps ..knowing that I'm not an expert ..
So I hope to simplify the steps in order to get ..

alhoaoy said:
I have the same problem ..
What the steps ..knowing that I'm not an expert ..
So I hope to simplify the steps in order to get ..
Click to expand...
Click to collapse
You'll have to find QPST which is a package of applications, including QFIL. Then you need to find the ZUI ROM and recovery, which will boot again your ZUK. I'll send ypu links ASAP. You can find them for yourself if ypu are in a hurry in xda site. don't worry you'll revive it!!

Nikosstamatiou said:
You'll have to find QPST which is a package of applications, including QFIL. Then you need to find the ZUI ROM and recovery, which will boot again your ZUK. I'll send ypu links ASAP. You can find them for yourself if ypu are in a hurry in xda site. don't worry you'll revive it!!
Click to expand...
Click to collapse
I have got QFIL and ZUI ROM
But when I'm press the buttons sound and Plug the charger does not appear in QFIL

alhoaoy said:
I have got QFIL and ZUI ROM
But when I'm press the buttons sound and Plug the charger does not appear in QFIL
Click to expand...
Click to collapse
try and follow these steps:
After you installed QPST, you will get a bunch of programs associated to it, start QFIL from the QPST folder
Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go

Nikosstamatiou said:
try and follow these steps:
After you installed QPST, you will get a bunch of programs associated to it, start QFIL from the QPST folder
Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
Click to expand...
Click to collapse
Thank you for helping me
Unfortunately it did not succeed to restore device
If you get this rom cm-12.1-YOG4PAS3OH-ham-signed factory With the existence of these files inside
prog_emmc_firehose_8974.mbn
xml file + the other patch

alhoaoy said:
Thank you for helping me
Unfortunately it did not succeed to restore device
If you get this rom cm-12.1-YOG4PAS3OH-ham-signed factory With the existence of these files inside
prog_emmc_firehose_8974.mbn
xml file + the other patch
Click to expand...
Click to collapse
Did you follow the steps as described?
Was your ZUK totally bricked or not?
Mine couldn't even boot into recovery. I had a constant bootloop lasting less than a second. But I saved it.
Do you want to tell me more?

Nikosstamatiou said:
Did you follow the steps as described?
Was your ZUK totally bricked or not?
Mine couldn't even boot into recovery. I had a constant bootloop lasting less than a second. But I saved it.
Do you want to tell me more?
Click to expand...
Click to collapse
The device was on the official rom YOG4PAS3OH
because of a network problem is not solved by format
I was setup Old official rom by the official recovery
then became when running show zuk sign and then resrart and stay that way

Related

My lenovo a6000 is hard bricked. PC not detecting it.

Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
arnab8820 said:
Hello all, I have a Lenovo a6000 smartphone. It was owned by my friend. She had a problem with the android os, so she went to a local store and the there it got hard bricked. Now if I turn it on it only vibrates once. no backlight or any picture. If I press and hold vol- and power buttons together LCD backlight turns on but no display. then it goes off and then again turns on. PC does not detect it. Can anyone help me getting it out from this state?
Click to expand...
Click to collapse
Try qfil method
JovanSijacki said:
Try qfil method
Click to expand...
Click to collapse
Can you give the link please..... please note the phone is no longer detected in pc
arnab8820 said:
Can you give the link please..... please note the phone is no longer detected in pc
Click to expand...
Click to collapse
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
I already have installed the drivers. Still not detected. Even the device manager does not show a device is connected
sasukay said:
You need to have adb and fastboot drivers for your phone to correctly get detected.
Here's the LINK FOR QFIL TUTORIAL. You'll need another set of drivers called as the QCOM drivers which are mentioned in the tutorial from the above link.
Hope this helps.
Click to expand...
Click to collapse
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
arnab8820 said:
Here the phone connects in Qualcomm hs-USB...... mode. But in case of mine, it does not even show up in the device manager.
Click to expand...
Click to collapse
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
sasukay said:
You should try changing the usb cable you are using. Or maybe that guy in the local repair shop didn't put the sub PCB board back correctly.
Click to expand...
Click to collapse
There is only one pcb in it. Changing the cable does not make a difference
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
arnab8820 said:
One update. I can get into the fastboot mode. But the bootloader is locked. What to do?
Click to expand...
Click to collapse
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
arnab8820 said:
Thanks! I will try it and post the results.
Btw are you sure it does not come with a locked bootloader? I tried to flash the stock recovery and got an error saying "unknown command or device is lock"
Click to expand...
Click to collapse
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also​ try
Code:
fastboot boot recovery.img
Sometimes only this works which temporarily boots into the custom recovery.
sasukay said:
Yeah bro I'm 100% positive. I think unknown command is displayed when you flash the wrong version of recovery.
You can also​ try
Sometimes only this works which temporarily boots into the custom recovery.
Click to expand...
Click to collapse
Ok friend i will post the results tonight
sasukay said:
Lenovo A6000 doesn't come with a locked bootloader B-l
If you can boot into fastboot then you should flash twrp from it depending on the current android version of the device. If it had been on kitkat flash this TWRP v2.8.6.0 or if it has been updated to lollipop then flash the latest TWRP v3.1.0.
For this you need to first have the fastboot drivers installed and also the minimal adb and fastboot tool. Then place the required TWRP in that folder, better rename the file to 'recovery.img' and then in the CMD window which you open by Shift + Right Click first type
Code:
fastboot devices
To check whether your device is detected by the tool and haa got drivers installed correctly.
Later, if successful​, type in
Code:
fastboot flash recovery recovery.img
Then you'll have TWRP recovery installed.
Then flash any ROM on the device using it.
Click to expand...
Click to collapse
Tried the above method but no luck it gives an error: "unknown command or device is lock".
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
sasukay said:
Try this with the CWM recovery too.
BTW does your device gets detected by fastboot devices command? Also, have you tried the QPST method?
Click to expand...
Click to collapse
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
arnab8820 said:
Device gets detected by fastboot devices command. I cant try qpst because the device is not detected in any other mode except fastboot. I hv all the drivers installed
Click to expand...
Click to collapse
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
sasukay said:
You've tried booting into Download mode? It requires you to press the VOL UP + POWER KEY, then you need to select the Download mode in it to perform flashing through QPST.
Also, you never mentioned what android version was the device on, earlier.
Click to expand...
Click to collapse
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
arnab8820 said:
If i press and hold vol up and power key together the phone only vibrates once and shows nothing. And i think my friend applied the lollipop update on it. She is not sure.
Click to expand...
Click to collapse
Try fastboot oem unlock
arnab8820 said:
Tried the above method but no luck it gives an error: "unknown command or device is lock".
Click to expand...
Click to collapse
I think you are missing something (maybe).
The command is "fastboot flash recovery recovery.img"
If the recovery files name is twrp.img then command will be "fastboot flash recovery twrp.img".

[guide] how to fix totally dead redmi note 4 | stuck in bootloop | qfil flashing

Hello everyone, in today's guide I will tell you all how to fix bootloop problem in Redmi note 4
NOTE: THIS FIX IS FOR THOSE WHOSE PROBLEM DIDN'T GET FIXED EVEN AFTER FLASHING WITH MIFLASH
QFIL is a tool which is used to flash stock firmwares in Qualcomm smartphones.
Prerequisites:
1)Bricked Redmi note 4 (lol I guess you have that already if you are reading this)
2) Working USB cable (You really dont want yourself smashing your head and then finding out faulty cable)
3) QPST Version 2.7.438.3 (Google it)
4) Unlocked bootloader
5) Platform Tools (For passing OEM EDL command)
6) Stock fastboot MIUI ROM (IMPORTANT: Use V8.1.10.0.MCFMIDI from here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz)
7)QDLoader HS-USB Driver for Redmi Note 4X
Note: I'm not responsible if you mess up your device the mentioned process helped me and others in fixing our devices. You yourself are responsible!
Steps:
1) Open QFIL tool from C:\Program Files\Qualcomm\QPST\bin or wherever you installed it. Run as administrator!
Note: Don't use older version QPST, because you will get an error message when writing userdata section.
2) In QFIL choose Flat Build option.
3) Make sure you you have extracted the above ROM file onto desktop
4) In QFIL tool browse and locate .mbn file
(Named like: prog_emmc_firehose_8953_ddr.mbn)
5) Click on Load XML and select rawprogram0.xml and patch0.xml inside your Fastboot ROM folder.
6) Now turn off your phone and enter Fastboot mode by pressing ans holding power button+vol down button. After that open platform tools folder downloaded above and right click opening cmd in that folder and write following command:
fastboot oem edl
And hit enter (The above command does require your bootloader to be unlocked so kindly keep that in mind before passing the command)
7) Your phone will exit Fastboot mode and red led will start blinking and your phone will be detected as COM port in QFIL tool.
8) At last hit download button, if you did everything right process should begin and end saying download complete.
9) You can now remove your phone and keep holding power button till it boots up. First boot will take some time.
Optional step 10) If you loose your IMEI in flashing process then you can flash your IMEI using Qualcomm IMEI tool (If you face problem in this then comment and i will come up with another guide regarding IMEI flashing)
Hope it helps, if yes be sure you hit that thumbs up button it gives me good feeling lol ?
Reply if you face any problem
Peace!
addymishra said:
Hello everyone, in today's guide I will tell you all how to fix bootloop problem in Redmi note 4
NOTE: THIS FIX IS FOR THOSE WHOSE PROBLEM DIDN'T GET FIXED EVEN AFTER FLASHING WITH MIFLASH
QFIL is a tool which is used to flash stock firmwares in Qualcomm smartphones.
Prerequisites:
1)Bricked Redmi note 4 (lol I guess you have that already if you are reading this)
2) Working USB cable (You really dont want yourself smashing your head and then finding out faulty cable)
3) QPST Version 2.7.438.3 (Google it)
4) Unlocked bootloader
5) Platform Tools (For passing OEM EDL command)
6) Stock fastboot MIUI ROM (IMPORTANT: Use V8.1.10.0.MCFMIDI from here: http://bigota.d.miui.com/V8.1.10.0....DI_20161228.0000.00_6.0_global_7557bfe334.tgz)
7)QDLoader HS-USB Driver for Redmi Note 4X
Note: I'm not responsible if you mess up your device the mentioned process helped me and others in fixing our devices. You yourself are responsible!
Steps:
1) Open QFIL tool from C:\Program Files\Qualcomm\QPST\bin or wherever you installed it. Run as administrator!
Note: Don't use older version QPST, because you will get an error message when writing userdata section.
2) In QFIL choose Flat Build option.
3) Make sure you you have extracted the above ROM file onto desktop
4) In QFIL tool browse and locate .mbn file
(Named like: prog_emmc_firehose_8953_ddr.mbn)
5) Click on Load XML and select rawprogram0.xml and patch0.xml inside your Fastboot ROM folder.
6) Now turn off your phone and enter Fastboot mode by pressing ans holding power button+vol down button. After that open platform tools folder downloaded above and right click opening cmd in that folder and write following command:
fastboot oem edl
And hit enter
7) Your phone will exit Fastboot mode and red led will start blinking and your phone will be detected as COM port in QFIL tool.
8) At last hit download button, if you did everything right process should begin and end saying download complete.
9) You can now remove your phone and keep holding power button till it boots up. First boot will take some time.
Optional step 10) If you loose your IMEI in flashing process then you can flash your IMEI using Qualcomm IMEI tool (If you face problem in this then comment and i will come up with another guide regarding IMEI flashing)
Hope it helps, if yes be sure you hit that thumbs up button it gives me good feeling lol
Reply if you face any problem
Peace!
Click to expand...
Click to collapse
Hi,
after your manual, download success, the device restarts, but it then gets stuck with the MI logo?
What can I do?
sieg
sieg01 said:
Hi,
after your manual, download success, the device restarts, but it then gets stuck with the MI logo?
What can I do?
sieg
Click to expand...
Click to collapse
Hello there,
First of all make sure that you are flashing the fastboot rom which I mentioned in the thread.
Now coming to your problem, open QFIL tool and open configuration panel. You will see many options, check for 'Erase before Download' option and make sure its unchecked then try flashing again. If the problem persist then send me screenshot of QFIL tool along with configuration.
All the best!
addymishra said:
Hello there,
First of all make sure that you are flashing the fastboot rom which I mentioned in the thread.
Now coming to your problem, open QFIL tool and open configuration panel. You will see many options, check for 'Erase before Download' option and make sure its unchecked then try flashing again. If the problem persist then send me screenshot of QFIL tool along with configuration.
All the best!
Click to expand...
Click to collapse
Hi again,
I have flashed again and in the " download configuration " I set " Erase before Download", please see the Attachment, unfortunately the same device restarts, but it then gets stuck with the MI logo?
sieg01 said:
Hi again,
I have flashed again and in the " download configuration " I set " Erase before Download", please see the Attachment, unfortunately the same device restarts, but it then gets stuck with the MI logo?
Click to expand...
Click to collapse
Dear, you DON'T NEED TO SELECT "ERASE BEFORE DOWNLOAD" !!! Now listen carefully what to do-:
1) Download mi flash tool and mi unlock tool
2) Your bootloader must be locked now so unlock it with mi unlock (Don't worry just use your mi account it will unlock successfully)
3) Once unlocked flash the fastboot rom in fastboot mode using mi flash tool. IMPORTANT: MAKE SURE YOU SELECT "CLEAN ALL" OPTION
4) Now when flashed your device will restart. Dont let it boot up. Press and hold power+volume down button till you enter into fastboot
5) From fastboot enter EDL mode using "fastboot oem edl" command. Red light will blink
6) Open QFIL and make sure "Erase before download" IS *NOT* SELECTED
7)Click download and you should be good to go
All the best
addymishra said:
Dear, you DON'T NEED TO SELECT "ERASE BEFORE DOWNLOAD" !!! Now listen carefully what to do-:
1) Download mi flash tool and mi unlock tool
2) Your bootloader must be locked now so unlock it with mi unlock (Don't worry just use your mi account it will unlock successfully)
3) Once unlocked flash the fastboot rom in fastboot mode using mi flash tool. IMPORTANT: MAKE SURE YOU SELECT "CLEAN ALL" OPTION
4) Now when flashed your device will restart. Dont let it boot up. Press and hold power+volume down button till you enter into fastboot
5) From fastboot enter EDL mode using "fastboot oem edl" command. Red light will blink
6) Open QFIL and make sure "Erase before download" IS *NOT* SELECTED
7)Click download and you should be good to go
All the best
Click to expand...
Click to collapse
1. My redmi is unlocked ( from Xiaomi )
2. MI flash tool don`t work, because I get error: can not found file flash_all.bat, so I dont`t use this tool
sieg01 said:
1. My redmi is unlocked ( from Xiaomi )
2. MI flash tool don`t work, because I get error: can not found file flash_all.bat, so I dont`t use this tool
Click to expand...
Click to collapse
In order to use mi flash correctly kindly place the fastboot rom in C: drive root directory then try flashing, it will work. Its a bug of mi flash
Hi I followed your all 9 steps in the first post. However, me too is stuck in 'mi' logo nothing happens waiting after 10 minutes
Then I followed the following steps, flashed by mi tool followed by QFIL. But my QFIL didn't have "ERASE BEFORE DOWNLOAD" option. I downloaded the exact QPST version 2.7.438.3 from gsmhosting forum.
Still the phone boots and stuck with 'mi' logo forever. I have tried flashing other ROMs like RR, lineageOS from TWRP but each of the ROM is stuck while booting . Only miuiPro "miuipro_v7.0_mido_v9.2.1.0_NCFCNEK.zip" manages to boot but keeps rebooting after every 2-3 seconds. My phone has been useless for 3 long days.
addymishra said:
Dear, you DON'T NEED TO SELECT "ERASE BEFORE DOWNLOAD" !!! Now listen carefully what to do-:
1) Download mi flash tool and mi unlock tool
2) Your bootloader must be locked now so unlock it with mi unlock (Don't worry just use your mi account it will unlock successfully)
3) Once unlocked flash the fastboot rom in fastboot mode using mi flash tool. IMPORTANT: MAKE SURE YOU SELECT "CLEAN ALL" OPTION
4) Now when flashed your device will restart. Dont let it boot up. Press and hold power+volume down button till you enter into fastboot
5) From fastboot enter EDL mode using "fastboot oem edl" command. Red light will blink
6) Open QFIL and make sure "Erase before download" IS *NOT* SELECTED
7)Click download and you should be good to go
All the best
Click to expand...
Click to collapse
biits1993 said:
Hi I followed your all 9 steps in the first post. However, me too is stuck in 'mi' logo nothing happens waiting after 10 minutes
Then I followed the following steps, flashed by mi tool followed by QFIL. But my QFIL didn't have "ERASE BEFORE DOWNLOAD" option. I downloaded the exact QPST version 2.7.438.3 from gsmhosting forum.
Still the phone boots and stuck with 'mi' logo forever. I have tried flashing other ROMs like RR, lineageOS from TWRP but each of the ROM is stuck while booting . Only miuiPro "miuipro_v7.0_mido_v9.2.1.0_NCFCNEK.zip" manages to boot but keeps rebooting after every 2-3 seconds. My phone has been useless for 3 long days.
Click to expand...
Click to collapse
Try downloading the lastest version from here:
https://androidmtk.com/download-qpst-flash-tool
Erase before download must be unchecked
And remember first boot does take some time so be patient a little. Hope it works!
addymishra said:
Try downloading the lastest version from here:
https://androidmtk.com/download-qpst-flash-tool
Erase before download must be unchecked
And remember first boot does take some time so be patient a little. Hope it works!
Click to expand...
Click to collapse
Hi, Thank you very much, I managed to boot the ROM using QFil , however in setup wizard I can't get past the getting device security info in mi account setup. Besides, dialogues for lots "app stopped working" keeps coming. and also there are frequent reboots
addymishra said:
In order to use mi flash correctly kindly place the fastboot rom in C: drive root directory then try flashing, it will work. Its a bug of mi flash
Click to expand...
Click to collapse
Hi,
II managed to flash successfully with MIflash tool, but after switching it on
do I have permanent boot loop with MI logo? Andere Fastboot ROM`s will MIflash nicht machen. Please look my Screenshot.
Greating
biits1993 said:
Hi, Thank you very much, I managed to boot the ROM using QFil , however in setup wizard I can't get past the getting device security info in mi account setup. Besides, dialogues for lots "app stopped working" keeps coming. and also there are frequent reboots
Click to expand...
Click to collapse
Strange :/ you can try miflash tool for that case. Download the lastest mi flash tool, enter into EDL mode using "fastboot oem edl" command then in mi flash drop down menu in left corner select "flash_factory.bat" and click flash. It will take around 400 seconds. Make sure you are in edl mode with red blinking light otherwise it will wipe your IMEI. Hope it works!
sieg01 said:
Hi,
II managed to flash successfully with MIflash tool, but after switching it on
do I have permanent boot loop with MI logo? Andere Fastboot ROM`s will MIflash nicht machen. Please look my Screenshot.
Greating
Click to expand...
Click to collapse
Are you able to enter into setup wizard? If not then try the procedure I posted above using factory flash. After flashing with mi flash once again try flashing with QFIL. It's sometimes hit or miss :/
addymishra said:
Are you able to enter into setup wizard? If not then try the procedure I posted above using factory flash. After flashing with mi flash once again try flashing with QFIL. It's sometimes hit or miss :/
Click to expand...
Click to collapse
Hi,
I don`t able to enter into setup wizard, because boot-loop, so I done following:
1. mi flash factory flash-successfully
2. mi flash flash once again-successfully
3. flashing with QFIL- successfully
After switch-on again boot loop every 22 seconds with mi-logo
Do you have any more tips for me?
Greating
sieg
sieg01 said:
Hi,
I don`t able to enter into setup wizard, because boot-loop, so I done following:
1. mi flash factory flash-successfully
2. mi flash flash once again-successfully
3. flashing with QFIL- successfully
After switch-on again boot loop every 22 seconds with mi-logo
Do you have any more tips for me?
Greating
sieg
Click to expand...
Click to collapse
Man, I think its some sort of hardware issue then. Or maybe your messed up your blobs or your partitions real bad and corrupted them. QFIL helped in my case. Got no more tips, maybe its time to visit service center brother One last shot you can give is to try flashing with QFIL first then with Mi Flash. That's last hope! All the best!
flash failed in QFIL please help
sohanaw said:
flash failed in QFIL please help
Click to expand...
Click to collapse
Which version of QFIL and which ROM are you flashing with? I managed to flash the said version in OP through QFIL without any error. However, other official versions like 9.xx fail to be flashed by QFIL
A solution that worked after all these troubles
Hi everyone,
This post is for those who are still struggling with 'cool' bootloop in Redmi note 4x irrespective of stock, custom ROMS, you are flashing.
Before all these steps I flashed "mido_global_images_V8.1.10.0.MCFMIDI_20161228.0000.00_6.0_global_7557bfe334.tgz" using QFIL first, then miFlash tool. I was greeted by "can't decrypt phone".
Refer to the OP
Then I flashed lazy_flasher and managed to boot into the stock ROM but couldn't get past the Mi account setup. Even my Keyboard app keeps stopping, so annoying.
The the below Steps I followed redeemed me of this agony powered by xiaomi:
1. Downloaded this firmware==>"global-mido-firmware-7.12.14.zip"
Mokee ROM==>"MK71.2-mido-201803080920-NIGHTLY"
open gapps arm-64, 7.1, pico
open gapps arm-64, 7.1, nano [BOTH] from gapps
2. flashed TWRP=3.1.1-0[official version] from the xda
Code:
fastboot flash recovery [name_of_recovery_image_of_twrp]
3. Entered into Recovery==>WIPE=>Advanced WIPE=> select all partitions==>WIPE[can leave Internal storage unchecked]
4. Then Format Data==>yes
5. Copied firmware, Mokee ROM, pico and nano gapps [4 items] to internal storage
6. Flashed downloaded firmware, then MOKEE ROM, then gapps-nano
7. Reboot to recovery
8. After entering Recovery, Reboot to system
Hopefully we will see mi logo, then Mokee robot animating soon enough. It will take you to setup wizard within 5-10 minutes, If you see any Google apps [Gboard in my case] stopping,
it may mean that google Play services were not installed properly[Don't know why]. In my case I couldn't set up Google account/framework first time. If it happens, go to settings,
enable developer options tapping BUILD version==>then enable USB debugging.
Then reboot to Recovery
Flash gapps-pico.
Do factory reset from Recovery, simple wipe.
Then reboot to System.[DON'T install TWRP as system app etc]
For me, this time I was able to setup google account from the setup wizard. Google service framework has been working without any issues. [ Again Don't know why]
This time I have been able to install my desired apps from playstore
Few more words:
Firstly, I tried flashing only pico, but I couldn't set up the google account, no matter how many times I reboot to recovery, wipe Dalvik-cache etc, then flash pico.
I described exactly what I did that worked out for me. There could be many possible orders, combinations, but I don't have time for that.
I tried to flash Alexy's "RR-N-v5.8.5-20180121mido_alexy.zip" ROM in combination with this firmware but it just will hang TWRP while flashing. only this MOKEE ROM worked with this firmware for me.
I wasted full 3 days for fixing this device. And no intention to tinker with it anymore, my communication has been in a mess!.
While in stock MIUI 'google *apps keeps stopping" just annoyed me as hell, so decided to switch, and after 3 days of disgusting 'Waiting period for bootloader UNLOCK' I couldn't even install a working stock
MIUI ROM now, maybe cheap hardware issue offered by Xiaomi. They have just made everything complex. This is my first and last device from them. My previous Moto G3 was amazing and would be with me had it not been stolen
Will be happy to help regarding this issue, and thank you the OP of this thread, who helped me realize that this device is still able to boot.
Wishing everyone in this note 4x trouble good luck!!
biits1993 said:
Hi everyone,
This post is for those who are still struggling with 'cool' bootloop in Redmi note 4x irrespective of stock, custom ROMS, you are flashing.
Before all these steps I flashed "mido_global_images_V8.1.10.0.MCFMIDI_20161228.0000.00_6.0_global_7557bfe334.tgz" using QFIL first, then miFlash tool. I was greeted by "can't decrypt phone".
Refer to the OP
Then I flashed lazy_flasher and managed to boot into the stock ROM but couldn't get past the Mi account setup. Even my Keyboard app keeps stopping, so annoying.
The the below Steps I followed redeemed me of this agony powered by xiaomi:
1. Downloaded this firmware==>"global-mido-firmware-7.12.14.zip"
Mokee ROM==>"MK71.2-mido-201803080920-NIGHTLY"
open gapps arm-64, 7.1, pico
open gapps arm-64, 7.1, nano [BOTH] from gapps
2. flashed TWRP=3.1.1-0[official version] from the xda
Code:
fastboot flash recovery [name_of_recovery_image_of_twrp]
3. Entered into Recovery==>WIPE=>Advanced WIPE=> select all partitions==>WIPE[can leave Internal storage unchecked]
4. Then Format Data==>yes
5. Copied firmware, Mokee ROM, pico and nano gapps [4 items] to internal storage
6. Flashed downloaded firmware, then MOKEE ROM, then gapps-nano
7. Reboot to recovery
8. After entering Recovery, Reboot to system
Hopefully we will see mi logo, then Mokee robot animating soon enough. It will take you to setup wizard within 5-10 minutes, If you see any Google apps [Gboard in my case] stopping,
it may mean that google Play services were not installed properly[Don't know why]. In my case I couldn't set up Google account/framework first time. If it happens, go to settings,
enable developer options tapping BUILD version==>then enable USB debugging.
Then reboot to Recovery
Flash gapps-pico.
Do factory reset from Recovery, simple wipe.
Then reboot to System.[DON'T install TWRP as system app etc]
For me, this time I was able to setup google account from the setup wizard. Google service framework has been working without any issues. [ Again Don't know why]
This time I have been able to install my desired apps from playstore
Few more words:
Firstly, I tried flashing only pico, but I couldn't set up the google account, no matter how many times I reboot to recovery, wipe Dalvik-cache etc, then flash pico.
I described exactly what I did that worked out for me. There could be many possible orders, combinations, but I don't have time for that.
I tried to flash Alexy's "RR-N-v5.8.5-20180121mido_alexy.zip" ROM in combination with this firmware but it just will hang TWRP while flashing. only this MOKEE ROM worked with this firmware for me.
I wasted full 3 days for fixing this device. And no intention to tinker with it anymore, my communication has been in a mess!.
While in stock MIUI 'google *apps keeps stopping" just annoyed me as hell, so decided to switch, and after 3 days of disgusting 'Waiting period for bootloader UNLOCK' I couldn't even install a working stock
MIUI ROM now, maybe cheap hardware issue offered by Xiaomi. They have just made everything complex. This is my first and last device from them. My previous Moto G3 was amazing and would be with me had it not been stolen
Will be happy to help regarding this issue, and thank you the OP of this thread, who helped me realize that this device is still able to boot.
Wishing everyone in this note 4x trouble good luck!!
Click to expand...
Click to collapse
will try this tonight, thanks bhai
sohanaw said:
will try this tonight, thanks bhai
Click to expand...
Click to collapse
Let me know bro what happens, hope it works for you
I wanted to use RR rom though, but in the end no ROM worked for me except this one. So I'm just happy with it.

Axon 7 (A2017G) Brick.

I had stock android 7, used the toolkit, "Unlocked" the bootloader, after that there was a part with erasing all data to factory due to an error, something along the lines there was a pin or password detected, and after I pressed reset the screen went black, and when it tries to boot it shows ZTE for a second and then it vibrates and shuts off instantly. So I can get it in to edl mode and I see the Qualcomm HS-USB QDLoader 9008 in my devices, but I can't find any thread to fix this. Tried flashing stock firmwares via MiFlash, no luck. And the thing is, most roms I download give me a batch of files in a zip, if I put them in a folder and try to flash I get this - Object reference not set to an instance of an object. Help asap, because I am having a horrible time using my partially destroyed S6 Edge Plus. If I spelled smth wrong sorry, Russian here.
This is what I had - My device is stuck on an 'Enter your password to start Android' screen.
Unfortunately this requires a factory reset.
1) Boot your device into recovery mode by pressing and holding the power and volume up buttons for 10-15 seconds.
2) Stock Recovery: Use the volume down key to go down to 'Wipe data/factory reset' and press power to select. Press the volume down key again to go down to 'Yes' and press power to select.
TWRP Recovery: Tap "Wipe" < Tap "Advanced Wipe" < Check the box next to "data" < Tap "Repair or change file system" < Tap "EXT4" < Swipe to confirm.
3) Reboot your device.
Jazkade said:
I had stock android 7, used the toolkit, "Unlocked" the bootloader, after that there was a part with erasing all data to factory due to an error, something along the lines there was a pin or password detected, and after I pressed reset the screen went black, and when it tries to boot it shows ZTE for a second and then it vibrates and shuts off instantly. So I can get it in to edl mode and I see the Qualcomm HS-USB QDLoader 9008 in my devices, but I can't find any thread to fix this. Tried flashing stock firmwares via MiFlash, no luck. And the thing is, most roms I download give me a batch of files in a zip, if I put them in a folder and try to flash I get this - Object reference not set to an instance of an object. Help asap, because I am having a horrible time using my partially destroyed S6 Edge Plus. If I spelled smth wrong sorry, Russian here.
Click to expand...
Click to collapse
I had a similar problem on my 2017U model after flashing a .zip that was supposed to remove the "bootloader is unlocked" screen that shows up after you unlock the bootloader. Long story short, the .zip wasn't meant for U models. Only G. So my phone was in a worse situation than yours and would not power on. You'll need to download an EDL recovery firmware .zip for your phone and place it within the toolkits folders manually and then go through the steps of the toolkit which I'll try to help you do.
First, download the full stock B09 (G) firmware from here. You can OTA update to the latest firmware after a successful flash. It's okay to flash an older firmware in this situation.
Once done, navigate to C:\Axon7Development\Axon7Toolkit\MiFlash\B09\ (copy/move the full .zip of the B09 firmware you downloaded in the first step into this folder) If the B09 folder doesn't exist under \MiFlash, create it manually.
Run the toolkit again from the start and type 11 "RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)" and hit enter. On the next screen type in the number that will restore B09. It should tell you how to put the phone in EDL mode and automatically open MiFlash. Make sure to follow the steps and paste the directory path of the firmware in the top bar in MiFlash. After you pasted it his Flash and it should successfully flash the firmware. If it gives you an error or times out, unplug the phone and try a different USB port or USB cable. It's obviously recommended you use the one that came with the phone. My first attempt at MiFlash timed out and didn't flash anything. I tried a different USB port and then it flashed.
After it flashes the firmware, leave the phone plugged in and hold down the power button for about 10 seconds until it restarts out of EDL. From there you should have a working phone again with some exceptions. It'll be on an older firmware so I would recommend booting into stock recovery and factory resetting data and wiping your cache. Then restart the phone and do an OTA update to the latest firmware. After you reach the latest firmware you can then use the toolkit for whatever you need.
Sidenote, your English is very good considering you're Russian. No need to apologize because your post had no spelling errors. :highfive:
brian117 said:
I had a similar problem on my 2017U model after flashing a .zip that was supposed to remove the "bootloader is unlocked" screen that shows up after you unlock the bootloader. Long story short, the .zip wasn't meant for U models. Only G. So my phone was in a worse situation than yours and would not power on. You'll need to download an EDL recovery firmware .zip for your phone and place it within the toolkits folders manually and then go through the steps of the toolkit which I'll try to help you do.
First, download the full stock B09 (G) firmware from here. You can OTA update to the latest firmware after a successful flash. It's okay to flash an older firmware in this situation.
Once done, navigate to C:\Axon7Development\Axon7Toolkit\MiFlash\B09\ (copy/move the full .zip of the B09 firmware you downloaded in the first step into this folder) If the B09 folder doesn't exist under \MiFlash, create it manually.
Run the toolkit again from the start and type 11 "RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)" and hit enter. On the next screen type in the number that will restore B09. It should tell you how to put the phone in EDL mode and automatically open MiFlash. Make sure to follow the steps and paste the directory path of the firmware in the top bar in MiFlash. After you pasted it his Flash and it should successfully flash the firmware. If it gives you an error or times out, unplug the phone and try a different USB port or USB cable. It's obviously recommended you use the one that came with the phone. My first attempt at MiFlash timed out and didn't flash anything. I tried a different USB port and then it flashed.
After it flashes the firmware, leave the phone plugged in and hold down the power button for about 10 seconds until it restarts out of EDL. From there you should have a working phone again with some exceptions. It'll be on an older firmware so I would recommend booting into stock recovery and factory resetting data and wiping your cache. Then restart the phone and do an OTA update to the latest firmware. After you reach the latest firmware you can then use the toolkit for whatever you need.
Sidenote, your English is very good considering you're Russian. No need to apologize because your post had no spelling errors. :highfive:
Click to expand...
Click to collapse
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.
Jazkade said:
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.
Click to expand...
Click to collapse
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable
Jazkade said:
When I type in 11 I don't have any options, it forces me to download B10, but when it tries it fails.
Click to expand...
Click to collapse
Did you create the B09 folder in the MiFlash directory? I also had errors downloading firmwares through the toolkit, which is why I had to do it manually and move the firmware into the proper directory for the toolkit.
brian117 said:
Did you create the B09 folder in the MiFlash directory? I also had errors downloading firmwares through the toolkit, which is why I had to do it manually and move the firmware into the proper directory for the toolkit.
Click to expand...
Click to collapse
Yes I did
Choose an username... said:
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable
Click to expand...
Click to collapse
Can you give me a link pls?
Choose an username... said:
I haven't read what the other guy said, but basically you have to use miflash. just use my DFU unbrick guide but from the point where you short the testpad to enter EDL. But instead of opening the phone just put it in edl via adb reboot edl or holding vol+ - and inserting the cable
Click to expand...
Click to collapse
Flashing in progress.. please may this work..
Oh yeis boiz, the phone is alive! And the main lol is, we have a guy that fixes devices for a living, and he was trashtalking that the Axon 7 is a trash phone and fixing it is a piece of cake, and he failed, and here I am thanks to you with a woring phone! I love you people, and xda in general!
EDIT: Seems you got it working. Congrats.
Jazkade said:
Oh yeis boiz, the phone is alive! And the main lol is, we have a guy that fixes devices for a living, and he was trashtalking that the Axon 7 is a trash phone and fixing it is a piece of cake, and he failed, and here I am thanks to you with a woring phone! I love you people, and xda in general!
Click to expand...
Click to collapse
Choose an username... said:
Click to expand...
Click to collapse
After I unlocked the bootloader via the toolkit by bkores, I get a message "To start android enter your password" even though it was a stock system with no password. Like I got every possible error and solved it and now this, just why?
Jazkade said:
After I unlocked the bootloader via the toolkit by bkores, I get a message "To start android enter your password" even though it was a stock system with no password. Like I got every possible error and solved it and now this, just why?
Click to expand...
Click to collapse
that's totally normal. Your internal storage is encrypted, you have to go into TWRP and format data (not wipe, format). Anyways by unlocking you lose all of your data so it's not like you lose anything
If it doesn't work, then you'll have to change the data partition's filesystem because it may be in F2FS. Change it back to ext4 if that happens
Choose an username... said:
that's totally normal. Your internal storage is encrypted, you have to go into TWRP and format data (not wipe, format). Anyways by unlocking you lose all of your data so it's not like you lose anything
If it doesn't work, then you'll have to change the data partition's filesystem because it may be in F2FS. Change it back to ext4 if that happens
Click to expand...
Click to collapse
I don't have TWRP, firs I Unlocked the bootloader, now I try to flash TWRP and get error due to the force encryption on Nougat, and I can't find a way to disable it, also now when I try to boot to stock recovery the led flashes for a milisecond and powers off.
Jazkade said:
I don't have TWRP, firs I Unlocked the bootloader, now I try to flash TWRP and get error due to the force encryption on Nougat, and I can't find a way to disable it, also now when I try to boot to stock recovery the led flashes for a milisecond and powers off.
Click to expand...
Click to collapse
Enter fastboot and type the command "fastboot erase userdata
Choose an username... said:
Enter fastboot and type the command "fastboot erase userdata
Click to expand...
Click to collapse
adb reboot fastboot and it just reboots normally.
Jazkade said:
adb reboot fastboot and it just reboots normally.
Click to expand...
Click to collapse
Well whatever then just install TWRP. Use controllerboy's guide
Choose an username... said:
Well whatever then just install TWRP. Use controllerboy's guide
Click to expand...
Click to collapse
idk how to downgrade to marshmellow.
Choose an username... said:
Well whatever then just install TWRP. Use controllerboy's guide
Click to expand...
Click to collapse
downgraded, unlocked, twrp is up and running

Looking for help installing TWRP

I have now spent the entire day trying to get this thing to work, and having used up all the help from xda, I am asking you guys for help. Here's my situation:
I am trying to install TWRP on my Zenfone Max Pro M1. So I followed all the guides available, and downloaded the drivers, unlock.bat, TWRP img etc and did what I have always done on all my phones.
My computer also recognizes the device when I try fastboot devices. But the second I try to fastboot flash recovery twrp.img, the phone goes onto a black screen with "Press any key to shut down" written on it. I have tried every combination out there, and I don't know what to do now.
Please help.
Did you unlock boot loader? After that press volume up and power button,then you can enter fastboot screen. After that use fastboot flash recovery twrp.img
I have same problem plz help
1. boot into fastboot.
2. make sure fastboot can see the device 'fastboot devices'
3. fastboot flash recovery twrp-xxx.img
4. boot into twrp.
Did that work?
chr0 said:
I have now spent the entire day trying to get this thing to work, and having used up all the help from xda, I am asking you guys for help. Here's my situation:
I am trying to install TWRP on my Zenfone Max Pro M1. So I followed all the guides available, and downloaded the drivers, unlock.bat, TWRP img etc and did what I have always done on all my phones.
My computer also recognizes the device when I try fastboot devices. But the second I try to fastboot flash recovery twrp.img, the phone goes onto a black screen with "Press any key to shut down" written on it. I have tried every combination out there, and I don't know what to do now.
Please help.
Click to expand...
Click to collapse
Did you find any solution to this problem?
Utsav_vats said:
Did you find any solution to this problem?
Click to expand...
Click to collapse
Yes. Use Powershell instead of the normal cmd
chr0 said:
Yes. Use Powershell instead of the normal cmd
Click to expand...
Click to collapse
No, you must have done something else too. I'm trying to use fastboot mode to flash the fastboot firmware using Asus Flash Tool but as soon as AFT detects the device, it goes all black with the screen saying" press any key to shut down". Did you installed any other drivers or used any other system to do it?
Utsav_vats said:
Did you find any solution to this problem?
Click to expand...
Click to collapse
Utsav_vats said:
No, you must have done something else too. I'm trying to use fastboot mode to flash the fastboot firmware using Asus Flash Tool but as soon as AFT detects the device, it goes all black with the screen saying" press any key to shut down". Did you installed any other drivers or used any other system to do it?
Click to expand...
Click to collapse
Nope. Just used Powershell to execute the bat file and then push TWRP.
CMD wasn't working for me.

The system has been destroyed please help

So I flashed the stock pie rom from this forum, came from pixel experience 9. After I flashed the ROM I also flashed the twrp installer and when I rebooted it says the system has been destroyed and press the power button to shut down. I can boot the phone in fastboot but it doesn't recognise it even though the drivers are installed and it worked perfectly before. The miflash program also doesn't recognise anything after I press refresh.
Is there anything I can do?
Boot into TWRP (by booting not flashing) and get a flashable rom with twrp for ex. https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
emiljano539 said:
Boot into TWRP (by booting not flashing) and get a flashable rom with twrp for ex. https://forum.xda-developers.com/mi-a1/development/twrp-stock-8-1-0-t3856328
Click to expand...
Click to collapse
I can't boot into recovery, the error message pops up on the screen
lvnatic said:
I can't boot into recovery, the error message pops up on the screen
Click to expand...
Click to collapse
You have to boot to twrp from the bootloder screen.
Use this recovery to boot from pc and never Flash twrp on pie.
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
lvnatic said:
So I flashed the stock pie rom from this forum, came from pixel experience 9. After I flashed the ROM I also flashed the twrp installer and when I rebooted it says the system has been destroyed and press the power button to shut down. I can boot the phone in fastboot but it doesn't recognise it even though the drivers are installed and it worked perfectly before. The miflash program also doesn't recognise anything after I press refresh.
Is there anything I can do?
Click to expand...
Click to collapse
Again unlock boot loader.
lvnatic said:
I can't boot into recovery, the error message pops up on the screen
Click to expand...
Click to collapse
As others set go into fastboot then use this command "fastboot boot TheNameOfTWRP.img"
emiljano539 said:
As others set go into fastboot then use this command "fastboot boot TheNameOfTWRP.img"
Click to expand...
Click to collapse
I tried that and fastboot doesnt recognise my device at all. When I simply type fastboot the device should appear with a code, wll when I type it nothing happes.
lvnatic said:
I tried that and fastboot doesnt recognise my device at all. When I simply type fastboot the device should appear with a code, wll when I type it nothing happes.
Click to expand...
Click to collapse
Strange. Do you have installed drivers/do you have used before adb in ur pc with mi a1?
emiljano539 said:
Strange. Do you have installed drivers/do you have used before adb in ur pc with mi a1?
Click to expand...
Click to collapse
Yes, I also have a redmi note 5 Pro and a mipad 4 and both work well with ADB.
Try flashint stock on EDL mode.
Same error with me today. Tried to restart 5 times. Its unbelievable but the fix was very easy. Just run "fastboot continue" and wait for 2 minutes for a working reboot!
Thanks for the Solution
Inferi0r said:
Same error with me today. Tried to restart 5 times. Its unbelievable but the fix was very easy. Just run "fastboot continue" and wait for 2 minutes for a working reboot!
Click to expand...
Click to collapse
Thanks for the solution. Worked for me as well for similar problem. A simplified step by step if anyone still couldn't get it to work.
Power off your phone as asked by the Error Message
Press Volume Down + Power button simultaneously to boot into fastboot.
Load Command Prompt in the ADB/Fastboot folder in your PC (ADB and other drivers need to be installed)
Type "fastboot continue" and press enter
And you are done. If your phone is not recognized by the PC (after you put it to fastboot mode) make sure you have proper Drivers installed for your devices. You can use MiFlashTools to install required drivers automatically.
yagya said:
Thanks for the solution. Worked for me as well for similar problem. A simplified step by step if anyone still couldn't get it to work.
Power off your phone as asked by the Error Message
Press Volume Down + Power button simultaneously to boot into fastboot.
Load Command Prompt in the ADB/Fastboot folder in your PC (ADB and other drivers need to be installed)
Type "fastboot continue" and press enter
And you are done. If your phone is not recognized by the PC (after you put it to fastboot mode) make sure you have proper Drivers installed for your devices. You can use MiFlashTools to install required drivers automatically.
Click to expand...
Click to collapse
Thanks for this. This happened to me two weeks ago, had to completely flash stock rom and begin from zero. Hopefully others will see this and avoid starting fresh.

Categories

Resources