yashsingh1/xdaforums huggingface dataset:
[HTC One X] reubenvarghese1:
[MENTION=618483]Thunder07[/MENTION] I don't think it is something to do with lollipop cause I just installed slimlp successfully and I am loving it. It is the cm 12 ROM which does not boot .with slimlp everything is perfect as far as multi ROM is concerned:)

---------- Post added at 01:25 AM ---------- Previous post was at 01:21 AM ----------

And yeah it also boots without the need of any charger or powerbank .keep up the great work ! Simply love it:)
[HTC One X] Thunder07:
ya it's not directly related to LP, but it's probably some configuration CM12 kernel uses, that’s causing this,

eitherway, its not effecting ZeusKL v10, which is based on CM12.
[HTC One X] Thunder07:
Update V31

-- Fix sdcard mounting issue on secondary ROM (New Layout Only)

-If you copied anything to Internal sdcard from a secondary rom before this update, you can retrieve it from /sdcard/multirom/roms/ROM_NAME/data/media/0/ from internal/secondary rom or even the recovery

http://d-h.st/wOg6

[MENTION=1207171]modest.young[/MENTION], [MENTION=2386852]cappuccina[/MENTION]

Thanks guys for spotting this,

the secondary rom created a new internal sdcard(just a folder) which was working an empty,

and since when i tested this, my sdcard was empty I was fooled :p
[HTC One X] modest.young:
[MENTION=618483]Thunder07[/MENTION] I have to say I have bad news....booting to internal ROM (XenonHD, AICP) ends with error: kexec kernel... ...operation not permitted...

I did installation on both internal ROMs twice but unsuccessful :crying:
[HTC One X] Thunder07:
ummmm... booting internal rom should not be effected by MR...

where are you getting this error from? Zeus or MR,

if Zeus are you getting rebooted into recovery, if so when that happens post "adb shell cat /proc/last_kmsg | grep zinit" into pastebin and link it,

if its MR (still cant see how its a problem, not that ive never been wrong), if that error keeps you in MR post "adb shell cat /proc/kmsg | grep -e trampoline -e multirom" and post that to pastebin,

if the phone reboots, cancel MR boot sequence, wait for adb to start and do "adb shell cat /proc/last_kmsg | grep -e trampoline -e multirom"

P.S. you can add ">logfilename.txt" to the end of each command to save the results into a file if you wish.

Edit: I probably wont be able to keep my eyes open enough to see your response,

so if you should try flashing MR again, if that doesnt work flash the older one just so you can get your phone booting again,

and if you dont have the older veriosn, you'd find it here, http://d-h.st/users/Thunder07/?fld_id=36592#files
[HTC One X] teemo:
Something's weird with latest MR 0222. Say version 2.7.? and look like it's for old layout?

Maybe it's just too late now...
[HTC One X] cappuccina:
I was just about to say the same. Multirom TWRP is Version 2.7.1. Previous Multirom TWRP was Version 2.8.4

And it fails to install Lollipop rom (but also Slimkat BIG) as secondary rom.

It recommends to update recovery for lollipop :P
[HTC One X] bilbonotry:
Same here. Could not install any lollipop ROM and recovery looks weird.
[HTC One X] Thunder07:
I have to get ready for college but this should be new recovery http://d-h.st/GY1l

I've setup a new build environment over the weekend and probably cloned the wrong branch.

anyway, as i said, I'm leaving to college now, so i didnt test this, but I'm running just 2 commits older recovery but its 2.8.5,

so everything should be the same.

this has been compressed so it can be flashed to the main recovery or just pushed to /data/media/0/multirom/roms/TWRP/boot.img
[HTC One X] bilbonotry:
[MENTION=618483]Thunder07[/MENTION] : it is not really urgent, but maybe you made a mistake ? Or I did not understand. The link points to a recovery.img which has a size of 7 Mbytes and we are supposed to replace a boot.img that has a size of 11 Mbytes.
[HTC One X] Thunder07:
I'm just that good :)

