Develop Bugs

MIUI 10 Update from China 10.0.6.0 OEDCNFH to Global 10.0.1.0 OEDMIFH problems

Really need help!
I successfully unlocked my Mi Max 3 using the official process. 14 day wait. No issues...booted back into MIUI 10' restored backup from MiCloud and was back to normal, except now it showed "unlocked" on startup screen.
It was running CN MIUI 10 V10.0.6.0 OEDCNFH
I had been reading that it was possible to flash the device with the global version of the ROM
I had several Google related issues with the Chinese ROM so I downloaded the MiFlash tool (2018.5.28.0), got the ROM from here: https://xiaomifirmware.com/roms/latest-official-miui-roms-for-xiaomi-mi-max-3/
and tried to flash it with Global 10.0.1.0 OEDMIFH
Result was the error "flash crclist error"
screenshot here
https://1drv.ms/u/s!ArN9mSbbMVT8gohpA03ob7X2FhjspQ
After this, the device is stuck in Fastboot mode and seems to no longer have a bootable ROM. Booting into recovery mode with vol up + power and restarting that way also just boots back into Fastboot.
I downloaded the Fastboot version of the ROM the phone was originally running 10.0.6.0 OEDCNFH and tried to flash that.
It also failed with the same error.
This user had the same issue with a Mi8:
https://forum.xda-developers.com/mi-8/help/failed-to-install-global-rom-via-mi-t3851636
The thread did not help me. There seems to be almost nothing related to this issue "flash crclist error" on XDA
My phone is not bootable now. No idea what to try next, I am a total novice in this area. I have since been reading about Anti Rollback Protection, I just don't know if this has anything to do with my issue. My device is not dead....it is booting into Fastboot, and I can still see it in MiFlash. If anyone could advise me I would be very grateful.

https://forum.xda-developers.com/mi-max-3/how-to/to-youre-stuck-edl-mode-black-screen-t3837846/page2
See my post there on page 2. It should fix your issue.

The path of the rom seems too long.
Create a new folder at the root of your C drive and give it a name without spaces, move all the contents of the extracted rom to that folder and try to flash again

opasha - thanks for reply
opasha said:
https://forum.xda-developers.com/mi-max-3/how-to/to-youre-stuck-edl-mode-black-screen-t3837846/page2
See my post there on page 2. It should fix your issue.
Click to expand...
Click to collapse
Hi and thank you for responding to my question.
I have tried the steps in your thread as follows:
1) Download Global Stable fastboot 10.0.1.0 from this thread: https://forum.xda-developers.com/mi-...-t3827503/amp/
2) Open MiFlashTool and navigate to 10.0.1.0 fastboot rom. At the bottom select 'Clean All Only' (do NOT select clean all and lock).
3) Hold power, volume up and volume down together for 10 seconds after plugging into PC. Your pc should detect your phone in EDL mode. Hit REFRESH button at the top of MiFlashTool and it will show up as COM XX or XXX for your USB connection. Try whichever USB port works. Then hit refresh. Then click Flash.
When I try step 3, what you describe does not seem to be the behaviour I am seeing. If I hold volume up + volume down + power simultaneously for 10 seconds, the device reboots straight back into the Fastboot screen (the one with the bunny). Is this normal? If not, what screen should be displayed on the device? There is no sign of MiFlash tool detecting the device differently at this point (COM XX or XXX)
When I refresh MiFlash it detects the device as pictured:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEJOYos6rGjNSM8vQ
If I flash it, it produces the same "flash crclist error" pictured here:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEIec-cB8pUMAVqLg
FYI the only way I can get the device to start in anything other than the Fastboot screen is to hold down the VOLUME UP key + power. This boots it into the Mi-Recovery 3.0 screen where I can see the Main Menu with 3 buttons: Reboot - Wipe Data - Connect with MiAssistant
Reboot goes back to Fastboot
Wipe Data also just reboots into Fastboot.
Connect with MiAssistant prompts to connect to Mi PC suite with diagram of device + USB cable + URL (I tried this but PC suite (version 3.2.1.3111_2717) does not recognise my device....this was also the case when the phone was working normally). If I don't try to connect with USB cable at this point it times out after about 30 seconds and boots back into the Fastboot screen.
The remaining steps in your thread did not seem to apply after step 3 failed.
No idea what to do. I posted this on MIUI forums too. Some people are suggesting I use ADB and install TWRP but I would need an idiots guide, I don't have any experience with either and would have no idea what I was doing....and I'm finding it extremely difficult to unearth anything useful from the **vast** number of Android related sites and forums relating to ROMs etc. For example, I can't find anything helpful about "flash crclist error". Maybe I should ask Xiaomi support?
At this point I just need to get *any* working ROM onto the device. I would not have unlocked it and attempted the switch from Chinese to Global if I hadn't read so much advice that this could be done very simply and without issues as long as the bootloader was unlocked. If you have any other advice for me please let me know!
Thanks again.

richard.rea said:
Hi and thank you for responding to my question.
I have tried the steps in your thread as follows:
1) Download Global Stable fastboot 10.0.1.0 from this thread: https://forum.xda-developers.com/mi-...-t3827503/amp/
2) Open MiFlashTool and navigate to 10.0.1.0 fastboot rom. At the bottom select 'Clean All Only' (do NOT select clean all and lock).
3) Hold power, volume up and volume down together for 10 seconds after plugging into PC. Your pc should detect your phone in EDL mode. Hit REFRESH button at the top of MiFlashTool and it will show up as COM XX or XXX for your USB connection. Try whichever USB port works. Then hit refresh. Then click Flash.
When I try step 3, what you describe does not seem to be the behaviour I am seeing. If I hold volume up + volume down + power simultaneously for 10 seconds, the device reboots straight back into the Fastboot screen (the one with the bunny). Is this normal? If not, what screen should be displayed on the device? There is no sign of MiFlash tool detecting the device differently at this point (COM XX or XXX)
When I refresh MiFlash it detects the device as pictured:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEJOYos6rGjNSM8vQ
If I flash it, it produces the same "flash crclist error" pictured here:
https://1drv.ms/u/s!ArN9mSbbMVT8gpEIec-cB8pUMAVqLg
FYI the only way I can get the device to start in anything other than the Fastboot screen is to hold down the VOLUME UP key + power. This boots it into the Mi-Recovery 3.0 screen where I can see the Main Menu with 3 buttons: Reboot - Wipe Data - Connect with MiAssistant
Reboot goes back to Fastboot
Wipe Data also just reboots into Fastboot.
Connect with MiAssistant prompts to connect to Mi PC suite with diagram of device + USB cable + URL (I tried this but PC suite (version 3.2.1.3111_2717) does not recognise my device....this was also the case when the phone was working normally). If I don't try to connect with USB cable at this point it times out after about 30 seconds and boots back into the Fastboot screen.
The remaining steps in your thread did not seem to apply after step 3 failed.
No idea what to do. I posted this on MIUI forums too. Some people are suggesting I use ADB and install TWRP but I would need an idiots guide, I don't have any experience with either and would have no idea what I was doing....and I'm finding it extremely difficult to unearth anything useful from the **vast** number of Android related sites and forums relating to ROMs etc. For example, I can't find anything helpful about "flash crclist error". Maybe I should ask Xiaomi support?
At this point I just need to get *any* working ROM onto the device. I would not have unlocked it and attempted the switch from Chinese to Global if I hadn't read so much advice that this could be done very simply and without issues as long as the bootloader was unlocked. If you have any other advice for me please let me know!
Thanks again.
Click to expand...
Click to collapse
Sorry, didn't realize this was new to you. Your fastboot mode is fine. Ignore my step 3 (my apologies for not clarifying since this step is not needed for you since your phone is in fastboot). All you need to do is have your phone flash this version of miui global through Miflash Tool. Let it reboot on its own.

