We've seen the rise of 4.9 kernel since last month. Maybe it's my time for changing rom since I got bored with what I am using right now. So as the title stated, is it working? also is OTA updates still working with this recovery? If it's not or you're not sure which recovery should I use?
4.9 kernel is being Pre-installed on many new updates of android 10 ROMs.
So you can choose and flash ROM which had 4.9 kernel pre-installed. Not sure if it available separately to flash, i would avoid to flash it on 3.18 since they are different and i wont want to cause any issue with device.
but if a ROM already has 4.9 kernel pre installed and there is 4.9 custom kernel available to flash then there should be no issue(but do check flashing guide first)
I did flashed latest build of Havoc OS which is as writing this comment Havoc-OS-v3.5-20200509 and it was running great, but it had slow charging issue and device was getting warm than normal charging so i went back to Havoc 2.9.
I flashed ROM with latest OrangeFox recovery and had no issue while flashing(i did backup everthing to avoid any issue) but it did went just fine.
Currently waiting for Havoc os update.
metelhammer said:
4.9 kernel is being Pre-installed on many new updates of android 10 ROMs.
So you can choose and flash ROM which had 4.9 kernel pre-installed. Not sure if it available separately to flash, i would avoid to flash it on 3.18 since they are different and i wont want to cause any issue with device.
I flashed ROM with latest OrangeFox recovery and had no issue while flashing(i did backup everthing to avoid any issue) but it did went just fine.
Currently waiting for Havoc os update.
Click to expand...
Click to collapse
So you did a clean install for a zip if it had 4.9 in update and currently installed was 3.18?
HuM4NoiD said:
So you did a clean install for a zip if it had 4.9 in update and currently installed was 3.18?
Click to expand...
Click to collapse
I did clean flash. if you are using any 3.18 kernel rom then clean flash is necessary to flash 4.9 kernel rom. do backup everything including persist backup too, to avoid any issue.
help
metelhammer said:
I did clean flash. if you are using any 3.18 kernel rom then clean flash is necessary to flash 4.9 kernel rom. do backup everything including persist backup too, to avoid any issue.
Click to expand...
Click to collapse
Hello I'm very insterested by this threads,
I have a 4x redmi with the MIUI premium 9.1stable rom and the kernel 3.18.31.
I would like to try to install a more recent rom as the author said
can you help me by giving me the procedure.
thanks a lot
korbendallas54 said:
Hello I'm very insterested by this threads,
I have a 4x redmi with the MIUI premium 9.1stable rom and the kernel 3.18.31.
I would like to try to install a more recent rom as the author said
can you help me by giving me the procedure.
thanks a lot
Click to expand...
Click to collapse
Well procedure is already mentioned in respected ROM thread(s) and it is pretty much the same for all the ROMs, no any different flashing method required for Redmi 4X unless it's instructed.
1. Backup everything in your device.
2. Download latest ROM Gapps of your choice. Magisk optional.
3. Reboot to recovery and wipe system, data, cache, dalvik, vendor. (wiping internal storage optional).
4. Flash ROM and Gapps.
5. Reboot to system.
Tanks for your answer,
Just try to flash the havoc-os3.x via recovery after wiping the system,data etc...as the procedure said with orangefox and It ended in an error message...
I should restore my previous rom
The error message indicates that the rom was no for my device santoni. I try to capture the message but I don't find the picture in the orangefox folder...
Interesting. I'm currently on latest release of LOS16.1. Want to try 10 roms in the future. So theres needed a full wipe to be able flash 4.9 kernel with latest roms? How their performance and battery life compared to pie roms? TY
Related
I just changed to CWM Recovery to explore arter97 kennel. Now I got issue that can not restore to previous ROM as CWM can not read TWRP data. So do we have any TWRP in zip so I can flash back by CWM?
Grab the latest TWRP .img from https://dl.twrp.me/zeroflte/ and flash with flashify inside android(flash recovery image). Arter kernel works great on TWRP but as the owner states, is not really tested with TWRP. I have been running that config with a 5.1 rom for quite some time using arter 11.
xecuter2 said:
Grab the latest TWRP .img from https://dl.twrp.me/zeroflte/ and flash with flashify inside android(flash recovery image). Arter kernel works great on TWRP but as the owner states, is not really tested with TWRP. I have been running that config with a 5.1 rom for quite some time using arter 11.
Click to expand...
Click to collapse
Many thanks for your information. As your experience, which one is better, Arrow or Back_to_Not3 with arter?
I'm running SOW rom right now but it may be best to wait for a 6.0/6.1 rom. I've had aweosme results with a bunch of the 5.1 roms, any should work properly with arter. Make sure you visit the baseband thread and update to DOJC to guarantee compatibilty. If you need help with that let me know, it requires odin but is easy, flash in the AP tab.
You need to flash the arter kernel cleaner before you flash another kernel.
https://drive.google.com/file/d/0B5Pl8DOq4VvfczctWWNsV0Z0LU0/view?usp=docslist_api
I never understood why other Developers have turned their head at the F2FS that can be formatted to your Data Partition with Phil's Touch..
Though I use TWRP.. I used Phil's to get my Data Partition to F2FS and with Arter97's Kernel.. It boosted my phones I/O bus significantly..
I don't care about over clocking since the phone is pretty quick as stock..
oh @trungctu you can install TWRP with the TWRP app from Google Play.. Just select your device and it will download and install it.. Just reboot and enjoy..
TWRP 3.0 was just released..
This link is TWRP 3.0 - flashable version...
Anybody able to update their oneplus to stable version of marshmallow that just got released. I am having few troubles doing it
Downloading.....
Cm-13.0-20160316-SNAPSHOT-ZNH0EAO1QB-bacon.zip (329.14 MB)
Downloaded and flashed , no issues till now. Gapps used = slim zero gapps 6.0.
COS13 will come in a week or two
help
drmuruga said:
Cm-13.0-20160316-SNAPSHOT-ZNH0EAO1QB-bacon.zip (329.14 MB)
Downloaded and flashed , no issues till now. Gapps used = slim zero gapps 6.0.
Click to expand...
Click to collapse
can you tell how you flashed it . I tried to do it but got error message
Cos13 is better power and performance
Sent from my A0001 using Tapatalk
try it with twrp 2.8.6.0
Hope u got the error 7 ?
if it was then this can solve ur problem
all the very best mate
Twrp 3.0.0
Clean flash
Slim_zero_gapps.BETA.6.0.build.0.x-20160121-1447.zip
Wipe cache/dalwik
Reboot.
Thats all
Guys, from what I read in the op, I get the feeling that he is confusing the recent CM13 snapshot with CyanogenOS13.
@kaskoraja
What rom is on your device right now?
Can you update from oneplus official signed CM12s to CM13-SNAPSHOT without data wipe??
drmuruga said:
Twrp 3.0.0
Clean flash
Slim_zero_gapps.BETA.6.0.build.0.x-20160121-1447.zip
Wipe cache/dalwik
Reboot.
Thats all
Click to expand...
Click to collapse
I want to update instead of starting from scratch. I tried with snapshot and CWM recovery and I couldnt do it by both ways
I tried stock version with cm recovery and update via ota then install through cm recovery but not able to flash gapps which was not present in ota , then flash twrp recovery and flash gapps via twrp shown more fc , so I reflash everything now no problem till now
drmuruga said:
Cm-13.0-20160316-SNAPSHOT-ZNH0EAO1QB-bacon.zip (329.14 MB)
Downloaded and flashed , no issues till now. Gapps used = slim zero gapps 6.0.
Click to expand...
Click to collapse
How do I flash this? Thru Cyanogen recovery? thru TWRP? If thru TWRP, which version?
I flash through twrp 3.0.0 recovery.there is no gapps in update, when I first flash through cm recovery , I need twrp to flash gapps but that lead to many fc . so I flash through twrp clean flash of ROM, gapps through twrp 3.0.0 official recovery
COS13 is on the way. "That said, you'll find that 13 runs amazing on the OPO thanks to both improvements in M and also the low level stuff we improved this time around. COS13 for the OPO is in final QA+cert so it won't be much longer (a few days we hope)."
Source (read comments): https://plus.google.com/+SteveKondik/posts/RNMSi2t33yN
Why this is in Themes and Apps?
SirSoviet said:
Why this is in Themes and Apps?
Click to expand...
Click to collapse
Because noobs and weed...
Hi! Currently running LOS 14.1 with Boeffla kernel, but I need to flash the stock one. Any ideas where to can find it?
Just flash rom.zip again on top of the current installation.
Or extract the boot.img from rom.zip, put it in a flashable zip and install it via twrp.
Will this overwrite only the system files? (I don't want to set up the phone from start... )
No if you just flash it on top of the current system, without any wipes or resets, all settings and datas should be still there.
Oh thanks! that's great! Can you do the same to try another ROM?
Switching from one rom to another with a so called dirty flash?
I would say: its not only not recommended :good:
You can try a dirty flash with a version update of the same rom, but all other would most likely end in problems. And latest than you will have do to a clean flash anyways. I would suggest you read the thread of your preferred rom(s) in advance and carefully (at least the last several pages) and than decide what and how you will flash.
Hello! I've been trying to install custom ROMs like HavocOS or REVOS but none of them let me they give me the same problem it is not possible to flash them. Before try it I did a full wipe in every partition, do they need MIUI to be flashed? Meanwhile I could be able to reflash a fresh version of miui.eu to not have a bricked phone.
VSMiguel said:
Hello! I've been trying to install custom ROMs like HavocOS or REVOS but none of them let me they give me the same problem it is not possible to flash them. Before try it I did a full wipe in every partition, do they need MIUI to be flashed? Meanwhile I could be able to reflash a fresh version of miui.eu to not have a bricked phone.
Click to expand...
Click to collapse
what problem are u facing or error that you are getting..
Ezio553 said:
what problem are u facing or error that you are getting..
Click to expand...
Click to collapse
If I remember right it was something like error 7 can not flash nameoftheromszip.zip with both havoc and rev. By the other side I hat no problem flashing a miui.eu ROM
VSMiguel said:
If I remember right it was something like error 7 can not flash nameoftheromszip.zip with both havoc and rev. By the other side I hat no problem flashing a miui.eu ROM
Click to expand...
Click to collapse
u tried the latest twrp 3.4.0.0 as i had the same error 7 : this rom is for raphael device.. for all aosp roms & few miui roms.
For AOSP roms i use twrp 3.4.0.0 and that works perfectly fine but for miui roms i need to open the zip of rom
then goto META-INF\com\google\android\ then from here i open the update script with notepad++ and replace all the raphael word with raphaelin as my device is indian unit and then press ctrl+s to save it then exit notepad++ the zip will ask to update press yes and then use that zip for flashing.
Sorry i just mentioned the full way how i flash as i also got the same error when i bought my device and tried flashing any rom directly.
Use TWRP 3.4 for aosp roms and it should flash directly and for miui roms i always have to modify the zip updater script to make it work.
VSMiguel said:
Hello! I've been trying to install custom ROMs like HavocOS or REVOS but none of them let me they give me the same problem it is not possible to flash them. Before try it I did a full wipe in every partition, do they need MIUI to be flashed? Meanwhile I could be able to reflash a fresh version of miui.eu to not have a bricked phone.
Click to expand...
Click to collapse
Look here
https://forum.xda-developers.com/k20-pro/how-to/simple-guide-flipkart-owners-t4151007/post83329343
Hi guys i am facing a liitle bit of a problem i unlocked my bootloader and flash some custom roms but after flashing lineage os the battery went down hill and tried to flash other roms to fix the problem also flashed the stock rom no luck.So i was trying to make a clean flash as last possible fix but the system and vendor options in advance wipe are not showing i mounted them but nothing show in advance wipe.I tried to flash different Twrp version old and new and still no luck also tried to flash Orangefox Recovery when i go to mount options and tried to ticked system and vendor it didnt ticked.I remember first time flashing Twrp after i reboot in recovery there was option (read only i guess) and i ignore it and it seems that's it become write only. (i tried to reflash the orangefox recovery and then the twrp to reset it but still no option for read only to untick it).Any idea to fix that issue?!Thanks.
Newbie2022 said:
Hi guys i am facing a liitle bit of a problem i unlocked my bootloader and flash some custom roms but after flashing lineage os the battery went down hill and tried to flash other roms to fix the problem also flashed the stock rom no luck.So i was trying to make a clean flash as last possible fix but the system and vendor options in advance wipe are not showing i mounted them but nothing show in advance wipe.I tried to flash different Twrp version old and new and still no luck also tried to flash Orangefox Recovery when i go to mount options and tried to ticked system and vendor it didnt ticked.I remember first time flashing Twrp after i reboot in recovery there was option (read only i guess) and i ignore it and it seems that's it become write only. (i tried to reflash the orangefox recovery and then the twrp to reset it but still no option for read only to untick it).Any idea to fix that issue?!Thanks.
Click to expand...
Click to collapse
Don't try to format or delete other partitions as data dalvik and cache! Risk of brick! And not necessary!
Only follow exactly step by step the ROM installation instructions
E.g.
👍 [SHARED][ROM] [ANDROID 13] [OSS] PULKITS lineage os 20 19.02.23/ checked by myself
Update on page 14 Update latest los 20 on page 7 I'm on pulkits android 13 for testing. Quiet good! Soon you'll get a beta! Thanks a lot to @Pulkit Agarwal Please donate him, thanks Update see post Post in thread '👍 [SHARED][ROM] [ANDROID...
forum.xda-developers.com
Newbie2022 said:
.... i was trying to make a clean flash as last possible fix but the system and vendor options in advance wipe are not showing i mounted them but nothing show in advance wipe......
Click to expand...
Click to collapse
I'm always surprised if someone want to do these kind of actions to resolve such relative simple problems. While imho nowhere such actions are described by flashing instructions.
"Simple" because the rom itself does work without issues, so the real reason for battery drain must be found, (wakelocks, sensors, updateproblems, running services etc.) which could be very time consuming,
By starting without Gapps to see what happens with battery, you find if the reason is rom or Google.
Other reasons could be VOlte, pocket detection, proximitysensor, hanging updates.
Flashing a new rom does replace the system and vendor partition, so everything what was on it is gone.
The data partitition needs to be formatted, because it is locked by encryption of the old rom.
Startup the new flashed rom after format data partition, does encrypt the new data again.
Laptapper said:
Don't try to format or delete other partitions as data dalvik and cache! Risk of brick! And not necessary!
Only follow exactly step by step the ROM installation instructions
E.g.
👍 [SHARED][ROM] [ANDROID 13] [OSS] PULKITS lineage os 20 19.02.23/ checked by myself
Update on page 14 Update latest los 20 on page 7 I'm on pulkits android 13 for testing. Quiet good! Soon you'll get a beta! Thanks a lot to @Pulkit Agarwal Please donate him, thanks Update see post Post in thread '👍 [SHARED][ROM] [ANDROID...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks man yes i know the risk but it seems to be the only option i have i tried to dirty flash Roms following instructions, but the battery drain issue persist so i was trying as last resort to clean flash and then stock rom in a hope to resolve the issue. Thank you very much really appreciated
Elinx said:
I'm always surprised if someone want to do these kind of actions to resolve such relative simple problems. While imho nowhere such actions are described by flashing instructions.
"Simple" because the rom itself does work without issues, so the real reason for battery drain must be found, (wakelocks, sensors, updateproblems, running services etc.) which could be very time consuming.
Flashing a new rom does replace the system and vendor partition, so everything what was on it is gone.
The data partitition needs to be formatted, because it is locked by encryption of the old rom.
Startup the new flashed rom after format data partition, does encrypt the new data again.
Click to expand...
Click to collapse
Yeah the issue was after flashing the rom something happened i don't know exactly what it is but the screen battery consumption hit the roof altouth i capped the refresh rate at 60 and use dark mode and brightness to 35 max . Before flashing the rom(lineage) i didnt had this issue with older other roms i flashed before the issue (pixel experience and pixel os)...I dirty flash other roms and even stock rom through Miflash tool but the same issue continued so i was hoping if i can clean flash the stock rom. Thanks alot man.
Newbie2022 said:
... i tried to dirty flash Roms following instructions, but the battery drain issue persist ....
Click to expand...
Click to collapse
"Dirty flash" means system and vendor partition will be replaced with the same files as before, but the data stays untouched. So this will have no impact on solving your problems.
"Clean flash" means the data is gone too for a new rom encryption.
With enabled encryption it is only possible to flash a new rom or stock rom by clean flash.
FYI: I solved huge battery drain what was caused by Pixel spoofing on a non Pixel.
Before I found this I was weeks further.
Only if everyone with the same rom has such drain too, there is something wrong with a rom.
If this is the case i can assure you this will be picked up by the developer of that rom.
If you have the same issue with different roms it could be directed to the hardware of the phone.
With RN10P the proximity sensor has known issues with some devices.
Elinx said:
"Dirty flash" means system and vendor partition will be replaced with the same files as before, but the data stays untouched. So this will have no impact on solving your problems.
"Clean flash" means the data is gone too for a new rom encryption.
With enabled encryption it is only possible to flash a new rom or stock rom by clean flash.
FYI: I solved huge battery drain what was caused by Pixel spoofing on a non Pixel.
Before I found this I was weeks further.
Only if everyone with the same rom has such drain too, there is something wrong with a rom.
If this is the case i can assure you this will be picked up by the developer of that rom.
If you have the same issue with different roms it could be directed to the hardware of the phone.
With RN10P the proximity sensor has known issues with some devices.
Click to expand...
Click to collapse
Ok i will check the spoof issue and try to flash stock rom again via Miflash tool hopefully the issue will be solved. Thanks a lot for the tips and insight