So let me see if i understand this correctly. From what i have read, it looks like i cant install CWM recovery without installing a custom Kernel? So me backing up my stock set up is pretty much out of the question? So everytime i wish to install a different custom rom i am essentailly reinstalling CWM recovery as well?
How can i backup my stock set up and restore it if i screw something up, or install a rom that i am not happy with? I am coming rom an epic 4g on sprint and it was different with that galaxy phone.
Flash a CF Root kernel that matches your firmware, create your near stock b/u. This will be your point to fall back on. 99.99% of ROMs you flash will include a kernel, that also has CWM, it may be a different version but they all work the same, for the most part. The majority of kernels include CWMr 5 or higher.
You'll always have the option of restoring your "stock" b/u so long as you don't delete it. Titanium b/u is the ticket to back up all your apps and their data rather than having to extract those apps/data from a CWM b/u.
You only have to root once. The easiest way to unroot is to flash a stock firmware. Flashing a stock kernel back on after you've rooted will replace CWM recovery with stock recovery, but you'll remain rooted. Probably doesn't address all your questions, but you've got a start.
mudferret said:
Flash a CF Root kernel that matches your firmware, create your near stock b/u. This will be your point to fall back on. 99.99% of ROMs you flash will include a kernel, that also has CWM, it may be a different version but they all work the same, for the most part. The majority of kernels include CWMr 5 or higher.
You'll always have the option of restoring your "stock" b/u so long as you don't delete it. Titanium b/u is the ticket to back up all your apps and their data rather than having to extract those apps/data from a CWM b/u.
You only have to root once. The easiest way to unroot is to flash a stock firmware. Flashing a stock kernel back on after you've rooted will replace CWM recovery with stock recovery, but you'll remain rooted. Probably doesn't address all your questions, but you've got a start.
Click to expand...
Click to collapse
forgot to mention that i am rooted now. using oneclickroot.
Just flash a custom kernel with CWM recovery installed inside.
Such as:
- Siyah
- Phoenix
- Ninphetamine
etc...
DO NOT FLASH STOCK KERNEL AS IT WILL DELETE CWM RECOVERY. ROM MANAGER DOES NOT INSTALL RECOVERY ON YOUR PHONE.
nicholaschum said:
Just flash a custom kernel with CWM recovery installed inside.
Such as:
- Siyah
- Phoenix
- Ninphetamine
etc...
DO NOT FLASH STOCK KERNEL AS IT WILL DELETE CWM RECOVERY. ROM MANAGER DOES NOT INSTALL RECOVERY ON YOUR PHONE.
Click to expand...
Click to collapse
is it as simple as using Odin, clicking PDA and flashing the downloaded kernel? and there should be no side effects from using a custom kernel such as Siyah?
Getting back to 100% stock is easy, odin flash a rom.
CF root *is* the stock kernel, just with some bits added (CWM recovery and root).
CF root with your stock rom is defo the safest bet.
jerseykat1 said:
is it as simple as using Odin, clicking PDA and flashing the downloaded kernel? and there should be no side effects from using a custom kernel such as Siyah?
Click to expand...
Click to collapse
Yes if you get the kernel in odin tar file, otherwise flash CF root and use CWM recovery to flash the zips.
So I finally tried some AOSP, but missed my camera immensely so I went to switch back to my backup that I made in TWRP.
Unfortunately AOSP roms use CWM recovery and it won't recognize my TWRP so I've tried to redo the Dual Recovery method but since I no longer have stock kernel it fails.
Now I've also tried to use fastboot to flash a boot.img which I thought was a stock kernel....but obviously I was wrong or it didn't want to work.
Either way as of now I'm using FlashTool to flash stock image, then root, then install DualRecovery again and THEN restore backup.
Does anyone know where I went wrong and hopefully provide a faster solution in case I go back to trying ASOP again? Maybe backup in CWM next time?
Now I do have to flashable DualRecovery.zip that I did try in CWM but it didn't work either, I'm guessing since I didn't have stock kernel...
Thanks in advanced. Why didn't Sony just have a dedicated recovery partition!
Flash doom Lords kernel (v9 is it?) which has twrp, restore back up, done
Mr.R™ said:
Flash doom Lords kernel (v9 is it?) which has twrp, restore back up, done
Click to expand...
Click to collapse
Thanks, I thought about that but I didn't want any other kernel than stock. Couldn't find stock, but I went the long route and now I'm back in business!
ZPaul2Fresh8 said:
Thanks, I thought about that but I didn't want any other kernel than stock. Couldn't find stock, but I went the long route and now I'm back in business!
Click to expand...
Click to collapse
the recoveries in the original development sections are actualy stock kernels with recovery, you could use those instead if you dont want dooms modded/custom kernel
Envious_Data said:
the recoveries in the original development sections are actualy stock kernels with recovery, you could use those instead if you dont want dooms modded/custom kernel
Click to expand...
Click to collapse
Well I did try to use the dual recovery but it didn't work. It says it is only for stock kernel so I didn't expect it to, but I had to try...
@ZPaul2Fresh8
EDIT: DON'T INSTALL IF YOU STILL WANT TO USE CM!!!
It won't boot the system of cm if you flashed the twrp img, just flash it if you want to go to a backup!
"
It was very easy for me, at the end i had a twrp 2.7.0.0 in my cm11'd Z2, you need pc, and usb cable, and fastboot and adb drivers, lol its way easier than flashing .ftf, go to http://forum.xda-developers.com/showthread.php?t=2764971 and download the zip and extract it, follow this tout: http://forum.xda-developers.com/showthread.php?t=1752270 and you will be all good...
I have RN4 SD with RR Nougat and ElectraBlue kernel. How can I reinstall stock kernel? And what is the latest android version of stock kernel for mido?
nikkky said:
I have RN4 SD with RR Nougat and ElectraBlue kernel. How can I reinstall stock kernel? And what is the latest android version of stock kernel for mido?
Click to expand...
Click to collapse
Reflash whatever ROM you are using to go back to stock kernel.
And how can I go back to stock ROM?
nikkky said:
And how can I go back to stock ROM?
Click to expand...
Click to collapse
If you wanna return to stock ROM including stock recovery etc. use MiFlash to flash stock fastboot image, guide = http://en.miui.com/thread-565784-1-1.html
It's really easy, just follow from point B).
I'm on RR nougat with fanvo kernel and redwolf recovery, i want to revert back to stock miui rom(only rom, i would like to keep redwolf), can you guy's show me the step? I try to flash stock rom 9.5.9 global in redwolf but failed. TIA
w4y4n said:
I'm on RR nougat with fanvo kernel and redwolf recovery, i want to revert back to stock miui rom(only rom, i would like to keep redwolf), can you guy's show me the step? I try to flash stock rom 9.5.9 global in redwolf but failed. TIA
Click to expand...
Click to collapse
Follow guide above (dont relock bootloader) and then just flash Redwolf.
Thank you sir, i'm aware about fastboot method, but i just don't have pc right now to flash, maybe there is other way to revert back without pc, by recovery method maybe? Btw, thank for your reply sir :good:
w4y4n said:
Thank you sir, i'm aware about fastboot method, but i just don't have pc right now to flash, maybe there is other way to revert back without pc, by recovery method maybe? Btw, thank for your reply sir :good:
Click to expand...
Click to collapse
Im pretty sure you can just download stock ROM from http://en.miui.com/download.html (down ATM for some reason) and flash it normally, also dont forget to flash lazyflasher since you are going back to stock. (Redwolf might be taking care of it, not sure)
I allready try it sir, it failed. Failed when flashing system in recovery (not finish flashing stock rom), phone suddenly reboot and stuck on logo. Force to reboot to recovery, can't mount system, but after reboot recovery everything back to normal, and flash RR again so i can use my phone :laugh:
Btw, i try to flash miui 9.5.9.0 NCFMIFA, sorry for my english
w4y4n said:
I allready try it sir, it failed. Failed when flashing system in recovery (not finish flashing stock rom), phone suddenly reboot and stuck on logo. Force to reboot to recovery, can't mount system, but after reboot recovery everything back to normal, and flash RR again so i can use my phone :laugh:
Btw, i try to flash miui 9.5.9.0 NCFMIFA, sorry for my english
Click to expand...
Click to collapse
Maybe you tried to flash fastboot ROM? Link filename you tried to flash.
Due download page shutdown, here is recovery file that i allready try to flash, miui_HMNote4XGlobal_V9.5.9.0.NCFMIFA_b57067babe_7.0
Sorry can't refer the link sir, just the file name :laugh:
w4y4n said:
Due download page shutdown, here is recovery file that i allready try to flash, miui_HMNote4XGlobal_V9.5.9.0.NCFMIFA_b57067babe_7.0
Sorry can't refer the link sir, just the file name :laugh:
Click to expand...
Click to collapse
You are kidding right? This is not even full ROM, this seems like incremental update package (only 45.1MB) that's why you cant flash it.
Just wait till http://en.miui.com/download.html is working and download latest stable or developer ROM and flash it.
Edit:
Here is link to stable 9.5.10.0 http://bigota.d.miui.com/V9.5.10.0.NCFMIFA/miui_HMNote4XGlobal_V9.5.10.0.NCFMIFA_2300218819_7.0.zip
Or developer 8.2.1 http://bigota.d.miui.com/8.2.1/miui_HMNote4XGlobal_8.2.1_7fda810f8d_7.0.zip
It full rom sir, about 1,3gb in size. Thank you sir, i'll try developer rom later
k3lcior said:
You are kidding right? This is not even full ROM, this seems like incremental update package (only 45.1MB) that's why you cant flash it.
Just wait till http://en.miui.com/download.html is working and download latest stable or developer ROM and flash it.
Edit:
Here is link to stable 9.5.10.0 http://bigota.d.miui.com/V9.5.10.0.NCFMIFA/miui_HMNote4XGlobal_V9.5.10.0.NCFMIFA_2300218819_7.0.zip
Or developer 8.2.1 http://bigota.d.miui.com/8.2.1/miui_HMNote4XGlobal_8.2.1_7fda810f8d_7.0.zip
Click to expand...
Click to collapse
Flashing the stock rom using OrangeFox recovery works? I'm on Lineage OS by Zeelog
Mido is a really cool device. I was using MiracleDROID from the beginning. Best ROM ever made (just my opinion). But it is not supported anymore. Thanks to Hikari no Tenshi and Lakku.
I can't call some telephone numbers anymore. No clue, why. I would like to "reset" the phone.
FW: org. stable ROM then following attached guide.
Is that a good idea? Any help or experience is appreciated.
i recently have tried many kernels like(sesh kernel)(lowrun kernel)(optimus drunk kernel) the problem is while iwas using one of them i restarted my device , to stuck at the brand name(poco)while booting up, i went to twrp many times and flashed many other kernels but got the same issue, only the stock kernel(miui offical kernel) worked and the phone booted up normally, iam so confused, i hope you help me with this issue or provide me info if u had countered this issue before on poco f1 device!
thanks for all your hard work developers!!!
Did you dirty flash the ROM zip in between flashing custom kernel? Shouldn't flash one custom kernel over another one. That can cause issues.
amn1987 said:
Did you dirty flash the ROM zip in between flashing custom kernel? Shouldn't flash one custom kernel over another one. That can cause issues.
Click to expand...
Click to collapse
dirty flash i dunno wat dirty mean here but yea iwas flashing kernel over kernel, also iam using miui offical rom no custom roms! if i need to flash rom zip everytime then its useless, i dont need to wipe my data everytime!
Yep, that's the problem, you don't just flash kernel over another one and expect your device to behave normally. Atleast dirty flash your rom so you have the original kernal back and try different kernel after that (though I wouldn't recommend). If you don't clean flash and encounter issues, it's your fault, don't whine.
khanhlinh said:
Yep, that's the problem, you don't just flash kernel over another one and expect your device to behave normally. Atleast dirty flash your rom so you have the original kernal back and try different kernel after that (though I wouldn't recommend). If you don't clean flash and encounter issues, it's your fault, don't whine.
Click to expand...
Click to collapse
i have nerver whined over this as you can see above, iwas clueless, that is why i asked in the first place, the thing iam bothered about it now is, if i need to (dirty?) flash my rom then i need to reset and delete allmy data again, never expected the need to do that, thx for ur reply and be assure i won't whine since i knew the issue and it's consequences!
Do you have the fastboot flash archive file on your PC somewhere? Of the stock rom you are currently using. You can check what version of official rom you are currently using and I can send you the boot.img file from the archive (that is the partition that contains the stock kernel). Flashing that is what reverts you back to stock kernel.
All of this is a requirement for flashing a different custom kernel. It goes like this : you flash a custom kernel >dont like it>flash the stock boot.img through recovery>reboot to system>go back to recovery>flash the new kernel you want to test. If I wasnt clear, contact me, I think I can help.
crazy_4_and1 said:
Do you have the fastboot flash archive file on your PC somewhere? Of the stock rom you are currently using. You can check what version of official rom you are currently using and I can send you the boot.img file from the archive (that is the partition that contains the stock kernel). Flashing that is what reverts you back to stock kernel.
All of this is a requirement for flashing a different custom kernel. It goes like this : you flash a custom kernel >dont like it>flash the stock boot.img through recovery>reboot to system>go back to recovery>flash the new kernel you want to test. If I wasnt clear, contact me, I think I can help.
Click to expand...
Click to collapse
about boot.img yea i have that system on my pc, but i already backed up the stock boot.img before installing my first custom kernel, but after that i didnt work as ur talking about reflashing stock kernel then boot then return to recovery then flash another custom kernel, instead i flashed custom kernel after another, didnt include between each custom kernel a stock kernel flash process, that is why iam having this issue, now even if i tried to flash custom kernel(although iam using now the stock kernel)i will end up soft bricked! but iam now need 1 help if youcan answear me bcs i dunno why icant make another thread,
if i used twrp backup process and created a restore zip for my system(nandroid backup for reflashing stock rom ) then i wiped my all data, then if the zip file is in my phone the it should be wiped out so, how can i then restore my zip or use it through twrp to restore my old system and everything(if the new rom wasn't good for me?????)
and if i moved the zip file i created using twrp to pc and my phone while flashing new rom got soft brick then how will the pc be able to recognize the phone to be able to move the zip file to it and then flash it through twrp??? i never found an answear through xda yet and hope ucan answear my questions and assure me before flashing my stock rom again! i dont want to lose any info about these process before flashing, if i lost, it would be too late for my precious data you knew!
Nasrk said:
about boot.img yea i have that system on my pc, but i already backed up the stock boot.img before installing my first custom kernel, but after that i didnt work as ur talking about reflashing stock kernel then boot then return to recovery then flash another custom kernel, instead i flashed custom kernel after another, didnt include between each custom kernel a stock kernel flash process, that is why iam having this issue, now even if i tried to flash custom kernel(although iam using now the stock kernel)i will end up soft bricked! but iam now need 1 help if youcan answear me bcs i dunno why icant make another thread,
if i used twrp backup process and created a restore zip for my system(nandroid backup for reflashing stock rom ) then i wiped my all data, then if the zip file is in my phone the it should be wiped out so, how can i then restore my zip or use it through twrp to restore my old system and everything(if the new rom wasn't good for me?????)
and if i moved the zip file i created using twrp to pc and my phone while flashing new rom got soft brick then how will the pc be able to recognize the phone to be able to move the zip file to it and then flash it through twrp??? i never found an answear through xda yet and hope ucan answear my questions and assure me before flashing my stock rom again! i dont want to lose any info about these process before flashing, if i lost, it would be too late for my precious data you knew!
Click to expand...
Click to collapse
First rule before flashing anything to your device - Always backup your data to your pc, cloud ,etc. You never know what can go wrong. Now for your kernel issue as crazy_4_and1 said you have to be on stock kernel to try a new kernel. Just flash boot.img to your boot partition through twrp. You don't have to flash the whole rom. Flashing boot.img doesn't wipe your data. And about your soft brick issue as long as twrp recovery is accessible you can restore your created backup. MTP works in twrp. You can flash your stock rom again without wiping internel storage to resolve any system related problems. Just wipe system, cache, data and dalvik/art. Your app data will be gone but your internal storage will be intact. You can also dirty flash without wiping data but it usually causes problems. If recovery can't be accessed you can flash fastboot rom. Fastboot rom will wipe everything.
callmebutcher101 said:
First rule before flashing anything to your device - Always backup your data to your pc, cloud ,etc. You never know what can go wrong. Now for your kernel issue as crazy_4_and1 said you have to be on stock kernel to try a new kernel. Just flash boot.img to your boot partition through twrp. You don't have to flash the whole rom. Flashing boot.img doesn't wipe your data. And about your soft brick issue as long as twrp recovery is accessible you can restore your created backup. MTP works in twrp. You can flash your stock rom again without wiping internel storage to resolve any system related problems. Just wipe system, cache, data and dalvik/art. Your app data will be gone but your internal storage will be intact. You can also dirty flash without wiping data but it usually causes problems. If recovery can't be accessed you can flash fastboot rom. Fastboot rom will wipe everything.
Click to expand...
Click to collapse
thanks for your great help, i will do as u said and inform you anything if something went wrong, thanks for simplified explanaitions that i think every begginer need it!
Nasrk said:
i recently have tried many kernels like(sesh kernel)(lowrun kernel)(optimus drunk kernel) the problem is while iwas using one of them i restarted my device , to stuck at the brand name(poco)while booting up, i went to twrp many times and flashed many other kernels but got the same issue, only the stock kernel(miui offical kernel) worked and the phone booted up normally, iam so confused, i hope you help me with this issue or provide me info if u had countered this issue before on poco f1 device!
thanks for all your hard work developers!!!
Click to expand...
Click to collapse
Which version of Android u use 9 or 10 please update Android 10 then
After flash any kernal flash Dfe zip then u must boot
But if u are want a best kernel with great performance and less heating than others then u must use amog787 kernel if u use once u stick with it always believed me this kernel is used in oxygen os if you use any oos rom then u know what I am talking
Nasrk said:
thanks for your great help, i will do as u said and inform you anything if something went wrong, thanks for simplified explanaitions that i think every begginer need it!
Click to expand...
Click to collapse
i did a process took 6 hours of my time, faced many errors but went out victorious, so the summary of my work is:
when u back up dont backup 'system' but backup everything its fine,
why?bcs when u want to restore using ur nandroid backup(its twrp backup) during the restore process when flashing 'system' it will give you error, just when u restore make sure system isnot the one beside others, also backup system image it is the system itself.
second, my poco f1 when was soft bricked(i bricked it) if u went to fastboot(if twrp recovery suddenly stopped appearing) in my situation adb didnt recognise the phone, so iwas almost hopeless, also miflash tool whenever i give it rom to flash it gives me errors, but somehow i went back to twrp and flashed the stock rom using usb(otg) thqt was my way to break through this issue, so ( never ever lose twrp, if u lost it, and adb drivers didnt recognise ur device while in fastboot(maybe it was bcs my old drivers or bug) ur doomed)!!!! and nandroid wont backup everything u need, just the apps and ur old system, all ur interneal storage(if u didnt wipe it like me) will still as it is, it isnt backed up with the backup zip!.
i tried many sites (including xda forums) to find solutions for my errors but none of them helped me out, so this is my experience and if someone need help ask me i will try ti help him, and i ask all of who sees this post to share his poco f1 experience bcs no matter developers says, the testers know the situation better!!
goodluck everyone!
varunsngh786 said:
Which version of Android u use 9 or 10 please update Android 10 then
After flash any kernal flash Dfe zip then u must boot
But if u are want a best kernel with great performance and less heating than others then u must use amog787 kernel if u use once u stick with it always believed me this kernel is used in oxygen os if you use any oos rom then u know what I am talking
Click to expand...
Click to collapse
i will try ur kernel but ur way of publishing kernel name is fishy!!
crazy_4_and1 said:
Do you have the fastboot flash archive file on your PC somewhere? Of the stock rom you are currently using. You can check what version of official rom you are currently using and I can send you the boot.img file from the archive (that is the partition that contains the stock kernel). Flashing that is what reverts you back to stock kernel.
All of this is a requirement for flashing a different custom kernel. It goes like this : you flash a custom kernel >dont like it>flash the stock boot.img through recovery>reboot to system>go back to recovery>flash the new kernel you want to test. If I wasnt clear, contact me, I think I can help.
Click to expand...
Click to collapse
Nasrk said:
i did a process took 6 hours of my time, faced many errors but went out victorious, so the summary of my work is:
when u back up dont backup 'system' but backup everything its fine,
why?bcs when u want to restore using ur nandroid backup(its twrp backup) during the restore process when flashing 'system' it will give you error, just when u restore make sure system isnot the one beside others, also backup system image it is the system itself.
second, my poco f1 when was soft bricked(i bricked it) if u went to fastboot(if twrp recovery suddenly stopped appearing) in my situation adb didnt recognise the phone, so iwas almost hopeless, also miflash tool whenever i give it rom to flash it gives me errors, but somehow i went back to twrp and flashed the stock rom using usb(otg) thqt was my way to break through this issue, so ( never ever lose twrp, if u lost it, and adb drivers didnt recognise ur device while in fastboot(maybe it was bcs my old drivers or bug) ur doomed)!!!! and nandroid wont backup everything u need, just the apps and ur old system, all ur interneal storage(if u didnt wipe it like me) will still as it is, it isnt backed up with the backup zip!.
i tried many sites (including xda forums) to find solutions for my errors but none of them helped me out, so this is my experience and if someone need help ask me i will try ti help him, and i ask all of who sees this post to share his poco f1 experience bcs no matter developers says, the testers know the situation better!!
goodluck everyone!
Click to expand...
Click to collapse
Well, I use Pitch Black Recovery, as it patches the installation of stock roms so I does not get erased by stock recovery. Then, the softbrick you are talking about is probably caused by flashing a kernel but not disabling dm-verity (that's a requirement if you want a stock rom/custom kernel combo) someone correct me if I'm wrong. So, the order, for a custom kernel install would be 1. Clean flash your ROM, 2. boot it 3. Reboot to recovery and flash the custom kernel 4. Flash dm-verity disabler 5. Reboot to system.
You just need a boot.img file on your sd card/pc, so you can flash just that file if your rom fails to boot.
I keep my phone unencrypted, so i use DFE/DM-verity disabler zip (literally just google it and it will point you to a thread here on XDA). I had a ****ton of proble.s booting a custom kernel/rooted official MIUI. And it was all due to flash order.
In my case it is : 1. Clean flash ROM 2. Boot it 3. Reboot to recovery 4. Change file system to f2fs (data lartition) 5. Flash Kernel/Magisk/DFE (in that order). 6. Reboot to recovery. Done. If you run into more problems booting, i bet it is due to a flash order mistske. So write here, Ill reflash, stay encrypted and check which order it is that these files need to be flashed in so it boots every time.
crazy_4_and1 said:
Well, I use Pitch Black Recovery, as it patches the installation of stock roms so I does not get erased by stock recovery. Then, the softbrick you are talking about is probably caused by flashing a kernel but not disabling dm-verity (that's a requirement if you want a stock rom/custom kernel combo) someone correct me if I'm wrong. So, the order, for a custom kernel install would be 1. Clean flash your ROM, 2. boot it 3. Reboot to recovery and flash the custom kernel 4. Flash dm-verity disabler 5. Reboot to system.
You just need a boot.img file on your sd card/pc, so you can flash just that file if your rom fails to boot.
I keep my phone unencrypted, so i use DFE/DM-verity disabler zip (literally just google it and it will point you to a thread here on XDA). I had a ****ton of proble.s booting a custom kernel/rooted official MIUI. And it was all due to flash order.
In my case it is : 1. Clean flash ROM 2. Boot it 3. Reboot to recovery 4. Change file system to f2fs (data lartition) 5. Flash Kernel/Magisk/DFE (in that order). 6. Reboot to recovery. Done. If you run into more problems booting, i bet it is due to a flash order mistske. So write here, Ill reflash, stay encrypted and check which order it is that these files need to be flashed in so it boots every time.
Click to expand...
Click to collapse
nice reply and thanks for your concerns, i use disable file encryptions but only when flashing magisk ,never expected to use it with custom kernels, but i have one thing bother me, u said that i need "clean flash rom" but i restored my rom using nandroid while i already had broked my phone(if i flashed any custom kernel other than stock kernel)so is my rom ok or not, do i need to flash a new stock rom? and is it recommended if iwant to change the custom kernel later to another custom kernel to flash stock kernel between them? do u have the flash order between custom kernels over stock rom without causing issues? i would like to know if u have any info, and
thanks for ur info that will help me in future!!!
Nasrk said:
nice reply and thanks for your concerns, i use disable file encryptions but only when flashing magisk ,never expected to use it with custom kernels, but i have one thing bother me, u said that i need "clean flash rom" but i restored my rom using nandroid while i already had broked my phone(if i flashed any custom kernel other than stock kernel)so is my rom ok or not, do i need to flash a new stock rom? and is it recommended if iwant to change the custom kernel later to another custom kernel to flash stock kernel between them? do u have the flash order between custom kernels over stock rom without causing issues? i would like to know if u have any info, and
thanks for ur info that will help me in future!!!
Click to expand...
Click to collapse
Not that you need to flash a stock ROM every time, I'd just do it the first "next" time (if you want to be sure you did nothing wrong, once, you NEED to flash a clean installation). I wouldn't know if your backup is fine if I dont know exactly what partitions did you backup and if you backed your system right after the installation.
It is not recommended it is OBLIGATORY to flash the stock kernel between the flashes.
If changing kernels, only, I just flash the stock boot.img, reboot to system to see if all is good, then reboot to recovery and flash the kernel+magisk (I cant remember exactly, but I think you lose root if you flash the stock kernel). Ill make a reminder to check.
crazy_4_and1 said:
Not that you need to flash a stock ROM every time, I'd just do it the first "next" time (if you want to be sure you did nothing wrong, once, you NEED to flash a clean installation). I wouldn't know if your backup is fine if I dont know exactly what partitions did you backup and if you backed your system right after the installation.
It is not recommended it is OBLIGATORY to flash the stock kernel between the flashes.
If changing kernels, only, I just flash the stock boot.img, reboot to system to see if all is good, then reboot to recovery and flash the kernel+magisk (I cant remember exactly, but I think you lose root if you flash the stock kernel). Ill make a reminder to check.
Click to expand...
Click to collapse
iam waiting for your response about root if it get earsed or not
Nasrk said:
iam waiting for your response about root if it get earsed or not
Click to expand...
Click to collapse
With flashing the stock kernel, it does.
Newer custom kernels apply a patch so magisk stays intact
Stock ones do not.