[ROM][flo|deb][UNOFFICIAL][LineageOS 20.0] - Nexus 7 (2013) Android Development

[ROM][flo|deb][UNOFFICIAL][LineageOS 20.0] - Nexus 7 (2013) Android Development

Thanks will download when I get home

lollyjay said:
Thanks will download when I get home
Click to expand...
Click to collapse
Cool .. go for it
It seems there are some download issues using mobile devices.
Google Mobile version wants to redirected to some ...mobile... link, which is not working.
At least for me.
Also the import into Google Drive App seems not to work.
If you choose "request desktop version" in Chrome mobile settings it should work.
On normal desktop browsers there are no problems.
This issue occurs since a few days .. for "all" my Google Drive projects

Hi I downloaded in Windows 10 and all working atm. More after I test.
---------- Post added at 08:31 PM ---------- Previous post was at 08:01 PM ----------
ROM seems fully functional. Working well with data and dalvik formatted f2fs.
Your recovery is also functioning well, with the the exception that it takes over a minute to load. Not a problem for me though.

This is related to F2FS .. if you would have ext4 data it will load much more quickly.

followmsi said:
This is related to F2FS .. if you would have ext4 data it will load much more quickly.
Click to expand...
Click to collapse
After installation, does not go into the recovery (3.0.2)
On version 3.0.3-3, such a problem will not exist?
Which sections have the format f2fs ?, and whether it is possible to add a night mode?

boom1982 said:
After installation, does not go into the recovery (3.0.2)
On version 3.0.3-3, such a problem will not exist?
Which sections have the format f2fs ?, and whether it is possible to add a night mode?
Click to expand...
Click to collapse
/system/bin/install-recovery.sh
You loose recovery .. this is normal ... if not rooted ..(SuperSU.zip)
The easiest solution is to install SuperSU.zip via TWRP.
Maybe I can remove it for next build .. not sure.
F2FS .. via TWRP
Wipe - Repair/Change file-system ...
Jus install the ROM and test and play yourself
Cheers

Does micro gapps work with this ROM, or only nano?
Reason I ask is that some things (Face Unlock) don't come with nano and there is no easy way to add that back in that I've found.

rajsris said:
Does micro gapps work with this ROM, or only nano?
Reason I ask is that some things (Face Unlock) don't come with nano and there is no easy way to add that back in that I've found.
Click to expand...
Click to collapse
Micro gapps works! [emoji6]

I cannot install Gapps 7.1.1 (tried micro and aroma), message saying I am on Android 6.0.1 and need to use proper version. Deb.

finkbg said:
I cannot install Gapps 7.1.1 (tried micro and aroma), message saying I am on Android 6.0.1 and need to use proper version. Deb.
Click to expand...
Click to collapse
I installed open gapps arm 7.1 pico with no problem. Not enough system available space for micro

You can try to resize file system of system partition inside TWRP to get full partition size.
Or use the Update.zip_resizefs_flo.zip inside the download folder.
Works for deb too.
Cheers

Hmmm not sure what I'm doing wrong. Tried the process twice, both times after reboot step, TRWP tells me no OS installed. Suggestions?

Enough space is available for micro. I managed to install it after a few reboots (no clue how). However, having converted data to f2fs, I now cannot write to data from within the ROM (play store crashes on install of any app, webview cannot start a download and camera cannot save photos). Latest rom from yesterday, haven't installed any fstab patches (thought this rom being the next release would not need any patches, am I correct?). Any suggestions?

