Related
Hello Friends,
If you want to re-size you tattoo to have more space for system and data partitions
Here is simple how to do.
No chance of bricking your phone, and it doesn't involve SPL
It works for installed ROM as well as new installations
It was done using the the scripts and information from following thread
http://forum.xda-developers.com/showthread.php?t=717874
Installation instructions:
download FR-recovery-v1.5.3-CustomMTD_S.zip and FR-boot-v1.5.3-CustomMTD_S.zip
reboot to recovery
and use following commands to specify partition size
Explanation of commands used below : after the mtd command first number is system size and the next is cache and remaining will be data partition
choose your cache partition size based on the fact, whether it uses for dalvik-cache or not.
If it used for dalvik-cache do not go less than 80mb (roughly) other wise 20 mb is fine.
Code:
adb shell
mount /sdcard
echo "mtd 200 20" > /sdcard/mtdpartmap.txt
backup your rom
wipe cache + data
If you are 'growing' system, make sure cache and data are clean
if your 'shrinking' system make sure system is clean
To wipe system you need clockworkmod-recovery
flash FR-recovery-v1.5.3-CustomMTD_S.zip
repeat wipe cache + data
reboot to recovery
At this point if you can either restore your existing installation
OR Flash fresh ROM and other extras
Finally flash FR-boot-v1.5.3-CustomMTD_S.zip
reboot
You could see re-partitioned tattoo with more space for system and data
Here are my Tattoo partition sizes before
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 95188 0 95188 0% /dev
/dev/block/mtdblock3 [B][COLOR="Red"]153600[/COLOR][/B] 137452 16148 89% /system
/dev/block/mtdblock4 [B][COLOR="Red"]153600[/COLOR][/B] 1172 152428 1% /cache
/dev/block/mtdblock5 [B][COLOR="Red"]169088[/COLOR][/B] 56596 112492 33% /data
and after following above instructions
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 95188 0 95188 0% /dev
/dev/block/mtdblock3 [B][COLOR="Red"]204800[/COLOR][/B] 118140 86660 58% /system
/dev/block/mtdblock4 [B][COLOR="Red"]20480[/COLOR][/B] 1164 19316 6% /cache
/dev/block/mtdblock5 [B][COLOR="Red"]251648[/COLOR][/B] 123200 128448 49% /data
It is recommended to use clockworkmod-recovery, although i could use AmornRA recovery (for a fresh install of ROM)
HELP TIPS or POINTS
You don't need to flash both of the files each time you install a new ROM.
You only need to flash the recovery patch once, unless you want to re-size or you installed a new recovery.
The boot patch *must* be flashed after you have installed a new ROM or kernel (boot.img) or for every restoring of backup.
If you are 'growing' system, make sure cache and data are clean
if your 'shrinking' system make sure system is clean
In order to wipe system, data, cache partitions
flash clockworkmod-recovery, and from recovery the recovery menu
go to "mounts and storage" option and wipe required partitions
If you want to restore original MTD, flash original recovery to wipe custom MTD
Here is the information for Developers to include this in their ROMs
ROM Zip Patcher for Devs
To make life even simpler for end users it is possible to integrate the 'patch' within a ROM
AutoMTD_partitionPatcher_v1.5.3.zip
currently Linux only,
within the zip is a tarball, untar that.
get that directory into your PATH, ( or just cd into it )
and then execute
Code:
PatchUpdateScript.sh <zip file to patch>
it will then
create a temp directory ( in your current directory )
copy your zip to it
extract required files
patch update(r)-script
zip and sign.
It simply saves the user from flashing the boot patch after flashing your ROM
Click to expand...
Click to collapse
Hope that is useful
All credit goes to Firerat (Custom MTD Partitions)
i have tested this now!
And it works great...
Although my linux machine did not have the java packs installed to patch the boot.img, i simply made nandroid backup and put img into zip afterwards.
Thanks for guide
Dexter_nlb said:
i have tested this now!
And it works great...
Although my linux machine did not have the java packs installed to patch the boot.img, i simply made nandroid backup and put img into zip afterwards.
Thanks for guide
Click to expand...
Click to collapse
Good that you could use it
I didn't have time to look in to ROM patching script, But how do you mention the partition sizes with this script?
Please let me know.
Cheers
rallapag said:
I didn't have time to look in to ROM patching script, But how do you mention the partition sizes with this script?
Click to expand...
Click to collapse
i initially used the txt file on /sdcard to configure the recovery, then when rom was installed patched it. then a nandroid backup and copied rom to my update.zip and reinstalled rom normally, with patch included..
this solution is of course for one size of mtd's, but it was even easier..
Sorry for my misunderstanding I just went through the autoMTD script and realized what you said earlier.
Auto MTD script patches boot.img, so for patched ROM's as well you need flash FR-recovery with mtdpartmap.txt in user sd card defining partition sizes.
Cheers
30A Full Stock (root, busybox, init.d, ext4) for SU-660
This is a patched firmware from my r990 for SU-660
we need to flash
AIO TOOLKIT SU660
Download
mirror
ICS FULL STOCK V30A SU660
Download
mirror
NEW SKYWALKER CUSTOM KERNEL for SU660 more here
Download (For help with the kernel thanks civato )
throw the card ICS FULL STOCK V30A SU660.zip and CivZ_SkyWalker_RF1.2_24RH-SU660
1. run the AIO-ToolKit.cmd
2. press the number "4" (Change Partitions from OLD to NEW layout and vice versa)
3. press the number "1" (P 990 - ICS Partitions layout)
4. press the number "1" (P990-ICS-cwm-6.0.2.5.img)
5. Connect your phone to your computer to a APX MODE (Turn off the phone Remove the battery, holding down both volume buttons + / - Connect the USB cable)
6. introduce the "OK" and press Enter
to complete the phone goes off, disconnect the USB cable, insert the battery, and switch on the phone. phone boot into cwm 6.0.2.5
First, install ICS FULL STOCK V30A SU660.zip
then CivZ_SkyWalker_RF1.2_24RH-SU660.zip
reboot and enjoy!
We have STOCK firmware root, busybox, init.d, ext4
if you do not work then sew ussd requests through smartflash Baseband v30A Download here
I have been running all day! do everything at your own risk, I bear no responsibility.
SuRMaJ said:
30A Full Stock (root, busybox, init.d, ext4) for SU-660
This is a patched firmware from my r990 for SU-660
we need to flash
AIO TOOLKIT SU660
Download.....
I have been running all day! do everything at your own risk, I bear no responsibility.
Click to expand...
Click to collapse
Does this have wifi working?Because the stock ics roms i did try didnt.Also does it have internal and external sd cards working?
hackarchive said:
Does this have wifi working?Because the stock ics roms i did try didnt.Also does it have internal and external sd cards working?
Click to expand...
Click to collapse
wifi, internal and external sd cards working very good
Bluetooth doesn't work Only me?
Di HarD said:
Bluetooth doesn't work Only me?
Click to expand...
Click to collapse
Bluetooth doesn't work
I will do something
this is the most functional rom for this device.Dont use bluetooth alot though but it would be good to have a fix.
i installed dovakhiin ics for old bootloader, the problem was the same. ROM is good, but, sorry to say i need bluetooth, because i have elm327 bluetooth in my car)
anyone have any ideas how to fix bluetooth?
This ROM is the most stable one I've seen. Only the huge downside is the Bluetooth. I mean I used it alot. :/
No SMS 160 Charac problem... its just Perfect with a slight downsider.
Hoping for a fix on this
I can not fix myself, I need help, I think the Problem in the modules, who knows what modules are responsible for BT
SU 660 ICS Full Stock Kernel
I compiled a full stock kernel (zImage) using the SU660 defconfig from source for y'all , hope this helps and hope it works out , it got all default modules included.
Just flash with cwm. I don't have the su660 , I got the 990.
See attachments.
If it was helpful a thank you button isn't to hard to press :good:
Maybe I do a OC version for y'all with extra modules......
EDIT:
This is a zImage only with modules so you need to flash this over a already existing installation, or you need to make me a backup of your boot.img (ICS) , post it and I will make a full kernel (zImage + ramdisk = boot.img) I got the ramdisk of the p990 but I don't know if it is 100% the same as SU-660.
civato said:
I compiled a full stock kernel (zImage) using the SU660 defconfig from source for y'all , hope this helps and hope it works out , it got all default modules included.
Just flash with cwm. I don't have the su660 , I got the 990.
See attachments.
Click to expand...
Click to collapse
Thank you friend! It works!
instructions in the first post fixed!
civato said:
I compiled a full stock kernel (zImage) using the SU660 defconfig from source for y'all , hope this helps and hope it works out , it got all default modules included.
Just flash with cwm. I don't have the su660 , I got the 990.
See attachments.
If it was helpful a thank you button isn't to hard to press :good:
Maybe I do a OC version for y'all with extra modules......
EDIT:
This is a zImage only with modules so you need to flash this over a already existing installation, or you need to make me a backup of your boot.img (ICS) , post it and I will make a full kernel (zImage + ramdisk = boot.img) I got the ramdisk of the p990 but I don't know if it is 100% the same as SU-660.
Click to expand...
Click to collapse
so can I use this kernel on your ROM?
nice to see you helping this community
Internal SD Problem
SuRMaJ said:
30A Full Stock (root, busybox, init.d, ext4) for SU-660
This is a patched firmware from my r990 for SU-660
we need to flash
AIO TOOLKIT SU660
Download
mirror
ICS FULL STOCK V30A SU660
Download
mirror
SU-660 Full stock ICS Kernel (For help with the kernel thanks civato )
Download
throw the card ICS FULL STOCK V30A SU660.zip and SU-660 Full stock ICS.zip
1. run the AIO-ToolKit.cmd
2. press the number "4" (Change Partitions from OLD to NEW layout and vice versa)
3. press the number "1" (P 990 - ICS Partitions layout)
4. press the number "1" (P990-ICS-cwm-6.0.2.5.img)
5. Connect your phone to your computer to a APX MODE (Turn off the phone Remove the battery, holding down both volume buttons + / - Connect the USB cable)
6. introduce the "OK" and press Enter
to complete the phone goes off, disconnect the USB cable, insert the battery, and switch on the phone. phone boot into cwm 6.0.2.5
First, install ICS FULL STOCK V30A SU660.zip
then SU-660 Full stock ICS Kernel
reboot and enjoy!
We have STOCK firmware root, busybox, init.d, ext4
if you do not work then sew ussd requests through smartflash Baseband v30A Download here
I have been running all day! do everything at your own risk, I bear no responsibility.
Click to expand...
Click to collapse
My internal SD showing 4.64 GB only
any fix on this??
waiting for the miracle cure!
civato said:
I compiled a full stock kernel (zImage) using the SU660 defconfig from source for y'all , hope this helps and hope it works out , it got all default modules included.
Click to expand...
Click to collapse
You know, bluetooth seems to work with your kernel, civato!
i'll tell firmly that it works tomorrow when i test it fully.
U are AWESOME!!!!!!!! CIVATO *salutes*
civato said:
I compiled a full stock kernel (zImage) using the SU660 defconfig from source for y'all , hope this helps and hope it works out , it got all default modules included.
Just flash with cwm. I don't have the su660 , I got the 990.
See attachments.
If it was helpful a thank you button isn't to hard to press :good:
Maybe I do a OC version for y'all with extra modules......
EDIT:
This is a zImage only with modules so you need to flash this over a already existing installation, or you need to make me a backup of your boot.img (ICS) , post it and I will make a full kernel (zImage + ramdisk = boot.img) I got the ramdisk of the p990 but I don't know if it is 100% the same as SU-660.
Click to expand...
Click to collapse
replaced the boot.img from backup boot.img
Info
Here is the full boot.img (zImage+ramdisk).
I put it in a cwm flashable zip , so just flash it with cwm.
ps: @SuRMaJ I noticed that the zip you uploaded the boot.img is installed on "/dev/block/mmcblk0p5". That is old GB partition layout.
In the cwm zip I uploaded (see attachments) the boot.img is installed in "/dev/block/mmcblk0p6" = ICS partition layout. I think that you are using the ICS partition layout and not the GB layout so the one you posted installed boot.img in the wrong place if you used it.
This is the partiton layout of the ICS recovery you say users need to pick (P990-ICS-cwm-6.0.2.5.img)
# mount point fstype device [device2] fstype2
/recovery emmc /dev/block/mmcblk0p8
/boot emmc /dev/block/mmcblk0p6
/cache ext4 /dev/block/mmcblk0p2
/data ext4 /dev/block/mmcblk0p9
/external_sd vfat /dev/block/mmcblk1p1
/sdcard vfat /dev/block/mmcblk0p11
/system ext4 /dev/block/mmcblk0p12
This is the partition layout of GB:
# mount point fstype device [device2] fstype2
/recovery emmc /dev/block/mmcblk0p7
/boot emmc /dev/block/mmcblk0p5
/cache ext4 /dev/block/mmcblk0p2
/data ext4 /dev/block/mmcblk0p8
/external_sd vfat /dev/block/mmcblk1p1
/sdcard vfat /dev/block/mmcblk0p9
/system ext4 /dev/block/mmcblk0p1
Click to expand...
Click to collapse
I'm guessing you are just using the installation zip of the CM boot.img version which was build to use on old partition layout.
civato said:
Here is the full boot.img (zImage+ramdisk).
I put it in a cwm flashable zip , so just flash it with cwm.
ps: @SuRMaJ I noticed that the zip you uploaded the boot.img is installed on "/dev/block/mmcblk0p5". That is old GB partition layout.
In the cwm zip I uploaded (see attachments) the boot.img is installed in "/dev/block/mmcblk0p6" = ICS partition layout. I think that you are using the ICS partition layout and not the GB layout so the one you posted installed boot.img in the wrong place if you used it.
I'm guessing you are just using the installation zip of the CM boot.img version which was build to use on old partition layout.
Click to expand...
Click to collapse
replaced the boot.img from backup CWM
can be combined ICS-SU-660-Full_Stock_bootIMG.zip and SU-660-Full_stock_ICS-Kernel.zip?
after the installation of your ICS-SU-660-Full_Stock_bootIMG.zip
When I connect the phone tightly usb asleep, only helps to pull out the battery
The only way to make nandroid backup then restore it when you have Locked bootloader. Original thread:
http://forum.xda-developers.com/showthread.php?t=2005187
This is whirleyes famous Boot Menu Manager. I've been using it when I had Motorola RAZR.
I only tested nandroid backup and restore and zip install. Both working OK. Most BMM features probably not working and I personally don't want to test it as i don't like install ROM from scratch,
USE it only if you're LOCKED, for UNLOCKED bootloaders use Dexter's CWM or TWRP
What working:
1. Nandroid backup and restore
2. Zip install from External SDCARD
Not working:
1. Touch screen
2. Radio/Kernel flashing
3. Running second system
Install:
Unpack zip, run install.bat
When BMM appear on screen use Vol+/Vol- to enter BMM then Power to accept.
Credits:
All credits goes to whirleyes
Proceed at your own risk. Don't try this if you're not comfortable fixing your phone/troubleshooting/flashing
I want to flash te zaiben rom? Is that possible?
Sent from my LG-P880 using xda app-developers app
yeah as it doesnt change kernel/recovery i think
Sent from my LG-P880 using xda app-developers app
Where do I have to put the .zip files? My phone does not show me the archives i placed on my internal storage
how do I boot into the recovery ??
It goes to a bootscreen of the recovery but then it reboots normal
Sent from my LG-P880 using xda app-developers app
Nice... In recovery my device uses Motorola ADB driver and Motocast starts... (Drivers are installed for my old Moto Defy...)
mrlollog said:
Where do I have to put the .zip files? My phone does not show me the archives i placed on my internal storage
Click to expand...
Click to collapse
Mountpoints are fail... External SD works fine
This is recovery.fstab file from BMM, I only modified 4 mount points. If someone can look into it BMM is located:
/system/etc/bmm
Code:
###################
# Motorola spyder #
###################
# BMM NOTICE:
# - Keep mount point in boot order. This file will be used to generate init.fs.rc
#
# mount point fstype device second device or options
#
/system auto /dev/block/platform/sdhci-tegra.3/by-name/APP
/pds auto /dev/block/pds
/preinstall auto /dev/block/preinstall
/data auto /dev/block/platform/sdhci-tegra.3/by-name/UDA
/cache auto /dev/block/platform/sdhci-tegra.3/by-name/CAC
/ext vfat /dev/block/mmcblk1p1
/int vfat /dev/block/mmcblk1p1
lukas77 said:
This is recovery.fstab file from BMM, I only modified 4 mount points. If someone can look into it BMM is located:
/system/etc/bmm
Code:
###################
# Motorola spyder #
###################
# BMM NOTICE:
# - Keep mount point in boot order. This file will be used to generate init.fs.rc
#
# mount point fstype device second device or options
#
/system auto /dev/block/platform/sdhci-tegra.3/by-name/APP
/pds auto /dev/block/pds
/preinstall auto /dev/block/preinstall
/data auto /dev/block/platform/sdhci-tegra.3/by-name/UDA
/cache auto /dev/block/platform/sdhci-tegra.3/by-name/CAC
/ext vfat /dev/block/mmcblk1p1
/int vfat /dev/block/mmcblk1p1
Click to expand...
Click to collapse
Int and Ext are the same (/dev/block/mmcblk1p1)
Nice! Now we just need ability to load 2nd kernel like in defy roms. Good work!
Sent from my rooted P880
Will there be a new version which allows users to flash new kernels?
I'm not skilled enough to make modification, hopefully Whirleyes can do it in his free time or we can ask Dexter to look into scripts and maybe he can make it working.
lukas77 said:
I'm not skilled enough to make modification, hopefully Whirleyes can do it in his free time or we can ask Dexter to look into scripts and maybe he can make it working.
Click to expand...
Click to collapse
Thanks! Maybe look at the code for defy and other phones that already have 2nd kernel for ideas :thumbup:
Sent from my rooted P880
does this able to flash Zaiben ROM?
vinnong said:
does this able to flash Zaiben ROM?
Click to expand...
Click to collapse
I can't flash the zaiban rom, maby you Have more luck
Sent from my LG-P880 using xda app-developers app
Delete
Unlock and install real recovery: http://forum.xda-developers.com/showthread.php?t=2245836
OP I respect your work but this is no longer needed, mods should close this as no ROMs use locked BL
Sent from my rooted P880
FD1999 said:
Maybe some people don't want to unlock the BL yet?
Gesendet von meinem LG-P880 mit Tapatalk 2
Click to expand...
Click to collapse
Now that it is unlocked for all there will never be ROMs for locked bootloader, you could make backups yes, but if you're not flashing anything there isn't much point imo
Sent from my rooted P880
Greetings there....does this recovery works if i want to flash zip files? Like customization or anything other than flashing roms
Sent from my LG O4X
Simple answer: No
Afro said:
Simple answer: No
Click to expand...
Click to collapse
???
You can use BMM for installing zipped customizations. And Aroma Installer uses full display...
MultiSystem is a powerful tool for locked- and unlocked-bootloader Android devices with many features that at least includes the following:
Keeps stock system partition safe/rooted
Permenant root survival with proper use
MultiROM support via virtual ROMs
Unlimited number of virtual ROMs
Booting options to choose stock, primary, or secondary virtual ROM
Any of the virtual ROMs can work as a recovery replacement
Flashing multiple ROMs at the same time without a reboot
Ability to create/install ROMs on Linux to microSD card
Great performance & battery life on virtual ROMs
Recovery solution to install ROMs or Mods
Easy upgrade to newer versions of Android
Ability to safely apply OTA updates to virtual system
Permissive SELinux and other kernel tweaks
Safe flashing that doesn't trip KNOX flag on Samsung devices
Wrapper script runs via ADB or a Terminal Emulator on device
APK to manage all MultiSystem functions with a nice UI and extra options
Management for the best performance & user experience
Support for all Android devices with microSD card
Portability to almost all devices
Compatibility with all Android versions
Click to expand...
Click to collapse
Q&A
What is the concept behind MultiSystem?
It runs virtual Android ROMs on microSD, like booting multiple systems on a PC from different partitions/disks. So, your stock system partition is kept safe/rooted. It won't affect performance or anything (might even be better on the virtual system if you've high quality microSD & the device supports its speed). Also, you can freely modify any of the virtual systems & in the worst case, reboot the safe stock system or another working virtual system to recover. So, no root loss or potential damage to the original device partitions.
Click to expand...
Click to collapse
Is it a recovery or an APK tool?
It's a shell script that hijacks system at early boot & force Android to boot from the stock system partition or a virtual system IMG & an APK that manages all booting options, virtual ROMs, and works as a recovery replacement + extra features...
Click to expand...
Click to collapse
Does it work as a recovery replacement?
It IS a POWERFUL recovery replacement. You can do whatever you do in recovery with the APK. HOW? recovery does its magic b/c it doesn't depend on the system & has its own kernel/ramdisk. In MultiSystem, you can boot a virtual ROM from extSD that sure doesn't depend on stock system partition or any of the other virtual ROMs (it does depend on the kernel, which you can't flash on locked devcies anyway). Hence, install, backup, restore, ... & all recovery functions are all possible +++ more features since you're running a full ROM not just a recovery ramdisk like Safestrap.
Bottom Line: I think it's the best & most convenient recovery replacement ever for locked devices & it can also attract unlocked devices for the powerful features, MultiROM, and recovery from within ROM.
Click to expand...
Click to collapse
Can I use FlashFire along with MultiSystem?
Yes. MultiSystem is compatible with FlashFire & fully supports it on stock & virtual ROMs. So, you can use both/any of them for flashing to either a stock or virtual ROM. However, it's recommended to use MultiSystem when flashing to the stock system partition (shouldn't be needed anyway since you can always be safe & flash to your old/new virtual ROMs).
Click to expand...
Click to collapse
Does MultiSystem require FlashFire?
No, MultiSystem doesn't require FlashFire. They're fully combatible though.
Click to expand...
Click to collapse
Would the virtual ROM we install be exactly the one in the stock slot?
In MultiSystem APK, you can create a virtual ROM from stock system, a copy from other virtual ROM, a new IMG, a dev-provided ROM, a flashable .ZIP, ... etc. Literally, your virtual ROMs can be any stock or custom ROM that's compatible with your firmware/kernel.
Click to expand...
Click to collapse
How can it run virtual ROMs from external microSD card?
External MicroSD will be formated into 2 partitions:
exFAT or FAT32 for the 1st partition (your new external storage)
EXT4 for the 2nd partition (your MultiSystem partition)
It'll hijack the system & boot a virtual system from the 2nd partition. The 1st partition will be automatically detected as your extSD.
Click to expand...
Click to collapse
Can I run unrooted virtual ROM for work apps or any other reason?
Yes. You can add unrooted virtual ROM & reboot to it via MultiSystem APK.
Click to expand...
Click to collapse
How do you boot back into a different ROM?
MultiSystem APK manages all functions including ROM activation & reboot to current system, another stock/virtual system, download mode, recovery, ... etc.
Click to expand...
Click to collapse
Will it be OK to still store media like movies/photos/music to extSD?
100% OK; That's my setup a few months ago. 2 virtual ROMs in the SECOND extSD partition in EXT4 format while all personal data are stored on the FIRST extSD partition in exFAT or FAT32 format... TWO COMPLETELY DIFFERET PARTITIONS.
Click to expand...
Click to collapse
How much space are we going to have for virtual ROMs?
The size of the 2nd partition is optional (> 4GB) for your ROMs, but here is an estimated sizes:
1 Virtual ROM Uncompressed = ~2.7 GB ---> ready for running
1 Virtual ROM Compressed = ~1.5 GB ---> for full ROM backups
I'd say better allocate 4 GB for each ROM you plan to run. If you just need one virtual ROM to keep stock system safe, 4 GB 2nd extSD partition is enough; The remaining space is allocated for the 1st extSD partition as your external storage.
For me, I run Linux too from extSD via MultiSystem. So, I've 64 GB extSD card with two partitions 32 GB each.
Click to expand...
Click to collapse
Can I clear up space on an existing SD card and partition it while full or will the entire card need to be wiped and partitioned from scratch?
You need to backup all your files; it'll be wiped & repartitioned.
Click to expand...
Click to collapse
How can I swap microSD cards & be able to run virtual ROMs?
You can swap microSD cards as you wish provided that the device is powered off; don't remove the microSD card when running a virtual ROM. If the new microSD card doesn't include a 2nd parition of available virtual ROMs, the device will boot directly to the stock system.
Click to expand...
Click to collapse
Is there a specific sd card you recommended for this?
I personally have two microSD cards:
SanDisk Extreme Plus 64GB (Up to 80MB/s read speed)
Samsung 64GB PRO (Up to 90MB/s read speed)
You don't have to change your microSD card for MultiSystem; any card you use on your device should work just fine. The need for more speed is relevant when the device supports that speed & if you're going to buy a new card anyway that you may use with a newer device later.
Click to expand...
Click to collapse
Can I copy virtual ROMs to a new microSD card?
Yes. I'll add a feature for swapping microSD cards so that you can backup/restore virtual ROMs from/to the current extSD to/from internal storage as follows:
power off device
use MultiSystem APK to backup your virtual ROMs
insert the new properly formatted microSD,
power on device (it'll boot to stock system)
use MultiSystem APK to restore your virtual ROMs
use MultiSystem APK to activate one of your virtual ROMs
use MultiSystem APK to reboot to any of your ROMs
Click to expand...
Click to collapse
What about other data/cache partitions and internal storage?
Only system img's are in the extSD. All ROMs share all other partitions. This substantially improves the performance & you won't notice any difference between your stock & virtual ROMs. The reason for performance improvement is that EXT4 loop devices are very fast in reading but not in writing. Your system partition is read-only while data (for example) is read write & cache IMGs cause problems like Safestrap issues on ROM slots. Also, you don't have to worry about switching data/settings between ROMs (they're shared), but you just need to regularly backup your important data (which is healthy anyway).
Click to expand...
Click to collapse
Can your elaborate where data is stored?
The userdata partition is also shared; so, you'll have access to all your FULL storage partitions & all apps/data similarly on either stock or virtual ROMs. This also solves the Safestrap issue of having less storage on ROM slots...
Click to expand...
Click to collapse
Will mSDcard incur a significant performance penalty on some devices?
there's no diffrerence between virtual & stock ROMs in terms of performance & battery life. The reason is simple: loop devices associated with the READ-ONLY system IMG mounted from EXT4 partition using a high-quality microSD card IS very fast more than enough.
The read speed is faster than the device can operate anyway + the exact same device should perform on the lowest speed when reading/writing from/to the FAT/FAT32/ExFAT extSD card (where you store your files or even move apps!!!) anyway, which is much slower than the read speed of a loop device mounted from EXT4 partition.
That's why data partition is shared for many reasons, including the poor READ/WRITE performance.
Click to expand...
Click to collapse
If virtual systems are read only, how do we modify them? Do we have to boot to another multisystem rom to modify a virtual rom?
The stock system partition is mounted by default read only & so are the virtual systems. To modify a stock/virtual system, the MultiSystem APK remounts them read/write. You can modify the currently running virtual system, copy it & modify the copy, modify another stock/virtual system.
Click to expand...
Click to collapse
How is a corrupted virtual rom handled? Does it see it's bad and default to stock system?
At early boot, MultiSystem checks for the microSD & active virtual ROM to boot it. There's a boot menu that gives you options to select a stock/virtual system, but it crashes on LP. I'm debugging it, but all functions won't be affected if I removed it. To fail safe, you can remove the microSD card to boot to stock system & restore/repair your virtual ROMs.
UPDATE1: MultiSystem v1.0.1 now allows you to also switch to stock system on boot to repair corrupted virtual IMGs or any other reasons. More options will be added during boot to ultimately select another virtual system if the active IMG is not booting normally (e.g., bootloop after applying a mod or flashing a bad .ZIP).
UPDATE2: Now, on boot, you can choose from two primary/secondary virtual ROM or stock ROM. Flashing multiple ROMs at the same time without a reboot is now possible.
Click to expand...
Click to collapse
How to check if an IMG is corrupted using MultiSystem status?
Code:
Current System IMG: Test_Rom.img
Current System DEV: [B][COLOR="Red"]/dev/block/mmcblk0p23[/COLOR][/B]
When you see "/dev/block/mmcblk0p23"; it's the original system partition; so MultiSystem failed to boot Test_Rom.img, but it should be your current system.
So, the check is simple based on "Current System Device":
/dev/block/mmcblk0p23 = Stock System Partition
/dev/block/loop0 = Virtual System IMG
Note: The block device number (mmcblk0p23) may vary per device & per variant !
Click to expand...
Click to collapse
Does android do any maintenance whatsoever on stored data within /data or external sd? So if I have an app installed on 1 system and not on another system will android see it and clear the data?
No, all storage partitions are shared between ROMs. If you installed an app, it'll be availabe for all of them. Since on locked devcies we're limited to stock manufacturer-based ROMs, this makes the switch between ROMs very convinient (you don't have to worry about your changes/data/setup & storage space on the another ROM; all ROMs share everything except system). However, you should make regular backups in case a virtual ROM (probably with unsafe mods) results in bootloop due to your user data. In this case, it's safe to wipe data & selectively restore apps/data from backup(s). Another advantage of sharing all storage partitions is that your messages/emails/etc received on a virtual ROM are immediated synced (actually shared) to the other ROMs.
Click to expand...
Click to collapse
Will anything like Xposed modify the virtual ROM system IMG as opposed to the stock system IMG?
When you run a Virtual System, everything incldung kernel & apps are hijacked to speak to it as the original system.
Click to expand...
Click to collapse
Can we install AOSP ROMs on locked devices?
You can only install stock/manufacturer-based ROMs on locked devices while unlocked devices can use kexec or flash the required kernel to boot any AOSP/Stock ROMs. I've got a Note 4 Developer Edition & a lot of development is planned to go there (thanks to the unlocked bootloader!) More devices will get supported including unlocked TMO & international variants after adding more features untilizing the unlocked bootloader with kexec'd kernels.
Click to expand...
Click to collapse
Are there limitations to the combinations of ROMs that can be loaded on the "stock" and "virtual" slots? Can you mix KK and LP?
Yes, if they can run on the same kernel. LP won't run on KK kernels & so, you'd have to upgrade the firmware anyway. As for running mixed compatible Android versions, this is possible but your'd have to backup your data before switching ROMs; if it cause no issues, enjoy smooth switch & if it doesn't, do factory reset in recovery & restore your data backup. Backups via MultiSystem are painless.
Click to expand...
Click to collapse
Are applications installed once for each ROM slot that has that applicaiton installed, or can I share a game across ROMs (for instance?)
Everything is shared between ROMs, which is very good for storage & for easy switching. Just make regular backups of your sensitive data.
Click to expand...
Click to collapse
How there are no performance hits while internal storage memory was much faster than any microSD technology?
Read speeds from microSD is very fast compared to write speeds & since virtual ROMs are actually a virtual read-only systems (hence, MultiSystem), they provide a high performance. Moreover, again, read speeds from EXT4 loop devices are higher compared to physical partitions. They're very bad in writing, which we don't need for the read-only "system".
Click to expand...
Click to collapse
Is there a preferred "daily driver" ROM that should be installed in the stock slot?
Uses a stock ODEXED ROM on stock slot for better stability!
Click to expand...
Click to collapse
Is it based off of Safestrap?
Short answer NO. I've been working on MultiSystem & Safestrap for ~7 months. Earlier versions of MultiSystem (called, JasmineREC) was based on Safestrap, but it failed to support newer versions of Android mainly due to TWRP changes in the graphics/UI libraries that cause segmentation fault & the stock kernel framebuffer issues. Then, I decided to find another solution. However, the basic idea of system hijack is powered by Safestrap (or 2nd-init recoveries in general) & all the work done by @Hashcode is GREATLY appreciated.
Click to expand...
Click to collapse
How can it overwrite system files while running?
MultiSystem allows you to install safe mod's or a ROM in full or OTA-like update. It's strongly recommended to install .ZIP files NOT to the current system, b/c some files can not be overwritten while running. So, you can use backup function to copy the current system & install to the new img or any of your other virtual systems. You'll have several options to activate a virtual img & reboot directly to stock system, any virtual img you've activated, quick reboot, Download/bootloader, recovery,... etc.
Click to expand...
Click to collapse
How would I benefit from it if I'm only running Stock ROM or would there be no point for me to install it?
If you run a ROM on stock system, you're vulnerable to root loss unless/untill a new rooting method for LP comes out. MultiSystem gives you the option to run safe-to-mod virtual ROMs + recovery replacement + extra features.
Click to expand...
Click to collapse
Is there a way to convert a normal ROM .ZIP into MultiSystem .IMG?
Create or copy any of your IMGs, activate it & reboot to the active IMG! Then, use FlashFire to flash the ZIP file. However, the updater-script should be safe/compatible. Some devs mount the phyical partition, which will redirect everything to it!!
For example:
Code:
mount(“ext4″, “EMMC”, “/dev/block/mmcblk0p23″, “/system”);
will mount the original system partition; while
Code:
run_program("/sbin/mount", "-t", "auto", "/system");
will mount the current system (stock or virtual). This is recommended/safe.
Click to expand...
Click to collapse
Would a KitKat ROM work with multisystem even though my stock is Lollipop?
Any ROM requires a compatible kernel & modem. So, running KK ROMs requires flashing KK firmware (namely, kernel & modem). This may work with MultiSystem on other devices, especially if the bootlpoader is unlocked. For example, I plan to add features for Note 4 DevED to allow different Android versions (including AOSP, manufacturer-based, & probably Linux systems) by utilizing kernel swapping or execution.
Click to expand...
Click to collapse
When MultiSystem comes out will it be open sourced?
Most probably, haven't decided yet!
Anyway, here's the repository on GitHub: https://github.com/hsbadr/MultiSystem
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Video Tutorials
A quick preview of MultiSystem v1.0 tested on Lollipop for VZW Note 3. The video has been captured on a stable virtual ROM of JasmineROM v5.0.1. It's FULLY compatible with FlashFire on virtual/stock systems. More devices will get supported as well, after required testing.
Facebook: https://www.facebook.com/hsbadr/videos/vb.331488823689599/428178174020663
How to check if you are running a Stock/Virtual System?
There're many ways to check whether you're running a Stock or Virtual system. MultiSystem app should include this simple check at some point. That's important to avoint ruining the Stock system & keep it safe. To make it clear to NOOBZ & anyone who's requesting "another" proof even though I owe hime nothing. Very weird!
Anyway, BusyBox mountpoint applet can print the current block/device mounted to /system mountpoint by running the following command:
Code:
busybox mountpoint -n /system
The stock system is mounts the original system partition:
Code:
[B][COLOR="Red"]/dev/block/mmcblk0p23[/COLOR][/B]
while the virtual system mounts a loop device associated with a system IMG:
Code:
[B][COLOR="Blue"]/dev/block/loop0[/COLOR][/B]
Here're two videos for both stock & virtual systems...
UPDATE:
Now, you could run the following command to print the current system (stock or virtual) and the system device (physical partition or loop device):
Code:
MultiSystem status
Note: The block device number (mmcblk0p23) may vary per device & per variant !
How to repartition microSD card for MultiSystem?
You can use any tool/program for partitioning on Android, Linux, Mac, or Windows. For example, MiniTool Partition Wizard is a good partitioning tool for Windows. So, let's use it for this task. Simply, you need to follow this PDF tutorial (thanks to @carl1961). In sum:
Step 1: delete old partitions on SD card
Step 2: create FAT32 PRIMARY partition
Step 3: create EXT4 PRIMARY partition
Then, apply changes (note that the program UI may get changed in newer versions).
Notes:
This partitioning tutorial doesn't create PRIMARY partitions (it creates logical partitions). So, you need to change "Create As" from "Logical" to "Primary" when creatig a partition.
The sizes of the two partitions are arbitrary depending on number of ROMs you plan to install on the 2nd EXT4 partition.
The 1st partition (check size) is automatically detected as your external storage
In Terminal Emulator or ADB shell, check the existence of the two partitions by running the following command (in red):
Code:
[email protected]:/ # [COLOR="Red"]ls -l /dev/block/platform/msm_sdcc.3/[/COLOR]
drwxr-xr-x root root 2015-05-02 21:08 by-num
lrwxrwxrwx root root 2015-05-02 21:08 mmcblk1 -> /dev/block/mmcblk1
lrwxrwxrwx root root 2015-05-02 21:08 mmcblk1p1 -> [COLOR="Blue"]/dev/block/mmcblk1p1[/COLOR]
lrwxrwxrwx root root 2015-05-02 21:08 mmcblk1p2 -> [COLOR="Blue"]/dev/block/mmcblk1p2[/COLOR]
/dev/block/mmcblk1p1 is mounted by Android as your external storage.
/dev/block/mmcblk1p2 is NOT mounted & will be your MultiSystem partition.
Click to expand...
Click to collapse
How to check microSD card partitions for MultiSystem?
You need to correctly repartition microSD card into two partitions:
exFAT or FAT32 for the 1st partition (your new external storage)
EXT4 for the 2nd partition (your MultiSystem partition)
Use the directions in this post!
You should check your 2nd SD partition in EXT4 format mounted to /MultiSystem:
check that the /MultiSystem directory exists after a reboot
check that the 2nd SD partition (/dev/block/mmcblk1p2) is mounted to /MultiSystem by running the following command in Terminal Emulator or ADB shell:
Code:
mount | grep /MultiSystem
The output should be:
Code:
/dev/block/mmcblk1p2 /MultiSystem ext4 rw,seclabel,relatime,data=ordered 0 0
How to check MultiSystem Installation?
The 1st thing to do after installing MultiSystem is to check the /MultiSystem directory & its contents (it shouldn't be empty!). Then, check usage by running the following commands in Terminal Emulator or ADB shell:
Code:
su
bash
MultiSystem
If it retuns "MultiSystem not found" or permission denied, try to use open MultiSystem app to Update Configurations & try again. If this does't fix it, try the following command:
Code:
/MultiSystem/bin/MultiSystem
This should work if you've MultiSystem binaries installed in (extracted to) /MultiSystem directory. If so, you can create a symlink in /system/xbin as follows:
Code:
mount -o remount,rw /system
ln -sv /MultiSystem/bin/MultiSystem /system/xbin/MultiSystem
Then, test it by running:
Code:
MultiSystem
The last thing before using it is to check the boot options: reboot & monitor the GREEN LED indicator for 3 seconds (change in the app) , which give you the following options:
Volume UP = Primary virtual ROM
Volume DOWN = Secondary virtual ROM
HOME KEY = Stock System
Sure, you should have installed one or more virtual ROMs.
Backup & restore or creating/installing a virtual ROM are easy as copy & paste: all img's will be at
Code:
/MultiSystem/img/system
To backup a virtual/stock system, you have many options:
Use create function to create from stock system
Use copy function to copy the IMG
Copy & paste with a new name
Use FlashFire (fully supported on virtual/stock ROMs)
...
If you've IMG mounting issues, run the following commands:
Code:
mount -o remount,rw /system
busybox ln -sv /proc/self/mounts /system/etc/mtab
If this doesn't help, try mounting from Terminal Emulator or ADB shell after selecting the IMG in MultiSystem app, by running the following command:
Code:
MultiSystem mount virtual
I've read up on the Q&A and development op. After following the instructions here is my current situation. I have the multisystem installed on a stock rooted rom(NCE w/OA1 bl). My ext sd is partitioned in two primary sections. One Fat32 and the other ext4. 50gb and 20(ish)gb. The app opens fine. I clicked install and received a toast notification on the bottom. Then I tried to flash the multisystem zip in safestrap. Flashing in multisystem was not possible for me. When I selected the zip from the multisystem "select file" option nothing appeared in the space under the option. When flash was pressed nothing happened. Anyways, I ended up flashing in safestrap. It appeared the the script was ran and my phone rebooted. The op said to wait for the green led light and set selinux to permissive. Never got that screen. I've tried it a few times now with same results. After I flashed the multisystem zip in safestrap and not getting the green led and multisystem screen on boot I tried flashing the zip in multisystem. Same result, I am unable to flash from the app. It lets me select the file. But after that it doesnt appear in the items to be flashed and pressing the flash button is met with a toast but nothing happens. I'm stuck any help is appreciated. Thanks.
stupid question. Do you have to be rooted for this to work?? Tried on locked lollipop bootlader from att and it force closes.
ecera said:
I've read up on the Q&A and development op. After following the instructions here is my current situation. I have the multisystem installed on a stock rooted rom(NCE w/OA1 bl). My ext sd is partitioned in two primary sections. One Fat32 and the other ext4. 50gb and 20(ish)gb. The app opens fine. I clicked install and received a toast notification on the bottom. Then I tried to flash the multisystem zip in safestrap. Flashing in multisystem was not possible for me. When I selected the zip from the multisystem "select file" option nothing appeared in the space under the option. When flash was pressed nothing happened. Anyways, I ended up flashing in safestrap. It appeared the the script was ran and my phone rebooted. The op said to wait for the green led light and set selinux to permissive. Never got that screen. I've tried it a few times now with same results. After I flashed the multisystem zip in safestrap and not getting the green led and multisystem screen on boot I tried flashing the zip in multisystem. Same result, I am unable to flash from the app. It lets me select the file. But after that it doesnt appear in the items to be flashed and pressing the flash button is met with a toast but nothing happens. I'm stuck any help is appreciated. Thanks.
Click to expand...
Click to collapse
You can't use the flash function until you correctly install MultiSystem. Follow OP instructions & install MultiSystem from within app; then, flash the ZIP file via FlashFire. If this doesn't work for you, send me the log file (if created at all) & /system/bin/e2fsck.
Also, you may get assistance from VZW N3 users here: http://forum.xda-developers.com/verizon-galaxy-note-3/help/qa-multisystem-android-t3089530
Billy06010 said:
stupid question. Do you have to be rooted for this to work?? Tried on locked lollipop bootlader from att and it force closes.
Click to expand...
Click to collapse
Root access is required.
Here are the two files. I odined to NCE w/OA1 bootloader because I ended up soft bricking after a failed flash attempt of the Multisystem.zip in flashfire.(no idea why that happened, I probably goofed up somewhere). Followed muniz's upgrade method for lollipop to keep root OC4 w/OA1 bootloader. Followed the steps as you said to properly install Multisystem. Same result. When I'm on lollipop when I click to add a file in the Multisystem apk it doesn't even open up the files. As it did when I was on 4.4.2 NCE. That's one difference I noticed. The reason I updated after I Odined to NCE stock was that the phone was really laggy. Overall it was the same result for me trying to install Multisystem. Again, I appreciate your help. Thank you.
I got this installed and everything looks correct, i dont see any green led on boot though. Do you need to have a second rom installed for mulisystem to show up?
Sent from my twi5ted SM-G900A using Tapatalk
ecera said:
Here are the two files. I odined to NCE w/OA1 bootloader because I ended up soft bricking after a failed flash attempt of the Multisystem.zip in flashfire.(no idea why that happened, I probably goofed up somewhere). Followed muniz's upgrade method for lollipop to keep root OC4 w/OA1 bootloader. Followed the steps as you said to properly install Multisystem. Same result. When I'm on lollipop when I click to add a file in the Multisystem apk it doesn't even open up the files. As it did when I was on 4.4.2 NCE. That's one difference I noticed. The reason I updated after I Odined to NCE stock was that the phone was really laggy. Overall it was the same result for me trying to install Multisystem. Again, I appreciate your help. Thank you.
Click to expand...
Click to collapse
It seems that you're missing some steps here. Could you please follow or this post or this one, but with skipping any device-specific steps? Just read that post to understand/find the step(s) you've missed. Also, before doing anything, you can check MultiSystem installation: http://forum.xda-developers.com/showpost.php?p=60554742&postcount=6
Rakuu said:
I got this installed and everything looks correct, i dont see any green led on boot though. Do you need to have a second rom installed for mulisystem to show up?
Click to expand...
Click to collapse
Which version have you installed? The latest version fixes LED indicator for S5 & S4.
hsbadr said:
It seems that you're missing some steps here. Could you please follow or this post or this one, but with skipping any device-specific steps? Just read that post to understand/find the step(s) you've missed. Also, before doing anything, you can check MultiSystem installation: http://forum.xda-developers.com/showpost.php?p=60554742&postcount=6
Click to expand...
Click to collapse
I followed the steps as explained in the two posts you quoted. Same result, no green LED after flashing the zip. I went to terminal emulator after flashing the zip and performed the command "mount | grep /MultiSystem" and nothing happens. I just get a new line for a different command. I went into /MultiSystem in root browser. Folder is empty. Not sure if that's normal. On a side note, Is there anyone on ATT S5 running rooted Lollipop that has successfully installed MultiSystem that can chime in?
ecera said:
I followed the steps as explained in the two posts you quoted. Same result, no green LED after flashing the zip. I went to terminal emulator after flashing the zip and performed the command "mount | grep /MultiSystem" and nothing happens. I just get a new line for a different command. On a side note, Is there anyone on ATT S5 running rooted Lollipop that has successfully installed MultiSystem that can chime in?
Click to expand...
Click to collapse
Ok, MultiSystem v1.3 will get released today.
hsbadr said:
Ok, MultiSystem v1.3 will get released today.
Click to expand...
Click to collapse
You are awesome and thanks again for helping me out.
hsbadr said:
Ok, MultiSystem v1.3 will get released today.
Click to expand...
Click to collapse
I have the latest one, my /Multisystem has some folders in it, mount | grep /Multisystem comes upbwoth proper output and running Multisysyem does give an output. Should i turn on runnkng at boot in the settings? Or is something broke that you're going to fix in 1.3?
Sent from my twi5ted SM-G900A using Tapatalk
Rakuu said:
I have the latest one, my /Multisystem has some folders in it, mount | grep /Multisystem comes upbwoth proper output and running Multisysyem does give an output. Should i turn on runnkng at boot in the settings? Or is something broke that you're going to fix in 1.3?
Click to expand...
Click to collapse
No, the on-boot commands is device-spcific kernel tweaks that are currently disabled. Check changelog in the main development thread. Mainly, it now has an option automatically mount the stock or secondary virtual IMG on boot. This has some flashing-releated considerations that I'll explain ASAP.
ecera said:
You are awesome and thanks again for helping me out.
Click to expand...
Click to collapse
You can consult @Rakuu on his successful installation of 1.3.
hsbadr said:
You can consult @Rakuu on his successful installation of 1.3.
Click to expand...
Click to collapse
I just want to double check, i'm not supposed to get any screen right? Just the green led which im supposed to press a key after seeing?
Sent from my twi5ted SM-G900A using Tapatalk
Quick summary, I can not:
mount -o remount,rw /system in normal mode even with root permission. Error is "Device busy"
modify files in /system in twrp and keep it persistent. It somehow roll back to the stock state after reboot into normal mode.
I'm a long-time linux user, and fairly familiar with rooting in pre-nougat versions. My previous phone is Oneplus-X in LineageOS-14, and I could do whatever I like with the system partition. Recently I received a P9 as present. I updated the rom to B377 and flashed OldDroid's TWRP-3.1.0+phh su. But I can not find a way to modify the /system partition. I need to change a lot of things, like /system/etc/hosts, adding apk into /system/priv-app, etc.
Could someone help?
ccaappton said:
Quick summary, I can not:
mount -o remount,rw /system in normal mode even with root permission. Error is "Device busy"
modify files in /system in twrp and keep it persistent. It somehow roll back to the stock state after reboot into normal mode.
I'm a long-time linux user, and fairly familiar with rooting in pre-nougat versions. My previous phone is Oneplus-X in LineageOS-14, and I could do whatever I like with the system partition. Recently I received a P9 as present. I updated the rom to B377 and flashed OldDroid's TWRP-3.1.0+phh su. But I can not find a way to modify the /system partition. I need to change a lot of things, like /system/etc/hosts, adding apk into /system/priv-app, etc.
Could someone help?
Click to expand...
Click to collapse
Hopefully this might help:
1. revert back to unmodified boot image (in TWRP flash from here[/URL or restore your backup from the unmodified boot image] , leave anything else untouched (especially TWRP 3.1.0-0 for EMUI 5)
2. flash this [URL="https://forum.xda-developers.com/showpost.php?p=71588837&postcount=102"]SuperSU image in TWRP (read the comments in the post please ... single bootloop ... then everything is ok and rooted)
3. install JRummy's BusyBox from Google Play (Stephen's won't work)
You are done and good to modify /system.
Note: resulting earthquakes, thunderstorms and spring floods from this work are solely under your own responsibility :laugh:
hakaz said:
Hopefully this might help:
1. revert back to unmodified boot image (in TWRP flash from here[/URL or restore your backup from the unmodified boot image] , leave anything else untouched (especially TWRP 3.1.0-0 for EMUI 5)
2. flash this [URL="https://forum.xda-developers.com/showpost.php?p=71588837&postcount=102"]SuperSU image in TWRP (read the comments in the post please ... single bootloop ... then everything is ok and rooted)
3. install JRummy's BusyBox from Google Play (Stephen's won't work)
You are done and good to modify /system.
Note: resulting earthquakes, thunderstorms and spring floods from this work are solely under your own responsibility :laugh:
Click to expand...
Click to collapse
1. I did a backup of boot partition before phh root, so should be able to restore the backup, instead of download the boot partition from others?
2. Is systemless supersu binaries need be individualized for every phone? Can I download systemless supersu from somewhere more semi-official? I'm not exactly comfortable installing zips from random links. ()
Ad 1. Till now rooting on our P9 works through injection of the su mounting routine into the kernel in boot section (if using a modified kernel + su installation or modifying the kernel during su installation itself doesn't make a difference). So any su installation modifies the boot section and you mess things up if you try to install another su on top of the other. Therefore reverting to the original boot image is mandatory before installation of another su.
Ad 2. The su is compiled against different platforms not phones (in our case arm64). So @Chainfire has the different platform variations in his package. The "shady" package in our case is basically the v2.79 stable version of 12/20 2016 (you can unpack both packages and compare them against each other, they are bit for bit equal) but has an P9 specific injection routine to modify the kernel. After installation you have pure su v2.79 stable on board - not more, not less.
Sorry, "normal" SuperSU packages won't work due to lacking the kernel modification (phh uses a modified kernel instead you have to flash separately on P9).
Cheers!
hakaz said:
Ad 1. Till now rooting on our P9 works through injection of the su mounting routine into the kernel in boot section (if using a modified kernel + su installation or modifying the kernel during su installation itself doesn't make a difference). So any su installation modifies the boot section and you mess things up if you try to install another su on top of the other. Therefore reverting to the original boot image is mandatory before installation of another su.
Ad 2. The su is compiled against different platforms not phones (in our case arm64). So @Chainfire has the different platform variations in his package. The "shady" package in our case is basically the v2.79 stable version of 12/20 2016 (you can unpack both packages and compare them against each other, they are bit for bit equal) but has an P9 specific injection routine to modify the kernel. After installation you have pure su v2.79 stable on board - not more, not less.
Sorry, "normal" SuperSU packages won't work due to lacking the kernel modification (phh uses a modified kernel instead you have to flash separately on P9).
Cheers!
Click to expand...
Click to collapse
Thanks buddy! I flashed systemless supersu, and stucked in infinite bootloop(it is only once in your post), probably because my model is EVA-AL00. I have to restore the previous boot.img.
ccaappton said:
Quick summary, I can not:
mount -o remount,rw /system in normal mode even with root permission. Error is "Device busy"
modify files in /system in twrp and keep it persistent. It somehow roll back to the stock state after reboot into normal mode.
I'm a long-time linux user, and fairly familiar with rooting in pre-nougat versions. My previous phone is Oneplus-X in LineageOS-14, and I could do whatever I like with the system partition. Recently I received a P9 as present. I updated the rom to B377 and flashed OldDroid's TWRP-3.1.0+phh su. But I can not find a way to modify the /system partition. I need to change a lot of things, like /system/etc/hosts, adding apk into /system/priv-app, etc.
Could someone help?
Click to expand...
Click to collapse
Same here with Oneplus 3T.
I just posted in another post (Google Pixel).
There I just guess it was a new encription way, now Im sure, all three devices with Android 7.1.1.....