Develop Bugs

[11.05.2011][CF-Root v3.3] JJ*, JM*, KA*, JQ1 - su+busybox+CWM3/RFS

This rooted kernel is for the "rooting beginners" and those who want to keep as close to stock as possible. CF-Root takes the kernel from an original Samsung firmware, and just adds root, busybox, and ClockWorkMod (CWM3) recovery
(1) THIS IS NOT A ROM - it is only a modified kernel. You need to have the relevant firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions. PLEASE READ THIS ENTIRE POST!
(2) THIS IS ONLY FOR GSM TAB. IT MAY WORK ON OTHERS VARIANTS, BUT YOU'RE ON YOUR OWN THERE !
(3) I have moved the description for the old FROYO CF-Root's to the next post, but the downloads for the FROYO CF-Root's are still attached to THIS post. The contents of THIS post however are about the GINGERBREAD CF-Root's
(4) MAKE SURE YOUR PHONE CAN ENTER DOWNLOAD MODE USING THE KEYCOMBINATION WHILE BOOTING BEFORE FLASHING CF-ROOT (or anything, really)
Donate
There have now been over 200.000 downloads of CF-Root for various devices, and many more if you include ROMs, kernels, etc that use it. Don't be a leech, buy me a beer (and use the "Thanks" button!)
Features
- The kernel is fully stock and taken from the original firmware, with just the following added:
- Root
- Superuser 2.3.6.1
- Busybox v1.16.2androidminimal (from CWM)
- Integrated CWM 3.0.0.5 / RFS
Instructions (short)
- Flash CF-Root-xxx-vX.X.tar (from the attached zip) as PDA in ODIN, without repartition. Done.
Instructions (long)
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached CF-Root-xxx-vX.X.zip
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-xxx-vX.X.tar
- Put your phone in download mode
- (USB) Connect the phone to your computer
- Make sure repartition is NOT checked
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)
Instructions (alternative if you are already running CF-Root 2.5 or newer)
- Copy the zip file to your SD card
- Stop sharing SD card with computer over USB, unplug the cable, etc
- Applications -> CWM -> Flash kernel. Select the ZIP file on your SD card.
- Done
Other kernels
Replacing CF-Root with other kernels and vice-versa sometimes works, sometimes it doesn't. I don't have a list.
When going from CF-Root to another kernel, root will usually stay, while CWM will be lost (unless the other kernel also includes it), but there should not be issues. The CWM Manager and Tweak Manager apps may remain, but they probably won't do anything useful.
CF-Root is made to be applied on a stock kernel. Going from a lagfixed kernel to CF-Root usually does not work. Unlagfix first.
ClockworkMod
CF-Root includes a special version of CWM3, modified to work with RFS. CWM3 by default does not support RFS, koush' versions are all based on ext4. The RFS compatibility is done with heavy scripting. CWM3 is also recompiled from source with some slight modifications to handle key input correctly.
CF-Root/CWM3 is NOT compatible with ROM Manager! Manage/perform your backup/restores from CWM directly or using the CWM Manager application included with CF-Root
- Booting into recovery will immediately give you CWM. The standard recovery will only be started if a Samsung package is detected.
- ADB is functional in recovery, however it may take up to a minute for it to start up after booting into recovery.
- When connected to ADB in recovery, you need to use "rootsh" command to get root, instead of "su". This will not prompt you, it will just give you root. Obviously the "rootsh" command does not work when booted normally.
CWM Manager
Because of incompatibility with ROM Manager, I wrote and included "CWM Manager". This is a new app (as of March 30, 2011) and beta. You can find it under Applications -> CWM. It is much faster to use than manually booting into CWM and selecting these options.
Features:
- Boot to CWM
- Backup firmware
- Restore backups
- Delete backups
- Install APKs
- Flash CWM3 update.zip's
- Flash kernels (zImage, zImage in TAR, zImage in ZIP, zImage in TAR in ZIP)
Note: If you flash a different kernel, CWM Manager may remain installed. However, functions may not work, because they need kernel compatibility ! At this version of CWM Manager this does not produce errors, it just doesn't do what you expect it to
Tweak Manager
CF-Root includes a number of tweaks that are applied on startup. A "Tweaks" application is included you can use to select which tweaks to apply.
Ext4 Manager
Ext4 is currently NOT supported on Gingerbread for the Galaxy Tab, unlike CF-Root for the Galaxy S.
Custom boot / init scripts
CF-Root will execute the following scripts if present, in the order listed:
- /system/etc/init.d/* (there can be many files here, no extensions! use #!)
- /system/bin/customboot.sh (busybox sh)
- /system/xbin/customboot.sh (busybox sh)
- /data/local/customboot.sh (busybox sh)
Please make sure you chown / chmod the scripts correctly so they can be executed.
Custom boot animations and binaries (note: broken in 3.2, fixed in 3.3)
CF-Root also supports custom boot animations:
- /system/media/bootanimation.zip
- /data/local/bootanimation.zip
And custom boot binaries:
- /data/local/bootanimation.bin
Installing busybox over the included version
It is possible to install a custom busybox over CF-Root v3.0 and newer. However, this is not without risk. CF-Root makes heavy use of scripting, and many CF-Root scripts rely on the internal busybox version. If you do install a seperate busybox version (always use "stericson" installer!), install it to /system/xbin. Installing it to /system/bin will mess things up for sure. Even if you do that part right, it may still break CF-Root, so make sure to make a backup before trying.
How ?
I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. Took me a few days to get it to this state. If this works right, however, next time it will probably take me a few hours tops
Download
LOOK WELL AT THE FILENAMES, MAKE SURE YOU ARE GETTING THE RIGHT VERSION !
CF-Root-TAB-KA1-v2.2.zip
CF-Root-TAB-JME-v2.2.zip
CF-Root-TAB-JJ7-v2.2.zip
CF-Root-TAB-JMG-v2.3.zip
CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.zip

Old FROYO CF-Root's
THIS IS NOT A ROM - it is only a modified kernel. You need to have the relevant firmware already on your device. You do NOT need to wipe anything for this patch. You DO need to read the instructions. PLEASE READ THIS ENTIRE POST!
THIS IS ONLY FOR GSM TAB. IT MAY WORK ON OTHERS VARIANTS, BUT YOU'RE ON YOUR OWN THERE !
Features
- Root
- Superuser 2.3.6.1
- Busybox 1.16.2 "androidminimal"
- ClockworkMod 3.0.0.0 (RFS) included as standard recovery
- The same Samsung kernel, just with some added files. The kernel is not recompiled.
Instructions (short)
- Make sure, if you just flashed a ROM, to boot this ROM at least once before flashing CF-Root ! (if you don't do this, ROM-based update scripts may not run)
- Flash CF-Root-.....tar (from the attached zip) as PDA in ODIN 1.7, without repartition. Done.
Instructions (long)
- Make sure, if you just flashed a ROM, to boot this ROM at least once before flashing CF-Root ! (if you don't do this, ROM-based update scripts may not run)
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached CF-Root-.....zip (note: it contains a tar file, WinRAR and WinZIP may also extract these... if you end up with a zImage, you extracted twice, instead of once)
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-.....tar
- Put your phone in download mode
- (USB) Connect the phone to your computer
- Make sure repartition is NOT checked
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)
Must know
- It is possible you have a protected bootloader, see this thread, and check if you have a protected bootloader. CF-Root does NOT work on protected bootloaders.
- This is an RFS version of CF-Root, if you have used Koush' CWM and your filesystems have been converted to Ext4, CF-Root will NOT work. You need to reflash a full stock ROM with RFS filesystem to use CF-Root.
- If you are using a lagfix, CF-Root will NOT work!
Root
As normal, "su" can be used to get root if your device is fully booted. If not, for example in recovery, you can use the "rootsh" command.
BusyBox
The included busybox version is 1.16.2, this comes from CWM3. It is NOT needed to install or upgrade BusyBox from Market. In fact, I strongly advise against it.
ClockworkMod 3 / RFS
CF-Root for the Galaxy Tab actually includes ClockworkMod v3 (unlike CF-Root for the Galaxy S) as the default recovery. Booting into recovery will give you CWM3.
This is a heavily modified version of Koush' original CWM3 for the Tab, which uses RFS and has been extensively tested. This took a LOT of work!
Main features (differences from Koush' version):
- Uses RFS instead of Ext4 - no filesystem conversion needed
- Nandroid is fully operational without file corruption
- Backups are stored on internal SD-card
- .android-secure (apps on external SD-card) is backed up and restored
Controls:
- Volume up/down to scroll through the list of options
- Power button to select an item
From version 2.3, a "CWM" entry is listed under applications to reboot into CWM, for your convenience
Important note
A full nandroid restore also restores the kernel from the backup. This will overwrite the CF-Root kernel, if you've made the backup using a different ROM or kernel. Use "advanced restore" to restore only pieces.
A trick:
When upgrading between ROMs, I usually make a nandroid backup before the upgrade, then after flashing the ROM, use "advanced restore" in CWM3 and restore only "data". This often just works. It can cause issues, but it's a neat trick to keep your data and settings between ROMs.
ROM Manager
This version of CWM3 is NOT fully compatible with ROM Manager.
Some things work, some things don't. Really I'd advise to just use CWM from recovery manually.
First time installing ROM Manager, it'll tell you to flash CWM, just pick one of the Galaxy Tab versions and don't worry, it won't be used.
To get into CWM, just select the "reboot into recovery" option.
None of the commands that actually do something in recovery work. For example, you can manage your backups (rename, delete), but the backup and restore options don't work. They will just boot into CWM, and you still have to select backup or restore manually.
If you've used CF-Root 1.3 and 1.4
Major difference: backups are now stored on internal SD-card. Simply move the "clockworkmod" folder from external SD-card to internal SD-card to get access to your old backups. Keep in mind that a restore overwrites the kernel (CF-Root) again, as stated above.
Donate
Buy me a beer, click here - I appreciate it! If you're not going to donate, at least use the thanks button!
How ?
I wrote my own toolchain to ease patching of initramfs, and that is what all this is based on. This is a continuation of my CF-Root for SGS.
Downloads
You will find several files listed. There are for different ROM families.
Go to Settings -> About phone -> Build number. It should say something like FROYO.xxyyy. yyy will be something like JJ1 or JMA. This is the part we are interested in, and would be the JJ* and JM* "family" of ROMs. From the downloads, simply pick the latest file that matches this!
The actual file name notes which version the kernel was taken from. Different kernels from the same family usually work fine.
Is your family of ROMs not listed ? Post in this thread, maybe I can make you a version. You'll have to guinea-pig for testing, though!
( pre-2.2 : 666 )

Changelogs
11.05.2011 - v3.3
- Custom bootanimations were broken in 3.2, now fixed
11.05.2011 - v3.2
- Ported all the updates from the latest SGS CF-Root to SGT:
--- Custom CWM 3.0.0.5 modded for dual EXT4/RFS operation
--- Added CWM Manager application (use this instead of ROM Manager, which is NOT compatible)
--- Added Tweak Manager application
--- Custom boot / init scripts support
--- Custom boot animation and binaries support
--- Different busybox versions are now installable
02.01.2011 - v2.3
- A "CWM" entry is listed under applications to reboot into CWM, for your convenience
14.01.2011 - v2.2
- Startup and shutdown sounds now always removed from /system when patching, to make sure there is space to put SuperUser.apk and su
- Patch status now saved in /system instead of /data. Fixes an issue with reflashing the ROM and re-installing CF-Root, which didn't always work before if you didn't wipe /data.
- Patch status from previous CF-Root versions is now removed
11.01.2011 - v2.1
- If /system is full, CF-Root will try removing the startup and shutdown sounds, then try rooting again. This should solve the issue of some people not actually getting root after flashing.
- "rootsh" command now only works in recovery, no longer in fully booted mode. Prevents sneaky programs from gaining root without you confirming.
- "sh" is now busybox shell only in recovery, and normal shell in fully booted mode. Fixes various issues both with normal commands as well as 3rd party programs.
- "reboot" command now works.
- Commands like "am" and "pm" now work, this allows Eclipse to work with the Tab again.
- Reduced size of zImage. May help people who have trouble flashing.
If you are running 2.0 and it is working fine, there is no strict need to upgrade, unless one of the things above is giving you problems.

Dear chainfire,
Thanks a lot for your efforts. I will try this and post result when i find some spare time.
Kind Regards,

Thanks man any chance for P1000JPJK2

on JM6 here failed and gave me the phone error and no boot. Had to run just pit 1 hidden file with repartition to get it to boot correctly again.
I also tried the euro bootlloader, it installs but then reboots to the galaxy tab screen and stays there.
Lordao

I will give this a try and let you know how guys went.
Update : It completely failed.
{
"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"
}
Oh great, now i cant find out how to download heimdall, to push back my old kernel. Great !

sedde said:
I will give this a try and let you know how guys went.
Update : It completely failed.
Click to expand...
Click to collapse
Same error as me
Lordao

Me too
With fresh Flashed JMD also Error.
Have tryed both JMD Versions.
To bad
Hope you bring it to work.

So all if you are having a flashing error ? That's so weird... will see what I can do about it. Has anyone been able to boot it yet ?
EDIT: From a quick look at other threads about this issue, apparently you need to KEEP ODIN OPEN and keep reflashing until it works. Strange I've never ever seen this error before on my SGS or SGT.

Chainfire said:
So all if you are having a flashing error ? That's so weird... will see what I can do about it. Has anyone been able to boot it yet ?
EDIT: From a quick look at other threads about this issue, apparently you need to KEEP ODIN OPEN and keep reflashing until it works. Strange I've never ever seen this error before on my SGS or SGT.
Click to expand...
Click to collapse
After flashing it once, if you try again you are getting stuck in SetupConnection and its doing nothing. I am willing to try it since i just got a backup of my whole thing, but i cant find heimdall to re-install the kernel back so i have to odin it all the time.

Chainfire , you are the man
It works pretty well with JM6 rom
My previous phone was galaxy s ... so I am quiet aware how to flash...
Next step , will be to update the clockwork recovery as ( access to external SD)
But well done for this release .... It will safe my time to manage my custom rom made

Which Busybox version did you use?

its working on JM4?

same fail error as others have received. Tried both JMC and JM6. Thanks for the effort - keep on trying! Glad to continue to test.

doesnt work on my tab (JM6)

Does not work here either with JMD
Tried to flash it with Odin(WinXp) and Heimdall(ubuntu).
Flashing back the original Kernel with heimdall worked fine.
Sent from my GT-P1000 using Tapatalk

Good news everyone! I've finally been able to replicate the issue. Now trying to find a fix (or WHY the problem occurs )

It seems that CWN doesn't flash on devices that has boot.bin of JJM6 or later...

Yeah I just figured the same thing. I wish I hadn't tried to find out, because I had a JM6 _without_ this problem, now I do have it.
The latest JMx ROMs install a new bootloader that uses signature verification. After flashing, it is impossible to flash sbl, boot, or zImage, if they do not have the correct signature.
That is also why many can no longer downgrade either, the old ROMs also don't have these signatures. If future official ROMs do not have them either, well then, we're all in a very big mess, because we will never get away from these JMx ROMs. We'll be stuck.
I've tried all the tricks listed in the various topic to downgrade, but none of them work if you have done full flash. Major bummer.

[CWM][Fastboot][CDMA/TORO] Clockworkmod Recovery 6.0.1.0

Hello Guys .. this is clockworkmod v 6.0.1.0 By Koush
Now It's The Final build
Here is what Koush said on his G+ Account
ClockworkMod Recovery 6 for Galaxy Nexus
... has been released on ROM Manager.
Changes:
New backup format that deduplicates data between backups.
Faster backups.
Fixed restores > 2GB.
Minor UI tweaks (new background, animated Android)
Future:
In the past, I have merged/rebased every CWM with AOSP. With Jellybean, I have decided this is no longer in the best interest of the project. There are only a few areas of AOSP recovery that are of interest (roots.c - file system, minui, and updater). Those will continue to be merged into CWM. Other than that, doing a full rebase with every code drop has been a giant headache, with the code churn from upstream that providing little to no value to CWM.
In any case, this unties my hands to deviate completely from AOSP, with the primary goal to make a much more polished touch UI.
ROM Manager
ROM Manager is a little over 2 years old, and though it has grown in features quite a bit since its first incarnation, parts are starting to show its age. I've been contemplating a significant UI rewrite for some time now, and will pull the trigger on that shortly. I also want to add in some features that I am hoping will be of some interest:
* A paid ROM section for devs to publish their work and support their hobby.
* Upload your current ROM to ROM Manager for anyone to use, from the device.
* Connect ROM Manager to the Recovery Builder for automatic updates of recovery. No device left behind
Speaking of the Recovery Builder; it has been pleasantly successful. To date, around 1700 recoveries have been built. Many for devices ROM Manager currently does not even support.
Anyways, if you have any suggestions for the future of ClockworkMod products, please drop me a line!.
Click to expand...
Click to collapse
Here Koush explains how the new CWM method works that makes the backup files so small in size
New ClockworkMod Backup Format
TL;DR:
Don't delete /sdcard/clockworkmod/blobs
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c6337ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Click to expand...
Click to collapse
{
"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"
}
Download links
CWM v6.0.1.0
http://goo.gl/Ohcrl
Touch CWM v6.0.1.0
http://goo.gl/DKxEX
Use Fastboot Commands to Flash it
Type " Fastboot Flash Recovery recovery-clockwork-touch-6.0.1.0-toro.img
or Fastboot Flash recovery-clockwork-6.0.1.0-toro.img
I take no credits for the Recovery i'm just trying to share it with you guys it's Done by Koushik as i mentioned
The original Post on G+ : http://goo.gl/jGgl5​

This is a flashable zip for the 6.0 series Touch recoveries, in case anyone wants it. Boot into recovery, install zip, choose zip, go back, go to advanced, reboot recovery, profit. I hold no responsibility if it blows up your phone, but I've tested each one before uploading. So enjoy and thanks to D3vious for the OP.
This is the Flashable zip for the 6.0.0.1 -------> http://dl.dropbox.com/u/17342655/CWM-Touch-6.0.0.1-Toro.zip
MD5 - 4acbc676039817382cab3e6338c1872f
This is the Flashable zip for the 6.0.0.4 -------> http://dl.dropbox.com/u/17342655/CWM-Touch-6.0.0.4-Toro.zip
MD5 - 4cfe0f710120c820915e37948ecc2cd2
This is the Flashable zip for the 6.0.0.5 -------> http://dl.dropbox.com/u/17342655/CWM-Touch-6.0.0.5-Toro.zip
MD5 - 026a7d86db10da65c358f1a67952bc1e

Thank you for posting this. The previous version didn't work well on my end. One press on the volume keys made the selection jump around and sometimes not even register the selection when selected and produce a black screen.
6.0.0.1 works great. I'll flash the touch when i get home.
I wish there was an app like Flash Image GUI that i used for my Evo 3d for the G-NEX. Unfortunately that's way beyond my abilities to cook up. If someone did it would be a money maker. Unless there's a way to trick Rom Manager into flashing the touch recovery
Sent from my Galaxy Nexus using Tapatalk 2

totally forgot I saw this on droid-life. Thanks for reminding me!

xavier86 said:
Thank you for posting this. The previous version didn't work well on my end. One press on the volume keys made the selection jump around and sometimes not even register the selection when selected and produce a black screen.
6.0.0.1 works great. I'll flash the touch when i get home.
I wish there was an app like Flash Image GUI that i used for my Evo 3d for the G-NEX. Unfortunately that's way beyond my abilities to cook up. If someone did it would be a money maker. Unless there's a way to trick Rom Manager into flashing the touch recovery
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Renaming it should work
Sent from my Galaxy Nexus using xda app-developers app

When in the Touch recovery when I go to reboot my device I get this screen that says:
"ROM may flash stock recovery on boot. Fix? THIS CAN NOT NE UNDONE."
The usual multiple NOs and a "YES - Disable recovery flash"
What does this mean? Do I choose yes? or keep hitting no or Go Back when I reboot?
I flashed using the CWMR Touch app which can flash IMG files
Also my background is grey not black?

Maybe I should give it a try.

destinydmm said:
When in the Touch recovery when I go to reboot my device I get this screen that says:
"ROM may flash stock recovery on boot. Fix? THIS CAN NOT NE UNDONE."
The usual multiple NOs and a "YES - Disable recovery flash"
What does this mean? Do I choose yes? or keep hitting no or Go Back when I reboot?
I flashed using the CWMR Touch app which can flash IMG files
Also my background is grey not black?
Click to expand...
Click to collapse
Background being gray is part of the change log, Koush just decided to change it is all. Its normal.
As for your other issue, I'm not sure. Mine definitely hasn't done that
Sent from my Galaxy Nexus using xda app-developers app

bill12690 said:
Background being gray is part of the change log, Koush just decided to change it is all. Its normal.
As for your other issue, I'm not sure. Mine definitely hasn't done that
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
EDIT: Refresh my memory on how to flash with flashboot commands again?? PLEASE
NEVERMIND READ THE WIKI

Saw it on Koush's G+ page don't delete the new "blobs" folder

Edit nevermind.

Works great but now when I reboot from recovery it throws up another menu and talks about stock recovery. Is this something I can delete from the recovery. I just want it to reboot with no warnings. If this is a new feature then that's fine. I am OK with it I just have never had this option and it reboots whether I click go back or yes

6.0.0.4 is out now

Khayos said:
6.0.0.4 is out now
Click to expand...
Click to collapse
Yep. Saw the announcement for the CWM update and got myself 6.0.0.4.

Where can you grab the 6.0.0.4 img file?

Any chance of a flashable 6.0.0.4? In the process of moving, don't have computer available to issue fast boot commands.
Sent from my Galaxy Nexus using xda premium

thenewguy821 said:
Any chance of a flashable 6.0.0.4? In the process of moving, don't have computer available to issue fast boot commands.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Use ROM manager

I did read somewhere you can put it on your SD card and use terminal emulator but have never done it myself. Sorry.

Is anyone else having problems backing up the blobs folder to your PC? Whether I use the Backup SD Card option in the toolkit or just try to drag and drop in Windows it fails to copy.

otaku91 said:
Is anyone else having problems backing up the blobs folder to your PC? Whether I use the Backup SD Card option in the toolkit or just try to drag and drop in Windows it fails to copy.
Click to expand...
Click to collapse
A moderator on AndroidForums said he was having issues with CWM 6.0.0.1 and restoring a NANDRIOD made with it. Has this issue been resolved with this build?

[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!

Credits:
Original version created in the summer of 2011. Thanks to birbeck for the usual random java guidance, slushpupie for his previous java guidance, dodgejcr for extreme amounts of testing, and one_love_420 and shift for some great graphics!
testers: JT-, couga6442, happytweak and many others I might have forgot in the furry of three days I built the initial app from scratch!
Thanks to SDX
Requires:
Unlocked bootloader and root access!
Background:
flash_image (bmlwrite) is an extremely useful utility for flashing custom kernels, boot logos (so far ONLY Samsung devices) and recoveries. This binary has made it possible to easily flash all these items and is used almost everywhere behind the scenes (i.e. in custom recoveries, packaged into a kernel /sbin directory, included in custom ROMs, etc).
Description:
This android application, FlashImageGUI, is basically a GUI interface for the linux binary, flash_image provided by google in AOSP for loading custom kernels and recovery images onto the phone.
This app allows the flashing of kernels and custom recovery images in normal android mode!
Current Device Support:
Full Kernel (Anykernel and boot.img) Flashing and Recovery (zip file or image) flashing: Moto G, Nexus 5, Sprint Galaxy S4, International HTC One, T-Mobile HTC One, Sprint HTC One, HTC EVO 4G LTE, HTC One S, HTC EVO 3D CDMA and GSM, HTC One XL, HTC Droid DNA, HTC Amaze, HTC Vivid/Holiday, HTC EVO 4G, HTC EVO Shift, Google Nexus 4, Google Nexus 10, Google Nexus 7, Samsung Google Galaxy Nexus, Nexus S/Nexus S 4G & LG Optimus
Full Kernel, Logo and Recovery flashing: Samsung Moment, Transform, Intercept and Acclaim - the s3c6410 series of devices
Full Kernel (zImage) Flashing: Samsung Epic
Check application version for updates
Future Support:
Let me know if there are any issues. Feel free to post the encountered issue and a link to the exact file that was flashed. Thanks for the support!
Install Directions:
Install process is the same as any other .apk. Download to computer and adb push or mount sdcard on computer and copy over or download directly to the phone. Use any file manager, adb, connectbot/terminal emulator to install.
My preferred method, maybe a bit technical: ./adb install c:\downloads\FlashImageGUI.apk
Download Locations
Market (99 cents!): Flash Image GUI
Release version (free): Flash Image GUI
Contact:
Any questions, comments, concerns, or issues, please post in this thread or send me an email! Thanks for all the help and support!
FAQ:
Q: Will this app support a marketplace to pick and chose kernels from?
A: No.
Q: Can I flash nandroid kernel backups?
A: Yes. Rename the specific image to boot.img and select from inside of Flash Image GUI. **Make sure to also load the associated modules or WiFi might stop working!
Screenshots:
{
"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"
}
Feedback:
Please post any helpful feedback. I'm always looking to improve the application!
Users Guide for flashing ONLY a Kernel (zip file):
1) Ensure the bootloader is unlocked and root access is properly setup
2) Make sure the selected Kernel is compatible with the currently loaded ROM. If not, this will result in a lot of frustration!!! See troubleshooting steps below.
3) Download kernel zip file to /sdcard.
4) Open Flash Image GUI, browse and select kernel zip file, downloaded/loaded to sdcard in previous step.
5) Flash Image GUI will validate that the kernel zip file contains the minimum required files
6) Select the Flash Image button and Flash Image GUI will load the kernel and the kernel modules from the source kernel zip file.
7) Reboot
Troubleshooting after Rebooting:
First step, when experiencing issues flashing is to RE FLASH the files again. Many times, re flashing again will clear up any issues. If not, see the issues/solutions below.
Issue #1: If the device hangs or reboots while on the splash screen, the kernel itself or the ramdisk packaged in the kernel is NOT compatible with your device!!!
Solution for #1: Have to boot into fastboot (or directly into the custom recovery) and load the custom recovery to flash a known good kernel or restore a previously known good nandroid backup. Command: fastboot boot c:\downloads\cwm-recovery.img
Issue #2: If the device hangs or reboots while on the boot animation, the ROM is likely NOT compatible with the kernel!!!
Solution for #2: Have to boot into fastboot and load the custom recovery to flash a known good ROM/kernel combination either from a zip file or restore from a nandroid backup.

Intresting and useful apps for newcomers

Excellent, I've bought and been using your paid app for quite some time now. It has saved me a lot of time and its super simple. I'm glad your supporting the Moto G as well
Sent from my Galaxy Nexus using Tapatalk

you want more complete? use console:
dd if=(file imput) of=(see above)
recovery -> /dev/block/mmcblk0p32 (only recovery.img)
boot -> /dev/block/mmcblk0p31 (only boot.img)
logo -> /dev/block/mmcblk0p27 (logo locked/unlocked, the same that flash on fastboot)
modem -> /dev/block/mmcblk0p1 (NON-HLOS.bin)
system -> /dev/block/mmcblk0p34 (system fastboot image)
< for more formats check partition layout >
example:
when i flash a recovery that i have downloaded
open terminal emulator:
$ su
# dd if=/sdcards/downloads/recovery.img of=/dev/block/mmcblk0p32
and ready, recovery flashed!

Boss442 said:
you want more complete? use console:
dd if=(file imput) of=(see above)
recovery -> /dev/block/mmcblk0p32 (only recovery.img)
boot -> /dev/block/mmcblk0p31 (only boot.img)
logo -> /dev/block/mmcblk0p27 (logo locked/unlocked, the same that flash on fastboot)
modem -> /dev/block/mmcblk0p1 (NON-HLOS.bin)
system -> /dev/block/mmcblk0p34 (system fastboot image)
< for more formats check partition layout >
example:
when i flash a recovery that i have downloaded
open terminal emulator:
$ su
# dd if=/sdcards/downloads/recovery.img of=/dev/block/mmcblk0p32
and ready, recovery flashed!
Click to expand...
Click to collapse
The directions above or similar variations are likely located in multiple guides on this forum. This thread is dedicated to Flash Image GUI.
In addition, to be comprehensive, the directions posted above will only work reliably for loading the recovery. These directions should not be follow for flashing a kernel as they ignore the kernel modules, which means that WiFi will likely not work as well as all other kernel modules.
For those users who prefer not to type long strings of commands in the terminal, memorize partition locations, or want to flash kernels properly, Flash Image GUI is a great tool, that I provide for free to XDA users!
Thanks for your support!

[TOOL] Lx Multi Tool v1.3.2 [WIN/LIN/MAC][Unlock/Recovery/Stock/Kernel/More]

{
"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"
}
It has LINUX/UNIX and MAC support!
​
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: ​Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.1 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
​
Download links: ​Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
​
[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.​
Known bugs/limitations: ​ - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)​
Changelog: ​
Check the changelog for each release here.
​
Tutorials/FAQ: ​
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload​
Sources: ​The official and original repository can be found here.​
Bug reports/Feature requests: ​If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.​
Licensing: ​Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.​
Tech and stuff: ​Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.​
Donations: ​Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760
​
Disclaimer:​I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.​Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!

I tried to make a backup but it kept on giving an error; oups something went wrong, could not open *path to backup*.
I thought it may be a permission issue, so checked the app had full permissions and granted it admin access too, still didn't work sadly. This is all using Windows 10 x64.

Dodgexander said:
I tried to make a backup but it kept on giving an error; oups something went wrong, could not open *path to backup*.
I thought it may be a permission issue, so checked the app had full permissions and granted it admin access too, still didn't work sadly. This is all using Windows 10 x64.
Click to expand...
Click to collapse
It's a bug of the platform tools used in the package, the latest version of platform-tools should work. I will try to update it today.
Edit: Fixed in 1.3.1

New update with some fixes that should have been implemented a long time ago...
- Fixed Sideload flashing
- Enabled Recovery rebooting
- Fixed open folder for Stock menu

[MOD][Z5] MultiROM v33x

{
"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"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. 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, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
WARNING
It is dangerous. 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 and you will have to flash factory images again. Make backups. Always.​
IMPORTANT
I'm not responsible for anything, you do all this on your own risk.
Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to TheMultiROM Menu (3 bars in the top right corner) to flash ROMs/kernels or other mods.
If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
Your device must not be encrypted.
When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.
INSTALLATION
Make sure you are on a Rom compatible with one of these kernels and flash it or use the non-kexec workaround. (See important Notices)
Reboot into MultiROM TWRP and flash the MultiROM installer
That's it. You can now go to TheMultiROM Menu (3 bars in the top right corner) to start flashing other ROMs.
Adding ROMs
Go to recovery, select TheMultiROM Menu (3 bars in the top right corner) -> Add ROM. Select the ROM's zip file and confirm.​
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. 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 USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.​
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 TheMultiROM Menu (3 bars in the top right corner) 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 TheMultiROM Menu (3 bars in the top right corner) -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/ (branch master)
Modified TWRP - https://github.com/multirom-htc/Team-Win-Recovery-Project (branch android-6.0)
Kernel w/ kexec-hardboot patch - https://github.com/Myself5/kernel/ (branch aosp/LA.BF64.1.2.2_rb4.7)​
FAQs can be found here.
CREDITs
Tasssadar
Olivier
nkk71
Garcia98
Thunder07
skin1980
Envious_Data
[NUT]
Panic Brothers
You might want to consider a Donation to Tasssadar, who is the Mastermind behind MultiROM
​
As well as a Donation to nkk71, who wrote the kexec-workaround and helped me a lot
​
Thanks a lot to those who have donated! The 2 really deserve it!​
XDA:DevDB Information
MultiROM for Sony Xperia Z5, Tool/Utility for the Sony Xperia Z5
Contributors
Myself5
Source Code: https://github.com/XperiaMultiROM/multirom/tree/master
Version Information
Status: Testing
Created 2016-05-08
Last Updated 2016-06-25

Important Notice
This Posts includes Important Notices you need to read if you want to use MultiROM on your Z5.
You need to a kexec-hardboot supporting kernel or the non-kexec workaround as described perfectly by @nkk71 here: http://forum.xda-developers.com/showpost.php?p=64248526&postcount=4 (Be sure to leave him a like!)
Recovery Notice: The Recovery is working with init_sony. If your Kernel is using a older way to load recoverys, then it wont work. Talk to your Kernel dev about using init_sony.
MOST IMPORTANT: When installing MultiROM on Stock, USB Connections will be broken (Charging is fine). It's caused by MultiROM screwing up the permissions of a init file which is responsible for USB. There are Kernels where USB is fixed already. A list of them is in post 3. For intrested Devs, this is how to fix it:
Just add
Code:
chmod 750 /init.usbmode.sh
to the on init step inside of init.sony.usb.rc. It will fixup the permissions MultiROM screwes up.

CHANGELOGs
General MultiROM Changelog can be found here:
Changelog
XperiaMultiROM Specific Changelog is here:
Recovery Changelog
MultiROM Changelog
DOWNLOAD
https://dl.myself5.de
The recovery.img is Tassadars modified TWRP to flash secondary Roms. It is needed to flash the secondary Roms.
SUPPORTED KERNELs
Basically you can use any Kernel you want, if you can live without Touch Support in MultiROM and use the no-kexec workaround.
However, if you want Touch Support as well as fixed USB and kexec-hardboot, use one of these kernels:
OM5Z Kernel
AndroPlus Kernel (not sure if AP Kernel has fixed USB)
If you want your favorite kernel to support kexec or at least working touch and USB, tell the dev to merge my commits.

Nice work mate :good::good:
Though every effort has been made to ensure some form of safeguards and redundancy, MultiROM has always been a "hack", and the no-kexec-workaround is as well.
The no-kexec-workaround is working nicely on HTCs (well at least M7, M8, and M9) and I've seen some other devices using it successfully as well.
As always, have your backups safely tucked away somewhere fully safe.
Happy testing, and feel free to mention me (easiest way for me to get notified), if you think there's an issue to be addressed with the workaround.... I've personally only used it on HTC M7, M8 and M9, so there may be device specific issues, which I cannot account for.
Special thanks to @Captain_Throwback , @ljjehl and @MassStash for all the help and encouragement
And a very special thanks to @z31s1g not only for the official TWRP theme, but all the help he provided bringing it to MultiROM in a very quick way, thanks :good:

Wow this is so nice I was waiting for this! I still have a few questions tho:
-Will this work with stock 6.0 with the modified stock kernel (DM-Verity disabled/ Sony RIC disabled / DRM-FIX) ? I'm worried if it will brick my device since you wrote you have a hard time with stock.
-What is no-kexec? Why do I need it?
-About the USB connection bug on stock so if I install your dirty fix everything will work as before? If I uninstall multiROM I assume the USB bug will go away right?
Thank you for your time sorry I'm a noob

zate27 said:
Wow this is so nice I was waiting for this! I still have a few questions tho:
-Will this work with stock 6.0 with the modified stock kernel (DM-Verity disabled/ Sony RIC disabled / DRM-FIX) ? I'm worried if it will brick my device since you wrote you have a hard time with stock.
-What is no-kexec? Why do I need it?
-About the USB connection bug on stock so if I install your dirty fix everything will work as before? If I uninstall multiROM I assume the USB bug will go away right?
Thank you for your time sorry I'm a noob
Click to expand...
Click to collapse
1. Yes, it will work (You just won't have touch in the MultiROM menu (don't worry, you can setup the kexec workaround to work automatically in TWRP, as well as navigate with the volume buttons inside the MRom Menu). The hard time I get is with porting kexec to the stock kernel.
2. The No-kexec workaround is a (ha, who tought that ) workaround to not use kexec-hardboot. Kexec hardboot is a technology to load a kernel into the RAM using an other kernel. This is how MultiROM usually works. Read more about that here if you're intrested: http://forum.xda-developers.com/showthread.php?t=2104706 . Now, the no-kexec workaround is doing it on a rather dirty (but nicely working) way. It flashes the secondary ROMs boot.img to your boot partition, and then modifies the mount points to link to the ROM files in your internal/external storage (whereever you installed your secondary ROMs). It is needed, because of (1.), and because stock will probably not able to load a AOSP Kernel once kexec is working (so stock can only load stock, and AOSP can only load AOSP. For everything else, you need the no-kexec workaround).
3. Yes. USB is not working, because a script (which is responsible to start the USB Service) has the wrong permissions after booting from the MultiROM Menu (I was not able to include a proper fix for it inside the MultiROM code itself, maybe I will be some day). My App just fixes the permissions and executes the script (which else would be done by the system automatically) (It's basically just executing these 2 commands when pressing the button (or at boot when you turn the autofix on) https://github.com/Myself5/andoid_p...ava/de/myself5/stockusbfix/FixIt.java#L31-L34). Once you remove MultiROM, the script will get its proper permissions back as its a ramdisk file, inside the ramdisk it actually has its proper permissions, it just doesnt when getting extracted from the ramdisk at boot and MultiROM follows (MultiROM messes up the permissions).
I hope that answers your questions, if not, feel free to ask again
P.S. Be sure to read nkk71s Info about how to enable the kexec-workaround in the post I linked in the important notices post, it might shed some more light on what is the non-kexec workaround.

Myself5 said:
SNIP
Click to expand...
Click to collapse
Thank you very much for your quick answer!
So if I understood this right the detailed instructions would be:
Flash TWRP-Multirom-20160507-00-sumire.img or the recovery.img or both(?) with fastboot(?) to get the modified TWRP w/ MultiROM support
Now with this Modded TWRP I need to enable that no-kexec workaround in the settings?
Flash the actual multiROM: multirom-20160507-v33x-UNOFFICIAL-sumire.zip in TWRP
Flash e.g. CM13 (Finally ) from here: http://forum.xda-developers.com/xperia-z5/development/rom-cyanogenmod-13-sony-xperia-z5-t3356163" via the MultiROM menu.
Install the usbfix.
Does the CM13 Rom need to be modified to work with MultiROM or will it work as it is?
Thank you in advance

zate27 said:
Thank you very much for your quick answer!
So if I understood this right the detailed instructions would be:
Flash TWRP-Multirom-20160507-00-sumire.img or the recovery.img or both(?) with fastboot(?) to get the modified TWRP w/ MultiROM support
Now with this Modded TWRP I need to enable that no-kexec workaround in the settings?
Flash the actual multiROM: multirom-20160507-v33x-UNOFFICIAL-sumire.zip in TWRP
Flash e.g. CM13 (Finally ) from here: http://forum.xda-developers.com/xperia-z5/development/rom-cyanogenmod-13-sony-xperia-z5-t3356163" via the MultiROM menu.
Install the usbfix.
Does the CM13 Rom need to be modified to work with MultiROM or will it work as it is?
Thank you in advance
Click to expand...
Click to collapse
1. TWRP-Multirom-Stock-20160507-00-sumire.img is the recovery you need. Flash it via
Code:
fastboot flash recovery TWRP-Multirom-Stock-20160507-00-sumire.img
(If the Stock is not working, use the other one, I don't know which of the 2 existing recovery loading tools your kernel is using).
2. First flash multirom, then enable it in the MultiROM Settings Tab inside TWRP (see important notices on how to do that, nkk71 describes it in the thread)
3. yes.
4. Exactly.
5. Yes, only needed for stock roms, don't forget that. Oh, and it requires root, so depending if you have root already, you also need to install SuperSU (use 2.71 beta, it worked fine for me)
6. No, the secondary Roms don't need any changes at all.
BTW, your questions seem to be common, do you mind if I copy them together with my answers to a little FAQ in post 2?

Myself5 said:
1. TWRP-Multirom-Stock-20160507-00-sumire.img is the recovery you need. Flash it via
Code:
fastboot flash recovery TWRP-Multirom-Stock-20160507-00-sumire.img
(If the Stock is not working, use the other one, I don't know which of the 2 existing recovery loading tools your kernel is using).
2. First flash multirom, then enable it in the MultiROM Settings Tab inside TWRP (see important notices on how to do that, nkk71 describes it in the thread)
3. yes.
4. Exactly.
5. Yes, only needed for stock roms, don't forget that. Oh, and it requires root, so depending if you have root already, you also need to install SuperSU (use 2.71 beta, it worked fine for me)
6. No, the secondary Roms don't need any changes at all.
BTW, your questions seem to be common, do you mind if I copy them together with my answers to a little FAQ in post 2?
Click to expand...
Click to collapse
Thanks for answering all my questions. That should have cleared it up for noobs like me
The instructions seem a bit summarily written so your answers help a lot.
Yes sure go ahead FAQ is always nice

noob flasher here not quite got this fully working with a secondary rom yet still trying, but one scenario I can't get my head around.
If your primary rom is stock no root. How can you install the usbfix? Is this scenario possible?

bongo1 said:
noob flasher here not quite got this fully working with a secondary rom yet still trying, but one scenario I can't get my head around.
If your primary rom is stock no root. How can you install the usbfix? Is this scenario possible?
Click to expand...
Click to collapse
Nope. USB Fix needs root to work. I am still working on a different workaround for it (maybe inside MultiROM), but thats lower priority.
Sent from my Xperia Z3 using Tapatalk

@Myself5 , hey.
Could you extend support to the z5 premium too maybe ?
Thanks
Regards
AVK

Ashray_Vk said:
@Myself5 , hey.
Could you extend support to the z5 premium too maybe ?
Thanks
Regards
AVK
Click to expand...
Click to collapse
I don't develop for devices I don't own, as I then can't guarantee that everything does work nor that it won't break someones device. If there is a developer working on satsuki who wants to port it and comes across problems, I'll gladly help, but I'm not going to blind-port it on my own, I hope you understand that

Hey I have the E6653 and I'm getting error 7 while flashing multirom. Recovery flashing was successful tho. Why am I getting the error the codename of my phone should be "sumire" or is there something I've missed?

zate27 said:
Hey I have the E6653 and I'm getting error 7 while flashing multirom. Recovery flashing was successful tho. Why am I getting the error the codename of my phone should be "sumire" or is there something I've missed?
Click to expand...
Click to collapse
hum, 6653 is what I have too. What did you flash it on? Which recovery did you use? The Stock or the other one?
Sent from my Xperia Z3 using Tapatalk

Damn man you answer fast
I flashed it via TWRP, TWRP 3.0.2-0 (wrong I guess), I tried to flash the stock recovery one
Here is my fastboot output:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users
\Pein\Downloads\TWRP-Multirom-Stock-20160507-00-sumire.img
target reported max download size of 536870912 bytes
sending 'recovery' (33988 KB)...
OKAY [ 1.118s]
writing 'recovery'...
OKAY [ 0.464s]
finished. total time: 1.584s
Seems like it wasn't successfull because TWRP seems like the same as before :/ Should I try the other recovery? (Without stock)

zate27 said:
Damn man you answer fast [emoji14]
I flashed it via TWRP, TWRP 3.0.2-0 (wrong I guess), I tried to flash the stock recovery one
Here is my fastboot output:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery C:\Users
\Pein\Downloads\TWRP-Multirom-Stock-20160507-00-sumire.img
target reported max download size of 536870912 bytes
sending 'recovery' (33988 KB)...
OKAY [ 1.118s]
writing 'recovery'...
OKAY [ 0.464s]
finished. total time: 1.584s
Seems like it wasn't successfull because TWRP seems like the same as before :/ Should I try the other recovery? (Without stock)
Click to expand...
Click to collapse
which kernel are you using?
BTW: MROM TWRP looks pretty similiar to the default TWRP, it just has 3 bars in the upper right corner which opens the Mrom Menu.
Sent from my Xperia Z3 using Tapatalk

kexec and Stock!
All right. I finally managed to get kexec-hardboot working on stock. I ported it to @AndroPlus Kernel at a first, because it seems to be the kernel you people use. I also uploaded a flashable zip (I used AndroPlus' flashable zip as a base), you can find it here:
Boot.img: http://dl.myself5.de/sumire/MultiROM/boot_E6653_M5_AP.img
Flashable ZIP: http://dl.myself5.de/sumire/MultiROM/Z5_AndroPlusKernel_M5_ModZ_Edit_Permissive_v27.zip
Source for it would be here: https://github.com/Myself5/android_kernel_sony_msm8994_kitakami_r2
I also send a PR for it to @AndroPlus (https://github.com/AndroPlus-org/android_kernel_sony_msm8994_kitakami_r2/pull/3)
(Ramdisk is from AndroPlus Kernel v27, with the fix below)
Oh, and because I am badass, I also fixed up USB on Stock with that Kernel.
For every Stock Kernel Developer who's intrested how I did that (looking at you @AndroPlus and @zacharias.maladroit), I simply adjusted the USB files permissions in the ramdisk.
Just add
Code:
chmod 750 /init.usbmode.sh
to the on init step inside of init.sony.usb.rc. I know it's dirty.. but hey. It surely is less dirty than my hacky App (which therefore is no longer needed BTW).

Will suzuran devices work

killedbyghost58 said:
Will suzuran devices work
Click to expand...
Click to collapse
No.
Regarding porting requests its the same as for Z5 Premium. If I don't own the device, I'm not going to port Mrom to it.
HOWEVER: For suzuran specifically, @oshmoun is working on porting MultiROM to it, based on my device trees which means MultiROM for Z5C is coming in the nearish future.