So I managed to root the C25Y by flashing stock firmware with a magisk patched boot.img using SP Upgrade Tool.
I wanted to update but OTAs won't work since I modified /system by deleting some bloatware.
Is there a way to flash stock system image without losing data, or maybe bypass the check?
Main reason I'm updating is because the system partition in storage is taking up 15GB. Updating usually reduces it to 7GB.
Related
Hi,
Sprint Note 5 here. Basically I'm just trying to get my phone to be unrooted to pass SafetyNet (Android Pay, Pokemon Go, and others) but have some system modications (adaway and removed boot sounds mainly).
What I did do is flash stock odin firmware, then twrp, supersu, and make my changes. Then if I just unroot with supersu it still fails SafetyNet. If I unroot and tell SuperSU to restore boot.img then I get a bootloop. Probably due to TWRP still being there and not stock Recovery? So I thought maybe from there I can just flash boot and recovery via odin but that didn't seem to work either. Is it possible to take the stock firmware and flash whatever I need except system? Or not possible to alter system and go back to stock boot/recovery?
Edit: I took stock firmware, extracted it, removed system.img, and repacked it up (sboot.bin, modem.bin, recovery.img, cm.bin, boot.img, cache.img) and flashed it . It works but then brings me to some "system update" screen and then stock recovery with a verity failed error. Reboot to device just bootloops. Maybe I need to just remove more than just system?
hey guys, i wanna know if i will still get ota updates if i unlocked the bootloader ??
i wanna unlock it and if i didn't flash TWRP after unlocking it i will be able to install the update ??
This thread is pretty old and it's referring to a Nexus 5, but I think the info holds true. Unlocking wont' stop ota updates, and if all it is is unlocked, then the ota update should install.
It's when you install twrp, or root, or a new system image, etc... that's when the ota update won't install.
https://forum.xda-developers.com/google-nexus-5/help/unlocking-bootloader-prevent-automatic-t3003581
When I unlocking the fastboot oem it will unlock but when I was goes enable to camera 2 I was applied patched boot img my mi a2 phone was stuck in between reboot only it'll showed Android one logo it not goes to restart after I waited 30 min I was flash my phone with new global ROM then it'll start. After that I check my if it's rooted or not .then found out my phone is not rooted properly
My question is can get OTA update ?
Ravirush said:
When I unlocking the fastboot oem it will unlock but when I was goes enable to camera 2 I was applied patched boot img my mi a2 phone was stuck in between reboot only it'll showed Android one logo it not goes to restart after I waited 30 min I was flash my phone with new global ROM then it'll start. After that I check my if it's rooted or not .then found out my phone is not rooted properly
My question is can get OTA update ?
Click to expand...
Click to collapse
In order to maintain the OTA compatibility there is one thing to bear in mind. The system must have the same parity as a standard image.
Changes to the build.prop (camera 2) or swapping out a boot image change this parity. Put the original boot and build.prop back and you should be OK.
Perhaps the best way to think about this is the red pill or the blue pill...
As for rooting - for our Xiaomi A2's the best way to root is to :
Unlock the bootloader (this will wipe your data - ensure you have backups)
Swap the boot.img for one that is Magisk compatible (from this point your OTA is broken)
Install magisk (for the SU)
At this point to get back OTA capability one has to uninstall Magisk and put back a standard boot.img - This hasn't worked for me since going Pie (I have thus swallowed the red pill)
If you touch your build.prop or other system files IMHO you can bury the OTA.
If I want a new version of android I'll manually flash the new image and go back through the rooting process and finish by modifying my build.prop.
There are Magisk modules that provide systemless changes but I've not tested these myself - I prefer to know exactly what I'm doing with my build.prop.
To get back to standard you can always flash a standard system image and if you really want to be clean you can relock the bootloader which will reset your phone as if it was out of the box.
Just to provide some more clarity, unlocking bootloader does not break OTA. OTA is broken only if you modify system partition. One important thing to note is that unlocking bootloader will break safety net. Meaning no Netflix and Pokemon go. But this can be easily fixed by just flashing Magisk.
Magisk and its modules don't modify system partitions. So you can go crazy with Magisk and still have OTA. Just be sure to restore the original magisk-less boot.img before upgrading via OTA as it will 100% cause boot loops..
Enabling camera2 api (via adb or terminal emulator) doesn't break OTA.
On my device, I have Magisk installed with viper4android, quickstep, and Camera2 api enabled and have OTAs intact. I just have to restore my original boot.img.
To be on the safe side, I would suggest you don't edit any files in system partition via file explorers and stay away from editing build.prop directly. You can edit build.prop via a Magisk module.
After the fiasco with the January update causing bootloops, I would suggest keeping bootloader unlocked so you can always downgrade or reflash your device if an OTA messes things up for you rather than having to give it for warranty.
Ashik_salim_ said:
Just to provide some more clarity, unlocking bootloader does not break OTA. OTA is broken only if you modify system partition. One important thing to note is that unlocking bootloader will break safety net. Meaning no Netflix and Pokemon go. But this can be easily fixed by just flashing Magisk.
Magisk and its modules don't modify system partitions. So you can go crazy with Magisk and still have OTA. Just be sure to restore the original magisk-less boot.img before upgrading via OTA as it will 100% cause boot loops..
Enabling camera2 api (via adb or terminal emulator) doesn't break OTA.
On my device, I have Magisk installed with viper4android, quickstep, and Camera2 api enabled and have OTAs intact. I just have to restore my original boot.img.
To be on the safe side, I would suggest you don't edit any files in system partition via file explorers and stay away from editing build.prop directly. You can edit build.prop via a Magisk module.
After the fiasco with the January update causing bootloops, I would suggest keeping bootloader unlocked so you can always downgrade or reflash your device if an OTA messes things up for you rather than having to give it for warranty.
Click to expand...
Click to collapse
hi my friend. i unlocked bootloader to flash persist.img beacause i have had problem with my camera. now it came april(2020) ota update but it fail. why? what can i do? I didn't root the phone. Only unlock bootloader and criticals
Dear all,
I've rooted my phone in July 2018 with the latest stock build from that timeframe. I'm getting notifications of OTA updates for the past 6 months that I've been swiping away and putting off. Obviously I cannot update OTA.
What are my options to update my phone if I want to maintain root? Is there a full build somewhere that I can install via twrp and flash SU or magisk over? Are there fully functional ROMs that I can periodically flash via TWRP to stay up-to-date and rooted? Or am I forced to revert to stock, update via OTA, then re-root?
I'm familiar with rooting but the G6 pathways have confused me compared to my previous OnePlus and Nexus phones. Thanks for your help.
You should only have to re-flash
OEM
Vendor
Boot
Recovery
to be able to apply the OTA.
Afterwards you just need to boot the twrp and install Magisk again, and maybe use the dmverity patch to disable forced encryption. <-- This has to be done BEFORE the first boot of the upated system, otherwise the phone will be encrypted again.
At least this is how it works on the G6 Play.
So basically I have to go back to stock, upgrade via OTA, and redo the entire root method, while wiping my phone clean each time with the OEM installation. Wish there was a more efficient way. Thanks for your input.
You can do that without loosing your apps/userdata.
Best bet would be to find the latest full image for your make/model and flash everything via fastboot. Just skip the part "fastboot erase userdata" or something like that, and you are good to go. Just remember the dmverity thing, if that is important/applicable for you.
Re-root is necessary either way, but that takes like 5 minutes, that shouldn't hold you up.
tintn00 said:
So basically I have to go back to stock, upgrade via OTA, and redo the entire root method, while wiping my phone clean each time with the OEM installation. Wish there was a more efficient way. Thanks for your input.
Click to expand...
Click to collapse
Brazilian PIE full ROM is out. If unencrypted, backup Oreo data in TWRP first. Second, you can fastboot flash this stock PIE rom & Reboot to PIE which will encrypt data. Third, fastboot flash unofficial TWRP recovery by Dejello (official TWRP can't install gapps for GSI ROMs and doesn't backup vendor partition). Fourth, format data to rid new PIE encryption. Fifth, install Universal Force Encryption Disabler 2/4/19 and Magisk 18.1 to root and prevent encryption. Sixth, restore unencrypted Oreo data.
If you're already encrypted, then do as above
HueyT said:
Brazilian PIE full ROM is out. If unencrypted, backup Oreo data in TWRP first. Second, you can fastboot flash this stock PIE rom & Reboot to PIE which will encrypt data. Third, fastboot flash unofficial TWRP recovery by Dejello (official TWRP can't install gapps for GSI ROMs and doesn't backup vendor partition). Fourth, format data to rid new PIE encryption. Fifth, install Universal Force Encryption Disabler 2/4/19 and Magisk 18.1 to root and prevent encryption. Sixth, restore unencrypted Oreo data.
If you're already encrypted, then do as above
Click to expand...
Click to collapse
I don't mind wiping my phone clean to get PIE. Will I have to wipe it clean every time there's an update?
There's a lot of mentioning of encrypt and unencrypted. If I'm starting over and wiping clean, what's the simplest method to maintain root? Staying encrypted or unencrypted?
The Brazilian PIE mentioned something about playstore uncertified. What does that mean?
Thanks!
tintn00 said:
I don't mind wiping my phone clean to get PIE. Will I have to wipe it clean every time there's an update?
There's a lot of mentioning of encrypt and unencrypted. If I'm starting over and wiping clean, what's the simplest method to maintain root? Staying encrypted or unencrypted?
The Brazilian PIE mentioned something about playstore uncertified. What does that mean?
Thanks!
Click to expand...
Click to collapse
If u want to backup data partition on TWRP, u have to be unencrypted for Moto G6 as TWRP can't decrypt data.
Rooting is just Magisk 18.1 and has nothing to do with encryption.
Uncertified is due to 1) unlocked bootloader, 2) Brazil ROM in USA--means little functionally
HueyT said:
Uncertified is due to 1) unlocked bootloader, 2) Brazil ROM in USA--means little functionally
Click to expand...
Click to collapse
Shucks my bootloader is unlocked. Sounds like the USA PIE is around the corner. I can wait but I hope the unlocked bootloader won't be a problem.
Thanks for your help.
tintn00 said:
Shucks my bootloader is unlocked. Sounds like the USA PIE is around the corner. I can wait but I hope the unlocked bootloader won't be a problem.
Thanks for your help.
Click to expand...
Click to collapse
Unlocked is safest guarantee against bricking. Don't worry about "uncertified" in Play store
Hi, I'm on Pie, rooted, Magisk, TWRP. I downloaded latest firmware through XperiFirm. If I remove file userdata_X-FLASH-CUST-C93B.sin from firmware, my apps will be intact. But can I also remove boot folder, to keep my current loader (TWRP)? Also will such upgrade remove root ?
Ideally I want to keep apps, TWRP, root (Magisk), not erase SD card. Is it possible?
Interested... I've think all time, to hold the user data, I just delete the sin file which contains the word user in front....
following this!
same situation, curious if a upgrade to new FW is able of keeping the userdata.
It's normal, that root is lost after update..... Supersu or Magisk must be flashed after update the system.
How to keep TWRP? It's the question, where TWRP is located and linked.... I must reflash also TWRP all time after new update.
Hello XDA fam, I just picked up a 3T and unlocked the bootloader.
I was just wondering what the general flashing process was for this
device (A3000). Also a tad confused about this dm-verity ...
disabler zip, is this and format data required every time you flash a
new ROM?
MoistPicklez said:
Hello XDA fam, I just picked up a 3T and unlocked the bootloader.
I was just wondering what the general flashing process was for this
device (A3000). Also a tad confused about this dm-verity ...
disabler zip, is this and format data required every time you flash a
new ROM?
Click to expand...
Click to collapse
Dm-verity warnings are similar to the unlocked bootloader screen you get, but are red. You get them if you are running stock OOS and modify the system partition.
You don't need the dm-verity disabler unless you've got a dm-verity warnings screen.
Note that you cannot disable the unlocked bootloader warning you get every time the phone boots except by re-locking the phone.
Another thing to note: if you are running stock OOS and flash TWRP, then TWRP will be replaced by the stock recovery when your reboot the phone unless you:
- use a patched boot image like the one from @Xennet's thread https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324/post79357241
- use a custom kernel, or
- use Magisk.
Flashing using TWRP is just like any other phone. If you're changing ROMs then you need to do a clean install (wipe /data and/system).
Some ROMs don't handle an encrypted phone (most Android 10 ones except for Los and PE), so you you have to remove the encryption before using those ROMs (TWRP>wipe>format data).
Finally if your phone is unlocked and running OOS 5.x or lower, and you want to upgrade to OOS 9.x then you'll either have to:
- remove the encryption (but can re-encrypt after installing 9.x) or
- use the modded firmware (that keeps the 5.x bootloader and keys) so that you don't have to remove the encryption. See https://forum.xda-developers.com/on...-5-0-8-firmware-barrier-t3941164/post79758055
Sent from my OnePlus3T using XDA Labs
BillGoss said:
Dm-verity warnings are similar to the unlocked bootloader screen you get, but are red. You get them if you are running stock OOS and modify the system partition.
You don't need the dm-verity disabler unless you've got a dm-verity warnings screen.
Note that you cannot disable the unlocked bootloader warning you get every time the phone boots except by re-locking the phone.
Another thing to note: if you are running stock OOS and flash TWRP, then TWRP will be replaced by the stock recovery when your reboot the phone unless you:
- use a patched boot image like the one from @Xennet's thread https://forum.xda-developers.com/oneplus-3t/how-to/dm-verity-disable-oxygen-os-t3922324/post79357241
- use a custom kernel, or
- use Magisk.
Flashing using TWRP is just like any other phone. If you're changing ROMs then you need to do a clean install (wipe /data and/system).
Some ROMs don't handle an encrypted phone (most Android 10 ones except for Los and PE), so you you have to remove the encryption before using those ROMs (TWRP>wipe>format data).
Finally if your phone is unlocked and running OOS 5.x or lower, and you want to upgrade to OOS 9.x then you'll either have to:
- remove the encryption (but can re-encrypt after installing 9.x) or
- use the modded firmware (that keeps the 5.x bootloader and keys) so that you don't have to remove the encryption. See https://forum.xda-developers.com/on...-5-0-8-firmware-barrier-t3941164/post79758055
Click to expand...
Click to collapse
Wow thank you for the detailed info, I really appreciate the insight.
I am currently running the latest OOS update 9.0.6 I believe.
Once I have TWRP installed do I swipe and enable modifications?
Flashing Magisk afterwards avoids the bootloop and allows me to
keep TWRP in place of the stock recovery as you said, correct?
So installing most ROMs seems fairly straightforward, following
the flashing instructions. However if I were to install an Android
10 ROM wouldn't formatting data remove all zips and everything
from the internal storage? So at that point I'd have to copy back
all my ROMs and zips back to the phone in TWRP and flash from
this point correct?
Sorry for the loads of questions, my most recent device was a
Note 9, which has a locked bootloader, so it has been a while since
I have flashed anything or used TWRP.
MoistPicklez said:
Wow thank you for the detailed info, I really appreciate the insight.
I am currently running the latest OOS update 9.0.6 I believe.
Once I have TWRP installed do I swipe and enable modifications?
Flashing Magisk afterwards avoids the bootloop and allows me to
keep TWRP in place of the stock recovery as you said, correct?
Click to expand...
Click to collapse
You don't need you enable modifications of the system partition. Any zip you flash will make the system writable if required.
So, just flash Magisk.
MoistPicklez said:
So installing most ROMs seems fairly straightforward, following the flashing instructions. However if I were to install an Android
10 ROM wouldn't formatting data remove all zips and everything from the internal storage? So at that point I'd have to copy back all my ROMs and zips back to the phone in TWRP and flash from this point correct?
Click to expand...
Click to collapse
Correct. So it's best to take a backup of your current system and backing up everything on internal storage (/sdcard) to an external drive or PC.
The fastest way to take the backup is to use ADB.
Code:
adb pull /sdcard
MoistPicklez said:
Sorry for the loads of questions, my most recent device was a
Note 9, which has a locked bootloader, so it has been a while since
I have flashed anything or used TWRP.
Click to expand...
Click to collapse
You'll find that nearly all the rom, kernel, and recovery development threads are under the OnePlus 3 forum in https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development as they are unified: good to flash on both the 3 and 3T.
Sent from my OnePlus3T using XDA Labs
BillGoss said:
You don't need you enable modifications of the system partition. Any zip you flash will make the system writable if required.
So, just flash Magisk.
Correct. So it's best to take a backup of your current system and backing up everything on internal storage (/sdcard) to an external drive or PC.
The fastest way to take the backup is to use ADB.
You'll find that nearly all the rom, kernel, and recovery development threads are under the OnePlus 3 forum in https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development as they are unified: good to flash on both the 3 and 3T.
Click to expand...
Click to collapse
Awesome info, big thanks to you my good sir. Finally
on Havoc 2.9 and decrypted. Now just gotta get a feel
for this phone and keep on reading. Cheers!