Database Info

Huawei Mediapad t3 7

Hello folks,
Bought a Mediapad T3 7 from Walmart recently. Has anyone found root yet? I tried all of the Kingroot, etc. APK's so far. Don't waste your time. Tried them all.
If our magicians here can find root, I'd love it!
Thanks,
Rich

Got the same request. Tried KingRoot and iRoot, cause you never know
I'd imagine it's coming one day or another. Tablet isn't that old yet.

Just a matter of somebody compiling twrp for it, I'd imagine..

I would love to know if any progress has been made. I need TWRP and an AOSP ROM. I love the devices look and feel, and its bluetooth operability. but absolutely DESPISE the UI and how it operates.

+1. Decent little tab but no built-in ext4 format for external SD, hoping for root. Getting it to run on stock android would be neat, too.

I tried the online root solutions-none of them work. Just tried Kingroot today and no good.

Same here I got a new huawei t3 10" great tablet by the way but no way I can root it.. I've tried all the Internet suggested ways and nothing seem to work at all but I manage to get the Device ID typing a code in the dialer.

Mercer99 said:
Same here I got a new huawei t3 10" great tablet by the way but no way I can root it.. I've tried all the Internet suggested ways and nothing seem to work at all but I manage to get the Device ID typing a code in the dialer.
Click to expand...
Click to collapse
hi, are you able to make calls on your T3 10? If yes, can you let me know your firmware details, thanks

buddimanv said:
hi, are you able to make calls on your T3 10? If yes, can you let me know your firmware details, thanks
Click to expand...
Click to collapse
Hi there, about that yes I can make phone calls with it I bought the Model with the 4G option (there is 3 models from the same Huawei tablet one of them is WiFi only and the other two can make phone calls) also I managed to unlocked the bootloader by using the device ID I got earlier and Huawei website.
mine is AGS-L09 model

Thanks Mercer99, appreciate it (for your device security, can you remove the image as this has your IMEI)- we have the same model, but different firmware.
AGS-L09C199B002 is “Saudi Arabia Oman Kenya Cameroon Jordan Qatar Ghana Android 7.0 EMUI 5.1” region.
AGS-L09C127B031 is “Greece Hungary United Kingdom Nonspecific Android 7.0_EMUI” . The dialer/calling function is disabled on this firmware - confirmed on Vodafone and EE network.
Is there any way you can extract the OEMINFO from your device and share it with us. This should enable me to debrand the phone if I can find your firmware (downloaded EUROPEAN version with Firmware finder already – so really need an European OEMINFO).
My phone is still locked to Vodafone so I am not sure whether I can flash the firmware or even need root to flash a different OEMINFO (bootloader is unlocked already).

Sorry buddimanv I would love to help but I don't know how

OEMinfo
Last time I did was with P9 Lite - changing from EE to European firmware using a tool (I think SRK Tool or “VNS-L21/22/23/31 [EU] Toolkit [0.0.0.12] All-in-One”) but it was rooted - seems like root is needed before anything. I think the process would be to change the firmware on tablet as well.....
I was hoping as bootloader is unlocked, we can retrieve OEMINFO from fastboot or something and debrand….would be good if anyone can clarify.

Possible Root Solution
Anyone prepared to test rooting method below?
How to install Magisk with ADB
How to install Magisk with ADB
Does not require the availability of custom recovery and root-access
1. Delete all other types of root-access and restore the partition image of the boot partition
2. Download Magisk v13.6 or later and download / unzip from the firmware partition image of the boot partition
3. Unpack the Magisk archive, put the boot image of the boot partition in the same folder, and rename it to boot.img
4. Rename the folder with the name corresponding to the architecture of your device (arm, arm64, chromeos, x64, x86), in magisk_inject
5. In the terminal, change the current directory to the folder with Magisk and run the following commands one at a time:
PHP:
adb shell "rm -rf / data / local / tmp / *"
adb push META-INF / com / google / android / update-binary common magisk_inject boot.img / data / local / tmp
adb shell "cd / data / local / tmp / magisk_inject; mv ../common/*.; chmod 755 *; sh ../update-binary indep boot_patch.sh ../boot.img; mv ../bin/ busybox busybox "
adb pull /data/local/tmp/magisk_inject/new-boot.img
adb shell "cd / data / local / tmp; rm -rf * .img magisk_inject / *. img update-binary bin common"
6. To flash the resulting boot partition image with the name new-boot.img
PHP:
fastboot flash boot new-boot.img
7. Download the system and make sure that Magisk Manager is installed and that its version corresponds to the version of Magisk. If not, manually install the correct version of Magisk Manager.
Click to expand...
Click to collapse
or follow original post
Via Magisk Manager (Only support v14.0+):
This method does not need root, and also does not require a custom recovery.
However, you MUST have a stock boot image dump beforehand, and also be able to flash the patched boot image, either through fastboot/download mode or ODIN
Install the latest Magisk Manager
If you're planning to flash the patched boot image through ODIN, go to Settings > Update Settings > Patched Boot Output Format, and select .img.tar. For normal users leave it as the default .img
Press Install > Install > Patch Boot Image File, and select your stock boot image file
Magisk Manager will now patch your boot image, and store it in [Internal Storage]/MagiskManager/patched_boot.img[.tar]
Flash the patched boot image to your device and reboot. Voilà!
Check whether Magisk Manager is installed and the version matches the latest one in the OP
If for some reason Magisk Manager isn't installed/upgraded automatically, please install it manually
Click to expand...
Click to collapse
Bootloader can be unlocked easily of course (code is given immediately) - here
I am tempted but trying to control myself as I don't have a copy of my existing firmware to revert back via dload method if something goes wrong. However, AGS-L09C199B003 firmware is available, so if it fails, I believe you can always go back to stock. I have a feeling this will work.

Took a risk and its rooted now - Magisk v14.0 installed fine and seems to be working (need to test further). Also, Vodafone unlocked the device now for me
Challenge now is to debrand so as to enable functions which has been disabled by Vodafone (namely calling).
Would appreciate if anyone can help - need OEMINFO from another region so as to change the firmware, especially European one or even other UK network who does not disable calling.

Could not contain myself…. In my quest to debrand so I can have a dialer/phone calling function, downloaded a firmware (either from FF Team or on the internet), tried flashing system.img file to see if it installs the dialer as it would not install extracted ones and it did not work. So tested with the boot.img and it did work but phone kept rebooting to eRecovery.
Restoring from TWRP (incomplete/untested) backup did not work. Can’t install any other regional firmware because of OEMINFO. eRecovery can’t find any firmware. The only thing – TWRP/Stock Recovery, eRecovery or bootloader!
Chatted with Huawei support and they won’t give me a link to download the firmware – want me to send for repair, which I don’t really want to – too much hassle and they may end up blaming me anyway….lol He agreed to upload one to their website if he can find one.
I would appreciate if anyone can give me an OEMINFO or link to EUROPEAN firmware with a dialer….. I think European one is AGS-L09C127B031CUSTC127D002 – would appreciate if anyone can share the file with me.