I switched compression type from gzip to lzma.

Edit: [MENTION=1207171]modest.young[/MENTION]

so can you confirm that return to the earlier version of MR solved the issue?
[HTC One X] bilbonotry:
Manual push did not work. I get my internal rom recovery when booting to TWRP
[HTC One X] modest.young:
I'll try to test it later today.

I tried ZeusKL v10 with MR v30 on [MENTION=698346]teemo[/MENTION]'s 2851.BiG twrp. And the result is that after the first reboot it directly boots to base ROM, no MR interface/ROMs selection dialog appears.

So no luck.

---------- Post added at 09:26 AM ---------- Previous post was at 09:23 AM ----------

[/COLOR]

+1 for me, updated recovery (with lzma compression) doesn't boot
[HTC One X] Thunder07:
MR V30 is for the old layout only, you need to flash the older v31 release http://d-h.st/dXjg

as for the recovery, the weekend is coming, so ill be able to test it myself :/
[HTC One X] bilbonotry:
Pasted recovery.img into multirom.zip in multirom/roms/TWRP/boot.img, flashed, got twrp 2.7.1 but still no joy to install secondary roms

[MENTION=618483]Thunder07[/MENTION] : no problem, there is no hurry, do not want to stress you
[HTC One X] bilbonotry:
Here is latest multi rom with boot.img from the one before since nobody uploaded it. Created secondary ROMs but had weird boot loops with secondary ROMs (one boot OK, second boot loop, wipe data, boot OK, then boot loop)

http://www.mediafire.com/download/jk15g8kzanwi1ec/multirom-201502mix-v31-UNOFFICIAL-endeavoru.zip
[HTC One X] bilbonotry:
I did not. Before there was an option to not share kernel between ROMs, it is not there anymore, so what is the current behaviour ?

Edit : ok, found the culprit. It was flashing Titanium Backup zip that messed up my ROMs.

Edit2 : nope, in fact it seems it was restoring apps with TiB that messed up apps uid and permissions in /data/data
[HTC One X] reubenvarghese1:
Can i install sense and lollipop now(new layout)

Can i install sense and lollipop.Before i had read that both cannot be installed together but that reply was posted before the sense rom for the new layout was released,so now that almost all the new roms are in new layout ,the question is being asked again
[HTC One X] cappuccina:
Yes you can. It's working good.

If you are on new layout and both roms use that layout.

There are 3 Sense roms AFAIK. SkyDragon Reborn, ARHD and ViperX. Just look in the New storage layout Thread.

---------- Post added at 01:03 PM ---------- Previous post was at 12:48 PM ----------

HI,

I've also experienced this behaviour. When using secondary roms, after a reboot all of a sudden bootloop.

Had to wipe data to make it work again. That is very unfortunate.

You say its titanium backup. Could be, is it normal that I had two different folders for TiB files once?

what did you do to prevent it. Not using TiB anymore? or is there an other way?

Thanks.
[HTC One X] reubenvarghese1:
Thanks a ton!!!Now i can peacefully shift to new layout:)
[HTC One X] Tanuj97:
why dont some of you guys make a video how to use multirom and how to flash various roms using it ..pls...i am new layout and want a sense rom without removing my lollipop rom .....help would be appreciated
[HTC One X] bilbonotry:
I could not. I am unable to use secondary ROMs, as soon as I install an apk next boot loops. I have seen permission errors in the logs but do not know what to do about them. Do you manage to have usable secondary ROMs?
[HTC One X] teemo:
I am running with 3 external Roms. Never have bootloops.

But sometimes have problems with restoring. I use 3cToolBox, but it might be the same issue as with tb.

Don't know if this is MultiRom or LP related?

When restoring, I usually install problem apps from market and restore only data. Keyboard app is always a problem app, sometimes Viber, don't remember what else is.

