I started fiddling even more with installing GSI-A partitions roms into the Ulefone Armor 6 as of today. Here's how you install GSI-A roms. I have tried roms from Android 8-10 official & unofficial. Lineage, RR, Pixel Experience, & etc...
Disclaimer:
I am not responsible if you damage, brick, or willingly alter your phone in any way shape or form blah blah blah, you get the point.
I did not fully test with 100 certainty these GSI-A roms below. Even the ones below that I did test have many bugs/issues. The ones below were the ones that booted correctly for me. Test at your own discretion. Some of these roms wont have SU & GAPPS.
Prerequisites:
Make sure you have an unlocked bootloader.
Make sure your phone has, TWRP installed.
Make sure you have drivers installed, here.
Fastboot & ADB tools, here.
Rom's I've tested & boot on Armor 6:
Android 10
1. (AOSP) Android 10 by phhusson
2. PixelExperience 10.0 BETA by ExpressLuke
3. Havoc OS 3.0 by ExpressLuke
Android 8
4. Resurrection Remix by phhusson
Any other GSI-A roms being supported can be found here, feel free to try out your own if you feel like it.
Installation:
1. Place your device in, "Fastboot mode"
2. Open up command prompt (cmd) on your computer, cd into the folder where fastboot & adb is in, and type, "fastboot erase system"
{
"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"
}
3. Now flash the GSI-A image to your Armor 6 system partition. "fastboot flash system (what ever your system name).img"
4. This following command will format userdata & cache. "fastboot -w"
5. Last but not least step using fastboot, is to reboot your device. "fastboot reboot"
Now, pay attention.
When you flash the system image to your device, it only flashes the minimum data size that comes with the image. You have to reboot into TWRP, Resize /data partition & format to EXT4 to get the full 128GB partition size.
6. Boot into TWRP. To do this, power off the device and press both the, "Power button + Volume up button" at the same time during which you should see the bootloader menu. To move between options to have to press the volume up, until you are hovering over, "recovery" option. Then press volume down, to select recovery and boot into it.
7. Select the, "wipe" option.
8. Select & check mark, "Data" first, then secondly, select, "Repair or change file system."
9. Resize the data partition.
10. Now change the file system format, to, "EXT4"
Now reboot the phone
That's all there's to it. Not all GSI-A images will work, if they don't work, the developer of that GSI-A has to make it so. Good luck.
thanks dude, are roms working without bugs? mobile network and gps working?
Weekend I will try to install the Ressurection Remix or Pixel Experience (10), I'm still in doubt rsr, and bring news if it's working well with me. thanks!
What is the current method we are using to bypass dm-verity?
Thanks a ton for your work.
Pergmen said:
What is the current method we are using to bypass dm-verity?
Thanks a ton for your work.
Click to expand...
Click to collapse
I format the partitions to ext4 and flashed the dm-verity zip. I'll send you the link once I get home.
SMAAALLL BR said:
thanks dude, are roms working without bugs? mobile network and gps working?
Weekend I will try to install the Ressurection Remix or Pixel Experience (10), I'm still in doubt rsr, and bring news if it's working well with me. thanks!
Click to expand...
Click to collapse
The AOSP 10 by phh, has a bug that I came about, that my computer couldn't detect my Armor 6 device. So unless you have a wireless app, you cant transfer files locally as of this version.
Pixel Experience has a bug, that you have to register your device as a custom rom with google. Otherwise the device can't download Google Play Store apps. I am currently running this version. I'm testing it more. I didn't test Havoc completely, but it doesn't come with Google Play Store.
Extosis said:
The AOSP 10 by phh, has a bug that I came about, that my computer couldn't detect my Armor 6 device. So unless you have a wireless app, you cant transfer files locally as of this version.
Pixel Experience has a bug, that you have to register your device as a custom rom with google. Otherwise the device can't download Google Play Store apps. I am currently running this version. I'm testing it more. I didn't test Havoc completely, but it doesn't come with Google Play Store.
Click to expand...
Click to collapse
oh, so I'm going to test Remix 9.0, I need USB working to test applications I develop.
Sent from my Armor_6 using Tapatalk
Unlocked the bootloader (After flashing to stock once) and flashed the following roms. Device is 6E:
PixelExperience
Resurrection Remix
UltraSuccRom
Bootloop on every one. All were ARM64, A bootable.
Interestingly, I couldn't get TWRP to boot/stick this time, either. Perhaps the official image is different? I have flashed to stock again and will go through the process of obtaining root. I will report back if flashing recovery with the TWRP app is successful.
[Update] TWRP installed through the TWRP app and can be booted through adb. I was able to successfully bypass DM-Verity. Attempting to boot into TWRP using key combinations apparently results in a system hang. I Will attempt flashing images with TWRP next.
[Update 2] No success with TWRP or Fastboot. Returning to stock...
does anyone have a link to dm verity to armor 6? thanks
Sent from my Armor_6 using Tapatalk
Pergmen said:
Unlocked the bootloader (After flashing to stock once) and flashed the following roms. Device is 6E:
PixelExperience
Resurrection Remix
UltraSuccRom
Bootloop on every one. All were ARM64, A bootable.
Interestingly, I couldn't get TWRP to boot/stick this time, either. Perhaps the official image is different? I have flashed to stock again and will go through the process of obtaining root. I will report back if flashing recovery with the TWRP app is successful.
[Update] TWRP installed through the TWRP app and can be booted through adb. I was able to successfully bypass DM-Verity. Attempting to boot into TWRP using key combinations apparently results in a system hang. I Will attempt flashing images with TWRP next.
[Update 2] No success with TWRP or Fastboot. Returning to stock...
Click to expand...
Click to collapse
My guide is for the Armor 6.
If I am not mistaken, I believe the Armor 6E has an A/B partition scheme. You can always check with the Treble Checker app on stock OS.
Extosis said:
My guide is for the Armor 6.
If I am not mistaken, I believe the Armor 6E has an A/B partition scheme. You can always check with the Treble Checker app on stock OS.
Click to expand...
Click to collapse
Unless it's wrong.
Pergmen said:
View attachment 4866669
Unless it's wrong.
Click to expand...
Click to collapse
Use A/B treble check gives A forsome reason but A ones dont work..
Pergmen said:
View attachment 4866669
Unless it's wrong.
Click to expand...
Click to collapse
Try, an GSI-A/B.
Let me know how it goes.
Extosis said:
My guide is for the Armor 6.
If I am not mistaken, I believe the Armor 6E has an A/B partition scheme. You can always check with the Treble Checker app on stock OS.
Click to expand...
Click to collapse
Extosis said:
Try, an GSI-A/B.
Let me know how it goes.
Click to expand...
Click to collapse
View attachment 4868641
Yep, Treble Checker was wrong. The Armor 6E is a/b. Thank you once again.
Pergmen said:
View attachment 4868641
Yep, Treble Checker was wrong. The Armor 6E is a/b. Thank you once again.
Click to expand...
Click to collapse
Nice! I'm so glad it worked!
Have you found any ROMs with working speakers? I haven't found any where the ringer or speaker is working.
Well, RRemix of this link was just the "bios screen", did I do something wrong?
I was able to install the latest Pixel Experience BETA and apparently it is working, I will test it in the next few days, USB is working normally.
update:
Not working NFC, Google Chrome, Rear Speaker, instagram and facebook videos lock the image and only play the audio.
SMAAALLL BR said:
Well, RRemix of this link was just the "bios screen", did I do something wrong?
I was able to install the latest Pixel Experience BETA and apparently it is working, I will test it in the next few days, USB is working normally.
Click to expand...
Click to collapse
Apparently the player is muted, I'm afraid of rebooting entrat in boot loop.
Has anyone tested the latest PixelXp and rooted?
---------- Post added at 02:08 PM ---------- Previous post was at 01:10 PM ----------
miklaw said:
Have you found any ROMs with working speakers? I haven't found any where the ringer or speaker is working.
Click to expand...
Click to collapse
I'm also without audio.
@Extosis, which system are you using?
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
Anyone tested the latest havoc 3.0?
updates:
-PixelExperience 10 ExpressLuke 28-10-2019:
fluid, a more stable, speaker does not work, nfc does not work, bluetoth works, headset works, insta / face videos only plays audio, some apps do not work, is the best I have tested;
-PixelExperience 10 ExpressLuke 16-10-2019:
unstable, not registered with play protect, speaker doesn't work, headset doesn't work, crashed and couldn't test anymore;
-Havoc 3.0 latest 10-11-2019;
fluid, less stable than pixel, no gapps, nfc apparently works, no speakers;
-RRemix phhuson gapps:
it's just the ulefone boot screen
-Evolution, Havoc2..9 and RRemix 7.0.3:
bootloop
I could not download any rom hosted on GitHub, very bad server, but I am going back to Stock while not updating update for PixelXP, I could not boot any rom from android 9 and all that flashed openGapps bootloop
edit:
If you are testing and finding solutions, please give feedback.
any android pie working well?
Are all Armor 6 devices without sound or only some? The 6E has sound on both AOSP and PixelExperience, if that information helps at all with figuring out the problem.
Observed issues with GSI images for 6E users (Tests ended November 9th):
-Spazzy GUI elements, specifically gifs and videos embedded in apps (It's pretty funny though)
-Extremely inaccurate battery charge reporting (Especially on PixelExperience, possibly unsafe)
-Cannot receive incoming calls (I'm on Verizon's network, which shouldn't be working to begin with, so your mileage may vary)
-Only boots once. Clearing the data partition is necessary to boot again.
-Screencasting (Doesn't work on stock either)
Observed working:
-Bluetooth audio
-Graphics processing unit
-Storage access on Windows over USB
-External Speaker and headphone output
-Camera and flash (Makes an audible click when closing on both GSI roms and stock. Strange.)
-All Play Store apps (That I tested)
-SMS, outgoing calls
The more information we have out there, the closer we get to... whatever we're trying to accomplish. Best of luck everybody.
Pergmen said:
Are all Armor 6 devices without sound or only some? The 6E has sound on both AOSP and PixelExperience, if that information helps at all with figuring out the problem.
Observed issues with GSI images for 6E users (Tests ended November 9th):
-Spazzy GUI elements, specifically gifs and videos embedded in apps (It's pretty funny though)
-Extremely inaccurate battery charge reporting (Especially on PixelExperience, possibly unsafe)
-Cannot receive incoming calls (I'm on Verizon's network, which shouldn't be working to begin with, so your mileage may vary)
-Only boots once. Clearing the data cache is necessary to boot again.
-Screencasting (Doesn't work on stock either)
Observed working:
-Bluetooth audio
-Graphics processing unit
-Storage access on Windows over USB
-External Speaker and headphone output
-Camera and flash (Makes an audible click when closing on both GSI roms and stock. Strange.)
-All Play Store apps (That I tested)
-SMS, outgoing calls
The more information we have out there, the closer we get to... whatever we're trying to accomplish. Best of luck everybody.
Click to expand...
Click to collapse
That actually helps guide me in the right direction, thanks!
Related
{
"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"
}
Supported devices
* US model running 7.1.1 b14 firmware.
First time install Instructions
Use these instructions when coming from any other ROM (stock, aokp, etc.)
Download ROM.
Download GAPPS if desired.
Boot into recovery.
Backup your current data.
Format/Wipe data.
Flash ROM.
Flash GAPPS if desired.
Reboot.
Upgrade instructions
Use these instructions when upgrading from a previous Lineage build.
Download ROM.
Boot into recovery.
Backup your current data.
Flash ROM.
Reboot.
Flashing instructions
There are two main ways to flash files onto your phone: local and sideload. Most people are only familiar with local, but sideload is much quicker and easier if you are at a PC.
Sideload
Download the ZIP file(s) to your PC. In TWRP, select advanced and then sideload. Swipe the slider to begin, then on your PC run "adb sideload <filename>".
Local
Download and/or copy the ZIP file(s) to your phone. Note whether they are on internal storage (the default) or the sdcard. In TWRP, select install, find your file, and select it.
Status
Current status: Stable
Known issues
None (hopefully).
Download
LineageOS Downloads - tulip
Tested with opengapps arm64 7.1 micro.
Sources
Device Tree
Kernel
Can this be flashed with current twrp?
Absolutely, that's what I did. Use sideload.
MrWhite0429 said:
Can this be flashed with current twrp?
Click to expand...
Click to collapse
Can't wait for those issues to be fixed so I can use it. Surprises me how fast you're working tdm
EEEEE I LOVE YOU
thank you so damn much tdm, i was scared this phone would be developmentally dead
Just installed and it works...pretty alright!
Bugs:
-Wi-Fi range seems to have shrunk ten-fold (LTE works perfectly fine, so it seems to be a problem with whatever Wi-Fi module(?) is being used with the ROM)
-Can't hear anyone on calls (What you already addressed)
That's all I've found so far. I was able to install SuperSU v2.79, which is super dope, and I've tested it with my good friend Titanium Backup to great results. Thanks a whole bunch for all the hard work, TDM!
P.S.: If you're dumb like me, and you're pretty new to all of this stuff, follow this guide that I sourced from the Open GApps FAQ to install the ROM:
A 'Clean' install consists of the following:
Factory Reset (or manually wipe (format) Data partition - Internal Storage wipe is NOT necessary)
Manually wipe (format) your System partition <-Unnecessary
Flash your ROM
Flash GApps package <-Use opengapps arm64 7.1 micro
Flash SuperSU v2.79 <-Use the arm64 version of SU found on the LineageOS website
Wipe the Dalvik & cache <-Unnecessary
Reboot (Because of the SuperSu install, there may be a bootloop or two. It also warned me before I rebooted that I didn't have an OS installed, even though I did.)
NOTE: YOU WILL LOSE ALL OF YOUR DATA AND APPLICATION SETTINGS using this method. Be sure to do a NANDroid backup prior in case you want to restore later.
Click to expand...
Click to collapse
Glad someone else got it to work, and thanks for the instructions. Note formatting /system is not necessary, neither is wiping cache or dalvik.
If you want su, lineage has a flashable root package. Check on their site. SuperSU may work but it's not supported in any way.
I'll check the WiFi stuff, I probably missed a config or calibration file or something.
The in-call audio is probably an issue in the amplifier code. I just got that working yesterday, so no surprise there. Fix should be relatively easy.
mattx1002 said:
Just installed and it works...pretty alright!
Bugs:
-Wi-Fi range seems to have shrunk ten-fold (LTE works perfectly fine, so it seems to be a problem with whatever Wi-Fi module(?) is being used with the ROM)
-Can't hear anyone on calls (What you already addressed)
That's all I've found so far. I was able to install SuperSU v2.79, which is super dope, and I've tested it with my good friend Titanium Backup to great results. Thanks a whole bunch for all the hard work, TDM!
P.S.: If you're dumb like me, and you're pretty new to all of this stuff, follow this guide that I sourced from the Open GApps FAQ to install the ROM:
Click to expand...
Click to collapse
I need a log from stock and I don't really want to flash back and forth. Can someone do me a favor and get a log of a phone call using stock 7.1.1? Just run eg. "adb logcat >call.log" and then make a call, establish voice communication, hang up, and hit ^C.
Thanks!
tdm said:
I need a log from stock and I don't really want to flash back and forth. Can someone do me a favor and get a log of a phone call using stock 7.1.1? Just run eg. "adb logcat >call.log" and then make a call, establish voice communication, hang up, and hit ^C.
Thanks!
Click to expand...
Click to collapse
Sent private message to you. That logfile was made right? (stock 1.2.0B09 7.1.1 tulip locked)
mattx1002 said:
LTE works perfectly fine
Click to expand...
Click to collapse
I know this is off topic, what carrier do you have? I think my carrier didn't activate LTE for me at all.
Thanks I got it. I used the amp parameters from your log but still can't get in-call audio. Need to keep looking....
maestromony said:
Sent private message to you. That logfile was made right? (stock 1.2.0B09 7.1.1 tulip locked)
Click to expand...
Click to collapse
Vixenko said:
I know this is off topic, what carrier do you have? I think my carrier didn't activate LTE for me at all.
Click to expand...
Click to collapse
I'm on T-Mobile.
I'm on AT&T. LTE works for me.
Vixenko said:
I know this is off topic, what carrier do you have? I think my carrier didn't activate LTE for me at all.
Click to expand...
Click to collapse
Okay been working away on this. Got the WiFi MAC and the notification light working. Still haven't figured out call audio, which is the biggest show stopper right now.
Got a question though....
As far as I can tell, the notification light hardware only seems to support a single color at a time (red, green, blue). They can't be mixed to provide eg. yellow or orange. So, it can't do the typical yellow for the "medium battery" color. What do you people prefer for that? What does stock show?
Thanks for your work again.
Stock:
Constant green when its fully charged (and blue blinking when notification arrived).
Constant blue when its charging.
Red Blinking when level is below 15%
In my opinion you can leave it like that.
tdm said:
Okay been working away on this. Got the WiFi MAC and the notification light working. Still haven't figured out call audio, which is the biggest show stopper right now.
Got a question though....
As far as I can tell, the notification light hardware only seems to support a single color at a time (red, green, blue). They can't be mixed to provide eg. yellow or orange. So, it can't do the typical yellow for the "medium battery" color. What do you people prefer for that? What does stock show?
Click to expand...
Click to collapse
mekzmaz323 said:
Thanks for your work again.
Stock:
Constant green when its fully charged (and blue blinking when notification arrived).
Constant blue when its charging.
Red Blinking when level is below 15%
In my opinion you can leave it like that.
Click to expand...
Click to collapse
I agree. I'm fine with it being the same.
WiFi and lte
My WiFi is very bad and unstable. Also I never have more than 1 bar of LTE signal. And when I make a call others can't here me and I can't here them.. Those are my only problems.
Version: B14
Thanks @tdm for all your work!
tdm said:
Here at long last, Lineage 14.1 for the Axon 7 Mini!
... I'll fill this post out more later ...
Current status: Alpha
Currently supported devices:
US variant (tulip) running 7.1.1 b14 firmware.
Known major issues:
Phone audio doesn't seem to work.
Bluetooth audio stutters incessantly, unusable.
Notification LED doesn't work.
Cannot seem to get NFC to work.
Known minor issues:
WiFi mac addr isn't set properly.
WiFi connection seems a bit flaky. (?)
Download:
lineage-14.1-20171019-UNOFFICIAL-tulip.zip
MD5=5b4ca59d5b9f69e59dc44ba28637b71a
Tested with opengapps arm64 7.1 micro.
Sources:
device_zte_tulip
kernel_zte_msm8952
Click to expand...
Click to collapse
These are known issues except for LTE. My LTE works fine and I have reports that others do also.
CRAFTER0302002 said:
My WiFi is very bad and unstable. Also I never have more than 1 bar of LTE signal. And when I make a call others can't here me and I can't here them.. Those are my only problems.
Version: B14
Thanks @tdm for all your work!
Click to expand...
Click to collapse
Today's build is up, with handset audio working!
I think the volume adjustments may need work, but I do hear audio.
I'm off work tomorrow so I may stay up tonight and give this a try! In anyone's opinion is this stable or suitable for daily use?
{
"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"
}
Resurrection Remix P
Code:
[SIZE="4"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/SIZE]
Resurrection Remix the ROM has been based on LineageOS, SlimRoms, Omni and original Remix ROM builds, this creates an awesome
combination of performance, customization, power and the most new features, brought directly to your Device.
Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy!
Special thanks to the LineageOS team, Omni team, SlimRoms and of course to all the supporters.
Make sure you have the latest TWRP.img
Download the latest RR-P zip and GApps zip (opengapps nano or smaller)
fastboot boot twrp.img (NEW!! See post #2 for info on installing TWRP)
If coming from stock for the first time, flash copy-partitions-AB.zip from second post (It takes a backup of active slot to inactive slot)
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (Note: this will wipe internal storage)
Flash latest RR-P.zip
Reboot and let the ROM boot once (it is necessary to reboot between ROM flash and GApps/Addon flash due to slot-swap logic)
Reboot back to bootloader and fastboot boot twrp.img again
In TWRP, choose -> Wipe -> Format data and type "yes" at the prompt (You may be able to get away with just doing a factory reset at this point, but that's on you to try)
Flash Google Apps package (optional)
Flash Magisk (also optional) (Note: If Magisk doesn't stick after setting up your device, fastboot boot twrp.img one last time and flash it again, no need to wipe anything)
First boot may take up to 10 minutes.
ROM Download
GApps
Resurrection Remix Source
Device Source
Kernel Source
Vendor Source
XDA Developers
LineageOs Team
Omni Team
And Of Course To All The Supporters, Donators And Users
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you, Team Resurrection Remix and me quite some time.
Download the MatLog app from the Play Store.
After downloading the MatLog app, go to the app settings, and change the log level to Debug.
Clear all previous logs and take the exact steps to produce the error you are receiving. As soon as you receive the error (probably a force close), go straight into MatLog and stop the log recording.
Copy and paste the entire log either to Hastebin or Pastebin
Save the log, and copy and paste the link into the thread with a brief description of the error.
XDA:DevDB Information
Resurrection Remix Pie v7.0.2, ROM for the Moto G6 Plus
Contributors
Jleeblanch, erfanoabdi, rahulsnair, RR Team
Source Code: https://github.com/ResurrectionRemix
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2019-02-25
Created 2019-02-26
Last Updated 2019-04-21
Copy partitions zip & TWRP installation info
[size=+2]Important info, please read...[/size]
Starting from build 20190414, encryption is disabled (temporarily) and you must clean flash
The new TWRP version now supports decryption on Pie when booting twrp. However, I have updated TWRP to include the new magisk repacktools which allows users to download and install one twrp.img without the need of an installer zip. The reason behind releasing the ROM with encryption disabled? If you were to try to install TWRP while using an encrypted ROM, you would end up in a bootloop that would bring you back to TWRP. But, install TWRP on a ROM with encryption disabled, and everything works as expected.
[size=+1]TWRP Installation[/size]
-> TWRP download || twrp-3.3.0-v2-evert-jlb.img
->>> The twrp.img you download above will also be the same twrp.img you will install, so make sure to put a copy on your device as well
-> Boot twrp
Code:
fastboot boot twrp-3.3.0-v2-evert-jlb.img
-> In TWRP, choose Advanced / Install Recovery Ramdisk
-> Select the twrp-3.3.0-v2-evert-jlb.img
->>> At this point twrp will automagically unpack your boot.img and the twrp.img, swap out the recovery-ramdisk, and repack your boot.img. When this process completes, twrp will be permanently installed.
->>> Always flash Magisk AFTER you've installed twrp
-> Reboot and enjoy. You should now be able to reboot to recovery from the Power Menu!!
DO NOT try to install twrp on an encrypted rom. You will most likely end up in a bootloop, you have been warned!
Important
To keep TWRP installed between ROM updates, there is a Magisk Module named "TWRP A/B Retention Script" by @osm0sis. Search for it within Magisk Manager Downloads section. You'll want to flash this script zip after each OTA has installed, but before you install Magisk to the Inactive Slot from Manager.
[size=+1]Coming from stock?[/size]
Make sure to flash the copy-partitions-AB.zip in twrp before you do anything else. You can download it from the attachment below...
Reserved
Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.
Woks awesome, thank you dev
Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.
WYPIERDAALAAC said:
Cool, i will test it now (im glad its official).
Ps dont do it "Perform a FULL factory wipe and wipe/system and dalvik cache as a precaution"
i meant wiping system.. even if we install custom rom after this it will be no os installed as twrp says.
Click to expand...
Click to collapse
The install instructions in the OP are generic, and don't necessarily apply for this device. You're better off following the install instructions from Lineage-16.0. I will update the OP with proper install instructions when I have some time asap.
LDMx96 said:
Excellent ROM.
Always loved RR ROMs.
Only downside I have is wondering if there will be anyway to get Google Pay working, as unfortunately it doesn't on this ROM.
Also, how can I disable the one button navigation style, as when I have a NAV bar on, I still have functions on my one button.
TIA.
Click to expand...
Click to collapse
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.
Jleeblanch said:
For now, if you've flashed Magisk, you can flash my Magisk module (or any module) that will help pass safetynet and show device as being certified in Play Store. This is why Google Pay doesn't work.
I had updated some blobs and build fingerprint to match the stock Pie update, but it seems to be causing the device to fail safetynet. I will have this fixed in the next update.
As for the fingerprint gestures always being enabled. I'm looking into this too. I'm assuming this has something to do with an overlay I added to insure the navbar was enabled on first boot (as without it, it's not). I hope to have this fixed for the next update as well.
Click to expand...
Click to collapse
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.
Awesome! I'm using magisk with Ainur Sauron and Viper, working flawlessly! Everything works pretty well so far. Thanks for the amazing job!
I flashed it over the stock pie without wiping system, only factory reset. I don't know if this helps because I'm still a newbie P, just sharing!
RR rocks!
LDMx96 said:
No problem, I won't flash Magisk if you're looking at getting it fixed I will just hang fire, it's not a much needed thing anyway, as Google Pay isn't a much needed thing for me, was just handy.
As for the Fingerpring Gestures that's fine, it's not harmful, I just thought I'd mention it.
I'm loving it so far, not had any problems all good.
Click to expand...
Click to collapse
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.
Jleeblanch said:
I will fix it, yes. It seems I got it right on Beckham, but not so much on Evert lol. Anyway, I'll have an update ready for the weekend. I don't use Google Pay much myself either, although as you said, it is handy. I'd prefer things worked out of the box rather than needing workarounds to fix things.
Click to expand...
Click to collapse
No worries mate, I'll look forward to the update on the weekend then.
Thanks a bunch.
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.
asesinodilusion said:
Excellent rom, I like it all of them, but it seems that it's only me who have trouble in calls, I can't hear nothing when I use headphones, it only works without headphones.
Pd. Sorry for my English
Click to expand...
Click to collapse
LDMx96 said:
I've just tested this too, no call volume when earphones are connected, but fine once disconnected.
Click to expand...
Click to collapse
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
There is a manual or some guide to do that? Please
asesinodilusion said:
There is a manual or some guide to do that? Please
Click to expand...
Click to collapse
There are basic instructions in the OP to take logs on the device using Matlog. There is also a decent tutorial here on xda: [Tutorial] How To Logcat
Jleeblanch said:
Someone mentioned this on telegram as well. If this is the only bug anyone has encountered, that's kinda awesome [emoji6].
However, as I don't have a pair of headphones to test with and possibly reproduce the issue, can one of you (or both) please get a log? I just need someone to reproduce the issue while taking a logcat and attach it here so I can diagnose and fix the issue.
Click to expand...
Click to collapse
https://www.dropbox.com/s/rqz2t7d57epq7i9/data.txt?dl=0
I hope this help
BT Calling not working
Hello together,
i installed th RR Rom on my phone and everything seems to be fine.
BUT the only thing is, "Bluetooth Calling" does not work. I tried it with to different Bluetooth devices, my oneplus wireless bullets, and my car.
No Microphone and no Sound is Working, very rare.
But when i do BT Calling with SIGNAL or VOIP app CSipSimple everthing is fine. It looks like, that the only problem is the telefone app itself from android pie.
Before i used the [ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus] and BT Calling was working fine!
Does someone have a tip for me, where i can take a look?
Thanks a lot.
Greetings
It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk
titofariasl said:
It works very well, except for the detail that sometimes there is lag and when making or receiving a call there is too much noise
Enviado desde mi Moto G6 Plus mediante Tapatalk
Click to expand...
Click to collapse
Is there any way of improving in-call audio quality? There is just too much background noise.
[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster
KUGO F5321
Hi! Just wanna share with you Android 11 ROM builded for Sony Xperia X Compact
Many Thanks for development @Cubbins
I'm not responsible for any damage caused with your device after flashing this ROM. Flash only on your own risk.
This ROM bring us Treble support ( ARM64 A/B ) structure for all GSI images based on 11 Android. Just flash any GSI at System partition after it.
How to Install:
1) Copy ROM to SD card and flash with recovery
2) Download SW_BINARIES_FOR_XPERIA_ANDROID_9.0_2.3.2_V9_LOIRE.ZIP, unzip and copy image to sdcard too
3) Flash Binaries with recovery to OEM/ODM partition
4) reboot
5) After reboot we need to flash/format userdata partition. So, download it and flash with ADB: fastboot flash userdata userdata.img or fastboot erase userdata
6) reboot.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop.
Features:
Working:
- Wi-Fi
- Bluetooth
- Fingerprint
- Sensors
- Camera
- Calling
- Music Playing
- GPS
Not Working:
You tell me
Sources:
build ROM sources:
github.com/ExplosiveLobster
kernel sources:
github.com/ExplosiveLobster/kernel_sony_msm-4.9
bug reports:
github.com/ExplosiveLobster/bug_tracker/issues
Screenshots:
{
"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"
}
Download:
Google Drive
Explosive Lobster - Google Drive
drive.google.com
Mega
3.11 GB folder on MEGA
12 files and 3 subfolders
mega.nz
So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.
mhemart said:
So good to see some people still working on this device. I'm considering leaving the official rom to this one as soon as GPS is operational. Thank you very much.
Click to expand...
Click to collapse
GPS Working fine with latest build, so you can try it right now
lubik1 said:
GPS Working fine with latest build, so you can try it right now
Click to expand...
Click to collapse
Really good, I have to backup my data and I'll give a try tonight. Thanks !
[QUOTE = "lubik1, post: 84244519, member: 5897890"]
Which vendor should I use?
mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
F5321 is for X compact.
mister-13x said:
Which vendor should I use?
Click to expand...
Click to collapse
SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.img
The one vendor binaries for both devices - suzu and kugo
Are the Flame Gapps in your Google Drive the Gapps you recommend, or can we just use OpenGapps as usual? This is my first experience with Android 11.
Edit1: Installation worked like a charm with your description. For me, there was no change after flashing userdata.img. The phone behaved the same way, whether I flashed userdata.img or I did not. What did NOT work was just to delete userdata - then my phone would show an error message after boot and just shut down again.
After every boot, I receive the error message “There’s an internal problem with your device Contact your manufacturer for details”. According to Google, this has something to do with Treble. I will install my apps now and get the tests going. Thank you SO much for this. If you leave your PayPal here somewhere, I will send you some small bucks that I can afford for the good development.
Spaceoid said:
Are the Flame Gapps in your Google Drive the Gapps you recommend
Click to expand...
Click to collapse
You can flash any Gapps you want, but this gapps was tested with EL ROM and work fine.
Spaceoid said:
Thank you SO much for this. If you leave your PayPal here somewhere
Click to expand...
Click to collapse
It's allways on my profile, on section "about"
Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
I just send you two coffees via PayPal for the good work. I know it is not much, sadly I am a student with little income... But I hope it keeps you energized for further improvements to the ROM!
After half a day of testing the pure ROM, without any apps and just Gapps, here is what I found so far:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general. Only a reboot fixes this.
- Regarding the error message mentioned in my last post, I found this:
How to Fix Android system There's an internal problem with your device
How to Fix Android system error "There's an internal problem with your device Contact your manufacturer for details" and How to remove NFC Service 'NFC keeps stopping'.
www.recovery-mode.com
I cannot say how reliable/safe this procedure is, though.
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
(- one minor thing - the alarm clock does work well, but it does only sound the alarm and not wake up the screen. So, before disabling the alarm, one has to unlock the screen first.)
Will start installing my apps now and keep on further testing.
mhemart said:
Hello. I had no time to perform an install yet but I have a question (maybe stupid ?). I noticed the binaries were for Android 9 but I saw that there was a newer version called SW_binaries_for_Xperia_Android_10.0.7.1_r1_v7a_loire (no more binaries for android 11). Do you think it could be used with your ROM ? Maybe it would prevent the message that Spaceoid see at every boot ?
Just in case, here is the link to the newest version : https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
Click to expand...
Click to collapse
I was about to ask the same. Are the 10 binaries not compatible?
@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.
@lubik1
This is being trebled? SELinux is permissive? If that's the case, I imagine the cache.img and boot.img can be used to GSI other OS'.
Warning:
We use /cache partition at thid ROM as a /vendor, so if you format /cache partition on recovery - you'll catch a bootloop. [QUOTE/]
Click to expand...
Click to collapse
&(*) said:
@betacrypt
Binaries for 10 are available however the kernel development was abadoned. Kernel 4.14 did not mature into an operational state. Kernel 4.9 is the current stable version, using the 9 binaries are the most recent option at the moment.
Click to expand...
Click to collapse
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks @lubik1 for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.
betacrypt said:
Ah that makes sense. Somehow I thought 4.14 was stable.
Also thanks for your efforts to create this! Glad to see continued support for the XC - was worried we'd lost support for it. I own two and had been hoping to see an update.
Click to expand...
Click to collapse
Don't forget to thank @Cubbins too for the build.
@lubik1 ,
Can you also provide a GSI variant (of boot.img and cache.img) for those of us who like to use other systems?
Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.
betacrypt said:
Anything different to do when rooting with Magisk? I flashed the latest Magisk in TWRP successfully but when I boot into system the Magisk App says no root.
Click to expand...
Click to collapse
Strange. I did the same this morning, downloaded latest Magisk version from Github, and it worked for me. I already used root for Titanium Backup. I used v21.2.
On another note, after one day of usage, I'd already consider this ROM quite stable. The wifi problem really is the main problem, as I only can connect to my home wifi in 20% of the day. I already lost all my mobile data because of that, now I am surfing in less than 2G speed on my phone xD
Spaceoid said:
- Wifi is working, but, at least for me, after like 30 minutes after every boot, it seems to break. After that, I am not able to reconnect to my home wifi network, or to find any Wifi networks in general.
Click to expand...
Click to collapse
We'll switch to another wi-fi driver on next build.
Spaceoid said:
- Regarding the error message mentioned in my last post, I found this:
Click to expand...
Click to collapse
Will be Fixed on next build
Spaceoid said:
- Connected to this, the NFC tile in the pulldown menu (from the status bar) does not work. I can activate NFC via the settings, though; I did not try yet if it really works, but at least it can be activated.
Click to expand...
Click to collapse
Will be added on next build
Spaceoid said:
- After every reboot, the phone forgets the time and date until it is connected to cellular network or wifi for the first time.
Click to expand...
Click to collapse
Missing rtc-service, will be added on next build
Hi all,
i was kinda bored and sick of no Custom ROM development for our beloved S6 so i thought i'd try using a GSI and i've got it booting so i thought i would share the instructions!
As usual all care no responsibility! Nothing here is without risk.
Android 13
5 March 2023 Security Patch Level
1. Unlock your bootloader. (Very easy to do - https://www.hardreset.info/devices/...-s6/faq/bootloader-unlock/samsung-bootloader/)
2. Download the official vbmeta image provided by TWRP > https://dl.twrp.me/gts4lv/vbmeta.tar.html
3. Download TWRP https://twrp.me/samsung/samsunggalaxytabs6qcomwifi.html
4. Open Odin
5. Put VBMETA.TAR in the CP Slot & TWRP in AP slot and flash. On reboot hold down the Pwr/Up button so it boots straight into TWRP or sometimes it can be overwritten.
3. Format Data, reboot back into TWRP and Full Factory Reset . (Take a backup if you need one).
4. Transfer the LoS image file to the tablet via TWRP then Flash the LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
(might need to use the adb push command to copy the file across) adb push filename.extension /sdcard
5. Flash magisk if you like.
6. Reboot to system and enjoy!
i used the one above which includes GAPPS though there are ones that don't if you prefer
I only just finished installing though - quick summary:
Working:
Fingerprint!
Hardware Buttons
SDCard
Wifi
Bluetooth
Gapps and Google Setup
Tablet is very fast!
Charging
USB File Transfer
Audio
Video out for USB-C
Auto-rotate
GPS
Official Samsung Keyboard Physically attached working fine too!
Themes
Colours
Mic
SPen
Not Working:
Only bottom speakers work
SafetyNet
Workarounds:
To pass SafetyNet (BASIC):
Flash Magisk in TWRP
Use Magiskhide
Turn on Zygist
Install Displax modified SafetyNet-Fix from link below;
hxxps://github.com/Displax/safetynet-fix/releases/tag/v2.4.0-MOD_1.2
Configure your Denylist in Magisk for Google Play Store and Services apps. (And anything else you need to not detect root).
To Fix Brightness:
Go to Settings - Phh - Misc Features - Tick the box for "Use Linear Brightness Slider"
To Help with Fingerprint:
Turn off taskbar in Settings to help alignment with Fingerprint scanner
Hope we can get some community effort behind this so we can bring this tablet back into support since Samsung gave up on it..
Credit to @AndyYan for the builds!
[GSI][13] LineageOS 20 TrebleDroid-based
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
RESERVED
In my case only bottom speakers work!
Sage said:
Hi all,
i was kinda bored and sick of no Custom ROM development for our beloved S6 so i thought i'd try using a GSI and i've got it booting so i thought i would share the instructions!
5.Install LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
Click to expand...
Click to collapse
Thanks so much for this!
I have built LOS for a couple unsupported devices in the past and would love to dedicate as much time and resources as needed to this project.
Could you share which build trees were used from Github and the extracted blobs?
I would like to replicate this build and put in a request with LOS developer stinX for an official one.
tablet_seeker said:
Thanks so much for this!
I have built LOS for a couple unsupported devices in the past and would love to dedicate as much time and resources as needed to this project.
Could you share which build trees were used from Github and the extracted blobs?
I would like to replicate this build and put in a request with LOS developer stinX for an official one.
Click to expand...
Click to collapse
I am not sure mate about the GIT and Blobs. These are GSI so "generic" so they may not have them. From my understanding they work with the existing Vendor image and take advantage of Treble to ensure everything works.
The source of the files is here:
[GSI][13] LineageOS 20 TrebleDroid-based
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project with extra...
forum.xda-developers.com
m0byn said:
In my case only bottom speakers work!
Click to expand...
Click to collapse
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.
Sage said:
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.
Click to expand...
Click to collapse
I should add i think this is MUCH faster than stock and battery life is looking great too!
I am happy there are some other people who are using this GSI on a Tab S6. I installed it some time ago and am very satisfied!
Some things I found:
Fingerprint XY coordinates are somehow off. Specifically, the symbol showing on screen and the actual reader are not on the same place. I think it is related to the app bar somehow, since it seems to be off by that. I think this could be fixed by an overlay.
Auto-brightntess is not available as well. Either use an app for that, or don´t use it. This can also be fixed by an overlay as far as I know.
Maybe it is also possible to get the top speakers working by making an overlay? I am not sure regarding this, however.
Obviously, DolbyAtmos is not included. However, I think there exists a Magisk Module. Maybe it would also be possible to integrate this into an overlay? This would be amazing
I am very new to the custom ROM/GSI scene. So, my experience with overlays and so on is basically none. However, I would try to contribute as good as I can if someone feels ready to create an overlay and then getting it implemented into the GSI.
Anyone interested in cooperating?
Sage said:
There are quite a lot of tweaks available in the PHH settings. I suggest you play around in there and you may get both sets of speakers working. I will do the same
I have added it to "Not Working" section.
Click to expand...
Click to collapse
I will try to do that as well...lets see.
I would explicitly add to the working section that the spen works and also pressure sensitivity of the spen works! At least in the Saber Handwritten Notes app which I use. This is amazing.
Sage said:
1. Unlock your bootloader. (Very easy to do - https://www.hardreset.info/devices/...-s6/faq/bootloader-unlock/samsung-bootloader/)
2. Install TWRP via Odin https://twrp.me/samsung/samsunggalaxytabs6qcomwifi.html
3. Full wipe thru TWRP. Including format data. (Take a backup if you need one).
4. Reboot back to TWRP.
5.Install LoS image through TWRP (System Partition) lineage-20.0-20230324-UNOFFICIAL-arm64_bgN.img (or whichever ARM64 flavour you like) from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-20-td/
6. Boot and enjoy!
Click to expand...
Click to collapse
Didn`t you patch the vbmeta.img, or did you flash the multidisabler zip?
Somehow, one has to disable verified boot such that you can even boot LineageOS...as far as I know!
m0byn said:
Didn`t you patch the vbmeta.img, or did you flash the multidisabler zip?
Somehow, one has to disable verified boot such that you can even boot LineageOS...as far as I know!
Click to expand...
Click to collapse
All I did was what I posted above! I'm surprised how easy it was tbh!
Sage said:
All I did was what I posted above! I'm surprised how easy it was tbh!
Click to expand...
Click to collapse
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...
m0byn said:
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...
Click to expand...
Click to collapse
Nope. Started from stock. Literally unlocked bootloader right before moving to GSI. Just like the steps above.
I did install Magisk which may help disable verified boot though
Sage said:
Nope. Started from stock. Literally unlocked bootloader right before moving to GSI. Just like the steps above.
I did install Magisk which may help disable verified boot though
Click to expand...
Click to collapse
Ah, that might make the difference! So I think it is worth to mention to either install Magisk, or to patch the vbmeta.img in order to boot. If coming from stock with the stock vbmeta.img, then Android Verified Boot will not allow booting into a different ROM.
m0byn said:
Did you start from stock rom? Maybe you already flashed a vbmeta.img or multidisabler.zip some time ago which is still in effect?
I really doubt that it is possible to boot a different os if verified boot of Android is not adjusted...
Click to expand...
Click to collapse
OP is wrong.
Be careful flashing the latest TWRP for SMT-860 Wifi with Odin.
This happened to me today after doing it. "Error verifying vmbeta image: Invalid vmbeta header"
{
"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"
}
The device gets stuck like this and won't boot anymore, but you can get it back to normal by flashing the recovery.img from your firmware files (It's in AP)
You cannot install TWRP on the Galaxy Tab S6 without fixing the vmbeta.img issue.
I tried with the latest Samsung firmware downloaded via SamFirm and an older one.
@m0byn: Do you know what needs to be done with the vmbeta.img on this device, to allow for TWRP to be flashed?
I have found many different prescribed solutions such as patching boot.img with Magisk or just the vmbeta.img , but nothing seems to work.
Tablet, search my post here https://forum.xda-developers.com/t/t865-rooting-with-android-12-bootloop-and-error.4452641/ and try
Hey man, thank you for the suggestion. That post seems to be about Magisk and rooting.
The problem here is the vmbeta.img.
According to older posts from 2021 this can be resolved by flashing vbmeta_disabled.tar , but the latest 2022 version of TWRP should no longer require this. It's weird.
I am sorry. I thought something went wrong when you patched the firmware with Magisk
Probably flashing Magisk automatically patches the vbmeta.img. Not sure though.
Follow the steps below. This is how I did it. It worked.
I am assuming a stock recovery in this process. If you already installed TWRP just try if it works as well. not sure if this is impacting the process.
Unpack firmware using 7Zip tool
Unpack AP.tar.md5 using 7Zip tool
Unpack vbmeta.img.lz4 using 7Zip-ZS tool
Open file in FrhedPortable (HEX editor) to patch it
Go to offset (block) 123 and write 03 and save
Compress vbmeta.img to vbmeta.img.tar using 7Zip tool
Connect device via USB to computer
Hold volume up & volume down buttons
Press volume up button to proceed to download mode
Open Odin -> verify whether device number is added
Untoggle "auto-reboot" in options
Select AP section
Choose patched vbmeta.img.tar file
Click start to flash
When flashing process is done: hold power & volume down button to exit and power off device
IMPORTANT: as soon as device shuts off immediately release volume down button and press volume up button to enter recovery mode
Click factory reset
Click reboot to bootloader
Thanks @m0byn I managed to figure it out with your help.
For anyone else facing the same problem, here is what you need to do:
Download the official vbmeta image provided by TWRP > https://dl.twrp.me/gts4lv/vbmeta.tar.html
Proceed to flash with Odin.
Put the TWRP recovery image in AP and vbmeta.tar in the CP slot.
After this you can boot into the TWRP recovery normally, but for some reason any changed settings in TWRP are not saved. So everytime I reboot into TWRP recovery all previously selected TWRP settings are lost. I wonder if that's normal, but everything else seems to work.
Next step will be flashing the Lineage GSI, i'll keep you guys posted.
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various proprietary hardware-specific code.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Information
This ROM uses source built kernel, kernel modules, and vendor image.
This ROM bundles the latest firmware so you don't have to worry about updating firmware.
To use the eSIM you need to have GApps
Instructions
Follow https://wiki.lineageos.org/devices/lynx/install for how to install
Downloads
Official Builds
Optional GApps: MindTheGapps
Reporting Bugs
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/*
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.
Known Issues
Face Unlock, because Google doesn't provide an AOSP option.
Contributors
mikeioannina
nicknitewolf
The LineageOS team
Source Code: https://github.com/LineageOS
Great
Great. Thanks. Just got my Pixel 7a today.
I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.
sumdewd01 said:
I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.
Click to expand...
Click to collapse
Does the Play Store icon exist?
The GApps package may just install Play Services and the Play Store, from which you can install all optional Google apps.
Such packages avoid installing these apps as system apps, since you wouldn't be able to uninstall them without root.
sumdewd01 said:
I gave it a shot and the rom itself works fine, but nothing I did would let Mindthegapps install. Do you have any suggestions? I am following the install steps exactly to reboot to recovery while still in recovery to sideload prior to ever starting the ROM. It says it installs fine but no icons ever show up for the Google apps.
Click to expand...
Click to collapse
You have to reboot to recovery again for it to install on the correct slot
Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install
Optimissimus99 said:
Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install
Click to expand...
Click to collapse
Hmm I guess the issue is with the partition system on our Pixel 7A so has nothing to do with the A/B partitions but the Pixel 7A uses special partitions for Boot and recovery etc, so I guess that the gapps packages can not detect/handle those partitions and therfor it does not work.
I recognized that when I wanted to flash Magisk, it shows as successfull but was not installed.
So I had to patch the init_boot file and flash that to the init_boot partition so I assume something like that applies for Gapps as well!
This was the issue I had. I tried multiple times and combinations to reflash and reboot, and reboot to recovery while in recovery and I eventually gave up and went back to stock. No Google icons of any sort and it would always say it installed fine.
Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?
treblechet said:
Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?
Click to expand...
Click to collapse
You can install Aurora Store and login there with your Google account.
treblechet said:
Ok, glad to see I'm not the only one having problems flashing GApps. Does anyone know of a method of getting just the play store functioning outside of flashing from recovery?
Click to expand...
Click to collapse
sumdewd01 said:
This was the issue I had. I tried multiple times and combinations to reflash and reboot, and reboot to recovery while in recovery and I eventually gave up and went back to stock. No Google icons of any sort and it would always say it installed fine.
Click to expand...
Click to collapse
Wishmasterflo said:
Hmm I guess the issue is with the partition system on our Pixel 7A so has nothing to do with the A/B partitions but the Pixel 7A uses special partitions for Boot and recovery etc, so I guess that the gapps packages can not detect/handle those partitions and therfor it does not work.
I recognized that when I wanted to flash Magisk, it shows as successfull but was not installed.
So I had to patch the init_boot file and flash that to the init_boot partition so I assume something like that applies for Gapps as well!
Click to expand...
Click to collapse
Optimissimus99 said:
Thank you very much for this ROM.
I will test it and see if it is stable. I hope we will have official lineageOS Builds soon.
Edit: GApps don't work for me either. I'm new to A/B devices (coming from Poco F1), so maybe it's a layer 8 error
I have flashed Lineage, than rebooted to recovery, flashed Gapps+magisk (did not throw any errors, log seemed fine).
No sign of Gapps being installed. So I did it again
Active Partition:A Flashed L+G+M, reboot
now active Partition:B Flashed L+G+M, reboot
now active Partition:A Flashed G+M, reboot
now active Partition:A Factory reset.
Now booted the phone, still no Gapps. However if I understand A/B Partitioning correctly, both Partitions should now contain Lineage, Gapps and Magisk.
What am I doing wrong? The recovery logs don't show any issues, all partitions get mounted, and it seems like the Gapps installer runs without problems.
Edit2: Just tried it again with todays build (from mega) - still the same issue. Gapps just don't install
Click to expand...
Click to collapse
Pulled old builds and uploaded new ones. Something went wrong with my build configuration which prevented gapps install. Please use the new pre-install steps and images too
Great work @nicknitewolf .. can i wonder what are the main things needed to clear the road for official LineageOS status? Is it that you're not really in the LineageOS community and expect @mikeioannina (who has official builds for most of the Pixel devices) to eventually do it? Or is it that there's specific issues or things that don't conform well. Either way, maybe mike has any idea if the 7a will get official support any time soon..
I will put this on a family member's new Pixel 7a, and maybe leave some feedback, but i still prefer official
mxz55 said:
Great work @nicknitewolf .. can i wonder what are the main things needed to clear the road for official LineageOS status? Is it that you're not really in the LineageOS community and expect @mikeioannina (who has official builds for most of the Pixel devices) to eventually do it? Or is it that there's specific issues or things that don't conform well. Either way, maybe mike has any idea if the 7a will get official support any time soon..
I will put this on a family member's new Pixel 7a, and maybe leave some feedback, but i still prefer official
Click to expand...
Click to collapse
No promises but we are waiting for June ASB
nicknitewolf said:
Pulled old builds and uploaded new ones. Something went wrong with my build configuration which prevented gapps install. Please use the new pre-install steps and images too
Click to expand...
Click to collapse
This fixed it, thanks. I would like to mention that there are sone UI inconsistencies when it comes to the status bar, there's padding on one side and not the other, and when you go into the notification drawer (I think that's what it's called, swiping down from the status bar) the time and the date are not aligned by a little bit vertically. It's a small problem but still somewhat noticeable.
nicknitewolf said:
No promises but we are waiting for June ASB
Click to expand...
Click to collapse
Ok, cool.. are you working together with people from the LineageOS team?
Also, since i never tried this before with any device - would it require a wipe with clean install to upgrade to official should the time come? Or it's likely to be compatible?
mxz55 said:
Ok, cool.. are you working together with people from the LineageOS team?
Also, since i never tried this before with any device - would it require a wipe with clean install to upgrade to official should the time come? Or it's likely to be compatible?
Click to expand...
Click to collapse
Yes and yes. I am already part of the LineageOS team... Current builds are signed with test keys but official builds are signed with separate keys, hence a full wipe is required. You could try the zip attached but I doubt it works (since I don't really wanna test it).
nicknitewolf said:
Reboot into fastboot (With the device powered off, hold Volume Down + Power)
Flash
Click to expand...
Click to collapse
Just wanna say it should be "Reboot into bootloader", as the bootloader type of fastboot is required to flash some of the images: the dtbo, vendor_boot and vendor_kernel_boot partitions can't be read by pure fastboot (what's usually called fastbootD) mode and will throw this sort of error:
Warning: skip copying .. name .. image avb footer (.. name .. partition size: 0, .. name .. image size: .. ).
Sending '.. name ..' (... KB) OKAY [ 0.404s]
Writing '.. name ..' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Click to expand...
Click to collapse
So anyone that got confused should just use `adb reboot bootloader` instead of reboot fastboot
I've flashed the ROM and so far it looks & feels really smooth, thanks!
Currently using GrapheneOS. Will flash LOS once they release a user build with release keys.