Mercer99 said:
Hi there, about that yes I can make phone calls with it I bought the Model with the 4G option (there is 3 models from the same Huawei tablet one of them is WiFi only and the other two can make phone calls) also I managed to unlocked the bootloader by using the device ID I got earlier and Huawei website.
mine is AGS-L09 model
Click to expand...
Click to collapse
More details and links for the bootloader please, I really need a tutorial-thanks.

dorpmuller said:
More details and links for the bootloader please, I really need a tutorial-thanks.
Click to expand...
Click to collapse
What a buncha bull**** the huawei site is. I got there and when I go to type the product id# in it brings up a calculator dialog with digits I don't even have on the calc.
Done with huawei. All night effing with this is enough. Won't deal with bizarre companies. I'll stick with my samsungs.
I tried... thanks for all of your responses.
Rich

dorpmuller said:
What a buncha bull**** the huawei site is. I got there and when I go to type the product id# in it brings up a calculator dialog with digits I don't even have on the calc.
Done with huawei. All night effing with this is enough. Won't deal with bizarre companies. I'll stick with my samsungs.
I tried... thanks for all of your responses.
Rich
Click to expand...
Click to collapse
I got stuck on the calculator part too. I didn't see the parenthesis buttons. But I turn the tablet on its sit. the view turned horizontal and i was able to see more buttons available. Horrible design for the calculator app.

Hi guys, can someone finally root this Tablet? I would also like to install TWRP to install an AOSP ROM.
Thank you!

Hi.
Did anyone succeed unlock Mediapad T3 7 bootloader ?
I have model BG2-W09 wifi only (European version). I have problem get product id
which is necessary part for bootloader unlock on Huawei site. Stucked to the calculator thing,
when i'll enter ()()1357946()()= on the calculator - i will get ERROR.
Contacted with the Huawei customer service for the help and got not nice answer:
We are unable to send boot loader code via email and can only be obtained through our website.
If you would want to unlock your phone, you should meet the following conditions:
1.Please register your Huawei ID in our official website on your phone.
2.Log in and logout your Huawei ID continuously for 14 days.
3.Each Huawei ID should not apply for the unlock code more than fifth time within 6 months.
Early people informed that email support works fast, but seems now the Huawei tightened terms.
Now i can expect 2 weeks everyday login to meet the requirements.
Some comments about tablet, maybe following helps someone.
One strange thing i've noticed with the tablet, it's not so easy bring up fastboot / recovery menu.
Pressing volume down + power brings up Chinese language test menu (8 options), nowhere to go with that,
pressing volume up + power brings up dialog with 3 options, "Reboot system now" or "Wipe data / factory reset" or "Wipe cache partition". Pressing by same all 3 buttons, volume up + volume down + power brings
up message that update not succeeded, update file not found on sd card. Also if you press only volume down and connect micro usb cable, it brings you to the Chinese test menu again. Also weird why European version tablet has at all Chinese test menu ?
I have triple boot desktop computer and i've downloaded 3 latest adb and fastboot platform-tools packages, for windows (using 10), mac and linux. With windows, using cmd i can start adb session, query device,
seems like everything works, when i'll try:
"adb reboot bootloader", device just reboots back to the main. Tried the same with the Ubuntu, same thing, adb helps finds the device, but when trying: "adb reboot bootloader" device just reboots into normal, not going into fastboot/rescue mode.
The thing is different with the mac (OSX 10.12), when i'll type to the terminal:
"adb reboot bootloader" the device rebooting into the fastboot mode.... and the terminal not responding any further, example when quering: "fastboot devices",
but having already fastboot mode activated on tablet and when rebooting desktop into windows 10 or ubuntu, i'm able using fastboot, tablet responds to the: "fastboot devices" or "fastboot oem get-bootinfo", even "fastboot oem unlock" responds informing about not valid key...
So far i'm able to put tablet into fastboot mode only using mac. Hope that's useful info for someone struggling
with same problems.
Unfortunately bootloader is still locked, problem finding product id, Huawei also did not help.
Huawei product id generator did not recognise Mediapad T3 versions.
Any ideas how to find product id or maybe someone can share the unlock code ?
Thanks in advance.

Xiaomi Black Shark Support/MEGATHREAD

