Database Info

[Q] PAC-man ROM not booting anymore

hi,
so as i can not post in the android development subforum i'll have to try it here..
I have: HOS with TWRP 2.4.4.0 (goo manager) with HBOOT 2.15 (S-ON) running PAC-man ROM 22.1 (the newest update)
also i have bubba v4 installed and everything was working really perfectly. (s2w and some kernel tuner settings)
yesterday i played a bit with UI settings, nothing that i thought would stop my device from booting..
today i woke up, the battery was empty so i plugged in, turned on and left, after a while i came back and it was still at the boot
animation (PAC is loading...).
now i have tried to reflash bubba, PAC (cache+dalvik wipe) and the boot.img via fastboot. still it is stuck on that loading screen.
now i'd really like to use this rom with the bubba kernel.
any clues how i could get it out of this boot cycle?
thanks
-t.

2.4.4.0 is kinda crap in certain things. Flashing roms is one of them. Please use 2.3.3.0 as this will work.

why do you think that twrp version is the problem?
flashing this rom with 2.4.4 has worked well, so flashing over the same ROM with it shouldn't be problem...?
when flashing or wiping everything seems to work normally.
also, i am not sure how to downgrade twrp!?
best,
-t.
edit: okay i found out, fastboot flash recovery .. should work. i'll let you know if it works afterwards *fingers crossed*
edit2: reflashing the ROM it takes much longer (maybe thats good?) i just hope it finishes at some point...
edit3: okay, so re-flashing with twrp 2.3.3.0 did'nt work either, it is still stuck at the "PAC loading..." stage
(yes, i flashed the boot.img too)
any more clues?
finally i had this phone set up just the way i wanted, it was perfect and then this. why couldn't it just keep working
makes me sad, i want to use my phone damnit

okay, so i flashed and wiped and flashed and wiped a few times, system, cache, dalvik whatever, suddenly it started working... i also flashed some different kernels (as i thought some bubba stuff might still be there)
soo IDK what it was but now it works again, thank god..
maybe its worth mentioning that i flashed an older PAC rom (v22.0.1_20130324-230044) though i am not sure if that was the problem...

Sorry, I was off for some time from this forum.
If your bootloader version is > 1.09 you'll have to flash the kernel separately due to some restrictions in the higher bootloader versions.
If e.g. you flashed boot.img only from the 'bubba.zip' you're missing some of the modules needed for working coming with that flashable zip. Just have a look inside the zip file and you'll see some different content besides the boot.img. So you need to flash the complete zip file (to get the modules) and separately again the boot.img (to get the kernel itself).
The point about 2.4.4.0 / 2.5.0.0 is, that some installer scripts for some roms don't work as they should.
:good:

Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Well nevermind I guess I learned something from this little action that cost me most of my precious Saturday...
Also I now tried flashing twisted 3 and bulletproof kernel neither of them worked for pac rom, maybe someone could explain to me which kernel works for which rom? I thought they are completely interchangeable as long as they are compatible to the hardware..
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Well, appreciate the help.
Best,
#t.
Sent from my One S using xda app-developers app harhar

Bulletproof is for sense
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | ElementalX_4.2

Aha okay, I thought sense is like any app running ontop of any kernel...alright.
Sent from my One S using xda app-developers app

tehtomi said:
Hey,
Thanks, yeah but the thing is I installed Bubba right I think. Even manually copying the modules and setting the permissions...
and it has been working. Does the system lose modules when the permissions are not exactly right? I remember leaving the exec permission on for the modules because I was lazy
Click to expand...
Click to collapse
Usually the installer script should set the right permissions already. Nah, modules shouldn't go lost this way ( system/lib/modules/*.ko).
tehtomi said:
And how do boot images work? I thought if you flash a boot image it overrides the old one, but flashing a Rom and then only installing a boot image from some kernel doesn't end with booting the rom (that's how I tried to repair it in the first place )
Click to expand...
Click to collapse
In short: boot.img = kernel
It's stored in an own partition (block) on the phone, That's why you have to use 'fastboot flash boot boot.img'. Same for radio: 'fastboot flash radio radio.img' and so on. The bootloader will load them first from this block. But search Google if you'd like to know more. lol
Usually there is a boot.img file in any rom.zip that can be extracted and flashed also it's supposed to be flashed with the rest of rom.zip in one go. Blame htc for their bootloaders which prevent you from this. That's why we talk about htc's half assed bootloader unlock.
To come to an end: There are sense based roms, AOSP and AOKP based roms. Whereas AOSP and AOKP based kernels could be interchangeable, sense based kernels are only compatible to htcs sense UI. That's why you can't mix them up with all the roms out there. Sense is deeply integrated into kernel.

N5 won't boot

I got my N5 yesterday
unlocked bootloader
running TWRP
can flash and setup any rom
CAN NOT GET ANY KERNEL TO BOOT (using CM types when available, latest try was running sylentprofet minimal}
not sure what is going on, probably something small that I am missing.
tried:
faux
franco
N3o
ElementalX
Sorry if it is a simple fix. Did try to search but no real results that helped

If you're running cm look for CAF kernels.

As stated above, the problem started when you flashed, faux, franco kernel. Elementalx has a version which is compatible to CM Roms but need to read well. I heard of some people having problems after flashing franco, where another kernel wouldn't boot after franco.
Do a clean Rom installation, boot the phone with the stock CM kernel, then try to flash Chaos kernel and see how it does

thanks
why do we now have to use a particular type of kernel now?
Thank you guys for the assistance I booted my AOKP rom then flashed chaos with no issues, I knew it was something simple. :victory:

orvon.freeman said:
why do we now have to use a particular type of kernel now?
Thank you guys for the assistance I booted my AOKP rom then flashed chaos with no issues, I knew it was something simple. :victory:
Click to expand...
Click to collapse
Glad you got it working
A quick search returned this from faux. more CAF info available around:
http://forum.xda-developers.com/showpost.php?p=46098546&postcount=15393

Issue with kernel for multirom

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?

[Q&A] [MOD] MultiROM v28d

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?

[Q] MultiROM secondary ROM boot loop

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.