Hey guys, i got my N5 like 3 days ago, and i rooted and flashed Faux Kernel and modded it with these mods:
Dalivk Patch
Sound Boost
Camera Improvements
Everything was great, however i heard about 4.4.1, so i flashed this rom ontop of 4.4 stock and now i reflashed all mods except the Dalvik Patch... Cause it says on the OP that it dosent work with Odexed roms...
So is their any way to either Deodex my rom or imrprove system performance without sacrificing battery?, like the dalivk patch did,
The bionic and dalvik patch works on odex no problem. The op probably just hasn't been updated with this info.
if you want to change to deodex just flash the doedex version without wiping to keep your data.
edit.. sorry just noticed there isn't a deodex version
Related
Hey guys so I just wanted to make sure I'm about flash the correct kernel to my S3. I'm currently running Liquid Smooth JB v2.4 and its stock leanKernel 3.4.45. I wanna flash KT747 AOSP JB MR1 3.4 VZW which I downloaded from ktsoonez thread http://forum.xda-developers.com/showthread.php?t=1853816. Does this look right to everybody?
Once I boot into recovery I can just flash the kernel then clear cache/dalvik and fix permissions, reboot and I'm set right?
I really don't want to mess this up lol.
wipe cache
wipe dalvik
flash kernel
wipe cache
wipe dalvik
fix permissions
reboot
thats always been my process and ive never had any problems.
name ersaiio
That seemed to work quite nicely ddurandSGS3 thank you!
Hi guys, I have a xt1032 with CM11 Snapshot.
I have the stock kernel and wanted to try FAUX kernel because it seems to be awesome!
But I have some doubts..
How can I backup the stock kernel and restore it if the FAUX kernel fails, without losing everything on the phone?
And to install it I have to download, put into the phone and flash using recovery? Or do I have to do some wipes?
So in case of brick I'm covered.
By the way... what kind of wipes can I do with TWRP that don't delete me any of my stuff (photos, apk's, ...)? Because I know that there are some system wipes that delete everything...
I hope you can help me with these questions!!
Thank you!!
1. Dont backup just the kernel, backup the whole Rom
2. Faux kernel doesnt work in CM. Maybe try Pink kernel instead or furnace or Render Kernel
3. To install a kernel you need to wipe cache and dalvik cache.
4. By wiping cache and dalvik cache you dont lose your data.
5. Always remember that you are responsible for any damage on your phone and noone else
6. If you get a bootloop then restore your backup
7 If your phone doesnt turn on at all and you dont even get into bootloader then i think you are game over
8. As you use CM i think you have already known some of the things .
9. Happy flashing
Thanks for your quick reply!
Last question ( for The moment ), doing a backup with twrp do I get a full ROM and kernel backup?
Solved!
I have installed the Pink Kernel and it works awesome! Just backed up the whole ROM and flashed it without any fear.
Thank you very much for the answers.
Bye!
Upgraded to Lollipop on my Z3 with the relevant pre rooted flashable firmware created using SuperSU 2.46 and NUT DualRecovery 2.8.9.
Upon installing Xposed alpha 2 alongside the flashable ARM.zip counterpart. Everytime I reboot I'm hitting bootloops and need to go to TWRP and wipe cache/"dalvik" cache to get the phone to boot.
Downside is it rebuilds the ART cache when it does boot which isn't a quick process.
Is there a fix for this?
SB13X said:
Upgraded to Lollipop on my Z3 with the relevant pre rooted flashable firmware created using SuperSU 2.46 and NUT DualRecovery 2.8.9.
Upon installing Xposed alpha 2 alongside the flashable ARM.zip counterpart. Everytime I reboot I'm hitting bootloops and need to go to TWRP and wipe cache/"dalvik" cache to get the phone to boot.
Downside is it rebuilds the ART cache when it does boot which isn't a quick process.
Is there a fix for this?
Click to expand...
Click to collapse
Xposed works on a debloated ROM.
For now.
Wiping cache is the only workaround for a normal boot.
TheTeslaCoil said:
Xposed works on a debloated ROM.
For now.
Wiping cache is the only workaround for a normal boot.
Click to expand...
Click to collapse
When you say works on a debloated ROM you mean works without bootloops? I've got Xposed working with my ROM without debloating it, just the bootloop cache wiping situation remains.
SB13X said:
When you say works on a debloated ROM you mean works without bootloops? I've got Xposed working with my ROM without debloating it, just the bootloop cache wiping situation remains.
Click to expand...
Click to collapse
That' s not working.
On a debloated one, there is no need to wipe cache.
I've rooted my phone using the despair kernel on Android M. I flashed via recovery but experiencing WiFi and cell drop outs every ten minutes simultaneously. Not had much experience flashing kernels - is there anything else I should have done?
You shoulda just used blackbird5308's stock root enabled kernel
Sent from my Nexus 5 using Tapatalk
Why should I? Are there known issues on despair? Can you just flash kernels without wiping?
Jinson7 said:
Why should I? Are there known issues on despair? Can you just flash kernels without wiping?
Click to expand...
Click to collapse
GIVE IT A SHOT:
you could try StephanMc's kernel. it's stock m preview 3 with root.
if your problems don't occur with this kernel they were either related to a bad dirty flash or related to the kernel.
here's the link:
http://forum.xda-developers.com/goo...om-android-m-preview-2-flashable-zip-t3157299
FROM MY EXPERIENCE:
i'm also running m preview 3 and if i want to try a new custom kernel i always flash StephanMc's kernel first (because it's purely stock + root).
then i wipe dalvik + cache and flash the desired kernel.
if you just want a rooted phone, you can simply stick to StephanMc's kernel.
PLEASE NOTICE:
some custom kernels recommend to wipe system and data and install the stock image (or custom rom) too.
IMPORTANT:
always backup your data! (see titanium backup)
SUMMARY:
as long as flashing stock kernel and wiping dalvik+cache before flashing my chosen custom kernel i will stick to this.
if you experiencing any problems completely wipe your phone, flash stock image, flash custom rom/kernel and restore your data backup.
Hey guys.
So tonight I wanted to try the nougat build which has been floating around on here for a couple of days. Because I need my main (fully functional & optimized) ROM, I installed MultiROM, and installed the (MultiROM optimized version of) AOSP nougat, with GApps, SuperSU(latest) & hw keys > soft-keys mods.
Everything worked out, but then when I tried booting the internal ROM, it just booted me into recovery.
So, what is happening here? Is there a way to make my main ROM bootable?
I had to reflash first Rom... Didnt loose data but had to reflash Rom+gapps+supersu
prohackerbro said:
I had to reflash first Rom... Didnt loose data but had to reflash Rom+gapps+supersu
Click to expand...
Click to collapse
Awesome! I went into recovery, flashed my rom + SuperSU + Xposed + Leaked Nexus launcher & I was up and running again
Only thing which I lost was the Nexus Launcher data, but I could've backed that up using Titanium backup. Meanwhile I've had the problem occur again, and fixed it with the same resolution. Currently it's in a state where it works perfectly. MultiROM is dodgy & weird sometimes...
Anyways, cheers :good: