yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] Mahdi786:
Re: [WiFi&3G] MultiROM v9 (updated recovery)

Hi everyone, can I use a different kernel for each ROM?
[Nexus 7 Original Development] daveheart14:
Yes, it is in zip format or img, there are no problems. More, by choosing the option "Dont share" when installing a new rom, it will retain its original kernel.

Excellent, have thought about integrating Pong in MultiROM ;)

Thank you again for this great mod
[Nexus 7 Original Development] rifraf1:
fstrim function

Can this app be used with a multirom setup. I am not even sure if the fstrim function works or is a placebo, either way I was wondering if it will mess with the N7 file system if it is setup to run multirom? Will it work for the current ROM data/cache/system partition that you are booted into only or will it affect all the multirom directory files that are installed?

Any one tried this or have any opinions?
[Nexus 7 Original Development] farmerbb:
So today, I updated my Ubuntu desktop install on my tablet using apt-get dist-upgrade, and it looked like there was an update to the flash-kernel package. Needless to say, it overwrote the "disabled" one and flashed an updated kernel, and when I tried to reboot my tablet into Android it just bootlooped. Thankfully I fastboot flashed franco.Kernel again and re-injected MultiROM to get my tablet working, and made sure to disable flash-kernel again. Just an FYI for anyone that uses Ubuntu with MultiROM, take caution when updating using apt-get :)
[Nexus 7 Original Development] EvanA:
fstrim is the linux trim utility for SSDs. It is definitely not a placebo. Here's an explanation of trim and why you need it. http://www.apartmenttherapy.com/trim-that-drive-why-trim-matte-142681

And trim will work fine with multirom because it's a hardware level operation. You only need to run it in one rom because if effects the entire flash storage.

EDIT: Also take a look at the LagFix xda thread. http://xdaforums.com/showthread.php?t=2104326
[Nexus 7 Original Development] Edwin184:
Hm, apparently I have been lucky as I also did an apt-get upgrade on my Ubuntu. It stopped the first time but after rebooting my Nexus and first reparing and then doing it a second time it worked well. Thanks for the warning but I thought Android and Ubuntu didn't share?
[Nexus 7 Original Development] SGWUser:
Re: [MOD][12 MAR] MultiROM v9 (updated recovery)

No, they don't share, but if you install a kernel inside Ubuntu, it will install the kernel to the default kernel path and that's where the Androidkernel is located. Normally, your Ubuntukernel is located inside the /sdcard/multirom folder somewhere, but because Ubuntu doesn't know it is installed through MultiROM it installs on the Androidkernel path.

Correct me if I'm wrong please :)
[Nexus 7 Original Development] Edwin184:
I hope you are as that would make any update a risk ;) . I understood that mountpoint / is specified at boot-time but I'm no expert at all.
[Nexus 7 Original Development] EvanA:
Re: [MOD][12 MAR] MultiROM v9 (updated recovery)

You're absolutely right. Now, multirom should have taken care of disabling flash-kernel when you installed ubuntu. It's possible you didn't install ubuntu after this was added to the recovery (1/30/2013). That aside, you shouldn't use dist-upgrade when updating ubuntu, just use upgrade and you should be safe.

Sent from my AOSPA 3.+ (self compiled) and m-kernel+ mr1 Nexus 7
[Nexus 7 Original Development] Tasssadar:
Yeah, after that recovery update, Ubuntu should not flash the kernel into boot partition. But I disagree with "do only apt-get upgrade", beause upgrade won't install new packages - for example new kernel. That might result in some features not working properly, because something needed the kernel update (it actually happened with the screen rotation, somebody on #ubuntu-arm didn't do dist-upgrade and the rotation just wasn't working).
[Nexus 7 Original Development] EvanA:
Re: [MOD][12 MAR] MultiROM v9 (updated recovery)

I'm just speaking solely on development releases of ubuntu. Sometimes dist-upgrade causes breakage and other issues. But since 13.04 is almost stable I suppose it's safer now.

