Database Info

Step by Step guides on rooting / un-rooting the T-mobile LG V10 for MM 6.0

Hello everyone,
Here are some step by step guides for those of you who need detailed instructions for rooting and un-rooting the T-mobile LG V10.
The guides are short and to the point and are meant to be followed one after the other (STEP#1 --> STEP#2 --> STEP#3).
For the step#3 guide, you must choose one out of the three available:
UnRoot, stock, or custom MM 6.0
Guides:
Tmobile-LGV10_pre_flash_MM_6_0_requirements_STEP_1
Tmobile-LGV10_pre_flash_MM_6_0_requirements_STEP_2
Tmobile-LGV10_flash_Stock_UnRoot_MM_6_0_STEP_3 <------ If you want to just have stock MM 6.0 only (no root, use this if you want to return the phone or sell it)
Tmobile-LGV10_flash_Root_Stock_MM_6_0_STEP_3 <------ If you want to just have stock MM 6.0 with root only
Tmobile-LGV10_flash_Root_Custom_MM_6_0_STEP_3 <------ If you want to have a custom MM 6.0 ROM with root
Tmobile-LGV10_Dirty_Cow_Root_MM_6_0 <------ If you want to gain root access on your stock MM 6.0 rom using the "dirty cow" exploit
The guides will walk you through:
Downloading and Installing the necessary drivers / tools
Unlocking your bootloader
Flashing the stock .kdz file
Flashing the rooted .TOT file
Using TWRP to gain root status
I assume the following:
Your T-mobile LG V10 phone is already on MM 6.0 not lollipop
If you are on lollipop YOU MUST follow the guides below in the exact order listed:
Tmobile-LGV10_pre_flash_MM_6_0_requirements_STEP_1
Tmobile-LGV10_pre_flash_MM_6_0_requirements_STEP_2
Tmobile-LGV10_flash_Root_Stock_MM_6_0_STEP_3
(If you don't, YOU WILL brick your phone! Also, keep in mind that once you upgrade to MM 6.0 YOU WILL NOT be able to downgrade!!)
You are using a Microsoft Windows operating system (Windows 7 or above)
You understand that all data on your phone will be deleted
You understand that your warranty is now gone
You understand that YOU MUST follow the guides one after the other (1 -> 2 -> 3). If you deviate from this YOU WILL NOT be successful in rooting your phone
You understand that YOU MUST follow the steps in the guides one after the other (1 -> 2 -> 3). If you deviate from this YOU WILL NOT be successful in rooting your phone
Your phone's USB PC Connection (mode your phone is in when connected to your PC) is on Media device (MTP) mode. ADB and Fastboot commands to the device WILL NOT work if device is not on this mode
***Un-root***​
If you want to "un-root" your device (go back to default stock) use the Tmobile-LGV10_flash_Stock_UnRoot_MM_6_0_STEP_3 guide.
(Keep in mind that this WILL DELETE all data on the phone)
***Fastboot device not detected issue***​
Please click on the link below and follow the guide:
Manually installing Android ADB USB Driver
***Dirty Cow Exploit for Root***​
I have added a new guide Tmobile-LGV10_Dirty_Cow_Root_MM_6_0 for those of you who would like to use the "Dirty Cow" exploit to gain root access
Link to download the guide (in case the guide attached to this thread is not showing): Click --> Tmobile-LGV10_Dirty_Cow_Root_MM_6_0
Using this exploit will allow you to install TWRP on your phone which allows you to install SuperSU.
Yes, this method to gain root works on the new software update H90120L as well as the older ones
You will have to first complete all of the steps in the guides listed below before attempting to use the Dirty Cow exploit.
- Tmobile-LGV10_pre_flash_MM_6_0_requirements_STEP_1
- Tmobile-LGV10_pre_flash_MM_6_0_requirements_STEP_2
Keep in mind that this exploit will eventually be patched
I am not responsible for what you do to your phone
***Disclaimer***​
I take no responsibility in what you do to your phone
The step-by-step guides in this thread were made with the assumption that you will strictly follow them one after the other.
(If you don't, YOU WILL brick your phone!)
READ! READ! READ! Search this thread, read the guides one by one step by step, and pay attention to detail! Most problems have solutions, you just have to do a little homework.
If you run into an problem, verify that you have correctly completed all the steps for each guide before posting to this thread. Most problems come from guides / steps that were skipped.
Not all phones are created equal. What works for one person's phone might not work for your phone. Some phones have hardware issues
that may not arise until you attempt to circumvent security aka (root, install TWRP, etc.)
Use a laptop that is fully charged and plugged in to an outlet instead of a regular PC (unless it has a UPS attached to it) just in case you lose power during the flashing process.
(If you use a regular PC without a UPS attached to it and you lose power during the flashing process, YOU WILL brick your phone!)
I would like to thank the following people:
Tungkick
For his support
Root for both (H90120e and H90120j) <-- You are the man sir!!
Instructions on flashing and recovering from boot-loop
Anyone else I forgot to mention and or involved in allowing the rest of us to get root on our beloved LG V10 phones again. The android community is awesome!!!
Please leave a thank you if you find any of this helpful

Confirmed Root Testers:
jun19inf
guytano86
demkantor
jamiesco12
nymica
Thanks for the great write up!
Also.... first!!

Reserved... Thank you...
Sent from my LG-H901 using Tapatalk

xtremelora said:
Reserved... Thank you...
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
You guys are awesome. Now LG can kiss my asss

ok, so here is my progress
started at never been rooted stock MM
unlocked bootloader
followed all steps in this guide (and from original posts)
at TWRP screen after .tot flash i chose read only - couldnt wipe or anything (errors)
adb sideload wouldnt work either
used tungkick's recommendation
adb shell
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
reboot
then i saw this and panicked a bit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pulled battery
held volume down/power/ etc to get to recovery
still twrp
attempted to wipe... filed
just went ahead and flashed Eliminater74's latest part2
reboot
and.....
I am rooted 6.0!!
all seems to work great so far!
will report back if i find issues
XDA has the best people, big thanks to @tungkick and @Eliminater74
and anyone else who helped along the way!

If phone have boot error then still reboot can not put twrp pls flash file this:
Fix phone boot veri......fail
https://drive.google.com/file/d/0B8mSVItI_cqRMXZ6cjBpVFdGVTA/view?usp=sharing
File tot only add bootloader can unlock in fastboot .
Flash kdz 6.0> flash file tot> go to develop option > enabable oem unlock and usb debugging> adb reboot bootloader> fastboot oem unlock> phone unlock now>> flash next file tot have add twrp again> phone can put twrp ok.

jun19inf said:
Hello everyone,
I made a step by step guide on how I managed to flash my LG V10 (tmobile) using the recently released files / methods. Hopefully this guide helps. Thank you.
I would like to thank the following people:
• Eliminater74 <-- great work with his roms / files
• Tungkick <-- followed his instructions on flashing and recovering from bootloop
• Anyone else I forgot to mention and or involved in allowing the rest of us to get root on our beloved LG V10 phones again. The android community is awesome!!
Click to expand...
Click to collapse
Wow, well articulated and simple step-by-step instructions. How much do you charge per hour....we should contract you for all installs.

Is it possible to do this and still retain data? Like not wipe data in twrp, or does it automatically wipe when flashing the tot file? I've had to flash one kdz in the past 3 years and that was to upgrade to mm, it didn't wipe data though. I'm assuming it's basically the same process with the tot?

Swizzle82 said:
Is it possible to do this and still retain data? Like not wipe data in twrp, or does it automatically wipe when flashing the tot file? I've had to flash one kdz in the past 3 years and that was to upgrade to mm, it didn't wipe data though. I'm assuming it's basically the same process with the tot?
Click to expand...
Click to collapse
Just use LG Backup. When I used it it restored even my side loaded apps.
This method requires a wipe so it will erase everything.

Double0EK said:
Just use LG Backup. When I used it it restored even my side loaded apps.
This method requires a wipe so it will erase everything.
Click to expand...
Click to collapse
That's normally what I do, but it's not so much apps as my concern as it is all my tedious settings.. Lol.. Thanks for the info..

Is this for 6.0? I got the phone with 6.0 so is it safe to root with this?
Sent from my LG-H901 using XDA-Developers mobile app

Jaimesco12 said:
Is this for 6.0? I got the phone with 6.0 so is it safe to root with this?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Exactly what this is for.

Swizzle82 said:
Exactly what this is for.
Click to expand...
Click to collapse
Awesome about to attempt this will report back.
Sent from my LG-H901 using XDA-Developers mobile app

Jaimesco12 said:
Awesome about to attempt this will report back.
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Guys make sure you unlock the bootloader first
http://forum.xda-developers.com/tmobile-lg-v10/general/t-mobile-bootloader-factory-unlocked-t3236224
otherwise it wouldn't work.
---------- Post added at 07:18 AM ---------- Previous post was at 07:16 AM ----------
guytano86 said:
Guys make sure you unlock the bootloader first
http://forum.xda-developers.com/tmobile-lg-v10/general/t-mobile-bootloader-factory-unlocked-t3236224
otherwise it wouldn't work.
Click to expand...
Click to collapse
Im rooted now Yay!!!

Another confirmed!!

Thank you
jaysonic88 said:
Wow, well articulated and simple step-by-step instructions. How much do you charge per hour....we should contract you for all installs.
Click to expand...
Click to collapse
Wanted to make sure it was easy to follow. Thank you.

The only problem I have with this is that I'm going up north after work tomorrow and won't have time until Tuesday to root. ?
But seriously, great write up! And thanks for taking the time to make it simple!
Sent from my LG-H901 using Tapatalk

Can anyone confirm which version of Supersu is installed via this method and if it installs systemless? TY

Worked for me ! Now rooted!
Sent from my LG-H901 using XDA-Developers mobile app

I can't say thank you enough I missed root/recovery so much!
Sent from my LG-H901 using XDA-Developers mobile app

Can CF-Auto Root G930F really do no harm instead of G930W8

Hey everyone,
Please bare with me, I haven't rooted a phone (using Chainfire's work with a custom stock rom) in over 3 years and I'm once again new at this.
Yesterday I flashed a stock rom (using Odin) to my S7 SM-G930W8 to downgrade from nougat back to Marshmallow 6.0.1 (G930W8VLU2APK3 , (carrier: Koodo), Canada). Now I want to root it (I know, I'll have to redo the whole process but while I have a fresh backup copy, why not) especially because of the software updates nagging. I haven't found any G930W8 root files, only G930F, and while some people say "Oh, just go ahead, doesn't matter", I just want further advice on if I should really use G930F even if my current model is G930W8. I don'T wanna mess anything with my carrier (like unable to place calls, or my IMEI numbers not showing up or anything uncool (yes, I know that my warranty will most probably be void but if it's "just" that, I can live with that)).
So, any advice ?

isnull said:
Hey everyone,
Please bare with me, I haven't rooted a phone (using Chainfire's work with a custom stock rom) in over 3 years and I'm once again new at this.
Yesterday I flashed a stock rom (using Odin) to my S7 SM-G930W8 to downgrade from nougat back to lollipop 6.0.1 (G930W8VLU2APK3 , (carrier: Koodo), Canada). Now I want to root it (I know, I'll have to redo the whole process but while I have a fresh backup copy, why not) especially because of the software updates nagging. I haven't found any G930W8 root files, only G930F, and while some people say "Oh, just go ahead, doesn't matter", I just want further advice on if I should really use G930F even if my current model is G930W8. I don'T wanna mess anything with my carrier (like unable to place calls, or my IMEI numbers not showing up or anything uncool (yes, I know that my warranty will most probably be void but if it's "just" that, I can live with that)).
So, any advice ?
Click to expand...
Click to collapse
Hi mate
Yes it does work in all Exynos variants
Check this confirmation from an user in Chainfire thread
https://forum.xda-developers.com/showpost.php?p=65982420&postcount=83
Just follow the steps as it was a G930F