Welcome!
This Megathread is to help bring the different threads together for the Xiaomi Black Shark (SKR-A0 or SKR-H0) since the xiaomi-black-shark tag is broken (at least for me it is). This will also serve as a one-stop shop for people who need general black shark support!
Disclaimer: You (the user) assume the risk for any bootloader unlocking, rooting, or any other modifying of your device. These can lead to phone's being bricked or boot-looped. We aren't to blame if the directions aren't followed to the T!
Tips before modding your phone
1. Stay organized! Make a folder for any files you download or data your backup so you don't lose anything important
2. Backup your user data onto your computer. It is guaranteed 100% of the time that your phone's data will be wiped when installing of uninstalling ANY of the modifications listed below. Unless you have been rooting and unlocking bootloaders for years, you don't want to skip this step.
Common ADB and Fastboot Commands
These are some commands you'll need to get to know:
adb devices: this shows what devices are currently connected to your computer
adb pull: this pulls a file from your phone and saves it to a location on your computer. You will need to specify the location of the file and the save location of the file
adb reboot bootloader: this reboots the phone into fastboot mode to use fastboot commands
fastboot devices: this shows what devices are connected to your computer in fastboot mode
fastboot boot filename.img: this boots the phone with using a image file of your choice
fastboot flash disk_partiton filename.img: this will flash an image file over the disk partition you want.
Example:
fastboot system system.img flashes a new system_a.img over the system parition of your phone's storage. This is where the main operating system is held on the phone.​fastboot reboot: reboots the phone
fastboot continue: boots the phone straight from fastboot into the system, not restarting the phone.
Unlock/Relock your Bootloader
WARNING: This WILL wipe your internal data
On Android, the phone must have an unlocked bootloader to enable some of the common modding features. These steps will unlock your bootloader.
Pre-requisites:
1. You will need the SDK Platform Tools downloaded onto your computer. This has the necessary adb and fastboot programs you will need in order to unlock your bootloader.
2. Enable Developer Options on the Phone
-Go to Settings -> About phone and tap the Build Number 7 times to enable Developer Options
3. Enable OEM unlocking
-For CN Version (SKR-A0):
Go to Settings -> Other Settings -> Advanced Settings -> Developer Options and Enable OEM unlocking. It will give you a warning pop up. Click yes to enable OEM unlocking.
-For Global Version (SKR-H0):
Go to Settings -> Developer Options and Enable OEM unlocking. It will give you a warning pop up. Click yes to enable OEM unlocking.
4. Enable USB Debugging. This lets you use ADB (Android Debugging Bridge) to send commands from your computer to the phone.
-For CN Version (SKR-A0):
Go to Settings -> Other Settings -> Advanced Settings -> Developer Options and Enable USB debugging.
-For Global Version (SKR-H0):
Go to Settings -> Developer Options and Enable USB debugging.
5. Boot into fastboot mode.
-Booting from the Phone:
Turn the Phone off
Press and hold the Volume Down Button
Turn the phone on while holding the volume down button
-Booting from the PC:
Connect your phone to your computer.
Go to where you downloaded the SDK platform tools. The folder name should be "platform-tools" and have "adb" and "fastboot" exe files in it.
Open a command prompt/terminal from that folder.
Run the command: adb devices
A pop up should show up on your phone. Click the checkmark next to "Always allow from this computer" and click ok. Your computer is now allowed to send commands to the phone.​
Now run the command: adb reboot bootloader
You should now be in fastboot mode!
To check if you're in fastboot mode:
Go to where you downloaded the SDK platform tools. The folder name should be "platform-tools" and have "adb" and "fastboot" exe files in it.
Open a command prompt/terminal from that folder.
Run the command: fastboot devices
If your device shows up then you're in fastboot mode! You should also see a line of text that says something like:
"Bootloader Locked"
"Bootloader Unlocked"
Unlocking your Bootloader:
1. If your phone says bootloader is locked:
While connected to your PC run the following commands:
-For SKR-A0
fastboot oem unlock
-For SKR-H0
fastboot flashing unlock
If there is a warning click to proceed with the unlock. THIS WILL WIPE YOUR DATA AT THIS TIME.
If your phone says bootloader is unlocked:
Skip this step!
Your Bootloader is now Unlocked!!
Relocking your Bootloader:[/size]
1. Boot into fastboot mode
2. Connect your phone to your computer
3. Run the Bootloader Lock command
3a. For Both Versions
fastboot flashing lock
WARNING: THIS WILL WIPE YOUR DATA.
Your bootloader is now Locked!
Rooting Using TWRP
Unlocked Bootloader Required!
Required files:
The latest Magisk Zip and APK files...it can be found here
A Computer with the latest SDK Platform tools
TWRP image file found at this thread
Do NOT download the installer.
1. Boot into fastboot mode and connect to your computer
2. Run the command: fastboot boot Name_of_twrp_file_.img
Replace Name_of_twrp_file.img with the name of the twrp image file you've downloaded for the blackshark
Tips:
If your screen is upside down, that's ok! Your touches will be in the same spot, the image is the only thing that's upside down.
On first boot, if TWRP is asking for a decryption password, you will need to wipe your data before going forward.
3. Move the Magisk Zip file to your phone's storage
4. On TWRP:
Click install -> Magisk.Zip file -> Swipe to confirm flash
5. After the install is complete: Swipe to reboot the phone
DO NOT INSTALL TWRP APP IF IT ASKS YOU TO
6. After the phone reboots, install the Magisk apk file
7. If you start the magisk app and it says Magisk is not installed, try rebooting your phone.
8. If you start the magisk app, and it asks to download extra resources, click ok.
You're now rooted!
Install GApps
Installing GApps should only be for the CN version!
You can find the directions and required files in this thread here
Factory Images
For the CN version (SKR-A0)
The factory images can be found on Google Drive here
For the Global version (SKR-H0)
[Guide] Restoring Black Shark 1 Global to Stock OTA bug fixed!
Using Project Treble (GSI) System Images!
What is Project Treble and GSI?
The Generic System Image (GSI) was added into Android 8.0 devices to enable OEM partners and developers to help with updating devices. Using an dual system approach (slot a and slot b) android phones can be updated seamlessly (without rebooting) and recover devices from a bad update.
Project Treble is an extension of this feature to enable developers to update their OS easier to new versions of Android! This includes *drum roll* the ROM commmunity!! So if your phone supports project treble and gsi (which the Black Shark does) we already have ROMs available to us!
The Downside to Project Treble Roms
Our Vendor File isn't compatible with Treble ROMs and we can't use other vendor files (as what I have seen so far) so these bugs will exist for now:
The S logo doesn't turn off. Stays Green lit.
You may not be able to increase screen brightness.
Fingerprint may not work on the Treble ROM.
Installing a Project Treble Rom
YOU WILL LOSE YOUR USERDATA. THERE IS NO GETTING AROUND THIS AS OF NOW.
Prerequisites:
Unlocked Bootloader on your phone and adb, fastboot, TWRP image and the most recent Magisk Zip on your computer.
For CN variants (SKR-A0) you may need to use the Global (SKR-H0) vendor and boot images. These steps were tested on using the Global Images
1. Choose your rom over here
2. Download the ARM64 A/B version of your rom of choice. The Black Shark supports Seamless Updates and it's based on the 64bit architecture (as are most modern phones).
3. Factory Reset your phone. You can do this either through the recovery or through the system settings.
4. Boot into bootloader mode on the phone and connect the phone to the PC.
5. Erase the system partition: fastboot erase system
6. Flash the new system OS: fastboot -u flash system system_image_file.img
7. Boot into TWRP from fastboot: fastboot boot twrp_file.img
8. Tap the DO NOT ALLOW SYSTEM MODIFICATIONS
9. Move the Magisk Zip file to your phone.
10. Click Install -> Magisk Zip -> Swipe to Install
11. Reboot the Phone
That's it! Your screen will be upside down during the media locking process (using a Disable Force Encryption file has not worked for me). Once your get to the setup page you may have to set it up with the screen upside down. THIS IS THE SAME AS HOW TWRP IS UPSIDE DOWN BUT THE TAPS ARE IN THE NORMAL SPOTS. If a warning comes up that's normal.
Android 9.0 Pie News!!!
https://forum.xda-developers.com/android/development/news-black-shark-2-features-coming-to-t3924703
How to Get CN Rom's Shark Space and MI Market onto Global ROM:
https://forum.xda-developers.com/an...-cn-shark-space-mi-market-blackshark-t3927854
Credits:
TWRP by @mauronofrio
Offical XDA Magisk Thread
@gilbert32 for factory global images

Placeholder
---------- Post added at 04:28 PM ---------- Previous post was at 04:25 PM ----------
Thank you for this thread.
I have a question to any Black Shark GLOBAL Owner:
If you have the Stock ROM, updated to the latest version, can you please contact me via private messages, or here.
I need your help to fix my phone to get OTA back running.
Meanwhile, i am figuring out a way to run Custom ROMs beside official ROMs.

gilbert32 said:
Thank you for this thread.
I have a question to any Black Shark GLOBAL Owner:
If you have the Stock ROM, updated to the latest version, can you please contact me via private messages, or here.
I need your help to fix my phone to get OTA back running.
Click to expand...
Click to collapse
No problem!
The CN version gets messed up on the OTA if your active boot is on B. It seems the OTA updates only work with active boot A. It also gets messed up obviously if the backup boot is not the same version. I had to make sure both system_a and system_b were on CN before updating system_a with the OTA.
Hope this helps.. obviously I'm a CN user, but you never know! :good:
gilbert32 said:
Meanwhile, i am figuring out a way to run Custom ROMs beside official ROMs.
Click to expand...
Click to collapse
I already have a linux environment in the works...

