Database Info

NS 9020t - problem flashing marmite_v4.4 kernel to miui 2.9.7

I'm having a problem flashing marmite 4.4 to the newest miui build (2.9.7).
Basically in cwm recovery and flashed the kernel.
Will say "ununderstandable message 3" and "lid is licked"
Reboot the device and it will get stuck on the miui boot screen.
Tried installing both the "stock OTA" and "All other ROM" version of marmite.
Same message comes up.
Already tried performing a full wipe (actual full restore, format system, format boot), reload the ROM.
Tried wipe cache and dalvic (even though it is not needed)
Just wondering if there is something incompatible or not.
I was able to flash air kernel without issues.
I haven't tried an older version of marmite yet, but will try later.
I'm not blaming marmite, it could be miui as well, or it could be just me.
I'm certain I'm flashing correctly.
I read bedalus' marmite post and saw 2 others with this issue (not same version of kernel or ROM).
The suggestion was that they didn't use the correct kernel for ROM.
I would assume miui would not be categorized as "stock OTA", so I tried "all other ROM" version first"
Am I doing something wrong?

There is a new version 4.5 the message you get I believe is like a joke. It does show however that the installation was successful.
Never experienced boot loops flashing his kernels.
Sent from my Nexus S

Actually, I downloaded that one just now to try and same issue.
It will just stall at the miui (ROM) boot screen.
I am trying some other stuff right now as well.
Really want to use this kernel. :good:
I'll report back later.
Thanks for the help.

Good luck. His kernel offers great speed and stability!
Sent from my Nexus S

For marmite 4.5, did a full wipe again, even formatted the SD partition.
So flashed miui 2.9.7.
Booted to the ROM.
Made sure things seem normal in the ROM.
Restarted just to be sure.
Boot back to recovery.
Flashed marmite 4.5
And it is stuck on the miui loading screen again.
Only thing I haven't tried this time is to fix permissions. (didn't wipe cache or dalvic either)
I'll try it again. :laugh:

Since I formatted the SD partition, it should rule out that it was something on the SD card right?
It's time consuming to copy things back to the NS.
I'll try an older version of marmite afterwards and then an older version of miui.
It should tell me what is causing the lock up by then. I think. :silly:
.... yes I have a lot of time ....

I forgot to mention one thing.
I'm flashing the official Chinese version of miui 2.9.7.
Wonder if that's the cause.
I guess I will download the US or UK version to try as well.

Well if your phone boots with original kernel, it must be kernel related. There's no need to wipe anything before flashing a kernel. Just flash it. It could be that the Chinese rom is different from the others, but that's a guess I'm no expert on compatability.
Sent from my Nexus S

kwibis said:
Well if your phone boots with original kernel, it must be kernel related. There's no need to wipe anything before flashing a kernel. Just flash it. It could be that the Chinese rom is different from the others, but that's a guess I'm no expert on compatability.
Sent from my Nexus S
Click to expand...
Click to collapse
Took some time to test, but sort of found my answer.
It's the official Chinese miui that's causing the issue.
Well at least some component in the ROM.
I tested with the MIUI UK (miuiandroid) version 2.9.7 and it installed like a charm.
Before flashing the UK version, I tested with earlier versions of marmite (4.3 and 3.5) on the Chinese 2.9.7.
All failed at the ROM boot screen.
I should check with the miuiandroid team and see what they changed that made it different.
When I was testing I did a full wipe, installed ROM, booted ROM, boot to recovery and flashed the kernel.
I didn't even wipe cache or dalvic (which is not needed anyways).
I had to do a full wipe because the ROM just wouldn't boot back up afterwards.
I'm tempted to test with an earlier version of the official Chinese miui and see if it makes any difference.
... too much time and/or no life ... :laugh:

Lol, well it's good you found your answer So its not a waste lf time as you learn from this
Sent from my Nexus S

If you flash air kernel, and if it worked, I guess marmite's boot.img type can cause a problem.
Sent from my Nexus S using Tapatalk 2

