Develop Bugs

i bricked my ZE551ML bad need help PLZ

i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:

FluidArc said:
i tryed to root my phone everything was going alright, but wen i went to boot it up i got stuck on
ASUS IN SEARCH OF INCREDIBLE and a loading logo, i can not get in to my bootloader
my pc detects it but fast boot and adb do not detect it
what do i do :crying::crying::crying::crying:
Click to expand...
Click to collapse
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.

now what do i do
i do not know what ferwere i am on and my recovery is broken how to i get it up and runing
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse

Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app

i can not enter recovery
dawnsleeper said:
Once happened to my zf2, what i did is formatting cache from the adb then my device could be detected, thus i could enter the recovery mode
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse

it is fix all good guys thx
FluidArc said:
i can not enter recovery
Click to expand...
Click to collapse

Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
dh_711 said:
Probably you soft bricked your phone. I got into a similar situation when I applied OTA after root. Dont worry, its very easy to recover your phone. It should be able to boot in Fasboot mode. If it does, follow follow this guide:
.theandroidsoul.com/how-to-unbrick-asus-zenfone-2-works-on-ota-fail-too-82039/ (Add www at the start)
Download the latest pre-rooted system .img from here:
mega.co.nz/#F!k4MHiAgL!dVuOKeH3eokcwPSNI79ffw
Download the stuff needed and then just follow the guide. Hopefully you recover your device. Best of luck!
EDIT: Forgot to add but did you install the adb drivers? Probably thats the reason Fastboot and adb dont detect it. Or did you go into the fastboot mode in the phone? If not, do that first. To do it, follow these steps:
1. Power your device down.
2. Press and hold the power and volume up button.
3. Release the power button when it vibrates.
4. Release the volume up button once the ASUS splashscreen appears.
5. Now the device should be in Fasboot mode.
6. Then connect your phone to your PC (dont forget to install the drivers!) using the USB Cable and go to the folder where the flashtools are.
7. Hold Shift and right click > then click open command window here
8. Type "fastboot devices". Enter the command two times. (Cause the first time it will start daemon or something like that)
If your device shows up, congrats! You are in fastboot mode and it is working.
Click to expand...
Click to collapse

Captain_Hindsight said:
Hey,
Could you please help me (or anyone for that matter).....I've soft bricked my phone and I'm a little weary about following any other steps incase I fully brick the phone.
I have a Zenfone 2 that was CN Z00A 2.20.40.63 , I tried to root because random chinese apps kept downloading on my phone and obv it soft bricked (kept looping at boot).....since then I have tried a lot of stuff without luck and my brain is fried from all the information.... I went to the recovery mode but ADP couldn't find my phone and then I loaded a recovery image on my SD calling it MOFD_SD.ZIP but that didn't work due to signature verification error. Now after reading what you wrote I can see that fastboot is recognizing my device....I would go through with the process but I'm afraid if I screw this one up it could be the end of fastboot working and therefore me being royally screwed.
Since my phone was naturally CN Z00A 2.20.40.63 I'm wondering if the pre-rooted images on the site you mentioned above will work? There is no download for CN Z00A 2.20.40.63 and I want to know whether it's safe to use CN Z00A 2.20.40.61 (or a WW image) or whether I have to try another option (if you have any suggestions).
If anyone could reply with help it would be greatly greatly appreciated.
Click to expand...
Click to collapse
Well, I'm not sure if it'll work but check this out (Scroll down to No. 4 - Changing from CN to WW version):
forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
I'm no expert, but to be honest the state your device is in, I don't see any other options. Because when my device (it had WW firmware) got soft-bricked, I followed the guide by androidsoul and it did recover my phone. Not sure about yours since its a CN one.
If you like living on the edge and are really desperate, go ahead try this out, if not, better wait for someone with more knowledge then me.
EDIT: I forgot but since ADB isn't working, you can't use this method. So the only option I see that you have is flashing a pre-rooted rom.

Miui 9.2.3 makes root impossible