MAX 404 said:
Hi mate
Yes it does work in all Exynos variants
Check this confirmation from an user in Chainfire thread
https://forum.xda-developers.com/showpost.php?p=65982420&postcount=83
Just follow the steps as it was a G930F
Click to expand...
Click to collapse
Hi, thanks for your quick reply !
But how do I know mine is not snapdragon and is exynos? Does W8 at the end imply it'S a exynos cpu ?

isnull said:
Hi, thanks for your quick reply !
But how do I know mine is not snapdragon and is exynos? Does W8 at the end imply it'S a exynos cpu ?
Click to expand...
Click to collapse
Hi
yes W8 model comes with a Exynos chipset......but you can always double check with an app like PhoneInfo

MAX 404 said:
Hi
yes W8 model comes with a Exynos chipset......but you can always double check with an app like PhoneInfo
Click to expand...
Click to collapse
Oh, thanks, neat little app. And yeah, exynos indeed:
screenshot

isnull said:
Oh, thanks, neat little app. And yeah, exynos indeed:
Click to expand...
Click to collapse
Great..now read.....and go for it
CF autoroot only works on MM in N you need to flash TWRP and then SuperSU-v2.79-SR3

MAX 404 said:
Great..now read.....and go for it
CF autoroot only works on MM in N you need to flash TWRP and then SuperSU-v2.79-SR3
Click to expand...
Click to collapse
1 - Did you mean only works on Marshmallow but that in Nougat you need TWRP ? (sorry to ask)
2 - Doing MM (and reinstalling MM) anyway (I just realized I had mistakenly typed "lollipop" in my opening question, I meant MM)
3 - Just downloaded "CF-Auto-Root-herolte-heroltexx-smg930f.zip", is it normal it's just 35 MB ? I was expecting something like ~2 GB, which would contain the modded (rooted) stock firmware
And yeah, I think I'll have more reading to do than I thought

