Database Info

[MOD][Z3C] MultiROM v33x

{
"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"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. 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, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
WARNING
It is dangerous. 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 and you will have to flash factory images again. Make backups. Always.​
IMPORTANT
I'm not responsible for anything, you do all this on your own risk.
Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to "Advanced -> MultiROM" to flash ROMs/kernels or other mods.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
I am not certainly sure about the compatibility with stock Roms, I still need to test this yet.
Your device must not be encrypted.
To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernels to add MultiROM support to your ROMs.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
Make sure you are on a Rom compatible with one of these kernels and flash it
Reboot into MultiROM TWRP and flash the MultiROM installer
That's it. You can now go to "Advanced -> MultiROM" to start flashing other ROMs.
Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. 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 USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
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.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/ (branch master)
Modified TWRP - https://github.com/XperiaMultiROM/android_bootable_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/Myself5/android_kernel_sony_msm8974/ (M5-Kernel)​
FAQs can be found here.
CREDITs
Tasssadar
Olivier
Garcia98
Thunder07
skin1980
Envious_Data
[NUT]
AndroPlus
Panic Brothers
If you think I deserve a donation, I won't stop you
Thanks a lot to those who have donated!​
You might want to consider a Donation to Tasssadar, who is the Mastermind behind all of this, I just ported it to the Z3C
​
XDA:DevDB Information
MultiROM for Sony Xperia Z3 Compact, Tool/Utility for the Sony Xperia Z3 Compact
Contributors
Myself5
Source Code: https://github.com/XperiaMultiROM/multirom
Version Information
Status: Testing
Created 2015-05-22
Last Updated 2016-06-06

CHANGELOGs
General MultiROM Changelog can be found here:
Changelog
XperiaMultiROM Specific Changelog is here:
Recovery Changelog
MultiROM Changelog
DOWNLOAD
https://dl.myself5.de
The recovery.img is Tassadars modified TWRP to flash secondary Roms. It is needed to flash the secondary Roms.
SUPPORTED KERNELs
M5-Kernel-L (starting with V2)
AndroPlus Kernel (starting with V19)
If you want your favorite kernel to support kexec tell the dev to merge my commits.

Reserved
General Informations about Kexec are coming here soon.

I have encountered problems with secondary rom flashing. First try your test carbon rom boot loop, second try restore back up of stock rom failed, third try fresh install of a stock rom failed, fourth try pac rom with your m5 kernel flashing ok but will not start
my primary is cm12.1 with your kernel

me too.
primary rom is stock LP 23.1.A.1.28 with androplusV55
i succeeded installing second rom being CM12.1 nightly build
first without gaaps cm12.1, as per selecting the rom from the romlist in twrp and choosing flash zip
then tried deleting it and added the rom again, this time i flashed gapps as per selecting the rom from the romlist in twrp and choosing flash zip
is gapps required to load cm successfully at all?
When selecting cm12.1 at the multirom boot menu it reboots and only shows the internal (stock) rom and boots just fine.
then i was thinking about doing the swap rom from twrp or perhaps flashing cm12.1 as primary and having stock as secondary.
or perhaps flashing cm12.1 from scratch and then add stock sony as secondary via an old backup
but then i stumbled into this thread http://forum.xda-developers.com/showpost.php?p=60906102&postcount=129
i used multirom twrp which is inbuilt in andrplusV55, not the one from myself5's dl site!
-androplus is stock only supporting
-m5 kernel is only cm12 supporting
and i coulnd't find the way to choose de-select kernel for secondary rom as found somewhere else
what a dilemma

New Version is online!
I just uploaded a new Version. I figured out that I used the wrong flags so booting Secondary Roms which don't boot with the primary kernel were not working. However, they do now (I booted 5.0 on a 5.1 Host System just to get sure).
Again, terribly sorry, but new version is up now
Also huge thanks @funiewski for the donation

Important
Just one question
now say i flashed CM 12 as a second ROM
when i boot to it , will apps which i already installed on the stock appear their ??
in other words , does the each ROM affect the other one ?? like if i put something on internal storage will appear on the other ROM ??

Myself5 said:
I just uploaded a new Version. I figured out that I used the wrong flags so booting Secondary Roms which don't boot with the primary kernel were not working. However, they do now (I booted 5.0 on a 5.1 Host System just to get sure).
Again, terribly sorry, but new version is up now
Also huge thanks @funiewski for the donation
Click to expand...
Click to collapse
nice one, indeed.
but i still had the same issue, couldn't load cm og pac as secondary rom
i had androplusV55, now i've updated to androplusV57, and it's working like a charm.
apperently it was a kernel issue
ps. noticed that gapps are required so it doesn't share apps i think?
not in my case though, hence im running stock rom as primary
probably M5 kernel can be flashed as well, as long as it is flashed through mulitrom twrp from listed roms, like update tutorial for secondary rom in OP
thanks very much

Hey freaks,
I think there is something to explain.
The first Thing you have to do and this is one of the most important thing:
Donate to Myself5 or even "Thankyou"
Because you must know, this Multirom MOD is very sensitive like a young good looking girl and it can feel a donation...and works even better after a Thank you
Remeber we are here in Z3 "Compact" Area you can NOT choose a Main Kernel for Z3 or other Xperia Models.
The Main Kernel must support kexec-hardboot (support for MultiROM), for Z3 Compact
The best way to get all to work is:
-Backup all you ROMs you have right now on your Device "Remeber Z3 "Compact"
-Save this to your SD Card
-clean your Phone
-Install CM12.1 latest Nighty
-boot one time and check if you have a Plain CM12.1 (LP 5.1.1) System. Now you have Cm12.1 and the Cyanogen Recovery on your Phone.
-Copy the File "multirom-20150524-v31x-UNOFFICIAL-aries.zip" and "multirom-20150522-v31x-UNOFFICIAL-aries.zip.md5sum" to your SD Card
-Shutdown your Phone and boot on Bootloader Mode (Press and hold Volume Up Button and insert USB Cable) a Blue LED appear now.
-Go with a Terminal in Administrator Mode in your ADB Folder with fastboot. (Windows PC)
-Copy one of the M5 V6 Kernel in the fastboot directory and copy the File TWRP-Multirom-20150524-00-z3c.img in the same directory
-type "fastboot devices" now you see your device is connected
-Now type "fastboot flash boot boot.img" <-- Boot .img is the M5 V6 kernel, you find in the release Zip Files from Myself5
-Now type "fastboot flash recovery TWRP-Multirom-20150524-00-z3c.img"
-Now type "fastboot reboot"
-Your Phone boots now normally and you should press Volume Up or down to enter TWRP MultiRom Recovery...Allmost all is done now.
-In Recovery Mode go to the Normal "Install" Button and choose the File "multirom-20150524-v31x-UNOFFICIAL-aries.zip" and flash this. Now reboot system.
Well done...Multiboot is installed.
Now you can go everytime you like in the recovery Mode and go to the Button Advanced -Multiboot and install other ROMs, like your Backups or CM12 builds.
All your Secondary Roms must be updated over the Advanced- Multiboot- List Roms feature. To update multiboot itself or the Main Cm12.1 Rom you have to flash over the Main install button.
If this is not working, delete Data and flash your Backup again and sell your Z3 Comapct and buy an IPhone. Apple take care of all your Data
Panic Brothers
-

@Myself5 some problems when restoring backup of stockrom with androplus kernel as secondary. file attached

edit :solved couldnt figure how to flash gapps , rooky mistake but figured it out ....u go to advanced tab in twrp/multirom/list rom/flash zip

First time using multirom, working perfectly. Have carbon, candy5 and another rom I'm testing all booting as expected, awesome work.
Official support from the multirom app would be a bonus [emoji33] [emoji106]

Oh, totally forgot about the app. It's coming next ofc, just need to setup the z3c folder on my server.
Sent from my Xperia Z3 using Tapatalk

Work with stock rom???
---------- Post added at 03:39 AM ---------- Previous post was at 03:35 AM ----------
AnGrY sCoTsMaN said:
First time using multirom, working perfectly. Have carbon, candy5 and another rom I'm testing all booting as expected, awesome work.
Official support from the multirom app would be a bonus [emoji33] [emoji106]
Click to expand...
Click to collapse
Ey bro on candy5 do you have full connection when you connect your cel into pc?

chikrron said:
Work with stock rom???
---------- Post added at 03:39 AM ---------- Previous post was at 03:35 AM ----------
Ey bro on candy5 do you have full connection when you connect your cel into pc?
Click to expand...
Click to collapse
you can have stock as primary with androplus kernel, I couldn't manage to have stock as secondary

Ok bro thanks for the tip I'll try later

Hi
So I installed your MultiROM together with the M5-Kernel and cyanogenmod. Afterwards I flashed the modified TWRP recovery. However TWRP has issues to mount my external sdcard (32 GB), its just shown as 0 MB and its not possible for me to re-partition or format it.
- It says "auto" as its file system
- Its formated as FAT32 (tried extFat too)
- This sdcard was taken over from my old i9300
Edit:
Seems I fixed it by booting into cyanogenmod and going under Settings/Storage and select "delete sdcard" down there. Strange.....
Anyways. Thanks for your work!

myself5.de is down
In Case someone noticed my server being down:
I am aware that my server is down, it got suspended by an Admin and I need to figure out why (I have not done anything forbidden, last thing I did was trying to setup an instance of Gerrit Code Review) that however is not that easy cause the server is sponsored and I only have access to the SolusVM Panel, I can't create Support tickets, so I now need to wait for my sponsor to answer me. Stupid as I am I don't have a mirror, cause I did not set up one yet... I hope someone can upload the latest Version and post a link here, would be greatly appreciated.
Regards
Myself5
EDIT: Server is meanwhile back. Thanks to everyone who provided a temporary link

Installing Roms on SD Card and External Memory
Hey guys, I was finally able to figure out a fix for the Roms not being able to boot from SDCard/external USB drives. I'm currently compiling a new build and it will be uploaded as soon as it's done, MultiRom Manager will get updated automatically too.
Progress on compiling can be seen here:
http://myself5.de:12345/job/XperiaMultiROM/37/console
Please be aware that booting Roms from SDCard/USB Media might take a bit longer than Roms installed on the internal Storage due to slower read/write speeds.
Regards

Myself5 said:
Hey guys, I was finally able to figure out a fix for the Roms not being able to boot from SDCard/external USB drives. I'm currently compiling a new build and it will be uploaded as soon as it's done, MultiRom Manager will get updated automatically too.
Progress on compiling can be seen here:
http://myself5.de:12345/job/XperiaMultiROM/37/console
Please be aware that booting Roms from SDCard/USB Media might take a bit longer than Roms installed on the internal Storage due to slower read/write speeds.
Regards
Click to expand...
Click to collapse
@Myself5 how about multirom app,can it work for aries?

[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.

[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.

[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [I9515][I9515L]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
​
Code:
* [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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 us for messing up your device, we will laugh at you.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)​Q: Whenever I try flashing any lineage-15.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.2. Simply flash version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
Q: Why is my phone warmer/hotter and the battery noticeably drained after flashing a build?
A: The wipe process that is a part of the installation procedure deletes some important configuration data, ie. BATTERYSTATS, which keep track of the battery's power level. These data ensure a balanced power management profile for all the hardware components of your phone. This is normal and nothing to worry about at all. Your battery drain will return to normal within a day or two.
If, however, you notice increased battery drain over a few days, check your signal. Android automatically re-directs battery power to the antennas to compensate for a weak signal from the tower to which your phone is connected at that time. If your signal is strong, check the following:
1) You missed one of the Wipe steps in the flashing procedure.
2) You are running an old bootloader or modem. Flash the most recent one listed for your variant either under the links below. Note: Use the "AP" button in Odin to flash ripee's combined BL_CP tar files.
3) How old is your battery? Official replacement Samsung batteries typically last around 1 year if you recharge them regularly, ie. once a day. Since the Galaxy S4 Value Edition over 4 years old, it is normal for your original battery to start failing, but official Samsung batteries should not cost more than USD 20 nowadays.
4) If all else fails, start over! Go through the entire installation procedure, including flashing a stock Marshmallow build, and going from there. Do NOT skip any steps this time!
Q: Will the jfvelte ever receive official builds from LineageOS?
A: In short, no. The reason is that, in order to get a modern version of Android working properly on an ageing device, some recent commits needed to have been reverted and some legacy commits needed to have been re-introduced into the current source branch. These include a fix for something as fundamental as video recording with both the AOSP and 3rd party camera apps.
Q: How often will new builds be released?
A: At least once per month: as soon as possible after each new Android security patch level is merged and whenever a new feature is added or a bug is fixed.
If the first Oreo build you are flashing is 0220 or later, please clean flash it, as some users have reported problems with dirty flashing builds from 0220 or later over top of builds older than 0220.​
ROMs
Exodusnick
Build files downloaded with the OTA updater can be found in /data/lineageos.updater. New builds are released weekly.
-
YouTube Video
Magisk
recommended Gapps Pico or Nano ARM 8.1
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of LineageOS 15.1!​
How to flash LineageOS and Open GApps​FULL WIPE (with external microsd card)
1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the external MicroSD storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with NO Home PC access)
1. Move any files you want to keep to a safe folder - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with Home PC access)
1. Move any files you want to keep to your Home PC - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibrate),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
13. Once first boot is completed you can safely move your files back onto your Internal Storage.
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation​1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
Bluetooth calls
- You tell us!
Changelog
All major features and bug fixes are discussed by Exodusnick and ripee in this thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- sombree and every other open source developer and tester who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the jfvelte.
Join us on Telegram[/URL], courtesy of Exodusnick!​
Sources
XDA:DevDB Information
LineageOS 15.1, ROM for the Samsung Galaxy S4
Contributors
Exodusnick
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: Stock KitKat for your variant.
Version Information
Status: Stable
Current Stable Version: 8.1.0
Stable Release Date: 2019-05-17
Created 2018-12-29
Last Updated 2019-06-19

