So today I wanted to root my phone and flash a custom rom. I went to the PC and setted my phone in download mode, opened Odin, downloaded the TWRP from the S9 (SM-G960F) XDA Forum then I've selected on AP (Odin) the .img file but it gave me error. My phone said "Custom Binary (USERDATA) blocked by FRP lock" and now when I try to boot it says "An error occurred while updating the device software use the emergency recovery function" but it won't be recognized by the tool. I'm basically stuck with my phone giving me this message with a blue background.
Edit: Nevermind, I fixed it and got TWRP to work.
G935P failed to root, shows "Custom binary blocked by SECURE BOOT (modem.bin)", help!
I have Samsung S7 Edge (G935P) that I wanted to unlock, is in android version 7.0, so I downloaded root file from https://download.chainfire.eu/1087/...to-Root-hero2qltespr-hero2qltespr-smg935p.zip and flash the phone with it but the root flashing did not complete, then the phone started writing that I flashed the phone with unsupported unlock file, then I download stock rom from https://www.sammobile.com/ and flash the phone complete and it started writing on top of the screen in red color this below;
Custom binary blocked by SECURE BOOT (modem.bin)
And also showing on the screen this on the link below;
https://lionfinger.com/gsmerrors/s7edge_error1.jpg
This are also how the download mode and recovery mode shows;
Download mode => https://lionfinger.com/gsmerrors/s7edge_error2.jpg
Recovery mode => https://lionfinger.com/gsmerrors/s7edge_error3.jpg
Please someone help me on how to revive the phone to boot completely.
Thanks!
Hi , try with this one :
https://updato.com/firmware-archive-select-model?record=E6BB0C3642A611E99F15FA163EE8F90B
or this one :
https://updato.com/firmware-archive-select-model?record=E8FFA23642A611E99F15FA163EE8F90B
Teddy Lo said:
Hi , try with this one :
https://updato.com/firmware-archive-select-model?record=E6BB0C3642A611E99F15FA163EE8F90B
or this one :
https://updato.com/firmware-archive-select-model?record=E8FFA23642A611E99F15FA163EE8F90B
Click to expand...
Click to collapse
Thanks.
Both of them are the same file.
If I flashed this file, will it make it to come on completely?
Thanks
So i recently bought my Samsung galaxy A 10 ,I have been trying to root it but no luck.i unlocked the bootloader, installed proper adb drivers and latest version of odin on my Pc. I was following procedures from rootmydevice.com slash root-samsung-galaxy-A10(sorry cant post external links, im new).evrything went fine up until i got to the flashing part using odin. I am not sure weather the twrp file is corrupt or I am missing something.anyone who might know please help.
here is my device info:
SM-A105F
Have you tried this tutorial:
https://forum.xda-developers.com/galaxy-a30/how-to/root-galaxy-a30-magisk-canary-relaese-t3936481
I'm stuck in two problems here...
1- I dont have the option OEM Unlock on my developers option. I think that it maybe because ive checked that option before and after that it desapeared... When entering on download mode, it shows OEM Lock: ON (L), i dont know if that means OEM is unlocked or locked...
2- I cant find the files in step 2: .extract the boot.img.lz4 from the AP file.
Just came here to find a root method for the SM-A105M. Seems like not a lot of love for the A10 here.. Lol Anyways, I will be testing this method I came across out tonight. I will post the link but can't confirm it's working. I'll post my results tomorrow.
https://rootmydevice.com/root-samsung-galaxy-a10/
Sassiest said:
Just came here to find a root method for the SM-A105M. Seems like not a lot of love for the A10 here.. Lol Anyways, I will be testing this method I came across out tonight. I will post the link but can't confirm it's working. I'll post my results tomorrow.
https://rootmydevice.com/root-samsung-galaxy-a10/
Click to expand...
Click to collapse
do not flash that recovery is for sm-a720f aka A7 2017 https://www.gsmarena.com/samsung_galaxy_a7_(2017)-8335.php
hanonicaro said:
Have you tried this tutorial:
https://forum.xda-developers.com/galaxy-a30/how-to/root-galaxy-a30-magisk-canary-relaese-t3936481
I'm stuck in two problems here...
1- I dont have the option OEM Unlock on my developers option. I think that it maybe because ive checked that option before and after that it desapeared... When entering on download mode, it shows OEM Lock: ON (L), i dont know if that means OEM is unlocked or locked...
2- I cant find the files in step 2: .extract the boot.img.lz4 from the AP file.
Click to expand...
Click to collapse
Hi everybody,
I managed to root my A105FN with this method but with using the Magisk Manager v7.3.1 (no need of Magisk Canary)
It will be good to have a TWRP as welll but couldnt find a compatible one for the A10 (maybe useful for no-verity-opt-encrypt-6.0 and RMM-State_Bypass_Mesa_v2 patch)
we need :
1. odin 13.3.1
2. official firmware for your device (to get the boot.img from AP_xxxx part => follow the other tutorial how to get boot.img and boot.tar magisk patched)(keep an original boot.tar, just in case stuck at boot)
3. 7zip ZS
4. Last Magisk Manager (for me was v7.3.1)
5. computer + usb cable
Warning : this root will give you big warning messages at every boot !
First you need to unlock your bootloader :
1/Under android, activate internet and go under "Developper Mode" (Setting>About>Software>Build Number and Tap on the build number repeatedly). OEM unlock option should be there.
If not wait and retry to see if there ... (needs internet, dont know why)
2/Then go under Recovery Mode (VolUp + Power at phone boot). No method to go "Download Mode" directly for my device.
3/Under Recovery, we need to unlock the bootloader as well. I cant remember what exactly I pressed but try to press VolUp or VolUP+VolDown just after you click to reboot under bootloader... It should show you a page where you can choose to unlock bootloader by long pressing VolUP. if you dont have it, retry again ... without that no Flash possible.
Warning : this unlock will give you a big warning at every boot !
4/if you managed to unlock the bootloader, it s almost finished... know under Download Mode with bootloader unlock, flash with Odin the magisk patched boot.tar. Do not forget to untick "reboot" under Odin.
(reminder:follow the other tutorial to get the file and remember to use the Magisk Manager v7.3.1 and not the canary.)
5/when flash done, reboot by pressing VolDown+Power then immediately on reboot VolUp to go under Recovery Mode.
6/Under Recovery, erase data/factory reset and reboot to system
(7/I dont know if it s necessary the VolUp at reboot till the vibration)
8/wait the booting ... if you are stuck on the warning page for a long time, retry to reflash the original boot.tar and restart from "1/"
9/if you managed to boot under android, good news you are rooted but it s not finished yet....
Under Android check you have "OEM unlock option" under Developper Mode (cf. 1/) otherwise at the reboot the system will go KO.
So when you have "OEM unlock" enabled you can install Magisk Manager. It will ask you to install something and it will reboot automatically. That s why check you have "OEM unlock" enabled before doing that !
10/After reboot, Done. ROOTED.. enjoy ! you can reboot as you want ...
Hi everybody
Yes, I facing same everyone's problem, I see on "download mode" it's show "OEM Lock: On (L)" I try all the ways to unlock in YouTube but no any method to unlock
I try to unlock with all tools I have but useless (my tool: Z3X, Miracle box, MCT Dongle , NCK Dongle, Octopus Suite Unlock, Samkey Unlock Crack)
I try to flash Custom Rom with Odin , Try to Install "Magisk" and "TWRP" by method in many website , it's useless at all
However I think I need to unlock OEM first but I can't because OEM not show in the developer option
I try all the ways to appear the OEM Unlock toggle by a changing date, Flash tar.md5, factory reset in many website it's can't help me
Samsung developer very strong and can't hacking to "OEM Lock : On (L)" on Android Pie 9.0??
1.power off device
2.while press and hold vol+ and vol- plug the data cable with pc
3.then warning screen apper
4.volume up long press.
5.then press volume up.
bootloader will unlocked!
*sorry for my bad english
keepfun said:
Hi everybody,
er Download Mode with bootloader unlock, flash with Odin the magisk patched boot.tar. Do not forget to untick "reboot" under Odin.
Everything is about having this flash file you said you used. Please send us the link for that twrp file or whatever it is called right now as it is maybe not a Team Win Rom.
Thank you for your help
Click to expand...
Click to collapse
Hi,
It is not a TWRP file, it is the boot.img file from the original firmware for A10, patched with Magisk to access the root function, unfortunately it does not work, have tested it.
Benjamin.L said:
keepfun said:
Hi everybody,
er Download Mode with bootloader unlock, flash with Odin the magisk patched boot.tar. Do not forget to untick "reboot" under Odin.
Everything is about having this flash file you said you used. Please send us the link for that twrp file or whatever it is called right now as it is maybe not a Team Win Rom.
Thank you for your help
Click to expand...
Click to collapse
Click to expand...
Click to collapse
IneedFiveMore said:
Yes, I facing same everyone's problem, I see on "download mode" it's show "OEM Lock: On (L)" I try all the ways to unlock in YouTube but no any method to unlock
I try to unlock with all tools I have but useless (my tool: Z3X, Miracle box, MCT Dongle , NCK Dongle, Octopus Suite Unlock, Samkey Unlock Crack)
I try to flash Custom Rom with Odin , Try to Install "Magisk" and "TWRP" by method in many website , it's useless at all
However I think I need to unlock OEM first but I can't because OEM not show in the developer option
I try all the ways to appear the OEM Unlock toggle by a changing date, Flash tar.md5, factory reset in many website it's can't help me
Samsung developer very strong and can't hacking to "OEM Lock : On (L)" on Android Pie 9.0
Click to expand...
Click to collapse
If you have an US variant of the A10, don't expect TWRP to work on your device.
So i have some problems installing TWRP and the problem is when i boot on Download Mode, connect my phone on the pc, open Odin, enable AP, select the TWRP file and flash simply got fail on odin after flashing and in the phone is give this error ''only official binaries released can be flash'' i search on internet how to solve and all the tutorials is saying to enable the OEM unlock but i have already enable in Devolper Options so i need help becouse i can't use my phone without root. I need response. (sorry for my bad english)
Anyone?
Start Odin, load the desired firmware in the corresponding slots and then connect your phone to your computer.
Hi folks,
I've got a new A52 5G and wanted it to root. TWRP couldn't be used, because each and every possible solution failed. I even got stuck at boot with a message that the recovery couldn't get startet, even if I just restarted the phone without pressing the keys and without plugged USB cable.
Even flashing the original firmware was not possible. Then I tried to lock the bootloader again and flashing of the firmware was going on with odin. Puh... Then I used the Magisk method without TWRP to change die boot.img with magisk and load it in Odin. Success! I had now root on the phone. Yesterday I read about uninstall Magisk and install it afterwards on the B partition for updating the firmware over OTA. But accidentally I pressed the button below "uninstall" and it performed imediately. Now my phone is dead again... With unlocked Bootloader it is stuck in a bootload and I can start the Samsung recovery mode to wipe the cache for example. I wiped the phone completely, but it is still stucked in a bootloop.
Then I tried my first method: Just lock the Bootloader again (in the download mode) and then flash the new firmware with odin. But Odin either crashes or is giving me instantly the message "failed".
When I'm trying to start the phone (it happened also after locking the bootloader) i'm getting the download screen and the message with a big red !
"partition boot
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot) : 23B8CFD554, (VEMETA) : D23E59ACD6
CUSTOM boot
VBMETA A526BXXU1AUCA, 38851814R"
Now I unlocked the bootloader again, to access the recovery mode so I can turn it off. Otherwise its stuck in the damn bootloop. Can't flash and wipe doesn't help either.
Please help me somehow -.-
why did you u
Insomnium_D said:
Hi folks,
I've got a new A52 5G and wanted it to root. TWRP couldn't be used, because each and every possible solution failed. I even got stuck at boot with a message that the recovery couldn't get startet, even if I just restarted the phone without pressing the keys and without plugged USB cable.
Even flashing the original firmware was not possible. Then I tried to lock the bootloader again and flashing of the firmware was going on with odin. Puh... Then I used the Magisk method without TWRP to change die boot.img with magisk and load it in Odin. Success! I had now root on the phone. Yesterday I read about uninstall Magisk and install it afterwards on the B partition for updating the firmware over OTA. But accidentally I pressed the button below "uninstall" and it performed imediately. Now my phone is dead again... With unlocked Bootloader it is stuck in a bootload and I can start the Samsung recovery mode to wipe the cache for example. I wiped the phone completely, but it is still stucked in a bootloop.
Then I tried my first method: Just lock the Bootloader again (in the download mode) and then flash the new firmware with odin. But Odin either crashes or is giving me instantly the message "failed".
When I'm trying to start the phone (it happened also after locking the bootloader) i'm getting the download screen and the message with a big red !
"partition boot
Reason boot: Hash of data does not match digest in descriptor. [2nd] (3)
Calculated Hash of (boot) : 23B8CFD554, (VEMETA) : D23E59ACD6
CUSTOM boot
VBMETA A526BXXU1AUCA, 38851814R"
Now I unlocked the bootloader again, to access the recovery mode so I can turn it off. Otherwise its stuck in the damn bootloop. Can't flash and wipe doesn't help either.
Please help me somehow -.-
Click to expand...
Click to collapse
why did you OTA update the rooted phone
it is clearly written that your phone might brick.
what happened to you is your boot.img file is replaced with the newer version try replacing with the boot.img file of previous version.
I didn't, because I get (as always, this is not my first rooted phone) the message, that the system has been changed. OTA is not working and I read that uninstall magisk, update the phone and BEFORE reboot install magisk again on partition B. But I accidentaly pressed the second option in magisk, complete uninstall or how its name is. Didn't expected, that its start instantly without a "Caution" message.
Uninstalling Magisk should not bring my phone into a bootloop anyway, even if I wipe the cache. Or am I wrong?
raja0408 said:
what happened to you is your boot.img file is replaced with the newer version try replacing with the boot.img file of previous version.
Click to expand...
Click to collapse
That is the problem how do I do that, when everything with odin stops imediately or odin crashes.
Does Odin give you any error messages? Are you patching all of the files for the firmware AP BL CP & CSC? Are you making sure to use the non home CSC? Have you tried using Samsung Smart Switch to recover your phone?
Smart Switch didn't recognize the phone. The only error on Odin was "succeed 0 / failed 1).
It worked with Windows 10 notebook and the USB C Port. However it didn't worked on Win 7 and regular USB Ports. Very strange. Well, but now I have the original firmware and again lots of bloatware. TWRP doesn't work, impossible to boot with it. How can I root the A52 with Magisk that way, to deactivate it - if needed - for firmware updates? The phone doesn't has A/B partition.
Same happened to me.
So, I have an A52 Indian version and want to flash the Canadian firmware. I downloaded different versions of the Canadian firmware and used Odin to flash. I followed the instructions on downloading the files, loading them into Odin,hit Start and it kept failing. It was giving an error message regarding a repartitioning error. Could this be due to having to tick "OEM Unlocking" in developer options which I hadn't done?
Hey, is your phone still stuck ?
SHAREit​