zROM+ 28.0.A.8.251 Android 5.0.2 - V1.1Sony Xperia Z3+ E6553
ROM Features
Based on Sony firmware 28.0.A.8.251 Generic Hong Kong
Aroma installer
Deodexed and zipaligned
Rooted with SuperSU preinstalled
Dual boot/ TWRP recovery environment
Custom kernel with runtime control of SELinux enforcing status and RIC disabled
Google apps updated and with customizable graphical installer for Gapps
Writeable external SD card
Xposed framework functional (in SELinux permissive mode)
Bloatware removed
The following apps and bloatware have been removed and can be installed directly from the Play store if desired. The first two are installable by selecting the appropriate option in the ROM installer
What's New
Xperia lounge
AVG Antivirus
AAStocks
Anonymous Data Collection
Facebook
Lifelog
Mobisystems File Commander
Mobisystems Office
MyXperia
Playstation App
Playstation Network Portal
Privilege Movies
Sketch
Socialife
Sony Movie Creator
Spotify
Trackid
Please hit the Thanks button if you use this ROM. Many downloads but few thanks....
Installation instructions
NOTE: You must perform a factory reset before install by wiping cache and data.
Click to expand...
Click to collapse
Step 1
Download the TWRP image for the Z3+ and unpack it
Download zROM+ and the zROM+ md5 file
Run a command shell
Code:
c:>adb reboot bootloader
c:>fastboot boot recovery.img
c:>adb push zrom-v1.1.zip /sdcard/zrom-v1.1.zip
c:>adb push zrom-v1.1.zip.md5 /sdcard/zrom-v1.1.zip.md5
The file is big, so it will take 5 or more minutes to complete the upload. If you're impatient put your external SD in a card reader and load it that way.
Step 2
In the interface for TWRP, navigate to Wipe and perform a factory reset
In the interface for TWRP, navigate to Install
Click install, select zrom-v1.1.zip from the internal storage
Swipe to flash
Read and follow the instructions
Reboot when complete
Click to expand...
Click to collapse
The first boot is painfully slow. It takes about 10 minutes, so just be patient. It will stay in the blue booting screen for a long time. This is normal. Do not reboot your phone. Just wait and it will eventually boot up. You can always rerun the installer to flash additional Google Apps. If you do so, be sure to deselect the install ROM option and do not do a factory reset.
Notes
This ROM has a kernel that supports runtime SELinux mode changes. The mode change is accomplished through a script /system/su.d/permissive.sh, which sets SELinux to permissive mode at boot time. If you wish to run Xposed, you must run SELinux in permissive mode. Failure to do so results in multiple system applications force closing at startup and a device that is locked up.
If you don't run Xposed I recommend that you keep SELinux in enforcing mode. To do so, go to Settings-->About and click multiple times on the Build number until it tells you that Developer mode is activated. When developer mode is activated, back out and select the Developer option and enable USB debugging. Now run an adb shell and remove the permissive mode script. Grant permission for USB debugging when the prompt comes up
Code:
c:>adb shell
[email protected]:/ $ su
Wait for the SuperSU prompt and grant permission to adb
Code:
[email protected]:/ # mount -o rw,remount /system
[email protected]:/ # rm -f /system/su.d/permissive.sh
[email protected]:/ # reboot
If you choose not to install any of the Google apps, a minimum core Google framework will be installed anyway. This includes Google framework, GmsCore, Google Play, Google Login Services, Google Contacts and Backup Sync, SteupWizard and OneTimeInitializer that runs after first boot. Apart from the Play store app and the first time setup apps, the rest of these apps are not visible in your app drawer.
While I have made every effort to test this ROM in a variety of different install scenarios, it is a beta ROM and you may experience some bugs. I make no warranty as to its fitness for purpose or its performance and you use it at your own risk.
PLEASE SEE NOTE BBELOW IN POST TWO ON USING XPOSED FRAMEWORK
This ROM now supports booting directly into TWRP recovery mode. To access recovery mode, power on the phone and when you see the yellow LED illuminate press the down volume button once or twice.
Downloads
TWRP v2.8.7.0 for Z3+
zROM+ v1.1 for Z3+ (md5: 999452b5ac29f92473b964af819a3cd6)
zROM+ v1.1 for Z3+ MD5
for GPL purposes, the kernel and associated dowloads
Changelog
Current changelog: -- 01 October 2015
01 October - Release v1.1
Add dual boot/recovery environment
Remove Android Pay due to Google restrictions on root
Update Google apps
19 September - Release v1 beta
Thanks To/Credits
amarullz for the Aroma graphical installer
The OpenGapps team at www.opengapps.org for the Gapps binaries for aarch64
osm0sis for some of the functions used in the installer script
XDA:DevDB Information
zROM+, ROM for the Sony Xperia Z4
Contributors
dl12345
ROM OS Version: 5.0.x Lollipop
Based On: 28.0.A.8.251
Version Information
Status: Beta
Current Beta Version: v1.1 beta
Beta Release Date: 2015-10-01
Created 2015-09-20
Last Updated 2015-09-19
Xposed framework v74 bootloops on Xperia Z3+. The reason for this is discussed in this post
To use Xposed on zROM+, please download the [UNOFFICIAL] xposed-v74-sdk21-arm64-dl12345-UNOFFICIAL-20150929 for Xperia Z3+
You MUST do a wipe cache and dalvik after installation otherwise you will get errors including one that claims your storage space is full and another 504 error when installing anything from the Play Store
Please read the instructions in the referenced post
Have been waiting for this with baited breath. So far so good! Thanks for the great work!
Do need unlockbootloader to install rom?
manhhung1420 said:
Do need unlockbootloader to install rom?
Click to expand...
Click to collapse
Yes.
Thank you for your efforts.
Any chance that this ROM can work for E6533 (dual SIM) variant? Or can you plan to support?
Rookie123 said:
Thank you for your efforts.
Any chance that this ROM can work for E6533 (dual SIM) variant? Or can you plan to support?
Click to expand...
Click to collapse
Offhand, I'd say it's unlikely. Sony has a different firmware for this phone.
I'm unlikely to support a device I don't have access to. Apologies.
Works great thanks. Is there any way to make a sound mod to increase headphones volume?
pikeylfc said:
Works great thanks. Is there any way to make a sound mod to increase headphones volume?
Click to expand...
Click to collapse
There's probably something in the xposed repository for that....
Am so sorry to heard that I wanted to install a fresh rom on my hot phone
lilloscar said:
Am so sorry to heard that I wanted to install a fresh rom on my hot phone
Click to expand...
Click to collapse
Sorry to hear what?
dl12345 said:
Sorry to hear what?
Click to expand...
Click to collapse
That this rom wont support the dual version
Great work! finally working recovery...but please..cant access my external sd card! fix this please!
chrisss5000 said:
Great work! finally working recovery...but please..cant access my external sd card! fix this please!
Click to expand...
Click to collapse
No problem here accessing my external SD card in recovery mode and when booted in the ROM. Have you formatted your external card? In recovery mode, the path to the external SD card is /external_sd...
so weird...try to enable it..but it dosent work...and the rom cant start...stock at bot sony xperia logo...
chrisss5000 said:
so weird...try to enable it..but it dosent work...and the rom cant start...stock at bot sony xperia logo...
Click to expand...
Click to collapse
You likely didn't do a wipe. Go to advanced wipe. Wipe dalvik cache, system, data, cache. Reinstall the rom.
dl12345 said:
You likely didn't do a wipe. Go to advanced wipe. Wipe dalvik cache, system, data, cache. Reinstall the rom.
Click to expand...
Click to collapse
I have installed roms like hundrad times...I did a factory reset and I did advanced wipe etc...dosent work..so weird..
I guess something is wrong..something with premissions? Because every time I have wiped my phones it takes a while..But when I wiped now with this recovery it was done in a heart beat...
chrisss5000 said:
I have installed roms like hundrad times...I did a factory reset and I did advanced wipe etc...dosent work..so weird..
I guess something is wrong..something with premissions? Because every time I have wiped my phones it takes a while..But when I wiped now with this recovery it was done in a heart beat...
Click to expand...
Click to collapse
You're installing on a Z3+ e6553 single sim version, right? My wipes are pretty quick too....once the wipe is done, go to the mount option in recovery, mount the filesystems and make sure they're empty (well, they will contain a lost+found folder for the ext4 filesystems and your sdcard contents for the /data filesystem).
Permissions are unlikely to be the problem. The ROM is untarred from an ext4 filesystem copy, so original filesystem permissions are preserved. It also installs an updated file_contexts and does a selinux restorecon to make sure selinux contexts are correct...
dl12345 said:
You're installing on a Z3+ e6553 single sim version, right? My wipes are pretty quick too....once the wipe is done, go to the mount option in recovery, mount the filesystems and make sure they're empty (well, they will contain a lost+found folder for the ext4 filesystems and your sdcard contents for the /data filesystem).
Permissions are unlikely to be the problem. The ROM is untarred from an ext4 filesystem copy, so original filesystem permissions are preserved. It also installs an updated file_contexts and does a selinux restorecon to make sure selinux contexts are correct...
Click to expand...
Click to collapse
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
dl12345 said:
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
Click to expand...
Click to collapse
Yes it is Xpera Z3+ E6553
Okay I will test it now! I will come back with results
big thanks!!
---------- Post added at 08:05 PM ---------- Previous post was at 08:00 PM ----------
dl12345 said:
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
Click to expand...
Click to collapse
Uhm should the installing just take 15 sec? I nearly drop my finger from the screen and it is wiped....something is wrong...
---------- Post added at 08:07 PM ---------- Previous post was at 08:05 PM ----------
dl12345 said:
Incidentally, on first boot, it takes a few minutes to get past the Sony logo. then once you hit the blue screen be prepared for a 10 minute wait...
Click to expand...
Click to collapse
it dosent work...it only get stuck at sony loggo
Related
Notes:
Click to expand...
Click to collapse
This build is a rework/continuation of MDJ Froyo Sense Revolution series
If m-deejay decides to update his original build, I will discontinue this build
Use this at your own risk. I will not be accountable if this causes you phone to fail, or you lose your data. The backup of your data is your responsibility.
I am a newbie to the android development, so please be patient with fixes and releases; and your help and advice will be appreciated.
Finally: Please, Click Thanks if you appreciate the build, and all works.
Kernel Usage
Click to expand...
Click to collapse
The kernel used in this ROM is based on MDJ S9.2, and have ported it, and have patched to the latest upstream with a lot of fixes Just to confirm, this kernel was originally S9.2 from MDJ, so up until then all credit is to him
The git is available here, check logs and diffs for the changes made. There is a neat build script to get it compiled for yourself if you want as well in Linux or cygwin. I am using the test branch at the moment.
ROM Links
Click to expand...
Click to collapse
I have tested an upgrade myself to these releases myself, and have not encountered any problems. But everyones setup is different, the upgrade process may work for you. But would recommend to do a NAND backup before you do. FINALLY, I will not be held responsible if you lose any data.
DFT releases will not be provided, so DON'T ask
The build of this ROM is available here, If anyone wants to have play with this build, then feel free to checkout the repository by running the following command in Linux. This will grab the whole repository onto your machine.
Code:
git clone http://github.com/arif-ali/android_leo_fsr.git
Froyo Sense Revolution 2.5.1 NAND CWM MAGLDR, Click or scan the image
Froyo Sense Revolution 2.5.1 NAND CWM cLK, Click or scan the image
Forum Links
Click to expand...
Click to collapse
ClockworkMod HowTo
cLK howto
config.txt Howto
Click to expand...
Click to collapse
ppp_mode - set PPP or not, valid values 1 or 0 (not for cLK)
gps_zone - zone from pool.ntp.org, values may be uk, us, europe etc... check pool.ntp.org, for all possible values
example config
Code:
ppp_mode=1
gps_zone=uk
cLK Howto
Click to expand...
Click to collapse
Download the attached cLK1.3.3_system_250M_arif-ali.zip, or cLK1.3.3_system_210M_arif-ali.zip
turn phone on with volume down key, so that it is in SPL
install cLK by double-clicking CustomRUU.exe
To install recovery download the correct one from post #2 of cLK thread (link below)
reboot phone into fastboot by keeping the back key pressed
flash recovery by running "fastboot flash recovery recovery.img"
How To (CWM - MAGLDR)
Click to expand...
Click to collapse
Make sure you have partitioned the SD card correctly (ext partition, and a vfat partition)
Make sure you have followed the ClockWorkMod Howto to add the recovery to the phone (see links in the thanks/credits section)
Download the link above and put it into the vfat partition, maybe in a folder called ROMS
Boot phone into MAGLDR by holding on the Red button/close call
Select AD Recovery (Option 8)
Select Install zip from sdcard
Select choose zip from sdcard
Select the ROM from the SD
Select Yes to install the zip
reboot the phone and enjoy
How To (CWM - cLK)
Click to expand...
Click to collapse
Make sure you have partitioned the SD card correctly (ext partition, and a vfat partition)
Download the link above and put it into the vfat partition, maybe in a folder called ROMS
Boot phone into fastboot by pressing the back key
flash the recovery using "fastboot flash recovery recovery.img"
reboot phone into cLK recovery by holding on the Home key
Select Install zip from sdcard
Select choose zip from sdcard
Select the ROM from the SD
Select Yes to install the zip
reboot the phone and enjoy
Howto ROM Manager
Click to expand...
Click to collapse
After booting into the phone, you need to create the following file on your sdcard, and reboot the phone. Hopefully after this, your phone should work.
Code:
/sdcard/clockworkmod/.settings
with the following contents
Code:
{"is_clockworkmod":true,"current_recovery_version":"3.0.1.9","readonly_recovery":false,"recovery_timestamp":1300214577721,"flash_recovery":"flash_image recovery %s ; ","reboot_recovery":"","detected_device":"leo"}
I will attempt to get this added in the next release
Please READ!!!
Click to expand...
Click to collapse
make sure that any app that you do install move it back to the phone, and that will automatically reside on the SD card in the ext2/ext3/ext4 partition
For the this ROM 210 MB in /system, So you need the Recovery_250M from the RaiderX303's thread
To Do List / Work in-progress
Click to expand...
Click to collapse
v2.6
Fix AudioFlinger Issue
Fix volume issues
Add Stock Theme Option
Thanks/Credits
Click to expand...
Click to collapse
m-deejay (ROM & kernel)
Cotulla (MAGLDR, HSPL)
kholk (Radio)
RaiderX303 (ClockworkMod)
birkoffsjunk (img2cwm)
tkirton (dtapps2sd)
cedesmith (cLK)
letama (ril_wrapper)
#htc-linux and #htc-linux-chat
All ROM users
Screenshots
Screenshots
Changelog
v2.5.1(25/03/2010)
new kernel AA 0.5 (see kernel changelog for details)
support for ROM Manager if using cLK
Add latest ROM Manager to cLK build
update to cLK 1.3.3
cache moved to mtd cache
Add ES File Explorer
Update gmail, youtube apks
v2.5(13/03/11)
added cLK support
moved AA 0.3 kernel
added PPP support
added config.txt support
fixed APN issue in framework
Initial Release (by me)
Downloading & try soon
chairman_palm said:
Downloading & try soon
Click to expand...
Click to collapse
Any feedback?
Update to 2.5.1
Updated, highlights below,
* new kernel AA 0.5 (see kernel changelog for details)
* support for ROM Manager if using cLK
* Add latest ROM Manager to cLK build
* update to cLK 1.3.3
* cache moved to mtd cache
* Add ES File Explorer
* Update gmail, youtube apks
enjoy
Ok I am jumping on board and will give this ROM a try will give feedback in a few hrs after ROM has settled in
Update: ROM loaded and runs really smooth, picture messages are blurry - only allows a max 300k message size
added English (US) through MoreLocale2 app
I know this is a work in progress so keep up the great work arif
Update 27Mar11 -
have been using this ROM just over 24hrs and so
fare not to bad
Battery drain is a little higher than what I am used to
Have to remember to us speaker phone when I make first
call after reboot due to Robot voice and subsequent freezing of my phone if I fail to do so.
Also have periodic data connection failure of which I do not
experience on my other HD2 with a diff. ROM.....This was just FYI and not meant to degrade your hard work Arif
stock theme
Here is an initial attempt at doing the Stock theme
http://www.multiupload.com/LL8NO4MB13
feedback would be great
Why sdext doesn't work? I have properly partitioned card which works with other roms, but here my phone states that I have 3mb free space after install. I even re partitioned card without success.
maxld said:
Why sdext doesn't work? I have properly partitioned card which works with other roms, but here my phone states that I have 3mb free space after install. I even re partitioned card without success.
Click to expand...
Click to collapse
Have you used the required config.txt?
Sent from my HTC HD2 using XDA Premium App
Honestly I tried to find it but I'm so blind that I did it without it. Thanks for the help mate.
Edit:
I searched again and still can't find it. Could you upload me one?
maxld said:
Honestly I tried to find it but I'm so blind that I did it without it. Thanks for the help mate.
Edit:
I searched again and still can't find it. Could you upload me one?
Click to expand...
Click to collapse
Look at the first post it tells you how to create one. Its simple open note pad on your computer put in the right details and save it as config.
Sent from my HTC HD2 using XDA Premium App
Yeah, i have read it, but there are only ppp and gps options listed.
maxld said:
Yeah, i have read it, but there are only ppp and gps options listed.
Click to expand...
Click to collapse
Okay try this in create the config.txt like I said and in it put a2sd_mode=data
Sent from my HTC HD2 using XDA Premium App
Thank you kindly for your help, sir. Unfortunately it didn't help, maybe OP will have a trick how to activate sd ext partition.
maxld said:
Thank you kindly for your help, sir. Unfortunately it didn't help, maybe OP will have a trick how to activate sd ext partition.
Click to expand...
Click to collapse
* create a file called config.txt
* add the following contents to the file
a2sd_mode=data
* run "adb push config.txt /sdcard/."
* reboot your phone.
If this doesn't work, then run the following commands
adb shell ls -l /dev
adb shell mount
adb shell df
and let me know the results
Thanks, I'll report results in a moment.
Edit 1: It will be a longer one, because my connection is ridiculously slow and I have to download sdk and jdk
Edit 2: None of your advices helped, still have 3.85 MB of free space.
Anyone have the new version?
giorgib said:
Anyone have the new version?
Click to expand...
Click to collapse
What do you mean writing "the new version"?
There isn't a new version yet, and haven't planned one as yet. But I have some ideas that I wanted to try to fix some of the issues that this ROM has
Most of my time has been spent on doing the CM nightlies and the CWR updates, and getting RM support for the leo. But I will see when I can get time out to do an update here as well.
[TOOL] [v3.2] [09NOV] Ubuntu Touch "system-image" Installer // w/o computers
# All credit goes to Ubuntu and contributors
ut-system-installer
I wanted to install Ubuntu Touch system-image (official, ro, OTA-enabled, for-sale-in-the-future) on my Galaxy Nexus, but there were some limitations and disadvantages to do so. It requires Ubuntu on my computer and completely wipes my device. Compared to cdimage-touch, which one can install easily with his/her phone, system-image is hard for some people to try, so I made a simple recovery-flashable zip with shell scripts to install it without computer and losing data. It downloads and installs system-image on your device(officially supported ones only).
What is does:
The same thing as doing
Code:
phablet-flash ubuntu-system --channel devel --no-backup
but without wiping the device, so
-Download files for installing Ubuntu Touch system-image (half-automatically)
-Install it on your device (supported ones by Canonical)
Supported Devices:
-Galaxy Nexus (maguro, toro, toroplus)
-Nexus 7 (grouper, tilapia)
-Nexus 4 (mako)
-Nexus 10 (manta)
Downloads:
http://d-h.st/users/zittoro/ut
Do not use anything in wip folder.
* This will install a CWM-based recovery from Ubuntu, and your device could brick but will not be compensated. *
How-to:
1. Download the zip.
2. Unzip it in /sdcard/Download/ut
3. Move or copy ut-system-dl(read "Arguments for "ut-system-dl"" in second post for options) to /data. Then run the script with root(su). You can just type these in terminal instead of doing this step manually (You need busybox and su installed)
Code:
su
cp -a /storage/emulated/0/Download/ut/ut-system-dl /data
sh /data/ut-system-dl
4. Zip everything in /sdcard/Download/ut
5. Flash it in recovery and reboot recovery (Just use the default install menu at home if you are using special recoveries like MultiROM)
6. Enjoy Ubuntu Touch
Bug reports: post your /sdcard/Download/ut/ut-system.log, /cache/recovery/last_log, and copy of the error if possible
Changelogs:
Code:
[b]09NOV2013[/b]
v3.2
-Added official UT disclaimer link
-Cleaner code
[b]07NOV2013[/b]
v3.1
-Support for "generic customization" channels
[b]03NOV2013[/b]
v3
-Support for "*-customized" channels
-More consistent and easier way of configuring files names to download
v2.2
-Download the recovery image properly as saucy-named doesn't exist in the path anymore. --Thanks to @pildoc for reporting.
[b]21OCT2013[/b]
v2.1
-Log file support to the installation script; still need recovery log because of "system-image-installer"
-Support for trusty-related channels
-Workaround for delta images when device files are the same
-Dropped support for old-channel device images
-Workaround for non-patched recoveries
-Show the actual device names rather than codenames to avoid confusion
[b]19OCT2013[/b]
v2
-Add support for deciding which build number to download --$4
-Fix delta image download
-Mount before extracting files
[b]18OCT2013[/b]
v1.2
-Fix for script error
-Aborts installation if script fails
v1.1
-Recovery installation fix; it wasn't moved to the correct path, my bad:(
-Added log file: ut-system.log
[b]16OCT2013[/b]
v1
-Initial
Arguments for "ut-system-dl":
-$1: -auto: default for script, automatically detects the device's codename using the value for "ro.build.product"
-DEVICE_NAME: images for DEVICE_NAME devices
-$2: -full: default for script, full images used for initial installation
-delta: delta images used for updates(OTA)
-$3: -CHANNEL: use CHANNEL channel to download images, default "devel"
-$4: -BUILD_NUMBER: build number of image
I dont get it
Sent from my Nexus 4 using xda app-developers app
gazhead said:
I dont get it
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It basically installs the recommended version of ubuntu touch
Looks like your path is wrong? If its going into download/ut shouldn't it be:
su
cp -a /storage/emulated/0/download/ut /data
sh /data/ut-system-dl
hockeyadc said:
Looks like your path is wrong? If its going into download/ut shouldn't it be:
su
cp -a /storage/emulated/0/download/ut /data
sh /data/ut-system-dl
Click to expand...
Click to collapse
Dang I made a mistake
Zittoro said:
Dang I made a mistake
Click to expand...
Click to collapse
Haha no problem. I'm trying this out on my phone(Maguro) and it gets stuck at connecting to the server. Any ideas? Just a ton of people trying to download right now?
hockeyadc said:
Haha no problem. I'm trying this out on my phone(Maguro) and it gets stuck at connecting to the server. Any ideas? Just a ton of people trying to download right now?
Click to expand...
Click to collapse
Can you get a screenshot for me?
Zittoro said:
Can you get a screenshot for me?
Click to expand...
Click to collapse
Actually, i just tried again and its working. 53 min ETA but its ok. When I zip this and flash it, does it remove my current recovery? How do I go back to my current rom in the future?
hockeyadc said:
Actually, i just tried again and its working. 53 min ETA but its ok. When I zip this and flash it, does it remove my current recovery? How do I go back to my current rom in the future?
Click to expand...
Click to collapse
It installs a CWM-based recovery with some tweaks and workout for system-image installation. Since it doesn't even touch your system partition, you can just flash an android kernel and get back to android.
Zittoro said:
It installs a CWM-based recovery with some tweaks and workout for system-image installation. Since it doesn't even touch your system partition, you can just flash an android kernel and get back to android.
Click to expand...
Click to collapse
Nice! That makes it pretty easy. Now we just need a way to dual boot lol. Perhaps a program that allows you to select android or ubuntu, and upon android selection it flashes a new kernel?
hockeyadc said:
Nice! That makes it pretty easy. Now we just need a way to dual boot lol. Perhaps a program that allows you to select android or ubuntu, and upon android selection it flashes a new kernel?
Click to expand...
Click to collapse
It's already possible on gnex.
http://forum.xda-developers.com/showthread.php?t=2480404
This kernel has tri-boot option for android and ut and recovery dual-boot using its recovery
Zittoro said:
It's already possible on gnex.
http://forum.xda-developers.com/showthread.php?t=2480404
This kernel has tri-boot option for android and ut and recovery dual-boot using its recovery
Click to expand...
Click to collapse
Awesome!
hockeyadc said:
Awesome!
Click to expand...
Click to collapse
Hey did you get it installed successfully? Some people in a different community say it doesn't. Did it boot into a new recovery when you rebooted it?
Zittoro said:
Hey did you get it installed successfully? Some people in a different community say it doesn't. Did it boot into a new recovery when you rebooted it?
Click to expand...
Click to collapse
I haven't tried yet. I realized how many apps I need and use on a daily basis, so I would rather not install it yet. Just gonna wait it out until Ubuntu is more complete.
Changelogs:
18OCT2013
v1.1
-Recovery installation fix; it wasn't moved to the correct path, my bad
-Added log file: ut-system.log
v1.2
-Fix for script error
-Aborts installation if script fails
Blur
can you guys explain to me step by step in doing so. Sorry for being a noob. i want to learn how to so that i can help others and also improve my knowledge..
subaash said:
can you guys explain to me step by step in doing so. Sorry for being a noob. i want to learn how to so that i can help others and also improve my knowledge..
Click to expand...
Click to collapse
1. Download the zip from the link
2. Unzip it to the specified directory on your phone (you can do this with a file explorer app)
3. Download a terminal app and copy and paste the "code" into it.
4. If you get an error, post your /sdcard/Download/ut-system.log. If you don't, zip everything in the specified folder and flash it in recovery
5. Reboot recovery right after the installation
Changelogs:
19OCT2013
v2
-Add support for deciding which build number to download --$4
-Fix delta image download
-Mount before extracting files
Will this work with kulturom(nexus7) AS secondary ROM?
Wysłane z mojego Nexus 7 przy użyciu Tapatalk
UPDATE: check out TowelRoot app by @geohot! One-click root solution that works with latest firmware released for Xperia M single/dual (provides half-root only, don't forget to apply root fixer)
Nicki Root is deprecated, it got merged in my new dd Flasher tool and works across many devices, not only Xperia M. The attachments and changelog from Nicki Root were kept below for archiving history, but I won't provide support for it anymore. For any problem you may encounter, go to dd Flasher thread. If you want to root Xperia M through dd Flasher, downgrade your device to Android 4.1 or 4.2.2 firmware, root it with Cydia Impactor and follow the instructions from dd Flasher thread.
Changelog
Version 2.0
• Nicki Root now is called dd Flasher
Old versions
Version 1.3.3
• Bugfixes for Linux script
• Updated SuperSU to 2.02
Version 1.3.2
• Make sure the temporary folder exists before pushing the script
Version 1.3.1
• Now compatible with Linux
Version 1.3
• Implement log capabilities (users can pull last log by selecting appropriate option in main menu)
• Drop "reboot in flash mode" (after using dd, system partition layout is different and device can't be rebooted)
• Check if LED can be used to indicate status, otherwise disable it
• Minor code changes
Version 1.2
• Rewrote most of the code
• Script now uses LED to indicate status
• By popular demand, dropped choice command in favour of set command (should work with Windows XP again)
• For every single command, script will now check if it failed or not and warn the user if anything get wrong
• Rewrote the mount/umount routine, loop device is selected automatically and resource busy issues are fixed now
• Can be used with half-rooted devices now (script check if device is fully rooted and apply root fixer at runtime if needed)
• Implemented "reboot in flash mode" command to avoid needing to pull/reinsert battery manually (experimental, sometimes doesn't work)
Version 1.1
• Make sure busybox is installed after first boot (previous versions pushed busybox but didn't install it)
• Drop choice32/choice64 applets and use built-in OS command (Windows XP no longer supported)
Version 1.0.1
• Typo fix (Nicky => Nicki)
• Updated busybox to 1.22.1
Version 1.0
• Initial release
Will test as soon as Indian Firmware Update show up...
Sent from my C2004 using Tapatalk
Well done @mbc07, this is great news. Dont forget to give credit to @joemarshall, afterall, he cane up with the idea . Thanks for testing it and creating this thread, nevertheless
sent from wadiya using my mafroom
I'll be trying this (probably) in the next hour, I'll post results for the Single SIM afterwards.
RESULTS TIME: This method of rooting worked and I am now running 4.3 with root access. Thank you.
Sent from my C1905 using xda app-developers app
Gonna test after I download 4.1.2 ftf, hope it works
rizla2 said:
Gonna test after I download 4.1.2 ftf, hope it works
Click to expand...
Click to collapse
It works perfectly, I'm now rooted on 4.3 thanks to this. The only error I had was when the tool first tried to push the system.ext4 to the SD Card, it said there wasn't enough space, I just deleted the incomplete copy and then ran the tool again and it worked.
Hmm, I'd not thought of mounting the image and doing dd, that is pretty tidy.
Balls, It didn't work for me first try, error mounting the loopback device, said it was busy. I'm re-flashing the phone back to 4.1 now. I've split the shell scripts into 2, first one does the modifications of system.ext4, second one does the dd flash, with a press any key between. That way if the modifications to system.ext4 fail, you're not stuck with an unrooted phone where system partition has already been written, and you can happily start again. I was flashing from sd card if that makes any difference.
Also, would it be possible to copy the reboot executable into your temp folder before you do the dd, so that you don't have to do the battery out reset in the middle of the process, or won't reboot work once you're in that state?
Edit: Second time lucky, thanks ever so much. Maybe I just needed to start from a blank slate version of 4.1, blimey that first boot takes some time though!
cheers,
Joe
mbc07 said:
It took me a lot of time and I tried a lot of methods but I finally managed to root the new 4.3 update without unlocking the bootloader, let's root that thing.
Requirements:
You will need FlashTool and the FTF file of 4.3 update for your phone
You should be running Android 4.1.2/4.2.2 firmware with full root. If you already updated to 4.3, sorry, you'll need to downgrade to 4.1.2/4.2.2 and root it, otherwise this method won't work
You should have at least 1.5GB of free space in your Internal Storage or in your SD Card. If you don't have enough space, the installation will be aborted and your phone will be left intact
Make sure you have full root (eg. your phone doesn't reboot when you remount /system with RW access). Using this method without full root may reboot your phone during the procedure, getting you in a bootloop
Currently the script works only on Windows, I'll try to get a Linux version soon
Getting system.ext4 file: before continuing, we'll need to extract system.ext4 from system.sin present in the update. Open the FTF it with WinRAR or 7-zip and extract system.sin somewhere, then open FlashTool, go to Tools => Sin Editor, locate the system.sin file extracted previously and then click in "Extract Data". You'll get system.ext4 in the same folder you extracted system.sin. Now you're good to go
Procedure:
Download the attached ZIP and unzip its contents somewhere
Move system.ext4 extracted previously to the same folder where root.bat is
Open root.bat and follow the instructions
After the process finished, the script will tell you and your phone will be in a frozen state (it's normal). At that point, you should manually remove the USB cable and then pull/reinsert your battery. DON'T TURN IT ON, we haven't finished yet (turning it on now will get you in a bootloop).
Open FlashTool again and flash the entire 4.3 FTF, but exclude system (if you forget to do so, the root will be removed and you'll need to start over)
After flashing finished, disconnect the USB cable and start your phone. If everything went well you should be in 4.3 now, with full root access
NOTE: I'm not that good with BASH/Shell scripts, and although I had implemented some sanity checks, something may have escaped that checks. So, if you do this procedure and the shell script finish with errors, it's better to start over since something may have not worked and you may be in a partial root state...
Click to expand...
Click to collapse
It worked for me thanks to you
About flashing 4.3 can I do a data and cache wipe?
Wysłane z mojego GT-P3110 przy użyciu Tapatalka
iks8 said:
About flashing 4.3 can I do a data and cache wipe?
Wysłane z mojego GT-P3110 przy użyciu Tapatalka
Click to expand...
Click to collapse
Flashtoll wil wipe data and cache when you flash 4.3 You don't need to do anything else.
paper13579 said:
Well done @mbc07, this is great news. Dont forget to give credit to @joemarshall, afterall, he cane up with the idea . Thanks for testing it and creating this thread, nevertheless
sent from wadiya using my mafroom
Click to expand...
Click to collapse
I still need to rework the OP, many people from Root for FTF 4.3 Update 15.4.A.0.23 LOCKED BOOTLOADER deserves credits, after all I wouldn't have that idea without their replies... Will get these guys credited in the OP soon
joemarshall said:
Hmm, I'd not thought of mounting the image and doing dd, that is pretty tidy.
Balls, It didn't work for me first try, error mounting the loopback device, said it was busy. I'm re-flashing the phone back to 4.1 now. I've split the shell scripts into 2, first one does the modifications of system.ext4, second one does the dd flash, with a press any key between. That way if the modifications to system.ext4 fail, you're not stuck with an unrooted phone where system partition has already been written, and you can happily start again. I was flashing from sd card if that makes any difference.
Also, would it be possible to copy the reboot executable into your temp folder before you do the dd, so that you don't have to do the battery out reset in the middle of the process, or won't reboot work once you're in that state?
Edit: Second time lucky, thanks ever so much. Maybe I just needed to start from a blank slate version of 4.1, blimey that first boot takes some time though!
cheers,
Joe
Click to expand...
Click to collapse
Thank you for the feedback, I'll try to add some sanity checks before using dd. About reboot, I tried using busybox reboot but nothing happened, the same for adb reboot. Apparently after using stop, the reboot command doesn't seems to work
Uh, I forgot... Anybody tried pushing to SD Card? Did it worked?
mbc07 said:
Uh, I forgot... Anybody tried pushing to SD Card? Did it worked?
Click to expand...
Click to collapse
Yes it did, sort of. The first time I did it I got an error saying there wasn't enough space (I had over 10GB free however). Once I got the error I deleted the incomplete file from my SD Card and then I ran the script again, this time it copied the file fully and then installed properly.
This occurred on the Single SIM C1905 Xperia M by the way.
Yes! Finally rooted. Thanks a lot!
Btw don't forget to change usb mode to mtp instead msc (I've tried msc and it can't copy files)
mbc07 said:
I still need to rework the OP, many people from Root for FTF 4.3 Update 15.4.A.0.23 LOCKED BOOTLOADER deserves credits, after all I wouldn't have that idea without their replies... Will get these guys credited in the OP soon
Thank you for the feedback, I'll try to add some sanity checks before using dd. About reboot, I tried using busybox reboot but nothing happened, the same for adb reboot. Apparently after using stop, the reboot command doesn't seems to work
Click to expand...
Click to collapse
At first time i've had also 'mount: mounting /dev/block/loop0 on /data/local/tmp/system failed: Device or res
ource busy'
Flash new, clean Android 4.1 solve problem.
Thank you very much.
Hey guys, does this give you full root?
sent from wadiya using my mafroom
paper13579 said:
Hey guys, does this give you full root?
sent from wadiya using my mafroom
Click to expand...
Click to collapse
Yes it does.
I'll check about the loop device errors (apparently they may occur in Xperia M single SIM), thanks for reporting guys...
paper13579 said:
Hey guys, does this give you full root?
sent from wadiya using my mafroom
Click to expand...
Click to collapse
Yes. I implemented the disable ric service method from [NUT] root fixer too
Man, this is a great achievement, you should be proud. Im about to try it now. Wish me luck
sent from wadiya using my mafroom
Before your script use dd it should check:
1. That there is no any apps mounted in /dev/block/loop0 (for example Swift Key). If yes, you will see 'mount: mounting /dev/block/loop0 on /data/local/tmp/system failed: Device or resource busy' (you can it by type losetup)
2. Phone is in MTP USB MODE. If you set to memory storage mode, Android will not access to sd card with system.ext4 image (script would check that can it access to /sdcard) and you will get mount argument error
EFIDroid
A UEFI based Android bootloader.
EFIDroid provides an easy Installer, good looking Material Design user interfaces and uses very dynamic code.
Homepage: efidroid.org
Take over control before loading the Operating system.
EFIDroid attempts to make it easy for both users and developers to control their boot experience.
Multiboot
Install and boot any number of operating systems and recovery tools.
Boot plugins
Change the boot behavior without modifying ROM's. Swapping internal/external memory, overclocking or modifying the ramdisk. Live and without any permanent modifications.
UEFI Apps
EFIDroid uses UEFI in the background which means that you can boot other bootloaders like GRUB or rEFInd and even small games
Download
see Installation section
Requirements
The main OS (that one you currently use) must be rooted to use the efidroid app.
You may be able to install magisk later in a secondary ROM (never tried it though)
Hint:
lineageos root add-on works (tested on LOS 15.1) and magisk will NOT work. Use supersu.
TWRP / FlashFire installable ZIP:
Stable: supersu-stable
Beta: supersu-beta
Latest: supersu
At the moment the only TWRP which is working for efidroid is: twrp-3.1.1 - any newer TWRP release will fail with a ramdisk size error which is not due to a missing kernel patch. It's a known issue for efidroid and one of the reasons for the efidroid rewrite
I maybe find a workaround to get newer TWRP versions installed.. we will see..
So if you have a newer version of TWRP installed currently: upgrade/downgrade to that version first.
Installation
A full howto with screenshots can be found here
Unlock your device! This will NOT work with a locked bootloader (you know about UsU?)
Download the EFIDroid Manager from Google Play Store - Has been removed..
Efidroid manager download: main efidroid thread
Download the latest version by opening the "Downloads" tab of this thread (requires to open this thread in a browser)
Activate my efidroid OTA server:
Option 1 (permanent): modify /system/build.prop
Boot to TWRP
Make a backup (including system partition)!
Mount System partition in TWRP
enable the efidroid OTA server:
Code:
adb shell
echo "efidroid.server_url=https://raw.githubusercontent.com/steadfasterX/efidroid_ota_lgg4/master" >> /system/build.prop
reboot
verify that the efidroid server URL has been set properly:
Code:
adb shell getprop efidroid.server_url
Option 2 (will be lost on reboot): using setprop
Set the efidroid OTA server:
Code:
adb shell
setprop efidroid.server_url https://raw.githubusercontent.com/steadfasterX/efidroid_ota_lgg4/master
verify that the efidroid server URL has been set properly:
Code:
adb shell getprop efidroid.server_url
Open EFIDroid Manager
HINT: If you see an error like "cannot load device info, please check your connection : no value for lge/H815" then the above OTA url has not been set or is set wrong.
Go to Install/Update
Click Install --> HINT: THIS WILL MOVE YOUR BOOT AND RECOVERY PARTITION CONTENT
This means
1. from now on EFIDroid will boot each time u power on the device.
2. the recovery partition gets backed up and you will see it in EFIDroid again as (if TWRP): TWRP (internal).
3. you can still boot your main ROM by just choosing it from the list --> your ROM name - (internal)
If you don't like this you can install EFIDroid to either: recovery or boot partition only. But this is a manual process and when you upgrade with EFIDroid Manager it may overwrite your changes.
Install a custom ROM
A full howto with screenshots can be found here
Open EFIDroid Manager
Open the menu "Operating Systems" and click the FAB (Floating Action Button) at the bottom
Choose in the screen /data/media/0/multiboot as location.
Enter a name for the ROM
Optional: Choose another icon for the ROM
You can leave the partitions as they are (Schema LoopSystem + BindOther) Press the tab "PARTITIONS" and choose "LoopAll". You will see that the data partition is quite big (the g4 internal storage is just 23 GB so you choose a smaller size for each ROM to fit all your ROM slots).
Tip "data" and select GB in the drop down. Choose a proper size (i.e. 2 GB) depending on what you wanna do with that ROM and how many you wanna install (each ROM will take 4 GB for system + the data size you choose here)
In the tab "REPLACEMENTS" click the floating plus button and add a new cmdline override:
Code:
Name = androidboot.selinux
Value = permissive
press the tick in the top right corner to finish the setup
Now you can see your newly created ROM slot in the list
Reboot
Once you are in the efidroid, you can navigate around with volume down to go down, volume up to go up and the power button to confirm your selection.
To flash a ROM to the new empty slot, select TWRP (Internal) , press power and select the slot name with power again
At the moment the system partition is just empty and needs to be formatted before you can use it!
In TWRP:
select WIPE -> Advanced Wipe -> select "system" and "cache", then swipe to wipe.
select WIPE -> "Format Data" button
Reboot -> System. When you see efidroid again choose TWRP and select the new ROM slot again to boot TWRP again.
Install your ROM of your choice.
Hint: If you get an error regarding device detection you have to remove the assert line(s) within the ROM zip first
Supported devices
Any LG G4 model which can be unlocked (yea even UsU ones but that still requires some more work to detect them properly)
Known Issues
The Operating System list in the EFIDroid Manager is empty just upgrade to the latest EFIDroid manager app..
after installing a ROM it may bootloop under some circumstances
AROMA installer flickers extremely. Workaround: press power to turn off screen then turn it on again. It still flickers but u can see and use the installer at least.
As we need to use TWRP 3.1.1 (see requirements) UsU devices get not detected correctly!
The state of this project is ALPHA so expect issues and even data loss is possible (so do a TWRP backup often)
Booting a secondary ROM and working in a secondary ROM may feel slower (that's by design)
if a ROM has set selinux to enforcing it will not boot! --> If you setup the ROM slot properly (see above REPLACEMENTS tab) you do not need to care about.
Without that adjustment in the efidroid manager you have to modify the boot.img of every ROM:
change the cmdline from
androidboot.selinux=enforcing
to
androidboot.selinux=permissive
I started a while ago to make selinux policies for efidroid but it's not that easy and so atm no ROM which has selinux set to enforcing will boot.
Credits
@m11kkaa for EFIDroid
@J0SH1X for bringing a first port for the G4
@steadfasterX for being steadfast and optimizing efidroid
XDA:DevDB Information
EFIDroid for the LG G4, Tool/Utility for the LG G4
Contributors
steadfasterX, @m11kkaa, @J0SH1X
Source Code: https://github.com/steadfasterX/efidroid_device_lge_g4
Version Information
Status: Alpha
Created 2017-04-14
Last Updated 2018-12-17
Workarounds for known issues
1) random app crashes, settings do not persist on reboot
The reason is that file permissions get not set correctly on the bind mounted data partition.
So nothing can be stored there (or what get stored will be stored with the wrong perms).
When creating a new ROM slot it is important (atm) that you choose LoopAll .
This would create a data partition image with 23 GB which is way too much so you need to touch the data partition in the partitions tab and set the size to GB and choose e.g. 2 GB.
2) no WiFi
First boot TWRP internal / primary slot
Code:
adb shell cp /data/misc/wifi/config /external_sd/data_misc_wifi_config
Then for each slot you created you must reboot TWRP in its slot and:
Code:
adb shell cp /external_sd/data_misc_wifi_config /data/misc/wifi/config
adb shell chown system.wifi /data/misc/wifi/config
adb shell chattr +i /data/misc/wifi/config
Reserved
I tried to install Efidroid on my LG G4 (H815, bootloader unlocked, ResurrectionRemix 5.8.2). I install the App and modify the build.prop with the efidroid url, but every time i start the app i get the error-massage:
Error. Can't load device info. Please check your connection. No value for lge/h815.
Could you help me fixing this?
jokuu said:
I tried to install Efidroid on my LG G4 (H815, bootloader unlocked, ResurrectionRemix 5.8.2). I install the App and modify the build.prop with the efidroid url, but every time i start the app i get the error-massage:
Error. Can't load device info. Please check your connection. No value for lge/h815.
Could you help me fixing this?
Click to expand...
Click to collapse
Oh damn. I forgot to update the OTA for the other devices..
There is nothing you can do on your site atm.. Sorry I will fix it asap and let you know..
.
Sent from my LG-H815 using XDA Labs
still hard at it heck yea
jokuu said:
I tried to install Efidroid on my LG G4 (H815, bootloader unlocked, ResurrectionRemix 5.8.2). I install the App and modify the build.prop with the efidroid url, but every time i start the app i get the error-massage:
Error. Can't load device info. Please check your connection. No value for lge/h815.
Could you help me fixing this?
Click to expand...
Click to collapse
ok done. please try again
.
steadfasterX said:
ok done. please try again
.
Click to expand...
Click to collapse
Now it works. Thank you! :good:
ok .. im able to boot a LL based ROM now (Imperium ROM).. but only ONCE. lol..
Well I can boot into it again after booting in the TWRP version of that ROM and doing a factory reset from within TWRP...
Cleaning /data, /cache and dalvik cache manually does NOT work.. interesting. <-- I tested with a special (FIsH) TWRP version which does not WIPE but RM only.. Once I switched to a regular TWRP it is still strange but at least behaves the same now: When I wipe /data and /cache I can boot (but only when wiping both).
Update:
Keeping strange:
When I wipe /data only -> no boot
When I wipe /cache only -> no boot
When I wipe both -> boot ok .. wtf.?!
I will look into /misc - maybe the reason can be found here!
.
I just booted a second rom successfully using efi on my h811
My primary rom: lineage nougat
My secondary rom: resurrection remix (mm)
First boot was slow, second a little less slow, third and so on boot at normal speed.
Anyone else with an h811 care to try it coz @steadfasterX thinks mine booted coz i have an h811.
So if anyone else with an h811 can test it, that would help.
Btw, you all jelly? :victory:
Update: i have a complex sort of bootloop.
I decided to flash gapps.
Now when i try to boot the rom, i get the optimizing apps screen, then starting apps, then the boot logo, then again starting apps, and again boot logo and it goes on like that.
If i clear cache and dalvik i get the optimizing apps again, then the circle continues.
Maybe its gapps?
Or maybe its coz you all were too much jelly
tanveer7652 said:
Update: i have a complex sort of bootloop.
I decided to flash gapps.
Now when i try to boot the rom, i get the optimizing apps screen, then starting apps, then the boot logo, then again starting apps, and again boot logo and it goes on like that.
If i clear cache and dalvik i get the optimizing apps again, then the circle continues.
Maybe its gapps?
Or maybe its coz you all were too much jelly
Click to expand...
Click to collapse
heat
kevp75 said:
heat
Click to expand...
Click to collapse
Heat? What do you mean
tanveer7652 said:
Heat? What do you mean
Click to expand...
Click to collapse
I believe he thinks you have the ilapo because he don't know what efidroid is.
have you tried to wipe /data as mentioned (on IRC) ?
.
tanveer7652 said:
Heat? What do you mean
Click to expand...
Click to collapse
steadfasterX said:
I believe he thinks you have the ilapo because he don't know what efidroid is.
have you tried to wipe /data as mentioned (on IRC) ?
.
Click to expand...
Click to collapse
LOL I have a good idea with efidroid is
Everytime you wipe cache/dalvik your device has to rebuild the dalvik.
When your device rebuilds dalvik it has to work.. and work hard... as a result of the device working harder than normal, it generates heat. if it gets too hot, it will reboot.
I sometimes get it on a plain ol' stock rom
@steadfasterX im back to work on it just bought a new g4 today and currently im in unlock progress
J0SH1X said:
@steadfasterX im back to work on it just bought a new g4 today and currently im in unlock progress
Click to expand...
Click to collapse
Congrats. Please remember some of us poor guys when u buy another g4 ?
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
kevp75 said:
LOL I have a good idea with efidroid is
Everytime you wipe cache/dalvik your device has to rebuild the dalvik.
When your device rebuilds dalvik it has to work.. and work hard... as a result of the device working harder than normal, it generates heat. if it gets too hot, it will reboot.
I sometimes get it on a plain ol' stock rom
Click to expand...
Click to collapse
But it doesn't get hot.
kevp75 said:
LOL I have a good idea with efidroid is
Click to expand...
Click to collapse
oh that's good
kevp75 said:
Everytime you wipe cache/dalvik your device has to rebuild the dalvik.
When your device rebuilds dalvik it has to work.. and work hard... as a result of the device working harder than normal, it generates heat. if it gets too hot, it will reboot.
I sometimes get it on a plain ol' stock rom
Click to expand...
Click to collapse
tbh I don't think that this is the case here. We have bootloops when something changes in /data. This is not heat related. It is something efidroid related..
J0SH1X said:
@steadfasterX im back to work on it just bought a new g4 today and currently im in unlock progress
Click to expand...
Click to collapse
u like pain do u ?
steadfasterX said:
oh that's good
tbh I don't think that this is the case here. We have bootloops when something changes in /data. This is not heat related. It is something efidroid related..
Click to expand...
Click to collapse
theres software bootloop and hardware bootloop. i only get software when i install something or say remove gapps. or mess with system . flashing rom fix it..
version 2 out now~~~
After researching the framework info, I found out MEA G8142 roms are able to be edited to work with xposed.
So I extracted the framework, added some info, changed build.prop, and there you go, it worked for my G8141.
It might also work with 2xx firmwares, but I am too busy right now!
1. Download 47.1.A.12.179 stock rom for G8141 or G8142 ROM, and completely erase your phone with it using flashtool (having a twrp backup of /data is perfectly fine), in wipe, select all, otherwise you will get problems with encryption
2. install twrp via fastboot flash recovery twrp.img
https://www.androidfilehost.com/?fid=890278863836296663
3. (G8141) recover my system backup using twrp, if you have dual sim G8142 you have to follow step 4 as well
https://www.androidfilehost.com/?fid=11050483647474827606
(version 2, replaced google apps, more debloat, more stable system)
to recover, simply make a backup of something, then you will see this in your sdcard: twrp/xxx/1970-xx-xx/xxx
copy my files in the last folder, then recover my system data
3.1 reboot quickly to twrp
****
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
download the 4 zip package kernel for your device and version, extract and put in your phone
****
3.2 install kernel (1), reboot to twrp
3.3 install zip files (2), (3), (4), xposed
3.4 install keyboard
https://androidfilehost.com/?fid=818070582850495399
for g8142 extra only:
4. edit build.prop
replace g8141 with g8142, e.g.
ro.build.product=maple_dsds
ro.semc.product.model=G8142
ro.semc.ms_type_id=PM-1031-BV
ro.semc.version.fs=GENERIC
ro.semc.product.name=Xperia XZ Premium
ro.semc.product.device=G81
ro.product.model=G8142
ro.build.flavor=maple_dsds-user
ro.product.brand=Sony
ro.product.name=maple_dsds
ro.product.device=maple_dsds
ro.build.description=maple_dsds-user 8.0.0 OPR6.170623.013 1 dev-keys
ro.build.fingerprint=Sony/maple_dsds/maple_dsds:8.0.0/OPR6.170623.013/1:user/dev-keys
can also just download this, put it in notepad++ and save as build.prop, push to system with 0600 permission
https://pastebin.com/0iyaEJGf
https://youtu.be/Yl4mUPdjMKc
proof it works
bugs:
1. do not update magisk
2. when adding any lock, like pin or security do NOT allow boot security, otherwise system ui will crash upon reboot
Where is the build.prop file?
amakuramio said:
currently uploading! done in few hrs
After researching the framework info, I found out ASEAN G8142 roms are able to be edited to work with xposed.
So I extracted the framework, added some info, changed build.prop, and there you go, it worked for my G8141.
It might also work with 2xx firmwares, but I am too busy right now!
1. Download ANY G8141 or G8142 ROM that is 179 version, and completely erase your phone with it using flashtool (having a twrp backup of /data is perfectly fine), in wipe, select all, otherwise you will get force close
2. install twrp via fastboot flash recovery twrp.img
https://www.androidfilehost.com/?fid=890278863836296663
3. recover my system backup using twrp, for g8142 you have to follow step 4
uploading currently, isdone within 15 mins
to recover, simply make a backup of anything, then you will see this in your sdcard: twrp/xxx/1970-xx-xx/xxx
copy my files in the last folder, then recover
3.1 reboot quickly to twrp
****
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
download the 4 zip package kernel for your device and version, extract and put in your phone
****
3.2 install kernel (1), reboot to twrp
3.3 install zip files 2, 3, 4, xposed
for g8142 extra only:
4. edit build.prop
replace g8141 with g8142, e.g.
ro.build.product=maple_dsds
ro.semc.product.model=G8142
ro.semc.ms_type_id=PM-1031-BV
ro.semc.version.fs=GENERIC
ro.semc.product.name=Xperia XZ Premium
ro.semc.product.device=G81
ro.product.model=G8142
ro.build.flavor=maple_dsds-user
ro.product.brand=Sony
ro.product.name=maple_dsds
ro.product.device=maple_dsds
ro.build.description=maple_dsds-user 8.0.0 OPR6.170623.013 1 dev-keys
ro.build.fingerprint=Sony/maple_dsds/maple_dsds:8.0.0/OPR6.170623.013/1:user/dev-keys
bugs:
1. do not update magisk
2. when adding any lock, like pin or security do NOT allow boot security, otherwise system ui will crash upon reboot
todo: need to optimize settings.apk (is zipaligned, but lags)
Click to expand...
Click to collapse
How about screen on time im using turbo75b(with mods and xposed) , i usually get more than 9 hours screen on time when have a little gaming and alot browsing and streaming videos, so my question is this rom is super debloated? Or no.
And next one is how many hours you get screen on time without enabling stamania mode.
Blackghosthm said:
How about screen on time im using turbo75b(with mods and xposed) , i usually get more than 9 hours screen on time when have a little gaming and alot browsing and streaming videos, so my question is this rom is super debloated? Or no.
And next one is how many hours you get screen on time without enabling stamania mode.
Click to expand...
Click to collapse
on wifi I get 8 hrs to 8.30
on 4g, drains very fast
but newer versions are faster (after march, sony use 8.1 compiler for faster apps)
its 89% upload
its also possible that I combine system from 179 with turbo rom 75, it should be compatible and easy to do.
jianlin3062 said:
Where is the build.prop file?
Click to expand...
Click to collapse
the build.prop file is in ''root/system/build.prop'' I use notepad++ to edit it on pc then push it back to the phone
twrp file manager, copy build.prop to sd card, copy to pc, replace maple with maple_dsds and g8141 with g8142, its easy to do
1. Can't log into Google And because it's constantly trying to connect to Google, it's lagging
2. Lots of ANRs that pop up for a second and close themselves
3. You forgot to leave a keyboard, LOL. I use gBoard anyway
4. Feels better than .75 anyway.
5. Launches with the .205 JanJan's kernel, but the WiFi doesn't work
I'll keep testing. THANK YOU A LOT!!!
upd. In China the whole Google is banned, and I only can log in via VPN-ned WiFi, which I can't use unless I install keyboard, lol.
upd. So, I've disabled the security on my WiFi. I've connected to the network from the very beginning. But still no success. Just black screen.
upd. I've flashed OpenGAPPS, thinking that it would help. And, guess what? Black screen.
I went further:
Chrome STOPS.
Google Earth STOPS.
Maps STOP.
Many cool features DO work, but because I can't log into my Google account, sadly, the FW for me is unusable here. I can't keep figuring out why, because I need a working device by tomorrow...
saved-j said:
1. Can't log into Google And because it's constantly trying to connect to Google, it's lagging
2. Lots of ANRs that pop up for a second and close themselves
3. You forgot to leave a keyboard, LOL. I use gBoard anyway
4. Feels better than .75 anyway.
5. Launches with the .205 JanJan's kernel, but the WiFi doesn't work
I'll keep testing. THANK YOU A LOT!!!
upd. In China the whole Google is banned, and I only can log in via VPN-ned WiFi, which I can't use unless I install keyboard, lol.
upd. So, I've disabled the security on my WiFi. I've connected to the network from the very beginning. But still no success. Just black screen.
upd. I've flashed OpenGAPPS, thinking that it would help. And, guess what? Black screen.
I went further:
Chrome STOPS.
Google Earth STOPS.
Maps STOP.
Many cool features DO work, but because I can't log into my Google account, sadly, the FW for me is unusable here. I can't keep figuring out why, because I need a working device by tomorrow...
Click to expand...
Click to collapse
you did something completely wrong
backup your data (if you want, prefer clean) flash a 179 stock firmware erase all otherwise force close, then restore my system, then flash the 4 zips, reboot after the first one, then flash last 3 zips I posted in the link up there, then xposed, then reboot
I really have 0 problems here. I thought I kept swiftboard in it? hmm. I will make a patch zip with keyboard in it, hopefully it helps. you can also push a keyboard app in system/app/Appname/app.apk 0644 permission
https://www.apkmirror.com/apk/swift...swiftkey-beta-7-0-8-363-android-apk-download/
can you do me a favor? make a screenshot of the system app scroll down, then send me. Maybe I uploaded wrong system?
do you can xposed patch on turbo final v2 rom?
it stucked.
amakuramio said:
you did something completely wrong
Click to expand...
Click to collapse
1. Flashed .179 with FULL WIPE.
2. pushed the TWRP and Kernel via ADB.
3. Entered the TWRP and restored your /system from the backup.
4. Flashed the Kernel again, just in case. (JanJan's 179)
5. Rebooted back into the TWRP and flashed the other three zips (2-Patching, 3-Magisk and 4-Permissive)
6. Flashed the Xposed v90-sdk26-beta3
7. Booted system.
Passed the welcome.
Installed the Xposed Manager and SwiftKey.
All the way get the FC messages that pop up for a second and disappear by themselves.
-Messaging keeps stopping.
Opened the Play Store, it kept loading something for a minute and then ...stopped too.
-Google Play Services keeps stopping.
This is 100% the right /system you've provided, but something just doesn't work.
I'm attaching a screen record from today.
I will update this post as it goes.
Also am gonna try:
-AndroPlusKernel 12 -
-Magisk 16.4 (instead of 16.0) -
-OpenGapps (instead of included) -
-Magisk-Systemless-Xposed (instead of flashing /system included) - works either way
saved-j said:
1. Flashed .179 with FULL WIPE.
2. pushed the TWRP and Kernel via ADB.
3. Entered the TWRP and restored your /system from the backup.
4. Flashed the Kernel again, just in case. (JanJan's 179)
5. Rebooted back into the TWRP and flashed the other three zips (2-Patching, 3-Magisk and 4-Permissive)
6. Flashed the Xposed v90-sdk26-beta3
7. Booted system.
Passed the welcome.
Installed the Xposed Manager and SwiftKey.
All the way get the FC messages that pop up for a second and disappear by themselves.
-Messaging keeps stopping.
Opened the Play Store, it kept loading something for a minute and then ...stopped too.
-Google Play Services keeps stopping.
This is 100% the right /system you've provided, but something just doesn't work.
I'm attaching a screen record from today.
I will update this post as it goes.
Click to expand...
Click to collapse
pushing a keyboard into the system will also help, but that is the way to do it, yes
do you have g8141 or g8142? google play issue is related to not updating proper build prop to your device
amakuramio said:
g8142
Click to expand...
Click to collapse
Oh, i forgot to mention it. I have extracted your build.prop (with added extra lines against the stock .179), changed the lines to the g8142 and saved it. I replace the build.prop to the one containing "g8142" lines right after restoring your /system, setting the rights to 0644, before the first boot.
lGIKDk said:
do you can xposed patch on turbo rom?
Click to expand...
Click to collapse
I can actually do that, but in the opposite way. Debloat exactly in the same way as turbo rom. its possible, but first I want people to try this out and see if ti works, before I make a rom that doesnt work.
saved-j said:
Oh, i forgot to mention it. I have extracted your build.prop (with added extra lines against the stock .179), changed the lines to the g8142 and saved it. I replace the build.prop to the one containing "g8142" lines right after restoring your /system, setting the rights to 0644, before the first boot.
Click to expand...
Click to collapse
can you try to enter system/priv app/gmscore, then inside the folder delete lib and gmscore.apk, then replace it with this
https://www.apkmirror.com/apk/googl...2-8-66-090400-200774163-android-apk-download/
GmsCore.apk with permission 0644
same with phonesky
https://www.apkmirror.com/apk/googl...6-08-all-0-pr-200628961-android-apk-download/
then reboot with dalvik and cache removed (2 things only) there may be LIB compatibility issues.
Hell if google play doesnt work for g8142, I can also do nanomod! which is very light on the battery
nanomod needs xposed, but it works with xposed, so
amakuramio said:
can you try to enter system/priv app/gmscore, then inside the folder delete lib and gmscore.apk, then replace it with this
Click to expand...
Click to collapse
working on it. 15 minutes please. nanomod would be AWESOME btw
p.s. you forgot a file in an inappropriate place: "/system/Settings zipaligned.apk" - wtf is that lol
---------- Post added at 05:41 PM ---------- Previous post was at 05:21 PM ----------
amakuramio said:
Hell if google play doesnt work for g8142
Click to expand...
Click to collapse
I've already tried the whole ROM with the OpenGapps yesterday, and it didn't work, but I gave it a try again with your files. :good: I didn't even replace the Build.prop - let it stay where it is.
So, on a clean flash:
1. I've replaced the GmsCore.apk, Phonesky.apk with the ones you gave me the links for
2. Gave them the proper permissions
3. Cleaned Dalvik
Result? Google Play Services keeps stopping.
Messaging and other apps kept FC too.
I don't think it's 8142's problem. I think there's something wrong with your /system
It is not only the Gapps problem, because Messaging and some other apps randomly FC too. Check the video in my previous post. It's a common problem, not only the Gapps fail.
Note! I don't do dirty flashes for testing purposes: every and each time I flashed everything cleanwise again, from scratch, with the flashtool rom, to make 100% sure.
Now, I don't know what to do. Any suggestions?
*trying one more time while you're thinking*
saved-j said:
working on it. 15 minutes please. nanomod would be AWESOME btw
p.s. you forgot a file in an inappropriate place: "/system/Settings zipaligned.apk" - wtf is that lol
---------- Post added at 05:41 PM ---------- Previous post was at 05:21 PM ----------
I've already tried the whole ROM with the OpenGapps yesterday, and it didn't work, but I gave it a try again with your files. :good: I didn't even replace the Build.prop - let it stay where it is.
So, on a clean flash:
1. I've replaced the GmsCore.apk, Phonesky.apk with the ones you gave me the links for
2. Gave them the proper permissions
3. Cleaned Dalvik
Result? Google Play Services keeps stopping.
Messaging and other apps kept FC too.
I don't think it's 8142's problem. I think there's something wrong with your /system
It is not only the Gapps problem, because Messaging and some other apps randomly FC. Check the video in my previous post. It's a common problem, not only the Gapps fail.
Note! I don't do dirty flashes for testing purposes: every and each time I flashed everything cleanwise again, from scratch, with the flashtool rom, to make 100% sure.
Now, I don't know what to do. Any suggestions?
Click to expand...
Click to collapse
if nothing works, then it means it must be a framework issue. I am on G8141 without any issues.
thanks for testing so far. I don't have g8142 so I cannot know.
1. in xposed install http://repo.xposed.info/module/com.thermatk.android.xf.fakegapps (do this first, just enable it, dont reboot in recovery yet)
2.delete the following
/system/app/GooglePrintRecommendationService/GooglePrintRecommendationService.apk
/system/app/GoogleAnalyticsProxy/GoogleAnalyticsProxy.apk
/system/app/GoogleExtShared/GoogleExtShared.apk
/system/app/GoogleContactsSyncAdapter/GoogleContactsSyncAdapter.apk
/system/priv-app/GmsCore/GmsCore.apk
/system/priv-app/GoogleBackupTransport/GoogleBackupTransport.apk
/system/priv-app/GoogleExtServices/GoogleExtServices.apk
/system/priv-app/GoogleFeedback/GoogleFeedback.apk
/system/priv-app/GoogleOneTimeInitializer/GoogleOneTimeInitializer.apk
/system/priv-app/GooglePartnerSetup/GooglePartnerSetup.apk
/system/priv-app/GoogleServicesFramework/GoogleServicesFramework.apk
/system/priv-app/Phonesky/Phonesky.apk
3. then flash nanodroid https://downloads.nanolx.org/NanoDroid/Stable/ then reboot. you might want to go options of google play then clear data afterwards.
(4. extra, see if settings folder in app is same permission as other folders, and if apk inside is also same as other apk in the different folders)
cant google login. it just black screen
amakuramio said:
if nothing works, then it means it must be a framework issue. I am on G8141 without any issues.
thanks for testing so far. I don't have g8142 so I cannot know.
Click to expand...
Click to collapse
The difference between them is minimal. Somehow it worked for me with OpenGapps. I'll set the phone up and leave it as it is, as it's 4:00 am already. I'm glad it worked somehow.
I'll test it during the week, though i've already found several issues, like, in Album app it doesn't allow to move from the internal memory to the folders on the SD card already existing (don't know why?? - Google Photos app does it with no problem)
lGIKDk said:
cant google login. it just black screen
Click to expand...
Click to collapse
Did you read the conversation here before posting your message? You're not alone in this problem.
Try flashing .179 again, with all the wipes, etc - following the instruction.
And flash Open Gapps right before you boot up in the system. It has JUST worked for me when I tried it in the last time, though it hadn't worked for me yesterday!
Active Screen, XZ2 Camera and some other XZ2 features, Xposed, WiFi, data, everything works just fine.
Had to spend two nights to achieve it, though.
Attaching a video of working Xposed. My device recognizes as Pixel XL because I have a Daydream Enabling magisk module.
amakuramio said:
I can actually do that, but in the opposite way. Debloat exactly in the same way as turbo rom. its possible, but first I want people to try this out and see if ti works, before I make a rom that doesnt work.
Click to expand...
Click to collapse
ok. i wait.
i hope completly version
amakuramio said:
After researching the framework info, I found out ASEAN G8142 roms are able to be edited to work with xposed.
So I extracted the framework, added some info, changed build.prop, and there you go, it worked for my G8141.
It might also work with 2xx firmwares, but I am too busy right now!
1. Download 47.1.A.12.179 stock rom for G8141 or G8142 ROM, and completely erase your phone with it using flashtool (having a twrp backup of /data is perfectly fine), in wipe, select all, otherwise you will get problems with encryption
2. install twrp via fastboot flash recovery twrp.img
https://www.androidfilehost.com/?fid=890278863836296663
3. (G8141) recover my system backup using twrp, if you have dual sim G8142 you have to follow step 4 as well
https://www.androidfilehost.com/?fid=674106145207498283
to recover, simply make a backup of something, then you will see this in your sdcard: twrp/xxx/1970-xx-xx/xxx
copy my files in the last folder, then recover my system data
3.1 reboot quickly to twrp
****
https://forum.xda-developers.com/xz-premium/development/kernel-sony-xz-premium-5-2018-t3784669
download the 4 zip package kernel for your device and version, extract and put in your phone
****
3.2 install kernel (1), reboot to twrp
3.3 install zip files (2), (3), (4), xposed
for g8142 extra only:
4. edit build.prop
replace g8141 with g8142, e.g.
ro.build.product=maple_dsds
ro.semc.product.model=G8142
ro.semc.ms_type_id=PM-1031-BV
ro.semc.version.fs=GENERIC
ro.semc.product.name=Xperia XZ Premium
ro.semc.product.device=G81
ro.product.model=G8142
ro.build.flavor=maple_dsds-user
ro.product.brand=Sony
ro.product.name=maple_dsds
ro.product.device=maple_dsds
ro.build.description=maple_dsds-user 8.0.0 OPR6.170623.013 1 dev-keys
ro.build.fingerprint=Sony/maple_dsds/maple_dsds:8.0.0/OPR6.170623.013/1:user/dev-keys
can also just download this, put it in notepad++ and save as build.prop, push to system with 0600 permission
https://pastebin.com/0iyaEJGf
https://youtu.be/Yl4mUPdjMKc
proof it works
bugs:
1. do not update magisk
2. when adding any lock, like pin or security do NOT allow boot security, otherwise system ui will crash upon reboot
todo: need to optimize settings.apk (is zipaligned, but lags)
Click to expand...
Click to collapse
Are you sure, this room created by you not @machao44
At least have him the credit,but thanks for debloating and modifying the rom.
Same as others Google play services crash like base rom(m-rom).
Blackghosthm said:
Are you sure, this room created by you not @machao44
At least have him the credit,but thanks for debloating and modifying the rom.
Same as others Google play services crash like base rom(m-rom).
Click to expand...
Click to collapse
though the rom is made by sony I got it from MEA version from XPERIFIRM and modified by me I did include HIS xposed fix (not directly).
What I did copy was the framework intents those are the same as his. If I modified framework myself and installed his xposed then because of mismatch the whole thing would crash so I had to force the same intents to match the signature.