I've already successfully booted Lineage OS, OnePlus UI and Resurrection Remix, however they are full of bugs, and completely unusable.
I just need the latest OTA on Global version to make sure it is not related to vendor files/boot image.

gilbert32 said:
I've already successfully booted Lineage OS, OnePlus UI and Resurrection Remix, however they are full of bugs, and completely unusable.
I just need the latest OTA on Global version to make sure it is not related to vendor files/boot image.
Click to expand...
Click to collapse
Shoot me a dm... I'm trying to build without success..I'm also using Omni as a base. Two heads are better than one!

JengaMasterG said:
Shoot me a dm... I'm trying to build without success..I'm also using Omni as a base. Two heads are better than one!
Click to expand...
Click to collapse
AFAIK, it's gonna be pretty hard to build without having the kernel sources. Unless they release them soon, building for the device directly is gonna be a long shot.
However, checkout the treble device forums. You can download and flash roms from that section, and they will probably boot, but you'll have problems with auto brightness, random reboots, etc.
I still can't get the auto brightness and device specific stuff to work.

I have been boot the rros in my CN version,and the auto brighness have been fixed,I think the RRos can used comfortablely,and if you hava tencent QQ,you can join my tencent group,and the number of group is 947723325,welcome all people who like playing blackshark1/helo/2,welcome.

a8530516 said:
I have been boot the rros in my CN version,and the auto brighness have been fixed,I think the RRos can used comfortablely,and if you hava tencent QQ,you can join my tencent group,and the number of group is 947723325,welcome all people who like playing blackshark1/helo/2,welcome.
Click to expand...
Click to collapse
can you share how you did it here?

JengaMasterG said:
The Model version is set by the vbmeta.img files. You should be able to find those here under the factory image files section.
If you want any future support, ask for it in in the megathread so we can keep all the support in one thread :good:
Click to expand...
Click to collapse
Hello im from twrp thread
That after im installing cn version it's keep tell me the build version was global not chinese version and cant update because it's keep show me global build mumber
I have flash it on system A
But when i reflash to global ota update can run update on system b
Thanks

khususgw said:
Hello im from twrp thread
That after im installing cn version it's keep tell me the build version was global not chinese version and cant update because it's keep show me global build mumber
I have flash it on system A
But when i reflash to global ota update can run update on system b
Thanks
Click to expand...
Click to collapse
Can you show us a screenshot of your phone with this build number issue? Also, can you list what steps you took to flash the CN version on top of the Global version?
Normally OTA update won't work when switching the OS from Global to CN and vice versa unless you flash both slots to be on the same version.

JengaMasterG said:
Can you show us a screenshot of your phone with this build number issue? Also, can you list what steps you took to flash the CN version on top of the Global version?
Normally OTA update won't work when switching the OS from Global to CN and vice versa unless you flash both slots to be on the same version.
Click to expand...
Click to collapse
first im format userdata
then flash using twrp for slot a and b
boot > system > vendor
and disableencrypt
after that wipe/davilk
change to slot a
flash using twrp
boot > system > vendor> and flash disableforceencrypt
start system without install twrp
when im boot using slot A
it's shown internal error
i have send the attachment file hope you can help me, thanks

khususgw said:
first im format userdata
then flash using twrp for slot a and b
boot > system > vendor
and disableencrypt
after that wipe/davilk
change to slot a
flash using twrp
boot > system > vendor> and flash disableforceencrypt
start system without install twrp
when im boot using slot A
it's shown internal error
i have send the attachment file hope you can help me, thanks
Click to expand...
Click to collapse
Hmm ok. I haven't seen this issue before, but I also didn't upload the vbmeta.img file for the CN version. The vbmeta handles the model number and could be affecting the build number for your device as well. I have uploaded them to the CN stock files for you to try.

Reply:
Xiaomi Black Shark support are the thing which people need to know now a days world is evolving and things are changing rapidly.

JengaMasterG said:
Hmm ok. I haven't seen this issue before, but I also didn't upload the vbmeta.img file for the CN version. The vbmeta handles the model number and could be affecting the build number for your device as well. I have uploaded them to the CN stock files for you to try.
Click to expand...
Click to collapse
thanks for your help
after uinstall magisk using twrp, my phone can encrypt but only slot b
if i boot using slot a, the error still shown up so i cant encrypt my phone to get OTA update
so if i boot using slot b know the version shown CN version
but if i change to slot a it's show CN but after i choose update the os change to global version
if i update my blackshark localy using *#*#1027#*#* the package dosnt exist
but using this version i can access the light menu and change the color mode
-------
from slot B i cant install the OTA
i still find out how to install the OTA from slot A
i will give the update
thanks

khususgw said:
thanks for your help
after uinstall magisk using twrp, my phone can encrypt but only slot b
if i boot using slot a, the error still shown up so i cant encrypt my phone to get OTA update
so if i boot using slot b know the version shown CN version
but if i change to slot a it's show CN but after i choose update the os change to global version
if i update my blackshark localy using *#*#1027#*#* the package dosnt exist
but using this version i can access the light menu and change the color mode
-------
from slot B i cant install the OTA
i still find out how to install the OTA from slot A
i will give the update
thanks
Click to expand...
Click to collapse
Okay, if anything, I would start from scratch and by flashing the images only. Don't flash the decryption zip until the phone's fully OTA updated.

JengaMasterG said:
Okay, if anything, I would start from scratch and by flashing the images only. Don't flash the decryption zip until the phone's fully OTA updated.
Click to expand...
Click to collapse
okay i will try it, now i just backup boot system vendor vbmeta from slot b and replace it to slot a

khususgw said:
okay i will try it, now i just backup boot system vendor vbmeta from slot b and replace it to slot a
Click to expand...
Click to collapse
Yeah you can do it that way!

JengaMasterG said:
Yeah you can do it that way!
Click to expand...
Click to collapse
hello thanks for helping me, now i have done boot using slot A or Slot B with encrypted device,
after that i install the magisk to make sure magisk not installed in my system
then i check setting update via OTA it's always loop to download the OTA (same if i boot using slot A or Slot B)
then i download the OTA update via PC and extract to sd card and push *#*#1207#*#* for update manually but the package not listed.

khususgw said:
hello thanks for helping me, now i have done boot using slot A or Slot B with encrypted device,
after that i install the magisk to make sure magisk not installed in my system
then i check setting update via OTA it's always loop to download the OTA (same if i boot using slot A or Slot B)
then i download the OTA update via PC and extract to sd card and push *#*#1207#*#* for update manually but the package not listed.
Click to expand...
Click to collapse
Ok. You will need to start from scratch. So format your data, flash the a images over BOTH the a and b systems, boots, vendors, and vbmetas. Next, reboot and DO NOT INSTALL MAGISK. Magisk modifies the system and vendor packages so the OTA won't work. This should be ok, but lmk if you run into issues.

