Related
Hi All,
Here is a new version of my boot manager.
If you didn't see first release, its purpose is to allow dual boot a firmware with two different kernels with a third one that manages boot selection:
{
"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"
}
Here is a demo of the previous version, it behaves almost the same:
Since first release, I added cwmod and twrp support for both build:
First build is run from native partition, and second build is installled on internal storage via loopbacks. Since first release, I added automatic loobpack creation:
CWM will take care of formatting them.
FIRST A BIG WARNING: all you'll see here is highly experimental, I'm not responsible for any damage or problem it could cause.
I don't have any idea if running a build on loops is wearing off flash memory, it could damage your device.
I don't think it dramatically change anything compared to standard wear on native partitions, but who knows... And something else could go wrong.
Pre-requisite
Currently, if you don't want to loose your current data, you have to be on a rom that has already be repackaged. By default, bootmanager installs Sony 6.1.A.2.55 kernel, so if you're using this firmware, no need to reflash it. For all the other roms, you will have to reflash the repackaged zip in the list below after installation. Don't wipe data/factory reset and you should be good to go. In both case, backup your stuff with Titanium Backup or something else!
Note: you won't be able to restore your previous cwm backups!
Installation:
Minimal setup:
Download bootmanager_0.8.zip (mirrors) (previous version bootmanager_0.6.zip).
Download one of the modified custom firmware in the list below
Install bootmanager zip from your current recovery or extract dual.elf and flash it from fastboot.
Reboot
If your previous rom was not 6.1.A.2.55 based (like cm10 or aokp for instance), reflash your firmware from TWRP for native with one of the native firmware listed below.
Reboot
Now, if you want to use dual boot functionnality:
Select TWRP for loopback
The first time, as you don't have loopbacks files on your internal storage, it will ask for system and data partition sizes. Be patient, it could take time to create them.
When finally recovery is displayed, select erase data/factory reset
then do erase system in partitions/format system
loopbacks are now ready, you can flash one of the available build repackaged for loop.
optionally flash regular google apps from here.
Upgrade from 0.6 or higher:
Upgrade should keep your existing firmwares,
optional, but highly recommended, backup your stuff with cwm and/or Titanium backup.
start stock or custom recovery
flash bootmanager_0.8_upgrade.zip (mirrors)
reboot
re-enable dual boot in settings
Recoveries:
Starting with 0.8, offline charging has been added to twrp. As it's not possible to add to cwm, it is highly recommended to stay on twrp and avoid cwm as it's much safer for your phone.
Starting with 0.5, you can choose between cwm and twrp and switch as you wish. Just flash with your current recovery the recovery you want:
- TWRP 0.8.0 (mirrors) (previous TWRP 0.6.1)
- CWM 0.8.0 (mirrors) (previous CWM 0.6.0)
- EXPERIMENTAL, please read this before installing, TWRP 0.8.2 TWRP 2.6.0 and new 3.4 bootmanager kernel.
Firmwares
Stock / native partitions (flash them from stock recovery)
Sony 6.1.A.2.45 (don't pay attention to filename, this is 2.45, not 2.56, it's a silly typo). Note: you don't have to flash it if you have stock already, it will become useful only later on.
Sony 6.1.A.2.45 addon unsecure kernel, Sony stock kernel only, with ro.secure=0
Sony 6.1.A.2.45 addon kernel modules, Flash this is you have wifi problem, (mostly useful if your firmware was using a custom kernel).
Sony 6.1.A.2.50 stock firmware with unsecure kernel.
Sony 6.1.A.2.50 addon Standalone unsecure kernel.
Sony 6.2.B.0.211 stock firmware, rooted, with busybox.
FXP 137 CM 9.1, original firmware thread here.
AOKP ICS m6 beta 1, thanks to Apology11 for repack! original firmware thread here.
Krabappel2548's KA19, mirrors, original firmware thread here.
Sony 6.1.A.2.55, mirrors, untested unsecure kernel only here.
FXP 147 CM 10, mirrors, original firmware thread here.
PA 2.55 17/11/2012, mirrors, original firmware thread here (kernel from FXP147)
AOKP JB Milestone 1 r1, mirrors, original firmware thread here.
FXP 148 CM 10, mirrors, original firmware thread here.
PAC 18.0.0, mirrors, original firmware thread here
FXP 150 CM 10, mirrors, original firmware thread here.
PA 2.55.1 17/11/2012, mirrors, original firmware thread here
FXP 150a CM 9.1, mirrors, original firmware thread here.
FXP 151 CM 10, mirrors, original firmware thread here.
Nova Xperia RC1, mirrors, original firmware thread here.
FXP 152 CM 10, mirrors, original firmware thread here.
PAC 18.0.2, mirrors, original firmware thread here
Nova Xperia RC2, mirrors, original firmware thread here.
Hei1125's unofficial cm10 20130109, original thread firmware here.
FXP 201 CM 10, original firmware thread here.
FXP 206a CM 10, original firmware thread here.
My JB 4.2.2 aosp build, beta 2, thread is here.
My JB 4.2.2 aosp build, beta 3, thread is here.
My JB 4.3 aosp build, alpha 0, thread is here.
My JB 4.3 aosp build, alpha 1, thread is here.
Custom / loopback partitions (flash them from custom recovery)
Sony 6.1.A.2.50 (buggy, will update soon).
Sony 6.1.A.2.50, kernel only.
Sony 6.1.A.2.55, mirrors (tested, is working properly).
Sony 6.2.B.0.211, stock firmware, rooted, with busybox.
MIUI 2.9.7, mirrors, original firmware thread here.
AOKP ICS m6 alpha 2, original firmware thread here.
Krabappel2548's KA19, mirrors, original firmware thread here.
FXP 145 CM 9.1, mirrors, original firmware thread here.
FXP 147 CM 10, mirrors, original firmware thread here.
PA 2.55 17/11/2012, mirrors, original firmware thread here (kernel from FXP147).
AOKP JB Milestone 1 r1, mirrors, original firmware thread here.
Sony stock Gingerbread 6.0.A.3.75 UK, mirrors. (enabling data makes the phone reboot for me, baseband/radio problem).
Sony 6.1.A.2.55 unsecure kernel only, mirrors
XTXperience 7, mirrors, original firmware thread here. Flash 6.1.A.2.55 kernel with it.
FXP 148 CM 10, mirrors, original firmware thread here.
PAC 18.0.0, mirrors, original firmware thread here
MIUI 2.11.5, mirrors (you have to flash one of these kernels)
FXP 150 CM 10, mirrors, original firmware thread here.
PA 2.55.1 17/11/2012, mirrors, original firmware thread here
FXP 150a CM 9.1, mirrors, original firmware thread here.
Nova Xperia RC1, mirrors, original firmware thread here.
FXP 152 CM 10, mirrors, original firmware thread here.
PAC 18.0.2, mirrors, original firmware thread here
PAC 19, original thread here.
Nova Xperia RC2, mirrors, original firmware thread here.
JellyBear 3.35, original firmware thread here.
Hei1125's unofficial cm10 20130109, original thread firmware here.
FXP 201 CM 10, original firmware thread here.
XTXperience 8.1, original firmware thread here.
FXP 206a CM 10, original firmware thread here.
Ubuntu Touch 0.0.0, thread is here. Note: BIG 540 MB download. It installs on a separate 1.2 GB loopback created by the installation zip.
DooMLoRD Sony JB 6.2.B.0.197 leak, original thread here, credits goes to DooMLoRD
My JB 4.2.2 aosp build, beta 2, thread is here.
My JB 4.2.2 aosp build, beta 3, thread is here.
My JB 4.3 aosp build, alpha 0, thread is here.
My JB 4.3 aosp build, alpha 1, thread is here.
Mirrors of few builds, thanks to elpelas
Repackager package for linux 64 bits, unzip and untar, run as root: ./repackage.sh source_file out_name
DONATIONS
Thanks to @rolex0815 for his donation!
FAQ
- Can I flash any update zip with BootManager ?
Most of the time, no. Some may work unmodified, like google apps that mounts system without using explicit partition. But most of the zips found here mounts directly native partitions so they won't work for build installed on loops. Last, all the kernel zips have to be modified. Flashing any unrepackaged kernel zip will replace boot manager completely and will kill it.
- Can I restore my previous CWM backups after installing bootmanager ?
Yes and no. Yes if you want to go back to where you were before installing bootmanager. No if you want to keep boot manager: restoring the backup will erase it.
Known issues
- Moved apps (to storage/sdcard) will disappear when booting from one build to another. I presume it happens because both builds are sharing storage and it messes up ext2sd scheme. As a workaround, move apps back to internal. This is not a boot manager issue per se, but it's more related to the way builds are repackaged, it probably requires different location for ext2sd. I'll take a look someday.
- Recoveries backups will backup/restore all kernels at once instead of of doing each one separately.
History
2013/02/21: version 0.8
- Offline charging embedded in TWRP, bootmanager is no longer using native build to provide it.
- 1 GB system loop size added
Note: Offline charging can't be added to CWM so CWM is not recommended anymore, TWRP is safer for power management.
2013/01/28: version 0.7
- New settings menu, single boot/dual boot, boot manager protection enable/disable, alternate enable/disable
- Default is now single boot: in this mode, boot manager is only using one kernel and is only providing separate recovery for it.
- TWRP upgraded to v 2.3.3.0
- Only released with aosp build
2012/11/20: version 0.6
- Default recovery is now twrp
- Default kernel is now from 6.1.A.2.55 firmware
- TWRP updated to fix keyboard in backups
- Boot menu now remember which kernel was launched and defaults to it at next boot.
- Bootmanager protection: flashing a kernel that hasn't been repacked should fail. Temporary protection removal here if you want to get rid of bootmanager with a normal firmware.
- Native partition protection: flashing from loop recoveries should not be able to mount native partitions
- Kernel flasher bug fix: layout should now be calculated properly and big kernels shouldn't trash bootmanager anymore
- Notification led color changes depending on which recovery is launched
- ram_console is now properly handled by boot manager kernel. From now on, you should go to a recovery to get the last_kmsg for a crashing kernel.
- Boot manager can be flashed from recoveries.
2012/10/20: version 0.5
- flashable recoveries (cwm and twrp)!
- new kernel layout to give more space to loop kernel
- boot menu delay countdown fix
- offline charging forwarded to native build
- pre-installed kernel is now 6.1.A.2.50 one.
- added recoveries for alternate (re-partitioned devices only)
2012/10/06: version 0.4
- initramfs location moved to 0x41500000 for aokp and cm10 compatibility
- debug traces left in cwm removed
- new kernel extraction command (ke)
2012/10/02: version 0.3
- cwm recovery bugfix to get proper Aroma colors.
- stock / custom name changed to native / loopback in menus.
- added menu for cache loopback to adjust cache size.
2012/09/10: version 0.2
- CWMod recoveries are now working for stock (native) and custom (loopbacks).
- Loopbacks files are created if they are missing with multiple sizes.
2012/09/04: version 0.1
- Initial release, original thread here.
For devs:
Source code:
Trimmed kernel uploaded to gitorious here , branch bootloader_kernel.
Boot menu (FBMenu, thanks to openAOS for initial release!) here.
Embedded kernel flasher kf : here.
Elf kernel splitter sksplit here. I use it mostly to extract kernel and cpio in repackaging firmware.
Background:
Here are some details on how it works:
I trimmed down a stock kernel to remove some fat and add a driver to set a specific memory location.
I embed a small assembly loader with this kernel and its cpio plus the other 2.
The tiny kernel is loaded first, it displays the menu and eventually starts cwm. The menu will set the memory location with the kernel choice, then reboot.
At next reboot, the assembly loader will detect the kernel choice and start the appropriate kernel.
So, in fact, you're booting two times, first the small loader, then the real boot.
It adds some boot time, but it's not dramatic. The advantage is that it's easy to build the loader, it's a simple init. Second advantage, the second kernel is running on a "fresh" start, no left-over in memory, no kexec patch to apply, it works with any kernel. Last, cwm can be embedded with the tiny kernel, so it's finally independent from the build kernel.
Repack sample, FXP137 cm9.1:
unzip ../downloads/FXP137-cm-9-20120908-UNOFFICIAL-nozomi.zip
sksplit boot.img
sudo su
mkdir cpio
cd cpio
cat ../sec1-0x41300000.bin | gzip -d | cpio -i --make-directories
emacs init.semc.rc
Code:
# mount mmc partitions
# mount /system, set up links to the modem, and remount r/o
mount ext4 /dev/block/mmcblk0p12 /system wait rw barrier=1
mkdir /system/etc/firmware/misc 0771 system system
mount ext4 /dev/block/mmcblk0p12 /system wait ro barrier=1
setprop ro.crypto.tmpfs_options size=128m,mode=0771,uid=1000,gid=1000
mount ext4 /dev/block/mmcblk0p14 /data wait noatime nosuid nodev data=ordered noauto_da_alloc
mount ext4 /dev/block/mmcblk0p13 /cache wait noatime nosuid nodev data=ordered noauto_da_alloc
becomes:
Code:
# losetup on storage
mkdir /sd
mount vfat /dev/block/mmcblk0p15 /sd wait rw
# ro directly as misc is created by install script
mount ext4 [email protected]/sd/custom_system.ext4 /system wait ro barrier=1
setprop ro.crypto.tmpfs_options size=128m,mode=0771,uid=1000,gid=1000
mount ext4 [email protected]/sd/custom_data.ext4 /data wait noatime nosuid nodev data=ordered noauto_da_alloc
mount ext4 [email protected]/sd/custom_cache.ext4 /cache wait noatime nosuid nodev data=ordered noauto_da_alloc
and:
Code:
exec sbin/bootrec
becomes
Code:
exec /system/bin/chargemon
and save
rm init.semc.rc~
cd sbin
rm e2fsck bootrec bootrec-device fix_permissions killrecovery.sh mke2fs nandroid-md5.sh parted postrecoveryboot.sh sdparted tune2fs
cd ..
find . | cpio -o -H newc | gzip > ../initramfs.cpio.gz
cd ..
rm -r cpio sec2-0x00020000.bin sec1-0x41300000.bin boot.img
mv sec0-0x40208000.bin zImage
emacs META-INF/com/google/android/updater-script
Code:
format("ext4", "EMMC", "/dev/block/mmcblk0p12", "0");
mount("ext4", "EMMC", "/dev/block/mmcblk0p12", "/system");
becomes
Code:
format("ext4", "EMMC", "/dev/block/loop2", "0");
mount("ext4", "EMMC", "/dev/block/loop2", "/system");
then
Code:
package_extract_file("boot.img", "/dev/block/mmcblk0p3");
becomes
Code:
package_extract_file("zImage", "/tmp/zImage");
package_extract_file("initramfs.cpio.gz", "/tmp/initramfs.cpio.gz");
assert(run_program("/sbin/kf", "2", "/tmp/zImage", "/tmp/initramfs.cpio.gz") == 0);
add before this :
Code:
show_progress(0.200000, 0);
show_progress(0.200000, 10);
this:
Code:
run_program("/sbin/busybox", "mkdir", "/system/etc/firmware/misc");
set_perm(1000, 1000, 0771, "/system/etc/firmware/misc");
and save, then finally:
zip -r ../cm9-loop.zip *
Repack Sample, 6.1.A.2.45 firmware on stock/native:
mkdir stock_6.1.A.2.45_zip
cd stock_6.1.A.2.45_zip
7z x ../downloads/LT26i_6.1.A.2.45_GENERIC_NL.7z
7z x "LT26i_6.1.A.2.45_GENERIC NL.ftf"
rm "LT26i_6.1.A.2.45_GENERIC NL.ftf"
mkdir zip_out
sin2raw kernel.sin kernel.elf
sksplit kernel.elf
mv sec0-0x40208000.bin zip_out/zImage
mv sec1-0x41300000.bin zip_out/initramfs.cpio.gz
sin2raw system.sin system.ext4
sudo su
mkdir system
mount -o loop -t ext4 system.ext4 system
cd system
... optionally add root, busybox:
cp -r /home/tama/supersu/system/* .
cd xbin
chmod 6755 su
cp /home/tama/cm9/out/target/product/gen9/system/xbin/busybox .
cp /home/tama/relink-busybox.sh .
chmod 755 relink-busybox.sh
cd ../..
tar -cvzf zip_out/system.tgz system
... get script from cm9, ..
cd zip_out
cp -a ../../fxp137_cm9_ziploop/META-INF .
emacs META-INF/com/google/android/updater-script
Code:
assert(getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "LT26a" || getprop("ro.build.product") == "LT26a" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi");
ui_print("LT26i 6.1.A.2.45 firmware for boot manager (stock)");
show_progress(0.100000, 5);
format("MTD", "system");
mount("MTD", "system", "/system");
show_progress(0.700000, 60);
package_extract_file("system.tgz", "/tmp/system.tgz");
assert(run_program("/sbin/tar", "-cvzf", "/tmp/system.tgz") == 0);
show_progress(0.200000, 10);
assert(run_program("/system/xbin/busybox-relink.sh", "");
unmount("/system");
package_extract_file("zImage", "/tmp/zImage");
package_extract_file("initramfs.cpio.gz", "/tmp/initramfs.cpio.gz");
assert(run_program("/sbin/kf", "1", "/tmp/zImage", "/tmp/initramfs.cpio.gz") == 0);
ui_print("Firmware installation complete");
Repackage sample, KA14 with Aroma installer
Code:
sudo su
mkdir ka14
cd ka14
unzip /home/tama/sony/downloads/KA14_Xperia_SSpeed.zip
mv zImage zImage.original
sksplit zImage.original
mkdir cpio
cd cpio
cat ../sec1-0x41300000.bin | gzip -d | cpio -i --make-directories
rm *~
rm init
rm init_gb
mv init_ics init
rm recovery.*
rm -r res
rm 1
rm init.sh
cd sbin
rm tune2fs sdparted parted nandroid-md5.sh nandroid mr mke2fs killrecovery.sh fota-ua fota-mke2fs fix_permissions e2fsck checkabortedflash autoroot.sh
ln -s /init ueventd
cd ..
find . | cpio -o -H newc | gzip > ../initramfs.cpio.gz
cd ..
mv sec0-0x40208000.bin zimage
emacs META-INF/com/google/android/updater-script
change:
Code:
assert(package_extract_file("zImage", "/tmp/zImage"),
write_raw_image("/tmp/zImage", "/dev/block/mmcblk0p3"),
delete("/tmp/zImage"));
to:
Code:
package_extract_file("zimage", "/tmp/zimage");
package_extract_file("initramfs.cpio.gz", "/tmp/initramfs.cpio.gz");
assert(run_program("/sbin/kf", "1", "/tmp/zimage", "/tmp/initramfs.cpio.gz") == 0);
Code:
zip -r ../bm_native_ka14.zip META-INF customize system zimage initramfs.cpio.gz
AOSP experiment
Special build, aosp 4.2.1 experiment!
This one is special and deserve specific instructions.
First, it's not functional, and will never be.
I just wanted to have a look at current status of AOSP experiment for Xperia S, it required much more fiddling than reasonable and ended into a monster.
Again, I take no responsability if you flash this. It doesn't work properly, it's not tested, it can be bad for your phone .
Second, if you want to install this, read carefully instructions, it's not packaged like a normal loop rom.
Last: special thanks to FXP team, it wouldn't have been this far with the work they did on CM10. I took few binaries from FXP release and few patches from Cyanogen repo, no way to make it run without the work they did.
Now, that the warning are there, here is the status:
What's working:
1) It boots
2) Audio
3) Phone call/sms
4) Wifi
What's not working:
1) Data
2) Storage
3) And much more
Pre-Installation:
1) You need around 2G free space on storage
2) It will replace your loop kernel but keeps the loopback files untouched
3) If you want to save your current kernel, you can do this from loopback recovery with adb:
Code:
adb shell ke 2 /tmp/zimage /tmp/initramfs
adb pull /tmp/zimage
adb pull /tmp/initramfs
Installation
From loopback recovery, install zip file.
Restore previous loopback rom
Flash build zip file without wiping data/cache
or if you saved your kernel previously:
Code:
adb push zimage /tmp
adb push initramfs /tmp
adb shell kf 2 /tmp/zimage /tmp/initramfs
adb shell sync
then boot your loopback build.
Download
Download rom here, mirrors.
FAQ
1) What is this ?
I started this to check status of Google/Sony AOSP experiment. I wanted to see how far they went and how it behaves.
2) Why not making it functional ?
As it is, it's not worth it. To have the running state I have, I had to patch google aosp source, patch kernel, fiddle with FXP binaries, etc... This build is a Frankenstein monster and it would take quite a big amount of work to end up with something that takes many things from CM and doesn't work as good as CM.
We'll see if Sony goes further in releasing proprietaries and source code, but without that, AOSP will end up in CM without CM bonus
Wow, this is far more superior than 0.1!
So now I can install every ROM on loops?
Vipitus said:
Wow, this is far more superior than 0.1!
So now I can install every ROM on loops?
Click to expand...
Click to collapse
No, that's not possible, you need adapted zip for it. Maybe in a future version, but I think it would be very difficult to patch cpio's on the fly.
I'll continue adapting few builds to give more choice though.
For now only CM9, yes?
---------- Post added at 10:02 PM ---------- Previous post was at 10:00 PM ----------
letama said:
(...)First make sure that your stock firmware is 6.1.A.2.56
Click to expand...
Click to collapse
Do this firmware exists?
Do you mean 6.1.A.2.45?
Oups, Yes, too much writing sorry typo fixed, thanks for noticing.
Cm9.1 only, I'll add more later on, cm10 is difficult because of uncompressed kernel, any other firmware in mind?
letama said:
Cm9.1 only, I'll add more later on, cm10 is difficult because of uncompressed kernel, any other firmware in mind?
Click to expand...
Click to collapse
AOKP JB, MIUI (on stock kernel)
AOKP is using CM10 kernel, so same problem, the 10+MB uncompressed kernel doesn't fit. I'll do MIUI first, it should be quicker...
make a stock + jb dual kernel too
thats needed most right now
Sent from my Xperia S using xda app-developers app
Letama sry i know you are tired but i didnt understand this with pack and repack stuff.
Do i have to do that by my self, or just flash and do what you write in first post?
And then i can switch from one rom to another on the go?
Sent from my LT26i
Seems download link for Cm9 is broken .
Sent from my Xperia S using xda premium
championswimmer said:
make a stock + jb dual kernel too
thats needed most right now
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
+1
I usually don't do that, but I agree. Stock + JB is a must, I guess...
Sent from my LT26i with Tapatalk 2
This is really nice! Fascinating...
Great Job!
I have a Q ? I tried it many times when I finished flash the CM9.1 over the Custom kernel. It always boot on custom kernel. It doest show for me 2 choises like in your video @@
Do I must use 2 roms only in your first page ??
[ROM][JB 4.1.2][Xperia S/SL] MIUI V5 MULTILANG UB [3.10.25] - CM10 BASED - STOPPED DEVELOPMENT
{
"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"
}
DEVELOPMENT OF THIS ROM IS STOPPED - THANK YOU FOR YOUR SUPPORT DURING THE TIME
NEW MIUI V5 ROM FOR SONY XPERIA S/SL - BASED ON SONY STOCK FW.96 IS NOW COMPLETELY BUG FREE AND WORKS MUCH BETTER THAN THIS CM10 BASED VERSION
NEW MIUI V5 ROM WORKING ON DEVICES WITH LOCKED/UNLOCKED BOOTLOADERS
STOCK BASED MIUI V5 ROM FOR SONY XPERIA S/SL LINK
ROM AUTHORS:
FD-Ghost - http://www.miui.com/space-uid-31268862.html
City Of Zero - http://www.miui.com/home.php?mod=space&uid=100209901
Midnight Souls (kin912) - http://www.miui.com/home.php?mod=space&uid=176034
BalcanGSM - http://en.miui.com/space-uid-84584497.html
ROM INFORMATION:
- Rom Base:
FreeXperiaTeam CM 10 (JB 4.1.2) FXP234 Release For Sony Xperia S LT26i (Nozomi) - http://freexperiaproject.com/
- MIUI Base(Closed Source):
Xiaomi MIUI V5 (JB 4.1.2) Weekly Release For Google Nexus - http://www.miui.com/getrom.php
- ROM Modifications:
Xiaomi MIUI Patchrom Adaptation For OTA Update Support And Various Bugfixes - https://github.com/MiCode/patchrom
- Kernel Base:
FreeXperiaTeam CM 10 FXP234 Android JB 4.1.2 Kernel (Version 3.4) - http://code.google.com/p/freexperia/
- Kernel Modifications :
Modified Base Kernel (No Source) - Tutorial For MIUI JB 4.1.2:
Adding ShellD Support
Add The Following To init.rc At The End With Other Main Classes:
Code:
[B][SIZE=2][COLOR=Blue]service shelld /system/xbin/shelld class main [/COLOR][/SIZE][/B]
Security Changes
Modify Following In default.prop Following Structure Of Other Main Classes:
Change ro.secure line to:
Code:
[SIZE=2][COLOR=Blue][B]ro.secure=0 [/B][/COLOR][/SIZE]
Delete The Following Line:
Code:
[SIZE=2][COLOR=Blue][B]ro.adb.secure=1 [/B][/COLOR][/SIZE]
Cache Symlinking
Modify Following In init.rc Following Structure Of Other Main Classes:
Find The Following Line:
Code:
[SIZE=2][COLOR=Blue][B]mkdir /cache 0770 system cache [/B][/COLOR][/SIZE]
The Value "0770" Is The Value That Is Needed.
It May Have A Value Such As 0771 Or Some Other.
Change To Look Like Above.
Next, Find This Area:
Code:
[SIZE=2][B][COLOR=Blue]# create dalvik-cache and double-check the perms, so as to enforce our permissions [/COLOR][/B][/SIZE]
You Should See Three Lines Below This.
Add The Following Line At The End Of That Code Block:
Code:
[B][SIZE=2][COLOR=Blue]symlink /data/dalvik-cache /cache/dalvik-cache [/COLOR][/SIZE][/B]
Next, Find This Line:
Code:
[SIZE=2][B][COLOR=Blue]mkdir /data/resource-cache 0777 system system[/COLOR][/B][/SIZE]
Just Like Before Value Can Be Different Than "0777".
Change Line To Look Like Above.
The Last Edit.
You Should Find A Line About Two Lines After Your Previous Edit.
It Should Look Like This:
Code:
[SIZE=2][COLOR=Blue][B]chmod 0777 /data/resource-cache [/B][/COLOR][/SIZE]
Edit Line To Produce The "0777" Value Shown In The Line Above.
Click to expand...
Click to collapse
- Kernel Included Custom Recovery :
TWRP FOTA Kernel Partition Recovery For Sony Xperia S - http://teamw.in/project/twrp2/144
ROM CREDITS:
Xiaomi MIUI Development Team - http://www.miui.com/getrom.php
Making This Great Rom And Developing Patchrom For Adaptation And Porting MIUI To Many Devices
MIUI Android Team - http://miuiandroid.com/
Multilanguage Translation Of MIUI Roms ,Bringing MIUI To Non-China Area And Big Contribution To MIUI Community
Free Xperia Team & Cyanogen Community - http://freexperiaproject.com/
Making Adaptation Of Great Cyanogen-Mod Rom For Xperia Devices,What Make Any Miui Porting Possible
Lens_Flare - http://forum.xda-developers.com/member.php?u=2399936:
Making Greatest Tutorial For Porting MIUI To Various Devices,And Big Help To MIUI Community
All Other Devs Which Help With Sony Xperia Custom Kernels,Rooting Methods And Recoveries
- DooMLoRD - http://forum.xda-developers.com/member.php?u=2784807
- Bin4ry - http://forum.xda-developers.com/member.php?u=1346722
- RaymanFX - http://forum.xda-developers.com/member.php?u=3463426
Notes:
Big Thanks XDA User Kikisss & schickel - File Hosting Web Space .
- All files and tutorials are colected from Internet & XDA Forums,so all regards are going to their authors.Also they could be used for installing any custom rom for Xperia S -
- I'm Not responsible for any eventual errors and misbeheaveing of your devices. -
ROM Changelog: - EVERYTHING WORKS -
Please Post Suggestion Or Bugs Languages included:
English
Chinese
Polish
Russian
Ukrainian
Slovak
Czech
French
Hungarian
Danish
Dutch
German
Greek
Spanish
Italian
Arabic
Norwegian
Hebrew
Vietnamese
Korean
Indonesian
Brazilian Portuguese
Turkey
Official Build 3.10.25 Changelog:
REQUIREMENTS & PROCEDURE TUTORIALS:
1.Pre - Requirements:
Windows OS powered Computer
Android Device Drivers Installed(Drivers Thread)
Enabled Settings → Security → Unknown Sources & Settings → Development → USB Debugging
Phone Battery charged - 60% at least.
Stock Or Stock Based Android Rom - Not Strictly Required But Best Because Of Bugs
2.Backup Your Data (Wondershare MobileGo,etc...)
3.Unlocked Bootloader
- TUTORIAL -
Sony’s Official Bootloader Unlocking Site
Note:
- Easiest way to enter Windows CMD is holding SHIFT + RIGHT CLICK on empty space in folder than choose option " Open Command Window Here " .
4.Root
- TUTORIAL -
Solution 1 - For all ICS firmware except 2.55.
(Thanks Bin4ry)
1.) Download attached Root_with_Restore_by_Bin4ry_v30.
2.) Extract it using 7zip
3.) Double click the RunMe.bat and follow instructions!
Xperia phones with "older" firmware = Normal mode
Sony Tablet and similar = Special mode
Xperia phones with JB Firmare = Mode 3
Solution 2 - For ICS firmware 2.55.
(Thanks wym986)
1.) Download and run ERoot 1.1 .
2.) Connect your Xperia S /SL to the Computer（The correct driver is needed ） with USB Debugging and unknows sources on
3.) Just click the “一 键 root ” then wait a moment
4.) when it says “恭 喜 您 ，获 取 root 权 限 成 功 ”，you are success.
Solution 3 - For JB firmware .200 / .211.
(Thanks DooMLoRD)
1.) Download attached SuperSU-1.25-Busybox-1.20.2-UPDATE.
2.) Enter Recovery (CWM) (restart device (turn off, turn on & vol+) and while on the SE logo, simply tap the screen of your phone several times.
3.) Select [install zip from sdcard]→[choose zip from sdcard]→[SuperSU-1.25-Busybox-1.20.2-UPDATE.zip] → [YES]
4.) Wait flash finished, press Back and select reboot system now [], the phone going to automatically restart.
5.Flash Recovery
- TUTORIAL -
Solution 1 - CWM Recovery
- ICS All Firmware -
(Thanks LEDelete)
1.)Download and install RecoverX Software
2.)Open RecoverX,select your device and recovery and click next.
3.)Install Busybox if program ask,wait till software download recovery for your device.
4.)Flash recovery.
All instruction are in the RecoverX Software,just read on-screen instructions.
- JB Firmware .200 / .211 -
(Thanks DooMLoRD)
Download the advanced stock kernel (contains recovery)
Advance Stock Kernel with Recovery v02 (FW: 6.2.B.0.200) (CWM 6.0.3.2)
Advance Stock Kernel with Recovery v01 (FW: 6.2.B.0.211) (CWM 6.0.2.7)
Connect device to PC with Debugging Enabled & Reboot device into fastboot mode
Code:
adb reboot bootloader
now flash the recovery using
Code:
fastboot flash boot kernel.elf
[where kernel.img is the name of the file image u downloaded]
thats it!
Solution 2 - TWRP Recovery - ICS Stock FW Only
1.)Download and install TWRP Recovery
2.)Enter fastboot mode .
Turn off your device. Hold volume up on the device and plug it into your computer. The device will now be in fastboot mode.
3.)Run the following command via the command line:
fastboot flash boot stock-6.1.A.0.452-twrp-2.4.0.0.elf
Notes:
- You will do all procedure from fastboot package folder which you already downloaded for bootloader unlocking. -
- Easiest way to enter Windows CMD is holding SHIFT + RIGHT CLICK on empty space in folder than choose option " Open Command Window Here " .
6.Flash MIUI V5 Rom - Download MIUI V5 3.10.25- STABLE (Official Port) -
[QRCODE]http://pan.baidu.com/share/link?uk=4112589721&shareid=1895046101[/QRCODE]
- FAST MIRROR FOR USERS OUTSIDE ASIA - (Thanks To BotAwesome)-
Download MIUI 3.4 English Kernel FXP234 (Flash It Via Fastboot)
Download OTA Update 3.10.18 - 3.10.25(Flash It Via Recovery Or Update Manager)
[QRCODE]http://goo.gl/mcREZ1[/QRCODE]
Download Multilanguage Addon 3.10.18(Flash It Via Recovery After First Reboot)
(Thanks To Novastylez )
[QRCODE]http://caro.miuiandroid.com/3.10.18/multi/miuiandroid_lang_nozomi-3.10.18.zip[/QRCODE]
Flash MIUI V4 Rom - Download MIUI V4 3.2.22 - FINAL STABLE
- Flash Tutorial -
1. Put xxx-3.10.11.zip copied to the root directory of cell phone (that is a direct copy)
2 .Enter Recovery (TWRP or CWM) (restart device (turn off, turn on & vol+) and while on the SE logo, simply tap the screen of your phone several times.
3. Select [wipe data / factory reset] → [YES]
4. Select [wipe cache partition] → [YES ]
5.Select [advanced] → [wipe Dalvik Cache] → [ YES ] → Back
6.Select [install zip from sdcard] → [choose zip from sdcard] → [xxx-3.10.11.zip] → [YES]
7.Wait flash finished, press Back and select reboot system now [], the phone going to automatically restart with installed MIUI ROM.
- First boot need ~ 3 - 5 min. -
7.Flash Google Apps (MIUI Gapps) - Download GAPPS 4.1.2
Flash GAPPS for V4 Rom - Download GAPPS 4.0.4
- GAPPS Tutorial -
1.After first boot reboot your phone to recovery again.
2.Select [install zip from sdcard] → [choose zip from sdcard]→ [miuiandroid_gapps-4.1.2-small_signed.zip] → [YES]
3. Wait flash finished, press Back and select reboot system now [], the phone going to automatically restart with installed GAPPS.
4.Set up your Google and Xiaomi Accounts(for themes).
< NOTES >
Click to expand...
Click to collapse
- TIPS -
Click to expand...
Click to collapse
- If you're coming from other MIUI V5 realase you don't need to [wipe data / factory reset], [wipe cache partition] and install the GAPPS.just flash this rom over previous. -
- Turn Rounded Corners Off,Limit Background Processes To 3 and Enable 'Force GPU rendering' In Development Settings And Reboot For Smoothness. -
- If you have "assert failed" error during flashing rom you can fix it easy by on this way:
Open the zip file with 7zip. go to META-INFcomgoogleandroidupdater-script drag it to your windows explorer (or other programs). open it with notepad :
assert(getprop(";ro.product.device" == ";LT26i"; || getprop(";ro.build.product" == ";LT26i"; ||
getprop(";ro.product.device" == ";galaxys2"; || getprop(";ro.build.product" == ";galaxys2"; ( Or Something Similar )
and
delete them entirely . save it. then drag n drop to your opened 7zip, replacing old updater-script. - (Thanks to m1st3r1)
- VALUABLE APPS -
Click to expand...
Click to collapse
CAMERA
Click to expand...
Click to collapse
- To Replace Native Camera Which Quality Is Poor I Suggest 4 Alternatives:
Download And Install SNAP CAMERA HDR(Trial Version Works Completely ,But You Must Disable Internet Connection To Use It)
Download And Install Attached MIUI Camera(Thanks Ghetto_Thug) + Panorama App(Thanks blakstar)(Install Panorama App And Copy MIUI Camera(8mpx/720p) To /system/apps ,Set Permissions + Reboot Device)
Download And Install LENOVO SUPER CAMERA(Thanks Ghetto_Thug)(Fully Working With Lot Off Options).
Download And Install SGS4 CAMERA GOOGLE EDITION(Photosphere Working,4.3 Look,8mpx Photo Res.).
ADD BLOCKING
Click to expand...
Click to collapse
To Block All Adverts,Malware/Spyware/Bloatware From Web ,Backup Your /System/etc/hosts file via Root File Manager And Download & Flash Attached File Via CWM - ADD BLOCKING (ThanksBSDgeek_Jake)
WIFI REGION CODE
Click to expand...
Click to collapse
If Anyone Have Problems With WIFI Region Code ,Just Install This APP/Open It/Tap Install WiFix/Allow Root Permitions/App Will Work Automaticly - WIFIX.(Thanks fardjad)
ADOBE FLASH PLAYER
Click to expand...
Click to collapse
Adobe Stop With Distribution Of Flash Player For Android For Versions >4.0.4 ICS.
Download And Install Attached "Adobe Flash Player 11.1.115.63" App.
Open Browser /Settings And Enable Plugins (Note:Adobe flash Player Not Working With Chrome Browser)
OPERATOR NAME
Click to expand...
Click to collapse
To Change / Remove Carrier Name In Status Bar Download And Install Attached "MiuiSpnConfig"App.
Open App -> Change Carrier Name (Works With Blank Space Too)
-> Save -> Airplane Mode On-> Airplane Mode Off.(Thanks panel1)
WEATHER
Click to expand...
Click to collapse
To Enable Miui Weather For All Countries Download And Install Miui Based WEATHER BZ.
(Note:Enable In App Settings MIUI Integration)
MIUI CONTROL PANEL & XPOSED ALTERNATIVE
Click to expand...
Click to collapse
To Enable Various MIUI Tweaks Download And Install WSM PROJECT.
For More Information on English Visit : LINK
(Thanks BurgerzMD)
MIUI V5 THEMES
Click to expand...
Click to collapse
- Check My MIUI v5 Themes Thread -
MIUI Themes Collection - JUNE 2013
MIUI Themes Collection - JULY 2013
LANGUAGE
Click to expand...
Click to collapse
To Change Language Of Your Device Download And Install Attached "Set Language" App.
Open App -> Choose Language -> Apply.(Thanks Simple App Factory)
MASS STORAGE
Click to expand...
Click to collapse
To Enable Mass Storage Mode (Fast Manipulation With Storage Memory)On Your Device Download And Install Attached "SD Mounter_2.0" App.
Open App -> Grant Root Permissions(First Time Only) -> Mount Internal Storage -> .(Thanks DooMLoRD)
:good:ENJOY YOUR MIUI V5 ROM:good:
XDA:DevDB Information
[ROM][JB 4.1.2][Xperia S/SL] MIUI V5 MULTILANG UB [3.10.25] - CM10 BASED - STOPPED DEVELOPMENT, a ROM for the Sony Xperia S
Contributors
ghetto_thug, FD-GHOST, kin912, Zero3545,NovaStylez
ROM OS Version: 4.1.x Jelly Bean
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Recovery
Based On: FreeXperiaProject CyanogenMod
Version Information
Status: Stable
Current Stable Version: 3.10.25
Stable Release Date: 2013-10-25
Created 2013-09-25
Last Updated 2013-11-01
Im sorry but this is a development thread, not for FAQ or Tutorials. Your thread header reads (ROM)...bla bla bla thus one would expect a ROM available for download. Please forgive me if I misunderstand.
precardo said:
Im sorry but this is a development thread, not for FAQ or Tutorials. Your thread header reads (ROM)...bla bla bla thus one would expect a ROM available for download. Please forgive me if I misunderstand.
Click to expand...
Click to collapse
Rom is uploading.
Please wait little bit more.
Is there any difference between this version and 3.4.24 version or can you post a changelog please
Thanks for your work
Sent from my LT26i using xda app-developers app
can you please provide original thread link ?
thank you.
---------- Post added at 11:55 PM ---------- Previous post was at 11:35 PM ----------
zaidx said:
Is there any difference between this version and 3.4.24 version or can you post a changelog please
Thanks for your work
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
You can find changelog here:
http://miuiandroid.com/community/threads/miui-rom-3-5-17-changelog.20459/
Original thread is in Chinese.Changelog is the same as http://miuiandroid.com/community/threads/miui-rom-3-5-17-changelog.20459/.
Whole rom is based on Cm10 FreeXperia Project from 17.05.2013.
As i know camera is only 720p (cyanogenmod).and you must couple times press home button to activate task killer.
Please post any other bugs.
i may be too tired but i see 3.5.22 and downloading 3.5.17..
other than that, is it still english/chinese or do we have multilanguage support?
Provide Mirror for MIUI download that link is not opening
I can't flash the rom
it shows
assert failed: getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi" || getprop("ro.product.device") == "galaxys2" || getprop("ro.buildproduct") == "galaxys2"
I'm pretty sure it's Xperia S in my hand
also, I have already restored to 6.1.A.2.55, rooted, restored to factory, cache/dalvik cache wiped
flashed with CWM
how can I solve this? thanks
Don't flash Roms from Galaxy s2
androidlover007 said:
Don't flash Roms from Galaxy s2
Click to expand...
Click to collapse
lol. it's for nozomi/lt26i/xperia s alright. the dev seemed forget to change it
Xenal said:
I can't flash the rom
it shows
assert failed: getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi" || getprop("ro.product.device") == "galaxys2" || getprop("ro.buildproduct") == "galaxys2"
I'm pretty sure it's Xperia S in my hand
also, I have already restored to 6.1.A.2.55, rooted, restored to factory, cache/dalvik cache wiped
flashed with CWM
how can I solve this? thanks
Click to expand...
Click to collapse
open the zip file with 7zip. go to META-INF\com\google\android\updater-script drag it to your windows explorer (or other programs). open it with notepad and change:
assert(getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "galaxys2" || getprop("ro.build.product") == "galaxys2");
to
assert(getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi");
or delete them entirely . save it. then drag n drop to your opened 7zip, replacing old updater-script.
done. and it's best if u flash the kernel first via fastboot,
Xenal said:
I can't flash the rom
it shows
assert failed: getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi" || getprop("ro.product.device") == "galaxys2" || getprop("ro.buildproduct") == "galaxys2"
I'm pretty sure it's Xperia S in my hand
also, I have already restored to 6.1.A.2.55, rooted, restored to factory, cache/dalvik cache wiped
flashed with CWM
how can I solve this? thanks
Click to expand...
Click to collapse
Go to meta-inf>Com>Google>Android>updater-script>
Remove this line in notepad++
assert failed: getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi" || getprop("ro.product.device") == "galaxys2" || getprop("ro.buildproduct") == "galaxys2"
Save and exit.
replace new updater script with original script ..
now start flashing ..
androidlover007 said:
Don't flash Roms from Galaxy s2
Click to expand...
Click to collapse
No, I didn't.
that error message said I'm flashing it from neither XS or S2
but I AM flashing it from XS
It's solved now
I found that I can flash it from FXP
but I can't flash it from stock rom 6.1.A.2.55
pretty weird
Setting contact images(or avatars) gets a FC, kills the entire system, forces launcher to redraw.
Edit: works by going through the gallery.
ghetto_thug said:
Original thread is in Chinese.Changelog is the same as http://miuiandroid.com/community/threads/miui-rom-3-5-17-changelog.20459/.
Whole rom is based on Cm10 FreeXperia Project from 17.05.2013.
As i know camera is only 720p (cyanogenmod).and you must couple times press home button to activate task killer.
Please post any other bugs.
Click to expand...
Click to collapse
The problem with task killer can be solved by the following steps:
- settings
- Buttons & keys
- Home key --> select "None" instead of the default "Launch Recent panel"
Long-pressing home key still brings the list of recent application and task killer.
Only this instruction install?
6.Flash MIUI V5 Rom - Download MIUI V5 3.5.22
- Flash Tutorial -
1. Put miui_lt26i_3.5.17_asdyfoiej1_4.1.zip copied to the root directory of cell phone (that is a direct copy)
2 .Enter Recovery (TWRP or CWM) (restart device (turn off, turn on & vol+) and while on the SE logo, simply tap the screen of your phone several times.
3. Select [wipe data / factory reset] → [YES]
4. Select [wipe cache partition] → [YES ]
5.Select [advanced] → [wipe Dalvik Cache] → [ YES ] → Back
6.Select [install zip from sdcard] → [choose zip from sdcard] → [miui_lt26i_3.5.17_asdyfoiej1_4.1.zip] → [YES]
7.Wait flash finished, press Back and select reboot system now [], the phone going to automatically restart with installed MIUI ROM.
- First boot need ~ 3 - 5 min. -
Garfi93 said:
Only this instruction install?
6.Flash MIUI V5 Rom - Download MIUI V5 3.5.22
- Flash Tutorial -
1. Put miui_lt26i_3.5.17_asdyfoiej1_4.1.zip copied to the root directory of cell phone (that is a direct copy)
2 .Enter Recovery (TWRP or CWM) (restart device (turn off, turn on & vol+) and while on the SE logo, simply tap the screen of your phone several times.
3. Select [wipe data / factory reset] → [YES]
4. Select [wipe cache partition] → [YES ]
5.Select [advanced] → [wipe Dalvik Cache] → [ YES ] → Back
6.Select [install zip from sdcard] → [choose zip from sdcard] → [miui_lt26i_3.5.17_asdyfoiej1_4.1.zip] → [YES]
7.Wait flash finished, press Back and select reboot system now [], the phone going to automatically restart with installed MIUI ROM.
- First boot need ~ 3 - 5 min. -
Click to expand...
Click to collapse
Only that instruction which is standard for installing almost any custom rom.
In next hour Fixed Release 3.5.23 is going to be uploaded.
Build is based on MIUI Official Release 3.5.17.
At the begining of next week official 3.5.24 will be online and also ported version for XS ,so i hope more bugfixes and battery optimisation.
version 3.5.23 link and qr code is on the first page.
Still based on official 3.5.17
more bux fixes,modded battery consumption,
fixed : Camera,task killer,assert errors,streamlines,fm fc,contacts picture fc,...
I need a english mirror, don't speak chinese
androidlover007 said:
I need a english mirror, don't speak chinese
Click to expand...
Click to collapse
Just click on the right link where filesize is written.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am proud to present first Dualboot project For Redmi Pro. This will allow any number of ROMs to be installed at the same time. It works by patching the secondary ROM's installation scripts and boot image to load the ROM files from an alternate location (/system/multiboot, /cache/multiboot, and /data/multiboot). Because of the way this is implemented, no changes to the primary ROM are necessary
What is DualBootPatcher?
DualBootPatcher is an open-source app that allows multiple ROMs to be installed on a single Android device. It does its best to work with existing code and does not require explicit support from ROMs. There are currently 200+ supported devices and their variations.
Information:
I have managed to support for Redmi Pro to the DualBootPatcher App, I am not the creator, just the supporter.
It's awesome and useful for testing out roms or if you want, switching ROMS.
Disclaimer:
Code:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
Requirements:
1. A Custom Recovery (TWRP)
2. A ROM
3. Dual Boot Patcher app and the DualBootUtilities.zip from the download section below.
What does the app do ?:
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.
Click to expand...
Click to collapse
How to use the App?
- Download, install and open the app.
- Swipe to the right to open the menu. Click "ROMS". Now if this is the first time you use it, it will ask you if you want to set kernel. Do so!
- After it has finished go to ROM Settings (primary ROM 3 dot menu) and select Update Ramdisk. It will update it and will ask you to reboot. Press Reboot Now, or Reboot later.
- Now Download any ROM you like and open the app again and open the menu and open Patch Zip File from the menu. Ensure that your Device is set to (eyeul) and under Partition configuration select secondary (will install 2nd ROM in /system) or data slot.
- Click continue and select where to save the patched file.
- You should see the file is being put in "Queue". Just click the confirm button to the upper right.
Note: If you want to go back, just swipe the ROM in queue to right and start over.
- The app will patch the zip. When done, go back to "ROMs".
- Click "Flash zip files" (the big pink button on the lower right). Click the pink plus button to add your previously patched zip file.
- Locate the file you have patched in step 7. Unless you have changed the name there, it should be something like ROM_name_partition_config_ID.zip (like RR-N-v5.8.3-20170707-omega-Unofficial_dual.zip).
- Click on that file and choose "Keep location". Now confirm the flash with the button on the upper right side.
Note: You can also install the patched zip files in recovery.
- It will now open the terminal and begin flashing the file. This requires some patience. After it has flashed the file you'll see success message in green.
- Now click back and you should see your newly installed ROM along with the Primary ROM.
Note: You can find more options by clicking on the three buttons on each ROM.
- Now reboot and wait till finishing 2nd ROM first boot. install DualBootPatcher apk so you can easily switch ROMs, there is another way to change ROMs: flash DualBootUtilities.zip and switch ROM manually.
Note: Using Bootui:
- Open app then select settings and press install (update) bootui. then Swipe to the right to open the menu. Click "ROMS" again and open secondary ROM Settings) and select Update Ramdisk, Now you can change ROMs simply using boot ui (something like grub bootloader but it works like twrp)
Partitions Configurations:
The patcher offers several locations for installing ROMs:
Primary: This is normally used for installing a zip to the primary ROM. It is not required, but is strongly recommended because it has code to prevent the zip from inadvertently affecting other ROMs.
Dual: Dual/Secondary is the first multiboot installation location. It installs to the system partition. This is a good spot for installing a second ROM because it doesn't take any space away from the internal storage.
Multi-slots: There are 3 multislots: multi-slot-1, multi-slot-2, multi-slot-3. These install to the cache partition. This is specifically for devices, like the Galaxy S4, that have a massive cache partition.
Data-slots: There can be an unlimited number of data slots. These install to the data partition and eat up space on the internal storage. This is useful for devices where the system partition is nearly full and the cache partition is tiny. These slots are named "data-slot-[id]", where "id" is something you provide in the app.
Extsd-slots: There can be an unlimited number of extsd slots. These install to the external SD card, which is useful as it keeps the ROMs off of the internal storage. Note that the ROM's data files are still stored on the data partition.
How to boot to another ROM ?
This is simple ... There is no reboot to primary, secondary or whatever. So all you have to do is:
1) Go to ROMs section of the App.
2) Click on the ROM you want to boot to. You should see "Switching ROM" message. After few seconds, you should see a report message saying that "ROM successfully switched".
3) Now just do a normal reboot of your device. See the magic! It should boot to the ROM you have switched on step 2.
Note: You can find more options by selecting the three buttons on each ROMs (like creating reboot widgets for directly rebooting to specific rom).
You also need to install the App to all of the ROMs you install. Otherwise, you want be able to boot to other ROMs!
Apps and Data sharing:
DualBootPatcher very recently got support for sharing apps and their data across ROMs. Maybe sharing is somewhat of a misleading term. The feature actually makes Android load the shared apps and data from a centralized location, /data/multiboot/_appsharing. So you're not sharing apps from one ROM to another per se. The ROMs are just loading the apps from one shared location. Let me make this clearer with an analogy.
Think of the people in a company office as ROMs. You want to share with your coworkers some documents (apps). Instead of telling them to come over to your desk to see those documents (sharing apps from one ROM to another), everyone goes to the conference room to look at the documents together (loading apps from a shared location). That's how app and data sharing is implemented.
Click to expand...
Click to collapse
To use app sharing, follow these steps in every ROM that you want to use app sharing: (doesn't work with JB ROMs)
Install the app you want to share
Open DualBootPatcher and go to "App Sharing" in the navigation drawer
Enable individual app sharing
Tap "Manage shared applications" and enable APK/data sharing for the app
Reboot
When you uninstall an app that's shared, it simply become unshared for the current ROM. That way, other ROMs are not affected. To continue the analogy above, if you quit your job, you won't shred the documents that everybody else was looking at.
If you unshare an app's data, it will go back to using the data it had before it was shared. In other words, you leave the conference room and go back to work on your own documents at your desk.
Click to expand...
Click to collapse
Other How to ?
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".
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:
All Downloads HereCheers ! we are officially supported
Note: You can download any version since "9.2.0.r295.g3b684238"
Screenshots:
No Screenshots, I need some
Sources:
DualBootPatcher: https://github.com/chenxiaolong/DualBootPatcher
DualBootUtilities: https://github.com/chenxiaolong/DualBootZips
Build instructions: https://github.com/chenxiaolong/DualBootPatcher/tree/master/docs
Redmi Pro Support:
https://github.com/chenxiaolong/DualBootPatcher/pull/707
Known issues:
- You tell me !
Credits:
@chenxiaolong for the awesome DualBootPatcher.
XDA:DevDB Information
[PATCHER][APP][OFFICIAL] Dualboot/Multiboot For Redmi Pro, Tool/Utility for the Xiaomi Redmi Pro
Contributors
yshalsager, chenxiaolong
Source Code: https://github.com/chenxiaolong/DualBootPatcher
Version Information
Status: Stable
Current Stable Version: 9.2.0.r295.g3b684238
Created 2017-08-19
Last Updated 2017-10-03
Notes
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
Code:
assert(getprop("ro.product.device") == "omega" || getprop("ro.build.product") == "omega" || abort("E3004: This package is for device: omega; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
2- To Flash AROMA ROMs flash patched zip from TWRP
Changelogs
-19/08/2017
Initial Release, waiting for adding officially
Much thanks
yshalsager said:
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
2- To Flash AROMA ROMs flash patched zip from TWRP
Click to expand...
Click to collapse
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try
yshalsager said:
1- If flashing Custom ROM Fail (like LOS 14.1):
you have to edit "updater-script" and remove assert lines like:
2- To Flash AROMA ROMs flash patched zip from TWRP
Click to expand...
Click to collapse
daffa ZRN said:
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try
Click to expand...
Click to collapse
Here are the screenshots
yshalsager said:
-19/08/2017
Initial Release, waiting for adding officially
Click to expand...
Click to collapse
Ok now it works but when rebooting to enter secondary rom (using bootUI) it just boots to twrp.
I'm using resurrection remix as the secondary ROM, also when it's flashing (through the app) the message is red not green which means a fail. Maybe the that's the problem. Pls help so I can test it out and report back
daffa ZRN said:
Ok now it works but when rebooting to enter secondary rom (using bootUI) it just boots to twrp.
I'm using resurrection remix as the secondary ROM, also when it's flashing (through the app) the message is red not green which means a fail. Maybe the that's the problem. Pls help so I can test it out and report back
Click to expand...
Click to collapse
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines
daffa ZRN said:
Pls help me when trying to patch my ROM (Los 13) it says that it need documents enabled from settings. The problem is I already have...
Please help me I'm very keen to be the first to try
Click to expand...
Click to collapse
You can choose zip using any explorer app like ES File
yshalsager said:
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines
Click to expand...
Click to collapse
Sorry but can you show me how(I'm a noob)
Wow, dual boot patcher stops working when pressing ROMs, I am in a redmi note 3 pro kate, since version 277 no longer works but in 257 down function without errors, someone else happens to this?
Error log:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Xiaomi/kate/kate:6.0.1/MMB29M/V8.2.4.0.MHRMIDL:user/release-keys'
Revision: '0'
ABI: 'arm64'
pid: 13581, tid: 14315, name: pool-1-thread-1 >>> com.github.chenxiaolong.dualbootpatcher.snapshot <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xdeadbaad
Abort message: 'invalid address or address of corrupt block 0x7fa60f0090 passed to dlfree'
x0 0000000000000000 x1 0000007faf7ba7d0 x2 0000000000000001 x3 00000000007fabf9
x4 0000000000000000 x5 00000000deadbaad x6 0000000000000000 x7 0000000000000010
x8 7f7f7f7fffff7f7f x9 6471656b631f6e73 x10 7f7f7f7f7f7f7f7f x11 0101010101010101
x12 0000007faf7ba7c8 x13 58934240ef78b85e x14 58934240ef78b85e x15 0030f907887041ba
x16 0000007faf7b4a58 x17 0000000000000000 x18 0000007faca2a000 x19 0000007fa60f0090
x20 0000007faf7bb000 x21 0000007fa60f00a0 x22 0000007faf7bba70 x23 00000055995187e8
x24 0000000000000002 x25 0000005599529258 x26 0000000000000000 x27 0000000032e3dbe0
x28 00000055995a5860 x29 0000007f93a7f060 x30 0000007faf753580
sp 0000007f93a7f060 pc 0000007faf753588 pstate 0000000060000000
backtrace:
#00 pc 0000000000047588 /system/lib64/libc.so (dlfree+408)
#01 pc 00000000000195a8 /system/lib64/libc.so (free+20)
#02 pc 0000000000029054 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so
#03 pc 0000000000029224 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so
#04 pc 0000000000011b40 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbcommon.so (_ZN2mb8format_vERSsPKcSt9__va_list+132)
#05 pc 000000000000abd0 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader11set_error_vESt10error_codePKcSt9__va_list+84)
#06 pc 0000000000009588 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader9set_errorESt10error_codePKcz+108)
#07 pc 000000000000d300 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so
#08 pc 000000000000c96c /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so
#09 pc 0000000000009ed8 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader4openEPNS_4FileE+308)
#10 pc 0000000000009a88 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmbbootimg.so (_ZN2mb7bootimg6Reader13open_filenameERKSs+216)
#11 pc 0000000000011ec8 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/lib/arm64/libmiscstuff-jni.so (Java_com_github_chenxiaolong_dualbootpatcher_nativelib_libmiscstuff_LibMiscStuff_getBootImageRomId+300)
#12 pc 0000000000603934 /data/app/com.github.chenxiaolong.dualbootpatcher.snapshot-2/oat/arm64/base.odex (offset 0x35c000)
I've use it for a long time,but i changed my model into Redmi Note 4(MTK) then I can use dualbootpatcher.now pro can use it with out changing model.it's great!:good:
yshalsager said:
Yep red message means it didn't flash successfully. Can you take a look at second post? You need to remove assert lines
Click to expand...
Click to collapse
Ok now I know how to remove those line and I did it, I removed the 1st and the 3rd line.
But now Im facing another fail on flash please help
zhaodelin2002 said:
I've use it for a long time,but i changed my model into Redmi Note 4(MTK) then I can use dualbootpatcher.now pro can use it with out changing model.it's great!:good:
Click to expand...
Click to collapse
You know how to fix my issue?
daffa ZRN said:
You know how to fix my issue?
Click to expand...
Click to collapse
sorry,my way isn't same as yours......
Ivan Torres said:
Wow, dual boot patcher stops working when pressing ROMs, I am in a redmi note 3 pro kate, since version 277 no longer works but in 257 down function without errors, someone else happens to this?)
Click to expand...
Click to collapse
The problem is from app. Not from your device. For me r199 works perfectly. You can use version in this thread also
daffa ZRN said:
Ok now I know how to remove those line and I did it, I removed the 1st and the 3rd line.
But now Im facing another fail on flash please help
Click to expand...
Click to collapse
Remove from starting of file to the end of line 3
The file should be started with "package" line
zhaodelin2002 said:
sorry,my way isn't same as yours......
Click to expand...
Click to collapse
What's your way, maybe I can try
daffa ZRN said:
What's your way, maybe I can try
Click to expand...
Click to collapse
modify build.prop
yshalsager said:
Remove from starting of file to the end of line 3
The file should be started with "package" line
Click to expand...
Click to collapse
Still not working do you have a ROM already modified?
Good afternoon I would like to know if there is any custom ROM 8.0 or 8.1 (Oreo) for flash in TWRP because I upgraded to Oreo Stock (soak test 2 - February) and my bootloader is 0xC180.
Thank you
carlosgeraldo said:
Good afternoon I would like to know if there is any custom ROM 8.0 or 8.1 (Oreo) for flash in TWRP because I upgraded to Oreo Stock (soak test 2 - February) and my bootloader is 0xC180.
Thank you
Click to expand...
Click to collapse
No, not yet. Wait for some time!
carlosgeraldo said:
Good afternoon I would like to know if there is any custom ROM 8.0 or 8.1 (Oreo) for flash in TWRP because I upgraded to Oreo Stock (soak test 2 - February) and my bootloader is 0xC180.
Thank you
Click to expand...
Click to collapse
you can install the rom xperience 12.1with android 8.1
MirandaEduardo said:
you can install the rom xperience 12.1with android 8.1
Click to expand...
Click to collapse
Good morning I'm currently on soak test 3 (bootloader 0xC182) can you tell me if this ROM is running on this bootloader?
carlosgeraldo said:
Good morning I'm currently on soak test 3 (bootloader 0xC182) can you tell me if this ROM is running on this bootloader?
Click to expand...
Click to collapse
I do not know if it can be installed, I'm with oxC180 and I have the xoprience rom running without problems and the root I have not managed to work that's why I have this rom
carlosgeraldo said:
Good afternoon I would like to know if there is any custom ROM 8.0 or 8.1 (Oreo) for flash in TWRP because I upgraded to Oreo Stock (soak test 2 - February) and my bootloader is 0xC180.
Thank you
Click to expand...
Click to collapse
Hey brother!
After searching and searching the forum, I also had that problem. I am in the bootloader 0xc182 (soak test 3)
The solution is the next:
In the .zip file of the custom rom, open the following route
omni-8.1.0-20180402-addison-HOMEMADE.zip \ META-INF \ com \ google \ android
Within the android folder there are two files, the one we need is called "updater-script"
you extract the file to the desktop of the pc and you change the extension to .txt or you open it with the note pad.
Once opened, with the option to search enter "bootloader" and in the results there will be several lines with the following command:
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command and put it after the last one that supports the rom. But this time modify the bootloader version, from 0xC105 to 0xC180.
You save the document (if you put the extension .txt, delete it)
Finally, the modified file adds it to the zip of the rom (replace the original)
And the rom can be installed without problem.
I hope I have helped you, greetings.
{
"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"
}
helldagp said:
Hey brother!
After searching and searching the forum, I also had that problem. I am in the bootloader 0xc182 (soak test 3)
The solution is the next:
In the .zip file of the custom rom, open the following route
omni-8.1.0-20180402-addison-HOMEMADE.zip \ META-INF \ com \ google \ android
Within the android folder there are two files, the one we need is called "updater-script"
you extract the file to the desktop of the pc and you change the extension to .txt or you open it with the note pad.
Once opened, with the option to search enter "bootloader" and in the results there will be several lines with the following command:
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command and put it after the last one that supports the rom. But this time modify the bootloader version, from 0xC105 to 0xC180.
You save the document (if you put the extension .txt, delete it)
Finally, the modified file adds it to the zip of the rom (replace the original)
And the rom can be installed without problem.
I hope I have helped you, greetings.
Click to expand...
Click to collapse
Thanks for the tip! I have a doubt! How to get back to Soak test 3?
which is the best rom for z play Oreo less bugs
helldagp said:
Hey brother!
After searching and searching the forum, I also had that problem. I am in the bootloader 0xc182 (soak test 3)
The solution is the next:
In the .zip file of the custom rom, open the following route
omni-8.1.0-20180402-addison-HOMEMADE.zip \ META-INF \ com \ google \ android
Within the android folder there are two files, the one we need is called "updater-script"
you extract the file to the desktop of the pc and you change the extension to .txt or you open it with the note pad.
Once opened, with the option to search enter "bootloader" and in the results there will be several lines with the following command:
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command and put it after the last one that supports the rom. But this time modify the bootloader version, from 0xC105 to 0xC180.
You save the document (if you put the extension .txt, delete it)
Finally, the modified file adds it to the zip of the rom (replace the original)
And the rom can be installed without problem.
I hope I have helped you, greetings.
Click to expand...
Click to collapse
Did your device work that way?
Which rom you were able to install using this method
Thx
helldagp said:
Hey brother!
After searching and searching the forum, I also had that problem. I am in the bootloader 0xc182 (soak test 3)
The solution is the next:
In the .zip file of the custom rom, open the following route
omni-8.1.0-20180402-addison-HOMEMADE.zip \ META-INF \ com \ google \ android
Within the android folder there are two files, the one we need is called "updater-script"
you extract the file to the desktop of the pc and you change the extension to .txt or you open it with the note pad.
Once opened, with the option to search enter "bootloader" and in the results there will be several lines with the following command:
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command and put it after the last one that supports the rom. But this time modify the bootloader version, from 0xC105 to 0xC180.
You save the document (if you put the extension .txt, delete it)
Finally, the modified file adds it to the zip of the rom (replace the original)
And the rom can be installed without problem.
I hope I have helped you, greetings.
Click to expand...
Click to collapse
Man i think i lov u, very thanks
helldagp said:
Hey brother!
After searching and searching the forum, I also had that problem. I am in the bootloader 0xc182 (soak test 3)
The solution is the next:
In the .zip file of the custom rom, open the following route
omni-8.1.0-20180402-addison-HOMEMADE.zip \ META-INF \ com \ google \ android
Within the android folder there are two files, the one we need is called "updater-script"
you extract the file to the desktop of the pc and you change the extension to .txt or you open it with the note pad.
Once opened, with the option to search enter "bootloader" and in the results there will be several lines with the following command:
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command
getprop ("ro.bootloader") == "0xC105"
(The lines it shows are the bootloader that the rom supports).
Copy the command and put it after the last one that supports the rom. But this time modify the bootloader version, from 0xC105 to 0xC180.
You save the document (if you put the extension .txt, delete it)
Finally, the modified file adds it to the zip of the rom (replace the original)
And the rom can be installed without problem.
I hope I have helped you, greetings.
Click to expand...
Click to collapse
It worked, I managed to flash have your tutorial.
thank you very much
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working :
Almost everything
What's not working :
VoLTE (?)
AudioFX on headphones
Maybe something else...
Instructions :
Download the latest build and gapps
Reboot to recovery
Make full wipe
Flash the latest build and gapps
Reboot
Downloads :
Builds : https://androidfilehost.com/?w=files&flid=266525
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html (I recommend MindTheGapps)
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][leland][8.1] LineageOS 15.1, ROM for the Honor 9 Lite
Contributors
AndropaX, LuK1337, surdu_petru
Source Code: https://github.com/AndropaX/android_device_honor_leland/tree/leland-8.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Beta Release Date: 2018-04-25
Created 2018-04-22
Last Updated 2018-04-25
Thanks for your work guys... Keep Rocking...
Video Review
@AndropaX
many thank's for your work !
this is the first LOS 15.1 that's work on my Ho9L, delivered with OREO.
first find of not work : gapps ( i am install open_gapps-arm-8.1-pico64-20180414.zip )
my stock-build : LLD-L31 8.0.0.127(C432)
my LOS is link from VigneshS007 for test
i am very happy to see LOS on my phone
my next test is your build 20180422 (if download end!) and i am read your link to Google Apps !
---------- Post added at 02:28 PM ---------- Previous post was at 01:44 PM ----------
sorry, this zip not work.
my do
- boot to recovery(twrp)
- twrp wipe
- twrp install lineage-15.1-20180422-UNOFFICIAL-leland.zip
E3004: This package is for device: leland,hi6250; this device is lld.
Updater process ended with ERROR: 7
It's twrp issue, you must delete assertion from updater-script
my way
- modify updater-script (erase line 1+2 "assertion")
- boot to twrp
- wipe
- twrp install lineage-15.1-20180422-UNOFFICIAL-leland.zip
- twrp install open_gapps-arm-8.1-pico64-20180414.zip
- twrp install magisk
- twrp wipe cache
- twrp reboot to system
- phone boot as a "new phone" (settings...) and WORK !
only problem with TB (no SU), is problem with magisk - not LOS. now i must search "why"
Wishes:
- modify updater-script before you upload
- how much work is modify button-layout ? i wish rotate from "return,home,oversight" to "oversight,home,return" (is Tradition on my phones)
Now i am LOS15.1 on my phone and test in next day's.
This is very good work ! Many thank's !!!
Thanks for your donation !
Unfortunatelly features like that must add lineage team...
A wipe what to do? And if I want to go back to the drain, how to do it? And on which version of the locale can be installed?
Thank you. I can confirm it's working great on my H9L: your ROM + Open GApps stock + Magisk 16 (root + SafetyNet pass).
The only strange thing I experienced so far is the camera. I each application the camera view sometimes shows stripes. It is flashing like each second. It is possible to make a shot and catch those stripes. Here's how it looks:
@vandal1979
my build LLD-L31 8.0.0.127(C432)
i am in twrp wipe /advanced / Dalvik + Cache + Data + internal Storage + System
if you wish return to previus (stock) ROM: FIRST twrp/Backup your System and Data AND test this ! reboot to system, erase 1..2 apps, boot to twrp, restore your backup, reboot to
system AND check! erased apps is return ? this is important - a backup with no checked restore = worse as NO backup !
install LOS
...
if you wish return: twrp/Restore. that's work on my phone with my build
way 2: you not use twrp
you need from your build: xyz(FULL). extract from this UPDATE.APP (inside from UPDATE.ZIP) "recovery_ramdis.img + recovery_ramdis.img.header, system.img + system.img.header
copy this to your adb-folder and flash recovery_ramdisk recovery_ramdis.img + flash system system.img.
now is stock-rom return on your phone. boot to eRecovery, factory reset and boot
i think LOS work on all (Cxx) but i no can test. test on your own risk, if you wish ! if you NOT have your build(FULL): let it be !!!
no matter what experiments you do with your phone : your build(FULL) is essential to return to stock !!! ONLY inside FULL you can extract the partitions you need !!!
Example Build LLD-L31 8.0.0.127(C432) / phone - model - OS - build - country
AND the best advice : read the other thread's in this forum(Honor 9 Lite). read, what other user have problem and what help !
A
good job! a lot of thanks you! hope u will fix an issue with the AudioFx on headphones, i really need this
lld al10
@AndropaX
Hi can I use it on LLD-AL10?
Error 7
E1001: Failed to update system image.
i've modified "assertion"
Thank you.
This doesn't tell me too much, I need recovery log
AndropaX said:
This doesn't tell me too much, I need recovery log
Click to expand...
Click to collapse
I:Copying file /cache/recovery/log to /cache/recovery/last_log
tw_get_context got selinux context: ubject_r:media_rw_data_file:s0
I:Got default contexts and file mode for storage files.
I:Attempt to load settings from settings file...
I:InfoManager loading from '/data/media/0/TWRP/.twrps'.
I:Backup folder set to '/external_sd/TWRP/BACKUPS/AYK4C17C13005188'
I:Copying file /etc/recovery.fstab to /cache/recovery/recovery.fstab
I:Version number saved to '/cache/recovery/.version'
__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
I:TWFunc::Set_Brightness: Setting brightness control to 2522
IageManager::LoadFileToBuffer loading filename: '/twres/languages/ot.xml' directly
parsing languageFile
parsing languageFile done
I:Translating partition display names
I:Backup folder set to '/external_sd/TWRP/BACKUPS/AYK4C17C13005188'
I:Switching packages (TWRP)
I:Starting Adb Backup FIFO
I:Skipping screen timeout: TW_NO_SCREEN_TIMEOUT is set
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
Iperation_start: 'Flashing'
Installing zip file '/external_sd/lineage-15.1-20180422-UNOFFICIAL-leland.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
I:Update binary zip
Verifying package compatibility...
Package doesn't contain compatibility.zip entry
I:Zip does not contain SELinux file_contexts file in its root.
SELinux: Loaded file_contexts
Target: Honor/lineage_leland/leland:8.1.0/OPM2.171019.029/1c342163a5:userdebug/test-keys
Target: Honor/lineage_leland/leland:8.1.0/OPM2.171019.029/1c342163a5:userdebug/test-keysExtracted file "/tmp/install/bin/backuptool.functions"
Extracted file "/tmp/install/bin/otasigcheck.sh"
Extracted file "/tmp/install/bin/backuptool.sh"
Extracted 3 file(s)
detected filesystem f2fs for /dev/block/bootdevice/by-name/system
detected filesystem f2fs for /dev/block/bootdevice/by-name/systemabout to run program [/tmp/install/bin/backuptool.sh] with 2 args
run_program: child exited with status 127
Patching system image unconditionally...
performing update
Patching system image unconditionally...blockimg version is 4
maximum stash entries 0
using existing stash /cache/recovery/2bdde8504898ccfcd2c59f20bb8c9c25f73bb524/
erasing 579847 blocks
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 12,1356,8059,327959,392704,393729,523776,524812,818688,819714,884224,885250,905216]
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
I:Install took 1 second(s).
Error installing zip file '/external_sd/lineage-15.1-20180422-UNOFFICIAL-leland.zip'
Updating partition details...
Iata backup size is 0MB, free: 24341MB.
...done
Why you formatted system to f2fs ? It must be ext4...
Wysłane z mojego LLD-L31 przy użyciu Tapatalka
AndropaX said:
Why you formatted system to f2fs ? It must be ext4...
Wysłane z mojego LLD-L31 przy użyciu Tapatalka
Click to expand...
Click to collapse
same problem with ext4 ( it was a try.)
thanks for the help
Hi,
Does video recording work (I think it probably does as this is a new phone, but just checking to be sure)?
About the stripes in camera, maybe try PHH's Treble EMUI Camera app. It may work better.
EDIT: also does this ROM function via Treble or the old way of ROM?
EDIT 2: If/When Honor update this device to P, we should get a vendor partition with full support for Dual-Camera! Look here: https://developer.android.com/preview/features#camera
Thanks!
Any best camera port for honor 9 lite with portrait mode
@AndropaX
install with twrp "lineage-15.1-20180425-UNOFFICIAL-leland.zip" NOT work on phones with OREO delivered.
the problem is : we need twrp with crypting.
only way at this moment : flash system los.img
big twrp-developer work on twrp with crypting. at this moment no twrp found WITH crypting.
Buing cheapest microSD card for now isn't a big deal...
Wysłane z mojego LLD-L31 przy użyciu Tapatalka
JamesBott said:
@AndropaX
install with twrp "lineage-15.1-20180425-UNOFFICIAL-leland.zip" NOT work on phones with OREO delivered.
the problem is : we need twrp with crypting.
only way at this moment : flash system los.img
big twrp-developer work on twrp with crypting. at this moment no twrp found WITH crypting.
Click to expand...
Click to collapse
AndropaX said:
Buing cheapest microSD card for now isn't a big deal...
Wysłane z mojego LLD-L31 przy użyciu Tapatalka
Click to expand...
Click to collapse
I assume you want data crypt so that you can access the rom zip? I would sideload personally.