Related
This project is now discontinued and will recieve no further updates nor support.
First of all, thanks petter (https://github.com/havlenapetr), Czech Samsung Galaxy developer, for idea and source codes.
What do I mean?
You have one ROM in internal memory as usual, and another one in folder on SD card ext partition. You can easily switch between them - just move rom from ext partition to some backup folder.
See guide in second post
How is it done?
Lets look on how android boots - its (roughly) like that:
1. Bootloader - forks between recovery, fastboot and normal boot
2. Linux kernel - Unpacks its initrd, loads drivers and many more things, not important now
3. Init - kernel runs this program, which mounts android partitions, sets correct permissions to files, starts services, and in the end, starts android itself
4. Android - Dunno much about it yet, anyway not important now
So, what we need to do is mount something else than internal memory in init. Init parses & runs simple scripts, which makes it simpler to mount sdcard folders.
We need to add mknod and bind mounting to init binary. Unfortunately, we dont have sources of init modified by LG (that thing is three(!) times larger than init compiled from AOSP, what the hell is in there?!). That is solved by running modified init, which parses "preinit.rc" with mounts and then runs LG init.
Commit: https://github.com/Tasssadar/init/commit/aa3604ca90f5ef9b688fdc2e3cc865aa29a54809
preinit.rc: https://github.com/Tasssadar/init/blob/b4e701e8bc4831fadbefa64be48300139dcc2023/ramdisk/preinit.rc
This would be all, if original LG init would not remount /system and /data from internal memory. Also, nearly every ROM has different init.rc, and wont boot without it.
To solve this, I created "import_boot" command in init, which copies *.rc files and LG init from ramdisk(well, its only folder with these files extracted from ramdisk for now) on sdcard ext partition. This command also puts comments out every line with mount /data, /system or /cache in init.rc file, so LG init wont remount them.
Commit: https://github.com/Tasssadar/init/commit/dc3fa50d65d1221a4fb819d8ee616765ee043e83, https://github.com/Tasssadar/init/commit/f7bc141b1e4b7d214e49d4bb005c71237231436c and https://github.com/Tasssadar/init/commit/1cde6b6a093d4ac1f961e610c5229605bc517b52
Format of ROM on ext partition:
All files from paritions in internal memory copied to sd ext partition with preserved owners and permissions(!).
So, when I copy data, I do "cp -r -p /data/* /sd-ext/multirom/rom/data/" (I suggest to run this via adb shell while in recovery).
Currently, I mount /system, /data and /cache from sdcard. If one or more of these folders does not exist, its equivalent from internal memory is used.
It would be nice to have *.img files from nandroid backups instead of this, but as far as I know, they cant be just mounted.
As for *.rc files, I put them into /sd-ext/multirom/rom/boot folder. I would like to just copy boot.img and extract files in init, but I did not find way to extract it when I have hardly STL usable in init. I'd like to use kernel's internal decompressor, but I dont know how.
Limitations
- Both ROMs must be compatible with one kernel - kernel is already loaded in init
- ROMs must be for same baseband, obviously
- Kernel modules(wifi, for example) of both ROMs must be compatible with one kernel. That can be easily solved by copying modules from one ROM to another, though.
- It will be slower than internal memory.
Integration with recovery
Definitely possible & usefull. This is integration in my modified AmonRa recovery: https://github.com/Tasssadar/Amon-R...mmit/bd0232f7379993c296b0223973b81e8c55dc3ee2
Security risk
/system on sdcard can't be mounted read-only - I'd have to mount whole sdcard read-only. This is possible security hole, but you cant do much without root anyway, because of permissions. And if you have root, it does not matter if its read-only or not.
Conclusion
So, it is possible to have dual-boot. You can use it to develop ROMs(you can directly edit data in /data and /system), as backup ROM when you are testing something in internal memory which does not boot, and you need to call someone or when our devices will be so old that bad blocks in internal memory wont allow us to boot
But, as you can see, It is not something that average user could do, at least not yet. Maybe I could modify recovery to do everything for the user (copy data from /system, /data and /cache, extract *.rc files from boot) and create some flashable ZIPs which would modify the init.
But there are some problems - some ROMs may not be compatible with this and there are multiple recoveries out there, but theres not single one which is only for our phone - both AmonRa and ClockworkMod are developed for wide range of devices. Yes, both of them can be modified, but I doubt they creators would accept such inflexible and device-specific thing.
What do you think, is it worth it?
Tested ROMs (first one is in internal memory, second one is on SDcard)
Working:
Megatron and stock v10a ROM - stock rom is slow
Megatron and devoid #froyo-final - like ten times faster than stock xD
LightRom(2.2.2) and devoid #froyo-final (and vice versa)
Megatron and Megatron - both ROMs can have a2sd
Megatron and Mik's CM7 6.5.8 - since v2
Gingerbread 2.3.4 from Optimus Net and CM7 6.6.1 (thx eduardogouveia for testing)
Stock 2.2.2 and CM7 6.5.8 (thx eduardogouveia for testing) - if you have ext4 partition, you need custom kernel for stock ROM.
.void 2.3.4 and stock V20B (thx diazneoones for testing)
CM7 6.5.8 and .void 2.3.4 (thx diazneoones for testing)
CM7 nightlies and Lupohirp's СM9 (thx aquapp for testing)
Not working
None found yet, but when CM7 is on sdcard, it looses root. Trying to figure out why. - fixed in v10
PS: I hope I explained it correctly, not exactly good at this. Do not fear to ask, if you don't understand something.
OK, here goes guide for average user. This is still highly experimental feature, keep that in mind. Backup, backup backups and backup them to PC, read whole guide first, I am not responsible for your bricked phone etc.
GUIDE:1. Requirements
Ext4/Ext2/Ext3 partition on SDcard big enough to hold all files from /system and /data, which is from 170mb to 400mb (depends on ROM and apps installed), so I think 512mb partition is minimum (if its 90% or so free).
Modified recovery. Only AmonRa and CWM version is available at this time, TeamWin is coming "soon". You can find flashable zip at the bottom of this post, flash it before you proceed to next move. If something goes wrong, you can restore your recovery with zips from here.
Kernel with ext2/3/4 support, which is basically every but stock
Both ROMs you wanna use must be compatible with same kernel. See Limitations in previous post
2. MultiROM instalation
- Via MultiROM Mgr application
I recommend you do nandroid backup before installing via this app.
Download MultiROM Manager (link at the bottom of this), tap to "Tap to install via this app" and wait. As simple as that. Mgr will also install recovery for you (It will ask you which one, you can select AmonRa, CWM and none). App can check & install update, too.- Via recovery
Just download multirom.zip at the bottom of the post, make nandroid backup and flash it. Your current ROM will be the one in internal memory, we will setup the one on the SDCard in next move.
Now, try to reboot the phone (boot will take little longer, because it has to mount ext partition). If it boots up correctly, then its OK - your ROM is supported. If not, then restore your nandroid backup and post your ROM name here, maybe I'll try to make it working.
3. Setup ROM on the sdcard
Make nandroid backup (I am not kidding, you will need this one), flash ROM which you wanna to have on SDcard, do the first boot (because it will create dalvik-cache, and you dont wanna do that when its already on sdcard) and reboot to recovery again.
Go to "MultiROM options" menu and select "Create from current ROM". It will do everything for you (it takes time, though). ROM on the sdcard is placed in /sd-ext/multirom/rom/, backups are in /sd-ext/multirom/backup/.
Restore nandroid backup from beggining of this step and reboot. Wait until Boot manager shows up, and select SDcard as boot location. ROM from sdcard should boot. If your ROM from internal memory boots or if its stuck, something got wrong and you should restore from backup.
4. MultiROM recovery menu description
Active/deactive state is for recovery only, you can boot ROMs from backup in boot manager - that means its N-times boot rather than dual-boot.
When not active(boot from internal memory):
Activate (move from backup) - when you already have backup, this will move it to active folder (fast).
Activate (copy from backup) - same as above, but it copies it instead of moving
Create from current ROM - pretty self-explanatory
Create from ZIP file - see http://forum.xda-developers.com/showthread.php?p=22194117#post22194117
When active(boot from sdcard):
Deactivate (move to backup) - Moves current ROM to backup folder, so next boot will be from internal memory
Backup - Creates backup of current ROM
Erase current ROM - Deletes current rom, next boot will be from internal memory
Copy modules from int mem - Copies modules from ROM in internal memory to SDcard. Try this if WiFi does not work in SDcard ROM.
Flash ZIP - flash ZIP file to ROM on SD card, for example gapps.
5. Config file:
It is recommended to use Multirom Manager(see bottom of this post) to change config file.
File itself is placed on sdcard and its name is multirom.txt. Description of its contents is in this post(post is updated if something changes): http://forum.xda-developers.com/showthread.php?p=20045183#post20045183
6. Key bindings:
Since v11, you also can control MultiROM via touchscreen.
Anywhere: Hold Power button to shut down the phone
While on main screen:
VolUp/Down - list between actions
Menu - Confirm action
Back - Reboot to recovery
Power button - Sleep mode
While playing tetris
VolUp - return to main screen
VolDown - pause
Menu - move the piece to left
Home - hard-drop
Back - rotate piece
Search - move the piece to right
FAQ:Q: It is slow!
A: Its sdcard. It just is slower than nand memory.
Q: It does not work with my ROM
A: Post your ROM combination here, maybe I'll see to it.
Q: When do I need to reflash?
A: When you flash new ROM or do something which rewrites boot partition. Most (if not all) kernels are using Koush's AnyKernel, so they should not cause any problems.
Changelog & Download:(Always flash newest version)
Uninstaller: http://www.mediafire.com/?3eco51f2t0at77o (info here)
Changelog AND DOWNLOAD LINKS have moved to github: http://tasssadar.github.com/multirom/
Recoveries
AmonRa - based on 3.06: http://www.mediafire.com/?ld9g81igvze7na0 (9th March 2012 21:57)
AmonRa - based on 2.2.1: http://www.multiupload.com/7Y5HHNEPOT (20th October 2011 22:29)
CWM: http://www.mediafire.com/?6rfw0qbrddzq5d8 (9th March 2012 21:57)
TWRP: http://www.mediafire.com/download.php?o8kphxmfk9l01tl (21st October 2012 23:49)
MultiROM Manager app
http://forum.xda-developers.com/showthread.php?p=20610052#post20610052
(Always use newest version)
v24 - http://www.mediafire.com/download.php?1xy52tamzepibrx (TWRP support)
v21 - http://www.mediafire.com/?u9c3bmfbtf57dtm (Add charger settings)
v18 - http://www.mediafire.com/?g1lpsp66jc1cb1b (Add boot location settings)
v17 - http://www.mediafire.com/?l1li51sseaisz5j (Add brightness setting)
v15 - http://www.multiupload.com/B65WPFMFXP (Show & reset tetris high score)
v14 - http://www.multiupload.com/FWB5UBSMO1 (Updater now also check for app update, some minor fixes)
v13 - http://www.multiupload.com/NYYBX9CAFD (Update translations, add support for optimus V - http://forum.xda-developers.com/showthread.php?p=20657898#post20657898)
v11 - http://www.multiupload.com/1L3294ZAU7 (Fix mount issues on some roms, add menu to main screen, add link to xda)
v10 - http://www.multiupload.com/B3AVSFKDOW (Create /sd-ext/multirom folder on install)
v9 - http://www.multiupload.com/WW7TUNP7RY (read http://forum.xda-developers.com/showthread.php?p=20624306#post20624306)
v8 - http://www.multiupload.com/6OD7RQ74OE
v7 - http://www.multiupload.com/DJKMUGIVJ0
Something like this have the Xperia series. Maybe u find something u can use there.
Sent from my LG-P500 using XDA App
so this means we can test roms without replace current ??
Yes. Is my english so bad or you just don't read what I wrote?
Tasssadar said:
Yes. Is my english so bad or you just don't read what I wrote?
Click to expand...
Click to collapse
For the last time,you're speaking english perfectly p)
how to install your zip of amonra recovery i try but the recovery says that the zip dont have updatescript so it gives error....
i dont understand how to do this but ii´m searching this for a long time,if you can make a more frindley all user guide it will be very cool thankyou and hope you could doot....
*sigh* once again, this is [dev] thread, this is not something you can flash, at least not yet. You would know that, if you'd read whole post.
eduardogouveia said:
how to install your zip of amonra recovery i try but the recovery says that the zip dont have updatescript so it gives error....
i dont understand how to do this but ii´m searching this for a long time,if you can make a more frindley all user guide it will be very cool thankyou and hope you could doot....
Click to expand...
Click to collapse
[dev] means this is not something ordinary. Don't know what it is, don't mess with it.
Tasssadar said:
*sigh* once again, this is [dev] thread, this is not something you can flash, at least not yet. You would know that, if you'd read whole post.
Click to expand...
Click to collapse
Don't worry, you'll get more "hao cán i flush this into ma phones?" questions, good luck.
sounds like fun
thanks for bringing it for optimus one
but i have one question for you
I think in future kernel changing will also possible
because if we can flash kernel then we can make it to change
right?
Tasssadar said:
Yes. Is my english so bad or you just don't read what I wrote?
Click to expand...
Click to collapse
Maybe you just helped us with boot manager app
Sent from my LG-P500 using xda premium
I read the post but since the download you have is of a amonra recovery modified by you,i thougt that was a regular zip and only then make by abd the tutorial,thats why hi also ask a more friendly use because i now its not for averager use no need to get obset however im still happy hi was searching for that so hi dont mind waiting you make it more simple... sorry if that ofend you or franco lol we have to learn and its very hard now how to develop without having the proper nowledge like you all devs have and hi respect every dev even of he just make a simple app,by the way just dont send me to school lol where could i learn the bases to umderstand how to program java and then develop im asking this because all books hi find rekire previous nowleged of some progaming could some dev. Pointing me somewhere where i could learn and please dont be rude im just asking because i just dont love i want and hi will learn...
And baking to the thread what you find for me is one of the best and most important for our phones thanks a lot now just wainting a day everybody could use your work thank you
Sent from my LG-P500 using XDA Premium App
So your main question is: "Is it worth it?"
I would say, "Hell yeah it is!" but then again I do not have the know-how to pull something like this off.
If you decide to go ahead with it, I wish you the best of luck =P
I just modified Koush's AnyKernel so that it can modify ramdisk's content, so it is possible to install it with .zip file via recovery. I will add some modified version of CWM & AmonRA, create some walkthrough video and write some guide soon(c).
By the way, that kernel which is in devoid #froyo-final cant mount ext4 partition in init, dunno why, I'll look into it after raid.
EDIT: wtf, it just works now, and I did nothing Oo
EDIT2: Changes commited, now It can installed/controlled only by flashable ZIPs and recovery(well, only my modified AmonRa recovery for now). I'll do the rest soon, but I dont know when - maybe tomorrow (oh my, it is today actually already), maybe next month.
Flashable zips and guide added, see first and second post.
keep going I wanted something like this waiting when it can boot stock<froyo> and cm7....
thanx
gingerbread test
well i try with V20C,2.3.4 port(both with a2sd)and didnt woork after flash multiromv1.zip,when reobooting always return to recovery,so in recovery i go to multirom options and says no multirom folder so i start to think a2sd imcompatibelity,so i grab 2.3.3 V20G without changes oficial as lg give us but the results where the same no a2sd problem....
well later i will flash oldbaseband and try one of your combinations but i think its not compatible with gingerbread.....
I think I found it - on GB, there is "on fs" trigger in init.rc, which has only mounts in there, but I need to comment them out - all of them, so "on fs" trigger is empty, and init parser cant handle that. Will update soon.
Ok i will remain in new baseband to try when you update your exclente work...
Sent from my LG-P500 using XDA Premium App
v2 released, I have tested it with CM7 6.5.8, problem with stock GB should be the same as with CM7.
Ladies and Gentlemen I present to you the
kn0x0ut Toolbox v2.30!
(complete, with knox 0x0 reference! hehe)
This script/toolbox allows you to install custom roms, and mods that you would normally have to flash with custom recovery.
(aroma installer and other magic like that gets ignored, but the aroma mods can usually be installed manually on a second run)
On top of that it allows you to create and restore backups of your system and data partition. (for "online" restore without needing custom recovery).
As we (hopefully) all know, if you want to keep knox warranty void at 0x0 you cannot use a custom recovery or kernel....
But let me start with a few words of warning:
Dont do anything obviously stupid...there are no safe-wheels for most commands.
(for example: dont "clean-base" or use "rom-install" without actually installing a new rom or you will most likely end up without system apps and device not booting correctly - like you wouldnt wipe system in a custom recovery without installing a rom...).
It can be used over adb or terminal, but if you install a rom the system ui gets stopped, so better do it over adb!
kn0x0ut toolbox is 100% safe for your device - no hardbrick or efs clear possible by using it!
The worst thing that can happen when using the kn0x0ut toolbox is that you have to factory reset or flash again with odin, so keep the odin file close. (at best this is a custom made RDLV odin.tar.md5 you used to upgrade your rom version with - or for people who have to use other methods because of the new bootloader - keep the last odin file close you used to upgrade also.. and the root method that worked for you)
This whole thing "programmed" on/for a N9005 but in theory it should work for all samsung devices - including the other knox enabled devices and even on many other devices. (but it might need some adjustments, so be careful and have a way to restore your stock rom before you try anything fancy with other devices)
If your knox warranty is already void aka 0x1 then you can still use the toolbox and its mods (some could actually be useful to anyone..) but it won't bring back the warranty.
I didn't really create this thing for me actually - I already did the all steps the toolbox can do by hand with adb terminal on my device (and perfected my method with lots of trial and error..), but I wanted you guys to also be able to enjoy custom roms while keeping your knox warranty intact and show samsung a big FU for putting us through this BS in the first place...
If you like the toolbox and appreciate the work I put into this please consider buying me a beer or hitting the thanks button at least.
---
This kn0x0ut toolbox itself requires root access (if you want to be able to install mods and files you need to be able to mount system writable)!
You will have to use "Root de la vega" or some other method to get rooted while keeping your warranty intact.
IF YOU GET "PERMISSIONS DENIED" ERRORS, PLEASE TRY THE FOLLOWING COMMANDS TO REMOUNT YOUR SYSTEM WRITABLE:
(please try them all, and report back in the thread which one works, and which fail or get permission denied)
Code:
mount -o rw,remount /system
mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
mount -o rw,remount /dev/block/mmcblk0p23 /system
---
How to use:
Extract the download from below to the root of your internal or external sd card.
The script will try to detect the folder first on the external and then on the internal sd.
(/mnt/extSdCard/kn0x0ut or /sdcard/kn0x0ut)
Then browse into that directory with terminal or adb shell and type:
Code:
sh kn0x0ut.sh
and you will get all the commands supported currently.
---
You can then use the command
Code:
sh kn0x0ut.sh kn0x0ut
to install the script to your system's xbin folder and create a symlink to "/system/xbin/knoxout" as well.
(if you want to upgrade kn0x0ut from an older version, make sure you delete all the duplicate old files from the kn0x0ut folder - basically everything but the "processed" and the backup folders if you have them, and replace them with the files from the latest versions download. Then re-run the "sh kn0x0ut.sh kn0x0ut" command to update the kn0x0ut script in your system/xbin folder as well)
From then on you can just type
Code:
kn0x0ut <command>
or even easier:
Code:
knoxout <commands>
The script will automatically detect the kn0x0ut folder on the external or internal sd. (external has higher priority if both present)
To install a zip file meant to be flashed in CWM, you put in into the "put_files_folder". You can put zip, tar, tar.gz or already extracted files and folders into there.
---
To actually work, the files/folders must be in a certain stucture. The script expects already extracted files which get placed into the put_files_here folder to be in the structure like they would appear on the device.
Think of the "put_files_here" folder as the root folder - files get placed on the system in the same structure as if the put_files_folder was the rootfs "/". So if you got a subfolder system/app inside the put_files_here folder, the files inside it will get pushed to /system/app... Hope this makes any sense, else someone else pls try to explain it better.
(NOTE: The script will only install files, it wont do additional magic if there is any contained inside the zip like aroma installer - its mainly meant to speed up the process of installing mods and/roms that require system files to be replaced. (and some things might need to be done by hand, if you want enhanced functionalities from aroma installer)
If you have a zip that does not fully install, check out if there are any scripts inside etc. - and also check the "not_installed" folder which gets created after each installation.
If you want to install a rom, make sure you are on the same base version as the rom you are trying to install. So if you want to flash rom "xyz" based on MK2 then you gotta have stock, but rooted MK2 installed (with odin and RDLV for example). If you want to mix versions, you can try - but I can't tell if that actually works or causes problems - I just would skip the BS and make sure you got the right base rom installed with odin before tying to install a custom rom with kn0x0ut...
---
See 2nd post for current command list.
See 3rd post for current list of available mods.
See 4th post for more detailed command explanation.
See 5th post for download.
Code:
>>> commands <<<
Help:
-----
help - Display help
listmods - Display a list of all available mods
Backup:
-------
backup-base - Backup system app and framework files
backup-efs - Backup efs partition
backup-system - Backup system partition
backup-data - Backup data partition
backup-full - Backup system and data partition
Installation / Restore:
-----------------------
install - Install contents of "put_files_here"
(place backup tar's there for restore)
For System Restore use "rom-install"!
For Data Restore run "clean-data" then "install"!
rom-install - As above but clean system apps, framework
and dalvik-cache before
Mod Installation:
-----------------
mod=[mods] - Install specified mods (for multiple seperate with ',')
Special:
--------
supersu - Install supersu v1.80 to xbin (incl. init.d support for all kernels)
busybox - Install busybox v1.21.1 to xbin (incl. symlink-redirect)
kn0x0ut - Install kn0x0ut v2.30 to xbin
fix_perm - Install fix_permissions v2.10 to xbin
backup_perm - Install backup_permissions v2.00 to xbin
Cleaning:
-----------------------
clean-dalvik - Clean dalvik-cache
clean-base - Clean system apps and framework (MAKE SURE YOU INSTALL NEW BEFORE REBOOT!)
clean-data - Clean data partition to restore from backup (leaves sdcard content alone)
Bloatware Removal:
------------------
removebloat-cooolboy - Remove most bloatware (based on CoOoL_BoY's bloatware remove script)
removebloat-zroice - Remove bloatware hardcore mode (beware - most google stuff gone except playstore)
>>> commands END <<<
Code:
>>> available mods <<<
Mod: acid
Description: ACID Audio Engine v5 (optimised for samsung)
Mod: acid_awesomebeats
Description: ACID Audio Engine AddOn - Awesome Beats
Mod: acid_noozxoide
Description: ACID Audio Engine AddOn - Noozxoide
Mod: aosp_browser
Description: AOSP Browser (with Google, Startpage & Startpage Mobile)
Mod: aosp_clock
Description: AOSP Clock (deinstall ClockPackage.apk if you want to use this)
Mod: bash
Description: BASH Shell
Mod: busybox
Description: busybox v1.21.1 (busybox.net) + special default symlink fixes
Mod: chronus
Description: Chronus Clock Widget
Mod: forcelte
Description: Init.d script to force lte on
Mod: onandroid
Description: onandroid script v9.20 + necessary binaries (mkyaffs2image, dedupe)
Mod: onandroid_n9005
Description: onandroid partition layout for N9005
Mod: openvpn
Description: openvpn binary v2.1.1 (statically linked, no libs necessary)
Mod: sqlite3
Description: sqlite3 binary + libs and init.d script to optimise db's at boot
Mod: zipalign
Description: zipalign binary + init.d script to run at boot (fixed to make it work!)
>>> available mods END <<<
Add ons and commands explained in detail:
1.) Fix permissions script is running after all the commands to ensure permissions are correct. You can also install the fix_permissions script as standalone command. (see command list)
2.) To install a rom or other cwm zip file put it into the "put_files_here" folder and run "install" or "rom-install" depending on what you want to do. You can also use this to restore system and data partition backups made by kn0x0ut or onandroid (those have to be in tar or tar.gz format).
3.) The busybox which gets installed is directly from busybox.net and has more commands than the "normal" busybox floating around from stericson.
Additionally if you use the "busybox" command some symlinks will get redirected from toolbox to busybox and give enhanced functions.
(for exampe: mv, cp, rmdir, rm, ...)
4.) "sqlite3" and "zipalign" will also install an init.d script so that they are running on system boot to optimize the dbs and/or zipalign the apks.
--- more to come ---
Current Version: v2.30
### Downloads ###
Please do link to this thread if you want to use the kn0x0ut toolbox for other projects.
(do not distribute kn0x0ut download links but instead link to this thread, not only for credits, but so people can report bugs etc in one place)
READ THE INSTRUCTIONS AND TRY TO REMOUNT YOUR SYSTEM WRITABLE BEFORE YOU TRY TO INSTALL A ROM! AND ONLY DO THAT OVER ADB SHELL!!!
>>> YOU HAVE TO RUN KN0X0UT AND ALL ITS COMMANDS AS ROOT USER IN TERMINAL OR OVER ADB SHELL. TO MAKE THE SHELL ROOT YOU HAVE TO TYPE "SU" AND THEN ENTER BEFORE USING ANY OF THE OTHER COMMANDS! <<<
kn0x0ut_2.31.zip - 14.84 MB
Do not run rom-install if any of the other commands fails, and please try them first. (at least busybox and supersu installation)
reserved
reserved
So if I already have Knox at 0x1 am I screwed?
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
harosxcomp170 said:
So if I already have Knox at 0x1 am I screwed?
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
Click to expand...
Click to collapse
well then this thing has no use to you, other than the addons and installing stuff on a running system instead of using custom recovery.
But it wont fix the knox warranty no. It just KEEPS it from getting tripped by allowing installs without custom recovery.
Now say if I odined back to completely stock with no root. Will that bring my Knox back to 0x0? Or has the damage already been done?
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
harosxcomp170 said:
Now say if I odined back to completely stock with no root. Will that bring my Knox back to 0x0? Or has the damage already been done?
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
Click to expand...
Click to collapse
sorry to say, but gtfo with these questions inside this thread! knox 0x1 stays knox 0x1 - so far nothing gonna bring it back - ssheeesh this you should really know man. one lil google search gives you 100 threads about just that! (completely offtopic to this tool also... sorry but is this xda or android central?!)
Yea sorry about that I didn't know if there was a break through or something I bought my phone off swappa with knox already voided.
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
harosxcomp170 said:
Yea sorry about that I didn't know if there was a break through or something I bought my phone off swappa with knox already voided.
Sent from my SM-N900TA running HyperDrive 3 using Tapatalk 2
Click to expand...
Click to collapse
well tbh, I wouldn't worry so much about it, I'm strongly considering to trip my flag to have custom kernel and recovery. This toolbox here can't fully replace it. But maybe we find a way to make our own signed kernels and/or recovieries or some other way around this knox warranty void bs.
My phone is still new and for such an expensive piece I rather don't risk anything before it's clear there are no bugs out or smth people dont yet know about (I mean with the hardware, not with my toolbox or smth). Plus its fun to try out whats possible.. (i learned so much about android and the shell by doin all this... good exercise hehe)
So until then I'll keep my warranty intact - and beside overclocking and some kernel tweaks and maybe easy nandroid backups/restore we can do quite alot.
---
@ the others with their flags still intact: Why so shy? Any success stories so far? This would get more attention if someone would confirm it working other than me hehe =). You all pushed me to make a script now use it! (try X-note for the start or smth .. thats what I'm using and it worked fine)
Cf root will trip the KnoX.
But samsung accepts one time warranty even if u tripped it.
This is my 3rd note, in 3 executive years. Ive never needed warranty. The golden rule with Samsung phones is if it works (hardware), it will stay to work for years. Just like German Mercedes from the '80s and '90 s.
Greetsz
Sent from my SM-N9005 using Tapatalk
but it's impossible to use your program without root? it's right. my phone it's already in rom MJ7, so, no soluce now to root without tripping the knox to 0x1..
Will i need to run scrtips once?
or before install more rom.
Will this wipe my phone? Dont wanna loose my data
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
no it wont wipe data partition.
If you just use the "install" command it wont wipe anything, just copy over and overwrite the files that exist.
If you use the "new_rom" command it will wipe the system apps and the framework before installing.
If you come from odexed and want to install deodexed version you must use the "new_rom" command or else you will have odex files and some incompatible system apps left.
---
I'm also working on a way to backup and restore system as well as data.
What I really would like to know is what happens if you create an odin image from your system partition and flash that back with odin or mobileodin. It would just "restore" the system to the state where you created the image, but the question is if that would trip knox or not.
To be honest I doubt it would, since we only install a system image back that was already "ok" for knox - you already got the custom system partition flag when one uses RDLV or somehow else attains root access because the system is not unmodified, so this wouldnt change anything.
The only problem with my thinking would be if odin / mobileodin implements a special check thats only triggered when you flash through it and which will then trigger the knox flag if it finds a custom image.
If you find any stories of people who just flashed a (custom) system image through odin or mobileodin please point me there. So this question can finally be answered fully.
If we could just flash system images with odin while leaving out kernel and recovery and keeping knox, this would make custom recovery obsolete kind of. The only thing we still couldnt do then would be to use custom kernel features. So please help me to find out!
Yeah
So will new rom erase
game saves
Sms
Installed apps
Settings?
Okay if i find such thread ill post or pm it to you
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
It shouldnt, although you might end up with other problems.. not 100% sure to be honest. (I only installed on freshly wiped device so far, or wiped afterwards etc, just to make sure)
Best thing to do is backup everything with titanium and then give it a try - but make sure you backup stuff to your external SD or copy it over to the pc, because the internal sd will get wiped if you have to factory reset. (just do a backup of everything with titanium and then copy the contents of your internal SD card (everything - to include game saves etc) to your pc.
If end up having to factory reset because of bugs from the old data you can just restore the apps with titanium and have your internal sd contents backed up.
---
If you give it a try (if you have the titanium backup and the internal sd contents you can always restore the old state at least) please report if you had to wipe data or if everything runs fine?
When I tested things around I did this already and the data stayed - but i did not test all the apps to really make sure.. so theres a small chance for problems - but I actually doubt it.
*** DISCLAIMER ***
I work on projects that may brick your device. Don't sue me, hate me or try and kill my dog if that happens. I will feel bad the community will feel bad and hopefully we'll find a way to get you going again. But, the very nature of my projects involves a certain amount of risk taken by YOU. And by using the projects that I work on, you've accepted that fact.
THERE IS AN UNKNOWN ISSUE WHERE IF YOU HAVE ENCRYPTION ENABLED AND INSTALL SS IT BOOTLOOPS. IF YOU FIT THIS DESCRIPTION PLEASE STAY AWAY FROM SAFESTRAP FOR NOW.
[SM-N9005] Samsung Galaxy Note 3 Safestrap
CURRENT PROJECT STATUS:
BETA
I had an XDA user request a build of Safestrap for the SM-N9005, and figured I might as well share it.
NOTE: Safestrap will not trip KNOX, because it doesn't not flash kernels
I know that the N9005 is an unlockable device but some users may want to save the warranty and only mess around with TW-based ROMs. That's what Safestrap is for. If you're unlocked you probably want CWM / TWRP installed as your recovery so that you can flash AOSP-based ROMs.
WHAT IS SAFESTRAP?
Safestrap is a Bootstrap / Recovery for locked bootloader phones. The goal is to avoid touching your primary system (I'll call this "stock" system) and only flash or make large changes to another place on your phone that Safestrap treats as a "2nd system" (in this case, it's a series of virtual ROM slots located on the internal emmc area: "/sdcard"). Once installed, you will see a "Splashscreen" giving you the option to hit "menu" to enter recovery. The recovery portion of Safestrap is now based on TWRP 2.7.1.x (a touch based recovery) and you can perform .zip installs, backups and restores here. The additional features I've added to TWRP are mostly located under the "Boot Options" menu:
Here you can create virtual ROM-slots (2 on the N3 due to partition size and internal space) for flashing ROMs. These ROM-slots allow for different sizes of /system, /data and /cache partitions. The defaults *SHOULD* be good enough for flashing the stock-based ROMs.
NOTE: The bigger you make these partition the less room you will have to make other ROM-slots.
You can activate a new ROM-slot by choosing the slot you wish to make active and then selecting the "Activate" button. Once active, you will see the "rom-slot#" up in the top of the screen shown in green. If you make the "stock" ROM active, then you can see it in the top shown in red.
Once a ROM-slot is active, all actions you would normally perform using TWRP are directed to that ROM-slot. For example, "Install" to flash a .zip, backup and restore.
For more information you can read up here:
http://blog.hash-of-codes.com/how-to-safestrap/
HOW DO I INSTALL SAFESTRAP?
Requirement: Root
[NEW FOR v3.75+ KK Safestrap] Requirement: busybox. If your stock ROM doesn't have it built-in you need to grab "Busybox" from the Play Store and run the installer.
Requirement: External SD card
Requirement: Allow APK install from Unknown Sources
Download the Safestrap APK
Find the APK using a Filemanager tool and open it on your device, then click "Install".
(If updating from an existing Safestrap you might be warned that this will over-write the existing installation. Click the "Yes" equivalent to this message.)
Once installed, open up the Safestrap application as you would any other app.
Agree to the disclaimer that you won't try to sue me and hunt me down with a rifle if you manage to break your phone..
Then use the "Install Recovery" button. You should see the current version down in the lower left corner of the window. And the "Status:" should say "Installed" when you're done.
From there you can reboot and you *should* see a new splash screen during the boot up. While this is showing you can enter Safestrap Recovery using the [ menu ] button.
That's it for the installation! Read below for a brief overview of Safestrap Recovery v3.x
INSTALL VIDEO by DMX: https://www.youtube.com/watch?v=_RZIyeUMK-Y&feature=youtube_gdata_player
HOW DO I ENTER RECOVERY?
During each reboot a splashscreen will be displayed showing whether the device is running a rom-slot or on the "Stock ROM".
Press the button shown on the screen to either enter "RECOVERY" or "CONTINUE" booting (or the hard button underneath each option).
HOW DO I UPGRADE SAFESTRAP?
Push the APK up to your sdcard.
Boot back into the "stock" rom-slot.
Go into your old Safestrap app and use the "Uninstall Recovery" button
THEN, open a "file explorer" of some sort (even TW "My Files" will work)
Browse to where you pushed the APK
Click on it and install like normal
Once installed, open the APK
Grant SU access
Use the "Install Recovery" button
All set, now you can reboot and re-activate whatever rom-slot you were using
KNOWN ISSUES:
SEE POST #2
DOWNLOADS:
CONFIRM THAT YOU ARE USING AN SM-9005 SAMSUNG GALAXY NOTE 3
FIND YOUR STOCK OPERATING SYSTEM VERSION BELOW AND USE THAT FILENAME:
[KITKAT:ND3]
LATEST BETA FILE: Safestrap-HLTEXX-ND3-3.75-B01.apk
[JELLYBEAN]
LATEST FILE: Safestrap-HLTEXX-3.71-B02.apk
XDA Downloads
Mirror 1 (Crackflashers)
CHANGELOG
[2014-06-26] Updated hijack for KK bugs
[2014-06-26] Fixed ROM-SLOT support
[2014-06-26] Fixed internal storage mount issue
[2014-06-26] TWRP 2.7.1 base update
[2014-01-11] Initial SM-9005 release
As of version 3.6x, Safestrap Recovery is now based on TWRP 2.7.1.x. For more on TWRP you can visit their website: http://www.teamw.in/
WARNING: Safestrap is heavily modified to be "Safe" for your device. Do not download TWRP from their website and expect it to work the same way. Also TWRP does not support Safestrap, tho some issues that may come up will be TWRP dependant, please try and contact myself or look on the forums for your device for answers before hunting down TWRP people. They won't be able to help w/ Safestrap specific questions.
Special Thanks To
DeesTroy, bigbiff & TeamWin for all their hard work making TWRP such a fantastic recovery
XDA:DevDB Information
Safestrap Recovery v3.71 (JB) / v3.75 B01 (KK/ND3), Tool/Utility for the Samsung Galaxy Note 3
Contributors
Hashcode, DeesTroy, bigbiff & TeamWin
Version Information
Status: Beta
Current Beta Version: v3.75 B01
Beta Release Date: 2014-06-26
Created 2014-01-12
Last Updated 2014-06-26
Reserved
KNOWN ISSUES:
PLEASE USE STOCK TOUCHWIZ FROM SAMSUNG FOR YOUR STOCK ROM -- FLASH TO ROM-SLOTS
If you install Safestrap on a rom-slot it will show "not installed". *DO NOT INSTALL SAFESTRAP ON A ROM-SLOT*
Rebooting from a rom-slot will end up at a blank screen. Battery pull and re-power on.
Sometimes the installation doesn't work correctly. If you don't see the splashscreen after a rebooting. Install Safestrap again. (DEBUGGING THIS AS I GET TIME)
If you don't see files on "Micro SDcard" for some reason try tapping that area and swapping to "Internal Storage" and then back again.
No Aroma installer support. This is due to the stock S5 kernel framebuffer. To build a recovery which worked, it needed QCOM patches. So will Aroma.
If you try a .zip file with an Aroma installer, it will most likely just hang.
If you use the "4way reboot" mod, then "Reboot Recovery" button in the Safestrap APK won't work correctly.
Reserved
wonderfull work.
My knox is 0x1 but i think lot of people like your work.
Thanks
never thought it would be released for hltexx.
i read about it some time ago and was really surprised about the rom slots feature.
i like the idea of having an alternative rom on my device.
downloading it now, will give some feedback later.
Thank you Hashcode!!!
Atm i can say that backuping works fine....looking for an second rom to test with X-Note as Stock, Aroma installer is not supported for now.....
Sent from my Safestraped SM-N9005 BlackBox
i successfully installed echoe rom 5 into rom slot 1 !
i like safestrap very much, easy to use and self explaining.
if you already have twrp installed, you do not loose it but you don´t need it anymore.
booting to recovery brings up your original twrp, a normal reboot shows the splash screen from where you can launch safestrap.
trying to install a rom with aroma installer of course doesn´t work but i tried just to see what happens :
the screen just freezes and you need to reboot by holding down the powerbutton, thats all.
you can restore a twrp backup of an aroma based rom, that you made from the stock rom slot, to another rom slot (i did it with a backup of bobcatrom).
but it looks like it uses the internal storage directory of the stock rom slot.
edit: seems like the original storage/emulated/0 is always used. i can see all the files from stock rom after installing a complete new rom.
so this isn´t really good for having 2 totally seperate operating systems installed, is it ?
have to read some more about it...
thanks a lot hashcode !
edit:
from the safestrap blog:
DON’T RESTORE A CUSTOM ROM-SLOT BACKUP TO THE STOCK ROM. THIS WILL MOST LIKELY BRICK YOUR PHONE.
Great Job
Thanks Hashcode, great tool!
Using it on a SM N-9005 without problems except I have a couple of ROMs that do not activate Wi-Fi.
Any clues?
I would love to be able to use this on the N900T
Sent from my SM-N900T using Tapatalk
ktetreault14 said:
I would love to be able to use this on the N900T
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
I've been using the AT&T Safestrap Recovery on my Tmobile N900T and it works perfect. I flashed the AT&T X-Note ROM port (in slot 1) that they have and it works fine on the N900T. It does install the AT&T CSC, but installing the TMO one causes crashing in the dialer (which also happens in the international rom currently out in the TMO forum). So, just keep the ATT CSC like it is. For Wi-Fi calling, I just boot back into the Stock slot and use the stock ROM.
The AT&T Safestrap: http://forum.xda-developers.com/showthread.php?t=2572978
The AT&T X-Note Port ROM: http://forum.xda-developers.com/showthread.php?t=2579773
sounds intresting...
Hashcode said:
...
CURRENT TESTS:
...
TEST #7: Restore stock ROM backup to stock slot: TESTING
TEST #8: Initial 2nd-init ROM installation on rom-slot RESULT: TESTING
TEST #9: Custom ROM flash on rom-slot: TESTING
...
Version Information
Status: Testing
Created 2014-01-12
Last Updated 2014-01-11
Click to expand...
Click to collapse
If I understand correctly right now all ROM slots boot using (all of them) the same kernel (which of course must be stock Samsung kernel in order to keep knox 0x0).
This means that with kernel 4.3 (and corresponding bootloader) all slots must also be 4.3, while with kernel 4.4.2 (and corresponding bootloader) all slots must also be 4.4.2 - is that correct?
Will existing version work with 4.4.2 or a new version will be needed?
Will this ever be able to backup efs like the official twrp? Also will this ever support aroma? I know you said the kernal doesn't support it, but I was wondering how mobile Odin can do it without tripping knox
Love your work, it is working like a charm
Sent from my SM-N9005 using XDA Premium 4 mobile app
Hi Hashcode
Yipee!!!
I'm so glad you decided to release this on the n9005.
i'm off on the weekend, will test this and let you know the outcome!!!
Again
Do not download. Please give another link.
@nguyenson318
Mirror 1: Goo.im Download <--- not working
Mirror 2: Crackflashers Download <--- is working
So far this is working perfectly on my note 3 n9005.
Have backup my stock (actual it a custom rom!!) and installed a couple of roms in the free slots and all is working.
Still testing the software out but its very good, esp. if you want to try all the rom being released without messing with your main system.
Still need to test whether restore works and at the moment i have notice that i still have CWM as my recovery but when booting to Safestrap TWRP takes over.
Like i said i'm still testing this great piece of software but Hashcode has done a great job making this work on the n9005
Well Done
I download from n9005 note 3 (Next Browser) but only 0.1KB is stopped.
nguyenson318 said:
I download from n9005 note 3 (Next Browser) but only 0.1KB is stopped.
Click to expand...
Click to collapse
Here is the file
To mods, please remove this post if it violates the forum rules
To Hashcode, if you prefer people to download from your links provided i shall remove this post, i do not wish to cause you any offense.
Thanks for creating a killer app and i hope you keep on improving this product
If you wish me to test any aspect of your software on my handset, please let me know
I'm sorry if i sound like an absolute noob...but this requires root.
Afaik rooting the Note3 trips the Knox warranty flag......thus no more warranty.
Am I wrong?
Nirak said:
I'm sorry if i sound like an absolute noob...but this requires root.
Afaik rooting the Note3 trips the Knox warranty flag......thus no more warranty.
Am I wrong?
Click to expand...
Click to collapse
This is for people who have rooted via kingo or URDLV etc that don't trip counter.
(Click on the image above to download my MultiROM Manager App)MultiROM for the Samsung Galaxy S3 i9305, brought to you by Alexander_the_B0ss
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy S3 4G. It can boot any Android ROM . Besides booting from device's internal memory, MultiROM could boot from external SD card(untested). The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system.
Features:
* Multiboot any number of Android ROMs (as many as your internal memory can hold)
* Restore nandroid backup as secondary ROM (damn useful feature)
* Boot from Internal memory and MicroSD Card
Warning!
This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong (even if never happened until now) and you will have to flash stock firmware with Odin. Make backups. I personally can't stress enough for you people to make nandroids becuase you never know.
Installation
Via MultiROM Manager app
This is the easiest way to install everything MultiROM needs. Install the app Install my modified app and select MultiROM and recovery on the Install/Update card the app is still in alpha, so don't select install, use manual install below. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are choosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must not be encrypted (hint: if you don't know what it is, then it is not encrypted).
MultiROM has 3 parts you need to install:
MultiROM itself - download the ZIP file and flash it in recovery.
Modified recovery - download the ZIP file and flash it in recovery or Mobile Odin app to flash the recovery.img contained inside ZIP.
Patched kernel (Only TWO: AGNi PureCM or AGNi PureSTOCK) - Download the ZIP file and flash it in recovery (seems like kexec-hardboot isn't activated by psndna88, so menu won't show up on boot)
*Downloads in Post #2*
If your MAIN ROM is TouchWiz or TouchWiz based, please use AGNi PureSTOCK kexec-hardboot status unknown, someone with stock rom please install app and tell me if kexec-hardboot is enabled.
If your MAIN ROM is not TouchWiz, but CM or AOSP (basically custom rom except MIUI) use AGNi PureCM no kexec-hardboot, tested.
You current rom will not be erased by the installation.
Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using MicroSD Card (UNTESTED)
During installation, recovery lets you select install location. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to MicroSD Card takes a bit more, because the external memory is (usually) slower and it needs to create the images. Also boot process is longer, highly depends on card's class. You can find ROMs installed on SD card in the "External" tab in boot menu.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
Add ROM - Add ROM to boot manager
List ROMs - List installed ROMs and manage them
Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
Settings - Well, settings
Manage ROM
Rename, delete - I believe these are obvious
Flash ZIP (only Android ROMs) - Flash ZIP to the ROM, for example GApps
Add/replace boot.img - Replaces boot.img used by the ROM, this is more like developer option.
Screenshots
Application
Recovery (Sorry for pictures...)
Bonus pic(zoom to see the RGBG-Matrix (PenTile))
My Homescreen and Lockscreen (for those interested)
Big thanks to Tasssadar for this awesome utility.
XDA:DevDB Information
MultiROM, multiboot tool for Samsung Galaxy S3 4G (i9305), Tool/Utility for the Samsung Galaxy S III I9300
Contributors
Alexander_the_B0ss
Version Information
Status: Beta
Current Beta Version: v32
Beta Release Date: 2015-08-30
Created 2015-08-29
Last Updated 2015-09-02
Reserved
DOWNLOADS
MultiROM itself: HERE (Check NOTE 2 below for testing zip)
Uninstaller: HERE
Recovery: HERE
Note 1: For recovery use 720x1280 multirom theme from here.
Note 2:
MultiROM Installer with MultiROMManager app and TWRP theme installation testing zip here. Basically what this zip does is, after MultiROM is installed, it copies to system/app my own version of MultiROM Manger to support i9305, then copies to the internal sdcard the theme for TWRP and sets the correct attributes.
What is that? I dont understand
a possibility to install more than just one operating system
Quick update for you guys:
Recovery works, but the theme is kinda weird, so use the theme provided for 'perfect' recovery
MultiROM menu won't show on boot, sent PM to Tassadar for help request. Meanwhile, i am trying to modify MultiROM Manager app to support i9305 to possibly have a workaround for the menu not showing up.
Stay tuned for more development and an OP update after everything is working. CYA
Another quick update for the ones interested in the project. I have succesfully compiled MultiROM Manger app that detects our device (after twenty attempts, then gave up and updated Android Studio to the latest version and redownloaded Android SDK and NDK. First attempt after reinstall worked).The APK fresh from the oven is here. This represents a milestone in MultiROM development because with the app now detecting the device one can avoid the boot menu not showing bug. BUT WAIT, THERE'S MORE
The bug i talked about is related to kernel, because the app doesn't detect kexec-hardboot.
Stay tuned for updated OP soon™.
Error in flashing. 'E: Error executing updater binary in zip '/external_sd/Roms/MultiRom/multirom-20150829-v32-UNOFFICIAL-i9305.zip'
Tried both with unmodified TWRP and MultiRom TWRP
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
fs71gh said:
Error in flashing. 'E: Error executing updater binary in zip '/external_sd/Roms/MultiRom/multirom-20150829-v32-UNOFFICIAL-i9305.zip'
Tried both with unmodified TWRP and MultiRom TWRP
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
Click to expand...
Click to collapse
Are you really trying to install this on Note 4? Damn. It is only for i9305, aka m3xx aka m3 aka S3 4G. So WRONG FORUM
Alexander_the_B0ss said:
Are you really trying to install this on Note 4? Damn. It is only for i9305, aka m3xx aka m3 aka S3 4G. So WRONG FORUM
Click to expand...
Click to collapse
Sorry for your confusion but we also have an Eclipse for S3 LTE which is already in this forum and my device is undoubtedly also S3 LTE and not Note 4
fs71gh said:
Sorry for your confusion but we also have an Eclipse for S3 LTE which is already in this forum and my device is undoubtedly also S3 LTE and not Note 4
Click to expand...
Click to collapse
I don't want to keep this on, but check this post out http://forum.xda-developers.com/not...-x-teamwin-t2956011/post57742832#post57742832 and see the codename for the SM-910F and check your reply from before
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
Alexander_the_B0ss said:
I don't want to keep this on, but check this post out http://forum.xda-developers.com/not...-x-teamwin-t2956011/post57742832#post57742832 and see the codename for the SM-910F and check your reply from before
Edit: MultiROM Manager_1.183-debug_183.apk also says "device not supported (trelte)". Tested with Eclipse rom
Click to expand...
Click to collapse
I guess the problem is with the rom specifically (some things left out while porting), as I got your your apk working with two other cm11 roms.
@Alexander_the_B0ss
Hi boss.
I like this dual-boot initiative but i have some problem with apk (device not supported (trelte)) but i think you can solve this.
I edit the updater-script and remove this line (assert(getprop("ro.product.device") == "i9305" || getprop("ro.build.product") == "i9305");) (i test now in terminal command: getprop ro.product.device and show me i9305 ..i dont now why i can't install zip package. but i solve this with removed line.
So, i install recovery (multirom recovery) and i install zip. I install your modded apk and i have error.
On recovery, i try to install a new rom, and was installed (but on internal_memory/multirom directory i dont see any folder/file..but my space on rom was used by "new rom")
I try to inject my kernel (pureSTOCK 5.9.2). Nothing happen when i reboot my phone. I think need to show a menu with "What rom do you want to boot"..but nothing.
I can help you with tests to dev this project.
Keep up
EDIT: And, i dont now how can install a theme for TWRP..because text buttons not aligned
il3gal said:
@Alexander_the_B0ss
Hi boss.
I like this dual-boot initiative but i have some problem with apk (device not supported (trelte)) but i think you can solve this.
I edit the updater-script and remove this line (assert(getprop("ro.product.device") == "i9305" || getprop("ro.build.product") == "i9305");) (i test now in terminal command: getprop ro.product.device and show me i9305 ..i dont now why i can't install zip package. but i solve this with removed line.
So, i install recovery (multirom recovery) and i install zip. I install your modded apk and i have error.
On recovery, i try to install a new rom, and was installed (but on internal_memory/multirom directory i dont see any folder/file..but my space on rom was used by "new rom")
I try to inject my kernel (pureSTOCK 5.9.2). Nothing happen when i reboot my phone. I think need to show a menu with "What rom do you want to boot"..but nothing.
I can help you with tests to dev this project.
Keep up
EDIT: And, i dont now how can install a theme for TWRP..because text buttons not aligned
Click to expand...
Click to collapse
Heh, the updater-script bug is well-known to me, i'll try to fix it in the upcoming updates. The manager app issue happens is because you are running a Note 4 ROM from this forum and that rom changes the ro.product.device if not mistaken. If I can make this work, which i will do, i will have a talk with the ROM developers to not alter the ro.product.device for the app to work. To install a TWRP theme you have the instructions along with the download here. Just make sure to download for 720p.
Alexander_the_B0ss said:
Heh, the updater-script bug is well-known to me, i'll try to fix it in the upcoming updates. The manager app issue happens is because you are running a Note 4 ROM from this forum and that rom changes the ro.product.device if not mistaken. If I can make this work, which i will do, i will have a talk with the ROM developers to not alter the ro.product.device for the app to work. To install a TWRP theme you have the instructions along with the download here. Just make sure to download for 720p.
Click to expand...
Click to collapse
Thanks for your "talk with ROM Developers". Hope kexec-hardpatch is enabled (if I am right) soon and we will have boot menu working
@Alexander_the_B0ss
Any update? I devices is see like: m3 not i9305
il3gal said:
@Alexander_the_B0ss
Any update? I devices is see like: m3 not i9305
Click to expand...
Click to collapse
The actual codename for i9305 is m3 or m3xx, i9305 is the 'commercial name'. About any updates: for now i have a dead hdd, so at least for a couple of weeks no updates. Sorry. And also I am sick and need to go to hospital.
Alexander_the_B0ss said:
The actual codename for i9305 is m3 or m3xx, i9305 is the 'commercial name'. About any updates: for now i have a dead hdd, so at least for a couple of weeks no updates. Sorry. And also I am sick and need to go to hospital.
Click to expand...
Click to collapse
Get well brother.
Get well soon friend
any news ?????
hi, does this work on the older i9300 model (3g)?
I don't have my device yet, but here's what someone with the device can do once you have unlocked your bootloader:
Update: This method will work once MagiskManager is patched to support the P3XL:
https://twitter.com/topjohnwu/status/1052993970303889418
1) Download the latest factory image from here:
https://developers.google.com/android/images#crosshatch
2) Extract the file to your pc somewhere. Inside the archive, there is a boot.img
3) Upload boot.img to /sdcard
4) Install Magisk Manager from the link below. You can use adb install from the command line, or upload to your phone and sideload it with some file manager app (Root explorer for example).
https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.0/MagiskManager-v6.0.0.apk
5) Open Magisk Manager app and choose install. Select the boot.img file you uploaded in step 3
6) Copy the patched_boot.img file generated from Magisk Manager in step 5 to your pc.
7) Reboot to bootloader (adb reboot bootloader) or Power off the phone completely, and hold volume down while you power it up.
8) fastboot flash boot patched_boot.img
9) Reboot and check to see if you have root in Magisk Manager.
If this does not work or you get into a boot loop or it freezes, simply reboot to bootloader and flash stock boot.img from the factory image.
We need twrp
TheUndertaker21 said:
We need twrp
Click to expand...
Click to collapse
I believe this method would bypass the requirement for twrp. I won't be able to test until I get home tonight but I will try and update later.
Apparently Topjohnwu has confirmed that MagiskManager does not patch the boot image correctly, so this does not work as of yet. Will most likely need a new version of MagiskManager to get this working. I will modify the first post accordingly.
TheUndertaker21 said:
We need twrp
Click to expand...
Click to collapse
No we do not.
Today is the day
From his Twitter. Should be any day now. Excited
https://twitter.com/topjohnwu/status/1053488124389720064?s=19
Welcome to the Magisk family, Pixel 3!
I originally planned to do more changes to Magisk Manager before a new public release, but I think people can't wait to root their shiny new Pixel 3, so here we go!
Up-to-date Documentations
Some subtle details, design choices, developer guides are all added to the documentations!
For most average users though, the most interesting part would be the tutorial: Best Practices for MagiskHide, please take some time and check it out!
Magisk Documentations
Boot Image Header v1
Google updated the boot image header format from v0 to v1 and was first used on the Pixel 3. The new header supports recovery DTBOs, which won't be used on any A/B devices, including Pixel 3 so that isn't the main issue here. The new format stores its version number to an originally unused entry in the header to determine whether the extended header entries is used. However in some freaking devices like Samsung's, they have been using the supposedly "unused" entry as the size of an non-AOSP "extra section" for quite a long time. magiskboot is designed to support extracting these extra sections (because people use Samsung), but with the introduction of header v1, the tool couldn't interpret the image properly, and thus generating invalid boot images.
magiskboot's boot image parsing, unpacking and repacking code was rewritten with C++ to utilize the more powerful language features due to the complexity (because I still need to support freaking PXA format headers used by old Samsung devices...)
MagiskSU Rewrite
Both the daemon and client side of MagiskSU is completely rewritten with improvements and optimizations, for example: simplified `su_info` caches, early ACK between daemon and client to prevent process freezing when denied, sending parsed command-line options instead of full arguments, and many more!
Samsung Defex Patches
A hexpatch for removing Samsung's new KNOX feature: Defex Safeplace was actually already introduced in previous releases, but that solution wasn't ideal since each new kernel release would generate different patterns. A more general patch (which is only a single CPU instruction!) was discovered and included into this new release.
Magisk-Modules-Repo Moderation
If you aren't aware, a team of zealous volunteer moderators were already starting to review new submission manually, being the gate keeper of our beloved Magisk-Modules-Repo. Hopefully this will prevent pointless/spam modules polluting the download section in Magisk Manager!
Thread closed as per OP request.
Thanks
SacredDeviL666
Forum Moderator.