Database Users

[MOD] MultiROM

this is beta release. for t900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/show....php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock firmware as primary. you can flash cm as additional.
Installation:
1. https://yadi.sk/d/9t2yfkIPc7yPj - this is modded recovery. flash via odin (updated 19/10. Thanks to @arcadia2uk for fix flashing bug)
2. https://yadi.sk/d/TtXcwe6Hc54cR - patched stock kernel
https://yadi.sk/d/r2lnH3N3c54eF - multirom main program
flash through modded recovery patched kernel and multirom.
uninstallation:
https://yadi.sk/d/r9ZLm0vCc68um - flash this uninstaller through recovery, then flash original twrp
known issues:
- 1920x1200 resolution in twrp
- in List Roms installed roms dont shown
- in multirom boot menu touchscreen downt work. use buttons (vol-,vol+,power)
multirom apk from play store doesnt support this release.

reserved

more reserved

bonuzzz said:
this is beta release. for t900 only.
I'll write full instruction later. For full description see http://forum.xda-developers.com/show....php?t=2011403
I'm not sure that everything is stable, so I dont publish source code. I dont want to distribute buggy sources. thanks for understanding.
for stock firmware only. for now. use stock frimware as primary. you can flash cm as additional.
Click to expand...
Click to collapse
Nice, I have to try this later on. I noticed that after having installed CM11, I can no longer flash touchwiz (I deleted my back-up, as I no longer needed it...), why I probably have to start all over and use Odin to re-install stock and then install multi ROM on top of it. I will look into it once I get some time over.
When you are saying "stock firmware", could this be any customized touchwiz ROM?
PS the link to the MultiROM decription does not work, here is the correct one http://forum.xda-developers.com/showthread.php?t=2011403

arcadia2uk said:
Nice, I have to try this later on. I noticed that after having installed CM11, I can no longer flash touchwiz (I deleted my back-up, as I no longer needed it...), why I probably have to start all over and use Odin to re-install stock and then install multi ROM on top of it. I will look into it once I get some time over.
When you are saying "stock firmware", could this be any customized touchwiz ROM?
Click to expand...
Click to collapse
yes, every touchwiz rom
I have to recompile cm kernel to support multirom. I'll do it later. It depends on Valera's decision whether support t900 or not.

bonuzzz said:
this is beta release. for t900 only.
Installation:
1. https://yadi.sk/d/Sm4V4SMDc54ay - this is modded recovery. flash via odin
uninstallation:
https://yadi.sk/d/Sm4V4SMDc54ay - flash this uninstaller through recovery, then flash original twrp
Click to expand...
Click to collapse
It doesn't seem correct that the modded recovery and the installer has the same d/l link?
---------- Post added at 11:35 PM ---------- Previous post was at 10:52 PM ----------
bonuzzz said:
yes, every touchwiz rom
I have to recompile cm kernel to support multirom. I'll do it later. It depends on Valera's decision whether support t900 or not.
Click to expand...
Click to collapse
When trying to flash the recovery with Odin there's an error message saying that the MD5 Hash value is invalid, recovery_mr_t900.tar.md5 is invalid.

I recompiled recovery and refreshed links. try again to flash.

bonuzzz said:
I recompiled recovery and refreshed links. try again to flash.
Click to expand...
Click to collapse
Odin is still diplaying the message that md5 is invalid.
Maybe a file w/o md5 would work?

arcadia2uk said:
Odin is still diplaying the message that md5 is invalid.
Maybe a file w/o md5 would work?
Click to expand...
Click to collapse
unpack archive and try to flash recovery.img with flashify. maybe change version of odin. i use 3.09.3