can not flash ROM
opasha said:
Sorry, didn't realize this was new to you. Your fastboot mode is fine. Ignore my step 3 (my apologies for not clarifying since this step is not needed for you since your phone is in fastboot). All you need to do is have your phone flash this version of miui global through Miflash Tool. Let it reboot on its own.
Click to expand...
Click to collapse
I can not flash the ROM Global Stable fastboot 10.0.1.0 (or any other ROM I have tried)
In the MiFlash tool I get the error "flash crclist error" as I have tried to explain in my previous posts.

richard.rea said:
I can not flash the ROM Global Stable fastboot 10.0.1.0 (or any other ROM I have tried)
In the MiFlash tool I get the error "flash crclist error" as I have tried to explain in my previous posts.
Click to expand...
Click to collapse
You're not extracting properly. Use 7zip. Then extract the folder and point Miflash to this extracted folder. - make sure inside this folder there are simply files and no other single folders - single folders within single folders usually means you have to extract again.

Just run the damn flash-all.bat for God sake...

SOLVED thank you!
opasha said:
You're not extracting properly. Use 7zip. Then extract the folder and point Miflash to this extracted folder. - make sure inside this folder there are simply files and no other single folders - single folders within single folders usually means you have to extract again.
Click to expand...
Click to collapse
You were right. I extracted using 7Zip instead of Winzip. Pointed MiFlash at the extracted folder. 10.0.1.0 Global flashed successfully.
**HUGE** thanks to you for your replies and help. Painful learning curve for me. Very happy to get my phone working again, this time with the ROM I wanted.
Thanks again
best regards

so im on the same version but xiaomi.eu... 10.0.6.0 can i go downgrade that global? using same method?

flashed over x.eu 10.0.6.0 with Global 10.0.1.0 using Miflash with fastboot rom, it rebooted into recovery screen saying "this version cannot be installed on this device"...at this point i started crying lol.
Plugged into mi suite to see if i could recover back to original china rom it shipped with, discovered the BL was locked again, unlocked again via mi tool and hey presto, it booted up with fully working Global rom!
I'm now in a good place.

flashed over x.eu 10.0.6.0 with Global 10.0.1.0 using Miflash with fastboot rom, it rebooted into recovery screen saying "this version cannot be installed on this device"...at this point i started crying lol.
Plugged into mi suite to see if i could recover back to original china rom it shipped with, discovered the BL was locked again, unlocked again via mi tool and hey presto, it booted up with fully working Global rom!
I'm now in a good place.

Repair your ROG2 phone with EDL mode，Official firmware！

Success is disgusted by some people, and will not share any files for free in the future.

Success!!!
This is awesome! Thanks much. I don't understand what you mean by "Factory setting must be restored after booting" though. Do you mean you need to go into Recovery mode and wipe the data?
Here's some instructions I put together that would have helped save me a lot of time. Please correct anything I missed:
After you have downloaded the zip file, here are the step-by-step instructions:
1. Extract the zipped folder wherever you want on your PC.
2. Open a CMD window.
3. cd /d <whatever path it is to the "\ASUS_ROG2_ZS660KL_QPST_Firmware\images" folder> e.g., "cd /d D:\RogPhoneII\ASUS_ROG2_ZS660KL_QPST_Firmware\images"
4. Make sure your PC is connected to the side port of your phone and the phone is in fastboot mode (Volume UP button + Power button).
5. Check and make sure your PC is connected properly by entering "fastboot devices" in the command window. You should see the ID of your device.
6. Then enter "fastboot oem enter-dload" in the command window. This will put the phone in emergency download mode (EDL). My phone went all black.
7. Open "\ASUS_ROG2_ZS660KL_QPST_Firmware\MiFlash2018-5-28-0" folder. Launch "XiaoMiFlash.exe".
8. Click "refresh". You should see a device in the list.
9. Click "select" and navigate to the "\ASUS_ROG2_ZS660KL_QPST_Firmware\images" folder.
10. Click "flash". Wait until it says "success".
11. After it's done, you'll hold down the UP button, Down button, and Power button on the phone at the same time until it shuts down.
12. Hold Up button and Power button at same to boot into fastboot mode again. Select Recovery mode by using the Up/Down buttons on the phone. Press the Power button to select.
13. Select "wipe data" from the drop down list. Go down the list of "no" until you get to the "yes" and press the Power button.
14. Select "reboot now".
15. Done.

greywookiee said:
This is awesome! Thanks much. I don't understand what you mean by "Factory setting must be restored after booting" though. Do you mean you need to go into Recovery mode and wipe the data?
Here's some instructions I put together that would have helped save me a lot of time. Please correct anything I missed:
After you have downloaded the zip file, here are the step-by-step instructions:
1. Extract the zipped folder wherever you want on your PC.
2. Open a CMD window.
3. cd /d <whatever path it is to the "\ASUS_ROG2_ZS660KL_QPST_Firmware\images" folder> e.g., "cd /d D:\RogPhoneII\ASUS_ROG2_ZS660KL_QPST_Firmware\images"
4. Make sure your PC is connected to the side port of your phone and the phone is in fastboot mode (Volume UP button + Power button).
5. Check and make sure your PC is connected properly by entering "fastboot devices" in the command window. You should see the ID of your device.
6. Then enter "fastboot oem enter-dload" in the command window. This will put the phone in emergency download mode (EDL). My phone went all black.
7. Open "\ASUS_ROG2_ZS660KL_QPST_Firmware\MiFlash2018-5-28-0" folder. Launch "XiaoMiFlash.exe".
8. Click "refresh". You should see a device in the list.
9. Click "select" and navigate to the "\ASUS_ROG2_ZS660KL_QPST_Firmware\images" folder.
10. Click "flash". Wait until it says "success".
11. After it's done, you'll hold down the UP button, Down button, and Power button on the phone at the same time until it shuts down.
12. Hold Up button and Power button at same to boot into fastboot mode again. Select Recovery mode by using the Up/Down buttons on the phone. Press the Power button to select.
13. Select "wipe data" from the drop down list. Go down the list of "no" until you get to the "yes" and press the Power button.
14. Select "reboot now".
15. Done.
Click to expand...
Click to collapse
Hi is the ASUS_ROG2_ZS660KL_QPST_Firmware\images
Folder in the zip you posted? Where do I find it?

PJay83 said:
Hi is the ASUS_ROG2_ZS660KL_QPST_Firmware\images
Folder in the zip you posted? Where do I find it?
Click to expand...
Click to collapse
The first entry of this thread.

Is the official firmware WW or CN?
I'm just thinking this is probably an easier way for CN guys to get WW if the QPST fw is WW

cheetah2k said:
Is the official firmware WW or CN?
I'm just thinking this is probably an easier way for CN guys to get WW if the QPST fw is WW
Click to expand...
Click to collapse
ww

greywookiee said:
This is awesome! Thanks much. I don't understand what you mean by "Factory setting must be restored after booting" though. Do you mean you need to go into Recovery mode and wipe the data?
Here's some instructions I put together that would have helped save me a lot of time. Please correct anything I missed:
After you have downloaded the zip file, here are the step-by-step instructions:
1. Extract the zipped folder wherever you want on your PC.
2. Open a CMD window.
3. cd /d <whatever path it is to the "\ASUS_ROG2_ZS660KL_QPST_Firmware\images" folder> e.g., "cd /d D:\RogPhoneII\ASUS_ROG2_ZS660KL_QPST_Firmware\images"
4. Make sure your PC is connected to the side port of your phone and the phone is in fastboot mode (Volume UP button + Power button).
5. Check and make sure your PC is connected properly by entering "fastboot devices" in the command window. You should see the ID of your device.
6. Then enter "fastboot oem enter-dload" in the command window. This will put the phone in emergency download mode (EDL). My phone went all black.
7. Open "\ASUS_ROG2_ZS660KL_QPST_Firmware\MiFlash2018-5-28-0" folder. Launch "XiaoMiFlash.exe".
8. Click "refresh". You should see a device in the list.
9. Click "select" and navigate to the "\ASUS_ROG2_ZS660KL_QPST_Firmware\images" folder.
10. Click "flash". Wait until it says "success".
11. After it's done, you'll hold down the UP button, Down button, and Power button on the phone at the same time until it shuts down.
12. Hold Up button and Power button at same to boot into fastboot mode again. Select Recovery mode by using the Up/Down buttons on the phone. Press the Power button to select.
13. Select "wipe data" from the drop down list. Go down the list of "no" until you get to the "yes" and press the Power button.
14. Select "reboot now".
15. Done.
Click to expand...
Click to collapse
Yes