May 2019. Updated from Miui 9.2.2 in which I happily had TWRP etc all working fine, to 9.2.3. After update I went to do a backup, but no TWRP working and was now unrooted, with only MiRecovery. I have spent many hours trying everything I know [not a lot actually] to root my Xiaomi Redmi 1s, update, sideload, XiaomiFlash etc, but all standard avenues have been turned off. MiRecovery keeps failing on Update.zip, Updater app has moved and will not now update anything except 9.2.3. It appears to have been a deliberate closing of all possibilities as this is the last Miui that will work on the Redmi 1s [from Miui on a Miui blog]. Adb, fastboot even fails. I hope I am wrong and someone here can tell me how to go back to rooted 9.2.2 as I was using. I even backed up in TWRP just before updating, but this is currently useless. I have searched and tried everything relating to Miui prior to 9.2.3, and everyone keeps saying their way will work on ALL Miui 9's, but clearly no-one has actually tried on 9.2.3. Buying a new phone would work, but I don't want to give up. The last gasp would be to reset to original and try to root and go from there [would this work?], but seeing they have closed ALL rooting avenues, that may also be unworkable.
Your help would be brilliant!
Terry

TRY THIS.
bkterrry said:
May 2019. Updated from Miui 9.2.2 in which I happily had TWRP etc all working fine, to 9.2.3. After update I went to do a backup, but no TWRP working and was now unrooted, with only MiRecovery. I have spent many hours trying everything I know [not a lot actually] to root my Xiaomi Redmi 1s, update, sideload, XiaomiFlash etc, but all standard avenues have been turned off. MiRecovery keeps failing on Update.zip, Updater app has moved and will not now update anything except 9.2.3. It appears to have been a deliberate closing of all possibilities as this is the last Miui that will work on the Redmi 1s [from Miui on a Miui blog]. Adb, fastboot even fails. I hope I am wrong and someone here can tell me how to go back to rooted 9.2.2 as I was using. I even backed up in TWRP just before updating, but this is currently useless. I have searched and tried everything relating to Miui prior to 9.2.3, and everyone keeps saying their way will work on ALL Miui 9's, but clearly no-one has actually tried on 9.2.3. Buying a new phone would work, but I don't want to give up. The last gasp would be to reset to original and try to root and go from there [would this work?], but seeing they have closed ALL rooting avenues, that may also be unworkable.
Your help would be brilliant!
Terry
Click to expand...
Click to collapse
Make the phone to factory setting.
Then ADB process ( Install "Minimal ADB and Fastboot) which will get installed in your Program Files (x86) folder.
Then COMMAND PROMPT inside the folder (after placing the TWRP image in that folder)
Type the following commands :
fastboot devices
fastboot flash recovery twrp.img (or whatever image filename is)
fastboot reboot
I guess, you aren't getting your Flash Recovery and is booting normal to homescreen.
You might be even trying to hold "Volume Up" button + "Power" button, and might be getting Mi Recovery,
Here is the IMPORTANT THING.
Right after you execute the last command "fastboot reboot"
quickly keep holding the "Volume UP" button only.
And VOILA, you will get the TWRP Flash Recovery Screen.
Click on THANKS button, if it worked for you.
Let me know if you are having any other problems with Redmi 1S.

Thank you so much. I will try this.
Valter Dan said:
Make the phone to factory setting.
Then ADB process ( Install "Minimal ADB and Fastboot) which will get installed in your Program Files (x86) folder.
Then COMMAND PROMPT inside the folder (after placing the TWRP image in that folder)
Type the following commands :
fastboot devices
fastboot flash recovery twrp.img (or whatever image filename is)
fastboot reboot
I guess, you aren't getting your Flash Recovery and is booting normal to homescreen.
You might be even trying to hold "Volume Up" button + "Power" button, and might be getting Mi Recovery,
Here is the IMPORTANT THING.
Right after you execute the last command "fastboot reboot"
quickly keep holding the "Volume UP" button only.
And VOILA, you will get the TWRP Flash Recovery Screen.
Click on THANKS button, if it worked for you.
Let me know if you are having any other problems with Redmi 1S.
Click to expand...
Click to collapse
Thank you so much. I will try this.

bkterrry said:
Thank you so much. I will try this.
Click to expand...
Click to collapse
Did it helped you???

Thank you
I admit to being too scared to do a factory reset and losing all my work/apps I had setup. I have given up and now go with the Google flow, but still say thank you for your kind reply.
Regards,
Terry

Need little bit help with bricked Note 8 Pro

Hi everyone,
I got Chinese version Note 8 Pro from Mi official store and unlocked bootloader after 7 days.
I downloaded Global MIUI 11 ROM via official miui download link, "ifelixit+FLASHER+TOOLKIT+Begonia" and installed ADB drivers etc.
After run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1, it installed recovery, then I'm able to boot into TWRP, and then I installed global rom from there, meanwhile wiped everything in it as I don't need China version rom. Phone reboot well and new global rom works great.
Then I try to install Magisk, I noticed recovery seems be restored to original, no worries, I re-run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1 to install TWRP again. Whatever I did, I cannot get TWRP back, when I hold power/+, it keep blank and will restart, but if I don't hold them, it can get into the system.
My first question is: 1. At this stage, is recovery crash already?
I didn't think too much and I get into system, install Magisk manager, let it to patch boot.img, I then use following command in fastboot mode
fastboot flash boot boot_patch.img
After I finished, I noticed maybe I can do TWRP here as well, then I also input
fastboot flash boot TWRP.img
After reboot, the phone is dead....No fastboot, NO recovery, no vibration. exactly described as here
[UNBRICK - stuck on DA mode / Authorised Service Account required]
https://forum.xda-developers.com/re...ide-unbrick-stuck-da-mode-authorised-t4000433
I re-think what I did, my question is
2. Will boot_patch.img Magisk patched not suitable for China phone with global rom?
3. Is fastboot dead because I installed recovery into boot via fastboot flash boot TWRP.img?
Thanks for your time and appreciated for any knowledgeable reply.

Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
---------- Post added at 09:00 AM ---------- Previous post was at 08:52 AM ----------
fastjohnson said:
Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
Click to expand...
Click to collapse
Remove the back off the phone and disconnect the battery for 5 min just to be sure hold the power button to clear all power left in the phone. Main objective is to get useage again fastboot or recovery. If you get recovery sideload your boot img and flash it on the next reboot twrp will be overridden.

fastjohnson said:
Flash your original boot.img for your original firmware or just download the xiaomitoolV2 and flash it that way. I see a lot of people flashing stock firmware using TWRP. Hence the v2 tool only works if your phone still fully boots. NOTE do not flash stock FW or UPDATE using TWRP you will brick the device. Chances are your FW didn't flash and just ADB CMD fatsboot flash boot ( then set BOOT.IMG ) in the CMD and get the devices booting again. Then use the V2 tool to flash the global firmware get that to stick then use the ifelixit tool to flash recovery once in recovery go advanced file mgr system-root at the bottom delete boot P then close AVB 2.0 then hit the install root button SU - magisk 19.4 will be installed. no need to wipe or format the phone ( DON'T FORGET TO WIPE CACHE & DALVIC.
---------- Post added at 09:00 AM ---------- Previous post was at 08:52 AM ----------
Remove the back off the phone and disconnect the battery for 5 min just to be sure hold the power button to clear all power left in the phone. Main objective is to get useage again fastboot or recovery. If you get recovery sideload your boot img and flash it on the next reboot twrp will be overridden.
Click to expand...
Click to collapse
Thanks. Currently my phone doesn't have reboot, no recovery, purely blank on screen, only power led shows when connecting via USB. In this situation, must open back case to disconnect the battery? I heard about it's free to go back to mi store and re flash it back. To open back case it won't have warranty anymore. Struggling....

idog8818 said:
Thanks. Currently my phone doesn't have reboot, no recovery, purely blank on screen, only power led shows when connecting via USB. In this situation, must open back case to disconnect the battery? I heard about it's free to go back to mi store and re flash it back. To open back case it won't have warranty anymore. Struggling....
Click to expand...
Click to collapse
I also have two bricked phones note 8 pro with no recovery, only white led shows when connecting via USB.
First bricked with TWRP and then flashed with false boot.img, second is bricked with OrangeFox-Unofficial-begonia.img.
I was open back case and disconnect the battery, stay 3 days but nothing working to reboot to fastboot or recovery.
Also I have already tried with short circuit test point to EDL mode but phone is still dead. I have downloaded many xiaomi and other tools and firmwares, installed all available usb drivers and reading all internet forums.
Please help!

Same
Hello,
I think I did the same error, flashing a wrong boot.img...
I tell you if I manage to do something.

hello, the solution to the problem is the battery is completely discharged until the device stops responding to any attempts to start using the key combination. unless you tried to flash a fastboot partition. the solution works after hard bricking after trying to upload incompatible twrp or other rom (I uploaded Chinese twrp on eu rom). ok, we start:
1. holding vol - and power plug in the usb cable (the buttons are released when the notification LED changes from very bright for a moment to slightly dimmed)
2. you will see the long unseen battery symbol with a lightning inside (i.e. a completely discharged battery, the charge status will begin to show the percentage)
3. Turn off the USB cable at 3 percent.
4. now an important thing - you need to start the phone only trying to enter the fastboot mode otherwise the phone will start to boot the system and get stuck again and you will have to unload it again
5. you will finally enter the fastboot , using only the software from xiaomi or xiaomi flash and fastboot rom
I succeeded after 2 weeks of waiting for it to discharge ...
I copied this tutorial from this partner klocek80 , and it worked perfectly
https://forum.xda-developers.com/showpost.php?p=81191977&postcount=72

danyv77 said:
hello, the solution to the problem is the battery is completely discharged until the device stops responding to any attempts to start using the key combination. unless you tried to flash a fastboot partition. the solution works after hard bricking after trying to upload incompatible twrp or other rom (I uploaded Chinese twrp on eu rom). ok, we start:
1. holding vol - and power plug in the usb cable (the buttons are released when the notification LED changes from very bright for a moment to slightly dimmed)
2. you will see the long unseen battery symbol with a lightning inside (i.e. a completely discharged battery, the charge status will begin to show the percentage)
3. Turn off the USB cable at 3 percent.
4. now an important thing - you need to start the phone only trying to enter the fastboot mode otherwise the phone will start to boot the system and get stuck again and you will have to unload it again
5. you will finally enter the fastboot , using only the software from xiaomi or xiaomi flash and fastboot rom
I succeeded after 2 weeks of waiting for it to discharge ...
I copied this tutorial from this partner klocek80 , and it worked perfectly
https://forum.xda-developers.com/showpost.php?p=81191977&postcount=72
Click to expand...
Click to collapse
This only helps when boot image is not damaged.

Duchan_xda said:
I also have two bricked phones note 8 pro with no recovery, only white led shows when connecting via USB.
First bricked with TWRP and then flashed with false boot.img, second is bricked with OrangeFox-Unofficial-begonia.img.
I was open back case and disconnect the battery, stay 3 days but nothing working to reboot to fastboot or recovery.
Also I have already tried with short circuit test point to EDL mode but phone is still dead. I have downloaded many xiaomi and other tools and firmwares, installed all available usb drivers and reading all internet forums.
Please help!
Click to expand...
Click to collapse
I'm with you. The boot image has error and when MTK realize it has something wrong it will NOT enter into fastboot. The only way to fix this is too use SP Flash Tool for deep flash. Mi store uses this way as well to fix the issue.

Try this:
https://c.mi.com/thread-2173190-1-0.html

ppthom said:
Try this:
https://c.mi.com/thread-2173190-1-0.html
Click to expand...
Click to collapse
This does NOT work. Please don't waste time on it.

:good:Thanks for clarifying this. Back to square one ...

idog8818 said:
Hi everyone,
I got Chinese version Note 8 Pro from Mi official store and unlocked bootloader after 7 days.
I downloaded Global MIUI 11 ROM via official miui download link, "ifelixit+FLASHER+TOOLKIT+Begonia" and installed ADB drivers etc.
After run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1, it installed recovery, then I'm able to boot into TWRP, and then I installed global rom from there, meanwhile wiped everything in it as I don't need China version rom. Phone reboot well and new global rom works great.
Then I try to install Magisk, I noticed recovery seems be restored to original, no worries, I re-run ifelixit+FLASHER+TOOLKIT+Begonia.bat and pick 1 to install TWRP again. Whatever I did, I cannot get TWRP back, when I hold power/+, it keep blank and will restart, but if I don't hold them, it can get into the system.
My first question is: 1. At this stage, is recovery crash already?
I didn't think too much and I get into system, install Magisk manager, let it to patch boot.img, I then use following command in fastboot mode
fastboot flash boot boot_patch.img
After I finished, I noticed maybe I can do TWRP here as well, then I also input
fastboot flash boot TWRP.img
After reboot, the phone is dead....No fastboot, NO recovery, no vibration. exactly described as here
[UNBRICK - stuck on DA mode / Authorised Service Account required]
https://forum.xda-developers.com/re...ide-unbrick-stuck-da-mode-authorised-t4000433
I re-think what I did, my question is
2. Will boot_patch.img Magisk patched not suitable for China phone with global rom?
3. Is fastboot dead because I installed recovery into boot via fastboot flash boot TWRP.img?
Thanks for your time and appreciated for any knowledgeable reply.
Click to expand...
Click to collapse
Are you recover your phone? I'm still waiting one year...

Duchan_xda said:
Are you recover your phone? I'm still waiting one year...
Click to expand...
Click to collapse
I didn`t find any background on your issue, just something like you actually have a device with white led light blinking.
I read this thread before (yes, some weeks ago) this happened to me yesterday https://forum.xda-developers.com/redmi-note-8-pro/how-to/guide-unlock-note-8-pro-authorised-t4168805 the short story is that I were trying to return to Miui 12 after of using some custom ROMs and something in the flashing process failed I mean it was an incomplete flashing and I assumed that most probably just the bootloader partition was damaged. The whole important fact in this situation is that you have yet available fastboot mode but like the splash partition with its image was gone I couldn `t see it and I were anyway in fastboot mode so I could flash the proper files to "unbrik" it. (my device is unlocked)
What you should try is connect it with PC while you`re pressing the volume down, enter to adb/fastboot environment and type fastboot commands to see if device is recogniced, you don`t have to hear constant reboot sounds or in this case press the power button simulating that you are powering off device.

never ending boot after stock ROM install

My Mi A2 Lite had stock rom v10.0.18.0, unlocked bootloader, Magisk v20.3 and TWRP using Offain v3.3.1.
I wanted to try dotOS custom ROM and followed this tutorial:
https://github.com/tkchn/daisyinstall
I begin with step 1 installing daisy global image v10.0.18.0 with flash_all.sh.
First time the script froze in the beginning.
I restarted it and it finished without errors but the following boot never ends.
I tried the same procedure with v10.0.3.0.
No errors and a never ending boot.
I tried to reinstall twrp from Offain using fastboot.
It looks OK but I can not press any button because the first twrp screen is frozen.
Now I can only enter fastboot.
adb does not recognize the device but fastboot seems to be working.
I am woried about my batery. I cannot see if it is charging because the boot is never ending. When I left fastboot without connecting USB cable I can turn off the phone but if I connect the charger the phone begins to work as if booting again and again.
What can I do to install the stock ROM without issues?

renatogui said:
My Mi A2 Lite had stock rom v10.0.18.0, unlocked bootloader, Magisk v20.3 and TWRP using Offain v3.3.1.
I wanted to try dotOS custom ROM and followed this tutorial:
https://github.com/tkchn/daisyinstall
I begin with step 1 installing daisy global image v10.0.18.0 with flash_all.sh.
First time the script froze in the beginning.
I restarted it and it finished without errors but the following boot never ends.
I tried the same procedure with v10.0.3.0.
No errors and a never ending boot.
I tried to reinstall twrp from Offain using fastboot.
It looks OK but I can not press any button because the first twrp screen is frozen.
Now I can only enter fastboot.
adb does not recognize the device but fastboot seems to be working.
I had frozen twrp screen before but usually managed to fix just by restarting the phone and using twrp offain in adb.
I am woried about my batery. I cannot see if it is charging because the boot is never ending. When I left fastboot without connecting USB cable I can turn off the phone but if I connect the charger the phone begins to work as if booting again and again.
What can I do to install the stock ROM without issues?
Click to expand...
Click to collapse
1- Download this: https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2- Create a new folder on your C drive and name it: adb
3- Extract & place everything from the platform-tools into your adb folder
4- Download this: https://drive.google.com/open?id=1SKIlWS-y6kNI4YIE2Sj4_9CcRJ9W0xTh
5- Extract & place it to your adb folder
6- Reboot your phone to TWRP and wipe it, then reboot to bootloader
7- Connect your phone to your PC
8- Go into the daisy_global_images_V10.0.9.0.PDLMIXM_9.0 folder and run: flash_all.bat
A window will pop up and install the stock mi a2 lite rom. Let it finish then your phone boot up. You will have to update your phone since this stock rom that I linked is a pretty old one.
Someone had a similar question in another forum, so I just copy my answer from there. If you have adb already installed you can ignore the first 3 steps.
I had frozen twrp screen a couple of times but managed to fix it by restarting the phone and re-open the powershell window in adb. I use twrp-daisy-3.2.3-0-offain.img

I'm afraid I cannot do step 6 as my TWRP is not working any more.
The remaining procedure I already did with 2 different daisy images V10.0.18.0 and 10.0.3.0.
In both cases the stock ROM was installed but the phone didn't finish to boot.
Why do you think it would be different if I use V10.0.9.0?
You said you fix frozen TWRP restarting the phone and re-openning the powershell in adb. My phone did not restart and adb does not work.

I was thinking I did not try to install stock image using MiFlash tool. I can do it if I get a windows computer available.
I saw people suggesting fastboot oem edl but I could not find a clear explanation of the procedure.
I understood that I must use MiFlash in that case too but the steps are not clearly defined and I need a windows computer anyway.
Does someone have a step by step to use fastboot oem edl?

renatogui said:
I'm afraid I cannot do step 6 as my TWRP is not working any more.
The remaining procedure I already did with 2 different daisy images V10.0.18.0 and 10.0.3.0.
In both cases the stock ROM was installed but the phone didn't finish to boot.
Why do you think it would be different if I use V10.0.9.0?
You said you fix frozen TWRP restarting the phone and re-openning the powershell in adb. My phone did not restart and adb does not work.
Click to expand...
Click to collapse
No particular reason behind 10.0.9.0 ... I just had that uploaded to my drive and when I posted this to another forum I didn't wanted to "waste" time to search for a link so I just used mine. Anyways u have to wipe your phone before installing stock rom.
The way I fixed mine is not working for you so Im afraid Im out of ideas.
Hope someone can help you out with it

thanks, anyway for your kind and quick answer.

I'd suggest giving MiFlash a try. Because a few times I tried flashing with the script file bundled with the stock ROM, I also had some bootloops, but MiFlash fixed the issue. When it comes to EDL flashing:
1 - Grab the 20160401 version of MiFlash from here : https://www.xiaomiflash.com/download/ (You need this version because it's the only MiFlash version that's capable of EDL flashing, mind you, you need a Windows PC and 64-bit hardware for this)
2 - Connect the phone in fastboot mode and type this command :
Code:
fastboot oem edl
Hit enter, this will take the phone into EDL mode, which means the screen will go black and the notification LED will start blinking.
3 - Now you're in EDL mode, open the MiFlash version I mentioned and Browse to find the location the stock ROM is stored, then hit refresh so that the software can recognize the phone.
4 - Hit flash to start flashing, but remember EDL flashing is a very fragile process, so make sure you don't lose power/shutdown the app while it's doing its job. After a successful flash, the app will say it is successful. Unplug the phone and start holding the power button to reboot. If you want to lock the bootloader, make sure to hold vol down as well and go into fastboot then re-lock the bootloader with :
Code:
fastboot oem lock
5 - Voila!

Thank you marstonpear for the detailed answer.
I will try MiFlash this evening and will post the result here.
I am very glad to count with more experienced people in fixing my errors.

Hello marstonpear,
I downloaded daisy image v10.0.13.0 that was suggested in XiomiFlash how to and try to flash it.
I got the error "mismatch image and device". This is very strange. Never had this before flashing with fastboot.
Do you think I could scrambled mi A2 lite so MiFlash cannot recognize it as a mi A2 lite anymore?
The only different think I did was interrupting my first flasing try using ^C when it was frozen.
I made 2 other tries after this with no errors. The only problem was the never ending boot.
My next try will be using image v10.0.18.0, the one I had installed before all this problems begin.

renatogui said:
Hello marstonpear,
Click to expand...
Click to collapse
marstonpear said:
I'd suggest giving MiFlash a try.
Click to expand...
Click to collapse
Quote marstonpear, like the quote above so that he get notification about your comment.
BTW, I never see this error before, you can try to google it.

coolwei1 said:
Quote marstonpear, like the quote above so that he get notification about your comment.
BTW, I never see this error before, you can try to google it.
Click to expand...
Click to collapse
I'm sorry. I tried hard how to quote and did'nt find.:cyclops:
I am almost learning...

marstonpear said:
I'd suggest giving MiFlash a try. Because a few times I tried flashing with the script file bundled with the stock ROM, I also had some bootloops, but MiFlash fixed the issue.
Click to expand...
Click to collapse
mismatched image and device error when MiFlashing image.
There are some sugestions about erasing the first 2 lines in flashing script ( where the daisy ROM is cheched in the image and the hardware) and flash again.
I am not sure this is a good idea. I'm affraid things could become worse.
But I am sure there is a Xiaomi Mi A2 Lite writen in the phone box and the image I used was daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04
What is next step?

renatogui said:
mismatched image and device error when MiFlashing image.
There are some sugestions about erasing the first 2 lines in flashing script ( where the daisy ROM is cheched in the image and the hardware) and flash again.
I am not sure this is a good idea. I'm affraid things could become worse.
But I am sure there is a Xiaomi Mi A2 Lite writen in the phone box and the image I used was daisy_global_images_V10.0.13.0.PDLMIXM_20190813.0000.00_9.0_5d0d486f04
What is next step?
Click to expand...
Click to collapse
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification. Simplest way to verify your device is indeed Mi A2 Lite is checking the back cover of the phone and seeing the androidone logo there. If the logo is there go on with the procedure of deleting the first line of the code, then flashing it. Never interrupt the flashing process as it may cause the device's hardware to fail afterwards. I'd suggest using 10.0.13.0 for flashing as that one is the latest ROM that's provided as full version by Xiaomi. If you're still using Linux/MacOS to flash the firmware, I had an issue before on my Mac that didn't let me flash the stock ROM: flash_all.sh was wrongly formatted, so I had to add "./" (dot slash without the quotation marks) to the beginning of every line in the code that began with "fastboot" to make it work.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh

marstonpear said:
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification. Simplest way to verify your device is indeed Mi A2 Lite is checking the back cover of the phone and seeing the androidone logo there. If the logo is there go on with the procedure of deleting the first line of the code, then flashing it. Never interrupt the flashing process as it may cause the device's hardware to fail afterwards. I'd suggest using 10.0.13.0 for flashing as that one is the latest ROM that's provided as full version by Xiaomi. If you're still using Linux/MacOS to flash the firmware, I had an issue before on my Mac that didn't let me flash the stock ROM: flash_all.sh was wrongly formatted, so I had to add "./" (dot slash without the quotation marks) to the beginning of every line in the code that began with "fastboot" to make it work.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh
Click to expand...
Click to collapse
Yes, there is the androidone logo in the back.
I had to interrupt the flashing the very first time because it stop before end like frozen.
You say I can damaged the hardware doing this?

renatogui said:
Yes, there is the androidone logo in the back.
I had to interrupt the flashing the very first time because it stop before end like frozen.
You say I can damaged the hardware doing this?
Click to expand...
Click to collapse
Yes the flash storage on the phone can be damaged just by interrupting the flashing process, especially while EDL flashing. So make sure you kill other unnecessary processes on your PC before you start flashing so it does not hang again.

marstonpear said:
If you're sure your device is daisy - Mi A2 Lite, you can delete the first line of the .sh or .bat to skip verification.
TL;DR : If device is daisy and you're on Windows, delete the first line and try again. If device is daisy and you're on Linux/MacOS, add "./" in front of every line that starts with "fastboot" in flash_all.sh
Click to expand...
Click to collapse
Now I know the reason of mismatching. All the scripts bundled with Xiaomi_Mi_A2_Lite_V10.0.13.0.PDIMIXM_20190807.0000.00_Global_9.0_XFT are made for jasmine. I will find another image more trustworthy than this one.

marstonpear said:
Yes the flash storage on the phone can be damaged just by interrupting the flashing process, especially while EDL flashing. So make sure you kill other unnecessary processes on your PC before you start flashing so it does not hang again.
Click to expand...
Click to collapse
I used the image v10.0.13.0 from https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
I check the scripts to verify if they are for daisy and flashed using MiFlash20191206.
At the end I got this error:
Not catch checkpoint [\$fastboot -s.*lock] .flash not done
:crying:

renatogui said:
I used the image v10.0.13.0 from https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
I check the scripts to verify if they are for daisy and flashed using MiFlash20191206.
At the end I got this error:
Not catch checkpoint [\$fastboot -s.*lock] .flash not done
:crying:
Click to expand...
Click to collapse
for others having the same probem I've learn in another thread that this error is issued because I did not choose the lock option below right of MiFlash tool. That is why it didn't catch the lock checkpoint. But the end of the message is not true because at this checkpoint, the flashing is already done. I simply turn the phone off and on again and the boot was normal.
Thanks for all that help me specially marstonpear.
Thread closed... until next problem.

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.