rajsris said:
Does micro gapps work with this ROM, or only nano?
Reason I ask is that some things (Face Unlock) don't come with nano and there is no easy way to add that back in that I've found.
Click to expand...
Click to collapse
Keep in mind that all Open GApps installs can be customized so if you want FaceLock you would chose the lowest package with it and them use the config file to remove the rest of the differences.
Also Face Unlock DOES come with Nano BTW, only package without it is Pico.
(Disclaimer: I'm a former Open GApps team member.)

Yes, micro works. It worked with the original ROM by nbehary and it works with this one as well.

finkbg said:
Enough space is available for micro. I managed to install it after a few reboots (no clue how). However, having converted data to f2fs, I now cannot write to data from within the ROM (play store crashes on install of any app, webview cannot start a download and camera cannot save photos). Latest rom from yesterday, haven't installed any fstab patches (thought this rom being the next release would not need any patches, am I correct?). Any suggestions?
Click to expand...
Click to collapse
Did you fix your problems ?
The fstab has been changed ... you can verify yourself.
Open terminal app ..
Code:
su -
cat fstab.flo
To see the current partitons and there used/mounted filesystems ..
Code:
mount
Pls have a look here ..
https://forum.xda-developers.com/showpost.php?p=71296026&postcount=716
F2FS seems to work fine on data - I still use it on cache only.
If you face strange issues, pls start with a fresh TWRP factory reset first.
Cheers

bgiesing said:
Also Face Unlock DOES come with Nano BTW, only package without it is Pico.
Click to expand...
Click to collapse
Thanks for the info, I meant pico actually, as all other nougat roms for this device only have space for that package.

followmsi said:
F2FS seems to work fine on data - I still use it on cache only.
Click to expand...
Click to collapse
Working fine here.

I have the rom flashed and everything looks good with cache and data converted to F2FS. However I am experiencing an odd issue. When i first set up the tablet I sign in with my gmail account and everything looks good. I do a clean setup so nothing restores and download the official gmail from the play store. Once it installs and opens it does not seem to notice that my google account is configured. It asks me to add a mail account and if i put the same account in it says the account already exists. I've factory reset this 3 times trying something different each time thinking maybe I did something dumb. Flashed many roms before and never seen this, any ideas?
---------- Post added at 08:07 PM ---------- Previous post was at 08:03 PM ----------
followmsi said:
You can try to resize file system of system partition inside TWRP to get full partition size.
Or use the Update.zip_resizefs_flo.zip inside the download folder.
Works for deb too.
Cheers
Click to expand...
Click to collapse
dumb question but what does the partition resize change it to? I was looking to find a stock partitioning sizes vs this script chart or explanation.

Related

[ROM][TUTORIAL][UNOFFICIAL] Cyanogenmod 7.2 for HTC EXPLORER/PICO A310e

RESERVED for FAQs and troubleshooting!!

ReSeRvEd just like that :silly:

:cyclops:
Reserved for Changelogs ....too lazy to do it now

Fantastic work!
But I suggest you to change the thread name, and including the following "[TUTORIAL]", because poeple will think that is the main thread to this rom.
Regards!

a nice guide to help people:good:, one thing to though is you need to say "backup your old rom with cmw 1st before installing any other" (just incase) and also to stop conflicts from other roms that have been installed you really need to format system, boot, in mounts/storage menu aswell as factory wipe..............

You sir just made my day.

LiVeRpOoL-FaN said:
a nice guide to help people:good:, one thing to though is you need to say "backup your old rom with cmw 1st before installing any other" (just incase) and also to stop conflicts from other roms that have been installed you really need to format system, boot, in mounts/storage menu aswell as factory wipe..............
Click to expand...
Click to collapse
Not really. You'd only ever need to do a factory wipe/reset and then dalvic-cache wipe Cheers.

Txask said:
Fantastic work!
But I suggest you to change the thread name, and including the following "[TUTORIAL]", because poeple will think that is the main thread to this rom.
Regards!
Click to expand...
Click to collapse
Did it ..thanx for the heads up!!(sorry reached thanx limit of the day will surely do it tomorrow)
LiVeRpOoL-FaN said:
a nice guide to help people:good:, one thing to though is you need to say "backup your old rom with cmw 1st before installing any other" (just incase) and also to stop conflicts from other roms that have been installed you really need to format system, boot, in mounts/storage menu aswell as factory wipe..............
Click to expand...
Click to collapse
Did this too..thanxx for the tip!!

AIndoria said:
Not really. You'd only ever need to do a factory wipe/reset and then dalvic-cache wipe Cheers.
Click to expand...
Click to collapse
thats what i thought..and dalvik cache also gets cleared by factory wipe!! Anyway whats the harm in being extra cautious!!

ToinouAngel said:
You sir just made my day.
Click to expand...
Click to collapse
I aim to please :angel:

vshl2995 said:
I aim to please :angel:
Click to expand...
Click to collapse
Yeah well I can't unlock the bootloader, thanks to HTC Sync who doesn't recognize my phone. So I'm screwed.

ToinouAngel said:
Yeah well I can't unlock the bootloader, thanks to HTC Sync who doesn't recognize my phone. So I'm screwed.
Click to expand...
Click to collapse
Did you download the latest htc sync software? Here
http://www.htc.com/sea/software/htc-sync/

vshl2995 said:
Did you download the latest htc sync software? Here
http://www.htc.com/sea/software/htc-sync/
Click to expand...
Click to collapse
Yeah, but no luck. I'll try on another laptop when I have a chance.
EDIT: Windows 8 seems to be the problem, I can't update the drivers with the unrevoked f.ile. So yeah, I'll try with Windows 7.

ToinouAngel said:
Yeah, but no luck. I'll try on another laptop when I have a chance.
EDIT: Windows 8 seems to be the problem, I can't update the drivers with the unrevoked f.ile. So yeah, I'll try with Windows 7.
Click to expand...
Click to collapse
You shouldn't really use consumer preview as your primary OS..u should install it in a different partition!!

vshl2995 said:
You shouldn't really use consumer preview as your primary OS..u should install it in a different partition!!
Click to expand...
Click to collapse
I know, I installed the Consumer Preview in order to try it out, problem is I was doing multiple things at the same time and accidentally installed it over Vista.
I was too lazy to reinstall Vista back so I just decided to wait for the final version to be released as the preview works just fine for everything I do with my laptop... Well until now anyway, ha.

ToinouAngel said:
I know, I installed the Consumer Preview in order to try it out, problem is I was doing multiple things at the same time and accidentally installed it over Vista.
I was too lazy to reinstall Vista back so I just decided to wait for the final version to be released as the preview works just fine for everything I do with my laptop... Well until now anyway, ha.
Click to expand...
Click to collapse
Lol..

(I would use jaggy's tutorial to ask but since it hasn't been active for ten days I thought I'd be better to ask here instead of bumping the other thread, if I'm wrong I apologize)
So yeah, I'm still at the rooting process and it seems I'm definitely out of luck on this one.
So first off, I apparently managed to unlock the bootloader (and it IS unlocked, when I'm in bootloader mode I do have the "*** unlocked ***" on top of the screen) and at the same time keeping my apps, settings, etc...This was the first flag that something was wrong.
Adding the Recovery seems to have worked out fine, however when I tried to install the Superuser.zip I got the apparently not-so-uncommon "(Status 0) Installation aborted" message. I did some research and tried the method of removing the extra "updater-script~" from the archive but it did not work. Tried the method of doing a nandroid backup and then installing Superuser but no luck either.
I'm getting seriously hopeless, any idea on what I might have done wrong and how to get Superuser working?

Which recovery did you install, I was having some problems flashing anything with non-yannou's (I know i wrote it stupid but, you've got the idea )
Anyway, give a try to flash some rom, not sure if it will work without superuser installed, but nothing worse can happen (I think)

shortyoko said:
Which recovery did you install, I was having some problems flashing anything with non-yannou's (I know i wrote it stupid but, you've got the idea )
Anyway, give a try to flash some rom, not sure if it will work without superuser installed, but nothing worse can happen (I think)
Click to expand...
Click to collapse
I installed the Recovery given by jaggy's tutorial. But Recovery isn't the problem as far as I know, since I've the option to install .zip file when in Recovery mode. My only issue comes from the fact that the Superuser file won't install itself.

