Database Info

[MOD][2015-08-29] MultiROM v32

​(Click on the image above to download my MultiROM Manager App)​MultiROM for the Samsung Galaxy S3 i9305, brought to you by Alexander_the_B0ss​
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I'm 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.
*
*/
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy S3 4G. It can boot any Android ROM . Besides booting from device's internal memory, MultiROM could boot from external SD card(untested). The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system.
Features:
* Multiboot any number of Android ROMs (as many as your internal memory can hold)
* Restore nandroid backup as secondary ROM (damn useful feature)
* Boot from Internal memory and MicroSD Card
Warning!
This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong (even if never happened until now) and you will have to flash stock firmware with Odin. Make backups. I personally can't stress enough for you people to make nandroids becuase you never know.
Installation
Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app Install my modified app and select MultiROM and recovery on the Install/Update card the app is still in alpha, so don't select install, use manual install below. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are choosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM itself - download the ZIP file and flash it in recovery.
Modified recovery - download the ZIP file and flash it in recovery or Mobile Odin app to flash the recovery.img contained inside ZIP.
Patched kernel (Only TWO: AGNi PureCM or AGNi PureSTOCK) - Download the ZIP file and flash it in recovery (seems like kexec-hardboot isn't activated by psndna88, so menu won't show up on boot)
*Downloads in Post #2*
If your MAIN ROM is TouchWiz or TouchWiz based, please use AGNi PureSTOCK kexec-hardboot status unknown, someone with stock rom please install app and tell me if kexec-hardboot is enabled.
If your MAIN ROM is not TouchWiz, but CM or AOSP (basically custom rom except MIUI) use AGNi PureCM no kexec-hardboot, tested.
You current rom will not be erased by the installation.
Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using MicroSD Card (UNTESTED)
During installation, recovery lets you select install location. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to MicroSD Card takes a bit more, because the external memory is (usually) slower and it needs to create the images. Also boot process is longer, highly depends on card's class. You can find ROMs installed on SD card in the "External" tab in boot menu.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
Add ROM - Add ROM to boot manager
List ROMs - List installed ROMs and manage them
Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
Settings - Well, settings
Manage ROM
Rename, delete - I believe these are obvious
Flash ZIP (only Android ROMs) - Flash ZIP to the ROM, for example GApps
Add/replace boot.img - Replaces boot.img used by the ROM, this is more like developer option.
Screenshots
Application
Recovery (Sorry for pictures...)
Bonus pic(zoom to see the RGBG-Matrix (PenTile))
My Homescreen and Lockscreen (for those interested)
Big thanks to Tasssadar for this awesome utility.
XDA:DevDB Information
MultiROM, multiboot tool for Samsung Galaxy S3 4G (i9305), Tool/Utility for the Samsung Galaxy S III I9300
Contributors
Alexander_the_B0ss
Version Information
Status: Beta
Current Beta Version: v32
Beta Release Date: 2015-08-30
Created 2015-08-29
Last Updated 2015-09-02

Reserved
DOWNLOADS
MultiROM itself: HERE (Check NOTE 2 below for testing zip)
Uninstaller: HERE
Recovery: HERE
Note 1: For recovery use 720x1280 multirom theme from here.
Note 2:
MultiROM Installer with MultiROMManager app and TWRP theme installation testing zip here. Basically what this zip does is, after MultiROM is installed, it copies to system/app my own version of MultiROM Manger to support i9305, then copies to the internal sdcard the theme for TWRP and sets the correct attributes.

What is that? I dont understand

a possibility to install more than just one operating system

Quick update for you guys:
Recovery works, but the theme is kinda weird, so use the theme provided for 'perfect' recovery
MultiROM menu won't show on boot, sent PM to Tassadar for help request. Meanwhile, i am trying to modify MultiROM Manager app to support i9305 to possibly have a workaround for the menu not showing up.
Stay tuned for more development and an OP update after everything is working. CYA

Another quick update for the ones interested in the project. I have succesfully compiled MultiROM Manger app that detects our device (after twenty attempts, then gave up and updated Android Studio to the latest version and redownloaded Android SDK and NDK. First attempt after reinstall worked).The APK fresh from the oven is here. This represents a milestone in MultiROM development because with the app now detecting the device one can avoid the boot menu not showing bug. BUT WAIT, THERE'S MORE
The bug i talked about is related to kernel, because the app doesn't detect kexec-hardboot.
Stay tuned for updated OP soon™.

Error in flashing. 'E: Error executing updater binary in zip '/external_sd/Roms/MultiRom/multirom-20150829-v32-UNOFFICIAL-i9305.zip'
Tried both with unmodified TWRP and MultiRom TWRP
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom

fs71gh said:
Error in flashing. 'E: Error executing updater binary in zip '/external_sd/Roms/MultiRom/multirom-20150829-v32-UNOFFICIAL-i9305.zip'
Tried both with unmodified TWRP and MultiRom TWRP
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
Click to expand...
Click to collapse
Are you really trying to install this on Note 4? Damn. It is only for i9305, aka m3xx aka m3 aka S3 4G. So WRONG FORUM