Edit: Where is your MultiRom folder? It must be in

/data/media/0/multirom

it will not work from

/data/media/multirom

TWRP sometimes get confused about this. Don't install MultiRom without having installed a ROM first.
[HTC One X] bilbonotry:
Thanks teemo, multirom is in the correct path, but I may have installed it without any ROM. I did not think about installing it again. If it is running OK for others, I will try it.

I have boot loops even when installing an apk manually, so it is not a restore problem. What version of multirom do you use?
[HTC One X] teemo:
Check the previous page, post #207 and #208

I don't know if the correct combination is uploaded somewhere. You can download mine here, remember it's for NEW Layout. It's on my dropbox, so it will disappear next time I clean the box :p
[HTC One X] cappuccina:
Well with sense roms I can't remember having bootloop. But lp roms give bootloops for me also.

Sometimes when I switch to internal and after that want to boot a secondary rom it loops .

Multirom is in the correct path also.

I also had trouble after installing apk's. But not always, that's the thing.

I thought it might be Xposed. Stopped using it for now but last time although nothing new installed I wanted to boot aicp it also gave me bootloop. So not sure.

For now only using lp as main and sense as secondary rom.
[HTC One X] teemo:
That might explain. I have only used slim and Sense as secondary. Could be something with the CM base, which I don't use :)

Guess it's time for me to try AICP or CM again.... Need some change now until Slim is fully back :laugh:
[HTC One X] cappuccina:
Not sure but I think I had slim rom also bootlooping...

Its quite annoying. I have to use titanium backup everytime before I switch.

I like keeping all my stuff hhh

The thing is if it loops the only solution is to wipe data as [MENTION=1160716]bilbonotry[/MENTION] said. Flashing rom again with only erasing cache and dalvik does not work.
[HTC One X] reubenvarghese1:
MultiRom still doesnt work with cm 12 based roms?

[MENTION=618483]Thunder07[/MENTION] -multiboot still does not work with cm12 roms as i flashed the aicp lp rom(cm based) today and done all the required steps (including boot.img stuff) but it boots back into multirom screen when i try to reboot the device and gives error (kexec support needed thing) .This is what used to happen in the faux version of zeus too.It works with the other roms which are below lp:confused:

Thanks
[HTC One X] teemo:
I just downloaded AICP 9 (New Layout). Rebooted to MultiRom. Installed AICP from MultiRom. Rebooted and chose AICP in boot selector. AICP booted without problems. I installed 3C ToolBox via file manager. Restored data via 3C ToolBox and all is good.

Rebooting.....

Edit:

... and now back in AICP - still no issues. Kudos to [MENTION=460472]eyosen[/MENTION] and [MENTION=618483]Thunder07[/MENTION]
[HTC One X] Thunder07:
sense roms always have messy update-scripts which could cause a failed secondary rom install, which sense rom have you tried, ill have a look at the script.

when was the last time you've ran "fastboot erase cache", you should do that and see if it helps... if not the solution might be more complicated.

this happens when when MR fails to find "second magic"(just paramators to tell MR to boot secondary rom), that would mostly happen if you lost last_kmsg due to power shortage to the ram which is unlikely or the more likely reason is new kernel fails to mount the new ramdisk, so it uses old ramdisk and new kernel which doesnt support kexec... this should have been fixed with the lastest Zeus-KL image... but there is a work around for that, after flashing a ROM extract boot.img from another working LP rom go to TWRP_MR->Multirom->list ROM-> {choose rom} -> remove boot.img -> add boot.img... this should allow that rom to boot, but you'd also need to get the modules for wifi/signal/bluetooth and every other driver to work.
[HTC One X] eyosen:
[MENTION=698346]teemo[/MENTION], finally got you into some rom other than slim :D
[HTC One X] cappuccina:
Yes Aicp runs great and smooth. Just had issues when installed as secondary.

Running it as main rom without problems.

