Why won't Team Win make TWRP for the pixel 6/7 line? Maybe I don't know something and there are some restrictions? This would really make it easier to create/install firmware and GSI firmware
TWRP is generally of little use on Pixel devices, which do not have a recovery partition. Since the bootloaders are easily unlocked and accept flashing commands, firmware can be flashed via ADB.
Installing GSIs is easy, just flash the system image to /system.
V0latyle said:
TWRP is generally of little use on Pixel devices, which do not have a recovery partition. Since the bootloaders are easily unlocked and accept flashing commands, firmware can be flashed via ADB.
Installing GSIs is easy, just flash the system image to /system.
Click to expand...
Click to collapse
I have spent more than 6 days installing Moto UI,OneUI,MIUI. Nothing helped, you need permissive magisk, which can only be installed via TWRP, and if you put it from a task in the system, then it does not want to work... Maybe I'm doing something wrong, if it's not difficult, could you give me instructions on installing GSI?
Max0nchik said:
I have spent more than 6 days installing Moto UI,OneUI,MIUI. Nothing helped, you need permissive magisk, which can only be installed via TWRP, and if you put it from a task in the system, then it does not want to work... Maybe I'm doing something wrong, if it's not difficult, could you give me instructions on installing GSI?
Click to expand...
Click to collapse
I literally just told you. GSIs come as an image. Flash to /system. Only works if the system partition is bigger than the image. Not sure how to safely resize.
There's also several guides around XDA that can help you. There's also the official Android Source guide.
Kind of wanted to follow up...
If recovery on Pixel isn't that useful (I don't know how much I agree with that. TWRP has saved me multiple times on my Pixel 5 and 2XL in the past), what is everyone doing for backing up/restoring the entire phone image?
100% agree. Both myself and a friend of mine never try new ROMs because we don't have a perfect backup of the current setup.
Max0nchik said:
I have spent more than 6 days installing Moto UI,OneUI,MIUI. Nothing helped, you need permissive magisk, which can only be installed via TWRP, and if you put it from a task in the system, then it does not want to work... Maybe I'm doing something wrong, if it's not difficult, could you give me instructions on installing GSI?
Click to expand...
Click to collapse
Which MIUI gsi did you try? thanks
mac231us said:
Which MIUI gsi did you try? thanks
Click to expand...
Click to collapse
All a13 on nippon chanel
Max0nchik said:
All a13 on nippon chanel
Click to expand...
Click to collapse
Thanks-I got this in hopes of trying some gsi's - returning it sadly ...and this is not related to your efforts but just in general about this device-am not interested in some super security graphene o/s etc....for that I simply take out my google account and don't sync (re-add it once in a while for some update) (and also remove many google apps, and change permissions in all or lock them down) regardless which flavor of android I am on....even the overlooked snooping gboard
Max0nchik said:
All a13 on nippon chanel
Click to expand...
Click to collapse
from what I recall on mi max 3, mix 2s etc when trying out gsi, there are other files that need to be flashed to make them boot-not sure how that can be done without a custom recovery
Max0nchik said:
I have spent more than 6 days installing Moto UI,OneUI,MIUI. Nothing helped, you need permissive magisk, which can only be installed via TWRP, and if you put it from a task in the system, then it does not want to work... Maybe I'm doing something wrong, if it's not difficult, could you give me instructions on installing GSI?
Click to expand...
Click to collapse
This should fix it without TWRP
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
Same for the b slot. You will find the needed images in the Factory Images ig.
Miustone said:
This should fix it without TWRP
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img
Same for the b slot. You will find the needed images in the Factory Images ig.
Click to expand...
Click to collapse
this not work
DevanteWeary said:
Kind of wanted to follow up...
If recovery on Pixel isn't that useful (I don't know how much I agree with that. TWRP has saved me multiple times on my Pixel 5 and 2XL in the past), what is everyone doing for backing up/restoring the entire phone image?
Click to expand...
Click to collapse
Absolutely agree. I like to randomly change things and revert... Like all the time. This is the first phone I can't really play with the way I like.
https://www.reddit.com/r/Pixel6/comments/r8ylqf/_/i2u2n0p
This should help u understand. Btw. Lineage OS and some ROMs are coming with own Recoveries since quite a Time. Had Xperias for long without TWRP and it sucked. But TWRP has hard Times with modern Android so...
Since short I own a Pixel 6a with Android 13. I want to flash KernelSU in order to root it. How would I do? I'm asking because TWRP method drops out. TIA
unlock bootloader, download pre-patched boot image and flash it from fastboot.
Related
Hey Guys, There is a TON of development for the oneplus 6.
I bought my daughter this phone as it was highly recommended and fairly inexpensive... I really want to achieve 2 things.
TWRP
Magisk
Is that currently possible ?
I need to install a bunch of apps that require root and Magisk is just such an easy program to work around in.
I've poked around but there doesnt seem to be a lot of concise guides.. ussually it's just...
Fastboot devices --> make sure it show's device
Fastboot OEM unlock
wipes the phone
Fastboot boot <twrp.img>
Then from TWRP I flash magisk.zip, from inside the OS, I then boot the magisk manager and everything is cool.
Thank's a ton!
marcusrab said:
Hey Guys, There is a TON of development for the oneplus 6.
I bought my daughter this phone as it was highly recommended and fairly inexpensive... I really want to achieve 2 things.
TWRP
Magisk
Is that currently possible ?
I need to install a bunch of apps that require root and Magisk is just such an easy program to work around in.
I've poked around but there doesnt seem to be a lot of concise guides.. ussually it's just...
Fastboot devices --> make sure it show's device
Fastboot OEM unlock
wipes the phone
Fastboot boot <twrp.img>
Then from TWRP I flash magisk.zip, from inside the OS, I then boot the magisk manager and everything is cool.
Thank's a ton!
Click to expand...
Click to collapse
So, are these things possible ?
marcusrab said:
So, are these things possible ?
Click to expand...
Click to collapse
Yes, totally possible.
Only thing is twrp for this device is somewhat touchy. Some have had to connect a mouse to the phone as touch screen is not working properly.
Not sure on flashing magisk through twrp (havent tried).
An easy way is download the same firmware you are on and extract the boot image, copy to the phone. install magisk manager and patch the boot image, then flash in fastboot.
- You can boot TWRP via fastboot (not fastbootd)
- Magisk can be flashed from TWRP
Yes to both. My G8P has been rooted for a while. I don't need a mouse on mine, but I've read about that.
I have found a method of Teclast P20HD to unlock bootloader which can be found in "https://forum.xda-developers.com/android/help/teclast-p20hd-android-10-tablet-4g-t4141997" and "https://forum.hovatek.com/thread-32287.html", but I'm not sure if that method also works on Teclast M40. If that method works can I restore the bootloader to lock state instead of relock state so I can keep the warranty.
I think re-locking a device's bootloader will not reinstate your device warranty as damage might have occurred when the device was unlocked. Take note that re-locking a bootloader will ensure that the device will only boot to Teclast signed and provided Android images.
AnKHqz said:
I have found a method of Teclast P20HD to unlock bootloader which can be found in "https://forum.xda-developers.com/android/help/teclast-p20hd-android-10-tablet-4g-t4141997" and "https://forum.hovatek.com/thread-32287.html", but I'm not sure if that method also works on Teclast M40. If that method works can I restore the bootloader to lock state instead of relock state so I can keep the warranty.
Click to expand...
Click to collapse
I succeeded in unlocking bootloader of M40 by hovatek's method, but didn't try rooting it.(https://forum.hovatek.com/thread-32674.html)
Here's M40 stock rom. In case you need to recover it...
https://1drv.ms/u/s!AtprAlErUyChn0V0socBsjcnolp8?e=DkJfUa
stock rom in teclast m40 too much error.Is there a better rom to replace? tks
If you suceeded to runlock bootloader, You can replace stock system to gsi system. You need to prepare linux PC (or live usb) and vbmeta.img (included in stock rom).
Generic system images | Android Open Source Project
source.android.com
When you flash, you should use linux PC (Windows pc won't recognize fastbootd mode) and android SDK's adb/fastboot (do not use apt-get install adb/fastboot.).
Download from here -> https://developer.android.com/studio/index.html#downloads
If you want to repalce to Gapps included rom, you need to delete product partiton
> ./fastboot delete-logical-partition product
I tried Android 11 GSI, but boot-looped in OS. Android 10 GSI rom works fine and less error happens.
bercypher said:
If you suceeded to runlock bootloader, You can replace stock system to gsi system. You need to prepare linux PC (or live usb) and vbmeta.img (included in stock rom).
Generic system images | Android Open Source Project
source.android.com
When you flash, you should use linux PC (Windows pc won't recognize fastbootd mode) and android SDK's adb/fastboot (do not use apt-get install adb/fastboot.).
If you want to repalce to Gapps included rom, you need to delete product partiton
> ./fastboot delete-logical-partition product
I tried Android 11 GSI, but boot-rooped in OS. Android 10 GSI rom works fine and less error happens.
Click to expand...
Click to collapse
That's good news for M40. Would you share in a little more detail how you suceeded in doing that? Greatly appreciate it. If we could flash gsi, that would open up a lot of choices.
I have unlocked bootloader successfully.
Which vbmeta.img is needed here? I have extracted vbmeta_system, vbmeta_vendor and vbmeta-sign. Thanks.
Can someone please start a telegram teclast group chat
jngiag said:
I have unlocked bootloader successfully.
Which vbmeta.img is needed here? I have extracted vbmeta_system, vbmeta_vendor and vbmeta-sign. Thanks.
Click to expand...
Click to collapse
According to the source, we have to flash vbmeta. But I flashed vbmeta, vbmeta_system, vbmeta_vendor just in case, as follows.(for unlocked device.)
./fastboot reboot fastboot
./fastboot --disable-verity --disable-verification flash vbmeta vbmeta-sign.img
./fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
./fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
./fastboot erase system
./fastboot delete-logical-partition product
./fastboot --disable-verity --disable-verification flash system (your gsi.img)
./fastboot -w
(When I flashed system, I also disabled verity and verification, but it may be unneccesary)
When I replaced GSI rom, I seemed to forget to wiping userdata.
So, if you wipe userdata, android 11 GSI rom may be flashable.
(Android 11 GSI is freshly made and under developing, so some trouble may be happened like MTK devices.)
NOTE: If you want to root M40, hovatek already succeeded to get root. Refer this
(Do not simply patch boot.img and flash. Device will boot-loop.)
How to root the Teclast M40
The Teclast M40 runs on Android 10 Q and Unisoc T618 Processor. Rooting this model is pretty much like rooting the Teclast P80X except there are some important differences. Things to note when trying
forum.hovatek.com
bercypher said:
According to the source, we have to flash vbmeta. But I flashed vbmeta, vbmeta_system, vbmeta_vendor just in case, as follows.(for unlocked device.)
./fastboot reboot fastboot
./fastboot --disable-verity --disable-verification flash vbmeta vbmeta-sign.img
./fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
./fastboot --disable-verity --disable-verification flash vbmeta_vendor vbmeta_vendor.img
./fastboot erase system
./fastboot delete-logical-partition product
./fastboot --disable-verity --disable-verification flash system (your gsi.img)
./fastboot -w
(When I flashed system, I also disabled verity and verification, but it may be unneccesary)
When I replaced GSI rom, I seemed to forget to wiping userdata.
So, if you wipe userdata, android 11 GSI rom may be flashable.
(Android 11 GSI is freshly made and under developing, so some trouble may be happened like MTK devices.)
NOTE: If you want to root M40, hovatek already succeeded to get root. Refer this
(Do not simply patch boot.img and flash. Device will boot-loop.)
How to root the Teclast M40
The Teclast M40 runs on Android 10 Q and Unisoc T618 Processor. Rooting this model is pretty much like rooting the Teclast P80X except there are some important differences. Things to note when trying
forum.hovatek.com
Click to expand...
Click to collapse
Which gsi image did you use? I tried Havoc (Havoc-OS-v3.8-20200821-Official-GApps-arm64-aonly & Havoc-OS-v3.8-20200821-Official-arm64-aonly), BlissROM and AOSP 11.0 v300.j. No luck, all ended up booting into fastboot mode only. I have flashed back to stock rom now.
jngiag said:
Which gsi image did you use? I tried Havoc (Havoc-OS-v3.8-20200821-Official-GApps-arm64-aonly & Havoc-OS-v3.8-20200821-Official-arm64-aonly), BlissROM and AOSP 11.0 v300.j. No luck, all ended up booting into fastboot mode only. I have flashed back to stock rom now.
Click to expand...
Click to collapse
I used PE plus Arm64 AB.(https://sourceforge.net/projects/an...us-10.0-20201105-GSI-ARM64-AB.img.xz/download)
I also tried Havoc v3.8 and AOSP 11, but it did not worked.
I don't know why they doesn't work
bercypher said:
I used PE plus Arm64 AB.(https://sourceforge.net/projects/an...us-10.0-20201105-GSI-ARM64-AB.img.xz/download)
I also tried Havoc v3.8 and AOSP 11, but it did not worked.
I don't know why they doesn't work
Click to expand...
Click to collapse
It is arm64 ab. My mistake of assuming it as arm64 aonly. I tried a few ab roms and as what you said, only PE plus is working. So far I have not noticed any bugs in PE plus. I like it more compared to the stock rom. Thanks a lot for the guide.
Another gsi rom (ShapeShiftOS-1.2.1_arm64-ab_gapps) flashed successfully. This rom has more features than PE Plus and is equally good.
jngiag said:
Another gsi rom (ShapeShiftOS-1.2.1_arm64-ab_gapps) flashed successfully. This rom has more features than PE Plus and is equally good.
Click to expand...
Click to collapse
Can you by chance post a link to where you downloaded this from?
Also any other options besides stock Rom available now?
Thank you this is a very nice thread. My first tablet and the mic is not working well. So need to flash the Rom to something else. Now to find out what is involved.
Rudy
RudyGireyev said:
Can you by chance post a link to where you downloaded this from?
Also any other options besides stock Rom available now?
Thank you this is a very nice thread. My first tablet and the mic is not working well. So need to flash the Rom to something else. Now to find out what is involved.
Rudy
Click to expand...
Click to collapse
You can download ShapeShift OS from here (https://sourceforge.net/projects/androidgsi/files/ShapeShiftOS/10/).
I have tried most of the Android 10 and 11 (arm64-ab with gapp version) gsi roms provided here ( https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list) and so far, only managed to get 2 gsi roms (PixelExperiencePlus and ShapeShiftOS by Diust) working.
I have also managed to install magisk manager successfully in stock rom but not in gsi roms. I am using ShapeShiftOS. Hope you can find a new one and share with us here. Good luck!
Sorry for such a noob question. But what is the difference between a and ab in the names of the releases?
Also have you guys tried using headphones with your M40 while talking to someone on it? Or even recording yourselves? How is the sound?
I don't use headphones, only bluetooth earbuds. By the way, bluetooth doesn't seem to work in gsi rom but stock rom is ok.
jngiag said:
I don't use headphones, only bluetooth earbuds.
Click to expand...
Click to collapse
Thank you for the report. I assume the volume level is good then in the stock ROM? People you speak to can hear you well?
jngiag said:
By the way, bluetooth doesn't seem to work in gsi rom but stock rom is ok.
Click to expand...
Click to collapse
WOW! So this is not se easy. Is it because the tablet is still new and the processor is so new? Will things settle down and stabilize?
RudyGireyev said:
Thank you for the report. I assume the volume level is good then in the stock ROM? People you speak to can hear you well?
WOW! So this is not se easy. Is it because the tablet is still new and the processor is so new? Will things settle down and stabilize?
Click to expand...
Click to collapse
The sound of stock rom in both speaker mode and bluetooth earbud is loud enough and okay. Sound of gsi rom in speaker mode is slightly better. Gsi roms are generic and usually need some fine tunning for specific devices.
RudyGireyev said:
Sorry for such a noob question. But what is the difference between a and ab in the names of the releases?
Also have you guys tried using headphones with your M40 while talking to someone on it? Or even recording yourselves? How is the sound?
Click to expand...
Click to collapse
Hello friend, I am newbie in Android. All I know about GSI is A only means your devices can boot only 1 /system partition. A/B means your devices can boot 2 /system partition: /system_a and /system_b.
I was gonna buy this tablet but I saw this is Unisoc which I am afraid of the support tools. So I bought M30 Pro instead. I will consider to buy M40 later if the price drops again.
Edit1: A/B is like seamless update over OTA. When you download firmware Updates from OTA your devices can flash during running the system to the other /system partition. Once your devices reboot the newly flashed /system partition will be active and the other recent /system will be inactive.
Edit2: You can download Project Treble Check app in Play Store to see which types of your system partition would be.
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
T4gB0t said:
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
Click to expand...
Click to collapse
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Hw4ng3r said:
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Click to expand...
Click to collapse
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
T4gB0t said:
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
Click to expand...
Click to collapse
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Hw4ng3r said:
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Click to expand...
Click to collapse
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
T4gB0t said:
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
Click to expand...
Click to collapse
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Hw4ng3r said:
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Click to expand...
Click to collapse
I downloaded the software from the official website and used payload dumper to extract the boot image. To be sure that I understood everything... you suggested to use "fastboot boot patched.img" instead of "fastboot flash boot patched.img", and once the phone restarted to go to magisk manager and click direct install.
Do I need Magisk Manager canary or the normal version for this to work and do I have to mantain the canary version or can I install the normal version once it is rooted?
Either 22.1 or Canary works for A11
Hw4ng3r said:
Either 22.1 or Canary works for A11
Click to expand...
Click to collapse
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
T4gB0t said:
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
Click to expand...
Click to collapse
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
T4gB0t said:
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
Click to expand...
Click to collapse
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Hw4ng3r said:
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Click to expand...
Click to collapse
So not Magisk v.23 but Magisk canary?
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Hw4ng3r said:
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Click to expand...
Click to collapse
Okay thanks, I'll try with v.23 first and If that does not work than I'll try with the canary one. Thank you very much!!!
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Wacko1805 said:
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Okay thank you, I'll try if the other method does not work
T4gB0t said:
Okay thank you, I'll try if the other method does not work
Click to expand...
Click to collapse
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Hw4ng3r said:
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Click to expand...
Click to collapse
I'm sorry to bother you again, but I tried with "fastboot boot patched.img" and it still did not work. It got stuck while booting again with "unable to parse kernel log" as error message. Do you have any other suggestions?
P.S. I got a full backup with "adb backup -apk -all -shared -f /path/to/location" today and thought about just doing a factory reset, trying to root the phone, restore the backup. Do you think that might actually work? Thank you for your help!
How exactly did you patched your boot.img?
FSadino said:
How exactly did you patched your boot.img?
Click to expand...
Click to collapse
I tried doing it with magisk (both v.23 and canary)
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?
Hello XDA developers, I'm in urgent and I have a really big problem. It sounds funny but, I deleted my realme ui recovery ,_,
I was trying to install PPUI 4.1 on my Realme 7 but I saw a tutorial that you have to erase the recovery to install TWRP. Please, I need a solution of how can I get it back. I also tried flashing a lot of recoveries and their vbmeta but nothing works. Sadly.
Edit: I'm on RMX2151_11_C.17 | Realme UI 2.0 Latest version
Here is the stock recovery
Chenes said:
Here is the stock recovery
Click to expand...
Click to collapse
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Sorry for a lot of questions, haha
iOussamato_ said:
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Click to expand...
Click to collapse
From what I read before, fastboot boot will only boot to that recovery file temporarily but I haven't tried it myself. It should be
Code:
fastboot flash recovery recovery.img
I'm not 100% sure it will work without problems, but if it did, your data will not be wiped.
I suggest you wait for someone else to answer coz I'm not expert. I only learned from guides in the telegram group.
Chenes said:
From what I read before, fastboot boot will only boot to that recovery file temporarily but I haven't tried it myself. It should be
Code:
fastboot flash recovery recovery.img
I'm not 100% sure it will work without problems, but if it did, you're data will not be wiped.
I suggest you wait for someone else to answer coz I'm not expert. I only learned from guides in the telegram group.
Click to expand...
Click to collapse
Can I have that Telegram group invite?
iOussamato_ said:
Can I have that Telegram group invite?
Click to expand...
Click to collapse
Realme 7 • Narzo 20 Pro • Global
Welcome To Realme 7 | Narzo 20 Pro Group • RM6785_updates(official-A12/A13)- @RM6785 / https://t.me/realme7updater • RM6785_Gaming- @RM6785Gaming • Realme 7 Cloud: @realme_7_cloud
t.me
iOussamato_ said:
You sure? I'm on RMUI2.0 and how do I flash it? Can I type 'fastboot boot recovery.img'? Are my data will be wiped?
Sorry for a lot of questions, haha
Click to expand...
Click to collapse
You can try, first, if fastboot works in your device, type adb reboot fastboot, once the script ends, quickly disconnect device from your PC and again reconnect it, you will be redirected to fastboot, if the bootloader is unlocked, you could flash it using fastboot commands.
If you can´t get it to work then you can flash it using SPFT https://spflashtool.com/, put the recovery, in the same folder, with the attached files. All the sources to can use the tool, here https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
SubwayChamp said:
You can try, first, if fastboot works in your device, type adb reboot fastboot, once the script ends, quickly disconnect device from your PC and again reconnect it, you will be redirected to fastboot, if the bootloader is unlocked, you could flash it using fastboot commands.
If you can´t get it to work then you can flash it using SPFT https://spflashtool.com/, put the recovery, in the same folder, with the attached files. All the sources to can use the tool, here https://www.getdroidtips.com/bypass-mediateks-sp-flash-tool-authentication-protection/
Click to expand...
Click to collapse
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
iOussamato_ said:
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
Click to expand...
Click to collapse
Most of the custom roms I've seen requires formatting data. Just to be sure have you unlocked bootloader already? That requires wiping data iirc.
If not then nothing will really work with what you're doing.
iOussamato_ said:
I have never used SPFlashTool before honestly, I'm just scared to break my phone or lost my data in it. I just wish to install a custom ROM
Click to expand...
Click to collapse
What you are saying now is totally different from what you firstly posted.
Installing a custom ROM doesn't require a stock recovery (just in case you are confusing), and obviously, to can switch from a stock ROM to a custom ROM, that has a total different basement, it's mandatory to format data, anyway, you should back up your data previously to do so.
SubwayChamp said:
What you are saying now is totally different from what you firstly posted.
Installing a custom ROM doesn't require a stock recovery (just in case you are confusing), and obviously, to can switch from a stock ROM to a custom ROM, that has a total different basement, it's mandatory to format data, anyway, you should back up your data previously to do so.
Click to expand...
Click to collapse
I meant, I wish to install a custom ROM but I cannot install a working recovery and wanted the stock one. Sorry
Chenes said:
Most of the custom roms I've seen requires formatting data. Just to be sure have you unlocked bootloader already? That requires wiping data iirc.
If not then nothing will really work with what you're doing.
Click to expand...
Click to collapse
Yes my bootloader is already unlocked
iOussamato_ said:
Yes my bootloader is already unlocked
Click to expand...
Click to collapse
Then you can root your phone 1st then backup your files to a computer and use migrate backup to backup app data. Note that migrate backup is limited to 4gb. Then do the fastboot flash i mentioned before
iOussamato_ said:
I meant, I wish to install a custom ROM but I cannot install a working recovery and wanted the stock one. Sorry
Click to expand...
Click to collapse
Why you are saying that you cannot install a working recovery, I don't know of any attempt you did to achieve it.
A stock recovery is not needed to install a custom ROM, and even you can't install a custom ROM using a stock recovery.
If you want to join, flashing your device and stuff like this, better learn how to use SPFT, also you have this tool https://github.com/bkerler/mtkclient, this can save your device, if something in the process goes wrong.
SubwayChamp said:
Why you are saying that you cannot install a working recovery, I don't know of any attempt you did to achieve it.
A stock recovery is not needed to install a custom ROM, and even you can't install a custom ROM using a stock recovery.
If you want to join, flashing your device and stuff like this, better learn how to use SPFT, also you have this tool https://github.com/bkerler/mtkclient, this can save your device, if something in the process goes wrong.
Click to expand...
Click to collapse
I wanted to flash stock rom to downgrade into Realme UI 1.0 then flash the custom recovery so I can flash a custom rom
iOussamato_ said:
I wanted to flash stock rom to downgrade into Realme UI 1.0 then flash the custom recovery so I can flash a custom rom
Click to expand...
Click to collapse
OK, then what you are trying to install is an "old" Android 10 based ROM, if this is the case, then just download a stock Android 10 ROM, flash it through SPFT, then use SPFT to flash the custom recovery, transfer the custom ROM to your external SD Card (preferably) or sideload it, through recovery, and flash it. In the process you need to unlock bootloader, and immediately to flash the custom recovery, boot to it, using hardware buttons.
SubwayChamp said:
OK, then what you are trying to install is an "old" Android 10 based ROM, if this is the case, then just download a stock Android 10 ROM, flash it through SPFT, then use SPFT to flash the custom recovery, transfer the custom ROM to your external SD Card (preferably) or sideload it, through recovery, and flash it. In the process you need to unlock bootloader, and immediately to flash the custom recovery, boot to it, using hardware buttons.
Click to expand...
Click to collapse
Do you know a tutorial of how to use SPFlashTool?
iOussamato_ said:
Do you know a tutorial of how to use SPFlashTool?
Click to expand...
Click to collapse
How to use SP Flash Tool
This is a step-by-step tutorial on how to flash stock rom to a Mediatek device using Smart Phone Flash tool. SP Flash tool is one application you could find very useful in fixing extreme cases of a br
www.hovatek.com
Alright so, it might sound funny but I think I fixed it. I was playing with my downloaded recoveries until I downloaded the stock recovery, it is compatible but when I do fastboot reboot recovery I get stuck at Orange State for like 30min and it boots me into the recovery so does anyone know a solution for this? And thank you for everything and sorry for wasting y'all's time. Sincereley.
iOussamato_ said:
Alright so, it might sound funny but I think I fixed it. I was playing with my downloaded recoveries until I downloaded the stock recovery, it is compatible but when I do fastboot reboot recovery I get stuck at Orange State for like 30min and it boots me into the recovery so does anyone know a solution for this? And thank you for everything and sorry for wasting y'all's time. Sincereley.
Click to expand...
Click to collapse
You have to boot to recovery using hardware buttons (PWR + vol. down), in regard to orange state, this is absolutely normal when bootloader was unlocked, it's not an issue but a cosmetic thing.