cheetah2k said:
Is the official firmware WW or CN?
I'm just thinking this is probably an easier way for CN guys to get WW if the QPST fw is WW
Click to expand...
Click to collapse
I think you're right.
---------- Post added at 07:56 AM ---------- Previous post was at 07:53 AM ----------
greywookiee said:
I think you're right.
Click to expand...
Click to collapse
Though, you still want to be able to do updates and stuff without needing someone to break all the files out into separate images. This was a huge life saver thanks to John.

Please help me. I have widevine security L3 instead of L1 (also at relock bootloader). Here is what happen to me:
1. Unlock the bootloader and get persist.img, but wrong size of package then i have lost the serial number (C4ATAS000000). The size of persist file is 16mb instead of 32mb by default.
2. Try to get another persist.img from another device, then use Ultra editor to find and change back to my real Serial Number. And it worked.
3. Figure out widevine security is always stay at L3, whenever bootloader is re-locked. Also Asus unlock bootloader apk from asus homepage is not working, it said "error network".
4. Do flash raw from all version, also factory reset...etc but no luck.
.............................................
Do you know what is really happened when we flash wrong persist.img and flash another persist (which is already change Serial number back to real one)?

Mistake

If your phone can only enter EDL mode (9008 mode)
this firmware is glad to help you. It can be flashed in through
the QPST tool, or it can be flashed in through the Xiaomi miflash tool.
To use the QPST tool, you must change the EMMC to UFS. No matter which tool you use,
you must restore the factory settings after the phone is turned on, otherwise the storage
of the phone will recognize the error! !! !!
Factory settings must be restored after booting! !! !!
The firmware is made through the official package UL-ASUS_I001_1-ASUS-16.0631.1910.35-1.1.207-user.zip
without any modification, Suitable for repairing phones that can only enter edl mode(9008 mode).
File Downlaod link:https://drive.google.com/open?id=1Pk...Sf6cDq7SuJiBBu
Click to expand...
Click to collapse
godmode post! thank you sir! Fixed my bricked rog 2

johnny886 said:
If your phone can only enter EDL mode (9008 mode)
this firmware is glad to help you. It can be flashed in through
the QPST tool, or it can be flashed in through the Xiaomi miflash tool.
To use the QPST tool, you must change the EMMC to UFS. No matter which tool you use,
you must restore the factory settings after the phone is turned on, otherwise the storage
of the phone will recognize the error! !! !!
Factory settings must be restored after booting! !! !!
The firmware is made through the official package UL-ASUS_I001_1-ASUS-16.0631.1910.35-1.1.207-user.zip
without any modification, Suitable for repairing phones that can only enter edl mode(9008 mode).
File Downlaod link:https://drive.google.com/open?id=1Pkt2k82JtK66DzJn3tSf6cDq7SuJiBBu
Click to expand...
Click to collapse
How do I change To use the QPST tool, you must change the EMMC to UFS. No matter which tool you use.

ltth said:
How do I change To use the QPST tool, you must change the EMMC to UFS. No matter which tool you use.
Click to expand...
Click to collapse
Thanks!

