I'm flashing roms for a very long time, but I ran into a problem, I can not understand:
I have unlocked my bootloader.
Flashed TWRP
Formatted all the partitions in TWRP.
I have flashed AOKP nightly 02/01/2014 but whenever I trie to flash a custom kernel (tried bricked and Franco) my phone won't boot. It's stuck at the Google logo.
How come?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Caspertje19 said:
I'm flashing roms for a very long time, but I ran into a problem, I can not understand:
I have unlocked my bootloader.
Flashed TWRP
Formatted all the partitions in TWRP.
I have flashed AOKP nightly 02/01/2014 but whenever I trie to flash a custom kernel (tried bricked and Franco) my phone won't boot. It's stuck at the Google logo.
How come?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Make sure all the partitions are the correct size as well as make sure the Kernel supports the ROM. If you read the individual kernel threads and do a search, the information should be available. Its been discussed that many ROMs have switched some code in the nightlies to not being supported by some kernels while others work (such as Chaos kernel working on CM ROM while Franco kernel works stock). Depends on your preference then once you find which are supported and which are not. There is also a thread (I believe in Original Development or the other development thread) that bridges the kernel support of some to work on the newer CM based nightlies based on the CAF/nonCAF system codes that are being worked on.
Caspertje19 said:
I'm flashing roms for a very long time, but I ran into a problem, I can not understand:
I have unlocked my bootloader.
Flashed TWRP
Formatted all the partitions in TWRP.
I have flashed AOKP nightly 02/01/2014 but whenever I trie to flash a custom kernel (tried bricked and Franco) my phone won't boot. It's stuck at the Google logo.
How come?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Because you flashed a kernel that is not compatible with the rom. Re-flash the rom and then find a kernel that is compatible with AOKP.
I was coming from the nexus 4 running AOKP and they have had a poll about caf or non-caf. They decided non-caf, that's why I thought Franco kernel should work (worked on nexus 4).
But I see I have to do some searching.
I thought the decision was already made by the AOKP to use aosp kernel.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Related
So I've been flashing various roms, kernels, and radios onto my Nexus S since the release. I've never read to deeply into the exact procedure for flashing these items.
I know you are suppose to wipe device, cache, davik, ect. But then are you suppose to flash the rom, reboot the device, and then flash the kernel and radio?
What if you wiped the device and just flashed a rom without a kernel? Does the kernel you have previously take into effect or is it built into the rom?
No, Roms come with a kernel. If you don't flash a kernel you will have whatever kernel the developer uses in his/her Rom.
Sent from my Nexus S 4G using XDA Premium App
housry23 said:
No, Roms come with a kernel. If you don't flash a kernel you will have whatever kernel the developer uses in his/her Rom.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Wha? Not all ROM's come with kernels... if you flash one that does not have a kernel then you will be left with what you had before (stock).
Hey guys
I'm running SlimBean 2.8.0 ROM and when I try flash a new kernel, device not boot. Logo Google pass and there isn't nothing more. Only backlight of hardware keys is on. SlimRom's boot animation is not show. I tried a lot of kernels (Matr1x, Air, vta2...) but no one was work. I tried wipe data and then flash a new kernel - no effect. Wiped dalvik cache - no effect. I tried to make clean install of SlimRom's (without Gapps) then flash new kernel - no effect again. Before flashing each of that kernels I make a clean install of SlimRom (with its stock kernel). Now I'm using stock kernel.
I need a custom kernel for USB host mode.
Any ideas?
Make sure you are flashing a cm kernel
Sent from my Nexus S 4G using xda app-developers app
n2d551 said:
Make sure you are flashing a cm kernel
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
+1 for that. At 2.8 SlimBean merged CM kernel code meaning you have to now flash the CM kernel and not the All Others.
I'll try this. Thanks
Edit: It works! Thanks again!
So I lost my phone, got a new one, rooted using the casual root/unlock w/twrp method found on this forum http://forum.xda-developers.com/show....php?t=2332825
Is it possible to somehow improperly root/unlock without bricking? Or that I just got a bad download. I am having random reboots with just about every kernel I flash, some worse than others. I can only run the stock kernel. Running a clean 2.9 and the latest TWRP. Would it be useful to do a full wipe and "reroot/unlock"
What rom are you using and what kernels are you trying to flash?
Sent from my SCH-I535 using Tapatalk 4
Right, sorry. Liquid 2.9..tried flashing multiple builds of BMS, a few lk builds, dkp, and team kernalizer kernel. I think that's all of the available kernels for the s3
Sent from my SCH-I535 using Tapatalk 4
ThunderRootedDragon said:
Right, sorry. Liquid 2.9..tried flashing multiple builds of BMS, a few lk builds, dkp, and team kernalizer kernel. I think that's all of the available kernels for the s3
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Clean flashes, freshly installed rom after first boot with the stock kernel, I reboot and flash the new kernel and just never fee stability.
Sent from my SCH-I535 using Tapatalk 4
ThunderRootedDragon said:
Clean flashes, freshly installed rom after first boot with the stock kernel, I reboot and flash the new kernel and just never fee stability.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Well, I follow AOSP kernel development a little bit. If I were you, I'd start by flashing a kernel built within seven days of July 20th cuz it seems every two to three weeks, kernel commits render older roms useless. If you don't follow AOSP commits in the more popular rom or kernel threads then I suggest staying away from custom kernels cuz they move quickly. Custom AOSP kernels built on 8/13 won't work on older roms for example.
Edit: I got July 20th cuz LiquidSmooth was last updated on July 20th btw. Just to be clear.
Good advice. I don't follow the aosp commits but I did have the same thought and flashed an older version of BMS (I really want to give it some burn) didn't work... I'll try an older build of lk too just to see where I am.
Really hoping 4.3 somehow resolves this issue for me.
Thanks for your help.
Sent from my SCH-I535 using Tapatalk 4
ThunderRootedDragon said:
Good advice. I don't follow the aosp commits but I did have the same thought and flashed an older version of BMS (I really want to give it some burn) didn't work... I'll try an older build of lk too just to see where I am.
Really hoping 4.3 somehow resolves this issue for me.
Thanks for your help.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Hope so too. I'm trying out Slim Bean beta 2 with BMS kernel from 8/15 and it's working great performance wise. I'd even suggest trying newer 4.3 rooms (CM, Unofficial CM, PA, etc) just for a couple hours and trying your hand with a custom kernel from 8/13 or newer. Or trying a newer 4.2.2 nightly with a custom kernel. For BMS, I believe GideonX said that 7/30 is the last JB 4.2.2 kernel he's made.
How long would you say you waited before flashing the kernel? I usually flash rom, reinstall my apps, set up home screens, then flash a kernel. Maybe 20 minutes between rom and kernel flash cuz of habit.
Sent from my SCH-I535 using Tapatalk 4
Atm i have elementalx kernel installed and thinking about switching to franco when i install a new rom. I am on stock rom and will probably flash to Slimkat, will i just have to flash Rom + google apps and then elementalx/franco?
Read the op for slim. If it says to flash gapps then you'll need to do that. Then flash the kernel
Sent from my Nexus 5 using XDA Free mobile app
flashdx said:
Atm i have elementalx kernel installed and thinking about switching to franco when i install a new rom. I am on stock rom and will probably flash to Slimkat, will i just have to flash Rom + google apps and then elementalx/franco?
Click to expand...
Click to collapse
Why elementalx again? You want franco, flash that!
Sent from my Nexus 5 using Tapatalk
I have some kernels for example AK and Boeffla,but them doesn't work in Slimrom.why?I think slim is development on asop that it support these kernel.Who can tell me why?
Sent from my Oneplus One using XDA Free mobile app
I have used ak kernel on Robbie's latest build no problem.
I've never had any problems flashing other kernels
Sent from my Nexus 5 using XDA Free mobile app
if use other language for example chinese,flash AK kernel on slimrom,it will reboot again....
I am having difficulty getting Franco Kernel to work, I just get a constant boot loading screen and have to force shut down, anyone know of any issues?
Cleared cache and dalvik before and after install and am using the right version for my device.
Same here
Flashing Franco's Kernel R24 and R42 for OPO resulted in hanging boot on logo. Reflash full rom and apps fixed it. But unable to flash Franco Kernel.