Related
Hi all,
I'm happy to share my TWRP 3.0.2-6 recovery, I ported it from the Elephone P9000. It's for Dual Sim only, please don't ask me for other models (Ultra inclued) I don't have enought time to build them all for now.
I think you just have to change the kernel with Carliv Image Kitchen to port it to your phone (never tested with this easy way), use my released recovery for your model as base for porting, same way for Ultra. Please report and share if working
In this version I fixed partition, you are able to backup and restore all 31 partitions ( except for Cache), all ext4 partitions can be mounted rw (be careful at what you are doing!!). And I applied a new theme (multilang).
Unlocking /data with password is not working.
Flash it with Fastboot.
Download:
https://mega.nz/#!9g53VJjC!1d3Aat3FMD9azFb6REFSj266sXkSI78tTetrZWZplQo
See you !
EDIT: Added screenshots
awww cant wait to try :good::good:
btw, do you have any tuts for building custom rom from the stock one?
caosugai said:
awww cant wait to try :good::good:
btw, do you have any tuts for building custom rom from the stock one?
Click to expand...
Click to collapse
No tuts for the XA, you can try some kitchens like "Assayyed kitchen" to edit the rom. Try guides for MTK devices (64bits) or CM/AOSP. But nothing is made for XA, use them as base.
i dont ask for specialized XA, just xperia rom in general
and can i use the same boot.img of xx.73 for the new rom xx.81?
caosugai said:
i dont ask for specialized XA, just xperia rom in general
and can i use the same boot.img of xx.73 for the new rom xx.81?
Click to expand...
Click to collapse
For Q&A other than TWRP 3.0.2-6 release it's here:
http://forum.xda-developers.com/xperia-xa/help/qa-t-template-thread-sony-xperia-xa-t3479938/page1
Thank you
Help...
rrvuhpg said:
Hi all,
I'm happy to share my new TWRP 3.0.2-6 recovery, I ported it from the Elephone P9000. It's for Dual Sim only, please don't ask me for other models (Ultra inclued) I don't have enought time to build them all for now.
I think you just have to change the kernel with Carliv Image Kitchen to port it to your phone (never tested with this easy way), use my released recovery for your model as base for porting, same way for Ultra. Please report and share if working
In this version I fixed partition, you are able to backup and restore all 31 partitions ( except for Cache), all ext4 partitions can be mounted rw (be careful at what you are doing!!). And I applied a new theme (multilang).
Unlocking /data with password is not working.
Flash it with Fastboot.
Download:
https://mega.nz/#!9g53VJjC!1d3Aat3FMD9azFb6REFSj266sXkSI78tTetrZWZplQo
See you !
EDIT: Added screenshots
Click to expand...
Click to collapse
Hi bro, how to boot into recovery on f3116, i use adb and button but i can't, phone restart and not boot into recovery.
ahero123a said:
Hi bro, how to boot into recovery on f3116, i use adb and button but i can't, phone restart and not boot into recovery.
Click to expand...
Click to collapse
HI, it will not boot to recovery if you have a stock boot
Download the rootpack for Dual Sim and flash the boot.img first.
Fastboot commands are:
"fastboot flash boot boot.img"
"fastboot flash recovery recovery.img"
without quotes.
Change the name of the .img if needed.
TL;DR: Nexus 9 bootloops with every ROM other than stock.
My Nexus 9 will bootloop whenever any custom ROM is installed on it. I follow the usual steps in TWRP (downloading ROM and Gapps, wiping factory reset, flashing the zips and wipe dalvik/cache) will not get any error during installation and regardless of the ROM, I will get my nexus stuck on Google logo. Then I will have to unroot and install stock again and it'll work.
Ive also tried Wugfresh Nexus Root Toolkit and it won't work either. As long as Im on stock, I can root as well and everything is fine.
Any idea what could be happening? I wanna get rid of the damn lag. Have tried Cyanogenmod, Slimrom6 and Pure Nexus Project. All with their recommended gapps and will always end up with my tablet stuck in the Google logo.
Any help is very appreciated.
Sounds like you are doing everything right..
How long are you waiting for the device to start up ? Is it possible you aren't simply waiting long enough ? I'd give it a good 10 - 20 minutes on 1st boot before deciding it's hung in a boot loop.
I am having the exact same problem. I have tried so many roms that install correctly and then when flashing gapps and rebooting it is stuck on the Google logo. And I left my tablet on for a few hours so its definitely bootlooping.
The only thing that comes to mind is bootloader... If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
yup, happening to me too. so, how can i flash the factory image now? thanks.
It's in the stickies. http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Sent from my Nexus 5X using XDA-Developers mobile app
links to 7.x compatible bootloader where?
maelfilk said:
If you coming to androind 7.x from android 6.x, you need to flash new bootloader (for example via ADB), otherwise you'll end up in a bootloop.
Click to expand...
Click to collapse
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
nexacan said:
I understand that i'll have to use adb (actually fastboot) to flash the bootloader. But where do i get the right one for android 7.x and flpunder device?
Could you please post the links for that?
Thanks in advance!
Click to expand...
Click to collapse
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
bootloader flashing process: enough to "fastboot flash bootloader boot*.img"?
maelfilk said:
You can download the necessary image here: https://developers.google.com/android/images
Inside the archive you'll find bootloader and vendor
Click to expand...
Click to collapse
I assume i need the latest 7.0.0 (NRD91N, Nov 2016) bootloader which is inside the latest build?
Then i will need to go through the process like:
Code:
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
Or do i have to do more like described here (Steps 8-9)?
Your help is appreciated, thanks again!
ps: for others who got stuck in the bootloop and don't know how to stop it or turn off the device:
1. reboot into recoverymode in case you have twrp
2. open a terminal
3. type in
Code:
poweroff
an hit enter
Yes, NRD91N
Well , all i did was simple
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
once complete
fastboot reboot-bootloader
That's it
Still not booting...
maelfilk said:
Yes, NRD91N
fastboot flash bootloader bootloader-flounder-3.48.0.0141.img
fastboot reboot-bootloader
...
That's it
Click to expand...
Click to collapse
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
ps: trying with cm-14.1-20161027-UNOFFICIAL-flounder.zip now, but boot seems to hang too and the upper part
of the Nexus 9 is getting really warm. I will leave it for 15 more minutes to wait and see what happens.
nexacan said:
Thanks for clarifying that. Unfortunately i still can't boot into AOSP_flounder_11-18-2016.zip
which i flashed afterwards. The bootloader is shown correctly though. But when i start the
Nexus 9 the message https://g.co/ABH is shown in red.
Which rom are you running? A CM build or AOSP?
Click to expand...
Click to collapse
Hmm sorry i don't knwo why this is happening.
Currently i reverted back to marshmallow roms, i find them more stable.
Do you have twrp? After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
maelfilk said:
Do you have twrp?
Click to expand...
Click to collapse
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
maelfilk said:
After flashing bootloader i go to twrp and do complete wipe and format data, then flash new rom. I had no problems booting.
Click to expand...
Click to collapse
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
nexacan said:
Sure, the latest from TWRP
twrp-3.0.2-1-flounder.img 13M 2016-08-24 16:30:03 EDT
I will try it again - exactly as you describe it. Maybe i missed a step.
How long did you wait after reboot for the system to start up?
Click to expand...
Click to collapse
About 10-15 minutes
It works now!
Thank you maelfilk, i got i running now.
CM boots properly now - though i cannot configure it. During the Setup process
in the first step of selecting the language it crashes. I am sure this will be fixed
with a later version of CM-14.1.
Does someone know any other source for CM-14.1 for flounder?
Meanwhile i will try AOSP again.
Edit: AOSP boots properly but unfortunately WLAN does not work in the AOSP_flounder_11-18-2016.zip build.
I guess this is why you stick to the 6.x builds maelfilk.
большое спасибо
nexacan said:
большое спасибо
Click to expand...
Click to collapse
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
link to the "vendor"
maelfilk said:
Glad it works
As for wlan problem, did you flash the vendor as well? If not it might be the problem
Click to expand...
Click to collapse
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
nexacan said:
Man, you are so helpfull! Where do i find the "vendor" (drivers?) please?
I guess i will find it as it is described here
Click to expand...
Click to collapse
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions in the link you gave. If you have trouble with wlan or camera it usually means that vendor is outdated.
Black bootscreen and hanging after flashing vendor.img (only vendor.img)
maelfilk said:
In the archive with bootloader is another archive with vendor and other images. Just flash it in twrp as in the instructions...
Click to expand...
Click to collapse
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
nexacan said:
I did that and now there is no bootscreen, and the Nexus 9 does not boot up
Maybe i am missing something again? I did a wipe and fresh install, but that did not help.
Also TWRP disappears after flashing vendor.img
Click to expand...
Click to collapse
Are you sure you chose to flash vendor.img in vendor partition in twrp?
I have a bricked Hisense A5 (Qualcomm, China) device which stays in a bootloop and I don't know how I can unbrick it.
Facts are:
Device: Hisense A5 (HLTE202N)
Firmware: Stock L1657 6.03.02.00 / Kernel 4.9.112
- I could flash in edl mode successful a stock firmware, but nothing changed after a reboot
- Device stays with "Hisense and powered by Android screen".
- The bootloader can't be unlocked
- teardown device and disabled battery for some minutes and tried to charge it with a wall charger -> bootloop
What I can (like before flashing in edl-mode):
- Entering edl-mode with a xiaomi edl-cable (Qualcomm HS-USB 9008er mode and diagnostic mode 900E after flashing)
- entering fastboot (pressing volume up while rebooting and connecting pc)
What I can't:
-flashing TF-Mode (Firmware on microSD)
-rebooting to system
-shutdown
-recharging wall charger (bootloop)
-not detected as usb-drive for filetransfer
This bootloop mode you can read quite often. The Xiaomi guys can fix this by flashing a fastboot Firmware, but they have an unlocked bootloader
Anybody knows a solution or what I can try to fix this?
Solved:
https://forum.xda-developers.com/showpost.php?p=82726877&postcount=7
JLowe said:
I have a bricked Hisense A5 (Qualcomm, China) device which stays in a bootloop and I don't know how I can unbrick it.
Facts are:
Device: Hisense A5 (HLTE202N)
Firmware: Stock L1657 6.03.02.00 / Kernel 4.9.112
[...]
Anybody knows a solution or what I can try to fix this?
Click to expand...
Click to collapse
Have you already considered trying to use the 6.09.06.00 ROM available via forum.xda-developers.com/showpost.php?p=82583733&postcount=28 ?
defylogic said:
Have you already considered trying to use the 6.09.06.00 ROM available via forum.xda-developers.com/showpost.php?p=82583733&postcount=28 ?
Click to expand...
Click to collapse
Yes, sorry forgot that to mentioned. Good point. That was the first I tried with some other guys in the thread but it doesn't work at all. Tried different microSD and formatting.
Well if the TF Mode not working with 6.0.9 and you have 6.0.3 which is already rooted logic say to try not with 6.0.9 but with 6.0.4 update or better with 6.0.3 but original i.e not rooted. I think something in 6.0.3 is not compatiblle with something in 6.0.9. Simply as that. I remember I say guy in thread for Hisense A5 root which had all update files and WeChat group?
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
gowin132 said:
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
Click to expand...
Click to collapse
Do you have the same files of 6.09.06 version? If yes, please share. I have same problem but my phone has latest OS version.
gowin132 said:
I think you have damaged the recovery or vbmeta partition. You can try to flash back the original boot, recovery and vbmeta partition of 6.03.02. I think this will unbrick your phone. I have uploaded these files to Google Drive. You can try to flash back these files to see if this can save your phone. These files are the original partitions from version 6.03.02. If you still fail, then you may need to flash back system.img or vendor.img, these files are huge. You can ask me later if you still fail.
https://drive.google.com/file/d/1LqcR6NVlSqL6gT6y1y1x9r58_LAKBBjd/view?usp=sharing
Click to expand...
Click to collapse
Great, these files are working flawless in qfil. Could recover the system and then update in Tf-Mode to actual 6.09
These are the original boot, recovery and vbmeta image from 6.09.06.
https://drive.google.com/file/d/1JeUEaBxpH5zu22v-6V_6LAqZzGuXmUhf/view?usp=sharing
Mehedi34 said:
Do you have the same files of 6.09.06 version? If yes, please share. I have same problem but my phone has latest OS version.
Click to expand...
Click to collapse
Do you guys have full firmware with system and other imgs?? Mine seems to still bricked
lillo9546 said:
Do you guys have full firmware with system and other imgs?? Mine seems to still bricked
Click to expand...
Click to collapse
I'm sorry for asking what is probably a silly question, but how exactly do you flash files like boot.img using Qfil ?
I can get into fastboot., but not edl mode.
I know old thread, but am having problems with a bricked A5. After a lot of trial and error, it sometimes gets into Fastboot mode. I can then ask for fastboot device and it responds with a hex number and fastboot.
When I try to flashall new partitions, it fails with:
fastboot: error: ANDROID_PRODUCT_OUT not set or non allowed.
Once I could flash individual partition with:
fastboot flash boot boot_recovery_vbmeta_6.03.02/boot.img
Sending 'boot' (65536 KB) OKAY [ 2.113s]
Writing 'boot'
But then it just sits there and nothing seems to happen.
Anyone has suggestions on what to try, am running out of ideas
.
It would be amazing if anyone could share:
- Stock ROM 6.12 full QFIL backup.
- EFS/QCN backup files.
Thanks
JLowe said:
Great, these files are working flawless in qfil. Could recover the system and then update in Tf-Mode to actual 6.09
Click to expand...
Click to collapse
Hi. I have the same problem as you, but I don't know how to flash those files with qfil. Can you please explain it to me?
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?