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.
Related
Hello!
I was wondering if anyone else saw that M4 Aqua has been officially added to the bootloader unlockable devices and that the Marshmallow Experimental binaries do contain binaries for Kanuti/Tulip which are of the same size as other devices' binaries (which makes me guess that they are way more complete and usable than what we could previously download). I have not yet compiled AOSP to see if my theory is correct but I will do it as soon as I can.
If someone else already tried please share the result
If you want a tester, I could do the job
It is currently compiling, I will update when it is done/fails.
Hoping someone makes a breakthrough with AOSP or CM 13. I feel like this phone has so much unused potential being chained by Sonys system , waiting to be released. Looking forward to hearing what happens with your compile
Hello once again!
The compilation has been finally successful.
If anyone wants to test it, here you have the links and guide that you need. Remember, this is NOT tested and I am in no way responsible if something happens to your phone (not that much can happen, worse case it does not boot and you have to flash using flashtool). This is Sony's Marshmallow Experimental AOSP build for this device by me.
Without further ado, this are the files that you have to download(copy and paste the link, XDA doesn't let me post it without the dashes):
Boot: //https://drive.google.com/open?id=0B0E3yd2mts3wWnpXVUU2Y2ZjWGM//
System: //https://drive.google.com/open?id=0B0E3yd2mts3wVmh4N0h4dkRYcGs//
Userdata: //https://drive.google.com/open?id=0B0E3yd2mts3wY3ZpX3NadmhSM0E//
After downloading them, simply copy them somewhere you can use fastboot and flash them :
fastboot –S 256M flash boot boot.img
fastboot –S 256M flash system system.img
fastboot –S 256M flash userdata userdata.img
I tested it and it resulted in an never-ending bootloop
nrokos said:
I tested it and it resulted in an never-ending bootloop
Click to expand...
Click to collapse
Can you get to the bootanimation?
If so, try to dmesg
dani020110 said:
Can you get to the bootanimation?
If so, try to dmesg
Click to expand...
Click to collapse
No, it's booting the sony logo and then black screen for some seconds and again the sony logo
Jacharcus said:
Hello once again!
The compilation has been finally successful.
If anyone wants to test it, here you have the links and guide that you need. Remember, this is NOT tested and I am in no way responsible if something happens to your phone (not that much can happen, worse case it does not boot and you have to flash using flashtool). This is Sony's Marshmallow Experimental AOSP build for this device by me.
Without further ado, this are the files that you have to download(copy and paste the link, XDA doesn't let me post it without the dashes):
Boot: //https://drive.google.com/open?id=0B0E3yd2mts3wWnpXVUU2Y2ZjWGM//
System: //https://drive.google.com/open?id=0B0E3yd2mts3wVmh4N0h4dkRYcGs//
Userdata: //https://drive.google.com/open?id=0B0E3yd2mts3wY3ZpX3NadmhSM0E//
After downloading them, simply copy them somewhere you can use fastboot and flash them :
fastboot –S 256M flash boot boot.img
fastboot –S 256M flash system system.img
fastboot –S 256M flash userdata userdata.img
Click to expand...
Click to collapse
nrokos said:
I tested it and it resulted in an never-ending bootloop
Click to expand...
Click to collapse
nrokos said:
No, it's booting the sony logo and then black screen for some seconds and again the sony logo
Click to expand...
Click to collapse
Do note you do need to flash the latest marshmallow ftf then this ROM due to the new bootloader present in the new ROMs which allows to load custom ROMs properly...
Can confirm bootloop flashing from stock 6.0.1. Flashing stock ftf, but will test again if something gets changed
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?
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?
Hello all, I've been trying to install /e/ OS GSI on my Redmi Note 11S, but that didn't go exactly well. Luckily, I managed to fix it. So before I brick this thing again, How should I install a GSI properly without bricking, and which GSI would you recommend? I am looking for something more privacy oriented. Thank you in advance
[TOOL][AUTOINSTALLER][GSI]SMINORI GSI AUTO INSTALLER FOCO M4 PRO
After i'm search many tutorial and thread about installing clean and optimal GSI and take a lot of time. So, i decided to make batch auto installer for GSI ROM for help u guys, this is easy way for installing gsi rom WITH JUST PRESS ENTER:sneaky...
forum.xda-developers.com
nothing other than that. thats it.
when it goes wrong u can easly flash full stock with miflshtool
lurchiii said:
[TOOL][AUTOINSTALLER][GSI]SMINORI GSI AUTO INSTALLER FOCO M4 PRO
After i'm search many tutorial and thread about installing clean and optimal GSI and take a lot of time. So, i decided to make batch auto installer for GSI ROM for help u guys, this is easy way for installing gsi rom WITH JUST PRESS ENTER:sneaky...
forum.xda-developers.com
nothing other than that. thats it.
when it goes wrong u can easly flash full stock with miflshtool
Click to expand...
Click to collapse
Thank you
Is there some sort of Linux alternative?
And which GSI would you recommend?
kritomas said:
Thank you
Is there some sort of Linux alternative?
And which GSI would you recommend?
Click to expand...
Click to collapse
I have tried Evolution X A13 & Pixel Experience Plus A13 & CRDROID A12 and on all of them I had issues with Wifi, bluetooth, thethering - non of them worked so I gave up and went back to miui
1. adb reboot bootloader
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (take the vbmeta.img file from your current firmware)
3. fastboot reboot fastboot (because gsi must be flashed in fastbootd )
4. fastboot getvar is-userspace
5. fastboot erase system
6. fastboot delete-logical-partition product_a
7. fastboot flash system YOUR_GSI_ROM.img (system.img)
8. fastboot reboot recovery
9. (in recovery) wipe data
10. (in recovery) reboot to system
i flashed yesterday Arrow OS lite A12 it has several fixes for most common problems on board and it worked very well and smooth.
on telegram you can found a magiskmodul fix for auto-variable Hz and a magisk modul for disable hw-overlays consistent. (cauz after reboot it turn back on automaticly)
BUT gaming performance is horrible and good kernel tweaks are over my level
Had someone tried any of these GSI images without having wifi / bluetooth issues?
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
..... flash vbmeta vbmeta.img (take the vbmeta.img file from your current firmware)
Click to expand...
Click to collapse
Where should I take the vbmeta.img for my phone?
shady9090 said:
Where should I take the vbmeta.img for my phone?
Click to expand...
Click to collapse
Download the Fastboot Firmware that match the Firmware on your phone from here: https://forum.xda-developers.com/t/...dmi-note-11s-4g-poco-m4-pro-4g-fleur.4428655/
Extract it with the file and in the images folder is the vbmeta.
I have this weird issue on every GSIs where the status bar isn't aligned with the camera. Does anyone know how I can fix that?
Dio Off-Brando said:
I have this weird issue on every GSIs where the status bar isn't aligned with the camera. Does anyone know how I can fix that?
Click to expand...
Click to collapse
In the Developer Options is a fix for that. But idk how the exactly Name was for it.
lurchiii said:
1. adb reboot bootloader
2. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (take the vbmeta.img file from your current firmware)
3. fastboot reboot fastboot (because gsi must be flashed in fastbootd )
4. fastboot getvar is-userspace
5. fastboot erase system
6. fastboot delete-logical-partition product_a
7. fastboot flash system YOUR_GSI_ROM.img (system.img)
8. fastboot reboot recovery
9. (in recovery) wipe data
10. (in recovery) reboot to system
i flashed yesterday Arrow OS lite A12 it has several fixes for most common problems on board and it worked very well and smooth.
on telegram you can found a magiskmodul fix for auto-variable Hz and a magisk modul for disable hw-overlays consistent. (cauz after reboot it turn back on automaticly)
BUT gaming performance is horrible and good kernel tweaks are over my level
Click to expand...
Click to collapse
So from Linux with platform-tool installed and by giving the mentioned commands I can flash Gsi rom Pixel Experience right???
fastboot delete-logical-partition product_a??? no b???
yes you can flash it from windows or from linux. they are the same commands..
and yes only a
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
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.