Alexander_the_B0ss said:
Are you really trying to install this on Note 4? Damn. It is only for i9305, aka m3xx aka m3 aka S3 4G. So WRONG FORUM
Click to expand...
Click to collapse
Sorry for your confusion but we also have an Eclipse for S3 LTE which is already in this forum and my device is undoubtedly also S3 LTE and not Note 4

fs71gh said:
Sorry for your confusion but we also have an Eclipse for S3 LTE which is already in this forum and my device is undoubtedly also S3 LTE and not Note 4
Click to expand...
Click to collapse
I don't want to keep this on, but check this post out http://forum.xda-developers.com/not...-x-teamwin-t2956011/post57742832#post57742832 and see the codename for the SM-910F and check your reply from before
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom

Alexander_the_B0ss said:
I don't want to keep this on, but check this post out http://forum.xda-developers.com/not...-x-teamwin-t2956011/post57742832#post57742832 and see the codename for the SM-910F and check your reply from before
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
Click to expand...
Click to collapse
I guess the problem is with the rom specifically (some things left out while porting), as I got your your apk working with two other cm11 roms.

@Alexander_the_B0ss
Hi boss.
I like this dual-boot initiative but i have some problem with apk (device not supported (trelte)) but i think you can solve this.
I edit the updater-script and remove this line (assert(getprop("ro.product.device") == "i9305" || getprop("ro.build.product") == "i9305");) (i test now in terminal command: getprop ro.product.device and show me i9305 ..i dont now why i can't install zip package. but i solve this with removed line.
So, i install recovery (multirom recovery) and i install zip. I install your modded apk and i have error.
On recovery, i try to install a new rom, and was installed (but on internal_memory/multirom directory i dont see any folder/file..but my space on rom was used by "new rom")
I try to inject my kernel (pureSTOCK 5.9.2). Nothing happen when i reboot my phone. I think need to show a menu with "What rom do you want to boot"..but nothing.
I can help you with tests to dev this project.
Keep up
EDIT: And, i dont now how can install a theme for TWRP..because text buttons not aligned

il3gal said:
@Alexander_the_B0ss
Hi boss.
I like this dual-boot initiative but i have some problem with apk (device not supported (trelte)) but i think you can solve this.
I edit the updater-script and remove this line (assert(getprop("ro.product.device") == "i9305" || getprop("ro.build.product") == "i9305");) (i test now in terminal command: getprop ro.product.device and show me i9305 ..i dont now why i can't install zip package. but i solve this with removed line.
So, i install recovery (multirom recovery) and i install zip. I install your modded apk and i have error.
On recovery, i try to install a new rom, and was installed (but on internal_memory/multirom directory i dont see any folder/file..but my space on rom was used by "new rom")
I try to inject my kernel (pureSTOCK 5.9.2). Nothing happen when i reboot my phone. I think need to show a menu with "What rom do you want to boot"..but nothing.
I can help you with tests to dev this project.
Keep up
EDIT: And, i dont now how can install a theme for TWRP..because text buttons not aligned
Click to expand...
Click to collapse
Heh, the updater-script bug is well-known to me, i'll try to fix it in the upcoming updates. The manager app issue happens is because you are running a Note 4 ROM from this forum and that rom changes the ro.product.device if not mistaken. If I can make this work, which i will do, i will have a talk with the ROM developers to not alter the ro.product.device for the app to work. To install a TWRP theme you have the instructions along with the download here. Just make sure to download for 720p.

Alexander_the_B0ss said:
Heh, the updater-script bug is well-known to me, i'll try to fix it in the upcoming updates. The manager app issue happens is because you are running a Note 4 ROM from this forum and that rom changes the ro.product.device if not mistaken. If I can make this work, which i will do, i will have a talk with the ROM developers to not alter the ro.product.device for the app to work. To install a TWRP theme you have the instructions along with the download here. Just make sure to download for 720p.
Click to expand...
Click to collapse
Thanks for your "talk with ROM Developers". Hope kexec-hardpatch is enabled (if I am right) soon and we will have boot menu working

@Alexander_the_B0ss
Any update? I devices is see like: m3 not i9305

il3gal said:
@Alexander_the_B0ss
Any update? I devices is see like: m3 not i9305
Click to expand...
Click to collapse
The actual codename for i9305 is m3 or m3xx, i9305 is the 'commercial name'. About any updates: for now i have a dead hdd, so at least for a couple of weeks no updates. Sorry. And also I am sick and need to go to hospital.

Alexander_the_B0ss said:
The actual codename for i9305 is m3 or m3xx, i9305 is the 'commercial name'. About any updates: for now i have a dead hdd, so at least for a couple of weeks no updates. Sorry. And also I am sick and need to go to hospital.
Click to expand...
Click to collapse
Get well brother.

Get well soon friend

any news ?????

hi, does this work on the older i9300 model (3g)?

[ROM 5.1.1] CM 12.1 Unofficial Memopad 10 FHD Lte - ME302KL

CyanogenMod 12.1 for the Memopad FHD 10 4G - ME302KL ​
{
"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"
}
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.
*/
-----------------------------------------------------------------------------------------------------------------------------------------------------------
What Works:
Touch
Display
Brightness (auto and manual)
4G Network
WIFI
GPS
Bluetooth
Accelerometer
USB Charging
USB OTG
USB Pendrive
Ext SDcard
Deep Sleep
Front and Back Camera
and other things...
Bugs
-----
-----------------------------------------------------------------------------------------------------------------------------------------------------------​
Installation
You have to unlock tablet with asus app.
You have to use SevenMaxs TWRP RECOVERY for Me302kl
1. Download the ROM and the BOOT.IMG from the link below
2. Download GAPPS
3. Transfer the zip files to your SD card
4. Reboot to recovery mode
Note: You Must use TWRP recovery
5. Optional: Do nandroid backup
6. Wipe data / Factory Reset
7. Install CM zip
8. THIS STEP IS EXTREMELY NEEDED: Make a backup of system partition
9. THIS STEP IS EXTREMELY NEEDED: Advanced wipe - Wipe only system partition
10. THIS STEP IS EXTREMELY NEEDED: restore system backup
11. Flash Open GApps zip - (do not flash pico gapps. It has a AOSP keyboard FC BUG - I flashed Stock)
12. Install Boot.img zip
13. Reboot to system
Enjoy LOLLIPOP!
The steps from 8 to 10 are needed because the new system installer make a copy by block, not by files. So the system partition will be large as the system image file. After flashed the system, we make a backup and format the partition. Now the size of system partition will be correct so we can restore the rom.
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Download: http://d-h.st/57LS This is only the ROM (system) without Boot.img - DONT'FLASH WITHOUT BOOT.IMG
Download Link for Boot.img http://d-h.st/nTaM
Download link for Boot.img with FastCharge [ http://www107.zippyshare.com/v/mrjjcDYf/file.html] thanks to SevenMaxs source.
Download Link for Framework-res.apk patched for Ext SD : http://www61.zippyshare.com/v/wONtvgZ4/file.html
Download TWRP Recovery by SevenMaxs : http://d-h.st/M3ep
To install recovery exstract frm the zip the file recovery.img and put it on the sdcard.
Then connect to the tablet with adb:
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p25
Reboot into recovery VOL+ AND POWER
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Source
Check out the KERNEL Source available on https://github.com/yatto/ME-302-KL
The rom is the Nexus 7 Official CM12.1 without some libs : system/lib/keystore.msm8960.so and power.msm8960.so and with the /system/vendor/lib/files from Me302kl 4.2.2 ROM
Feel free to submit any fixes, Just remember to give proper credits when using other people's source.
Credits
Cyanogenmod team
SevenMaxs for his recovery TWRP
If i missed someone contact me!
-----------------------------------------------------------------------------------------------------------------------------------------------------------
XDAevDB Information
CyanogenMod 12.1 for Me302kl, ROM for the Asus Memopad FDH 10 4G
ROM OS Version: 5.1.1 Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod for Nexus7 2013
Version Information
Status: Beta1, Stable

All OK
Thank you!
The main camera is working, but I have not found how to switch on the front?
And It seemed to me too big image on the screen, I was a little turned down the dpi settings.

AlexXx70 said:
Thank you!
The main camera is working, but I have not found how to switch on the front?
And It seemed to me too big image on the screen, I was a little turned down the dpi settings.
Click to expand...
Click to collapse
The cameras are hard to fix. They are used in different way by nexus7 and me302kl... I'm working hard on it...
In next release i'll fix the external SD. In my test it works ! Nexus 7 does not have an external_sd so i had to modify kernel, initrd and framework to make sd working...
Have a nice day...

cool
Thanks for this will be giving it a try this weekend.

Boot Img Updated ! link at 1st post.
Fix Cameras
Fix Sdcard
You have to replace framework-res.apk to make extSD working.
1) Download framework-res.apk from the link at 1st post
2) Copy it on sdcard (internal)
3) open a terminal emulator or ADB shell ant type :
Code:
[B]su
mount -o rw,remount /system
cd /system/framework
rm framework-res.apk
cp /sdcard/framework-res.apk ./
chmod 644 framework-res.apk
reboot[/B]
Enjoy LOLLIPOP

