Develop Bugs

[Firmware](Upgrade+Root/Downgrade/Unroot) Files+Flashing Guide [TOT/KDZ/TWRP] 7/07/19

This is for LG G3 D851 ONLY
TOT/KDZ/TWRP Untouched stock restore​
IF YOU WANT TO USE THIS GUIDE WAIT UNTIL I HAVE THE LGUP METHOD UP
Who can benefit from this?
Anyone who softbricked with access to download mode [KDZ RECOMMENDED]
Anyone who wants to use the OTA function after root [TWRP RECOMMENDED]
Anyone who needs to send the phone in for repair [TOT RECOMMENDED]
Anyone who wants to be on the most recent firmware [TWRP RECOMMENDED]
Anyone who wants to downgrade *After you update to 20B it is recommended to not downgrade. If you do you WILL have connection problems
Anyone who wants to return to stock from aosp or aokp
Tip: Most of the time TWRP will do what you need without the troubles and baggage TOT and KDZ bring. It will downgrade, upgrade, root, fix soft bricks or just give you a fresh untouched operating system (no personal data left on the phone if you follow instructions). It will also get rid of any proof on the phone that you were rooted (my t-mobile reports root to a remote server nothing can be done about that).
Strengthens and weaknesses for each method click here
TWRP Files/flashing guide Most recent = D85130g_00_0420 (07/05/17)
(This is a WIP)
Download your preferred choice of D851xxx-Untouched_Stock_Restore.zip HERE (Perfect 1:1 image unlike most roms)
Also download and copy superSu & twrp to your external sd if you want root and custom recovery SUPERSU DOWNLOAD AND TWRP-2.8.6.0-d851.zip
Copy D851xxx-Untouched_Stock_Restore.zip to phone (external sd if available)
Reboot into twrp
For firmware update do not wipe! skip to step 8. If you want untouched stock continue with step 4.
If upgrading from kitkat to lollipop wipe system before flashing.
Click [Wipe]
Click [Advanced Wipe] (For full wipe stock restore only)
Select dalvik cache, system, Data, Internal storage (only if you use external for downloaded file) and cache
Click the home Icon in the bottom left
Click [Install]
Select D851xxx-Untouched_Stock_Restore.zip (make sure you select the proper sd card)
If you want root and/or twrp add UPDATE-SuperSU-v2.37.zip to the queue by touching [Add More Zips]
Repeat for TWRP-2.8.6.0-d851.zip
Swipe to install [====>]
Install will now begin, pure stock: system, kernel, recovery, modem and rpm will be installed
After completion click [wipe cache/dalvik] (do not skip especially if you dirty flashed)
Swipe to wipe [====>]
Click [back]
Click [reboot system] (it might say no os but it is wrong you do have a os click restart anyway) [dirty flash will not have that problem]
If your sending for repair or jump do a factory reset with what should now be the stock recovery just to be safe.
DO NOT INSTALL ROOT UNLESS YOU WANT IT TO BE ROOTED
LGUP (KDZ/TOT)
(This is a WIP)
Check back later
KDZ files/flashing guide (Use TWRP if you can)
(This is a WIP)
Here are the KDZ files for the D851 I will keep this up to date as they are released
Make sure you uncompress the file!
Most recent Firmware
D85130g_00_0420 (07/05/17)
Old Firmware
D85130e_00_0711 (08/08/16)
D85130d_00_0404 (05/02/16)
D85120G_00 (10/05/15)
D85120E_00 (06/10/15)
D85120B_00 (04/17/15)
D85110R_00 (12/2/14)
D85110M_00 (09/10/14
D85110C_00 (07/16/14)
KDZ FLASHING GUIDE
For windows vista - windows 8.1
Very buggy on windows 8/8.1 x64 YMMV
Will not work on windows xp or older​
Click to expand...
Click to collapse
Download, extract and install LGUnitedMobileDriver
Download, extract and install VBCFJRedist_AIO_x86_x64
Download and extract LG Flashtool 2014.7z (This is not the same flash tool in TOT method)
Download one of the KDZ files from the beginning of the post and extract it in the Flashtool folder
Make sure you are at least at 50% battery
Enter download mode by holding the volume up button + plug the phone into the computer from a powered off state
Run LGFlashTool2014.exe as administrator
select type [CDMA] (Yes CDMA works just fine for our T-Mobile GSM phones DO NOT USE THE OTHER OPTIONS)
phone mode [diag]
reset time [33000]
select the KDZ file you extracted from inside the flashtool folder (D851xxx_00.kdz)
select [normal flash] (no wipe) or [CSE flash] (wipe) (Recommended)
click [start]
Select Country and Language Just leave default selections and click OK (Republic of Korea is the only country and it defaults to English)
It will analyze the phone extract the firmware and upgrade your phone automatically you will see progress on both the computer and phones display once the s/w upgrade percentage gets to about 80% your phone will restart don't freak out all went well and it will boot up to the LG welcome screen and if you selected CSE it will restart one last time
Total flash time for me was 2 minuets 56 seconds
If you use the normal flash you might need to do a factory reset if you get in a bootloop after flash
cse should have 0 problems on boot
Credits:
All credit goes to quangnhut123 for creating this tool you can find his thread HERE
TOT files/flashing guide
(This is a WIP)
Download, extract and install VBCFJRedist_AIO_x86_x64.exe
Download, extract and install LGUnitedMobileDriver
Download and extract lg flash tool (This is not the same flash tool in KDZ method)
Download and extract LG_D851.10C_TOT&DLL.7z
Make sure you are at least at 50% battery (if you can)
Enter download mode by holding the volume up button + plug the phone into the computer from a powered off state
Leave phone plugged in and in pc go to settings/control panel/device manager/ports right click on lgemobile serial port and click properties then select the port settings tab and click advanced then change com port number to 41 and click ok
Unplug phone
Run LGFlashTool.exe as administrator
If you get a DBMS WINDOWS leave it on ?? ?? (Korea Factory) and click ok
Check select manual mode
For DLL click [...] and select the dll from the package you extracted (LGD851_20140611_LGFLASHv160.dll)
If you are getting a model check error download/extract and try this generic LG dll
For S/W click [ADD] and select the tot from the package you extracted (LGD851AT-01-V10c-310-260-JUN-20-2014+0.tot)
Make sure in action mode BOARD DL is selected and in connection mode USB is selected
Click [OK]
Click the [yellow arrow] that is pointing to the right
Wait until Port 1 (COM41) says READY! (could take a couple minutes give it time)
Plug your phone back in and it will start flashing automatically DO NOT UNPLUG THE PHONE
After its done sending the firmware over your phone will reboot into mini os and you will see a blue screen with a big 2 wait until you see a big 3 then unplug the phone and close the lgflashtool program. Your phone might automatically reboot on 3 but it hasn't for me If it doesn't just pull the battery put it back in then power up. After one of the updates this step may be different then described. If you have problems just ask and myself or somebody else will be able to help.
Everything that lives inside the KDZ files except system HERE
(If you want the system.img download the twrp files)

Software version D85130g
Android 6.0.1
July 5, 2017
2G/3G data roaming fix
Google monthly security patch
LG app fix
software stability and software improvements
Software version: D85130e
Android 6.0.1
August 8, 2016
Google security enhancements
Software stability
Software version: D85130d
Android version 6.0
May 2, 2016
Android Marshmallow
Wi-Fi Calling improvements
Software version: D85120g
Android version 5.0.1
October 5, 2015
Messaging security improvements (Stagefright)
Software version: D85120e
Android version 5.0.1
June 10, 2015
Android 5.0 Lollipop
Turns on VoLTE
Wi-Fi Calling 2.0
Software stability
Software version: D85120b
Android version 5.0.1
April 7, 2015
Android 5.0 Lollipop
Turns on VoLTE
Wi-Fi Calling 2.0
Software version: D85110r
Android version 4.4.2
December 2, 2014
Wi-Fi Calling enhancements
Security enhancements
Bluetooth connectivity improvements
Various bug fixes
Software version: D85110m
Android version 4.4.2
September 10, 2014
Wi-Fi Calling enhancements
Security enhancements
Various bug fixes
Software version: D85110c
Android version 4.4.2
July 16, 2014
Original software version

So use this method to flash back to stock?

RMXO said:
So use this method to flash back to stock?
Click to expand...
Click to collapse
Correct it also gives developers a chance to start making stock roms even though we don't have root or a recovery yet.

What is a KDZ file?

wirelessrevolution said:
What is a KDZ file?
Click to expand...
Click to collapse
It holds all of the files and partitions for flashing back to stock.

Updated OP with Flash method!

ThePagel said:
Updated OP with Flash method!
Click to expand...
Click to collapse
thanks OP.

thanks for this OP.
now since TWRP was released for the t-mobile g3, soon enough this kdz package will be converted to a TWRP compatible flash package

TYVM, it worked like a charm.

Thanks for the guide ! Will definitely come in handy

Ok now I'm not sure if im reading this correctly but it says in OP to Download one of the KDZ files from the beginning of the post and extract it in the Flashtool folder from his thread, now when i got o his thread I only see the G2 files not the G3? someone maybe point me to the one i need for the D851?
EDIT: never mind im an idioto! disregard

turilo said:
Ok now I'm not sure if im reading this correctly but it says in OP to Download one of the KDZ files from the beginning of the post and extract it in the Flashtool folder from his thread, now when i got o his thread I only see the G2 files not the G3? someone maybe point me to the one i need for the D851?
EDIT: never mind im an idioto! disregard
Click to expand...
Click to collapse
Ill move the credits to the bottom of the op so no one else can get confused

Mine times out at 2%
Any ideas??

Mikey said:
Mine times out at 2%
Any ideas??
Click to expand...
Click to collapse
what operating system are you on?

Great guide! Just what I was looking for. 2 questions though... Will this unroot your device? (I would presume untouched stock means that, but you know what happens when I presume. I make a pres of you and me). (I'm looking for a reliable to way to uproot, just in case I want to get an OTA). Also, could you link to the G3 drivers in the OP? This is gonna be my go to post if anyone asks me about it...
Sent from my Nexus 10 using XDA Premium 4 mobile app

ThePagel said:
what operating system are you on?
Click to expand...
Click to collapse
Win7 Ultimate 64-Bit

Mikey said:
Win7 Ultimate 64-Bit
Click to expand...
Click to collapse
Worked for me on 8.1 so it should work for you. Install Microsoft c++ runtime 2012 or 2013 then try again. Also make sure you have the proper drivers installed. Ill upload both runtime and drivers when i get home so if you cant find them check back around 6 or 7.
*Edit
Also make sure your running as administrator.

DefinityX said:
Great guide! Just what I was looking for. 2 questions though... Will this unroot your device? (I would presume untouched stock means that, but you know what happens when I presume. I make a pres of you and me). (I'm looking for a reliable to way to uproot, just in case I want to get an OTA). Also, could you link to the G3 drivers in the OP? This is gonna be my go to post if anyone asks me about it...
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks!
It will unroot you and it already saved my butt after I accidentaly formatted most of the partitions on the phone. I plan on uploading the unified lg drivers tonight along with c++ runtime. Im also going to hunt down a nice guide and link to it for flashing via the lg suite if this fails. The lg suite way is a pain in the a** but should work if this one fails.

Mikey said:
Win7 Ultimate 64-Bit
Click to expand...
Click to collapse
ThePagel said:
Worked for me on 8.1 so it should work for you. Install Microsoft c++ runtime 2012 or 2013 then try again. Also make sure you have the proper drivers installed. Ill upload both runtime and drivers when i get home so if you cant find them check back around 6 or 7.
*Edit
Also make sure your running as administrator.
Click to expand...
Click to collapse
If you need drivers for Windows (thanks @autoprime for having these handy!):
Everyone Else: http://downloads.codefi.re/autoprime...Ver_3.11.3.exe
Click to expand...
Click to collapse
UPDATE
1- I downloaded 2013 Runtime 2013 from here: http://www.microsoft.com/en-us/download/details.aspx?id=40784
2- Rebooted my PC
3- Followed the instructions in OP, performing the CSE flash.
4- Received a timeout error really quick but it started to flash.
5- Around 80% the phone went black and never booted to the LG screen, after it hit 100% I unplugged it, removed the battery and rebooted it.
Booting up it entered some mode for a split second and rebooted itself.
Once on homescreen, it rebooted itself one last time.
I'm UnRooted now
I guess i needed to install C++ Runtime
Thanks

how to fix The dead android bot with error when enter recovery?

hello
i have rooted the device using the "1 CLICK ROOT TOOL" and now i have the dead android bot with error when i enter recovery.
i have tried the "fastboot erase cache" command at fastboot mode but it did not help
is their a way to fix it?

Try pressing Volume + key and Power. Don't hold just press. It might take a few goes to get it right. I had the same problem. That means that the update you have downloaded (saved on your system) fails to install.

hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem

koby058 said:
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
Click to expand...
Click to collapse
Awh sorry, I thought you can't get into recovery.
Try sideloading the stock Firmware. Go to official ASUS website and download it from there. It's about 1 GB. On this website you can find instructions on how to do it. http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 Section 3.2)
After that you can download OTA updates and install them using method described here http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835, "Steps to Apply OTA manually".
OTA can be downloaded from there (look at the later posts for newer OTA) http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999
I had a very similar problem few days ago. That solved it. Had a similar problem a few days ago coz I messed up my build.prop

hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?

koby058 said:
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
Click to expand...
Click to collapse
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.

rlaw said:
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
Click to expand...
Click to collapse
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.

NiKiToS-04 said:
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
Click to expand...
Click to collapse
No worries, I've made the same mistake before. We've all been there, still learning new things about this phone after months of using it!

ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?

koby058 said:
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
Click to expand...
Click to collapse
The 2.20.40.58 OTA was bugged and pulled from release. Just flash the full stock 2.20.40.59 firmware available from ASUS site and stop modifying your phone if you want to remain trouble-free with OTA updates. Or if you choose to continue to root and tinker with your phone accept that some things might get broken.

[GUIDE] Official updates on a M2 tablet with root/changed recovery

Official updates for our M2 tablet,
although having installed another
recovery and root access, already.​
- Disclaimer
Well, whatever you do with this guide is all up to you and in your own responsibility. You
should have basic knowledge about ADB and flashing, which is explained in many other
threads here on our beloved XDA.
- Issue
When you used this guide (https://goo.gl/r04XjJ) or any other one to give your M2 tablet
another recovery and therefore root rights, you have now the problem, that EMUI will show
you new updates, but you are not able to install them, because of the missing stock recovery,
of course.
- Solution
So, you have to flash back the original stock recovery, getting the official update and then you
can flash back your TWRP recovery.
- Guide
1. You should start your EMUI update programme/app and start the download of your update.
When it is finished, it will ask you to reboot into recovery and install automatically. As you have
no stock recovery I strongly advise not to do so. Usually nothing happens, but there is one case
reported, where it somehow ****ed up the guy's tablet. I am not sure, if that story is true, but
well, I have warned you.
2. Just turn your tablet off after you have finished downloading the update (it will wait now in
the directory "HwOUC" on your tablet and it is called "update.zip" - just let it sleep there).
3. Start the tablet in the fastboot recovery mode, meaning plugging in the USB cable (connected
to the computer) and hold the buttons "power" and "volume down", immediately, until a white
screen appears, which is the fastboot recovery screen. It should tell you, it has the bootloader
unlocked, which is normal, because you did that earlier on with any of the other guides (see above).
4. Copy the downloaded stock recovery of your choice to your ADB directory. In my case this is
"c:\ADB", but this depends on your way of installation.
5. Now open up a command line in Windows (with Windows key + R) and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
6. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery stock-recovery.img
fastboot reboot
If you renamed the recovery file, then you have to consider that in the command, of course.
7. The device will reboot directly into the recovery, because it "sees" the update in the update
directory et voila ... you are getting your awaited update. Sometimes it will boot not into the EMUI
recovery directly, but then you hast have to start the tablet normally, open up the EMUI app and
download the update again and do the OTA update properly with the reboot it tells you to do,
when it is finished.
8. Okay, now you have received your update, but if you want to have back your TWRP, you just
have to turn off your tablet and boot into the fastboot recovery again (see 3.).
9. You have to copy your TWRP recovery to your ADB directory (in my case "twrp.img" in "c:\ADB").
10. Now open up a command line in Windows (with Windows key + R and type "cmd") and go to
your ADB directory, using commands like "cd .." and "cd adb".
11. When having arrived in the ADB directory, you have to enter these commands one after the other:
fastboot flash recovery twrp.img
fastboot reboot
12. The tablet will reboot and you are back to a working lovely updated M2 tablet.
- Root:
If you want to have root rights, I strongly recommend flashing Magisk within TWRP, because it is
just a nice and more modern approach to having root. It works very fine on my M2 10 tablet. The
link for the files and guide is here:
https://goo.gl/UXYk4d
It is very easy. You just flash Magisk 12 in TWRP and then install the Magisk Manager app from the
Play store.
- Files for M2-802L and M2-A01L:
https://ufile.io/0df492 (all four recoveries here)
https://files.fm/u/aajdmadr (all four recoveries here)
https://www.file-upload.net/download-12438839/HuaweiM2recoveries.rar.html (all four recoveries here)
Have fun with your updated tablet. ... and I am happy, if I could help you - any coffee appreciated.
...
..
.

+++ saved +++

Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.

what android version ?? M2-801L, thanks

Eagle-no1 said:
what android version ?? M2-801L, thanks
Click to expand...
Click to collapse
M2-A01L, not M2-801L. For all 8 models you find your ROMs here:
https://forum.xda-developers.com/me...om-8-0-models-stock-marshmallow-roms-t3535466
or
https://forum.xda-developers.com/me...-b207-android-6-0-marshmallow-emui-4-t3533572
or
https://forum.xda-developers.com/mediapad-m2/development/rom-stock-rooted-xposed-t3519031

xsycox said:
Additionally, I can offer you the updates B007 and B010 (most current one) for the
M2 10 LTE (M2-A01L), because I managed to save them/back them up. These are the
European versions of B007 and B010 with all language files, I believe.
So, who is having a M2-A01L and is still sitting on B006 or B007, might try a manual
update, which is as easy as pie. It is just one simple step.
Also, an update from B009 to B010 might be possible.
Of course, I cannot give any guarantee for Huawei's update files, which you will
understand, I guess.
Click to expand...
Click to collapse
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Sent from my htc_pmeuhl using XDA Labs

Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?

5m4r7ph0n36uru said:
I'd greatly appreciate it, if you could share. Got the problem that my A-01L got corrupted. The only official ROM I've been able to find has been B005 what is somewhat old. As it seems to be a pre-release version the tablet doesn't find any updates. Thus I'd like to try to upgrade to B007, or even B010 manually when I'm back home. Currently I'm on a weekend trip as friends of mine are going to marry tomorrow. Thus I'd be able to download them on Sunday evening if you'd provide them.
Regards
Click to expand...
Click to collapse
https://forum.xda-developers.com/me...om-official-manual-updates-m2-tablet-t3595211

zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.

zedoc said:
Tried Magisk but can't pass Safetinet test even with Magisk hide enable...
is it working for you?
Click to expand...
Click to collapse
xsycox said:
I have Magisk running on several devices, including the M2-A01L, but I must admit,
I never got the Safetynet passed, even with Magisk hide enabled.
I just use it as systemless root and with systemless Xposed, which is great.
Click to expand...
Click to collapse
After enabling magisk hide, you have to reboot your device. Got the 801L working with that and safetynet passes.

Noob Question on recovery files
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!

myst771 said:
Hi, and thanks for a incredible well detailed guide for updating. Came here because I haven't found any good recovery files for the wifi model. I've been trying (unsuccessfully may I add...) to install TWRP and magisk. So, my question is: can the recovery files for the LTE model be used on the wifi model? (M2-A01w). Thanks for your help!
Click to expand...
Click to collapse
Sorry, I have been on vacation.
To be honest, I am not sure, if the recovery for M2-A01L works on M2-A01w, too, but you can just try it.
I think, there should not be that big a problem, because the recovery has nothing to do with Wi-Fi or LTE, at all. It is just important, that partition tables and drives are accessible the same way and well, I really think, there is not much difference in between the M2 10 models.
From M2 8 to 10 there is a difference, of course. That is why I uploaded both recoveries (for 802L and A01L).
Just use that guide (https://forum.xda-developers.com/mediapad-m2/how-to/guide-unlock-bootlader-twrp-root-huawei-t3322340) without the SuperSU flashing and my recoveries in this guide.

Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.

Shocker580 said:
Hi guys,
I need help, I have a M2 10 LTE previously modded with TWRP for root and I've just followed this guide to update from 007 to 010 version.
So I've flashed the stock-recovery, rebooted the tablet, requested the firmware update (I don't know if I got any error during the process) and the tablet has rebooted. Now it's stuck on HUAWEI logo..
I use this tablet for work so I really need to recover it asap.
Please help.
Click to expand...
Click to collapse
Could upload the B010 fullstock ROM/firmware. Thus you could reset the device to the latest stock ROM using the /dload method and gain a factory rested Huawei, as if out of the box. Just quote me if you'd want me to upload and I'll share the link asap. Took that way myself as soon as I found the full stock ROM.
Sent from my htc_ocnuhl using XDA Labs

thanx

Dear xsycox
I have an issue where I updated my W version tablet to L version accidentally and I am having issue getting it back..
I am currently trying to get some help in this thread: https://forum.xda-developers.com/me...-m2-installed-wrong-update-zip-t3563105/page2
Can you please help me out? do you have any idea what ican do to get back to W version?
Thanks!

BND-L24 System update failed

I'm not the kind of person to ask for help if the answer to my problem might be out there already. I've followed relevant threads. I've searched XDA and googled. I've tried some things. I'm stuck.
I have an unlocked bootloader and FRP. When I go into Settings, OEM unlocking is greyed out. (Yes, I can use the phone.)
I do not have TWRP (anymore). I flashed stock recoveries.
I'm on build B101 and System Update is prompting my to update to B130. I can download it and, when prompted, reboot into recovery to update automatically.
I get to 100% and get the following error:
Software install failed!
Failed to check the update files.
Please download the package again.
Reboot system now
(See screenshot attached)
Now that it's available in Firmware Finder, I attempted to load B150 as well. Same thing.
I tried relocking bootloader, but it immediately prompts me to factory reset. After doing that, I get to reboot into recovery by default, other recovery by pressing the buttons, or fastboot via my PC.
Now, since we STILL don't have full firmware (supposed to have gotten it Friday, right?) I'm reluctant to use the images from here, especially if I'm not sure that would actually fix my issue.
What is going on with my software update? How do I fix this?
Did they actually release the BND-L24 firmware and no one noted it here?
Help, please!
Thanks.

johncro13 said:
I'm not the kind of person to ask for help if the answer to my problem might be out there already. I've followed relevant threads. I've searched XDA and googled. I've tried some things. I'm stuck.
I have an unlocked bootloader and FRP. When I go into Settings, OEM unlocking is greyed out. (Yes, I can use the phone.)
I do not have TWRP (anymore). I flashed stock recoveries.
I'm on build B101 and System Update is prompting my to update to B130. I can download it and, when prompted, reboot into recovery to update automatically.
I get to 100% and get the following error:
Software install failed!
Failed to check the update files.
Please download the package again.
Reboot system now
(See screenshot attached)
Now that it's available in Firmware Finder, I attempted to load B150 as well. Same thing.
I tried relocking bootloader, but it immediately prompts me to factory reset. After doing that, I get to reboot into recovery by default, other recovery by pressing the buttons, or fastboot via my PC.
Now, since we STILL don't have full firmware (supposed to have gotten it Friday, right?) I'm reluctant to use the images from here, especially if I'm not sure that would actually fix my issue.
What is going on with my software update? How do I fix this?
Did they actually release the BND-L24 firmware and no one noted it here?
Help, please!
Thanks.
Click to expand...
Click to collapse
I'm not certain why that happens, But I have a guess.
On each update that I have looked at, the recovery gets and update too. So different signatures and such.
Maybe the "stock" recovery you have re-flashed, is not correct version for your installed and update rom.
I cannot confirm this as I am missing the update app.
If you could help me with my missing files , I could help you with your update problem.
You could help me by pulling a list of packages installed so I can see what apps I have missing, and hopefully get them back (stock only, preferably done after a fresh factory reset.)
Directions for this on this thread.

See attached.

johncro13 said:
See attached.
Click to expand...
Click to collapse
thank you that helps.
I see I am missing an entire folder.
/data/hw_init
Could you see if it is accessible .
Code:
mkdir %userprofile%\Desktop\hw_init
adb pull /data/hw_init %userprofile%\Desktop\hw_init
I think it is not permitted though.

Uploaded. See referenced thread. I hope it helps!

johncro13 said:
Uploaded. See referenced thread. I hope it helps!
Click to expand...
Click to collapse
I will see what I can do with that. And hopefully can get past any file verification. And if I figure that out it should help you too.
Or , with my luck, the moment I figure it out , the stock firmware will come out.
I pushed the hw_init folder to /data while in twrp, then put stock recovery back(the version I expect should be correct) and I got same update failed error, as the OP.
That tells me maybe is probably some other reason , besides the version of stock recovery is causing this trouble.

Not sure if there is confirmation of successful update while bootloader is unlocked or not. Too late for me to try tonight, but next I will re-lock bootloader and try again.
My last (really current) phone needed to be re-locked in order to take updates.
**UPDATE**
re-locking bootloader did not help any at all. I still have error failed to check file, please download again.

On the manual update to oreo thread, they are using a "stock-ish" recovery named "no-check"
I am thinking I might flash that recovery to try and force this update to install.

BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?

johncro13 said:
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
Click to expand...
Click to collapse
tried it earlier today. Same error. will not finish update

johncro13 said:
BND-RECOVERY-NoCheck.img? Is that region-specific? Will it work with the BND-L24?
Click to expand...
Click to collapse
I have ordered a second 7x. I plan to pull the hw_init folder , and the remainder of /data that might be missing from this device , because of a result of formating it in twrp. I plan to restore that as an image, in hopes of getting updater to complete properly. And if that works, you will be able to use my backup and update your phone too.
If not , well , doesn't hurt to try.
I'm comparing the images pulled from my device and the images available for the Indian "return to stock thread. And I see the problem with the USA L24 version.
The cust.img for usa has no app folder.
It did not make sense to me before why there was apps only installed in /data. Because /data should be able to be fully wiped and your system will recreate the file structure. But The apps should have been on one of the images.

My second phone arrived today. I pulled the hw_init folder from it.
did a diff comparison on the updater app from the new phone and and the one that I had to apply patches to , to bring it up from b101 to b140. The result was 100% same.
and three more apps where in the hw_init folder as well. (bloat apps really)
now the bad news.
My original phone (the one that I had formatted /data on). Now has the same /data/hw_init folder as the brand new device. But always shows no update available.--It showed update once, the first time checked, install failed , now shows nothing available.
And the new phone does show an update available (B150) , but fails to install. Then after the failed install, now it shows no update available.

That's insane.
So... in summary, neither will update? Neither the original nor the unaltered brand-new device?

If anyone else has had this issue but has since resolved it, would you mind letting us know how? @mrmazak is working on it and I've also been told by the FUT team that I should expect some kind of communication from "Oscar Felix."
(If you've searched the forums for other Honor or Huawei devices, you probably already know that there is some speculation about whether or not Oscar Felix is a real person.)

I have the same problem but I'm stuck on update b140 and I can't even get the face unlock feature update. I was rooted with twrp recovery but now I have reinstalled the stock recovery and removed root

Sonny1732 said:
I have the same problem but I'm stuck on update b140 and I can't even get the face unlock feature update. I was rooted with twrp recovery but now I have reinstalled the stock recovery and removed root
Click to expand...
Click to collapse
Did you get the Oreo update today?

No I didn't, did you find out what can we do about this?

Is it a way I can update my phone manually

I'm watching this thread , myself. That might be the key.

Hopefully something comes up soon or is there a rom I can get if I reroot my phone?

Question [Oneplus9 Pro][Oxygen OS] All stock updates fail after reboot

As the title states, I'm having problems updating my One+ 9 Pro. It's all stock, no root, no custom ROM. My current build number is 11.2.10.10.LE15BA and I get a notification to update to C.47 (build LE2123_11.C.47_1470_202203102117). Downloading and installation works well, but after the needed reboot I get the message that the update failed. No further info about why and when exactly.
What I tried to far in addition to update via system settings:
- local update to C.47, same behaviour => installing works and fails after reboot
- local update to a beta build => installing works and fails after reboot
- updating to C.64 with oxygen installer => instantly fails in the settings
I don't want to root or unlock the bootloader. Any tip is highly appreciated.

Latest OTA for le2123 is in the screenshot, are you updating using oxygen updater?

Are you out of file space on your phone?

@Appreciative I'm not out of space. 80Gigs are free.
@AndyC76 the system settings want to update to C.47, oxygen updater to C.64. The C.64 Full ROM shows an Error when I try to do a local update.

@nurbs999 what hardware version is your phone? You'll find this in the box.
I am puzzled, the screen shot i posted earlier shows c64 is the current version of oos A12 that has been pushed ota to my le2123.
AHH so I read from your message you're using oxygen updater attempt a local update c64 update
Before we go any further, which working version is currently installed on your phone, we know it's not c47, as you got an OTA update asking you to upgrade
Very strange, something got confused

I'm sorry but what do you mean by hardware version?
The current version on my phone is 11.2.10.10.LE15BA, Android 11 based

nurbs999 said:
I'm sorry but what do you mean by hardware version?
The current version on my phone is 11.2.10.10.LE15BA, Android 11 based
Click to expand...
Click to collapse
There is an OOS 12 update before the Oxygen Updater app update. Use the OOS system update and not oxygen updater app

It seems like mine and @nurbs999 devices are exibiting the same issue. To be clear, as I understand OP s/he like me have attempted to install the OTA update first as presented by the stock android system upgrade process but after install and reboot the OS reports that the upgrade failed. After this, trials using local update / oxygen updater has been tried but all failing as described in OP.

nurbs999 said:
As the title states, I'm having problems updating my One+ 9 Pro. It's all stock, no root, no custom ROM. My current build number is 11.2.10.10.LE15BA and I get a notification to update to C.47 (build LE2123_11.C.47_1470_202203102117). Downloading and installation works well, but after the needed reboot I get the message that the update failed. No further info about why and when exactly.
What I tried to far in addition to update via system settings:
- local update to C.47, same behaviour => installing works and fails after reboot
- local update to a beta build => installing works and fails after reboot
- updating to C.64 with oxygen installer => instantly fails in the settings
I don't want to root or unlock the bootloader. Any tip is highly appreciated.
Click to expand...
Click to collapse
just let the system do what it has to do.
Update thru OTA System. Even if it fails once, do the updates again until you reach lastest official OTAs

fiskhest said:
It seems like mine and @nurbs999 devices are exibiting the same issue. To be clear, as I understand OP s/he like me have attempted to install the OTA update first as presented by the stock android system upgrade process but after install and reboot the OS reports that the upgrade failed. After this, trials using local update / oxygen updater has been tried but all failing as described in OP.
Click to expand...
Click to collapse
Exactly.
@Steve0007 The problem is that the OTA update always fails. I tried it 6 times without success. As a last resort I tried the update thru oxygen updater, also without success.
To be clear: the running OS version doesn't change between updates.

nurbs999 said:
Exactly.
@Steve0007 The problem is that the OTA update always fails. I tried it 6 times without success. As a last resort I tried the update thru oxygen updater, also without success.
To be clear: the running OS version doesn't change between updates.
Click to expand...
Click to collapse
And for me, I've probably tried the OTA update 20 times over a span of six months before I did a complete reflash with latest msmtools, hoping that would solve my issue. After reflash, I did five more tries before I started looking for alternative solutions. Are we supposed to just bash our heads on the failing OTA update until it (hopefully) succeeds?

nurbs999 said:
As the title states, I'm having problems updating my One+ 9 Pro. It's all stock, no root, no custom ROM. My current build number is 11.2.10.10.LE15BA and I get a notification to update to C.47 (build LE2123_11.C.47_1470_202203102117). Downloading and installation works well, but after the needed reboot I get the message that the update failed. No further info about why and when exactly.
What I tried to far in addition to update via system settings:
- local update to C.47, same behaviour => installing works and fails after reboot
- local update to a beta build => installing works and fails after reboot
- updating to C.64 with oxygen installer => instantly fails in the settings
I don't want to root or unlock the bootloader. Any tip is highly appreciated.
Click to expand...
Click to collapse
I have the same problem
Unlock bootloader, flash rom via recovery (you will not be able to relock it after updating)

nurbs999 said:
Exactly.
@Steve0007 The problem is that the OTA update always fails. I tried it 6 times without success. As a last resort I tried the update thru oxygen updater, also without success.
To be clear: the running OS version doesn't change between updates.
Click to expand...
Click to collapse
Are you able to reflash the latest Android 11 (10.10 version)?. This ways you would make sure you have the latest on both slots. From there just OTA system to get the latest

@Steve0007 I just tried that. I downloaded the image from here
The OTA update still fails. Same behaviour as before.

nurbs999 said:
I'm sorry but what do you mean by hardware version?
The current version on my phone is 11.2.10.10.LE15BA, Android 11 based
Click to expand...
Click to collapse
What you have furnished is the OOS version. What we are asking for is the initial hardware version viz. whether China, India, Global etc. As the user you are replying to says, it will be on the box the phone came in.
nurbs999 said:
I'm not out of space. 80Gigs are free.
Click to expand...
Click to collapse
That is for the data partition. What is the space left in the system partition since the OS will install to that?

Hm, this is the only label I can find.

nurbs999 said:
Hm, this is the only label I can find.
View attachment 5726527
Click to expand...
Click to collapse
There it is, it is a LE2123. It is a EU model and it seems to be flashed with the EU version of OOS as stated by you. Now let others more knowledgeable than me reply to you.

I've posted here for you,
One option you have is to use the MSM tool and go back to full and working stock.
Post in thread 'OP9Pro - Repository of MSM Unbrick Tools (TMO, EU, GLO, IN)' https://forum.xda-developers.com/t/...ick-tools-tmo-eu-glo-in.4272549/post-87526839

@AndyC76 thank you.

Well.. That is the one I've reflashed and tried with on my end, with no change in behavior. I'll have to wait a couple of days until I am able to reflash again. Hoping you have better results than me @nurbs999 !