Sent from my AOSPA 3.+ (self compiled) and m-kernel+ mr1 Nexus 7
[Nexus 7 Original Development] dwxvi:
Strange problem with removed MultiROM installation.

A few weeks back I decided to give MultiROM a try considering I like flashing ROMs so much on my N7. However, I was not able to get to a computer and properly flash the modified recovery to accompany it, so I restored my backup from earlier.

Now there is a folder labeled MultiROM that is in my storage and no matter how many times I attempt to delete it, it just keeps coming back.
[Nexus 7 Original Development] EvanA:
Did you try deleting it from recovery?

Sent from my AOSPA 3.+ (self compiled) and m-kernel+ a46 Nexus 7
[Nexus 7 Original Development] rebel1699:
Re: [MOD][12 MAR] MultiROM v9 (updated recovery)

It is protected. Use a file explorer with root permissions and go to /data/media/0 and you should be able to delete from there.
[Nexus 7 Original Development] FitAmp:
EDIT : solved by reflashing multirom and repatch init
[Nexus 7 Original Development] FitAmp:
Re: [MOD][12 MAR] MultiROM v9 (updated recovery)

I am unable to boot Ubuntu from flash drive I'm running latest mkernel and my USB is ext3 formatted
[Nexus 7 Original Development] rebel1699:
Re: [MOD][12 MAR] MultiROM v9 (updated recovery)

What type of flash drive? 3.0? A 2.0 stick will be painfully slow. Also, can you not boot it, or does it not show up in the usb menu? Does it freeze? Loop? More specifics for better help. I personally use ext4.
[Nexus 7 Original Development] FitAmp:
Re: [MOD][12 MAR] MultiROM v9 (updated recovery)

In the multirom menu it is not recognized. But in recovery it is.

USB 2.0 8gb drive
[Nexus 7 Original Development] daniel.alomar:
Can not boot internal ROM

Hi,

I have installed CM 10.1 besides the internal one and Ubuntu on a external SD. I was able to boot all the ROMs, but lately I was using just the CM one, upgrading it and using the "Inject curr. boot sector" option. But I do not know when, something has changed 'cause I have the "Internal" rom option at MultiROM menu but when I choose it, It appears the CM animation boot logo but nothing happens. Inside the TWRP recovery I can not see the internal ROM when I list them, it only appears. Can I recover the internal ROM without to have to restore to the stock factory image?

Regards,
[Nexus 7 Original Development] rebel1699:
Re: [MOD][12 MAR] MultiROM v9 (updated recovery)

Resrart your n7 with the usb stick unplugged. When you get to the multirom menu, click the usb tab. Plug in the usb stick. After a few moments, it will show up. But be warned, the speed on a usb 2.0 stick will be terrible. Usb 3.0 and external hdd are by far the most practical choices.
[Nexus 7 Original Development] FitAmp:
Re: [MOD][12 MAR] MultiROM v9 (updated recovery)

Just found out mkernel has no ext3 support, trying ext4 right now.

Thanks for the info :)
[Nexus 7 Original Development] rebel1699:
Re: [MOD][12 MAR] MultiROM v9 (updated recovery)

If you are using Ubuntu, the kernel should not matter as it uses its own kernel. When you i stall it, you have to make sure the do not share kernel is selected.

---------- Post added at 08:00 PM ---------- Previous post was at 07:58 PM ----------

Kernel does not matter when installing ubuntu. It uses its own kernel. In multirom before you install, make sure to choose "do not share" for the kernel.
[Nexus 7 Original Development] FitAmp:
Re: [MOD][12 MAR] MultiROM v9 (updated recovery)

It installs to USB drive fine. And I know :p

Just when the device boots to multirom menu when you choose which rom to boot, the ext3 drive wasn't recognized because the main kernel (mkernel) was already started which doesn't support ext3.

