Manual Updating: How-To Preserve Root Access and Bootloader Unlock!
update... as of Nov 10 2014:
Official Lollipop for D855 and F400 has come out... following my instructions here you can still get bump'd - http://forum.xda-developers.com/showpost.php?p=56650179&postcount=59
So far, no anti-rollback in sight but I would still be careful of future updates.. and all other G3 devices models should be careful before taking an OTA (AT&T/Verizon... maybe).
Follow the steps above and you will ALWAYS have access to root/bump and flash anything you want.
This thread assumes you are already rooted, have TWRP installed and can read English.
If you have those 3 covered the rest is EASY as long as you read.
If you are unsure of any terms used in this post please search XDA/Google instead of asking in here.
Background
I'll get this out of the way right now... if you do not care about having access to Bump or root you can ignore all of this and continue to take LG's OTA updates. One could argue that taking OTA updates is required to maintain any level of safety/security... but that goes out the window once you start rooting and installing recovery/roms anyway. Regardless, I am not telling anyone not to update. But if you do update... do it manually. As of Oct 18 2014, every single G3 variant has root and bootloader unlock.. either out of the box(D851) or thanks to Bump. There is no need to ever take an OTA from here on out. The latest D855 and F400 OTA updates have blocked TowelRoot, IORoot and even Stump.. pretty sure only PurpleDrake works on them for now... I would expect PurpleDrake to be patched soon enough. And with official Lollipop updates coming root will only get harder. But.. as long as we install everything through TWRP manually we can update while keeping root/unlock/Bump.
Yes, we can downgrade using LG FlashTool but that could be blocked at any time with an OTA update to prevent rollback(Samsung does this).
Yes, it's possible to complete an OTA upgrade and maintain root but there is no way to know for sure if root will stick. And the OTA is upgrading the bootloader. Why gamble? This post is just a suggestion on how to stay updated without locking yourself out of anything... but it's not a rule. Just one of many options you can take. But if you do lose root or bootloader unlock after an OTA... don't go asking any devs when then next root tool is coming out or if there's a magical way to downgrade the bootloader. Overview
With all that said... now that we're all rooted and unlocked I decided to make a thread on how to:
1. Block OTA updates and remove OTA packages and that annoying notification. Easy!
2. Download updates manually.. no OTA zip needed. Easy!
3. Manually flash updates without losing root or Bump. Easy!
Most of us have access to the same files found in the latest OTA.. either with a .KDZ or .TOT(Sprint and AT&T refuse to release KDZ files..it seems they would prefer you to not be ale to fix the phone yourself). We can extract the individual partition files from a KDZ/TOT and easily flash them through TWRP. ATT/Sprint users will need leaked TOT files... or something like a pre-patched System.img/Boot.img/Modem.img from a user who has run a modified OTA update... yet managed to keep/regain root. More on that possibly in the future.
The main things we want out of a new OTA update:
A. Radio/Modem.img - although newer isn't always better
B. Kernel/Boot.img - this is often where root is blocked in new updates. But update manually and it no longer matters since we can root system through TWRP.
C. Rom/System.img - this is where most of the "fixes" in updates happen.. and what most people want from an OTA.
D. *Optional: Bootloader stack/Aboot.img,SBL1.img, DBI.img, LAF.img, RPM.img, TZ.img - this is where downgrading and Bump could be blocked. Avoid updating for now unless you are 110% sure you know what you're doing.How-To Block and Remove OTA Updates
If you are flashing custom roms in TWRP.. I'd expect OTA updates to already be removed. If you get an OTA update while running a custom flashable rom be sure to ask the dev why he can't make a proper custom rom that keeps you safe from OTA updates.
Block
Open LG Hidden Menu (3845#*851#) --> WLAN Test --> OTA Setting --> Disable
*Replace "851" with your devices model number, 850, 852, 855 etc.
This seems to only work on D851, D851 and D855 versions (possibly D857/8/9 and F400). AT&T, Verizon and Sprint users have reported the Hidden Menu method does not work. If you have one of those devices you can use a RootExplorer-type app to find the OTA related APK and rename the file to ____.apk.bak or use Titanium Backup to freeze it. If using Titanium Backup look for com.lge.lgfota.permission, OTA or System Update and freeze it. If looking for apk and odex file to rename.. search for OTA or FOTA or LGDMSClient.. etc
If you see an "Apps update" that just might be the "LG Apps" and not a firmware update. Updating LG apps is safe.. firmware is not (if you want to be able to maintain root/mods).
Remove OTA Update(and notification)
If an OTA notification is on your device you most likely already have the OTA file on your phone. If rooted, you can remove the OTA files and get rid of that annoying notification.
Updates are found in the /cache/ folder on your phone. Using a RootExplorer-type app(or ES File Explorer) browse to the root of your phone(NOT the root of your internal storage, /sdcard/, but the actual phone). If using ES File Explorer you may have to use the "show hidden files" option and grant the app root. You will see the update .zip file in cache if you did everything correctly. If no one has already uploaded the OTA zip.. copy the update to your sdcard and then upload for everyone else. Now delete the zip file from /cache/.
Deleting the file in /cache/ will get rid of the OTA but will not get rid of the notification. To get rid of notification:
1. Pull the notification shade down on your phone
2. Long press on the OTA notification until you see the App Info option pop up.
3. Click App Info and uncheck the Show Notifications box.
How-To Download Updates and Extract KDZ/TOT Files
1. Easiest way to obtain updates would be to look in this around XDA in your proper subforum for an update already posted by someone else. With Bump, many flashable rom zips will be popping up. Roms usually contain "system" and "boot"... which are two of the three things we generally want from an update. The third being the modem.. which is never included in a flashable rom and often not required to be updated. If you want the updated modem you will have to look around for the file or use the steps below to get it yourself.
2. If there is a new OTA update, no one has already posted the updated flashable files and you can't wait any longer... it is time to take matters into your own hands. Instead of giving in and taking the official OTA or begging others for help.. download the updated KDZ for your device yourself. And NO, we will NOT be not flashing the full KDZ.. we are just taking some files from it.
You can get your devices KDZ by visiting THIS LINK and entering in your MEID or IMEI.. it will give you a link to the latest available KDZ from LG. Sometimes KDZ files take a few days to show up after the OTA.. give it a little time. Do not beg in thread for KDZ files. Help yourself or wait for someone to post the files you were looking for.
It is encouraged to share not only KDZ and TOT files... but the extracted System/Boot/Modem images you extract from them as well. Only one person needs to download a KDZ per DeviceVariant/SoftwareVersion... that person can then share and everyone else just downloads from their link. You no longer have to be a "rom dev" of even know how to make a flashable zip to help share updates with others.
Anyway... to extract these partitions after downloading the KDZ/tot you can check out the following posts for scripts/tools to make things easy:
a. CLICK HERE [Tool][python] LG Compressed KDZ Extractor - by thecubed Script to extract partitions from KDZ.
b. CLICK HERE SystemMerger.py - by cybojenix Script to merge split system files from extracted KDZ.
c. CLICK HERE [TOOL]LG Bin Firmware Extractor - by xonar_ Script to extract TOT files and merge system.img's into one.
d. CLICK HERE [TOOL] KDZ and TOT Extractor - by bullghost Windows tool, adds all features of the scripts above with an easy to use UI.
invisiblek has updated xonar_'s LGBinExtractor to work with some more G3 devices - https://github.com/invisiblek/LGBinExtractor
If you have a question about an extraction tool be sure to read everything in the 4 threads. Post in the above threads if your question is still unanswered. Between the 5 extraction links above you can extract any G3 KDZ/TOT on Linux, OSX or Windows.
And remember, the main partitions we want from the TOT or KDZ: modem, boot and system.
Alternatively you can extract the KDZ directly on your phone -- click HERE.
Since more than a few people are having issues manually extracting... I will show an example that came from this thread and how to correct it:
KDZFileTools.py -f D85510L_00.kdz -x
[!] Error: Unsupported KDZ file format.
[ ] Expected: 0x28 0x5 0x0 0x0 0x34 0x31 0x25 0x80 ,
but received 0x28 0x5 0x0 0x0 0x24 0x38 0x22 0x25
Two things wrong here... first, the command is incorrect. when using the KDZFileTools.py "-x" is not used.. you want "-s 0" to extract the DZ.
Example:
Code:
python KDZFileTools.py -f D85510L_00.kdz -s 0
The second error is the "Expected.. but received" message. To fix this just open the .py script up in a proper text editor(notepad++ on windows for example).. find "x28x05x00x00x34x31x25x80" in the script...
replace it with "x28x05x00x00x24x38x22x25" (or whatever string is given after the "but received" output.. use logic) then save script.
rerun script. DZ will now extract into the "kdzextracted" folder. Once that finishes extracting you can use the Windows GUI tool to extract the .DZ file into individual partitions (and merge system). Or you can continue using the manual script methods.
To manually extract the DZ you're going to now use the DZFileTools.py script to split the DZ file (that's in the kdzextracted folder) into individual partitions.
Example:
Code:
python DZFileTools.py -f kdzextracted/D85510l_00.dz -x
that command will extract all your partitions into the dzextracted folder. Now drop the SystemMerger.py - by cybojenix file linked above into the dzextracted folder.. cd into the dzextracted folder and run that script to merge all the split system partitions into one system file.
Code:
python SystemMerger.py
All done.. you now have the boot, modem and full system.img to flash on your phone (along with every other partitions that comes with a kdz). :good:
3. Other methods for obtaining updated files would be grabbing the OTA update zip from the /cache folder and trying to pull files out of that.. or having an "in" and getting some leaked files or TOT. Sprint and AT&T users would benefit most from a leaked updated TOT.
Where-To Download KDZ Files
In this section I want to start a collection of all the latest KDZ files for all G3 devices.
You can help me out by either posting your KDZ link with FULL info about the KDZ/DEVICE..
Example of a helpful post:
derp said:
Hi, here is my model info and kdz url below...
LGD855
A6NEWH
D85510L_00
16GB
http://csmgdl.lgmobile.com/dn/downloader.dev?fileKey=FW978806432109876543213/D85510L_00.kdz
Click to expand...
Click to collapse
OR you can PM/Private Message me your IMEI so I can look up all the models and latest KDZ's myself. This would help me the most but I understand the security concern. If security is an issue.. you could leave the last 3 digits off the end so I dont have your exact #. If you trust me.. please consider sending me your IMEI if you own one of the devices I need listed below...
KDZ Links Below
Team Codefire had to come through once again and supply TOT files to the USA carriers that provide no public KDZ (AT&T, Sprint, Verizon)
AS985 (USA Regional) - NEED IMEI
D850 (USA AT&T) - 10D TOT (AT&T has no public KDZ files. Feel free to complain to them.)
D850PR (Puerto Rico Claro) - NEED IMEI
D851 (USA T-Mobile) - 10M KDZ
D852 (Canada) - NEED IMEI for D852 Bell, D852 Rogers and D852G
D855 (Europe) - 10L Netherlands 16GB | 10L Germany 16GB NEED MORE IMEIS
D855AR (Argentina) - NEED IMEI
D855K (Australia) - NEED IMEI
D855P (Brazil / Mexico) - NEED IMEI
D855TR (Turkey) - NEED IMEI
D857 (China) - 10C KDZ NEED IMEI STILL
D858 (China / Hong Kong) - NEED IMEI D858 and D858HK
D859 (China) - NEED IMEI
F400 (Korea)- F400L 20E,
LS990 (USA Sprint) - ZV4 TOT (Sprint has no public KDZ files. Feel free to complain to them.)
US990 (USA US Cellular) - 10C KDZ
VS985 (USA Verizon) - 12B
Click to expand...
Click to collapse
How-To Manually Flash/Update Device w/ System.img, Boot.img and Modem.img
1. You downloaded a custom rom flashable zip a rom has made for the community. Roms contain "system" and "boot"
Flash these in TWRP and follow any instructions in the thread/post where you downloaded it. Rom questions belong in those specific rom threads.
You may have to wipe data/factory reset in TWRP, depending on rom.. or you may need to flash a gapps zip if using an aosp-type rom.. etc..
There's no need to worry about OTA's using this route. Proper custom roms will never include the bootloader stack or anything that could remove your bootloader unlock. And just about all custom roms come with a pre-rooted "system" so you don't have to worry about root either. Remember to make a backup in TWRP before flashing anything.
2. You obtained some boot.img,modem.img,system.img files... either extracting from TOT/KDZ yourself or downloaded files another XDA member has uploaded. This method is something you can do all by yourself... no help from a dev needed. To make this method just as easy as flashing a custom rom zip in method #1.. I have made 3 flashable zip files - [Flash2System.zip, Flash2Boot.zip and Flash2Modem.zip]
Download them to your phone using the link below then follow the directions that follow...
DOWNLOAD FLASH2 FILES FROM CODEFIRE HERE
A. Make a new folder on your internal sdcard called: flash2
B. Download and place Flash2System.zip, Flash2Boot.zip and Flash2Modem.zip on your phone. Internal/external sdcard.
C. Stick system.img, boot.img and modem.img into the /sdcard/flash2/ folder. Files must be named system.img, boot.img and modem.img
D. Create backup's in TWRP.
E. In TWRP, flash Flash2System.zip and/or Flash2Boot.zip and/or Flash2Modem.zip to install your updated images.
F. If you have flashed a stock system.img you will need root. After the flash completes press Reboot System and TWRP will ask if you want root. Go thru the process in TWRP then reboot. After booting you may have a notification to finalize root. Few more clicks and you're rooted... it's that easy. No more worrying if root is patched in the latest OTA update... or having to undo everything you changed in stock so that the OTA doesn't brick you.
Flash2*.zip didn't work? Make sure your system/boot/modem.img files are in the /sdcard/flash2/ folder. Internal sdcard!
How-To Properly Share KDZ/TOT and other Update Files
If you have a new KDZ or have already extracted the KDZ.. please share it with the rest of us in this thread! Please post the KDZ link along with the exact model, region software version and size. Example: D855 Germany 10L 16GB KDZ.
If you want to share your extracted system.img, boot.img and modem.img files please upload them somewhere and share the link. Please specify if you would like others to mirror your files or not (if hosting them on personal server).
Please label all shared files properly! Name them appropriately with boot, modem or system in the name.. as well as the FULL model and software version. Entering my IMEI into the KDZ generator from the last section I can see my device info such as: LGD851TN and D85110M_00. Exact models and software versions are important so other users know which files they need to flash and which to avoid. You should only flash files for your exact device variant. An example name based on my info above: LGD851TN_10M_00_Boot.img (this can be renamed later to boot.img once downloaded or placed on sdcard).
Click to expand...
Click to collapse
More G3 Flash2 Threads:
[FIX] Stuck in Custom Recovery [TWRP/CWM] (After trying OTA)
[EFS] LG G3 EFS Backup and Restore
XDA:DevDB Information
Flash2, Tool/Utility for the LG G3
Contributors
autoprime
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2014-10-18
Last Updated 2014-12-11
Reserved
Nice. On the LS990 (Sprint), it appears that the APK responsible for OTA is titled "com.lge.lgfota.permission" version 4.4.2-LS990ZV41403169216
If I'm looking at the wrong app, someone please correct me, so that other users don't freeze this app and think they're covered, but I froze it and rebooted with no problems.
I also had to run the command line "am start com.lge.hiddenmenu ....[etcetera]" to get into the OTA enable/disable screen.
Block and remove instructions won't show, "spoiler" text reads "blocked"
Sent from my LG-D850
I have Verizon and after i enter : am start com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons in to adb i get an error:
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
starting: intent {act=android.intent.acton.MAIN cat =[android.intent.category.LAUNCHER] cmp=com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons} does not exist.
cali4nia831 said:
I have Verizon and after i enter : am start com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons in to adb i get an error:
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
WARNING: linker: app_process has text relocations. This is wasting memory and is a security risk. Please Fix.
starting: intent {act=android.intent.acton.MAIN cat =[android.intent.category.LAUNCHER] cmp=com.lge.hiddenmenu/.wlan_service.wifi_ota_buttons} does not exist.
Click to expand...
Click to collapse
did you install the hiddenmenu.apk as the link instructed?
then entered the following commands like the URL says:
Code:
adb shell
su
am start -a android.intent.action.MAIN -n com.lge.hiddenmenu/com.lge.hiddenmenu.HiddenMenu
which should then give you the hidden menu where you can "WLAN Test --> OTA Setting --> OFF"
Yes I did install the apk as instructed. It does open up the hidden menu after i enter those commands and after that error message but there is no WLAN TEST in the hidden menu that i can see.
---------- Post added at 10:55 PM ---------- Previous post was at 10:42 PM ----------
autoprime said:
did you install the hiddenmenu.apk as the link instructed?
then entered the following commands like the URL says:
Code:
adb shell
su
am start -a android.intent.action.MAIN -n com.lge.hiddenmenu/com.lge.hiddenmenu.HiddenMenu
which should then give you the hidden menu where you can "WLAN Test --> OTA Setting --> OFF"
Click to expand...
Click to collapse
Okay so i got it to the hidden menu to pop up as well as OTA enable/disable page even though it still gives me the same error message. I tap ENABLE and it says ENABLE but then i go back to the hidden menu and it still isn't listed...
EDIT:
Ended up just renaming the LGFOTA.apk file listed in the first reply above. So I should be good to go...
cali4nia831 said:
Yes I did install the apk as instructed. It does open up the hidden menu after i enter those commands and after that error message but there is no WLAN TEST in the hidden menu that i can see.
---------- Post added at 10:55 PM ---------- Previous post was at 10:42 PM ----------
Okay so i got it to the hidden menu to pop up as well as OTA enable/disable page even though it still gives me the same error message. I tap ENABLE and it says ENABLE but then i go back to the hidden menu and it still isn't listed...
Click to expand...
Click to collapse
Don't tap Enable.. Tap Disable... and that's it. OTA disabled... off.. all done.
Someone can provide me with img files? I dont have a PC, just using my phone PM if you can help me.
autoprime said:
word
XDA:DevDB Information
Flash2, Tool/Utility for the LG G3
Contributors
autoprime
Version Information
Status: Stable
Current Stable Version: 1.0
Created 2014-10-18
Last Updated 2014-10-18
Click to expand...
Click to collapse
Don't stick threads.. stick the man
He knows too much
Thanks for all your work
Edit: Can someone sticks his threads ?
Sorry for my noobish post, but where can I find tool for extracting KDZ for LG G3? You just provide link for GitHub, not for .exe program. Thanks.
First of all, thanks for the guide! It will help a lot of users in preserving bump and root
I don't think that leaving boot/etc .img out will help. LG engineers aren't stupid. The can, for example, do it like this: after "m" update all our phones will reflash aboot/etc partitions to patched versions on 1 jan 2015. The partition's images will be hidden in some big system file, while the waiting daemon will be hidden in, for example, healthd. We will never discover it until it's too late. GG WP.
That said, I really doubt that they will do it that way, but this is still a possibility. I guess i'll flash AOSP/CM/OMNI/smthing rom ASAP.
pRo_lama said:
Sorry for my noobish post, but where can I find tool for extracting KDZ for LG G3? You just provide link for GitHub, not for .exe program. Thanks.
Click to expand...
Click to collapse
link a, b ,c , d in the O.P. mate.. He provided all you need.... =)
The Python scripts and Windows GUI App, don't work for my D855 kdz files.
Don't have linux currently setup to test the last one (needs to be compiled).
L10nH34Rt said:
The Python scripts and Windows GUI App, don't work for my D855 kdz files.
Don't have linux currently setup to test the last one (needs to be compiled).
Click to expand...
Click to collapse
I'm on windows 8 mate... use the phython first with the kdz, then you can use the one with GUI for the dz file....
The hidden menu setting ever resets? Not after reboot, factory reset etc?
teddy0209 said:
I'm on windows 8 mate... use the phython first with the kdz, then you can use the one with GUI for the dz file....
Click to expand...
Click to collapse
I get an unsupported KDZ format error, that's my problem.
L10nH34Rt said:
I get an unsupported KDZ format error, that's my problem.
Click to expand...
Click to collapse
Well, I just extracted mine.... d855, v10i..
Check the command...
teddy0209 said:
Well, I just extracted mine.... d855, v10i..
Check the command...
Click to expand...
Click to collapse
I tried to extract v10l and it failed.
i deleted system updates with tibu should i delete LGFOTA.apk? under system,etc security there are a file named otacerts.zip should i delete that one to.
Related
On the Huawei site I was able to find a link to the original Honeycomb firmware for the generic Mediapad... does anyone have the links to the T-Mobile firmware?
Huawei Honeycomb Download Links
I would love to have these also.
Sent from my HUAWEI MediaPad using xda premium
Xanderful said:
I would love to have these also.
Sent from my HUAWEI MediaPad using xda premium
Click to expand...
Click to collapse
+1 This is a must have if we ever need to send the tablet back for warranty.
I am awaiting for my Springboard to arrive from USA in 10-14 days.
If (cross my fingers) I'll recieve it alive, the first thing in my todo list is to try backup images from all partitions (though warranty is not my case).
PS
If somebody can reguest SIM unlock code from TMO - I'm very curious, if there are a lot of binary differences between locked (before) and unlocked (after) nv_data.bin, or just a couple of bytes?
As promised:
www . 4shared . com/folder/WbaOrqKb/TMO_SB.html
www . filefactory . com/f/9296e687aa0253d5/
(sorry, too young to post links... extra spaces added)
Stock TMO SpringBoard S7-303uV100R001C201B027 partitions dump.
Except 4(extended), and those with individual data (5,13,14,16) partitions not being overwritten with known updates, 18 (recovery2) the same as recovery, 25 and 26 are empty.
Assuming "fastboot flash boot boot.img" etc for each partition.
Naming and filenames are in every huawei_partition.xml availiable - the only difference in partition table against MediaPad is mmcblk0p27 (/sdcard) which is intact during flashing.
Happy rooting and recovering!
PS
And for those who missed "4G" in general Huawei ROM's - just look at \hwcust\tmobile_us\resource\xml\cust.xml :
Code:
<!--begin DTS2011070602393 y00140144 add for TMO Data Icon Req-->
<boolean EDGE_shows_2G="true">
<boolean UMTS_shows_4G="true">
<boolean HSPA_shows_4G="true">
<boolean Roaming_shows="false">
<!--end DTS2011070602393 y00140144 add-->
Seems to me that T-Mobile treat all "except EDGE" as "4G" - one can decide for himself if this marketing bull**** worth thinking about.
thanks for posting this - would this follow the dload update process ? would you be able to type up how to restore this?
Bump. I downloaded Huawei's official 3.2 software update, then replaced all of the files in the update.zip folder with those posted. I was able to flash them onto my Springboard, and it said it completed successfully. Now, however, whenever I start the tablet, it just goes into a boot loop. Any thoughts?
There must be "log" and "sync_log" files on external sd card, which You used to update.
Can You post them anywhere?
jwhite326 said:
Bump. I downloaded Huawei's official 3.2 software update, then replaced all of the files in the update.zip folder with those posted. I was able to flash them onto my Springboard, and it said it completed successfully. Now, however, whenever I start the tablet, it just goes into a boot loop. Any thoughts?
Click to expand...
Click to collapse
I am not an expert but you might want to check on the file permissions.
Is it possible for someone to build a dload folder to install the above firmware?
Might it be possible to repack the T-Mobile system img with root, so that we can get root without changing firmwares?
Thank you so much for this. I needed it when I bungled up my system partition.
I was on a later OTA, so flashing your system img backup reverted me to an older firmware. This had some incompatibilities in terms of wi-fi and the front-facing camera, which I fixed by also flashing the kernel (boot img). In order to trigger it to propose an OTA update, I then had to also flash the cust img.
Having done that, I sniffed out in alogcat the URL of the OTA update:
http://android.clients.google.com/packages/ota/huawei_springboard_mediapad/009e6fd7c5ce.update.zip
im looking at the partitions xml and i cant figure out what is what, i know i can fastboot flash system, cache, userdata, boot, recovery etc, but what about the rest of the files - how do we flash them? what are the partition names? my springboard is totally screwed and stuck at the huawei logo i can only get to fastboot...any help would be appreciated
ZV6 is out!! And NO this is not Lollipop... it's still Android KitKat 4.4.2
Thanks to an anonymous donor we now have the ZV6 TOT. I have broken down the TOT and also uploaded the individual partitions which can be flashed if rooted. Speaking of root... ZV6 blocks Stump Root. If you wish to use ZV6 and have root you must install Bump'd TWRP while on ZV4 then manually flash the ZV6 boot/modem/system partitions... OR you may be able to root on ZV4 then take the official ZV6 OTA update and keep root -- the OTA has NOT been pushed yet so it is too early to say for sure. Remember to NEVER take an OTA if you have modified your SYSTEM partition at all (xposed/tethermod/etc) OR if you have TWRP installed.
Changelog:
Google Security Patches
Qualcomm Security Patch
International Voice over WI-FI
Improve unlock algorithm when phone is in the pocket
Enhancements to the LG Home (Sluggish UI fix)
Enhancement to the compass application
Enhancement to the Auxiliary cable recognition.
Mobilize Device Content Caching - An application caches HTTP web and app data on the device (not the Network), making the retrieval of data faster and saving bandwidth on the network
--TOT (*.zip) can be downloaded *HERE*
Flash this TOT using the same method as ZV4. You will need to select "Board DL" in LG Flash, otherwise you will get stuck. After the TOT flashes it will reboot your phone into the "MiniOS".. unplug the USB cable and press and hold the power button on the phone then press on the "Normal Boot" option on your phones screen. You are now on stock ZV6. Remember... there is no root for ZV6 so do not flash ZV6 TOT unless you don't mind being without root.
--Individual ZV6 partitions to flash manually can be downloaded *HERE*
I am removing the system.img from Codefire but thanks to @budeone system.img has been mirrored HERE. Feel free to make more mirrors of system...
The bootloader does NOT need to be updated in order to use the ZV6 boot/modem/system images. It's completely optional to flash the bootloader files (aboot, sbl1, dbi, laf, factory, tz, rpm). To flash the boot, modem and system partitions manually someone can make some new flashable *.zips containing the partitions... OR you can use my "flash2" *.zips which can be found under the How-To Manually Flash/Update Device w/ System.img, Boot.img and Modem.img section in my *[PSA] NO OTAs!! | Keep Root/Unlock | How-To: Block OTA, DL SW/FW, Update Manually* thread. You simply stick any loose system.img and/or boot.img and/or modem.img on your internal sdcard and flash my premade flashable zips in TWRP to install them.
--ZV4-to-ZV6 OTA Update Zip can be downloaded *HERE*
You must have a stock recovery and stock system partition for this to work. Being rooted may be OK but if you've edited or removed apks or other files or edited the build.prop then OTA zip may fail the integrity check. Root may not stick thru OTA.. until someone confirms one way or the othe the risk is yours.
Directions:
1. Remove USB cable from phone.
2. Power phone off.
3. Press and hold volume down + power until you boot into stock recovery.
4. Select "update with adb"
Rename zip file into update.zip
Code:
adb sideload update.zip
Alternate Directions to skip using ADB (needs microSD card):
1. Format microSD card as EXT4.
2. Rename zip to update.zip
3. Move update.zip onto external SD card. EZ way would be to stick SD card in phone then connect phone to PC and use MTP.
4. Power off and boot into stock recovery (vol down + power)
5. Select the Update from SDCARD option.
Alternate Directions to skip using ADB (must have root):
1. Stick OTA zip file in the /cache directory
2. Power off and boot into stock recovery (vol down + power)
3. Select the Update from cache option... then select the update zip you placed in /cache
As mentioned above.. ZV6 blocks Stump Root. Bump is not blocked.. so as long as you have root with ZV4 you can manually update to ZV6 and keep Bump'd TWRP or flash any Bump'd kernel or rom. No anti-rollback has been added to this update either.. so downgrading to ZV4 works!
Click to expand...
Click to collapse
Autoprime. Thank you for your work. +1
I've tried using the flash2 with system, boot and modem imgs being in flash2 folder on the internal storage. But It says it successfully flashed them but reboot and nothing.
Nada. I don't believe its really flashing them since it goes really quick.
Well, took me a bit to get back up and running... but yeah, not seeing much of a difference in this versus ZV4. (Well, except losing root since I'm impatient and flashed the TOT.)
Interesting any major changes or is it a security update
autoprime said:
ZV6 is out!! And NO this is not Lollipop... it's still Android KitKat 4.4.2
Click to expand...
Click to collapse
I'll mirror when I get home from work today. Thanks man!
@autoprime I read all the above, but do you know if we take zv6, can we revert by .tot to zv4? I know there's been issues with that in the past.
Warboy said:
I've tried using the flash2 with system, boot and modem imgs being in flash2 folder on the internal storage. But It says it successfully flashed them but reboot and nothing.
Nada. I don't believe its really flashing them since it goes really quick.
Click to expand...
Click to collapse
the flash2 files have a check in them to make sure the proper file is in its proper place before anything else.. this way it doesnt erase your partition if its not actually going to flash a new file. Perhaps the folder is named Flash2 with a capital F? If the folder is named "flash2" with lowercase f and is located at /sdcard/flash2/ on your phone.... and the files are named system.img modem.img and boot.img with all lowercase letters.. it should work. They have been confirmed working by many users across all G3 models.
If there is still an issue.. please provide a recovery.log if possible.
engine95 said:
@autoprime I read all the above, but do you know if we take zv6, can we revert by .tot to zv4? I know there's been issues with that in the past.
Click to expand...
Click to collapse
No issues downgrading. There'd be giant red letters everywhere otherwise. But I have now added a mention in the OP that specifies downgrading is still an option. :good:
ZV6 upgrade went just fine, as you stated. No problems using flash2 stuff and let TWRP save the root. It seems to upgrade the Home launcher as well as the contacts database. It also upgrades the Sprint data-sharing activity. In other words, ZVF6 works fine, but is not a big update.
Flashable zip should be up tonight. Tomorrow at latest.
http://forum.xda-developers.com/showthread.php?p=56937777
I have a working compass!
I flashed the modem.img first with no apparent change, then the system.img... Shazammm! After calibration, the compass seems to be accurate. This was the big flaw for me on an otherwise lovely device and now it seems to be working. Now I can look forward to a Lollipop update.
I pray it fixes the bluetooth. I have a Chrysler U Connect system and my G3 or a G3 Vigor for my girlfriend will not stay paired to the unit.
After unzipping the system.img zip, it's named "14-system.img".
I plan on using the "flash2" process of upgrading.
Do I need to rename "14-system.img" to just "system.img" for the flash2 procedure to work?
Thank you
EDIT: I went back and re-read Auto's manual update procedure and can confirm, yes, I do need to rename "14-system.img" to "system.img"
autoprime said:
the flash2 files have a check in them to make sure the proper file is in its proper place before anything else.. this way it doesnt erase your partition if its not actually going to flash a new file. Perhaps the folder is named Flash2 with a capital F? If the folder is named "flash2" with lowercase f and is located at /sdcard/flash2/ on your phone.... and the files are named system.img modem.img and boot.img with all lowercase letters.. it should work. They have been confirmed working by many users across all G3 models.
If there is still an issue.. please provide a recovery.log if possible.
Click to expand...
Click to collapse
The files are in the internal SDcard under "/sdcard/flash2/*.img" * being there respected names
here is the link to the recovery.log
http://pastebin.com/AE7y7KAH
Warboy said:
The files are in the internal SDcard under "/sdcard/flash2/*.img" * being there respected names
here is the link to the recovery.log
http://pastebin.com/AE7y7KAH
Click to expand...
Click to collapse
thanks for log. odd, the only error in the log is that it doesn't see the system.img file and then aborts.
for whatever reason it's checking /sdcard/flash2/ and not finding the file. Not sure where to go from here. Logs would suggest that the file name is incorrect or folder name is wrong. But you've said they are correct.. so.. idk.
To debug this further.. can you connect to adb shell while in TWRP? And paste the output from the following commands?
Code:
adb shell
cd /sdcard/flash2/
ls
autoprime said:
thanks for log. odd, the only error in the log is that it doesn't see the system.img file and then aborts.
for whatever reason it's checking /sdcard/flash2/ and not finding the file. Not sure where to go from here. Logs would suggest that the file name is incorrect or folder name is wrong. But you've said they are correct.. so.. idk.
To debug this further.. can you connect to adb shell while in TWRP? And paste the output from the following commands?
Code:
adb shell
cd /sdcard/flash2/
ls
Click to expand...
Click to collapse
http://imgur.com/J5FkM9V
http://imgur.com/RGnDXyZ
Warboy said:
http://imgur.com/J5FkM9V
http://imgur.com/RGnDXyZ
Click to expand...
Click to collapse
I'm officially stumped
everything looks right. just not meant to be on your device I guess.
I'm reaching here.. but maybe there's some issue if you used MTP? Versus using ADB push to put the image on your phone?
Have you noticed if the modem or boot image has updated (those would be fast flashes) and just system is not working? or all 3 not working? You'd have to check the software settings under About Phone to see if baseband(modem) or kernel changed.
you could always use the dd command to try and flash the image while in TWRP..
Code:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/sdcard/flash2/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
The 2 dd commands should take a minute or three to complete.
Or just wait for engine95's stock rooted ZV6 rom.
autoprime said:
I'm officially stumped
everything looks right. just not meant to be on your device I guess.
I'm reaching here.. but maybe there's some issue if you used MTP? Versus using ADB push to put the image on your phone?
Have you noticed if the modem or boot image has updated (those would be fast flashes) and just system is not working? or all 3 not working? You'd have to check the software settings under About Phone to see if baseband(modem) or kernel changed.
you could always use the dd command to try and flash the image while in TWRP..
Code:
adb shell
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/sdcard/flash2/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
The 2 dd commands should take a minute or three to complete.
Or just wait for engine95's stock rooted ZV6 rom.
Click to expand...
Click to collapse
Should it be Flash2 not flash2
thznutz87 said:
Should it be Flash2 not flash2
Click to expand...
Click to collapse
I tried having a capital F and that didn't change anything.
system.7z
https://mega.co.nz/#!G0onwR5T!QV-NZ2hpAIllAX9tKCNBDkGLyE7AWD241Stws-c6y18
Hi everybody
I own an Xperia Pro MK16i. The phone is still on stock ROM (4.0.2.A.0.58 GB 2.3.4) and the bootloader is still locked. The only thing I did recently is root the phone successfully with eRoot.
Now, the phone still gets the OTA updates, right now it does notify me that the "new" update 4.0.2.A.0.62 (the latest GB release available for my phone) is ready to download. I would like to install this update in order to try it and only after eventually switch for ICS 4.0.4 (4.1.B.0.587 is the latest).
I was wondering myself:
1) Is there any way to backup the OTA update in order to save and store it for the future? I red that OTA update files end up in the /cache folder and thank to root access I managed to open that folder and see that as soon as I download the OTA update a download_package.bin is created inside the folder; the problem is that the file is less than 8MB and it's a BIN file. What this file is for and is there any way to make use of it? The only thing I know is that it's too small to be the real firmware/rom...right?
2) Is there any chance for me to get somewhere the 4.0.2.A.0.62 stock rom with the proper customization number? My phone is unbranded and purchased in Italy where I live, customization version is: 1249-7782_R12D
3) What does this customization mean? Is it about language? About preinstalled apps? Or what? Someone could clear me the whole thing please?
Many thanks
goriath said:
1) Is there any way to backup the OTA update in order to save and store it for the future? I red that OTA update files end up in the /cache folder and thank to root access I managed to open that folder and see that as soon as I download the OTA update a download_package.bin is created inside the folder; the problem is that the file is less than 8MB and it's a BIN file. What this file is for and is there any way to make use of it? The only thing I know is that it's too small to be the real firmware/rom...right?
Click to expand...
Click to collapse
OK, I digged around about this point and just for reference I share what I found.
The main problem with OTA updates is these packages are binary DELTA packages; they are not the full ROM/FW release, but they contain only the differences between the source ROM (the firmware installed in the phone) and the target ROM (the updated firmware you want to install in the phone).
I took a look inside the BIN file with an HEX editor and what I found confirm the dependance between the update and the stock ROM:
<?xml version="1.0" encoding="ISO-8859-1"?>
<metadata version="3.2">
<product>
<manufacturer>SonyEricsson</manufacturer>
<model>MK16i</model>
<hwplatform>MSM7x30/8x55</hwplatform>
</product>
<update>
<generation>
<version>2.0.0.24</version>
<date>2012-02-01T11:01:38+01:00</date>
<rb_version>6.2.29.19</rb_version>
<rb_ua_version>6.2.29.19</rb_ua_version>
</generation>
<source>
<software>
<revision>4.0.2.A.0.58</revision>
</software>
<customization>
<variant>1249-7782</variant>
<revision>R12D</revision>
</customization>
</source>
<target>
<software>
<revision>4.0.2.A.0.62</revision>
</software>
<customization>
<variant>1249-7782</variant>
<revision>R12D</revision>
</customization>
</target>
</update>
</metadata>
This explains why my download_package.bin is large only 7.55MB; it does update (add/replace files to) the actual ROM. And this is the reason why updates through OTA are sequentials; I cannot install latest GB OTA update w/o go through every previous update first.
So this binary package alone is not useful to create a full ROM of any sort, cannot be flashed as is and cannot be extracted/unpacked/decrypted unless to be a developer and doing reverse engineering.
So my friend got an update to the huawei XT. He was already at b160. The new update is labeled as b170 which i think it could gain some hope this phone will get nougat sometime (most likely not). The update only has a device security patch. The security is from june 5 which is pretty old but i guess it's better. If someone else received the update post it here
got the notice for update at noon today - but alas, I have mine rooted so it tried to update, and then reset and is back at 160.
and yes, was really hoping beyond hope for some Nougat...
We need someone then to unroot the phone and update to b170 or at least check how to update to b170
See this post and links in it for how we updated before if the phone was already rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
ensol52 said:
So my friend got an update to the huawei XT. He was already at b160. The new update is labeled as b170 which i think it could gain some hope this phone will get nougat sometime (most likely not). The update only has a device security patch. The security is from june 5 which is pretty old but i guess it's better. If someone else received the update post it here
Click to expand...
Click to collapse
Paisley Pirate said:
got the notice for update at noon today - but alas, I have mine rooted so it tried to update, and then reset and is back at 160.
and yes, was really hoping beyond hope for some Nougat...
Click to expand...
Click to collapse
divineBliss said:
See this post and links in it for how we updated before if the phone was already rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
Click to expand...
Click to collapse
If anyone is able to capture the B170 update and upload it somewhere I'll try and make a TWRP flashable update
My phone doesn't see any updates yet
Could you briefly describe how to do this please? Can it be done from a phone with a locked bootloader or must the bootloader be unlocked?
clsA said:
If anyone is able to capture the B170 update and upload it somewhere I'll try and make a TWRP flashable update
My phone doesn't see any updates yet
Click to expand...
Click to collapse
divineBliss said:
Could you briefly describe how to do this please? Can it be done from a phone with a locked bootloader or must the bootloader be unlocked?
Click to expand...
Click to collapse
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
clsA said:
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
Click to expand...
Click to collapse
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
redbeard1083 said:
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
Click to expand...
Click to collapse
HwOUC/****** (numbers)
redbeard1083 said:
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
Click to expand...
Click to collapse
MT2-User said:
HwOUC/****** (numbers)
Click to expand...
Click to collapse
Thanks seems AT&T likes to put them in the path I described though
I'm pretty sure we can edit the updater script to install this from TWRP if someone captures it
clsA said:
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
Click to expand...
Click to collapse
working on grabbing it now.
Tried grabbing it - and messed up and got past the waiting part - it tried to update and (of course) failed. I'll give it another shot shortly.
Paisley Pirate said:
working on grabbing it now.
Tried grabbing it - and messed up and got past the waiting part - it tried to update and (of course) failed. I'll give it another shot shortly.
Click to expand...
Click to collapse
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
clsA said:
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
Click to expand...
Click to collapse
When I get it I'll get all that as well.
The ATT update note calls it B160_B170_SMR_100 , I hit continue when I tried to hit "remind me later" - but it redownloaded.
Ghost Commander shows nothing in the /cache - odd - so I don't know where it's actually sticking it. I'm searching for it both under that name above and also as update.zip and anything else I can think of (by date, since it just re-downloaded)
I'll grab and document all the info on what I got where.
File is in /cache/fotapkg/ but is named package_temp.zip
I have it out, xda won't accept the file that large, trying to figure out how to link that file only to my onedrive so you can get it without access to all my other junk (sorry)
clsA said:
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
Click to expand...
Click to collapse
https://1drv.ms/u/s!AkvKyEBneZGLjuQ44wo1pwjtdbgOCA
OneDrive link to file package_temp.zip should be 102 mb in size.
Got it using Total Commander. It seems to be better at grabbing root files than Ghost was.
Also, one other note - I modified the permissions from root root to everyone so that may need to get changed back (or not - you tell me) to be able to get it to move.
Paisley Pirate said:
https://1drv.ms/u/s!AkvKyEBneZGLjuQ44wo1pwjtdbgOCA
OneDrive link to file package_temp.zip should be 102 mb in size.
Got it using Total Commander. It seems to be better at grabbing root files than Ghost was.
Also, one other note - I modified the permissions from root root to everyone so that may need to get changed back (or not - you tell me) to be able to get it to move.
Click to expand...
Click to collapse
ok my phone doesn't see the file as an update ..where was it located ?
that is the file sent down from ATT to the phone. I have unzipped it and looked at it as well -it's 209MB unzipped. Contains the following files and drawers:
cust.new
cust.patch
cust.transfer
system.new
system.patch
system.transfer
UPDATE.APP
(drawer) META-INF
(drawer) com
(drawer) android
otacert
(drawer) google
(drawer) android
update-binary
update-script
blacklist.conf
CERT.RSA
CERT.SF
MANIFEST.MF
If you can't get the .zip to open, let me know and I'll stick it on one drive unzipped.
Paisley Pirate said:
that is the file sent down from ATT to the phone. I have unzipped it and looked at it as well -it's 209MB unzipped. Contains the following files and drawers:
If you can't get the .zip to open, let me know and I'll stick it on one drive unzipped.
Click to expand...
Click to collapse
file opens fine ..where was it located on the phone
clsA said:
file opens fine ..where was it located on the phone
Click to expand...
Click to collapse
as I said earlier - /cache/fotapkg/
Paisley Pirate said:
as I said earlier - /cache/fotapkg/
Click to expand...
Click to collapse
Well I'm sorry to report so far I have had no luck installing this thing
I have tried the dload/update.app using the dialer method and the update flashes but you have no wifi afterwords
and the phone still shows you on B160 (cust not updated / system files not patched)
I also tried with Flashify and Stock recovery and used an edited updater script in TWRP and all fail for one reason or another
Sooo the only way we will get this is if someone that has done the update
uses TWRP and creates a system.img and cust.img and uploads it somewhere for me
So I can build the B170_Full_Update.zip
Any idea how the phone installs this OTA zip file?
Is the updater-script failing because of assert statements for cust and system?
Have you had success patching cust and system using the OTA updater-script/OTA zips for the Huawei Ascend XT before? How did you end up getting the cust and system for your B160 Update zip? Probably from a TWRP of someone's updated B160, which is what we need to do for B170 now, I'm guessing?
Thanks for your efforts on this and answering my questions.
clsA said:
Well I'm sorry to report so far I have had no luck installing this thing
I have tried the dload/update.app using the dialer method and the update flashes but you have no wifi afterwords
and the phone still shows you on B160 (cust not updated / system files not patched)
I also tried with Flashify and Stock recovery and used an edited updater script in TWRP and all fail for one reason or another
Sooo the only way we will get this is if someone that has done the update
uses TWRP and creates a system.img and cust.img and uploads it somewhere for me
So I can build the B170_Full_Update.zip
Click to expand...
Click to collapse
Hi,
in this tutorial I will guide you how to upgrade from Nougat to Oreo and updating Oreo to newer version, when they are released.
NEW! Update Oreo to Pie - in testing now, please report!
ANNOUNCEMENT - 06 March 2019: Since I fried my phone with wrong update files, I don't own a P10 anymore. I'm still active on XDA but can't give as much support as usual for the P10. If you find any issues or have any suggestions, please post it here and qoute me. Everyone is free to use and edit my script and release it in a new threat. If someone needs help with that, let me know.
Special thank are going to @mankindtw who wrote the script and @Blackball who released something similar for the P10Plus.
I just edited the script for working with the P10 to make it easier for you.
DISCLAIMER: I don't give any warranty. I tested this on 5 devices without any problems.
This Tutorial ist just for the Huawei P10 (VTR).
This tutorial has two versions:
Tutorial 1: Upgrading your P10 from Nougat to Oreo
Tutorial 2: Updating to a newer Oreo version.
Prerequisites: You need a sd card with minimum 4gb free space, formatted in FAT32.
Also you need an unlocked bootloader and TWRP installed.
Read first, then do it.
Backup, backup, backup - please, don't blame me when you notice data loss.
For everyone who don't know how to unlock bootloader and install TWRP, here's a short tutorial:
Unlocking bootloader (will void warranty!):
The site is down at the moment. There's no official statement from Huawei if they shut it down completely or if there's just an error on this site. Fact is, at this moment you can only get an unlock code by sending Huawei support an E-Mail or using DC Phoenix (costs around US$5)!
If you found another solution, tell it here for everyone, please!
- Go to settings app and write down you IMEI, Build-Number and Model-Number. VERY IMPORTANT!
- Open phone app and dial *#*#1357946#*#* - write down the Product-ID and Serial Number. VERY VERY IMPORANT!
- Go back to settings, open developer options and activate OEM-Unlock and USB-Debugging.
- Go to this site, login or create account, follow the steps and fill out the forms to get your unlock code.
- VERY VERY VERY IMPORTANT: Write it down on paper, pc, laptop, tablet - everything you have. If you lost it and brick your phone with locked bootloader, you'll not be able to unbrick it without payed services like FunkyHuawei!
- ALSO VERY IMPORTANT: Do a backup of everything you need! Unlocking the bootloader will cause a factory reset, all data will be removed!
- Now turn off your phone.
- Connect it to USB and turn it on while holding the volume-down button.
- You should see the fastboot screen with green FRP Lock and Bootloader Lock.
- AGAIN: BACKUP! Do you have your unlock code save?
- Type following command into your cmd or terminal: "fastboot oem unlock CODE"
- Confirm the unlock with volume-up and power button.
- Done, phone will do a factory reset and the bootloader is unlocked.
Install TWRP:
- Open the developer settings and enable the the "OEM Unlock" and "USB Debugging" if you haven't done it already.
- Download the right TWRP version: TWRP 3.1.1-0 for Nougat by @OldDroid - TWRP 3.1.1 for Oreo by @Blackball.
- Boot into fastboot mode by turning off the phone, connect it via usb to you pc and power it on while holding down Volume-Down until you see the white fastboot screen.
- Flash the TWRP version - there are two different commands for Nougat and Oreo:
Nougat:
Code:
fastboot flash recovery TWRP.IMG
Oreo:
Code:
fastboot flash recovery_ramdisk TWRP.IMG
- Test it by turning off the phone with holding the power buttong until it's off and boot the phone with DISCONNECTED usb while holding Volume-Up.
Now the real thing:
Tutorial 1 - Upgrade Nougat to Oreo
Do not use this to unbrick your P10 or REinstall Oreo! This works only, if you're on Nougat! Otherwise you can full brick your P10!
Mention: I didn't loose any data after upgrading from Nougat to Oreo with this method. None of the guys who tested it noticed any data loss. BUT, no warranty for this!
BACKUP BEFORE YOU UPGADE!
- First you need to find your correct firmware for your model on the Huawei Firmware Database. This is not a rebrand tutorial!
Link: http://pro-teammt.ru/firmware-database or use the links for L09/L29 I provided below.
- When you found your version (example VTR-L29C432B360) find the row which containts "FullOTA-MF" and click on "filelist". Only tested with B360 FullOTA-MF, one guy bricked his phone using B365 Full-OTA-MF-PV, I think it's because B365 is an update from B360, but I really don't know if B1xx to B365 alway bricks your phone! Just use B360 and then use oreoupdate.zip for updating to a newer version - this method is tested on multiple devices without any problems.
- You need three files: update.zip, update_data_full_public.zip, and update_full_MODEL_hw_[].zip (example update_full_VTR-L29_hw_eu.zip).
- When you downloaded all three files rename it after this:
update.zip stays.
update_data_full_public.zip stays.
update_full_MODEL_hw_[].zip to update_full_hw.zip.
- Download this rar archive (alternative link without ads if you don't want to support me ) - Version 060518, MD5 0637269f1dc9b9a509de97ff14559f4a.
- Extract the archive on your sd card - you should have a folder named "oreoupgrade" on it. This folder contains three files: oreoupgrade.zip, VTR_RECOVERY_NoCheck.img and VTR_RECOVERY2_NoCheck.img.
- Put the three update zips you downloaded before inside the "oreoupgrade" folder on sd card.
- Your SD card has to look like this:
{
"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"
}
- Insert the sd into your phone and boot into TWRP.
- AGAIN: DO A BACKUP!
- Tap on Install, navigate to your sd card and into the oreoupgrade directory.
- Tap on oreoupgrade.zip and install it.
- The phone will restart by itself - don't press any button!
- eRecovery will start and install the update - if you didn't do anything wrong, it should take around 2 minutes and the phone will do a reboot.
- If the phone won't reboot after update wait at least 5 minutes until you do it by yourself (I had this issue with only one P10).
That's it - you should have Oreo installed.
The script installs the original recovery, so TWRP is removed. The bootloader stays unlocked.
Tutorial 2 - Updating Oreo version
Do not use this if you're on Nougat! This Tutorial is only to upgrade the Oreo / EMUI 8 version! Don't use it to unbrick, if you don't know what you do!
BACKUP BEFORE YOU UPDATE!
I tested it on 24.03.2018 with my VTR-L29C432. I updated from B360 to B365 without any problems. No data loss, no bugs notices. Update process took around 4 minutes.
- First you need to find your correct firmware for your model on the Huawei Firmware Database. This is not a rebrand tutorial!
Link: http://pro-teammt.ru/firmware-database or use the links for L09/L29 I provided below.
- When you found your version (example VTR-L29C432B360) find the row which containts "FullOTA-MF" and click on "filelist". BFullOTA-MF-PV seems to mean "Public Version". I tested it on three devices without any problems but one guy notified me that B365 FullOTA-MF-PV bricked his phone after using this to upgrade from Nougat. For me it works fine.
- You need three files: update.zip, update_data_full_public.zip, and update_full_MODEL_hw_[].zip (example update_full_VTR-L29_hw_eu.zip).
- When you downloaded all three files rename it after this:
update.zip stays.
update_data_full_public.zip stays.
update_full_MODEL_hw_[].zip to update_full_hw.zip.
- Download this rar archive (alternative Link without ads if you don't want to support me ) - version 040518, MD5 c4c7b33d104b696a6132f8be1f36ba0b
- Extract the archive on your sd card - you should have a folder named "oreoupdate" on it. This folder contains three files: oreoupdate.zip, VTR_RECOVERY_OREO_NoCheck.img.
- Put the three update zips you downloaded before inside the "oreoupdate" folder on sd card.
- Your SD card has to look like this:
- Insert the sd into your phone and boot into TWRP.
- AGAIN: DO A BACKUP!
- Tap on Install, navigate to your sd card and into the oreoupdate directory.
- Tap on oreoupdate.zip and install it.
- The phone will restart by itself - don't press any button!
- eRecovery will start and install the update - if you didn't do anything wrong, it should take around 2 minutes and the phone will do a reboot.
- If the phone won't reboot after update wait at least 5 minutes until you do it by yourself (I had this issue with only one P10).
That's it - you should have updated Oreo to a newer version.
The script installs the original recovery, so TWRP is removed. The bootloader stays unlocked.
If there are any issues with this notify me so we can work together to find a solution!
Please post the TWRP log and a screenshot of your oreoupgrade / oreoupdate directory on your sd card with file sizes. With this information it's easier to help.
Tutorial 3 - Updating Oreo version with official EMUI updater
Do not use this if you're on Nougat! This Tutorial is only to upgrade the Oreo / EMUI 8 version! Don't use it to unbrick, if you don't know what you do!
This Method is only if there's an official update released for your device by Huawei. You'll get a system update notification. If there's no such notification use Tutorial #2!
MENTION: I tested it on my device from B365 to B369 without any problems. If there are any issues, please notify me. Brick risk is barely 0 because it's using offical update files downloaded by EMUI.
BACKUP BEFORE YOU UPDATE!
- Check if there's an official update available in system settings. You should also get a notification. DO NOT INSTALL, YET!
- Download this rar archive (alternative Link without ads if you don't want to support me ) - version 130618, MD5 52cb33d74055f01a2fb4425d5b918b18.
- You can choose two different places where you extract it:
- 1. Without root: SD card: Just extract the archive on SD card, so you'll have a directory on it called "officialupdate". Inside this directory are two files: "officialupdate.zip" and "VTR_RECOVERY_OREO-NoCheck.img".
- 2. With root: /cust directory. Extract the archive with a file manager of your choise and put the "officialupdate" directory into /cust.
- Now boot into TWRP and install the officialupdate.zip on SD or in /cust - /cust needs to be mounted. Go to "Mount" and just check "cust". Then go to "Install" and navigate to the .zip file.
- TWRP will install the modified recovery - it's the same one as in Tutorial #2.
- Reboot into system
- Install the update and the update process will start.
Note: The reboot after the update can take a few minutes (my phone took around 5 minutes!). Don't abort the reboot process!
You also need to install the root again after this update!
Note #2: I need testers for it. Please write here in this threat if it worked for your or not with phone information (model, version, etc.).
Tutorial 4 - Upgrading Oreo to Pie - IN TESTING NOW!
Do not use this if you're on Nougat! This Tutorial is only to upgrade EMUI 8 to 9! Don't use it to unbrick, if you don't know what you do!
BACKUP BEFORE YOU UPDATE!
I tested it on 24.03.2018 with my VTR-L29C432. I updated from 8.0.0.381 to 9.0.1.157 without any problems. No data loss, no bugs notices. Update process took around 5 minutes + 5 minutes for booting.
- First you need to find your correct firmware for your model on the Huawei Firmware Database. This is not a rebrand tutorial!
Link: http://pro-teammt.ru/firmware-database or use the links for L09/L29 I provided below.
- When you found your version find the row which containts "FullOTA-MF" and click on "filelist".
- You need three files: update.zip and update_full_MODEL_hw_[].zip (example update_full_VTR-L29_hw_eu.zip).
- When you downloaded both files rename them after this:
update.zip stays.
update_full_MODEL_hw_[].zip to update_full_hw.zip.
- Download this rar archive - version 190219 MD5 37b51e19f70af6a896cadd522342e213
- Extract the archive on your sd card - you should have a folder named "pieupgrade" on it. This folder contains two files: pieupgrade.zip, VTR_RECOVERY_OREO_NoCheck.img.
- Put the three update zips you've downloaded before inside the "pieupgrade" folder on sd card.
- Insert the sd into your phone and boot into TWRP.
- AGAIN: DO A BACKUP!
- Tap on Install, navigate to your sd card and into the pieupgrade directory.
- Tap on pieupgrade.zip and install it.
- The phone will restart by itself - don't press any button!
- eRecovery will start and install the update - if you didn't do anything wrong, it should take around 2 minutes and the phone will do a reboot.
- If the phone won't reboot after update wait at least 5 minutes until you do it by yourself (I had this issue with only one P10).
That's it - you should have updated to EMUI 9 / Pie.
The script installs the original recovery, so TWRP is removed. The bootloader stays unlocked.
Please note, that there's no TWRP for Pie at the moment. You may not be able to install Magisk! If you find a working TWRP, let me know!
Please note that this is too new to know everything. If you have any issues, let me know. I can't guarantee that this script works for you.
Only use your model region, only use it with B376++, only install the Pie-Beta if you know about the risk to brick your phone.
Be also aware that installing not official released version can cause a not certified play protect status! I noticed this on my P10 after updating to 9.0.1.157. I didn't notice any issues with that, yet, but I can be.
Tutorial 5 - Updating Pie and downgrading to Oreo - IN TESTING NOW!
Do not use this with Nougat or Oreo! This script is for Pie, only!
BACKUP BEFORE UPDATING / DOWNGRADING!
This script will work for updating Pie version and also for downgrading back to Oreo, with the right files.
Read the tutorial first before you do anything! BRICK RISK IS HIGH!
Special thanks to @lukasob, who helped me with this script.
- First you need to find your correct firmware for your model on the Huawei Firmware Database.
- ATTENTION FOR DOWNGRADING: There are downgrade updates available, mostly to version 384. Those downgrades are containing only 2 files instead of 3:
- "update.zip"
- "update_full_MODEL_hw_[].zip"
If there's also a "update_data_full_public.zip", it's the wrong downgrade! DON'T USE THIS!
THIS WILL CAUSE FULL HARD BRICK!
- When you downloaded both files rename them after this:
update.zip stays.
update_full_MODEL_hw_[].zip to update_full_hw.zip.
- Download this rar achive - version 180319 MD5 e53284141f1d93ac2e6ab9d1f528db08
- Extract the archive on your sd card - you should have a folder named "pieupdate" on it. This folder contains four files: pieupdate.zip, VTR_RECOVERY_OREO_NoCheck.img, pie_stock_recovery.img.
- Put the TWO update zips you've downloaded before inside the "pieupdate" folder on sd card.
- Inser the sd into your phone and boot into TWRP (flash the Oreo TWRP which you can find here on XDA. It'll work with this).
- AGAIN: DO A BACKUP!
- Tap on Install, navigate to your sd card and into the pieupdate directory.
- Tap on pieupdate.zip and install it.
- The phone will restart by itself - don't press any button!
- eRecovery will start and install the update - if you didn't to anything wrong, it should take around 2 minutes and the phone will do a reboot.
That's it. You either did an update or a downgrade, depending on which files you've used.
It's really important to flash the correct downgrade files, otherwise you'll brick your phone totally! I did this and even with DC Phoenix I couldn't recover my phone yet.
Flash stock recovery with Pie - TWRP or Root needed
- Download Pie update.zip and extract the UPDATE.APP.
- With Huawei Update Extractor (Google it, please) extract RECOVERY_RAMDIS.img and ERECOVERY_RAMDIS.img (you need to disable the file verification in the settings of HUE)
ROOT METHOD (all commands without qoutes):
- Put the two files in the root directory of your phone's internal memory without any directory
- Use a terminal emulator or adb shell on your pc.
- Enter following command to find out which device you're on: "/dev/block/platform/"
- You should see either "ff3b0000.ufs" or "hi_mci.0" after confirm the command with enter - remember it, I call it TYPE in the following commands.
- Access root privileges with "su" --> ENTER
- Now enter two commands and confirm with enter after each:
"dd if=./RECOVERY_RAMDIS.img of=/dev/block/platform/TYPE/by-name/recovery_ramdisk" --> ENTER
"dd if=./ERECOVERY_RAMDIS.img of=/dev/block/platform/TYPE/by-name/erecovery_ramdisk" --> ENTER
- Done, if there are no error outputs.
TWRP METHOD:
Download this file and put it on external sd in a directory called "flashrecovery". (used zippyshare, because mega is slow at the moment)
Extract RECOVERY_RAMDIS.img and ERECOVERY_RAMDIS.img from UPDATE.APP and put it into flashrecovery on sd (file names are important and also case sensitive!).
Install the flashrecovery_pie.zip with TWRP. The phone will reboot after flashing the recovery.
Magisk installation - NOUGAT AND OREO ONLY! NOT WORKING ON PIE
It's a bit more complicated to install Magisk with EMUI 9 than it was before.
Instructions can be found here.
I didn't try it, yet. Please report if this works.
EDIT_MAGISK:
I tried to patch recovery image with Magisk but with this the phone doesn't boot with enabled root.
Let me know, if you find any solution.
Thanks for testing @tangoalfa
Addition: Root with Magisk by @Blackball
Special thanks to @mleczan who provided the code for eMMC devices!
KNOWN ISSUES
- @SwiftingDuster got is bootloader loggeg with VTR-L29C636B362 coming from B162. It can be produced by the firmware files, I really don't know.
- eMMC version of P10 can be bricked! Thanks @mleczan for notice. If possible I will release an eMMC version, but without testers I can't do it.
--- U P D A T E - C H A N G E L O G ---
UPDATE 130618 - Only officialupdate
- Fixed an issue with the script, should work know (theoretically - can't test it at the moment!)
UPDATE 020618 - Only officialupdate
- Added a third guide for using official update method by EMUI.
Testers needed!
UPDATE 060518 - Only oreoupgrade
- Added support for eMMC devices
Thanks to @mleczan who provided me information about eMMC devices!
Testers for both versions are still welcome and wanted - I need information if it's working or not (I can't provide any warranty for safety!)
UPDATE 040518 - Only oreoupdate
- Added support for eMMC devices.
Special thanks to @mleczan who provided the code for eMMC devices!
Testers with eMMC devices are needed! Please read post #219!
UPDATE 080418
- Fixed oreoupdate - should work now!
UPDATE 050418
- Added comments to TWRP output
- Added security and fail safety
(check if all files are present and in the right directory, if not, it stops)
IF YOU FIND ANY ERRORS OR TYPOS PLEASE REPORT !!
UPDATE 130318
- Fixed a typo on oreoupdate, sorry for this guys!
UPDATE 120318
- Fixed the script for oreoupdate.
- Added version number 120318 for better overview of updates.
- Added MD5.
- Added firmware links for VTR-L09 and VTR-L29 version B360 provided from hwmt firmware database.
- Added screenshots of sd card directory.
- Edited the tutorial for unlocking bootloader and installing TWRP.
UPDATE 180319
- Added spoilers, for better overview
- Added pieupdate, for updating pie and downgrading to oreo
Greetings,
Jannomag
Can i lock the bootloader again after this Method?
Jannomag said:
Hi,
in this tutorial I will guide you how to upgrade from Nougat to Oreo and updating Oreo to newer version, when they are released.
Special thank are going to @mankindtw who wrote the script and @Blackball who released something similar for the P10Plus.
I just edited the script for working with the P10 to make it easier for you.
DISCLAIMER: I don't give any warranty. I tested this on 5 devices without any problems.
This Tutorial ist just for the Huawei P10 (VTR).
This tutorial has two versions:
Tutorial 1: Upgrading your P10 from Nougat to Oreo
Tutorial 2: Updating to a newer Oreo version.
Prerequisites: You need a sd card with minimum 4gb free space, formatted in FAT32.
Also you need an unlocked bootloader and TWRP installed.
Read first, then do it.
Backup, backup, backup - please, don't blame me when you notice data loss.
For everyone who don't know how to unlock bootloader and install TWRP, here's a short tutorial:
- Save all your data, make a backup. Unlocking the bootloader will cause a factory reset!
- Open the developer settings and enable the the "OEM Unlock" and "USB Debugging".
- Boot into fastboot mode by turning off the phone, connect it via usb to you pc and power it on while holding down Volume-Down until you see the white fastboot screen.
- Download the right TWRP version: TWRP 3.1.1-0 for Nougat by @OldDroid - TWRP 3.1.1 for Oreo by @Blackball.
- Flash the TWRP version - there are two different commands for Nougat and Oreo:
Nougat:
Oreo:
- Test it by turning off the phone with holding the power buttong until it's off and boot the phone with DISCONNECTED usb while holding Volume-Up.
Now the real thing:
Tutorial 1 - Upgrade Nougat to Oreo
Mention: I didn't loose any data after upgrading from Nougat to Oreo with this method. None of the guys who tested it noticed any data loss. BUT, no warranty for this!
BACKUP BEFORE YOU UPGADE!
- First you need to find your correct firmware for your model on the Huawei Firmware Database. This is not a rebrand tutorial!
Link: http://pro-teammt.ru/firmware-database
- When you found your version (example VTR-L29C432B360) find the row which containts "FullOTA-MF" and click on file list.
- You need three files: update.zip, update_data_full_public.zip, and update_full_MODEL_hw_[].zip (example update_full_VTR-L29_hw_eu.zip).
- When you downloaded all three files rename it after this:
update.zip stays.
update_data_full_public.zip stays.
update_full_MODEL_hw_[].zip to update_full_hw.zip.
- Download this rar archive.
- Extract the archive on your sd card - you should have a folder named "upgrade" on it. This folder contains three files: oreoupgrade.zip, VTR_RECOVERY_NoCheck.img and VTR_RECOVERY2_NoCheck.img.
- Put the three update zips you downloaded before inside the "upgrade" folder on sd card.
- Insert the sd into your phone and boot into TWRP.
- AGAIN: DO A BACKUP!
- Tap on Install, navigate to your sd card and into the upgrade folder.
- Tap on oreoupgrade.zip and install it.
- The phone will restart by itself - don't press any button!
- eRecovery will start and install the update - if you didn't do anything wrong, it should take around 2 minutes and the phone will do a reboot.
- If the phone won't reboot after update wait at least 5 minutes until you do it by yourself (I had this issue with only one P10).
That's it - you should have Oreo installed.
The script installs the original recovery, so TWRP is removed. The bootloader stays unlocked.
Tutorial 2 - Updating Oreo version
MENTION: This method isn't tested because of the lack of newer version. But it's the same thing as upgrading and should work. I can't give warranty for this. If there will be any problems with it, just contact me and we can work on a solution.
BACKUP BEFORE YOU UPDATEE!
- First you need to find your correct firmware for your model on the Huawei Firmware Database. This is not a rebrand tutorial!
Link: http://pro-teammt.ru/firmware-database
- When you found your version (example VTR-L29C432B360) find the row which containts "FullOTA-MF" and click on file list.
- You need three files: update.zip, update_data_full_public.zip, and update_full_MODEL_hw_[].zip (example update_full_VTR-L29_hw_eu.zip).
- When you downloaded all three files rename it after this:
update.zip stays.
update_data_full_public.zip stays.
update_full_MODEL_hw_[].zip to update_full_hw.zip.
- Download this rar archive.
- Extract the archive on your sd card - you should have a folder named "update" on it. This folder contains three files: oreoupdate.zip, VTR_RECOVERY_OREO_NoCheck.img.
- Put the three update zips you downloaded before inside the "updatee" folder on sd card.
- Insert the sd into your phone and boot into TWRP.
- AGAIN: DO A BACKUP!
- Tap on Install, navigate to your sd card and into the upgrade folder.
- Tap on oreoupdate.zip and install it.
- The phone will restart by itself - don't press any button!
- eRecovery will start and install the update - if you didn't do anything wrong, it should take around 2 minutes and the phone will do a reboot.
- If the phone won't reboot after update wait at least 5 minutes until you do it by yourself (I had this issue with only one P10).
That's it - you should have updated Oreo to a newer version.
The script installs the original recovery, so TWRP is removed. The bootloader stays unlocked.
If there are any issues with this notify me so we can work together to find a solution!
Thanks for testing @tangoalfa
Greetings,
Jannomag
Click to expand...
Click to collapse
Do we have to take FF IMEI check into account before applying this method?
MajaronM said:
Do we have to take FF IMEI check into account before applying this method?
Click to expand...
Click to collapse
FF IMEI check? Do you mean the unlock code generator by Huawei, where you need to enter product no. and IMEI? If yes, you have to do it, because you need to u lock the bootloader.
Jannomag said:
FF IMEI check? Do you mean the unlock code generator by Huawei, where you need to enter product no. and IMEI? If yes, you have to do it, because you need to u lock the bootloader.
Click to expand...
Click to collapse
In Firmware Finder app, you have to check if the update is compatible with your phone. The app check this with the Imei code of the phone. My phone is not yet approved with the actual b360. I was wondering if it was safe to install it.
I can confirm that it Works smoothly as silk!
I went from Romfromfuture B179 worked like a charm.
Thanks.
MajaronM said:
In Firmware Finder app, you have to check if the update is compatible with your phone. The app check this with the Imei code of the phone. My phone is not yet approved with the actual b360. I was wondering if it was safe to install it.
Click to expand...
Click to collapse
Don't use the app. Read the guide, use the Database via Webbrowser on your PC.
Jannomag said:
Don't use the app. Read the guide, use the Database via Webbrowser on your PC.
Click to expand...
Click to collapse
Thanks, I'll give it a try!
Thanks for the tutorial, i find the hwota method more straight forward and the steps are actually pretty much the same to achieve that goal.
LwannaCM said:
Thanks for the tutorial, i find the hwota method more straight forward and the steps are actually pretty much the same to achieve that goal.
Click to expand...
Click to collapse
The script does the same as HWOTA but I know some guys who had problems with HWOTA. Also HWOTA doesn't support the Oreo recovery command, so you have to modify the script by yourself, which isn't easy for everyone. For me this is easier than HWOTA, for others it's not, but you still can choose your favorite method.
I have a problem, I go to install the oreoupdate.zip with all the correct files in the folder but when the device reboots it goes back tot TWRP recovery with this error.
skolebolle said:
I went from Romfromfuture B179 worked like a charm.
Thanks.
Click to expand...
Click to collapse
Please, can you tell me what you do? Did you lost you data? I'm now on 179 FromFuture. Do you have Magisk and what rom you flash?
Sent from my Huawei P10 using XDA Labs
Hi!
I did not lost data at all. Just root. Followed the guide with a room that FF says is approved to my device. Did not restart after update thought. But restarted myself after some minute's.
Supergood rom with speed and good battery management.
Jannomag said:
The script does the same as HWOTA but I know some guys who had problems with HWOTA. Also HWOTA doesn't support the Oreo recovery command, so you have to modify the script by yourself, which isn't easy for everyone. For me this is easier than HWOTA, for others it's not, but you still can choose your favorite method.
Click to expand...
Click to collapse
There you are totally right. I never thought about it yet, because i wans´t curious (or stupid) enough to use the beta. So i wasn´t in the position to update oreo.
Just curious, did you use the hwota8 from mankindtw for this (https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-oreo-update-package-t3699522)?
I can also confirm it´s working, so thanks again!
If it´s ok for you, i will post your guide in my thread?
SeanTho said:
I have a problem, I go to install the oreoupdate.zip with all the correct files in the folder but when the device reboots it goes back tot TWRP recovery with this error.
Click to expand...
Click to collapse
If you read the error text, then you should be able to find a solution by yourself.
The update.zip is missing. Did you download the three update files and placed them into the oreoupgrade folder on SD card?
Jannomag said:
If you read the error text, then you should be able to find a solution by yourself.
The update.zip is missing. Did you download the three update files and placed them into the oreoupgrade folder on SD card?
Click to expand...
Click to collapse
Yes I followed the guide and made sure all the files were in the right place
SeanTho said:
Yes I followed the guide and made sure all the files were in the right place
Click to expand...
Click to collapse
Can you share a screenshot of you SD card content including content of oreoupgrade folder on it, please? I need to be sure. Is your sd card formattet to FAT32?
Jannomag said:
Can you share a screenshot of you SD card content including content of oreoupgrade folder on it, please? I need to be sure. Is your sd card formattet to FAT32?
Click to expand...
Click to collapse
Of course, here you go
And there we have it.
The folder name is wrong, it hast to be "oreoupgrade" and it should've this name when you extract it. The script looks for the path /sdcard/oreoupgrade/...