Hello I am currently running lineage os 14 on my phone with a custom kernel installed and want to install magisk but I have read that you need to flash the kernel after flashing magisk but I don't want to lose my data. Therefor I am thinking about first flashing magisk and then emidlity after that flashing my kernel again. Would that work or could some problem occur.
If you have TWRP on your device, try backup everything and then flash magisk
1. Wipe dalvik & cache
2. Dirty flash your rom
3. 1 & boot into os
4. flash magisk & 3
5. flash your custom kernel & 1
I forgot about this rule and added magisk with the custom kernel already in place. Have I already lucked out or is the pain yet to come? Should I remove magisk before applying my next rom update?
Epilogue: updated rom, wiped caches, and everything turned out fine.
Fdraco10 said:
If you have TWRP on your device, try backup everything and then flash magisk
Click to expand...
Click to collapse
so you've got perfect battery life using glassfish? can I ask how
Related
So I downgraded my Oneplus 3 from 3.5.2 to 3.2.6 and this was kind of a painful process, so I decided to share my experience with you.
If you follow this guide you will successfully downgrade from the latest Community Build to the newly released stable.
Note: Just because this worked for me, doesn't mean that it will work for you! Use this guide on your own risk and always use backups!
You'll need:
- Oneplus with OOS 3.5.2 and modified TWRP
- OxygenOS 3.2.6 Full ROM
- Latest official TWRP
- AndroidSDKSlim (needs Oneplus 3 USB drivers installed)
- SuperSU 2.78 SR1
- Xposed Framework (optional)
- Debloat Script (optional)
Downgrade:
Before you start, please create a COMPLETE backup of all your data.
You will factory reset your phone during the process.
1. Copy OOS 3.2.6 Full ROM, SuperSU, Xposed, Debloat Script to your Oneplus
2. Flash modified TWRP if you haven't already
3. Boot into modified TWRP
4. Select Wipe -> Advanced Wipe -> Select all but internal storage -> Swipe to Wipe
5. Install OOS 3.2.6 Full ROM
6. Reboot into system and use the installation wizard to setup your phone (do not setup fingerprints, or any device PIN)
7. Reboot into bootloader
8. Connect your phone to a PC/Notebook
9. Extract AndroidSDKSlim to your Desktop and copy twrp-3.0.2-1-oneplus3.img into \AndroidSDKSlim\android-sdk-windows\platform-tools
10. Run CMD with admin rights and navigate to \AndroidSDKSlim\android-sdk-windows\platform-tools
11. Run "fastboot flash recovery twrp-3.0.2-1-oneplus3.img" to revert to official TWRP recovery
12. Disconnect your phone and boot into recovery
13. Dirty flash OOS 3.2.6 again (this might sound stupid but it's mandatory)
14. Still in recovery, flash SuperSU, Xposed and Debloat Script
15. Wipe Dalvik & Cache
16. Reboot into system and setup your phone
Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?
darkbash said:
Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?
Click to expand...
Click to collapse
You're welcome.
Unfortunately, I can't provide guides for procedures I never went through.
But I asume that you could just flash any Custom ROM after you completely wiped your phone in step 4. So instead of flashing OOS 3.2.6 afterwards, just flash a custom ROM. Be sure that you have all zips you need on your internal storage and a backup to revert back to, if anything goes wrong. Otherwise you will have to use ADB sideload to install a ROM.
Ok, so I have a Modified TWRP installed already. Question is If I want to flash other ROMS after wiping system,dalvik/cache,data etc. Do I have to Flash official TWRP first followed by firmware,ROM, etc?
or firmware first then ROM and lastly official TWRP?
it's quite confusing.
I made a mistake and I installed the modified recovery installed the 3.5.2 rom and before booting I decided to restore my nand backup so I flashed the official twrp recovery and now I can't go to recovery anymore and the phone doesn't boot.
I imagine I have to sideload the modified twrp again but how do I do that? How do I reboot to bootloader ?
This is the only sign of life
gigeaky said:
I made a mistake and I installed the modified recovery installed the 3.5.2 rom and before booting I decided to restore my nand backup so I flashed the official twrp recovery and now I can't go to recovery anymore and the phone doesn't boot.
I imagine I have to sideload the modified twrp again but how do I do that? How do I reboot to bootloader ?
This is the only sign of life
Click to expand...
Click to collapse
Flash modified TWRP, and the recovery will return. then, follow the guide. it happened to me too.
darkbash said:
Thanks for your guide !
Can you just please detail how to revert back to a custom ROM like RR or Nuclear when we come from Oxygen OS 3.5.2 community build ?
Click to expand...
Click to collapse
First flash modified TWRP than install official 3.2.4 than flash CM ROM or custom ROM
uniQ191 said:
So I downgraded my Oneplus 3 from 3.5.2 to 3.2.6 and this was kind of a painful process, so I decided to share my experience with you.
If you follow this guide you will successfully downgrade from the latest Community Build to the newly released stable.
Note: Just because this worked for me, doesn't mean that it will work for you! Use this guide on your own risk and always use backups!
You'll need:
- Oneplus with OOS 3.5.2 and modified TWRP
- OxygenOS 3.2.6 Full ROM
- Latest official TWRP
- AndroidSDKSlim (needs Oneplus 3 USB drivers installed)
- SuperSU 2.78 SR1
- Xposed Framework (optional)
- Debloat Script (optional)
Downgrade:
Before you start, please create a COMPLETE backup of all your data.
You will factory reset your phone during the process.
1. Copy OOS 3.2.6 Full ROM, SuperSU, Xposed, Debloat Script to your Oneplus
2. Flash modified TWRP if you haven't already
3. Boot into modified TWRP
4. Select Wipe -> Advanced Wipe -> Select all but internal storage -> Swipe to Wipe
5. Install OOS 3.2.6 Full ROM
6. Reboot into system and use the installation wizard to setup your phone (do not setup fingerprints, or any device PIN)
7. Reboot into bootloader
8. Connect your phone to a PC/Notebook
9. Extract AndroidSDKSlim to your Desktop and copy twrp-3.0.2-1-oneplus3.img into \AndroidSDKSlim\android-sdk-windows\platform-tools
10. Run CMD with admin rights and navigate to \AndroidSDKSlim\android-sdk-windows\platform-tools
11. Run "fastboot flash recovery twrp-3.0.2-1-oneplus3.img" to revert to official TWRP recovery
12. Disconnect your phone and boot into recovery
13. Dirty flash OOS 3.2.6 again (this might sound stupid but it's mandatory)
14. Still in recovery, flash SuperSU, Xposed and Debloat Script
15. Wipe Dalvik & Cache
16. Reboot into system and setup your phone
Click to expand...
Click to collapse
worked like magic. Thankyou for this education. it didnt work when i followed other folks. Much appreciated.
So it seems I have booted with 3.5.2 and modified recovery. Now my question is: can I reboot in recovery at step 7 and install the original twrp recovery? Or can I use flashify? As I don't have access to a pc
I did ok but cant use adaway do you have a fix for it?
Enviado do meu ONEPLUS A3003 através de Tapatalk
I'm trying to return to 3.2.6 after trying 3.5.2.
However, after flashing and booting 3.2.6, I boot into fastboot mode and the official TWRP refuses to flash. It reports that it's failed and then I'm left with no recovery until I reflash the modified TWRP.
I could try restoring my Nandroid backup of 3.2.6 with the modified TWRP, but I'd prefer to return to the official TWRP before doing this.
Any suggestions?
Edit: Fixed it. I downloaded the official TWRP again and it flashed. The first download must have been corrupted.
I followed a different method and successfully downgraded today to a former nandroid. I was rooted without xposed.
3.2.6 to 3.5.2 dirty flash
- installed modded twrp
- performed backup on 3.2.6
- installed modded 3.5.2 (the only that flashes in twrp)
- installed root SR1
- wiped caches only
- reboot
3.5.2 to 3.2.6 restore
- downloaded 3.2.6
- boot to modded twrp, wipe both caches, data, system
- flashed 3.2.6 stock and root SR1
- restored 3.2.6
- wiped caches
- reboot
- enjoying my LTE again
Without first installing stock, after a restore my phone was boot locking right after the oneplus white logo (capacitive buttons would light up, but it would not boot to red logo). Had to press vol down and power to force it to boot menu to select recovery and get back to twrp
Hope this helps someone, it's a bit easier than swapping twrps and no need to boot up/flash 3.2.x twice.
So if I am on the CB and want to go back to 3.2.6
I can flash 3.2.6 with the modded TWRP
Then flash Official TWRP and boot?
If I have official recovery, no root, and locked bootloader, can I downgrade from 3.5.3 to 3.2.6 without any problems, just by sideloading the zip in ADB? Thankss
popab said:
If I have official recovery, no root, and locked bootloader, can I downgrade from 3.5.3 to 3.2.6 without any problems, just by sideloading the zip in ADB? Thankss
Click to expand...
Click to collapse
i would also like to know this please
bigup7 said:
i would also like to know this please
Click to expand...
Click to collapse
I did it and it does work perfectly. Just make sure to wipe data from recovery after flashing.
I was on Comunity Build v.3.5.4. I want it back FreeDom v.1.6.
I did:
1. Flash Twrp-3.0.2-19-oneplus3.img.zip. Somebody sugested original twrp 3.0.2.1 from twrp site. For me did NOT work. Phone not booting in recovery with 3021.
2. Advanced wipe. Wipe dalvik cache/cache/system/data
3. Flash Freedom v.1.6. Clean Flash it's safer & better.
Done. System works. Recovery works.
null0seven said:
I was on Comunity Build v.3.5.4. I want it back FreeDom v.1.6.
I did:
1. Flash Twrp-3.0.2-19-oneplus3.img.zip. Somebody sugested original twrp 3.0.2.1 from twrp site. For me did NOT work. Phone not booting in recovery with 3021.
2. Advanced wipe. Wipe dalvik cache/cache/system/data
3. Flash Freedom v.1.6. Clean Flash it's safer & better.
Done. System works. Recovery works.
Click to expand...
Click to collapse
I am on CB Freddom os
I want to go back either to stock or to op3lite.
I cant reboot to recovery.
But adb works yet.
What to do plz suggest.
Sent from my ONEPLUS A3003 using Tapatalk
1. If system don't boot. Reboot to fastboot.
- Flash recovery.img. If PC don't see youre phone option 2.
2. If system boots, open phone like normal.
- Extract recovery img. Put it on the TWRP file on phone sd card.
- Download Flashify from play. Open it, flash img of recovery. Open recovery to chech if it works.
Try with both recovery (3.0.2.0 or modified 3.0.2.-19). One of those will work.
Im getting system partition has unexpected contents after OTA update after installing step 5 ????
Not sure what I'm doing wrong. I clean install Purenexus 7.1.2 (latest) with the recommended gapps, let it boot and get setup. Then I install Magisk and let it fully reboot. Then I try installing the ElementalX 4.20 kernal and it won't finish booting after that. Help! I did it twice now and got the same result.
Jwikoff99 said:
Not sure what I'm doing wrong. I clean install Purenexus 7.1.2 (latest) with the recommended gapps, let it boot and get setup. Then I install Magisk and let it fully reboot. Then I try installing the ElementalX 4.20 kernal and it won't finish booting after that. Help! I did it twice now and got the same result.
Click to expand...
Click to collapse
Hello,
Maybe try this way:
Install ROM and reboot to system
Reboot twrp, Install kernel first and magisk.
Reboot.
Good luck...
That seems to be working. Thanks!
Jwikoff99 said:
That seems to be working. Thanks!
Click to expand...
Click to collapse
Hey,
You're welcome.
As both Magisk and EXKernel alter boot.img, I guess EX needs to be installed first. If you install after Magisk, it brakes a part of Magisk modifications. Hence the bootloop. But it's just an assumption.
Cheers...
Mmmh,
I did a clean flash with ROM (purenexus_shamu-7.1.2-20170423-OFFICIAL), GApps (BeansGapps-Mini-7.1.x-20170415) - reboot and start new system.
Than I fashed Magisk-v12.0 for root and installed Magisk-Manager.
After that I flashed ElementalX-N6-4.20 (and today ElementalX-N6-4.21).
Everything runs without any issue!
Yeah I was kinda wondering what happens when I try to install a kernel update since that would be like what I was doing before.
Hi guys. I have an unrooted phone and got the recent official Oreo update (32 bit) from Moto. My phone is the made in india version. I want to install Pixel Experience [AOSP][r26] rom. What are the steps I need to follow? Do I have to root the device first? What are some issues that may arise? I heard there's a problem with kernel where device runs at 1.4 GHz instead of 2 GHz.
androidman2018 said:
Hi guys. I have an unrooted phone and got the recent official Oreo update (32 bit) from Moto. My phone is the made in india version. I want to install Pixel Experience [AOSP][r26] rom. What are the steps I need to follow? Do I have to root the device first? What are some issues that may arise? I heard there's a problem with kernel where device runs at 1.4 GHz instead of 2 GHz.
Click to expand...
Click to collapse
Hello, first thing you need to do is flash a custom recovery, I highly recommend TWRP for you device, you can find here at Moto g5s plus XDA forum in kernel and custom posts. After you flash the custom recovery you flash magisk (root) through TWRP. At the same posts you can search and find the correct custom Rom for your device, or search on Google for pixel experience website and download the rom from there. Before you flash the rom make a full backup of your phone (system partitions, etc...) with TWRP. I recommend use a SD card to store the rom to flash. There is a lot of risks, but if you do everything that the rom tutorial says I doubt that something bad is going to happen. If you get stuck at TWRP or at boot loop you can flash the original Rom for you device through fastboot and fastboot mode.
What I always do
1 flash twrp
2 reboot for twrp and wipe, advanced wipe, wipe system, wipe data, wipe cache, wipe dalvik-cache
3 flash rom, flash gapps, flash magisk
After a long time I was finally able to unlock my Redmi Note 7.
I realized that flashing and other things on this device are a little bit more complex than on other devices I have had in the past.
Therefore I want to know what are the do's and dont's of this device and maybe make a comprehensive list so that everyone can avoid BRICKING or running into trouble while messing around with their phone.
I have seen things such as:
- never wipe system (which i'm not sure is true btw)
- dm-verity and vbmeta stuff (when to do it and what is it for? - some do it, some don't... which is confusing)
etc.
As you can tell I'm a newbie with this device.
Would be cool if you guys could give some input in order to create a comprehensive list.
Thanks!
Yeah Same thing here !!!
I've been using this phone for a month, i'm not an expert but if it can help around.
-Most custom ROM have they steps to flash and are usually the same for a clean flash (Wipe Cache, Dalvik/Art Cache, Data and System)
-If the custom ROM need it you will need to flash Vbmeta, usually the most ROM already have it inside, and a few have it as an external zip, this is only needed "once" you are coming from MIUI to a custom ROM, otherwise you don't.
-Other custom ROM will ask you to flash global firmware and that's just a 60MB zip that you will found in the ROM links usually, as I said most of the Custom ROM post have their steps.
-Dm-verity is something i haven't had to face as a problem so far so can't help abot that, but following the steps have never cause me any trouble.
What to do?
-First read the post of the Custom ROM including their answers, as it always help before flashing something because you will read if it have any kind of problem or etc from users feed back, and of course the OP info.
-Always have a backup of your stock ROM and personal data to avoid any lost.
-The break-the-glass solution in case of any problem will be always to know which version of phone do you have and have a Fastboot ROM for emergencies or if you are returning to MIUI stock, and the MIFlashTool from MIUI site.
-Always clean flash when you are going to another rom.
What not to do:
-Wiping and formating things you don't know what are you messing with, eg. Vendor partition.
-Never do a dirty flash over another custom ROM or stock, only do dirty flash in the same ROM type if the Dev says is possible to "update" that rom with that method, otherwise do a clean flash.
-Never flash another MIUI ROM that's not your type (China, Global, EEA, Rus, etc) with the MIFlashTool.
-Never flash or use the MIUI Tool with low battery
This might be the common and global things that always someone can tell you, if not the much but i hope it might help
never wipe system, unless you're planning to install another rom after that.
/system is where your OS (ROM) is located, wiping it is wiping your OS from your phone.
IDK much about disable DM-v and vbmeta, all I know is we need these two for disabling android's verified boot, secure boot thingy from google. yay.
AFAIK, we have 3 ways to disable DM-V
Using ofox, open settings > ota > mark on 'disable dm-v' before flashing ROM
by flashing disable dmv zip
by flashing magisk because it's included in magisk.
just do one of them but you can do all three, it doesn't really matter.
and vbmeta is needed only if you're on MIUI and about to flash AOSP rom.
but lately most custom AOSP already zipped with vbmeta so you don't need to worry about that.
here's how I flash ROMs
format data,
reboot recovery,
wipe cache, dalvik, system, data, internal,
flash firmware
flash ROM
flash gapps (optional)
flash kernel (optional)
flash magisk
reboot
hope this helps.
Wipe system if you are installing another rom otherwise you will end in bootloop because there is no system to boot.
Get a latest flashable firmware for your Note7 and place it in your mobile in case you get bootloop.
Install Recovery have every thing always backup.
Use Titanium backup for your apps even system apps should be backedup if you are going to modified system apps or delete them .
I just got the device 2 hours ago already making an optimized/rooted/debloated stock rom for it .
vexa said:
never wipe system, unless you're planning to install another rom after that.
/system is where your OS (ROM) is located, wiping it is wiping your OS from your phone.
IDK much about disable DM-v and vbmeta, all I know is we need these two for disabling android's verified boot, secure boot thingy from google. yay.
AFAIK, we have 3 ways to disable DM-V
Using ofox, open settings > ota > mark on 'disable dm-v' before flashing ROM
by flashing disable dmv zip
by flashing magisk because it's included in magisk.
just do one of them but you can do all three, it doesn't really matter.
and vbmeta is needed only if you're on MIUI and about to flash AOSP rom.
but lately most custom AOSP already zipped with vbmeta so you don't need to worry about that.
here's how I flash ROMs
format data,
reboot recovery,
wipe cache, dalvik, system, data, internal,
flash firmware
flash ROM
flash gapps (optional)
flash kernel (optional)
flash magisk
reboot
hope this helps.
Click to expand...
Click to collapse
Mmm, I used to flash custom ROMs like this way:
- wipe cache, dalvik, system, data, internal,
- format data,
- reboot recovery,
- flash firmware (never did it)
- flash ROM
- flash gapps (optional)
- flash kernel (optional)
- flash magisk
- reboot
What do you mean by flashing a firmware before custom rom? (red)
CrashOverride93 said:
Mmm, I used to flash custom ROMs like this way:
- wipe cache, dalvik, system, data, internal,
- format data,
- reboot recovery,
- flash firmware (never did it)
- flash ROM
- flash gapps (optional)
- flash kernel (optional)
- flash magisk
- reboot
What do you mean by flashing a firmware before custom rom? (red)
Click to expand...
Click to collapse
this firmware, because some roms require certain firmware version (usually the latest stable one)
vexa said:
this firmware, because some roms require certain firmware version (usually the latest stable one)
Click to expand...
Click to collapse
Ohh didn't know. Thanks for letting it me know.
I only flashed, until now, RR and AEX. Now I'm back on Xiaomi.eu ROM But never had any problem.
Hey guys I was wondering something I haven't installed the latest update yet and my phone is rooted and has TWRP on it soo not sure if i can just update with all that or like i should restore the phone to its original state then update
Last version of TWRP I tried (3.4.0-0) did not work properly with Android 10, don't know about the new 3.4.0-1 because I switched to OrangeFox which can decrypt Android 10 without issues.
As for the update process, you need to get the Recovery ROM update package, you can download it from the official xiaomi site, put it, Magisk and your kernel if you use a custom one either on the phone's internal storage or even better your SD card and flash from recovery in this order:
1. ROM
2. Kernel
3. Magisk
4. Wipe Dalvik\cache
5. Reboot to system
I did it exactly like this a few times now, granted it was with xiaomi.eu instead of stock but the process should be the same.
This should just update the phone without wiping anything and with maintaining root, just make sure to do it from a recovery that can decrypt the phone.
Maranex said:
Last version of TWRP I tried (3.4.0-0) did not work properly with Android 10, don't know about the new 3.4.0-1 because I switched to OrangeFox which can decrypt Android 10 without issues.
As for the update process, you need to get the Recovery ROM update package, you can download it from the official xiaomi site, put it, Magisk and your kernel if you use a custom one either on the phone's internal storage or even better your SD card and flash from recovery in this order:
1. ROM
2. Kernel
3. Magisk
4. Wipe Dalvik\cache
5. Reboot to system
I did it exactly like this a few times now, granted it was with xiaomi.eu instead of stock but the process should be the same.
This should just update the phone without wiping anything and with maintaining root, just make sure to do it from a recovery that can decrypt the phone.
Click to expand...
Click to collapse
Well I have a few questions
By recovery ROM you mean from here https://c.mi.com//miuidownload/detail?device=1900376 the full ROM? like I just flash the ROM file using TWRP well OrangeFox version right and it will keep all my apps and data
Yes, you flash the rom from mi.com.
Don't "just" flash it or you'll loose root and OrangeFox, flash in this order:
1. ROM
2. Kernel
3. OrangeFox (I added this step because you are on official MIUI and the update will replace your custom recovery unless you re-flash it after the rom.)
4. Magisk
5. Wipe Dalvik\cache
6. Reboot to system
Before flashing make sure you are flashing the right rom for your variant and region.
Other than that, you should be good, I updated like this three times and had no data loss.