(The main kernel boots before multirom)
[Nexus 7 Original Development] rebel1699:
Re: [MOD][12 MAR] MultiROM v9 (updated recovery)

Ahh, I get what your saying now.
[Nexus 7 Original Development] FitAmp:
Re: [MOD][12 MAR] MultiROM v9 (updated recovery)

Ext 4 drive still wasn't detected :( maybe its the drive I was using
[Nexus 7 Original Development] FitAmp:
Tried latest ubuntu desktop core again (Installed internal) got errors, heres log

Edit: solved, see next post by tassadar
[Nexus 7 Original Development] Tasssadar:
@FitAmp: There seems to be something wrong with your MultiROM installation:

Check if these two files exists, multirom_vX_n7-signed.zip file should install both of them, so just reflash it.

Also, there might be problem with buffer overflow in the recovery, if reflashing the ZIP does not work, try to rename the ubuntu image to something shorter (u.img for example).

As for the USB drive not getting detected, start MultiROM, plug-in the USB drive, go to USB tab, wait for a while (30-60s) and then switch to misc and press "Copy log to /sdcard".

This creates file /sdcard/multirom/error.txt, it contains log - you have to access it either from recovery or from android with root access as /data/media/0/multirom/error.txt. Get me that file, so I can see what is going on in there.
[Nexus 7 Original Development] FitAmp:
Re: [MOD][12 MAR] MultiROM v9 (updated recovery)

I'll try reflashing now and reinstall Ubuntu.

As for USB I'll try when I'm home.

Thank you :)

Edit: those files infact did not exist ... I reflashed multirom then repatched init and it booted just fine :) I don't know why those files were missing, weird :p anyways thanks for the help!

Latest Ubuntu feels smooth
[Nexus 7 Original Development] Tasssadar:
MultiROM v10 and new recovery were released. The main feature is...

New MultiROM installer ROM format

This is a new format, generally for Linux-based ROMs (webOS, plasma, bohdi...). This means (for you, user) that these ROMs can be now installed to USB drive. This new format also checks if there is enough space in the install location and a few more things. If you're a developer and wanna know more, read README in this folder on github: https://github.com/Tasssadar/multirom/tree/nexus7/installer

ADB support

MultiROM now has adb daemon running. This means that when you see the MultiROM UI, you can use adb shell, pull, push and reboot. Android isn't running yet, so you can't use all adb features, /data is mounted at /realdata and /system is not mounted at all. It is useful for me and for (some?) other developers though. It is also disabled by default, because it means root access with no security whatsover, but I suppose that is not a big problem, because recovery does the same thing. Go to recovery, Advanced->MultiROM->Settings to enable it (top right corner).

Misc

Brightness setting, color "themes", battery status.
[Nexus 7 Original Development] rebel1699:
Awesome upgrades, Tasssadar. Im ready to fill my ext hdd up again. Thanks for the new features.
[Nexus 7 Original Development] ikslawlok:
Thank you for the "Inject curr. boot sector" option :

:good::laugh:
[Nexus 7 Original Development] moparman1969:
When I try to download it says authorize download is there a password or have to many people downloaded it
[Nexus 7 Original Development] ikslawlok:
Just authorize download

Envoyé depuis mon Nexus 7 par Tapatalk HD
[Nexus 7 Original Development] thoiloidainhan:
Just request desktop site from browser settings
[Nexus 7 Original Development] rydog66:
i was able to download just now no problems
[Nexus 7 Original Development] amhatter:
So any way to adjust CPU settings in Ubuntu desktop? Thank you in advanced!
[Nexus 7 Original Development] farmerbb:
You should just be able to use the terminal to adjust them like you can in Android. It's the same Linux and mostly the same kernel.
[Nexus 7 Original Development] FitAmp:
Its using the stock kernel with minimal changes. You won't be able to overclock

Nexus 7/Rasbeanjelly/Franco.Kernel
[Nexus 7 Original Development] DorkyDev:
Note 2 Supported?