Actually it's not sense roms that make problems or the installation that's failing.

It's just that when lollipop roms are installed as secondary, sometimes after installing an app or maybe changing something after a reboot there is a bootloop. Or all of a sudden when switching from main to secondary again.

And reflashing the rom / wiping system and caches doesn't help. Data has to be wiped.

So maybe something about the data partition.?
[HTC One X] reubenvarghese1:
[MENTION=618483]Thunder07[/MENTION] - I always wipe cache with fastboot and I use do the boot IMG thing with every secondary ROM.Moreover I forgot to mention that I was using sense as primary and aicp as secondary. Aicp works well as primary but that was the case even before :)

EDIT:and how to fix ram power shortage stuff?I don't know what it means but my battery level was low while flashing the secondary ROM(if this helps in any way:silly:)
[HTC One X] osama-selo:
I had this problem when I switched to the New Layout using ARHD... I spent a whole day trying to fix it, and I found out that the problem was with the permissions, so I wiped everything again and BEFORE copying anything to the phone I entered the following command into the Terminal of TWRP:

chown -R media_rw:media_rw /data/media/0/

And re-installed everything again... and the problem is GONE.
[HTC One X] bilbonotry:
Thanks, but I happened to be the one who uploaded a patched version of multiromv31. Nevertheless I tried your version, and could not install ARHD Big, whereas I could with mine. So reinstalled mine, installed ARHD Big which works good (but Sense5 toolbox does not change interface). I can confirm that Sense (or at least ARHD, could not boot Viper -> error /data is busy) as secondary rom does not boot loop when installing an app, whereas I reproduced boot loops on AICP 9 as secondary rom by installing manually 3C toolbox.
[HTC One X] teemo:
I'm afraid cappuccina is right. Did you try to boot to primary and then back to secondary LolliPop ?

[MENTION=2386852]cappuccina[/MENTION], I don't have to do anything other than boot primary, to kill my secondary AICP.

1. Install AICP9 -> secondary

2. Boot AICP9 and let it settle (only enable root and debugging)

3. Reboot to AICP9 - everything is still fine

4. Reboot to Internal

5. Reboot to AICP9 => bootloop

These dirs contexts (and their /data/app-lib links) gets relabeled to "media_rw_data_file" after running internal ROM:

u:object_r:bluetooth_data_file:s0 com.android.bluetooth
u:object_r:system_app_data_file:s0 com.android.development
u:object_r:system_app_data_file:s0 com.android.inputdevices
u:object_r:system_app_data_file:s0 com.android.keychain
u:object_r:system_app_data_file:s0 com.android.location.fused
u:object_r:radio_data_file:s0 com.android.mms.service
u:object_r:nfc_data_file:s0 com.android.nfc
u:object_r:radio_data_file:s0 com.android.phone
u:object_r:system_app_data_file:s0 com.android.providers.settings
u:object_r:radio_data_file:s0 com.android.providers.telephony
u:object_r:system_app_data_file:s0 com.android.server.telecom
u:object_r:system_app_data_file:s0 com.android.settings
u:object_r:radio_data_file:s0 com.android.stk

[MENTION=618483]Thunder07[/MENTION], is there a description somewhere, telling what goes on behind the scene, or is it only in Tassadars code ?
[HTC One X] Thunder07:
i can confirm the bootloops as well...

I don't have the time to confirm whats causing it, but i can only assume its LP rom itself...

there isnt much documation of the code, but it isnt that hard to follow...

MR boots, after you select a rom, it kexec the kernel, that kernel would contain trampoline which checks for 2nd magic(just a string in kmsg_last).. to verifys booting a 2nd rom,

if it find it, it will mount the correct img/folder to /system,/data,/sdcard and then everything is left to android init,

if it doesnt find 2nd magic, it will boot MR <--- this is how MR is also started on ZeusKL.

now, if you select the Internal ROM, MR would just shutdown and call android init and everything boots normally....