[Q&A] [ROM] [MM 6.0] [ KatKiss-Katshmallow ]

{
"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"
}
KatKiss Marshmallow ROM
Asus TF300T Q&A Thread
Please note that this version is made for and tested on the TF300T model.
Thanks to keep this thread for the TF300T
Rom Thread: http://forum.xda-developers.com/transformer-tf300t/development/rom-t3237867
-

Long time starting whilst whilst "optimizing App 1 of 1"
Great job Tim,
Have successfully installed ROM 007 and recommended GAPPS. Works well, but on restart spends several minutes with “Android is starting optimizing App 1 of 1”.
I have checked the forum and others have mentioned this but have not spotted a fix.
Any advice?
Thanks

DPR59 said:
Great job Tim,
Have successfully installed ROM 007 and recommended GAPPS. Works well, but on restart spends several minutes with “Android is starting optimizing App 1 of 1”.
I have checked the forum and others have mentioned this but have not spotted a fix.
Any advice?
Thanks
Click to expand...
Click to collapse
not sure,
I don't have that issue.
Try to format /cache and dalvik-cache to force a full optimize process.
Maybe something went wrong whent art tried to optimize one app.
Did it do that from the 1st install or after you restored some of your apps ?
Would help to find out which app it is exactly.
If it is still doing it after the cache and dalvik format,
reboot and Grab a logcat right after it is done optimizing the 1 of 1 app.

timduru said:
not sure,
I don't have that issue.
Try to format /cache and dalvik-cache to force a full optimize process.
Maybe something went wrong whent art tried to optimize one app.
Did it do that from the 1st install or after you restored some of your apps ?
Would help to find out which app it is exactly.
If it is still doing it after the cache and dalvik format,
reboot and Grab a logcat right after it is done optimizing the 1 of 1 app.
Click to expand...
Click to collapse
Tim, thanks for a prompt response. I have now done a clean install, including a factory reset and data format.
Problem still present on second boot, with only apps in your recommended GAPPS package installed.
Then installed ES File Explorer and Chainfire's LiveBoot to create the logcat.log file. However, I don’t have the knowledge to understand the output, even with the help of google.
I then wiped cash and dalvik and on restart the optimization process moves along at a reasonable pace, but spends a long time optimizing app 69 of 72. Not sure if this helps, and remember this is with ES File Explorer and Liveboot installed.
Any advice would be appreciated.
Regards

