Dears,
I have nexus 5 with open bootloader + Recovery clockwork-6.0.4.4 + root + MIUI V5 custom Rom
because the lag and the hate of my phone especially when Turn on 3G data, I decided to change the kernel to custom kernel
then I used the franco kernel r63 from this post
http://forum.xda-developers.com/google-nexus-5/orig-development/kernel-franco-kernel-r53-t2508284
I used the "franco.Kernel updater Free App" to download the latest update and flash it
but after that the nuxes 5 didn't work, still stock on the logo of Rom !!
I tried to install the stock kernel from this link boot-4.4.1 by "fastboot flash boot" command but still same problem
and also I tried to install the Trinity Kernel "T5-4.4.2-B10" by flashboot command and still same problem,
and tried to re flash the Zip file of MUIU Rom, but nothing new, same problem stock on the logo picture of Rom when start !
any help please ?
I want to install the franco kernel with my MIUI Rom, even if the solution will remove all my App & data no problem !
none of those kernels are miui compatible. what you have to do is either flash the miui kernel(or compatible) or just reflash miui dirty(don't wipe anything).
Or just flash away from MIUI to get rid of your lag problem.
simms22 said:
none of those kernels are miui compatible. what you have to do is either flash the miui kernel(or compatible) or just reflash miui dirty(don't wipe anything).
Click to expand...
Click to collapse
simms22
Many thanks for you, I change the kernel and used this "Silean Kernel Nexus 5", which is compatible with MIUI rom, and My Nexus 5 go a way from last problem ! Thanks again. :good:
SilkyJohnson said:
Or just flash away from MIUI to get rid of your lag problem.
Click to expand...
Click to collapse
Thanks for your Idea, this is my first time with this rom and I found it Good if the new kernel will solve these two problems ! I hope or I will get new Rom ! do you recommend any new good Rom ?!
Nuxes 5
Sent from my Nexus 5
Related
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
I was flashing air kernel with cwm and succeded, but when i rebooted afrer flashing, the phone won't get to Google logo. I flashed Blue color + 65 fps HELP PLEASE
Nexus S, stock jelly bean 4.1.2, rooted, tried to flash air kernel..
Please someone reply. After the Google logo, the phone just goes blank... tried a battery pull and nothing..
matejilic said:
I was flashing air kernel with cwm and succeded, but when i rebooted afrer flashing, the phone won't get to Google logo. I flashed Blue color + 65 fps HELP PLEASE
Nexus S, stock jelly bean 4.1.2, rooted, tried to flash air kernel..
Please someone reply. After the Google logo, the phone just goes blank... tried a battery pull and nothing..
Click to expand...
Click to collapse
can u still go into recovery ??
power + volume up
ahmadalraii said:
can u still go into recovery ??
power + volume up
Click to expand...
Click to collapse
yes, i can. I tried to flash Matr1x kernel, reflash Air and flash AOKP milestone 1, situation is the same, it shows only the google logo, after that i can see nothing, blank screen..
did u try a whole new combo..
try hellybean rom 4.2 with airkernel..
not all roms works with all kernels some roms have thier own kernels like cm
is your problem that u want this specific rom to boot and u have tried many kernels and stuck in bootloops
or ur phone is not working with any rom ? and any kernel >?
be carefull if flashed a jelly bean rom to flash a jellybean kernel ..or hust try to boot with the provided kernel with the zip rom
Wipe data in CWM. Make a backup first.
Factory reset and wipe data,cache before trying it again.
Sent from my Nexus S
ahmadalraii said:
did u try a whole new combo..
try hellybean rom 4.2 with airkernel..
not all roms works with all kernels some roms have thier own kernels like cm
is your problem that u want this specific rom to boot and u have tried many kernels and stuck in bootloops
or ur phone is not working with any rom ? and any kernel >?
be carefull if flashed a jelly bean rom to flash a jellybean kernel ..or hust try to boot with the provided kernel with the zip rom
Click to expand...
Click to collapse
my phone worked with stock. Then i tried to flash air kernel to stock rom to increase performance, but i got stock in bootloop i guess (wont go past the google logo..)
seibott said:
Factory reset and wipe data,cache before trying it again.
Sent from my Nexus S
Click to expand...
Click to collapse
tried multiple cache wipes/ dalvik cache wipes and factory resets.. i guess i'll try to flash stock image from google in hope to fix it...
i managed to flash cm 10 on my nexus s and it fixed all the problems. thank you for your help guys, cheers!
matejilic said:
i managed to flash cm 10 on my nexus s and it fixed all the problems. thank you for your help guys, cheers!
Click to expand...
Click to collapse
cheers ...:laugh:
Hi everyone, i'm running viper 2.4.1 with hboot 1.14 on my phone right now. However, when i tried to flash other custom kernels , i have a weird problem with my phone as it can't re-connect to wifi ( i set my phone to turn off wifi when screen is off). It's always says error and i have to reboot my phone to get it work again. Here what i've did
- flash elementalX 3.2 kernel=> wifi problem=> re-flashed kernel& boot.img=> still have wifi problem
- switch to beatmode 4.4 kernel=> same problem=> reflash kernel + boot.img from elementalX ( beatmode kernel doesn't have boot.img)==> problem still there
- flash stock kernel=> doesn't work, i guess i have to flash stock boot.img but i don't know where to find it
- fresh re-flash viper rom + beatmode kernel/elemenatalX=> wifi problem
- re-flash viper rom only ( with stock kernel comes along with it) => everything works perfectly
===> so i'm stucked right now. i tried to search in kernels thread, viper threads but there is no answers. Can someone help me to solve this problem?
P/s: i always wipe cache/davik cache before and after i flashed things
The kernel is the boot.img
Are you fastbooting the img
WiFi issues almost always are caused by the boot img
Try and fastboot the boot.img from the kernels that you want to use...and make sure their compatible with the Rom you choose
Sent from my HTC One X using Tapatalk 2
Viper Tom Is compatible with elementalx /beatmode kernels I believe. I also always flash boot.img (comes along with kernel) in fastboot mode.
tritran18518 said:
Viper Tom Is compatible with elementalx /beatmode kernels I believe. I also always flash boot.img (comes along with kernel) in fastboot mode.
Click to expand...
Click to collapse
You r correct sir, flash boot..img is an option with elemental jb 1.3 version plus other goodies from flar, great battery life with viper Rom and that kernel
As I said: I was wandering if it is possibile to change kernel, I tried this one, installed with aroma, but my Sensation is stuck in a bootloop.
I'm S-on, I tried to flash either with and without the 4ext smart flash with the same result.
Anyone has a solution?
Fulvio93 said:
As I said: I was wandering if it is possibile to change kernel, I tried this one, installed with aroma, but my Sensation is stuck in a bootloop.
I'm S-on, I tried to flash either with and without the 4ext smart flash with the same result.
Anyone has a solution?
Click to expand...
Click to collapse
flash the boot.img of the rom manually
see here how
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1step)
otherwise flash another kernel
which kernel did you use?
rzr86 said:
flash the boot.img of the rom manually
see here how
http://forum.xda-developers.com/showthread.php?t=1631861 (only extra 1step)
otherwise flash another kernel
which kernel did you use?
Click to expand...
Click to collapse
Sorry! I forgot to past the link and then I had to wait five minutes to edit my post and, well, I forgot again.
This is the kernel: http://forum.xda-developers.com/showthread.php?t=1216197 I don't really need it but I would have tried some oc and the sweep2wake function and stuff, so, any other kernel (or even the rom one, if it's possible to set it) is the same to me.
Just to tell you: I flashed Jellybam after a full wipe, and it was working, then flashed the kernel, then, when I got stuck in the bootloop I flashed Jellybam again without wiping, right now all works properly.
Fulvio93 said:
Sorry! I forgot to past the link and then I had to wait five minutes to edit my post and, well, I forgot again.
This is the kernel: http://forum.xda-developers.com/showthread.php?t=1216197 I don't really need it but I would have tried some oc and the sweep2wake function and stuff, so, any other kernel (or even the rom one, if it's possible to set it) is the same to me.
Just to tell you: I flashed Jellybam after a full wipe, and it was working, then flashed the kernel, then, when I got stuck in the bootloop I flashed Jellybam again without wiping, right now all works properly.
Click to expand...
Click to collapse
That kernel is NOT designed for AOSP Jelly Bean ROMs like JellyBAM. That kernel is designed for Sense Ice Cream Sandwich ROMs, so it's to be expected that your phone won't boot after flashing that over JellyBAM. If you want a kernel to use with JellyBAM that has all the features that you just mentioned (Sweep2Wake, OC, etc.) then try my kernel (Sultan kernel). The thread is here: http://forum.xda-developers.com/showthread.php?t=2035897
android1234567 said:
That kernel is NOT designed for AOSP Jelly Bean ROMs like JellyBAM. That kernel is designed for Sense Ice Cream Sandwich ROMs, so it's to be expected that your phone won't boot after flashing that over JellyBAM. If you want a kernel to use with JellyBAM that has all the features that you just mentioned (Sweep2Wake, OC, etc.) then try my kernel (Sultan kernel). The thread is here: http://forum.xda-developers.com/showthread.php?t=2035897
Click to expand...
Click to collapse
Yeah well, I was looking at the title of that kernel thread while I realized which was the problem, I'm glad to tell you that I flashed your kernel last night (I'm Italian) and after a whole day using it I have to say that I really like it (even if I've to settle with all the differences between the governors and the best way to set them with aroma).
Thank you!
Hello.
I currently have my pico with stock rom, with sense 3.5. and i'm tryin to flash a new rom, but every time i try to flash one from this thread ( http://forum.xda-developers.com/showthread.php?t=1754876 ) i got stuck on htc logo screen. and i cant get passed it... i've wiped everything, reflashed kernel, reflashed stock, but still cant get it to work. maybe these kernels arent for stock roms, if they're not, can you point some kernels that work on stock?
thanks in advance.
Stock rom should have stock kernel too.
Flash the gingerbread kernels.. they must work. PS: The ROM.zip already contain kernels that get installed when the zip is flashed.
Red Devil said:
Flash the gingerbread kernels.. they must work. PS: The ROM.zip already contain kernels that get installed when the zip is flashed.
Click to expand...
Click to collapse
where can i find those gingerbread kernels? so if they're inside the "rom.zip" is it possible to "extract" them to a flashable zip? only the kernel withouth the rom itself...?
Gingerbread kernels are in the Index of all kernels..
From the ROM.zip if you want to extract them then just extract the boot.img normally and also extract the modules from the zip .. in /system/lib..
In fastboot mode flash boot.img via :
Code:
fastboot flash boot boot.img
and
then via adb push the modules. I suggest you search a bit and find some answers yourself . Its easier that way cause these questions have been answered millions and millions of times. So use the search function
i've searched, and believe me when i say that i havnt found anything about this... all the kernels i go for, on the thread only talks about the kernel itself and not the roms compatible... and i've tried that method and got stuck on htc green logo... thanks for answering
these kernels work on stock rom:
1- cranium kernel
2- ateeq kernel
3- garuda's kernel
search them in the development thread I hope you'll find them.
i've tried all those kernels... one by one and never got passed the htc green logo... always get stuck there... i tried flashing trough fastboot and trough recovery... nothing works... any other suggetions?
try to flash ateeq rom then ateeq kernel..it works for me.
but i dont want to have ateeq rom, i want to stay with my stock rom, but change the kernel... only that. but thats for answering. i'm getting used to the idea that i cant be changed (the stock kernel).
thanks
Need urgent help
i had rooted my pico months back and was on different custom roms......now i want 2 get back to the stock rom which i have downloaded Odexed Stock ROM Flashable Zip (With Link2SD Support)(Revision 3)(http://forum.xda-developers.com/showpost.php?p=40385554&postcount=76) and i have flashed this rom 5 - 10 times and everytime i reboot after flashing the rom.....i am stuck on htc boot logo.....can u plssssss help