yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] pr@tt:
Free space got lost after flashing secondary ROM

Hello All,

I have several ROMs installed via MultiROM (Ubuntu Touch, Firefox OS, CM12.1). But weird thing happened to my Nexus 7 (flo, 16Gb) on the weekend.

I wanted to add a new one Bliss Rom 6.0 by Team Bliss as a secondary ROM. At the first time installation failed, and I expected that free space be the same as before but I noticed it has decreased by ~500Mb. So I've tried one more time, failed and again I've lost 500Mb. I tried to google something on that but no success. So yesterday I spent a lot of time trying to find something that may take this place on my device but nothing unusual was found (checked /data/media/0/multirom and explored almost all internal memory). I decided to make one more try to add this ROM. This time installation was successful but as it was Marshmallow ROM it hasn't booted so I've removed it. Nevertheless I looked at the amount of free space that has left after all this manipulations and again - minus 500Mb :(

So totally I've lost 1.5Gb of internal memory. I haven't tried to re-flash factory images yet. I'd like to figure out what is going on. So I have a couple of questions here :

Did anybody tried to flash this ROM as secondary via MultiROM ?

Did anybody faced the similar behavior ever ?

What can be done to find missing space and get it back ?

Appreciate any response.
[Nexus 7 (2013) Original Android Development] hachiroku:
wow i was struggling with frustration for about an hour. this works perfectly on my flo version. confusing as there were no instructions, but i simply flashed within recovery.
[Nexus 7 (2013) Original Android Development] dragancla:
Guys, I need some help.

So, I installed ElementalX-N7-5.07 kernel.

Then I opened the MultiROM app on my rooted stock 6.0.1 Nexus 7 2013 FLO and installed MultiROM.

When it booted into the MultiROM boot menu I picked Reboot Recovery.

Went to Advanced->MultiROM->Add ROM.

Chose the DirtyUnicorn 5.1.1 ROM and installed the pico gapps.

Booted DirtyUnicorn, all was fine.

Tried to boot back into the Marshmallow internal ROM, it just sent me back to Recovery.

Tried to reinstall supersu and then the kernel again, restarted tablet, chose Internal ROM, booted again back to recovery.

Tried restoring the nandroid backup I did just before I installed the kernel. It says:

Restoring System...

and 10 seconds afterwards:

E:extractTarFork() process ended with ERROR=255

But installing the ROM in MultiROM from backup works fine but it still doesn't boot, still sends me to Recovery.

Also, recovery keeps asking me to install SuperSU because it "does not appear to be rooted" but I keep saying "Do Not Install" every time. Not sure if relevant or not.

Anyone have any idea what I should do to boot into my internal ROM?
[Nexus 7 (2013) Original Android Development] drewski_1:
May be the Multirom from the app, which I don't think he's been updated for MM.

Try the one in the link from the post right above yours.

Sent from my 6.0 OG Shield Tablet
[Nexus 7 (2013) Original Android Development] dragancla:
Fixed it by flashing https://www.androidfilehost.com/?fid=24269982086994463, as you said. Thanks!
[Nexus 7 (2013) Original Android Development] nicche:
Hi guys, I need some help too... I'm feeling close to the solution but I can't understand where I make mistake. (sorry for my bad english)

I've had already installed: Elemental XN7-5.08 kernel, the BETA-SuperSU-v2.67 and multirom recovery on my Nexus 7 2013 FLO.

At first I installed the multirom app by appstore but when I chose the internal rom ( my first rom is MM 6.0.1 sotck, rooted ) it sent me to recovery... I tried many times but the results were the same.

Then I flashed the .zip suggested by drewski_1 and it works, I mean if I choose te internal rom it starts without problems but when i try to flash miui_Nexus7_4.3.14_a387a94c89_4.4 and then i choose this rom by the multirom boot it sent me in to recovey again why?? Miui rom is too old??
[Nexus 7 (2013) Original Android Development] drewski_1:
i'd guess it's too old being a KK / 4.4 based ROM.
[Nexus 7 (2013) Original Android Development] Tasssadar:
MultiROM v33 and updated recovery was just released. [MENTION=2605798]nkk71[/MENTION] and [MENTION=2719389]z31s1g[/MENTION] pretty much made this update possible by their contributions, thanks!

It has some compatibility fixes and updates TWRP to 3.0.0. CM13 now works, as well as system-less su (use BETA 2.67-20160203160253 ( http://bit.ly/m_su ) or newer).

ZIPs made from factory images of 5.1.1 and 6.0.1 can be found on androidfilehost and basketbuild (unmodified stock images, no root, no anything. Forceencrypt and verify is disabled in these).
[Nexus 7 (2013) Original Android Development] nkk71:
Congrats, nice to see you back.

I personally also want to thank [MENTION=1162986]Captain_Throwback[/MENTION] for his continued drive (and driving me mad :p), amongst many other things... if I were to list them they would be too long)

and [MENTION=2719389]z31s1g[/MENTION] for jumping to our help so quickly (not to mention all the great things he's done for official twrp as well)

Many thanks to both of you, for all help and support.

nkk71
[Nexus 7 (2013) Original Android Development] followmsi:
Works like a charm .. Thanks a lot !
[Nexus 7 (2013) Original Android Development] nkk71:
Glad it is :good::good:

took quite some work, testing, and such

hope we didnt miss anything, but the new changes will allow for easier merges rebasing, in the future
[Nexus 7 (2013) Original Android Development] osm0sis:
Hmm, not working here trying to install or update Ubuntu Touch..

Unable to find partition for path '/data'

Edit: Not working in recovery to add another Android ROM either, not even after I deleted /data/media/0/multirom and started over with a fresh MR install flash.
[Nexus 7 (2013) Original Android Development] Ænimal:
Adding secondaries without issues here :good:
[Nexus 7 (2013) Original Android Development] nkk71:
Can you pull the /tmp/recovery.log after the failed flash, please

Also my devices don't have Ubuntu Touch, so there was/is no way for me to test those
[Nexus 7 (2013) Original Android Development] drewski_1:
i am able to add a secondary Android ROM (Pure Nexus 20160203 build) fine.

have not tried Ubuntu Touch
[Nexus 7 (2013) Original Android Development] osm0sis:
Weird. I wonder what the hell is going on.. :confused:

I just booted a fresh download of TWRP_multirom_flo_20160207.img, sideloaded multirom-20160207-v33-flo.zip and attempted to add back my Firefox OS secondary ROM (which adds just like Android). Still getting that /data error that breaks Ubuntu Touch OTAs but the secondary ROM otherwise appears to add okay. :cyclops:

http://pastebin.com/VgGYYUeU

Edit: [MENTION=2605798]nkk71[/MENTION] Here's a failed UbuntuTouch install:

http://pastebin.com/HJgemj96

The "Unable to find partition for path '/data'" error occurs even with the old multirom-20151113-v32-UNOFFICIAL-flo.zip where it did previously work 100% with it so it must be some issue with the MultiROM TWRP 3.0.0-0 build.
[Nexus 7 (2013) Original Android Development] nkk71:
Unfortunately, I know very little (make that an overstatement.... I know absolutely nothing about Ubuntu Touch installs, or Firefox OS); from the looks of it, the second pastebin is an OTA/ORS script, which [possibly / probably] fails due to:

line 1003: sh: system-image-upgrader: not found

the first pastebin, looks like a normal install , but a few things do seem weird, about "resource busy"... something I encountered while debugging systemless SuperSU,

but to be honest... not sure how that affects the installs, or if / what I may have broken along the way

unfortunately, there is no way atm for me to duplicate the problem (since I have neither access to these devices, nor those OSs), but i'll look into it.

sorry for the trouble :angel:
[Nexus 7 (2013) Original Android Development] osm0sis:
Yeah, the UbuntuTouch installs are initiated by the MultiROM app, so it may be ORS.

No worries! I've just gone back to running normal TWRP for now (since I was only really using MultiROM for the UbuntuTouch support while otherwise running stock + custom kernel). Maybe [MENTION=3418703]Tasssadar[/MENTION] could also take a look since it does seem to be an issue with the updated recovery build rather than the MultiROM zip; it all still works perfectly with TWRP MultiROM 2.8.7. Let me know if/when you guys want me to test a new recovery build. :)
[Nexus 7 (2013) Original Android Development] Voklav:
+1

Same here.
[Nexus 7 (2013) Original Android Development] nkk71:
did you actually the read the post just above yours?
[Nexus 7 (2013) Original Android Development] Voklav:
O hahah it was not loading.... Sorry hahaha - I didn't see any of this post :D

Personal note : back to opera.

Edit:

LOL that fix was a quick ! :)

Everiting work fine :)
[Nexus 7 (2013) Original Android Development] samsungf6500:
hello,

several times I tried to activate encryption on secondary aosp rom without success.

primary rom was always the same as secondary aosp rom during test.

i tried different stock android roms 4.4.4 , 5.1.1 and for the moment 6.0.1.

The disk is ext4 format.

i am using the lte version of the nexus 7

maybe some of you have an idea what i need to take care about

thank you
[Nexus 7 (2013) Original Android Development] osm0sis:
Nice, OP updated with a 0210 recovery build for those who didn't notice. Thanks [MENTION=2605798]nkk71[/MENTION] and [MENTION=3418703]Tasssadar[/MENTION]. :)

I'm at work but I'll do some testing in a bit to make sure Ubuntu and the /data error are gone. :good:

Edit: Yup! All good now on both fronts! Great work gentlemen! Fully functional again. :D
[Nexus 7 (2013) Original Android Development] osm0sis:
[MENTION=2605798]nkk71[/MENTION], Sailfish OS icon for the repo?

https://openrepos.net/sites/default/files/styles/thumbnail/public/packages/721/icon-sailfish.png
[Nexus 7 (2013) Original Android Development] bmakk2055:
[MENTION=3418703]Tasssadar[/MENTION] could you fix your flashable stock img flo? I keep getting a script update error when flashing as primary rom.
[Nexus 7 (2013) Original Android Development] brownstyle:
i got error failed to mount/cache while setting up multirom..my device is asus ze550kl but i edited the build.prop similar to nexus.help pls
[Nexus 7 (2013) Original Android Development] drewski_1:
I don't think you can just modify build.prop and use the N7 multirom on another device
[Nexus 7 (2013) Original Android Development] samsungf6500:
Hello,

I understand that it is difficult to answer my previous question.

Maybe this one is easier,

Is someone of you using the encryption ?

if yes what is your configuration ?

Which primary image do you use ?

Which kernel do you use on the primary rom ?

Which secondary image do you use ?

Which kernel do you use on the secondary rom ?

Thank you for your help.
[Nexus 7 (2013) Original Android Development] tiidigital:
encrypted device...

i've installed multirom.. and i did a device encryption using the internal rom, cm13, with a 4x4 pattern...

when the encryption finished and the device rebooted it got stuck in boot loop... i rebooted and it got stuck again in bootloop without asking me for the decryption pattern at boot... next i booted into multirom recovery.. and it asked me for the unlock pattern... i put the correct pattern (i'm 100% sure it is the correct pattern) and it says "wrong pattern.. please try again".. furthermore i gone snooping around inda file manager and also terminal... not doing anything concrete... so i decided to reflash system with a backup that i've done b4... flashed a backup of a aicp rom... wich is cm13 based.. and when i rebooted it appears now onscreen at boot "encrypted device... please enter your password" and it shows the pattern dots though 3x3 instead of 4x4...

/data was formated as f2fs b4 encryption

how can i make multiboot recognize the correct pattern

how can i change the boot screen to show a 4x4 pattern instead of 3x3

so..

i have recovery working (except the multiboot button)

i have adb & fastboot access

can i get some advise from any expert on the subject???

thank you very much in advance
[Nexus 7 (2013) Original Android Development] osm0sis:
[MENTION=3418703]Tasssadar[/MENTION], the devel-proposed channel for UbuntuTouch flo disappeared in the in the last MultiROM app update. Can you add it back?

PSA: r455 is broken by the way, doesn't get past the Google logo. Trying to do a fresh install is how I noticed it was missing in the app. ;)

devel r8 works if people want to try the Ubuntu 16.x branch with less chance for breakage, and rc-proposed is good for the latest 15.x fixes.
[Nexus 7 (2013) Original Android Development] samteeee:
Greetings;

I installed ubuntu touch through the "multirom manager" and all went smooth but It

won't pass Google screen. Any suggestion?

Thank you.
[Nexus 7 (2013) Original Android Development] osm0sis:
Read the post before yours?
[Nexus 7 (2013) Original Android Development] samteeee:
Thanks for replying.

I tried the others as well to no avail!

It must be my set up, right?
[Nexus 7 (2013) Original Android Development] Oicebot:
Sorry to be a pain here. I've got the same issue(stuck at google logo) when install Ubuntu Touch in my Nexus7(2013) stock 6.0.1 with multirom.

Yes, I've read the previous posts between page 126 to 129, it seems that this issue was come with the latest TWRP multirom v3.0.0, right?

So I wonder where can I download the latest working version of TWRP multirom img( I tried the latest build v20160210, no luck), thank you for your time.

EDIT: Strange... I found the old TWRP_multirom_flo_20150212.img (v2.8.5), so I use fastboot to flash that recovery into my device. But still I got stuck at google logo after I re-install the UbuntuTouch (devel-proposed,v467) ...
[Nexus 7 (2013) Original Android Development] osm0sis:
As I said in my post, use rc-proposed/ubuntu (currently r397) or devel/ubuntu (currently r8). It all works fine for me with the latest MR TWRP3.
[Nexus 7 (2013) Original Android Development] knopancakes:
Hello,

I seem to also be having the same issue as Oicebot. I have tried both devel r8 and r7, and some older utopic builds, and in all cases the tablet simply reboots after sitting at the Google screen for a moment. I'm on the 2013 Nexus 7 (LTE/deb) stock 6.0.1 with multirom. I have been using the images for |deb| from Tassadar's server.

I've also tried installing Ubuntu Touch from several of the channels on Tassadar's sever by using the ubuntu-device-flash utility, and each time Ubuntu starts up, the Ubuntu logo displays for a few seconds before it changes to a picture of a chip with an "X" through it and a message directing to connect to a PC for recovery.

From this I've gathered that there may be something wrong with the Ubuntu Touch builds for my target platform, but I find it strange that using the same images through Multiboot does not even yield a loading screen for Ubuntu before the device resets.

Any insight would be greatly appreciated.
[Nexus 7 (2013) Original Android Development] osm0sis:
Might be something up with deb support then, since devel r8 and rc-proposed r397 both install and boot fine from the MultiROM app for me on my flo.
[Nexus 7 (2013) Original Android Development] knopancakes:
En Taro [MENTION=3418703]Tasssadar[/MENTION], I will send you cookies if you fix this or suggest a viable workaround.
[Nexus 7 (2013) Original Android Development] Pawel01:
Strange. I try to install devel r8 as secondary Rom, and it also stucks at the Google Logo. Cm13 as primary and stock rooted 5.0 as secondary allready there, with ElementalX. Latest Multirom- and MR-TWRP-Version.
[Nexus 7 (2013) Original Android Development] erikieperikie:
I'm getting the infamous ‘Unfortunately, Setup Wizard has stopped.’ problem. I've read about it in numerous threads all over the web, but I can't fix it using the proposed solutions, e.g. fixing the permissions of the Setup Wizard app: they are already granted. Ungranting and regranting them doesn't work either.

I'm trying to install CM13 as a secondary ROM with Multirom. I've downloaded the latest stable release and the opengapps micro package. I go into TWRP-MR recovery -> MR -> Add ROM -> flash CM13 zip -> flash gapps -> reboot system. I've tried all kinds of dalvik/cache/data wiping of the ROM in between and after the gapps installation. Nothing seems to work.
[Nexus 7 (2013) Original Android Development] klaust58:
I read, the actual opengapps packages are broken...

Gesendet von meinem HTC One_M8 mit Tapatalk
[Nexus 7 (2013) Original Android Development] knopancakes:
Are you on the LTE model? It seems something is wrong with the images being held on Tassadar's server that supports the packages for deb. I got Ubuntu Touch working on mine just now by switching to the images for flo, the wifi-only model. I was able to do this by going into the MultiRom Manager options menu and tapping the version number until it gave me developer options, then changing the device name from deb to flo. There is also an option to change the server address.

It seems someone else has a more up to date server here - [system-image dot ubports dot com]. Sorry about syntax, I'm a newbie so it doesn't let me post link. MultiRom doesn't seem to support adding ROM archives manually, and this alternative server doesn't have a manifest.json like Tassadar's so this might be a dead end.

I notice a major difference in the amount of time it took to install the flo ROM vs the deb ROM, in that flo took much longer. Something is definitely amiss somewhere.
[Nexus 7 (2013) Original Android Development] erikieperikie:
That could be the case, of course. I've found the solution here: use the CM13 GApps from http://www.teamandroid.com/gapps/.
[Nexus 7 (2013) Original Android Development] muhammad_fatah:
I installed Ubuntu touch on my deb but the device is just hanging around the Google logo (cause it's not actually installing Ubuntu touch) , I saw some people facing the same problem. Here's my recovery log, hope anybody can help....

Starting image upgrader: Thu Mar 31 11:47:49 CDT 2016

Loading keyring: archive-master-tasemnice.tar.xz

8192+0 records in

8192+0 records out

33554432 bytes (32.0MB) copied, 0.247479 seconds, 129.3MB/s

Setting up swapspace version 1, size = 33550336 bytes

swapon: /cache/recovery/SWAP.img: Unknown error -38

Temporary swap setup failed! Does the kernel support swap?

Processing the command file

Formating: data

Formating: system

0+0 records in

0+0 records out

0 bytes (0B) copied, 0.000245 seconds, 0B/s

Filesystem label=

OS type: Linux

Block size=4096 (log=2)

Fragment size=4096 (log=2)

128000 inodes, 512000 blocks

25600 blocks (5) reserved for the super user

First data block=0

Maximum filesystem blocks=4194304

16 block groups

32768 blocks per group, 32768 fragments per group

8000 inodes per group

Superblock backups stored on blocks:

32768, 98304, 163840, 229376, 294912

Loading keyring: image-master.tar.xz

Loading keyring: image-signing.tar.xz

__bionic_open_tzdata: couldn't find any tzdata when looking for CST6CDT,M3.2.0,M11.1.0!

__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!

Keyring expired: /cache/recovery/image-signing.tar.xz

system-image-upgrader failed

I:Set page: 'action_complete'

I:operation_end - status=1
[Nexus 7 (2013) Original Android Development] osm0sis:
I seem to recall [MENTION=2719389]z31s1g[/MENTION] saying he finished up work on the new TWRP3 dark theme for MultiROM. Hopefully it gets merged in for MultiROM TWRP 3.0.1. :fingers-crossed:
[Nexus 7 (2013) Original Android Development] roofrider:
I'm waiting for it tooooooooo...but where is tassadar!?
[Nexus 7 (2013) Original Android Development] pr@tt:
Yesss!!! Finally I've managed to fix this!

I tried Resize option of TWRP recovery for /data partition and it gets me back my 1.5 GB. Woohoo!

I hope somebody find this useful. See more details about this option https://twrp.me/site/update/2015/06/22/twrp-2.8.7.0-released.html
[Nexus 7 (2013) Original Android Development] osm0sis:
Maybe [MENTION=2605798]nkk71[/MENTION] can make sure everything's up to date again so [MENTION=3418703]Tasssadar[/MENTION] can just pull the trigger on an official release? Or maybe even hook us up with an unofficial build if Tas is away for a bit again. :)

I haven't looked but I presume [MENTION=2719389]z31s1g[/MENTION]'s theme update would be pull requested or something? :good:
[Nexus 7 (2013) Original Android Development] nkk71:
I've been busy rewriting my no-kexec-workaround, so haven't updated 3.0.2, but [MENTION=1162986]Captain_Throwback[/MENTION] has here

This not only brings it up to date with TWRP 3.0.2, and the new stock theme by [MENTION=2719389]z31s1g[/MENTION], but also includes many multirom related fixes (post February 10 build)

New theme screenshots:

Splash

Main Menu (notice the MultiROM button is in the top right, to access MultiROM functions)

MultiROM Main

MultiROM Storage Selector

MultiROM Settings

etc ;)
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
Sweet thanks ? Works for the N5, will have to try the N7 now
[Nexus 7 (2013) Original Android Development] Sparviero:
Hi everyone, if my primary rom is stock, how can I install the monthly ota update?

I can't find zips flashable with twrp.

Thank you!

---------- Post added at 09:47 AM ---------- Previous post was at 09:45 AM ----------

Hi everyone, if my primary rom is stock, how can I install the monthly ota update?

I can't find zips flashable with twrp.

Thank you!
[Nexus 7 (2013) Original Android Development] drewski_1:
Bad Boyz is a flashable, rooted, stock. It's been getting updated with each monthly patch

http://xdaforums.com/nexus-7-2013/development/rom-bad-boyz-nexus-7-stock-rooted-t3219148
[Nexus 7 (2013) Original Android Development] followmsi:
hi

I have made an Update.zip for secondary ROM myself .. based on latest stock rom boot.img and system.img only.

Used the following code ..

ui_print("boot.img");
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
ifelse(is_mounted("/system"), unmount("/system"));
format("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "0", "/system");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
ui_print("system.img");
package_extract_file("system.img", "/dev/block/platform/msm_sdcc.1/by-name/system");
unmount("/system");
ui_print("Installation complete!");
ui_print("OK Done - Please reboot!");

The update.zip script above created the new secondary rom for multirom - no problems so far.

I did also simg2img system.stock.img system.new.img. ;)

I can loop mount the system.new.img without problems.

But when I boot into this new secondary ROM it fails .. will post the log file later on.

I have checked the update.zip rom from multirom team and from bad boyz.

Both are using extracted system.img or do extract before.

And set permissions .. etc. via update.zip.

Not like me pushing the system.img directly.

package_extract_file("system.img", "/dev/block/platform/msm_sdcc.1/by-name/system");

For the boot.img it seems to be no problem .. but for system.img ?

Why does it not work like this for system.img ?

EDIT: The multirom_log.txt on sdcard has 0 bytes.

Thanks for some help !