Hi All
I succesfully upgraded my firmware and am running the newest Viper and it works great. After reading about multi-rom I got super excited as there was a program I used with a pervious androud (htc phne even i think) to switch between MIUI and a few other ROMS.
Anyways.. I get the "non-exec kernel error" inside of ROM manager as well as TWRP under multiROM ( i think when I attempt to flash another rom in a diff slot).
I've tried installing a few of the kernels through the multirom app and it always seems sucessful as well as just downloading the kernels and flash in TWRP without error.
Does anyone have any suggestions or any extra info I can provide to get this to work? I'd LOVE multiROM so I can try new things and keep my daily driver.
Thanks in advance friends
I have been playing with this also recently. As far as I can tell only the select few kernels work with multirom. The kernel has to be patched to work with multirom. I'm using lunar kernel(as my primary rom kernel) and everything works fine. You can't use any of the kernels from the international m8 that's on multirom thread. Those are not designed for Verizon m8. I made the mistake of trying to flash those also.
Only the primary ROM needs to be patch with exec. Make sure if your flashing a kernel to a secondary ROM do it in twrp under multi ROM advanced settings and choose the ROM you want to flash the kernel to. The twrp main screen is for your primary rom
Sent from my One M8
I can't get the multirom manager app to "see" the ROM I want to install....Where does one put (ie: folder placement) the zip file you want to install as your secondary?
Related
I know a while back when i installed cm7 on my vibrant i had to do a lot of steps with clrad and flashing kernels one at a time... if i install with "rom manager" do i need to do any other step? does it change the kernel and everything for me already???
All ROMs have Kernels, otherwise they wouldn't work. If you want CM7 you can flash the latest Nightly using Rom Manager and aside from selecting to flash the gapps package too, there's no need to flash anything else.
Custom Kernels can be flashed from Recovery after the fact if you feel the need to try them.
So, I am going to do a lot more research prior to rooting, but I had a couple of general questions that I was wondering about, before I begin the steps leading up to rooting.
1) I presume the easiest way for me to root my Thunderbolt is the Revolutionary Root? This will take be through rooting and installing the CW recovery that I need, correct?
2) Right after I root, If I want to install roms/kernels? than I can just get Rom Manager from the android market?
3) Once I install Rom Manager, can I just flash a rom that is compatible with my Thunderbolt? Can I just flash a kernel that is compatible with the Rom?
I suppose where I get a lil lost is the flashing compatibility part. What kernels work with what roms, what roms I can flash... I have read a number of articles, so I suppose what I'm asking is...
Will the process more or less be: Revolutionary Root, Install Rom Manager from market, flash a rom (just the most popular one). Is the Kernel flashing piece important? Do I need to flash a different kernel? Is it easy to tell in Rom Manager which kernel/rom I can use?
Yes use revolutionary to root and install custom recovery (cwr). You can use ROM manager to download custom roms if you want, only roms for your device will show up. Or you can download custom roms from forums, this is the method I prefer.
Just use kernel that comes with the Rom for the time being some developers include a custom kernel and others make modifications to the HTC kernel itself. Kernels are seperated in development section having to do with sense and aosp that is the first way to seperate them. Second would be leak the kernel was based on such as imo test 3.8 was based on newest leak so it works for just about if not all newest sense roms. When in doubt fire up a question in the Rom thread itself and ask what kernels those people are using, find a Rom like BAMF or thunderstick or synergy where the developers or support staff are very active.
Also you will need to flash a new radio right after rooting if you are still using froyo, I am using newest leak but different phone work differently. Once you install the radio VIA Hboot. Reboot phone and remove zip file from root of SD card now place your Rom image on SD card and reboot to recovery and install your new Rom.
Sent from my Thunderbolt using XDA App
This is good info.. thanks.
Well, I am upgraded to Gingerbread as of VZW's last update and still unrooted and stock.
So, if I were to root (using revolutionary) and install Rom Manager... could I just install something like Cyanogenmod or BAMF right through Rom Manager?
What do you mean by kernel that comes with the Rom? The kernel that is listed to use with the Rom? Or do you mean if I flash BAMF or something popular, just leave whatever kernel I have as is?
Bwangster12 said:
This is good info.. thanks.
Well, I am upgraded to Gingerbread as of VZW's last update and still unrooted and stock.
So, if I were to root (using revolutionary) and install Rom Manager... could I just install something like Cyanogenmod or BAMF right through Rom Manager?
What do you mean by kernel that comes with the Rom? The kernel that is listed to use with the Rom? Or do you mean if I flash BAMF or something popular, just leave whatever kernel I have as is?
Click to expand...
Click to collapse
When you flash a rom it flashes the kernel too with whatever one the devs packed with it.
Sent from my HTC ThunderBolt using Tapatalk
Okay, clear enough.
So, for someone like myself, just use revolutionary root, install rom manager and play around a lil with flashing roms using rom manager for awhile. I understand that I can install roms from my SD card, but it sounds like at least initially installing roms right from rom manager would be the simplest. I can also not worry about installing a different kernel during this "honeymoon" phase. Just pick the latest version of whatever Rom I want and flash the rom?
After you root you need to install superuser so CWM can function. I have read that some people flash their CWM via hboot after s-off and then go right to recovery to flash the root gaining RUU, then enjoy your root.
Do not flash ROMs right from CWM reboot to recovery clear data/cache and under advanced davlik cache and then install Rom from install from SD and choose zip file and I always store mine in downloads since I download all my roms right to my phone and download md5 checker from market and always check the md5 if it does not match don't think its a mistake redownload and try again.
Sent from my Thunderbolt using XDA App
Agreed, it is better to install the ROM through recovery instead of installing through ROM manager as sometimes it doesn't work right.
Don't forget to use thank you for all you great answers.
Sent from my Thunderbolt using XDA App
So I am new to htc and new to what to do, been on Samsung for years and htc is way different.
First, once I update firmware will it be safe to flash the roms in the android development section even if they are from July or August ?
Do the Roms include kernels or do I need to find one and flash it after I flash the rom along with gapps ? If so what kernels do you recommend and /or do you have a list of some of them ?
What is fastboot and how do I use it? I am updating the firmware through sd card method but also want to update the twrp and I heard that is done through fast boot. Does that require a computer or?
Thank you for taking the time to read my questions
thrgk said:
So I am new to htc and new to what to do, been on Samsung for years and htc is way different.
First, once I update firmware will it be safe to flash the roms in the android development section even if they are from July or August ?
Do the Roms include kernels or do I need to find one and flash it after I flash the rom along with gapps ? If so what kernels do you recommend and /or do you have a list of some of them ?
What is fastboot and how do I use it? I am updating the firmware through sd card method but also want to update the twrp and I heard that is done through fast boot. Does that require a computer or?
Thank you for taking the time to read my questions
Click to expand...
Click to collapse
First off I assume you are s-off and unlocked via firewater or sunshine.
1) this is only anectodal but I ran ViperROM 1.8 (4.4.2 based) with the 4.4.3 firmware for a few weeks without issue.
2) all Roms come with a kernel. Some are stock, some are custom but they all come with one. ASSUMING you are s-off then the packaged kernel will be flashed along with the rom. If you're looking for a custom kernel make sure you find a Sense/GPE/AOSP kernel which matches your rom type (SENSE/GPE/AOSP) and flash it AFTER flashing the rom. Flashing a rom will overwrite whatever kernel you previosly had installed with the new rom's kernel. I am currently runing ViperROM 2.5 which is a Sense ROM with the EliteLunar kernel (sense version) with no issues.
3) fastboot is an interface between a computer and your phone. I always find it alarming when people ask this question. Learn and become familiar with fastboot BEFORE YOU FLASH ANY ROMs OR ZIP FILES IN RECOVERY. I'm not being rude, I assure you this is sound advice. Many fastboot tasks can be performed with apps like flashify or by a flashable zip file which many devs are kind enough to create. However, having fastboot set up and functional (that includes knowledge of how to use it) is irreplaceable if/when things go downhill.
cntryby429 said:
First off I assume you are s-off and unlocked via firewater or sunshine.
1) this is only anectodal but I ran ViperROM 1.8 (4.4.2 based) with the 4.4.3 firmware for a few weeks without issue.
2) all Roms come with a kernel. Some are stock, some are custom but they all come with one. ASSUMING you are s-off then the packaged kernel will be flashed along with the rom. If you're looking for a custom kernel make sure you find a Sense/GPE/AOSP kernel which matches your rom type (SENSE/GPE/AOSP) and flash it AFTER flashing the rom. Flashing a rom will overwrite whatever kernel you previosly had installed with the new rom's kernel. I am currently runing ViperROM 2.5 which is a Sense ROM with the EliteLunar kernel (sense version) with no issues.
3) fastboot is an interface between a computer and your phone. I always find it alarming when people ask this question. Learn and become familiar with fastboot BEFORE YOU FLASH ANY ROMs OR ZIP FILES IN RECOVERY. I'm not being rude, I assure you this is sound advice. Many fastboot tasks can be performed with apps like flashify or by a flashable zip file which many devs are kind enough to create. However, having fastboot set up and functional (that includes knowledge of how to use it) is irreplaceable if/when things go downhill.
Click to expand...
Click to collapse
Thanks for all the info. So if I am on 4.4.3 and want to flash a 4.4.2 rom just flash the 4.4.2 firmware just to be safe before flashing the 4.4.2 rom?
Also where are the kernels located ? Are they carrier dependent as I didn't see any yet browsing but didn't look hard either.
So I can do flash boot through flashify and be ok? Now all roms and kernels are flashed through twrp tho right ?
EDIT: actually fastboot can flash rom and kernels so no real need for custom recovery other then for convenience?
Btw do you have a kernel recommendation for aosp, sense, ? I already saw your recommendation for sense above.
Thanks !!
Sent from my SM-N900V using XDA Free mobile app
I have a feeling that it's simply not necessary to downgrade your firmware in order to run a 4.4.2 rom but you should find a more reputable source than myself. I'm just trying to answer these easy questions to save time for the guys who really know what they're doing. Once you do start flashing things, always make sure 1) they are for your device (and carrier, unless unified for all carriers) and 2) the md5 of the downloaded file matches that provided by the hosting website or the OP.
I'm not a fan of flashing utilities simply because I've heard of instances where they don't work correctly. For example, I keep hearing how the TWRP manager app flashes TWRP to the system partition on Verizon devices and sends the phone into a sort of recovery loop. I would suggest gaining knowledge about the fastboot flash command "fastboot flash <partition name> <filename.extension>" and how to enter and flash within RUU mode.
My experience is that ROMS and kernels are easiest flashed through a custom recovery especially when the developer packages it with an Aroma installer script.
A few Sense/GPE custom kernels exist for verizon. There's MassStashed and Checkm8 (no longer maintained?) for 4.4.2 roms. Also, for 4.4.3 roms I only know of the EliteLunar kernel which isn't on XDA although you can find a few links to it in the forums if you search. Last I knew, there weren't any AOSP kernels which work with verizon but that might not be true anymore. The general HTC One m8 forum may have some kernels which aren't represented in the verizon-specific forum. Just make sure and find out if they're compatible with verizon devices. I'm pretty happy with sense so I haven't wondered off to AOSP like I usually do.
so do you recommend to use flashify or no?
thrgk said:
so do you recommend to use flashify or no?
Click to expand...
Click to collapse
Its the easiest way
thrgk said:
so do you recommend to use flashify or no?
Click to expand...
Click to collapse
I'm not saying you shouldn't use flashify, it's awfully convenient. Just make sure you're using it for the convenience and not because you don't know how to accomplish the same tasks in recovery/fastboot.
Q&A for [MOD] MultiROM v28d
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
My stock rom is not booting anymore. just black screen for more than 1 minute...
Installing multirom through the app
Hi guys, I've used the whole morning to read through all 100+ pages today. Now i'm back home and i'm ready to install this. But then I found out on the OP that it states that "You can install it either from MultiROM Manager app or from this guide".
Now im wondering if it means that i could just install the app through google play and its done? So i do not need to go through flashing it through recovery, modify recovery? just patching the kernel?
EDIT: i think i actually did it successfully already. Thanks for the great work 1
My personal cm11 builds, using no modifications won't boot using multi boot. Do I need to include something extra?
You need to use a patched kernels like ak kernels
Sent from my A0001 using XDA Free mobile app
chak29 said:
You need to use a patched kernels like ak kernels
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Even if it's secondary rom?
The internal ROM needs the patched kernel.. The secondary ROM don't need. But not all the ROMs works with multirom..I use cm11s38r with ak patched kernel(make sure you get the right kernel) for the internal. Secondary I use mahdi and liquids works fine both stock kernel...
Sent from my A0001 using XDA Free mobile app
Guys if I install multirom. Will I be able to have whatsapp in every rom? Or I should verify always the number?
tapyon said:
Guys if I install multirom. Will I be able to have whatsapp in every rom? Or I should verify always the number?
Click to expand...
Click to collapse
As Whatsapp verifies your device (and rom) you'll have to verify your number every time you boot into another rom!
WhatsApp won't synchronise all your messages. (I'm pretty sure, the ones you wrote won't show up)
Edit:
Die anyone managed to install Dirty Unicorns as a secondary rom? Mine doesn't boot :/
Ok so i've run into some alarming problem (by alarming i mean that i haven't found i solution and that i can't boot)
So after I rooted my phone (TWRP installed) i decided to install multirom, i folowed the procedure. Custom TWRP is installed and running, the boot menu is working perfectly, and i havce the custom kernel, only problem is, i haven't any secondary rom installed, and i can't boot to primary (black screen for 2-3 minute then reload multirom boot menu)
Does any one have any idea of what i can do to try to fix this ?
ETA: I managed to boot to main rom again by flashing CM11s from the OPO toolbox, device ended up not rotted and iv'e got Cyanorecovery (default one) and default kernel.
After some test i'm sure the kernel is the source of the problem, i can easly get the recovery but everytime i try to install the kernel the phone won't boot or bootloop.
So essentially the kernel downloaded from the app doesn't seem to cooperate
CountDooku said:
As Whatsapp verifies your device (and rom) you'll have to verify your number every time you boot into another rom!
WhatsApp won't synchronise all your messages. (I'm pretty sure, the ones you wrote won't show up)
Edit:
Die anyone managed to install Dirty Unicorns as a secondary rom? Mine doesn't boot :/
Click to expand...
Click to collapse
I found a one way to do it. Titanium Backup ^^
Copy >>> restore in the new rom and u have whatsapp working in two roms.
Hey I'm trying to flash ak on my 3rd ROM but keep getting binary could not update from zip error? ... Any help with this
I tried to flash liquidsmooth as secondary ROM. But then com.android.gsf.login seems to be not working.
Anyone else facing this problem? Tia
Android L only work as internal ROM. I tired many combinations. Always ended up boot loop.
Sent from my A0001 using XDA Free mobile app
Multirom work fine with Lolipop
I just flash Lolipop on my opo and it work fine, but if i flash it in secondary it cannot work.. So first I flash it as secondary, after complete of flashing I swap the internal ROM with the L ROM.. After L ROM become internal ROM I wipe it again then I flash all the file again.. Then it work fine, even I change the L ROM to secondary it work fine.. but my primary ROM cannot boot.. So for my primary ROM I will reset it back and flash the ROM back to see how it goes then..
cyanogen don't boot anymore
hello, thanks for the awesome work, i'm having an issue with cm (on my oneplus one) the other roms boot and works fine; but cm stay stuck on a black screen (i made cm updates :s) i already tried to flash kernel again but i doesn't work; an idea to fix this ?
Multirom and L
Having some difficulty getting Multirom to run an L ROM. When I install an L ROM as secondary and try to Boot, I get a bootloop. Then when I try to boot any of my other secondaries, they get stuck on the boot image after trying to boot L. I have to reflash the existing secondaries to get them to work. The Primary is never affected, it boots fine. I am running CM11s as primary with the AK.010.OPO.CM12 kernel. I have updated TWRP to the 20141116 version. The L version is bpear96's 11/16. Any help would be appreciated!
Yellowish screen
Hi, I just installed multirom on stock rooted rom and after reboot my screen became yellowish. I think it's a patched kernel problem. Anyone has got a solution?
Is it possible to have mahdi as primary rom and cm11s as secondary, and vice versa?
Sent from my iPhone using Tapatalk till i get my Bacon
Hello, I have cm11s 44s with stock kernel. If i want cm12 as secondary I have to flash cm12 kernel in multirom app?
I had stock 5.0 and installed MultiROM via fastboot. And after that I tested out xTraSmooth 3.1 on the secondary ROM so I pretty much liked it so I said **** it, why not make it the primary. So I formatted the device completely secondary and primary and all. And I copied the zip files and flashed them as primary. I also flashed MultiROM v30 as when I went to advanced it said MultiROM wasn't installed or something like that. Anyway, I wanted to test some more ROMs now, I ended up with a bootloop or updater binary error.
So, I said I'll test it on the same ROM I had tested before, which is now my primary one. So I flashed another xTraSmooth as secondary, it flashed without a problem but still I got a boot loop. So, I tried installing the modified TWRP again using fastboot, flashing MultiROM again and flashing the ROM again but still. I got a bootloop. I even flashed a nightly kernel from frnaco after that and still a bootloop. What should be done? Or is this some new problem with MultiROM?
Bump
SA3DX said:
... I also flashed MultiROM v30 as when I went to advanced it said MultiROM wasn't installed or something like that. ...
Click to expand...
Click to collapse
That sounds very strange to me! I'd try a fresh install using the MultiROM Manager Android App. Make sure that the status displayed in the app does NOT say Kernel: doesn't have kexec-hardboot patch! (see Installation section in the first post of the MultiROM thread).
... another xTraSmooth as secondary, it flashed without a problem but still I got a boot loop. So, I tried installing the modified TWRP again using fastboot, flashing MultiROM again and flashing the ROM again but still. I got a bootloop. I even flashed a nightly kernel from frnaco after that and still a bootloop.
Click to expand...
Click to collapse
Did you try the newest version of xTraSmooth (3.3)? I had a quite similar situation with AICP for Nexus 7. In fact, at first it never got past the boot animation and then "suddenly", with a newer version, things were fine.
You may also want to try installing another ROM as secondary, just to make sure your current MultiROM installation works as it should.