All fix avilable (no network solved)
Watch it carefully do it step by step as showen in my video you will never brick if you follow my video
All required files are in the video description
This guide Tested on the firmware (20e ,20c,20d) (if you didn't see your firmware don't worry leave a command , I will help you ! )
How to check the frimware:
* Go to Settings - >System -> About phone -> sofware version ( eg: V20e-IND-XX so use 20e rootboot file)
All required files are in the video description
watch it in 720p only 40 mb
subscribe for more lg g8x content !!!
If any issue let me know i will help you with that
I've rooted with Magisk and root seems to be working. I then restored the abl_a back to abl_a and abl_b partition. Now I keep getting system UI crashes and the phone app freezes when I try to make a call.
cyr4n0 said:
I've rooted with Magisk and root seems to be working. I then restored the abl_a back to abl_a and abl_b partition. Now I keep getting system UI crashes and the phone app freezes when I try to make a call.
Click to expand...
Click to collapse
looks like your device is not a 20e firmware (audio not work,cant make a call ,ui crash) i will help you to root just share the boot_a img (stock)
[email protected] said:
looks like your device is not a 20e firmware (audio not work,cant make a call ,ui crash) i will help you to root just share the boot_a img (stock)
Click to expand...
Click to collapse
Hello,
I have the exact same issues. Didn't notice the Indian variant on Magisk in the Root guide, and ended up with an unusable phone.
You say boot_a image stock, do you mean from before the whole process? I unfortunately didn't back up this particular partition..
Boot.zip contains the boot.img file pulled from the kdz of the US G850 20b.I don't know if this is useful, but I got it...
ReadData_.ufs_Lun4_...... is the boot_a file pulled from my phone after I turned it into a buggy mess I also don't know if this helps, but I do need help getting my phone working again if you'd be so kind. This is NOT the boot_b flashed as boot_a like mentioned in the video.
rainbowtuba said:
Hello,
I have the exact same issues. Didn't notice the Indian variant on Magisk in the Root guide, and ended up with an unusable phone.
You say boot_a image stock, do you mean from before the whole process? I unfortunately didn't back up this particular partition..
Boot.zip contains the boot.img file pulled from the kdz of the US G850 20b.I don't know if this is useful, but I got it...
ReadData_.ufs_Lun4_...... is the boot_a file pulled from my phone after I turned it into a buggy mess I also don't know if this helps, but I do need help getting my phone working again if you'd be so kind. This is NOT the boot_b flashed as boot_a like mentioned in the video.
Click to expand...
Click to collapse
The one you provided was not help ,Give me the stock boot_a img (download the whole kdz and extract the boot_a.img)
rainbowtuba said:
Hello,
I have the exact same issues. Didn't notice the Indian variant on Magisk in the Root guide, and ended up with an unusable phone.
You say boot_a image stock, do you mean from before the whole process? I unfortunately didn't back up this particular partition..
Boot.zip contains the boot.img file pulled from the kdz of the US G850 20b.I don't know if this is useful, but I got it...
ReadData_.ufs_Lun4_...... is the boot_a file pulled from my phone after I turned it into a buggy mess I also don't know if this helps, but I do need help getting my phone working again if you'd be so kind. This is NOT the boot_b flashed as boot_a like mentioned in the video.
Click to expand...
Click to collapse
Or you can flash the kdz back (make sure you are using the correct KDz
How do I flash the KDZ? I have tried pushing it with LGUP but it hasn't been successful.
Also, I've extracted the kdz with LG Firmware Extract but I'm not seeing a boot_a.img. The closest thing I see is boot.img_257490
I think I'm stuck now. I tried to use LGUP but now I can't even boot into anything but fastboot. Now it fails the security check and goes into fastboot. Unlocking the bootloader doesn;t work now and it's stuck on locked...
BTW, I renamed the boot.img_257490 and tried to flash it via fastboot but the error was "sending boot_a - too large" so I think this IS the boot_a. Not that it may matter for me at this point lol
rainbowtuba said:
How do I flash the KDZ? I have tried pushing it with LGUP but it hasn't been successful.
Also, I've extracted the kdz with LG Firmware Extract but I'm not seeing a boot_a.img. The closest thing I see is boot.img_257490
I think I'm stuck now. I tried to use LGUP but now I can't even boot into anything but fastboot. Now it fails the security check and goes into fastboot. Unlocking the bootloader doesn;t work now and it's stuck on locked...
BTW, I renamed the boot.img_257490 and tried to flash it via fastboot but the error was "sending boot_a - too large" so I think this IS the boot_a. Not that it may matter for me at this point lol
Click to expand...
Click to collapse
wait ill share you my lg up and kdz extractor.
and are you sure you downloaded the correct one?
[email protected] said:
wait ill share you my lg up and kdz extractor.
and are you sure you downloaded the correct one?
Click to expand...
Click to collapse
Now that I'm trying it again, it's failing to pull it. The DZ seems to pull from the KDZ, but anything from the DZ fails with an incorrect header check error. It's a blank file. I'm sure you noticed that before I did.
rainbowtuba said:
Now that I'm trying it again, it's failing to pull it. The DZ seems to pull from the KDZ, but anything from the DZ fails with an incorrect header check error. It's a blank file. I'm sure you noticed that before I did.
Click to expand...
Click to collapse
KDZ Extractor LG
Download the Zip : http://www.mediafire.com/file/0a6iikrao70ma5s/KDZTools_20200305.7z/file Extract the file zip Copy the Downloaded KDZ into the KDZ Extractor folder Open "OneKeyExtraction.bat" It will Start to extract the file for you The...
forum.xda-developers.com
use this
[email protected] said:
KDZ Extractor LG
Download the Zip : http://www.mediafire.com/file/0a6iikrao70ma5s/KDZTools_20200305.7z/file Extract the file zip Copy the Downloaded KDZ into the KDZ Extractor folder Open "OneKeyExtraction.bat" It will Start to extract the file for you The...
forum.xda-developers.com
use this
Click to expand...
Click to collapse
Thank you, here is the boot_a.img
EDIT: I have potentially good news! I was completely stuck in a boot loop, but using the files from the KDZ (modem_a, modem_b, boot_a,boot_b, abl_a, and abl_b) and pushed them each with fastboot. The device restarted (with sound!) and it is resetting to stock now. We'll see what happens!
rainbowtuba said:
Thank you, here is the boot_a.img
Click to expand...
Click to collapse
How to restore download mode ?
can we root on 20f?
What about 20b
I own a LG G8x Sprint fw model with SW version g850um20f build qkq1.200216.002 with April Security patch. I unlocked the bootloader with this method after I sim unlocked it today. Interestingly I have now a T-mobile splash screen perhaps because I tested the sim unlock with my t-mobile sim? Either way it provisioned all the T-mobile operator software so it got rid of all the Sprint garbage and loaded volte wifi calling etc...I have yet to test all the features but it did it all for me after the factory reset happens when the boot loader unlocks. I did not load the original abl_a abl_b backup files back to the device. Was the patched abl file a US model dump?
Me gustaría saber si la versión 20j de sprint también se puede rootear
Anyone successful unlock the 20b (G8X Us variant)? Having a hard time finding any info on unlocking this version.
20b
Adminislayer said:
Anyone successful unlock the 20b (G8X Us variant)? Having a hard time finding any info on unlocking this version.
Click to expand...
Click to collapse
I did 20j sprint yesterday.
The hardest part was to get into EDL.
Where are you stuck?
BTW, does anyone have the twrp bin for these phones? I can't find a working link. I just want to boot into twrp temporary to do a system image.
Related
Hi everyone,
I have an 10.8 inch wifi only tablet imported from China, non-pro, model CMR-W09C00 which was running firmware B123.
I was playing around trying to convert it to a global firmware and tried to flash it with the same firmware 123 but for CMR-W09C432 using Huawei Firmware Finder.
Turns out this was a pretty bad idea
Now the tablet is not booting and I can't figure out how to recover. Here's what I tried:
1. eRecovery is not working, it downloads the firmware completely and tries to install but fails. It did work fully once before I tried to flash the wrong firmware.
2. Wiping cache and data partition does nothing
3. I have access to fastboot and can unlock/lock the bootloader at will.
4. I have the full-OTA zip file for the original firmware CMR-W09C00B123 and have extracted all the img files contained in update.app
5. I'm trying / hoping to flash images to recover (with bootloader unlocked) but I'm a bit confused at this step.
All the instructions I found in my research mention mostly flashing just boot.img, system.img and recovery.img but I'm missing some of those files from the update.app or I guess they could be named differently. I don't have a boot.img, just a fastboot.img which I'm sure is not the same. I also don't have a recovery.img, just recovery_ramdis, recovery_vbmeta, recovery_vendor, erecovery_ramdis, erecovery_vendo, erecovery_vbmet and erecovery_kerne.
I was able to flash system.img successfully but that didn't help.
Also tried to use the unbrick feature from Huawei Multi-Tool but here again I seem to be missing image files. Multi-Tool says it needs system.img, ramdisk.img, cust.img, ramdisk_recovery.img and userdata.img.
Of those, I think I'm missing cust.img for sure, ramdisk_recovery I might have but it's named differently (recovery_ramdis) and userdata.img I don't think I really need.
I'm attaching a txt file with a list of all the img files I do have in case it can be useful or rings a bell for someone.
Oh yeah, I also tried flashboot update update.zip but it's only giving me this warning:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
So...does anyone have any advice or suggestions? Is there a better method to recover that I missed?
Any help is appreciated!
Flash the ramdisk.img to ramdisk and report back please. I have an M3 that is in the same condition as yours, but I am on an extended deployment and won't be able to test this for at least another month :/
fargonaz said:
Flash the ramdisk.img to ramdisk and report back please. I have an M3 that is in the same condition as yours, but I am on an extended deployment and won't be able to test this for at least another month :/
Click to expand...
Click to collapse
Thanks for taking the time to the reply mate, sorry to hear about your M3.
I tried fastboot flash ramdisk ramdisk.img and it said flashed successfully but the device is still not booting. Nothing else seems to have changed either.
Let me know if I misunderstood what you wanted to try or if you have any other ideas.
Cheers
etheberge said:
Hi everyone,
I have an 10.8 inch wifi only tablet imported from China, non-pro, model CMR-W09C00 which was running firmware B123.
I was playing around trying to convert it to a global firmware and tried to flash it with the same firmware 123 but for CMR-W09C432 using Huawei Firmware Finder.
Turns out this was a pretty bad idea
Now the tablet is not booting and I can't figure out how to recover. Here's what I tried:
1. eRecovery is not working, it downloads the firmware completely and tries to install but fails. It did work fully once before I tried to flash the wrong firmware.
2. Wiping cache and data partition does nothing
3. I have access to fastboot and can unlock/lock the bootloader at will.
4. I have the full-OTA zip file for the original firmware CMR-W09C00B123 and have extracted all the img files contained in update.app
5. I'm trying / hoping to flash images to recover (with bootloader unlocked) but I'm a bit confused at this step.
All the instructions I found in my research mention mostly flashing just boot.img, system.img and recovery.img but I'm missing some of those files from the update.app or I guess they could be named differently. I don't have a boot.img, just a fastboot.img which I'm sure is not the same. I also don't have a recovery.img, just recovery_ramdis, recovery_vbmeta, recovery_vendor, erecovery_ramdis, erecovery_vendo, erecovery_vbmet and erecovery_kerne.
I was able to flash system.img successfully but that didn't help.
Also tried to use the unbrick feature from Huawei Multi-Tool but here again I seem to be missing image files. Multi-Tool says it needs system.img, ramdisk.img, cust.img, ramdisk_recovery.img and userdata.img.
Of those, I think I'm missing cust.img for sure, ramdisk_recovery I might have but it's named differently (recovery_ramdis) and userdata.img I don't think I really need.
I'm attaching a txt file with a list of all the img files I do have in case it can be useful or rings a bell for someone.
Oh yeah, I also tried flashboot update update.zip but it's only giving me this warning:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
So...does anyone have any advice or suggestions? Is there a better method to recover that I missed?
Any help is appreciated!
Click to expand...
Click to collapse
I think I am in a similar spot. I went from a custom ROM back to stock, but now all attempts at installing full OTAs fail. Did you ever figure this out how to fix it?
Thanks
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
cubano2031 said:
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
Click to expand...
Click to collapse
Sent from my LGE LM-X410.FGN using XDA Labs
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Rebel_X said:
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Click to expand...
Click to collapse
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
Thanks a lot!! And it was as simple as that. It works fine. :good:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
MAREK10747 said:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
Click to expand...
Click to collapse
Hi,me devie is I4293
I have unrar the rom , so i get the boot_X-FLASH-ALL-8F02.sin
would you mind to make the kernel for me?
the file is here :
https://drive.google.com/file/d/1sywqfBtELSTgRXtTBEvlI454K_1ul-1h/view?usp=sharing
my gmail is [email protected]
you can send it to me.
thank you.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
yishisanren said:
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
Click to expand...
Click to collapse
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Zaben said:
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Click to expand...
Click to collapse
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
yishisanren said:
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
Click to expand...
Click to collapse
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
wang4632 said:
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
Click to expand...
Click to collapse
older version can not patch boot.img, because when you click "install the zip",it will let you update the new verison.
Any news on the boot loop situation? I also encounterd this problem and back to running original boot.img. having an unlocked bootloader is useless without root ?
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Did you lose any feature like super vivid mode and camera focusing after unlocking the bootloader?
can't find the driver, the model is l421dual sim, can't rooting, have i already patched the boot img?
My I4293 stuck in bootloop~~help ~!
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
This phone cannot be rooted at this time due to the lack of the img.patch and no driever.
Zack_U said:
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
Click to expand...
Click to collapse
Are you still stuck? For all of the latest Sony phones try NewFlasher instead.
https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
Flashtool doesn't support our phones. Magisk 19.1+ currently doesn't work with our phones. Hopefully 19.4 will fix that.
This Guide will explain how to root your LG G8X
* Disclaimer*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* YOU are choosing to make these modifications, and if
* you blame me in any way for what happens to your device, I will laugh at you.
*Wait, what? No. Me or somebody else will help you
Click to expand...
Click to collapse
Prerequisites
Unlock phone using the guide here: https://forum.xda-developers.com/t/guide-how-to-unlock-bootloader-of-lg-g8x.4198025/
Do not restore abl before rooting.
Magisk Patched Boot (20e, Indian Variant): https://drive.google.com/file/d/1s2A7RUOptXer5LGMtbGV9SKg0kcyL_NP/view?usp=drivesdk
1. Download the magisk patched boot.
2. Copy it over to your fastboot directory.
3. Connect phone in fastboot mode.
How to put phone to fastboot mode?
#1: Using Button Combination
Power off phone, press and hold Vol- and insert usb cable. You’ll be in fastboot
#2: Using ADB
Connect phone to pc, enable USB Debugging. Then run this command
Code:
adb reboot fastboot
4. Now run the command
Code:
fastboot flash boot Magisk_Patched.img
fastboot reboot
5. Download and install Magisk Manager
6. Done! Your phone is rooted now.
To restore Network follow the guide in bootloader unlock thread...
If you have a different G8X variant or are on a different firmware
1.Backup boot_a or boot_b using QFIL (Partition Manager>Read Data, Check Bootloader unlock guide for more details)
2. Install Magisk Manager
3. Click on Install and use Patch image function.
4. Save the boot image to pc.
5. Flash it in Fastboot using the command given above.
Known Issues: FP is broken
Thankyou
(copypasta'ed from the other thread)
For those who have yet to do this, I suggest extracting boot_a/b at the same time you flash the abl image. Prior to doing the fastboot oem unlock, use the Magisk patch file option (installed on the same or another device, and doesn't need to be rooted) to create a rooted boot image using adb push/pull. Once you fastboot oem unlock, go back into the bootloader and instead of fastboot flash boot, you can fastboot boot magisk_patched.img.
Once you go through the setup, you can open Magisk, which will download and install the full Manager app, at which point it will most likely reboot. You will need to fastboot boot again, and you should be able to do a normal Magisk install. I've usually found that as long as the patched boot is of the same Android version and within a few month of the patch level, it'll boot happily enough to do this. Afterwards, you can restore your abl image as you no longer need to use fastboot commands.
Doing this allows Magisk to save the stock boot image, and also allows you to get OTA updates by restoring the stock image right before any updates. Otherwise you will never be able to do an OTA update as it checks if the boot partition has been modified before installing the updates. Since there are no kdz for the US carrier models, your only other option would be to "brick" your device to try get your carrier's service center to restore a working firmware image.
-- Starfox
Sorry I posted in the wrong thread. I've deleted the contents, but wasn't able to delete the post itself
Guys, I am trying to follow this guide using the "different variant" method, but as soon as I boot after flashing boot.img the touchscreen doesn't work. Only way to get it back is to flash the boot_a.bin and boot_b.bin using QFIL. What am I doing wrong?
Is there a magisk patched image for the g850u20i
Is there an update for magisk patch image for 20b (unlocked US variant)?
Edit: Got my 20b version rooted.
Downloaded stock rom for the G850QM20b, extracted the kdz file to dz to .img grabbed the stock boot_a.img file and ran it in Magisk manager app, took the converted .boot.a.img (now renamed magisk_patched_clT14.img) and dropped it in platform tools, went fast boot, then flashed it. Came back up great, no issues and root access is clear.
Dapeplezchamp said:
Is there a magisk patched image for the g850u20i
Click to expand...
Click to collapse
I have 20j and I can't even get into edl or fastboot... Can you get into fastboot mode? I've tried adb and button combos
robnitro said:
I have 20j and I can't even get into edl or fastboot... Can you get into fastboot mode? I've tried adb and button combos
Click to expand...
Click to collapse
I cannot.I've tried everything I know to do.I'm so cautious with this phone because I got it at a steal off of eBay and would hate to brick it.
Dapeplezchamp said:
I cannot.I've tried everything I know to do.I'm so cautious with this phone because I got it at a steal off of eBay and would hate to brick it.
Click to expand...
Click to collapse
follow the video here, I got it to work
hold power and vol down , itll countdown to reboot.... as soon as it does that- while holding down and power tap the up button
How to Unlock Bootloader and Root Lg G8x + (also a Video Guide)
All fix avilable (no network solved) Watch it carefully do it step by step as showen in my video you will never brick if you follow my video :):love: All required files are in the video description This guide Tested on the firmware (20e...
forum.xda-developers.com
Is there a image for the g850UM20g?
edit:
I have a copy of boot_a but in the fastboot it tells me that I am using abl_b and I don't know if boot_a is compatible with abl_b and i can't enter EDL mode
So my understanding is you can have a rooted phone, but FP will be broken no matter what and possibly audio as well. You can fix this by reinstalling a Pie version from KDZ, fix it then reinstalling a 10, but then the root will be gone (but the bootloader remains unlocked). Is this correct?
zdanee said:
So my understanding is you can have a rooted phone, but FP will be broken no matter what and possibly audio as well. You can fix this by reinstalling a Pie version from KDZ, fix it then reinstalling a 10, but then the root will be gone (but the bootloader remains unlocked). Is this correct?
Click to expand...
Click to collapse
Yes, rooting will be gone and Bootloader remains unlocked forever. You have to root it again in A10
For anyone in the future: you can have both root and fingerprint. Follow the bootloader unlock guide up to the point where you have to backup your boot_a. After that you don't use the patched boot_a in the instructions, instead patch your own version with magisk and flash that instead with QFIL. I now have a working V20h EU version with root, fingerprint and working audio.
Anu one have LMG850UM 20f magisk patched boot file?
Country china
Lg g8x
Kanhei015 said:
Anu one have LMG850UM 20f magisk patched boot file?
Country china
Lg g8x
Click to expand...
Click to collapse
I do. But it's an EU version, so I'm not sure it would work for you. However it's easy to just make your own!
- Install Magisk manager on the phone. You don't need open bootloader or anything for that
- Get your own 20f boot_a using QFIL
- Copy your own boot_a to the phone or on an SD card
- In Magisk Manager you choose to install magisk, select patching an IMG file method and give it the boot_a
- If Magisk reports success you'll now have a magisk_patched_boot_a file. Copy that back to your PC
- Using QFIL flash that in place of your original boot_a
- Keep a copy of your original boot_a thou, you can go back with QFIL at any time.
- If you mess up royally and the phone doesn't boot, you can still recover it by re-flashing your firmware with LGUP 1.17. You'll have to download your region's firmware for that and you'll loose all data, so make a backup beforehand!
edit: double post
zdanee said:
For anyone in the future: you can have both root and fingerprint. Follow the bootloader unlock guide up to the point where you have to backup your boot_a. After that you don't use the patched boot_a in the instructions, instead patch your own version with magisk and flash that instead with QFIL. I now have a working V20h EU version with root, fingerprint and working audio.
Click to expand...
Click to collapse
Hi, thanks for sharing the steps!
I followed your steps but don't have audio/network/fingerprint after flashing patched boot. Later I also tried to restore abl_a/b, then I had audio and network working, but still no fingerprint.
In my case, fingerprint stopped working once bootloader is unlocked, before even flashing the patched boot.
Did you have working fingerprint right after you flash patched boot? Did you restored abl_a/b?
I also tried to follow another post to get fingerprint working, but I can only find 10b kdz of my variant (twn), I downgraded to android 9 using that kdz, still cannot get fingerprint to work.
james508959 said:
Hi, thanks for sharing the steps!
I followed your steps but don't have audio/network/fingerprint after flashing patched boot. Later I also tried to restore abl_a/b, then I had audio and network working, but still no fingerprint.
In my case, fingerprint stopped working once bootloader is unlocked, before even flashing the patched boot.
Did you have working fingerprint right after you flash patched boot? Did you restored abl_a/b?
I also tried to follow another post to get fingerprint working, but I can only find 10b kdz of my variant (twn), I downgraded to android 9 using that kdz, still cannot get fingerprint to work.
Click to expand...
Click to collapse
I also messed up at first, since there were no ready-made boot_a for my region/version I just grabbed the indian one for 20e, and yes, that did break my audio, fingerprint and possibly network, I didn't test that one. I did have a KDZ for my region thou, so I flashed back a 10c version, I needed the 1.17 tool, not the 1.14 or 1.16 one (those did not work) and in my case I needed the second version of 10c, not the first one to fix the fingerprint. After flashing 10c I did all the steps and regained my fingerprint reader without an issue (so no, it did not work right away, I did need to go into the service menu and do the test), audio and network also worked right away. After that I flashed my latest KDZ (20h) and using magisk manager made my own boot_a and was able to root with a working fingerprint. I did not dare to update Magisk after this thou, I only needed it to grant root for my adblocker, and it's hidden from everything else, I don't think I'll ever even start magisk again, so I don't really want to update it either.
Did you restore abl_a/b at all? I can only get into download mode (to use LGUP) after I restore abl_a/b.
Anyways, I think flashing using LGUP overrided the abl, and that's why audio and network worked right away (to my understanding)
My LGUP tool worked fine, but there only 10b for my TWN variant, I couldn't find 10c anywhere... (only 10b, 20a, 20b available)
I never flashed other's patched boot, I used QFIL to get my boot_a.bin and patched it using Magisk on another phone. Then I used fastboot to flash boot. (I did this right after unlocked BL, all before I restored abl).
Did you also use QFIL to get boot_a or did you use KDZ extractor? I'm having problem with my KDZ extractor tool, encoding issue or sth.
My variant is G850EMW, should I try the indian 10c kdz (which is also G850EMW)? Would that work? Not sure what risk cross region flashing poses, or even if LGUP would let me flash it at all.
james508959 said:
Did you restore abl_a/b at all? I can only get into download mode (to use LGUP) after I restore abl_a/b.
Anyways, I think flashing using LGUP overrided the abl, and that's why audio and network worked right away (to my understanding)
My LGUP tool worked fine, but there only 10b for my TWN variant, I couldn't find 10c anywhere... (only 10b, 20a, 20b available)
I never flashed other's patched boot, I used QFIL to get my boot_a.bin and patched it using Magisk on another phone. Then I used fastboot to flash boot. (I did this right after unlocked BL, all before I restored abl).
Did you also use QFIL to get boot_a or did you use KDZ extractor? I'm having problem with my KDZ extractor tool, encoding issue or sth.
My variant is G850EMW, should I try the indian 10c kdz (which is also G850EMW)? Would that work? Not sure what risk cross region flashing poses, or even if LGUP would let me flash it at all.
Click to expand...
Click to collapse
No, I did not restore abl_a/b, and after KDZ the bootloder remained open, so there is no need to, the phone still reports an open bootloader at boot. If it _does_ override it thou it seems it's not neccessary to have, as I could root the phone and could keep the open bootloader anyways.
I used QFIL to get my own boot_a, and used it again to flash it back too.
My EU (Hungarian T-mobile) version is also G850EMW. My understanding is that if LGUP lets you flash a KDZ it's probably gonna work, but in the worst case scenario as long as you have a known good KDZ for your model you can always come back to that, so I guess you can experiment?
I've also only found a 20b version of KDZ for TWN, but it's release date is similar to 20h in the EU, so maybe these numbers doesn't mean they are the same KDZ, only that 20x meant it's Android 10 and the letter is the revision. Based on this it's possibe you don't need a 10c to restore your fingerprint, just try the earliest 10x KDZ you can get your hands on (for me the 10c was the earliest one). Alternatively you can try the 10c I used for mine, it's EU Hungarian, but the default language is still English and you'll re-flash it anyways: https://lg-firmwares.com/downloads-file/21667/G850EMW10c_00_OPEN_EU_DS_OP_1122
Hello, I am from Canada and I just got a Moto G Power (2021) XT2117-4 with the firmware QZBS30.Q4-43-129-2. I unlocked the bootloader thru Motorola with no problems. I installed Rescue and Smart Assistant and downloaded my firmware. I patched the boot.img thru Magisk and flashed it to my phone using ADB. I was not able to achieve root. I also tried to boot thru recovery mode but got the no command sign. I then rescued my phone and tried it again flashing to both boot_a and boot_b still to no avail. If anyone has any info on why this is and has a solution to my problem it would be greatly appreciated.
jwreidmoto said:
Hello, I am from Canada and I just got a Moto G Power (2021) XT2117-4 with the firmware QZBS30.Q4-43-129-2. I unlocked the bootloader thru Motorola with no problems. I installed Rescue and Smart Assistant and downloaded my firmware. I patched the boot.img thru Magisk and flashed it to my phone using ADB. I was not able to achieve root. I also tried to boot thru recovery mode but got the no command sign. I then rescued my phone and tried it again flashing to both boot_a and boot_b still to no avail. If anyone has any info on why this is and has a solution to my problem it would be greatly appreciated.
Click to expand...
Click to collapse
Does the phone boot with the patched boot.img ?
sd_shadow said:
Does the phone boot with the patched boot.img ?
Click to expand...
Click to collapse
Yes.
jwreidmoto said:
Yes.
Click to expand...
Click to collapse
What does the magisk app say?
Can you share a screenshot?
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
What does the magisk app say?
Can you share a screenshot?
Click to expand...
Click to collapse
That is just how the patched boot.img is created.
Now you have to flash it with fastboot.exe
Been thru that already no root.
Do I have to rename it to boot.img when I flash it or can I leave with with the patched name?
I am going to start from scratch again. I don't think I made a mistake because I rooted my G7 Play this way too. I also get feedback from terminal confirming flashing.
jwreidmoto said:
Do I have to rename it to boot.img when I flash it or can I leave with with the patched name?
Click to expand...
Click to collapse
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
and
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and more
Rooting your phone is still possible — and fun — these days. Here's how to do it on your Android device.
www.xda-developers.com
Followed link instructions exactly and still no root. Maybe I have to go with a TWRP recovery method. I will keep checking forums for others having same issue.
jwreidmoto said:
Followed link instructions exactly and still no root. Maybe I have to go with a TWRP recovery method. I will keep checking forums for others having same issue.
Click to expand...
Click to collapse
Ok, if you want help you have to give details.
No root means nothing.
I downloaded firmware from Rescue assistant copied boot.img to phone selected it thru magical and patched it. Copied patched boot.img to PC. Put it in ADB folder renamed it back to boot.img. Opened up ADB terminal and flashed - fastboot flash boot boot.img. Terminal said writing boot_a......okay.....finished. reboot no root. Tried again with flashing to boot_a and to boot_b. Reboot still no root. That's about all I can tell you everything checked out including ramdisk - yes in Magisk, boot.img from same firmware that is currently on phone. Not sure why it's not working.
Actually, sorry phone is now rooted. Once I added root checker to superuser in magisk it showed phone was successfully rooted Thanks for all your help!
Just to confirm, as I've yet to root my device and may encounter this same issue. Did you solve it having done anything different with the rooting procedure or was it a simple matter of adding the root app to Magisk SU? If the latter, Did magisk display the SU prompt at all?
Yes, the root instructions are good. I think why Magisk did not prompt me, initially was because my phone was setting up for the first time and it was bogged down by Google restoring apps etc. Now Magisk prompts me every time for root apps.
So I'm Down to Help this is what I did. So
Download Rescue and blah blah assistant
Found My Phone Checked and Double Checked all information then when I did so I extract led the Folder to My desktop, looked inside it's little bundle of goodness to find boot.img pulled it out and connect my Moto G.
At This Point I Just Opened up My Phone storage (from My P.C) pulled it out and stuck it in my main storage.
At that point Went and Got Magisk v.23 renamed the download as Magisk v.23.apk
Then Riped her Open Like A wild animal installed the .apk (If the File Manager or whatever you are using won't let you install go to settings for the particular File Manager you are using on your phone and allow download a from unknown sources)
Pulled out the boot.img I put in my main storage and went to My sexy New Magisk App and selected "select and Patch a file"
At the Point stepped out for a quick smoke and had a tug.
Then your final product will be Magisk_patchedv23.img (or something like that)
Then after you get all that mumbo move that back to your P.C
I assume you have adb fastboot
So then I pull it up (not sure if it affects anything but I did adb Root)
Anywho first I did
adb devices -l
As soon as I see my phone se then I know I got it.
#also side not make sure the wording next to the device says device
Ok so at the point type
adb reboot fastboot
Then repeat same command as the adb one
Fastboot devices
#seeyour device? Dope
Then wherever you put that patched image sometimes you need to put the FULL path
Example for me it was
Fastboot flash magisk_patched.img boot
Which didn't work so tried the _a still nothing soo hence the FULL PATH I put it on my desktop if you don't know the full path right click the file and hit properties
final Command for me
fastboot flash boot C:\Users\insan\Desktop\magisk_patched.img
Boom Done and Done!!!! And as always take Back Ups Before and After and Save that Patch .img
I've needed it like 10 times !
Hope That Helps Ya
And the last pic Is Proof
God Bless, and Good Luck!
..the vbmeta.img and boot_a from the unlocked variant? I tried flashing TWRP kind of half cocked, and yea... Anyhow, if someone has either\or or both of these files, hook a brother up!
Disregard. I was able to unbrick with the dre8t_10_O.05_210713.ops firmware floating around. It wouldnt let me flash via MSMDownloadTool, however I was able to decrypt/extract the ops file with the oppo_decrypt python script, then reflash the vbmeta and vbmeta_system partitions plus boot_a and userdata with the extracted files.
PHEW had me scared for a minute
the.real.p3y0t3 said:
..the vbmeta.img and boot_a from the unlocked variant? I tried flashing TWRP kind of half cocked, and yea... Anyhow, if someone has either\or or both of these files, hook a brother up!
Click to expand...
Click to collapse
For future reference:
For unlocked variant:
Download the latest OTA update from the OnePlus website and you can use any assortment of payload dumpers to obtain all of the raw image files.
My payload dumper of preference is Fastboot Enhanced/Payload Dumper. It can even install the full OTA via fastboot/fastbootd
For T-Mobile and Metro variants I would recommend the T-Mobile MSM tool and update from there.
The download link to "Incremental OTAs" can be scraped from the system logcat at time of download.
I haven't looked much into incremental OTA and how it is setup yet.
Thanks for the heads up. I actually already had the above mentioned OPS file when I bricked my device, I just hadn't been able to extract, then decrypt it. Had to download a obscure bzip2 binary for windows to extract the tar, etc etc.
A seller from ebay sent a t-mobile (2118) that was carrier unlocked, wasn't able to unlock the bootloader. Is there anything I can do?