Flashing order? - Nexus 5 Q&A, Help & Troubleshooting

Just curious as to what is the best order for flashing a Custom ROM, Kernel, Gapps and finally Magisk? Would I flash Magisk last to patch the custom kernel?

1. Custom ROM
2. GApps
3. Magisk
4. Kernel (that's the recommended order for blu_spark)

Related

[ROM] Commotio B140 (hiaeuhl)

I didin't know about Commotio until I accidently came across it while searching for the latest Vanir ROM. For what I know, Commotio and Vanir share the same device tree and are much similar. Commotio however releases new functionality in it's ROM's that eventualy might endup in a Vanir ROM. (Anyone, correct me if I'm wrong).
So I got curious and tested Commotio's last build, B140 08202017 for the hiaeuhl. I must say, this is an excellent ROM if your bored with LinageOS. Stable, fast and comes with full OMS support for substratum. During the installation (flash by twrp) it installs the latest stable magisk version by default. I found out that the latest superSU+suhide is much more stable. So I removed magisk and rooted Commotio with SuperSU+suhide, SafetyNet doesn't stand a chance.
Links:
Commotio ROM's for the hiaeuhl here
Magisk removal tool (flashable zip) here
Latest SuperSU by Chainfire (flashable zip) here
Suhide 1.08 by Chainfire (flashable zip) here
Aroma SuperSUconfig 1.00 (flashable zip) here
OpenGApps here
Installation:
1. Clear data and dalvik/cache
2. Flash ROM
3. Flash GApps
4. Remove Magisk or keep it as it is and enjoy your ROM (remove Magisk Manager manually once booted into OS)
5. Flash SuperSUconfig. Choose to disable forced data encryption and install in systemless SBIN mode (important!)
6. Flash latest SuperSU
7. Flash latest suhide
8. Reboot
I want to remind you guys, you have to be on MM firmware with the latest TWRP recovery installed to get this to work.
Enjoy
Some screenshots can be found here
And oh, don't bother me with old threads about Commotio just to point out you remember what you've read two years ago. I'm just trying to keep the forum alive and maybe trigger custom developers to provide us with more ROM's.
My Device Us Unlocked. S-off Rooted. Firmware 2.18.617.30 Nougat 7.0 . How Can I install that Rom ?
Hi
Hi guys i need a help can someone take the nogut version twrp backup for htc one a9 or please make the sense based nogut rom plz.plz
Nuroxy said:
My Device Us Unlocked. S-off Rooted. Firmware 2.18.617.30 Nougat 7.0 . How Can I install that Rom ?
Click to expand...
Click to collapse
first you have to downgrade your firmware to 1.5x or wait for developers to publish a ROM capable of working with 2.X firmware. I have feeling this is gonna take some time. Once set to the right firmware, flash the ROM as you usually do.
eavandijk83 said:
I didin't know about Commotio until I accidently came across it while searching for the latest Vanir ROM. For what I know, Commotio and Vanir share the same device tree and are much similar. Commotio however releases new functionality in it's ROM's that eventualy might endup in a Vanir ROM. (Anyone, correct me if I'm wrong).
So I got curious and tested Commotio's last build, B140 08202017 for the hiaeuhl. I must say, this is an excellent ROM if your bored with LinageOS. Stable, fast and comes with full OMS support for substratum. During the installation (flash by twrp) it installs the latest stable magisk version by default. I found out that the latest superSU+suhide is much more stable. So I removed magisk and rooted Commotio with SuperSU+suhide, SafetyNet doesn't stand a chance.
Links:
Commotio ROM's for the hiaeuhl here
Magisk removal tool (flashable zip) here
Latest SuperSU by Chainfire (flashable zip) here
Suhide 1.08 by Chainfire (flashable zip) here
Aroma SuperSUconfig 1.00 (flashable zip) here
OpenGApps here
Installation:
1. Clear data and dalvik/cache
2. Flash ROM
3. Flash GApps
4. Remove Magisk or keep it as it is and enjoy your ROM (remove Magisk Manager manually once booted into OS)
5. Flash SuperSUconfig. Choose to disable forced data encryption and install in systemless SBIN mode (important!)
6. Flash latest SuperSU
7. Flash latest suhide
8. Reboot
I want to remind you guys, you have to be on MM firmware with the latest TWRP recovery installed to get this to work.
Enjoy
Click to expand...
Click to collapse
How about the camera working on Commotio ??????in lineage os camera is not working properly.and most of 3rd party camera app not working....
Camera is working fine
Tried latest build on 1.56.401 firmware Encryption unsuccesfull error all the time.
Someone know if in this rom with old firmware the hotspot working?
Hey I'm on the new firmware and I've been trying to follow your instructions here and am failing. I am able to follow you till flashing the magisk uninstaller. Then when I use the aroma installer to config su on the first page i select systemless bin mode(explicitly states for >=8.0) then i disable force encryption and click on next and complete config but when i flash the superuserSU.zip it installs the binary files in the /data/ directory and then the suhide fails to install. am I doing something wrong.?
Namaless said:
Someone know if in this rom with old firmware the hotspot working?
Click to expand...
Click to collapse
newest version woking fine .best rom ever :good:

