[GCAM] Buffer fix by Wyroczen
Hey, I've made buffer fix for LG V40 in a form of TWRP flashable zip and second option with file for replacement:
It will fix lagging viewfinder in GCAM both nightsight and normal mode.
Instructions:
Boot into TWRP, mount vendor, flash zip.
Requirements:
Stock android 9 work (may or may not work in others)
Downloads:
Celsoazevedo: https://www.celsoazevedo.com/files/android/p/lg-v40-buffer-fix/
Donation:
If you want, you can support my work by sending me donation
https://www.paypal.me/wyroczen
XDA: DevDB Information
LG V40 TWRP flashable lib fix.
xenius9 said:
patched lib for android 10. wyroczen helped me do it)
Click to expand...
Click to collapse
What's this?
View attachment fix-buffer-Magisk.zip
View attachment fix-buffer-TWRP.zip
Well gonna try it on Android 10 Pixel Experience and report back with Gcam 7
Ainz_Ooal_Gown said:
Well gonna try it on Android 10 Pixel Experience and report back with Gcam 7
Click to expand...
Click to collapse
lib from android 9, Android 10 may not work.
bsg19071979 said:
lib from android 9, Android 10 may not work.
Click to expand...
Click to collapse
Well the magisk module didn't show up at all
Ainz_Ooal_Gown said:
Well the magisk module didn't show up at all
Click to expand...
Click to collapse
View attachment fix-buffer-Magisk_Q.zip
working great on stock, just used latest GCam_7.3.018_Urnyx05-v1.5.apk
EDIT: it seems after using stock camera, the lag is back. Stock camera crashed for me but worked again after restart. For anyone who wants to revert the change I have attached original, untouched file from Pie firmware.
Scratch that, my phone reverts to default file after reboot, something is not right with Magisk, will have to check, sorry for confusion
If I'm unrooted, can I use this?
Does anyone know how to manually replace the lib file without using TWRP? I'm rooted and have tried several root file managers. Seems like the original file is still there after reboot.
This is for stock ROMs, I am currently using 20f:
you have to disable verity:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
you can dump vbmeta.img using qfil
You have to install Magisk also, so dump with qfil boot_a and boot_b, upload them to your phone and patch them with Magisk Manager, back to qfil and flash patched versions back. You will have working root.
Use any File Manager with root to replace com.qti.chi.override.so (SHA1: DE4248C89864CFD676522FE8BD19AA03D4A2BF3E) inside /vendor/lib/hw/
Use external SD card in this process, will save you a lot of headaches and don't use TWRP. For some reasons it doesn't work on stock.
Thanks. I learn something every day. Motorollas disable dm-verity automatically after unlocking the bootloader, so never had to do this seperatly before.
Will the fastboot commands wipe user data?
Does "adb disable-verity" work on those phones as well? Or must it be done in fastboot?
it doesn't wipe user data
well, this was working on 20e fw but it doesn't work anymore on 20f fw, I can't mount /vendor or /system as RW in TWRP
could be a TWRP issue. I'm on 20e currently. Is there a 20f for US retail?
banesi said:
you have to disable verity:
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img
you can dump vbmeta.img using qfil
Click to expand...
Click to collapse
Worked great to disable Verity! Thank you. Took me a moment to realize that I had to copy the vbmeta partitions first, using QFIL. Then rewrite the partitions using the fastboot commands from your post.
The post above should be sticky or prerequisite for the OP.
Unfortunately even with the lagfix file replacing the stock file, Im stll getting the same lag in GCam.
For some unkown reason even when you magisk/twrp buffer fix, file stays the same
---------- Post added at 12:16 ---------- Previous post was at 11:34 ----------
bsg19071979 said:
View attachment 4994459
View attachment 4994461
Click to expand...
Click to collapse
well, this is wrong, lib files inside those zips are just stock files, not modified files
I have updated my previous post.
That did the trick. Gcam working great now!
Had to get the file again, this time downloading it directly from celsoazevedo.com. This time the SHA1 matched what you had in your post above.
For reference, using GCam 7.3 from Urnyx05 v1.5 with the config file below. Not claiming it's the perfect, but so far so good....
https://f.celsoazevedo.com/file/cfiles/gcm1/GCam_7.3.018_Urnyx05-v1.5.apk
Config file
https://www.celsoazevedo.com/files/android/p/f/2020/02/7.2uryny2.1.xml
banesi said:
For some unkown reason even when you magisk/twrp buffer fix, file stays the same
---------- Post added at 12:16 ---------- Previous post was at 11:34 ----------
well, this is wrong, lib files inside those zips are just stock files, not modified files
I have updated my previous post.
Click to expand...
Click to collapse
when I use your override file on andriod 10( lg v40,v30b), some funtion has bug , cine video mode can't see any thing but full green screen. hope U can do something, THX!
Sadly this breaks HDR 10 and cine video on stock Q right now. Hope you'd be able to look at this issue! Good job with the buffer fix
skeeeee said:
Sadly this breaks HDR 10 and cine video on stock Q right now. Hope you'd be able to look at this issue! Good job with the buffer fix
Click to expand...
Click to collapse
Same here! But this doesn't break these features. It just gives green screen in viewfinder but records the video normally
Related
Did some learning, some digging, and found what is so broken on the current TWRP builds that are out there.
We're missing one line in the fstab.qcom
Code:
/dev/block/bootdevice/by-name/oem /oem ext4 ro wait
So I did the simple fix. Took TWRP 3.2.1-R20 (which supports backing up OEM) and added that line to fstab.qcom.
You can now backup & restore the OEM partition using TWRP and it isn't broken for OTAs.
EDIT: backup & Restore might still be broken, but it does not damage the OEM just booting TWRP. Looking into how to backup via image instead of backup via TWRP GUI.
Edit2: I've fixed the OEM backup so it now backs up as an image like /system does. This takes up 768MB of space compared to the previous 141MB, but for working OTAs it's worth it. Enable compression and the extra space isn't wasted. I've uploaded the fix as well and updated the link at the bottom of the post.
To add this fix to TWRP for devs, change the line in \etc\recovery.fstab from
Code:
/oem ext4 /dev/block/bootdevice/by-name/oem flags=backup=1;display="OEM"
to
Code:
/oem emmc /dev/block/bootdevice/by-name/oem flags=backup=1;display="OEM"
Adding that as an additional line will allow us to pick between a bitwise perfect OEM backup or just a basic "copied files" backup.
In the meantime, you can back up OEM using DD.
You can install Magisk in TWRP without breaking OEM.
I've tested and confirmed this on my XT1806 but it should work with all of them.
I've linked to the file at the bottom of this post. It's able to be directly flashed over your existing TWRP.
To fix your OEM partition for future updates:
Identify what software you're running. If you are running the first Oreo OTA build, just download the full firmware file and fastboot flash the OEM partition again. Then OTA should take
If you are running October patch, you will need to fastboot flash the first Oreo OTA OEM file and then ADB Sideload the October OTA on top of it. Then you're up to date. The October OTA can update just the OEM partition without needing to patch the rest.
If you are running Nougat, same applies, Just fastboot flash whatever OEM you are currently on and then OTAs should work.
To all TWRP devs, please add the OEM RO line to your fstab.qcom so we don't run into this in the future. it's a simple fix.
Edit3: I've added the ability to backup the Persist file as well since that's not included in standard R20. link updated as well.
DOWNLOAD:
https://drive.google.com/open?id=1FRWyndazNcfDugHExAOvSvDdOfy53PYq
That's pretty cool
squirting the #hit out of me!
thx
Thanx. Flashing via adb succeeded, installed Magisk 19.1 at once, System booted normally. Fine
But was is meant by "In the meantime, you can back up OEM using DD."? May i not take a TRWP backup? Using stock oreo 8.1.0, and plan to flash a custom rom, maybe pie...
Thanx in advance!
Klaus R said:
Thanx. Flashing via adb succeeded, installed Magisk 19.1 at once, System booted normally. Fine
But was is meant by "In the meantime, you can back up OEM using DD."? May i not take a TRWP backup? Using stock oreo 8.1.0, and plan to flash a custom rom, maybe pie...
Thanx in advance!
Click to expand...
Click to collapse
Hi,
My bad. Just use the current link and do a regular backup. That line is out of date when I was still experimenting
pizzaboy192 said:
Hi,
My bad. Just use the current link and do a regular backup. That line is out of date when I was still experimenting
Click to expand...
Click to collapse
Sorry for asking, being quite an newbie. "use the current link and do a regular backup" means, use Backup feature in TWRP normally?
Klaus R said:
Sorry for asking, being quite an newbie. "use the current link and do a regular backup" means, use Backup feature in TWRP normally?
Click to expand...
Click to collapse
Yup! I believe the file is called twrp-sanders-r20-oemsafe (might also mention persist)
I just did a rebbot in fastboot mode, from there to recovery, TWRP starts. Excellent. But internal storage (Data) is 0MB? Did i forget something?
Tanx a lot for your assistance
Klaus R said:
storage (Data) is 0MB
Click to expand...
Click to collapse
Seems to be encryption problem. https://forum.xda-developers.com/doogee-mix/how-to/fixed-how-to-remove-data-encryption-twrp-t3757595
Can't fix the problem. First everything's fine, twrp's backup shows some Mb in /data (caused by magisk or su). So decryption is working at that point. Then, after booting into system and doing some settings, root is still there (rootchecker), but back to twrp there will be /data again with 0MB.
Anyone a hint? Main purpose of twrp for me is taking backups (before trying custom roms)
Running stock oreo 8.1.0 Europe with 01.02.19 sec patches
Need the TWRP installer please
Need the TWRP installer please
does this, or any similar twrp increase the chances of getting volte (which works on my xt1806 in stock oreo when i use the lenovo recovery app) up and running on say RR pie builds (which i was using unpatched twrp 3.2.1-r16 to install RR and gapps, then booting, updating OTA, then going back to install the TWRP 3.3 from this forum to flash Magisk)?
---------- Post added at 02:33 PM ---------- Previous post was at 02:31 PM ----------
Souravskrba said:
Need the TWRP installer please
Click to expand...
Click to collapse
the "installer" is either fastboot from your PC or install from your current TWRP (if you already have another version installed) hit install then >> flash img button)
hi this fixes the error 1 when flashing magisk?
thanks
M4T145 said:
hi this fixes the error 1 when flashing magisk?
thanks
Click to expand...
Click to collapse
Probably no. Search for Treble TWRP Moto G5s Plus on google. You need a trebelized TWRP in order to flash magisk.
link doesn't exist.
Please update the link to the file. Gdrive page results in URL not found.
I'm confused about the current level of support of TWRP for Moto G5s+ "sanders" - Latest TWRP (3.4.0.0) runs using fastboot boot but can't be installed. Older versions are all hosted on unofficial sites and have broken links or seem untrustworthy. Does anyone has a link to a legit TWRP for sanders which is recent, works, and is hosted on a trustworthy site?
krist0ph3r said:
I'm confused about the current level of support of TWRP for Moto G5s+ "sanders" - Latest TWRP (3.4.0.0) runs using fastboot boot but can't be installed. Older versions are all hosted on unofficial sites and have broken links or seem untrustworthy. Does anyone has a link to a legit TWRP for sanders which is recent, works, and is hosted on a trustworthy site?
Click to expand...
Click to collapse
Download the one that's there in the Sanders Telegram group.
krist0ph3r said:
I'm confused about the current level of support of TWRP for Moto G5s+ "sanders" - Latest TWRP (3.4.0.0) runs using fastboot boot but can't be installed. Older versions are all hosted on unofficial sites and have broken links or seem untrustworthy. Does anyone has a link to a legit TWRP for sanders which is recent, works, and is hosted on a trustworthy site?
Click to expand...
Click to collapse
I've had troubles with recent versions of TWRP too, mostly with encryption . That's why I stuck with 3.2.1.r22; it's the only one I've had no trouble with so far. It doesn't support OTA update, but I've had no problem with manual updates. FYI I'm using Arrows 11.
It may not be as trustworthy as you'd hope for, but here's the link anyway: https://upload.disroot.org/r/NaH0_6dV#DZn8wBuuDERBm+db05p15OPzT5F/f2LFvs+IT5E54O4=
sBinnala said:
Download the one that's there in the Sanders Telegram group.
Click to expand...
Click to collapse
link?
okayk said:
I've had troubles with recent versions of TWRP too, mostly with encryption . That's why I stuck with 3.2.1.r22; it's the only one I've had no trouble with so far. It doesn't support OTA update, but I've had no problem with manual updates. FYI I'm using Arrows 11.
It may not be as trustworthy as you'd hope for, but here's the link anyway: https://upload.disroot.org/r/NaH0_6dV#DZn8wBuuDERBm+db05p15OPzT5F/f2LFvs+IT5E54O4=
Click to expand...
Click to collapse
no luck, same error that i get with 3.4.0.0:
Code:
> fastboot flash recovery "twrp-sanders-treble-new(ByGeneticEnginer).img"
target reported max download size of 534773760 bytes
sending 'recovery' (14636 KB)...
OKAY [ 0.320s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.179s]
finished. total time: 0.503s
October security patches released...
https://dl.google.com/dl/android/aosp/blueline-qp1a.191005.007-factory-c36610c6.zip
Worked exactly the same as the 10 and .C3 build for me. Flash-all (minus -w) and patched boot in Magisk. No issues.
4.3 MB from the C3 update.
After the C3 update I had an improvement in the battery's life but after few days was the same. I hope this will better this time.
Edit : multi-tasking freeze is here again...
sliding_billy said:
Worked exactly the same as the 10 and .C3 build for me. Flash-all (minus -w) and patched boot in Magisk. No issues.
Click to expand...
Click to collapse
It worked fine for 10 and .c3 build, but magisk_patched.img does not work for me. It installs fine and the phone boots up fine but magisk says it is not installed
Code:
~/Downloads/pixel3/blueline-qp1a.191005.007$ sha256sum magisk_patched.img
46432e0feae1b97f631165a10eb0049041c2e6fffce89a6a2733bf8aee9dc9ac magisk_patched.img
Do you have the same sha256sum? I used canary build of magisk to patch it.
---------- Post added at 09:49 PM ---------- Previous post was at 09:36 PM ----------
wildnux said:
It worked fine for 10 and .c3 build, but magisk_patched.img does not work for me. It installs fine and the phone boots up fine but magisk says it is not installed
Code:
~/Downloads/pixel3/blueline-qp1a.191005.007$ sha256sum magisk_patched.img
46432e0feae1b97f631165a10eb0049041c2e6fffce89a6a2733bf8aee9dc9ac magisk_patched.img
Do you have the same sha256sum? I used canary build of magisk to patch it.
Click to expand...
Click to collapse
Nevermind. I had to patch with beta version of magisk. Version: 19.4 (19400) and it worked.
wildnux said:
It worked fine for 10 and .c3 build, but magisk_patched.img does not work for me. It installs fine and the phone boots up fine but magisk says it is not installed
Code:
~/Downloads/pixel3/blueline-qp1a.191005.007$ sha256sum magisk_patched.img
46432e0feae1b97f631165a10eb0049041c2e6fffce89a6a2733bf8aee9dc9ac magisk_patched.img
Do you have the same sha256sum? I used canary build of magisk to patch it.
---------- Post added at 09:49 PM ---------- Previous post was at 09:36 PM ----------
Nevermind. I had to patch with beta version of magisk. Version: 19.4 (19400) and it worked.
Click to expand...
Click to collapse
Good deal. I just never leave Canary for my Pixel 3 and Pixel 3 XL despite having other devices on stable or Beta.
what Google Play System update patch level are you guys on? I'm back to August, 1 from September, 1 after installing the October OTA.... so what's going on here?
Installed yesterday. Now wireless provider signal only shows as 4G, no LTE.
Can I use the same magdisk patched image from C3? Or should I pull the boot image from this update?
gmmurphy said:
Can I use the same magdisk patched image from C3? Or should I pull the boot image from this update?
Click to expand...
Click to collapse
It might work, but I think it is asking for trouble. Try the installation method at https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
It is much simpler, and you don't need to patch boot images. I just did it an hour ago using the latest Magisk from the Canary channel. I saw a report in another thread the latest from the Beta channel also works. I don't think it works with Magisk from the stable channel, but have not tried it.
dcarvil said:
It might work, but I think it is asking for trouble. Try the installation method at https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
It is much simpler, and you don't need to patch boot images. I just did it an hour ago using the latest Magisk from the Canary channel. I saw a report in another thread the latest from the Beta channel also works. I don't think it works with Magisk from the stable channel, but have not tried it.
Click to expand...
Click to collapse
Did you uninstall all the modules before doing this?
georgs_town said:
Did you uninstall all the modules before doing this?
Click to expand...
Click to collapse
No, I did not uninstall the modules, I just followed the instructions in the tutorial.
I was able to flash the factory image by running the "flash.bat" script with "-W" removed. Security update is dated Oct 5, Google Play system is dated Sept 1. Just to be safe, I uninstalled Cerberus before running the script as Cerberus caused me issues transitioning from Android Pie to Android 10 last month.
Other than Cerberus, I only have magisk for rooting, no modules loaded, no edXposed. I re-routed using the latest Canary build for Magisk, patching the boot.img and then flashing the magisk_patched.img in fastboot mode.
So I'm having another major problem. When I updated to 10 from 9 running dirty unicorns, everything flashed fine except for the image update zip. I remember it had something to do with the active slot but I cant remember for the life of me what I did last time to get the image to flash. Currently when I run flash all bootloader and radio flash fine, but flashing the image zip my phone boots into the fastbootd recovery screen and fastboot command screen shows fastboot: error: command failed. Sending sparse product b FAILED.
Any help would be greatly appreciated. Right now I'm stuck in fastboot on my phone.
Edit: I just did a factory wipe and it's flashing fine now. I'm guessing it had something to do with the magisk patched boot img I was using. I really don't know what the problem was.
I am on Android 10 and can't install latest small security update. https://i.imgur.com/0TMV5i8.png
Before I've restored image according to Magisk doc https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Ipeacocks said:
I am on Android 10 and can't install latest small security update. https://i.imgur.com/0TMV5i8.png
Before I've restored image according to Magisk doc https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Click to expand...
Click to collapse
Just download the full factory image, edit the flash all file to remove the -w, and then flash that in fastboot mode. Make sure you save the flash all file and the -w is removed before you use it. Trying to take the ota on a rooted device doesn't work well.
@jd1639 w/o -w root will disappear but my personal data on phone persists?
Ipeacocks said:
@jd1639 w/o -w root will disappear but my personal data on phone persists?
Click to expand...
Click to collapse
Yes, you'll loose root but your data will all be there. You'll have to move a copy of the stock boot.img file to your device, let magisk patch it, then move the patched file to your pc and flash that with fastboot. Almost all of us do this process with each update.
@jd1639 Are you talking about this `-w`?
https://imgur.com/nlbZdht
Ipeacocks said:
@jd1639 Are you talking about this `-w`?
https://imgur.com/nlbZdht
Click to expand...
Click to collapse
No. Download the factory image to your pc and extract it, it's a zip file. In there you'll see a flash-all.bat file. Edit that. I use notepad ++. Then save it and just double click on the edited file (I'm assuming your using a windows pc). There is also another zip file you'll find after you've extracted the factory image. Extract that too and you'll find the boot.img file you'll need to patch with magisk for root.
Edit, sorry, I didn't look at the image you uploaded that closely. It is the -w I was referring to.
VERY IMPORTANT:
Please make sure your boot.img version matches the ROM version . that's mean if you update your device then you have to use patch boot.img from new recovery rom.never use the old one. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
Yes you can root your phone without data loss. You do not need to you type so much command line. You have to patch the stock boot image file with magisk manager. Then you have to download a a blank vbmeta.img file.(link in this post)
Then run this command
fastboot flash vbmeta vbmeta.img
fastboot flash boot patch-boot.img
%%replace patch-boot as your file name...
I guarantee you no data loss.
Remember one thing...
You must patch the correct boot image of your rom... If you to flash a wrong version of bhoot image then you have some problem.
Suppose you update miui global 11.0.5.0 from 11.0.4.0 and you use 11.0.4.0 version patch boot image file....
Then your device boot up but you can not play any music .....i do this dump thing.....but do not worry just flash currect patch boot image and your problem is gone...
Shas45558 said:
Yes you can root your phone without data loss. You do not need to you type so much command line. You have to patch the stock boot image file with magisk manager. Then you have to download a a blank vbmeta.img file.
https://forum.hovatek.com/thread-32719.html
Go to method 3....log in to download vbmeta.img file.
Then run this command
fastboot flash boot patch-boot.img
fastboot flash vbmeta vbmeta.img
%%replace patch-boot as your file name...
I guarantee you no data loss.
Remember one thing...
You must patch the correct boot image of your rom... If you to flash a wrong version of bhoot image then you have some problem.
Suppose you update miui global 11.0.5.0 from 11.0.4.0 and you use 11.0.4.0 version patch boot image file....
Then your device boot up but you can not play any music .....i do this dump thing.....but do not worry just flash currect patch boot image and your problem is gone...
Click to expand...
Click to collapse
Hey @Shas45558, I can't root MIUI V11.0.7.0.Q having tried these steps on a friend's phone yesterday. It worked on my phone on V11.0.50.Q but I also installed that update though my bootloader is still locked as you may know
nielsync said:
Hey @Shas45558, I can't root MIUI V11.0.7.0.Q having tried these steps on a friend's phone yesterday. It worked on my phone on V11.0.50.Q but I also installed that update though my bootloader is still locked as you may know
Click to expand...
Click to collapse
Do u flash vbmeta.img?? (Download from this post)
It workes for me every time...
When any update appires you should download full recovery rom reather then otq update.
Then extract and patch boot which is insiDe the recovery rom...
It will must work...
Shas45558 said:
Do u flash vbmeta.img?? (Download from this post)
It workes for me every time...
When any update appires you should download full recovery rom reather then otq update.
Then extract and patch boot which is insiDe the recovery rom...
It will must work...
Click to expand...
Click to collapse
That's exactly what I did. Downloaded the full recovery rom and extracted it. Patched the boot.img inside images folder with Magisk canary and after copied it to my PC and flashed it via fastboot. I then flashed the vbmeta after. Do you mind sharing with me your patched boot image for V.11.0.7Q? Maybe I'll have luck with that otherwise I did everything right. Its really strange.
nielsync said:
That's exactly what I did. Downloaded the full recovery rom and extracted it. Patched the boot.img inside images folder with Magisk canary and after copied it to my PC and flashed it via fastboot. I then flashed the vbmeta after. Do you mind sharing with me your patched boot image for V.11.0.7Q? Maybe I'll have luck with that otherwise I did everything right. Its really strange.
Click to expand...
Click to collapse
You should use your phone and magisk manager To patch boot image file...
Do not use computer to patch it
I give the boot file in this post which root your redmi 9 based on global v11.0.7.0....
Do not flash it on outher version...
Extract mboot7.tar you get mboot7.img....
Flash it and enjoy root on globalv11.0.7.0....
Do not forget to flash vbmeta.img....
Flash vbmeta file then patch boot file..
Good luck..
Shas45558 said:
You should use your phone and magisk manager To patch boot image file...
Do not use computer to patch it
I give the boot file in this post which root your redmi 9 based on global v11.0.7.0....
Do not flash it on outher version...
Extract mboot7.tar you get mboot7.img....
Flash it and enjoy root on globalv11.0.7.0....
Do not forget to flash vbmeta.img....
Flash vbmeta file then patch boot file..
Good luck..
Click to expand...
Click to collapse
Thanks a lot it worked!!! :good:
I've been patching using Magisk Manager canary version on the phone. What version of Magisk Manager did you use It's really strange
nielsync said:
Thanks a lot it worked!!! :good:
I've been patching using Magisk Manager canary version on the phone. What version of Magisk Manager did you use It's really strange
Click to expand...
Click to collapse
I use this version of magisk manager and it always work
Shas45558 said:
I use this version of magisk manager and it always work
Click to expand...
Click to collapse
Thanks. I've been using Magisk Manager beta/canary and it seems it does not patch the boot image properly. You are the best.
Thanks for the post. It helped me to root my redmi note 9.
nielsync said:
Thanks. I've been using Magisk Manager beta/canary and it seems it does not patch the boot image properly. You are the best.
Click to expand...
Click to collapse
Welcome. Redmi 9 and redmi note 9 are are based on same chipset mt6768....
And so the process help you. I think it is the same to root any device running on Android 10.
And vbmeta.img which I provide upper post, is a universal vbmeta.img. you can use it to flash any Android device which has vbmeta partition because this vbmeta.img is a dummy file or you can call it as a blank file...
Shas45558 said:
Welcome. Redmi 9 and redmi note 9 are are based on same chipset mt6768....
And so the process help you. I think it is the same to root any device running on Android 10.
And vbmeta.img which I provide upper post, is a universal vbmeta.img. you can use it to flash any Android device which has vbmeta partition because this vbmeta.img is a dummy file or you can call it as a blank file...
Click to expand...
Click to collapse
My issues was patching using the canary version of Magisk Manager which isn't stable enough and was probably not patching the boot image properly as opposed to Magisk Manager 7.5.1 which is the stable version. Nice explanation on the vbmeta.img file.
VERY IMPORTANT:
Please make sure your ROM version matches the ROM version of those patched boot image and files. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
For the post author:
Thanks for your effort
I understand you are trying to help and that you put a note at the end of your post. But please make it clear at the BEGINING, that this method is valid for this specific ROM Version "xx.x.xx.x.x"
I guess this still doesn't unlock the bootloader, and what about system updates?
Kiwironic said:
VERY IMPORTANT:
Please make sure your ROM version matches the ROM version of those patched boot image and files. If they mismatch you might brick your phone and MediaTek phones are HELL to unbrick.
YOU HAVE BEEN WARNED.
For the post author:
Thanks for your effort
I understand you are trying to help and that you put a note at the end of your post. But please make it clear at the BEGINING, that this method is valid for this specific ROM Version "xx.x.xx.x.x"
Click to expand...
Click to collapse
Ok i do ir on top and bottom of the post and thanks for your advice:good::good:
I have an issue. I cannot install any custom recovery on Redmi 9, no matter how much I try (Twrp or PBRP). Every time the phone reboots directly. There is anyone that can help me?
rizelgeorgel said:
I have an issue. I cannot install any custom recovery on Redmi 9, no matter how much I try (Twrp or PBRP). Every time the phone reboots directly. There is anyone that can help me?
Click to expand...
Click to collapse
Download pbrp from official website.then extract it and you will get a .img file.flash it via fastboot mood and the cmd is
fastboot flash recovery pbrp.img
*Change pbrb.img according to your file name.
One big question..did you unlock your bootloader and root your device?
Thank you very much! I succeeded according to your advice!
shas hows pbrp?
regarding flashing?
mhark.moby said:
shas hows pbrp?
regarding flashing?
Click to expand...
Click to collapse
Pbrp is in beta testing....so it has some bug and there's no use to install..
Buenas tardes tengo problemas al cargar el parche de magisk en redmi 9. Cuando cargo el boot.img parchado de magisk el tlfn queda en bootloop estoy en la version 11.0.8 global.
I have camera issues. After ubl unlocked and rooted. When i record in my camera, my phone reboot on itself. So i think the problem is my patched boot.img and vbmeta.img Please reply me asap
inigueal said:
I have camera issues. After ubl unlocked and rooted. When i record in my camera, my phone reboot on itself. So i think the problem is my patched boot.img and vbmeta.img Please reply me asap
Click to expand...
Click to collapse
Same with me after UBL from B.53. Record camera doesn't work. Rebooting....
Doddy_Doda said:
Same with me after UBL from B.53. Record camera doesn't work. Rebooting....
Click to expand...
Click to collapse
do you fixed the problem or still fixing?
Still fixing on custom rom PE11. I have tried various cameras but they still can't record video. Always freezes while recording, and the result is an error.
The previous thing I did UBL during the B.53 stockrom. I disable verification flash vbmeta according to the instructions and flash PBRP then flash this rom. Then I returned it to B.53 stock rom when recording video is normally only stock rom B.53 can do it.
Doddy_Doda said:
Still fixing on custom rom PE11. I have tried various cameras but they still can't record video. Always freezes while recording, and the result is an error.
The previous thing I did UBL during the B.53 stockrom. I disable verification flash vbmeta according to the instructions and flash PBRP then flash this rom. Then I returned it to B.53 stock rom when recording video is normally only stock rom B.53 can do it.
Click to expand...
Click to collapse
oh i just realized that my magisk patched boot.img was b.49 but my rmx2001 is in b.53. so just need to reflash stock/original b.53 boot.img and vbmeta.img
inigueal said:
oh i just realized that my magisk patched boot.img was b.49 but my rmx2001 is in b.53. so just need to reflash stock/original b.53 boot.img and vbmeta.img
Click to expand...
Click to collapse
i got that magisk patched boot.img from another post, from someone with username veez or idk
inigueal said:
oh i just realized that my magisk patched boot.img was b.49 but my rmx2001 is in b.53. so just need to reflash stock/original b.53 boot.img and vbmeta.img
Click to expand...
Click to collapse
Heya, i don't had this sort of problems
Can you give me patched vbmeta + boot for B53?
(also, tried to update my phone from b49 to b53 but got recovery loop, and i must go to authorized service center to fix my phone cuz i can't install custom recover, some sort of fixes for this?)
Received the tablet in the mail, and now looking to root via Magisk (and ideally a custom recovery like TWRP).
I found this video describing a way to download the stock ROM from Teclast:
Has anyone achieved root on this device? Can anyone confirm Treble ROM compatability for GSI A/B?
On the russian forum 4pda somebody posted the patched boot.img and vbmeta.img files required for rooting.
If anyone is registered on the forum he might try to grab the files, for me it gives 404 error when trying to download, though im not registered..
Teclast T40 Plus - Обсуждение - 4PDA
Teclast T40 Plus - Обсуждение, Планшет, 10,4
4pda.to
NightLord said:
On the russian forum 4pda somebody posted the patched boot.img and vbmeta.img files required for rooting.
If anyone is registered on the forum he might try to grab the files, for me it gives 404 error when trying to download, though im not registered..
Teclast T40 Plus - Обсуждение - 4PDA
Teclast T40 Plus - Обсуждение, Планшет, 10,4
4pda.to
Click to expand...
Click to collapse
Good find, but the link no longer works. It gives me a 404: https://4pda.to/forum/dl/post/24458874/T40_Plus_root.7z
My guess is it would work if we were logged in, its just that i cant create an account since i cannot get past rhe russian captcha
Yeah, I also can't register without knowing the Russian keyboard layout and how to identify the characters. Perhaps someone with this knowledge can register and attach the required images to root here?
Slightly off topic while someone manages to grab the files from 4pda
Do you actually get 50000+ gpu score in antutu with the t40? I have the maxpad i11 which is in theory the same hardware, and I only get 42000. I even flashed the t40 firmware on the device, but gpu score didnt budge.
To be on topic: if you want root, you may also flash phhuson's treble GSI rom-s. I tried his version of android 12, and it works, and has root.
NightLord said:
Slightly off topic while someone manages to grab the files from 4pda
Do you actually get 50000+ gpu score in antutu with the t40? I have the maxpad i11 which is in theory the same hardware, and I only get 42000. I even flashed the t40 firmware on the device, but gpu score didnt budge.
To be on topic: if you want root, you may also flash phhuson's treble GSI rom-s. I tried his version of android 12, and it works, and has root.
Click to expand...
Click to collapse
These ROMs? https://github.com/phhusson/treble_experimentations/releases
ForgottenSolstace said:
These ROMs? https://github.com/phhusson/treble_experimentations/releases
Click to expand...
Click to collapse
Yes.
You can either install them via DSU as dual-boot OS beside your stock rom, or just flash system partition (inside super) via fastbootd (you are going to have to delete product partition to have enough space inside super for the system image) and use them as primary OS.
Gotcha:
Just ordered a T40 Plus, did you manage to get root?
Flashing the boot and vbmeta partitions with the images attached to my previous post will grant you root on the stock t40 plus firmware.
I myself moved on to using android 12 gsi images.
NightLord said:
Flashing the boot and vbmeta partitions with the images attached to my previous post will grant you root on the stock t40 plus firmware.
I myself moved on to using android 12 gsi images.
Click to expand...
Click to collapse
Hi NightLord, can you explain easily the root steps for this device? do we need the software that we see in the video at the beginning or is ADB enough?
Marynboy78 said:
Hi NightLord, can you explain easily the root steps for this device? do we need the software that we see in the video at the beginning or is ADB enough?
Click to expand...
Click to collapse
Hey,
You need to use the spreadtrum research download tool (RDT), not the one seen in tthe video in the first post.
See this guide on how to use the RDT.
The basic concept is that you need to download the official firmware from the teclast homepage, load it into RDT, uncheck all partitions (save for those that are compulsory and cannot be unchecked), select only boot and vbmeta partitions, and as images to be flashed you need to browse the ones found in the archive I posted, instead of those found in the original firmware package.
Begin flashing, your device will perform a hard reset, and then you should boot into rooted firmware.
Theoretically you should be able to flash both partitions (boot and vbmeta) via fastboot too, but when I tried, i got an error message saying boot.img was too large or something. Flashing via RDT went without problem. The only caveat is that flashing via RDT will always hard reset your device.
NightLord said:
Flashing the boot and vbmeta partitions with the images attached to my previous post will grant you root on the stock t40 plus firmware.
I myself moved on to using android 12 gsi images.
Click to expand...
Click to collapse
How to install android 12 gsi on this device?
marinzrncic said:
How to install android 12 gsi on this device?
Click to expand...
Click to collapse
First you need to unlock the bootloader. You need to be patient when you are flashing the unlock, my device took some 10 mins to complete, but in the end it succeeded (on the 2nd try, mind you.)
Here is a guide for unlocking in windows, though it is in russian (Im attaching the required modified fastboot in case you cannot download it from 4pda).
When you're done unlocking the bootloader, you've already done the hard part.
Next, download your preferred GSI image from Google, from phhusson's, or whatever else you find (Pixel Experience for eg.). Mind you, that the image from Google contains the Android 12L version.
Next you will flash your active system partition with the GSI image. To do that, initate ADB connection to your tablet, then enter fastbootd, by issuing the command:
fastboot reboot fastboot
you can check your active system slot by:
fastboot getvar all (but it will be slot "a" unless you have received an OTA update previously)
you need to free up some space by deleting the logical partition product otherwise you wont be able to flash your gsi:
fastboot delete-logical-partition product_a
(in case your active slot is "a")
then you can move forward to actually flashing your GSI:
fastboot flash system_a whateverisyourimagefilename.img
Lastly, you will need to wipe userdata, which can be done on the tablet by switching to recovery from fastbootd, and then selecting wipe userdata, or maybe the fastboot -w command does the same.
Reboot, and enjoy your GSI.
I'm using the Google 12L GSI, and it is perfectly stable for daily usage. For bluetooth audio to work, you will have to disable bluetooth a2dp hardware offload in developer options.
NightLord said:
First you need to unlock the bootloader. You need to be patient when you are flashing the unlock, my device took some 10 mins to complete, but in the end it succeeded (on the 2nd try, mind you.)
Here is a guide for unlocking in windows, though it is in russian (Im attaching the required modified fastboot in case you cannot download it from 4pda).
When you're done unlocking the bootloader, you've already done the hard part.
Next, download your preferred GSI image from Google, from phhusson's, or whatever else you find (Pixel Experience for eg.). Mind you, that the image from Google contains the Android 12L version.
Next you will flash your active system partition with the GSI image. To do that, initate ADB connection to your tablet, then enter fastbootd, by issuing the command:
fastboot reboot fastboot
you can check your active system slot by:
fastboot getvar all (but it will be slot "a" unless you have received an OTA update previously)
you need to free up some space by deleting the logical partition product otherwise you wont be able to flash your gsi:
fastboot delete-logical-partition product_a
(in case your active slot is "a")
then you can move forward to actually flashing your GSI:
fastboot flash system_a whateverisyourimagefilename.img
Lastly, you will need to wipe userdata, which can be done on the tablet by switching to recovery from fastbootd, and then selecting wipe userdata, or maybe the fastboot -w command does the same.
Reboot, and enjoy your GSI.
I'm using the Google 12L GSI, and it is perfectly stable for daily usage. For bluetooth audio to work, you will have to disable bluetooth a2dp hardware offload in developer options.
Click to expand...
Click to collapse
thank you very much
NightLord said:
Hey,
You need to use the spreadtrum research download tool (RDT), not the one seen in tthe video in the first post.
See this guide on how to use the RDT.
The basic concept is that you need to download the official firmware from the teclast homepage, load it into RDT, uncheck all partitions (save for those that are compulsory and cannot be unchecked), select only boot and vbmeta partitions, and as images to be flashed you need to browse the ones found in the archive I posted, instead of those found in the original firmware package.
Begin flashing, your device will perform a hard reset, and then you should boot into rooted firmware.
Click to expand...
Click to collapse
Did we need unlock bootloader first or we can flash root without unlock bootloader?
Thx
ardianz said:
Did we need unlock bootloader first or we can flash root without unlock bootloader?
Thx
Click to expand...
Click to collapse
I have no idea because I havent tried yet. But I would guess it might be possible that you can flash the patched boot.img along with vbmeta.img with RDT, and it might work, if they do pass Android Verified Boot check.
NightLord said:
Gotcha:
Click to expand...
Click to collapse
will these files work on android 10 or android 11? I have a unisoc T618 and unisoc T310. I was hoping to flash both tablets to get root access.
and also do you have a twrp for T40_plus or any unisoc generic twrp?