yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] nkk71:
well, i didnt use an USB-OTG to install (maybe I'll try that tomorrow), but just for info:

1- downloaded S.ROM-M7-Sense7-Harman-SE-SignROM2.zip

2- made sure it's not corrupt

3- looked at the updater script... nothing strange in there (so I didnt change a single thing)

4- install directly to secondary

5- and voila:

EDIT: and yes bootup takes forever, including the "Android is upgrading" part :mad::mad:
[One (M7) Original Android Development] alex26aly:
OK, will try from internal memory, one question

can I install v32f over 32e?? or I have to unninstal ver 32e first?

UPDATE: from internal memory no problem, could be a bug? On the usb I had around 200mb free after I copied the rom, could this be a problem?
[One (M7) Original Android Development] nkk71:
no need to "uninstall", actually never uninstall as it will remove all multirom files and all of your secondary roms!!!

i just got "M7_Sense7_artmod_10.0.zip" downloaded, and putting it on my OTG... will flash from there and report back...
[One (M7) Original Android Development] nkk71:
Well really slow over OTG, 67/171...
[One (M7) Original Android Development] nkk71:
well OTG is kinda slow, but still

flashed directly from USB-OTG to internal
[One (M7) Original Android Development] alex26aly:
thanks, will try a different usb device, a 8gb one, maybe that was the problem
[One (M7) Original Android Development] alex26aly:
the USB stick was the problem
[One (M7) Original Android Development] ljjehl:
Does this OTG recognize over 32GB drives?? Reason why I asked, 2.8.7.0+ is out with 64GB support (resize2fs)
[One (M7) Original Android Development] nkk71:
Never had any issues myself.

I am (and having been for about 2 years now) using a Corsair Voyager GO 64GB

as well as a regular OTG cable + normal 64GB sticks

and never had any issues (and I've used exFAT format as well as FAT32).... only thing still to test would be an EXT4 partition
[One (M7) Original Android Development] ljjehl:
Nice to know!! I only have 32GB atm, but do plan to add a 64 or 128 to my arsenal soon! I use an awesome adapter from Meenova!! ATM I have a 32GB card in it... **check attachment**
[One (M7) Original Android Development] nkk71:
Can you confirm Sprint working properly, so I can add that information to the OP.

Lollipop should work fine as primary, I've had NuSense7 and ViperOne 8+ElementalX as primaries and both worked fine.

Remember he has a Sprint variant, so he need to only flash things meant for Sprint (it's a CDMA phone and has a different partition layout)

As mentioned above you need to stick with things meant for Sprint variant, even though the recovery and multirom are "patched" to be compatible with GSM, Sprint and Verizon versions, most installer scripts still rely on hard-coded block numbers, which are different between GSM and Sprint versions, so be careful what you flash.
[One (M7) Original Android Development] mitchst2:
[MENTION=2605798]nkk71[/MENTION]

You are probably right about lollipop primary's. I've not had a rom in the primary slot for ages, just kernel.

I tried moving GPE 5.1 to primary and got the not booting ROM in order to protect it message. But now I think of it I was trying out xceed kernel on it. So it's likely the fact that kernel doesn't have kexec patch that's the issue. Will try something else later.

Sorry for the confusion.

mitchst2
[One (M7) Original Android Development] ljjehl:
[MENTION=2605798]nkk71[/MENTION],

I dont know if this was something of an oversight or not:

The original update for MultiRom 32 had a advanced wipe change to separate the internal storage from the other partitions. The current put it back to the original, before 32. (internal storage was moved to second from bottom, now back to third.)

This is just a minor inconvenience for advance wipe users, IMO. It does have the capability to accidentally wipe your internal if you're not careful. I've done that on more than one occasion(big fingers). :silly:

**I thought I did send this post last night, must have been dreaming....** :laugh:
[One (M7) Original Android Development] nkk71:
:cyclops: you prefer this: https://www.androidfilehost.com/?fid=24052804347765642
[One (M7) Original Android Development] ljjehl:
Absolutely!! I appreciate your work!! It does save on errors in development, especially when you are burning the midnight oil (lack of sleep) :highfive:
[One (M7) Original Android Development] miko12312:
Sprint support works , with nusense 5.0.2 7 rom with nuk kernel , but still haven't been able to boot into second rom past boot animation with 5.1 aosp , also multirom app still has no support , also the miui roms are only for m7 not m7spr
[One (M7) Original Android Development] nkk71:
Good to know :)

I have no support for the multirom app, at the moment... not sure I ever will; we'll see.

1- have you been able to boot any secondary ROM? (make sure it's compatible with Sprint

2- if you're getting to the bootanimation, then it's doing "something"... have you waited long enough?

otherwise,

A- please give me link to the ROM

B- when it hangs, reboot to recovery and "adb pull /proc/last_kmsg" and upload that

C- upload the updater-script (found in ROM.ZIP -> META-INF\com\google\android)
[One (M7) Original Android Development] miko12312:
OK tested a couple roms and kernels , found some problems, so if you don't know what your doing don't try or if you mess up you have to format your data or ruu your phone , the nusense rom is not stable if not setup correctly , ended up with having boot issues , but I have been succefully able to boot into a secondary rom but still testing other mods and diffrent versions of Android also the miui roms you posted are only for the m7 not m7spr , I will try to update with more info as my internet is bugging out recently
[One (M7) Original Android Development] nkk71:
please re-read http://xdaforums.com/showpost.php?p=61570231&postcount=55

and the post above yours about (A, B and C)

just in case it's unclear,

1- I don't officially support Sprint or Verizon, since I cant test them.

2- "... As mentioned above you need to stick with things meant for Sprint variant, even though the recovery and multirom are "patched" to be compatible with GSM, Sprint and Verizon versions, most installer scripts still rely on hard-coded block numbers, which are different between GSM and Sprint versions, so be careful what you flash. "

3- [MENTION=4333421]mitchst2[/MENTION] was sharing his personal setup on his device (not Sprint)... it works for him, and I'm happy it works for him.

nowhere

did I say / were you told to use MIUI ROMs

(not to mention those posts were all in the wrong thread anyway, I had to copy them here)

4- "if you don't know what your doing don't try" -> absolutely correct, not only should you not be messing with your phone if you don't know what you're doing, you should definitely stay away from multirom... in case you missed it in the OP:

​

5- I would be more than happy to remove Sprint and Verizon support, if that suits you better, since I can't personally test them.
[One (M7) Original Android Development] miko12312:
Looks like base rom has to be sense based doesn't matter as long as the so far only kernel elemental x has the patch , if using nusense 7 selinux set to permissive will bootloop the device ,so far just leave the base rom as stock, with musense 7 flash then back up boot.img youll have boot problems with some modifications to the base rom ,because after flashing it needs fastboot flash boot boot.img form the zip , all roms so far booting up as secondary , third ,etc., ended up having to start everything new. Either the rom I'm using as base is messed up or other roms are conflicting with eachother
[One (M7) Original Android Development] mitchst2:
I'm happy too :D

Miui is indeed personal choice not a requirement.

On another note. I'm using Viper now and don't want to change the kernel. Is there any way to add kexec patch to the stock kernel?

mitchst2
[One (M7) Original Android Development] nkk71:
why not just use elementalX instead, i wouldnt know how to add kexec to an existing kernel.... that's beyond me :o
[One (M7) Original Android Development] mitchst2:
I could and might at some point. It breaks Dolby audio on that ROM as stock kernel is patched for it. There is a fix for ex though. Want to see how stock kernel performs for a while. Will ask if stock kernel has kexec patch first. No biggie as OK as secondary anyway.

mitchst2
[One (M7) Original Android Development] maxpaynezm:
mitchst2 there is solution, delete ds.apk in system/app and install this mod http://xdaforums.com/showthread.php?t=2211163

i have viper rom 9, this mod works great with this super kernel :D
[One (M7) Original Android Development] mitchst2:
Cheers. Seen that just staying stock for now. As I say no big deal as it runs fine as a secondary.

mitchst2
[One (M7) Original Android Development] ljjehl:
I have kexec added to my source kernel for Xenon:

https://github.com/ljjehl-XHD/andro...mmit/9cd68a1983281f5664c3425552528c45107abb48

https://github.com/ljjehl-XHD/andro...mmit/b81ab08c48c2631ea547e966ed3c3ff09f2467b2

For any of you that can build a simple kernel or Rom, all you need is this in your kernel.
[One (M7) Original Android Development] miko12312:
Not trying to get you to remove it ,trying to get more support , just pointing out what happens , I'm willing to test what ever, with the right setup everything runs with no problems , does apps in roms base and secondary etc conflict with each other
[One (M7) Original Android Development] mitchst2:
Do you mean does the same app in the primary and secondary conflict. If so no. They are standalone installs with their own data and cache.

mitchst2
[One (M7) Original Android Development] wiQbold:
Hi.

I tried to flash all of these recoverys with success, but it reboot to system not in recovery.

tried with fastboot and flashify, tried with erase cache.

no idea what i ve done wrong!?

could someone help or lead me to the right column/thread!?

m7_ul s-off

darkbootloader

HBOOT1.61

ARHD92.0

7.19.401.2

ElementalX 20.2

(xposed, ICECave10.2)
[One (M7) Original Android Development] nkk71:
did you check MD5 on the download?

here's how i flash recovery (I really prefer fastboot flash over apps):

C:\ADB3>[B][COLOR="Blue"]fastboot devices[/COLOR][/B]
HTxxxxxxxxxx fastboot

C:\ADB3>[B][COLOR="Blue"]fastboot flash recovery TWRP-multirom-20150627-v32f-UNOFFICIAL-m7univ.img[/COLOR][/B]
target reported max download size of 1514139648 bytes
sending 'recovery' (14930 KB)...
OKAY [ 1.913s]
writing 'recovery'...
OKAY [ 1.360s]
finished. total time: 3.273s

C:\ADB3>
[One (M7) Original Android Development] ljjehl:
First you need to make sure you are connected in bootloader. I suggest "sudo fastboot devices", so you can make sure fastboot works. If it doesnt, nothing you do after that will.
[One (M7) Original Android Development] wiQbold:
Thanks you both...

I have flashed firmware with normal Bootloader & now it worked!!

[checked that md5sum. it is the same.

I am @ work so I use Windows instead of Linux.. I could give it a try @ home..

I use adb & fastboot from android-studio-bundle-135.1740770-windows.

adb & fastboot worked for my m7, m8 and my Nvidia tablet..

then I select RECOVERY from HBOOT.

then the bootsplash shows for a few seconds and it reboots normally to ARHD..

then i d flashed the TWRP 2.8.7.0 and try to get in recovery and it worked.

then I tried to flash the recovery Image from within the recovery, but the same problem to get back in recovery..

I tried to rename it to "recovery.img" but also the same problem

What has struck me is that the TWRP-folder is a file when android has boot.

so maybe it would be mounted with the original TWRP.

so i decide to rename it, that the modified TWRP could create a new one..

but nothing changed

I don t know how to get a log?

last year I d use the version 29 in the other thread. maybe I d bricked somethng??

or maybe the darkbootloader?]
[One (M7) Original Android Development] miko12312:
When flashing roms it wipes the data for all roms , it seems like it uses the app data for all roms been noticing it , have to make backups of all apps I mainly use
[One (M7) Original Android Development] mitchst2:
Not had that myself

mitchst2
[One (M7) Original Android Development] nkk71:
it's probably best if i completely remove Sprint and Verizon (I dont support them anyway, since i have no way of testing), and if nobody (who is actually testing them) wants to provide me with the ABCs

from previous post(s):

2- if you're getting to the bootanimation, then it's doing "something"... have you waited long enough?

otherwise,

A- please give me link to the ROM (

thread and file

)

B- when it hangs, reboot to recovery and "adb pull /proc/last_kmsg" and upload that

C- upload the updater-script (found in ROM.ZIP -> META-INF\com\google\android)
[One (M7) Original Android Development] miko12312:
Everything works , every rom from jb to lollipop , just have issues with rom app data it wipes , when flashing a new rom through multirom , since every rom auto wipes before flash unless option not to is there other than that I know what I'm doing , I just can figure out why it's doing that , exposed installer works with multi boot , flashing mods idependenly , no need to drop support only put into beta , If it hangs its because of the setup , you have to setup it a certain way
[One (M7) Original Android Development] mitchst2:
If I follow what you are saying.

When installing a secondary ROM I always install without wipe as it's not necessary.

mitchst2
[One (M7) Original Android Development] nkk71:
we seem to have a huge language barrier here :(

and as long as you do not give details about

your setup

don't even provide a link to what you are flashing,

nor how you are flashing

there's very little anyone can do, or fix it

I've asked several times, but you do not want to post the necessary information

that is your choice, and I can't do anything about it

.
[One (M7) Original Android Development] nkk71:
Teaser :p

notice anything new
[One (M7) Original Android Development] mitchst2:
Yes

mitchst2
[One (M7) Original Android Development] nkk71:
you have mail, hmm not sure that came out right :eek:

hopefully in the coming day or two...
[One (M7) Original Android Development] ljjehl:
2.8.7 looks interesting....lol
[One (M7) Original Android Development] nkk71:
updated to MultiROM TWRP to 2.8.7 (the one dated 20150704) in the same folder, direct link

TWRP_multirom-20150704-v32f-UNOFFICIAL-m7univ.img

fastboot flash recovery TWRP_multirom-20150704-v32f-UNOFFICIAL-m7univ.img

I was trying to get encryption to work, just to keep up with official multirom (then i would have bumped version to 32g), but that didnt work for me,

... let's just say EPIC FAIL :o

(well it worked in recovery, but ended in not in multirom bootup, bootlooping the ROM... an occasional successful boot

once

:p)

and honestly, I dont really see why I would even bother, as all the ROMs (primary and secondary) would have to be AOSP based, so no HTC Sense or GPE ROMs

enjoy, let me know if you run into any bugs
[One (M7) Original Android Development] rhong:
Thanks for the update..running sense 7 as primary and various secondary like miui6 , aosp and sense. No problems.thank a lot
[One (M7) Original Android Development] ljjehl:
Does OTG still work in the newest version? I am currently trying to use it, but have not been able to connect in recovery.
[One (M7) Original Android Development] nkk71:
still works for me (i've tried ext4, f2fs, and exfat) on a 8GB stick (my 64GB is currently busy :) ), but this still applies for some reason

i was never able to figure the MTP (on-off-on) nor the OTG problem :(
[One (M7) Original Android Development] miko12312:
Been having adb trouble since I had setup my PC for an LG phone , once I get it running today for my HTC I'll get all the information
[One (M7) Original Android Development] ljjehl:
I just wiped my 32GB to ext4, so thats why I asked. I thought I read a procedure before that sometimes it didnt connect until you did a routine to connect? It connects fine in a rom, but lately no signs of life in recovery

Edit: I was right. I removed while in rom, I then inserted after I booted to recovery. Its now Aliiiive!! :P
[One (M7) Original Android Development] nkk71:
So it's working? As before?

In a year or two, someone will fix it :)
[One (M7) Original Android Development] -leo-:
On my pn07120 it has the same problem on otg and mtp so i use single rom now......... :P
[One (M7) Original Android Development] ljjehl:
I dont really see much of an issue with mtp. As for OTG, if you eject USBdrive while in a rom, then reboot to recovery, it should work fine. I added it while in rom, then rebooted to recovery. It was unresponsive as OTG until I rebooted back to rom and ejected it
[One (M7) Original Android Development] nkk71:
the official version of TWRP http://teamw.in/project/twrp2/

has the same problems, so since i'm probably using the same kernel source, the multirom version will suffer the same effects.

toggling (On->Off->On) MTP to get it to work is easy enough

as for OTG you dont need to boot up the rom, just unplug it, then in recovery select reboot->recovery; once it's back in recovery plug it in and mount it
[One (M7) Original Android Development] -Juff-:
Thanks for all the updates! :)

I've a question now... Can I install ROMs with Aroma installer normally and without any problems? I'm currently using pretty much only CM-based ROMs, but I want to give the new ViperOne a try. When I started the flashing process, I was just wondering if Aorma maybe messes with some MultiROM things.
[One (M7) Original Android Development] nkk71:
yep, should be good to flash [almost] anything.... everything is working for me

as always, backups are highly recommended, especially a nandroid backup of your "daily driver" (and copy that to PC too)

i've had no problems with AOSPs (CMs or other), Sense, GPE, MIUI, even some ASOP ROM (sorry, the last one is kinda a joke :p)

last ViperOne I flashed was 8.0.0, and straight to secondary with no problems
[One (M7) Original Android Development] mitchst2:
ViperOne 9 OK

Running it as a secondary ATM.

mitchst2
[One (M7) Original Android Development] razielmkd:
For all you got problem with recovery can't run newer version than 2.6.3.3 flash this recovery it works, thank you dev for this
[One (M7) Original Android Development] MaratabHashmi:
Thanks [MENTION=2605798]nkk71[/MENTION]

USB OTG work for me
[One (M7) Original Android Development] Qu3ntin0:
Multirom for Sprint HTC One M7

Since MultiROM doesn't workfully on the Sprint HTC One M7 (wls) on Lollipop 5.0.2, I made some modificationsand so you can download all the necessary files from my Github: https://github.com/Qu3ntin0/qu3ntin0.github.io/tree/master/multirom
[One (M7) Original Android Development] browy:
Hello guys. Can some one please help me solving this issue? My internal ROM is pure android 5.1 and my secondary ROM is CM11. After flashing the secondary ROM, my primary ROM can't read anything from the sd card. I use ES File Explorer and Solid Explorer to check, both show me that I have an empty internal storage. However when I connect my phone to my laptop, everything is still there.

On the secondary ROM I do have access to the internal storage, I've only lost access with the first ROM.

Really hope someone can help me.
[One (M7) Original Android Development] nkk71:
Thanks, but I would highly recommend either fixing the apk, or removing it, the following is going to cause major headaches for anybody that installs it on non Sprint devices:

{
"names": [ [COLOR="Red"][B]"m7", "m7_ul", "cm_m7", "m7gsm"[/B][/COLOR], "m7wls" ],
"manifest_url": "http://qu3ntin0.github.io/multirom/manifest.json",
"check_gpg": false,
"ubuntu_touch": {
"enabled": false
},
"devices": [
{
"name": "recovery",
"path": "/dev/block/mmcblk0p36"
[COLOR="Red"]^^ on m7(GSM) this is actually the [B][U]cache[/U][/B] partition[/COLOR]

},
{
"name": "boot",
"path": "/dev/block/mmcblk0p35"
[COLOR="Red"]^^ on m7(GSM) this is actually the [B][U]system[/U][/B] partition[/COLOR]

},
{
"name": "cache",
"path": "/dev/block/mmcblk0p38"
[COLOR="Red"]^^ on m7(GSM) this partition doesnt even exist[/COLOR]

}
]
},

that's one of the reasons I havent added MultiROM Manager app support
[One (M7) Original Android Development] nkk71:
try a restorecon while in the primary ROM:

adb shell
su
restorecon -FR /data/media
exit
exit

reboot if necessary
[One (M7) Original Android Development] browy:
Thank you very much. That really helps.
[One (M7) Original Android Development] mitchst2:
Was going to post that.

This issue isn't Multirom related, it's a lollipop thing many people seem to have.

mitchst2
[One (M7) Original Android Development] Qu3ntin0:
I'm get the error: "Failed to download info about updates!" whenever I put it as a new group. Any help?

---------- Post added at 04:28 PM ---------- Previous post was at 04:21 PM ----------

@nkk71 I'm getting the error: "Failed to download info about updates!" whenever I put it as a new group. Any help?
[One (M7) Original Android Development] aditya desai:
I wanted to remove multiboot,when I try flashing multirom uninstall.zip..its giving error,some thing like this "E:/error executing updater binary in zip"
[One (M7) Original Android Development] nkk71:
sorry my bad, that was an old version, and which would only work with the first release, so it would have failed on the first assert (model check)

updated it now: https://www.androidfilehost.com/?fid=24052804347771492

(same file name, but different hash)
[One (M7) Original Android Development] nkk71:
no idea really, but used to happen sometimes (with v29)

i'll look into adding MultiROM Manager support over the weekend

EDIT: i guess you have a Sprint M7, are you having any problems like miko12312 above?
[One (M7) Original Android Development] miko12312:
Nothing is actually created in multirom folder on /0/sd even with es file manager with root and hidden folders options on I can not find were they are installed and created throughout the whole phone , also yes the recovery is 2.8.6 univ multirom, one problem with the recovery mtp and adb seems not to work unless the system is mounted and selinux permissive is possible, been running for a couple days with out problems , and the boot.img needs to be flashed or the stock kernel is used something that has been an issue with nusense7 roms , its pretty much flashing the nuk kernel over the stock kernel with a flag I think , it's in the nusesne 7 forum for sprint , with out that fastboot flash multirom will not work , multirom has no problem with daily use and causes bootloop with or without multirom on the m7spr , just with what I have stated in previous post , I also notice in the update script for multirom zip it flashes the necessary files for Ubuntu touch , but will the files for the m7 work for sprint , you got most of the big parts working just the little details need to be adjusted , if there are other files or logs I can pull let me know , multirom is compatible with lollipop , aslong as you have a kernel that's patched with the hard kexec or whatever , I will also take a look at the other post that have problems and see what they can be , maybe a new forum for just sprint multirom for q&a should be made, make things a little more clearer for diffrent variants , I will also go through your setup of the recovery log and check the diffrences on yours
[One (M7) Original Android Development] mitchst2:
ROMs are stored here as op has already mentioned.

data/media/0/multirom

mitchst2
[One (M7) Original Android Development] miko12312:
Files found , now is it possible to use the files to install Ubuntu touch for the m7 on m7spr since all the files to boot are installed
[One (M7) Original Android Development] domicq:
although is your multirom zip universal for all version of m7, you have another chance to get multirom app working for all devices properly.

just add to manifest gsm device with correct partitions, sprint with correct partitions etc., but the links will be same for all devices.