[ROM] Sailfish OS for the Xiaomi Mi2 / Mi2S (aries)

[ROM] Sailfish OS for the Xiaomi Mi2 / Mi2S (aries) - Xiaomi Mi 2

{
"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"
}

Updates
2020-03-31 Alternative sfos download
2019-08-08 Add support for Devices with merged partitions
Disclaimer
WARNING: "Modifying or replacing your device’s software may void your device’s warranty, lead to data loss,hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with this project is responsible for your actions but yourself. Good luck."
About Sailfish OS
Sailfish OS is a GNU/Linux based mobile operating system, which is gesture-driven for the ease of use. It runs natively as glibc (not Android's bionic), has bash and busybox (not toolbox), uses Qt for UX, and other opensource projects in its middleware -- which basically is just like a Linux on your desktop, but needs Android drivers for some of device's hardware.
Change log
2019-08-08 Support for devices with merged partitions (alpha based on cm-12.1)
2019-07-13 Resolve touch issue on some models
2019-07-10 OTA
2019-07-08 Init
What works
calls/SMS/data
audio
camera
video
wifi
bt
gps
sensors
what's not
Hotspot (not tested yet)
FM (not tested yet)
Known Issues
First boot may fails then shows lock screen without showing security setting. Need to reboot
Issue on Devices with unmerged partitions only:
Internal sdcard cannot show size in settings since it's mounted to /home/nemo/sdcard
Issue on Devices with merged partitions only:
First boot camera may fails. Need to reboot
Alpha version until now, not support OTA
How to install
1. precondistions
BACKUP YOUR FILES FIRST
MAKE CLEAR YOUR DEVICE PARTITIONS are MERGED or UNMERGED. Both are supported, but if you want unmerge partitions just flash earlier DEV rom with unmerged partitions (e.g. MIUI v5 4.12.5).
2. install steps
2.1. install steps for devices with UNMERGED partitions:
unlock bootloader
flash twrp recovery & format data/cache partition
flash zip with twrp. flash official stable CyanogenMod 11.0 ROM or cm-11-20190626-UNOFFICIAL-aries.zip
reboot to CyanogenMod, after init down, reboot to recovery
flash sailfishos zip with twrp. flash sailfishos-aries-release-3.0.2.8.zip
alternative download: sailfishos-aries-release-3.0.2.8.zip
reboot
2.2. install steps for devices with MERGED partitions:
unlock bootloader
flash twrp recovery & format data/cache partition
flash zip with twrp. flash CyanogenMod 12.1 ROM cm-12.1-20190804-UNOFFICIAL-aries.zip
reboot to CyanogenMod, after init down, reboot to recovery
flash sailfishos zip with twrp. flash sailfishos-aries-release-3.0.3.9-L-alpha-20190808.zip
alternative download: sailfishos-aries-release-3.0.3.9-L-alpha-20190808.zip
reboot
OTA updates
Only support for Devices with UNMERGED partitions until now. To upgrade to a new Sailfish OS release, enter these commands as root
Code:
ssu re 3.0.3.9
version --dup
WIKI Page
https://wiki.merproject.org/wiki/Adaptations/libhybris/Install_SailfishOS_for_aries
Bug report
Please report bugs in this thread
Thanks
birdzhang, mal, and all from #sailfishos-porters

wow! great efforts, thank you!
looks like our beloved mi2(s)s have nine lives..

Hello, thank you for your dedication to make my phone another ROS. Here I have a few bugs that need feedback. I successfully flashed the Sailfish os according to your tutorial, but stuck in the language selection interface. In this interface, my touch screen doesn't work, how should I solve it? (A lot of people have already fed back this question)

丶Nanmu said:
Hello, thank you for your dedication to make my phone another ROS. Here I have a few bugs that need feedback. I successfully flashed the Sailfish os according to your tutorial, but stuck in the language selection interface. In this interface, my touch screen doesn't work, how should I solve it? (A lot of people have already fed back this question)
Click to expand...
Click to collapse
Thank you for your feedback. Sorry i cannot provide solution now because i've never met this bug before so i need more info to check what's wrong there.
Could you help provide more details?
1. your device model, mi2 or mi2s 16g or mi2s 32g?
2. have you flashed back to the version with unmerged partitions? which cm rom you've flashed?
3. it's only touch screen not work, right? how about ui? is there any crash or reboot occur?
perhaps you can try to reboot it / just reflash sailfish os zip

丶Nanmu said:
Hello, thank you for your dedication to make my phone another ROS. Here I have a few bugs that need feedback. I successfully flashed the Sailfish os according to your tutorial, but stuck in the language selection interface. In this interface, my touch screen doesn't work, how should I solve it? (A lot of people have already fed back this question)
Click to expand...
Click to collapse
and how about if you flash cm rom without sailfish os ? does touch work or not after you boot to cm?

liuxdev said:
Thank you for your feedback. Sorry i cannot provide solution now because i've never met this bug before so i need more info to check what's wrong there.
Could you help provide more details?
1. your device model, mi2 or mi2s 16g or mi2s 32g?
2. have you flashed back to the version with unmerged partitions? which cm rom you've flashed?
3. it's only touch screen not work, right? how about ui? is there any crash or reboot occur?
perhaps you can try to reboot it / just reflash sailfish os zip
Click to expand...
Click to collapse
1. My device model is mi2s 16g.
2. I have flashed back to the version with unmerged partitions (the version you suggest ) and the cm rom is cm-11-20190626-UNOFFICIAL which you provide in this post.
3.The ui works well, but I couldn't choose the language, and I couldn't go into the next step of initialization. It do not crash or reboot occur.
---------- Post added at 07:49 AM ---------- Previous post was at 07:38 AM ----------
liuxdev said:
and how about if you flash cm rom without sailfish os ? does touch work or not after you boot to cm?
Click to expand...
Click to collapse
It works well on cm rom, and I have initialized the cm before I flash the sailfish os.

丶Nanmu said:
1. My device model is mi2s 16g.
2. I have flashed back to the version with unmerged partitions (the version you suggest ) and the cm rom is cm-11-20190626-UNOFFICIAL which you provide in this post.
3.The ui works well, but I couldn't choose the language, and I couldn't go into the next step of initialization. It do not crash or reboot occur.
---------- Post added at 07:49 AM ---------- Previous post was at 07:38 AM ----------
It works well on cm rom, and I have initialized the cm before I flash the sailfish os.
Click to expand...
Click to collapse
Thank you for you info. It seems nothing wrong in kernel.
Perhaps it's due to different touch screen hw applied on different devices. It's a little hard to debug because both my two devices can not reproduce this issue.
if you can use adb on your pc, you can try to reboot to twrp, mount system and data, then try to find "droid-hal-device.conf" which locates at /etc/, pull it to you pc, check this line in editor: "LIPSTICK_OPTIONS=-plugin evdevtouch:/dev/input/event3". modify "event3" to "event0" or "event1" or "event2". push back to device where it locates, reboot to test then.

liuxdev said:
Thank you for you info. It seems nothing wrong in kernel.
Perhaps it's due to different touch screen hw applied on different devices. It's a little hard to debug because both my two devices can not reproduce this issue.
if you can use adb on your pc, you can try to reboot to twrp, mount system and data, then try to find "droid-hal-device.conf" which locates at /etc/, pull it to you pc, check this line in editor: "LIPSTICK_OPTIONS=-plugin evdevtouch:/dev/input/event3". modify "event3" to "event0" or "event1" or "event2". push back to device where it locates, reboot to test then.
Click to expand...
Click to collapse
Thank you, I will try it soon.

丶Nanmu said:
Thank you, I will try it soon.
Click to expand...
Click to collapse
my mistake. the location may not /etc/ when boot to twrp. should be in /data/.

Great work:good:
Is it possible to install apps (apks) or are there still difficulties?

King-Ossy said:
Great work:good:
Is it possible to install apps (apks) or are there still difficulties?
Click to expand...
Click to collapse
sorry to tell you i can't provide method about installing apks here due to license limitation. you can manage it yourself.

liuxdev said:
my mistake. the location may not /etc/ when boot to twrp. should be in /data/.
Click to expand...
Click to collapse
I have tried it, but it still doesn't work.
I also do something which might help you analyse my problem.
The screenshot is located on /dev/input:
View attachment 4791109
Ha, I have found that my device is event1. There is some cats:
/dev/input # cat /proc/bus/input/devices
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="pmic8xxx_pwrkey"
P: Phys=pmic8xxx_pwrkey/input0
S: Sysfs=/devices/platform/msm_ssbi.0/pm8921-core/pm8xxx-pwrkey/input/input0
U: Uniq=
H: Handlers=event0 cpufreq
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="atmel_mxt_ts"
P: Phys=
S: Sysfs=/devices/i2c-3/3-004b/input/input1
U: Uniq=
H: Handlers=event1 cpufreq
B: PROP=2
B: EV=b
B: KEY=40000800 40 0 0 0
B: ABS=6618000 0
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="apq8064-tabla-snd-card Button Jack"
P: Phys=ALSA
S: Sysfs=/devices/platform/soc-audio.0/sound/card0/input2
U: Uniq=
H: Handlers=event2 cpufreq
B: PROP=0
B: EV=3
B: KEY=fe 4 0 0 0 0 0 0 0
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="apq8064-tabla-snd-card Headset Jack"
P: Phys=ALSA
S: Sysfs=/devices/platform/soc-audio.0/sound/card0/input3
U: Uniq=
H: Handlers=event3
B: PROP=0
B: EV=21
B: SW=1c054
I: Bus=0018 Vendor=0001 Product=0001 Version=0001
N: Name="mhl_rcp"
P: Phys=
S: Sysfs=/devices/i2c-0/0-0064/input/input4
U: Uniq=
H: Handlers=event4 cpufreq
B: PROP=0
B: EV=3
B: KEY=a 0 0 0 0 218300 4102 c0000801 801680 0 100000 10000ffc
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="gpio-keys"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/platform/gpio-keys/input/input5
U: Uniq=
H: Handlers=event5 cpufreq
B: PROP=0
B: EV=3
B: KEY=c0000 0 0 0

丶Nanmu said:
I have tried it, but it still doesn't work.
I also do something which might help you analyse my problem.
The screenshot is located on /dev/input:
View attachment 4791109
Ha, I have found that my device is event1. There is some cats:
/dev/input # cat /proc/bus/input/devices
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="pmic8xxx_pwrkey"
P: Phys=pmic8xxx_pwrkey/input0
S: Sysfs=/devices/platform/msm_ssbi.0/pm8921-core/pm8xxx-pwrkey/input/input0
U: Uniq=
H: Handlers=event0 cpufreq
B: PROP=0
B: EV=3
B: KEY=100000 0 0 0
I: Bus=0018 Vendor=0000 Product=0000 Version=0000
N: Name="atmel_mxt_ts"
P: Phys=
S: Sysfs=/devices/i2c-3/3-004b/input/input1
U: Uniq=
H: Handlers=event1 cpufreq
B: PROP=2
B: EV=b
B: KEY=40000800 40 0 0 0
B: ABS=6618000 0
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="apq8064-tabla-snd-card Button Jack"
P: Phys=ALSA
S: Sysfs=/devices/platform/soc-audio.0/sound/card0/input2
U: Uniq=
H: Handlers=event2 cpufreq
B: PROP=0
B: EV=3
B: KEY=fe 4 0 0 0 0 0 0 0
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="apq8064-tabla-snd-card Headset Jack"
P: Phys=ALSA
S: Sysfs=/devices/platform/soc-audio.0/sound/card0/input3
U: Uniq=
H: Handlers=event3
B: PROP=0
B: EV=21
B: SW=1c054
I: Bus=0018 Vendor=0001 Product=0001 Version=0001
N: Name="mhl_rcp"
P: Phys=
S: Sysfs=/devices/i2c-0/0-0064/input/input4
U: Uniq=
H: Handlers=event4 cpufreq
B: PROP=0
B: EV=3
B: KEY=a 0 0 0 0 218300 4102 c0000801 801680 0 100000 10000ffc
I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="gpio-keys"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/platform/gpio-keys/input/input5
U: Uniq=
H: Handlers=event5 cpufreq
B: PROP=0
B: EV=3
B: KEY=c0000 0 0 0
Click to expand...
Click to collapse
The bug is still there even if you modified it to "event1", right?

liuxdev said:
The bug is still there even if you modified it to "event1", right?
Click to expand...
Click to collapse
Yes, my touch screen still doesn't work:crying:. Do you need any log? I think I can do some thing to help you.

丶Nanmu said:
Yes, my touch screen still doesn't work:crying:. Do you need any log? I think I can do some thing to help you.
Click to expand...
Click to collapse
Then twrp input devices may different from that in sailfish. Could you try more value like event4/event5/event6, and show how you did that in cmd line?

liuxdev said:
Then twrp input devices may different from that in sailfish. Could you try more value like event4/event5/event6, and show how you did that in cmd line?
Click to expand...
Click to collapse
Sorry, I have found the problem, my device is event2, it works well! Thank you!

丶Nanmu said:
Sorry, I have found the problem, my device is event2, it works well! Thank you!
Click to expand...
Click to collapse
glad hear that. now my issue is how to get a device same as yours so that i can try to fix it with general solution.
btw, you said "a lot of" people have this issue but i can't see in this thread. not sure if event2 is correct node for all devices

I got another issue here. While learning a basics tutorial, it always back to beginning. Is there any way to skip or fix that?

ekaka said:
I got another issue here. While learning a basics tutorial, it always back to beginning. Is there any way to skip or fix that?
Click to expand...
Click to collapse
Do you mean it back to beginning even if you press "continue"?
well, you can just skip that by tapping on the each corner of the screen clokwise, while starting from left-top corner.

liuxdev said:
glad hear that. now my issue is how to get a device same as yours so that i can try to fix it with general solution.
btw, you said "a lot of" people have this issue but i can't see in this thread. not sure if event2 is correct node for all devices
Click to expand...
Click to collapse
Yes, they are in MIUI form, some of them can flash your rom normally, and others can flash your rom normally by change it to "event2"!

Related

[4.5.2013][UTIL][Win]Android Ultimate Toolbox Pro - The Ultimate Android Utility

{
"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 present you Android Ultimate Toolbox Pro, the ultimate Android utility! As the name says, it's a toolbox-like program that offers many features that make the usually not-so-easy tasks easier.
Caution! This program is not foolproof! Do not try to outsmart it by playing tricks, because you may result with an expensive brick in the worst case!
Requirements
Microsoft .NET Framework 4 (Client Profile is also needed)
Java JDK and JRE and Android SDK
Key features
Update.zip creator
Update.zip signer
Flash kernels
Flash recovery images
Flash upate.zip
Flash system images
Flash data images
Flash splash images
Install APKs (system and user)
Uninstall APKs (system and user)
Unpack APKs
Repack APKs
Sign APKs
Deodex APKs, Jars (both computer and device)
Zip-align APKs
Check MD5 sums
File manager
Root checker
Root your device
Unroot device
Logger (logcat and dmesg)
Rebooter (normal reboot, reboot in recovery, reboot in bootloader, reboot from fastboot)
Backup manager
Backup/restore apps NEW!!
Device ID configurator (device name, build number, Android version)
Unlock bootloader
Lock bootloader
Wipe (system, data, cache, boot, recovery)
And much more to come!
Note: make sure to read the help topics before using Android Ultimate Toolbox Pro.
Download
(If you don't see the download button, click here)
(If you don't see the changelog button, click here)
Latest version: 1.2.0.0
Credits
fdespotovski - icon
RegawMod - AndroidLib library
Google - aapt and zipalign binaries
Ryszard Wiśniewski (brut.alll) and Connor Tumbleson - apktool
Creators of smali and baksmali - smali and baksmali binaries
Martin Gagne - loading circle
cdesai - help
Rebellos - help
Zoran Despotovski - tester
Special thanks goes to my supporters bigrammy, imilleson and DeepUnknown. Thanks guys, you're awesome!
Error reporting
If you want to report a misbehavior of Android Ultimate Toolbox Pro, just fill out this form and I'll take a look at it and fix it as soon as possible.
Before posting a question in this thread:
-please search if the question is already posted and answered
-read all of the help topics
trust me, you'll save both yours and mine time.
Feedback is always appreciated.

What's new?
Code:
v1.0.0.0 [14.09.2012]
Initial release
v1.0.1.0 [24.10.2012]
-Bug fixes
-Performance improvements
-The program doesn’t need the Visual Basic Power Pack anymore
-New feature: Restart Android services (accessible in Settings)
-New setting: enable/disable grid in file manager
v1.0.2.0 [21.11.2012]
-Bug fixes
-Added ‘Check all’ and ‘Uncheck all’ buttons in the Backup configurator window
-New in Update Creator: the text dialogs for file and directory locations and permissions suggest common values
-New in Update Creator: the text dialog for the file location has a check box to set the same location for the next files
-Added buttons for the video review and changelog in the main menu
-Small under-the-hood improvements
v1.1.0.0 [22.01.2013]
-Added ‘Unpack APKs’ feature
-Added ‘Repack APKs’ feature
-Added ‘Sign APKs’ feature
-Added ‘Deodex APKs / Jars’ feature
-Added ‘Zip-align APKs’ feature
-Reorganized the main window
-Added binaries: apktool, smali, baksmali, aapt, zipalign, signapk
-New settings: delete unsigned APKs after signing, sign APKs after repacking, ask for framework dependencies, custom framework location (needed for deodexing), use custom framework for unpacking APKs, zip-align APKs after deodexing
-Usability and performance improvements, bug fixes
-...
v1.1.1.0 [09.02.2013]
-Fixed bug related to unpacking APKs
-Improved the APK uninstallation feature, now you can uninstall more than one APKs at once
-New feature: Update manager, displays latest version and changelog when an update is available
-Updated AndroidLib library to 1.5.1.0
-Updated apktool binary to 1.5.2
-Performance improvements
v1.1.1.1 [09.03.2013]
-Reverted AndroidLib library to 1.3.0.0 because of broken features with version 1.5.1.0 (fixed Update.zip creator and Backup/Restore features)
v1.2.0.0 [4.5.2013]
-Added features: backup and restore apps
-Added 'Size' column to the 'Update entries' list in the Update creator
-Bug fixes

Reserved...

nice tool may come in handy, will this work on non nexus devices because when i installed on bottom left corner it says only for nexus devices, i have an lg device

Very good , thank you very much

hsingh1993 said:
nice tool may come in handy, will this work on non nexus devices because when i installed on bottom left corner it says only for nexus devices, i have an lg device
Click to expand...
Click to collapse
Yes, it will. Only the functions for bootloader unlocking and locking are for Nexus devices, but the others are universal.
kinghunki said:
Very good , thank you very much
Click to expand...
Click to collapse
I'm glad you like it.
Sent from my HTC EVO 3D X515m using xda app-developers app

Will this work for htc devices which doesn't have s- off?
Sent from my HTC One X using xda premium

timlambo said:
Will this work for htc devices which doesn't have s- off?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes, but not all features will work. For instance, you won't be able to flash system, data, kernel, recovery and splash images, which require a bootloader that supports fastboot commands (which indeed is a S-OFF bootloader). If you are on unlocked S-ON bootloader (HTC Unlock), then they should also work.

despotovski01 said:
Yes, it will. Only the functions for bootloader unlocking and locking are for Nexus devices, but the others are universal.
I'm glad you like it.
Sent from my HTC EVO 3D X515m using xda app-developers app
Click to expand...
Click to collapse
thanks great tools now i can remove system app whenever i want and can customize my rom a little.

I recently tried this app, and seems that has very useful functions, thanks.
I have a problem with backup future though. My device(U8800) has a difference about recovery and boot images. Has a seperate fat32 partition which mounted as .cust_backup, in which are the recovery.img, boot.img and some other system files.
So, the app cannot backup recovery and boot. Only backup system and data. The approach used on CMW recovery for my device, is to just copy and compress all this partition which is less that 200MB.
Can you implement support for this in the app?
Here is the mounts of my device:
Code:
[email protected]:/ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 rw,relatime,user_xattr,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p13 /data ext4 rw,relatime,user_xattr,barrier=1,nomblk_io_subm
it,data=ordered 0 0
/dev/block/mmcblk0p6 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,no
mblk_io_submit,data=ordered 0 0
/dev/block/mmcblk0p14 /HWUserData vfat rw,relatime,uid=1000,gid=1015,fmask=0002,
dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,u
tf8,errors=remount-ro 0 0
/dev/block/mmcblk0p1 /.cust_backup vfat ro,relatime,fmask=0000,dmask=0000,allow_
utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
0 0
/dev/block/vold/179:14 /mnt/sdcard1 vfat rw,nosuid,nodev,noexec,relatime,uid=100
0,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso88
59-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/foursqwifi.aithanasakis-1 vfat ro,dirsync,nosuid,nodev
,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shor
tname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.mobappbox.pyramidrun-1 vfat ro,dirsync,nosuid,node
v,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,sho
rtname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.svox.classic.langpack.ell_grc_fem-1 vfat ro,dirsyn
c,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/taxy.kwd-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1
000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf
8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/gr.digitalblast.drivesafe-1 vfat ro,dirsync,nosuid,nod
ev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,sh
ortname=mixed,utf8,errors=remount-ro 0 0
thanks in advance.

despotovski01 said:
After months of hard work, I present you the ultimate Android utility, Android Ultimate Toolbox Pro! As the name says, it's a toolbox-like program that offers many features that make the usually not-so-easy tasks easier.
Caution! This program is not foolproof! Don't try to outsmart it by playing tricks, or you may result with an expensive brick in the worst case!
Requirements
Microsoft .NET Framework 4 (Client Profile is also needed)
Java JDK and JRE and Android SDK (for signing update.zip files)
Visual Basic Power Packs 10 - download here
Key features
Update.zip creator
Update.zip signer
Flash kernels
Flash recovery images
Flash upate.zip
Flash system images
Flash data images
Flash splash images
Install APKs (system and user)
Uninstall APKs (system and user)
Check MD5 sums
File manager
Root checker
Root your device
Unroot device
Logger (logcat and dmesg)
Rebooter (normal reboot, reboot in recovery, reboot in bootloader, reboot from fastboot)
Backup manager
Device ID configurator (device name, build number, Android version)
Unlock bootloader
Lock bootloader
Wipe (system, data, cache, boot, recovery)
And much more to come!
Note: make sure to read the help topics before using Android Ultimate Toolbox Pro.
Download
(If you don't see the download button, click here)
Latest version: 1.0.0.0
Credits
fdespotovski - icon
RegawMod - AndroidLib library
cdesai - help
Rebellos - help
Zoran Despotovski - tester
Error reporting
If you want to report a misbehavior of Android Ultimate Toolbox Pro, just fill out this form and I'll take a look at it and fix it as soon as possible.
Before posting a question in this thread:
-please search if the question is already posted and answered
-read all of the help topics
trust me, you'll save both yours and mine time.
Feedback is always appreciated.
Video coming soon!
Click to expand...
Click to collapse
excellent work !

dancer_69 said:
I recently tried this app, and seems that has very useful functions, thanks.
I have a problem with backup future though. My device(U8800) has a difference about recovery and boot images. Has a seperate fat32 partition which mounted as .cust_backup, in which are the recovery.img, boot.img and some other system files.
So, the app cannot backup recovery and boot. Only backup system and data. The approach used on CMW recovery for my device, is to just copy and compress all this partition which is less that 200MB.
Can you implement support for this in the app?
Here is the mounts of my device:
thanks in advance.
Click to expand...
Click to collapse
Hi, mate,
First off, thanks for using my new program. I'm looking forward to adding support for your devce, but first I need to know how do you flash and backup recovery and boot images? Do you just flash that combined partition, or you flash the boot and recovery images seperately?
Sent from my HTC EVO 3D X515m using xda app-developers app

The backup is, as I mentioned, the folder Image(which contains the system files) from .cust_backup partition. The device has a special pink screen in which the pc loads this partition and I just replace the recovery.img with the custom one. Same and with boot.img can happens, but usually, for custom roms, is contained on update.zip.

dancer_69 said:
The backup is, as I mentioned, the folder Image(which contains the system files) from .cust_backup partition. The device has a special pink screen in which the pc loads this partition and I just replace the recovery.img with the custom one. Same and with boot.img can happens, but usually, for custom roms, is contained on update.zip.
Click to expand...
Click to collapse
OK, I will see what I can do with that.

So, what do you think about this program? Is it OK? Should I change anything?

Excellent will take a look as soon as my pc is operational thank you

Is it possible to root Galaxy Nexus running on 4.1 JB with FIDO network???

Cool to see more and more people developing using my library AndroidLib

I was wondering when using this app of yours, what state should the phone/tablet/device be in? ie: recovery, phone on but screen off, phone on and screen on etc etc. And I was wondering also how you are able to make it so that the app can root all sorts of different devices.

ashqmallik said:
Is it possible to root Galaxy Nexus running on 4.1 JB with FIDO network???
Click to expand...
Click to collapse
Theoretically it should be a cinch to root the GNex via this utility as long as you have set up your Android SDK properly. Your bootloader should be unlocked (If not use Feature #20 to do so). Subsequent rooting and then pushing a custom recovery via adb should be very simple.
DISCLAIMER: I have not used this utility to Unlock and Root my GNex. I am only going by the universal methods and assumptions regarding recent Samsung devices. I did use the method given in my signature.

kitchen rom

I'm creating a cooked rom based on the stock rom ita LT9 4.1.2, you can change the battery in the status bar without Xposed? I would include the circular battery with percentage inside. decompiling an apk? which one?

stefano_te said:
I'm creating a cooked rom based on the stock rom ita LT9 4.1.2, you can change the battery in the status bar without Xposed? I would include the circular battery with percentage inside. decompiling an apk? which one?
Click to expand...
Click to collapse
I think it's enough that you throw it into the SystemUI.apk(have a look inside that apk, if it's not there then it is in secframework.apk) (/res/.../XHDPI). Open the apk in winrar (you might have to rename it from .apk to .zip) and drag and drop the new files. Decompiling isn't necessary for this sort of thing.
Also, check this out:
http://forum.xda-developers.com/showthread.php?t=1918500
I did this a long time ago so some of what I just said might be wrong, if you need more help then just say so.

I would like to use as a basis the stock rom 4.1.2 : N7000XXLT9_N7000ITVLT3_ITV.zip
I used the kitchen to create workfolder following all the steps suggested by the program , I found the following problems:
1 ) during the procedure appeared to me the following warning :
Warning : A valid boot.img is not found . You have the option to add a
' fake ' boot.img So THAT the features of the kitchen can still
function normally.
This boot.img will be automatically removed from your ROM 's
ZIP file When Is It built .
Add boot.img (y / n)? (default: y) "
is this normal? how to solve ?
2 ) Working folder information ( v)
Android OS version: 4.1.2
Device: GT- N7000
Model: GT- N7000
ROM Name : JZO54K.N7000XXLT9
CSC version: It 's normal that there is nothing written here ?
Rooted ( Superuser app + su) : NO
Rooted ( unsecured boot.img ) : UNKNOWN how I fix this ?
BusyBox installed : NO
BusyBox run-parts support: UNKNOWN UNKNOWN how I fix this ?
Apps2SD (Apps to EXT) enabled: NO
/ data / app enabled: NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support: NO
/ system / framework is deodexed : NO
/ system / app is deodexed : NO
modem.bin found: YES
ROM will wipe all data : NO
3) throughout the META-INF folder there are only 2 files: update-script; update-script.bak
4) scripts / get_api_level: line 18: more: command not found
5) I checked the update-script and there are 3 warning in the report:
7/101: copy_dir PACKAGEystem SYSTEM:
8/101: format PRELOAD:
>> WARNING: Partition not recognized
9/101: copy_dir PACKAGEreload PRELOAD:
>> WARNING: PRELOAD: not found in working folder
10/101: symlink dumpstate SYSTEM:bin/dumpcrash
11/101: symlink toolbox SYSTEM:bin/cat
82/101: set_perm_recursive 0 2000 0755 0755 SYSTEM:bin
83/101: run_program PACKAGE:create_preload_symlinks
>> WARNING: create_preload_symlinks not found in working folder
84/101: set_perm 0 3003 06755 SYSTEM:bin/ip
How do I resolve this? I tried a lot of on-line but have not found anything. My goal is to make me a custom rom from the last stock (LT9) ... what should I do?