Articudos said:
If you flash air kernel, and if it worked, I guess marmite's boot.img type can cause a problem.
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Not sure what the boot.img type is, but I'll look it up. Thanks.
I posted on miuiandroid forums and someone replied saying that the Chinese version is odexed and not busyboxed.
UK and US version is definitely deodexed, I downloaded them and checked. I haven't found out how to check busybox.
I have a few choices.
1. I can use the UK or US version, since I was able to flash marmite on them... easy way out.
2. Find out how to deodex the ROM and, I guess, how to add busybox (?)... I get to learn more stuff.
3. Use a way faster ROM (eg. Paranoid Android - great ROM by the way!) and flash marmite on it as well... but really want to use miui again.
Thanks guys for your help though. Really appreciate the information. :good:

Glad you found a solution

[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.

[UNOFFICIAL][ALPHA] MultiROM v32

For those of you who don't know, MultiROM is a mod that lets you boot an arbitrary number of ROMs at once. It contains three parts: a modded version of the TWRP recovery, the MultiROM bootloader, and a kernel installed on the primary ROM that has support for kexec-hardboot. As far as I know, the only kernel for Moto X with kexec-hardboot support is tdhite's TDHK Kernel. If you have a ROM that is based on AOSP 4.4.4-5.0.x, please install this kernel then try using this build of MultiROM. The recovery image is tested and seems to be working; however, I do not have an AOSP ROM right now, so you are flashing at your own risk. Don't hold me responsible for bricking, breaking, or face-eating spaghetti monsters that arise from using this mod.
Installing
Connect your device to your computer via USB and run
Code:
adb reboot bootloader
in a terminal/cmd. Wait for the device to reboot to the bootloader, then run (as root/administrator)
Code:
fastboot flash recovery recovery.img
in the folder that you downloaded recovery.img to.
To install the MultiROM bootloader (after installing a kexec-hardboot kernel to your primary ROM!) upload multirom.zip to your device via adb push, mounting the device onto your computer, downloading the file directly, etc. then reboot to recovery and flash.
You can uninstall by flashing multirom_uninstaller.zip in TWRP (you will still have the modded recovery, just flash your choice of recovery to uninstall it).
Submitting bugs
If you experience bugs, make a post reply with this format:
Primary ROM: (provide name & link if possible)
Primary Kernel: (provide name & link if possible)
Secondary ROMs: (list all of them, provide links if possible)
Pastebin link to /sdcard/multirom/error.txt : (It might not exist, check anyway)
Pastebin link to /proc/last_kmsg : (this file lasts 1 reboot, access it from recovery immediately after the bug)
Other notes:
Download
https://www.dropbox.com/sh/rixkydvznnwjtd7/AAA5C6NLyW_RTNqg7_CWjQcva?dl=0
Credits
MultiROM team
TWRP team
kladd for his GitHub source (I made modifications to support MultiROM)
Makalak and Elimin8er on the #multirom irc channel for helping me build MultiROM
Linus Torvalds
Many other people that did work behind the scenes that I probably don't even know of
And of course, Praise DuARTe

Reserved

Reserved II

Reserved III
Last one, I promise!

OK so I tried this out. I do have multirom experience with my Nexus 4. I was in CM12.1. With tdhite's 1-11-15 kernel which according to his changelog has kexec support. Installation of multirom recovery went fine. Rebooted recovery. Installed multirom.zip went fine. I installed another cm12.1 ROM as a secondary ROM to test and it installed fine. Rebooted. In the multirom boot I chose the secondary ROM, it failed to boot saying primary ROM kernel did not have kexec support. So I'm assuming either the kernel doesn't have full kexec support for multirom or something else is borked. I'll ask about kexec support in his kernel thread. Any other thoughts?

@tdhite can help in patching kexec for his kernel to get the multi rom fully working

I have fixed kexec on the kernel
U applied wrong patch on it

Brawn_Sg said:
I have fixed kexec on the kernel
U applied wrong patch on it
Click to expand...
Click to collapse
Link to fixed kernel?

perfoliate said:
Link to fixed kernel?
Click to expand...
Click to collapse
Multirom is not far
I have made the kernel and I will make my separate multirom and twrp
So wait for today
Everything of mine will be separate

If anybody'd like to help out on the kernel/patch, as I might not get much time to work on it for the next few weeks, I can put everything on github and post it here.

seems to be running awesomely amazing on my phone good work yall

JCroffut said:
seems to be running awesomely amazing on my phone good work yall
Click to expand...
Click to collapse
Which kernel did you use?
Tdhk-24-05?

Yea the newest tdhk. It seems he fixed kexec

@JCroffut - Are you using "stock" as the main ROM with the recent "LP" kernel?

JCroffut said:
Yea the newest tdhk. It seems he fixed kexec
Click to expand...
Click to collapse
Thanks for the heads up. I'm going to try out this kernel tomorrow and if it works fine I'm going to talk with tdhk to see if he can help me out with making a general patch to try and merge into the cm kernel. Sorry I haven't done much here lately, finals are soon and I'm juggling 3 big projects. Again thanks for the heads up.
Sent from my Moto X using XDA Forums

Right now im only using 1 rom, but last night i had Carbon as my primary, with tdhk, and I had Paranoid as a secondary, again with tdhk. Everything ran fine.

JCroffut said:
Right now im only using 1 rom, but last night i had Carbon as my primary, with tdhk, and I had Paranoid as a secondary, again with tdhk. Everything ran fine.
Click to expand...
Click to collapse
Thanks for the info - I was hoping to keep stock as my Primary.

JCroffut said:
Right now im only using 1 rom, but last night i had Carbon as my primary, with tdhk, and I had Paranoid as a secondary, again with tdhk. Everything ran fine.
Click to expand...
Click to collapse
can you list out all the steps you went through? i tried this setup but multirom keeps saying that the kernel doesn't support kexec-hardboot (can confirm carbon rom is running tdhk 05-24).

thejrcrafter2 said:
can you list out all the steps you went through? i tried this setup but multirom keeps saying that the kernel doesn't support kexec-hardboot (can confirm carbon rom is running tdhk 05-24).
Click to expand...
Click to collapse
Same results here. Getting same error.

Pk I return to this project
Someone who knows how to compile kernel
Actually I don't have build machine
Or someone who has ubuntu
I will provide him with my new kexec kernel source
Tell me anybody ?

Can't boot into fresh custom rom anymore -> keeps booting recovery (TWRP)

I was running OdexLite V4.2 but I was having some issues. I thought this was caused because I flashed it over my Marshmallow rom. So I flashed the latest available S6 edge official firmware from sammobile (G925FXXU5EQI6_G925FPHN5EQI2_PHN) and after that I fully booted the phone and shut it down. Then through Odin I flashed TWRP (twrp-3.1.1-0-zerolte.img.tar) and tried to install OdexLite again. I tried V4.2, V4.1, V4.0 but all of them kept rebooting me back into recovery. No matter what I tried. I haven't tried another ROM yet, tried to download NOBLE NOUGAT S8 PORT 5.1 but I don't have an Telegram account. I can't seem to find a download link without having to use my phone number.
What can be the cause of my phone to keep rebooting into the recovery? I already used V4.2 (till this morning) and it always worked. I redownloaded the file (V4.2 and TWRP) but that didn't change anything. Then I flashed back to stock Marshmallow like before, fully booted the system, shut down and install TWRP again. And then tried to flash V4.2 (and after that V4.1 and V4.0) but still my phone keeps rebooting into recovery after finishing the ROM. I tried various options in the aroma installer (stock choices and the same choices I made the first time when it worked)
I did a full erase (erase everything) and then copy the files through TWRP to the phone and flash it. And erased everything and used an OTG stick with the files to flash. I tried factory reset, wipe cache, etc. after the phone reboots back into recovery after the installation.
What's going wrong?? Please help me I don't know what else to try...

No, only the ROM files

rifek4 said:
That's maybe why...
Click to expand...
Click to collapse
I also replied to you in the other topic, I didn't had to do it before and the install instruction don't mention to install root either. But today I found flashing root can be the solution (while it wasn't mentioned in the startpost)
But V4.2.3 fixes the recovery loop. I'm now going to try V4.1 and/or V4.0 with flashinh magisk afterwards to see if that solves the problem.
Links to the solution page (page 100)
https://forum.xda-developers.com/ga...lite-rom-920f-920i-925f-925i-t3550706/page100
But thanks anyhow, I didn't know that I had to flash that. I just followed the instructions to be sure I didn't skip anything important :good::good:

rifek4 said:
Because that isn't nothing new and every one user who flashing custom ROM's must know that every time after flash ROM we must flash ROOT
Click to expand...
Click to collapse
I have flashed a_lot_of_roms on many different phones and I almost never had to do this. The times I had to do this, it was always instructed in the install routine I had to. Never had a loop to recovery before. I guess it was luck? Especially because the exact same rom worked before without flashing root. But this was a first for me and I'm flashing roms since the MDA Compact
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But I'm happy I've learned this today, wished I learned this already yesterday :silly: missed my sleep this night
(Nederlandse Pool?)

rifek4 said:
Yes, same for me, I modding phone since 2006/7 year then we did mainly Sony Ericsson's and Nokia modding, later was more... If you Google my nick names "Leito07" with "Sony", "Nokia" word then you will see my first mods, sometimes there even are files from almost 10 years ago, look HERE: http://www.topsony.com/forum/showthread.php/18057-SquaSh-WBXML-Acoustic-by-Leito07
But on currently models like S6 with custom 7.0 FW for example we always must flash ROOT to patch boot image, otherwise phone will give us bootloop...
P.S.
Yep, you? Nederlandse Dutch misschien? :laugh:
Click to expand...
Click to collapse
Nice! Haha
P.S.
Nee geen probleem, enkel nieuwsgierig haha. Ik gewoon Hollandse Hollander. Geen Turkse, geen Poolse, gewoon lekker standaard :laugh:

rifek4 said:
Jaaaa... Zo standaard niks... Ik weet dat je alle racisten bent, maar we praten niet over het hier...
Click to expand...
Click to collapse
Haha uiteraard. Nee gewoon een brave Nederlander. Wel fan van Poolse vrouwen

rifek4 said:
Because that isn't nothing new and every one user who flashing custom ROM's must know that every time after flash ROM we must flash ROOT
Click to expand...
Click to collapse
That's false. You don't need to flash root, only roms that need that, like Noble.

Markos said:
I was running OdexLite V4.2 but I was having some issues. I thought this was caused because I flashed it over my Marshmallow rom. So I flashed the latest available S6 edge official firmware from sammobile (G925FXXU5EQI6_G925FPHN5EQI2_PHN) and after that I fully booted the phone and shut it down. Then through Odin I flashed TWRP (twrp-3.1.1-0-zerolte.img.tar) and tried to install OdexLite again. I tried V4.2, V4.1, V4.0 but all of them kept rebooting me back into recovery. No matter what I tried. I haven't tried another ROM yet, tried to download NOBLE NOUGAT S8 PORT 5.1 but I don't have an Telegram account. I can't seem to find a download link without having to use my phone number.
What can be the cause of my phone to keep rebooting into the recovery? I already used V4.2 (till this morning) and it always worked. I redownloaded the file (V4.2 and TWRP) but that didn't change anything. Then I flashed back to stock Marshmallow like before, fully booted the system, shut down and install TWRP again. And then tried to flash V4.2 (and after that V4.1 and V4.0) but still my phone keeps rebooting into recovery after finishing the ROM. I tried various options in the aroma installer (stock choices and the same choices I made the first time when it worked)
I did a full erase (erase everything) and then copy the files through TWRP to the phone and flash it. And erased everything and used an OTG stick with the files to flash. I tried factory reset, wipe cache, etc. after the phone reboots back into recovery after the installation.
What's going wrong?? Please help me I don't know what else to try...
Click to expand...
Click to collapse
Make sure the ROM your flashing is ROOTED, if not ROOT is yourself and try again.

phone can't boot after flash custom kernel

I have a 6x phone (hi6250 hl40 version).
I retryed compire kernel from source before,for run frida(because default kernel not enable "PTRACE" ).
It running well ,just wifi not work.
Today I want retry again
I compired kernel from a diferent source
After flash kernel ,my phone even can't boot into bootloader.
Is any way to solve it without wipe data?
Thanks

solution here

Bro, could you please upload the flashed kernel? I tried several days but all failed. I really need this. Thanks!