DPR59 said:
Then installed ES File Explorer and Chainfire's LiveBoot to create the logcat.log file. However, I don’t have the knowledge to understand the output, even with the help of google.
Click to expand...
Click to collapse
post the logcat file here.

timduru said:
post the logcat file here./
Tim, sorry but can not work out how to post the file.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

DPR59 said:
Great job Tim,
Have successfully installed ROM 007 and recommended GAPPS. Works well, but on restart spends several minutes with “Android is starting optimizing App 1 of 1”.
I have checked the forum and others have mentioned this but have not spotted a fix.
Any advice?
Thanks
Click to expand...
Click to collapse
i have the same problem not a big issue just a bit annoying

[email protected] said:
i have the same problem not a big issue just a bit annoying
Click to expand...
Click to collapse
Seems to be google gms app taking too much time to optimize for users who left /data as ext4
I'll increase the timer in V008,
but if you change /data to f2fs that should be faster and work fine too.
It seems to be the difference between those who have the issue and those who don't: /data ext4 Vs f2fs

timduru said:
Seems to be google gms app taking too much time to optimize for users who left /data as ext4
I'll increase the timer in V008,
but if you change /data to f2fs that should be faster and work fine too.
It seems to be the difference between those who have the issue and those who don't: /data ext4 Vs f2fs
Click to expand...
Click to collapse
hey, sorry for the noob question but how do i change to f2fs and also the browser seems to block going on google sites that are advertised if i try go on bookings.com for example through a google search it says err connection refused

[email protected] said:
hey, sorry for the noob question but how do i change to f2fs
Click to expand...
Click to collapse
Wipe => Advanced wipe
check the box for data then click on Repair or change file system
then click F2FS
and also the browser seems to block going on google sites that are advertised if i try go on bookings.com for example through a google search it says err connection refused
Click to expand...
Click to collapse
That's the adblocker included.
What is the hostname in the url? I can remove that to let it go through.

timduru said:
Wipe => Advanced wipe
check the box for data then click on Repair or change file system
then click F2FS
Click to expand...
Click to collapse
it seems I'm very unlucky lol, I tried doing this but get an error that says file system could not be changed or something like that, I tried some other sollutions on google but none of them worked, I still get the same error

