I currently have the SM-935F, Note FE International Variant
I wanted to flash TWRP and It failed, someone told me to use magisk and patch boot.img. I did that, flashed it and still failed.
I get this " Custom binary blocked due to remaining installment balance " When flashing custom stuff..
Related
Hello i have the Samsung Galaxy M10 SM-M105F.
I need to root the Phone for make Custom Rom or Edit the Scripts.
I have OEM Unlock the Bootloader and install the Unofficial TWRP with Odin From here
https://forum.xda-developers.com/ga...p-3-3-0-twrp-recovery-samsung-m10-sm-t3925243
TWRP work, but the System is in Bootloop.
Pls i need help to root My Device with working TWRP, System boot and Root
BlacklightMG said:
Maybe try flashing 'no-verity-opt-encrypt' and 'RMM Bypass' zip files?
EDIT: Flash Magisk zip too (it removes dm-verity), and format the data partition
Click to expand...
Click to collapse
It'll be rooted when you flash Magisk. And install the Magisk Manager APK too, to allow root control.
I actually rooted without TWRP by flashing the patched boot image generated from Magisk, and then performed a factory reset because file integrity couldn't be verified. But the Magisk binaries worked.
Amazing, can you pls Upload your Modified Bootloader for me and all People here ?
For make the Galaxy M10 open for users and Dev's.
Sorry for the late reply, but it's always better to do it yourself depending on what OTA update you are currently on. Download the firmware, extract the boot image and patch it with Magisk Manager. Then flash it with ODIN or Heimdall while in download mode. Then I had to factory reset because file integrity could not be verified. But the root was preserved.
BlacklightMG said:
Sorry for the late reply, but it's always better to do it yourself depending on what OTA update you are currently on. Download the firmware, extract the boot image and patch it with Magisk Manager. Then flash it with ODIN or Heimdall while in download mode. Then I had to factory reset because file integrity could not be verified. But the root was preserved.
Click to expand...
Click to collapse
Can you show us how to extract the boot image and patch it with magisk manager ?
I have on my SM-M105FD the Firmware 8.1.0 and Working Root.
Download the Firmware 8.1.0 on the PC and the AP File put on the Phone.
Download and install magisk apk on your Device and patch the AP in Magisk file.
flash the Firmware full with Odin but put on the AP Option the Patched AP file flash and work.
I have with Magisk install the Xposed Framework and install nice plugins.
My phone became stuck in a boot loop so i tried to go back but whenever i try to flash the stock rom through odin it says sw REV. Check fail (Bootloader) Device: 2, Binary 1
Iam Facing A Problem Kindly Guide Me Samsung Galaxy M10 Smm105f U2 Installed Twrp Rec
Iam Facing A Problem Kindly Guide Me
Samsung Galaxy M10 Smm105f U2
Installed Twrp Recovery With Odin
Wiped Data
Flashed Successfuy
No Verify Opt
Rmm State Bypass
And Magisk
Now I Want To Boot In System But After Booting In System Process Device Asking Me For A Password
"Ur device Is encrypted For Security Plz Type ur Pswrd "
Even I Haven't Locked Phone With Any Kind Of Privacy
And I Have Also Flashed A New Firmware But Problem is same it's Not Booting in System
It won't work on android 10, you have to switch to android 8.1,then try ?
DJSAJJAD said:
Iam Facing A Problem Kindly Guide Me
Samsung Galaxy M10 Smm105f U2
Installed Twrp Recovery With Odin
Wiped Data
Flashed Successfuy
No Verify Opt
Rmm State Bypass
And Magisk
Now I Want To Boot In System But After Booting In System Process Device Asking Me For A Password
"Ur device Is encrypted For Security Plz Type ur Pswrd "
Even I Haven't Locked Phone With Any Kind Of Privacy
And I Have Also Flashed A New Firmware But Problem is same it's Not Booting in System
Click to expand...
Click to collapse
It won't work on android 10, you have to switch to android 8.1,then try ?
Hello,
I've been using magisk for some time now and no problem until now. I recently updated my firmware to the last version and intended to update it and keeping magisk, but it didn't worked.
Every time I would flash magisk to the boot image by any mean, the system would boot and tell me "system was modified : press the nuke button to restore it (you will lose all your data lol)" or womething like that.
I was able to flash the stock update and get my phone working with the last firmware but magisk is not installed. I also installed TWRP without problems (helped me a lot to flash the stock boot.img and restore the phone).
I tried to install magisk using :
- Odin : Modified boot.img using magisk app and repacked as boot.img.lz4 in the AP file (with correct lz4 parameters)
- TWRP : Flashed modified boot.img from earlier
- TWRP : Flashed magisk ZIP directly
- Odin : Flash full AP modified by Magisk app
Every time, I have that black screen that tells me my system will be wiped if I continue. Magisk, Odin or TWRP do not return any error
Feel free to ask for any file or further info and thank you for your help !
Firwmare version is A520FXXUGCTKA_CL19831441_QB36271825_REV00
Magisk app returns :
- Ramdisk YES
- A/B NO
- SAR NO
Did you try after you install the new rom through Odin, then instal Twrp and then in Twrp you Format data(not wipe) then immediately install magisk. If dosen't work try with another firmware.
I never update firmwares if there isn any visible difference. Mostly is always some security fixes which i dont care about.
hey, Im having a different issue where after installing lineage 18.1 on my a5 i flashed the latest magisk but once i got in the phone it cycled into a bootloop and now it's eternally turned off cant even turn it into twrp. any suggestion?
Hello,
I purchased a G970F for the second time because I hard-bricked the first one due to not exercising as much caution, and since then, I've learned about the added difficulty the S10 generation has compared to the only other Samsungs I've had the displeasure of working with (S5, S4). I've read a number of guides since then, but I'm not entirely sure which still apply and which do not, since a lot of them are from 2019 / early 2020, and I've somehow managed to only soft-brick it once before bringing it back to current condition.
So, where I stand with my G970F:
Bootloader unlocked, downloaded the latest firmware via Frija (Android 11), patched the AP file, flashed the patched AP, along with BL, CP, CSC via Odin, booted with Magisk, then installed TWRP with SU privileges by downloading TWRP on the Play Store, going through the steps, yadda yadda. I've followed the two official guides (Official installation steps for Magisk by John Wu, and TWRP installation guide for Samsung Galaxy S10e (Exynos), also on the official page.
This is where I get stuck. I've come across some older guides on XDA that mention flashing multi-disabler, as well as mention of disabling FBE immediately after installing TWRP, on the TWRP 3.4.0 for Galaxy s10 Exynos thread on XDA. I don't know if these still apply (they're from 2019), because when I tried disabling FBE and booting to TWRP, it still shows the directories as encrypted hash, and when I tried flashing the multi-disabler on TWRP and rebooting, it gets stuck on Samsung splash (soft bricked), so I had to reboot to TWRP, reboot to download mode via ADB, then reflash the firmware with patched OS to start over. Multi-disabler soft-bricked my device, so I'm guessing it's not compatible with devices with Android 11?
The end goal for me here is to flash a custom rom safely, but I'm concerned about a few things:
The first time I hard-bricked my first G970F, it was during a root attempt, and the last thing I did was wipe data on TWRP, flash a zip, and reboot - and this essentially made it impossible to get into either Download mode or Recovery, it would just vibrate on black screen, stuck in a forever boot loop with no means to turn it off. I had to open the device to manually disconnect the battery.
I'm being extra cautious not to repeat the above scenario, so here is where my concern is: I've read that S10 series only have an A partition which leads to Magisk having to reside in a parasite-like existence with recovery, and the other landmine is that there is a 'VaultKeeper' that locks up the bootloader if an unauthorized OS is detected or some sort? I'm thinking that maybe either of these was responsible for my first G970F being stuck in an unbootable state, so I want to navigate carefully here.
I want to flash one of the unofficial roms linked on XDA by @expressluke , and I have Magisk patched AP + stock firmware + TWRP, only steps I have taken were from the two official guides (not XDA threads) for TWRP and Magisk, which never mentioned 'multi-disabler' nor disabling FBE. From my current state, how do I go about flashing the custom rom without potentially damaging recovery / partitions / triggering some Samsung trap like VaultKeeper? I'm a bit keen to do this, since it looks like having Magisk + stock firmware for some reason only recognizes my storage as 32GB instead of 128GB.
I had received incremental Update which I went through with. Then after incremental update was done, Downloaded the full ROM from oxygen updater and flashed patched boot, vendor boot and disabled dm-verity with vbmeta. Now the phone still shows orange state after flashing the patches and vbmeta. Is it because I rooted the phone on an incremental update? Will flashing the full zip (same version) and then rooting work? Or will it brick the phone. Will the orange state message go away if I do a full zip flashing via local update and then disable dm-verity with vbmeta. Please help me
Currently on NE2211_11_C.22
sinduchari said:
I had received incremental Update which I went through with. Then after incremental update was done, Downloaded the full ROM from oxygen updater and flashed patched boot, vendor boot and disabled dm-verity with vbmeta. Now the phone still shows orange state after flashing the patches and vbmeta. Is it because I rooted the phone on an incremental update? Will flashing the full zip (same version) and then rooting work? Or will it brick the phone. Will the orange state message go away if I do a full zip flashing via local update and then disable dm-verity with vbmeta. Please help me
Currently on NE2211_11_C.22
Click to expand...
Click to collapse
same with me, after check with fastboot oem device-info the device is unlocked
Wrong thread. Sorry.
1> The Shamshung recent firmware upgrade CWD1 might have some patches that makes rooting problemtic. I flashed TukiROM1.2 with Magisk 26.1 (boot.img patch method) the first time and it worked but as soon as I connected to wifi somehow it upgraded to Magisk Delta (thats how I came to know about the existence of Magisk Delta). Both Magisk 24.3 & 26.1 are not surviving reboots even after flashing (Magisk.OTA.persistence-v1.zip). So staying rooted on a stock factory rom is still an issue. I will try TukiRom1.3 though I request OP to compress the ROM file from 2.7GB to lesser if possible.
2> GSI RAW image files don't go past the bootlogo screen. I tried system image files Elixir, LPOS, Crdroid, EvolutionX, Derpfest etc., none of them booted no matter what dmverity or multidisaabler etc. I flashed before or after. The same raw images used to boot on the same device when it was Andoid 11 but now on Andoid 13 Stock Factory ROM CWD1 GSI images dont boot.
3> Since Magisk is either bootlooping the device after reboot/ After flashing Magisk/or Magisk patched images not surviving reboots, so when I flash the Stock boot image it goes straight to download mode with Vbmeta signed using public key etc errors, or if I flash Magisk patched boot image from TWRP it stuck on Shamshung logo.
4> I have tried some of Dev Roynas ROMs [https://sourceforge.net/projects/a51-builds-by-royna/files/] but they all end up with [TWRP error : 1 Assert failed : update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")] also same error through Sideload.
5> I tried (systemrw_1.32_flashable) by Dev Lebigmac but since the altercation between XDA & Lebigmac on March 2023 he got banned from XDA, I cant get hold of (systemrw_1.4_flashable) to try to check if CWD1 Update is RO-Rom and anything other than 1UI5.1 based wont flash etc.
If anyone has any solutions for CWD1 Factory Stock Rom pls assist. TIA