Check my old tutorial I used myself when cooking Custom Roms for the N7000 with the kitchen. Following the steps should avoid most problems.

ThaiDai said:
Check my old tutorial I used myself when cooking Custom Roms for the N7000 with the kitchen. Following the steps should avoid most problems.
Click to expand...
Click to collapse
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue?
Please wait ...
scripts/choose_rom: line 110: more: command not found
Enter selection number (default=1, cancel=0, r=refresh):
is a problem? I can go on with 1 (default)?

stefano_te said:
CREATE WORKING FOLDER FOR ROM
==============================
Ensure there is at least one ROM under the 'original_update' folder!
Select an option:
s - Show supported formats
x - Abort, don't create working folder
Or press Enter to continue?
Please wait ...
scripts/choose_rom: line 110: more: command not found
Enter selection number (default=1, cancel=0, r=refresh):
is a problem? I can go on with 1 (default)?
Click to expand...
Click to collapse
Sorry, but only repeating the problems you actually have won't solve anything because it isn't really clear what you did before.
The error here seems to be a hint that your cygwin installation isn't correct.
So please try to follow the steps in my tutorial exactly. Start from scratch.

ThaiDai said:
Sorry, but only repeating the problems you actually have won't solve anything because it isn't really clear what you did before.
The error here seems to be a hint that your cygwin installation isn't correct.
So please try to follow the steps in my tutorial exactly. Start from scratch.
Click to expand...
Click to collapse
It works. I have re-installed windows ...
can you tell me how to add new info in device info? (rom name, rom maker, release date, build version ...)