isnull said:
1 - Did you mean only works on Marshmallow but that in Nougat you need TWRP ? (sorry to ask)
2 - Doing MM (and reinstalling MM) anyway (I just realized I had mistakenly typed "lollipop" in my opening question, I meant MM)
3 - Just downloaded "CF-Auto-Root-herolte-heroltexx-smg930f.zip", is it normal it's just 35 MB ? I was expecting something like ~2 GB, which would contain the modded (rooted) stock firmware
And yeah, I think I'll have more reading to do than I thought
Click to expand...
Click to collapse
Hi
1 That is right
2 I thought so...
3 Yes 35MB is about right ....is not the whole rom is only patching some modifying

MAX 404 said:
Yes 35MB is about right ....is not the whole rom is only patching some modifying
Click to expand...
Click to collapse
Oh cool, thanks! Is there any comprehensible guide here (or anywhere) for this? Like is it's just a patch if I load it in Odin's AP or BP or whatever... (not specified in Chainfire's post) ? I'm willing to read a 24 hour long paper if I need to

isnull said:
Oh cool, thanks! Is there any comprehensible guide here (or anywhere) for this? Like is it's just a patch if I load it in Odin's AP or BP or whatever... (not specified in Chainfire's post) ? I'm willing to read a 24 hour long paper if I need to
Click to expand...
Click to collapse
Ok , get your reading glasses out....
This is the official post....
https://forum.xda-developers.com/galaxy-s7/development/sm-g930-exynos-cf-auto-root-t3337353
And here the instructions for CF Autoroot
ODIN flashable devices
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as PDA.
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3-v1.85.exe file, press the PDA button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Extract from here
https://autoroot.chainfire.eu/

MAX 404 said:
Ok , get your reading glasses out....
This is the official post....
https://forum.xda-developers.com/galaxy-s7/development/sm-g930-exynos-cf-auto-root-t3337353
And here the instructions for CF Autoroot
ODIN flashable devices
BASIC INSTRUCTIONS
All downloads contain .tar.md5 files flashable in ODIN as PDA.
Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off), then start the included Odin3-v1.85.exe file, press the PDA button, select the .tar.md5 file, and click Start. You can find more detailed instructions and assistance at XDA.
A modified recovery and cache partition will be flashed, which will install (only) SuperSU, then clean-up the cache partition and re-flash the stock recovery.
For the root to work, the device must reboot into recovery. Most devices will do this automatically after flashing these files, but in case that does not happen, please boot into recovery manually.
UNLOCK BOOTLOADERS
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Extract from here
https://autoroot.chainfire.eu/
Click to expand...
Click to collapse
Wow, thanks so much!
Quick question: once I'm flashed & rooted (when everything's been successful), can I turn off "OEM Lock" or do I leave it on?

