[ROM] AOSP 10 [arm64/arm] - Treble-Enabled Device Development A/AB ROMS

This is AOSP 10 for devices lunched with Android 9.0 , for older devices and devices with overlays and better support generally use this :
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
but if you want lean & mean AOSP with no modification and minimal gapps , here you go :
https://mega.nz/#!y7J1DCRL!YcPmXLGf71ptVF4IP3N_46Y5o4yOOac32Pj1lSmQ0G0
also it is a user build so it passes basicintegrity , to pass CTS install safeteypatcher from magisk repo .
arm build :
https://mega.nz/#!7yggQC5A!EyXx_ZJ1hGInlf_XXYwYAZU8qtErajsNJzGdmDsEWqs

any source?github?

reynard1 said:
any source?github?
Click to expand...
Click to collapse
it's built on top QP1A.191105.004 with mindthegapps :
https://gitlab.com/MindTheGapps/vendor_gapps

@AJ
Be more specific in describing your builds. Arm64 - A-only or A/B ?

Nordicus said:
@AJ
Be more specific in describing your builds. Arm64 - A-only or A/B ?
Click to expand...
Click to collapse
Need this info OP

Nice work. Could you upload an arm32 version?

Nordicus said:
@AJ
Be more specific in describing your builds. Arm64 - A-only or A/B ?
Click to expand...
Click to collapse
Go to proper thread from OP. That one is only some like an info, I think.

Nordicus said:
@AJ
Be more specific in describing your builds. Arm64 - A-only or A/B ?
Click to expand...
Click to collapse
read this :
https://source.android.com/setup/build/gsi#p-gsi-build-targets
the new naming arm64 apply to both AB and non AB .

Hanthonious said:
Nice work. Could you upload an arm32 version?
Click to expand...
Click to collapse
arm build added .

AJ said:
arm build added .
Click to expand...
Click to collapse
Awesome man thanks but is A64 a-only supported?

Not booting, is the arm32 system A or AB?

Hanthonious said:
Not booting, is the arm32 system A or AB?
Click to expand...
Click to collapse
you have to be on stock rom then flash system & vbmeta with :
fastboot --disable-verification flash vbmeta vbmeta.img
and it works on both a and a/b if your device shipped with android 9

mahmmoud1231 said:
Awesome man thanks but is A64 a-only supported?
Click to expand...
Click to collapse
Check post #8

AJ said:
This is AOSP 10 for devices lunched with Android 9.0 , for older devices and devices with overlays and better support generally use this :
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559
but if you want lean & mean AOSP with no modification and minimal gapps , here you go :
https://mega.nz/#!y7J1DCRL!YcPmXLGf71ptVF4IP3N_46Y5o4yOOac32Pj1lSmQ0G0
also it is a user build so it passes basicintegrity , to pass CTS install safeteypatcher from magisk repo .
arm build :
https://mega.nz/#!7yggQC5A!EyXx_ZJ1hGInlf_XXYwYAZU8qtErajsNJzGdmDsEWqs
Click to expand...
Click to collapse
bugs reported?

I tried flashing this rom via fastboot but faced sparse error, tried with twrp but system failed to boot. My device is Infinix s5, I am able to boot phh gsi 9.0 without issues and yes my device was released with android 9.0.

contactwajeeh said:
I tried flashing this rom via fastboot but faced sparse error, tried with twrp but system failed to boot. My device is Infinix s5, I am able to boot phh gsi 9.0 without issues and yes my device was released with android 9.0.
Click to expand...
Click to collapse
The official flashing instructions :
Code:
fastboot erase system
fastboot flash system system.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot reboot
If the sparce error means nit enough space in system do :
fastboot delete-logical-partition product_a if A is your main slot