[email protected] said:
it seems I'm very unlucky lol, I tried doing this but get an error that says file system could not be changed or something like that, I tried some other sollutions on google but none of them worked, I still get the same error
Click to expand...
Click to collapse
You need to use a recovery that supports it and is not buggy.
ie use the KANG TWRP linked in the 1st post of the rom
(Some of the TWRP out there won't support formatting F2FS correctly.)

timduru said:
You need to use a recovery that supports it and is not buggy.
ie use the KANG TWRP linked in the 1st post of the rom
(Some of the TWRP out there won't support formatting F2FS correctly.)
Click to expand...
Click to collapse
thanks this solved everything, you really are a mastermind

DPR59 said:
timduru said:
post the logcat file here./
Tim, sorry but can not work out how to post the file.
Click to expand...
Click to collapse
Tim, update
have now changed /data to f2fs and installed version 008 of the ROM, not added any of my apps yet but so far no apps optimizing on a restart. Thanks for you help with this, donation on the way, and keep up the great work.
Paul
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Screen rotation cure?
I have found that with rotation control app installed, but NOT running, auto rotate appears to work for apps I am using, if rotate screen is enabled in display properties.
No need for manual rotation, indeed, the rotation app is not running, just installed then stopped in app properties.
So far works every time for me

Hey Tim just for curiosity sake would there be any benefit in having cache and system as f2fs aswell? If so can you make the next update compatible I tried doing it just to see if it would work but was just stuck on the meerkat screen so I put system and cache back to ext4

Fantastic work, Timduru. I installed the 08 without a problem and without changing partition to F2FS. Installation and App optimization took less than 10 min. I got frustrated though because of the autorotation issue and the lack of marshmallow support (card access) of some apps (i.e. Dropsync). With the 09 and the autorotation issue solved I will go back to MM. Thanks for your effort :good::good::good::good:
I actually hadn't touched my TF300t for the last year. But with your great roms - it is a pleasure to use it again.

MPSmart said:
Fantastic work, Timduru. I installed the 08 without a problem and without changing partition to F2FS. Installation and App optimization took less than 10 min. I got frustrated though because of the autorotation issue and the lack of marshmallow support (card access) of some apps (i.e. Dropsync). With the 09 and the autorotation issue solved I will go back to MM. Thanks for your effort :good::good::good::good:
I actually hadn't touched my TF300t for the last year. But with your great roms - it is a pleasure to use it again.
Click to expand...
Click to collapse
Is 7 --> 8 --> 9 dirty flashable?

Google Play Wont Download apps
I installed the ROM but for some reason none of the apps will install from Google Play. They start downloading and stay downloading forever - never actually downloading.
Any suggestions....
Thanks
Jay

timduru said:
You need to use a recovery that supports it and is not buggy.
ie use the KANG TWRP linked in the 1st post of the rom
(Some of the TWRP out there won't support formatting F2FS correctly.)
Click to expand...
Click to collapse
Thanks for all your work on this ROM.... A noob here, am using the KatKiss Lollipop v030 and it is the best. Have tried to install KatKiss Marshmallow v009, seems to be slow as i suspect am doing it wrong, here is the steps i did using TWRP 2871.
1. Full Wipe = success
2. Flash KatKiss Lollipop v009, flash super su, flash gapp (in that order) = success
3. Wipe cache/davlic = success
4. Tried to change data to f2fs with twrp 2871 = not allowed or error or failed
5. Reboot to system = tablet booted to marshmallow but very slow even though i let it optimize for an hour and a
half.
Questions:
1. When should i change the data from ext4 to f2fs? Is it before step 1 or after step 1, step 2?
2. I also see some post that i should unmount, how to do that and in which step should i do unmount?
3. Maybe TWRP 2871 is the culprit?
I update TWRP by flashing the latest TWRP(zip file). The problem now is the latest twrp(2872) is an img file.
Will that img file be flash to update my TWRP?
Have returned back to KatKiss Lollipop v030. Sorry for all this troubles, this tablet is my only computer and you made it very fast. Helps me with my studies. If someone can help me?

[FIXED][OFFICIAL][APP]Dualboot Patcher For Lenovo A6000/+

{
"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"
}
I am proud to present the official dual boot project for Lenovo A6000. 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
What is DualBootPatcher?DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 200+ supported devices and their variations.
Information:I have managed to get Lenovo A6000 to the DualBootPatchers Official list, I am not the creator of the Dualboot patcher, just the supporter.
It's awesome and useful for testing out roms or if you want, switching ROMS.
Disclaimer:
Code:
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. Hard. A lot.
Requirements:1. A Custom Recovery (TWRP)
2. A ROM
3. Dual Boot Patcher app from the download section below.
4. A rare thing you find now-a-days on XDA known by the codename: B.R.A.I.N
What does the app do ?:It patches...
Custom kernels for dual boot support
ROMs to make them boot as secondary
Gapps
Any other mod you would like to install on your secondary ROM
What's supported ?
Except Toaster and Alarm clocks pretty much everything is supported.
Click to expand...
Click to collapse
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
-Grant Root Permission
-Go to settings and select install bootui
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later, and if you weren't asked to set kernel then select set kernel also.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to "a6000-Lenovo-A6000" and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip.
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Using Bootui:
- After installing (update) bootui, and flashing the secondary ROM then go to "ROMS" section again and open secondary ROM Settings) and select Update Ramdisk, Now when you will reboot a TWRP like Screen will appear, in that select whichever ROM u wanna boot.
Note-
Clean Flashing any simple ROM from TWRP will wipe both the ROMs, so if you clean flash and want to dual boot, follow the instructions again.
Partitions Configurations:
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.
How to boot to another ROM ?This is simple ... . So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Instead you can use the bootUI to switch ROMs as stated above
Apps and Data sharing:
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
Click to expand...
Click to collapse
To use app sharing, follow these steps in every ROM that you want to use app sharing:
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
Click to expand...
Click to collapse
FAQs
How do I uninstall the secondary ROM
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".
OK, Now i Want to change my Primary ROM but want to keep the Secondary 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
I wanna change the secondary ROM
Wipe it using the 3 dot menu and 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
Ok but the Update Ramdisk failed
Dont worry simply follow the further steps, i have got it thoroughly tested on the telegram group and by myself
But I have the 8GB Variant so wont flashing secondary ROM eat my Storage space?
The Answer is NO, you may not be able to flash Gapps in some cases for secondary ROM, but as long as you flash the secondary ROM in /system, your storage space wont be used
Downloads:
https://dbp.noobdev.io/downloads/Cheers ! we are officially supported
Note: You can download any version since "9.3.0.r97.g737d9dd5"
Sources:DualBootPatcher:https://github.com/chenxiaolong/DualBootPatcher
Lenovo A6000 Support:
https://github.com/chenxiaolong/DualBootPatcher/pull/922
Known Issues:
Comment here if you face any.
Credits:
@chenxiaolong for the awesome DualBootPatcher.Other people behind the DualBootPatcherAnd Me :V
XDA:DevDB Information
[OFFICIAL][APP]Dualboot Patcher, Device Specific App for the Lenovo A6000/Plus
Contributors
[email protected]_, chenxiaolong
Source Code: https://github.com/varunhardgamer/DualBootPatcher
Version Information
Status: Stable
Created 2017-11-04
Last Updated 2017-11-04

This is more than awesome dude.

Reserved

Fine...
Something new for A6k/+

[email protected]_ said:
Reserved
Click to expand...
Click to collapse
Oops!!! Seems I posted before OP. Sorry for that.

Jitheshwar said:
Oops!!! Seems I posted before OP. Sorry for that.
Click to expand...
Click to collapse
No problem dude, you reserved for me :good:

is anyone having problem with the ramdisk update as every time i update it gives error and create a log and i also attaching the log for that and i am on aosp extended 4.4

garvit girotra said:
is anyone having problem with the ramdisk update as every time i update it gives error and create a log and i also attaching the log for that and i am on aosp extended 4.4
Click to expand...
Click to collapse
I know that and we are checking it again, looks like something got derped

EDIT-> The issues are fixed grab the latest snapshot

The fix has been added, download fhe latest snapshot and enjoy

Astala vistala baby
Varun you are the man

Tried the latest update of release 125 but no solution update ramdisk still fails every thing else work like set kernel upate boot ui everything else work only update ramdisk dont work

garrygarvit said:
Tried the latest update of release 125 but no solution update ramdisk still fails every thing else work like set kernel upate boot ui everything else work only update ramdisk dont work
Click to expand...
Click to collapse
Clean flash and try again, have tested the build myself and its working, clean flash the rom becausethe older dualboot may have left some remnants

[email protected]_ said:
Clean flash and try again, have tested the build myself and its working, clean flash the rom becausethe older dualboot may have left some remnants
Click to expand...
Click to collapse
Done the clean flash but no help ramdisk still fails in aex 4.4 as my primary rom and i also flashed the utilities for some help but no help only update kernel and boot ui works

garvit girotra said:
Done the clean flash but no help ramdisk still fails in aex 4.4 as my primary rom and i also flashed the utilities for some help but no help only update kernel and boot ui works
Click to expand...
Click to collapse
Well i find the solution i revert to the stock rom of lenovo and try dual boot patcher work in that ramdisk kernel boot ui all work i think the problem is in the .aex rom by the thanks for all help varun
---------- Post added at 09:08 AM ---------- Previous post was at 08:46 AM ----------
Well a new problem arises now after all success that now when i am not able to download any things from chrome or other browser in the internal storage it shows no sd card detected download failed by the then i checked into storage there both my internal storage and external storage dont know why this happen now i fed up of all this. Now i will be only to stock rom for some while no rooting no flashing

garvit girotra said:
Done the clean flash but no help ramdisk still fails in aex 4.4 as my primary rom and i also flashed the utilities for some help but no help only update kernel and boot ui works
Click to expand...
Click to collapse
Right now i am on aex 4.4 dual booting aicp

[email protected]_ said:
Right now i am on aex 4.4 dual booting aicp
Click to expand...
Click to collapse
Updating ramdisk on work for in lenovo stock rom not on aex even after the clean flash

Dual Boot
Hello Varun
Can i Dual Boot Stock Kitkat and Viper
as Both has different Android version. so difference is only of one flaashable file that is: kk to lp firmware patch .
so how to do that.

[ROM] LITE OS 6.0 v2 for realme 2 pro [STABLE][CUSTOM STOCK ROM]

{
"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"
}
★LITE OS 6.0 V2
(Based on stock os)
Stable and can be used as daily driver
Watch video for review and install-
https://youtu.be/q3L25WblKLM
Rom features-
✪Prerooted
✪Odexed this time
✪Debloated
✪Busy Box
✪Qn Engine
✪Some of The Major Init.d tweaks......
✪Zero FC.(If You Follow my guidelines)
✪Nano
✪High Touch Sensitivity (Driver Moded)
✪Swap enabled (upon request)
✪Ram Optimization
✪Loop Smoothness Tweak
✪SD card Read Write Speed Optimization
✪Sqlite Optimization
✪Net Speed & DNS Tweaks
✪Darky Zip-align
✪Build Prop Tweaks
✪Battery Saving script
✪Decrypted
✪Liquid UI
✪Kernal optimization
✪Gpu driver refined
✪Unecessary resources removed inside app and system for better optimization
✪And more if u explore ~_~
Donators -
Dr_lokman_sir
Anurag singh
Syam velchuri
Donate to apperciate and support :
7804011237 (Google pay/tez)
7804011237 (Paytm)
7804011237 (Phonepe)
[email protected] (UPI ID)
PAYPAL : www.paypal.me/mks7s
Source used for build -Stock kernel and stock rom
Downloads -
(Make complete backup first , and scroll down more and read F.A.Q too for your general questions )
✪LITE V2 ROM LINK
✪LITE APPS LINK
Instructions -
1.Download ROM
2.Place rom in internal memory
3.Wipe everything except internal and memory card
4.Flash and reboot
5.Install missing package from r2x2 recovery
6.done. if you can't understand my instructions then watch video tutorial
Missing packages (install only if you need !) -
(Scroll down and read F.A.Q for installation)
✪Assitive touch - LINK
✪Clone apps - LINK
✪Gesture U.I - LINK
✪Night shield - LINK
✪Oppo gallery - LINK
✪Long screenshot & other - LINK
✪U.I Sound - LINK
✪Oppo backup & restore - LINK
✪Call recording - LINK
Reproduction,remodification and use of any components of this rom in other rom/mod is not allowed

F.A.Q -
1.Is there any bug?
Ans - no ,if you found one please let me know
2.How to install missing packages ? proper way
Ans - install along with rom when you freshly install rom and
1.mount system first from recovery
2.then install missing packages and reboot system .
3.Having problems to get root rights for titanium backup and other ?
Ans - flash LINK zip again ! And uninstall magisk app and install app manually by extracting LITE APPS zip
4.quick pic and magisk not opening ?
Ans - extract LITE APPS zip and install it manually
5.Im having transparent lockscreen problem ?
Ans - just set any wallpaper it will get fixed or use color os theme store to fix it by changing theme
6.Im missing some apps from lite os , is there any way to get them ?
Ans - yes comment down below , i'll upload for u okay (will take time)
7.My phone is encrypted , should i flash this rom ?
Ans - decrypt from here {Mod edit} although rom is decrypted already if u try to install this on your encrypted phone then you'll need to format data
8.Are other zip required to wipe anything ?
Ans - No just flash by recovery and reboot okay
9.Im on color os 5 and gsi , can i flash this directly ?
Ans - No , first upgrade from this link - {Mod edit} U must be on color os 6 already inorder to flash this ROM
10.how do i fix this red root notification bar ?
Ans - follow this to remove root notification bar {Mod edit} and if u don't like xposed then use system ui tuner from playstore
11.Im facing strange problems ? which happens to no one !
Ans - you'll be ignored because you are'nt following what i said above and in video too !

Honest user review -
Q.1 How's performance ?
Ans -
Q.2 How's ram management ?
Ans -

Just finished downloading... Have been waiting for this

BUG (?): If you have a lockscreen enabled, and then if you backup this ROM and the Data partition using R2X2 Recovery and then restore it, the phone will refuse to accept your passcode and deny access. Even if you reset the passcode, you'll never be able to unlock the lockscreen. Remove your lockscreen passcode before backup, otherwise you'll be permanently locked out of your own data.
---------- Post added at 04:01 PM ---------- Previous post was at 03:54 PM ----------
Also, after 3 clean installations, I can confirm that the root warning notification fix does not work on this ROM by the given method. Could not flash the Riru zip.
Update: The notification fix works. I had to flash Magisk 17.1 seperately. But somehow, R2X2 Recovery kept losing grasp of /system, so the flash kept failing. I had to unmount and remount /system manually before flashing Magisk. If you face the same problem, try this.

CerinCorbierre said:
BUG a.... IMPORTANT NOTE for users: ........n. ...., o.....
---------- Post added at 04:01 PM ---------- Previous post was at 03:54 PM ----------
.....
Click to expand...
Click to collapse
Ofcourse if you try backup any rom with locked password , it will have password after restore for sure !!!! don't u know ????
Just reset the data or don't create backup of data
I don't get it why you highlighting such things with red words without having proper knowledge about it
And about red root notification , reset data again and flash magisk as mentioned in post and flash riru and ed exposed , it will work for sure
As its working for me and 99% people out there in my group !

Bro, why are you sending so many exclamation marks? I'm not shouting. Chill, man.
anabhi said:
Ofcourse if you try backup any rom with locked password , it will have password after restore for sure !!!! don't u know ????
Just reset the data or don't create backup of data
I don't get it why you highlighting such things with red words without having proper knowledge about it
Click to expand...
Click to collapse
I do. It's just that in case of my previous phones, they accepted the correct password after restoration. ColorOS/LiteOS does not accept the password. Maybe this problem is unique to ColorOS. You know better than I do, obviously.
anabhi said:
And about red root notification , reset data again and flash magisk as mentioned in post and flash riru and ed exposed , it will work for sure
As its working for me and 99% people out there in my group !
Click to expand...
Click to collapse
I wiped data and flashed LITE APPS.zip again, 3 times. Didn't work.
Should I erase internal storage, too? I'll try it if you tell me to.
I also tried flashing Magisk 17.1 seperately, but it fails to mount /system in recovery.

anabhi said:
And about red root notification , reset data again and flash magisk as mentioned in post and flash riru and ed exposed , it will work for sure
As its working for me and 99% people out there in my group !
Click to expand...
Click to collapse
Update: I've finally solved the problem. Thanks for your patience and attempts to help. But even though I reset my data 5 times and tried, it didn't work.
I did something else.
I tried to flash Magisk seperately, like you said. It kept failing because R2X2 Recovery kept saying "! Cannot mount /system".
I had already wiped the system and reinstalled LiteOS twice. Didn't help. Same problem.
So, a while ago, I manually unmounted and remounted /system in R2X2 Recovery 3-4 times. Then I tried flashing the Magisk zip, it worked. I didn't need to reset data.
After rebooting, I had to I was finally able to flash the Riru module in Magisk and follow your method.
Maybe R2X2 Recovery has a small bug? I had to manually unmount and remount system to get things working.
Anyway, thanks for all these amazing works, man. The red notification is finally gone.

Im already chill bro but you shouldn't send any confirmation that its not working on my rom , even though it works alright that's what im trying to tell you
Im happy your issue gotta solved enjoy .

So far I've 2 problems with the Magisk.
# Magisk that comes with the installation (LITE APPS) doesn't successfully install Riru module and that's why the red blinking is still there.
# If I flash latest Magisk (19.2/3), it is able to install riru and other modules successfully but the Magisk is installed as "Core Only Mode" and you can never change that. That mode disables the modules and there comes the blinking issue.
I've tried to solve this multiple times and in many ways (re-flash,mounting etc.) but failed. What should I do now ?

Sayed Anan said:
So far I've 2 problems with the Magisk.
................... What should I do now ?
Click to expand...
Click to collapse
Read question 3 from f.a.q and module working fine on 17.1 and why u updating to 19.1 when Its not supported on our device
Install below zip by recovery
https://www.androidfilehost.com/?fid=6006931924117891637
Then extract lite apps zip and install magisk app normally

Thanks for the rom and solution of the red blinking.
Keep up the great works. Peace.

anabhi said:
thanks for lite os v2...keep it up..:good:
Click to expand...
Click to collapse

U welcome sayed and meraj

Need Vendor zip
Bro, apps fc and battery backup decreased. (sot- 6 hourz). Plz provide vendor img.. Want to reflash lite os.

indra94 said:
Bro, apps fc and battery backup decreased. (sot- 6 hourz). Plz provide vendor img.. Want to reflash lite os.
Click to expand...
Click to collapse
Bro just reflash rom zip again without wiping anything
Vendor.img is already there in lite os rom if u wanted to flash separately
Which apps force closing btw ?

Bugs Maybe ?
# When I use USB Tethering, sometimes (I've noticed 3 times, not everytime) my phone's apps are automatically closed and then after 2/3 seconds, showing a black screen, it comes back to normal (like it was forced closed).
# The second is that my notification bar is not showing last 3 icons from 2nd row.

Any suggestions ? Thanks.

Sayed Anan said:
# When I use USB Tethering, sometimes (I've noticed 3 times, not everytime) my phone's apps are automatically closed and then after 2/3 seconds, showing a black screen, it comes back to normal (like it was forced closed).
# The second is that my notification bar is not showing last 3 icons from 2nd row.
View attachment 4783982
Any suggestions ? Thanks.
Click to expand...
Click to collapse
About force close , i'll look
And your notification panel facing problem because of system ui tuner , reset system ui tuner preset and reboot

How to enable full Google Assistant in LiteOS v2? "Ok Google" isn't working. Can't launch Google Assistant buy long-tapping the Home button either.

Does magisk HIDE works....pl let me know as I use many banking apps ...

[ROM][11.0][4.9][AOSP][KUGO] Explosive Lobster

[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

Database Info

welcome