bonuzzz said:
unpack archive and try to flash recovery.img with flashify. maybe change version of odin. i use 3.09.3
Click to expand...
Click to collapse
I renamed the tar file by taking away the .md5, that worked.
The boot with the stock ROM went fine. However, I tried install my cm11 by restoring a backup and got stuck, or so I thought it actually came to life after having looked a SOD for 5 min. so I guess it went well. Next problem is that when I'm on the MultiROM boot menu it doesn't give me the option to select the alternative ROM, but makes the countdown and then boots internal. There is no possibility for me to select my alternative ROM as the blue strip does not react to touch. Well, I hope you understand what I mean...
---------- Post added at 09:59 AM ---------- Previous post was at 09:29 AM ----------
bonuzzz said:
unpack archive and try to flash recovery.img with flashify. maybe change version of odin. i use 3.09.3
Click to expand...
Click to collapse
It might also be linked to the fact that the recovery is trying to validate the ROM as a v2awifi, while it should be v2wifixx on the T-900.
I assume the recovery.img need to be modified?
---------- Post added at 10:19 AM ---------- Previous post was at 09:59 AM ----------
It's actually as simple as touch mode that is disabled in the bootmenu, and you have to use up/down keys to select and power key to confirm your ROM choice (I bet it says this in the OP already...)
Now when that is cleared out it seem to be running great, but as I need to test drive another T-900 Rom I have to uninstall it as I need original TWRP to flash that ROM, due to the naming convention.
After all this gave me the opportunity to test the uninstaller that also worked well
.
So the only issue is the Recovery naming convention the T-900 should be v2wifixx.
This is how I came to have the v2wifixx:
TWRP 2.8.0.0 downloaded from http://www.techerrata.com/browse/twrp2/v2wifixx where I selected openrecovery-twrp-2.8.0.0-v2wifixx.img.tar and flashed it with Odin 3.07. This is the most common version for T-900 owners, as they followed the posted instructions HERE. It's also the version for which Valeria ported the cm-11.

I dont have t900, so i dont know these details
v2wifixx or v2awifixx?

bonuzzz said:
I dont have t900, so i dont know these details
v2wifixx or v2awifixx?
Click to expand...
Click to collapse
v2wifixx is the one. (no a after the 2)
But as I mentioned, apart from the small glitches you mention in the OP everything runs smoothly, and what a relief it is to quickly transfer between different ROMs. Great work, I just wished we had a decent touchwiz ROM for the T-900... Thank you, Great work (but I'm getting used to it ) With this, the only thing I had wished for is a 64G internal SD, rather than the 32G I have, unfortunately you can't perform miracles Bonuzzz.
I've been looking into MultiROM before, bet never saw the need for it, but after this experience I have also installed it on my HTC One (m8) which allows me to test ROMs quickly and smoothly, what a difference it makes.

Updated 10/18/2014 08:40am EST
Temporary work around:
1. backup you TouchWiz ROM* (TW),
2. install cm11(s) prior to MultiROM and make a backup,
3. recover your TW, and
4. proceed with MultiROM install after Bonuzzz's instructions in post 1
Once a fixed recovery is available, simply flash this new recovery image and you're good to go. As of that point you can update cm11 nightly's on the go.
HOW to Updating/changing ROMs
Primary ROM (Internal)
- Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs) (note: don't forget fixed kernel)
- Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
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.
* I installed Bonuzz's Custom ROM 1.0.1 (for the P-900) and flashed his MultiROM kernel (see post 1) on top of it. And with no other modifications it seems to work perfectly well. I have only encountered a single minor issue, auto screen-rotation didn't work, but mine is always locked in landscape anyway. I froze the TouchWiz launcher and using Google Now Launcher instead, it couldn't be done w/o freeze, and also fixed an issue with incorrect cropping of my wallpaper. After all everything is good, and as always a great performance by Bonuzzz. Thank you/arc

reuploaded recovery. try again.

bonuzzz said:
reuploaded recovery. try again.
Click to expand...
Click to collapse
It looks like you accidentaly re-uploaded the same file, I have the same error message saying:
This package is for device: v2wifixx; this device is v2awifi.
E:Error executing updater binary in zip '/tmp/mr_update.zip'
Click to expand...
Click to collapse

arcadia2uk said:
It looks like you accidentaly re-uploaded the same file, I have the same error message saying:
Click to expand...
Click to collapse
you talked about multirom file but wrote recovery. i tried to find problem in wrong place.. redownload again

bonuzzz said:
you talked about multirom file but wrote recovery. i tried to find problem in wrong place.. redownload again
Click to expand...
Click to collapse
I sent you an e-mail about the problem a few minutes ago

Am I correct to assume that the only way to install cm-11 with gapps is by flashing a backup under MultiROM?
Or, at least until you can get the Advanced/MultiROM/List ROMs option corrected, since that seems to be to only place where you can flash a .zip on top of an existing ROM, and this install option only allow you to make a simple flash, or have I missed something?

bonuzzz said:
reuploaded recovery. try again.
Click to expand...
Click to collapse
Do I feel that you're abandoning this project, when you're this close....

[WORKAROUND - MULTIROM] How to avoid "error executing updater binary in zip"

[WORKAROUND - MULTIROM] How to avoid "error executing updater binary in zip"
When trying to add a secondary ROM using Multirom on my 1+1 64GB, I found out that in most cases is impossible to flash it because you get this error:
"error executing updater binary in zip..."
and the installation aborts.
I'm not a modder / builder / programmer / hacker, and googling didn't helped, so I tryed a logical workaround (for my brain) and it seems to work!
Let's say that ROM-1 is your primary one, and ROM-2 is the one you want as secondary but you got the error
You can do this in the same recovery session, without to reboot in the middle.
1) enter your TWRP and make a nandroid backup of your ROM-1 (to restore later)
2) do the standard factory reset wipe of primary rom to be safe
3) flash ROM-2 as primary rom
4) make a nandroid backup of primary rom (so you will have a backup of a clean ROM-2)
5) do the standard factory reset wipe of primary rom to be safe
6) restore your ROM-1 backup to have your primary rom again
7) go in Advanced -> Multirom -> Add Rom -> From Backup -> and choose your ROM-2 backup
8) flash it!
9) reebot system
Now in the Multirom booting menu you should be able to boot the secondary rom, that is named like the ROM-2 backup name you choosed.
Hope this works for you too!