I think I need some help.
Currently I have CM 11 installed and I'm trying to install CM 12.1.
I follow instruction step by step, but all I get is endless reboot into black screen right after asus logo.
I still can access TWRP recovery by holding vol+ so I restored CM 11 for now.
What can possibly cause this issue? I can provide TWRP log if this may help, but I'm not sure how to attach file here.
Thank you for all your hard work and sorry for bothering and being such a noob.

redunka said:
I think I need some help.
Currently I have CM 11 installed and I'm trying to install CM 12.1.
I follow instruction step by step, but all I get is endless reboot into black screen right after asus logo.
I still can access TWRP recovery by holding vol+ so I restored CM 11 for now.
What can possibly cause this issue? I can provide TWRP log if this may help, but I'm not sure how to attach file here.
Thank you for all your hard work and sorry for bothering and being such a noob.
Click to expand...
Click to collapse
Make sure that you have done all the Wipes (cahe, dalvik cache, data without data/media). Follow the istructions. If you like provide logs. After bootloop, in recovery "/proc/last_kmsg" log will be interesting. Also TWRP log.

yattodettaman said:
Make sure that you have done all the Wipes (cahe, dalvik cache, data without data/media). Follow the istructions. If you like provide logs. After bootloop, in recovery "/proc/last_kmsg" log will be interesting. Also TWRP log.
Click to expand...
Click to collapse
Yeah, I double-checked all steps, did I miss anything?
1. Wipe dalvik cache, cache and data without data/media
2. Install cm-12.1-test.zip
3. Backup system partition
4. Advanced wipe - wipe system partition
5. Restore system backup
6. Flash GApps (Open GApps stock 5.1)
7. Install Boot.img (ME302KL_LP_READY.zip)
Would you mind if I send you logs in private message?