OB10 to custom roms

Hi there, can someone enlighten me how yo flash custom roms?my device already unlocked bootloader and i know how to flash cuz i play with xiaomi mi5, sams galaxy3 , sony x8.
For now i dont have a twrp. Im going twrp by fastboot before this.
Im really sure that i already go through all of the post. But seems from OB10 is really complicated.
1.ready fastboot twrp, bluspark twrp,roms, gapps and magisk( if necessary) and custom kernel
2.fastboot twrp by cmd or else
3.wipe what here? Or just factory reset and leave internal storage?
*Here i confused, do i need to wipe for both slot. Im still new to a/b partition. And do i need to do that for both slot to flash as steps 4-10 as below?
4.flash roms then bluspark twrp
5.reboot to recovery
6.flash gapps,magisk? Then twrp back?
7.reboot to twrp
8.flash custom kernel then twrp again?
9.reboot system
10. End right?
Please help me here. I cant find the real and proper steps. The only way i found is from OB7 to custom roms as they share same security patch.
Thanks for any help.
1. Flash any strock rom.zip partition A.
2. After that recovery.zip
3. Reboot back to recovery
4. Confirm you are in another slot B
5. Flash stock rom.zip. Which slot first is not important.
6. After that flash recovery.zip and then reboot.
After that you can install whatever you want.
That what I do if im switching roms and trying new stuff.
Working everytime.
Until OB7 and stable 9.0.2 I used fasboot roms, flashed via AIO tool, but new fastboot roms working different and I got laggy video and audio.
Okeh thats clear for both slot. But for OB10 to any customs rom is it needed to flash OB7?
What do you mean by stock rom?bete rom or stable rom?
slayerliar said:
Okeh thats clear for both slot. But for OB10 to any customs rom is it needed to flash OB7?
What do you mean by stock rom?bete rom or stable rom?
Click to expand...
Click to collapse
Stock any offical rom for OP6
9.0.2 or 9.0.3 or any OB3,4,5,6,7,8,9,10
If you want custom rom, look instructions, there is mentioned what is base rom. That you need flash.
If there is custom rom based OB7 then you need flash OB7(probably working lower builds also)
Thank brotha. I think they need to state which firmware do we need to start from. Otherwise it will be like me that confusing as they will patch up more and more security.
slayerliar said:
Thank brotha. I think they need to state which firmware do we need to start from. Otherwise it will be like me that confusing as they will patch up more and more security.
Click to expand...
Click to collapse
Pie ROM, pie firmware. (Except pre release betas)
Oreo ROM, Oreo firmware.
ROM - always flash latest firmware of the OS you want pie or Oreo (I always go for latest and don't have any issues . Tho I'm back to oos ,debloated now.)
Twrp - Always after ROMs, before roboot.
Gapps - after twrp and reboot, to make sure it installs to the right slot, that's why you install twrp and then reboot.. this will change your slot from A to B or from B to A. Manual switch is never necessary
Flashing gapps flashes to the slot you are in right now, so flashing before the first reboot (after twrp flash) Will get it to the wrong slot.
Magisk - if you want root. After all.
After all this you can, if you want, flash decrypt ..if you don't need your device to be encrypted,this Will give you more to think of tho.. let's just not go into this now.
i understand the process, but get confused at which file to specifically flash twice when they say
"latest firmware of the OS". So lets say the custom ROM i want to flash needs a PIE firmware 9.0.2 or higher,
what file am i supposed to flash?
9.0.2-PIE-OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9-FASTBOOT.zip
or
OnePlus6Oxygen_22_OTA_027_all_1810260000_d46787d2c9.zip

Losing TWRP and Magisk after update