Sounds like a reasonable workaround, it will take more time but if it works it's ok !
did you tried to install some CM12 or Lollipop 5.0 roms in that way?
if yes, which ones?

seblog said:
Sounds like a reasonable workaround, it will take more time but if it works it's ok !
did you tried to install some CM12 or Lollipop 5.0 roms in that way?
if yes, which ones?
Click to expand...
Click to collapse
For now in this way I installed these Lollipop based roms, that with normal method gave error:
http://forum.xda-developers.com/one...rom-liquidsmooth-v4-0-bacon-pre-alfa-t2938615
http://forum.xda-developers.com/oneplus-one/development/rom-slimsaber-bacon-t2858033
http://forum.xda-developers.com/one...m-bliss-stalk-team-bliss-bacon-10-28-t2921057
:good:

Temasek for example has a modded updater script. I'm no coder lol but I wonder if it is specific to the temasek ROM? If not it could be used also. Apparently you can use an app called Zarchiver to replace the updater script, or 7zip on a computer.
Sent From Bacon

Many thanks for your message. I have the exact same problem with LP based roms. However, SlimSaberLP seems to be an exception. I have CM12 20141124 Unofficial as my primary rom and SlimSaber is the only LP based rom that will install and boot. All KK based roms install as secondary fine.
Wonder if there is a shorter work around?
@ek69 what is the updater script and how do you install it?
Thanks!
Edit: Ok I've just tested this method and it works well. Installed Liquidsmooth LP rom which seems to be running great.