Any feedback?

yattodettaman said:
Any feedback?
Click to expand...
Click to collapse
It's greate. All working fine.

Root
How to get ROOT now?

Which G-apps do you think is better for the ME302KL tablet?
I'd use "Open GApps arm 5.1 Stock" (arm 32).
Do you think that's good?

feedback
Followed all steps.
Booting took long long time with the ASUS logo flashing up time to time.
After some minutes lollipop robot came out, after a long while more appear the sign "Android starting - Applications....." and after 5 min. the tablet was ready.
Did the patch for external SD card and rebooted.
Took (again) very long time in rebooting but in the end everything seemed to work correctly.
The only problem is that the app "Premium Play" doesn't work because it see the devices as rooted. But it isn't.... or is it?( rooted, I mean)
The other thing is the time for booting but I think we can stand it.
Thank you very very much for your work, we all appreciate it very much.
---------- Post added at 02:02 PM ---------- Previous post was at 01:08 PM ----------
Display start flashing when you type something.
Tried different keyboards, than the default google one, the problem remain.
bye

hi¡¡ can i use this rom on fhd 10 without lte and 4g?

bepigreen said:
Followed all steps.
Booting took long long time with the ASUS logo flashing up time to time.
After some minutes lollipop robot came out, after a long while more appear the sign "Android starting - Applications....." and after 5 min. the tablet was ready.
Did the patch for external SD card and rebooted.
Took (again) very long time in rebooting but in the end everything seemed to work correctly.
The only problem is that the app "Premium Play" doesn't work because it see the devices as rooted. But it isn't.... or is it?( rooted, I mean)
The other thing is the time for booting but I think we can stand it.
Thank you very very much for your work, we all appreciate it very much.
---------- Post added at 02:02 PM ---------- Previous post was at 01:08 PM ----------
Display start flashing when you type something.
Tried different keyboards, than the default google one, the problem remain.
bye
Click to expand...
Click to collapse
Sorry I can't go on testing because an old problem of my tablet jump out again : touchscreen stop working.
I tried everything but nothing really worked the only thing that keep the problem more stable is the kernel inside the sevenmaxs patch :ME302KL_Boot-jb-14.09.25-Perun_by_SevenMaxs.zip.
So I have to go back to it.
Good luck for your fabulous work
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
shindya228 said:
How to get ROOT now?
Click to expand...
Click to collapse
Actually CyanogenMod is a native rooted firmware.
Go in setting and find "root"

Everything is working - both cameras and extsdcard!
Many thanks for your job!!! :good::good::good:
But framework-res change through Root explorer.
Guys, don't forget activated superuser in settings of CM before mounting exsdcard.