isnull said:
Wow, thanks so much!
Quick question: once I'm flashed & rooted (when everything's been successful), can I turn off "OEM Lock" or do I leave it on?
Click to expand...
Click to collapse
Up to you mate......mine is in unlock position

MAX 404 said:
Up to you mate......mine is in unlock position
Click to expand...
Click to collapse
Oh cool, thanks. Think I'm ready now, will post a screenshot when I'm done, after re-reading a couple of things (Samsung Pay (which I don't use anyway), etc). You've been a huge help!

MAX 404 said:
Up to you mate......mine is in unlock position
Click to expand...
Click to collapse
It worked! Hell yeah. Thanks again! I'm def' gonna donate to Chainfire, this was rather easy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

isnull said:
It worked! Hell yeah. Thanks again! I'm def' gonna donate to Chainfire, this was rather easy
Click to expand...
Click to collapse
Yeah he deserve it !!!
Cool mate glad for you.

@MAX 404
Is it normal when I wipe cache partition now I get a red text saying "dm-verity verification failed" ? I just Googled it and some say it's because I might have flashed an incompatible ROM before rooting but I for sure flashed a compatible one. Otherwise, does it even matter whether it says that or not?
Also, unrelated, I tried a trick to quit having software updates (firmware by Samsung) by clicking on the FotaAgent and "installing" it (doesn't actually install it, in /system/priv-apps/ (going by memory here, might be mistaken) but then I had the nagging "Unfortunately, Software Update has stopped" message a couple of times in a row on each boot or every time I turn on Wi-fi. I then tried fixing THAT by disabling DiagMonAgent through BK Disabler, but that now gives me a message (on boot up) saying "All apps associated with this action have been blocked, disabled or uninstalled". Not the end of the world but still, is there a way to end all this? I was thinking re-flashing the ROM (stock) but I'm hoping there's another solution.

Just in case someone was going to reply to this here, I moved the "Software update" question here since it's a whole other story.

isnull said:
@MAX 404
Is it normal when I wipe cache partition now I get a red text saying "dm-verity verification failed" ? I just Googled it and some say it's because I might have flashed an incompatible ROM before rooting but I for sure flashed a compatible one. Otherwise, does it even matter whether it says that or not?
Also, unrelated, I tried a trick to quit having software updates (firmware by Samsung) by clicking on the FotaAgent and "installing" it (doesn't actually install it, in /system/priv-apps/ (going by memory here, might be mistaken) but then I had the nagging "Unfortunately, Software Update has stopped" message a couple of times in a row on each boot or every time I turn on Wi-fi. I then tried fixing THAT by disabling DiagMonAgent through BK Disabler, but that now gives me a message (on boot up) saying "All apps associated with this action have been blocked, disabled or uninstalled". Not the end of the world but still, is there a way to end all this? I was thinking re-flashing the ROM (stock) but I'm hoping there's another solution.
Click to expand...
Click to collapse
Hi
Regarding Dm-Verity ,, is a message that detects that the sytem is not 100% original , is easy to solve if you have a custom recovery installed then you can flash a dm-verity and force encryption disabler zip. without a custom recovery is a little harder... but if it is not giving you any trouble let it be....
Regarding the software update issue ..no idea how to solve it , never had that problem..sorry only thing i can think of is to re flash rom...BTW once you are rooted ther will not be updates for your device....OTA check your binary status if is not original...there is no OTA

MAX 404 said:
Hi
Regarding Dm-Verity ,, is a message that detects that the sytem is not 100% original , is easy to solve if you have a custom recovery installed then you can flash a dm-verity and force encryption disabler zip. without a custom recovery is a little harder... but if it is not giving you any trouble let it be....
Regarding the software update issue ..no idea how to solve it , never had that problem..sorry only thing i can think of is to re flash rom...BTW once you are rooted ther will not be updates for your device....OTA check your binary status if is not original...there is no OTA
Click to expand...
Click to collapse
Thanks for taking the time. Oh, I see, so from what I understand the dm-verity is not really an issue. Thanks for the tip on the custom recovery. But from what you know (doesn't have to be exact), even if I have the capability (say with twrp) do I really need to flash the dm-verity & force encryption disabler? Or is it for those who are just nagged by the small text when they're in recovery mode?
It's REALLY GOOD to know about the OTA not pushing through or by push-notifications if rooted, next time I flash it (still didn't have time to get around it) I'll just root it directly after and nevermind all the steps to deactivate the firmware updates, thanks!

isnull said:
Thanks for taking the time. Oh, I see, so from what I understand the dm-verity is not really an issue. Thanks for the tip on the custom recovery. But from what you know (doesn't have to be exact), even if I have the capability (say with twrp) do I really need to flash the dm-verity & force encryption disabler? Or is it for those who are just nagged by the small text when they're in recovery mode?
It's REALLY GOOD to know about the OTA not pushing through or by push-notifications if rooted, next time I flash it (still didn't have time to get around it) I'll just root it directly after and nevermind all the steps to deactivate the firmware updates, thanks!
Click to expand...
Click to collapse
Hi mate
If your only modification to the system is just root and you do not notice any thing strange let it be do not flash dm verity zip , that error is caused by a "flag" set by the kernel as far as i know it should not be a problem , actually latest SuperSu should take care of it also

[Rom] Bootloader Recover Huawei Watch 2 BT LEO-B09/LEO-BX9

Hi Everyone,
As some of you have tested the first firmware (4G) available in the Bluetooth version, our friend @mcdull and @sorayahya have fixed a broken Watch using below firmware.
Sorayahya will post the manual in this same thread so all of you can make your watches functional again.
Link: https://mega.nz/#!gqQATbga
Decryption key: !mD2smD4jEq_FOkhE1uy0PQ5uf6XYpxR0wxxkM6msPiE
Special thanks to @mcdull for preparing this file to all of us.

So after downloading the above files from dr_chch's post extract the files. After that we will need to get QPST which has the program called QFIL which we will be using to unbrick the watch.
Download “QPST 2.7 (QFIL)” from HERE and extract it to an empty folder. Install QPST by double clicking setup.exe.
Now you want to plug in your Huawei Watch 2 to the PC using the charging cable that came with the watch.
At first you might get a notification from the PC that the usb device is unknown, if that happens you will need to hold down on your watch's right top button for around 30 seconds. After that you should get a notification from your PC that a new device was plugged in and it will start to install a new driver. Once that's done you should have a "Qualcomm HS-USB QDLoader 9008" device show up in your device manager.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We won't be needing the storage device to show up so if it doesn't for you that's alright.
Next we will open QFIL from start menu, if it's not in the start menu you can locate it by going to Program Files\Qualcomm\bin\. You should see "Qualcomm HS-USB QDLoader 9008" written on the top, if it's not then click on the "SelectPort" button and then select "Qualcomm HS-USB QDLoader 9008". After that Insert all the necessary file needed by QFIL:
(1)The programmer will be prog_emmc_firehose.mbn;
(2)Use the rawprogram0.xml;
(3)Use the patch0.xml;
(4)Hit “Download” button.
If the process you did with QFIL finished successfully, the watch will boot again. If not then try to restart the program and repeat the same process again until you succeed.
At this point your watch is alive again but without a firmware so you will need to flash the correct ROM through fastboot.
For that you can check out the guide dr_chch made here:
https://forum.xda-developers.com/watch-2/development/rom-huawei-watch-2-bt-leo-b09-leo-bx9-t3616779

Thanks for the files and the recovery guide. Please make sure you understand the below before your recovery.
1. You will probably lost the original MAC Address of your WIFI and Bluetooth. But at least the device will work with both functions, it will assign another MAC Address for you.
2. The recovery file includes only the boot loader, you still need to boot into fastboot (holding the device power button until you feel it vibrate. Then quickly release and press the power buttons) to flash the latest ROM downloaded from here.

Mod Edit
what you can help?

dr_chch said:
Hi Everyone,
As some of you have tested the first firmware (4G) available in the Bluetooth version, our friend @mcdull and @sorayahya have fixed a broken Watch using below firmware.
Sorayahya will post the manual in this same thread so all of you can make your watches functional again.
Am getting an error accessing the mega link.
Click to expand...
Click to collapse

kenmlax said:
dr_chch said:
Hi Everyone,
As some of you have tested the first firmware (4G) available in the Bluetooth version, our friend @mcdull and @sorayahya have fixed a broken Watch using below firmware.
Sorayahya will post the manual in this same thread so all of you can make your watches functional again.
Am getting an error accessing the mega link.
Click to expand...
Click to collapse
kenmlax said:
Was this solution ever shared cause ive been waiting for it for quite some time now... my huwei watch model is LEO-DLXX
Click to expand...
Click to collapse
You wont need this file as this is for de-bricking the BT version only.
And the mega link works just fine.
Click to expand...
Click to collapse

mcdull said:
kenmlax said:
You wont need this file as this is for de-bricking the BT version only.
And the mega link works just fine.
Click to expand...
Click to collapse
Is there a way to unbrick the 4g version of this watch. specifically the LEO-DLXX
Click to expand...
Click to collapse

kenmlax said:
mcdull said:
Is there a way to unbrick the 4g version of this watch. specifically the LEO-DLXX
Click to expand...
Click to collapse
If you noticed all the quote, reply, pm name... I have answered you MANY times.
Click to expand...
Click to collapse

Code:
Start Download
Program Path:C:\Leo\prog_emmc_firehose.mbn
COM Port number:7
Sahara Connecting ...
Sahara Version:0
Start Sending Programmer
Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download
I'm getting this error. I tried multiple Desktop's and win7/10

Just learned of this thread......
I am wondering if anyone got the LEO-DLXX Watch 2 4G working again? Mine is recognized in QFIL as a qualcomm 9008, but that is as far as I can get. Has anyone been able to get the bootloader working with the files in this thread? I'm not sure what happened to mine, but it got bricked while installing the global ROM Huawei2_NXG46W_Global_4G. It is strange how it worked for so many people, but not mine. Any help or guidance is appreciated.

stephen1981 said:
I am wondering if anyone got the LEO-DLXX Watch 2 4G working again? Mine is recognized in QFIL as a qualcomm 9008, but that is as far as I can get. Has anyone been able to get the bootloader working with the files in this thread? I'm not sure what happened to mine, but it got bricked while installing the global ROM Huawei2_NXG46W_Global_4G. It is strange how it worked for so many people, but not mine. Any help or guidance is appreciated.
Click to expand...
Click to collapse
it worked for me

I tried many times now and still get the error message.
Also i've used all of the program build's
Is there anyone who can assist me in this process?

luciano1961 said:
it worked for me
Click to expand...
Click to collapse
The ROM worked for you or were you able to recover the boot loader? Has the LEO-L09S recovery found here: https://forum.xda-developers.com/watch-2/help/flashed-huawei-watch2-power-t3632341 worked for anyone?
basziee said:
I tried many times now and still get the error message.
Also i've used all of the program build's
Is there anyone who can assist me in this process?
Click to expand...
Click to collapse
Are you getting the sahara protocol error message as well? Are you trying to use QFIL to restore the bootloader on the LEO-DLXX watch?
Two strange things happened when flashing the ROM from this thread: https://forum.xda-developers.com/watch-2/development/rom-huawei-watch-2-4g-l-09s-global-t3602205
First, it took a very long time for the device to show up with adb devices. There was a device there, but it wasn't listing every time I connected. As soon as I did, I went ahead but probably shouldn't have. Second, the fast boot process seemed to go along as normal (I have flashed a few ROMS, but never on a watch) until it came to the system. The system fast boot process took seconds....not longer than bootloader, boot, etc.... That is something I have not experienced before and thought it may have to do with a smaller system for android wear, but in fact it is not that small. After that, well it is bricked, but at least showing as a qualcomm disk.
I guess I have to wait until the recovery bootloader (firehose, rawprogram etc..) is leaked for the LEO-DLXX device. There is no possibility of returning the device or paying for service since it was bought in China and brought to Canada where it hasn't even been released yet.

stephen1981 said:
Are you getting the sahara protocol error message as well? Are you trying to use QFIL to restore the bootloader on the LEO-DLXX watch?
Click to expand...
Click to collapse
Yes everytime I tried to flash the .mbm file I get the sahara protocol error saying it is 0 bytes.
I also tried draining the battery fully and I switched between many desktop's
And still no luck
And quick question: my friend has the same watch. Can i do something with that to fix my own?

Has anyone successfully flashed the Huawei Watch 2 Pro (LEO-DLXXU)?
I'm keen to get my watch compatible with Play store apps rather than Huawei App Store, but I'd be keen to hear from someone who has been successful.

Hi @dr_chch, do you have the files for DLXX ? I tried to flash the Google P preview forgeting that I have a 4G and not BT model and It totally bricked my watch...

Supercairos said:
Hi @dr_chch, do you have the files for DLXX ? I tried to flash the Google P preview forgeting that I have a 4G and not BT model and It totally bricked my watch...
Click to expand...
Click to collapse
same here, i just wish someone would help us find the right files for the 4G version.

Same problem with my LEO-DLXX. I noticed that 1 of 3 files needed to flash has wrong name
rawprogram_unsparse.xml , nor rawprogram0.xml
Is there a problem with this?

Supercairos said:
Hi @dr_chch, do you have the files for DLXX ? I tried to flash the Google P preview forgeting that I have a 4G and not BT model and It totally bricked my watch...
Click to expand...
Click to collapse
You mean Oreo?

hackintosh5 said:
You mean Oreo?
Click to expand...
Click to collapse
Nope he means P as in this

Question The current system is not compatible with the hardware........What's the problem?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello~
After a long time I got p11.
happy sitting at the computer
Changed to global rom.
The latest version of the current global rom is 210805 (8/27)
After installing 210805 ROM, a message is displayed like the picture.
And it turns off automatically
But if I install older version 210520(5/31)
There's nothing wrong with it! Messages like pictures are not displayed
Also, if I update from version 210520 (after all, the latest version 210805)
Also displayed like a picture
What's the problem?
Because my native language is not English
I am very sorry for the poor language
I wish you good luck in your daily life
I look forward to your kind comments
thank you

1. Flash J606F Factory rescue.
2. Flash J606F 210805 ROW.
But after these processes, I lost my serial number.

guess you are from China lol
me with the same problem.
TRY 1. Unbox, then Qfil, flash 210906, incompatible;
TRY 2. downgrade to 12.0.519 then Qfil 210121, it's ok. But the first OTA, incompatible;
now I'm staying at 12.6.084, adb delete most of the useless apps.
I don't like ZUI HOME, dare not to delete it though.

me too ((

the bad is: it's said they add some restrictions to prevent users flashing cross-region roms in ZUI 12.6.
the good: we can use Qfil to flash back to any firmware that can run normally.
Now, I'm using the latest ZUI 12.6 (cuz I'm in China), with adb having deleted most of the useless apps. And since it has the google framework, we can simply install a googleplay.apk. It runs pretty good for now.

Upppppp.

ong14 said:
1. Flash J606F Factory rescue.
2. Flash J606F 210805 ROW.
But after these processes, I lost my serial number.
Click to expand...
Click to collapse
please more elaborate.

famicom9x said:
please more elaborate.
Click to expand...
Click to collapse
1. Flash rescue mode from h*t*t*p*s*://4pda.to/pages/go/?u=https%3A%2F%2Fandroidhost.ru%2FY1n&e=103996404
2. Flash latest firmware from h*t*t*p*s*://mirrors.lolinet.com/firmware/lenovo/Tab_P11/TB-J606F/TB-J606F_S120228_210906_ROW.zip
3. Done

ong14 said:
1. Flash rescue mode from h*t*t*p*s*://4pda.to/pages/go/?u=https%3A%2F%2Fandroidhost.ru%2FY1n&e=103996404
2. Flash latest firmware from h*t*t*p*s*://mirrors.lolinet.com/firmware/lenovo/Tab_P11/TB-J606F/TB-J606F_S120228_210906_ROW.zip
3. Done
Click to expand...
Click to collapse
1. can i use qfil to flash rescue rom ?
2. do i need to open the rom to see it work ?
3. then i immediately flash the lastest firmware rom?
4. do i need to unlock device or something?

Just flash rescue mode via qfil as usual, then official pad11(global) or xiaoxin(Chinese) firmware.
Be warned, you may lost your serial number.

ong14 said:
Just flash rescue mode via qfil as usual, then official pad11(global) or xiaoxin(Chinese) firmware.
Be warned, you may lost your serial number.
Click to expand...
Click to collapse
is there any way to restore serial number? and now my device can't boot it lost recovery, and is stuck in bootloader mode! Can you help me!

Did you flash rescue mode? It should boot up without problem.

ong14 said:
Did you flash rescue mode? It should boot up without problem.
Click to expand...
Click to collapse
it's still the same! after flashing finished, it rebooted and entered fastboot mode.

Please post your qfil settings.

ong14 said:
Please post your qfil settings.
Click to expand...
Click to collapse
Its.

hauuet said:
Its.
View attachment 5425061
Click to expand...
Click to collapse
i've seen someone posted that you need to unlock the device to flash international rom, not sure it's true or not, still wait for someone to post a VERY DETAIL tutorial about how to do this for noob like me

famicom9x said:
i've seen someone posted that you need to unlock the device to flash international rom, not sure it's true or not, still wait for someone to post a VERY DETAIL tutorial about how to do this for noob like me
Click to expand...
Click to collapse
No need to unlock to flash Global Rom.
Only version 210520 can be used. The other versions cannot be used.
Config like me.
Sorry I use GG tranlate

hungali33 said:
No need to unlock to flash Global Rom.
Only version 510520 can be used. The other versions cannot be used.
Config like me.
Sorry I use GG tranlate
Click to expand...
Click to collapse
where can i download the old 510520 version?

whitemilk_kor said:
View attachment 5407263
Hello~
After a long time I got p11.
happy sitting at the computer
Changed to global rom.
The latest version of the current global rom is 210805 (8/27)
After installing 210805 ROM, a message is displayed like the picture.
And it turns off automatically
But if I install older version 210520(5/31)
There's nothing wrong with it! Messages like pictures are not displayed
Also, if I update from version 210520 (after all, the latest version 210805)
Also displayed like a picture
What's the problem?
Because my native language is not English
I am very sorry for the poor language
I wish you good luck in your daily life
I look forward to your kind comments
thank you
Click to expand...
Click to collapse
닉네임 보니 한국인이신것 같네요!
LMSA를 이용해서 210906 펌웨어 재설치해보시겠어요?

hungali33 said:
No need to unlock to flash Global Rom.
Only version 510520 can be used. The other versions cannot be used.
Config like me.
Sorry I use GG tranlate
Click to expand...
Click to collapse
guess you are talking about "210520". That's the only "latest" rom working on Chinese version pad.

Help, I have a redmi 9a and after trying to downgrade a version of miui it gave it hardbrick and when flashing it in sp it gives me a status error

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

duvanlop04 said:
Click to expand...
Click to collapse
Use this sp flash tool

Rares6567 said:
Utilice esta herramienta flash sp
Click to expand...
Click to collapse
thanks I'm going to flash it to see if it lets me

duvanlop04 said:
thanks I'm going to flash it to see if it lets me
Click to expand...
Click to collapse
Did it work?

Dalzz said:
Did it work?
Click to expand...
Click to collapse
Not yet, I'm talking with him in private. Do you have the same problem, hard bricked device??

Rares6567 said:
Not yet, I'm talking with him in private. Do you have the same problem, hard bricked device??
Click to expand...
Click to collapse
Yes, I have the same problem after flashing old MIUI version.

Dalzz said:
Yes, I have the same problem after flashing old MIUI version.
Click to expand...
Click to collapse
You can flash new miui version?

Rares6567 said:
You can flash new miui version?
Click to expand...
Click to collapse
I can't right now since I dont have access to my PC

Dalzz said:
I can't right now since I dont have access to my PC
Click to expand...
Click to collapse
Ahhhh sad

why does it become hard bricked after trying to downgrade?

Download latest china rom then use sp flash v5.2020

jdd1996 said:
why does it become hard bricked after trying to downgrade?
Click to expand...
Click to collapse
I don't know but i think because when you have like data from miui 12.5 and want to downgrade to 12.0.10 your miui 12.5 data will be there and this will not work properly, and yeahh.... You can't do that if u don't format ig

i see i understand.
I have 12.5.4.0 RCDMIXM --
How can i flash a custom recovery in it ? I try flashing orange fox but it gives me a dm-verity error, and even if i get to the recovery, it gets stuck on the loading screen.

jdd1996 said:
i see i understand.
I have 12.5.4.0 RCDMIXM --
How can i flash a custom recovery in it ? I try flashing orange fox but it gives me a dm-verity error, and even if i get to the recovery, it gets stuck on the loading screen.
Click to expand...
Click to collapse
I don't think there is a orange fox version for android 11( I'm not sure) so can u try twrp. If no try flashing the vbmeta (idk)

Rares6567 said:
I don't think there is a orange fox version for android 11( I'm not sure) so can u try twrp. If no try flashing the vbmeta (idk)
Click to expand...
Click to collapse
My last stock ROM was 12.5.7 A11 based.
I tried twrp 3.4 and .5 and both work good.
In second time I flashed orange fox with success (despite android 11 not supported) and everything works fine.
However I suggest first to flash stock 12.0.10 and after.flashing OF to see working wifi and BT.

I tried flashing 12.0.10.0 and phone would never boot, i'm not very tech savvy, i ended up deleting that ROM by mistake one day. So i dont have it anymore, 4.2 gb i lost there. In regards to the custom recovery, i'll maybe try twrp, thanks
(it all sounds too risky and problematic, im not sure if i want to continue with this phone, for now i just keep it off, its so bad, i dont use it, no custom recovery, no roms, nothing, everything bugged, it gets bricked easily, xiomi cloud, xiomi login, 3 different security methods, SLA, DA, im so overwhelmed by the amount of sh!"# it has, that its just not a pleasant experience, i haven't been able to use a single custom rom, and i have downloaded around 11 GB's in files with mobile data, i haven't been able to do anything, and i have been trying to mod it for the past 2-3 months and no progress. The rest of the phones i've had just , sudo fastboot flash system <image name> and its done, simple to use recoveries, everything easy. This one is a puzzle saying
" Do not buy me or use me " Going back 20 versions to flash a rom , what a joke, what did they smoke? kornflakes?
The Pinephone allows root on the default Rom, just simply go to developer options, and toggle
" Root Access " And the integrated options will give it to you, no google in it, nothing. Many phones like that one allow OEM unlock (Bootloader- Unlock) Natively, integrated without adb or fastboot. This Xiomi crap sold its soul to the china president and the gouverments, and to google. Bloated with crap, no freedom(they try to tie you to a MIUI account), No proper user control/autonomy, no capabilities, a cpu older than their previous releases.
I honestly feel like an old man trapped in 1980 with an old Commodore 64 , not knowing how to program anything with it ,or how to make a command work. Everything just gives error. And most importantly i feel i own a product worst than the Commodore 64.
I feel like i will have to wait another 20 years in order to see improvements, some kind of Windows, or more advanced version of Linux on the phone, polished ubuntu touch, or Fedora in it. Because right now it just sucks. The whole playstore structure, and the whole default OS is garbage on 92% of the phones.
I quit on them for the next 20 years.
WE should support the Pinephone, Oneplus, raspberry, in any case, Good Companies, not this Xiaomi crap.

<Moderator Edit>: Original English version of quote added.
jdd1996 said:
why does it become hard bricked after trying to downgrade?
Click to expand...
Click to collapse
yes

Thank god I fixed my phone, I just had to press volume + and - and wait a few seconds after I did the bypass with the latest china rom and sp flash tool v5.2020

duvanlop04 said:
Thank god I fixed my phone, I just had to press volume + and - and wait a few seconds after I did the bypass with the latest china rom and sp flash tool v5.2020
Click to expand...
Click to collapse
Happy to hear that bro! Have a good night/day!