this wouldn't have been practical since my kernel was the only kernel supporting kexec, and we cant update kernel through recovery, (thus inject image option in TWRP_MR wont work).... long story short, i replaced android init with my own init (zinit), which basically just kexec a new kernel while avoiding MR (since that image didn't have trampoline), thus it booted normally after kexec.

none of this should effect ownership of any files, let allow specifically a 2ndary rom files.

try this...

adb shell

su

cat *.rc | grep media

then check those lines to see if you have anything changing ownership.
[HTC One X] reubenvarghese1:
Error booting into internal rom

[MENTION=1207171]modest.young[/MENTION] , [MENTION=698346]teemo[/MENTION] -How did you fix this issue?I tried installing the older version of multiboot and i also tried what u did(modify twrp booot.img in newer version of mr-31) but still the same error comes.MR boots into secondary rom without a problem but only for internal rom this issue comes up.

PLS NOTE-I did not wipe everything and start from scratch.I first went to fastboot and flashed zeus and then went to BIG twrp2.5.3 and flashed the multi rom zip and tried booting into internal :confused:
[HTC One X] cappuccina:
When installing your internal/main rom, did you flash it via the aroma-kl-flasher? Kexec kernel? aromafm_endeavoru-KL-Beta4.5.zip

It's not only flashing zeus kernel and that's it.

You have to flash the rom via aroma KL flasher.

Are you using the New Layout?

You would have had to wipe everything for that anyway.

I think you are mixing old and new layout, cause in the other thread you talk about old layout.
[HTC One X] bilbonotry:
[MENTION=618483]Thunder07[/MENTION] : Here is the result of cat*.rc | grep media for CM12.

I do not see anything relevant.

root@endeavoru:/ # cat *.rc | grep media
cat *.rc | grep media
mkdir /mnt/media_rw/usbdisk 0700 media_rw media_rw
mkdir /data/media 0770 media_rw media_rw
chown media media /sys/htc/media_boost_freq
chown media media /sys/devices/platform/tegra_uart.2/a2dp_tuning
group media bluetooth
# virtual sdcard daemon running as media_rw (1023)
service sdcard /system/bin/sdcard -u 1023 -g 1023 -t 4 -l /data/media /mnt/shell/emulated
service fuse_usbdisk /system/bin/sdcard -u 1023 -g 1023 -w 1023 -t 4 -d /mnt/media_rw/usbdisk /storage/usbdisk
mkdir /mnt/media_rw 0700 media_rw media_rw
mkdir /data/misc/media 0700 media media
mkdir /data/mediadrm 0770 mediadrm mediadrm
onrestart restart media
service media /system/bin/mediaserver
user media
group audio camera inet net_bt net_bt_admin net_bw_acct drmrpc mediadrm qcom_diag
# HAL that runs inside the mediaserver process. The process runs as uid
# media, gid audio and is therefore not allowed to create files in /data.
mkdir /data/cam_calib 0770 media system
chown media system /sys/power/suspend/mode
onrestart restart media
/dev/tegra_avp 0660 media media
/dev/tegra_rpc 0660 media media
/dev/tegra_avpchannel 0660 media media
/dev/tegra_audio_avpchannel 0660 media media
/dev/tegra_sema 0660 media media
/dev/tegra_mediaserver 0660 media media
/dev/ar0832* 0660 media camera
/dev/tps61050-1 0660 media camera
/dev/ov9726 0660 media camera
/dev/tegra_camera 0660 media camera
/dev/camera* 0660 media camera
/dev/focuser* 0660 media camera
/dev/torch* 0660 media camera
/dev/s5k3h2y 0660 media camera
/dev/ov8838 0660 media camera
/dev/s5k6a1gx03 0660 media camera
/dev/aat1271 0600 media camera
/dev/ad5823 0660 media camera
/dev/rawchip0 0660 media camera
/dev/spi_rawchip 0660 media camera
/dev/nvhost-isp 0660 media media
/dev/nvhost-mpe 0660 media media
/dev/nvhost-vi 0660 media media
/dev/video0 0660 media camera
/dev/video1 0660 media camera
/dev/block/mmcblk0p2 0640 media system
[HTC One X] reubenvarghese1:
Solved the problem.I had forgotten to use aroma kl flasher :p