First post updated with the link [http://www107.zippyshare.com/v/mrjjcDYf/file.htmlmg]
It is the boot.img with FastCharge.

yattodettaman said:
Any feedback?
Click to expand...
Click to collapse
Booting time (first installation and simple restart) take long time: the ASUS logo appears and than go away (blank screen) and then re-appears.. 3/4 times.
I have no tried the sdcard fix.
I have the problem of the Display flashing blue when typing something.
Problably wifi is a bit slow (i was comparing it with phone in downloading apps from play store ).

i tried it and it's an awesome rom
But the update didn't work with me
My device kept booting over and over again but nothing happened
Please help me to fix it and use sd card at my device

carlo.bar said:
Booting time (first installation and simple restart) take long time: the ASUS logo appears and than go away (blank screen) and then re-appears.. 3/4 times.
I have no tried the sdcard fix.
I have the problem of the Display flashing blue when typing something.
Problably wifi is a bit slow (i was comparing it with phone in downloading apps from play store ).
Click to expand...
Click to collapse
For the blue flashing try this: go on settings, display and lights, then enable .e xtended display.
For the First boot... It is not normal.

[ROM] [7.1.1] [PORT] [Unofficial] A.O.S.P - UMI London - FINAL

This rom is a port from dogee x5 device nougat 7.1.1 by SnowCatPDA.
{
"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"
}
LISTS OF DEVICES WITH THESE LCD THAT CAN RUN AOSP 7.1.1 WITHOUT ANY PROBLEM
otm1283
nt35521
with possible display problems after flashing the rom
s6d7aa0
Code:
#include
/*
* 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.
*/
Installation Instructions:
Download TWRP 3.1.1 from here. flash using spflash tool
Download ROM from <DOWNLOAD LINK BELOW>
Download OpenGapps nano or pico from OpenGapps
(choose Arm Android 7.1 )
or
Download BeansGapps MINI from BeansGapps
(choose the MINI Package)
*********
Boot to recovery
full wipe: system, data, cache, dalvik/art cache
flash rom
flash gapps
root of your choice
reboot system
making init.d work
follow instructions from here under aio patch v4
there is also a magisk module for init.d you can search for it here in xda.
bugs
front cam - kernel related issue - meaning i cannot fix it!
music fc once
tell me
ROM OS Version: 7.x Nougat
Based On: AOSP
Version Information
Status: Stable
Stable Port Release Date: 2017-08-22 (lol)
Ported 2017-08-22
screenshots
AOSP 7.1.1 v2.1​
screen flicker fixed
front cam fixed
camera right pixel
music fc fixed
more ram efficient
ril improved (i guess) - pls test both sim signal and comment below
revised swap script for performance
new kernel
new baseband - from MAY (umi_london) update
faster shutdown & reboot
quick power-on
hibernate support
bugs:
factory reset not working, it makes the rom unbootable after reboot
..tell me
new:
documents
deskclock
recorder
latinime (smaller size)
pixel launcher updated
jelly browser
greenify
installed as user app:
greenify
rom:
fully stable
deknoxed
debloated
deodexed
zipaligned
installation
full wipe
flash simultaneously
. rom
. gapps arm 7.1 (beansgapps/opengapps pico)
. supersu/magisk
reboot system
screenshots
https://file.army/i/6KgIUj
https://file.army/i/6Kgxol
https://file.army/i/6KgZuk
https://file.army/i/6Kgufv
https://file.army/i/6KgvVH
https://file.army/i/6KgERf
https://file.army/i/6KgOAI
https://file.army/i/6KglnV
https://file.army/i/6KgLTp
rom link
screenrcord here
AOSP 7.1.1 v2.3​
whats new:
camera2 as default camera
right pixel 8mp back 2mp front
lawnchair
smoother than the previous version
less lag
permissive on boot
init.d works
added chromium as default browser
removed some apps on previous version
bluetooth audio works
corrected battery capacity into 2050 mah
more..
not tested:
RIL (pls comment below for issues)
not working/bugs:
tell me..
ROM info:
debloated
deknoxed
zipaligned
gapps already in the zip
magisk already in the zip
note: whether you like magisk or not you dont have any choice
as i used it to switch selinux to permissive on boot, also, because
of this init.d works and other tweaks..
kernel-adiutor not responding?
-grant root permission to solve this issue
avoid updating runtime-opt. module
-may cause fc to some apps
documents (downloads) can no longer see sdcard
-go to settings, app, look for documents and clear its data
installation:
OWNERS OF w370 WITH THE LATEST MAY 04th 2017 FIRMWARE
full wipe (system, data, cache, dalvik/ART cache)
flash ROM.zip
reboot
OWNERS OF w370 5002W variant WITH THE LATEST JULY 25th 2017 FIRMWARE- TESTERS ONLY
full wipe (system, data, cache, dalvik/ART cache)
flash ROM.zip
flash firmware_patch.zip
reboot
link:
aosp 7.1.1 v2.3
5002w_patch
screenshots:
https://file.army/i/XnPKQl
https://file.army/i/XnPzN7
https://file.army/i/XnPZPf
https://file.army/i/XnPIlv
https://file.army/i/XnPLbQ
https://file.army/i/XnP6FV
https://file.army/i/XnPMla
AOSP 7.1.1​
what's new:
re-worked
feradroid engine
some of the hidden features unlocked e.g night light, etc..
circle battery icon
added dirac
5 GHz AP Band
some default apps replaced/updated
kernel adiutor removed
beansgapps removed from .zip
removed "x" on signal bar
set minimum brightness value to 3 (works when autobrightness is off)
"screen overlay detected" (of some apps) error fixed
camera2 shutter fixed
transfer files to ext-SDcard without write permission
fmradio fixed
battery saver color mode changed
new documentsui icon
add-ons:
miui camera, accessible in settings/display - backup cam incase you dont like camera2
the app is in beta stage so expect a few bugs..
rounded corner in settings/display
font chooser in settings/display
when applying a font and does not work after tapping set, just reboot manually, apply same font again, then reboot agiain.
wifi pass in settings/display
autorun manager in settings/display
terminal app
2nd option to choose default write disk
TO SET DEFAULT ENTRY
OPEN ROM.ZIP
NAVIGATE TO install/data/
extract SDPath file
open using notepad++ or similar program
choose value according to your needs
default = 0
values:
0 = data will be written on phone memory
1 = data will be written on external sdcard
drag and drop SDPath file back into the rom.zip and flash
if you decided to change to ext-sdcard just navigate into /data/SDPath
edit using esfile explorer or similar app and save
then go to settings/storage and match your setiings
reboot
HERE'S THE TRICK
TURN ON BATTERY SAVER, I BET YOU'LL BE AMAZED!!
Installation Instructions:
UMI LONDON
Full wipe (System, Cache, Data, Dalvik/ART cache)
Flash ROM
reboot
UMI LONDON 5002W
Full wipe (System, Cache, Data, Dalvik/ART cache)
Flash ROM
flash firmware patch (link above)
reboot
AOSP 7.1.1 - <i have lost my files due to corrupted harddisk so i will release different updated version of aosp>
screenhots:
AOSP 7.1.1 FINAL​
link here
gcam as default camera
enabled ambient display by default
added useful magisk modules for rom performance
..more..
how to:
goto recovery
wipe everything except ext-sdcard
flash rom.zip
reboot system
install kernel adiutor and busybox
run k.a
under CPU, change CPU GOVERNOR - ondemand ---for best deepsleep
credits:
xda
4pda
aosp
Ninnix96
SnowCatPDA
@deletescape
@topjohnwu
fordza - for sharing the kernel
vo-1/a-1 - who compiled the kernel 3.18.35 for london
feravolt
@kishorerprem
fxsheep
for the magisk modules​ @veez21 -art optimization
@Jman420 -selinux permissive script
@korom42 -simple init.d enabler​

Link is dead
Can you re-upload?

lamensje said:
can you re-upload?
Click to expand...
Click to collapse
link updated. Rom updated.

ian97 said:
link updated. Rom updated.
Click to expand...
Click to collapse
Thanks! I will try it out.

Hi! Thanks for the rom. Looks real nice!
However, I'm getting the screen blinking with v2.1, it flashes on and off about every second. I've tried reflashing, disable auto brightness and GPU options in developer menu. Is there any fix?

GiantChicken said:
Hi! Thanks for the rom. Looks real nice!
However, I'm getting the screen blinking with v2.1, it flashes on and off about every second. I've tried reflashing, disable auto brightness and GPU options in developer menu. Is there any fix?
Click to expand...
Click to collapse
sorry about that. but do you happen to flash this rom on 5002W london variant?

updated op notes. sorry about not mentioning this rom is for non 5002W variant.

@GiantChicken @lamensje
v2.3 available for download. skipped v2.2 i forgot to upload this before..

ian97 said:
@GiantChicken @lamensje
v2.3 available for download. skipped v2.2 i forgot to upload this before..
Click to expand...
Click to collapse
Thanks for the update, but I still have the screen flicker sadly.
I don't know which model Umi London I have (I don't know where I can find it).
I didn't do a clean install from 2.1 to 2.3 (maybe that's why there still screen flicker?).
I tried the '5002w_patch', no change.
Any suggestions?

