I don't know what I did but I think it's really serious and important for me to be solved, that's why I am requesting for your help!
As I have reached the of Limit flashing ROMs over and over again, I came to the following occasion:
After casually flashing a new oreo based ROM, having installed also the Gapps, everything was fine for the time being. Suddenly when I tried to flash the magisk manager, from TWRP recovery it was saying that the installation had failed and that magisk failed to mount vendor(never before asked)!
I flashed one or two times stock ROM(miui 9), but I think that it might not be the proper one! For example, there used to be such a problem in the past, but when I slashed stoke MIUI 8 the problem was fixed! I don't know what's going on!
I also get sometimes unusual errors from TWRP and my device seems to be unstable! Do you think that I might have caused a serious problem to my device after flashing and flashing over and over again?
Here is a screenshot: https://drive.google.com/file/d/18xj7Xj3UWWG7NW7N_uOt7iECBMvkoyRP/view?usp=drivesdk
Device: mido
TWRP: any
ROM: any
Magisk: any
**Problem solved**
Steps to solution:
1. Flash latest MIUI from custom recovery or Mi Flash.
2. Boot up and finish the initial set up.
3. Reboot into recovery and flash latest magisk zip file.
4. Reboot and see that magisk manager is installed
5. Then reboot again into TWRP, wipe everything and format data!
6. Flash ROM, GAPPS and then latest magisk manager!
Done!
David_#27 said:
I don't know what I did but I think it's really serious and important for me to be solved, that's why I am requesting for your help!
Click to expand...
Click to collapse
The questions are - which TWRP (and is it standard or Treble); which ROM (and is it standard or Treble)? which Magisk (and is it standard or Treble)?
DarthJabba9 said:
The questions are - which TWRP (and is it standard or Treble); which ROM (and is it standard or Treble)? which Magisk (and is it standard or Treble)?
Click to expand...
Click to collapse
First of all I noticed the problem when I had official TWRP 3.2.1-0, OMNI ROM(Oreo 8.1) and standard magisk manager(v16.0) zip file!
Do you have an SD card in your phone? Maybe that's causing problems.
I don't see why flashing ROMs a lot would cause you many issues. Could even be a hardware issue with your onboard eMMC storage or something else.
David_#27 said:
First of all I noticed the problem when I had official TWRP 3.2.1-0, OMNI ROM(Oreo 8.1) and standard magisk manager(v16.0) zip file!
Click to expand...
Click to collapse
Hmmm ... perhaps you should wipe everything (system, cache, and dalvik) and then format your data partition (which will also wipe your internal SD) and start afresh.
Go back to stock rom using fastboot method or MiFlash tool, that way you'll go back to complete stock and it maybe able to solve your problem
@DarthJabba9 and @rrgreatvijay5, thanks a lot for you're help, but I've already tried both of the methods you provide me! Maybe it is a hardware issue like @sk8223 says...
But, I won't quit till I find the solution to this problem!
The hardware is FINE! FIY, we were together when we were flashing, so let me provide some additional info.
We flashed the latest Dev ROM that was available, the one from the 29th of March. Everything flashed successfully, MIUI, TWRP, ROMs, other mods, etc. Only Magisk has issues so this is in no way a hardware issue. The worst thing that could have happened would be to mess up the partitions on your emmc, but that is extremely unlikely and can be fixed.
The question we should be asking here is what firmware do most people use? We'll just download and flash that.
Thanks all for your help!
---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------
sk8223 said:
Do you have an SD card in your phone? Maybe that's causing problems.
I don't see why flashing ROMs a lot would cause you many issues. Could even be a hardware issue with your onboard eMMC storage or something else.
Click to expand...
Click to collapse
That's a good point. Not the emmc part, but the SD part. Try moving the Magisk zip to the root of your internal storage.
chrismin13 said:
The hardware is FINE! FIY, we were together when we were flashing, so let me provide some additional info.
We flashed the latest Dev ROM that was available, the one from the 29th of March. Everything flashed successfully, MIUI, TWRP, ROMs, other mods, etc. Only Magisk has issues so this is in no way a hardware issue. The worst thing that could have happened would be to mess up the partitions on your emmc, but that is extremely unlikely and can be fixed.
The question we should be asking here is what firmware do most people use? We'll just download and flash that.
Thanks all for your help!
---------- Post added at 12:25 PM ---------- Previous post was at 12:23 PM ----------
That's a good point. Not the emmc part, but the SD part. Try moving the Magisk zip to the root of your internal storage.
Click to expand...
Click to collapse
That's exactly what I meant! Thank you Chris!
So guys what firmware do you use in order to flash custom roms?
David_#27 said:
So guys what firmware do you use in order to flash custom roms?
Click to expand...
Click to collapse
You may try any of these, i usually flash latest one.
https://androidfilehost.com/?w=files&flid=236737
Edit: If you have already tried fastboot flashing method, my guess would be your firmware has already restored to stock, so it wont make any difference, but still give it a shot
Did you by any chance change the partitions fro F2FS to EXT4? Could that cause problems?
sk8223 said:
Did you by any chance change the partitions fro F2FS to EXT4? Could that cause problems?
Click to expand...
Click to collapse
No I didn't... The partitions is already ext4 formatted!
sk8223 said:
Did you by any chance change the partitions fro F2FS to EXT4? Could that cause problems?
Click to expand...
Click to collapse
Correct me if I'm wrong, but all partitions on mido are ext4. AFAIK, he has never changed any partitions to F2FS. Still, going back to stock would revert that and we have done that already a couple of times.
@David_#27 Let's try going back to stock again and flashing Magisk on MIUI, just to be sure.
chrismin13 said:
Correct me if I'm wrong, but all partitions on mido are ext4. AFAIK, he has never changed any partitions to F2FS. Still, going back to stock would revert that and we have done that already a couple of times.
@David_#27 Let's try going back to stock again and flashing Magisk on MIUI, just to be sure.
Click to expand...
Click to collapse
Very good idea dude! I will give it a shot!
I don't think this could have been the solution since magisk basically patches the boot image and that is different for all the roms (it comes with the rom). Oreo is a treble built and i suppose magisk doesn't support it as of now, the second time you flashed the rom (after flashing miui) was it a nougat based rom???.
Although I found a link to a custom magisk made for treble builds {https://forum.xda-developers.com/project-treble/trebleenabled-device-development/unofficial-treble-enabled-resurrection-t3761279}. But I tried it and it didn't work for me. So I guess we will have to wait for @topjohnwu to release treble support. Correct me if I a wrong
Maximus909 said:
I don't think this could have been the solution since magisk basically patches the boot image and that is different for all the roms (it comes with the rom). Oreo is a treble built and i suppose magisk doesn't support it as of now, the second time you flashed the rom (after flashing miui) was it a nougat based rom???.
Although I found a link to a custom magisk made for treble builds {https://forum.xda-developers.com/project-treble/trebleenabled-device-development/unofficial-treble-enabled-resurrection-t3761279}. But I tried it and it didn't work for me. So I guess we will have to wait for @topjohnwu to release treble support. Correct me if I a wrong
Click to expand...
Click to collapse
Just flash casually this one: https://drive.google.com/file/d/1Agu5zLOi5U37Ri8-fGFNOre2LY32_WGX/view?usp=drivesdk
If the problem remains, you should flash latest stock ROM, using TWRP or MiFlash and then try it all over again!
David_#27 said:
Just flash casually this one: https://drive.google.com/file/d/1Agu5zLOi5U37Ri8-fGFNOre2LY32_WGX/view?usp=drivesdk
If the problem remains, you should flash latest stock ROM, using TWRP or MiFlash and then try it all over again!
Click to expand...
Click to collapse
I am about to try 16.4 treble built...found the link after a bit of digging... If it works (or it doesn't) I will update, also using the redwolf treble built recovery, checking if that helps....
David_#27 said:
Just flash casually this one: https://drive.google.com/file/d/1Agu5zLOi5U37Ri8-fGFNOre2LY32_WGX/view?usp=drivesdk
If the problem remains, you should flash latest stock ROM, using TWRP or MiFlash and then try it all over again!
Click to expand...
Click to collapse
All right so all done, and succeful this time. Now the problem was actually with the recovery and not magisk itself.... So what we need to do is flash redwolf recovery for tteble builds and download treble compatible 16.4 magisk version. I tried flashing through standard twrp but failed so we need this treble build :good:
Redwolf Recovery {treble build, for MIDO ONLY} : https://androidfilehost.com/?fid=746010030569954397 .
Magisk 16.4 modded : https://androidfilehost.com/?fid=962187416754478287 .
Related
Hai.
I have a galaxy note 3 sm n9005. Have already rooted by finding forum from xda and even install twrp recovery following the guides given.
But im trying to install custom rom. And tried all the roms tat is given from xda for note 3 and could install single one.
Please help to resolve this problem. Im confuse.
Tq.
Not enough details.
It's probably the version of recovery you're using.
Which version of TWRP and what errors are you receiving?
es0tericcha0s said:
Not enough details.
It's probably the version of recovery you're using.
Which version of TWRP and what errors are you receiving?
Click to expand...
Click to collapse
Im using twrp 3.0.2.1 and everytime i try to install a rom it stuck at samsung screen.
And it show md5 not found.
What roms have you tried? What firmware were you on before you started flashing? Sometimes newer roms need the newest firmware like the bootloader and modem to run correctly. Are you wiping system, data, and both caches? If you are going from a Touchwiz rom to, say, a CM based, it might also be necessary to wipe the internal storage. Of course you should back all that up to a PC first, if you do that.
es0tericcha0s said:
What roms have you tried? What firmware were you on before you started flashing? Sometimes newer roms need the newest firmware like the bootloader and modem to run correctly. Are you wiping system, data, and both caches? If you are going from a Touchwiz rom to, say, a CM based, it might also be necessary to wipe the internal storage. Of course you should back all that up to a PC first, if you do that.
Click to expand...
Click to collapse
Resurrection remix.unicorn.slim.and all cynogen rom is working. Im trying install s7edge custom rom for darkwolf and darklord. I even updated the bootloader and modem according to tutorial. I used odin to flash them..
N9005xxugboa1
Lrx21v.n9005xxugbob6
I have my stock rom n internl backed up. I try all. And still it always stuck on samsung screen.
Are you installing the kernel after the rom flash? A lot of newer Samsung roms don't have the kernel built in like CM roms.
es0tericcha0s said:
Are you installing the kernel after the rom flash? A lot of newer Samsung roms don't have the kernel built in like CM roms.
Click to expand...
Click to collapse
How can install kernel after. Everytime i install it reboots its self to samsung screen. Or should go back to recovery and install the kernel back. And thank you for your help till now.
That's definitely why it's not booting, if you didn't do the kernel. If the rom has the Aroma installer, typically the last question asks if you want to reboot now and has a check mark in by default. Just uncheck and it'll go back to recovery. But you can also just go back and flash now and should be good.
es0tericcha0s said:
That's definitely why it's not booting, if you didn't do the kernel. If the rom has the Aroma installer, typically the last question asks if you want to reboot now and has a check mark in by default. Just uncheck and it'll go back to recovery. But you can also just go back and flash now and should be good.
Click to expand...
Click to collapse
I have uncheck the reboot after install. When i install the rom it automatically reboot itself. It doesnt show anything or show done. Once it even show os not found.
Hi
Where can i install or find the latest kernel
It's in the installation instructions for the rom.
es0tericcha0s said:
It's in the installation instructions for the rom.
Click to expand...
Click to collapse
Hi.
I have found the bootloader and modem for my sm n9005 from the installation instruction for the rom.
I try to flash according to the tutorial.and my baseband didnt change. I try flash using odin 3times.
Im not sure where i did wrong.can u help me
Tq
Remove the battery for 10 seconds. Put it back in and reboot to download mode. Uncheck auto reboot. Flash then check auto reboot and flash again. Should stick.
tq
es0tericcha0s said:
Remove the battery for 10 seconds. Put it back in and reboot to download mode. Uncheck auto reboot. Flash then check auto reboot and flash again. Should stick.
Click to expand...
Click to collapse
Tq
Will try and let you know
sitijohn85 said:
Tq
Will try and let you know
Click to expand...
Click to collapse
Hi
I tried as said and it didnt chnge.
Can i ask bootloader should be at bl and modem should be at cp. Is it correct.
Hi
Thank you for your help.
I did the change on bootloader and modem.
Now im i need to know two more thing.
I download 2 dffernt kind of bootloader n modem.
I flash blxxxxxbpb1 and cpxxxxxboj1..this 2 files were tar.md5 files
Another one which i didnt flash. Blxxxxxxbpb1 and cpxxxxxxxbpb2..this 2 files are tar.tar files..
Can i know whats the different with this 2 files.
One more thing is when i chnge the bootloader and modem will the kernel changes. Or is it different.
Please guide me..im confuse.
Someone might have just mislabeled them. Flashing those will not affect kernel. Different partition of the phone.
Hi
I did change the bootloader n modem.
And even change the kernel as told in the forum. It was note5 port kernel.7.1.0..
After trying to install the darkwolf rom.it was still the same..it did not work.
Please help me
sitijohn85 said:
Hi
I did change the bootloader n modem.
And even change the kernel as told in the forum. It was note5 port kernel.7.1.0..
After trying to install the darkwolf rom.it was still the same..it did not work.
Please help me
Click to expand...
Click to collapse
This is the recommended kernel
https://www.androidfilehost.com/?fid=24572369242687310
Recommended recovery is TWRP 2.8.7.0 not the newer 3.0+
Flash other recovery. Boot to TWRP. Wipe system, data, cache, dalvik. Flash rom. Wipe caches. Flash kernel. Reboot. Should work according to lots of people on the thread for that rom.
Hi.
How flash kernel.
just flash the tar.md5 file or the tar.zip file
My mother uses the stock i9100, form the french provider buygues, kernel 3.0.31, and want the update android 6 for this phone. I do not know much about android, and all the information here is in english so it is even harder to figure what files to download.
I went to the official thread for cm13, but they do not say how to start from stock. they say that I need some stock rom+root, like the closed thread here, but the files are deleted by a moderator,
http://forum.xda-developers.com/galaxy-s2/help/guide-26-12-flash-stock-firmware-rom-t2365701
I downloaded odin and the samsung drivers, then the latest official cm13. i work on windows 8.1
So where do I get the files to root the phone on android 4.1.2, then I guess the recovery twrp in order to install cm13 ?
I won't give you detailed infos because i just don't remember them well anymore.
But the basic workflow AFAIR is to root the phone, have a custom kernel which support your rom AND iso rec twrp (i think Dorimanx should do).
Then you need to repartition your phone using Lanchon method, but to do so you need to flash iso rec twrp. Then you flash the Lanchon script for increasing the system partition to 1gb.YOU MUST KEEP THE PRELOAD PARTITION as cm13 need it.
Then flash cm13 and pico gapps in one go.
Don't reboot but reflash the iso rec twrp (not sure if really needed) and reboot recovery.
Reboot system and wait (1st boot can take up to 20 minutes)
As you see it is a long go and I advise to read a lot here before trying this.
In particular check the iso rec twrp thread and the Lanchon repit thread here on xda (just google them)
Good luck
Yeah I managed to install Cm13 with twrp up to date. I had to use odin, install cm12.1 and
the file kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100-for-ODIN
then recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100-WITH-PRELOAD-SUPPORT
then lanchon-repit-20160406-system=1.0-data=same-sdcard=max-preload=min+wipe-i9100
Ok, great and nice to know preload set as min works.
blue whale said:
Yeah I managed to install Cm13 with twrp up to date. I had to use odin, install cm12.1 and
the file kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100-for-ODIN
then recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100-WITH-PRELOAD-SUPPORT
then lanchon-repit-20160406-system=1.0-data=same-sdcard=max-preload=min+wipe-i9100
Click to expand...
Click to collapse
You succeeded which is fine. But just a comment:
you wouldn't have needed the recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100-WITH-PRELOAD-SUPPORT.zip, if you use the lanchon-repit-xxxxxxxx-i9100.zip for repartitioning, as this tool will always take care of the formatting anyway (either keeping or wipeing it). I made that "special" recovery to allow the formatting for ODIN-with-pitfile-users in a gui. So the official unmodded TWRP would have done it as well for your described way.
And actually I would have a second comment:
There are also ways to do all that without ODIN, just in case you don't like the yellow triangle. Maybe I'll put the information on that together one day, as I find it much more comfortable not to depend on an USB-connection (with a possible slack joint) and to run everything right on the phone.
blue whale said:
Yeah I managed to install Cm13 with twrp up to date. I had to use odin, install cm12.1 and
the file kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100-for-ODIN
then recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100-WITH-PRELOAD-SUPPORT
then lanchon-repit-20160406-system=1.0-data=same-sdcard=max-preload=min+wipe-i9100
Click to expand...
Click to collapse
I managed to install CM 12.1, stable version on my galaxy S2. Now I have standard CyanogenMod Recovery.
I wanted to install CM13 but I wasn't able to do it. I don't know how to install, TWRP recovery. I've downloaded all the necessary files, flashed the file "kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100-for-ODIN" using Odin 3.07 and then my phone entered in a bootloop. Now I reflashed stock rom because i didn't know what to do.
Please, can you, or someone make an explicit step by step, NOOB STYLE, guide to upgrade from CM 12.1 to CM13?
I followed many tutorials and I`m still stuck at replacing CWM recovery with TWRP. Please Help!
andrei.bg said:
Please, can you, or someone make an explicit step by step, NOOB STYLE, guide to upgrade from CM 12.1 to CM13?
Click to expand...
Click to collapse
Exactly for that, there is the most comprehensive one here already:
[GUIDE][NOOB-FRIENDLY]Want to update to CM13? Read this first!
If you read its first three posts and you don't manage to do it, no guide will make you do it...
andrei.bg said:
I managed to install CM 12.1, stable version on my galaxy S2. Now I have standard CyanogenMod Recovery.
I wanted to install CM13 but I wasn't able to do it. I don't know how to install, TWRP recovery. I've downloaded all the necessary files, flashed the file "kernel-Lanchon-TRIM-IsoRec-20160111-cm-12.1-i9100-for-ODIN" using Odin 3.07 and then my phone entered in a bootloop. Now I reflashed stock rom because i didn't know what to do.
Please, can you, or someone make an explicit step by step, NOOB STYLE, guide to upgrade from CM 12.1 to CM13?
I followed many tutorials and I`m still stuck at replacing CWM recovery with TWRP. Please Help!
Click to expand...
Click to collapse
I remember installing ''recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100-WITH-PRELOAD-SUPPORT'' with odin 3.07 (section pda??), after I installed cm 12.1 from
http://galaxys2update.com/
then do not forget to install the zip file,
lanchon-repit-20160406-system=1.0-data=same-sdcard=max-preload=min+wipe-i9100
from within TWRP, to resize your partition and it takes a while
then install CM13, then ''erase davik cache'' and pico gapps and erase ''davik cache''
blue whale said:
I remember installing ''recovery-the.gangster-IsoRec-TWRP-3.0.2-1-i9100-WITH-PRELOAD-SUPPORT'' with odin 3.07 (section pda??), after I installed cm 12.1 from
http://galaxys2update.com/
then do not forget to install the zip file,
lanchon-repit-20160406-system=1.0-data=same-sdcard=max-preload=min+wipe-i9100
from within TWRP, to resize your partition and it takes a while
then install CM13, then ''erase davik cache'' and pico gapps and erase ''davik cache''
Click to expand...
Click to collapse
No need to install twrp with preload as the @the.gangster provided also a twrp 3.0.2-1.zip. without preload support.
And: zip files can be flashed in Recovery and not with Odin (only as tar-file e.g. xxx recovery.tar in PDA)
And when flashing the lanchon latest zip file i would also recommend to increase data (1.0GB system and 4.0GB data).
And as the.gangster said before he has to read the recommended Guide.
It doesn't make sense to flash all sort of things without knowing how to .....
Sent from my ME173X using XDA-Developers mobile app
Here is what you are looking for, suis mon tuto :
https://forum.xda-developers.com/galaxy-s2/help/guide-tutorial-samsung-galaxy-s2-i9100-t3538601
Without Odin, flash Recovery, Kernel, Re-partiton and flash CM13
Hello again, and thank you all for the great community xda has become.
I managed to install CM 13 on my S2 a few months ago.
I find it kinda slow....
anyway.... taking in mind that for cm 13 we had to repit to gain extra space...what are the steps for going back to stock?
Thank you!
andrei.bg said:
Hello again, and thank you all for the great community xda has become.
I managed to install CM 13 on my S2 a few months ago.
I find it kinda slow....
anyway.... taking in mind that for cm 13 we had to repit to gain extra space...what are the steps for going back to stock?
Thank you!
Click to expand...
Click to collapse
You have to repit again with the original pit file or a pit that includes a 512mb preload partition, choose your desired pit from this zip but it must have preload 512mb in its name,
1.5GB PIT Files
, the zip includes one pit with 1.5gb system and a very small preload partition, this one is useless for your condition, the other pits are also 1.5gb system but all with 512mb preload partition, except for one pit that is the STOCK pit that sets the partitions to its original state, i recommend using one of the 1.5gb system with 512mb preload, because it's suitable for the stock rom and any other rom even cm13 and LineageOS 14.1, you may change your mind after all, there are plenty of roms to try
Regards Migo
PROBLEM SOLVED, THANK YOU !
Hi.
I just recently rooted my Honor 5X (KIW-UL00 , it's the chinese model)
I then tried installing a custom ROM, the LineageOS. Problem being that I was stuck in a weird BootLoot. When I rebooted the system, it showed me the usual Honor page for like 4-5 seconds, then the loading screen for LineageOS. After like 10 seconds, the animation stopped, the thing crashed and my phone restarted to the Honor page, then Lineage, then crash ... So I booted my phone with TWRP, tried Wiping the Cache and System and started over again with installing Lineage. The same thing happened. I then tried with 3 other custom ROM'S and the same thing happened. I don't know what I did wrong, I am wiping my cache and Dalvic each time, but I can't figure out what to do.
I'm looking for someone who could help me fix this. I am thinking about flashing the stock ROM, I just don't know how to do it, because it seems different than the custom ROM'S
PS: I'm looking for a kick fix, because I kinda really need my phone xD
Thank you!
Ok so, quick update, I got rid of TWRP by flashing the stock recovery over it. I tried to follow this:
https://forum.xda-developers.com/honor-5x/help/honor-5x-kiw-ul00-boot-loop-t3449554
(DigiGoon's first answer) but it told me that the installation failed.
So in short, my phone is actually in a endless bootloob, trying to boot no ROM, because the're none.
what's the stock system version you were running before you flashed the custom rom? B418 is the latest non VoLTE firmware.
It was Marshmallow 6.0.1... I found my mistake
We can't downgrade using the SD card method and I was trying to install 5.0
Now I need to find the stock version for the KIW-UL00 6.0.1
you can downgrade with the help of hisuite by huawei.
if your stock system was above B422, you can use this patch to stop the bootloop,
just flash the file in twrp after you flash the rom. https://mega.nz/#!tK51gDRL!S9oYLBTeFDbN0hOCzt5jQ5DYECObFC08YMr-Kml6scc
Problem is that I dont have any ROM or custom recovery running on my phone. I can only acess the bootloader, the eRecovery (that for some magical reasons, doesn't work for me) and the SD card installer, that also doesnt work because the only thing I can find is a UPDATE.APP that is on 5.0, when my phone was on 6.0.1, which doesn't work.
HiSuite doesn't even connect and I don't know what VolTE is, can you explain?
Can someone can help me in finding the Stock ROM for KIW-UL00 (the chinese version of Honor 5x) on android 6.0.1. I can find those for every country except china...
EDIT, I was able to get back on TWRP, so I can add files in my phone
haubudam, i freaking love you dude, you saved me
Thank you SOOOOOOO much
haubudam said:
you can downgrade with the help of hisuite by huawei.
if your stock system was above B422, you can use this patch to stop the bootloop,
just flash the file in twrp after you flash the rom. https://mega.nz/#!tK51gDRL!S9oYLBTeFDbN0hOCzt5jQ5DYECObFC08YMr-Kml6scc
Click to expand...
Click to collapse
Thanks man. I was also stuck up in the same problem for a day and flashing BaPatch.zip solved the issue.
Uvneshkumar said:
Thanks man. I was also stuck up in the same problem for a day and flashing BaPatch.zip solved the issue.
Click to expand...
Click to collapse
Can u send me the screenshot of files in zip?
gopinaidu77 said:
Can u send me the screenshot of files in zip?
Click to expand...
Click to collapse
https://mega.nz/#!tK51gDRL!S9oYLBTeFDbN0hOCzt5jQ5DYECObFC08YMr-Kml6scc
Uvneshkumar said:
https://mega.nz/#!tK51gDRL!S9oYLBTeFDbN0hOCzt5jQ5DYECObFC08YMr-Kml6scc
Click to expand...
Click to collapse
Thank you
haubudam said:
you can downgrade with the help of hisuite by huawei.
if your stock system was above B422, you can use this patch to stop the bootloop,
just flash the file in twrp after you flash the rom.
Click to expand...
Click to collapse
My version of the firmware is B245. Your patch did not help me, there is no newer version of firmware for KISH-UL00 than 245. What should I do?
Sodomit666 said:
My version of the firmware is B245. Your patch did not help me, there is no newer version of firmware for KISH-UL00 than 245. What should I do?
Click to expand...
Click to collapse
It was necessary to update the stock firmware to the latest version and then flash custom.
guys want to flash twrp to flash notification zip but am confused about few thing can you guys can help if the possible explanation in simple words will be appreciated
1: I read my data will get encrypted (what is this thing all about ) what encryption means i mean i know what encryption is in general but what does it mean here and how will it affect me i dont care if my user data get deleted when i flash but i dont wana get bootloop or soft brick
2: any proper noob friendly tutorial
3: can i flash global beta through twrp i dont want root etc just twrp
4 : can i retain twrp after i install global beta without root and magisk
5 : isnt there any portable twrp which i can boot to to flash that zip and all back to normal mean stock recovery
Check this out. Twrp is not official yet, but can use force encryption disabler to keep TWRP work on next reboot to recovery. So far no problem to flash rom via twrp.
https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
thomas140 said:
Check this out. Twrp is not official yet, but can use force encryption disabler to keep TWRP work on next reboot to recovery. So far no problem to flash rom via twrp.
https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
Click to expand...
Click to collapse
thnax for the reply ut that is what my confusion is what dycription means and how it effects
bravo2526 said:
thnax for the reply ut that is what my confusion is what dycription means and how it effects
Click to expand...
Click to collapse
For what I know, if you boot into twrp via fastboot, it will be encrypted back to stock recovery if you don't install the force encryption disabler.
Meaning that, this force encryption disabler is to help to keep the twrp recovery.
thomas140 said:
For what I know, if you boot into twrp via fastboot, it will be encrypted back to stock recovery if you don't install the force encryption disabler.
Meaning that, this force encryption disabler is to help to keep the twrp recovery.
Click to expand...
Click to collapse
o yes its making sense now so if i dont use encryption disabler it will return me to stock recovary. and i f i do it will keep the twrp. ok if it is the case then what will happen if i flash twrp and flash that notification zip and reboot it without that encryption disabler will my phone will be reset or not on next boot
bravo2526 said:
o yes its making sense now so if i dont use encryption disabler it will return me to stock recovary. and i f i do it will keep the twrp. ok if it is the case then what will happen if i flash twrp and flash that notification zip and reboot it without that encryption disabler will my phone will be reset or not on next boot
Click to expand...
Click to collapse
Shouldn't need to reset, just that when you go to next reboot recovery, stock recovery will haunt you.hahaha...
thomas140 said:
Shouldn't need to reset, just that when you go to next reboot recovery, stock recovery will haunt you.hahaha...
Click to expand...
Click to collapse
lolz haunt in good or bad way?
bravo2526 said:
lolz haunt in good or bad way?
Click to expand...
Click to collapse
Well, There's no good and bad when you still can boot as per normal, just that the recovery will be different, either twrp or stock though...
Use the one with working decryption so you don't have to worry about it. Forget every other Recovery and the Encryption Disabler, it just makes things complicated and it's an out-of-date work around for other Recovery's which aren't fixed yet.
If you use official MIUI then you will need to reflash or boot TWRP again if you want to use it, because stock Recovery will replace TWRP when you boot official MIUI. This isn't so bad because it keeps OTA working (unless you flashed Magisk of course, which will need to be uninstalled first before OTA).
CosmicDan said:
Use the one with working decryption so you don't have to worry about it. Forget every other Recovery and the Encryption Disabler, it just makes things complicated and it's an out-of-date work around for other Recovery's which aren't fixed yet.
If you use official MIUI then you will need to reflash or boot TWRP again if you want to use it, because stock Recovery will replace TWRP when you boot official MIUI. This isn't so bad because it keeps OTA working (unless you flashed Magisk of course, which will need to be uninstalled first before OTA).
Click to expand...
Click to collapse
Does this link ok to go for since it mention with working decryption?
https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004
Now I am still using the version that needs the disabler, can I just reflash the new twrp file, clear dalvik cache?
thomas140 said:
Does this link ok to go for since it mention with working decryption?
https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004
Now I am still using the version that needs the disabler, can I just reflash the new twrp file, clear dalvik cache?
Click to expand...
Click to collapse
You can dirty flash the recovery over the one you currently have, it won't affect your phone at all. Keep in mind though that your device will stay decrypted, you'll have to encrypt it manually via the phone settings.
franz said:
You can dirty flash the recovery over the one you currently have, it won't affect your phone at all. Keep in mind though that your device will stay decrypted, you'll have to encrypt it manually via the phone settings.
Click to expand...
Click to collapse
Interesting, if stay decrypted, that's fine as the twrp will continue stay for future reboot to receovery.
You said that can manually encrypt via phone setting, but how to do that?
thomas140 said:
Well, There's no good and bad when you still can boot as per normal, just that the recovery will be different, either twrp or stock though...
Click to expand...
Click to collapse
so refreshing to know. The only thing that haunts is boot loop to which we non-tech guys are afraid of and technical guys assume that every one knows the basics and hence the confusion occurs as no clear guide becomes available in new days of any mobile launch waiting a noob friendly thread for poco which might explain these in an order but thanx for the time you took to clear a bit
thomas140 said:
Interesting, if stay decrypted, that's fine as the twrp will continue stay for future reboot to receovery.
You said that can manually encrypt via phone setting, but how to do that?
Click to expand...
Click to collapse
yeah its interesting to know i mean why its needed or y will anyone will encypt it again. any scenario ?
bravo2526 said:
yeah its interesting to know i mean why its needed or y will anyone will encypt it again. any scenario ?
Click to expand...
Click to collapse
Perhaps, break up with the mistress (TWRP) and go back to the wife/husband(Stock recovery)? :laugh:
thomas140 said:
Perhaps, break up with the mistress (TWRP) and go back to the wife/husband(Stock recovery)? :laugh:
Click to expand...
Click to collapse
lolz you are funny so you are tempting us to keep mistress no problem if it locks your wealth(data) . meanwhile, global beta 8.10.25 is up for twrp anyone tried?
bravo2526 said:
lolz you are funny so you are tempting us to keep mistress no problem if it locks your wealth(data) . meanwhile, global beta 8.10.25 is up for twrp anyone tried?
Click to expand...
Click to collapse
No idea, I am still stick with miui global 9.6.25. haha
ps: I have no mistress but I have a wife:laugh:
bravo2526 said:
guys want to flash twrp to flash notification zip but am confused about few thing can you guys can help if the possible explanation in simple words will be appreciated
1: I read my data will get encrypted (what is this thing all about ) what encryption means i mean i know what encryption is in general but what does it mean here and how will it affect me i dont care if my user data get deleted when i flash but i dont wana get bootloop or soft brick
2: any proper noob friendly tutorial
3: can i flash global beta through twrp i dont want root etc just twrp
4 : can i retain twrp after i install global beta without root and magisk
5 : isnt there any portable twrp which i can boot to to flash that zip and all back to normal mean stock recovery
Click to expand...
Click to collapse
The simplest option for u is to download twrp with working encryption.
Dont flash it , just boot into recovery by fastboot command thru adb.
Flash whatever u want to and once done flashing , reboot and u will boot with stock recovery. That way for stock roms u can update via OTA also.
There's a thread in Q&A , will post the link in some time , would suggest u read it.
https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-root-unlock-bootloader-t3852520
thomas140 said:
Does this link ok to go for since it mention with working decryption?
https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004
Now I am still using the version that needs the disabler, can I just reflash the new twrp file, clear dalvik cache?
Click to expand...
Click to collapse
That's the only one last I checked, yes that's it.
You will need to reflash stock ROM (actually just vendor) if you want to enable encryption enforcement again in your ROM.
CosmicDan said:
That's the only one last I checked, yes that's it.
You will need to reflash stock ROM (actually just vendor) if you want to enable encryption enforcement again in your ROM.
Click to expand...
Click to collapse
Hmm..
My current info:
Mini 9.6.25
Twrp (need to flash with Force encryption Disabler)
So here's my step to do:
Download the twrp with decryption enabled.
Download same stock rom.
Flash the stock rom
Flash the new twrp I downloaded.
That's all?
Will it be asking for password and stuff? Because as I know if it happens, I need to wipe data, right?
Another scenario, if I am going to flash miui 10 beta or stable in the future, I need to wipe data to get it work after flash?
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.