Hello, I initially rooted my device (SM-A536B) with magisk. The process was unlocking the bootloader and flash patched AP (magisk) along with BL, CSC, etc. with Odin and perform a factory reset, as it was the initial rooting (firmware: A536BXXU2AVG1). Recently a new firmware (A536BXXU3AVGA) was released and I tried the same method using HOME_CSC. The result was a mandatory factory reset due to a boot loop. Everything else is working fine, despite that I had to recover all userdata from backups.
The question is: Has anyone figured out a way to flash new firmware (security patch e.g.) while maintaining all userdata, without having to perform a factory reset every time ? I am working with a productive device and can't test all scenarios.
Suggestions would be flashing only patched AP, patched AP with Home_CSC, deinstalling magisk prior to flashing or maybe something different.
Please share your experience.
Regards
Wow, I was under the impression that using HOME_CSC would be enough. I'll definitely keep an eye out on this thread to see if someone can explain a bit in detail why this didn't work.
My question to you would be, did you have any magisk modules installed?
If so, when it went into bootloop did you attempt to start the phone up in Safe mode so that it would disable all active magisk modules?
ShaDisNX255 said:
Wow, I was under the impression that using HOME_CSC would be enough. I'll definitely keep an eye out on this thread to see if someone can explain a bit in detail why this didn't work.
My question to you would be, did you have any magisk modules installed?
If so, when it went into bootloop did you attempt to start the phone up in Safe mode so that it would disable all active magisk modules?
Click to expand...
Click to collapse
I got the 'Systemless Hosts' module active, but no twrp or other custom recovery installed. I remember the phone went into a trimmed recovery after about three failed attempts to start up. There I was able to only view logs, restart or reset to factory state. I rebooted to regular recovery mode using power down+side key and cleared cache what didn't help, so I had to reset the phone. I don't think there was a safe mode feature available in the recovery menu. Maybe it is possible to tweak this with adb commands. Someone with a spare phone may test these scenarios
Andoreid said:
I got the 'Systemless Hosts' module active, but no twrp or other custom recovery installed. I remember the phone went into a trimmed recovery after about three failed attempts to start up. There I was able to only view logs, restart or reset to factory state. I rebooted to regular recovery mode using power down+side key and cleared cache what didn't help, so I had to reset the phone. I don't think there was a safe mode feature available in the recovery menu. Maybe it is possible to tweak this with adb commands. Someone with a spare phone may test these scenarios
Click to expand...
Click to collapse
Well to boot into safe mode you usually just have to hold the VOL DOWN key throughout the boot process. Keep it in mind, may be useful for the future.
ShaDisNX255 said:
Well to boot into safe mode you usually just have to hold the VOL DOWN key throughout the boot process. Keep it in mind, may be useful for the future.
Click to expand...
Click to collapse
Ah yes, could have helped to figure out if the device would have started at least. Is userdata available in safe mode ?
With Magisk v21, there’s a new feature that will automatically disable all modules when the device is booted into Safe Mode. The primary aim of this feature is to help users deal with rogue modules. I should have read this earlier
(see here: https://www.thecustomdroid.com/uninstall-magisk-modules-in-twrp-recovery-guide/)
I can't tell if the modules remain disabled after rebooting normally because you cannot open 3rd party apps in safe mode. If not or removing them entirely is necessary, solution could be removing magisk modules with adb like mentioned on the site:
Code:
adb wait-for-device shell magisk --remove-modules
This should work even if USB debugging is off as long bootloader is unlocked.
This only works IF magisk modules are the problem with booting into os.
Additional info can be found here: https://forum.xda-developers.com/t/...les-without-magisk-and-twrp-recovery.4394991/
Andoreid said:
I can't tell if the modules remain disabled after rebooting normally
Click to expand...
Click to collapse
Yes, they stay disabled.
Ok so we need test objects now Don't hesitate to write down your experience.
And Samsung should include the safe mode feature into the recovery mode !
Has anyone being rooted and using magisk updated to A536BXXU4AVH9 and experienced any flaws ?
Using the magisk file, AP, BL and the HOME_CSC, you can upgrade without losing anything
I did it yesterday on my A53
You mean AP mod, CP, BL and Home_CSC I suppose. Did you have to deactivate or deinstall any modules prior to the upgrade ?
Everything went well on my side too. Only difference was I activated USB debugging prior to the update as a precaution measure.
VJ1 update without problems, this time usb debugging wasn't on.
Andoreid said:
VJ1 update without problems, this time usb debugging wasn't on.
Click to expand...
Click to collapse
Good afternoon
Besides AP mod, BL, CP and Home_CSC, do you do anything else? do i have to flash any kernel? disable AVB? Is it necessary to do a factory reset?
It wasn't necessary to disable or deinstall anything. Just flash the corresponding files with odin, I used v3.14.4. Good luck
Andoreid said:
VJ1 update without problems, this time usb debugging wasn't on.
Click to expand...
Click to collapse
Good afternoon Besides AP mod, BL, CP and Home_CSC, do you do anything else? do i have to flash any kernel? disable AVB? Is it necessary to do a factory reset?
Andoreid said:
It wasn't necessary to disable or deinstall anything. Just flash the corresponding files with odin, I used v3.14.4. Good luck
Click to expand...
Click to collapse
Thanks! I'll try, see if there's any luck!
Related
Okay. I'm late getting into the pixel 3 game because I got my pixel 2 late last year. But i've just purchased it recently and it's great. But iv'e been unable to root it & I've never had any trouble rooting any Google devices in the past, stretching back to the nexus 3. I've always been under the impression that Google encourages rooting, or at least, makes no attempt to stop it. So I'm surprised that I even feel the need to make this post. I can find plenty of people talking about rooting even up to February's security patch, but nothing for Google's current most recent security patch (March 2019). Nothing I do seems to make any difference, I've followed steps on several tutorial threads to the letter and still end up in a boot loop. I'm tempted to downgrade so I can root, but I'd like to avoid that if possible. Am I the only one having this issue? I'm not able to find a wealth of people complaining about it, which strikes me as weird. Has Google done something with this update to actively block Magisk, or what? I'm at a loss. Like I say, never have I ever encountered such a road block in rooting any device.
Anyways, hopefully someone can ease my frustrations by at least sharing in them. Thanks for any replies.
This assumes you have already unlocked the bootloader...
1. Fastboot boot TWRP.
2. If you don't want permanent TWRP, skip to step 5. Otherwise, go to step 3.
3. Flash TWRP zip.
4. Reboot to recovery.
5. Flash magisk zip.
6. Reboot to system
That's it. It's the same on every security patch.
This is exactly what I am doing. I've also tried manually patching the boot image and live booting it as well as flashing it, but none of these methods render any different result. I've done it so many times I don't need to follow instructions, I only looked at tutorials because it kept failing. I've definitely got the bootloader unlocked but every time I install Magisk I get boot looping.
You need to boot into system before flashing magisk.
watlingj said:
This is exactly what I am doing. I've also tried manually patching the boot image and live booting it as well as flashing it, but none of these methods render any different result. I've done it so many times I don't need to follow instructions, I only looked at tutorials because it kept failing. I've definitely got the bootloader unlocked but every time I install Magisk I get boot looping.
Click to expand...
Click to collapse
Maybe a shot in the dark, but, in twrp, after you flash the magisk zip, reboot to twrp, flash the magisk uninstaller, then flash magisk again. I had the same issue when I updated to 9.0 on my P2XL :good:
wangdaning said:
You need to boot into system before flashing magisk.
Click to expand...
Click to collapse
I've never had issues without booting back to system before flashing magisk.
Badger50 said:
Maybe a shot in the dark, but, in twrp, after you flash the magisk zip, reboot to twrp, flash the magisk uninstaller, then flash magisk again. I had the same issue when I updated to 9.0 on my P2XL :good:
Click to expand...
Click to collapse
Thanks for the suggestion but alas, still boot looping.
wangdaning said:
You need to boot into system before flashing magisk.
Click to expand...
Click to collapse
I've tried this, it didn't make a difference.
OK, try:
1) Flash factory image, remove -w if you want
2) Reboot system then reboot bootloader
3) Fastboot boot TWRP (if you flash install zip reboot system again, then back to recovery)
4) Flash magisk v18.1 (redownload it to eliminate bad dl as culprit)
Not sure what is causing your problems. The initial guide is the same as with the march update. I have done it several times without issue.
wangdaning said:
OK, try:
1) Flash factory image, remove -w if you want
2) Reboot system then reboot bootloader
3) Fastboot boot TWRP (if you flash install zip reboot system again, then back to recovery)
4) Flash magisk v18.1 (redownload it to eliminate bad dl as culprit)
Not sure what is causing your problems. The initial guide is the same as with the march update. I have done it several times without issue.
Click to expand...
Click to collapse
Sorry for the late reply, i actually ended up returning it to stock and swapping it for a different one, because my speaker was making a weird sound when i was calling and it was having bluetooth issues, this one rooted perfectly fine first try.'
Except, Magisk randomly can't detect it's self through it's own manager app, but all my installed modules are working.. but i can't... manage them..
Hi,
So I followed this tutorial https://oneplus.gadgethacks.com/how...thout-losing-root-no-computer-needed-0192638/ (but I used more up to date downloads links than what was on the article) to update my phone to the latest oxygenos on my OnePlus 6.
The install went well, I could reboot on my phone without problems. The thing is when I ran magisk manager it said that magisk wasn't installed. So I rebooted to twrp and flashed again magisk then rebooted. Now when the phone rebooted and asked me for my pin number it automatically went to "Shutting down phone" and rebooted to twrp. So I flashed the magisk uninstaller but it didn't rebooted well. Then I thought I had to switch the active slot, so in twrp I switched to slot A. Then it rebooted on fastboot. I understood I did something really bad so I ran "fastboot --set_active=b" on my computer.
Now my phone cannot actually boot and everytime I get in twrp except that now it doesn't ask me to unlock the phone to decrypt it and just asks me if I want to get into twrp in read only mode. When I navigate to /sdcard, it is full of weird folder name which is because, if I understand well, twrp has failed to decrypt it.
Is my phone bricked? Can I recover data? Can I repair my installation?
EDIT: if you need more informations that I forgot to give don't hesitate to ask.
EDIT2: I tried to reboot to fastboot mode and issue on my computer "fastboot boot twrp-3.2.3-1-enchilada.img" to see if the official twrp could decrypt the data (I'm currently using bluespark's twrp). I get the following error: "FAILED (remote: unknown command)". I understand now I'm pretty ****ed. Right now I'd only like to recover my data (mostly hundreds of pictures) and then flash a stock rom (except if it's actually possible to repair the system and boot normally). How can I decrypt /sdcard if twrp can't do it?
Thanks in advance for your help, I'm pretty lost right now and it's quite an urgent situation.
I got a new error when issuing "fastboot boot boot.img" after I rebooted to System from twrp:
```
Downloading 'boot.img'
OKAY [ 0.692s]
booting
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Finished. Total time: 0.719s
```
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
noom4_5 said:
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
Click to expand...
Click to collapse
Once in your booted TWRP from 'fastboot boot twrp.img' ... Flash OOS (9.0.5 from xda forums), flash blu_spark-TWRP, reboot TWRP... Now you can root your phone (flash Magisk), flash a kernel. All should be good.
I would suggest in future, use these forums for download links, tutorials, and check this Q&A forum (literally 3-5 posts on first half of page 1 with similar problems. Just follow instructions to update if you don't know how (they are always on first page of the thread where you get your downloads from).
Thank you for your answer, everything's back to normal
I'll make sure to follow the official tutorials next time.
only4dank said:
Once in your booted TWRP from 'fastboot boot twrp.img' ... Flash OOS (9.0.5 from xda forums), flash blu_spark-TWRP, reboot TWRP... Now you can root your phone (flash Magisk), flash a kernel. All should be good.
I would suggest in future, use these forums for download links, tutorials, and check this Q&A forum (literally 3-5 posts on first half of page 1 with similar problems. Just follow instructions to update if you don't know how (they are always on first page of the thread where you get your downloads from).
Click to expand...
Click to collapse
Good advice. I'd also like to add so everyone is aware, it's a good idea to disable all magisk modules before an update. Also disable your lockscreen pin, fingerprint... Basically any security. You can always re-enable these once updated. It just makes for less complications when updating. I'd also recommend downloading magisk modules outside of the app and keep them in a folder called magisk modules. That way, if for some reason magisk didn't retain the ones you downloaded after disabling and installing an oos update, you don't have to rely on your memory to look up\install them.
thejase said:
Good advice. I'd also like to add so everyone is aware, it's a good idea to disable all magisk modules before an update. Also disable your lockscreen pin, fingerprint... Basically any security. You can always re-enable these once updated. It just makes for less complications when updating. I'd also recommend downloading magisk modules outside of the app and keep them in a folder called magisk modules. That way, if for some reason magisk didn't retain the ones you downloaded after disabling and installing an oos update, you don't have to rely on your memory to look up\install them.
Click to expand...
Click to collapse
I never disable/uninstall Magisk modules. Nor do I disable lockscreen pin, fingerprint.
Theres no point at all. If flash things logically (correctly) you won't reboot your system without non-stock recovery, or no root.
only4dank said:
I never disable/uninstall Magisk modules. Nor do I disable lockscreen pin, fingerprint.
Theres no point at all. If flash things logically (correctly) you won't reboot your system without non-stock recovery, or no root.
Click to expand...
Click to collapse
There absolutely is a point. Many people have had encryption issues in twrp when updating. In addition, I myself have had a magisk issue where one of the modules wouldn't run properly when updating to pie and as a result, it didn't boot. Using a terminal magisk module uninstaller in twrp to disable the module fixed the issue. This is merely advice to eliminate all possible failures when updating. If it works for you without doing these things, mazel tov, but this is for those that have had issues and want to minimize the odds of that happening again.
thejase said:
There absolutely is a point. Many people have had encryption issues in twrp when updating. In addition, I myself have had a magisk issue where one of the modules wouldn't run properly when updating to pie and as a result, it didn't boot. Using a terminal magisk module uninstaller in twrp to disable the module fixed the issue. This is merely advice to eliminate all possible failures when updating. If it works for you without doing these things, mazel tov, but this is for those that have had issues and want to minimize the odds of that happening again.
Click to expand...
Click to collapse
Fair enough. But moving from Oreo to Pie is a little bit different then Pie OTA updates. I have 6-7 modules recently in Magisk - and never uninstalled Magisk or removed modules while updating Android Pie.
When I came from Oreo, I did a clean wiped system. To me, that makes sense - because it is a dramatic change in the system (whereas OTA updates for same android version are pretty minuscule).
only4dank said:
Fair enough. But moving from Oreo to Pie is a little bit different then Pie OTA updates. I have 6-7 modules recently in Magisk - and never uninstalled Magisk or removed modules while updating Android Pie.
When I came from Oreo, I did a clean wiped system. To me, that makes sense - because it is a dramatic change in the system (whereas OTA updates for same android version are pretty minuscule).
Click to expand...
Click to collapse
The only module I had to manually remove, because OOS refused to boot after an update, was "OOS Native Call Recording Enabler".
And before I knew that was causing it... I factory reset, then everything was fine until the next update xD
I even made a Backup/restore magisk data script, but seeing as it backed up/restored that module too it would still refuse to boot after an update.
ante0 said:
The only module I had to manually remove, because OOS refused to boot after an update, was "OOS Native Call Recording Enabler".
And before I knew that was causing it... I factory reset, then everything was fine until the next update xD
I even made a Backup/restore magisk data script, but seeing as it backed up/restored that module too it would still refuse to boot after an update.
Click to expand...
Click to collapse
Same. But if you install it with version 8.0 after the update, it works again. Just f.y.i..
noom4_5 said:
I got a new error when issuing "fastboot boot boot.img" after I rebooted to System from twrp:
```
Downloading 'boot.img'
OKAY [ 0.692s]
booting
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Finished. Total time: 0.719s
```
Click to expand...
Click to collapse
noom4_5 said:
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
Click to expand...
Click to collapse
Can you tell me which TWRP image you used to get past this issue? I have tried both 3.2.3-1 and 3.3.0-0 several times with zero luck this far. Thanks!
wwwryan said:
Can you tell me which TWRP image you used to get past this issue? I have tried both 3.2.3-1 and 3.3.0-0 several times with zero luck this far. Thanks!
Click to expand...
Click to collapse
Answered my own question but wanted to leave this here for others just in case it is helpful. Using twrp-3.2.3-x_blu_spark_v9.91_op6.img I was able to fastboot boot the img file and this version of TWRP offered to decrypt. From there first thing I did was adb pull my entire sdcard to my PC for save keeping.
My issue was a result of restoring from an earlier backup to recover some data. I had recently updated to 9.0.5 but accidentally deleted something I had no backup for so was restoring a previous TWRP back from 9.0.4. After the restore I couldn't boot the OS and all official version of TWRP would no longer offer to decrypt my data. Of course, I could not restore the backup I had just taken either since it was encrypted on the internal SD card. From now on I will just take TWRP backups to external storage via OTG USB and not even risk it.
Happened to me a few days ago
You can NOT recover your data. But you will be able to fix your phone.
Just do a Factory Reset from TWRP (Wipes Everything) and a wipe of system etc
Then just sideload or put the latest OOS back on the phone and install it.
Trust me, I have tried everything for trying to recover and decrypt the data... Somehow our phones did change the Encryption Keys from /data/unencrypted so there is no way to recover unless you can get the same key out of luck of using the encryption algorithm and salting process that Android uses.
https://imgur.com/y8ENw77
https://imgur.com/q7BPOCy
I've done this a few times. Actually... every time I update; save for the last two times. Just two notes that you already seem to have figured out:
1) Always remember turn off your active modules. (Just turn them off, you don't need to uninstall them.) Simply doing that seems to have fix OTA issues for me. I try to do it before I even download the update and definitely before I install it.
2) No matter how badly I foul up (except for the first time), I never wipe it when trying to fix it. Just side boot Blu Spark TWRP and flash the OS again. Boot it up once without root. Then go ahead to side boot Blu Spark TWRP again to root. I never install TWRP to the device at all. Even with Blu Spark, it seems to get iffy with me. If I want to flash something, I just let it wait until I'm home so I can side load Blu Spark.
Hi,
i have TWRP installed with Magisk and ElementalX, everything was working fine, i just got an update for "google play system update" which i had to install.
I did that, but now i'm stuck on Bootloader screen which then boots into Fastboot Mode after a minute. Holding volume buttons and power does not help.
I still have following files that might help:
TWRP installed and the zip file for TWRP(which is still installed and working)
zip file for older version of Magisk
zip file for ElementalX
Is there anything i can do with TWRP or fastboot to keep my current files?
I assume my boot.img is missing due to that update?
I was running the latest OOS version.
Thanks in advance
Pixelhouse said:
Hi,
i have TWRP installed with Magisk and ElementalX, everything was working fine, i just got an update for "google play system update" which i had to install.
I did that, but now i'm stuck on Bootloader screen which then boots into Fastboot Mode after a minute. Holding volume buttons and power does not help.
I still have following files that might help:
TWRP installed and the zip file for TWRP(which is still installed and working)
zip file for older version of Magisk
zip file for ElementalX
Is there anything i can do with TWRP or fastboot to keep my current files?
I assume my boot.img is missing due to that update?
I was running the latest OOS version.
Thanks in advance
Click to expand...
Click to collapse
Did you have any magisk modules installed before the reboot? If so delete them in TWRP data/adb/modules
@soka said:
Did you have any magisk modules installed before the reboot? If so delete them in TWRP data/adb/modules
Click to expand...
Click to collapse
First of all thanks for helping me, i did have 1 module installed vyper4android, which is already removed.
Also when i switch from Slot it goes past the bootloader screen but its stuck on the loading oneplus logo.
If it helps this is the current folderstructure: https://pastebin.com/xMWeW1uk.
Should there not be a build.prop in there?
Pixelhouse said:
First of all thanks for helping me, i did have 1 module installed vyper4android, which is already removed.
Also when i switch from Slot it goes past the bootloader screen but its stuck on the loading oneplus logo.
If it helps this is the current folderstructure: https://pastebin.com/xMWeW1uk.
Should there not be a build.prop in there?
Click to expand...
Click to collapse
Sounds like your Data is corrupt , if it wasnt it would def boot on a different slot.
I would suggest copying your data from your phone and make a back onto PC when phone is booted in TWRP.
Once done, wipe data only in TWRP , phone should boot.
Sorry wish i knew a better solution, been through myself a few times. Good luck:good:
@soka said:
Sounds like your Data is corrupt , if it wasnt it would def boot on a different slot.
I would suggest copying your data from your phone and make a back onto PC when phone is booted in TWRP.
Once done, wipe data only in TWRP , phone should boot.
Sorry wish i knew a better solution, been through myself a few times. Good luck:good:
Click to expand...
Click to collapse
Thanks for the info, i'm backing up my data as we speak but i prefer to wait for perhaps another persons view to see if a complete reset can be prevented with a lesser aggresive approach.
Thanks for your time though, have a nice day!
Pixelhouse said:
Thanks for the info, i'm backing up my data as we speak but i prefer to wait for perhaps another persons view to see if a complete reset can be prevented with a lesser aggresive approach.
Thanks for your time though, have a nice day!
Click to expand...
Click to collapse
Best of luck , i would also like to know if there is another approach to this.
Hello!
I wanted to update my oneplus 8 from 11.0.4.4 to newest version. OTA was not working idk why. I had magisk in place and I patched magisk to second partition or something like that [I dont remember how it was called] - I'm sure this is the reason of the problems. I turned off devices and wanted to boot into recovery, but suddenly it boot into Qualcomm crash dump mode with message: Attempted to kill init! exitcode: 0x00007f00 do_exit - that's all. I can't boot the system, I can;t boot into recover, I flashed patched boot, I flashed recovery - none of these works. Fastboot is present and recognized by PC.
First question can I do some backup through fastboot? To be honest I was not prepared for such problems. APKs are not even such a problem I care more about photos, documents and other data.
Can I flash some rom and restore phone back to life without wiping my personal data?
Maybe an idea would be to load TWRP recovery and then do backup, but how to boot into recovery when even after flashing recovery or booting via fastboot it enters in qualcoom crash dump mode. Something must be corrupted, but is it possible to fix some partition just in order to flash recovery to do backup of the files?
Please can you help me? I tried with some tutorials, but no success...
What did you try doing if OTA wasn't working?
You won't be able to use TWRP since you're on Android 11.
Okay I managed to get back to normal - since like I mentioned i patched the magisk into second slot, then probably this corrupted something. What has helped me is this: fastboot --set-active=b
It was not working via powershell I had to launch CMD and then it worked I switched slot to "b" and phone booted normally.
Regarding OTA I have no idea what has happened. The only things I have done is magisk with modules like xXx No Limits and YTB Vanced. To be honest nothing more. I'm at Oxygen OS 11.0.4.4.IN21AA with bootloader unlocked. What would you suggest to do in order to update to newest version?
I would disable the magisk modules first in case that is what caused problems. Then do a local upgrade using the full OTA zip. Then install magisk to the inactive partition. I think that would work, but I'm not sure if a messed up A partition might affect the installation. I don't think so, but I haven't read anything about it. After, you can try re-enabling the magisk modules.
I turned off all the modules obviously and still OTA is not working via the oneplus updater. It does not see the zip rom even though it's in the main directory. I don't know what is wrong...
Oh, that's strange. I don't know how to recover from there. If it were me, I would just backup my files and MSM, but that's a lot of work.
Did you check the obvious things for the zip file like making sure it ends in the right extension? Sometimes if you download it from OnePlus, it has a jar extension instead of zip.
L
trinidude4 said:
Oh, that's strange. I don't know how to recover from there. If it were me, I would just backup my files and MSM, but that's a lot of work.
Did you check the obvious things for the zip file like making sure it ends in the right extension? Sometimes if you download it from OnePlus, it has a jar extension instead of zip.
Click to expand...
Click to collapse
Lol yes you're right it was jar. Now the updater sees the zip file, but I'm afraid to update because I'm not sure if the phone won't brick or bootloop. What do you think?
I think it should be fine. I think the only thing that got messed up was the boot partition on the A slot and that will get overwritten with the OTA.
How about the root and magisk?
Okay I updated and it's working fine. I'm on 11.0.7.7 but now magisk is not working, how to get it back?
remialfa said:
Okay I managed to get back to normal - since like I mentioned i patched the magisk into second slot, then probably this corrupted something. What has helped me is this: fastboot --set-active=b
It was not working via powershell I had to launch CMD and then it worked I switched slot to "b" and phone booted normally.
Regarding OTA I have no idea what has happened. The only things I have done is magisk with modules like xXx No Limits and YTB Vanced. To be honest nothing more. I'm at Oxygen OS 11.0.4.4.IN21AA with bootloader unlocked. What would you suggest to do in order to update to newest version?
Click to expand...
Click to collapse
Any idea if it's possible to do something similar to rooted OP6?
I have a similar situation where I tried to update magisk and ended up with a bricked device.
I can reboot to fasboot, but I can't boot to recovery or flash anything through some pc flashing apps.
Hey Guys,
I Recently got a Bootloop problem with my s10/SM-G973F.
And after trying every other way of solving this and not having USB- Debbuging activated or the OEM unlocked my last option is to save the Data.
And after figuring out i could save them with a TWRP recovery i always read that u need to have AVB disabled in order to flash a custom ROM , but beacause USB-deb. isn't active I see no way to flash TWRP without getting a vbmeta error or a even harder Brick.
Is there any other way to use TWRP, flash a new vbmeta.img/boot.img or save the Data
hoping for good news
Brekker
With regards to this thread's title: NO.
Ok then let me change the question: Is it possible to flash/install TWRO without USB-Debugging?
Flashing Recovery / OTA / ROM is done by means of Fastboot, what requires phone gets booted into it's bootloader - what typically is done via ADB.
If installing a custom Rom by ADB there will be no problems with AVB you mean?
the problem with flashing by ADB in my case is that the phone isn't unlocked and i can't go into developer options to do so
brekker said:
Hey Guys,
I Recently got a Bootloop problem with my s10/SM-G973F.
And after trying every other way of solving this and not having USB- Debbuging activated or the OEM unlocked my last option is to save the Data.
And after figuring out i could save them with a TWRP recovery i always read that u need to have AVB disabled in order to flash a custom ROM , but beacause USB-deb. isn't active I see no way to flash TWRP without getting a vbmeta error or a even harder Brick.
Is there any other way to use TWRP, flash a new vbmeta.img/boot.img or save the Data
hoping for good news
Brekker
Click to expand...
Click to collapse
Can you boot into download mode? If so, you should be able to flash the stock firmware via Odin, just make sure you use the "Home CSC" file in the CSC slot in Odin when you flash the firmware nd not any other CSC, this should flash without wiping the user data that you are trying to save.
I already tried a firmware flash(first try newest one/2. & 3. try older ones). Result: still bootloop/ only getting to recovery mode.
What brought me up with the idea that my own data probably is corrupt.
Since i CAN go to recovery mode i thought i might just change this one to TWRP from where i could save my date (safe to SD) but because AVB and bootlocker are active/locked i wasn't able to install TWRP(didn't try because i heard of vbmeta errors) .
Is there another way i could install TWARP in my situation or save the data?