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 ??
WARNING: This rom is by far not suitable for daily usage and flashing it is at your OWN RISK! (my HTC One X has survived so far )
I've compiled a CM-13.0 from for the HOX.
While it is kind off working, it is very unstable.
Butttttt, when it's stable it's damn fast for what I've experienced so far.
What is broken:
audio
camera
wifi
gps (needs to be confirmed)
bluetooth (needs to be confirmed)
installing an app doesn't make the app appear in the launcher
I've attached the GDB debugger to the mediaserver process to start viewing the breakpoints but I didn't succeed.
(for people that are curious, here is the crashlog: http://pastebin.com/KN9s7C7K)
The only way this rom currently boots is when the GDB is attached and I am slowly stepping trough the main_mediaserver.cpp source code. I think this works because the mediaserver get's started too soon, and thus some of the hardware related things are not ready. If only I had the tegra3 source code for the audio.primary.tegra.so and the camera.vendor.tegra.so files. That would make my life a lot easier since I'd have just changed the code to be compatible with Android 6.0.
If you've got a spare HTC One X and you'd like to test and help me out, you can flash this rom and let me know what is working or not.
There is a build running right now and I'll let you know the results when it's finished.
XDA:DevDB Information
[ROM/WIP][CM-13.0/LOS-14.1][6.0.1/7.0.1] CM13.1 or LOS 14.1 - HTC One X, ROM for the HTC One X
Contributors
tim687, DevUt
Source Code: https://gitlab.com/endeavoru
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.1.x
ROM Firmware Required: HBOOT 1.72.0000 or higher
Based On: CyanogenMod
Version Information
Status: Testing
Current Stable Version: -
Current Beta Version: -
Created 2017-03-02
Last Updated 2017-05-21
Obtaining device logs
Obtain (boot-) logs
There are a few ways to obtain the bootlogs when the device doesn't (fully) boot.
A recovery with file manager is required (most TWRP's have it)
Get kernel logs:
#1: Boot into recovery (press and hold volume down and press the power button). Then with the volume buttons go down to recovery and press the power button.
#2: Make sure that the sd card is mounted, if not go to the mount menu of TWRP.
#3: Go to Advanced -> File Manager, then navigate to /proc and copy the files last_log and last_kmsg to the sdcard (/sdcard).
#4: Go back to the mount menu, and Enable MTP. (I need to Disable MTP unplug the USB, wait ~5 seconds, Enable MTP and plug the USB in the computer, for the device to show)
#5: Copy the last_log and last_kmsg to your computer and send them in this thread to me (not the actual text, but the files themselves, pastebin is also allowed).
#6: Describe your problem! What is the device doing? Is it still showing the HTC logo, is the CM animation still running or did it froze?
#7: Make sure that you are able to test a new build and be able to reproduce the crash
Get ADB access
If you need to clean flash a new version of this rom, please do that first, so that the files you are placing inside the /data partition don't get erased.
Locate the adbkey.pub file on your computer.
On Windows it is in C:\Users\<username>\.android\On Unix (Linux and OSX) it is located under ~/.android
#1: Make the following directory tree:
misc\adb#2: In the adb folder create a file named "adb_keys"
#3: Open the file with any editor.
#4: Paste the contents of the adbkey.pub file in the adb_keys file. If you want to authorize multiple computers, just paste the next key in the line below the first key.
#5: Save the file
#6: Boot into recovery (press and hold volume down and press the power button). Then with the volume buttons go down to recovery and press the power button.
#7: Go back to the 'Mount' menu, and Enable MTP. (I need to Disable MTP unplug the USB, wait ~5 seconds, Enable MTP and plug the USB in the computer, for the device to show)
#8: Make sure that the sd card and /data is mounted, if not go to the mount menu of TWRP.
#9: Copy the directory tree you've created in #1 to the sd card of your device.
#10: Go to 'Advanced' -> 'File Manager', then navigate to '/sdcard' and click on the 'misc' folder, then click on 'select' -> 'Copy Folder' -> 'data' -> 'Select' and swipe to confirm.
#11: To start the logs to appear on your screen enter the following command (the same for Windows and Unix users, it requires the ADB binary and executable folder to be in your path):
adb logcat && adb logcatYou might want to save the log to a (text-) file, you can do that by changing the command to (note: If the file exists, it gets overwritten!)
(adb logcat && adb logcat) > adb_bootlog.txt#12: Post the logfile in this thread (not the actual text, but the file, pastebin is also allowed)
#13: Describe your problem! What is the device doing? Is it still showing the HTC logo, is the CM animation still running or did it froze?
#14: Make sure that you are able to test a new build and be able to reproduce the crash
Reserved
How to flash:
For full safety, please do a clean flash everytime a new build has come out!
#1: Extract boot.img from the zip.
#2: Flash the zip
#3: Clear data and cache
#4: Restart in fastboot mode and use fastboot flash boot boot.img to flash the boot image
#5 (optionally): follow the steps in the post above to obtain (boot-)logs
Changelog:
20170304:
Used audiowrapper, to hopefully fix the audio
Social links
Social:
{
"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"
}
Telegram Group: https://t.me/htconexwip
Me: https://telegram.me/timkoers
Nice
---------- Post added at 05:27 PM ---------- Previous post was at 05:26 PM ----------
@DevUt
yes... great news for our old One X !!
Guys, the latest build is up, not sure if it will boot though. Please let me know
IIRC I solved the mediaserver crashes @mrbtree98 ?
Which tree are you using ?
The crashes are relates to the hal changes
DevUt said:
IIRC I solved the mediaserver crashes @mrbtree98 ?
Which tree are you using ?
The crashes are relates to the hal changes
Click to expand...
Click to collapse
I can't remember if you did or not. I think you were working on it though.
mrbtree98 said:
I can't remember if you did or not. I think you were working on it though.
Click to expand...
Click to collapse
Ah! I remember it now we fixed it !
Remember I was deleting some lines in init.rc to remove mediserver !
DevUt said:
Ah! I remember it now we fixed it !
Remember I was deleting some lines in init.rc to remove mediserver !
Click to expand...
Click to collapse
At which three? I might be able to build one today.
I've synced LineageOS 14 with the CM-14 trees, and the compilation doesn't even start, so I'll have to look in to that
I just want to thank you or making this rom. I am on cm12 and once this rom is more stable I will flash it and give it a try.
Might take a while howeve ?
College has started again
Yay, I have a One X, would love to try out the rom, although audio, gps and camera are quite a necessity I keep wondering, how difficult is it to fix those kinds of issues?
Byrkoet said:
Yay, I have a One X, would love to try out the rom, although audio, gps and camera are quite a necessity I keep wondering, how difficult is it to fix those kinds of issues?
Click to expand...
Click to collapse
Audio is very difficult, the audio subsystem has changed during the upgrade from 5 to 6.
I haven't got time to try to fix them.
Don't expect very much very soon
Hello,
Really cool what you do, the One X under Marshmallow is extraordinary, you have all my encouragement and I'm looking forward to testing.
I have a question...why not directly compile a Nougat version?
DeepScred said:
Hello,
Really cool what you do, the One X under Marshmallow is extraordinary, you have all my encouragement and I'm looking forward to testing.
I have a question...why not directly compile a Nougat version?
Click to expand...
Click to collapse
I'm working on it
Hey tim687,
really nice what you do. How is it going?
MrSirMan said:
Hey tim687,
really nice what you do. How is it going?
Click to expand...
Click to collapse
It's going very good with me man! Not with the rom however, I haven't found time to start working on it.
I've been very busy with various project for my school and at home.
I am not sure when I'll have time to start working on it again...
Thanks for the interest though!
I just get one today and would help you with testing if any of the issues has been fixed, unfortunately they are major =/
Nethunter Kernel for Samsung Galaxy S7 (SM-G930F/FD) Stock Oreo
Code:
I am not responsible for bricked devices.
If you going to flash it, you accepted it.
Of course your warranty is void.
This thread is only for herolte . If you have Edge go here
FEATURES:
BadUSB
HID gadget keyboard/mouse (with possibility to temporarily disable)
DriveDroid
USB WiFi, mac80211 (Monitor mode, packet capture, packet injection) [Compatibility List]
Ethernet
F2FS
Bluetooth HCI USB support
RTL-SDR DVB support
Boeffla wakelock blocker v1.10
Wireguard
Enable Netfilter Target TTL
rtl88xxau driver
rtl8188eus driver
Download:
Latest version G930F here.
Installation:
1. Flash latest TWRP twrp-3.3.0-1+ ( to see data partition with enabled disk quota)
1. TWRP Backup your ROM
2. Flash G930F_Nethunter_StockOreo_v*.img
3. Flash Universal DM-Verity, ForceEncrypt (You don't need to disable disk quota)
3. Flash latest Magisk 19.1+
4. Extract libs WiFi_fix_Libsecure_storage.so.zip to folders: /system/lib & /system/lib64 with rw-r--r-- permissions to libs.
5. Install busybox
6. Install Magisk Nethunter module from repository
7. Install kalifs-armhf-*.tar.xz by Nethunter manager
8. Extract Nethunter_Binaries.7z and binaries to folders:
Firmwares: system/etc/firmware and give permissions to every file rw-r--r--
hid-keyboard binary: system/xbin/ OR system/bin/ and give permissions to it rwxr-xr-x
9. Reboot
Loadable modules:
G930F_Nethunter_Modules_vX.X.zip extract only modules for your version of kernel.
In every kernel folder are modules and firmware. You need only modules which you want to use.
For example if you don't want use tuners and dvb-frontends. Don't load modules from /modules/drivers/media tuners and dvb-frontends
In firmware are compiled firmwares for some of modules to use they you need to copy they to system/etc/firmware.
basic commands:
insmod 88XXau.ko - load module
rmmod 88XXau.ko - unload module
lsmod - list loaded modules
Some modules depend on another modules. If you want load rt2800usb.ko, you need first load rt2800lib.ko.
Another way to load modules is Module Loader
Copy modules to storage and choose modules which you want to load (load they more than 1 times, this apk load modules from up to down it don't look at dependence from modules)
EXTRA:
1.In Utilities.7z are wifi testing tools binaries like aircrack-ng compiled from source of nexmon (Not needed for Nethunter only for test tools direct from android without Nethunter)
2. DriveDroid without bugs made by disabling HID Patch:
To disable HID Patch: use this command in terminal: "echo Y > /sys/module/g_android/parameters/hid_disable"
Changing mode isn't instant after changing module status. Use DriveDroid (mount iso -> dismount) to active hid_disable.
To enable HID Patch: "echo N > /sys/module/g_android/parameters/hid_disable" and use DriveDroid like with disabling HID Patch.
HIDPatchSwitch this is simple script which can switch between HID enabled and disabled and show changed status.
Old Installation steps:
1. TWRP Backup your ROM
2. Flash G930F_Nethunter_StockOreo_v*.img
2.1.Look at EXTRA.
3. Flash latest Magisk (Recommend 18.1+ version, 18.0 could make frezzes)
4. Extract libs WiFi_fix_Libsecure_storage.so.zip to folders: /system/lib & /system/lib64 with rw-r--r-- permissions to libs.
5. Install busybox can be one from Magisk repository
6. Install Magisk Nethunter module from repository
7. Install kalifs-armhf-*.tar.xz by Nethunter manager
8. Extract Nethunter_Binaries.7z and binaries to folders:
Firmwares: system/etc/firmware and give permissions to every file rw-r--r--
hid-keyboard binary: system/xbin/ OR system/bin/ and give permissions to it rwxr-xr-x
9. Reboot
Now you have Nethunter on your Stock Oreo ROM.
EXTRA:
1.If you want to have unencrypted data partition:
1.1. Format data partition(you lose your data).
1.2. After flashing kernel flash "remove encryption.zip".
1.3. Reboot to system (First start configuration wizard).
1.4. Reboot to twrp and flash Magisk.
Screens:
{
"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"
}
XDA:DevDB Information
[KERNEL] [G930F] Nethunter for Stock Oreo ROM, Kernel for the Samsung Galaxy S7
Contributors
Wirusx
Source Code: https://github.com/Svirusx/NetHunter-s7-kernel-StockOreo
Kernel Special Features:
Version Information
Status: Testing
Created 2019-02-05
Last Updated 2019-05-16
CHANGELOG
2020-12-06 - v1.5.1
Added loadable modules support
Update to Samsung source G930FXXS6ESI4
Enable Netfilter Target TTL
Added rtl88xxau driver
Added rtl8188eus driver
2019-05-16 - v1.4
Nethunter defconfig fixes
2019-04-20 - v1.3
Added monitor mode patches to some wifi usb drivers.
Added possibility to disable HIDPatch (this fixes DriveDroid)
Added HIDPatchSwitch: Simple sh script to switch status of HIDPatch (Info in comments in script)
2019-02-25 - v1.2
Added missing drivers like SUNRPC, NFS v4 etc.
Added Boeffla wakelock blocker
Removed unnecessary drivers.
2019-02-05 - v1.1
Rollback encryption drivers.
2019-02-05 - v1.0
Initial release.
Reserved
A Few Questions:
First of all, sorry if this is a silly question, but how are you supposed to flash the kernel when its in .img format? When i try to flash it with twrp it just asks mart wether i want to flash to the boot or recovery. Which do i choose? Also where do i get the disable encryption.zip that you mention in EXTRAS? Thanks so much for porting this to oreo though!
Jack_Rickwood said:
First of all, sorry if this is a silly question, but how are you supposed to flash the kernel when its in .img format? When i try to flash it with twrp it just asks mart wether i want to flash to the boot or recovery. Which do i choose? Also where do i get the disable encryption.zip that you mention in EXTRAS? Thanks so much for porting this to oreo though!
Click to expand...
Click to collapse
1. Choose boot. If you flash it like recovery than you lose TWRP and you need flash TWRP again by Odin.
2. disable encryption.zip i found sometime ago on this forum but now i can't find it again. I attach it to this post. I don't know why but only this one works for my phone to remove force encryption.
Ok, thx!
Wirusx said:
1. Choose boot. If you flash it like recovery than you lose TWRP and you need flash TWRP again by Odin.
2. disable encryption.zip i found sometime ago on this forum but now i can't find it again. I attach it to this post. I don't know why but only this one works for my phone to remove force encryption.
Click to expand...
Click to collapse
Ok, it seems to work well up to the wifi fix mart, but no matter what i seem to do, it wont let me change the permissions of the wifi fix libs! Do you have any idea why that might be?
Jack_Rickwood said:
Ok, it seems to work well up to the wifi fix mart, but no matter what i seem to do, it wont let me change the permissions of the wifi fix libs! Do you have any idea why that might be?
Click to expand...
Click to collapse
You need to have those files in linux partition like ext4 (system partition is fine for it)
So move files to system/vendor/lib64 and /system/vendor/lib and then change permissions.
you need too remount system partition because default it is read only. Some root explorers do that automatically.
If you have those files in microsd and most time it is exFAT or FAT32 here aren't unix permissions so you can't change permissions here.
Oh, ok, thx so much! Ive got it now
Wirusx said:
You need to have those files in linux partition like ext4 (system partition is fine for it)
So move files to system/vendor/lib64 and /system/vendor/lib and then change permissions.
you need too remount system partition because default it is read only. Some root explorers do that automatically.
If you have those files in microsd and most time it is exFAT or FAT32 here aren't unix permissions so you can't change permissions here.
Click to expand...
Click to collapse
Sorry, last thing. Some wifi hacking apps (like deauthentication) dont seem to be working. Would this be because i have to install the nexmon stuff, or is it just not working yet? If its because i have to install the nexmon stuff, what folder do i put them in and which permissions?
Jack_Rickwood said:
Sorry, last thing. Some wifi hacking apps (like deauthentication) dont seem to be working. Would this be because i have to install the nexmon stuff, or is it just not working yet? If its because i have to install the nexmon stuff, what folder do i put them in and which permissions?
Click to expand...
Click to collapse
For wifi testing you need special usb wifi dongle could be with AR9271 chip. If you want try wifi testing tools without usb wifi dongle you need to switch to Nethunter for LineageOS 14.1 it have monitor mode in interne wifi card.
All needed tools are IN Nethunter chroot soo you don't need binary from nexmon. You need to use Kali terminal or VNC to try wifi testing tools.
If you don't have needed tool in Nethunter chroot you need to update or install it like on normal Linux apt-get ...
Compile for Mi Mix 2 please? Lineage 15.1
Wirusx said:
Nethunter Kernel for Samsung Galaxy S7 (SM-G930F/FD) Stock Oreo
Code:
I am not responsible for bricked devices.
If you going to flash it, you accepted it.
Of course your warranty is void.
This thread is only for herolte . If you have Edge go here
FEATURES:
BadUSB
HID gadget keyboard/mouse
DriveDroid
USB WiFi, mac80211 (Monitor mode, packet capture, packet injection)
Ethernet
F2FS
Bluetooth HCI USB support
RTL-SDR DVB support
Download:
Latest version G930F here.
Installation:
1. TWRP Backup your ROM
2. Flash G930F_Nethunter_StockOreo_v*.img
2.1.Look at EXTRA.
3. Flash latest Magisk (Recommend 18.1+ version, 18.0 could make frezzes)
4. Extract libs WiFi_fix_Libsecure_storage.so.zip to folders: /system/lib & /system/lib64 with rw-r--r-- permissions to libs.
5. Install busybox can be one from Magisk repository
6. Install Magisk Nethunter module from repository
7. Install kalifs-armhf-*.tar.xz by Nethunter manager
8. Extract Nethunter_Binaries.7z and binaries to folders:
Firmwares: system/etc/firmware and give permissions to every file rw-r--r--
hid-keyboard binary: system/xbin/ and give permissions to it rwxr-xr-x
9. Reboot
Now you have Nethunter on your Stock Oreo ROM.
EXTRA:
1.If you want to have unencrypted data partition:
1.1. Format data partition(you lose your data).
1.2. After flashing kernel flash "remove encryption.zip".
1.3. Reboot to system (First start configuration wizard).
1.4. Reboot to twrp and flash Magisk.
2.In Utilities.7z are wifi testing tools binaries like aircrack-ng compiled from source of nexmon (Not needed for Nethunter only for test tools direct from android without Nethunter)
Screens:
XDA:DevDB Information
[KERNEL] [G930F] Nethunter for Stock Oreo ROM, Kernel for the Samsung Galaxy S7
Contributors
Wirusx
Source Code: https://github.com/Svirusx/NetHunter-s7-kernel-StockOreo
Kernel Special Features:
Version Information
Status: Testing
Created 2019-02-05
Last Updated 2019-02-06
Click to expand...
Click to collapse
Can you please compile this for Mi mix 2 (Chiron) on lineage 15.1 if you have time
Thanks in advance.
@Wirusx do you have telegram support group?
Wow, amazing! Great job! But as I understand it, Monitor mode and packet injection does not work here? Need to connect a usb wifi adapter?
Is it possible that in the future on the stock rom we will get these functions?
Cheers for porting this to Oreo. I may look at including this in my own kernel if you don't mind
Great job for porting this on Oreo, i was still using the one made for note 7 porting on Hydra ROM with Dualboot Patcher. Unfortunately when I flash it it freeze on the first screen of the boot, i'm on the last update of the _alexndr ROM, I tried flashing magisk 18.1 after the kernel or flashing kernel, remove_encryption.zip and magisk 18.1 as you suggested but I got the same result. Could this be becouse I'm on S3ERLF?
ModX81 said:
@Wirusx do you have telegram support group?
Click to expand...
Click to collapse
Sry no telegram support group,
_Danil_ said:
Wow, amazing! Great job! But as I understand it, Monitor mode and packet injection does not work here? Need to connect a usb wifi adapter?
Is it possible that in the future on the stock rom we will get these functions?
Click to expand...
Click to collapse
Monitor mode working when you have special usb wifi adapter like TP-Link TL-WN722N.
All wifi usb adapters with AR9271 chip are fine for kali linux and for this Nethunter port
but you can try my port of LineageOS 14.1 it have support to monitor mode by nexmon ( it's not perfect like usb dongle but works...)
djb77 said:
Cheers for porting this to Oreo. I may look at including this in my own kernel if you don't mind
Click to expand...
Click to collapse
Its open source project made for fun. Do that if you want
SLAYER96 said:
Great job for porting this on Oreo, i was still using the one made for note 7 porting on Hydra ROM with Dualboot Patcher. Unfortunately when I flash it it freeze on the first screen of the boot, i'm on the last update of the _alexndr ROM, I tried flashing magisk 18.1 after the kernel or flashing kernel, remove_encryption.zip and magisk 18.1 as you suggested but I got the same result. Could this be becouse I'm on S3ERLF?
Click to expand...
Click to collapse
Normally i don't use csc mods and this Nethunter is made from Samsung Sources for Stock ROM kernel it may not working with custom ROMs.
When you format data partition and then flash STOCK ROM you can run it for first time it is going to STOCK recovery and install csc than is reboot and NOW you need to go to download mode and flash TWRP and then further like in tutorial but alternative to it could be my next custom kernel port.
I'm busy with porting the best custom kernel which i'm using on my S7 TGPKernel by djb77. I think i can today or tommorow publicate first version of this Nethunter MOD.
Execution of wifite :crying:
All right, thanks for the NetHunter kernel for the stock oreo for Samsung S7, the detail is when starting wifite I get a message to install additional components
, and the second message when downloading from github the first package "aanarchyy", I get an installation error, some way to repair it ?
, and another way to install all packages from a single installation ?, Thanks Svirusx :good:
k4mu5 said:
All right, thanks for the NetHunter kernel for the stock oreo for Samsung S7, the detail is when starting wifite I get a message to install additional components
, and the second message when downloading from github the first package "aanarchyy", I get an installation error, some way to repair it ?
, and another way to install all packages from a single installation ?, Thanks Svirusx :good:
Click to expand...
Click to collapse
I think, this is a repository problem, additional necessary components are not installed. I installed the repositories through katoolin. And now there are no problems, and always fresh libraries on nethunter.
_Danil_ said:
I think, this is a repository problem, additional necessary components are not installed. I installed the repositories through katoolin. And now there are no problems, and always fresh libraries on nethunter.
Click to expand...
Click to collapse
thanks for answering and your help, but sorry if I look a bit clumsy, but pyrit does not appear in the katoolin menu or under what name is, or could you give me a hand to install full wifite?, on the websites I visited mentioned the installation but for linux or ubuntu and with nvidia card, some clue if it serves as something for smarthphone, thanks
{
"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"
}
Team Bliss is pleased to present to you
BlissRoms based on Android 11
Bliss ROMs comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all platforms you run Bliss on.
Before you Download take note of this:
This is an unofficial build. It may have some undiscovered bugs. So, please use at your own risk.
If you find a bug or have any suggestion, message me on Telegram
BlissROM DownloadLatest TWRP recovery Download
Installing from Android 10 Rom's.
- Install latest TWRP
- Flash BlissROM
- Flash TWRP
- WIPE DATA
- Reboot to TWRP
- Reboot to System and #StayBlissful
If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you and our team quite some time.
-Download the Catlog app from the Play Store.
-There is also a donate version which you can purchase to show appreciation.
-After downloading the Catlog app, go to the app settings, and change the log level to Debug.
-Clear all previous logs and take the exact steps to produce the error you are receiving.
-As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.
-Copy and paste the entire log either to Hastebin or Pastebin
-Save the log, and copy and paste the link into the forum with a brief description of the error.
BlissRoms GithubBlissRoms GerritBlissRoms Device SourcesBlissRoms Kernel SourceDevice TreeDevice Tree (wahoo)
BlissRoms Website Bliss Blog BlissRoms FacebookBlissRoms TwitterBlissRoms InstagramBlissRoms Telegram GroupBlissRoms Announcements Telegram ChannelBliss Wiki
Donate:
Donate to Maintainer:
@jackeagle
@electrikjesus
@Rohanpurohit
@rwaterspf1
@ideaman924
@Makaveli_da_dev
@ElfinJNoty
@BitOBSessiOn
@customworx
@nilac
@sixohtew
@aclegg2011
@Roger.T
@T.M.Wrath
@kanttii
@REV3NT3CH
@techfreak243
@SuperDroidBond
@USA_RedDragon
@bcrichster
@DeadmanxXD
@krittin98
@blackscorpion
@TechExhibeo
@DroidBot
@Siphonay
@pacer456
@nitin1438
@theGeekyLad
@kunalshah912
@LordArcadius
@AryanAA
A huge thanks to Chainfire, CM/LineageOS, Android-x86, Jide, topjohnwu (Magisk) @farmerbb & all the other developers who work hard to keep all the great features coming!
We really appreciate all your knowledge & hard work!
Thank you for using Bliss! And as always: #StayBlissful
*Reserved*
Cant flash NikGapps on it, using the vanilla build (i prefer up to date GApps), NikGapps reports 0 free space on /system - seen this on a few ROMS...no idea why it wont let me install
Doing adb shell df -h /system after flash and reboot reports 1Gb free...but yet still NikGapps wont install on there
Same NikGapps (full, with config to cherrypick what i use) as i use on Proton, PixelExeprience
Back to Proton/PixelExperience for now
Edit/Update:
Looks like it may be a NikGapps build issue, im downloading a new one and will retest
Nope, that didnt do it either.
Just flashed the gappd build and things are working smooth and apps are getting restored as i write. Will monitor the performance and battery drain over the next couple of days.
Couldnt find active edge in here, hopefully it's added in future builds.
73sydney said:
Cant flash NikGapps on it, using the vanilla build (i prefer up to date GApps), NikGapps reports 0 free space on /system - seen this on a few ROMS...no idea why it wont let me install
Doing adb shell df -h /system after flash and reboot reports 1Gb free...but yet still NikGapps wont install on there
Same NikGapps (full, with config to cherrypick what i use) as i use on Proton, PixelExeprience
Back to Proton/PixelExperience for now
Edit/Update:
Looks like it may be a NikGapps build issue, im downloading a new one and will retest
Nope, that didnt do it either.
Click to expand...
Click to collapse
I think you need to check if the system_root partition is mounted or not. I faced that error too. Had to format the system partition into ext4 and then I could install opengapps and nikgapps as well. Currently I am on the vanilla build with opengapps (pico) installed on it.
RealOkabe said:
I think you need to check if the system_root partition is mounted or not. I faced that error too. Had to format the system partition into ext4 and then I could install opengapps and nikgapps as well. Currently I am on the vanilla build with opengapps (pico) installed on it.
Click to expand...
Click to collapse
I had to do the EXT2 to EXT4 trick on /data already because of the old storage = 0 issue, i wish someone would fix TWRP
I didnt check for system_root or notice it though, so ill look into it, cheers...
So no edge sense in this build?
RealOkabe said:
I think you need to check if the system_root partition is mounted or not. I faced that error too. Had to format the system partition into ext4 and then I could install opengapps and nikgapps as well. Currently I am on the vanilla build with opengapps (pico) installed on it.
Click to expand...
Click to collapse
Is there any benefit over gapps?
73sydney said:
Cant flash NikGapps on it, using the vanilla build (i prefer up to date GApps), NikGapps reports 0 free space on /system - seen this on a few ROMS...no idea why it wont let me install
Doing adb shell df -h /system after flash and reboot reports 1Gb free...but yet still NikGapps wont install on there
Same NikGapps (full, with config to cherrypick what i use) as i use on Proton, PixelExeprience
Back to Proton/PixelExperience for now
Edit/Update:
Looks like it may be a NikGapps build issue, im downloading a new one and will retest
Nope, that didnt do it either.
Click to expand...
Click to collapse
Always using for all roms without gapps this configuration and works everything fine.
Here me nikgapps.conf
# NikGapps configuration file
# visit https://nikgapps.com/misc/2020/11/22/NikGapps-Config.html to read everything about nikgapps
# If you are not sure about the config, just skip making changes to it or comment it by adding # before it
#InstallPartition=system
mode=install
# set WipeDalvikCache=0 if you don't want the installer to wipe dalvik/cache after installing the gapps
WipeDalvikCache=1
# set WipeRuntimePermissions=1 if you want to wipe runtime permissions
WipeRuntimePermissions=0
# Addon.d configs set them to 0 to skip the functionality
execute.d=1
mount.d=1
unmount.d=1
# Addon version (set it to 3 if you use lineageOs recovery, set it to 2 if you're using twrp recovery)
addon_version.d=2
# Following are the packages with default configuration
# Set Core=0 if you want to skip installing all packages belonging to Core Package
Core=1
>>ExtraFiles=1
>>GooglePlayStore=1
>>GoogleServicesFramework=1
>>GoogleContactsSyncAdapter=1
>>GoogleCalendarSyncAdapter=1
>>GmsCore=1
DigitalWellbeing=1
VancedManager=0
GoogleMessages=0
GoogleDialer=0
GoogleContacts=1
CarrierServices=1
GoogleClock=1
# Set SetupWizard=0 if you want to skip installing all packages belonging to SetupWizard Package
SetupWizard=1
>>SetupWizard=1
>>GoogleRestore=1
>>GoogleOneTimeInitializer=1
# Set Pixelize=0 if you want to skip installing all packages belonging to Pixelize Package
Pixelize=1
>>PixelSetupWizard=1
>>AndroidMigratePrebuilt=1
>>PixelTips=0
>>PixelConfigOverlays=1
GoogleCalculator=0
Drive=0
GoogleMaps=0
GoogleLocationHistory=1
Gmail=0
GooglePhotos=0
DeviceHealthServices=1
GoogleDuo=0
Velvet=1
GBoard=1
# Set PixelLauncher=0 if you want to skip installing all packages belonging to PixelLauncher Package
PixelLauncher=1
>>PixelLauncher=1
>>DevicePersonalizationServices=1
>>QuickAccessWallet=1
# Set GoogleFiles=0 if you want to skip installing all packages belonging to GoogleFiles Package
GoogleFiles=0
>>GoogleFiles=1
>>StorageManager=1
PlayGames=0
GoogleCalendar=0
MarkupGoogle=1
GoogleWallpaper=1
GoogleFeedback=0
GooglePartnerSetup=1
GoogleSounds=1
AndroidDevicePolicy=1
GoogleKeep=0
Books=0
Assistant=1
YouTubeMusic=0
GoogleRecorder=1
GoogleTTS=1
GoogleTalkback=1
DeviceSetup=1
AndroidAuto=0
# Set GoogleChrome=0 if you want to skip installing all packages belonging to GoogleChrome Package
GoogleChrome=1
>>GoogleChrome=0
>>WebViewGoogle=1
>>TrichromeLibrary=1
GoogleDocs=0
GoogleSheets=0
GoogleSlides=0
# Set CoreGo=0 if you want to skip installing all packages belonging to CoreGo Package
CoreGo=0
GoogleGo=1
AssistantGo=1
MapsGo=1
NavigationGo=1
GalleryGo=1
GmailGo=1
irmas5 said:
Always using for all roms without gapps this configuration and works everything fine.
Here me nikgapps.conf
# NikGapps configuration file
# visit https://nikgapps.com/misc/2020/11/22/NikGapps-Config.html to read everything about nikgapps
# If you are not sure about the config, just skip making changes to it or comment it by adding # before it
#InstallPartition=system
mode=install
# set WipeDalvikCache=0 if you don't want the installer to wipe dalvik/cache after installing the gapps
WipeDalvikCache=1
# set WipeRuntimePermissions=1 if you want to wipe runtime permissions
WipeRuntimePermissions=0
# Addon.d configs set them to 0 to skip the functionality
execute.d=1
mount.d=1
unmount.d=1
# Addon version (set it to 3 if you use lineageOs recovery, set it to 2 if you're using twrp recovery)
addon_version.d=2
# Following are the packages with default configuration
# Set Core=0 if you want to skip installing all packages belonging to Core Package
Core=1
>>ExtraFiles=1
>>GooglePlayStore=1
>>GoogleServicesFramework=1
>>GoogleContactsSyncAdapter=1
>>GoogleCalendarSyncAdapter=1
>>GmsCore=1
DigitalWellbeing=1
VancedManager=0
GoogleMessages=0
GoogleDialer=0
GoogleContacts=1
CarrierServices=1
GoogleClock=1
# Set SetupWizard=0 if you want to skip installing all packages belonging to SetupWizard Package
SetupWizard=1
>>SetupWizard=1
>>GoogleRestore=1
>>GoogleOneTimeInitializer=1
# Set Pixelize=0 if you want to skip installing all packages belonging to Pixelize Package
Pixelize=1
>>PixelSetupWizard=1
>>AndroidMigratePrebuilt=1
>>PixelTips=0
>>PixelConfigOverlays=1
GoogleCalculator=0
Drive=0
GoogleMaps=0
GoogleLocationHistory=1
Gmail=0
GooglePhotos=0
DeviceHealthServices=1
GoogleDuo=0
Velvet=1
GBoard=1
# Set PixelLauncher=0 if you want to skip installing all packages belonging to PixelLauncher Package
PixelLauncher=1
>>PixelLauncher=1
>>DevicePersonalizationServices=1
>>QuickAccessWallet=1
# Set GoogleFiles=0 if you want to skip installing all packages belonging to GoogleFiles Package
GoogleFiles=0
>>GoogleFiles=1
>>StorageManager=1
PlayGames=0
GoogleCalendar=0
MarkupGoogle=1
GoogleWallpaper=1
GoogleFeedback=0
GooglePartnerSetup=1
GoogleSounds=1
AndroidDevicePolicy=1
GoogleKeep=0
Books=0
Assistant=1
YouTubeMusic=0
GoogleRecorder=1
GoogleTTS=1
GoogleTalkback=1
DeviceSetup=1
AndroidAuto=0
# Set GoogleChrome=0 if you want to skip installing all packages belonging to GoogleChrome Package
GoogleChrome=1
>>GoogleChrome=0
>>WebViewGoogle=1
>>TrichromeLibrary=1
GoogleDocs=0
GoogleSheets=0
GoogleSlides=0
# Set CoreGo=0 if you want to skip installing all packages belonging to CoreGo Package
CoreGo=0
GoogleGo=1
AssistantGo=1
MapsGo=1
NavigationGo=1
GalleryGo=1
GmailGo=1
Click to expand...
Click to collapse
Dude, i know how to make a config file
Sui77 said:
So no edge sense in this build?
Click to expand...
Click to collapse
No Edge sense. And I have fallen back to Havoc for now, as the settings in this ROM is very agressive in killing apps even if they are idling in background like cpu or battery monitor apps.
Haven't faced that in audio or IM calls.
palimatix said:
No Edge sense. And I have fallen back to Havoc for now, as the settings in this ROM is very agressive in killing apps even if they are idling in background like cpu or battery monitor apps.
Haven't faced that in audio or IM calls.
Click to expand...
Click to collapse
Unfortunately ive noticed this too, across most current ROMs, a lot of background apps/processes getting killed, even if not optimized in battery optimization.
Case in point, and most notable, because it vibrates everytime it loses connection, is all the Galaxy Wear related apps/processes for my Active 2 watch. The ridiculous thing is that the processes die and the watch goes into standalone mode pretty much ONLY when youre actively using the phone. Even browsing a website will cause the watch dropout
Devs are being too aggressive in optimization or performance, yes you can alter these settings yourself with some fiddling, but shouldnt have to out of the box...
In better news, after a couple of days being stuck in the custom build system and NikGapps, the lovely dev fasttracked my stuck custom build and i have it downloading now, my custom build comes in at 740Mb, wont need a config file at all as it only has my cherrypicked apps that i use and should hopefully cause less storage issues than the full one at 1Gb
Just plain rude to make a thread one day after I built the bliss.
I will not make one with this.
Blackjubel said:
Just plain rude to make a thread one day after I built the bliss.
I will not make one with this.
Click to expand...
Click to collapse
I thought you had just made a test build...that you posted in the other thread...
Not sure this dev was aware?
So....still no go here
Still unable to get this to work, more work than ive ever put into trying to flash any ROM ever
Even with my new custom smaller NikGapps...
Process (from other ROM):
adb reboot bootloader
fastboot erase userdata && fastboot erase system_a && fastboot erase system_b
fastboot boot twrp-3.5.2_9-0-taimen.img (note i tried 3 other versions)
change filesystem on data and system (from) EXT4 to EXT2 and back to EXT 4 again
(all partitions mounted correctly - usually i just do all this blindly from my PC via command line and never look at the phone)
adb sideload Bliss-v14.2-taimen-UNOFFICIAL-vanilla-20210502.zip
adb reboot bootloader
fastboot boot twrp-3.5.2_9-0-taimen.img
adb sideload NikGapps-73sydney-arm64-11-20210504-signed.zip
errors out again about not enough room on system.....ffs....spent 2 days on this...not the same error as yesterday, now its clear the ROM doesnt leave enough room on /system
Getting tired of ROMS you cant actually put your own GApps on, this is now one of 3 current ROMS that error our when trying to do what people like me have done for eons...since the beginning of time, and Android
Back to something that works, for the second night in a row...
ROMS with a /system size issue that i will no longer test (unless someone wants to fix them):
BlissROM (this vanilla version)
Havoc
ArrowOS
Of course devs could make people like me wanting to use their own GApps redundant by updating their included G-Apps, because thats why i dont use GApps included builds, the GApps are always months out of date, and so apart from a massive zip download, then i have to download another 400-600Mb of updates from the App Store
At this point im going to stick between Proton (when thats fixed) and PixelExperience and stop testing other ROMs, wastes too much time
Blackjubel said:
Just plain rude to make a thread one day after I built the bliss.
I will not make one with this.
Click to expand...
Click to collapse
If you want to maintain it then I can just stop.
73sydney said:
So....still no go here
Still unable to get this to work, more work than ive ever put into trying to flash any ROM ever
Even with my new custom smaller NikGapps...
Process (from other ROM):
adb reboot bootloader
fastboot erase userdata && fastboot erase system_a && fastboot erase system_b
fastboot boot twrp-3.5.2_9-0-taimen.img (note i tried 3 other versions)
change filesystem on data and system (from) EXT4 to EXT2 and back to EXT 4 again
(all partitions mounted correctly - usally i jst do all this form my PC via command line and never look at the phone)
adb sideload Bliss-v14.2-taimen-UNOFFICIAL-vanilla-20210502.zip
adb reboot bootloader
fastboot boot twrp-3.5.2_9-0-taimen.img
adb sideload NikGapps-73sydney-arm64-11-20210504-signed.zip
errors out again about not enough room on system.....ffs....spent 2 days on this...not the same error as yesterday, now its clear the ROM doesnt leave enough room on /system
Getting tired of ROMS you cant actually put your own GApps on, this is now one of 3 current ROMS that error our when trying to do what people like me have for eons...
Back to something that works, for the second night in a row...
At this point im going to stick between Proton (when thats fixed) and PixelExperience and stop testing other ROMs, wastes too much time
Click to expand...
Click to collapse
Dude, just change filesystem on your data partition and install normally through twrp. It works. I am using the same. If not, then go for the gapps build or download the factory image that I have posted on sourceforge.
RealOkabe said:
Dude, just change filesystem on your data partition and install normally through twrp. It works. I am using the same. If not, then go for the gapps build or download the factory image that I have posted on sourceforge.
Click to expand...
Click to collapse
Please read my post again, where i clearly state i change the filesystem to EXT2 and then back to EXT4 on both data and system to properly mount them and have them correct size...thats not it, its the ROM
As i said, if devs want to build GApps included ROM's with up to date GApps, then im up for that....but i wont be downloading any GApps included ROMS that have GApps in them that are months old and then having to waste 400-600Mb on top of that out of my data allowance to update GApps from the Play Store (i cant be the only person annoyed by this). Unless devs want to pay my data bills, of course.
The entire reason i prefer GApps free builds...especially testing multiple ROMs is because it saves me data/money. I can download NikGapps once a month and flash them across multiple ROMs, where as if i downloaded GApps included ROM's (with out of data GApps), im wasting so much data/money it isnt funny...
3 x GApps(less) ROM's a month = @2.1 Gb
1 x NikGapps a month = @700Mb
Total = 2.8Gb
3 x GApps(included) ROM's a month = @3.5 Gb
3 x 400Mb updates for out of date GApps from Play Store = @1.2Gb
Total = 4.7Gb
Big difference, hope that makes it clear
Okay so since there is someone else who wants to maintain this rom, I will be stepping down from this. I will be back with some other rom. Thanks for trying it out. Do look forward to my next work.
@73sydney, I already talked about this before, but my advice was ignored
After flashing rom in both slots, flash nikgapps and if it gives an error about insufficient memory, then switch to another slot, reboot into twrp again and flash nikgapps again
{
"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"
}
Droidian is a GNU/Linux distribution based on top of Mobian, a Debian-based distribution for mobile devices. The goal of Droidian is to be able to run Mobian on Android phones.
This is accomplished by using well-known technologies such as libhybris and Halium.Carefully read the whole post before jumping to installation.They are important to give you the best idea of the current state of the OS.
What is working:- Alarm Clock (bullseye/stable only. Doesn't work on bookworm/nightly)
- Manual brightness
- Vibration
- Carrier info, signal strength
- Data connection (read bugs section)
- Incoming, outgoing calls
- SMS in, out
- Change audio routing
- Voice in calls
- Volume control in calls
- Bluetooth
- WiFi
- Proximity
- Rotation
- Touchscreen
- Earphones
- Headphones
- Loudspeaker
- Microphone
- Volume control
- Pin unlock
- Waydroid
- Wireguard
What doesn't work:- Most of the things not mentioned above.
Bugs:- RIL gets broken after switching airplane mode or modem off/on. Fixed after a reboot.
- Mobile data stops working after making or receiving calls. Toggle mobile data on and off from the settings app.
- Mobile data doesn't work in the first 2-3 minutes after reboots. Toggle mobile data on and off from the settings app after waiting a while to get it working.
- Droidian has no power management yet so you're left with only the 5020mAh battery which can last up to 6 hours without heavy usage.
Installation:
Make a backup now, as your device will be wiped.
Click to expand...
Click to collapse
Download the needed files and tools
Droidian rootfs (specific build required)
Android 10 (Q) stock firmware
Latest TWRP recovery
Adaptation (unofficial)
Device preparation
A USB 2.0 port/hub with an actual USB 2.0 controller is recommended (Using fastboot on a USB 3.0 port may cause errors with some Xiaomi devices)
Save your APN (Android)
The Access Point Name or APN can be found in the Settings menu of Android
Take a piece of paper or a text editor, and write down everything that you see on that screen
These are likely to include a URL (e. g., internet.carrier.net), a username, and possibly a password
Unlock the bootloader (Computer)
Refer to the instructions provided by the device manufacturer
Other useful sources include the LineageOS wiki and xda-developers
Boot into recovery (Computer)
Boot TWRP by running fastboot boot twrp-VERSION-miatoll.img
Wipe the device (TWRP)
Go to the Wipe menu
Select Advanced wipe
Tick the boxes called Dalvik / ART cache, Cache, System, Vendor, Data
Swipe to Wipe
Go back to the previous menu
Choose Format data and type yes
Go back to the main menu and select Reboot
Choose Bootloader
Boot TWRP again by running fastboot boot twrp-VERSION-miatoll.img
Copy the files to the device (Computer)
When TWRP is booted, open the device’s Internal storage from your computer
Copy all of the files you downloaded to this folder
Droidian installation (TWRP)
Install recovery
Install the file called twrp-VERSION-miatoll.img as an Image to the Recovery partition
Install Droidian rootfs
Install the file called droidian-rootfs-arm64_YYYYMMDD.zip as a Zip file
Alternatively, you can enter ADB sideload mode and run adb sideload droidian-rootfs-arm64_YYYYMMDD.zip
Installation is optional for stable releases, but it is recommended, because it helps with debugging
Finalizing the installation
Install adaptation package as a flashable zip (TWRP)
Install the file called adaptation-droidian-miatoll.zip as a Zip file
Alternatively, you can enter ADB sideload mode and run adb sideload adaptation-droidian-miatoll.zip
Boot your device
Go to the Reboot menu and choose System
TWRP might complain that there is no OS installed, but that’s fine
The first boot may take longer, and at least one spontaneous reboot is expected during the process
You should be greeted with the lock screen, the default password is 1234
Congratulations, if everything went well, now you should be running Droidian.
Notes:
Recovery
Use the recovery linked at the start of this page. The installation might fail with other recoveries that the one mentioned above.
Default password
The default password is 1234.
Apn
Mobile data needs an APN to be set up from Settings -> Mobile Network -> Access Point Names.
Broken mobile data after calls
Data connection might break after receiving and making calls. Switch it off and on from Settings -> Mobile Network to fix it. Be careful to not turn off the mobile modem or a device restart might be required.
Broken calls
Switching airplane mode on and off or switching the mobile modem off and on from the Quick Settings or the Settings App will break calls. If that’s the case reboot the phone to fix it.
Out of storage
By default when flashing Droidian it allocates 8GB of memory to the system. This might not be enough and luckily you can allocate more storage with ADB by running (while in recovery): adb shell e2fsck -fy /data/rootfs.img and adb shell resize2fs -f /data/rootfs.img xG where x is the amount of GB to allocate (eg: 50G for 50 GB).
Status
Droidian GSIs are experimental! Bugs and missing features are expected.
SSH access
Connect your phone to your computer and type ssh [email protected], the password is 1234 (on Windows, you may need PuTTY)
Applications
You can find a list of mobile-friendly Linux applications at LinuxPhoneApps
Credit:Marcel Alexandru Nitan
Droidian Mobian UBports
You can ask for assistance specific to this device at Droidian for miatoll devices.
Sources:- kernel
- adaptation package
Donate:- PayPal
- Revolut
Announcement/Update ~ Droidian
Support for Droidian Bullseye has been discontinued. Droidian Bookworm has become more stable while the old Bullseye version hasn't received any updates from the devs since December 2021.
Users that are still on Bullseye are recommended to backup their data and install the Bookworm version for Droidian by following the new instructions located at https://devices.droidian.org/devices/miatoll/
For already Bookworm users:
Until now we've used the same ramdisk Ubuntu Touch uses because Droidian had no dynamic partition support. That has been changed on the previous days and a new adaptation package has been created to update the old ramdisk we used.
I've disabled the old miatoll ppa repository so the kernel won't get updated since it will "wipe" all the data and modifications.
To continue to receive kernel updates add the new miatoll ppa repository:
Your data and system changes will be cleared but will remain in /userdata/rootfs-overlay which will no longer be used after updating to the latest kernel as all the changes are now written into the Droidian rootfs.
Bash:
sudo curl -# --proto '=https' --tlsv1.2 -Sf https://miatoll-linux.github.io/repo/miatoll.gpg --output /usr/share/keyrings/miatoll.gpg && \
echo "deb [signed-by=/usr/share/keyrings/miatoll.gpg] https://miatoll-linux.github.io/repo/ bookworm main" > ~/miatoll.list && \
sudo mv ~/miatoll.list /etc/apt/sources.list.d/miatoll.list && \
sudo apt update
sudo apt upgrade
Thanks for the new Rom!
Can you reduce installation step. Currently it's too lengthy to follow.
Amazing work man! But I would be surprised if anyone would be even able to flash it. Recently I uploaded a ROM with a fully automated installer and even that was too complicated for many people so I already feel sorry for this thread and You the Dev.
Other than that. Thank You soooo much for this <3. I can't wait to flash it!
ProtoDeVNan0 said:
Amazing work man! But I would be surprised if anyone would be even able to flash it. Recently I uploaded a ROM with a fully automated installer and even that was too complicated for many people so I already feel sorry for this thread and You the Dev.
Other than that. Thank You soooo much for this <3. I can't wait to flash it!
Click to expand...
Click to collapse
Not to go off topic but that's one of the reasons I stopped making Roms on XDA and instead keep them for myself lol.
Anyways OP, Amazing to see people working on Debian based Roms for our device. Will definitely be checking this out sometime this week!
[email protected] said:
Thanks for the new Rom!
Can you reduce installation step. Currently it's too lengthy to follow.
Click to expand...
Click to collapse
Unfortunately I can't. The recoveries we have available for our phones are not able to mount the raw img file (rootfs.img) so sideloading the devtools and the adaptation package is not possible so we have to manually fix the mount via losetup and make the extraction of the packages above ourselves.
Probably everything will be fixed when we're going to get a fully working and stable recovery.
hi! what is it the current situation of battery drain, i really want to give a try
[email protected] said:
Thanks for the new Rom!
Can you reduce installation step. Currently it's too lengthy to follow.
Click to expand...
Click to collapse
Installation steps reduced
[email protected] said:
hi! what is it the current situation of battery drain, i really want to give a try
Click to expand...
Click to collapse
Well it improved since the last time. Don't expect days of battery life but it's enough to get you through the day
*Waydroid can decrease the battery like a lot btw.
Hi, I really love your work @nitanmarcel
Thanks
How is this for daily use?
Mobile data problems fixed?