Does this work on Note 2 variants as well? I have a i317, there's no real steps on how to do it if so, would we (the Note 2 users) also have to flash the custom kernel as well? I'd really love to give this a shot, but so many uncertainties as I see people with a Note 2 in their signature using tapatalk but no real word of success comng from them and if it's on their Note 2 they're using....
[Nexus 7 Original Development] ChemicalSymphony:
With the newest recovery, when the screen automatically turns off from inactivity, it will not come back on no matter what i do.
[Nexus 7 Original Development] FitAmp:
No! Do not flash this on any device besides the Nexus 7 (grouper)

Multirom has support only for Nexus 7.

Nexus 7/Rasbeanjelly/Franco.Kernel
[Nexus 7 Original Development] ayanamirei33:
did you try tapping the screen?? pressing the power and volume buttons won't work... ;)
[Nexus 7 Original Development] ChemicalSymphony:
Nice! Can't believe I didn't try that.

---------- Post added at 01:34 AM ---------- Previous post was at 12:57 AM ----------

My Ubuntu desktop install just took an hour. When I rebooted, it hung at the Google screen. So I held the power button to reset it to get to the bootloader. It took a long time to allow the volume buttons to change the function but they eventually worked. I then booted into recovery. I thought maybe I was running low on storage space so I then deleted the raring-preinstalled-desktop-armhf+nexus7.img.gz file to get some back. After that, I clicked the Inject curr. boot sector button and then rebooted. Everything worked fine after that. I'm not sure what the problem was exactly but one of the two things I did worked.
[Nexus 7 Original Development] amhatter:
I had the same issue, twrp settings-screen off-0. Fixed it for me.

---------- Post added at 09:10 AM ---------- Previous post was at 09:05 AM ----------

Is there a way to edit the kernels code to allow for "automatic" oc? So that the kernel defaults to an above stock clock speed. I don't know if that really makes sense or not, not really sure how to put into words what I'm trying to get at. Lol:)
[Nexus 7 Original Development] jsauder2:
not sure if this is what you're thinking of, but back when I had a droid x wizardofoz made a thing called bootmenu. it loaded prior to recovery and would let you choose between cwm and rzr recoveries, as well as giving you a menu to choose the gov and oc/uv settings prior to boot. it saved those settings so one you had it set up, it loaded by default on every boot until you changed it. there were also some other options included for various fixes and tweaks.

Sent from my Nexus 4
[Nexus 7 Original Development] PVL_93_RU:
Tassadar, could you please explain the new installer format a bit further? I don't seen to entirely get it even after reading the readme.

Do I correctly understand that now Ubuntu Touch ROM can be packed into a .zip archive which then should be renamed to .mrom, and along the image of the ROM, the archive should contain the 4 directories (rom, root.dir, preinstall, postinstall)?
[Nexus 7 Original Development] Tasssadar:
The format is made so that primarily Linux-based ROMs (bohdi, plasma, webOS) can be installed to USB drive. These ROMs create only tar.gz archive with their root, so some kind of installer is needed. Previusly, I was using just normal ZIPs flashable by recovery, but there was no way to install the ROM to USB drive, so I created new format.

There is no reason to use this format for Ubuntu touch, because it can already be installed to USB drive.

The file itself is ZIP archive, with folders and files named certain way so that recovery can take them and install to appropriate place. See for example WebOS installer, just open it with WinRAR or whatever: http://xdaforums.com/showthread.php?p=39937682#post39937682
[Nexus 7 Original Development] Gingerbread23:
Does USB mounting in TWRP not work or I'm just blind?
[Nexus 7 Original Development] Forty.Two:
If you are looking for new things to implement, how about password protection before boot?
[Nexus 7 Original Development] FitAmp:
Is it only me or does others have the ui freezing shortly after using some programs in Ubuntu desktop?

Nexus 7/Rasbeanjelly/Franco.Kernel

---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------

Its mounted at /usb-otg I believe