I'm running stock ROM on unlocked bootloader with root through Magisk. I've been using TWRP, but changed over to Blu_spark TWRP recently.
Every time I update my OS Ota, I lose TWRP and Magisk. The Magisk app is installed, but the ROM is not rooted. If course, if I try to install patch the system so it's rooted through the Magisk app, it says that it can't unpack the file. If I reboot to recovery to install from there, I get the stock recovery, not TWRP.
I tried to re-install TWRP and Magisk once before, and borked my phone. I had to quote and start from scratch. I lost all data since I wasn't rooted and Titanium Backup would not run.
What is the proper way to get TWRP and Magisk back after an OTA update?
Flash them after you flash update zip. If you don't you will lose recovery and root every time. Gets overwritten by stock recovery. Normal behavior
Sent from my ONEPLUS A6003 using Tapatalk
So you're saying that instead of doing the OTA update, I should download the update from here, and manually update it ? Can I just install the update? I'm rooted, (well, I was) so the OTA will only download the full update. Is that required instead of the update?
I really have to do a full re-install for every update? That sucks. A lot.
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
MickyFoley said:
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
Click to expand...
Click to collapse
Ok. Cool. I tried that last time, but it failed. As a result, I'm a bit anxious about doing it again. Hopefully, I won't have any problems this time.
Thanks for the info.
I have had similar troubles as you, here's an overview of how to solve those problems.
OTA through OS:
Download and install OTA
Use Magisk Manager to download the TWRP A/B retention script and install it
Install Magisk to current and inactive slot
Reboot
Guys I am using latest blu_spark twrp. my bootloader is unlocked and I am running oxygenOS openbeta23. Following is my problem.
My flash order: (Note: already I have bue_spark twrp recovery running without issues)
1. Flash the full OTA(openbeta)
2. Flash the blu_spark twrp zip file on both active and non active slots.
3. Flash the latest magisk zip file. If step 3 is not successful means I will try to reboot in to recovery and again flash the magisk installer zip.
Until some time back all this worked fine. But for last 2-3 times although the flashing process of twrp zip on both slots ends with success message, when I reboot to recovery from twrp in order to flash magisk, the device boots in to stock recovery. I don't know how even after flashing twrp zip on both slots successfully why the devices bootbback to stock recovery. Then to have blu_spark twrp I have to connect my device to a computer in fastboot mode and then boot in to custom recovery using the blu_spark twrp image file and again flash the blu_spark twrp zip file which is inconvenient and also requires a computer.
Am I missing anything here?? If yes why this method was working perfectly before? Please somebody help.
Regards,
Sivabalan K
I flash in following order my stable updates
Flash full rom zip
Flash bluespark recovery
Restart into bluespark recovery
Flash magisk
Restart into Android
Everything works flawless. Magisk installed with all the modules running
Hi guys,
Don't you need to disable lock pattern/PIN or fingerprint/face ID? And don't need to uninstall magisk modules?
I never update my OP6 from my initial unlock/twrp/magisk and I'm a bit anxious to do it now...
Thanks
PS : I'm using original twrp (3.2.3-1), is this a problem?

Is there a latest stock ROM I can flash instead of the custom ROM I'm using now?

I'm TWRP'd and Magisk'd running a custom ROM (Havoc}, but it's a little buggy. I'm looking to flash a stock ROM with the latest OxygenOS, and then maybe use a Magisk module over that.
Can I? And if so, can you point me to the correct custom ROM thread? I see a couple, but not sure which one is flashable, and which one is for restoring the phone to completely stock (removing TWRP, etc.).
I suggest using this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
-BoneZ- said:
I see a couple, but not sure which one is flashable, and which one is for restoring the phone to completely stock (removing TWRP, etc.).
Click to expand...
Click to collapse
I don't think you can flash a stock ROM, and keep TWRP without flashing TWRP again. TWRP will always be removed when flashing a stock ROM, since recovery doesn't reside on it's own partition for this device, but rather is on boot.img, which by definition needs to be flashed with the ROM (contains the kernel).
AFAIK, you will need to flash the stock ROM then flash TWRP and Magisk again. To do that, fastboot flash the above linked stock ROM, then fastboot boot TWRP.img, then in TWRP flash TWRP installer zip and flash Magisk. Wouldn't take long to do, just have the TWRP zip and Magisk zip on the phone ready to go, before you flash the stock ROM.
redpoint73 said:
I suggest using this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
I don't think you can flash a stock ROM, and keep TWRP without flashing TWRP again. TWRP will always be removed when flashing a stock ROM, since recovery doesn't reside on it's own partition for this device, but rather is on boot.img, which by definition needs to be flashed with the ROM (contains the kernel).
AFAIK, you will need to flash the stock ROM then flash TWRP and Magisk again. To do that, fastboot flash the above linked stock ROM, then fastboot boot TWRP.img, then in TWRP flash TWRP installer zip and flash Magisk. Wouldn't take long to do, just have the TWRP zip and Magisk zip on the phone ready to go, before you flash the stock ROM.
Click to expand...
Click to collapse
I want to flash havoc OS and want to know if I can go back to OOS if I download the full OTA zip and flash it like you normally would (twrp and magisk)
D.Va said:
I want to flash havoc OS and want to know if I can go back to OOS if I download the full OTA zip and flash it like you normally would (twrp and magisk)
Click to expand...
Click to collapse
I have the same question. I'm on Havoc now and unencrypted and would like to back up Havoc and go back to OOS for now due to WiFi calling not working. With out having to reflash Twrp etc
The_Keeper86 said:
I have the same question. I'm on Havoc now and unencrypted and would like to back up Havoc and go back to OOS for now due to WiFi calling not working. With out having to reflash Twrp etc
Click to expand...
Click to collapse
Anyone?

Magisk with custom kernel

It's been a long time since I've used a custom kernel on any of my devices.
What is the correct installation order:
Custom kernel
Magisk
Or
Magisk
Custom kernel
I am new to this too, but the steps in this guide to add a custom kernel worked for me:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
I've been using blu_spark kernel but I've been installing magisk 1st, and then the kernel on FKM. The script is well made so this doesn't affect now!

Categories

Resources