I haven't even booted the device yet, but would like to make slight modifications.
I have to stay "stock" / non-root because of apps I use for work, but can do roms & kernels.
I intend on booting up, installing Pie / latest updates, etc....
I want to use AOSPex & ElementalX right off the batt.
So should I:.
1. Flash AOSPex & set everything up, then flash ElementalX afterwards?
Or.
2. Flash AOSPex + ElementalX together at boot?
Ph0z3 said:
I haven't even booted the device yet, but would like to make slight modifications.
I have to stay "stock" / non-root because of apps I use for work, but can do roms & kernels.
I intend on booting up, installing Pie / latest updates, etc....
I want to use AOSPex & ElementalX right off the batt.
So should I:.
1. Flash AOSPex & set everything up, then flash ElementalX afterwards?
Or.
2. Flash AOSPex + ElementalX together at boot?
Click to expand...
Click to collapse
Shouldn't be a problem flashing kernel straight after the rom and before first boot. Though worst case scenario just reflash the rom zip, boot to system, reboot to recovery then flash the kernel
cd993 said:
Shouldn't be a problem flashing kernel straight after the rom and before first boot. Though worst case scenario just reflash the rom zip, boot to system, reboot to recovery then flash the kernel
Click to expand...
Click to collapse
Right on. Thank you.
Related
Hey guys,
I'm new to the Xperia Arc development and need some help with installing a custom rom. I've done quite a bit of reading but still can't figure out what is wrong and why it's simply not working.
So from what I gathered the steps to ensure a successful flash are:
Firstly flash a stock rom via flashtool ie LT18i_4.1.B.0.587.ftf
flash LT18i_4.1.A.0.562_Kernel > root the device > flash back to LT15a_4.1.B.0.587_Kernel
Then now that the device is rooted, I need to install a recovery such as CWM via RecoverX
So, so far so good as I can access CWM, stock rom works fine as well
So then next step is to unlock the bootloader
pretty sure this worked, as when i tried to unlock it again, it said it failed as it was already unlocked
Now flash a custom kernel, in this case i flashed the 146 FXP CM kernel
This also seemed successful as I was presented with a custom splash screen
So then after custom kernel is installed I enter recovery, wipe the cache and reset factory settings, format the data system and cache as well as wiping the dalvik and battery stats.
After, I installed the custom rom zip file, in this case it was aokp_anzu-ota-eng.kxp_build5 and then google apps and then reboot.
So my problems begin here.
My phone seems to be stuck in the boot process (sometimes), on the "initiating swagger" splash screen and it goes crazy. I've tried flashing this rom with other kernels (fusion 3.9) and sometimes it actually loads up into the rom. But the rom is extremely laggy, applications freeze and close and the wifi never works
So my question is, is there any steps or procedures that I am missing, not doing right or in the correct order?
I don't think it's any hardware issues as wifi works in the stock rom, and it's fairly smooth and fluid.
Also, is there a better way to flash roms so that I don't need to do this entire process of flashing a stock rom, rooting, unlocking bootloader, installing recovery every time I want to flash a new rom? And when I flash a custom kernel first, then flash a custom rom that has a kernel inbuilt (cm10) does the custom rom's kernel replace the one i just flashed, reason for asking is that the instructions say to flash the custom kernels and then the roms, but yeh just hasn't been working for me so not really sure how to do what.
I'd really appreciated any help or insight!
Thanks
http://forum.xda-developers.com/showthread.php?p=18445331#post18445331
XperienceD said:
http://forum.xda-developers.com/showthread.php?p=18445331#post18445331
Click to expand...
Click to collapse
Thanks! I've read your guide (what I based my flashing on) and it seems consistent with what I have done, on the surface of it anyway. If you think I missed or overlooked something, would it be possible to point it out?
If your boot loader is unlocked it's as simple as this...
1. Flash kernel
2. Wipe cache etc
3. Install ROM
...I always reboot before installing anything else as I've found it can break the installation of the ROM.
XperienceD said:
If your boot loader is unlocked it's as simple as this...
1. Flash kernel
2. Wipe cache etc
3. Install ROM
...I always reboot before installing anything else as I've found it can break the installation of the ROM.
Click to expand...
Click to collapse
As ExpirienceD says,just one more thing flash kernel modules if you need to.
So:
1.Flash kernel
2.Full wipe data/cach...etc...
3.Flash ROM
4.Flash kernel modules
Sent from my LT15i using xda premium
Hi,
I am considering to flash ElementalX kernel and CleanRom on my stock nexus 7 2013 wifi. Is it correct if the steps I take are:
1. Rooted with Toolkit (i. unlock bootloader and ii. root?)
2. Flash CleanRom
3. Flash Stock kernel (is this step necessary?)
4. Flash ElementalX
Please let me know if there are other steps or things that I need to be aware. Thanks!
For step one you have to unlock boot loader in order to root. You also need to flash a custom recovery such as twrp or clockworkmod.
Also step 3 is unnecessary. After you flash cleanrom, you should just flash ElememtalX. Have fun
Sent from my Nexus 7
The toolkit will do it for you, I recommend TWRP recovery.
After that just flash the kernel.
Remember always to follow instructions.
Hi, i've got a total noob question about flashing the kernel. I've already unlocked, rooted and installed a custom rom on my Nexus (CM11) and i was just about to install the Glitch kernel for it. My question is: can i change the settings of the glitch kernel later? I mean if i choose now to overclock my cpu/gpu or underclock it, can i change it later without going into recovery and flashing the kernel again? It would be a bit of a chore to change everything all the time just to listen longer to music, or play some games at better fps... (battery vs performance)
And do i have to wipe the device before installing the kernel?
EDIT:
Ok, so i've tried to flash my kernel, but it just won't work. Always locks on boot, and i have to restore back to stock and try again. These are the steps i take:
1. install CM11 (20140324 nightly-flo build)
2. Install gapps
3. install kernel (glitch, bulletproof, elemental x - i always choose newest android 4.4.1 build)
4. brick
It doesn't matter if i go wild and choose some crazy oc and undervolting, or just as close as possible to stock (with some tweaks) it always ends the same. Light blue screen with green stripes, or it won't boot at all.
any suggestions?
DoczuPL said:
Hi, i've got a total noob question about flashing the kernel. I've already unlocked, rooted and installed a custom rom on my Nexus (CM11) and i was just about to install the Glitch kernel for it. My question is: can i change the settings of the glitch kernel later? I mean if i choose now to overclock my cpu/gpu or underclock it, can i change it later without going into recovery and flashing the kernel again? It would be a bit of a chore to change everything all the time just to listen longer to music, or play some games at better fps... (battery vs performance)
And do i have to wipe the device before installing the kernel?
EDIT:
Ok, so i've tried to flash my kernel, but it just won't work. Always locks on boot, and i have to restore back to stock and try again. These are the steps i take:
1. install CM11 (20140324 nightly-flo build)
2. Install gapps
3. install kernel (glitch, bulletproof, elemental x - i always choose newest android 4.4.1 build)
4. brick
It doesn't matter if i go wild and choose some crazy oc and undervolting, or just as close as possible to stock (with some tweaks) it always ends the same. Light blue screen with green stripes, or it won't boot at all.
any suggestions?
Click to expand...
Click to collapse
That means you're flashing the incorrect version of the kernel, from now on if you are flashing a rom see if its CAF-based or AOSP-based, for example CM is CAF-based, so you'll need to flash the correct version of the kernel, look in the kernel threads for the CAF kernel download, I know that Glitch and ElementalX have kernel compatible for CAF -based roms
DoczuPL said:
Hi, i've got a total noob question about flashing the kernel. I've already unlocked, rooted and installed a custom rom on my Nexus (CM11) and i was just about to install the Glitch kernel for it. My question is: can i change the settings of the glitch kernel later? I mean if i choose now to overclock my cpu/gpu or underclock it, can i change it later without going into recovery and flashing the kernel again? It would be a bit of a chore to change everything all the time just to listen longer to music, or play some games at better fps... (battery vs performance)
And do i have to wipe the device before installing the kernel?
EDIT:
Ok, so i've tried to flash my kernel, but it just won't work. Always locks on boot, and i have to restore back to stock and try again. These are the steps i take:
1. install CM11 (20140324 nightly-flo build)
2. Install gapps
3. install kernel (glitch, bulletproof, elemental x - i always choose newest android 4.4.1 build)
4. brick
It doesn't matter if i go wild and choose some crazy oc and undervolting, or just as close as possible to stock (with some tweaks) it always ends the same. Light blue screen with green stripes, or it won't boot at all.
any suggestions?
Click to expand...
Click to collapse
ElementalX kernels newest build is 4.4.2 not 4.4.1 and also a good tip stated above to see if you need a CAF of AOSP kernel.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Thanks for the advice, i'll try to flash it again when i'm back home. Cheers guys!
Which one should you use?
What are the benefits?
Security concerns?
Can I install a kernel without reflashing OS?
Used my T now for some days rooted with supersu and using xposed, but would like to tweak the performance and battery life some more.
Cheers.
Kernels tend to work differently depending on your individual setup. I recommend trying each one you like for a week so it can settle in. Flash in twrp and wipe only the caches. Your OS will be fine.
In terms of security I would use kernels that are frequently updated and maybe are always upstream synced. I would dirty flash the OS or the stock kernel at least before changing custom kernels as they tend to have unknown bugs when dirty flashing custom kernel over custom kernel.
The benefits are that you can choose whether to limit performance for more battery life or to go beast mode with full power but by sacrificing battery life. It simply gives you more advanced control over it.
Thanks for the replies!
Installed Blue_spark kernel and tweaked the clockspeed some. Works like a charm, I guess OTA updates are out of question?
Would agree mostly with the above. But I tried dirty flashing FreedomOS Rom once, and that was a bootloop. Dirty flashing with OnePlus isn't like HTC 10/11 Roms/Devs. They always work no issues when dirty flashing.
You could always flash the stock boot.img in TWRP, Select flash Image, select the boot.img, and the boot partition to flash. You will lose root though. So you need to install Magisk, have that handy as well. And, then try another Kernel.
I love custom roms however my wifi alway quits on any roms other than oxygen based roms. It works for the initial setup but after first reboot it never works. Ideas anyone?
What kernel are you using?
se7ensde said:
What kernel are you using?
Click to expand...
Click to collapse
I'm using stock kernel now with oxygen os. When trying custom rom it always with the included kernel. I've tried a few like phoenix, liquid,and a few others. Any ideas?
mauserruger said:
I'm using stock kernel now with oxygen os. When trying custom rom it always with the included kernel. I've tried a few like phoenix, liquid,and a few others. Any ideas?
Click to expand...
Click to collapse
Have the same problem
Sounds like a radio problem, are you using the correct firmware? Though project Phoenix packages the firmware in, it might work better if you do a complete format of your phone.
Format all data (after backing up essential files)
Install firmware (most roms are on ob3)
Install rom
Install kernel (flash kernel recommended)
Install gapps (official are out now)
Boot and configure
Reboot to recovery, flash magisk
preference said:
Sounds like a radio problem, are you using the correct firmware? Though project Phoenix packages the firmware in, it might work better if you do a complete format of your phone.
Format all data (after backing up essential files)
Install firmware (most roms are on ob3)
Install rom
Install kernel (flash kernel recommended)
Install gapps (official are out now)
Boot and configure
Reboot to recovery, flash magisk
Click to expand...
Click to collapse
I'll try this! Thanks
Biggest fix for me was not selecting to restore WiFi passwords on Google setup!
This is probably a noob question, but is it safe to restore a kernal backup with a kernal manager/flasher? I'd assume most
would recommend a dirty flash, or restore dtbo partitions. Thank you!
Adelino80 said:
This is probably a noob question, but is it safe to restore a kernal backup with a kernal manager/flasher? I'd assume most
would recommend a dirty flash, or restore dtbo partitions. Thank you!
Click to expand...
Click to collapse
Assuming you backed up the kernel on the same firmware/ROM version you're running now, should be fine. I've switched between stock kernel and custom kernel (and back) this way several times. I use EX KM instead of Franco, same thing though.
terlynn4 said:
Assuming you backed up the kernel on the same firmware/ROM version you're running now, should be fine. I've switched between stock kernel and custom kernel (and back) this way several times. I use EX KM instead of Franco, same thing thoug
Click to expand...
Click to collapse
terlynn4 said:
I backed it up stock kernal, and am still using stock Oxygen OS since my phone is my daily driver, and I need it to work. Can i just flash the Stock_Op9pro_30_boot.img and restore said partitions that way, since im still on A11? and if so do i need to wipe my dalvik cache, etc, and then flash boot.img, dtbo, and vendor_boot imgs to both slots?
Click to expand...
Click to collapse
terlynn4 said:
Assuming you backed up the kernel on the same firmware/ROM version you're running now, should be fine. I've switched between stock kernel and custom kernel (and back) this way several times. I use EX KM instead of Franco, same thing though.
Click to expand...
Click to collapse
I backed it up stock kernal, and am still using stock Oxygen OS since my phone is my daily driver, and I need it to work. Can i just flash the Stock_Op9pro_30_boot.img and restore said partitions that way, since im still on A11? and if so do i need to wipe my dalvik cache, etc, and then flash boot.img, dtbo, and vendor_boot imgs to both slots?
Adelino80 said:
I backed it up stock kernal, and am still using stock Oxygen OS since my phone is my daily driver, and I need it to work. Can i just flash the Stock_Op9pro_30_boot.img and restore said partitions that way, since im still on A11? and if so do i need to wipe my dalvik cache, etc, and then flash boot.img, dtbo, and vendor_boot imgs to both slots?
Click to expand...
Click to collapse
I have not done it by flashing partitions, though I'd expect it to work. I've only flashed kernels (both custom .zips and backups) via kernel manager on A11. I don't see any reason why you'd need to flash the additional partitions unless the custom kernel (or other customizations you're using) made changes to any of those.
terlynn4 said:
I have not done it by flashing partitions, though I'd expect it to work. I've only flashed kernels (both custom .zips and backups) via kernel manager on A11. I don't see any reason why you'd need to flash the additional partitions unless the custom kernel (or other customizations you're using) made changes to any of those.
Click to expand...
Click to collapse
I see, well I was able to restore back to my stock kernel. I had made a backup prior with Franco Kernal Manager and was able to restore stock, and flashed to Arter Kernal. Thanks for the help!
Adelino80 said:
I see, well I was able to restore back to my stock kernel. I had made a backup prior with Franco Kernal Manager and was able to restore stock, and flashed to Arter Kernal. Thanks for the help!
Click to expand...
Click to collapse
If you go back to stock from arter kernel you will need to flash vendor_boot.img dbto.img and boot.img from the version you are currently on though.