AJ said:
The official flashing instructions :
Code:
fastboot erase system
fastboot flash system system.img
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot -w
fastboot reboot
If the sparce error means nit enough space in system do :
fastboot delete-logical-partition product_a if A is your main slot
Click to expand...
Click to collapse
I followed the exact same instructions, I get the following error after I enter fastboot flash system system.img
"Invalid sparse file format at header magic"
Edit: that is when I tried to flash with twrp, but it resulted in bootloop just soon after the initial device logo. Please advise.

contactwajeeh said:
I followed the exact same instructions, I get the following error after I enter fastboot flash system system.img
"Invalid sparse file format at header magic"
Click to expand...
Click to collapse
Which fastboot and system are you using ??

AJ said:
Which fastboot and system are you using ??
Click to expand...
Click to collapse
fastboot version 29.0.5-5949299
Installed as C:\Windows\fastboot.exe on windows 10

contactwajeeh said:
fastboot version 29.0.5-5949299
Installed as C:\Windows\fastboot.exe on windows 10
Click to expand...
Click to collapse
I would try older fastboot that mtch your rom security patch , and also maybe try linux if you have access to it .

Related

Teclast M40 How to unlock bootloader?

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.

Development GSIs status + boot dump

Hello,
Here is the status as of few days ago. So most of Phh-based GSI should have the same status, just pick whichever you want.
What works:
- Backlight control works (requires "Force alternative backlight scale" in Treble Settings => Misc)
- 5G
- Bluetooth
- A2DP/Bluetooth media (requires "Force disable A2DP offload" in Treble Settings => Misc)
- USB-C headset
- Speaker
- 90Hz screen (Recommend "Force FPS" to 90Hz in Treble Settings => Misc)
- BSG GCam
- SELinux enforcing
- Encrypted userdata
- 65W Dash charge
What doesn't work:
- Under-display fingerprint
- Others?
Fixed in my AOSP GSI v311 (2021-08-07):
- Access to auxiliary cameras (Expose Aux cameras in Treble Settings => Misc)
Fixed in future AOSP GSI release:
- VoLTE (needs to click all 4 options in Treble Settings => IMS Settings)
- Alert slider
Links:
My AOSP GSI
List to other GSIs -- I recommend to try out LeOS, CAOS, or AndyYan's LineageOS
Flash procedure:
- Unlock bootloader
- Reboot into bootloader
- Download https://dl.google.com/developers/android/qt/images/gsi/vbmeta.img
- `fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img`
- `fastboot reboot fastboot`
- `fastboot flash system system-roar-arm64-ab-gapps.img`
- On the phone itself, do a full factory reset
As a small bonus, I attach the boot.img that I got on my device. It could be useful for people wanting to root with magisk, since currently the stock ROM isn't available. In exchange, I'd really like a dump of system partiton
Hmm... if i patch the boot dump with magisk it doesnt boot... if i flash the dump as it is, it boots fine
Thanks BTW!
do i have to flash vbmeta as well?
HofaTheRipper said:
do i have to flash vbmeta as well?
Click to expand...
Click to collapse
Hum yeah, it's likely that if you modify boot.img you need to disable boot.img verification through vbmeta
phhusson said:
Hum yeah, it's likely that if you modify boot.img you need to disable boot.img verification through vbmeta
Click to expand...
Click to collapse
OK i shouldnt have done this... now i have root bot no wifi/bluetooth anymore :-(
HofaTheRipper said:
OK i shouldnt have done this... now i have root bot no wifi/bluetooth anymore :-(
Click to expand...
Click to collapse
Does fingerprint unlocking work properly after rooted?
mlgmxyysd said:
Does fingerprint unlocking work properly after rooted?
Click to expand...
Click to collapse
Yes but i am rooted on oxygen... i think this boot.img missmatches with my modem firmware and so wifi and bluetooth is broken.
@phhusson do you have your modem.img for me to fix my problem or do you have another idea?
Hum there is no modem partition
hmmm do you have any idea, why my wlan and bluetooth isnt working anymore? wrong version of boot.img?
Have no bt address and a weird wifi mac
HofaTheRipper said:
hmmm do you have any idea, why my wlan and bluetooth isnt working anymore? wrong version of boot.img?
Click to expand...
Click to collapse
Do you have Indian varient?
No... should be EU Variant
ravinder0003 said:
Do you have Indian varient?
Click to expand...
Click to collapse
No should be EU Variant
Yeah it should be vendor/boot mismatch, so AFAIK, I'm on latest OTA, I'm assuming you too?
[ro.bootimage.build.fingerprint]: [alps/vnd_oplus6893/oplus6893:11/RP1A.200720.011/1626976753491:user/release-keys]
[ro.odm.build.fingerprint]: [OnePlus/DN2103EEA/OP515BL1:11/RP1A.200720.011/1626976753491:user/release-keys]
This is the build I currently have.
I've attached my vendor as well (which contains the kernel module that I'm guessing you are missing)
Can you dump your system partition, and send it to me? I need it for various developments
phhusson said:
Yeah it should be vendor/boot mismatch, so AFAIK, I'm on latest OTA, I'm assuming you too?
[ro.bootimage.build.fingerprint]: [alps/vnd_oplus6893/oplus6893:11/RP1A.200720.011/1626976753491:user/release-keys]
[ro.odm.build.fingerprint]: [OnePlus/DN2103EEA/OP515BL1:11/RP1A.200720.011/1626976753491:user/release-keys]
This is the build I currently have.
I've attached my vendor as well (which contains the kernel module that I'm guessing you are missing)
Can you dump your system partition, and send it to me? I need it for various developments
Click to expand...
Click to collapse
How do i flash this vendor.xz ?
my build is now (broken wifi / bt):
[ro.bootimage.build.fingerprint]:[OnePlus/DN2103EEA/OP515BL1:11/RP1A.200720.011/1627567766349:user/release-keys]
[ro.odm.build.fingerprint]: [OnePlus/DN2103EEA/OP515BL1:11/RP1A.200720.011/1627567766349:user/release-keys]
i would be happy to help you with a system dump. please tell me what to do.
K, looking at your properties, looks like I don't have the latest OTA, hum weird.
Decompress vendor.xz into vendor, then `fastboot flash vendor vendor` (you can rename vendor.xz to vendor.img.xz if it eases your spirit)
To make a system dump, from termux, with magisk installed, do:
`su` then `dd if=/dev/block/mapper/system of=/sdcard/system.img`, then retrieve system.img to your computer, compress it, and send it
phhusson said:
K, looking at your properties, looks like I don't have the latest OTA, hum weird.
Decompress vendor.xz into vendor, then `fastboot flash vendor vendor` (you can rename vendor.xz to vendor.img.xz if it eases your spirit)
To make a system dump, from termux, with magisk installed, do:
`su` then `dd if=/dev/block/mapper/system of=/sdcard/system.img`, then retrieve system.img to your computer, compress it, and send it
Click to expand...
Click to collapse
ok i will make the dump
btw:
C:\Fastboot\Fastboot ROMinstaller\fastboot_installer>fastboot flash vendor vendor
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/6 (131056 KB) OKAY [ 3.116s]
Writing 'vendor' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
This is what im getting
You need to do `fastboot reboot fastboot` before being able to flash vendor
phhusson said:
You need to do `fastboot reboot fastboot` before being able to flash vendor
Click to expand...
Click to collapse
Thank you very much! its working!!!
system.img is on the way!