stefano_te said:
It works. I have re-installed windows ...
can you tell me how to add new info in device info? (rom name, rom maker, release date, build version ...)
Click to expand...
Click to collapse
No. Because you do this partly when using the kitchen step by step. Or when changing your updater-script.
The kitchen is a great help and simplifies cooking a rom - but it still is a little bit more complicated than heating baby food in the microwave. And if you really want your "custom" rom you should start to learn what happens in each step. And this can't be done by revealing everything...

[RECOVERY][cancro] TWRP v3.0.0-0 Touch Recovery

{
"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 Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Changelog
2016/03/09
- upstream changes
- testing decryption fix
2016/02/08
- version 3.0.0-0 official builds available
2016/02/07
- version 3.0.0-0
2015/06/21
- version 2.8.7.0
2015/06/14
sync with upstream
new theme preview
[*]2015/03/28
FIX Aroma File Manager and Aroma Installer compatibility
[*]2015/03/26
new version 2.8.6.0 released
upstream changes
Note: Old themes might not work properly because of changes to how theme layout works.
[*]2015/02/26
Official Builds are ready
[*]2015/02/25
upstream changes
enabled crypto support
last build before official TWRP support
[*]2015/02/15
fixed /sdcard mount issue
[*]2015/02/13
v2.8.5.0
upstream changes
Note: internal memory can be accessed from /data/media/0
[*]2015/01/29
Removed Crypto support (was causing problem with MIUI Roms updater_binary)
upstream changes
-- option to cancel backup operation
[*]2015/01/27
USB-OTG Fixed
Added Crypto support.
changed backup path to include MI_3W instead of <device-id>
[*]2015/01/26
initial build
Click to expand...
Click to collapse
BUGS
Slow speed of flashing compare to older versions not in official builds
Source
Code:
TWRP source : [URL="https://github.com/kundancool/android_bootable_recovery"]GitHub[/URL]
Download
Download from
Official TWRP Page
Download :
twrp-3.0.0-0-cancro-20160309.zip (SHA1 - c7d06012141d0cab24b0a47a44f072b47f3e5b01)
Download : Mediafire
twrp-3.0.0-0-cancro-20160309.img (SHA1 - deaa2fe66e30aaf5379ea41513dc8b043d1f79f3)
Download : Mediafire
Build Archive
Mirror :
twrp-3.0.0-0-cancro.zip (MD5 - b035ec78655eac89705ec861536ea17d)
Download : Mediafire
twrp-3.0.0-0-cancro.img (MD5 - 18132373d2630e5e82d15415211e4504)
Download : Mediafire
twrp-3.0.0-0-cancro-07022016.zip (MD5 - 51d6fd99de337b504921a26ce5487e04)
Download : Mediafire
twrp-3.0.0-0-cancro-07022016.img (MD5 - d4c0a39f641ebfd352e5388336b514cd)
Download : Mediafire
** Theme Preview build **
TWRP-v2.8.7.0-cancro-preview-20150621.zip (MD5 - fc7f6dcec428e57a79e8b3f2e329bce9)
Download : Mediafire
TWRP-v2.8.7.0-cancro-20150621.zip (MD5 - 361a870381a04b8173b53ba7cc689d77)
Download : Mediafire
TWRP-v2.8.7.0-cancro-20150621.img (MD5 - 76c0d23e9eea75c6669420cf7a7f4569)
Download : Mediafire
Mirror :
openrecovery-twrp-2.8.5.0-cancro.zip (MD5 - 8726197381ebb2cc182574f28b550635)
Download : Mediafire
openrecovery-twrp-2.8.5.0-cancro.img (MD5 - ee2b5b10a0fc2bd03eda7af1738b522a)
Download : Mediafire
TWRP-v2.8.6.0-cancro-20150614.zip (MD5 - e496e485673c854cffb44b9aac7fbce2)
Download : Mediafire
TWRP-v2.8.6.0-cancro-20150614.img (MD5 - 4f9b6ede9cf940717f84a88220f3d614)
Download : Mediafire
TWRP-v2.8.6.0-cancro-20150328.zip (MD5 - 66d13719c04cb39e046b1270779911b6)
Download : Mediafire
TWRP-v2.8.6.0-cancro-20150328.img (MD5 - 24e1e7f396a1960b5dca831dc17af919)
Download : Mediafire
TWRP-v2.8.6.0-cancro-20150326.zip (MD5 - 04f08398f7a014235a351a254e78eccc)
Download : Mediafire
TWRP-v2.8.6.0-cancro-20150326.img (MD5 - 3f410e34b516ab9aff156c85ee00b6ea)
Download : Mediafire
TWRP-v2.8.5.0-cancro-20150225.zip (MD5 - 33d37bfd5d0ddbe210fd8f07900da78e)
Download : Mediafire
TWRP-v2.8.5.0-cancro-20150225.img (MD5 - 3c9cd01eaf313f160af1174c7a33f0cd)
Download : Mediafire
TWRP-v2.8.5.0-cancro-20150215.zip (MD5 - 5f29a1279edb9f04d3598ad100c90e07)
Download : Mediafire
TWRP-v2.8.5.0-cancro-20150215.img (MD5 - 83814b472c098ba68e6c2f5a28428c42)
Download : Mediafire
TWRP-v2.8.5.0-cancro-20150213.zip (MD5 - f57ae8613cf4844d55820133b76d25e7)
Download : Mediafire
TWRP-v2.8.5.0-cancro-20150213.img (MD5 - 55cf7e9d32289e74e5ae47a74896460f)
Download : Mediafire
TWRP-v2.8.4.0-cancro-20150129.zip (MD5 - c7c7445d07114a9a08ee52633cb52201)
Download : Mediafire
TWRP-v2.8.4.0-cancro-20150129.img (MD5 - 6475bdd695224ca49157974654a710bd)
Download : Mediafire
TWRP-v2.8.4.0-cancro-20150127.zip (MD5 - bd4c15799a9da7c4647e784d3cc12edf)
Download : Mediafire
TWRP-v2.8.4.0-cancro-20150127.img (MD5 - abe8604df0f333268122c40c23f92fe7)
Download : Mediafire
TWRP-v2.8.4.0-cancro-20150126.zip (MD5 - a40da155f08d5bc07a3643ab042d0cd4)
Download : Mediafire
TWRP-v2.8.4.0-cancro-20150126.img (MD5 - bf792728c17dcf16a963bec35e69c942)
Download : Mediafire
Click to expand...
Click to collapse
Screenshot
FAQ
Q. Does it support Dual Boot
A. No, it does not support Dual Boot.
Q. Where can I find themes for this
A. Check this thread or download any one from this list of 1080p themes
Q. How to apply themes
A. copy downloaded theme.zip file to /sdcard/TWRP/theme/ui.zip (rename theme.zip to ui.zip)
Q. I am getting can't execute updater_binary
A. unmount /system and try flashing ROM zip again.
Click to expand...
Click to collapse

thanks

Thanks!! I love you dev! (No homo)

pretty confused, is this the same twrp recovery made by juliuss in miui.es forum?
if not, is it compatible with both system1 and system2, or just system1?
thanks btw, we really needed this!!!

moly82 said:
pretty confused, is this the same twrp recovery made by juliuss in miui.es forum?
if not, is it compatible with both system1 and system2, or just system1?
thanks btw, we really needed this!!!
Click to expand...
Click to collapse
no it is not the same, I have not made it compatible with both systems as I use single system only.

OTG
does this support USB OTG?
recommended instalationl via CWM or updater app?
thanks.

dunno about otg. flashed via cwm, no problems at all

tongueinamow said:
does this support USB OTG?
recommended instalationl via CWM or updater app?
thanks.
Click to expand...
Click to collapse
I don't have OTG drive to test will you test and report back?
I was thinking of changing backup path from device id to "MI_3W" any opinion about this change?

its awsome dev.. always wanted twrp on my mi3

Wow thanks a lot!
I really hope you'll support dualboot in future versions =)
I may test it soon on my Mi4.

kundancool said:
I don't have OTG drive to test will you test and report back?
I was thinking of changing backup path from device id to "MI_3W" any opinion about this change?
Click to expand...
Click to collapse
i tested it, otg is not working... btw good work..

kundancool said:
I don't have OTG drive to test will you test and report back?
I was thinking of changing backup path from device id to "MI_3W" any opinion about this change?
Click to expand...
Click to collapse
yes mi3w is better than device id for me too

New builds are up and fixed USB-OTG (Tested!)

kundancool said:
New builds are up and fixed USB-OTG (Tested!)
Click to expand...
Click to collapse
TDB can wait (I imagine it will be difficult to implement it) but can you at least work on adding support for system2? That would convince me to switch from CWM r11 by furniel and donbot.
Not saying I'm NOT gonna try this out...downloading now... :good:

kundancool said:
New builds are up and fixed USB-OTG (Tested!)
Click to expand...
Click to collapse
finished already number of thanks.. so thank you!
yes support for system2 would be great, but I can leave also with system1 only actually. for sure still better than using cwm for me... but it could be implemented pretty easiliy or it would be very hard/impossible?
also one final question: does format /system work without problems? because in the twrp version from the miui.es forum it make troubles it seems, so I am a little worried and would like a confirmation if you tested it before to try here (don't feel like using fastboot now to fix a eventual big mess... ) thanks again!

moly82 said:
finished already number of thanks.. so thank you!
yes support for system2 would be great, but I can leave also with system1 only actually. for sure still better than using cwm for me... but it could be implemented pretty easiliy or it would be very hard/impossible?
also one final question: does format /system work without problems? because in the twrp version from the miui.es forum it make troubles it seems, so I am a little worried and would like a confirmation if you tested it before to try here (don't feel like using fastboot now to fix a eventual big mess... ) thanks again!
Click to expand...
Click to collapse
well I have added option to mount both systems but formatting and flashing is not yet done
I have tested backup and restore I hope that will do the job

kundancool said:
well I have added option to mount both systems but formatting and flashing is not yet done
I have tested backup and restore I hope that will do the job
Click to expand...
Click to collapse
Wait, so as of now (if you released a new build in current state) we could use both systems?
Flashing to system1, taking a backup, then restoring to system2?

The Dork Knight Rises said:
Wait, so as of now (if you released a new build in current state) we could use both systems?
Flashing to system1, taking a backup, then restoring to system2?
Click to expand...
Click to collapse
No, as I said right now you can only mount and browse system 2 in TWRP Dual Boot is not yet implemented.

kundancool said:
No, as I said right now you can only mount and browse system 2 in TWRP Dual Boot is not yet implemented.
Click to expand...
Click to collapse
Ok, so backup and restore on system2 NOT working?
I thought it was, and we could restore a backup to system2 (as we can't directly flash) and boot into it using the DualBootSwitch app...:silly:

The Dork Knight Rises said:
Ok, so backup and restore on system2 NOT working?
I thought it was, and we could restore a backup to system2 (as we can't directly flash) and boot into it using the DualBootSwitch app...:silly:
Click to expand...
Click to collapse
You would still need a seperate data partition for that which requires complete true dual boot support..

[WORKAROUND] Bootloops due leaking handles with Xposed in Lollipop

Fix found and released:
http://forum.xda-developers.com/showthread.php?p=60454547
Downloads & instructions: http://forum.xda-developers.com/showthread.php?t=3034811
Discussion & Q&A:http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118
I asked moderator to close this thread as issue was fixed by releasing new version of Xposed framework. Please send your further questions and post to respective thread.
This thread is about workaround found for bootloops of Xposed in XPERIA family Lollipop. Because of development progress, I have decided to remove historical development, you can see it here:
LATEST VERSION will be always posted at the END of this post
PLEASE READ INSTRUCTIONS .... The attachment IS NOT flashable!!! For flashables see EDIT 5 and bellow...
I hope I can present some good news for users with locked bootloaders who are getting bootloops with Xposed and Lollipop.
This is still continuous WIP. Know what you do, this is a development thread.
For time being, most complete solution by my opinion was made by @mionica, see EDIT 6 and hist post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123? and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
As you may already know, we have find out, that some undetected error is causing system to bootloop, if too many applications are installed.
Exact numbers are varying between different ROMs and devices, generally the maximum number of apps is about 320-330.
Debloating (uninstalling unnecessary apps) helps, but remains limiting and for many frustrating. After a research, we have found out,
that there is probably a bug, that is causing many files being left open when booting Lollipop with Xposed.
Users on unlocked bootloader may modify certain kernel parameters to raise number of open files. This can not be done on Locked Bootloader.
After some research and hours of experiments, I found a way, how to change the filelimit for Zygote and subsequent processes. Therefore every child of zygote (hence every app etc.) will inherit raised open files limit from 1024 to 4096.
This change should work on all 5.0 compatible system, not only XPERIAs, however I only tested it on Z3 D6603 fw 690. But the modification
is done on Linux system level, therefore it should teoretically work just everywhere... It should work also on Locked bootloaders as well.
The principle is easy, however implementation was a tricky, because of lack of native linux utils support on Android and fact that we can not
easily modify booting behaviour. But gladly enough we have XZDualRecovery (gret thanks @[NUT])....
XZDualRecovery enables to call init scripts on startup. I have created a startup script that waits for zygote process to come up, and calls
external program that changes open file limits for that process. This external program is compiled by me from source provided by http://lzone.de/cheat-sheet/ulimit
Prerequisities: Functional XZDualRecovery or other form of init.d support.
Installation:
Extract downloaded ZIP file, it contains:
flimit-binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
remount /system rw (mount -o remount,rw /system)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
test run installation:
Code:
su
/data/flimit/flimit $(pgrep zygote)
output should be:
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=1024; hard=4096
New limits: soft=4096; hard=4096
If not, check permissions etc.
Check script by running:
Code:
su
sh /system/etc/init.d/01_flimit
it should now give output (if you succesfully ran /data/flimit/flimit....):
Code:
[email protected]:/data # /data/flimit/flimit $(pgrep zygote)
Previous limits: soft=4096; hard=4096
New limits: soft=4096; hard=4096
reboot
Thats all. Now you can install and update lot more applications. Now I have about 455 packages reported by pm list packages and no bootloop.
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
EDIT:Please let me know, if you had to modify the script or instructions to work on your device, so I can perhaps make better or more universal version. Thank you guys.
EDIT 2:While this workaround makes it possible to run Xposed on untouched vanilla Stock ROM, you may still consider debloating it, as debloating will make run your device more smoothly and saves battery. Guys who made debloating scripts made significant efforts in identifying which apps can be safely removed without harming any significant functionality.
EDIT 3:The ZIP is NOT flashable, follow instructions ^^^^ --- buddy @McBane87 is developing flashable version.
EDIT 4:Buddy @nurps found a bug causing Opera browser to quit upon starting. @mionica proposed lowering softlimits for open files to 2048 from 4096 in first version of script. Version 1.1 is released.
EDIT 5:Buddy @McBane87 created customized flashable version of this workaround, so you can flash it from recovery if you struggle with bootloops, dont like to wait fro 300apps to optimize after Dalvik wipe and mess with adb/terminal..
http://forum.xda-developers.com/showthread.php?p=60276913
EDIT 6:Buddy @mionica published another flashable zip. It is complete installer for the workaround, so far most sofisticated workaround from system point of view. The uninstaller completely removes Xposed if you are too tired of it and forgot to make backup Files are bellow, for instructions etc. check it out on http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123 and for latest development at http://forum.xda-developers.com/showpost.php?p=60333600&postcount=285
Changelog:
v1: Initial release
v1.1: Changed limits to 2048 from 4096 as high limits caused Opera Webbrowsers to crash
v2.0 Reference script - for production please flash @mionica version of flashable, my script is published for educational purposes. added mionicas mod to detect only changed limits and subsequently remove only those that are child of zygote
***************************************
I would like to thank mainly to @[NUT] and to guys who made significant effort with debloating, made other discoveries or were an inspiration
for me, including but not limited to @serajr @moly82 @AndroPlus (for his work on file limits in kernel) @redincali and of course to @rovo89
for his Xposed framework. My apologies if I forgot someone, PM me, its 2 o'clock in morning
or in this post http://forum.xda-developers.com/showpost.php?p=60349914&postcount=354
While I have developed initial version (see history), other guys (mainly @mionica and @McBane87) greatly enhanced and redeveloped whole thing.
Current development version and downloadable files you can always find in @mionica post http://forum.xda-developers.com/showpost.php?p=60298690&postcount=123
@mionica managed to analyze boot process on both ROMs with and without Xposed and came to conclusion that leaks are caused by Xposed process leaking open file handles, see here http://forum.xda-developers.com/showpost.php?p=60373854&postcount=417
There is a current version of the workaround fix (see above), that seems to be the last possible, before Xposed will be released with patch addressing that issue. Good news is that thanks to @mionica precise analysis, @rovo89 - developer of Xposed is already aware of the problem nad it´s cause.
Recommended installation steps:
by @mionica
Anybody who is still having any kind of issues, for whatever reason, please do the following:
get into TWRP;
install, in this order, without rebooting:
xposed-uninstall-v1.1.zip
If you don't have an sd card, you'll need to reboot once after the uninstall .zip, boot the system normally, then get back in the recovery and install the other 3. This only applies to people who don't use an SD card
xzdr-busybox-enable-v1.0.zip
xposed-sdk21-arm-date.zip
xposed-leakplug-v1.2.zip
copy the logs to the PC, over USB:
uninstall_xposed.log
install_busybox.log
install_leakplug.log
each of the 3 zip's will tell you where it saved the log (it's usually the external sdcard)
reboot to system
Thanks in advance for not asking any questions about whether you have to do any of these steps; yes, you have to.
Click to expand...
Click to collapse
If you follow other instructions than provided by @mionica please get then support from someone else than him.
The basic idea behind is that Xposed bootloops because of it exhausted resources available due to probably internal bug. The workaround basically provides higher limits for open files during boot and restores previous limits after device has booted. The latest flashable installer is very advanced and automates the installation, including necessary checks for proper XZDR configuration, busybox etc.
When you experience bootloops after installing Xposed, or you had Xposed working and it started to bootloop after you have installed new app or upgraded a system app, simply reboot to recovery and flash the zip. No need to wipe anything.
When installing new, I recommend flashing this zip first, then install Xposed usual way (flash, wipe, reboot, install Xposed apk, install modules).
Be aware that while the workaround works for about 80% of cases, there are people who have lots of applications or heavily modified system, experiencing random reboots. Cause is under investiogation, but most probably is in Xposed itself.

Excellent work friend @ondrejvaroscak. Congrats! Awesome

Was waiting a long time for this! Thanks man! working perfectly.

Working perfectly on D6603, thanks

I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button

Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?

Thanks Bro , Very Nice !!
Perfect Work !!

Z1, C6903
Thank you for this great solution, works on Z1.

NetSkill said:
I am gonig to try this asap! Awesome job!
One more thing, if i understand right, now we can install as many apps as we want or the limit is just higher but still there?
Can we now use regular reboot button from power menu withouth getting bootloop?
--Guys lets go ahead and rape the thanks button
Click to expand...
Click to collapse
Unless I will be blessed with some debugging skills, I have no clue... I think limit is just much higher. Once you reach limit you can simply edit script and change two numbers...
Yes, now regular reboot works.
Sent from my D6603 using XDA Free mobile app

norti said:
Thank you @ondrejvaroscak for this solution!
@rovo89 any chance this could be integrated in the xposed installer?
Click to expand...
Click to collapse
I think it will take time, because first @rovo89 would probably want to investigate, how much is it a bug, a constellation of coincidences and so on. I am not sure, if the same bootloops appear only on XPERIAs or it is a phenomenon on other brands as well... And given the fact, that big number of Samsungs can not run Xposed at all, maybe he will try to solve that Samsung puzzle as priority. But that is only guess..

Working on fully setup 5.02 on Z2 thanks.

ondrejvaroscak said:
Installation:
Extract downloaded ZIP file, it contains:
flimit - binary executable for changing open file limits
01_flimit - shell script called by init
flimit.c - source code of binary executable
Enable init.d support in XZDualRecovery by editing XZDR.prop and change dr.initd.active=true
Dont forget to have enabled byeselinux (dr.keep.byeselinux=true)
copy flimit and 01_flimit to /data/local/tmp (or push adb)
create directory /data/flimit
copy flimit to /data/flimit and make executable (chmod 777)
create directory /system/etc/init.d with and chmod 777 /system/etc/init.d
copy 01_flimit to /system/etc/init.d and chmod 777 /system/etc/init.d/01_flimit
Click to expand...
Click to collapse
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa

hispanico957 said:
Thank a lot for big news.... just a clarification:
Which xdual recovery we must have ? also the last 2.8.12 ?
The file XZDR.prop i have located on external memoery...it's correct ?
When you said create a directory /data/flimit.. in where ?
In which way i can "..enabled byeselinux (dr.keep.byeselinux=true).."
Thank
Hispa
Click to expand...
Click to collapse
Any recovery that supports init.d and byeselinux. So if you find this two settings in your XZDR.prop, you just enable them by setting "true".
I tested with 2.8.12,
XZDR.prop is located in /sdcard1 so its External SD card. If no SD card, then its located in /cache.
/data/limit you create absolutely, it means in / is folder data (that already exists) and you create flimit in /data, so:
Code:
adb shell
su
mkdir /data/flimit
byeselinux you enable by setting "dr.keep.byeselinux=true" in XZDR.prop (it may be set to false by default depending on version fo XZDR you have).

Ok fine... for verify all you said:
{
"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"
}
dont find ? where i wrong ??? the folder and file are present
Thank
Hispa
P.S.
Whe you said :
But as soon as I disable the init.d support, it bootloops. So re-enable by edititng XZDR.prop and it again boots.
Click to expand...
Click to collapse
i mean to pu dr.initd.active=false ??
and last after all i can install xposed over .726 odexed ?

hispanico957 said:
Ok fine... for verify all you said:
su
/data/flimit/flimit $(pgrep zygote)
this command from ADB ?
Thank
Hispa
Click to expand...
Click to collapse
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app

Great thanks

ondrejvaroscak said:
from adb or directly in terminal app if you have one..
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Thank solved but see please my post #14
Hispa

In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !

Pandemic said:
In XZDR.prop i dont have: dr.keep.byeselinux so must i add it if so then under which line ?
I have the latest version of recovery.
Sent From MoonWalker Provolution V1.0 [Beta] Based On LP 5.0.2 !
Click to expand...
Click to collapse
+1 i too cannot find thet line

hispanico957 said:
Ok fine... for verify all you said:
dont find ? where i wrong ??? the folder and file are present
Click to expand...
Click to collapse
can you run "ls -l /data/flimit/*" and paste output to reply?
Whe you said :
i mean to pu dr.initd.active=false ??
Click to expand...
Click to collapse
Exactly, when you put dr.initd.active=false and have full stock, it should again bootloop. Then you replace the XZDR.prop file with version with init.d enabled and it should boot normally again.
and last after all i can install xposed over .726 odexed ?
Click to expand...
Click to collapse
I think without any problem. Deodexing has nothing to do with working Xposed, but it is may be necessary for some modules (Gravitybox?)?

ESCAPE key mapping in DEX mode

I have the keyboard book cover and i really miss the ESC and del keys. One way around this is to use a keymapper software and you are done. But this is not the scenario when used in DEX mode. In DEX mode you wont be able to change the keyboard to the custom one. So i was researching how to edit the kl and kcm files to get the job done. However i am not able to achieve my goal that is remap '~' ( the first key ) to ESCAPE.
The tablet is rooted with magisk on android Q.
Code:
# tail -n11 /proc/bus/input/devices
I: Bus=0018 Vendor=04e8 Product=a035 Version=0000
N: Name="Tab S5e Book Cover Keyboard"
P: Phys=
S: Sysfs=/devices/platform/soc/880000.i2c/i2c-7/7-002a/input/input13
U: Uniq=
H: Handlers=sec_key_notifier event7
B: PROP=0
B: EV=13
B: KEY=4 0 0 0 0 0 0 0 0 0 2400169000400000 77ffffffffffffc
B: MSC=10
mounted the /system to readwrite
Code:
mount --remount / -w
changed directory to /system/usr/keylayout and /system/usr/keychars couldnt find the relevant Vendor_04e8_Product_a035.kl and Vendor_04e8_Product_a035.kcm respectively. So i created them by copying generic.kcm and generic.kl files.
Now in the kl file . KEY1 is ESCAPE. which is what i want. but after doing the above i am not getting the action of ESCAPE after a disconnect and reconnect and testing in termux. will the OS never use the custom kl and kcm files that i created ?

Hi. Did you manage to find a way? Thanks.

gabrielgon said:
Hi. Did you manage to find a way? Thanks.
Click to expand...
Click to collapse
Sorry i have not found a way.

Hello,
It seems that android is inspecting through a lot of directories until finding a suitable charmap.
See, maybe, Android documentation :
Android doc
If you find those kl & kml files, it would be interesting to share them.
And if you could retrieve the french language keyboard (fr-FR) charmap (maybe after downloading it, it would be useful for me as I would like to map not only ESC key, but F1... F12 also).
As we can select apparently other keyboards mapping for Book cover keyboard (tried with "Extra keyboard layouts" on Play Store, they're selectable), so maybe a solution would be to generate an APK embedding the new keyboard charmap using something like this https://exkeymo.herokuapp.com/ (or generate the APK from scratch).

Delete please.

Database Users

welcome