JengaMasterG said:
Ok. You will need to start from scratch. So format your data, flash the a images over BOTH the a and b systems, boots, vendors, and vbmetas. Next, reboot and DO NOT INSTALL MAGISK. Magisk modifies the system and vendor packages so the OTA won't work. This should be ok, but lmk if you run into issues.
Click to expand...
Click to collapse
after i try flash from scratch
and using old vendor b
still i cant do the OTA update

Lenovo S5 Pro - L58041 (Global) [2020.03.21]

Welcome to this little thread in which I'll provide every useful information about this device based on my and other users's experiences. If you know something, that I didn't mention, please reply to this thread in order to help out each other even more effectively. Thanks and pleasant reading!​
The Lenovo S5 Pro is a very decent mid-ranger with good specs and even better pricing. We all know, that chinese manufacturers tend to install bloatware on their products time to time. In our case, Lenovo didn't release a single update since 2018 Novemer to this device. It means, that it came out with Android 8.1 Oreo (2018 November Security Patch) and left untouched. This is even worse, than Meizu which is famous for it's neglecting policy of software updates for global users. Now, that we know all this, it's not a surprise, that we are here on our favourite developer forum.
*** General information | Links | Downloads | Credits ***​
The official global firmware is now saved and available (thanks to our forum member nikosddesign) here: download & link to the post
Everything you will possibly need (PC software, drivers, stock camera app, VoLTE modem etc...) is available in this Yandex Disk, you just have to navigate to each one. (Most of the content is in russian, since Yandex is the russian Google, but it's not hard to find the files you'll need).
The previous links and the following tutorials are only available, because suninterbru (from 4pda forums) and radiationofthenation provided these informations and the tutorials, also so much thanks to everybody on the 4pda forums, who provided useful information and files, большое спасибо!
Even though the bootloader unlock, TWRP install and rooting should not cause data loss, be careful and create a backup. You can back up only your files and data or your whole ROM, it's up to you.
Please note, that after you've unlocked your bootloader, everytime your reboot or turn on your phone a warning will pop up during the boot process for about 1 second. On Android 9.0 Pie vendor the message pops up for about 5 seconds. The warning is about the side effects of modifying the system software and it also says, that it is not recommended to store any personal data on your device anymore. Please ignore this message, since it's only popping up, because manufacturers usually don't like, if you modify your device.
Pro tip: If you keep pressing your power button for a little longer you can skip the alert and boot faster.
*** Bootloader unlock ***
Please note, that your warranty will become invalid/void after you unlock your bootloader or root your device.​
0. In your device's developer settings enable bootloader/OEM unlock and USB debugging.
1. Visit the official ZUI bootloader unlock website.
2. Enter your IMEI1 number in the first field. (You can find your IMEI numbers in Settings\About or in the dialer enter: *#06#).
3. Enter your serial number in the second field. (You can find your serial number in the fastboot menu). The one in the settings is not good in this case! (To access the fastboot menu, turn off your phone, then press the power button and after you see your screen light up, immediately press the volume down (-) button or while it's turned on and USB Debugging is enabled, simply type in the terminal/cmd ,,adb reboot bootloader").
4. In the next field enter your email adress. (Please note, that Tutanota won't work, Gmail is recommended or other not secure email providers).
5. Enter the verification numbers in the last field.
6. Tick the checkbox.
8. Click on the blue button.
7. Now check your inbox and/or spam folder, because Lenovo just sent you your custom sn.img, only for your phone.
8. Save the sn.img to your PC and install ADB drivers system-wide. (Thank you Snoop05 for your work)!
9. Open a terminal/cmd on Windows. You should be in the same directory, where your sn.img file is, with the terminal. To change directories type ,,cd your directory goes here" and hit ENTER.
10. Run the following commands:
- adb reboot bootloader
- fastboot flash unlock sn.img
- fastboot oem unlock-go
11. Congratulations! Your bootloader is now unlocked!
*** TWRP Recovery ***​1. Download the .img file from here.
2. The steps are similar to the bootloader unlocking:
- adb reboot bootloader
- fastboot flash ,,downloaded" .img
- After the flashing is done DON'T reboot to the system, instead navigate to the ,,Reboot Recovery or Recovery Reboot" option and select it. (Volume keys and power key - you know the drill) This will ensure, that the TWRP Recovery doesn't get ereased on reboot(s)!
3. After you've successfully rebooted into TWRP, you should root your device with Magisk, to prevent the recovery erasure!
*** ROOT ***​1. The good old SuperSU is no longer in the picture, but don't worry a new player is in the game. Download Magisk from here. (Thank your for your work topjohnwu)!
2. After you've downloaded the flashable .zip copy it to the main directory/root of your device.
3. Reboot to TWRP.
4. Click install, select the flashable .zip file.
5. The installation process should start.
6. Reboot, after finished.
7. Check if Magisk Manager is installed or not, if yes tap and update it.
8. If you did not succeed, please check the Magisk topic for solutions or reply to this thread.
*** Factory reset | Stock ROM | Unbrick | LOST IMEI/PERSIST/EFS | QCN BACKUP/RESTORE ***
!!! NEVER EVER TICK ,,ERASE ALL BEFORE DOWNLOAD" IN QFIL, OTHERWISE YOU WILL LOSE YOUR IMEI AND THE ABILITY TO CONNECT TO MOBILE NETWORKS !!!​
If you accidentally clicked on that option you will have to restore someone elses QCN backup. (It will not work, if you backup your own QCN and rewrite your IMEI and restore it, so do not waste your time with that)! Luckily, a member of the 4PDA forums published their qcn backup. (большое спасибо geepnozeex)! QCN backup for Lenovo S5 Pro. (I modified the link, because the original one is no longer valid)
1. Download the linked QCN file.
2. Make sure, that you are on one of the Stock ROMs, however the recommended ROM is this one.
3. You will have to be rooted to put your device in diagnostics mode. To do that, follow this tutorial.
4. You will have to edit the QCN file with HxD, in order to write your own IMEI into.
5. Open the file with HxD and search for 08 8A 76 06 06 14 57 95 32. This is the IMEI 2. You will have to insert your IMEI 2 from the box here, but first you will have to convert it into Hexadecimal numbers.
6. Convert your IMEIs into Hexadecimal numbers here.
7. You will have to rewrite and insert your values insted of the previous one.
8. Search for 08 8A 76 06 06 04 67 98 72. This is IMEI 1. Convert your IMEI 1 into Hexadecimal numbers, too and replace.
9. Save the file (Ctrl + s)
10. Open QFIL and click on Tools, then QCN Backup/Restore.
11. Choose the QCN file, you wrote your IMEI into.
12. Click on Restore QCN.
13. There is a chance, that the process/progress bar won't finish till the end. No problem, just reboot to EDL mode through TWRP/Advanced and restore the recommended stock ROM.
14. You should have everything working fine, now.
To factory reset or unbrick your device, follow this tutorial on 4PDA. [Don't panic you don't have to know russian, just follow the instructions on the pictures! To see the pictures, click on the bold text.] ,,(спойлер (+) (Инструкция по прошивке)" ~ or ~ Download any of the previously linked STOCK ROMs to your device's main folder and flash them through TWRP. Most of them are in flashable .zip formats and should work well. A simple factory reset in TWRP is recommended before installing any of the ROMs, be careful this action will erease your data from your phone!
(Please note, that most of the time you'll have to use the QPST/QFIL method, because the flashable .zip files always expect a specific vendor version, usually a lower one, so you can upgrade with flashable .zips, but possibly can't downgrade, so you have to use QFIL)!
*** GSI custom ROMs ***
Our device is arm64-aonly, so please only use according GSIs. Note, that I will link only those GSIs, which are booted successfully on my device!​
~ phhusson's official GSI list: here
~ phhusson's AOSP GSI (Android Open Source Project): here
~ developerluke's ExpressLuke GSIs: here
~ eremitein's CAOS GSI Project: here
~ eremiten's LOSQ GSI Project: here
~ igors1974's Amber GSIs: here
~ tunasahinn's and yek4perf's Tunahan's GSI builds: here
~ mrsshunt3r's albus-gsi: here
Note, that you should keep up with the developments and update your system, if needed! These are just a few GSIs, that I've tested personally on my phone, but you can always keep up with the latest news and try new GSIs out, thanks to phhusson's official GSI list!
*** How to flash an Android 10 GSI ***​
1. Download the latest custom phh-magisk from here. (Thank you developerluke and phhusson)!
2. Download the latest Disable_Dm-Verity_ForceEncrypt from here. (Thank you Zackptg5 and others)!
3. Download your desired GSI.
4. You can flash from an USB-OTG flash drive or from the storage of your phone. (I personally have a dedicated USB for this purpose).
4.1 If you are coming from stock ROM you will most likely need to Format Data in this step, because the Disabler won't be able to decrypt the data and, that will cause a stuck at the boot logo!
4.2 Reboot Recovery
5. In TWRP perform a normal factory reset
6. Flash Disable_Dm-Verity_ForceEncrypt. (Cache wipe is optional).
7. Flash your GSI image.
8. Format Data (Skip this step if you already did this in 4.1)!
9. Reboot Recovery (Skip this step, too if you already did this in 4.2)!
10. Flash Magisk-phh
(11. Wipe cache/dalvik).
12. Reboot System
13. Enjoy!
*** Possible GSI bugs ***
Please note, that bugs can differ/vary on different GSIs, the numbers are not fully accurate!
​
1. The default camera app will work, however it doesn't support HDR, panorama or portrait modes. It also can't record in 4K resolution. Freezing is also possible. ~ 50%
2. First time, when you open the camera it'll stuck on loading, but after you go back and open it again it will work flawlessly. ~ 50%
3. No audio/microphone during phone calls. ~ 15%
*** Guaranteed GSI bugs*** ​1. The infrared face unlocking will not work, only fingerprint authentication is working. ~ 100%
2. You won't be able to charge your device while it's turned off, after you plug it in, it will automatically boot up. ~ 100%
3. Auto brightness. ~ 100% (There is a fix for auto brightness below)!
*** Camera fix (GSI) ***
(If you get ,,serious camera error" or your camera freezes on HDR)​
1. Download a custom camera app, where you can manually adjust the ISO level.
2. With OpenCamera, for example you have to adjust ISO to 800 and never above, because your camera will freeze!
3. So, always keep ISO 800 or under. With these settings even HDR shots are working!
*** Auto brightness (GSI) ***​1. Download framework-res__auto_generated_rro.apk from this thread.
2. Follow the instructions, which are described in this post. (You will need to have root to use ,,su" commands).
3. Thank you MishaalRahman and kAs1m for the apk and the instructions!

Twrp disappears when restarting
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.

kcire_eae said:
Help, twrp disappears when restarting. After installing it by: "fastboot flash recovery trwp.img". right there I start it with the "Vol + Power" keys and it starts correctly but when you turn it off and back in, "stock recovery" appears again. I also installed it again using the same twrp, but it disappears again.
Click to expand...
Click to collapse
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.

Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
It didn't work, given: "fastboot: usage: unknown reboot target recovery" Sorry for the long time to answer, I only have mobile data, and from this same mobile I answer, and I use google translator, I'm from Mexico.

Halwer said:
Hello, please don't reboot after sending the recovery image to the phone. Execute the:" fastboot reboot recovery " command. Now it is going to work.
Click to expand...
Click to collapse
Foto

kcire_eae said:
Foto
Click to expand...
Click to collapse
Well, it looks good. Maybe only " reboot recovery " is enough.

Halwer said:
Well, it looks good. Maybe only " reboot recovery " is enough.
Click to expand...
Click to collapse
It didn't work, friend, but I appreciate the help.

kcire_eae said:
It didn't work, friend, but I appreciate the help.
Click to expand...
Click to collapse
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?

Halwer said:
I'm sorry. Do an internet search and check related TWRP forums for solutions for this specific issue. For me everything is working fine. Are you sure you unlocked your bootloader first?
Click to expand...
Click to collapse
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.

kcire_eae said:
Help, I did the following and I no longer start my mobile:
-fasboot flash recovery twrp.img.
-fasboot flash boot twrp.img.
-fasboot reboot.
now just start twrp even if restart restart twrp again, in the twrp browser my sdcard files are shown, maybe you can still help me please.
Click to expand...
Click to collapse
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.

Halwer said:
You should not have flash the recovery image to the boot partition. These partitions are not the same, be careful! Now you can save your data from TWRP via MTP connection to your computer. After that restore your phone with QPST to the latest pie ROM or to the oreo ROM from yandex. The oreo ROM is flashable from recovery, it is easier.
Click to expand...
Click to collapse
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:

kcire_eae said:
Is it possible to just flash the boot partition (boot) again, if I get the boot.img from another rom?
I don't want to lose the stock rom:crying:
Click to expand...
Click to collapse
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.

Halwer said:
Maybe you can try to download a ROM file, extract it and flash the boot image, but I'm not sure if it is going to work.
Click to expand...
Click to collapse
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.

kcire_eae said:
I'm going to try, and even,
on this page there are android 9, will it be true?
"https: // mirrors.lolinet.com/ firmware / lenovo /l58041/"
but first I will do it with the "O" stock, which you mention here.
I hope it will work again.
Click to expand...
Click to collapse
You should do the oreo version, if your were on the global oreo ROM. After that you can try the pie version, if nothing works don't worry you can do a backup of your data from twrp to your computer and flash a custom ROM or the chinese Pie version, which is recommended. With root access you can easily debloat the chinese ROM and with AdAway you can disable all communications pointing to chinese servers or websites. I also found these. Maybe you can give them a try.

After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" .
prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata".
rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"

kcire_eae said:
After a few hours I was finally able to install the "Chinese stock rom", although I struggled, since the files of the "rom" of the l58041 do not quite coincide with the "stupdroid" tutorial and some files have two different versions, something like that:
here I chose the "ddr" prog_emmc_firehose_xxxx_ddr.mbn (.elf). prog_emmc_firehose_xxxx.lite.mbn (.elf).
here I chose the "retain_userdata" rawprogram0.xml. rawprogram0_retain_userdata.xml.
and in qfil "Flat Build", however I don't know if it was the right thing because at the beginning I was asked for a password ("but that's another topic").
To add a language (without root), use local more apk.
"https: // c. mi. com / thread-2098669-1-0.html"
To root the "radiationofthenation" thread worked me.
"https:. //forum .xda-developers . com/general/help/lenovo-s5-pro-root-global-firmware-help-t3895643/page2"
Click to expand...
Click to collapse
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.

Halwer said:
I'm glad it is working for you now. Yes, you are right the tutorials flap at some points, but there are other tutorials which you can follow and make it work. For the first time I was struggling with the restoration, too. You will see, that the chinese ROM is quite good, you just have to uninstall the bloatware and disable spying DNS requests.
Click to expand...
Click to collapse
Ohh, explain more about spying. And also if you know something about the message that Android told me when I start. I remember that I flashed twrp.img using "fastboot", and when I asked for a password to decrypt, it only allowed me to clear cache and dalvit cache (I did wipe), and when I started again I showed a message saying that I was encrypting and a percentage, just here, I interrupted the process by turning off the cell phone, and flashed again with qfil (download). So when I start I just remember that I said something about the cell phone being restored and then I could restore the copy with my Google account. So what I think is that when the message of "TO START ANDROID ENTER YOUR PASSWORD" is displayed, it may work to interrupt or perhaps to put the incorrect password many times to automatically reset or also choose "rawprogram0.xml" in qfil (but I did not dare because it deletes it the information related to the imeil and the signal or at least that says some comments ). Now there is only one who can interpret what happened and to have clearer the restoration process, the rom seems to me very much the problem of the language is solved with "more local", I am from Mexico (At & t).

good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g

nikosddesign said:
good morning i have good new
i have been backing up the global rom
just wants to go a long time it is super compressed 3.5giga and it is regular size 10.6 g
Click to expand...
Click to collapse
Thank you, I'm sure some people will find it very useful!

Hello
it's about 4gigabyte have to be patient.
i have very bad internet connection...

Root LG Velvet (LM-G900EM)

Finally got root on LG-Velvet LM-G900EM
Here is how i did.
I know...this is finally little bit complicated, but i dont want to copy something that possibly affects copyrights or other stuff.
Here is all that i've learned and done.
So you should be able to root also.
Prerequisites:
(allways have a valid backup)
- Unlocked LG-Velvet-Bootloader (on android device)
- Installed Python (on pc):
https://www.python.org/
- Unpacked Steadfast kdz-tools (on pc):
https://github.com/WildOne69/kdztools
(Modify the undz.py: Put a # in line 26. This should look like this:"#import zstandard as zstd"
Otherwhise you will get an error:"ModuleNotFoundError: No module named 'zstandard'"
- Downloaded Velvet Stock-Rom (kdz) (on pc)
http://lg-roms.com/lg-firmware/lmg900em/g900em10c/9081
1. Download the kdz-rom from lg-roms (on pc)
(this uses a special download-tool which may be spain)
Finally you should have something like:
G900EM10f_00_0716.kdz
2. Extract a dz-file from the kdz-file. (on pc)
Go to the directory where you've stored the kdz-tools.
example:
python unkdz.py -f G900EM10f_00_0716.kdz -x
(this gains something like G90010f_0_user-signed-ARB0_COM1_EU_OP_0716.dz in a subdirectory)
3. Extract the boot.img from the extracted dz-file. (on pc)
example:
python undz.py -f c:G90010f_0_user-signed-ARB0_COM1_EU_OP_0716.dz -s 40
..now you've got a boot_a.image hopefully in a subdirectory.
This is the original boot.img
4. Copy the boot.img to your mobile. (from pc to android device)
5. Run Magisk and patch the extracted boot.img (on android device)
6. Copy the magisk_patched.img to your computer again. (from android device to pc)
7. adb reboot bootloader (on pc)
Keep in mind that the Velvet is an A/B device, so we need to flash the boot.img twice.
8. fastboot flash boot_a magisk_patched.img
(on pc)
9. fastboot flash boot_b magisk_patched.img
(on pc)
10. fastboot reboot
(on pc)
11. Open Magisk and pray that you've root.
(on android device)
Have fun.
BR
Mike
PS:
Be careful locking your bootloader afterwards. As i've observed locking the bootloader again resets the mobile back to factory-defaults...so all your work has been gone.
I'm not responsible if you brick your device or it takes harm in any case.
Updates: As LG launched updates twice meanwhile i was forced to patch the boot-partitions again.
Simpliest way to do the updates with root:
- Start the update with LG-Bridge.
- After the download of the new KDZ is complete copy it out of the temp-directory (to extract the boot_a.img later)
- Do the phone-update with LG-Bridge. (Now your phone is in an unrooted state again)
- proceed with steps 2-11
- Jobs done (Actual android-version rooted)

Is there anyway to get this to work with lg-G900UM

Catrock31 said:
Is there anyway to get this to work with lg-G900UM
Click to expand...
Click to collapse
I think the way is the same.
Just depends on the possibility to get an bootloader-unlock file fron LG or not.

MikGx said:
I think the way is the same.
Just depends on the possibility to get an bootloader-unlock file fron LG or not.
Click to expand...
Click to collapse
Guys, can you upload the stock ringtones ?
Thks

Nice work OP. Works like a charm. I remember the pre-Nougat days when rooting an Android device was, for the most part, a simple affair. Nowadays, with A/B partitions, Forward Error Correction (FEC), system-as-root, etc., rooting is tedious to say the least. Nice job figuring this one out. :good:

Hi!
The undz.py returs this error message :
File "undz.py", line 173
if cmd.batchMode:
^
TabError: inconsistent use of tabs and spaces in indentation
Can you help?

Bandetos said:
Hi!
The undz.py returs this error message :
File "undz.py", line 173
if cmd.batchMode:
^
TabError: inconsistent use of tabs and spaces in indentation
Can you help?
Click to expand...
Click to collapse
Just a fast shoot before quittin the day:
Kdz-filename you downloaded is exactly the same as i wrote? (If you got a newer version the kdz-riddle would start again...as this unkdz/undz project is some years old and discontinued.)
@the 1st step this error looks like another dz or corrupt dz-file. (Give the download and kdz unpack a 2nd try?)
Another guess could be that you maybe choose another slice (-s number)?
There are 2 boot-images as velvet is an a/b device.

MikGx said:
Just a fast shoot before quittin the day:
Kdz-filename you downloaded is exactly the same as i wrote? (If you got a newer version the kdz-riddle would start again...as this unkdz/undz project is some years old and discontinued.)
@the 1st step this error looks like another dz or corrupt dz-file. (Give the download and kdz unpack a 2nd try?)
Another guess could be that you maybe choose another slice (-s number)?
There are 2 boot-images as velvet is an a/b device.
Click to expand...
Click to collapse
it doesn't working
maybe attach the boot.img file

if you check the version of python you got:
Python.3.8_3.8.1776.0
?
to be honest...dont want to take care on a file-store in the internet.

LG launchned a new FOTA...and a new kdz.
Turned out that flashin the old magisk_patched.img (boot.img) extracted from the old kdz causes UI-performance problems if you reflash it after update.
Usually magisk-SU should work if you prevent reboot after install the FOTA and then flashing magisk in the newest app version to the inactive slot.
Failback: if you run into this performance-issues, you can use lg bridge (!!!hopefully have an existing LG-Switch-Backup!!!) to set back your Velvet to defaults.
You can copy out the new kdz during the extraction-phase of LGBridge (so you dont need to download it extra) from your win-userprofile (c:\users\username\AppData\Local\LG.....\Update(something)\*.kdz
...and extract the new boot.img as described in the first article.
Install magisk and root the boot.img also as described first.
Then restore your latest LGSwitch backup and all is fine.
At the moment im working on a twrp-solution based on the work of mauronofrio from twrp-team. I can boot TWRP (based on avicii .13) but i am only able to backup (metadata and super).
Not gettin userdata and boot(recovery). Thi is hard as the velvet seems to be treble&A/B.
...i'm no dev...just like to play lego. )

Either way, it's good to see that we at least have a few people trying to figure out things with this device. Honestly, I still carry my Redmi Note 7 Pro with me every day because of how much I miss being able to download a custom rom etc.
MikGx said:
LG launchned a new FOTA...and a new kdz.
Turned out that flashin the old magisk_patched.img (boot.img) extracted from the old kdz causes UI-performance problems if you reflash it after update.
Usually magisk-SU should work if you prevent reboot after install the FOTA and then flashing magisk in the newest app version to the inactive slot.
Failback: if you run into this performance-issues, you can use lg bridge (!!!hopefully have an existing LG-Switch-Backup!!!) to set back your Velvet to defaults.
You can copy out the new kdz during the extraction-phase of LGBridge (so you dont need to download it extra) from your win-userprofile (c:\users\username\AppData\Local\LG.....\Update(something)\*.kdz
...and extract the new boot.img as described in the first article.
Install magisk and root the boot.img also as described first.
Then restore your latest LGSwitch backup and all is fine.
At the moment im working on a twrp-solution based on the work of mauronofrio from twrp-team. I can boot TWRP (based on avicii .13) but i am only able to backup (metadata and super).
Not gettin userdata and boot(recovery). Thi is hard as the velvet seems to be treble&A/B.
...i'm no dev...just like to play lego. )
Click to expand...
Click to collapse

Catrock31 said:
Is there anyway to get this to work with lg-G900UM
Click to expand...
Click to collapse
Hello.
I have a LG from Freedom Mobile.
Does this procedure work on their phones?
I'd like to use the dual sim capabilities.

JackTheMan18 said:
Hello.
I have a LG from Freedom Mobile.
Does this procedure work on their phones?
I'd like to use the dual sim capabilities.
Click to expand...
Click to collapse
I did that on an LM-G900EM. (No dual sim)
As i did it just usin the stock-rom, theoretically dual sim capability shoudnt get lost.
All this stands and falls with the possibility to unlock the bootloader.
If LG provides an unlock-code the rest should work.

Good
Very good, you are very good. As a LG velvet Chinese user, I sincerely hope that you can develop a ROM compatible with China’s 5G

BruceLee131 said:
Very good, you are very good. As a LG velvet Chinese user, I sincerely hope that you can develop a ROM compatible with China’s 5G
Click to expand...
Click to collapse
There was no development.
In my 1st article i just described how to extract, rooted and flashed the original stock boot.img
This should be possible for everybody who:
- got the bootloader unlock code from lg
- isnt afraid to flash boot.img to the mobile
BR
M.

MikGx said:
Just a fast shoot before quittin the day:
Kdz-filename you downloaded is exactly the same as i wrote? (If you got a newer version the kdz-riddle would start again...as this unkdz/undz project is some years old and discontinued.)
@the 1st step this error looks like another dz or corrupt dz-file. (Give the download and kdz unpack a 2nd try?)
Another guess could be that you maybe choose another slice (-s number)?
There are 2 boot-images as velvet is an a/b device.
Click to expand...
Click to collapse
I'm also getting this error. I did try a second time following your steps to a tee and still getting the same error.

MikGx said:
There was no development.
In my 1st article i just described how to extract, rooted and flashed the original stock boot.img
This should be possible for everybody who:
- got the bootloader unlock code from lg
- isnt afraid to flash boot.img to the mobile
BR
M.
Click to expand...
Click to collapse
Hi, I have bought LG Wing. I have entered into Developer Mode and I have activated OEM unlocked option. So do I need a bootloader unlock code? Can I root LG Wing with your instructions?

How did you get adb to recognize your device once you put it in download mode?

MikGx said:
I think the way is the same.
Just depends on the possibility to get an bootloader-unlock file fron LG or not.
Click to expand...
Click to collapse
I'm sorry if this is a dumb question, but if it isn't possible to get an unlock code for the G900UM (U.S. model), is there a way to gain SU status/root without unlocking the bootloader? I'm sure there's no exploit to unlock the bootloader without LG code, but I saw in some other threads (different makes/models) discussion of gaining SU via fastboot without unlocking the bootloader? So if my main concern is knowing everything that is on my phone and eliminating privacy/security vulnerabilties, can I gain SU status without unlocking the bootloader?

MikGx said:
There was no development.
In my 1st article i just described how to extract, rooted and flashed the original stock boot.img
This should be possible for everybody who:
- got the bootloader unlock code from lg
- isnt afraid to flash boot.img to the mobile
BR
M.
Click to expand...
Click to collapse
I got the unlock.bin file from LG.
I'm not afraid to flash any partition...
it's simply impossible to flash twrp-3.4.0-g900em-dom133.imgù
writing 'recovery'...
FAILED (remote: Cannot flash this partition in unlocked state)
And even boot with that recovery
downloading 'boot.img'...
OKAY [ 0.718s]
booting...
FAILED (remote: BootImage is Incomplete)
Finally i'm not able to extract boot.img form LG kdz stock rom

Question Rog phone 5 Rom WW

I have a Rog phone 5 Tecent moved rom WW, but it occurs error of losing fingerprint, and not update FOTA. Can you help me? I want move Rom WW to CN Tencent, fix error fingerprint.
If there is a video tutorial that would be great. Tks ad.

Edit: I made it a separate thread
RAW Firmware Collection and Guide
All fastboot / adb commands require using the side USB-C port https://developer.android.com/studio/releases/platform-tools.html#download Make sure you have fastboot installed Add platform tools to PATH (post 2) Make a backup of anything...
forum.xda-developers.com