Related
Thanks to serajr here - https://forum.xda-developers.com/showpost.php?p=75505302&postcount=2973 Go directly to that post and give thanks.
You need:
Stock O ftf (best to use Flashtool/Xperifirm)
Modded boot img for 34.4.A.2.19 - https://mega.nz/#!AgtQ2Sob!JjLRcUVjuy6FNanjGY49g-YYmkcda04witfHp4hwvmo
Modded boot img for 34.4.A.2.32 - https://mega.nz/#!Z1tzEJbZ!e9ET_RtUpKjXRwnJa_TDsMrVwvT-hPxmk06KtryHOuc
Modded boot img for 34.4.A.2.85 - https://mega.nz/#!p5UwAabR!_ofmr_WdId9RdH48Xb3cZtSIzsQ6qcTJTAFYcKHFWJE
Kernel elf file to use with rootkernel [34.4.A.2.85] - https://mega.nz/#!M102lYTZ!9bj2KE-vbNWlej3Dw0NuiXJcfpgiy16svSHud73bLfw
Modded boot img for 34.4.A.2.107 - https://mega.nz/#!Nls0EQBR!Cc4lVcA85f8YeNTo8nMqsuwLzveW5duSbyeZDlI5kDE
Kernel elf file to use with rootkernel [34.4.A.2.107] - https://mega.nz/#!Zp10CASK!iGLE94Tj1SSk1U2p4KLpVrcGmD68C3YvqKMXD6VPFjI
Modded boot img for 34.4.A.2.118 - https://mega.nz/#!14VkzCCB!GK-KEv0A-ZyhysXc1-IusyJjJEB-D5ZWOLm1DRt31tA
Kernel elf file to use with rootkernel [34.3.A.2.118] - https://mega.nz/#!Ylcm1SwA!GuX9dfd2HAqLXy1jom-C6mgP0s4jYXl9qSySkvb_mtA
TWRP - https://forum.xda-developers.com/x-compact/development/ub-twrp-v3-2-1-xperia-x-compact-t3793837
1. Flash stock ftf from Xperifirm via Flashtool
2. After flash, connect in fastboot (before booting phone) and type in command line 'fastboot flash boot boot.img' (this assumes that your modified boot img is in the current directory,and is named 'boot.img'; otherwise, you need to edit the command accordingl)
3. Then type 'fastboot flash recovery twrp-3.2.1.img' (same note as above)
Done
Now, you can flash Magisk, (or whatever), and have root access.
If you want Drm fix, flash serajr's zip here - https://forum.xda-developers.com/attachment.php?attachmentid=4404527&d=1517335127
If you want to restore your own ta with munjeni tool, you will need to patch boot img yourself with rootkernel tool here - https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
How to get stock kernel elf and patch your boot img with rootkernel:
1. Download and build stock ftf from Xperifirm via Flashtool
2. Go to Flashtool > tools > sin editor, and navigate to stock kernel sin file, in the downloaded firmware folder. Click on sin file and choose 'exrract data', and it will create a kernel elf.
3. Follow the guide by serajr. You need only to put the kernel elf into rootkernel folder, then open a command prompt there and run 'rootkernel kernel.elf boot.img'. Answer all questions 'yes', unless you want to skip drm fix and restore your own ta, (if that's the case, you need your target file in that folder renamed to TA.img). After script runs, you will have a new boot img that you can use to follow the guide.
Done...
Magisk, MicroG, and Xposed tested... (update - I haven't tried yet, but I've read that Xposed not working on ...85; update 2 - confirmed, bootloop; update 3 - Xposed fix now available here - https://forum.xda-developers.com/x-compact/themes/xposed-fix-118-t3870673)
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Can confirm the above method worked for me. I used the TA.img instead of drm fix, and i get root and security test still have widefine and fidokeys enabled.
Just slight reminder for linux user, you need to add execute permission on both `rootkernel` and `bootimg`, otherwise rootkernel tool will fail with permission issue.
levone1 said:
I made a patched boot img with rootkernel tool and uploaded it. Link in op. Don't forget to thank serajr...
Click to expand...
Click to collapse
With which options is your modified boot image prepared?
maluus said:
With which options is your modified boot image prepared?
Click to expand...
Click to collapse
Dm-verity disable - yes
Force encrypt disable - yes
Drm fix - yes
For Drm fix you still have to flash serajr zip. If you want to restore ta with munjeni tool, you will need to patch boot yourself.
Op updated for 3-click root...
SuperSU,Xposed
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
...
Arsis said:
Hello,
can you please help me with a little problem? I just did everything step by step, but I can't still get root access (after flashing boot.img SuperSU still shows "no root detected"). And one more question. I used that DRM fix zip, but still get "Not provisioned". Am I miss something? (but nevermind, I can use my TA backup, but I'm just curious about that).
Thanks guys.
Click to expand...
Click to collapse
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
I was able :laugh::good: Xposed release link
levone1 said:
Boot img just enables modification by disabling Sony security stuff, but you still need to flash whatever mod you want. So after flashing boot and recovery img, then flash supersu (or whatever), and you should have root.
I can't say about drm fix, since I've never used it before, but I don't think it will show fido provisioned, etc, because it simply recreates the drm functions through a different method, (not with ta).
Click to expand...
Click to collapse
Oh, well. Thank you! It's working now.
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Stephenhs said:
Hello,
i flashed on my sony with oreo this boot.img and twrp and im stuck on sony logo. Any ideas what could be wrong? I tried android 34.4.A.0.364 singapure and UK versions and neither of these works with this twrp.
I have the newest platform-tools and flashing went well.
Thanks
Click to expand...
Click to collapse
Can you try running the tool and creating the boot.img yourself? I use the singapore ftf and doesn't have problem booting the system (with the boot img I created myself). I do not put twrp on boot img though. I boot twrp from fastboot when needed
I created boot.img and everything works Thanks a lot!
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Kianush said:
I dont understang the part that says :
Android Oreo ramdisk patching needs some additional files, and they must be copied from Oreo /system into the rootkernel's filesystem_files folder, prior to run the script, and they are:
Code:
/system/vendor/etc/fstab.qcom
/system/vendor/etc/init/hw/init.qcom.rc
/system/vendor/etc/init/hw/init.target.rc
(you can pull these files through adb, or even converting system.sin to system.ext4 and take them out from there - just copy them, and DO NOT touch its contents)
how to do that!? im noob...
Click to expand...
Click to collapse
Post linked in op has special instructions for us with Xc - skip that part.
https://forum.xda-developers.com/showpost.php?p=74724162&postcount=2793
hello guys, i've created a boot.img whit the tool of rootkernel whit my ta.backup but it does not work. the boot it's ok but if i chek my drm keys they say not provisioned. my ta.backup load 2.097.152 byte like the post shows. can someone help me? thanks
update:
sorry guys, i've done again the kernel patch whit my ta backup and this time goes perfect. i don't know why the first time didn't work but now it's ok!
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Wxfdswxc said:
I tried the 3 click method, without doing any boot image myself, but impossible to decrypt with TWRP (or reboot to system).
Click to expand...
Click to collapse
Twrp - https://forum.xda-developers.com/x-compact/development/twrp-3-2-1-decryption-t3751998
As for rebooting to system, can't say for sure... Root method involves only changing boot img, so shouldn't affect system. Any errors in fastboot, etc?
Original flash should be clean flash official stock ftf from Xperifirm. First boot could be 10 minutes...
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.
I have a bricked Hisense A5 (Qualcomm, China) device which stays in a bootloop and I don't know how I can unbrick it.
Facts are:
Device: Hisense A5 (HLTE202N)
Firmware: Stock L1657 6.03.02.00 / Kernel 4.9.112
- I could flash in edl mode successful a stock firmware, but nothing changed after a reboot
- Device stays with "Hisense and powered by Android screen".
- The bootloader can't be unlocked
- teardown device and disabled battery for some minutes and tried to charge it with a wall charger -> bootloop
What I can (like before flashing in edl-mode):
- Entering edl-mode with a xiaomi edl-cable (Qualcomm HS-USB 9008er mode and diagnostic mode 900E after flashing)
- entering fastboot (pressing volume up while rebooting and connecting pc)
What I can't:
-flashing TF-Mode (Firmware on microSD)
-rebooting to system
-shutdown
-recharging wall charger (bootloop)
-not detected as usb-drive for filetransfer
This bootloop mode you can read quite often. The Xiaomi guys can fix this by flashing a fastboot Firmware, but they have an unlocked bootloader
Anybody knows a solution or what I can try to fix this?
Solved:
https://forum.xda-developers.com/showpost.php?p=82726877&postcount=7
JLowe said:
I have a bricked Hisense A5 (Qualcomm, China) device which stays in a bootloop and I don't know how I can unbrick it.
Facts are:
Device: Hisense A5 (HLTE202N)
Firmware: Stock L1657 6.03.02.00 / Kernel 4.9.112
[...]
Anybody knows a solution or what I can try to fix this?
Click to expand...
Click to collapse
Have you already considered trying to use the 6.09.06.00 ROM available via forum.xda-developers.com/showpost.php?p=82583733&postcount=28 ?
defylogic said:
Have you already considered trying to use the 6.09.06.00 ROM available via forum.xda-developers.com/showpost.php?p=82583733&postcount=28 ?
Click to expand...
Click to collapse
Yes, sorry forgot that to mentioned. Good point. That was the first I tried with some other guys in the thread but it doesn't work at all. Tried different microSD and formatting.
Well if the TF Mode not working with 6.0.9 and you have 6.0.3 which is already rooted logic say to try not with 6.0.9 but with 6.0.4 update or better with 6.0.3 but original i.e not rooted. I think something in 6.0.3 is not compatiblle with something in 6.0.9. Simply as that. I remember I say guy in thread for Hisense A5 root which had all update files and WeChat group?
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
gowin132 said:
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
Click to expand...
Click to collapse
Do you have the same files of 6.09.06 version? If yes, please share. I have same problem but my phone has latest OS version.
gowin132 said:
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
Click to expand...
Click to collapse
Great, these files are working flawless in qfil. Could recover the system and then update in Tf-Mode to actual 6.09
These are the original boot, recovery and vbmeta image from 6.09.06.
https://drive.google.com/file/d/1JeUEaBxpH5zu22v-6V_6LAqZzGuXmUhf/view?usp=sharing
Mehedi34 said:
Do you have the same files of 6.09.06 version? If yes, please share. I have same problem but my phone has latest OS version.
Click to expand...
Click to collapse
Do you guys have full firmware with system and other imgs?? Mine seems to still bricked
lillo9546 said:
Do you guys have full firmware with system and other imgs?? Mine seems to still bricked
Click to expand...
Click to collapse
I'm sorry for asking what is probably a silly question, but how exactly do you flash files like boot.img using Qfil ?
I can get into fastboot., but not edl mode.
I know old thread, but am having problems with a bricked A5. After a lot of trial and error, it sometimes gets into Fastboot mode. I can then ask for fastboot device and it responds with a hex number and fastboot.
When I try to flashall new partitions, it fails with:
fastboot: error: ANDROID_PRODUCT_OUT not set or non allowed.
Once I could flash individual partition with:
fastboot flash boot boot_recovery_vbmeta_6.03.02/boot.img
Sending 'boot' (65536 KB) OKAY [ 2.113s]
Writing 'boot'
But then it just sits there and nothing seems to happen.
Anyone has suggestions on what to try, am running out of ideas
.
It would be amazing if anyone could share:
- Stock ROM 6.12 full QFIL backup.
- EFS/QCN backup files.
Thanks
JLowe said:
Great, these files are working flawless in qfil. Could recover the system and then update in Tf-Mode to actual 6.09
Click to expand...
Click to collapse
Hi. I have the same problem as you, but I don't know how to flash those files with qfil. Can you please explain it to me?
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.