lamensje said:
Thanks for the update, but I still have the screen flicker sadly.
I don't know which model Umi London I have (I don't know where I can find it).
I didn't do a clean install from 2.1 to 2.3 (maybe that's why there still screen flicker?).
I tried the '5002w_patch', no change.
Any suggestions?
Click to expand...
Click to collapse
full wipe is needed to flash this rom. but if the screen still flickers then you are having a kernel issue. meaning 3.18.35 compiled by vo-1 isnt for your device (5002w variant) ..i really am still confused about this phone because one of the member of my site with 5002w london reported that the ROM (aosp 7.1.1) is working fine on him only the camera focus isnt working but working for me.

Hi.
com.android.phone has stopped after clean flash of any version linked in OP. Either with sim inserted during phone setup or after. Tried typical solutions cleaning caches etc, nothing helps. I noticed it dowloaded some messed up apn settings, so I added my provider settings and same story. SIM is working in another phone andprocess is crashing with other sims too.

Is it mt6580?

Eazart said:
Is it mt6580?
Click to expand...
Click to collapse
Yeah it is, and stock firmware is : MP_mt6580_w370_5002w_91umi_cc_64gbitp8d3_m_wcdma_mul_20170725-115119_songlixin_PC

hideo86 said:
Yeah it is, and stock firmware is : MP_mt6580_w370_5002w_91umi_cc_64gbitp8d3_m_wcdma_mul_20170725-115119_songlixin_PC
Click to expand...
Click to collapse
Is it twrp flashable? I want to port it to my device mt6580 kernel 3.18.35

