FIrst things first...
Code:
Disclaimer:
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 the tool you find here 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. Your warranty will be void if you tamper with any part of your device / software.
Now that we have that done...
Repartition guide for
The GT-i9100
Introduction:
This script came a long way before landing here. It originally came from @forumber2 with his guide for the GT-i9300. It then went on to the Note 2 by @ninekaw9 and @smeet.somaiya before I decided to port it over to this lovely device.
Click to expand...
Click to collapse
What does the script do?
It basically removes the partitions present from your device and creates partitions with modified sizes.
TLDR: A flashable .pit file
Images
Result
{
"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"
}
Click to expand...
Click to collapse
Features
Adds more space for more apps.
Reduced cache partition for even more space for apps.
No need for a computer, fully flashable in CWM.
How To Install?WARNING: From this point onwards, this guide requires your fullest attention so that it will not brick your device. I tested this on my own i9100, and it is working perfectly.
Links will be provided at the end of the post.
This will wipe everything from your device! Please make a backup before proceeding. Don't say I didn't warn you.
There are two methods to flashing this script. Both works perfectly fine.
Method 1 If you're using 1.1 and above, steps 6-9 are not needed!
Download the two recoveries provided in the Download post below.
Reboot into recovery (CWM or TWRP needed)
Flash philz_touch_6.07.9-i9100.zip and reboot into recovery.
Flash the repartition-apps<xxx>-data<xxx>.zip (Note: It will hang at rebooting to recovery in 5 seconds. Just take out the battery and boot it to recovery.)
Flash kk-kernel-05-01-TWRP.zip and reboot into recovery.
Click on Wipe, then Advanced Wipe.
Tick Internal Data, then click on Repair or Change File System.
Click on Change File System, click on EXT4, then swipe to confirm.
Click on Change File System again, click on exFAT, then swipe to confirm.
Go back to Advanced Wipe, tick on
Dalvik Cache
Cache
System
Data
emmc
Then swipe to wipe the 5 partitions.
Next, click on Install and install your preferred ROM.
Reboot and enjoy!
Method 2 If you're using 1.1 and above, steps 5-8 are not needed!
Download TWRP and the "parted" file from the bottom of the post.
Using a root browser (Root Browser recommended), place the parted file you have downloaded into /system/bin and set its permissions to "RWXR-XR-X".
Reboot into recovery and flash kk-kernel-05-01-TWRP.zip and reboot into recovery.
Flash the repartition-apps<xxx>-data<xxx>.zip
Click on Wipe, then Advanced Wipe.
Tick Internal Data, then click on Repair or Change File System.
Click on Change File System, click on EXT4, then swipe to confirm.
Click on Change File System again, click on exFAT, then swipe to confirm.
Go back to Advanced Wipe, tick on
Dalvik Cache
Cache
System
Data
emmc
Then swipe to wipe the 5 partitions.
Next, click on Install and install your preferred ROM.
Reboot and enjoy!
XDA:DevDB Information
Flashable zip to repartition the S2, Tool/Utility for the i9100
Contributors
Irwenzhao, smeet.somaiya
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2015-02-01
Beta Release Date: 2015-02-07
Created 2015-02-01
Last Updated 2015-06-26
Reserved
Changelog
1/2/2015
First release!
7/2/2015
Beta 1.01 released!
Changelogs:
Edited the script to not reboot into recovery. Not sure if it works, not an experienced Edify coder.
Click to expand...
Click to collapse
8/2/2015
Mirrors added. Mirrors for beta build will be added at a later date. Thanks for all the support!
20/3/2015
Untested bugfix for 1.0 is out! Please report the results. If it works I'll label it as stable.
28/3/2015
I have tested the fix and it works perfectly. it has been labeled as stable. Enjoy even more memory now! Sorry for the long wait!
Updated steps!
Method 2 added and necessary files uploaded!
25/6/2015
Update 1.1 is here! Major update MUST READ!
This update eliminates steps 6-9. After using the script, you can install a ROM DIRECTLY, how cool is that?
Downloads:
Repartition .zip files
1.1
reparitition1.1apps4.5gb-data9gb.zip
reparitition1.1apps7.3gb-data6gb.zip
1.0
repartition1.0-apps4.5gb_data9gb.zip (Mirror)
repartition1.0-apps7.3gb_data6gb.zip (Mirror)
Recoveries
TWRP (Mirror)
Philz (Mirror)
BETA/MISC
parted (Mirror) (for Method 2)
Reserved
Notes, Warnings and some Random Stuff (MUST READ)
Do you need a zip file with a custom partition size? Post a feature request and I'll attend to it ASAP!
I will be updating this thread (probably) weekly, but I will provide support through my mobile device.
DO NOT use this on stock ROMs. You will brick your device.
Follow the guide CAREFULLY. Please.
Hey there,
First response it seems. I'll have to try this later as I haven't had to repartition my S2 and it sounds a lot quicker than using say ODIN for the job. Anyone had any issues yet?
omallz said:
Hey there,
First response it seems. I'll have to try this later as I haven't had to repartition my S2 and it sounds a lot quicker than using say ODIN for the job. Anyone had any issues yet?
Click to expand...
Click to collapse
No issues on my device so far.
Do you need a zip file with a custom partition size? Post a feature request and I'll attend to it ASAP!
Yeah, it's would be great to have a zip-file for coming back to stock partition also!
Thanks.
Sergey2510 said:
Do you need a zip file with a custom partition size? Post a feature request and I'll attend to it ASAP!
Yeah, it's would be great to have a zip-file for coming back to stock partition also!
Thanks.
Click to expand...
Click to collapse
You'll have to do that using a .pit file. I think it's required to flash stock ROMs.
Repartition sizes
@Irwenzhao Could you please explain the attached files of Repartition sizes ?
I mean.. what will be the configuration and new sizes category wise ..
and Kindly share/upload another way to download the attached files too.. getting this error from Dropbox
"Error (509)
This account's public links are generating too much traffic and have been temporarily disabled! "
Thanks
adnan7khan said:
@Irwenzhao Could you please explain the attached files of Repartition sizes ?
I mean.. what will be the configuration and new sizes category wise ..
and Kindly share/upload another way to download the attached files too.. getting this error from Dropbox
"Error (509)
This account's public links are generating too much traffic and have been temporarily disabled! "
Thanks
Click to expand...
Click to collapse
Apps<xxgb> means that there'll be xxgb of space available to install apps and Data<xxgb> simply means that there'll be xxgb of space available for your music/documents/files.
Too much traffic? I wasn't expecting this many people! Shall provide a mirror ASAP.
Irwenzhao said:
Apps<xxgb> means that there'll be xxgb of space available to install apps and Data<xxgb> simply means that there'll be xxgb of space available for your music/documents/files.
Too much traffic? I wasn't expecting this many people! Shall provide a mirror ASAP.
Click to expand...
Click to collapse
Thanks already waiting
Mirrors up. Mirrors for beta build will be provided at a later date.
I am sorry if this is a stupid question, but what happens to the space between 12.4 GB and 15.2 GB? In the original partitioning there is 1.94+11.5 = 13.44 GB of space, while this setup has only 4.48+6.33 = 10.81 GB. Thank you for you time.
jeffrey2121 said:
I am sorry if this is a stupid question, but what happens to the space between 12.4 GB and 15.2 GB? In the original partitioning there is 1.94+11.5 = 13.44 GB of space, while this setup has only 4.48+6.33 = 10.81 GB. Thank you for you time.
Click to expand...
Click to collapse
Must be another typo I did while writing the script on my phone. Will correct it when I have the time.
Stock or Samy Based ROM *Custom Partitions*
@Irwenzhao is it possible to flash stock ROM or OMEGA v61 etc on the customized partitions ???
adnan7khan said:
@Irwenzhao is it possible to flash stock ROM or OMEGA v61 etc on the customized partitions ???
Click to expand...
Click to collapse
Stock ROM NO. Third Party Touchwiz ROM is a yes.
when I perform the last step for the 5 options on advanced wipe, I get wipe failed. What does that mean?
Irwenzhao said:
jeffrey2121 said:
I am sorry if this is a stupid question, but what happens to the space between 12.4 GB and 15.2 GB? In the original partitioning there is 1.94+11.5 = 13.44 GB of space, while this setup has only 4.48+6.33 = 10.81 GB. Thank you for you time.
Click to expand...
Click to collapse
Must be another typo I did while writing the script on my phone. Will correct it when I have the time.
Click to expand...
Click to collapse
can you please upload screenshot of storage after you update or correct the script
Dropbox had locked the files
It will work with the stock rom 4.1.2?
Thank you. After following your steps, my storage now changed. for device and USB. awesome work..
Related
Hi all, I have managed to merge the code and develop a new function to upgrade all the build using one update package in the future.
Thus, I intend to merge all the Nand version into this thread
All the SD&MAGLDR version into this thread, which will also easy for me to take care of the builds. thanks.
Let a figure come to speak first
{
"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"
}
Uploaded by viperd using DL Desire Z v3.5, DL Data2SD/Ext4 v3.0
Since the DL Desire ARA v1.1 was disclosed in this thread, in order not to cause more confusion, have to release it before my plan.
v2.0 is based on Desire HD 1.72, and themed similar to Coredroid.
v1.0 is based on Desire HD 1.84, pure stock version, and actually, the base is much newer and advance than v2.0
Btw, my focus is still on desire z, if you want prompt support or have problem with this build, suggest you try rafpigna or markinus or imilka's, they are all excellent dhd builds.
If you have problem, please post to my test place or ask my testers, I may not be able to visit this thread frequently.
to my testers, I don't mind you disclose my test place to others as long as they are kind enough.
Click to expand...
Click to collapse
Features:
All my new builds have the following features:
1. All in one package, can be flashed to Nand or boot from SD or Load from Magldr.
2. All the build is squashed, once set the swap_mode=2, can delete the squashed.sqsh file from /system to release 160M space from system, but you must keep the swap_mode=2 untouched.
3. All the build can use Update_DL to update or change anything you want.
4. Equipped with DL Data2SD/Ext4 v3.0 developed by myself and freak, with following features:
-- auto detect and make use of your 2nd and 3rd partitions with high performance
-- auto convert the system.img to system.ext2 for SD/MAGLDR
-- auto partitioning your SD Card once set the format_ext4=9 (need test).
-- format 2nd partition with proper block size of ext4 with format_ext4=1, which is used for data partition
-- change ppp/rmnet with ppp_mode=0 or 1.
-- set you gps zone with gps_zone="your country code"
-- can use Update_DL to update system incrementally, all the Update_DL plugin I previous published(backup/restore, secue) is still applicable
-- the backup/restore can backup and then restore your whole system including: settings, sms, email, etc, you even can use this to migrate your data.img to ext4(set data_img=1 to use data.img and do the backup, and then set the data_img=0 to use the ext4 and do the restore.)
-- once you encounter the boot loop and FC, you can use the rescue plugin to rescue your system.
-- we are now testing the next version of our Data2SD/Ext4 which is more intelligent, can even detect where the system is loaded from(nand, magldr or sd), and your mobile type(EU modal or Tmous) to choose the best settings automatically.
Actually, many builds in this forum adopt part or full of our initrd to provide the high performance ext4 support.
Click to expand...
Click to collapse
DL DesireDH v1.0 ARA Series
1. Based on the official HTC ACE 1.83.415.4 RUU ARA, specific for Arabic, Stock version.
2. Also equipped with DL Data2SD/Ext4 v3.0.
Click to expand...
Click to collapse
DL DesireDH v1.0 Series
1. Based on the newest Desire HD 1.84.661.1 RUU, Stock version.
2. the new version of DL Data2SD/Ext4 v3.0
3. use gpc kernel which can easily be changed to any other kernel by using the Update_DL[/SIZE]
Click to expand...
Click to collapse
DL DesireDH v2.0 Series
1. Based on the very popular Desire HD 1.72.405.3 RUU, Themed similar to Coredriod.
2. Also equipped with DL Data2SD/Ext4 v3.0.
3. For ppl like theme, should try this version.
Click to expand...
Click to collapse
Download
DL DesireHD ARA v1.1
DL DesireHD v2.0
DL Desire HD v1.0
Upgrade package v1.1
Click to expand...
Click to collapse
How to install
For Nand:
just extract the Desire_DL and Update_DL(for upgrade) folder from the package to the root of your SDCard, flash.
change the config.txt.nand to config.txt and modify the config in it.
For SD/MAGLDR:
just extract the Desire_DL and Update_DL(for upgrade) folder from the package to the root of your SDCard, answer yes when ask for overwrite.
change the config.txt.sd to config.txt and modify the config in it. (Nand)
or change the config.txt.magldr to config.txt and modify the config in it. (Magldr)
If you encounter mobile data issue, please check here
The first boot will take a very long time, especially for SD/MAGLDR due to system will convert the system.img to system.ext2, need 10-20 mins depends on the speed of your SDCard.
After the install, please reboot your system at lease twice to let the system settle down.
Suggestion changing the kernel to gpc if you encounter any issue.
Click to expand...
Click to collapse
How to upgrade or change kernel or customize the system
1. more kernel can be found here,
--a. For Nand, just extract the Update_DL folder to the root of your sdcard, boot twice.
--b. For SD, extract the Update_DL folder to the root of your sdcard, and copy the zImage file from /Update_DL/update/kernel_files to Desire_DL, boot.
--c. You can also use the same kernel package, but replace the kernel file with your own under /Update_DL/update/kernel_files. (for SD/Magldr version, the zImage file should be put under Desire_DL)
2. for system upgrade or bugfix, extract the Update_DL folder from a update package to the root of your sdcard, reboot.
3. if you intend to replace any file from the system, use rootexplorer to delete the target file first, then put the file to /Update_DL/root/system..., e.g, if you want to change the framework.res, just delete the origin file from /system/framework, then, put your own file under /Update_DL/root/system/framework, boot.
Click to expand...
Click to collapse
Plugin for DL Desire Series
1.backup/restore
2.Rescuing your system from boot loop or FC.
3.Patch for TMOUS MMS
Click to expand...
Click to collapse
How to load from MAGLDR
1. Press the power button during reboot
2. Select "Services" from MAGLDR menu
3. Select BootSettings
4. Select AD SD Dir
5. Choose the Desire~1
6. Back to the Boot from AD SD.
Click to expand...
Click to collapse
Useful info
1. Q&A
2. How to install and config
3. Step by step.
4. Another step by step.
Click to expand...
Click to collapse
DL Desire Series
1. DL DesireHD Nand thread.
2. DL DesireHD SD thread.
3. DL DesireZ Nand thread.
4. DL DesireZ SD thread.
Click to expand...
Click to collapse
downloading...
reserve for update
Can I use the data.img from the DesireZ build?
etayel said:
downloading...
Click to expand...
Click to collapse
you even fast than me.
dandiest said:
you even fast than me.
Click to expand...
Click to collapse
waiting for 1.83...........
Thank you very much, downloading...
Will reply the result after complete tested.
Any screenshot will be appreciated...
downloading.............
...............
hhhddd999 said:
Can I use the data.img from the DesireZ build?
Click to expand...
Click to collapse
Can we use or no????
upgrade procedure
Hallo, master!
firts of all many thanks for your big and amazing work!
sorry for the stupid question, but if I have installed your DL DesireZ v.3.4, now may just put into the sd root the DL DesireHD Update_DL folder?
and the other folder zipped in (called Desire_DL)??
I'v tested the 1.1 now, and there is stil no mobil-data by me
wifi and all other, I tested runs best.
I started from WinMob in the normal way
what is this??can anyone here tell me??..
Haha, I never think of ppl want so many builds, so unfortunately, you can only run one of my build at one time and rename the other.
paocavallo said:
Hallo, master!
firts of all many thanks for your
big and amazing work!
sorry for the stupid question, but if I have installed your DL DesireZ v.3.4, now may just put into the sd root the DL DesireHD Update_DL folder?
and the other folder zipped in (called Desire_DL)??
Click to expand...
Click to collapse
Sent from my DL DesireHD v2.0 internal using XDA App
I put another mobile data fix in the desire z v3.5 upgrade package under Desire_DL folder, I believe it should be able to solve this issue.
kajos said:
I'v tested the 1.1 now, and there is stil no mobil-data by me
wifi and all other, I tested runs best.
I started from WinMob in the normal way
Click to expand...
Click to collapse
Sent from my DL DesireHD v2.0 internal using XDA App
Thanks for your great effort.
Downloading...
Oh it's magics
How long is this very long time ? I wait for 2h now, and nothing happens....
Fatso said:
How long is this very long time ? I wait for 2h now, and nothing happens....
Click to expand...
Click to collapse
oh... can't be that long, should not more than 15min, maybe you will have to check your SDCard.
or just remove the battery and reload it again.
If still have problem, delete the system.ext2 in the Desire_DL and let system regenerate it.
Are there any major differences between this and DesireZ? Obviously this won't rotate at the homescreen(which I like) but what about other things?
Forget it, I'm gonna try it anyways I'm also trying the new format_ext4=9. I'm using a 2GB SD card, I'm curious to see how well/bad it works. I'm gonna wait about 20 minutes for the boot, if it doesn't finish then I'm rebooting.
Good build but with MAGLDR it is giving me a very bad wake up lag of 5-10 second. Rest everything is fine.
Greetings!
I have decide long enough and here i am, trying to build my own ROM and share with you guys.
I am still new in creating my ROM, yet i wanna challenge myself and try to have fun with it. To be honest, it is harder than i thought with no complete tutorial out there.
I am planning to start things slowly and learning as i go along. Thus, i start with the basic, modifying stock ROM, and de-odex them. Clear all the bloatware or what i think is not necessary.
Please take note this is just a trial. If you are interested, do try out, and let me know how or where i can improve. I am noob, please don't flame me.
Current Release
MJ ROM: Trial Version 1.3 - 16.04.2012
Firmware: I9100XWLP7
CSC: XENLP3
Kernel: current LATEST Siyah Kernel v3.1rc4 (dual boot supported )
Coming Soon:
add in call recording feature
add in toggle bar - Postpone! Seems like Lidroid method will supercede my translucent status bar.will fine other method to make both thing works.
planning to switch launcher, as i am not too fond with Apex (suggestion please)
create my own logo (might take times, still figuring out)
Beats audio, anyone? (some claim it doens't work, does it? )
Click to expand...
Click to collapse
Bugs:
Not everything is perfect, though i expected a perfect ROM to ease everyone. However, there are some minor bug i encounter. Not a big deal.
- Keyboard not poping up at the initial setup the ownership of the phone
solution: i realise it takes time for the ROM to load up the keyboard (maybe due to language change from netherland to english - united state issue). what i do is, i just press back and forward few time, and the keyboard will initially pop up. don't worry, it just happen the very first time android setup. no more issues after that.
- Messaging app cannot use
solution: i suspect this is Apex Launcher issues. just delete the dock bar Messaging shortcut. Drag and put the new Messaging app from app drawer and you are good to go.
Click to expand...
Click to collapse
Change Log - trial version 1.3 - 16.04.2012:
latest siyah kernel v3.1rc4 with dual boot supported!
add in cool boot animation (my own creation )
add in honeycomb battery mod as default
Click to expand...
Click to collapse
Change Log - trial version 1.2 - 15.04.2012:
latest siyah kernel v3.1rc3 with dual boot supported!
50% translucent status bar
open up hidden samsung cool wallpapers! more selection available!
add in cool boot animation (android destroy apple!)
add in big android battery mod - Done! All you need to do is to download the zip file from below link and flash it with CMW recovery option. Simple and easy. (separate flashing)
add in honeycomb battery mod (separate flashing)
Click to expand...
Click to collapse
Change Log - trial version 1.1 - 14.04.2012:
SuperSU (FULLY ROOTED NOW! )
CWM with touch menu!
latest siyah kernel v3.1rc2 with dual boot supported!
old bootloader for use of USB jig (fully tested, remove yellow triangle and remove binary counter! )
overclock to 1.4ghz
Click to expand...
Click to collapse
Change Log - trial version - 13.04.2012:
Apex Launcher v1.5 (Touch Wiz launcher remove due to force close)
Fully Deodexed
Zipaligned
BusyBox
SuperSU (not really working, i lost the root access, not sure why )
NO WIPE
remove all bloatware and unnecessary apps
Click to expand...
Click to collapse
Benchmark scores for reference:
Quadrant Benchmark(1.2ghz): 3866
Antutu Benchmark(1.2ghz): 6399
WARNING: i have tried running overclock to 1.4ghz, but the score is opposite. i got very ridiculous low score in quadrant benchmark. bug in new firmware?
Don't try to overclock unless you know how to fix it.
Click to expand...
Click to collapse
WHO SHOULD TRY
-Those who want total stock ROM experience with root access,
-Those who is kind enough to train a new developer for S2 and keep the development alive!
Before you did any chances or installation, please make a backup just in case you are not happy and wanna revert back! I will not be responsible for any damages occurred to your phone! I have tested everything myself before i release it to the public, to minimize the errors.
Installation Guide
- Download the ROM (don't unzip)
- Copy the .ZIP file to your INTERNAL SD card
- Boot your phone into CWM (hold Vol Up, Home & Power Button)
- Wipe data/factory reset
- Wipe cache
- Wipe dalvik cache
- Select 'Install ZIP from SD Card'
- Select 'Choose Zip from SD Card'
- Then select the the rom .zip file you downloaded
- Reboot
Battery Mod Installation Guide
1. Download the Battery_Mod.zip.
2. Put it in your internal SD card.
3. Open CMW from your app drawer.
4. Choose "Flash update" (Flash and update .zip).
5. Browse for the Battery_Mod.zip file.
6. Flash it and enjoy!
DOWNLOAD
MJ ROM TRIAL VERSION 1.3 IS UP FOR FREE!
CLICK HERE TO DOWNLOAD
Download Big Android Battery Mod Here!
Download Honeycomb Battery Mod Here!
Screenshot as per below.
New screenshot for new release added (MJ - Trial version 1.3)!
{
"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"
}
NEW Battery MOD with Big Android!
New screenshot for new release added (MJ - Trial version 1.3)!
Credit:
Currently quite busy with modification. Will add in every help i got from this xda shortly.
Credit back to respective developers!
LP7 it's not AOSP man ! it's SAMMY-based.
by the way, welcome here and good luck in this jungle.
for the beginning, try to post some screenshoot, of course to full root your rom, choose a sympathic theme, put call recording and the new siyah kernel.
cya !
nesquix said:
LP7 it's not AOSP man ! it's SAMMY-based.
by the way, welcome here and good luck in this jungle.
for the beginning, try to post some screenshoot, of course to full root your rom, choose a sympathic theme, put call recording and the new siyah kernel.
cya !
Click to expand...
Click to collapse
thanks man! btw, is it legal to use theme provide here? can i use the mod they provide here? i scare i violate the rules or whatever copyright thingy.
U can use themes,apps and other mods from developers just ask their permission first and credit them in your op.
About supersu,you need to install(push) binary for it to work. Think it's binary is a xbin file, but not sure ask in chainfire thread.
anyways good luck with your project
zodiaxe66 said:
U can use themes,apps and other mods from developers just ask their permission first and credit them in your op.
About supersu,you need to install(push) binary for it to work. Think it's binary is a xbin file, but not sure ask in chainfire thread.
anyways good luck with your project
Click to expand...
Click to collapse
thanks for your hints and advise. really appreciate it.
edit: i think i found the reason on why my custom ROM is not rooted. it seems like i am using stock ROM unrooted, that's why it is not rooted. base on my research, i just have to flash the stock ROM, root it, flash kernel and old bootloader. back up, and start cooking afterward. correct me if i am wrong.
anyway, gonna try it tomorrow. used almost full day in trial and error, at least i can flash and run my first trial.
Mj rom trial version 1.2 is here!
MJ Rom Trial Version 1.2 is up!
Try it out for free!
Please don't flame me. Learning in progress.
New big android battery mod added!
Follow the steps below to flash it to my ROM:
1. Download the Battery_Mod.zip.
2. Put it in your internal SD card.
3. Open CMW from your app drawer.
4. Choose "Flash update" (Flash and update .zip).
5. Browse for the Battery_Mod.zip file.
6. Flash it and enjoy!
Might compile couple more battery mod to suit different people. Stay tune!
Bugs encounter. No worry, just a minor one.
Other than that, everything should work fine.
hi guys, thanks for trying out my own. i realise it is kinda messy, so i decide to try to recompile every for next release. hopefully the minor bug can be fixed.
give me sometimes as i am doing everything from scrap.
Good luck to u project .
milandhal said:
Good luck to u project .
Click to expand...
Click to collapse
thank you
MJ ROM Trial version 1.3 is up
{
"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"
}
Informations
Hey guys, today i will show DualBootPatcher one of the best apps for multi ROMs (i think this is the unique app for this ).
I have managed to support Samsung Galaxy Prime ( G530x )
I am not the creator, just the supporter
Disclaimer
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.
It patches...
Custom kernels for dual boot support
ROMs so that they can be installed as secondary
Google Apps packages for AOSP-based ROMs
SuperSU so that it can be used in the secondary ROM
What's supported?
Except Toaster and Alarm clocks pretty much everything is supported.
How to use the patcher
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
Instructions for dual booting
Before doing anything, download the Dual Boot Patcher app and the DualBootUtilities.zip 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
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?
You can flash the DualBootUtilities zip from recovery. It will provide a menu interface that allows switching to the various ROMs.
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".
Alternatively, flash the DualBootUtilities zip from recovery, which will also allow you to wipe a 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
Downloads:
I recommend against using the stable version of the patcher right now. So many changes have been made in regards to device support, ROM support, and general bug fixes that it's better to use the unstable snapshot builds until the next stable release is made.
[LINK] Dual Boot Patcher (Snapshots) and DualBootUtilities recovery zip
Source code:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Know Issues
- The ROMs section sometimes bug and get a infinite refresh, close the app and open app again.
- Simple Anouncement : Please refrain from using /system and /cache partitions for secondary rom install
Special Thanks
@chenxiaolong for the awesome DualBootPatcher.
XDA:DevDB Information
Dualboot Patcher G530x, Tool/Utility for the Samsung Galaxy Grand Prime
Contributors
faizauthar12
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Stable
Created 2017-03-26
Last Updated 2017-03-26
Reserved
Reserved
Here we go, the screenshots!
Can i use the stock rom as primary and other rom as secondary? Need help to this, haha
DexIdiotGT said:
Can i use the stock rom as primary and other rom as secondary? Need help to this, haha
Click to expand...
Click to collapse
Yes, that's the main reason why i port this tools
It means 2 different roms???
Dehieu2003 said:
It means 2 different roms???
Click to expand...
Click to collapse
Yes it is...
3, 4 or even 10 roms at once installed
Just like a dualboot or triple boot at desktop
faizauthar12 said:
Yes it is...
3, 4 or even 10 roms at once installed
Just like a dualboot or triple boot at desktop
Click to expand...
Click to collapse
Did you have a tutorial about this? I don't understand
Dehieu2003 said:
Did you have a tutorial about this? I don't understand
Click to expand...
Click to collapse
go to ROMs tabs to patch your current kernel with mbtool
then:
prepare your ROM that will be patched
open DualBoot Patcher app
go to Path Zips File
press the "+" icon
and press "Add flashable zip"
allow the permission...
choose the zip file ( rom )
now choose the partition configuration
Code:
Primary rom is the current rom..., use this option to update the rom..
Secondary till multi slot 3 will use system partition
Data slot will eat the internal storage..
Extsd slot will eat the external storage, Sdcard
after that give an ID for your rom
( this will give a dedicated folder for it)
if you give pacman rom with ID "1" , slot 1 will be reserved for pacman, if you want to upgrade it
go back to partition configuration then give the same ID..
patched?
flash it via recovery
faizauthar12 said:
Here we go, the screenshots!
Click to expand...
Click to collapse
Hey there,
I have tried this on my fortunave3g. My primary rom is stock 5.0 TouchWiz and I am trying to install AEX 4.6. But I am facing issues installing it. I followed the instructions given on the apps GitHub page.
Patched the ROM using the app and flashing it from the app, everything okay but stuck at "Patching system image unconditionally". I sat there for 1 hrs but nothing happen. So I closed that and tried installing it with TWRP. From there, it was able to create system.img and other images but it fails to run updater-script.
Have any idea why this happens?
Sent from my fortunave3g using XDA Labs
TLDR:
1: MAKE A BACKUP. Seriously.
2: Downloads in second post. Flash recovery, then kernel, then MultiROM.
{
"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"
}
Introduction
This is a port of Tassadar's MultiROM, a multi-boot mod for OnePlus 2. 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.
This is still experimental!
Make backups. Seriously. Please.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via USB-C OTG cable
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.
Installation
2.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.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP_multirom_oneplus2_YYYYMMDD.img) - download the IMG file from second post and use fastboot to flash it.
MultiROM (multirom-YYYYMMDD-vXX-oneplus2.zip) - download the ZIP file from second post and flash it in recovery.
Your current ROM will not be erased by the installation.
Adding ROMs
1. Android
Go to recovery, select 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 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 MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Note that swapping roms between internal and external is not supported (yet). Also, after flashing a factory image to the primary system and boot partition, make sure to immediately inject MultiROM before first boot, otherwise the secondary ROMs will be deleted.
Source code
MultiROM - https://github.com/nkk71/multirom/tree/master (branch master)
Modified TWRP - https://github.com/nkk71/Team-Win-Recovery-Project (branch android-7.1-mrom)
Device tree: https://github.com/MZO9400/device_oneplus_oneplus2-mrom -b twrp-mrom
Thanks
This port is based on the hard work of Tassadar, 500 Internal Server Error, Geoff Levand, webgeek1234, Mike Kasick, Npjohnson, Hashbang173, and many others. Thank you.
Issues
- None that are known. If you find one that this thread does not know about/hasn't answered (solid rule, read the last three pages of the thread befre reporting an issue), report it in the thread
- IF YOU GET LOCKED OUT OF YOUR DEVICE: Don't worry! Your data is fine. Simply boot to TWRP, choose 'Advanced' ==> 'Terminal Command' ==> type "rm -rf /data/system/gatekeeper.*.key" (without the quotes). This is a dirty fix, and should only be used to recover data, not as a permanent solution! After you recover your data, wipe /data (you don't have to wipe Internal Storage), and re-setup the device.
Changelog
Here
Downloads
Downloads in second post
NOTE:
Third party kernels with kexec-hardboot support (can be flashed to primary ROM): THIS IS NO KEXEC MultiROM, you don't necessarily need kexec hardboot supported kernels
Extra Information
Unlike some of the other 64-bit MultiROM ports, this port does have kexec-hardboot enabled, which is less risky and speeds up boot into secondary ROM. Anyone porting MultiROM to a Snapdragon 810 device may find the source to be useful. The patch was written by @500 Internal Server Error
XDA:DevDB Information
MultiROM for OnePlus2, Tool/Utility for the OnePlus 2
Contributors
MZO, nkk71, martinusbe
Source Code: http://github.com/multirom-dev
Version Information
Status: Stable
Current Stable Version: v33b
Stable Release Date: 2017-05-13
Current Beta Version: v33b
Beta Release Date: 2017-04-20
Created 2017-04-20
Last Updated 2017-05-13
MultiROM (folder):
DOWNLOAD
MultiROM v33b
TWRP MultiROM v3.1.1
MultiROM Uninstaller
MultiROM manager modified with OP2 commits has been attached to this post
Method of flashing multirom.
________________
1. Go to TWRP 3.1.0 officially that u already have
2. Flash the multirom image file .. and select recovery when it asks whether u want boot or recovery.
3. When successful go back to maim page and hit reboot recovery
4. Now its multirom
5. Flash the provided multirom zip file. An auto reboot will occur. Hit cancel and go to MISC tab to hit reboot recovery
6. Now the existing rom u had , is primary
7. Go to 3 dot menu of TWRP on upper right corner.
8. Select add rom
9. Flash desired rom
10. Reboot recovery again when successful
11. Go to 3 dot menu again and select list rom
12. Tap on add zip file and add gapps here... That is whatever u file want to flash on a rom just select that rom from rom list and add zip from there
[when flash a secondary, u have to flash zip, then back, and add zip and flash gapps]
13. Hit reboot system.
14. Now a screen will appear even before boot to.ask which rom u want to flash. For the very first time the option is set to, if u don't select any it will boot to primary after 5 seconds, so u hit cancel on that screen (pop up actually)
15. Select the desired rom , double tap on it and it will boot.
First boot of a new rom takes at least 15 to 20 real life minutes.
Notes:
__
To change the option of count down of rom booting selection, go to settings of multirom twrp and turn off option from there. Now every time u reboot.. it will ask which rom u want to boot. And if u don't select any it will stay on same screen till u click something
Tested so far:
Nougat based ROMs
OOS stock
OOS based ROMs
H2OS
MIUI
FlyME
Okay so @Tomsgt has made an amazing guide on how to set up and run MultiROM for our device (or any device), you can find his video right here:
<Mod Edit: Link removed for promoting paid service.>
Awesome work
Yay
btw, link to devicetree doesn't work. found it anyway https://github.com/AOSP-JF-MM/platform_device_oneplus_oneplus2/commits/aosp-7.1.2_mrom
martinusbe said:
Yay
btw, link to devicetree doesn't work. found it anyway https://github.com/AOSP-JF-MM/platform_device_oneplus_oneplus2/commits/aosp-7.1.2_mrom
Click to expand...
Click to collapse
Fixed!
Was getting installation aborted error...removed device check and installed successfully...
Thanks...
[email protected] said:
Was getting installation aborted error...removed device check and installed successfully...
Thanks...
Click to expand...
Click to collapse
Probably because of the ROM. It might need more tags since we can't agree on ONE name
MZO said:
Probably because of the ROM. It might need more tags since we can't agree on ONE name
Click to expand...
Click to collapse
Its working fine now...awesome work... :good:
Great man, thanks a lot.
Sent from my ONE A2003 using XDA-Developers Legacy app
MZO said:
Fixed!
Click to expand...
Click to collapse
cool, thanks for keeping authorship btw
martinusbe said:
cool, thanks for keeping authorship btw
Click to expand...
Click to collapse
My pleasure used your commits and you helped me in the final stage — well deserved!
MZO said:
Probably because of the ROM. It might need more tags since we can't agree on ONE name
Click to expand...
Click to collapse
maybe add some of the known used ones here https://github.com/AOSP-JF-MM/platf...lus2/blob/aosp-7.1.2_mrom/BoardConfig.mk#L231
martinusbe said:
maybe add some of the known used ones here https://github.com/AOSP-JF-MM/platf...lus2/blob/aosp-7.1.2_mrom/BoardConfig.mk#L231
Click to expand...
Click to collapse
Yes! I have done that locally — not sure what other devices names to add. If @[email protected] would let me know his device name I'd be obliged ?
MZO said:
Yes! I have done that locally — not sure what other devices names to add. If @[email protected] would let me know his device name I'd be obliged ?
Click to expand...
Click to collapse
yea, not sure if that takes a comma separated list
been a while since i looked at it all, but i think i didn't have a comma in there on op3
martinusbe said:
yea, not sure if that takes a comma separated list
been a while since i looked at it all, but i think i didn't have a comma in there on op3
Click to expand...
Click to collapse
Yep it worked with commas. Uploading now two more names: Oneplus2 (pretty common), onePlus2 (what was I thinking??)
Will i need to wipe internel storage for first time
ShaDow18 said:
Will i need to wipe internel storage for first time
Click to expand...
Click to collapse
No you won't.
MZO said:
No you won't.
Click to expand...
Click to collapse
What about recovery do i really need fastboot mode or flasify can also do
*** Disclaimer
Code:
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 the instructions or the linked things before doing anything!
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 and I promise, I will!
Introduction
I decided I wanted a more up-to-date CM11 build, so here it is, a new build of LineageOS 11, for D605!
Images
{
"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"
}
Features
* Quite default LineageOS 11 but with USB OTG and offline charging
Installation instructions
* Under construction
Changelog
* Creating once finished
Downloads
Checksums:
* Uploading once finished
Download
* Uploading once finished
Sources
* https://github.com/Avamander/android_device_lge_d605
* https://github.com/Avamander/android_kernel_lge_d605
FAQ
* Under construction
Thanks To/Credits
Code:
* Varcain
* Puresoul_CZ
So, let me know if you're even interested.
XDA:DevDB Information
LineageOS 11 for D605, ROM for all devices (see above for details)
Contributors
Avamander, Varcain, Puresoul_CZ
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: LineageOS
Version Information
Status: Abandoned
Created 2017-09-25
Last Updated 2020-07-04
Planned:
* Fix to reallow XPosed
Thanks Avamander! I'll test your ROM asap! Thank you again for your efforts!
ps: is the new build including the WiFi CRAK fix?
ps2: do you have any resource where to find any guide to compile it?
thePanz said:
Thanks Avamander! I'll test your ROM asap! Thank you again for your efforts!
ps: is the new build including the WiFi CRAK fix?
ps2: do you have any resource where to find any guide to compile it?
Click to expand...
Click to collapse
About CRACK, haven't checked, not sure a patch has been released for LOS11, if it has after the build date, let me know and I'll rebuild it.
I used the this https://wiki.lineageos.org/devices/d855/build but replaced d855 in commands with d605 and manually downloaded the sources to the according folders.
@Avamander: I tried to install your LineageOS ROM on top of a CM11 (by Varchain, the v11 release), but I get a "Status 7" error.
The error reports "set_metadata_recursive: some changes failed"
Checked the MD5 of the ZIP file and it is correct, both on my PC and on the SD.
Can you help me with the installation?
thePanz said:
@Avamander: I tried to install your LineageOS ROM on top of a CM11 (by Varchain, the v11 release), but I get a "Status 7" error.
The error reports "set_metadata_recursive: some changes failed"
Checked the MD5 of the ZIP file and it is correct, both on my PC and on the SD.
Can you help me with the installation?
Click to expand...
Click to collapse
Did you wipe /system (and /cache) and are you using TWRP v2.6.3.0 (that's what I use)?
Avamander said:
Did you wipe /system (and /cache) and are you using TWRP v2.6.3.0 (that's what I use)?
Click to expand...
Click to collapse
I was using a CWM version 2, and I had to update to the latest v3 (from Varchain, :
https://mega.nz/#!QXZUnbwQ!BRI3ENa-53StAjr2Tq1R-hmyIJ9ZDERWIAxXpx9Hye4) and it is now installing. Or do you suggest to update to TWRP?
I'll test it now.
thePanz said:
I was using a CWM version 2, and I had to update to the latest v3 (from Varchain, :
https://mega.nz/#!QXZUnbwQ!BRI3ENa-53StAjr2Tq1R-hmyIJ9ZDERWIAxXpx9Hye4) and it is now installing. Or do you suggest to update to TWRP?
I'll test it now.
Click to expand...
Click to collapse
Let me know if the latest works. If it doesn't, let me know if TWRP works
Avamander said:
Let me know if the latest works. If it doesn't, let me know if TWRP works
Click to expand...
Click to collapse
Ok, CWM v3 installed and Lineage-v11 installed, too.
The install went OK. Few issues encountered so far:
1. looks like the phone WiFi is configured for US area (thus, only channels 1-11 are working, but not mine, as it was configured on channel 13. I had to use https://forum.xda-developers.com/showthread.php?t=1982149 to properly fix it. Would be great if the ROM comes with the 1-13 set of channels.
2. Installing TitaniumBackup: install ok, but it did not run, ADB reported "libtitanium.so not found". Looks like the v8.1.0 is not able to extract the ARM library. I had to extract it from the APK (found here https://www.androidapksfree.com/apk/titanium-backup-apk-latest-version-download/download/) and manually push the library with "adb push libtitanium.so /data/data/com.keramidas.TitaniumBackup/files/"
Couldn't find anywhere else why those errors are caused. Do you have the same behaviour?
btw: thanks for your effort in keeping the D605 alive
thePanz said:
Ok, CWM v3 installed and Lineage-v11 installed, too.
The install went OK. Few issues encountered so far:
1. looks like the phone WiFi is configured for US area (thus, only channels 1-11 are working, but not mine, as it was configured on channel 13. I had to use https://forum.xda-developers.com/showthread.php?t=1982149 to properly fix it. Would be great if the ROM comes with the 1-13 set of channels.
2. Installing TitaniumBackup: install ok, but it did not run, ADB reported "libtitanium.so not found". Looks like the v8.1.0 is not able to extract the ARM library. I had to extract it from the APK (found here https://www.androidapksfree.com/apk/titanium-backup-apk-latest-version-download/download/) and manually push the library with "adb push libtitanium.so /data/data/com.keramidas.TitaniumBackup/files/"
Couldn't find anywhere else why those errors are caused. Do you have the same behaviour?
btw: thanks for your effort in keeping the D605 alive
Click to expand...
Click to collapse
I will investigate the WiFi issue... The TiBu issue, sounds weird, though a lot of old exploits have been patched and some apps might be expecting they exist. Though in my case I could install TiBu without issues from Google Play. I updated the planned task list.
Avamander said:
I will investigate the WiFi issue... The TiBu issue, sounds weird, though a lot of old exploits have been patched and some apps might be expecting they exist. Though in my case I could install TiBu without issues from Google Play. I updated the planned task list.
Click to expand...
Click to collapse
Thank you!
As a side note: CWM v3 is also able to lokify the ROM after flashing Varchain added it "because I am lazy" (cit.)
thePanz said:
Thank you!
As a side note: CWM v3 is also able to lokify the ROM after flashing Varchain added it "because I am lazy" (cit.)
Click to expand...
Click to collapse
That means it would still break the signature if I would release a signed image.
Quick update: the offline-charging is not working.
Switching off the phone and connecting the charger will boot up the phone in the default mode, not "only charging".
I know this might be a minor bug but auto brightness doesn't work.
DJ-SMOKE_300 said:
I know this might be a minor bug but auto brightness doesn't work.
Click to expand...
Click to collapse
Never has, never will, there's no brightness sensor hardware.
Avamander said:
Never has, never will, there's no brightness sensor hardware.
Click to expand...
Click to collapse
Oh. Thanks for clearing that up. All in all its mostly stable. :good:
Another thing i noticed is that some system processes crash at random times. And if I have my own wallpaper set if that happens and I reboot the device it resets.
DJ-SMOKE_300 said:
Another thing i noticed is that some system processes crash at random times. And if I have my own wallpaper set if that happens and I reboot the device it resets.
Click to expand...
Click to collapse
Seen that happen a few times, but without logs of the crash I can't help you.
1. Please remove the space character from the link to md5 for ROM.zip. I think it is easier to place a checksum instead of a link.
2. Last edited by Avamander; 26-12-2017 at 23:23. Reason: New build revert.
Has the file changed on the server, has it been refreshed or something else?
---------- Post added at 23:26 ---------- Previous post was at 23:11 ----------
Avamander said:
(...)
Installation instructions
* Use TWRP, wipe everything, (...)
Click to expand...
Click to collapse
Is there really a reason to clean Internal storage and sdcard?
> 1. Please remove the space character from the link to md5 for ROM.zip. I think it is easier to place a checksum instead of a link.
It's more work to create the file for the recovery to verify it. The space is part of the link.
> 2. Last edited by Avamander; 26-12-2017 at 23:23. Reason: New build revert.
Has the file changed on the server, has it been refreshed or something else?[
Nope
> Is there really a reason to clean Internal storage and sdcard?
Internal storage? If you mean /data, yes, but /sdcard doesn't need to be wiped.
As a sidenote, I've been rebuilding the entire system today, will see if that brings back the WiFi.