I am trying to flash Magisk to my Samsung Galaxy Tab S using TWRP but keep getting an error 1 code. Tablet is running Android 6.0.1, build T800XXS1CRI5.
The work around appears to require the stock boot.img file to create a patch.
Does anyone have this or know where I could find this?
Related
I neglected my phone for a while because it seemed like I was updating all the time. Now i am not sure of the best way to get current. I am currently on version 7.1.2. any advice? Thanks in advance
You should be able to flash the 8.0.0 OTA and then I'd flash the latest security update. Flashfire should work fine if you're rooted
Sent from my Nexus 5X using XDA-Developers Legacy app
The thing I am looking at says
"1. You'll need bootloader, radio and vendor images from latest Google OTA ( Current: OPR4.170623.006 )"
How do I get this? I already had it rooted and twrp installed.
Krazy_Calvin said:
The thing I am looking at says
"1. You'll need bootloader, radio and vendor images from latest Google OTA ( Current: OPR4.170623.006 )"
How do I get this? I already had it rooted and twrp installed.
Click to expand...
Click to collapse
If you are already rooted I would recommend checking out this guide https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930. Scroll down to the section labeled "9. How To Update To A New Build Of The Stock ROM".
The stock nexus images can be downloaded from https://developers.google.com/android/images.
After flashing you would have to root again using your preferred method. I haven't had any problems rooting with Magisk.
You'll have to reinstall twrp and any system mods you've previously installed when flashing this way though.
Hey, this worked perfect. Thank you.
So I just got this phone and im trying to install TWRP, root and put a custom rom in it.
When installing TWRP I get " only official binaries are allowed "
When downgrading I get " SW REV. CHECK FAIL. DEVICE: 4, BINARY: 2 "
And I chose this Stock firmware SM-A520F_1_20170629171527_2zusihxm47_fac for the BL
OEM unlock is turned on
FRP Lock is turned off
Any Ideas?
xDreDz said:
So I just got this phone and im trying to install TWRP, root and put a custom rom in it.
When installing TWRP I get " only official binaries are allowed "
When downgrading I get " SW REV. CHECK FAIL. DEVICE: 4, BINARY: 2 "
And I chose this Stock firmware SM-A520F_1_20170629171527_2zusihxm47_fac for the BL
OEM unlock is turned on
FRP Lock is turned off
Any Ideas?
Click to expand...
Click to collapse
Try flashing other version of twrp
Or downgrade to a earlier version
And some say that you have to wait 7 days yo get odin working properly after updating to the march downloader
elcreepyFP said:
Try flashing other version of twrp
Or downgrade to a earlier version
And some say that you have to wait 7 days yo get odin working properly after updating to the march downloader
Click to expand...
Click to collapse
Did some research and I need to wait it out. The RMM: Prenormal is messin up the flash. Ffs.. we bought the phone we should be able to do anything with it
Oh god... Look, you can't bowngrade your phone because of the bootloader. You can only update it. If you want to fix that RMM thing you have to wait up to 1 week without shutting down, or restarting your phone and without turning off the Wifi. If you do that you can flash twrp after a week and then inside twrp you can flash the rmm state fix (only official binaries)
Downgrade the boot to the newest 6.0 stock one alongside the newest 7.0, that's what I did to bypass the block Samsung put in
Please can you explain how you did it as I'm also stuck in the rmm lock. Did you inject the 6.0 shoot.bin into the 7.0 bootloader?
elderwolf123 said:
Downgrade the boot to the newest 6.0 stock one alongside the newest 7.0, that's what I did to bypass the block Samsung put in
Click to expand...
Click to collapse
Please can you explain how you did it as I'm also stuck in the rmm lock. Did you inject the 6.0 shoot.bin into the 7.0 bootloader?
darkhandsome18 said:
Please can you explain how you did it as I'm also stuck in the rmm lock. Did you inject the 6.0 shoot.bin into the 7.0 bootloader?
Click to expand...
Click to collapse
So go and download both the newest 6.0 and 7.0 stock Rom. Extract all the 7.0 into a folder except the boot.tar, open the 6.0 zip and just copy the boot.tar file and flash all of those like that. By doing so it should work unless there was an update after I did mine. Either way its worth giving it a shot
So heres whats going on. I am running Unlegacy android on my Verizon Galaxy Nexus as Kitkat runs the best on this phone and they are keeping the security update patches mostly up to date. Well i have been unable to get Root to work. Everytime i am met with Root binarys are not installed or detected. I have tried the latest SuperSU.zip and even going back a few but none of them work. On the forums for the rom it says *want root? just flash the latest SuperSU.zip* and that does not work. When i flash back to stock and root using Nexus Root Toolkit it works perfectly. I tried the Nexus Root Toolkit on the custom rom and that failed. I am at a loss right now and am wondering What am i doing wrong? Could someone point me in the right direction?
Dudefoxlive said:
So heres whats going on. I am running Unlegacy android on my Verizon Galaxy Nexus as Kitkat runs the best on this phone and they are keeping the security update patches mostly up to date. Well i have been unable to get Root to work. Everytime i am met with Root binarys are not installed or detected. I have tried the latest SuperSU.zip and even going back a few but none of them work. On the forums for the rom it says *want root? just flash the latest SuperSU.zip* and that does not work. When i flash back to stock and root using Nexus Root Toolkit it works perfectly. I tried the Nexus Root Toolkit on the custom rom and that failed. I am at a loss right now and am wondering What am i doing wrong? Could someone point me in the right direction?
Click to expand...
Click to collapse
use this one instead -> https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Now im having trouble getting busybox to install to the su/xbin location. Is really annoying as some of my root apps wont work correctly in busybox does not install there.
How to root first time phone with latest update with magisk method?
I'm find this simple way without TWRP
Is this way good?
No need to install TWRP in this way and no need some other .zip files like "no verify opt encrypt"
or something like that is not necessary. Is that a good idea? What are these additional .zip files for?
I have some experience with root on older samsung phones that have been routed by installing TWRP and flashing .zip magisk pach.
Nothing more was needed.
In short,
This way from joutube goes like this:
First the OEM is unlocked, magiskmanager.apk is downloaded and installed apk. After that the AP file that we downloaded before of firmware is patched with magisk app and inserted into the downloads folder.
After that, we flash the patched AP file over the odin and that's it. Will this work for me on the latest firmware?
I found this way that involves installing TWRP and some zip file.
xxsen said:
How to root first time phone with latest update with magisk method?
I'm find this simple way without TWRP
Is this way good?
No need to install TWRP in this way and no need some other .zip files like "no verify opt encrypt"
or something like that is not necessary. Is that a good idea? What are these additional .zip files for?
I have some experience with root on older samsung phones that have been routed by installing TWRP and flashing .zip magisk pach.
Nothing more was needed.
In short,
This way from joutube goes like this:
First the OEM is unlocked, magiskmanager.apk is downloaded and installed apk. After that the AP file that we downloaded before of firmware is patched with magisk app and inserted into the downloads folder.
After that, we flash the patched AP file over the odin and that's it. Will this work for me on the latest firmware?
I found this way that involves installing TWRP and some zip file.
Click to expand...
Click to collapse
I have used the method on a Samsung Galaxy Xcover 4s with new firmware.
However I don't know if it will work with Samsung Galaxy S9 due to the need for "dm-verity and force encryption disabler".
Have you rooted?
I have a consumer cellular branded XT2052-5. I'm running Android 10 Build Number QPGS30.82-135-16 which has the Dec 1 2021 security patch. I have successfully unlocked my bootloader, installed ofox recovery.img, and patched the boot.img using Magisk app. I'd like to update my ROM to the latest security patch.
As I understand from this webpage: https://www.thecustomdroid.com/install-ota-update-rooted-android-device-guide/ one option is use the Android Settings -> Systems -> Advanced -> System Update to download and then install the OTA, but don't reboot until after running Magisk and installing on the new partition. However, while it seems to install "Software update unsuccessful, couldn't apply system update to moto e..." (not verbatim since the message disappears quickly). Note also that the update file size is listed as only ~65MB while the example screen in the instructions at thecustomdroid.com inedicate it sholud be >1.5GB.
Anyway, I have resisted patching the boot.img and installing it in the other A/B partition via the Magisk app and am wondering how to proceed.
Can someone help me?
Mike
I had the same issue when trying to update via OTA. After testing I realized that the reason I couldn't update was because of the custom recovery installed. So I started all over went back to stock firmware using a program called RSD Lite to remove custom recovery completely and updated via OTA then patched with magisk. I ditched the custom recovery since it is not needed if you are on stock firmware.