Database Users

[HOW-TO] Convert to F2FS on Nexus 6 (ALMOST - Any Rom)

BE WARNED - THIS WILL ERASE EVERYTHING ON YOUR PHONE. DO NOT ATTEMPT THIS IF YOU HAVE NOT MADE A BACKUP AND/OR ARE NOT READY TO REINSTALL EVERYTHING ON YOUR PHONE FROM SCRATCH.
Credit goes to bbedward for his initial thread regarding this concept.
STATUS:
2017/01/08 - Not liking the performance of my Galaxy S3, so I've ordered a new phone (Huawei P8 Lite) for $58 from eBay! Supposedly brand new. I figured I'd have to give it a try just to see. Once I set this phone up I'll start tinkering with my Nexus 6 again. Phone should arrive around 17 Jan!
FOCUS:
Getting F2FS on ANY ROM, but for my purposes, I'm focused on getting F2FS with Flash Kernel to work on Nitrogen OS (if this can be done, then it can be done with any ROM!)
BASICS:
- Need recovery & kernel that support f2fs (tools + kernel driver version must match or be compatible - not sure what the specifics are yet)
Latest New Info:
- The Flash has said that his kernel and crDroid work with F2FS (I haven't tested it myself yet - this version of crDroid actually specifies F2FS support)
2017/01/08
- Found this thread by NABENDU1. It's for Nexus 4, but it gives some good insight on how F2FS works.
- @vprasad1 found another working combination (post #15) - franco.Kernel - r60 Anykernel 7.1.1 with Danvdh's Stock Lite N6F26Q 7.1.1
Explaining a few details:
The issue here is that the exact version of F2FS tools included in most modded recoveries isn't actually specified (that I have found) and the version of tools that end up in the ROM (/system/bin/), which come from the recovery unless built into the ROM, must be compatible. One of the following is true (not sure which one yet):
- the F2FS tools version must be the same or greater than the kernel driver support version
- the F2FS tools version must be the same or less than the kernel driver support version
- the F2FS tools version must match the kernel driver support version
Given that The Flash is consistently including the latest F2FS support in his kernel, and since I've had the most trouble getting F2FS support to work with his kernel and other ROMs that technically don't support F2FS (using bbedward's method mentioned above - link to thread included) I'm inclined to think that the F2FS tools must be the same or greater version compared to the kernel driver support, though I have no way of confirming this yet. Hopefully I'll have different luck with Flash Kernel v1.7!
========
I used:
- Nexus Root Toolkit v2.1.9
- Nitrogen OS 2016-11-19
- MagiKernel v1.1 Stable-1023
- TWRP 3.0.2-0 (modded by xanaxdroid - thread is here)
(TWRP v3.0.2-0 by xanaxdroid mirror) - the original link is down.
I'll take these down if xanaxdroid asks. I have yet to hear from him...
Steps for clean install (and initial install of F2FS recovery / conversion to F2FS):
1) revert to stock (Nexus Root Toolkit)
2) flash recovery with f2fs support (Nexus Root Toolkit)
3) boot into recovery on device
4) full wipe device (normal wipe)
5) convert /cache & /data to f2fs
6) copy over desired kernel and rom to /sdcard
7) install rom & then kernel
8) run adb commands:
# adb shell
# mount -o rw /system
# cp /sbin/fsck.f2fs /system/bin/
# cp /sbin/mkfs.f2fs /system/bin/
# chmod a+x /system/bin/*f2fs*
9) reboot
========
When changing ROMs/kernel (F2FS recovery already installed):
1) boot into recovery
2) do full wipe (f2fs should have stayed from the first time)
3) install rom & then kernel
4) run adb commands:
# adb shell
# mount -o rw /system
# cp /sbin/fsck.f2fs /system/bin/
# cp /sbin/mkfs.f2fs /system/bin/
# chmod a+x /system/bin/*f2fs*
5) reboot
========
More semi-lengthy explanation about fstab:
bbedward suggests a difference in the fstab as being the primary suspect causing the difference in compatibility. Here's the only difference I could find that seemed to be relevant:
- the fstab that worked (MagiKernel + TWRP v3.0.2-0 (by xanaxdroid) + Nitro OS)
/devices/*/xhci-hcd.0.auto/usb* auto auto defaults voldmanaged=usb:auto
- the fstab that didn't work (Flash Kernel + TWRP v3.0.2-0 (by xanaxdroid) + Nitro OS)
*block/sda* auto auto defaults voldmanaged=usbdisk:auto,noemulatedsd
Both fstab files did clearly have the lines needed to mount /data and /cache as f2fs, but they were identical.
NOTE: I also tried TWRP v3.0.0-0 (by xanaxdroid) with Flash Kernel and still no dice. I'm a fan of Flash Kernel since it's my first custom kernel I've played with. I hope to be able to use it some day with Nitrogen OS! Until then, thanks MagiKernel! (maybe I'll convert??? ) <- MagiKernel development has halted for now
========
What I've tried before:
All of the following implies that I've used the previously mentioned adb commands to copy over the f2fs tools and set the proper permissions.
In my experience, it seems that f2fs requires just the right combination of kernel + recovery. For example I used Nitrogen OS (2016-11-19) + Flash Kernel + mod TWRP 3.0.2-0 and it hasn't worked for me, but Nitrogen OS + MagiKernel + mod TWRP v3.0.2-0 did work. The failure for f2fs to work with Nitro OS + Flash Kernel is very reproducible, as is the success with Nitro OS + MagiKernel. (Again using TWRP v3.0.2-0 modded by xanaxdroid).
Keep in mind that the developer of Flash Kernel (developed by The Flash) has tested his kernel with crDroid (a CyanogenMod base ROM) and it worked for him, but I don't know what version of modded TWRP he was using and what version of f2fs tools were in that recovery. From what I've noticed, there seems to be a fundamental difference with CyanogenMod based ROMs when it comes to f2fs support, either that or there's just a version mismatch of f2fs tools between certain recovery + kernel combos. I don't know enough to understand the difference yet, but it is clear that just because a kernel claims to support f2fs doesn't mean that it will work with any ROM, even if you follow bbedward's tutorial mentioned at the top of this post.
The kernel and the recovery must work together (as in what version of mkfs.f2fs / fsck.f2fs supported by kernel & recovery must match (i think - thanks to bbedward again for this info)). The main issue here is that most modded recovery zips/imgs (that I have found) don't list the version of f2fs tools they have. On the other hand usually you can see this info on the main page of any given kernel developer.
I haven't found any specific rhyme or reason yet, but for those looking for Nitrogen OS (2016-11-19 - Android 7.1 - Nougat) + f2fs, this will help you.
NOTE: I'm a clean-freak, so I enjoy clean flashes, so my instructions are geared toward clean flashes, not dirty flashes. Having said that, doing this with a dirty flash is possible, but it will depend on the ROM/kernel you choose as to the details in how you upgrade/switch the ROM/kernel. Done properly, you should only have to switch file systems once and forego any future wiping of your /sdcard or internal storage.
========
NOTE : You'll know your recovery + kernel combo isn't working right when it takes longer than usual to get off the bootloader screen and start with your ROM's animation boot screen. If it's taking too long, you're probably having everything converted back to ext4.
*** WARNING *** WARNING *** WARNING *** WARNING ***
DO NOT INTERRUPT THIS PROCESS DURING BOOT. If you do then you'll render your /data partition inaccessible. It's still fixable with Nexus Root Toolkit > revert to stock, but that's a pain and it takes a while.
This OP will be updated as new info is uncovered!

Thank you for the updated tutorial and information! Been reading up on the benefits and side effects of f2fs. But wasn't sure on whether to do it. Like you I am on nitrogen ROM, 12.4.26. and am a fan of flash kernel. Il will definitely look into this. Also I notice that the link you posted for magikernel isn't working. Either way huge thank you.
Edit - Just read the original thread. Want to thank you again for hoe you asked for his approval first before making a new thread. Very respectful. Not to say people don't respect devs or users in general. Just wanted to add I appreciate you taking the time to reach out him first prior to making this thread.
Thank you again.
Sent from my Nexus 6 using XDA-Developers mobile app

ozzmanj1 said:
Thank you for the updated tutorial and information! Been reading up on the benefits and side effects of f2fs. But wasn't sure on whether to do it. Like you I am on nitrogen ROM, 12.4.26. and am a fan of flash kernel. Il will definitely look into this. Also I notice that the link you posted for magikernel isn't working. Either way huge thank you.
Edit - Just read the original thread. Want to thank you again for hoe you asked for his approval first before making a new thread. Very respectful. Not to say people don't respect devs or users in general. Just wanted to add I appreciate you taking the time to reach out him first prior to making this thread.
Thank you again.
Click to expand...
Click to collapse
Thanks for the feedback!
I'm still researching a way to get Flash Kernel with Nitro OS + f2fs. I have some ideas. I'll update the first post with any new findings.
Edit: unfortunately MagiKernel is dead. So ill be hot on another trail soon. Also MagiKernel isnt as good as Flash out-of-the-box in my experience so far.

ozzmanj1 said:
Also I notice that the link you posted for magikernel isn't working. Either way huge thank you.
Click to expand...
Click to collapse
I actually just tested the link to MagiKernel on my PC and my phone (on XDA Labs) and it worked fine. Are you using another (older) version of XDA forum viewer?
EDIT: OP updated. The "issues" we all run into is a version mismatch between RECOVERY & KERNEL mostly. As long as RECOVERY & KERNEL f2fs tools match, then you can copy over (mkfs.f2fs & fsck.f2fs) from /sbin/ to /system/bin/ and get any ROM to be compatible with F2FS.
EDIT: modified links and removed "" in URL tags. The quotes were necessary for proper display in the XDA Labs app, but not compatible with XDA Legacy app. I've switched to use XDA legacy!

Will this fix low battery throttling and video recording

PunishedSnake said:
Will this fix low battery throttling and video recording
Click to expand...
Click to collapse
LOL, no.
This won't "fix".... ANYTHING.
In fact, this will very likely BREAK things.

Lol how so

No not breaking things here ... Not any more than usual tinkering under the hood... I'm just trying to flush out bbedward's old thread with some more info...

PunishedSnake said:
Will this fix low battery throttling and video recording
Click to expand...
Click to collapse
To give you an answer, no it won't. This info will only "possibly" help you get a ROM to run on f2fs that was not initially designed to do so.

@ozzmanj1
Well the Nitrogen OS ROM developer just let me know he has no plan to include F2FS tools. Looks like we gotta go with plan B...

TheArkive said:
@ozzmanj1
Well the Nitrogen OS ROM developer just let me know he has no plan to include F2FS tools. Looks like we gotta go with plan B...
Click to expand...
Click to collapse
That is a darn shame. Looking at the comparisons of Ext4 and F2FS and it makes me wonder why it has gone more popular. I appreciate your time and work looking into this. Sadly with my schedule I do not have to do a lot of digging with wife, and kids and works....blah blah....lol. Anyways, thank you for letting me know about Nitro.
Side note, any suggestions on another ROM that you are aware of that supports F2FS?

ozzmanj1 said:
That is a darn shame. Looking at the comparisons of Ext4 and F2FS and it makes me wonder why it has gone more popular. I appreciate your time and work looking into this. Sadly with my schedule I do not have to do a lot of digging with wife, and kids and works....blah blah....lol. Anyways, thank you for letting me know about Nitro.
Side note, any suggestions on another ROM that you are aware of that supports F2FS?
Click to expand...
Click to collapse
The Flash said that latest crDroid worked fine. I haven't been able to confirm yet. I have a new smartphone on the way to setup as my primary phone while I experiment on my Nexus 6. Won't get here until Jan 23rd

TheArkive said:
The Flash said that latest crDroid worked fine. I haven't been able to confirm yet. I have a new smartphone on the way to setup as my primary phone while I experiment on my Nexus 6. Won't get here until Jan 23rd
Click to expand...
Click to collapse
Just came across this new kernel that has f2fs support. Based on flash kernel and afew other kernels.
http://forum.xda-developers.com/showthread.php?t=3526034
Going to look into it as flash kernel may drop nexus 6 support soon due to school obligations
Sent from my Nexus 6 using XDA-Developers mobile app

ozzmanj1 said:
Just came across this new kernel that has f2fs support. Based on flash kernel and afew other kernels.
http://forum.xda-developers.com/showthread.php?t=3526034
Going to look into it as flash kernel may drop nexus 6 support soon due to school obligations
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for the news! I'll be checking that out as well.

FYI this works using franco.Kernel - r60 Anykernel 7.1.1 with Danvdh's Stock Lite N6F26Q 7.1.1
Code:
mount | grep f2fs
/dev/block/platform/msm_sdcc.1/by-name/userdata on /data type f2fs (rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type f2fs (rw,seclabel,nosuid,nodev,noatime,nodiratime,background_gc=on,user_xattr,inline_xattr,acl,inline_data,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6)
I tried Aero 1.0 Linaro kernel with Danvdh's Stock Lite N6F26Q 7.1.1 but it kept forcing /cache and /data to return to ext4.

Could also be that the rom is coded not to allow it as it is not really stable enough. Main reason it is not implemented in Android.

zelendel said:
Could also be that the rom is coded not to allow it as it is not really stable enough. Main reason it is not implemented in Android.
Click to expand...
Click to collapse
Was that in response to my post???
Sent from my SM-N910T using Tapatalk

vprasad1 said:
FYI this works using franco.Kernel - r60 Anykernel 7.1.1 with Danvdh's Stock Lite N6F26Q 7.1.1
I tried Aero 1.0 Linaro kernel with Danvdh's Stock Lite N6F26Q 7.1.1 but it kept forcing /cache and /data to return to ext4.
Click to expand...
Click to collapse
Many thanks for the info! I'm definitely trying to find combinations that in fact do work, and hopefully derive a method for getting it to work on other combinations as well (hopefully).
Thanks again for the help!

TheArkive said:
Many thanks for the info! I'm definitely trying to find combinations that in fact do work, and hopefully derive a method for getting it to work on other combinations as well (hopefully).
Thanks again for the help!
Click to expand...
Click to collapse
Just a quick link I came across. Not sure if it's useful but as it pertains to f2fs I thought I'd share.
https://www.xda-developers.com/xda-...upersu-has-trouble-with-f2fs-data-partitions/
Sent from my Nexus 6 using XDA-Developers Legacy app

What is F2FS
Can Ya Here Me Now

[UNOFFICIAL][PATCHER][APP] DualBootPatcher for Galaxy A5 2017 Exynos

I'm proud to present the first dual boot project for the Samsung Galaxy A5 2017 Exynos version. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary.
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads
Patcher: Download
Utilities: Download
XDADevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy A5 2017 Exynos
Contributors
simon151102
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Beta

simon151102 said:
I'm proud to present the first dual boot project for the Samsung Galaxy A5 2017 Exynos version. This project started off as a feature in my ROM, but not anymore. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary.
Donators
A huge thanks goes out to all of the donators for supporting this project! I if forgot to add you (and you want to be added), please send me a quick PM.
See all of our supporters here
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
NOTE: If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Otherwise, any mods will need to be patched before flashing.
How to use the patcher
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
Well, Just flash the patched zip file via recovery (Custom Recovery, like TWRP of course)
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
How do I...?
Switch the ROM if something doesn't work properly?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a ROM.
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Downloads
Patcher: https://drive.google.com/open?id=18rN9RqiSWlbwBXPlZzdsXw4W4ZQD2tId
Utilities: https://drive.google.com/open?id=158n-YhyHqjvNfhZJWpFTYWgDIqsIBaaL
XDADevDB Information
DualBoot Patcher APP, Device Specific App for the Samsung Galaxy A5 2017 Exynos
Contributors
simon151102
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Beta
Click to expand...
Click to collapse
But, there is official support for our device, what's different in this version?

sheepkill15 said:
But, there is official support for our device, what's different in this version?
Click to expand...
Click to collapse
Ofiicial patcher only supports the A5 2017 with Snapdragon SoC, it wont work on the Exynos version. Basically the only difference is the architecture.
A patched ROM for A5 2017 Snapdragon wont work on A5 2017 Exynos. So heres support for the Exynos version

simon151102 said:
Ofiicial patcher only supports the A5 2017 with Snapdragon SoC, it wont work on the Exynos version. Basically the only difference is the architecture.
A patched ROM for A5 2017 Snapdragon wont work on A5 2017 Exynos. So heres support for the Exynos version
Click to expand...
Click to collapse
I see. I didn't know that

sheepkill15 said:
I see. I didn't know that
Click to expand...
Click to collapse
No problem dude?

Wait, there is a version of the A5 2017 with Snapdragon Soc?

MinwooChong said:
Wait, there is a version of the A5 2017 with Snapdragon Soc?
Click to expand...
Click to collapse
Yeah, the US A5 2017 is powered by a Snapdragon 660. Other countries (like korea, germany, ...) have Samsungs Exynos 7880 instead.

Does it support Oreo and pie ROMs???

iloveoreos said:
Does it support Oreo and pie ROMs???
Click to expand...
Click to collapse
Im able to boot Oreo and Pie ROMs, but I have not tested much ROMs (only tested RR with android 8 and PixelExperience with android 9).
For me they are working without problems

simon151102 said:
Im able to boot Oreo and Pie ROMs, but I have not tested much ROMs (only tested RR with android 8 and PixelExperience with android 9).
For me they are working without problems
Click to expand...
Click to collapse
Cool. Hope I have success with this version.

I just tried pixel experience as the second rom. Failed with error 1 like normal. Is there a certain slot that works better? I usually do ext sd.

iloveoreos said:
I just tried pixel experience as the second rom. Failed with error 1 like normal. Is there a certain slot that works better? I usually do ext sd.
Click to expand...
Click to collapse
I always use data slot, extsd isnt working for me(dont know why).
But make sure you checked the A5 2017 exynos, it normally checks the snapdragon one when patching a zip

Update 13 Feb
Patcher and Utilities built from latest sources with support for A5 2017 Exynos and (because someone in the main DBP thread asked) support for S9 Plus Snapdragon.
Patcher: https://drive.google.com/open?id=1ND...Jh4imaAbgR1Chz
Utilities: https://drive.google.com/open?id=13H...1PlJ6bI8bpydSh

Update
Added a few more codenames (A520W, A520DS)
Patcher: Download
Utilities: Download

Update
Re-compiled the app with a different linker (got some errors before)
Patcher: Download
Utilities: Download

simon151102 said:
Update
Re-compiled the app with a different linker (got some errors before)
Patcher: Download
Utilities: Download
Click to expand...
Click to collapse
Tried with the last update and dual boot app keeps stopping..(force closes)
EDIT:The app force closes only when i press the tab ROMS.

broky said:
Tried with the last update and dual boot app keeps stopping..(force closes)
EDIT:The app force closes only when i press the tab ROMS.
Click to expand...
Click to collapse
Which ROM are you using as primary ROM?
I cant reproduce the error on any of my ROMs.
Sharing logs would be great

simon151102 said:
Which ROM are you using as primary ROM?
I cant reproduce the error on any of my ROMs.
Sharing logs would be great
Click to expand...
Click to collapse
I m using Hades rom V6 for primary.

broky said:
I m using Hades rom V6 for primary.
Click to expand...
Click to collapse
I think this is a ROM-related bug Im not able to fix.
This bug has to be fixed in the sources I guess, and as Im not a programmer, I have no idea how to do this.
Im sorry

Boot loop on a520f after updating ramdisk
After updating ramdisk for primary rom (hadesrom v1.5) phone goes into bootloop.
But lineageos 16 as secondary works well even after updating ramdisk.

[ROM]ZTE Blade v10 (v1000) GSI

I managed to install Android 11 lineage os 18.0 on this phone.
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
The only bug I can find is cut off rounded corners when dpi of the screen got changed.
If there is any interest in this phone I will post a guide.

Hi , is it working good ?? can you post photos and guide in details please ? ThANK YOU !!!

Bravo and well done. I loved my Blade back in the day.

tkaczyk24 said:
I managed to install Android 11 lineage os 18.0 on this phone.
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
The only bug I can find is cut off rounded corners when dpi of the screen got changed.
If there is any interest in this phone I will post a guide.
Click to expand...
Click to collapse
Please make a guide

I would appreciate a guide. Thanks!

phrak9 said:
I would appreciate a guide. Thanks!
Click to expand...
Click to collapse
There’s a solution, but German: https://www.android-hilfe.de/forum/...163/android-10-fuer-das-blade-v10.951084.html
I Attached a translation ...

Did you brick your phone?
I have built a new StockRom based on v1.2 (not TELCEL) for ZTE Blade v10 MT6771.
It works great but knowledge of using SP_Flash_Tool is necessary. Link can be found in PDF-File.
Additionally I added the links of Android 10 v2.1 and v2.2. All Files are downloadable.

Merci

Installation of “Android 12” is also possible.
1. Install Stockrom 1.2 (see above) without formating
2. Boot “Recovery”
3. Wipe Cache and Data
4. Boot "Bootloader" and install "TWRP"
Use “adb” or “TWRP” flashing custom rom.
Roms available here: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I was testing - DescendantOS, ArrowOS, Corvus, crDroid, AOSP, CherishOS, SuperiorOS.
I examined in particular "Rooting" and the functions of "TWRP" successfully.
But stay carefully. I don’t know if all functions are working.

Is 'Android 12' working fine on the phone? Thanks!

In particular, I tested only "Root" (Magisk) and "TWRP" functions. Other apps also worked very well. For example, "Google Speech" had no problems. However, I did not test the phone function, since I did not use the main phone for my tests.
Suggestion: To be on the safe side, make a complete(!) backup with TWRP, using a USB stick (16GB or more) as storage. But first format the stick with ExFat, not FAT32 or NTFS, because the file 'system image = system_image.emmc.win' has about 5GB. Well, it takes some time ... about 20-30 minutes.
So far positive: SuperiorOS, KomodoOS, crDroid, CherishOS, xdroid, EvolutionX, dotOS, Descendant, Corvus, Awaken, AncientOS, ArrowOS
Others partially prevented boot or responded incorrectly.

kilowatito17 said:
In particular, I tested only "Root" (Magisk) and "TWRP" functions. Other apps also worked very well. For example, "Google Speech" had no problems. However, I did not test the phone function, since I did not use the main phone for my tests.
Suggestion: To be on the safe side, make a complete(!) backup with TWRP, using a USB stick (16GB or more) as storage. But first format the stick with ExFat, not FAT32 or NTFS, because the file 'system image = system_image.emmc.win' has about 5GB. Well, it takes some time ... about 20-30 minutes.
So far positive: SuperiorOS, KomodoOS, crDroid, CherishOS, xdroid, EvolutionX, dotOS, Descendant, Corvus, Awaken, AncientOS, ArrowOS
Others partially prevented boot or responded incorrectly.
Click to expand...
Click to collapse
Great! Thank you very much for your update!

'Android 13' and ZTE Blade v10 (V1000)

"Pixel Experience Plus" I tested even more positively, but with the same limitations.
https://github.com/ponces/treble_build_pe/releases/download/v2022.11.24-plus/PixelExperience_Plus_arm64-ab-vndklite-13.0-20221124-UNOFFICIAL.img.xz

TWRP works with https://sourceforge.net/projects/gsi-projects/files/A13/ArrowOS/08012023/ ...

Furthermore noteworthy:
crDroid (Nazim):
https://github.com/naz664/crDroid_gsi/releases/download/v2023.04.08/crDroid-9.3-arm64_bgN-Unofficial.img.xz
SparkOS (Nazim):
https://github.com/naz664/SparkOS_gsi/releases/download/v2023.03.20/SparkOS-13.5.5-arm64_bgN-Unofficial.img.xz

Hello. i got a zte blade v30 vita what i can do with it

urued said:
Hello. i got a zte blade v30 vita what i can do with it
Click to expand...
Click to collapse
Sorry, I only work with Blade V1000, so I can not give any advices.
( Perhaps possible: Root zte, install TWRP and make a full(!!!!) backup - look at #12 because of usb-stick OTG - --> https://twrpupdate.com/how-to-install-twrp-recovery-on-zte-blade-v30-vita/ )
No more help possible

kilowatito17 said:
In particular, I tested only "Root" (Magisk) and "TWRP" functions. Other apps also worked very well. For example, "Google Speech" had no problems. However, I did not test the phone function, since I did not use the main phone for my tests.
Suggestion: To be on the safe side, make a complete(!) backup with TWRP, using a USB stick (16GB or more) as storage. But first format the stick with ExFat, not FAT32 or NTFS, because the file 'system image = system_image.emmc.win' has about 5GB. Well, it takes some time ... about 20-30 minutes.
So far positive: SuperiorOS, KomodoOS, crDroid, CherishOS, xdroid, EvolutionX, dotOS, Descendant, Corvus, Awaken, AncientOS, ArrowOS
Others partially prevented boot or responded incorrectly.
Click to expand...
Click to collapse
Please a guide to install evolution x.
I tried the few options I found and only got Brick my phone

Use "SP_Flash_Tool_v5.2216" (https://www.mediafire.com/file/6i3lk32xjezu2b3/SP_Flash_Tool_v5.2216_Win.zip/file) for unbricking. See PDF at #7, #6 and download. After that unroot, install TWRP. Try once more, but never format !!!

[ROM][UNOFFICIAL][PORT] Resurrection Remix Q for htc one m8

ive used Lineage OS' device tree for the htc one m8 to port Resurrection Remix Q to the HTC one m8.
thought i better post it here, seeing as there seems to be no other RR Q ports for this phone anywhere else.
just flash it via TWRP.
please let me know if you find anything thats broken. im rather new to ROM making.
note: this rom isn't pre-odexed so first-boot might take a bit.
this is the kernel source i used: https://github.com/LineageOS/android_kernel_htc_msm8974/tree/lineage-17.1
and this is the device tree: https://github.com/LineageOS/android_device_htc_m8/tree/lineage-17.1
all i did was copy&paste the kernel and dev tree into RR's source directory, rewritethe references to lineage inside the device files to reference RR, fixed some SELinux compatibility issues, and then proceeded as normal to build RR.
UPDATE: 03-02-2021
fixed boot failure after restoring TWRP backup

i have been made aware that this does not boot upon restoring a TWRP backup.
i have updated the zip in the original post to fix this.

Any plans to get on official RR?

fela4 said:
Any plans to get on official RR?
Click to expand...
Click to collapse
likely not. RR hasnt supported the m8 in a few years now.

mathew2214 said:
ive used Lineage OS' device tree for the htc one m8 to port Resurrection Remix Q to the HTC one m8.
thought i better post it here, seeing as there seems to be no other RR Q ports for this phone anywhere else.
just flash it via TWRP.
please let me know if you find anything thats broken. im rather new to ROM making.
note: this rom isn't pre-odexed so first-boot might take a bit.
this is the kernel source i used: https://github.com/LineageOS/android_kernel_htc_msm8974/tree/lineage-17.1
and this is the device tree: https://github.com/LineageOS/android_device_htc_m8/tree/lineage-17.1
all i did was copy&paste the kernel and dev tree into RR's source directory, rewritethe references to lineage inside the device files to reference RR, fixed some SELinux compatibility issues, and then proceeded as normal to build RR.
UPDATE: 03-02-2021
fixed boot failure after restoring TWRP backup
Click to expand...
Click to collapse
The ROM itself is excellent,I have one on Samsung, but this one does not work at all, the interface freezes constantly.Very sorry...

try formtatting data to f2fs and then clean-flashing the rom.

mathew2214 said:
try formtatting data to f2fs and then clean-flashing the rom.
Click to expand...
Click to collapse
Does this ROM work well for you?

@[email protected] said:
Does this ROM work well for you?
Click to expand...
Click to collapse
yes! it works rather well. most of the issues i run into are magisk bugs. other than that there's only the occasional systemui lag that lasts for maybe a second or two, and this only happens maybe once a day. i should be noted that i reboot my phone several times a day, and i dont use Gapps.

mathew2214 said:
yes! it works rather well. most of the issues i run into are magisk bugs. other than that there's only the occasional systemui lag that lasts for maybe a second or two, and this only happens maybe once a day. i should be noted that i reboot my phone several times a day, and i dont use Gapps.
Click to expand...
Click to collapse
I don't use Gapps,I use MicroG and I have a system freeze in almost every application.

@[email protected] said:
I don't use Gapps,I use MicroG and I have a system freeze in almost every application.
Click to expand...
Click to collapse
sounds like a storage operation issues. see if switching the system partition format to ext4, cache to ext4. userdata and internal storage to f2fs helps at all. clean-flash after you change formats. if that does nothing, please tell me if the presence (or lack of) an external SD card affects this in any way.

mathew2214 said:
sounds like a storage operation issues. see if switching the system partition format to ext4, cache to ext4. userdata and internal storage to f2fs helps at all. clean-flash after you change formats. if that does nothing, please tell me if the presence (or lack of) an external SD card affects this in any way.
Click to expand...
Click to collapse
I tried to use this ROM in various ways, switching the system partition to ext4 and to f2fs, both with an sd card and without sd. Nothing helps - constant freezes of the smartphone, yesterday I installed Lineage 17.1-it works smoothly and without delays. And so I wanted Resurrection Remix Q, sorry...

I tried to do a clean install ,and then I tried to flash over RR-P-v7. 0. 2-20190507-m8-Release, nothing helps.It freezes so that you have to press the off button and the volume rocker with two fingers until a full reboot.

update rom

miyqwx said:
update rom
Click to expand...
Click to collapse
sorry but i cannot. i am no longer in possession of a functioning m8.

mathew2214 said:
sorry but i cannot. i am no longer in possession of a functioning m8.
Click to expand...
Click to collapse
If you post a video on how to port a rom, maybe I can add non-ROMs to the device, example havoc

mathew2214 said:
sorry but i cannot. i am no longer in possession of a functioning m8.
Click to expand...
Click to collapse
i tried various tests and i found a working rom on the device but the screen was not working there was a mouse as if using a computer
-
The processor in the rom I ported is the same as the processor of the m8

Android S GSI (System-As-Root) on on Smart Tab M10 (TB-X605F)

Preface: After trail and error on installing Android GSI ROMs to my TB-X605F, I successfully made it after reading this thread written by @Yahoo Mike, which is also of great significance for my research. Generalizing it to the newer version Android-Installing and the other partition architectures, I finally drew a conclusion on how to install Android S GSI (System-As-Root) on on Smart Tab M10 (TB-X605F).
Credits:
　　　　@AndyYan, builder of the GSI images which was used in this project.
　　　　@erfanoabdi, developer of MakeMeSar patch.
　　　　@phhusson, developer of phh project treble ROMs.
　　　　@Yahoo Mike, illuminator of installing GSI on this device.
(Sorted alphabetically)
　　In this article, I'll introduce the way to install Android S GSI ROMs on the Lenovo Smart Tab M10 (I've only tested it on TB-X605F since I got one at hand. Theoretically, the other tablets in this series, such as TB-X605L should also work). Broadly speaking, this is a generalized method to install all System-As-Root GSI ROMs on this device, but I haven't tested it with the other kinds of ROMs. So, before we start, make a full backup of your device, which'll prevent you from lose all your important data after formatting your device. Also, you'd better to get knowledge of what you're doing and what you're going to do. This project is currently experimental, which means you may brick your device at any time, which is at your own risk.
　　Here are the steps.
1. Restoring Stock Android Pie Firmware with EDL.
　　1.1. Download the stock pie firmware from https://mirrors.lolinet.com/firmware/lenovo/Tab_M10/TB-X605F/.
　　1.2. Assume that you've backed your device up, if not, do it now. Then, reboot it into EDL mode. There're many ways to do it, power it off and press Vol+ and Vol-, connect it with the PC at the same time. If you have TWRP installed in it, you can also get your device into TWRP and press "Reboot->EDL". Or you can reboot it into fastboot mode and use this command:
fastboot reboot edl
Click to expand...
Click to collapse
If your device is unfortunately in "brick" status or your system cannot do such operations for certain reasons, you can open the back case, short these two test points shown in the picture. and connect it with your PC.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
　　1.3. Flash the firmware into your device via QPST or QComDLoader.
2. Installing TWRP.
　　2.1. Download the TWRP from https://twrp.me/lenovo/lenovo_X605F.html. Currently, I'm using ver 3.6.0.
　　2.2. Unlock the bootloader.
　　2.3. Reboot your device into fastboot, and
fastboot flash recovery path/to/twrp/img
Click to expand...
Click to collapse
　　2.4. Reboot into TWRP by pressing Vol+, Vol- and Power.
3. Getting Files Prepared.
　　3.1. We aim to install Android S GSIs on this device, @phhusson's GSIs are a good choice, you can find them at Project Treble GSI images. Currently, I use the LineageOS 19.0 built by @AndyYan as example. I got it here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-19.x/.
　　　　IMPORTANT: As we all know, this device use A-only partition architecture and no System-As-Root support, which is originally not supported by Android S. As a result, we're going to patch it to run Android S. As a consequence, when you're chose ROMs, download the ROMs which're ARM64 A/B Vndklite (arm64_bvS-vndklite) to match the patched device.
　　3.2. Download the System-As-Root patch which makes the device support System-As-Root. This patch called MakeMeSar, made by @erfanoabdi. You can find it here: https://androidfilehost.com/?fid=4349826312261728344. This patch will rewrite your boot partition to support System-As-Root, as a result, all the changes you've applied to the boot partition (such as magisk root or supersu root) will be gone.
　　3.3. Download the Disable_Dm-Verity. This is a patch to get rid of dm-verity and to disable the Verified Boot, which'll disable force encrypt of userdata partition and prevent the TWRP from being raplaced with the stock recovery. Get it here: https://zackptg5.com/android.php#disverfe.
　　3.4. Download the modify_phh_gsi.sh made by @Yahoo Mike. On conscious that it has trouble in mounting system when the device was patched to support System-As-Root, I modified the script to support (only) System-As-Root. Get it here: https://github.com/JunASAKA/modify_phh_gsi_sar.
4. Flashing
　　4.1. Boot into TWRP.
　　4.2. Format userdata partition and transfer all related files into your device.
　　4.3. Flash MakeMeSar patch.
　　4.4. Flash Dm-Verity patch.
　　4.5. Flash Android GSI ROMs. You can also do this in fastboot mode:
fastboot flash system path/to/gsi/img
Click to expand...
Click to collapse
　　4.6. Reboot into TWRP again (Simply press Reboot->Recovery in TWRP).
　　4.7. Resize2fs system and run the modify_phh_gsi_sar.sh in terminal. Firstly, press "Wipe->Advanced Wipe->Select system->Repair or Change File System->Resize File System" in twrp before using the script. Tnen, in the terminal:
sh path/to/modify_phh_gsi_sar.sh
Click to expand...
Click to collapse
　　4.8. Format userdata partition again to clean up (You can skip this step if you commit no change to userdata partition).
　　4.9. Reboot to system (In TWRP, press Reboot->System).
5. Your device will boot into the System you flashed if everything goes well. Enjoy !
fin. Here are the screenshots of Lineage OS 19.0 installed.
ps. Known Issues.
　　1. The system may mistake the tablet for "emulated device".
　　2. Cannot decrypt userdata even if the Dm-Verity was installed.
Further research is on going.
　　For other things regarding the GSI ROMs, such as GAPPS and Magisk root, it's strongly recommend to read this thread written by @Yahoo Mike.

浅香ジュン said:
ps. Known Issues.
　　1. /system_root cannot be mount in TWRP.
　　2. Cannot decrypt userdata even if the Dm-Verity was installed.
Click to expand...
Click to collapse
Sounds like TWRP will need to be modified for SAR devices.
My first guess is that the fstab needs to be updated to add a mount for /system_root. And the BoardConfig.mk needs some extra entries for the A12 keymaster to work (PLATFORM_VERSION and PLATFORM_VERSION_LAST_STABLE).
If you DM me the fstab from your patched boot.img, I'll build you a modified twrp on the weekend.
Hopefully, we can use the same TWRP for SAR and non-SAR tablets.

After modifing to SAR, any problems using LMSA to restore the tablet back to stock ?

Yahoo Mike said:
Sounds like TWRP will need to be modified for SAR devices.
My first guess is that the fstab needs to be updated to add a mount for /system_root. And the BoardConfig.mk needs some extra entries for the A12 keymaster to work (PLATFORM_VERSION and PLATFORM_VERSION_LAST_STABLE).
If you DM me the fstab from your patched boot.img, I'll build you a modified twrp on the weekend.
Hopefully, we can use the same TWRP for SAR and non-SAR tablets.
Click to expand...
Click to collapse
Well, I think I found the solution to system-mounting. After flashing the system.img, before executing the modify_phh.sh, Go to ”Wipe->Advanced Wipe->Select system->Repair or Change File System->Resize File System”. And then execute the modify_phh.sh. This way, the system can be successfully mount. Just press “mount” in twrp and select system, the /system_root and /system will be mount automatically. Consequently, I think the fstab of TWRP version 3.6.0 is all set and needn’t to be modified, it can automatically detect whether the device is SAR or not.
Yahoo Mike said:
After modifing to SAR, any problems using LMSA to restore the tablet back to stock ?
Click to expand...
Click to collapse
As to restoration, I haven’t try LMSA yet, I always use EDL mode for restoration. But since the MakeMeSAR patch will only make differences to boot partition, I think LMSA should also work, but I haven’t tested it yet.
Additionally, there is another problem that there is “About Emulated Device“ shown in settings main page instead of “About Tablet”. I am wondering why the ROM mistake my tablet for a emulated device? I tried to add
ro.build.characteristics=tablet
Click to expand...
Click to collapse
to build.prop both in vendor and system partition, but it seems to be of no avail.
I am making further researches on that and data partition decryption.
Thanks for your help, I’ll update my post later.

浅香ジュン said:
Well, I think I found the solution to system-mounting. After flashing the system.img, before executing the modify_phh.sh, Go to ”Wipe->Advanced Wipe->Select system->Repair or Change File System->Resize File System”. And then execute the modify_phh.sh. This way, the system can be successfully mount.
Click to expand...
Click to collapse
Resizing in TWRP just runs resize2fs. The script does that. Maybe it's the order the commands are run in? Or maybe the command needs to be run against a different partition for SAR? The script currently only checks for /system.
浅香ジュン said:
Additionally, there is another problem that there is “About Emulated Device“ shown in settings main page instead of “About Tablet”. I am wondering why the ROM mistake my tablet for a emulated device?
Click to expand...
Click to collapse
Is that how MakeMeSAR works? I couldn't find any documentation about it. Unpacking the RAM cpio in MakeMeSAR might hold the answer.
You might also find a hint in the phh GSI or AOSP code. There will be a test that results in "Emulated Device". Whatever the conditions of that test are, they will point you in the right direction.

Yahoo Mike said:
Resizing in TWRP just runs resize2fs. The script does that. Maybe it's the order the commands are run in? Or maybe the command needs to be run against a different partition for SAR? The script currently only checks for /system.
Is that how MakeMeSAR works? I couldn't find any documentation about it. Unpacking the RAM cpio in MakeMeSAR might hold the answer.
You might also find a hint in the phh GSI or AOSP code. There will be a test that results in "Emulated Device". Whatever the conditions of that test are, they will point you in the right direction.
Click to expand...
Click to collapse
Yes, that may helpful to find out more information about SAR in this device, I’ll test the Phh GSI today.

Hi really impressed by the work being done here,always wanted to try out a12 doing it now btw can i use any pixel gsi with this or maybe anyway that the new android 12L gsi works on this tab as it is optimized for large screen devices

FrontMan69 said:
Hi really impressed by the work being done here,always wanted to try out a12 doing it now btw can i use any pixel gsi with this or maybe anyway that the new android 12L gsi works on this tab as it is optimized for large screen devices
Click to expand...
Click to collapse
I think most of the phh-gsi based ROMs, Pixel Experience included, should work fine. As to Android 12L, it’s worth a try!

浅香ジュン said:
I think most of the phh-gsi based ROMs, Pixel Experience included, should work fine. As to Android 12L, it’s worth a try!
Click to expand...
Click to collapse
Thanks! keep up the good work

浅香ジュン said:
I think most of the phh-gsi based ROMs, Pixel Experience included, should work fine. As to Android 12L, it’s worth a try!
Click to expand...
Click to collapse
hi tried the pixelexperience gsis they seem to not flash show not enough storage available
maybe its a device specific restriction

FrontMan69 said:
hi tried the pixelexperience gsis they seem to not flash show not enough storage available
maybe its a device specific restriction
Click to expand...
Click to collapse
Well, that’s because the system partition is not big enough to install pixel experience. But you could try to re-partition the tablet with the “parted”. Just delete the original system partition and create a new one bigger, I used to re-partition my Huawei mobile when installing custom GSIs.

浅香ジュン said:
Well, that’s because the system partition is not big enough to install pixel experience. But you could try to re-partition the tablet with the “parted”. Just delete the original system partition and create a new one bigger, I used to re-partition my Huawei mobile when installing custom GSIs.
Click to expand...
Click to collapse
hi sorry for the ping but i cannot install gapps with los nikgapps installs but play store doesnt show up and bitgapps doesnt install

Update: So far tried Pixel Experience , Octavi,ArrowOS and phh gsis out of all only lineage works no success at install gapps on lineage so far

FrontMan69 said:
Update: So far tried Pixel Experience , Octavi,ArrowOS and phh gsis out of all only lineage works no success at install gapps on lineage so far
Click to expand...
Click to collapse
I'm sorry for hearing that. And according to my experience installing gapps, that's may on account that there is no enough space left in system partition. The best way to solve it is to re-partition the device, which is testing by me. Btw, is there no original gapps installed in Pixel Experience?

浅香ジュン said:
I'm sorry for hearing that. And according to my experience installing gapps, that's may on account that there is no enough space left in system partition. The best way to solve it is to re-partition the device, which is testing by me. Btw, is there no original gapps installed in Pixel Experience?
Click to expand...
Click to collapse
pixel experience doesnt flash saying that there isnt any more storage left in the partition with octavi and arrow i get error 4 in twrp aosp cannot be resized and with los as i said gapps cannot be flashed

I followed the instructions and got vanilla A12 AOSP (squeak) loading.
After boot, is anyone else getting the error message: Android System: there's an internal problem with your device. Contact your manufacturer for details. ?
credstore crashes during init. So that might be causing the error message (?)
As for TWRP, keymaster is crashing. That's why there's no decryption. I'll strace it tomorrow to see if we can get around it.
And I can confirm LMSA restores stock ROM fine after using MakeMeSAR. (BTW, LMSA now uses QFil rather than QComDLoader.)

Yahoo Mike said:
I followed the instructions and got vanilla A12 AOSP (squeak) loading.
After boot, is anyone else getting the error message: Android System: there's an internal problem with your device. Contact your manufacturer for details. ?
credstore crashes during init. So that might be causing the error message (?)
As for TWRP, keymaster is crashing. That's why there's no decryption. I'll strace it tomorrow to see if we can get around it.
And I can confirm LMSA restores stock ROM fine after using MakeMeSAR. (BTW, LMSA now uses QFil rather than QComDLoader.)
Click to expand...
Click to collapse
i tried squeak with go gapps didnt flash also btw big fan mike any working a11 gsis ? also how can i repartition my tablet

Bad news on the TWRP front. There are two issues.
First, the Keymaster key data structure was changed in A12. I can patch TWRP to fix that. Easy!
But the second issue is massive. Keymaster is crashing with "Configure failed" after a KM_ERROR_INVALID_ARGUMENT (-38) error. This is pointing to a version mismatch.
There have been extensive modifications to the TWRP A11 git branch to patch that error. Those modifications have not been made in the A9 branch. Probably because not many people are putting A12 on devices originally released with A8.
We are stuck with stock keymaster blobs from A9. For compatibility reasons, I need to compile TWRP from the A9 branch. It might be possible to use keymaster blobs from a similar A10 device - assuming the kernel needs no modifications. If someone wants to put in the time to get this working, I'm happy to offer you some hints to get you started. You can PR the updates to my github repo. If it works, I'll push them to TWRP gerrit.

Yahoo Mike said:
Bad news on the TWRP front. There are two issues.
First, the Keymaster key data structure was changed in A12. I can patch TWRP to fix that. Easy!
But the second issue is massive. Keymaster is crashing with "Configure failed" after a KM_ERROR_INVALID_ARGUMENT (-38) error. This is pointing to a version mismatch.
There have been extensive modifications to the TWRP A11 git branch to patch that error. Those modifications have not been made in the A9 branch. Probably because not many people are putting A12 on devices originally released with A8.
We are stuck with stock keymaster blobs from A9. For compatibility reasons, I need to compile TWRP from the A9 branch. It might be possible to use keymaster blobs from a similar A10 device - assuming the kernel needs no modifications. If someone wants to put in the time to get this working, I'm happy to offer you some hints to get you started. You can PR the updates to my github repo. If it works, I'll push them to TWRP gerrit.
Click to expand...
Click to collapse
OK, I’ll check it. But I think it seems impossible for me to do that. Anyway, I’ll try my best.

Why can't I use the camera? The camera App stops running when it opens.