Eazart said:
Is it twrp flashable? I want to port it to my device mt6580 kernel 3.18.35
Click to expand...
Click to collapse
Original firmware flashed/reflashed through sp flash tool , roms from this topic- TWRP, I didn't try original=> twrp.
edit; and yes , same kernel

hideo86 said:
Original firmware flashed/reflashed through sp flash tool , roms from this topic- TWRP, I didn't try original=> twrp.
edit; and yes , same kernel
Click to expand...
Click to collapse
Will port to my device soon any known bug?

This is what keep coming up when I port this Rom... How can I fix it?

I am trying to install any of the AOSP roms to Umi London (Umidigi W5002), no success. I was on stock 20170725, then installed TWRP and tried any of the AOSP versons, but is goes to infinite bootloop.
Bootloop is caused with and without the W5002 patch).
Recovery and fastboot are working perfectly. I OEM unlocked the stock rom from dev.options and thru fastbot, just to mention. Any solution or advice wil be helpful. Thanks.

Hello guys!! As i can remember i dont have any issue with the dialer. If you want a clean port with this rom grab the latest aosp 7.1.1 by snowcatpda (google his name and youll see his site where he put his roms for mt6580) then grab my port aosp 7.1.1 final's files -- framework-res, settings.apk systemui.apk..
This rom works fine with enforcing, permissive is likely making the rom unstable but with this init.d works well.
My umi died few months ago- cracked screen, wet hardware. So i can no longer help you guys.

