Related
NOTE:
This will be my last GB rom since sources for Galaxy S Advance has been released, I'll by making a JellyBean port of the SGSA to the Ace 2. Unless Sammy releases JB to our phone. I'm also going to buy Galaxy S Advance or the Galaxy S III mini(not available yet here in HK execpt the parallel ones and in expansys.com.hk) to replace my Ace 2.
Introduction:
First of all, I made this ROM specifically for the Galaxy Ace 2 GT-I8160 with a baseband of ZSLG1/ZSLK2 which is from Hong Kong.
The reason I made this ROM started with a severe scrolling problem with all Galaxy Ace 2 here in Hong Kong installed with the I8160ZSLG1 firmware, scrolling continuously is not possible because as soon as you scroll while the menu list is still moving or scrolling, touchscreen becomes unresponsive, unless you re touch the screen. this ROM has no BusyBox installed, its just a stock ROM with same UI, same funtionality
UPDATE V3:
Sorry for the late responses. I've been busy working here in my company. Anyway, this will be my last GB rom since sources for Galaxy S Advance has been released, I'll by making a JellyBean port of the SGSA to the Ace 2.
Original Stock ROM I8160ZSLK2(Hong Kong)
GT-I8160V3
Link to Stock XXLK7 Kernel with CWM and init.d support
List of Changes:
NEW
-based on I8160XXLK7
-permanent removal of CPU rendering, uses GPU rendering by default.
-init.d support
--place your favorite init.d tweaks inside /system/etc/init.d
-busybox 1.19.4/ZipAlign/Sqlite3(compatible with the newest Supercharger V6)
-deleted some unneeded files from lib folder.
Recent Changes
-all language files are for UK, so there's no chinese, but if you know english, that would be fine
-multi tap alphanumeric keypad bug fixed
-scrolling bug fixed
-STOCK UI(Same functions, same look and feel)
-Zipaligned APK's before packing
-Deodexed
-Rooted
-disabled ScrollingCache for smooth scrolling(modified framework.jar, not a build.prop tweak)
-disabled all camera sounds including autofocus
-Samsung bloatwares REMOVED
NOTE:
It is recommended to flash the kernel from the link provided above.
Installing instructions:
-make a backup of your phone
-flash the stock ZSLK2 firmware
-flash the kernel from the link provided above
-format /data, /cache and /system(THIS WILL DELETE ALL YOUR SETTINGS AND DATA)
-wipe dalvik cache
-wipe battery stats
-unmount all volumes
-flash the ZIP file and wait it to finish
-reboot(startup takes long time since dalvik is being rebuild)
-when booting is done, setup your phone, language, time, etc.
-before installing apps, reboot phone
-then you can start installing your apps
NOTE:
-Kies over Wifi is removed, clicking on it from the menu will force close the settings application.
-Don't attempt to flash this ROM to a different baseband, your phone will still work but you will not have a GSM/3G/Network signal.
WARNING APPLIES ONLY TO V1 and V2:
WARNING: BusyBox is partially supported using the busybox installer, however, there are many chances that it will make your device bootloop.
Version 2:
Original Stock ROM ZSLG1(Hong Kong)
GT-I8160V2
XXLI2 stock kernel
Version 1:
DOWNLOAD:
CWM_flashable_ROM
all credit goes to dsixda for the android kitchen
sorry, dumb question again.
in cwm menu, i don't see option to unmount volume, so how could i do that??
edit: found it in "mount and storage", sorry.
Everything seems running just fine, but the battery graph seems broken (gaps in between) in battery status??
---------- Post added at 11:28 PM ---------- Previous post was at 11:14 PM ----------
and the chinese character in your rom is simplied chinese (GB) while i use tradional chinese (BIG5).
Could you list the files responsible for those tradional chinese chars and i put it back to system via sort of root explorer??
Thank you.
How do we flash the stock rom back ? Do i need to wipe cache again and stuff?
And what do i choose in odin? cuz the file is just one.. and it asks for bootloader and etc?
Bocko92 said:
How do we flash the stock rom back ? Do i need to wipe cache again and stuff?
Click to expand...
Click to collapse
The stock rom provided here is for flashing with odin (select "pda" in odin, and select the .tar file)
I'm not sure if it is needed for odin, but if you flash rom with clockwork mod, then wipe /data, /system, and /cache is a must. just as the instruction stated, wipe these 3 partitions, then format it and umount them.
Bocko92 said:
And what do i choose in odin? cuz the file is just one.. and it asks for bootloader and etc?
Click to expand...
Click to collapse
In odin, select pda and then select the .tar file you downloaded. DO NOT touch anything else. then click start.
** Please correct me if I'm wrong. **
xmlnoob said:
Everything seems running just fine, but the battery graph seems broken (gaps in between) in battery status??
---------- Post added at 11:28 PM ---------- Previous post was at 11:14 PM ----------
and the chinese character in your rom is simplied chinese (GB) while i use tradional chinese (BIG5).
Could you list the files responsible for those tradional chinese chars and i put it back to system via sort of root explorer??
Thank you.
Click to expand...
Click to collapse
doesn't seem to have the battery problem on me though, take a look at the screenshot, for the languages, sorry I think its from the CSC files, you can try flashing a CSC provided on my original ROM, but I don't know what effect does it have when flashed, I didn't add any language since I don't read chinese, thou I live here in Hong Kong
anyway, I'll try extracting the language traditional chinese and will make a CWM flashable file.
Anyway, the reason why I have low battery life is I use
CPU Governor: performance(only at 800Mhz - no deep sleep, no downclock, CPU always at 800Mhz full speed)
I/O Scheduler: noop
results? no lags in UI or browser. but battery last only 1 day, than 2days using default CPU settings.
kevincaja said:
doesn't seem to have the battery problem on me though, take a look at the screenshot, for the languages, sorry I think its from the CSC files, you can try flashing a CSC provided on my original ROM, but I don't know what effect does it have when flashed, I didn't add any language since I don't read chinese, thou I live here in Hong Kong
anyway, I'll try extracting the language traditional chinese and will make a CWM flashable file.
Anyway, the reason why I have low battery life is I use
CPU Governor: performance(only at 800Mhz - no deep sleep, no downclock, CPU always at 800Mhz full speed)
I/O Scheduler: noop
results? no lags in UI or browser. but battery last only 1 day, than 2days using default CPU settings.
Click to expand...
Click to collapse
Yea, i think the gap is actually the period of hard reboot, so its a false alarm The graph is ok without reboot.
regarding cwm flashable langauge file, i dont need to wipe data/ factory reset for that i assume?
Thank you.
---------- Post added at 08:21 PM ---------- Previous post was at 08:13 PM ----------
And by the way, the phone number(caller id??) format is now showing XXX-XXX-XX, can i edit it to show XXXX-XXXX or XXXX XXXX ??
xmlnoob said:
Yea, i think the gap is actually the period of hard reboot, so its a false alarm The graph is ok without reboot.
regarding cwm flashable langauge file, i dont need to wipe data/ factory reset for that i assume?
Thank you.
---------- Post added at 08:21 PM ---------- Previous post was at 08:13 PM ----------
And by the way, the phone number(caller id??) format is now showing XXX-XXX-XX, can i edit it to show XXXX-XXXX or XXXX XXXX ??
Click to expand...
Click to collapse
no need to wipe, just flash the CWM zip file, the caller ID is a feature of the Indonesian firmware, so we either have to edit some framework or apk's which will take sometime
kevincaja said:
no need to wipe, just flash the CWM zip file, the caller ID is a feature of the Indonesian firmware, so we either have to edit some framework or apk's which will take sometime
Click to expand...
Click to collapse
Arrh, regarding the caller id format, just changed the langauge to "English (UK)" get the job done o7.
xmlnoob said:
Arrh, regarding the caller id format, just changed the langauge to "English (UK)" get the job done o7.
Click to expand...
Click to collapse
yeah it worked, thanks
Have you ever used multimount sd app on rooited ace2?? this little app works fine on my old rooted HTC wildfire but not on ace2.
Wondering if any way to do dual mount on ace2, ie connect to computer as mass storage device while still the sdcard(s) are still mounted on the phone.
Thank you.
xmlnoob said:
Have you ever used multimount sd app on rooited ace2?? this little app works fine on my old rooted HTC wildfire but not on ace2.
Wondering if any way to do dual mount on ace2, ie connect to computer as mass storage device while still the sdcard(s) are still mounted on the phone.
Thank you.
Click to expand...
Click to collapse
haven't tried it yet, but I think it will not work, I guess...
Hey btw, can i use the zip created by this http://uot.dakra.lt/kitchen/ on your rom? i want the battery status in notification bar to show %.
Thank you.
xmlnoob said:
Hey btw, can i use the zip created by this http://uot.dakra.lt/kitchen/ on your rom? i want the battery status in notification bar to show %.
Thank you.
Click to expand...
Click to collapse
Just followed the instruction there and it generated a cwm compatible zip, installed and works nicely.
xmlnoob said:
Just followed the instruction there and it generated a cwm compatible zip, installed and works nicely.
Click to expand...
Click to collapse
I was just about to say yes, but then since you've done it, I'd say good for you!
I8160L can't
sathit2499 said:
I8160L can't
Click to expand...
Click to collapse
this ROM is for the GT-I8160 only.
App Downloading Problem
Hi
Great rom. Quite stable and scrolling works properly now as advertised (I actually thought the broken scrolling was an intentional design and not a bug, but its back to normal now thanks to the rom)
I do have 3 questions / problems though.
1. Not sure if anyone else has this problem, but after flashing, I am unable to install any apps from the google market when on wifi. I can browse the market and websites easily, but the downloading bar never initiates. Once I switch to 3g, the app starts downloading. Before I flashed this rom, wifi downloading of apps from google play worked on the same network.
2. When I enter recovery mode (volume up + home + power) my recovery mode is "Android Recovery 3e" not CWM recovery. As such, I only have the options to flash a .zip or wipe data / cache. Is this normal. I tried flashing Antsm's update_su and it remains android recovery.
3. This is minor. But when I try and use LMT launcher (http://forum.xda-developers.com/showthread.php?t=1330150) with the pie buttons, only the home button works. The other buttons do not. They worked fine before I flashed this mod. Not sure if anyone else has tried LMT with this rom?
4. Will kernels or roms based off of other firmwares work with our HK baseband and still have working scrolling on 3g/phone?
Thx alot for your support for the HK firmware
chzyken said:
Hi
Great rom. Quite stable and scrolling works properly now as advertised (I actually thought the broken scrolling was an intentional design and not a bug, but its back to normal now thanks to the rom)
I do have 3 questions / problems though.
1. Not sure if anyone else has this problem, but after flashing, I am unable to install any apps from the google market when on wifi. I can browse the market and websites easily, but the downloading bar never initiates. Once I switch to 3g, the app starts downloading. Before I flashed this rom, wifi downloading of apps from google play worked on the same network.
2. When I enter recovery mode (volume up + home + power) my recovery mode is "Android Recovery 3e" not CWM recovery. As such, I only have the options to flash a .zip or wipe data / cache. Is this normal. I tried flashing Antsm's update_su and it remains android recovery.
3. This is minor. But when I try and use LMT launcher (http://forum.xda-developers.com/showthread.php?t=1330150) with the pie buttons, only the home button works. The other buttons do not. They worked fine before I flashed this mod. Not sure if anyone else has tried LMT with this rom?
4. Will kernels or roms based off of other firmwares work with our HK baseband and still have working scrolling on 3g/phone?
Thx alot for your support for the HK firmware
Click to expand...
Click to collapse
ANSWERS:
To 1: I to, experiences that problem, still fixing it
To 2: You didn't flash the kernel properly, try flashing a custom kernel again.
To 3: Don't know what launcher is that.
To 4: Yes it will, we only need to copy a some specific files for 3G/GSM/Network to work.
kevincaja said:
ANSWERS:
To 1: I to, experiences that problem, still fixing it
To 2: You didn't flash the kernel properly, try flashing a custom kernel again.
To 3: Don't know what launcher is that.
To 4: Yes it will, we only need to copy a some specific files for 3G/GSM/Network to work.
Click to expand...
Click to collapse
In that case, I'll wait for that wifi fix. Will keep using the this rom in the meantime.
I'll wry about cwm next time I need to flash.
And the launcher problem started working but itself. Don't think it's a rom problem. Thx again!
Sent from my GT-I8160 using xda app-developers app
And again, here I am with the ROM for GT-I8190L
Tweaks:
Code:
- Ext4 Optimization Tweaks
- Many build.prop tweaks
- Battery tweak
- sqlite_optimize
- Darky ziaplign
- V6 120MB LMK Addon
- Bravia Engine
- xLoud Engine
- 4cyl Turbo Engine by [URL="http://forum.xda-developers.com/member.php?u=4741717"]Exit_Only[/URL]
- A lot of Samsung's bloatware removed
Instructions
1. download the zip files
2. put the zip files onto your sd card
3. reboot into recovery
4. flash BenzROM-V2L.zip file from your sd card
5. reboot.
ROM is wipe now for better compatibility. Backup your data before proceeding.
Download Link - ROM V2 <<< Click.
Thanks to Chainfire for his root.
Thanks to leather.face for his script.
Thanks to my country neighbour dariolob for his DMod V3 build.prop tweaks and his mods.
Thanks to Exit_Only for his 4cyl Turbo Engine tweaks, awesome work!
Thanks to vonuzu for his Call Recording mod
Thanks to cheech01 for his StatusBar mods.
ROM has been updated
Added: A custom power menu with Download and Recovery options.
Added: AOSP Lockscreen
Added: Long press back button to kill an app
Added: Automatic Battery Calibration on first flash
Added: Colorized days in S-Planner
Disabled: Contacts joining limit
Disabled: OTA Service and removed "Software Updates" from Settings
Disabled: Phone number auto-formatting
Enabled: Sub-symbols on stock keyboard - Long press to insert symbol
Enabled: Scheduled messages in stock SMS app
Enabled: MMS download even with data off
Enabled: Folders for messages
Modded: In-call vibration for notifications enabled
Modded: Inverted email app from black to white - much more readable
Modded: No MMS conversion,no contact limit, real timestamps with sent time instead of received
Modded: Added camera shutter sound toggle in settings
Modded: Camera is now available during a call
Modded: Enabled emojis in stock browser
Modded: Added confirmation prompt when exiting from browser
Modded: Added "Exit" button to browser in menu
Modded: Home browser page instead of about:blank when opening a new tab
Fixed: SuperSU root not working after flash
Fixed: Some scripts not working properly
Fixed: Radio not working for some users after flashing
Fixed: Auto-Wipe will NOT wipe your internal storage anymore
Changelog
Code:
- Updated 4cyl Turbo Engine to v0.3.2_r1
- Completely redid the updater-script (Thanks to [URL="http://forum.xda-developers.com/member.php?u=4741717"]Exit_Only[/URL] for his help)
A Reminder!
Please don't send me PMs about tech support! If you do, they will be ignored and deleted immediately. Ask your questions here.
Awesome! Thanks! I'm at work right now but will test it tonight.
Hello...This it a amazing work. I have a question... I install this rom perfect, but i change the dpi to 170. In this case everything works perfect but the skin for dial can't arrange to the new format...Exists some way to fix this ? Thanks you...
Flashed. All great. Lost root at first but flashed the file and all is well. Thank you very much!
I have one question. I mean I backed up, and all is fine but my internal sd card got wiped, unlike it should. Is that part of your wiping process or is it something with the s3 mini. Just for future reference.
DAMADRIC said:
Hello...This it a amazing work. I have a question... I install this rom perfect, but i change the dpi to 170. In this case everything works perfect but the skin for dial can't arrange to the new format...Exists some way to fix this ? Thanks you...
Click to expand...
Click to collapse
No there's no way to fix this
swagmeister said:
Flashed. All great. Lost root at first but flashed the file and all is well. Thank you very much!
I have one question. I mean I backed up, and all is fine but my internal sd card got wiped, unlike it should. Is that part of your wiping process or is it something with the s3 mini. Just for future reference.
Click to expand...
Click to collapse
My wiping process wipes /data and /cache partitions and nothing else. I don't know what that was.
ROM updated, first post updated.
Hello.
Thanks for your time and work...Looks amazing.
I solve the problem with the dpi dialer installing a exdialer from google play, and work excellent...
In another point i reinstall the update for this rom ,but when this finish i begin and dont show the activity for phone, nothing appear to introduce the sim code and the phone its deactivate...Its this normal ?
Thanks Doug...
Is your network working, can you call, send text messages?
yes, with the file before , i installed and everything its ok, with this i can't use the phone services...
Im from Costa Rica, what its the exactly rom or baseband, that i need to install to work ok with 850 3G line. Or what it the correct baseband stock rom that i need to download to work normally...
Help please....
Benzonat0r said:
My wiping process wipes /data and /cache partitions and nothing else. I don't know what that was.
Click to expand...
Click to collapse
Damn that's wierd. I'll be more carefull next time.
New version? Sweet! Thanks
DAMADRIC said:
yes, with the file before , i installed and everything its ok, with this i can't use the phone services...
Click to expand...
Click to collapse
I didn't do anything drastic to the ROM I've just added some symlinks to make root and some scripts work.
It should work.
Benzonat0r said:
I didn't do anything drastic to the ROM I've just added some symlinks to make root and some scripts work.
It should work.
Click to expand...
Click to collapse
I think that i was install before a wrong area stock rom. Do you know or recommend what is the better to install this device to work with 3g 850 band, in Costa Rica and i can install your amazing rom?....
You can flash modem.bin from your original stock ROM. Extract it uzing 7zip or WinRAR, upload it somewhere and paste the link here, I'll make it flashable via Odin.
A question a bit off-topic... is there anyway to know which mods can be installed on any S3 Mini (I8190, I8190L, I8190N) and which mods can't? I'm guessing that anything that has to do with kernel has to be very device specific, but can I flash any custom recovery (CWM, TWRP) regardless of the phone's version?
Well for instance, the L version doesn't have NFC and the N version does, they could differ in lots of things so no you can't just flash anything on it.
Benzonat0r said:
Well for instance, the L version doesn't have NFC and the N version does, they could differ in lots of things so no you can't just flash anything on it.
Click to expand...
Click to collapse
Alright, thanks. I don't really need the custom recovery right now but I wanted to be sure for future reference.
Modem Bin
Benzonat0r said:
You can flash modem.bin from your original stock ROM. Extract it uzing 7zip or WinRAR, upload it somewhere and paste the link here, I'll make it flashable via Odin.
Click to expand...
Click to collapse
Hello.
Thanks for your help...
Well i dont have a modem.bin from a original stok, but i used and install very good its from stock rom from TTT.
You can have access by this url https://docs.google.com/folder/d/0B9a5cmEC8OPYSFQ4eTVhY3hnRjg/edit?usp=sharing
Please let me know if you can give me this file to install via odin to test with your rom.
Thanks for your help again.
My skype: damadric
OsoAlgo said:
Alright, thanks. I don't really need the custom recovery right now but I wanted to be sure for future reference.
Click to expand...
Click to collapse
I added CWM recovery with no issues on my L.
DAMADRIC said:
Hello.
Thanks for your help...
Well i dont have a modem.bin from a original stok, but i used and install very good its from stock rom from TTT.
You can have access by this url https://docs.google.com/folder/d/0B9a5cmEC8OPYSFQ4eTVhY3hnRjg/edit?usp=sharing
Please let me know if you can give me this file to install via odin to test with your rom.
Thanks for your help again.
My skype: damadric
Click to expand...
Click to collapse
http://www.4shared.com/file/LdRUFrLL/modemtar.html?
Flash this via Odin.
Benzonat0r said:
http://www.4shared.com/file/LdRUFrLL/modemtar.html?
Flash this via Odin.
Click to expand...
Click to collapse
Hello ...
First ...Thanks for all your help...
Only for records.
I have a i8190L, i insist to install the version...
The first version with V3 in the name for i8190L ,works perfect,
In the second update , i try to install by any ways and nothing inclusive with your incredible help of the MOMEM in tar file, and nothing , ever startup with no phone detect.
Then strange but i try to install the version for i8190 V3 in the another post and works wonderfull, even with the updates.
Strange but i would to continue enjoy and testing your work and this version works without problem.
Thanks for all your help and would track your work...
DualBootPatcher
A big thanks to @chenxiaolong for originally creating this wonderful utility.
What is dual booting?
It is like having 2 ROMs installed at once, and you can switch to other ROM without flashing it all over again, your data, stuff everything is preserved.
How to use the patcher?
A quote from the author himself:
Android
Download the patcher apk and run it. Tap "Patch Zip File" from the navigation drawer and choose the file you want to patch.
Windows (GUI)
Double click DualBootPatcher.exe and choose the file you want to patch.
--------
After patching the zip file, a new file, like some_rom_dual.zip file will be created. For example, patching ktoonsez's
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013.zip
would create a new
KT-SGS4-JB4.3-AOSP-TMO-08.28.2013_dual.zip
Click to expand...
Click to collapse
For now we dont have Windows executable, so only prefer to use the android app.
How to dual boot?
Before doing anything, download the App from the download section below.
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
With that said, let's get to the "how to"!
First, boot into your primary ROM and install the Dual Boot Patcher app
Open the app and go to "Roms" in the navigation drawer. It will ask if you want to set the kernel. Make sure that you do.
Go to "Patch zip file" in the navigation drawer and patch the ROM or zip you want to install. You can select one of the installation locations described above.
There are two ways of flashing the patched zip file. You can either flash it normally from recovery or flash it using the in-app flashing feature. Both methods are explained below.
Flashing from recovery
To flash from recovery, just flash the patched zip file like you would for any other zip. Nice and simple.
In-app flashing
To use in-app flashing, go to "Roms" in the navigation drawer, tap the floating button on the bottom right, and add the zips you want to install. You can queue multiple zips and they will all be flashed in one go. Once you've added all the zips you want to flash, click the check mark in the action bar and they will be flashed right away.
A normal backup from recovery will backup every ROM. If you would like to back up ROMs individually, please see @rlorange's awesome tool: http://forum.xda-developers.com/showthread.php?t=2491299
Click to expand...
Click to collapse
App 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.
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.
(Hope my analogy didn't suck too much )
How do I?
Switch the ROM if something doesn't work properly ?
If you have TWRP, you can also switch manually by tapping Install -> Images (bottom right) -> Go to /sdcard/MultiBoot/[Your ROM]/ -> flash boot.img.
Wipe /cache, /data, /system, or dalvik-cache?
The easiest way is to do it from the app while booted in another ROM. Just go to "Roms" in the navigation drawer, tap the 3 dots options menu for the ROM you want to wipe, and tap "Wipe ROM".
NOTE: Don't use the recovery's built-in wiping abilities as that may delete non-primary ROMs!
Update the primary ROM?
Patch the zip for primary and flash it. The "primary" installation target is designed so that other ROMs won't be affected when you want to flash something for the primary ROM.
Update a non-primary ROM?
Patch and flash the zip exactly like how you did it the first time.
Flash a mod or custom kernel for the primary ROM?
Patch it for primary before flashing. If the zip does not wipe /cache, it is also safe to flash it directly.
Flash a mod or custom kernel for a non-primary ROM?
Just patch and flash it
Click to expand...
Click to collapse
Downloads
App - Here
Credits
@chenxiaolong and to all the contributors in this project
XDA:DevDB Information
DualBootPatcher for Lenovo Vibe K5 & K5 Plus , Tool/Utility for the Android General
Contributors
Dreamstar, chenxiaolong
Version Information
Status: Beta
Created 2016-12-19
Last Updated 2016-12-25
Reserved
Thanks for this!
Can anyone confirm this working?
Can confirm this is working in Lenovo Vibe K5 a6020a40 device thanx for this you are awesome
This is truly awesome!!
First I flash stock then vegito then dual boot patcher apk and make dual boot flashable zip and when flashing through twrp it fails to flash and this error. On apk
Device a46 2gb
netship said:
First I flash stock then vegito then dual boot patcher apk and make dual boot flashable zip and when flashing through twrp it fails to flash and this error. On apk
Device a46 2gb
Click to expand...
Click to collapse
Get it from here its official now
https://dbp.noobdev.io/supported_devices.html#device_info_20
Dreamstar said:
Get it from here its official now
https://dbp.noobdev.io/supported_devices.html#device_info_20
Click to expand...
Click to collapse
Wow man just wow!
Dreamstar said:
Get it from here its official now
https://dbp.noobdev.io/supported_devices.html#device_info_20
Click to expand...
Click to collapse
Thank you Very much!!
Recieved error message while installing secondary rom.
Guys any solution?
pradeesa said:
Recieved error message while installing secondary rom.
Click to expand...
Click to collapse
You may try this.
netship said:
You may try this.
Click to expand...
Click to collapse
I tried bro still same problem...
pradeesa said:
Recieved error message while installing secondary rom.
Click to expand...
Click to collapse
Upload that log file here
Error log
App sharing not working.. or I'm doing something wrong.. don't know but not working for me.
What about efidroid manager
Can anybody try to port it to lenovo k5??
Last I checked with 10/4 aicp nightly, it's not working. Needs some fixes.
pradeesa said:
Recieved error message while installing secondary rom.
Click to expand...
Click to collapse
Same here tried changing name no success
Heyo, guys. I wanna show u my own ROM based on LineageOS 14.1.
Flash it as u flash another ROMs:
Wipe System, data, caches
Flash ROM
Flash Gapps
Flash SuperSu if u want
For update just do dirty flash.
Hope that u'll like this ROM.
Download link:
AFH
Big thanks to @romilparh who was the first man who helped me with beginning things.
Thanks to @jhalayashraj who taught me some things
Thanks to @amardeep434 who also helped me a lot
Thanks to @danieldmm who also helped me with a lot of things
Also thanks to @TechExhibeo my sensei who can help with ton of problems and advise smth
And thanks @jgcaap for some interesting things on github.
LineageOS
Kernel
Device
Have a good use and thanks
umm.. First?
EDIT: Hey Oleg, nice to see your CM. Will download asap.
hey there, I was on resurrection remix 6.0, i followed the given steps
> flashed the latest version of TWRP image
>flashed the Lineage OS 14.1 zip via twrp (yes i wiped everything)
when i try flashing the open gapps mini zip (ARM, 7.1, mini); it says insufficient system storage (error code 70), i even selected advanced options and tried resizing system partition and then flash the gapps zip, but it still says insufficient storage (p.s i would’nt like to downgrade pico version or so)
but it seems like there’s enough storage (1300mb system storage)
how can i resolve this issue?
Thanks in advance.
Tried doing the same with cm 14.1 with the same Gapps and it works.
thank u very much for this awesome rom.
Wow this ROM is awesome! I just saw LineageOS 14.1 for the OnePlus One yesterday. No bugs so far, It seems really stable and a great and probably the best daily driver ROM.
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
nolsen311 said:
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
Click to expand...
Click to collapse
i'm not facing any problem with AdAway and viper in 20170109 build.
NeolWhyt said:
hey there, I was on resurrection remix 6.0, i followed the given steps
> flashed the latest version of TWRP image
>flashed the Lineage OS 14.1 zip via twrp (yes i wiped everything)
when i try flashing the open gapps mini zip (ARM, 7.1, mini); it says insufficient system storage (error code 70), i even selected advanced options and tried resizing system partition and then flash the gapps zip, but it still says insufficient storage (p.s i would’nt like to downgrade pico version or so)
but it seems like there’s enough storage (1300mb system storage)
how can i resolve this issue?
Thanks in advance.
Tried doing the same with cm 14.1 with the same Gapps and it works.
Click to expand...
Click to collapse
Probably u're doing smth wrong...
nolsen311 said:
No one's posted about this yet, so I'll ask: on the 20170103 build there are some errors with "insufficient space" on the system partition. Specifically when trying to build a new hosts file for AdAway. I haven't had problems previously, this has only shown up since migrating to your Lineage build. It's possible that this is related to new Nougat filesystem security and the message from AdAway just isn't very clear, which I'll check after I download the 20170109 build.
I'm also having issues getting the driver for Viper to load. It doesn't seem to want to do it. every time I walk through the process, the status is still unloaded.
update: remounting /system RW didn't have any effect on my ability to build the new hosts file. :crying:
Click to expand...
Click to collapse
Doesn't have any problem. All is ok.
Okeys said:
Doesn't have any problem. All is ok.
Click to expand...
Click to collapse
Oh, OK. Everything's OK. Cool.
I noticed that viper isn't included in the build any more. So everything must be even more OK now, right?
Whatever issues I had seem to have been resolved after updating to 20170109. We'll see after this runs for a couple days. Right now adaway is able to do its thing without error and at least audioFX seems to work.
Thank you for building these for us.
Sent from my A0001 using Tapatalk
nolsen311 said:
Oh, OK. Everything's OK. Cool.
I noticed that viper isn't included in the build any more. So everything must be even more OK now, right?
Whatever issues I had seem to have been resolved after updating to 20170109. We'll see after this runs for a couple days. Right now adaway is able to do its thing without error and at least audioFX seems to work.
Thank you for building these for us.
Click to expand...
Click to collapse
Viper is still included. Just change SELinux mode. I'll change on needed later.
Have a good use
I have tried to flash the OS. I have wiped the data, cache, dalvik cache and system partition (recovery TWRP 3.0.2.0).
After that I have flashed build `lineage-14.1-20170109-Okeys-bacon` and the pico GApps (mini cause insufficient system storage error).
Then when I tries to boot, and it takes more then 20 minutes to boot (the OS still didn't booted).
Is it normal? What should I do?
f2sf it's supported?
hyper_davide said:
f2sf it's supported?
Click to expand...
Click to collapse
Now not.
ppp99 said:
I have tried to flash the OS. I have wiped the data, cache, dalvik cache and system partition (recovery TWRP 3.0.2.0).
After that I have flashed build `lineage-14.1-20170109-Okeys-bacon` and the pico GApps (mini cause insufficient system storage error).
Then when I tries to boot, and it takes more then 20 minutes to boot (the OS still didn't booted).
Is it normal? What should I do?
Click to expand...
Click to collapse
All in ext4?
Okeys said:
All in ext4?
Click to expand...
Click to collapse
Just checked, YES.
https://www.androidfilehost.com/?w=files&flid=132556
Thanks so much Okeys! this is the best ROM I could find so far, it works so perfectly!!
Summary of my attempts:
(1)I tried "lineage-14.1-20170130-nightly-bacon-signed.zip" from lineageos
* lower kernel: 3.4.112
* not support system root, need install supersu.
* System APP: "SoundRecorder" and "Screencast" were merged and replaced with "Recorder", I don't like the new "Recorder", the recorder file is much bigger than "SoundRecorder"
(2)I tried "RR-N-v5.8.1-20170131-bacon-Official.zip" from remix
* Same as lineage above
* Support system root option, not need supersu
(3)lineage-14.1-20170126-Okeys-bacon.zip
* new kernel: 3.4.113
* not support system root, need install supersu.
* keep the original "SoundRecorder" and "Screencast"
* The only problem I met is "Left Wipe" doesn't switch to "Google" with Pixel Launcher for Andriod 7.1, but I find a solution and fixed it.
** see my post: https://forum.xda-developers.com/oneplus-one/help/fix-left-wipe-doesnt-switch-to-google-t3549497
Please change to coloros blobs dude
20170202 Bacon Gesture Settings
lineage-14.1-20170202-Okeys-bacon flashed a few minutes ago. Noticed that the Gestures settings no longer allows control over music and camera gestures. They are on by default, and I guess can no longer be turned off.
Hope this helps,
E.
Hi All,
sharing the guide to install the multiple Rom's in our Axon 7 (as we don't have multi-boot in place).. as the development already kicked with Noughot.. and multiple roms are landing here...
this is for people who can't move out of Stock (due to Audio issues including me) and want to sneak peak the other LOS based roms.
Dual Boot Patcher is an app created by chenxiaolong for S4 initially and it broadly supports more than 150 devices now, whoever used in S4 would be familiar with it.. this app allows you to have multiple ROMs on a single device.
If you loved his work, go to his thread say Thank You
Axon 7 is official supported
I have tried with RR as Secondary and it's working.. so thought of sharing this.
For More details on this Dual Patcher official Thread:
https://forum.xda-developers.com/showthread.php?t=2447534
Working:
- patch ROM zip files
- patch GAPPS zip files
- patch SuperSu zip files
Instructions: More details
Keep the Stock Rom as always Primary.
Use the Data slot and create a name for the folder, as the System/Cache space will be small for LOS Rom
If you want to flash the LOS, RR roms remove the below script in the update-script (ROM\META-INF\com\google\android)
Code:
assert(getprop("ro.product.device") == "ailsa_ii" || getprop("ro.build.product") == "ailsa_ii" || getprop("ro.product.device") == "axon7" || getprop("ro.build.product") == "axon7" || abort("E3004: This package is for device: ailsa_ii,axon7; this device is " + getprop("ro.product.device") + "."););
assert(axon7.verify_trustzone("TZ.BF.4.0.1-00315") == "1");
ui_print("Target: ZTE/P996A01_N/ailsa_ii:7.0/NRD90M/20170128.052618:user/release-keys");
Issues:
- Encryption and Boot UI are not supported
- trustzone verification in the Update-script will fail while flashing the TWRP, remove the above code before flashing the zip file.
- Pins, patterns or passwords are wrong in one of the ROMs . Then simply delete the file /data/system/locksettings.db (your saved fingerprints won't be lost) with TWRP.
Warning: for me setting the PIN in one rom works, if i enabled PIN in 2 roms it's not working, everytime you have to delete the locksettings.db and boot into other rom. Fingerprint works in 2 ROMS
- if In-app flashing doesn't work, you have to use TWRP to flash the patched zip files (use the latest TWRP)
- If flashing of a patched zip fails for any reason, you have to choose another install location ("Partition Configuration" in the app) when patching the same zip file again!Note: If flashing fails, first look up the error at /sdcard/MultiBoot.log and google it before reporting it...
Download
Download Dual Boot Patcher APP
Download Dual Boot Utilities
Credits to:
@chenxiaolong - for the great app and supporting till date.
@jimbo77 - for making Dual boot Axon 7 official support
@Glove007 - for additional details on workaround for Op3 - applies to Axon7
XDA Community
if i missed any plz let me know.
i can't find anyother thread related to this Dual Patacher, if it's available please merge the thread.
Do I lose any data/factory reset when I do this? Is it possible to go back to single boot easily without losing anything?
Nik2424 said:
Do I lose any data/factory reset when I do this? Is it possible to go back to single boot easily without losing anything?
Click to expand...
Click to collapse
No you won't lose any data when you flash this.. (But take a backup for safety)
Plz follow this steps.
Install the Dual patcher app and set the current Rom as primary
Make sure you patch the second Rom and Gapps (Super SU optional) in the Dual Patcher App before flashing in TWRP (or it will overwrite the Primary ROM)
in the patched rom remove the TrusstZone entries as mentioned in OP
then flash it via TWRP.
the Rom will be added to your Data or Cache based on the selection you made while patching the Zip file in the Dual Patcher (Preferable is data slot, and rom will be saved in Data>multiboot).
once logged in the Second rom, use the patcher to set the Rom as secondary.
when you want to switch rom, select the rom in the Dual Patcher app and reboot. (the app will move the correct boot.img to partion and selected rom will boot. )
if you want to Wipe Primary Rom or Second/Third Rom use the Dual Boot Utilities in the TWRP, this will wipe only the specified rom and you Second/third Rom won't get deleted. (if you wipe data/cache using TWRP menu, it will wiped your Second/third roms)
Thank you for detailed steps; but i have to ask, what is this trustzone error? Does it have negative impacts?
Nik2424 said:
Thank you for detailed steps; but i have to ask, what is this trustzone error? Does it have negative impacts?
Click to expand...
Click to collapse
those are added in the Rom to validate you're flashing in the right firmware.. like Noughot roms shouldn't be flashed in MM firmware.
Nothing wrong here in removing in those lines during flashing as secondary Roms..
I think I'm going to do this on my phone. @`SBR` can you verify my steps?
I'm on LineageOS now. I go back to stock by flashing stock A2017G Nougat via TWRP, since the primary ROM needs to be stock.
(OR is it possible to just install the Dual Boot Patcher app and install stock ROM from LineageOS and then select the stock ROM to be primary?)
I download latest LineageOS, I patch it with the Dual Boot Patcher utilities
I download the Gapps, I patch it with the Dual Boot Patcher utilities
I edit the update-script and remove the quoted lines
I install the dual boot patcher app
I use it to install the patched LineageOS and Gapps zips to a data slot (new folder I created) If this doesn't work, I use TWRP to install the patched zips
I delete file /data/system/locksettings.db to solve the PIN issue. I can only set PIN unlock on one of the two ROMs.
I boot to both ROMS and select stock as primary and LineageOS as secondary
I manually set messenger and other wanted apps as shared so I can use them from both OS'es?
Does this seem about right?
Thanks.
So glad this got brought to our phone
I think I'm going to do this on my phone. @`SBR` can you verify my steps?
I'm on LineageOS now. I go back to stock by flashing stock A2017G Nougat via TWRP, since the primary ROM needs to be stock.
(OR is it possible to just install the Dual Boot Patcher app and install stock ROM from LineageOS and then select the stock ROM to be primary?)
STOCK Rom is heavy and may not support all the time as Kernel has limited functionlity so patching may fail sometimes in the Stock rom, but you can try that as well and let us know.
I download latest LineageOS, I patch it with the Dual Boot Patcher utilities
I download the Gapps, I patch it with the Dual Boot Patcher utilities
you should patch with Dual Patcher APK... -- Dual Boot utilities will be flashed in TWRP to install/wipe/update Primary Roms without impact to other Roms.
I edit the update-script and remove the quoted lines - yes
I install the dual boot patcher app - in primary Rom, yes
Open the App, give Root permission - it will prompt you for making the kernel as Primary, set it now - this is required so that App can switch between multiple Roms
1. basically the App will copy the boot.img of primary into storage>multiboot>primary
2. when you install the secondary rom and boot it up, install the app set the rom as secondary.
3. it will copy the secondary rom boot.img in to the same folder
4. whenever you switch rom, the app will copy the switched roms's boot.img to the Boot partiion so that corresponding rom will start on reboot
I use it to install the patched LineageOS and Gapps zips to a data slot (new folder I created) If this doesn't work, I use TWRP to install the patched zips
In-app flashing is failing for me, use TWRP to flash it.
I delete file /data/system/locksettings.db to solve the PIN issue. I can only set PIN unlock on one of the two ROMs. - yes
I boot to both ROMS and select stock as primary and LineageOS as secondary
Set the Primary when you installed the App in primary Rom itself.
and set the secondary when installed the app in secondary rom
I manually set messenger and other wanted apps as shared so I can use them from both OS'es?
I doubt App sharing is working correctly, please try and let me know
hope this helps
Does this seem about right?
Thanks.
Worked!
Great, this workd for me thanks!
thank you so much for this post
Hey OP
God knows how much I have been waiting for this even before I owned 2017U Because I knew devs would struggle a lot on porting multimedia experience between the stock and the custom
Anyways I have some questions but before everything I like to clarify that I got a big upgrade (from S2/s3 mini/grand 2) to my luxurious Axon 7, I have never dealt with fastboot or ARM64 ever before so it'll be kinda hard for me
1. Is this DB method have unified boot.img?? or simply have shared kernel??The main reason is that I need to flash a custom kernel on my secondary ROM, If that will mess up I will just replace RR's (my favorite ROM) boot.img before flashing or any possible way that works.
2. Is there any way to have f2fs on the secondary ROM???
(Like changing to f2fs first then flashing RR then using DB method to flash stock ROM or something as the guy mentioned above?partitioning may work??? Any other way? ) I mean the obvious reason is that we know how OP3's nand performance increased with f2fs.
Long story short I need both f2fs and custom kernel for ultimate performance because sd820 seems good for heavy usage but I want more control for extreme situations.
I'd like a confirming answer instead of a normal one due to the lack of experience with newer devices
Sebastian Fox said:
Hey OP
God knows how much I have been waiting for this even before I owned 2017U Because I knew devs would struggle a lot on porting multimedia experience between the stock and the custom
Anyways I have some questions but before everything I like to clarify that I got a big upgrade (from S2/s3 mini/grand 2) to my luxurious Axon 7, I have never dealt with fastboot or ARM64 ever before so it'll be kinda hard for me
1. Is this DB method have unified boot.img?? or simply have shared kernel??The main reason is that I need to flash a custom kernel on my secondary ROM, If that will mess up I will just replace RR's (my favorite ROM) boot.img before flashing or any possible way that works.
2. Is there any way to have f2fs on the secondary ROM???
(Like changing to f2fs first then flashing RR then using DB method to flash stock ROM or something as the guy mentioned above?partitioning may work??? Any other way? ) I mean the obvious reason is that we know how OP3's nand performance increased with f2fs.
Long story short I need both f2fs and custom kernel for ultimate performance because sd820 seems good for heavy usage but I want more control for extreme situations.
I'd like a confirming answer instead of a normal one due to the lack of experience with newer devices
Click to expand...
Click to collapse
1. it's not a unified Boot.img.. every Rom has it's own kernel and it set it in the DB app. you can install custom kernel in your secondary (make sure it's pacthed) and set the rom as secondary Kernel in DB app.
2. DB doesn't care you have a Ext4 or F2FS, as long as your rom works it should work there as well.
`SBR` said:
STOCK Rom is heavy and may not support all the time as Kernel has limited functionlity so patching may fail sometimes in the Stock rom, but you can try that as well and let us know.
Click to expand...
Click to collapse
I tried flashing Ressurection Remix inside of stock A2017G nougat, but after a reboot the phone hung at the unlocked bootloader warning.
So is it advisable to flash the stock system inside of RR and set it as primary?
mvortex3710 said:
I tried flashing Ressurection Remix inside of stock A2017G nougat, but after a reboot the phone hung at the unlocked bootloader warning.
So is it advisable to flash the stock system inside of RR and set it as primary?
Click to expand...
Click to collapse
there is no problem in flashing Stock rom, if it works.
did you set the primary kernel in the DB app. for RR which slot you have selected? if there are enough space for ROm it won't boot..
check the log for any issues reported on this.
`SBR` said:
there is no problem in flashing Stock rom, if it works.
did you set the primary kernel in the DB app. for RR which slot you have selected? if there are enough space for ROm it won't boot..
check the log for any issues reported on this.
Click to expand...
Click to collapse
Thanks very much for your fast reply.
When I checked the main thread it seems like this problem may be caused by not flashing a patched kernel as well, so I will try that presently and report back!
Edit: The patched kernel I'm using (AX7Kernel) is returning the error: "unable to find boot block location!", I've tried googling it but haven't found anything. Would you happen to know what might be causing this? Flashing in TWRP seems to have fixed this. Attempting boot now.
Edit 2: Boot didn't succeed, I was faced with 5 vibration then a restart to TWRP, where I used the Dual Boot utilities to change back to my Primary (stock) boot.
I'm going to try the other way round, with RR as primary and Stock as (secondary) data boot.
`SBR` said:
1. it's not a unified Boot.img.. every Rom has it's own kernel and it set it in the DB app. you can install custom kernel in your secondary (make sure it's pacthed) and set the rom as secondary Kernel in DB app.
2. DB doesn't care you have a Ext4 or F2FS, as long as your rom works it should work there as well.
Click to expand...
Click to collapse
thanks for that reply, although I still need some more information
can you provide a quick howto get Resurrection on f2fs alongside the stock?? I only know how to format/change with twrp from ext4-f2fs plus, what I get from this post is, that it'll use the data partition, I didn't see any mention of repartition or whatsoever, so I am afraid that it won't work because stock nougat is ext4 I want the stock as primary and F2fs RR as secondary. Is that not possible?
Sebastian Fox said:
thanks for that reply, although I still need some more information
can you provide a quick howto get Resurrection on f2fs alongside the stock?? I only know how to format/change with twrp from ext4-f2fs plus, what I get from this post is, that it'll use the data partition, I didn't see any mention of repartition or whatsoever, so I am afraid that it won't work because stock nougat is ext4 I want the stock as primary and F2fs RR as secondary. Is that not possible?
Click to expand...
Click to collapse
thats not possible...
`SBR` said:
thats not possible...
Click to expand...
Click to collapse
Oh then it seems we reached a blocked road, is there anyway to convert the stock to f2fs??? Partitioning data???
I will try partitioning if possible but it's useless if the dualboot app/utility doesn't support it.
im facing a 5 vibration reboot to twrp after flashing rr patched. stock is primary, rr is data slot.
tried with lineage too, no luck same problem. help plz guys, this is a really awesome tool, i want this to work
Nik2424 said:
im facing a 5 vibration reboot to twrp after flashing rr patched. stock is primary, rr is data slot.
tried with lineage too, no luck same problem. help plz guys, this is a really awesome tool, i want this to work
Click to expand...
Click to collapse
for me i'm able to ptach RR and it's working in data slot..
did you try to install anything after patched RR and patched Gapps?