Development Oneplus Nord 2 Oxygen 11.3 DN2103 EEA ROM

Flash at your own risk. I am not responsible for any damage or data loss to the device during this process!
Downloads:
The Fastboot restoration file can be downloaded in here:
DN2103_11_A.07
DN2103_11_A.10 *deleted
DN2103_11_A.11 *deleted
please use ota files to upgrade
File folder on MEGA
mega.nz
include Flash Root & TWRPinstaller
tool for Windows (.bat)
Special Thanks: @HofaTheRipper @phhusson
Caution! Please check your version on your mobile phone before flashing. these files may only be used for V07!​If you want to upgrade, use the ota files here.​
Oneplus Nord 2 Oxygen 11.3 DN2103_11_A.10 EEA ROM
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! Downloads: The Fastboot restoration file can be downloaded in here: https://mega.nz/folder/bMwxRCKb#E_ZX3TfA9hhbuODHMquxDA include...
forum.xda-developers.com
before flashing
Backup your nvcfg.img, nvdata.img, nvram.img, persist.img, proinfo.img, protect1.img and protect2.img with Partition Backup from Playstore
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
Interesting! Could I ask what ROM this is?
Eastw1ng said:
Interesting! Could I ask what ROM this is?
Click to expand...
Click to collapse
Hi, this is Oxygen OS .. I forget it in the Title Thanks
11.3.A07 EEA and​11.3.A10 EEA​
After doing this, will the updates come from oneplus as usual?
xirosiman said:
After doing this, will the updates come from oneplus as usual?
Click to expand...
Click to collapse
Yes, but i not test to Upgrade
sakarya1980 said:
Hi, this is Oxygen OS .. I forget it in the Title Thanks
11.0.3.A07 EEA​
Click to expand...
Click to collapse
Hey thanks for the reply, my question was mostly if this is the stock rom for the oneplus nord 2, or is this a different rom made compatible?
Eastw1ng said:
Hey thanks for the reply, my question was mostly if this is the stock rom for the oneplus nord 2, or is this a different rom made compatible?
Click to expand...
Click to collapse
Stock, not custom
sakarya1980 said:
Yes, but i not test to Upgrade
Click to expand...
Click to collapse
I tested. You must flash without root, then can you upgrade @xirosiman
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process!​
OTA files here (put this files to your OTG)
File folder on MEGA
mega.nz
Click to expand...
Click to collapse
Stock boot.img https://mega.nz/folder/fZx2nBaR#Q33lJstFRMQg6_0j7Z0TJw
Click to expand...
Click to collapse
Please use this commands
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta2.img
Fastboot flash boot nord2_stock_boot_A07.img
ok i managed to make it run.
when all is done, it can not boot.
i managed to flash the boot.img from the other thread in order to make it run.
xirosiman said:
ok i managed to make it run.
when all is done, it can not boot.
i managed to flash the boot.img from the other thread in order to make it run.
Click to expand...
Click to collapse
You must flash vbmeta2 then boot.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta2.img
Do you try v10? You can not flash from v7 to v10 and please check your driver
ok i have done it. Somehow the wifi toggle wasnt working but after flashing vbmeta and boot its ok.
i managed to go to A7 stock and now is updating to A10.
One thing i noticed, the combination of volume down and start button has changed only to fastboot.
And the only way to go to recovery is from command
also it can not recognise the sim cards
and the updade through ota is failed. it can not verify says
xirosiman said:
ok i have done it. Somehow the wifi toggle wasnt working but after flashing vbmeta and boot its ok.
i managed to go to A7 stock and now is updating to A10.
One thing i noticed, the combination of volume down and start button has changed only to fastboot.
And the only way to go to recovery is from command
also it can not recognise the sim cards
and the updade through ota is failed. it can not verify says
Click to expand...
Click to collapse
You can't update from 7 to 10. You must flash ota file with v9, then Upgrade to 10.
Wlan and Bluetooth works, after flash v7 again
Here ota files
https://mega.nz/folder/rQhhHQpA#nNHvPlmzBXwPjmaFpuDa2Q
Please put both file to your otg storage and flash it, with stock recovery. Every time after flash vbmeta2
You can start recovery with fastboot reboot recovery
Downgrading from 10 to 7 was not successful. Even if the rom works it can not recognise the sim cards.
Now i am flasing 10 to see if it works
during flashing its says "Invalid sparse file format at header magic" do this has something to do with drivers?
xirosiman said:
Downgrading from 10 to 7 was not successful. Even if the rom works it can not recognise the sim cards.
Now i am flasing 10 to see if it works
during flashing its says "Invalid sparse file format at header magic" do this has something to do with drivers?
Click to expand...
Click to collapse
dont abort this. Invalid sparse file format at header magic" is normal, but you must wait ...
sakarya1980 said:
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process!​
Please use this commands
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta2.img
Fastboot flash boot nord2_stock_boot_A07.img
Click to expand...
Click to collapse
Did a full upgrade from stock 07 to 09 then 10, went perfectly.
Thanks Sakarya!
Eastw1ng said:
Did a full upgrade from stock 07 to 09 then 10, went perfectly.
Thanks Sakarya!
Click to expand...
Click to collapse
Hi, good ota flash 07 to 09?
Yeah OTA flash from 07 to 09, then a flash from 09 to 10 and followed up with the rooted boot image to make sure everything was as you described. Works flawlessly!
Is there any way to flash the ROM without fastboot? I bricked the phone and I'm unable to get to fastboot.
Update tonOxygen 11.3 DN2103_11_A.10 EEA​include Flash Root & TWRPinstaller
tool for Windows (.bat)
[RECOVERY][UNOFFICIAL] TWRP 3.5.2_11-0 for OnePlus Nord 2 5G [denniz]
https://forum.xda-developers.com/t/...-2_11-0-for-oneplus-nord-2-5g-denniz.4335021/