Nexus 7/Rasbeanjelly/Franco.Kernel
[Nexus 7 Original Development] drewski_1:
It works. Need to dig up the N7 and find the right directory.
[Nexus 7 Original Development] ChemicalSymphony:
Any way to make multirom boot the internal rom after a set time? I sometimes turn off my Nexus and put it in a zippered case. Often, when I take it out later, it has been accidentally turned on and is very hot and the battery is almost dead. I'm worried that I will ruin it eventually and it's making me consider removing the mod. Other than that I love it and I really appreciate the work put into this.
[Nexus 7 Original Development] thereal_bigjake:
advanced/multirom/settings IIRC

Nexus 7 | AOSPA 3.15 | M-Kernel | Action Launcher Pro
[Nexus 7 Original Development] ChemicalSymphony:
I can't thank you enough.
[Nexus 7 Original Development] Gingerbread23:
Sorry but i dont know what you mean.

The console always says "E:Unable to mount '/usb-org'
[Nexus 7 Original Development] ikslawlok:
TWRP is out 2.5.0.0 !
[Nexus 7 Original Development] Tasssadar:
Recovery updated to TWRP 2.5: http://www.mediafire.com/?k156jivtnfs3rgl
[Nexus 7 Original Development] drewski_1:
Sorry, I meant I need to dig out my N7 to tell you the directory, but it looks like someone else gave it /usb-otg from the root

Just verified on the N7 and it mounts and is accessible for me

Forgive my ignorance, what is "the console"

Sorry can't be more help.
[Nexus 7 Original Development] rydog66:
Hey there, AWESOME MOD here!! I have a couple quick ?uestions tho.

1. I only need to use the patched kernel(s) if I wanna use Ubuntu right?

2. do I have to put a stock rom back on my device as the "primary"? I flashed several just asap when I unlocked then rooted it & have settled on something I am very pleased with & have had NO issues with. I do want to use this tool and try others, but keep the smooth 5.0 rom as my primary, if possible. If it is required or very strongly recommended to put a stock one back on as primary, I will. I can still use my nandroid that I made of it, right.

Thanks for sheding some light on this for me. I do have experience with the Boot Manager app. I use it on my EVO 4G and love it. This seems very similar, with some pretty amazing extras, like the whole Ubuntu thing....unreal!!!

Thanks & CHEERS,
[Nexus 7 Original Development] EvanA:
1. You need the patched kernel for any rom multiboot.

2. It doesn't matter what your internal rom is. I have PA as mine right now.

Sent from my AOSPA 3.+ (self compiled) and m-kernel+ a49 Nexus 7
[Nexus 7 Original Development] rydog66:
sweet, thanks a million. I'm right in the middle of gettin this done so I can use it...IMMEDIATELY. I'm helping test a new rom for our N7!! So I'm anxious. Thanks for your help.
[Nexus 7 Original Development] Gingerbread23:
Ok sorry i misunderstood you.

With console i meant the log window, there is a button in the middle next to the back button.
[Nexus 7 Original Development] ikslawlok:
Hello, I have two another suggestions on the modified interface TWRP

After making this :

Install -> (Zip selection) -> Swipe to confirm - > (Processing)

1) Currently, if we do "Inject. curr boot sector", we have :

Is it possible to replace with

2) Currently, if we do "Wipe cache/dalvik", we have :

Is it possible to replace with

