Related
Since our device still no TWRP Support, i will give you a simple guide how to root redmi 9 using magisk. Original guide is here
Big Thanks to @N3OMOD :good::good::good:
EDIT: NO FORMAT DATA REQUIRED BUT BACKUP ALWAYS RECOMMENDED
REQUIREMENT :
- Already UNLOCK BOOTLOADER
- Magisk Manager
- Internet Connection
- Your PC already installed adb&fastboot driver
- Boot.img from your current MIUI version (EXTRACTED FROM MIUI FULL RECOVERY ROM)
- vbmeta.img
Known Limitation:
- Can't modify system partition
- Maybe cause selinux problem
How to:
STEP 1
- Backup Always Recommended
- Install Magisk Manager
- Turn ON Internet Connection and Open Magisk Manager
- Press install button > select method patch a file > choose boot.img from your current miui version > WAIT UNTIL DONE
- Open download folder and copy magisk_patched.img to your PC (adb tools usually in C:\ADB and Fastboot)
- Download vbmeta.img in attachment and copy to C:\ADB and Fastboot
STEP 2
- Go to fastboot (press and hold >>> power+volume down)
- open command prompt in C:\ADB and Fastboot then type this code one by one carefully
Code:
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_redmi9.img (WARNING: if not successful cause bootloop)
fastboot flash boot magisk_patched.img
fastboot reboot
- Open Magisk Manager (Internet Connection required for download some magisk files and will automatically reboot in 5 minutes)
- DONE....ENJOY ROOT ACCESS :good::good::good:
NOTES
Tested on MIUI 11.0.3.0-11.0.6.0 GLOBAL ID, 11.0.7.0-11.0.8.0 GLOBAL
Use your own magisk patched boot from your current miui version, click here for miui full recovery rom
Q&A
Q: How to completely uninstall magisk?
A: Flash miui fastboot rom via Mi Flash or Flash full recovery rom
Q: Bootloop?
A: Disable vbmeta not successful, use adb fastboot in my comment or flash stock boot.img
Credit :
Alloh SWT
@topjohnwu for magisk
@N3OMOD for root guide xiaomi mediatek
Me for tester
i can't boot vbmeta.img
Fastboot : unrecognised option ' --disable-verity'
AstroKkngTool said:
i can't boot vbmeta.img
Fastboot : unrecognised option ' --disable-verity'
Click to expand...
Click to collapse
download my attachment adb_fastboot.zip
extract & copy folder to C:/ then try again
How did you unlock the bootloader on global rom?
Or you have non NFC version of Redmi 9?
afah_me said:
Since our device still no TWRP Support, i will give you a simple guide how to root redmi 9 using magisk. Original guide is here
Big Thanks to @N3OMOD :good::good::good:
REQUIREMENT :
- Already UNLOCK BOOTLOADER
- Magisk Manager
- Internet Connection
- Your PC already installed adb&fastboot driver
- Boot.img from your current MIUI version (EXTRACTED FROM MIUI FULL RECOVERY ROM)
- vbmeta.img
Known Limitation:
- Can't modify system partition
- Maybe cause selinux problem
- Must have stock boot.img
How to:
STEP 1
- BACKUP ALL YOUR DATA BECAUSE IT WILL FORMAT DEVICES
- Install Magisk Manager
- Turn ON Internet Connection and Open Magisk Manager
- Press install button > select method patch a file > choose boot.img from your current miui version > WAIT UNTIL DONE
- Open download folder and copy magisk_patched.img to your PC (adb tools usually in C:\ADB and Fastboot)
- Download vbmeta.img in attachment and copy to C:\ADB and Fastboot
STEP 2
- Go to fastboot (press and hold >>> power+volume down)
- open command prompt in C:\ADB and Fastboot then type this code one by one carefully
Code:
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_redmi9.img
fastboot erase userdata
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
- Setup your phone again
- Reinstall Magisk Manager and open it (Internet Connection required for download some magisk files and will automatically reboot)
- DONE....ENJOY ROOT ACCESS :good::good::good:
NOTES:
Tested on MIUI 11.0.3.0 GLOBAL
Use your own magisk patched boot from your current miui version, click here for miui full recovery rom
Credit :
Alloh SWT
@topjohnwu for magisk
@N3OMOD for root guide xiaomi mediatek
Me for tester
Click to expand...
Click to collapse
It WORKS. I'm on MIUI 11.0.4.0 GLOBAL. Huge Thanks :fingers-crossed:
Thanks it works my phone .
I am on miui 11.0.2 v. (Redmi 9 prime)
There is no update sill now,
There no Firmware 11.0.2 what I am using
What can I do further????
Can I flash the latest Global Rom on my phone using Fastboot mode????
Why Аndroid is 10 oreo? (pictured)
afah_me said:
Since our device still no TWRP Support, i will give you a simple guide how to root redmi 9 using magisk. Original guide is here
Big Thanks to @N3OMOD :good::good::good:
REQUIREMENT :
- Already UNLOCK BOOTLOADER
- Magisk Manager
- Internet Connection
- Your PC already installed adb&fastboot driver
- Boot.img from your current MIUI version (EXTRACTED FROM MIUI FULL RECOVERY ROM)
- vbmeta.img
Known Limitation:
- Can't modify system partition
- Maybe cause selinux problem
- Must have stock boot.img
How to:
STEP 1
- BACKUP ALL YOUR DATA BECAUSE IT WILL FORMAT DEVICES
- Install Magisk Manager
- Turn ON Internet Connection and Open Magisk Manager
- Press install button > select method patch a file > choose boot.img from your current miui version > WAIT UNTIL DONE
- Open download folder and copy magisk_patched.img to your PC (adb tools usually in C:\ADB and Fastboot)
- Download vbmeta.img in attachment and copy to C:\ADB and Fastboot
STEP 2
- Go to fastboot (press and hold >>> power+volume down)
- open command prompt in C:\ADB and Fastboot then type this code one by one carefully
Code:
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta vbmeta_redmi9.img
fastboot erase userdata
fastboot erase cache
fastboot flash boot magisk_patched.img
fastboot reboot
- Setup your phone again
- Reinstall Magisk Manager and open it (Internet Connection required for download some magisk files and will automatically reboot)
- DONE....ENJOY ROOT ACCESS :good::good::good:
NOTES:
Tested on MIUI 11.0.3.0 GLOBAL
Use your own magisk patched boot from your current miui version, click here for miui full recovery rom
Credit :
Alloh SWT
@topjohnwu for magisk
@N3OMOD for root guide xiaomi mediatek
Me for tester
Click to expand...
Click to collapse
Why Аndroid is 10 oreo? (pictured)
Mantipallykrishna said:
I am on miui 11.0.2 v. (Redmi 9 prime)
There is no update sill now,
There no Firmware 11.0.2 what I am using
What can I do further????
Can I flash the latest Global Rom on my phone using Fastboot mode????
Click to expand...
Click to collapse
Are you from India? I wanted to ask, is a model with NFC officially sold in your country?
iYowo said:
Why Аndroid is 10 oreo? (pictured)
Click to expand...
Click to collapse
Good catch, I missed this information when I had a look!
It seems to be a issue with the app he's using!
DevCheck by Flar2 (who does the ElementalX kernel for years on many different devices) reports the android version correctly - and I personally trust rather Flar2's App then anything else!
Should be just a bug in the App that OP uses...
Edit: also selinux appears to be disabled in OPs screenshot, I wonder if he did this on purpose or what the deal is (another App bug?) because usually Magisk patches selinux but doesn't disable it, at least from my experience...
Sent from my galahad using XDA Labs
afah_me said:
Since our device still no TWRP Support, i will give you a simple guide how to root redmi 9 using magisk. Original guide is here
Big Thanks to @N3OMOD :good::good::good:
REQUIREMENT :
- Already UNLOCK BOOTLOADER
- Magisk Manager
- Internet Connection
- Your PC already installed adb&fastboot driver
- Boot.img from your current MIUI version (EXTRACTED FROM MIUI FULL RECOVERY ROM)
- vbmeta.img
Known Limitation:
- Can't modify system partition
- Maybe cause selinux problem
- Must have stock boot.img
How to:
STEP 1
- BACKUP ALL YOUR DATA BECAUSE IT WILL FORMAT DEVICES
- Install Magisk Manager
- Turn ON Internet Connection and Open Magisk Manager
- Press install button > select method patch a file > choose boot.img from your current miui version > WAIT UNTIL DONE
- Open download folder and copy magisk_patched.img to your PC (adb tools usually in C:\ADB and Fastboot)
- Download vbmeta.img in attachment and copy to C:\ADB and Fastboot
STEP 2
- Go to fastboot (press and hold >>> power+volume down)
- open command prompt in C:\ADB and Fastboot then type this code one by one carefully
- Setup your phone again
- Reinstall Magisk Manager and open it (Internet Connection required for download some magisk files and will automatically reboot)
- DONE....ENJOY ROOT ACCESS :good::good::good:
NOTES:
Tested on MIUI 11.0.3.0 GLOBAL
Use your own magisk patched boot from your current miui version, click here for miui full recovery rom
Credit :
Alloh SWT
@topjohnwu for magisk
@N3OMOD for root guide xiaomi mediatek
Me for tester
Click to expand...
Click to collapse
Any bootloop Risk? Please helpme, i am noob
Modelo M2004J19G no NFC
MIUI GLOBAL 11.0.4 STABLE QJCMIXM
Android 10
Sam Nakamura said:
Good catch, I missed this information when I had a look!
It seems to be a issue with the app he's using!
DevCheck by Flar2 (who does the ElementalX kernel for years on many different devices) reports the android version correctly - and I personally trust rather Flar2's App then anything else!
Should be just a bug in the App that OP uses...
Edit: also selinux appears to be disabled in OPs screenshot, I wonder if he did this on purpose or what the deal is (another App bug?) because usually Magisk patches selinux but doesn't disable it, at least from my experience...
Click to expand...
Click to collapse
idk sir, i just download root check app & open it after root successfully ??
KevinTM93 said:
Any bootloop Risk? Please helpme, i am noob
Modelo M2004J19G no NFC
MIUI GLOBAL 11.0.4 STABLE QJCMIXM
Android 10
Click to expand...
Click to collapse
Yes, definitely bootloop risk!
Make sure you understand the instructions in this post and to have the stock kernel stored close to you, in theory you should be easy able to restore the device from bootlooping by flashing the unmodified stock kernel...
And you'll need to unlock the bootloader which will factory reset the device, so before playing around you'll probably want to backup your important files and do the unlocking process, which takes a while on xiaomi phones
Sent from my galahad using XDA Labs
Deleted...already explained
Sam Nakamura said:
Yes, definitely bootloop risk!
Make sure you understand the instructions in this post and to have the stock kernel stored close to you, in theory you should be easy able to restore the device from bootlooping by flashing the unmodified stock kernel...
And you'll need to unlock the bootloader which will factory reset the device, so before playing around you'll probably want to backup your important files and do the unlocking process, which takes a while on xiaomi phones
Click to expand...
Click to collapse
Thank you very much, I understand that there is always a risk of bootloop, but I wanted to know if with those specifications I could perform this method ... another question, where can I download the specific stock rom for my device? I appreciate your help, un MI Page i found MIUI global 11.0.5.0 QJCMIXM, and my device is MIUI global 11.0.4.0 QJCMIXM...
KevinTM93 said:
Thank you very much, I understand that there is always a risk of bootloop, but I wanted to know if with those specifications I could perform this method ... another question, where can I download the specific stock rom for my device? I appreciate your help, un MI Page i found MIUI global 11.0.5.0 QJCMIXM, and my device is MIUI global 11.0.4.0 QJCMIXM...
Click to expand...
Click to collapse
you can find the lancelot miui full recovery rom in here :
https://xiaomifirmwareupdater.com/miui/lancelot/
11.0.5.0 > global stable beta
11.0.4.0 > global stable
if you want 11.0.5.0 so update your rom first,,, if not, you can download miui 11.0.4.0 rom there and ready to patch boot.img...
I can't boot vbmeta.img
Fastboot : unrecognised option ' --disable-verity
Zeppelin_Elevation said:
Are you from India? I wanted to ask, is a model with NFC officially sold in your country?
Click to expand...
Click to collapse
There is no NFC in Redmi 9 Prime Lancelot (INDIA)
ممكن اتواصل معاك فديو شرح
Hamoo kamshto said:
ممكن اتواصل معاك فديو شر [\QUOTE]
PLEASE use english as required by the forum rules, so everyone can understand and contribute, also you'll get help much faster!
Sent from my Google Pixel 3 XL
Click to expand...
Click to collapse
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.
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?
The process of flashing alone is conventional, shouldn't even need a thread to detail, but still leaving a thread here for search indexing.
With an unlocked BL, flash an ARM64 AB GSI within fastbootd, reboot to recovery, format userdata, reboot, profit. vbmeta isn't even needed in my case.
EDIT: One thing that's unconventional and I forgot to mention is, for many GSIs, you gotta delete product_a to make room prior to flashing:
Code:
fastboot delete-logical-partition product_a
EDIT2: Magisk doesn't like to see product_a go. Instead, just flash a blank one (from #15) to it:
Code:
fastboot flash product product_gsi.img
Thanks to @Whoareyou for the original finding and @darkghost568 for additional ideas.
Are we getting closer?
Winnower Amber said:
Are we getting closer?
Click to expand...
Click to collapse
To proper custom ROMs? Dunno, I don't do bringups. I'll at least make/refine/submit the device overlay so GSIs would look proper.
Note that Magisk seems incompatible and prevents booting, at least when paired with my GSI - need to restore to stock boot image. Mine comes with PHH-SU so I'm not keen on getting Magisk working anyway.
OK I'll ask since I have no clue. What's a GSI?
alarmdude9 said:
OK I'll ask since I have no clue. What's a GSI?
Click to expand...
Click to collapse
Home
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
AndyYan said:
Not sure why the GSI front is so quiet even after TMO variant got its unbrick tools...
Click to expand...
Click to collapse
I'm personally waiting until TWRP is more stable for this device before jumping into GSI.
Android 12 boots unsurprisingly as well, not as usable as 11 ofc.
A Generic System Image, is a universal version of android, which is available since project Treble separated the O/S into a "HAL" (Hardware Abstraction Layer) driver layer interface and the core operating system.
boot contains the kernel.
vendor, vendor_dlkm, odm, odm_dlkm are the drivers.
system, system_ext are the O/S core.
product is device specific O/S customizations.
Overview | Android Open Source Project
source.android.com
Project Treble is a good thing, making strides for Android to become a standardized operating system.
GSI install Guide:
Using information from:
Generic system images | Android Open Source Project
source.android.com
We find that we are supposed to flash vbmeta.img with "--disable-verification" because GSIs don't "include a verify boot solution". However, this step is not required on our particular device, due to OnePlus specific changes of verification being automatically disabled upon bootloader unlock.
Prerequisites: unlocked bootloader, up to date fastboot installed on a computer
1. Boot the phone into fastbootd mode by:
booting into recovery mode, by holding power and volume down during boot, then
rebooting into fastboot (only) mode, using touch menus: advanced, reboot into fastboot, then
connecting usb-c to a computer and using the poorly named command:
fastboot reboot fastboot.
Now we can use fastbootd commands.
2. We must erase the system partition:
fastboot erase system
3. next we need to obtain a GSI. I used phhusson's GSI build.
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Choose arm64-ab for our phone's architechture
floss for open source apps but no GAPPS or vanilla for no GAPPS,
don't choose vndklite (Vendor Native Development Kit Lite) as it is a compatibility version for older versions of android's "HAL" layers.
"system-roar-arm64-ab-floss.img.xz"
decompress it to .img (and rename to GSI.img for brevity)
4. If we attempt to flash our GSI into the system partition:
fastboot flash system GSI.img
It will inevitably fail due to "not enough space to resize partiion"
The tool isn't smart enough to handle this task of resizing a "full" dynamic partition.
So we have to delete virtual partitions out of super to make room.
5. We must remove any present -COW partitions, which are Copy On Write partitions, which seem to be made by an A-Only virtual dyamic upgrade system. Their purpose is to host temporary changes to a partition, so the original partition is preserved for an emergency rollback, using associated interfaces to the original partition and the COW partition for access.
check your "fastboot getvar all" for any COW partitions, and delete them.
fastboot delete-logical-partition system_b-cow
6. In the official documentation, they admit that we have to delete the product partition(s) manually to make room.
fastboot delete-logical-partition product_a
fastboot delete-logical-partition product_b
7. With that done, we can reattempt to flash the GSI.
fastboot flash system GSI.img
8. The official instructions then require a fastboot -w in order to clear user data and "system partitions" data, but this is optional.
Are (A11 based) GSI's daily-drivable on the N200?
Also, do they allow for safetynet for banking apps, etc?
oCAPTCHA said:
Unofficial lineageOS 18.x by AndyYan is a Phhusson GSI derivative that claimed partial Magisk compatibility, but it also would not boot when Magisk patched. microG signature spoofing was not supported.
Click to expand...
Click to collapse
That Magisk compatibility does work on most other devices, even including an OPPO device which N200 is a rebadge of. Not sure why it is. Install PHH's Superuser and you get root for apps at least.
MicroG support is limited to priv-app for safety, as shown here.
BTW, long writeup, might wanna cut it down and/or add some emphasis?
lzgmc said:
Are (A11 based) GSI's daily-drivable on the N200?
Click to expand...
Click to collapse
VoLTE is one major hardware feature I can't verify; basic functionalities should be good. Heck, I daily-drive GSI on a device that has way more bugs than this.
mthous01 said:
Also, do they allow for safetynet for banking apps, etc?
Click to expand...
Click to collapse
PHH's "securize" option might allow you to do so for now (and unroot). I don't use GAPPS at all.
Rooting GSI Android 11
@AndyYan
AndyYan said:
That Magisk compatibility does work on most other devices, even including an OPPO device which N200 is a rebadge of. Not sure why it is. Install PHH's Superuser and you get root for apps at least.
MicroG support is limited to priv-app for safety, as shown here.
BTW, long writeup, might wanna cut it down and/or add some emphasis?
VoLTE is one major hardware feature I can't verify; basic functionalities should be good. Heck, I daily-drive GSI on a device that has way more bugs than this.
PHH's "securize" option might allow you to do so for now (and unroot). I don't use GAPPS at all.
Click to expand...
Click to collapse
Rooting GSI Android 11
Have you tried this yet, to get Magisk to work? I'm still on the bubble on wiping my phone and trying this, as it's my only daily driver right now.
mthous01 said:
Have you tried this yet, to get Magisk to work?
Click to expand...
Click to collapse
The /sbin hack is already integrated, but that doesn't seem enough here.
To root y'all need to do:
fastboot create-partition-primary 512 product
Then flash the attached product.
Then flash your rooted img, it'll boot successfully.
This GSI also works beautifuly, even has 90hz, if only there was an overlay for fingerprint scanning.
http://[STRIKE]https://jmirror.ml/0:/Jarvis-Mirror/Pixel5-Beta5-CB-GSI-Tutorials.7z[/STRIKE]
https://sourceforge.net/projects/gsitutorials-sgsi/files/SGSI/A12Beta/Pixel5-SP1A-A12-SGSI-GSI-Tutorials.7z/download
Whoareyou said:
To root y'all need to do:
fastboot create-partition-primary 512 product
Then flash the attached product.
Click to expand...
Click to collapse
OPlus devices really like to throw files (overlays, fstab, etc.) everywhere... TIL, thanks.
I tried out WhoAreYou's product image using
fastboot create-logical-partition product 512
(His syntax gave an error.)
While It did allow me to boot with a Magisk 23 patched boot.img along with Phhusson's vanilla GSI, Magisk did not work. The Magisk 23 app gave a strange error "Unsupported Magisk Version, This version of the app does not support Magisk version lower than v20.4". I downgraded to Magisk Manager 7.3.2 and the system hung whenever Magisk ran instead. Perhaps it is a conflict with the SU system in the GSI. I tried the "securize" option in the Phh treble menu, which caused a reboot, but did not remove root / su . I do not know how to remove the SU modifications present in the GSI, if that is required.
I attempted to use his product image along with his linked pixel 5 beta Android 12 GSI, but the system would not boot with a Magisk 23 patched boot.img.
I attempted to use his product image along with AndyYan's Unofficial Lineage 18.1, but the system would not boot with a Magisk 23 patched boot.img.
oCAPTCHA said:
I tried out WhoAreYou's product image using
fastboot create-logical-partition product 512
(His syntax gave an error.)
While It did allow me to boot with a Magisk 23 patched boot.img along with Phhusson's vanilla GSI, Magisk did not work. The Magisk 23 app gave a strange error "Unsupported Magisk Version, This version of the app does not support Magisk version lower than v20.4". I downgraded to Magisk Manager 7.3.2 and the system hung whenever Magisk ran instead. Perhaps it is a conflict with the SU system in the GSI. I tried the "securize" option in the Phh treble menu, which caused a reboot, but did not remove root / su . I do not know how to remove the SU modifications present in the GSI, if that is required.
I attempted to use his product image along with his linked pixel 5 beta Android 12 GSI, but the system would not boot with a Magisk 23 patched boot.img.
I attempted to use his product image along with AndyYan's Unofficial Lineage 18.1, but the system would not boot with a Magisk 23 patched boot.img.
Click to expand...
Click to collapse
oCAPTCHA said:
Could you flash a stock kernel on top of a GSI, then reroot with Magisk?
Click to expand...
Click to collapse
Try this updated GSI from the stable release, I just flashed it and it's definitely working:
https://sourceforge.net/projects/gsitutorials-sgsi/files/SGSI/A12Beta/Pixel5-SP1A-A12-SGSI-GSI-Tutorials.7z/download
Am using the same product I linked and magisk canary patched stock boot.img, Literally works perfectly aside from the fingerprint scanner.
oCAPTCHA said:
I tried out WhoAreYou's product image using
fastboot create-logical-partition product 512
(His syntax gave an error.)
While It did allow me to boot with a Magisk 23 patched boot.img along with Phhusson's vanilla GSI, Magisk did not work. The Magisk 23 app gave a strange error "Unsupported Magisk Version, This version of the app does not support Magisk version lower than v20.4". I downgraded to Magisk Manager 7.3.2 and the system hung whenever Magisk ran instead. Perhaps it is a conflict with the SU system in the GSI. I tried the "securize" option in the Phh treble menu, which caused a reboot, but did not remove root / su . I do not know how to remove the SU modifications present in the GSI, if that is required.
I attempted to use his product image along with his linked pixel 5 beta Android 12 GSI, but the system would not boot with a Magisk 23 patched boot.img.
I attempted to use his product image along with AndyYan's Unofficial Lineage 18.1, but the system would not boot with a Magisk 23 patched boot.img.
Click to expand...
Click to collapse
^
Hi everyone, sorry for my bad english but i sure we can help me to find a PIXEL EXPERIENCE fluid rom for my Xiaomi Mi 11 Lite 5G (8+128).
I searched the entire internet to find the rom but none of that are good for myself.
FCsperimentx said:
Hi everyone, sorry for my bad english but i sure we can help me to find a PIXEL EXPERIENCE fluid rom for my Xiaomi Mi 11 Lite 5G (8+128).
I searched the entire internet to find the rom but none of that are good for myself.
Click to expand...
Click to collapse
you have to take GSI rom here..
You can check my personal PE 12.0 build, been using it for 2 weeks and it works alright not 100% perfect.
Releases · aurotones/renoir
Contribute to aurotones/renoir development by creating an account on GitHub.
github.com
Ho un grosso problema sul mio dispositivo: quando provo a installare una rom personalizzata lo smartphone si blocca sul bootloop e I install again the stock miui con MIFlashTool.
I tried everything but the smartphone still have this problem.
FCsperimentx said:
Ho un grosso problema sul mio dispositivo: quando provo a installare una rom personalizzata lo smartphone si blocca sul bootloop e I install again the stock miui con MIFlashTool.
I tried everything but the smartphone still have this problem.
Click to expand...
Click to collapse
i updated install instructions. Also don't forget you must be on MIUI 12.5.7 firmware base.
I downloaded MIUI 12.5.7 but everything is the same.
Now when i write .\adb reboot fastboot the phone reboot itself on FASTBOOTD.
I tried everything but nothing just change because the xiaomi’s stuck on bootloop.
FCsperimentx said:
I downloaded MIUI 12.5.7 but everything is the same.
Now when i write .\adb reboot fastboot the phone reboot itself on FASTBOOTD.
I tried everything but nothing just change because the xiaomi’s stuck on bootloop.
Click to expand...
Click to collapse
You downloaded MIUI 12.5.7 is a good start but you could have alternatively download and flash only the firmware base which is only about 100MB. Also I see the instructions were not 100% clear, hope this will be clear enough for you. Also before you do, backup your files!
1. You supposed to go into bootloader, not fastboot.
Code:
adb reboot bootloader
2. Flash boot.img and vendor_boot.img files through fastboot command on your PC.
Code:
fastboot flash boot_ab ./boot.img
fastboot flash vendor_boot_ab ./vendor_boot.img
3. Now you need to go into recovery mode. It should say pixel experience recovery on top of the screen.
Code:
fastboot reboot recovery
4. Select Apply update -> Apply from ADB.
5. Now sideload the zip file through adb command on your PC
Code:
adb sideload ./PixelExperience_renoir-***.zip
6. You may need to format your data so it will boot properly.
Above commands are examples but might be different on your type of operating system you're using, so take them as example, not the exact command that will guaranteed to work.
If you're still having problem then, there's underlying problem that i'm not aware of and hope someone else will help you to flash it.
Hi, I don't get it I tried everything can't make it work. I finally flashed vendor_boot, and booted on TWRP 3.6.1_11-0 in order to manage to side load on Renoir, and I get this error all time (with the 12 and 12 plus official release of pixel experience) as on the picture.
Could you help me, it's been 6 month I don't manage to installé any pixel experience on this phone. First time I' m stuck with a smartphone ever ... Official/gsi nothing works, I only manage to flash the MIUI ROM and lineage os....
I'm desperate .
Eightkiller said:
Hi, I don't get it I tried everything can't make it work. I finally flashed vendor_boot, and booted on TWRP 3.6.1_11-0 in order to manage to side load on Renoir, and I get this error all time (with the 12 and 12 plus official release of pixel experience) as on the picture.
Could you help me, it's been 6 month I don't manage to installé any pixel experience on this phone. First time I' m stuck with a smartphone ever ... Official/gsi nothing works, I only manage to flash the MIUI ROM and lineage os....
I'm desperate .
Click to expand...
Click to collapse
TWRP doesn't support Android 12 yet, you need LineageOS or Pixel Experience recovery to sideload.
Edit: Follow instructions here: https://wiki.pixelexperience.org/devices/renoir/install/
aurotones said:
TWRP doesn't support Android 12 yet, you need LineageOS or Pixel Experience recovery to sideload.
Edit: Follow instructions here: https://wiki.pixelexperience.org/devices/renoir/install/
Click to expand...
Click to collapse
Thx for your answer the problem is I can't manage to boot on pixel experience recovery as shown in the tutorial. It says ok when I flash but I can only get to fastboot. And when I just try to fastboot boot 'myrecovery.img', it just rebbotsyto fastboot. That's why I tried to boot on TWRP which works without any trouble :s
Eightkiller said:
Thx for your answer the problem is I can't manage to boot on pixel experience recovery as shown in the tutorial. It says ok when I flash but I can only get to fastboot. And when I just try to fastboot boot 'myrecovery.img', it just rebbotsyto fastboot. That's why I tried to boot on TWRP which works without any trouble :s
Click to expand...
Click to collapse
TWRP will never work but while you're on TWRP your base should be on V12.5.7.0.RKIEUXM, flash that first in TWRP and then maybe try flash boot.img and vendor_boot.img and go to recovery mode. Without it you will never be able to install. Please give me details what your phone is, is it 5G variant with renoir codename?, is it global or china?, did it had MIUI 12.5 or 13?, these informations are necessary.
aurotones said:
TWRP will never work but while you're on TWRP your base should be on V12.5.7.0.RKIEUXM, flash that first in TWRP and then maybe try flash boot.img and vendor_boot.img and go to recovery mode. Without it you will never be able to install. Please give me details what your phone is, is it 5G variant with renoir codename?, is it global or china?, did it had MIUI 12.5 or 13?, these informations are necessary.
Click to expand...
Click to collapse
It had MIUI 12.x and it is a "eu" phone, I tried to flash the V12.5.7.0.RKIEUXM (miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0) from twrp it's not working with the same errors messages. I don't really know what to do, i managed to put back my 12.6 beta stock miui from "xiaomi.eu_multi_MI11Lite5G_21.7.7_v12-11-fastboot" version.
When i'm stuck i'm forced to install this back to not be stuck on fastboot loop. I found a "renoir_eea_global_images_V12.5.7.0.RKIEUXM_20220105.0000.00_11.0_eea" fastboot version but the installation is not working (would you have one working from my config ?).
I also tried to flash the firmware (fw_renoir_miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0 ~104mo) which gave me an "orange" fastboot instead of the fastboot with the funny character. And tried to install the recovery from pixel after but still stuck on fastboot.
Hope it will help you a bit more to help me
Eightkiller said:
It had MIUI 12.x and it is a "eu" phone, I tried to flash the V12.5.7.0.RKIEUXM (miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0) from twrp it's not working with the same errors messages. I don't really know what to do, i managed to put back my 12.6 beta stock miui from "xiaomi.eu_multi_MI11Lite5G_21.7.7_v12-11-fastboot" version.
When i'm stuck i'm forced to install this back to not be stuck on fastboot loop. I found a "renoir_eea_global_images_V12.5.7.0.RKIEUXM_20220105.0000.00_11.0_eea" fastboot version but the installation is not working (would you have one working from my config ?).
I also tried to flash the firmware (fw_renoir_miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0 ~104mo) which gave me an "orange" fastboot instead of the fastboot with the funny character. And tried to install the recovery from pixel after but still stuck on fastboot.
Hope it will help you a bit more to help me
Click to expand...
Click to collapse
i feel like your partition is messed up by TWRP so my advice is clean flash V12.5.7.0 fastboot rom with method of "flash_all.bat" on windows, "flash_all.sh" on linux i forgot the filenames but there's also method with lock in the name which you should avoid and then never touch or install TWRP as it's a bit unstable even with Android 11 roms, now you flash boot.img and vendor_boot.img provided by Pixel Experience through bootloader that only spells fastboot, no extra letter at the end.
This is important, Rebooting into bootloader and fastboot is different, when you do 'adb reboot fastboot' it will show fastbootd with orange text which something you should avoid, instead do 'adb reboot bootloader' or by vol down + power button and flash those 2 files.
If you still having problems try changing your boot slot by
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
And then
Code:
fastboot reboot recovery
If you still having problems, then head over to this telegram group and get help from ROM maintainer: https://t.me/arixelogroup
The Official build Pixel Experience is now available for renoir
It works perfectly on my device
PE for renoir
RGB39 said:
The Official build Pixel Experience is now available for renoir
It works perfectly on my device
PE for renoir
Click to expand...
Click to collapse
Attention that, Don't flash miui13 before flashing pe, or your wlan won't work.
aurotones said:
i feel like your partition is messed up by TWRP so my advice is clean flash V12.5.7.0 fastboot rom with method of "flash_all.bat" on windows, "flash_all.sh" on linux i forgot the filenames but there's also method with lock in the name which you should avoid and then never touch or install TWRP as it's a bit unstable even with Android 11 roms, now you flash boot.img and vendor_boot.img provided by Pixel Experience through bootloader that only spells fastboot, no extra letter at the end.
This is important, Rebooting into bootloader and fastboot is different, when you do 'adb reboot fastboot' it will show fastbootd with orange text which something you should avoid, instead do 'adb reboot bootloader' or by vol down + power button and flash those 2 files.
If you still having problems try changing your boot slot by
Code:
fastboot --set-active=a
or
Code:
fastboot --set-active=b
And then
Code:
fastboot reboot recovery
If you still having problems, then head over to this telegram group and get help from ROM maintainer: https://t.me/arixelogroup
Click to expand...
Click to collapse
Thx, but that's what i'm trying to do since yesterday, but i don't manage to fresh install 12.5.7.0 with the fastboot rom i found (miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0
I always get errors when i run the flash_all.bat, saying that my rom is more recent than the one i'm trying to flash. I tried to delete the "if statement" checking for the versions, but seems to mess up with the "directories name" after.
Would you have some link or place where i can get a working 12.5.7.0 with fastboot install ? I'll try it properly from this one.
Thanks in advance.
Eightkiller said:
Thx, but that's what i'm trying to do since yesterday, but i don't manage to fresh install 12.5.7.0 with the fastboot rom i found (miui_RENOIREEAGlobal_V12.5.7.0.RKIEUXM_325e38b5bf_11.0
I always get errors when i run the flash_all.bat, saying that my rom is more recent than the one i'm trying to flash. I tried to delete the "if statement" checking for the versions, but seems to mess up with the "directories name" after.
Would you have some link or place where i can get a working 12.5.7.0 with fastboot install ? I'll try it properly from this one.
Thanks in advance.
Click to expand...
Click to collapse
Use XiaoMiFlash
Download Official Xiaomi Mi Flash Tool All Versions
xiaomimiflashtool.com
or fastboot v29.0.5
Download Platform Tools for Android SDK Manager
Download Android SDK Platform-tools 29.0.0 , 29.0.0 , 30.0.0 , 30.0.0 , 31.0.0 , 31.0.0 , 31.0.0 , 33.0.0 , 33.0.0 , 33.0.0 , 34.0.0 ,
androidsdkmanager.azurewebsites.net
mitanyan98 said:
Use XiaoMiFlash
Download Official Xiaomi Mi Flash Tool All Versions
xiaomimiflashtool.com
or fastboot v29.0.5
Download Platform Tools for Android SDK Manager
Download Android SDK Platform-tools 29.0.0 , 29.0.0 , 30.0.0 , 30.0.0 , 31.0.0 , 31.0.0 , 31.0.0 , 33.0.0 , 33.0.0 , 33.0.0 , 34.0.0 ,
androidsdkmanager.azurewebsites.net
Click to expand...
Click to collapse
Thx for your answer, as i was saying: same error with mi flash tool (look the screenshot)
And if i comment the "checking parts" inside the .bat files, i get directories error on windows: it does not seem to check properly my direcotries name
for example a line is like this:
fastboot %* flash crclist %~dp0images\crclist.txt || @ECHO "Flash crclist error" && exit /B 1
the %~dp0images seems to be my path, but it's not taken properly into accoutn, seems to have " quote problems with the path
Edit: I had to double quote " the path inside the script as my path was having spaces inside
Thx for you help, I managed to install it, the only problem was to properly install 12.5.7 After succeding that everything worked as it should
RGB39 said:
Attention that, Don't flash miui13 before flashing pe, or your wlan won't work.
Click to expand...
Click to collapse
So that's why... so many hours wasted trying to get Wi-Fi to work. I had the "fantastic idea" of flashing the official global miui (renoir_global_images_V13.0.4.0.SKIMIXM_20220412....) prior to installing DotOS and when wi-fi did not work, flashed Pixel Experience...
And I'm pretty sure flashing miui 12.x will trigger ARB and brick the phone. Right?