ltth said:
Thanks!
Click to expand...
Click to collapse
Hi, I've managed to unbrick my ROG Phone II Tencent Edition 8/128 with a locked bootloader having "slot _a" error. Provided that you can do fastboot.
My equipment for flashing, for sure you already have ADB installed in your computer, my computer is an x64 Intel Windows 10 laptop, I used USB 2.0 not USB 3.0
Credit to @johnny886 for the sharing the tool,
"If your phone can only enter EDL mode (9008 mode)
this firmware is glad to help you. It can be flashed in through
the QPST tool, or it can be flashed in through the Xiaomi miflash tool.
To use the QPST tool, you must change the EMMC to UFS. No matter which tool you use, -(I personally :did" not change anything, I just downloaded the file and followed grewookie's instruction below )
you must restore the factory settings after the phone is turned on, otherwise the storage
of the phone will recognize the error! !! !!
Factory settings must be restored after booting! !! !!
The firmware is made through the official package UL-ASUS_I001_1-ASUS-16.0631.1910.35-1.1.207-user.zip
without any modification, Suitable for repairing phones that can only enter edl mode(9008 mode).
File Downlaod link: https://drive.google.com/open?id=1Pk...Sf6cDq7SuJiBBu"
Credits to @greywookiee for the super clear instruction:
"Here's some instructions I put together that would have helped save me a lot of time. Please correct anything I missed:
After you have downloaded the zip file, here are the step-by-step instructions:
1. Extract the zipped folder wherever you want on your PC.
2. Open a CMD window.
3. cd /d <whatever path it is to the "\ASUS_ROG2_ZS660KL_QPST_Firmware\images" folder> e.g., "cd /d D:\RogPhoneII\ASUS_ROG2_ZS660KL_QPST_Firmware\imag es"
4. Make sure your PC is connected to the side port of your phone and the phone is in fastboot mode (Volume UP button + Power button).
5. Check and make sure your PC is connected properly by entering "fastboot devices" in the command window. You should see the ID of your device.
6. Then enter "fastboot oem enter-dload" in the command window. This will put the phone in emergency download mode (EDL). My phone went all black.
7. Open "\ASUS_ROG2_ZS660KL_QPST_Firmware\MiFlash2018-5-28-0" folder. Launch "XiaoMiFlash.exe".
8. Click "refresh". You should see a device in the list.
9. Click "select" and navigate to the "\ASUS_ROG2_ZS660KL_QPST_Firmware\images" folder.
10. Click "flash". Wait until it says "success".
11. After it's done, you'll hold down the UP button, Down button, and Power button on the phone at the same time until it shuts down.
12. Hold Up button and Power button at same to boot into fastboot mode again. Select Recovery mode by using the Up/Down buttons on the phone. Press the Power button to select.
13. Select "wipe data" from the drop down list. Go down the list of "no" until you get to the "yes" and press the Power button.
14. Select "reboot now".
15. Done."

followed the steps until number 8 after i clicked refresh the MI app stopped responding (not responding).. dont know what im doing wrong..

tuannghia1985 said:
Please help me. I have widevine security L3 instead of L1 (also at relock bootloader). Here is what happen to me:
1. Unlock the bootloader and get persist.img, but wrong size of package then i have lost the serial number (C4ATAS000000). The size of persist file is 16mb instead of 32mb by default.
2. Try to get another persist.img from another device, then use Ultra editor to find and change back to my real Serial Number. And it worked.
3. Figure out widevine security is always stay at L3, whenever bootloader is re-locked. Also Asus unlock bootloader apk from asus homepage is not working, it said "error network".
4. Do flash raw from all version, also factory reset...etc but no luck.
.............................................
Do you know what is really happened when we flash wrong persist.img and flash another persist (which is already change Serial number back to real one)?
Click to expand...
Click to collapse
请问要怎么得到另一个设备的persist.img，然后怎么编辑sn，最后要怎么写入手机？有具体的步骤 吗
Mod Traduction :
May I ask how to get the persist.img of another device, then how to edit the sn, and finally how to write it to the phone? Are there specific steps?
Click to expand...
Click to collapse

葫芦娃搞奥特曼 said:
请问要怎么得到另一个设备的persist.img，然后怎么编辑sn，最后要怎么写入手机？有具体的步骤 吗
Click to expand...
Click to collapse
Get another user persist.img (with correct 32.768 kb)
Using HEX editor or Ultra Edit to find SSN, ISN and IMEI in persist.img
Return to fastboot - then 9008 mode, use bat to write back to your phone and you will have back Asus unlock bootloader apk (working), have Serial number back.
For question: "How could i find real SSN, ISN and real IMEI?"
Please use command "fastboot oem device-info" in fastboot mode, it will show your real information.
Br,

greywookiee said:
This is awesome! Thanks much. I don't understand what you mean by "Factory setting must be restored after booting" though. Do you mean you need to go into Recovery mode and wipe the data?
Here's some instructions I put together that would have helped save me a lot of time. Please correct anything I missed:
After you have downloaded the zip file, here are the step-by-step instructions:
1. Extract the zipped folder wherever you want on your PC.
2. Open a CMD window.
3. cd /d <whatever path it is to the "\ASUS_ROG2_ZS660KL_QPST_Firmware\images" folder> e.g., "cd /d D:\RogPhoneII\ASUS_ROG2_ZS660KL_QPST_Firmware\images"
4. Make sure your PC is connected to the side port of your phone and the phone is in fastboot mode (Volume UP button + Power button).
5. Check and make sure your PC is connected properly by entering "fastboot devices" in the command window. You should see the ID of your device.
6. Then enter "fastboot oem enter-dload" in the command window. This will put the phone in emergency download mode (EDL). My phone went all black.
7. Open "\ASUS_ROG2_ZS660KL_QPST_Firmware\MiFlash2018-5-28-0" folder. Launch "XiaoMiFlash.exe".
8. Click "refresh". You should see a device in the list.
9. Click "select" and navigate to the "\ASUS_ROG2_ZS660KL_QPST_Firmware\images" folder.
10. Click "flash". Wait until it says "success".
11. After it's done, you'll hold down the UP button, Down button, and Power button on the phone at the same time until it shuts down.
12. Hold Up button and Power button at same to boot into fastboot mode again. Select Recovery mode by using the Up/Down buttons on the phone. Press the Power button to select.
13. Select "wipe data" from the drop down list. Go down the list of "no" until you get to the "yes" and press the Power button.
14. Select "reboot now".
15. Done.
Click to expand...
Click to collapse
johnny886 said:
If your phone can only enter EDL mode (9008 mode)
this firmware is glad to help you. It can be flashed in through
the QPST tool, or it can be flashed in through the Xiaomi miflash tool.
To use the QPST tool, you must change the EMMC to UFS. No matter which tool you use,
you must restore the factory settings after the phone is turned on, otherwise the storage
of the phone will recognize the error! !! !!
Factory settings must be restored after booting! !! !!
The firmware is made through the official package UL-ASUS_I001_1-ASUS-16.0631.1910.35-1.1.207-user.zip
without any modification, Suitable for repairing phones that can only enter edl mode(9008 mode).
File Downlaod link:https://drive.google.com/open?id=1Pkt2k82JtK66DzJn3tSf6cDq7SuJiBBu
Click to expand...
Click to collapse
Just 2 doubts:
1. Will I get OTA update after doing this?
2. I am on A10 Beta 6. will It be successful to roll back to this firmware?

Hi in Mi Flash when i refresh and select flash it gives me an error object reference not set to an instance of an object please help me

Help
Gives me Sarahah error on QPST and also gives a flash error on MI flash

[RMN8Pro][Global] Bootloop fix

Evening guys, let's fix the Bootloop of our RMN8Pro if we have installed a menu Recovery TWRP faulty/unsuitable or we have installed a ROM that does not belong to our smartphone.
This method is valid for China to global or Global to global.
NOT FOR INDIAN (sorry about that)
You'll need:
ADB files
Fastboot ROM V10.4.5.0.PGGEUXM
Download both files and unzip them in C:/ADB (if you don't have that folder... just create it)
You will need to rename the file extension of the file <<begonia_eea_global_images_V10.4.5.0.PGGEUXM_20191007.0000.0000_9.0_eea_f796762f8a.tgz>> from .tgz to .rar
Let's go!!
Turn the phone off, turn it on in fastboot mode (by pressing both POWER and VOL- ) and connect the phone to the PC with its USB cable.
Open a CMD command console (in administrator mode) in C:/ADB and type this (press enter when finished typing):
Code:
fastboot devices
If you have the drivers installed and everything goes well, a series of alphanumeric characters will appear, such as for example:
Code:
a6ghfxfv6 fastboot
Perfect, we can go on.
Next we will flash one by one the files needed to revive the phone.
Write the following lines and press enter at the end of each of them (wait for the files to be installed between line and line):
Code:
fastboot boot boot.img
fastboot flash system.img
fastboot flash vendor.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img
When you're done, restart the phone with:
Code:
fastboot reboot
Congratulations, you have your RMN8Pro fixed.

klurosu said:
Evening, let's fix the Bootloop of our RMN8Pro if we have installed a menu Recovery TWRP faulty/unsuitable or we have installed a ROM that does not belong to our phone.
This method is valid for China to global or Global to global.
NOT FOR INDIAN (sorry about that)
You'll need:
ADB files
Fastboot ROM V10.4.5.0.PGGEUXM
Download both files and unzip them in C:/ADB (if you don't have that folder...create it)
You will need to rename the file extension of the file <<begonia_eea_global_images_V10.4.5.0.PGGEUXM_20191007.0000.0000_9.0_eea_f796762f8a.tgz>> from .tgz to .rar
Let's go!!
Turn the phone off, turn it on in fastboot mode (by pressing both POWER and VOL- ) and connect the phone to the PC with its USB cable.
Open a CMD command console (in administrator mode) in C:/ADB and type this (press enter when finished typing):
If you have the drivers installed and everything goes well, a series of alphanumeric characters will appear, such as for example:
Perfect, we can go on.
Next we will flash one by one the files needed to revive the phone.
Write the following lines and press enter at the end of each of them (wait for the files to be installed between line and line):
When you're done, restart the phone with:
Congratulations, you have your RMN8Pro fixed.
Click to expand...
Click to collapse
So, this is basically a guide of how to flash the images through fastboot, right? Why not just use MiFlash when we are in fastboot mode?

polfrank said:
So, this is basically a guide of how to flash the images through fastboot, right? Why not just use MiFlash when we are in fastboot mode?
Click to expand...
Click to collapse
Because it doesn't work???
Don't believe me?, Just try
send from an RMN8 Pro (xiaomi.eu custom rom)

Miflash will work if in fastboot and have an MI account had requested to unlock BL.
Don't believe me? You try.

idog8818 said:
Miflash will work if in fastboot and have an MI account had requested to unlock BL.
Don't believe me? You try.
Click to expand...
Click to collapse
You still need authorized account Sherlock.
(Omg this guys...)
send from an RMN8 Pro (xiaomi.eu custom rom)

klurosu said:
You still need authorized account Sherlock.
(Omg this guys...)
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
if you don't apply for the Mi account to unlock BL, how will you able to flash anything? Only 2 mins for a new account.....What the problem will be?

idog8818 said:
if you don't apply for the Mi account to unlock BL, how will you able to flash anything? Only 2 mins for a new account.....What the problem will be?
Click to expand...
Click to collapse
Read again (this time read well please) 2 posts above
send from an RMN8 Pro (xiaomi.eu custom rom)

klurosu said:
Read again (this time read well please) 2 posts above
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
Read again but didn't get it. What do you mean ....

idog8818 said:
Read again but didn't get it. What do you mean ....
Click to expand...
Click to collapse
That you still need an Authorized Xiaomi's Account to do that with the old method dude.
send from an RMN8 Pro (xiaomi.eu custom rom)

klurosu said:
That you still need an Authorized Xiaomi's Account to do that with the old method dude.
send from an RMN8 Pro (xiaomi.eu custom rom)
Click to expand...
Click to collapse
What do you mean by Authorized Xiaomi's Account?? As far as I know, there're 2 types of Mi accounts we commonly talk here.
1. Normal Mi account: used to unlock BL and this can be used in miflash to flash rom, I've tried 100 times in fastboot, and works every time. I registered this account I guess 5 years ago when I need to request unlock BL on note 3 . As I said above, it needs 2 mins to register.
2. Authorised service account: This is not we can easy to register, It's for Mi service center or developers for repair/develop purposes. If no rec, no recovery, blank screen, it can be recovered by SP flash tool, which will need this type of account. This is also why users in following post looking for unbricking.
[GUIDE] [begonia] UNBRICK - stuck on DA mode / Authorised Service Account required
https://forum.xda-developers.com/re...a-mode-authorised-t4000433/page7#post81175069
---------- Post added at 01:20 AM ---------- Previous post was at 01:17 AM ----------
I can prove this by my bricked redmi note 8 pro.
I used my mi account to unlock BL, flashed global rom, but I cannot use it in SP FLASH TOOL to restore because my MI account is not an Authorised Service Account

Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?

nutellamarco said:
Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?
Click to expand...
Click to collapse
At the moment you only can do a deep flashing in EDL mode, and need an authorized account... You need to contact someone with this type of account and flash... ( And give some money...)

nutellamarco said:
Hello,
I have a nex Redmi Note 8 pro, I unlocked it after I use Ifixit.. to install twrp, the phone was in bootloap, after I tried to flash with fastboot commands. Now the phone is off and I have a black screeen. I can't power it on (vol + or -) does not work. power on no more. It is not recognized with miunlock. No fastboot nor recovery. Please help me how I can do?
Click to expand...
Click to collapse
Some people are saying they managed to bring to life a phone without rocovery without fastboot mode.search and maybe you find a way. As i remember they said with phone turned off you press volume - and power and you have about 5 seconds to flash. I don't know more details.i wish you success

hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.

nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.
Click to expand...
Click to collapse
as far as I know spflash tool should be ready to flash,. it means with all the files selected, the combination is keeping vol+ and connect the USB cable to PC port, I recommend you search in Google about flashing mediatek devices... Good luck

Literally this guide is really about just how to flash with fastboot instead of Mi Flash(tool which can use anyone with Xiaomi Phone - doesn't require Authorized Service ACC)
nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.
Click to expand...
Click to collapse
I had this problem at the weekend(Stuck at EDL mode - tried to flash with SP tool but without success(needed service acc - brom error)), you can use SP flash tool with authorized service acc - fastest way, maybe there will be some cracked security file in the future as one for redmi 6. Or do battery trick. You are stick at EDL mode and cannot reboot from it. You can wait to discharge your phone(Tooks ~2 day with pushed power button) then connect into computer and when the led turn less bright use vol - + power to get into fastboot or disconnect battery and reconnect with pushed vol - to get into fastboot(I have used this three times because of installing wrong recovery).

Aglik-x said:
Literally this guide is really about just how to flash with fastboot instead of Mi Flash(tool which can use anyone with Xiaomi Phone - doesn't require Authorized Service ACC)
I had this problem at the weekend(Stuck at EDL mode - tried to flash with SP tool but without success(needed service acc - brom error)), you can use SP flash tool with authorized service acc - fastest way, maybe there will be some cracked security file in the future as one for redmi 6. Or do battery trick. You are stick at EDL mode and cannot reboot from it. You can wait to discharge your phone(Tooks ~2 day with pushed power button) then connect into computer and when the led turn less bright use vol - + power to get into fastboot or disconnect battery and reconnect with pushed vol - to get into fastboot(I have used this three times because of installing wrong recovery).
Click to expand...
Click to collapse
Thanks a lot for your reply
I will do that. But How I can know that phone is on to discharge battery? Best regards

nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.[/QUOTE
My oneplus 6 I used to do kind of the same thing... With the phone plugged and everything ready to flash... I used to press - plus power button and it would starting the process..
Click to expand...
Click to collapse

petenoni said:
nutellamarco said:
hello
thanks for your ideas, I can't enter in fastboot mode nor recovery. The screeen is black. When I tried with spflash, when I push together vol+ and vol- i hear a noise, but nothing happens with spflash.
I am trying. I think it is loosed.[/QUOTE
My oneplus 6 I used to do kind of the same thing... With the phone plugged and everything ready to flash... I used to press - plus power button and it would starting the process..
Click to expand...
Click to collapse
I try this method, the spflash does not start
I tried all touche combinaisons.
I will wait until the battery were empty and try again.
Thanks for your reply
Click to expand...
Click to collapse

bootloop fix worked for me
I try to post this yesterday but nothing happened so what i did was...
i installed TWRP and in twrp i wipe all data , system, vendor and reboot phone. that was wrong and i stuck in bootloop. so i go back to fastboot and type commands as u say....
fastboot boot boot.img
fastboot flash system.img
fastboot flash vendor.img
fastboot flash cust cust.img
fastboot flash recovery recovery.img - nothing worked
maybe u forgot some commands.... so i use...
fastboot boot boot.img -dont use, it didnt work
fastboot flash system system.img -ok
fastboot flash vendor vendor.img -ok
fastboot flash cust cust.img -ok
fastboot flash recovery recovery.img - but instead of official recovery i used TWRP.img and after reboot a finally boot into TWRP and i flash xiaomi.eu rom and after reboot magisk and all works fine. im not developer but this method worked for me and excuse my english i have global device

Bootloader Unlock and Root Instruction - No Octoplus Box Required

Do you want to bootloader and unlock and root your V35? Do you want to do this yourself? Are you feeling the need for some adventure? If you answered yes to these questions, then you are at the right place. The goal with these instructions is to make the process as smooth and pain-free as possible. These instructions are based upon what I know works through firsthand experience and what I have gathered reading. My experience is with an AT&T branded V350AWM. Others also report success. That said, there can still be problems leading to bricked phone so don’t continue if you are not comfortable with the risk. An unavoidable side-effect of bootloader unlocking is that all data on your phone will be erased. Make a back up if you don’t want to lose it permanently.
This is what you will be doing in a nutshell.
Setting the phone into a baseline Oreo conditions
Extraction of abl, laf, and boot partititions
Installation of the engineering abl and erasing the laf's using QFIL
Unlocking the phone
Flashing to Pie and maybe Q in the future if you want to update from Oreo
Generation and installation of a magisk-patched boot image for root
Upon successful completion, you will have a fresh, bootloader unlocked and rooted phone that is otherwise stock.
Preparation and requirements:
On the hardware side, you will need a PC with MS Windows installed either directly or as a virtual machine and a high quality USB cable designed for data transfer. Older USB 2.0 hardware is preferred when working with LG phones. There is a long list of software to install.
Minimal adb and fastboot
Instructions: https://forum.xda-developers.com/showthread.php?t=2317790
Download: https://www.androidfilehost.com/?fid=746010030569952951
The LG mobile drivers, http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Dev-Patched LGUP
Instructions and warnings in post #6 with thanks to @ChazzMatt: https://forum.xda-developers.com/lg-v35/help/att-v35-unlocked-wont-verizon-t3958765
Download with thanks to @tecknight for the software: https://androidfilehost.com/?fid=11410963190603845019
9008 Port Driver:
https://raw.githubusercontent.com/g...alcomm_QDLoader_HS-USB_Driver_64bit_Setup.zip
QPST with QFIIL
Some basic instructions: https://androidmtk.com/use-qpst-flash-tool
Download: https://qpsttool.com/qpst-tool-v2-7-480
Download and install each of these programs on your PC in the listed order.
You are also going to need some super important supporting files that make all of this magic possible.
The V35 engineering abl that will give you fastboot with thanks to @vlad48 for making it available: https://www.androidfilehost.com/?fid=1395089523397895796. Yes,it says V20, ignore it, it is fine. Extract abl_a and abl_b, and append a “.img” extension to each. Note the locations on your PC for future use.
The recently available emergency download (EDL) firehose that makes direct partition flashing possible released by Biao on Telegram. It is available here:
https://androidfilehost.com/?fid=4349826312261705871
or as an attachment in @Xsavi’s similar and earlier instructions for the V40: https://forum.xda-developers.com/lg-v40/development/unlock-lg-v40-via-9008-root-t-mobile-t4042207
Note its location for later use.
Troubleshooting:
These instructions assume that your phone boots normally. Even with that there can still be issues due to software drivers and pc-hardware. They can be broadly summarized as a difficulty getting the computer to recognize and communicate with the phone and vice-versa. They arise frequently. If you encounter difficulties, review these troubleshooting tips compiled and written by @ChazzMatt and taken from his V30 WTF instructions.
Look in your ADB folder on your PC and confirm all known Windows file extensions enabled, https://goo.gl/YxLRG5.
Confirm all Windows hidden files and folders are visible, https://goo.gl/1jBKne.
Confirm USB debugging is on in Developer Options, and your PC has authorization for your phone, https://goo.gl/DgojL9.
Install another version of ADB. Install as close to the root of your hard drive as possible. X:\ADB where X is your hard drive.
Re-install LG mobile drivers, https://is.gd/Jbrvx1.
Try another USB cable.
Installing this Windows driver found attached to this post, (Thanks @gazzacbr and @FZZF) https://goo.gl/CqqNZT.
Install Google USB driver, (Thanks @s0lidsneak) https://goo.gl/z2Tahw.
Try another USB port on your computer or try cheap USB 2.0 hub, https://is.gd/gM1mM0.
Reboot the computer.
Try another computer. (THIS usually solves the problem, https://goo.gl/x637H1. Kudos if you find an an old Win7 PC, https://goo.gl/EaGMhs.)
Master Reset (full reset of phone using hardware buttons), https://goo.gl/N4LcLD. Phone will be reset anyway after bootloader unlock. Doing it prior may fix something preventing the command from working.
Step 1: Setting an Oreo baseline:
The engineering files for bootloader unlock of the V35 phone are designed to work with Oreo. If you are an Pie or Q, it is highly recommended that you flash back to Oreo. For those of you with the common AT&T V350AWM model that is not on Oreo, there are a couple of points to consider
AT&T does not release flashable roms. If you are on AT&T Pie or eventually Q, there is no going back unless of course you take the time to make a backup of the rom itself. That is not covered in this guide nor am I aware of a guide on how to do this.
AT&T sim-locks its branded V35’s and the menu to unlock is specific to the AT&T rom. You should strongly consider purchasing of a sim-unlock code and applying it before flashing another rom!
To set the baseline:
If you are already on Oreo perform a master reset. To do this, start by turning the phone off. Then press and hold the power and volume - buttons at the same time until you see the LG logo appear. When the LG log appears, release the power button and then press and hold it again while continuing to press the volume – button. Follow the menus to perform the reset.
If you are on Pie or Q, you are going to flash or cross-flash back to Oreo. The kdz's are available for downloaded from https://lg-firmwares.com/lg-lmv350ulm-firmwares/#tab=firmwares. Reports are that roms can be cross-flashed across V35 models with the exception of the Korean V350N. If you are not familiar with the roms, the favored ones are the Google Fi / North American versions for the V350ULM. Down load the latest Oreo version
https://lg-firmwares.com/downloads-file/18971/V350ULM10i_00_NAO_US_OP_0221, md5sum: 64554877b692601d5906d2bdc9691712​To flash the rom, turn the phone off, press and hold the volume – button while connecting it to the computer’s USB. The phone screen should show “Download Mode”. Start-up LGUP on your PC, select the rom kdz, and flash it using “Refurbish”. Do not use any other modes or you will have serious trouble!
Step 2: Partition Extraction, Modification and Bootloader Unlock
Enable “OEM Unlock”: Turn on the phone and go through a minimal set-up process. Next go to Settings→ System→ About Phone→ Software info. Repeatedly tap on “Build Number” until you receive a message that you are now a “Developer”. Next go to Next go to Settings→ System→Developer options. Look for “OEM unlock” and flip the switch to on. Exit the “Settings” menus.
Boot the phone in EDL 9008 mode: The “button dance” to put the phone into EDL mode requires quick hands. To increase the likelihood of success, take the phone out of any case to expose the volume buttons. With the phone fully booted and turned on, connect it to your computer by USB. Press and hold the power and volume – keys at the same time. The phone will likely take a screenshoot, keep holding the buttons, afterwards it will bring up a reboot countdown message. With one second left, start pressing the volume + button while still keeping the power and volume – buttons pressed. The phone will show a black screen and windows with make its connection sound if you succeeded in reaching ECL mode. Release the button immediately. Look at your computer, you should also see an entry in the Windows Device Manager under “Ports” that reads:
“Qualcomm HS-USB QDLoader 9008 (COMXX)”
where XX is the port. The phone will just reboot if you didn’t click the volume + button sufficiently fast. Keep trying, you will eventually succeed. If the screen on the phone does go black and you don't see the phone listed in the Windows Device Manager, then you should check installation of 9008 port driver.
Start and configure QFIL: Go to the Start Menu or whatever passes for it on your Windows computer and fire up QFIL. Survey the screen:
You should see “Qualcomm HS-USB QDLoader 9008 XX” next to “Select Port…”.
There should be small text in the lower right corner that reads “Storage Type:”; Select “ufs”.
There is a subheading near the upper left that reads “Select Build Type”. Tick “Flat Build”.
Now using the “Browse…” button under the “Select Programmer", navigate to the folder that contains the firehose file, “prog_ufs_firehose_Sdm845_lgev40.elf” and select it.
Extract partitions: Click on “Tools” in the menu bar of QFIL. Select “Partition Manager”. You will be asked if you selected the correct firehose. If you did then click OK. A screen will now appear that lists partitions on your phone. Scroll down the list and look for “abl_a”, “laf_a”, “abl_b”, and “laf_b”.
Right click on “abl_a”
Select “Manage Partition Data”
Select “Read Data…”
Open a folder and navigate to location where the extracted file is located. The QFIL “Status” output shows the location and filename. On my PC, it reads:
“C:\Users\whoiam\AppData\Roaming\Qualcomm\QFIIL\COMPORT_XX\ReadData_ufs_xxxxx.bin” where XX is the port number and the “xxxxx” are details about the partition name. Copy the file to a dedicated folder and rename it “abl_a.img”.
Repeat the this process for “laf_a”, “boot_a”, “abl_b”, “laf_b”, and “boot_b” partitions. Note the locations of these files as back-ups and also for the following section on rooting.
Use QFIL to get fastboot:
Write the engineering abl’s: In QFIL, do the following:
Right click on abl_a.
Select “Manage Partition Data”
Select “Load Image”
In the dialog, Navigate to the location of the engineering abl_a.img file you downloaded in the preparation section, select it, and click “Open”.
Repeat this same procedure for abl_b.
Erase laf’s: In QFIL, do the following:
Right click on “laf_a”
Select “Manage Partition Data”
Select “Erase”
Confirm that you want to erase
Repeat for laf_b.
Unplug the phone from USB
Press and hold the power and volume - buttons until the LG V35 boot logo appears. Allow the phone to reboot.
Turn the phone off.
Unlock the bootloader:
Enter fastboot mode: Hold the volume + button and plug in the USB cable. The phone will boot to a series of menus that include “Start” and “Power off”.
Run a command prompt as Administrator. If necessary navigate to the directory where you installed adb.exe and fastboot.exe.
Check that the phone communicates with fastboot: Type “fastboot devices” and press enter. It should return details about your device. It reads “LMV350AWMxxxxxxx fastboot” with my phone.
Bootloader unlock: Type “fastboot oem unlock”. Congratulations if it reports OK, your phone is now unlocked. If it reports failed then try another USB port on your PC, a better/different cable, and potentially even another PC.
Reboot the phone
Step 3: Restore download mode and flash to desired rom:
If the current version of Oreo is where you want to be then skip to Step 4.
If you want to upgrade to Pie or eventually Q, then you need to restore the laf_a, laf_b, abl_a, and abl_b partitions to recover download mode. It should be clear from what you have done above with QFIL how to do this.
Download the kdz of your desired rom. The Google/NAO version of Pie is recommended and available at this link, https://lg-firmwares.com/downloads-file/22230/V350ULM20f_00_NAO_US_OP_0218.
To flash the rom, turn the phone off, press and hold the volume – button while connecting it to the computer’s USB. The phone screen should show “Download Mode”. Start-up LGUP on your PC, select the rom kdz, and flash it using “Refurbish”. Do not use any other modes or you will have serious trouble!
Step 4: Install Magisk for Root:
Re-enter EDL mode with the above button dance procedure
Extract boot_a and boot_b partitions: Click on “Tools” in the menu bar of QFIL. Select “Partition Manager”. You will be asked if you selected the correct firehose. If you did then click OK. A screen will now appear that lists partitions on your phone. Scroll down the list and look "boot_a” and “boot_b”.
Generate a Magisk-patched booted image working directly with the phone:
Download a stable version of Magisk Manager from the official website: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445. It should be saved in the “Download” folder.
In Settings, navigate to Apps & Notifications→ Special access → Install unknown apps. Click on File Manager and set it to allowed.
Open the “File Manager” app and navigate to the Download folder.
Select and install the “MagiskManager-v7.5.1.apk” file keeping in mind that the version numbers may be different.
Connect the phone to USB and place it in file transfer mode.
Copy boot_a.img and boot_b.img to the phone Download folder
Start “MagiskManager” and select “Install”. When presented with the option, tap “Select and Patch a File”.
Navigate to the “Downloads” folder where and select boot_a.img.
There will now be a file named “magisk_patched.img” in the “Downloads” folder. Change its name to magisk_patched_a.img.
Repeat this process with boot_b.img.
Install the Magisk-patched boot images using the PC:
Copy the magisk_patched_a.img and magisk_patched_b to the windows computer.
Put the phone into 9008 EDL mode with the button dance described above.
Start QFIL, configure it as described above, and then click on “Tools” in the menu bar of QFIL and Select “Partition Manager”.
Scroll through the list of partitions and locate boot_a. Right click on it and select “Load Image”. Point it to the magisk_patched_a.img file.
Repeat the previous step for boot_b and load the magisk_patched_b.img file
Reboot your rooted phone.
Step 5: Remove Root Checker: (Added 20200409)
I say with sarcasm that another way that LG has made our lives better was to implement a root-check and monitoring system. Many here are familiar with the root check daemon from the V30. There is a root-check disable twrp package to fix this problem. Installation and use of TWRP for the V35 is tricky. Don't worry, there is another way.
Put the phone in USB debug mode
Connect to your computer
With adb from a command prompt on the computer do the following
adb devices <-- If your devices is properly connect and recognized, adb will respond
List of devices attached
LMV350XXXXXXXXX device
adb shell <-- If you have a shell into the phone you will now see
judyp:/ $
pm uninstall -k --user 0 com.lge.srtc <-- This command removes the root checker, if it succeeds you will get the response:
Success
pm uninstall -k --user 0 com.lge.mlt <-- This command removes the LG monitor, if it succeeds you will get the response:
Success
Happy Rooting!

Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?

THANK YOU for this. Seriously. Really well done. I can't wait to try it if I ever get my phone back into shape where I CAN try it. ?

There are several posts by owners of AT&T branded V35's who cross-flashed to the Korean V350N Pie rom successfully. They were in a rush for Pie and it was released for Korean models first. Still, I have in my notes not to do the reverse, but I can't find the link. Hypothetically, one can recover from about anything using 9008 mode and QFIL provided you have back ups of the partition images of your phone.
fpozar said:
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
Click to expand...
Click to collapse

cmrntnnr said:
There are several posts by owners of AT&T branded V35's who cross-flashed to the Korean V350N Pie rom successfully. They were in a rush for Pie and it was released for Korean models first. Still, I have in my notes not to do the reverse, but I can't find the link. Hypothetically, one can recover from about anything using 9008 mode and QFIL provided you have back ups of the partition images of your phone.
Click to expand...
Click to collapse
I was one of those who leaped to the Korean KDZ. Now I am running NAO firmware. Guide looks well written. I might wind up taking the leap. Good job bro!

Thanks, I follow your steps very carfully, and now I have a rooted v35.

Nicely done. Thank yoh for sharing the result.
fpozar said:
Wow,
Thanks for the great guide, can't wait to try this.
One question, though, regarding your cross flashing warning. Where did you get the information that Korean V35 can not cross flash? I own a Korean model and it's kinda annoying to constantly be in roaming mode, I was hoping that ULM will change that. So basically, the best I can do is root, not other rom is okay for LM-V350N?
Click to expand...
Click to collapse
vavoo said:
Thanks, I follow your steps very carfully, and now I have a rooted v35.
Click to expand...
Click to collapse

So due to prior.... mishaps, my phone will not boot ("all slots are unbootable!"), and fastboot produces "Flashing Unlock is not allowed" every time the OEM unlock is attempted. What should I do?

I am stuck at Fastboot Mode. It says the "Device state - Unlocked", but when if I choose Start or Power off/on my phone it just goes back into fastboot everytime.
1. I installed and flashed the Pie rom you linked in step 1
2. I turned "Oem unlock" to On.
3. placed the phone in 9008 mode, backed up abl_a, laf_a, boot_a, abl_b, laf_b, and boot_b.
Loaded the img to abl_a and abl_b.
Finally, Erased laf_a and laf_b
4. within fastboot, unlocked bootloader
Any ideas ?

If the phone unlocked, go back into 9008 EDL mode and restore the laf and abl images using your backups. That should get you booting.

dave1567 said:
Any ideas ?
Click to expand...
Click to collapse
1. Download the attached EDL.zip
2. Extract it to a local folder on your PC
3. While your V35 is in fastboot mode plug it to your PC via USB (USB2 port preferred)
4. Double click on RebootEDL.bat
5. Phone will enter 9008 (EDL) mode screen will be black.
6.Using QFIL flash back your PIE abl_a and abl_b
7. Using QFIL flash attached FTM partition from FTMV35PIE.zip.
8. Hold Vol-and power to reboot.

vlad48 said:
1. Download the attached EDL.zip
2. Extract it to a local folder on your PC
3. While your V35 is in fastboot mode plug it to your PC via USB (USB2 port preferred)
4. Double click on RebootEDL.bat
5. Phone will enter 9008 (EDL) mode screen will be black.
6.Using QFIL flash back your PIE abl_a and abl_b
7. Using QFIL flash attached FTM partition from FTMV35PIE.zip.
8. Hold Vol-and power to reboot.
Click to expand...
Click to collapse
I didn't use your bat since it looks like I can still boot into 9008 mode with the button dance method.
Unfortunately, still nothing!
I flashed my abl_a.img and abl_b.img backups I made to the abl_a/b partitions and flashed your FTM_BL.img to my FTM partition, but it didn't seem to do anything except cause some graphical glitches within fastboot menu (everything still functioned though)
Just in case, I re-locked my phone (fastboot oem lock) and started the QFIL process over (flashing with engineered abl_a and abl_b imgs)
Then within fastboot mode, I ran "fastboot oem unlock" a few times because it fails, but finally it went through
Now the phone is unlocked again, but still just always just boots into fastboot mode!

Of course it will boot only to fastboot as you are using engineering abl from Oreo - please understand there is a signature check match which fails and you will not be able to continue booting.
So, in brief, you need to have all partitions on respective bootable slot form either Oreo or Pie kdz version. So you need to be sure that you flashed your PIE abl wither via QFIL or via LGUP.

vlad48 said:
Of course it will boot only to fastboot as you are using engineering abl from Oreo - please understand there is a signature check match which fails and you will not be able to continue booting.
So, in brief, you need to have all partitions on respective bootable slot form either Oreo or Pie kdz version. So you need to be sure that you flashed your PIE abl wither via QFIL or via LGUP.
Click to expand...
Click to collapse
Unfortunately, I don't understand. Thanks for trying to help though.
Anyways, I managed to fix the problem and I'm all set.
- Restored my laf_a and laf_b partitions
- Booted into download mode and re-installed the pie image with LG Up.
- Was now able to boot normally
- Followed the instructions in the guide to get magisk installed and now I'm all set!
Thanks all and hope this helps someone

I scouted my way through these very same steps a couple weeks ago. Soft bricked my device a couple times ? but eventually got her there. Glad too see a dedicated guide is out now. Only problem I've run into is the ctsprofile:fail problem. Been able to fix with spoof pixel fingerprints but it's not ideal. Still looking for solutions if anyone knows anything.

Iantuition said:
So due to prior.... mishaps, my phone will not boot ("all slots are unbootable!"), and fastboot produces "Flashing Unlock is not allowed" every time the OEM unlock is attempted. What should I do?
Click to expand...
Click to collapse
What is the minimum needed for you to enter download mode? I have backups of most partitions i will be happy to share and you can use Qfil to flash those to get to download mode then use LGUP to flash a normal kdz? If so, let me know.

so somehow between qfil and getting fastboot i've got myself in trouble. i dont understand what i did wrong but i got stuck in a fastboot loop and tried following some of the fixes mentioned previously in this thread. when i get back to qfil and try to go to partition manager it wont let me see any of the partitions and shows various sahara errors and fails in the log box. can someone please help idk what to do

Sorry to hear that. The first time I tried to use QFIL I got a Sahara error and could not see partitions. It was resolved by reinstalling the 9008 port driver and then QPST in that order. It happened again later when windows tries to be helpful by automatically reinstalling drivers when the phone is plugged in but with a mode change.
Flowtron3000 said:
so somehow between qfil and getting fastboot i've got myself in trouble. i dont understand what i did wrong but i got stuck in a fastboot loop and tried following some of the fixes mentioned previously in this thread. when i get back to qfil and try to go to partition manager it wont let me see any of the partitions and shows various sahara errors and fails in the log box. can someone please help idk what to do
Click to expand...
Click to collapse

Will this help me sim/carrier unlock my v35awm?

Can you lock the bootloader after this is done and keep root? Need it for banking apps.

Question Stuck in Fastboot, HELP needed

Okay, I messed up.
Device OP9Pro EU version.
Used Updater and updated to O12 and device went to Fastboot mode.
Tried:
to flash/boot twrp - no luck
found fastboot restore rom in 4PDA, flashed, restarted back to fastboot
manually fastboot flash - extracted Oxygen rom with payload dumper - back to fastboot.
Trying to find a way from fastboot to EDL to use msmtool.
HAS ANYONE IDEAS?

ptr21 said:
Okay, I messed up.
Device OP9Pro EU version.
Used Updater and updated to O12 and device went to Fastboot mode.
Tried:
to flash/boot twrp - no luck
found fastboot restore rom in 4PDA, flashed, restarted back to fastboot
manually fastboot flash - extracted Oxygen rom with payload dumper - back to fastboot.
Trying to find a way from fastboot to EDL to use msmtool.
HAS ANYONE IDEAS?
Click to expand...
Click to collapse
Use the MSM unbrick tool and bring it back to android 11!

herrieberry said:
Use the MSM unbrick tool and bring it back to android 11!
Click to expand...
Click to collapse
I cant enter edl mode. Key combinations are useless. Any time I connect phone to PC, it goes to fastboot mode.

It brings you back to android 11.2.2.2 (Razorcortex)

power of the phone
plug in the phone to pc
start msm tool
press vol up, vol down and power button together for a few seconds
tools starts updating the phone

herrieberry said:
It brings you back to android 11.2.2.2 (Razorcortex)
Click to expand...
Click to collapse
How to do - I'm stuck in fastboot, cant enter edl.

herrieberry said:
power of the phone
plug in the phone to pc
start msm tool
press vol up, vol down and power button together for a few seconds
tools starts updating the phone
Click to expand...
Click to collapse
The phone is off.
Any time I connect it ti PC fastboot boots up, no way to enter EDL.

Try to connect it first and then power of?

herrieberry said:
Try to connect it first and then power of?
Click to expand...
Click to collapse
No luck.
I can power off from fastboot menu, 3 seconds and it restarts in fastboot again.

fastboot erase userdata or
fastboot format userdata

MrSteelX said:
fastboot erase userdata or
fastboot format userdata
Click to expand...
Click to collapse
Did.
Back to fastboot again.

OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
that should help to msm phone to working order

MrSteelX said:
OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)
By using these tools, you accept full responsibility for your actions. Your warranty is void should you run any of these utilities without OnePlus support present. I am not responsible for bricks, fires, nuclear war, etc. If you modified any...
forum.xda-developers.com
that should help to msm phone to working order
Click to expand...
Click to collapse
Thanks, but the phone is still stuck in fastboot mode.
I cant enter EDL.
I power off the phone and when I connect phone to PC, it still boots to FASTBOOT, whatever keycombination I use. Every time.

Get msm up and ready.. Click box to use "lite firehose." then power off ur phone from fastboot.. While holding vol buttons plug in and quickly click enum and soon as it says connected click start. I've had samw problem with msm constantly turning phone on. Eventually u will get it. Click box for firehose lite and u shld be good

Shooter7889 said:
Get msm up and ready.. Click box to use "lite firehose." then power off ur phone from fastboot.. While holding vol buttons plug in and quickly click enum and soon as it says connected click start. I've had samw problem with msm constantly turning phone on. Eventually u will get it. Click box for firehose lite and u shld be good
Click to expand...
Click to collapse
I got it... almost.
I established connection, started to flash and DEVICE NOT MATCH IMAGE error appeared.
I am sure I have EU device 2123, selected eu from droplist in MSMtools.
Now What?

Did u click box for "use firehose lite".? If so u either can try unchecking sha256 check or try to find msm for EU

lemonadep_22_E.05_210324.zip | by craznazn for OnePlus 9 Pro
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com

ptr21 said:
I got it... almost.
I established connection, started to flash and DEVICE NOT MATCH IMAGE error appeared.
I am sure I have EU device 2123, selected eu from droplist in MSMtools.
Now What?
Click to expand...
Click to collapse
With this options it' s working for me

Option Target select EU

Something I figured out on my 9Pro is that it would only stay in EDL mode for about 10 seconds if nothing was done. It would then boot into recovery or fastboot. Here's how I got mine to work, with the phone powered off I got the MSM tool all set up to go. If your phone is starting up as soon as you plug the cable in make sure you're holding vol up and down while plugging in, otherwise pwr+vol up+vol down. As SOON as the device connects hit the start button on msm tool (if you wait msm tool would not start because the phone was no longer in edl mode). The flash then went through and I was back to Android 11. Hope that helps.
It took a few tries but I got it to work.