@Djevoultion I have tested and used the zarchiver app method I said myself many times and it works without using this work around (so it's much easier and simpler). The thing is the updater-script file must be modified by the Dev to allow the lollipop ROM to be installed as secondary in multirom. Temasek unofficial cm12 has an updater-script modified that is provided by the Dev that allows it, and as far as I know is specific to that ROM.
Sent From Lollipopified Bacon Goodness!

[Q] error excecuting updater binary in zip with twrp

hi guys when I try to flash a rom appears the message "error excecuting updater binary in zip" someone know how to solve it?
Sorry for my bad english

Your English is fine. Check to make sure there are no spaces in the file name, and if there are, replace them with dashes or underscores. Then try running the zip again.

Strephon Alkhalikoi said:
Your English is fine. Check to make sure there are no spaces in the file name, and if there are, replace them with dashes or underscores. Then try running the zip again.
Click to expand...
Click to collapse
there is no space in the name :\ maybe can be a problem of the recovery's version ?

I mentioned it because the presence of spaces was the reason my copy of Optimized CM12 failed to install. What version of TWRP are you running?

2.8.5.0

Upgrade. 2.8.6.0 is available from the TWRP homepage (once the page comes back up), though I believe a customized copy is available for Alucard and Antares One's Optimized CM12 build in I9505 Original Android Development.
EDIT: 2,8.6.0 can be downloaded from here.

AntaresOne's TWRP will convert the system to F2FS automatically when flashing a rom. He said he was going to make it a choice in a future update. Don't know if he gotten around doing so.

GDReaper said:
AntaresOne's TWRP will convert the system to F2FS automatically when flashing a rom. He said he was going to make it a choice in a future update. Don't know if he gotten around doing so.
Click to expand...
Click to collapse
This problem started when I tried to flash cyano 12 based on 5.1.1 (by AntaresOne) before doing this everything was fine. Maybe the recovery couldn't convert system to F2FS, can be this?

Strephon Alkhalikoi said:
Upgrade. 2.8.6.0 is available from the TWRP homepage (once the page comes back up), though I believe a customized copy is available for Alucard and Antares One's Optimized CM12 build in I9505 Original Android Development.
EDIT: 2,8.6.0 can be downloaded from here.
Click to expand...
Click to collapse
Thank you, I will try it

eleonora97100 said:
Thank you, I will try it
Click to expand...
Click to collapse
It doesn't necessarily needs to be converted. It can run with the default ext4 too. Problem with converting is that it will wipe your internal storage. So that into account.

I had the binary updater issue occur on a flashable zip I made. The cause? I accidentally deleted the line that told TWRP to mount the system partition. Restoring the line solved the issue, so check the script. The developer may have accidentally missed a line.

thank you guys I upgraded the recovery and now it works fine thank you very much

[Help] I can't root or install cm

Hi.
I bought the nvidia shield android tv pro (500GB model). the built-in OS is... well you probably know it`s bad...
so I installed the custom rom from here http://forum.xda-developers.com/android/development/rom-t3138575
the custom rom works fine and I just wanted to install cm and supersu. however, when I boot TWRP (2.8.6.0) and try to install, it fails (can`t mount storage).
I tried it a few times and couldn't get it to work.
the only solution I can think of is installing TWRP (instead of just booting to it). should I do that? I thought it`s best to keep the original recovery.
Thanks!
Images attached.

I'm not an expert, but I had trouble rooting too. With my 16 GB model I had to manually mount the relevant partitions in TWRP (fill in the checkboxes in "Mount") before I flashed SuperSU. Also, it appears that you're using teletype's TWRP? I think that's for the 16 GB model only. Make sure you're using Steel01's latest version here: http://forum.xda-developers.com/and...very-twrp-2-8-6-0-shield-tv-variants-t3140926
Also, what do you mean by "install cm"? Because there's not yet any working build of CyanogenMod that I know of for this device.

BenjiHansell said:
I'm not an expert, but I had trouble rooting too. With my 16 GB model I had to manually mount the relevant partitions in TWRP (fill in the checkboxes in "Mount") before I flashed SuperSU. Also, it appears that you're using teletype's TWRP? I think that's for the 16 GB model only. Make sure you're using Steel01's latest version here: http://forum.xda-developers.com/and...very-twrp-2-8-6-0-shield-tv-variants-t3140926
Also, what do you mean by "install cm"? Because there's not yet any working build of CyanogenMod that I know of for this device.
Click to expand...
Click to collapse
I tried manualy mounting... it doesn't mark the checkbox, only logs 'can`t mount /...' .
I used the TWRP posted in this forum (all varients) - the same one you sent.
by "install cm" I meant "install google`s stuff":
Gapps for CM 12.1 arm64 version: http://wiki.cyanogenmod.org/w/Google_Apps
(from here http://forum.xda-developers.com/android/development/rom-t3138575)
basicaly I don't have to root. it's just a bonus. however, I do HAVE to install somehow google`s apps (mainly the play store). how do I do that?

i installed the default supersu that come with the twrp and the update supersu trough the play store and issues was fixed, it was the easier thing to do, goo luck

aniel300 said:
i installed the default supersu that come with the twrp and the update supersu trough the play store and issues was fixed, it was the easier thing to do, goo luck
Click to expand...
Click to collapse
how do I do that? and I don't have a play store, I installed that custom rom.

ohh im sorry i did not read your post but you should ask the developer of the rom and/or install latest trwp available, best luck

Android N Preview 2 npc91k (flashable & image with no encryption and dm verification)

Android N Preview 2 npc91k (flashable & image with no encryption and dm verification)
This thread is for the second Android N Preview.
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​** The following are instruction for installing Android N Preview 2 image released by Google on 4/13/2016. After the installation you will have TWRP recovery 3.0.2-0 with the data partition erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **​Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery (keeps your data and current recovery)
1- You need to have TWRP installed on your phone.
2- Download this flashable zip..
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N Preview 2. If your internal storage is unencrypted before flashing it remains unencrypted.
For some people this didn't work. It seems to be the case when you have been encrypted by your previous Android N installation, in which case TWRP seems to have difficulty reading the file, and that seemingly Preview 2 doesn't play nice with TWRP. It works best when you are unencrypted and your recovery is 3.0.2-0. Thanks to @gammaxgoblin, @blitzerking1, @Michael in ATL, @HueyT, and @PhillyFlyer for debugging and hints.
Method 2: Flash update using a computer (wipes everything, unencrypts data, and upgrades TWRP)
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N with unencrypted internal storage. Your TWRP is also upgraded to 3.0.2-0.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root and other issues
To obtain root after installing this update you should flash SuperSU 2.71 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133. Despite the fact that SuperSU 2.71 is supposedly re-written for Android N, there are still some apps that seem to have a problem obtaining root. The commonest complaint on this thread so far has been about Adaway. If you want to block Ads just manually do what Adaway does. Download a hosts file from any ad block list server such as http://winhelp2002.mvps.org/hosts.htm, copy the files on your sdcard, boot the phone into recovery, and using the TWRP file manager replace the file /system/etc/hosts with this file and set its permissions to 644 (rw-r--r--).

wouldnt flash first go. redl now
no flash again

gammaxgoblin said:
wouldnt flash first go. redl now
no flash again
Click to expand...
Click to collapse
Same happened to me. It would not flash, same error

gammaxgoblin said:
wouldnt flash first go. redl now
no flash again
Click to expand...
Click to collapse
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?

najoor said:
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
Click to expand...
Click to collapse
Same error for me as well. I can extract the zip and view the file it is talking about. I also tried on TWRP 3.0.1-0 and TWRP 3.0.2-0
Everything is working perfect for me with the new zip. I have a unencrypted phone and used 3.0.2 TWRP.

najoor said:
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
Click to expand...
Click to collapse
i tried 3.0.1 and 3.0.2 and i can also see the file

Method 2 works great

Method two works I used it myself

Shall I flash preview 2 directly from marshmallow?

Seems like TWRP is having a lot of troubles with each version of N Preview's encryption. I have same problem with both N6 and N6P, as do others in that forum too....:/

i have latest twrp, download a ota update from ofiicial site in zip file and flash it over in twrp. boot normally and works fine. only flash supersu 2.71 and it's unencrypted at all.
ps. TB not works for me ind N prew2 so i flash perv1, restore from TB and flash prew2 over it.

marius987 said:
i have latest twrp, download a ota update from ofiicial site in zip file and flash it over in twrp. boot normally and works fine. only flash supersu 2.71 and it's unencrypted at all.
ps. TB not works for me ind N prew2 so i flash perv1, restore from TB and flash prew2 over it.
Click to expand...
Click to collapse
Sorry for the stupid question. What do you mean for TB?

cerico76 said:
Sorry for the stupid question. What do you mean for TB?
Click to expand...
Click to collapse
I'm going to assume it stands for Titanium Backup.

Waiting for fixed method #1

outkastz said:
I'm going to assume it stands for Titanium Backup.
Click to expand...
Click to collapse
Ah,yes! Thanx!

Can someone please provide a link to the desktop website for the flashable zip?

Just to help with the installation of method 2, holding shift and right clicking a blank space in your unzipped folder, you can click open command window here. That will save you having to CD all the way to it.
Sent from my Nexus 6 using XDA-Developers mobile app

I did method 1. It upgraded fine. All my data remained. It killed root (expected this) and my TWRP. I was unencrypted before attempting.
I went and downloaded the latest TWRP and flashed via fastboot. Then downloaded latest SuperSU from http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 and flashed it via my newly installed TWRP. Root confirmed and all is well.
Good to go Thanks!

I've got an "Invalid boot image" issue :
Any tought ?

outpox said:
I've got an "Invalid boot image" issue :
Any tought ?
Click to expand...
Click to collapse
You may have to flash a previous stable release of marshmallow or lollipop from Google first and then try this because something seems to be corrupted in your system.