Related
Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.
judask24 said:
Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.
Click to expand...
Click to collapse
No luck here...there is post over on Android Forums that Verizon users are getting the 4.4.4 OTA update but nobody has posted the captured zip file yet.
Captured Verizon CDMA Moto G 4.4.4 Update Zip
Here's a link to download the new Verizon Moto G 4.4.4 CDMA version of Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
http://goo.gl/Vuw0P9
or
http://www.mediafire.com/download/3q7paotltq951id/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.
netkeys said:
Here's a link to download the new Verizon Moto G 4.4.4 CDMA version of Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
http://goo.gl/Vuw0P9
or
http://www.mediafire.com/download/3q7paotltq951id/Blur_Version.173.44.20.falcon_cdma.Verizon.en.US.zip
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.
Click to expand...
Click to collapse
That 173.44.20.falcon_cdma.Verizon.en.US is the 4.4.2 Kit Kat currently installed on the G's. I am looking for the newer one. 210.12.41.falcon_cdma.Verizon.en.US which is the 4.4.4 update.
judask24 said:
That 173.44.20.falcon_cdma.Verizon.en.US is the 4.4.2 Kit Kat currently installed on the G's. I am looking for the newer one. 210.12.41.falcon_cdma.Verizon.en.US which is the 4.4.4 update.
Click to expand...
Click to collapse
This is the file downloaded on 7-21-2014. Attached is a screen shot of the updater.
netkeys said:
I have not installed it yet as I'm running a Boost Mobile Moto G flashed to Verizon Wireless running on Page Plus that's rooted. I'm waiting to see if someone has completed the update without problems before I try.
If someone attempts the update for a Page Plus flashed Moto G let me know how it goes.
Click to expand...
Click to collapse
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.
randomchaos26 said:
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.
Click to expand...
Click to collapse
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when I check for system update in settings, still says "software is up to date". Any suggestions?
chinocritter said:
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when when I check for system update in settings, still says "software is up to date". Any suggestions?
Click to expand...
Click to collapse
It was pulled from the /cache folder. If you put in /storage/sdcard0 you may also need to rename to update.zip
randomchaos26 said:
I have a Page Plus flashed Moto G, it's only a backup phone, so I guess I'll be the guinea pig today. I'll let you know if it catches on fire, burns down the neighborhood, kills small fluffy animals, etc.
Click to expand...
Click to collapse
Yes please do. My wife's phone is wanting to update since Sunday night.
Seems to work just fine on Page Plus after the update, root works, and nothing has caught on fire yet. Edit: Tested data and calling, both seem to work fine.
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
If you want to get rid of the ugly "WARNING BOOTLOADER UNLOCKED IT WILL KILL YOUR FAMILY" boot logo, flash the logo.bin (fastboot flash logo logo.bin) in the attached zip file. It is just a simple hex edit of the logo address in the file header. I've included the original as logo.bin.bak so you can verify it against the original, and compare the two files if you want to see how it's done.
chinocritter said:
I am also on cdma Moto G (stock/no root) flashed to Page Plus...I downloaded the captured update zip and put in root of SD but is not detected when I check for system update in settings, still says "software is up to date". Any suggestions?
Click to expand...
Click to collapse
I think you can select "apply update from sdcard" in the recovery mode. No?
EDIT: You flashed to PagePlus. I missed that part. Sorry about that.
I was on a AOSP based rom.
So I flashed back to stock via CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.
Booted up once to make sure the the flash went well.
Flashed CWM via bootloader. Tried TWRP first, did not work with the update.zip.
Renamed the zip above to update.zip and flashed via cwm. Worked fine. (yes the zip is 4.4.4)
Before rebooting, went ahead and flashed supersu.zip.
Then rebooted back to bootloader and flashed my preferred recovery, TWRP.
All seems well. This is on PagePlus.
Bout time we get 4.4.4. I'm also using Boost Moto G to Verizon/Page Plus. I will update when I have free time. Thanks for the info, guys.
XDA Dark said:
Bout time we get 4.4.4. I'm also using Boost Moto G to Verizon/Page Plus. I will update when I have free time. Thanks for the info, guys.
Click to expand...
Click to collapse
It sounds like the 4.4.4 update is working fine...the only issue is that there doesn't seem to be a full stock 4.4.4 flash available (like we have for 4.4.2), and from what I can tell from posts (haven't tried this myself), you cannot reflash the full stock 4.4.2 after the 4.4.4 update since the bootloader and/or partitions have changed. There may be some workarounds, but those seem to be for other models or geographies as best I can tell. Once we have the full 4.4.4 flash, then at least you can always revert to that, but it doesn't appear to be released yet.
I've been keeping an eye out for the update OTA. I guess I'd rather just go down that path officially since my phones not rooted and had stock locked bootloader. Just wish it would hurry up and be pushed to my device.
Install zip via stock recovery
judask24 said:
Verizon announced yesterday they have released the OTA update for 4.4.4 for the Verizon Moto G, 210.12.41.falcon_cdma.Verizon.en.US. I was wondering if anyone has captured the update yet as mine still says Software is up to date. Even tried the Framework Trick with no luck.
Click to expand...
Click to collapse
Ota file works it is 4.4.4 update for Verizon Mota G. Download zip to phone power off. Hold down power and volume down for a few seconds release. Once at menu go to recovery. Once in recovery android with exclamation with no options will appear. Press and hold Volume up for 10 seconds continue to hold while now also pressing power button for 3 seconds release. Your in recovery mode select update from zip and proceed. Happy camping with new dialer update camera shots in low lightness and other fixes and features!
randomchaos26 said:
Seems to work just fine on Page Plus after the update, root works, and nothing has caught on fire yet. Edit: Tested data and calling, both seem to work fine.
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
If you want to get rid of the ugly "WARNING BOOTLOADER UNLOCKED IT WILL KILL YOUR FAMILY" boot logo, flash the logo.bin (fastboot flash logo logo.bin) in the attached zip file. It is just a simple hex edit of the logo address in the file header. I've included the original as logo.bin.bak so you can verify it against the original, and compare the two files if you want to see how it's done.
Click to expand...
Click to collapse
Followed these directions and worked without any problem.
The fixed the external USB mounting problem that was in 4.4.2
I updated today on Boost Mobile Moto G flashed to Page Plus with no issues... Success
Sent from my XT1028 using XDA Free mobile app
randomchaos26 said:
Steps to update (this assumes your bootloader is already unlocked and you have cwm recovery installed):
Save the update zip and the cwm flashable supersu zip to your phone.
Boot into cwm recovery and do a backup (assuming you have space on /media/data for a backup.)
Reboot to bootloader.
Restore *just* your system partition to stock with fastboot (using: CFC-fastboot_falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip)
Boot into cwm again, apply the update zip, then immediately apply the supersu zip.
Boot up normally and let it do its update stuff, then go into titanium backup and kill off any of the verizon bloatware that you don't want.
Click to expand...
Click to collapse
Thanks for the instruction. Questions:
(1) My flashed page plus moto-g is on rooted stock rom (with unlocked bootloader of course). Do I still need to restore the system partition back to stock?
(2) What is "CFC-fastboot"? Do you mean
fastboot falcon_verizon_user_4.4.2_KXB20.9-1.10-1.20_22_release-keys.xml.zip
(i.e. no underscore between fastboot and falcon) ?
Thanks!
it's available on OTA now yay
Stuck on BrightHouse Nougat? NOT ANYMORE!!!
For the RETAIL UNLOCKED USA VARIANT RS988 ONLY!!!
THIS IS NOT A UNIVERSAL LG DEVICE CURE ALL!!!!
-> Without autoprime None of this would be possible!
autoprime said:
{
"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"
}
LG G5 ALL-IN-ONE THREAD
y u quote OP?
Follow me on twitter for future updates on LG-related things - twitter.com/@utoprime
Find this thread helpful? Hit the Thanks button!
Feeling extra generous? Feel free to contribute to my LG G5 fund...
click my name at the top of any post and hit donate or click here.
#TEAMCODEFIRE
Click to expand...
Click to collapse
autoprime said:
UPPERCUT allows LGUP to instantly work with a ton of different LG models. No more hunting around for specific model files or being stuck without your model being detected. Simply install LGUP. Double-click the UPPERCUT.exe and LGUP will open and detect your device.
Information:
What's LGUP? LGUP is LG's internal Windows-only tool for flashing LG devices with stock firmware in KDZ, DZ and TOT formats. Previously extra installers and unique settings were needed for each model. Many less popular devices didn't have the files needed to work with their device.Well with UPPERCUT just double-click the EXE and LGUP will open and recognize your device.
Requirements:
1. Windows computer or virtual machine.
2. LG's Windows USB drivers installed and working.
3. LGUP 1.14 installed
4. LG device must show in Windows Device Manager under "Ports" as a LG Serial COM port.
5. KDZ, DZ or TOT file for your device.
How-to:
1. With all requirements above met... download and unzip UPPERCUT.
2. Double-click the UPPERCUT.exe every time you want to use LGUP. It's that simple.
Downloads:
UPPERCUT | LGUP | LG G5 Files | LG USB Drivers
When LGUP works for your model please post it in the thread! List:
your model (H850, D852, F600L etc..)
the software build you were on before flashing in LGUP (10A, 22C, 30B etc..)
the KDZ or TOT name you flashed using LGUP (H91810i_00_1202.kdz etc..)
Versions:
1.0.0.0 - Supports LG devices using a MSM 8996/8994/8992/8976/8952/8939/8937/8916/8909/8226 chipset. Street Fighter 2 SFX.
Let me know which combos do/dont work for you... UPPERCUT version, LGUP version, Current phone software version and KDZ/TOT software version and if the KDZ/TOT is custom or official.
Devices Supported:
G4, G5, G6, V10, V20, Flex 2, G Pad X, K10 and many more!
FAQ:
Q: Why isn't this working?
A: UPPERCUT requires LGUP 1.14 (not 1.11) installed in its default location prior to running.
Q: Why isn't anything happening when I press the boxing glove picture in this thread?
A: Really? ...
Q: What is this?
A: This is the simplest way to make LGUP work with your LG device.
Q: Refurbish option in LGUP doesn't work, what now?
A: Boot into stock recovery after the flash finishes and perform a factory reset. This is the same outcome as if Refurbish was selected.
Q: Why does this TOT file keep failing?
A: In most cases you're either trying to downgrade and it has been blocked by your phones download mode (not anti-rollback fuse.. that is different)... OR you are trying to use a custom-made TOT file which is not official or signed by LG. Flash an official KDZ instead. Do not ask for KDZs in this thread.. not the place.
Q: Where can I find a KDZ for my phone?
A: This is not a KDZ thread. Take the KDZ questions elsewhere.
Q: Why is my anti-virus scanner flagging this?
A: It's a false positive. Scanners like Kaspersky know better and don't flag the app but some others do. See post #59 for more info.
Q: Why is my device's model not detected in LGUP?
A: Make sure your devices chipset is supported by UPPERCUT. All models and software variants may not be supported even though chipset is listed.
If using a confirmed working device with UPPERCUT but your device is still not detected in LGUP you may have a "corrupted" misc partition...
as a last resort it has been confirmed in post #70 that wiping misc then booting into download mode allows the device to be detected with UPPERCUT + LGUP 1.14. This may not always work. And without root you cannot do this.
For more G5 info see my All-in-One Thread HERE
Follow me on twitter for future updates on LG-related things - twitter.com/@utoprime
Find this thread helpful? Hit the Thanks button!
Feeling extra generous? Click my name at the top of any post and hit donate or click here.
#TEAMCODEFIRE
this post looks best in desktop view using 2015 dark theme
Click to expand...
Click to collapse
Thank These Threads Above ^^^
Download ->
RS988 Build 11c TWRP Flashable Complete
RS988 Build 11c KDZ
UPPERCUT
Procedure ->
Flash Build 11c with TWRP -> Boot into force reboot loop.
Pull the battery and boot to Download Mode
Use UPPERCUT to REFURBISH Build 11c back onto your device with the Build 11c KDZ
SUCCESS!!!
Want Nougat for US back?
Just OTA back to Nougat for US
XDA:DevDB Information
Official RS988 USA Retail Unlocked BrightHouse Fix / Fully Functional Stock Downgrade, ROM for the LG G5
Contributors
CIGBURN, autoprime
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.1.x
ROM Firmware Required: ANY Firmware Capable for RS988 Retail Unlocked Only
Based On: STOCK
Version Information
Status: Stable
Current Stable Version: FINAL
Stable Release Date: 2017-10-29
Created 2017-10-30
Last Updated 2017-12-22
Has anyone done this and can confirm working? I want to buy LG G5 RS988 but I need root!!
CIGBURN said:
Stuck on BrightHouse Nougat? NOT ANYMORE!!!
For the RETAIL UNLOCKED USA VARIANT RS988 ONLY!!!
THIS IS NOT A UNIVERSAL LG DEVICE CURE ALL!!!!
-> Without autoprime None of this would be possible!
Thank These Threads Above ^^^
Download ->
RS988 Build 11c TWRP Flashable Complete
RS988 Build 11c KDZ
UPPERCUT
Procedure ->
Flash Build 11c with TWRP -> Boot into force reboot loop.
Pull the battery and boot to Download Mode
Use UPPERCUT to REFURBISH Build 11c back onto your device with the Build 11c KDZ
SUCCESS!!!
Want Nougat for US back?
Just OTA back to Nougat for US
XDA:DevDB Information
Official RS988 USA Retail Unlocked BrightHouse Fix / Fully Fictional Stock Downgrade, ROM for the LG G5
Contributors
CIGBURN, autoprime
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.1.x
ROM Firmware Required: ANY Firmware Capable for RS988 Retail Unlocked Only
Based On: STOCK
Version Information
Status: Stable
Current Stable Version: FINAL
Stable Release Date: 2017-10-29
Created 2017-10-30
Last Updated 2017-11-01
Click to expand...
Click to collapse
I did by accident Flash the 10h firmware and was stuck on brightpoint I can confirm that this method does work thank you
I followed all the steps, but I keep running into the same issue:
Using LGUP to flash the 11c kdz file, LGUP gets stuck at %10 showing the error report: "Error: 0x2BC, Invalid command response code = 0x80000121".
After that, my phone would only boot to Download Mode, so I had to use LGUP to flash a (Brightpoint) 10h kdz file. (LGUP had no issue with the 10h kdz file.)
Yes, I am using LGUP Store Version 1.14 and the DLL Version is 1.0.28.9
What am I doing wrong? I need to get rid of this Brightpoint issue in order to unlock the bootloader!
Wait, do you mean "Brighthouse" or "Brightpoint"?????????
TheTechHobbyist said:
I followed all the steps, but I keep running into the same issue:
Using LGUP to flash the 11c kdz file, LGUP gets stuck at %10 showing the error report: "Error: 0x2BC, Invalid command response code = 0x80000121".
After that, my phone would only boot to Download Mode, so I had to use LGUP to flash a (Brightpoint) 10h kdz file. (LGUP had no issue with the 10h kdz file.)
Yes, I am using LGUP Store Version 1.14 and the DLL Version is 1.0.28.9
What am I doing wrong? I need to get rid of this Brightpoint issue in order to unlock the bootloader!
Wait, do you mean "Brighthouse" or "Brightpoint"?????????
Click to expand...
Click to collapse
Never mind. I just realized this fix is for phones that were built for the open market and switched to brightpoint by accident. My phone (probably) came with Brightpoint. (I bought it used.)
Awkydee said:
Has anyone done this and can confirm working? I want to buy LG G5 RS988 but I need root!!
Click to expand...
Click to collapse
This is a fix for those who accidentally flashed bright house. I can 100% confirm that this works it even allows you to official ota back to nougat.
TheTechHobbyist said:
I followed all the steps, but I keep running into the same issue:
Using LGUP to flash the 11c kdz file, LGUP gets stuck at %10 showing the error report: "Error: 0x2BC, Invalid command response code = 0x80000121".
After that, my phone would only boot to Download Mode, so I had to use LGUP to flash a (Brightpoint) 10h kdz file. (LGUP had no issue with the 10h kdz file.)
Yes, I am using LGUP Store Version 1.14 and the DLL Version is 1.0.28.9
What am I doing wrong? I need to get rid of this Brightpoint issue in order to unlock the bootloader!
Wait, do you mean "Brighthouse" or "Brightpoint"?????????
Click to expand...
Click to collapse
You have to use twrp to flash the correct un-modified stock in the instructions and that will tell download mode that the usa fingerprint is on the phone and will allow you to use the refurbish option. You have to flash stock in twrp first before using LG UP. Please re-read the instructions in the OP, thanks!
i flashed the 11c full package using TWRP then refurbished the 11c KDZ using LGUP and UPPERCUT and took OTA to 11d after installation the phone required a PIN to power on the device and i entered my pin and it says wrong 29/30 left
BahaEzawi said:
i flashed the 11c full package using TWRP then refurbished the 11c KDZ using LGUP and UPPERCUT and took OTA to 11d after installation the phone required a PIN to power on the device and i entered my pin and it says wrong 29/30 left
Click to expand...
Click to collapse
This device setups with /data partition encryption. Do a factory reset with stock recovery to fix this.
After carrying out the process, i can not enter the bootloader with:
adb reboot bootloader
then it restarts itself.
How can I access the bootloader?
darkalexpp said:
After carrying out the process, i can not enter the bootloader with:
adb reboot bootloader
then it restarts itself.
How can I access the bootloader?
Click to expand...
Click to collapse
Are you back on Marshmallow? If so then you can't reboot into bootloader anymore.
I can confirm that It is working, I've first flashed the zipfile,
but then stayed in twrp to try and keep twrp as recovery in a cheeky way, by using adb and using the dd command I've overwritten twrp again to it's rightful partition,
pulling the battery afterwards, and reattempting to go into twrp, however it failed, after the recovery menu buttons (yes>yes) some red text appeared at the left top corner about MISMATCH, figures, 11c doesn't recognize the unlock..
I then returned to following the instructions, letting the phone boot loop (when getting into the encrypting you're data and the wallpaper),
Got into download mode, flashed 11c (I did have some wierd message about 'partitions have changed (system, backup gpt, and more..), would you like to continue?' Yes, I don't care, It's a kdz, I trust it..
Phone successfully flashed the kdz, and booted, although I had my heart drop, since in the past it happened to me and I couldn't fix it:
A few seconds (1 to 10) after boot finishes and setup wizard comes up, the device randomly reboots, without reason, and does so on all subsequent boots,
with the kdz returning the og stock recovery, I then opted to factory reset, after that boot was stable, and didn't restart, gone straight to checking updates, and 11d came up
Hope this helps anyone, I was stuck on 10h Brightpoint (rooted&magisk&xposed&twrp) for 2 years, no tethering and weird bugs, now on my path to nougat again, to have all my rooted&magisk&xposed&twrp back with security and bug fixes
Will update here when finished, PM me If I DONT (I hate when people don't update)
Edit #1: When 11d boots with bootloader unlocked there's 'your device cannot be checked for corruption' in a different way then 10h had
And, after the update to 11d, first boot failed because it requested my encryption unlock key, factory reset again, fixed it, boot is stable
11d is Android M 6.0.1
Edit #2: 11d has update to 21a, downloading now...
Edit #3: haven't updated yet, confirmed - 'adb reboot bootloader' getis into fastboot, flashing twrp worked, I'm going to skip the OTE update, and just flash the ZIP file (AFTER yet another wipe, and double check that 11d download has been canceled [someone was stuck because he tried to both flash while fota already downloaded])
Edit #4: Flashing 21a worked, but this time, I deleted "recovery-from-boot.p" file in the root of /system, and installed magisk, although, had to do another wipe (basically wipe every change..), now on 21a Stable boot
Edit #5: Again, 21a wanted to OTA to 21b, I skipped it, got into TWRP, and repeat steps to root 21a, Flash the Complete 21d zip, delete "recovery-from-boot.p" file in the root of /system, and reset the misc partition, to make sure TWRP and phone doesn't conflict (dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=256 count=1 conv=notrunc), flash magisk, phone boots successfully (one restart after setup wizard probably to properly set google account or something, after that, systemless xposed, and I'm golden..)
Can uppercut be used to install 10h after 21d? Does it wipe away the userdata? I know I am trying to go the other way instead of what this thread intended. But I don't have any KDZ for any RS988 version after 10c. Flashing kdz of 10c using uppercut just aborts the process after 4%
Full Background:
My LG G5 (RS988) was already on 21d when it started throwing "System.ui is not responding error" after boot. The screen remains blank when error comes and closing it doesn't give access to unlock screen. However, it seems all other apps and processes are working fine in backend - just that home screen is unable to It was never rooted or had bootlocker unlocked. I am primarily interested in recovering my data, so factory reset is not an option for me. I cannot use ADB as I cannot unlock my screen because of this error.
It took me 2 full days to finally successfully upgraded my ancient firmware (L09C16B170) to the updated version (L09C432B397). There are a lot pieces of information that I gathered from this forum and all over the internet that collectively helped me navigate this ordeal. Just want to share it with anyone who is in the same boat, although I know that P9 won't last for too long since P10 has been out for a while. However, if you still want to revive your P9, keep reading.
Requirement
Before reading, you need to understand ways of entering different modes of your P9 phone, which will be used many many times during your upgrade:
Enter recovery mode (also how you enter TWRP) - see this GUIDE
Enter fastboot mode - see this GUIDE
Enter manual upgrade mode (also called dload method; This is NOT TWRP method) - see this GUIDE. Please IGNORE any software or download information in this guide. I want you to refer to this guide for how to do it, NOT what to use or download!
You also need to download and know how to use ADB tool which is quite simple. Search the forum or google and you will find plenty of information and the download links. If you hate command lines, you can even use the GUI version from here.
You will probably also need to use Firmware Finder for Huawei (HWFF) to download firmware of interest for manual update during this process. HWFF is an app that can be installed for free via your phone Google Play Store. The downloaded firmware is saved under the HWFF folder in the internal memory. You might need to unzip these files for upgrade via dload method or directly via TWRP method without unzipping. However TWRP method requires you to unlock the bootloader and install TWRP in the phone (see below for details).
First step - debranding
If you are already on C432xxxx, you might just skip this step. I followed this thread partially (Debranding Guide by Z-Blade), since the whole thing doesn't work for me 100%.
Z-Blade did a fantastic job describing how to debrand his C34 firmware to C342B361. My original version is C16B170 which is a South Africa branded firmware. But I found certain steps in this guide could be omitted and certain steps didn't work in my case. Here is my modified version based on Z-Blade's version:
1. Unlock your bootloader and install TWRP
How to unlock bootloader? Follow this GUIDE. Even though it's for Huawei Ascend XT. It works for P9 as well. You only need to complete Part 1.
After you unlock the bootloader, install TWRP. Depending on which firmware version you're on, the version of TWRP that might work for your device changes. I encountered numerous booting loops due to incorrect version of TWRP. Finally I found that these three versions work for me (3.1.0-0, 3.1.1-0, 3.1.1-1). Always go with the highest version first (3.1.1-1). If you find yourself stuck in the booting screen, long press your power button until you get out of it and install another version of TWRP. Please go to TWRP official website to download TWRP for Huawei P9. Follow this GUIDE to install TWRP recovery on your phone.
2. Flash OEM info file for C432
After you unlock the bootloader and install TWRP recovery, download oeminfo-huawei-p9-eval09-c432.zip from this THREAD and flash it via TWRP method.
3. Flash C432B136 firmware
Download and flash the dload-huawei-p9-eval09-eva-b136.zip via dload method from this thread. After flashing and rebooting your phone, you should be on the L09C432B136 firmware. NOTE: If it boots up to a white screen asking you to enter password, reboot into recovery by holding volume up when you powering up your phone, do a wipe partition and factory reset. You may need to reboot your phone a number times before the phone boots up correctly.
Up to this stage, you have debranded your phone to an european version.
Second step - stepwise firmware upgrade
1. Update from B136 to B166 or B182
As mentioned in Z-Blade's original post, many people will not be able to directly update from B136 to B182. I am one of them. Go into the updater in the phone setting, refresh "check for update". If you can receive B182 update, by all means go for it. If you only receive B166 update, go for it as well. After B166 update and rebooting your phone, check updater again to see if you receive B182 update in the Settings menu. If this method does not work, manually update to B182 by following the steps here via dload method.
2. Update firmware from B182 to B360/361/378 and also upgrade OS from Android 6.0/EMUI 4.1.x to Android 7.0/EMUI 5.0
According to Z-Blade, "After your phone has rebooted and you are on the B182 firmware, you need to now update the firmware to B361 via Huawei Updater 2.0". However, in my case, I tried many times and always failed at this step. I found a workaround by updating to B360 instead of B361. Please follow this GUIDE to update to B360 or B361, whichever works for you. However, please pay attention to following change that I found critical:
- The version of Huawei HiSuite is critical for the success in this step. The GUIDE provided Hisuite download link (version 5.0.0.301_OVE). However, it does not work together with Huawei Updater 2.0 in my hands. This error has wasted me almost half day. Instead, I finally found out the problem and went to HERE to download the version 5.0.1.300 and it finally worked
- However, if even after HiSuite and Updater both work together fine the update does not proceed successfully (the updater might get stuck), you need to update it manually via dload method. Search EVA-L09C432B360 or EVA-L09C432B361 in Firmware Finder for Huawei as mentioned above and download the Full-OTA version (~2G). After download, move the corresponding folder containing firmware zip files under "HWFF" folder in the internal memory to the external SD card. Unzip the firmware file and update your phone using dload method. You may also try TWRP method which can install zip files directly, but at this point, you bootloader will be re-locked and TWRP will be gone. You need to unlock the bootloader and re-install TWRP again as mentioned above.
After you successfully update the firmware to B360 or B361, now you should have Android 7.0 and EMUI 5.0 on your phone. Now go to the updater in your phone setting. You should receive B378 OTA update. Proceed with the update...
You might not need to strictly follow following steps to update your phone to any firmware beyond B378. However, since a lot of new ROMs are based on B380+ or even B390+, if you want to use those, you might need to further update your firmware first.
2. Update firmware from B378 to B383
After updating to B378 and rebooting your phone, check if your phone receives B383 update OTA. If yes, proceed. If not, go to HWFF, download B383 Full-OTA firmware and update via either dload or TWRP method.
3. Update firmware from B383 to whatever later version
After successfully updating your phone to B383, you basically can flash your phone with anything firmware and ROMs built on B380+. I find it unnecessary to update to B386. What I did was that I directly updated from B383 to B394 by following this GUIDE. Since I wanted to try BlueWei 5.7 which is based off B397, I also followed the same guide to update my firmware to B397 before flashing BlueWei ROM.
Now please enjoy all kinds of new ROMs and the fast, revived P9. After this update, my P9 is super smooth (the original firmware and OS was utterly slow and sluggish) and I think I will keep using this phone until it really can't keep up with the hardware requirement of new apps etc.
Hope my guide is helpful!
Nice job to update things and summarize all together. Few comments, though
- Not necessary to go back to c432 b136, to b182 is enough:
https://forum.xda-developers.com/showpost.php?p=75105886&postcount=280
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
- For Nougat, please use Huawei P9 Nougat TWRP:
https://forum.xda-developers.com/p9/development/twrp-t3565703
- For DLOAD method, FullOTA-MF-PV versions should be used
- Besides the two methods listed to initiate DLOAD update, there is also a third one:
'Dial': *#*#2846579#*#*
Project Menu will open, select Software Update
Hello guys am using an Frd L02 ( Indian variant) and my phone is still stuck on January patch. Firmware Finder shows lots of updates but none are being pushed to my device. Any idea what could be the issue.
Also can i flash the firmware shown on firmware finder?
The issue is... Honor OTA system itself. xD
Best way to flash unapproved firmware installation is RedLotus method: https://forum.xda-developers.com/honor-8/how-to/guide-flashing-unapproved-firmwares-t3668306 (Unlocked Bootloader required - unlocking Bootloader do a Factory Reset/Wipe internal storage)
About a year ago I downgraded my quark to android 4.4.4, though it started an automatic update to marshmallow, and after it finished, I was presented with this (picture is in a attachment) afaik the bootloader is or was unlocked. I tried flashing stock but it fails.
sambow23 said:
About a year ago I downgraded my quark to android 4.4.4, though it started an automatic update to marshmallow, and after it finished, I was presented with this (picture is in a attachment) afaik the bootloader is or was unlocked. I tried flashing stock but it fails.
Click to expand...
Click to collapse
You have to flash the same or newer firmware you had before you downgraded. Your bootloader is still whatever that is before you downgraded to 4.4.4.
The only way you can flash older is to leave off the bootloader as well as leave off gpt.bin. That's what you did when you went back to 4.4 4. But this automatic update was STILL probably older than what you were on a year ago. So, it borked your phone because it was flashing older bootloader and gpt.bin files.
Sent via open market LG US998 V30/V30+
I came from a custom rom, so i guess that means I'm out of luck since i can't flash twrp.
sambow23 said:
I came from a custom rom, so i guess that means I'm out of luck since i can't flash twrp.
Click to expand...
Click to collapse
I didn't say anything about flashing TWRP.
When you downgraded to stock 4.4.4 you didn't use TWRP. Flash the stock firmware the normal way.
You flashed stock firmware, but had to leave off bootloader and gpt.bin.
When you allowed the automatic update to happen (to older Marshmallow than what you had before you downgraded), you broke that rule.
Sent via open market LG US998 V30/V30+