[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 DualBootPatcher​And 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.

[10] LineageOS 17.1 for z3c

{
"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"
}
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* 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.
*/[/COLOR]
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation instructions
Prerequisites:
Unlocked Sony Xperia Z3 Compact
Fastboot drivers to install TWRP
Micro-USB Cable to connect your phone to your computer
Install:
Reboot to TWRP. *
Wipe cache, dalvik cache, data and system.
Install ROM.
Install 10.0 Gapps for ARM. **
* recommended TWRP: Post #2
** optional, opengapps
Downloads
Download the ROM
Over the Air Updates
To use OTA updates please read Post #2
Sources
DEVICE:
https://github.com/LineageOS/android_device_sony_z3c
https://github.com/LineageOS/android_device_sony_msm8974-common
https://github.com/LineageOS/android_device_sony_shinano-common
KERNEL:
https://github.com/LineageOS/android_kernel_sony_msm8974
Addons
OpenGapps
Magisk
Thanks
Whole LineageOS Team for this amazing ROM
@koron393
@SpiritCroc
@Myself5
@nailyk
@drakonizer
@rcstar6696
@tomascus
I hope I haven't forgot anyone
Bugs
Current hardware support state: Gist
WHAT'S BROKEN
You tell me.
XDA:DevDB Information
LineageOS 17.1 for z3c, ROM for the Sony Xperia Z3 Compact
Contributors
NeoArian
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: 23.5.A.1.291
Based On: AOSP
Version Information
Status: Beta
Created 2019-10-02
Last Updated 2020-01-04

OTA and TWRP recovery
Over the Air Updates
My upload script automatically pushed OTA updates to my GitHub.
If you want to make them visible through the Updater you can flash the attached magisk module LineageOS-17.1_z3c-OTA-v1.zip or add the line
Code:
lineage.updater.uri=https://raw.githubusercontent.com/ArianK16a/OTA/lineage-17.1/z3c.json
manually to your build.prop. You should use the recommended TWRP so that the updates flash fine.
TWRP recovery
TWRP 3.3.1 for our z3c with Android 10!
The TWRP for Android 10 is attached to this post.
Source is available at: https://github.com/z3c-pie/twrp_device_sony_z3c/tree/android-10.0
Changelog for twrp-3.3.1-1-z3c-20191212-sar.img
Improved System as root support, /system is a symlink to /system_root/system now
Changelog for twrp-3.3.1-1-A10.0-z3c.img
Added Bootlogo, booting from offline state will display the original sony logo now instead of nothing
Fixed fastboot boot
Updated kernel cmdline from 23.5.A.1.291
How to install this build:
Reboot to fastboot by holding volume up while connecting your device to your computer
Open a terminal and move to the directory with TWRP in it
Rename the downloaded image to twrp.img
Type
Code:
fastboot flash recovery twrp.img
Boot into TWRP while the device is powered off press the power and volume down button
Feel free to ask questions or give feedback about TWRP here .
Have a nice day!
Additional information about the recovery on this device:
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this method to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
Click to expand...
Click to collapse

The new build is up!
Get it from here: https://sourceforge.net/projects/ep...age-17.0-20191002-UNOFFICIAL-z3c.zip/download
Make sure to use the new TWRP from Post #2 because Android 10 introduces System-as-Root which can lead to weird behaviour in the old TWRP.
Note that there are not all features from LineageOS 16.0 ported over yet and there can be unexpected, yet unlisted bugs.
MY personal hardware support list can be found here: https://gist.github.com/ArianK16a/1e46c463a5c910efb322d9cf0e16c3c0 but as always, i can't guarantee you anything!
Happy flashing!

I will try, thx :>
but there are no opengapps for 10,
what about this? will be good?
https://www.cyanogenmods.org/download-gapps-for-android-10/

hah ok now I don`t know anything... ;/
still same problem with this freakin camera and torch exactly like in v16
all my steps:
1.
flashtool64 -> Stock Android 6.0.1 for D5803 - 23.5.A.1.291 - Unbranded - Baltic Generic (1288-5413)
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
2.
TWRP for 6.01 - with this https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Kernel .575 -> recovery for mm575 ->kernel .291
3.
installation of yours TWRP - twrp-3.3.1-A10.0-z3c
4. in twrp 3.3.1 wipe cache, dalvik cache, data and system, rom installation
5. camera and torch doesn`t working ;/ "camera keeps stopping" and torch is greyed out

NIce, thank you

hhpl said:
hah ok now I don`t know anything... ;/
still same problem with this freakin camera and torch exactly like in v16
all my steps:
1.
flashtool64 -> Stock Android 6.0.1 for D5803 - 23.5.A.1.291 - Unbranded - Baltic Generic (1288-5413)
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
2.
TWRP for 6.01 - with this https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Kernel .575 -> recovery for mm575 ->kernel .291
3.
installation of yours TWRP - twrp-3.3.1-A10.0-z3c
4. in twrp 3.3.1 wipe cache, dalvik cache, data and system, rom installation
5. camera and torch doesn`t working ;/ "camera keeps stopping" and torch is greyed out
Click to expand...
Click to collapse
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
hhpl said:
I will try, thx :>
but there are no opengapps for 10,
what about this? will be good?
https://www.cyanogenmods.org/download-gapps-for-android-10/
Click to expand...
Click to collapse
There are GApps: https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/

NeoArian said:
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
Click to expand...
Click to collapse
ok I had something in my head that I needed first this marshmallow recovery... I don`t know why
but now I flashed once again 291 and then yours twrp and wiped all the stuff ofc included data and still torch and camera doesn`t work ;/

hhpl said:
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
ok I had something in my head that I needed first this marshmallow recovery... I don`t know why
but now I flashed once again 291 and then yours twrp and wiped all the stuff ofc included data and still torch and camera doesn`t work ;/
Click to expand...
Click to collapse
Format is not wipe. Make sure that twrp asks you to confirm by typing yes.

NeoArian said:
Format is not wipe. Make sure that twrp asks you to confirm by typing yes.
Click to expand...
Click to collapse
ok done, once again nothing new, still same situation

Can this ROM be installed on top of LineageOS 16 without wape?

Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks

marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
Are you talking about the GApps I posted a few posts back? https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/ If I remember correctly I didn't have problems while I tested them...

NeoArian said:
Are you talking about the GApps I posted a few posts back? https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/ If I remember correctly I didn't have problems while I tested them...
Click to expand...
Click to collapse
No, I found a beta version on Google.
Gotta check again with the one you provided, I'll edit this post in a while
Edit: buttons don't work again

marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
wow, so what I`m doing wrong... could you tell me how you install this rom step by step and what rom you had before? steps before installation and steps after or something, I have installed this rom 10 times and never got my camera work, that is crazy

hhpl said:
wow, so what I`m doing wrong... could you tell me how you install this rom step by step and what rom you had before? steps before installation and steps after or something, I have installed this rom 10 times and never got my camera work, that is crazy
Click to expand...
Click to collapse
The same basic steps you'll find in the OP

marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
I've experienced the same issue after installing gapps - only back button works. Gesture navigation is working fine.
Other bugs I've noticed:
-battery icon style cannot be changed
-launching camera app with hardware button doesn't work
-system accent color cannot be changed (there is only one option listed)

Barciej33 said:
Other bugs I've noticed:
-battery icon style cannot be changed
-launching camera app with hardware button doesn't work
-system accent color cannot be changed (there is only one option listed)
Click to expand...
Click to collapse
You must read 1st to 3rd post.
LOS17 is just getting started.
Note that there are not all features from LineageOS 16.0 ported over yet and there can be unexpected
Click to expand...
Click to collapse

@NeoArian Any chance for a screen recording of how it runs?

JamesMars said:
@NeoArian Any chance for a screen recording of how it runs?
Click to expand...
Click to collapse
No? If you are interested you can test it yourself.
I have my holidays now anyway.