Thank you for taking the time to read
[Nexus 7 Original Development] Kiinasu:
fastboot flash recovery TWRP_multirom_n7_20130409.img
sending 'recovery' (8810 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s

get this error. bootloader 4.18. newest adb. installed multirom_v10_n7-signed.zip first. rom is paranoid 3.15 with trinity kernel. anyone know how to fix it?

current recovery TWRP 2.5.0.0
[Nexus 7 Original Development] thereal_bigjake:
Have you tried renaming it to just recovery.img? Flashed fine for me but I always rename it.. Just a thought...

Nexus 7 | AOSPA 3.15 | M-Kernel | Action Launcher Pro
[Nexus 7 Original Development] Kiinasu:
fastboot flash recovery recovery.img

sending 'recovery' (8810 KB)...

FAILED (command write failed (Invalid argument))

finished. total time: 0.002s

yes, still wont work. with the goo.im app i could flash the normal TWRP .img. but fastboot flash won't work. any chance to flash it a other way?
[Nexus 7 Original Development] rydog66:
I was getting that error just last night installing this for the 1st time (not an update or anything) I use the Toolkit for the N7 too, but this fastboot/bootloader is essentially the same process weather you use the toolkit or not. The solution for me, after pulling my hair out, and using some colorful language, was a simple reboot on my computer. Even if it doesn't fix your problem, it definately can't hurt. Good luck!!

CHEERS,
[Nexus 7 Original Development] thereal_bigjake:
You could make a flashable zip, but it might be a better idea to figure out what is going on.

Have you tried redownloading, reboot bootloader, reboot pc, or trying a different usb port?

Nexus 7 | AOSPA 3.15 | M-Kernel | Action Launcher Pro
[Nexus 7 Original Development] ikslawlok:
Sudo fastboot flash recovery TWRP_multirom_n7_20130409.img works

Envoyé depuis mon Nexus 7 par Tapatalk HD
[Nexus 7 Original Development] Bronto9:
Download from the play store flash image gui, it allows you to flash kernels and recoveries IMGs directly from android

EDIT: here it is https://play.google.com/store/apps/details?id=com.joeykrim.flashimagegui

Inviato dal mio Nexus 7 con Tapatalk 2
[Nexus 7 Original Development] Kiinasu:
yeah, was testing, while you added the link. worked thanks.
[Nexus 7 Original Development] instanton:
Ubuntu raring update results in boot failure

Just made a sudo apt-get update && apt-get dist-upgrade and after that rebooting the device fails. The first reboot resulted in a black screen. Then I booted into recovery and chose Inject curr boot sector from there. The next reboot led me to the screen for choosing roms to boot. But choosing eith internal rom or the ubuntu just upgraded results in boot failure:

1. Choosing internal rom resulted in a boot loop and it stops at the same screen for choosing roms;

2. Choosing Ubuntu resulted in some error message saying that the kernel does not support kexec functionality.

I was using the kernel_kexec_41-2 kernel, so I reinstalled that kernel from recovery and did the Inject curr boot sector once again. After that the Ubuntu image boots normally, but the internal rom still does not boot (always looped to the same screen). I read from previous post in this thread that some others also have experienced a similar problem. I would like to know the following:

1. What I should do next to make the internal rom work again without damaging data and/or reflashing the Ubuntu image?

2. How can such a problem be avoided in future upgrades for Ubuntu?

Thanks a lot.
[Nexus 7 Original Development] EvanA:
Try to repatch the ubuntu init.

EDIT: Nevermind, should've read better...

Sent from my AOSPA 3.+ (self compiled) and m-kernel+ a49 Nexus 7
[Nexus 7 Original Development] SANCAH:
Just updated recovery, kernel and MultiRom using Image GUI. I can verify the version of recovery and kernel I have, but how can I check what version of MultiRom I have I installed?
[Nexus 7 Original Development] rebel1699:
When you first boot, tap the misc tab and the version info is on the lower left.
[Nexus 7 Original Development] SANCAH:
Thanks a lot. Everything is how it should be. Great job! Great community!

Sent from my Samsung Galaxy S III
[Nexus 7 Original Development] instanton:
Thanks anyway. I have made every effort to rescue the internal rom but no success. Finally made a backup of data and reflashed the stock rom. Doing this the Ubuntu system is completely gone. This is the second time I was forced to reflash stock rom after upgrading Ubuntu, and I will not reinstall Ubuntu again until a 100% safe resolution is found.
[Nexus 7 Original Development] FitAmp:
Oops wrong thread