THANKS:good:
[HTC One X] teemo:
Thanks

I added these restorecon's to AICPs init.tegra3-common.rc :

on post-fs
# Try to fix context when using MultiRom
restorecon /data/data/com.android.bluetooth
restorecon /data/data/com.android.development
restorecon /data/data/com.android.inputdevices
restorecon /data/data/com.android.keychain
restorecon /data/data/com.android.location.fused
restorecon /data/data/com.android.mms.service
restorecon /data/data/com.android.nfc
restorecon /data/data/com.android.phone
restorecon /data/data/com.android.providers.settings
restorecon /data/data/com.android.providers.telephony
restorecon /data/data/com.android.server.telecom
restorecon /data/data/com.android.settings
restorecon /data/data/com.android.stk

# Create /dev/ttyACMX0 for poweron_modem_fls.sh

This let it boot all the way. There may be other files to restore, but it's a good start.

I saw Tassadar made some commits, adding a button to fix broken contexts:

28.3.2015
=====================
* Update to TWRP 2.8.6
* Added "restorecon" option to secondary ROMs (in MultiROM -> List ROMs),
should be used to fix broken SELinux contexts, which can be causing
bootloops of secondary ROMs
[HTC One X] Thunder07:
ya that would fix it, but they'd need to be using that ramdisk (or dev will need to adopt it(if they cared)) for it to work.

well, just with tassadar on IRC if you want to join... and we found the problem

init.rc: restorecon_recursive /data

those are also found on the secondary ROMs as well, but Tassadar actually account for those and removes them before boot...

but due to the way HOX is bootloader locked, and im the only one with a kexec kernel, i kexec the internal ROM manually(bypassing the check for internal ROM).

Tassadar's recommendation is to just avoid primary all together :p

I'm trying to think of a way around it... but the easiest way would be your way(but you'd still need it to be adapted).... and also compiling the new recovery, so you can restorecon on demand... not ideal but thats it...

there is another way, but requires a small amount of work.... you can use AromaKL to apply that fix on any new installed kernel...

but that would require unpacking the ramdisk, "sed -i -e "s/restorecon_recursive \/data//" ./init.rc", repack.(well as i wrote this post.. i worked on AromaKL patch and its done... this will prevent further ROM bootloops but wont fix the old one)

my exams are in less then 10 days, so i wont be able to attend to this until Im done with them,

as you know, my phone is as good as dead, so i dont use it much, which makes stuff like this easy to miss,

so i'd recommend you take over the project, you're already building ROMs & TWRP, so this shouldn't be too much.

###as i said above, i ended up doing this as i was thinking about it. :p

if you'd like to apply the fix through aroma, you'd only need to edit this script, (there isnt even a need to recompile aroma, just unzip the existing one and replace this file with the patched one).

https://github.com/Thunder07/AROMA-Filemanager/blob/master/assets/assets/kl-update-script

### will update AromaKL soon.

Edit:

Fix attached, d-h.st is not uploading, so fix is attached to this post.

note, that this will prevent primary rom from bootlooping secondary ROMs but will not fix current bootlooped ROMs until the new updated TWRP_MR is compiled(you can wait, or remove and reinstall secondary rom).

I'd like for someone (teemo) to take over this project, but if he's/anyone is not up for the task, I'd release one more TWRP update.

Edit:

NOTE:

AromaKL v4.6 is to be used with the new layout

while AromaKL v4.2 to be used with the old layout.
[HTC One X] Tanuj97:
is the multirom app working properly for the new layout ??