Reserved

Reserved

deleted

Thanks . Can you please build rom with Android GO configuration enabled because I think it will improve performance of this device.

adarshadhungel1 said:
Thanks . Can you please build rom with Android GO configuration enabled because I think it will improve performance of this device.
Click to expand...
Click to collapse
You are no doubt correct, but at this stage we are re-building the sources in the lineage-15.1 branch, for which there are currently none. Once we figure that out, we'll take a look at Go.

wifi is not working.
Is there a workaround for it ?

blunatic said:
wifi is not working.
Is there a workaround for it ?
Click to expand...
Click to collapse
Read the OP please. This rom is a WIP.

hello I have this very good equipment the update towards lack since android already goes for its version 9 if I would like to know the wifi for when it will be?? thanks.

hello such thanks for the contribution, the following when I try to install I do all the procedure as it appears in the indications, but when restarting the phone freezes in the logo of lineage and re-start from there does not pass does not arrive nor to how to configure the rom that can be due?

Kelbimiguel said:
hello such thanks for the contribution, the following when I try to install I do all the procedure as it appears in the indications, but when restarting the phone freezes in the logo of lineage and re-start from there does not pass does not arrive nor to how to configure the rom that can be due?
Click to expand...
Click to collapse
Which build did you try installing?

Don't installation
with this ROM I observed that it is the most recent

lineage-15.1-20181226-UNOFFICIAL-jfve "this rom does not install"

Kelbimiguel said:
lineage-15.1-20181226-UNOFFICIAL-jfve "this rom does not install"
Click to expand...
Click to collapse
Ok thank you for your feedback. I will delete this build.
When I am ready with another build, I will let you know.

Installed
Ready installed and running, wifi does not work or read the Micro SD, I'm still trying ...

Kelbimiguel said:
Ready installed and running, wifi does not work or read the Micro SD, I'm still trying ...
Click to expand...
Click to collapse
Yes, this build works, unfortunately we lost the copy of the sources, and I'm trying to re-create exactly what we did to make 1208 work.

lineage-15.1-20181226-UNOFFICIAL-jfvelte.zip

hello install the rom that you just published the lineage-15.1-20181226-UNOFFICIAL-jfvelte.zip and when installed, the screen does not react to touch it, you can not configure or do anything...

Kelbimiguel said:
hello install the rom that you just published the lineage-15.1-20181226-UNOFFICIAL-jfvelte.zip and when installed, the screen does not react to touch it, you can not configure or do anything...
Click to expand...
Click to collapse
Yes, I suspected as much, this is a known bug. I will keep working on it.

delete my thread immediately thank you ........