Question How to install a GSI properly?

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

Development [RECOVERY] TWRP for Samsung Galaxy Tab A7 Lite [Universal] [UNOFFICIAL] [Android 13]

Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the Galaxy Tab A7 Lite.​
Download - You'll always find the latest release in here: https://github.com/DevZillion/android_device_samsung_gta7litewifixx/releases​Known Issues / Report Issues - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx/issues​Telegram support group - https://t.me/gta7litegroup​
How to install​
[Boot Into Download mode by inserting an usb cable while holding both volume buttons]
Flash the latest .tar release from releases.
Hold the recovery combination (Volume Up + Power) while the .tar is flashing via the odin tool.
When booted up into TWRP go Flash and flash this zip, then go to Wipe > Format Data, all your data will be lost.
You can now boot into your system and do whatever you want.
Click to expand...
Click to collapse
​Flashing Disabled vbmeta (To boot a modified system)​
Spoiler: View
Extract the vbmeta.img.lz4 from the AP slot in your firmware.
Remove it's lz4 compression [for Windows use lz4]:
Code:
sudo apt-get install lz4 -y
lz4 vbmeta.img.lz4
Click to expand...
Click to collapse
Reboot into fastboot from TWRP flash vbmeta using this command line:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Sources​
TWRP Source - https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
Device Tree - https://github.com/DevZillion/android_device_samsung_gta7litewifixx/
Kernel Source - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx
Click to expand...
Click to collapse
Special thanks to:​
TeamWin for the Recovery Project.
Zillion for doing the device tree & kernel.
Click to expand...
Click to collapse
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
Genial!!
Zillion said:
Team Win Recovery Project or TWRP for short. Its a fully touch driven user interface, completely theme-able & you can change just about every aspect of the look and feel.
Now ported to the Galaxy Tab A7 Lite WiFi.​
Download - You'll always find the latest release in here: https://github.com/DevZillion/android_device_samsung_gta7litewifixx/releases​Known Issues / Report Issues - https://github.com/DevZillion/android_kernel_samsung_gta7litewifixx/issues​Telegram support group - https://t.me/gta7litegroup​
How to install​
​Flashing Disabled vbmeta (To boot a modified system)​
Sources​
Special thanks to:​
Actual TWRP status: Bugfixing; Try at your own risk and only if you know what you're doing.
Click to expand...
Click to collapse
it boots, touch does not work but its usable with a mouse and gives an error "unable to mount /data"
dda7lite said:
it boots, touch does not work but its usable with a mouse and gives an error "unable to mount /data"
Click to expand...
Click to collapse
Please, read the How To Install section.
Zillion said:
Please, read the How To Install section.
Click to expand...
Click to collapse
I did but the file that needs to be flashed is unavailable in that link
dda7lite said:
I did but the file that needs to be flashed is unavailable in that link
Click to expand...
Click to collapse
Thanks for reporting the issue, link fixed.
Zillion said:
Thanks for reporting the issue, link fixed.
Click to expand...
Click to collapse
i have other problem error "E:unable to open block device /dev/block/sda: No medium found"
What is vbmeta?
I want to install Elixir Project. Is it necessary to do something from the vbmeta? Or just flashing the rom is enough?
chocovo said:
What is vbmeta?
I want to install Elixir Project. Is it necessary to do something from the vbmeta? Or just flashing the rom is enough?
Click to expand...
Click to collapse
Flash vbmeta is necessary to boot a new system but it's easy to flash too.
dda7lite said:
Flash vbmeta is necessary to boot a new system but it's easy to flash too.
Click to expand...
Click to collapse
I understand that the vbmeta is pulled from original samsung firmware, lz4 format stripped and flashed by AP. Then we implement the command by TWRP and the desired rom is installed.
Is that so?
Does the vbmeta step have to be done every time I put a new rom or only once?
Sorry for my english
chocovo said:
I understand that the vbmeta is pulled from original samsung firmware, lz4 format stripped and flashed by AP. Then we implement the command by TWRP and the desired rom is installed.
Is that so?
Does the vbmeta step have to be done every time I put a new rom or only once?
Sorry for my english
Click to expand...
Click to collapse
I only did once and I didn't use the stock vbmeta I just searched "vbmeta disabled Samsung" it should show up with vbmeta disabled android 11 but works the same on 13 and I didn't use TWRP only fastboot so i don't know how to flash it there.
Btw your English is good don't worry.
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
chocovo said:
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
Click to expand...
Click to collapse
Yeah
chocovo said:
After installing TWRP I can't install the fbe. TWRP doesn't recognize my device's internal memory either.
Click to expand...
Click to collapse
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Zillion said:
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Click to expand...
Click to collapse
Bootloop after
Zillion said:
Because you need to flash the fbe_disabler using some usb otg, external sd card or by pushin the zip to /tmp, flash it and then format /data.
Click to expand...
Click to collapse
My device is a T220.
The touch does not work in TWRP and I use a mouse. I use Micro SD to install the FBE. But when trying to install it gives me an error in the data folder. Although apparently it seems to be installed.
I format data as you indicate and restart in fastboot in TWRP to put the vbmeta by ADB and install a GSI. But it generates bootloop.
I don't know if I'm missing some step.
chocovo said:
My device is a T220.
The touch does not work in TWRP and I use a mouse. I use Micro SD to install the FBE. But when trying to install it gives me an error in the data folder. Although apparently it seems to be installed.
I format data as you indicate and restart in fastboot in TWRP to put the vbmeta by ADB and install a GSI. But it generates bootloop.
I don't know if I'm missing some step.
Click to expand...
Click to collapse
If you really want to flash a gsi and can't get it to work use a fastboot enabled recovery that's what I did
dda7lite said:
Bootloop after
Click to expand...
Click to collapse
Disable vbmeta, it's the only thing I can see you missed.
um i flashed the recovery to my sm-t220 but i do not have a usb otg i am buying it today in the meanwhile i tried to boot back to one ui 5.1 the one i have but it only shows twrpto reboot i used power + volume down but it shows twrp and power + volume up dosnt do anything
Gian-D said:
um i flashed the recovery to my sm-t220 but i do not have a usb otg i am buying it today in the meanwhile i tried to boot back to one ui 5.1 the one i have but it only shows twrpto reboot i used power + volume down but it shows twrp and power + volume up dosnt do anything
Click to expand...
Click to collapse
Force restart and keep the usb cable connected to the PC and tablet then as soon as screen blinks hold volume +and-

Categories

Resources