Related
How to Root Samsung Galaxy Note 10+ & Flash TWRP (Exynos Only)
NOTICE :
Before you move further, make clear that rooting device -
- Your warranty will be void
- Some of functions may not work on rooted device, some function may get back with un rooting, some may never.
- All your data on device will be lost
- Flashing custom binaries may brick (Usually soft but can be hard brick too) your device, so follow it on your own risk!
If you are ready with condition, move further -
Click to expand...
Click to collapse
Important : Since android Q, there is changes in rooting process, specially if you needs root with TWRP, So here I am dividing this guide in two parts.
1.Root with self preparing files (No TWRP) - Here you needs to patch stock files yourself. No TWRP installed.
2.Root with TWRP - You needs to just flash pre-patched files, Here you needs to have ROM installed same base as per files available. Though mostly latest verson will be available.
PART 1 : (Root Pie/Q base with magisk with patching files yourself, No TWRP)
Before moving to root device, must read every single instruction given below as any small mistake can lead to fail to achieve root or may brick the device.
A.Preparing Root files
You need to patch file to flash using Odin to root device.
1. Download stock firmware for your device (google search will give you many sites to download it) some common are e.g. Sammobile, Samfirmware tool)
you need to download file according your region and model (Dial *#1234# will give you details of existing firmware, download accordingly)
2. Once you finish download, extract files and keep all files on PC. From extracted files a file with name AP_[device_model_sw_ver].tar.md5 copy to your device.
3.Download Latest Magisk Manager and Install to your device
4.Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (AP_[device_model_sw_ver].tar.md5)
5.Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
6.Copy patched file magisk_patched.tar to Your PC
7.Download latest Odin (one is attached to end of this post) and extract to a folder on PC (I recommend on desktop)
Now next step is to modification on device
B. Unlocking Bootloader
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!)
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode,long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device
C.Installation (Flashing) custom binaries
1. Switch off the device and reboot to download mode (As said earlier) and select volume up to continue
2. Open Odin (downloaded from above instruction) as administrator
Select magisk_patched.tar file you have patched (as above instruction copied to PC) for AP tab of Odin
Select BL,CP and CSC file (Extract from stock firmware you have downloaded) with according respective tab of Odin (This is important, DON'T flash only magisk_patched.tar )
3.From Odin option - uncheck Auto Reboot option
4.Now start flashing and wait till it finish. When you see a PASS sign on Odin, disconnect device.
Now magisk is successfully finished but yet you need to follow instructions below.
D. Factory reset & Boot with magisk
After disconnecting device, keep holding Vol down + Side key to exit from download mode.
Here is very important - when you see device reboot As soon as the screen turns off, immediately press Volume Up + Side Key to boot to recovery partition. continue pressing the volume up button until you see the stock recovery screen.
In the stock recovery menu, use volume buttons to navigate through menus, and the power button to select the option. Select Wipe data/factory reset to wipe the data of the device.
Select Reboot system now, and immediately press Volume Up + Side Key. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
The device will automatically reboot for the first time it boots. This is completely normal and done by design.After the device is booted up, do the usual initial setup. You shall see Magisk Manager in your app drawer; if not, manually install the APK you downloaded and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Voila! Enjoy Magisk
PART 2 : (Root Q base with TWRP)
This requires to have your device on same base as per base of pre-patch files. I am giving link below of my ROM
http://www.mediafire.com/folder/d4ugie4yadxu6/N975F - Click link - First select your device (N970/N975/N976) - download file Instructions_Root_TWRP_BootloopFix.pdf
This file have complete details about how to root with stock recovery/TWRP. Also all required patched files will be available in "Q" folder of your device section,
Also "Q" folder have file BASE_N97*.txt - Name of this file indicates Model and base used for patched files, you should have same base installed.
Important :
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
(Powering up normally) → (System with NO Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
For more details read Installation guide by @topjohnwu from Here
All credit and thanks go to
@topjohnwu for magisk & Guide.
geiti94 for TWRP Here OP & Source
ianmacd for latest TWRP - Here OP & Source
Happy rooting!
Xposed
Just tried and eDxposed working fine.
- Install EdXposed installer
- from magisk download install Ritu-core module
- from magisk download install Ritu - EDxposed (yahfa)
Done.
We strongly recommend to make EFS backup as soon as you root device and store it to safer place
Don't you lose some Samsung function when you root and even relock the bootloader?
MrPhilo said:
Don't you lose some Samsung function when you root and even relock the bootloader?
Click to expand...
Click to collapse
Who cares?
Development can't go without this.
We developer need to risk it. No way.
Nice, already patched the rom to flash with odin. What is the button combination for recovery ?
Did that for a friend of mine on the S10e, guess the steps are all the same ??
Nice, so you will start to make roms ?
Keep it coming :laugh:
optx said:
Nice, already patched the rom to flash with odin. What is the button combination for recovery ?
Did that for a friend of mine on the S10e, guess the steps are all the same ??
Click to expand...
Click to collapse
OP updated for combo key
dr.ketan said:
OP updated for combo key
Click to expand...
Click to collapse
Many thanks, now i just have to wait for the Note 10+ to arrive in a few hours :highfive:
dr.ketan said:
Who cares?
Development can't go without this.
We developer need to risk it. No way.
Click to expand...
Click to collapse
Waiting for your guide, twrp, magisk and so on...
I am not developer, just tester, but still need root...
Dr Ketan. Most Welcome My Bro. Follow you since Note 9. U rock my bro :good:
namfat said:
Waiting for your guide, twrp, magisk and so on...
I am not developer, just tester, but still need root...
Click to expand...
Click to collapse
Twrp not available and possible only after samsung release kernel source code. Great news is @ianmacd getting N10 who known for twrp development. :good:
dr.ketan said:
Twrp not available and possible only after samsung release kernel source code. Great news is @ianmacd getting N10 who known for twrp development. :good:
Click to expand...
Click to collapse
That's really good to hear.
With you and the guy you've mentioned we have everything we need.
Cheers!
Did you have the OEM unlock right away in Developer options ? Cant see it on mine...
First Phone ever that has no OEM unlock right away ...
dr.ketan said:
Twrp not available and possible only after samsung release kernel source code. Great news is @ianmacd getting N10 who known for twrp development. :good:
Click to expand...
Click to collapse
OK then, please share root instruction first.
I dont know if N10 have the same problem but it happened with latest base on S10 5G that only using stock recovery if need rooted.
optx said:
Did you have the OEM unlock right away in Developer options ? Cant see it on mine...
First Phone ever that has no OEM unlock right away ...
Click to expand...
Click to collapse
My device have OEM unlock option available. If you dont have, maybe you need to wait for 7 days.
OP Updated with full instruction about how to root.
Kindly go through detail before proceed.
I'm assuming this is for Exynos version ONLY?
No where do I see this prerequisite posted anywhere but has always been in the past.
cpufrost said:
I'm assuming this is for Exynos version ONLY?
No where do I see this prerequisite posted anywhere but has always been in the past.
Click to expand...
Click to collapse
I have added to title but prerequisite is having OEM unlock enable which I believe not having on snapdragon isn't?
dr.ketan said:
I have added to title but prerequisite is having OEM unlock enable which I believe not having on snapdragon isn't?
Click to expand...
Click to collapse
So far with the SD when you go into developer mode there is no OEM unlock and I doubt it will show up later.
Don't know what is wrong. I have OEM turned on, Downloaded latest magisk manager, flashed all 4 parts. It did not work. If I flash stock, all is fine. Any clues ?
Pinu'u said:
Don't know what is wrong. I have OEM turned on, Downloaded latest magisk manager, flashed all 4 parts. It did not work. If I flash stock, all is fine. Any clues ?
Click to expand...
Click to collapse
OEM lock should be turned off AFAIK
Thx, will give it a try after flashing back stock.Irritating that OP says turn on ...
How to Flash TWRP & Root Samsung Galaxy A10 series (Unlocked Exynos Only, A10s (A107F/M) not supported)
NOTICE :
Before you move further, make clear that rooting device -
- Your warranty will be void
- Some of functions may not work on rooted device, some function may get back with un rooting, some may never.
- All your data on device will be lost
- Flashing custom binaries may brick (Usually soft but can be hard brick too) your device, so follow it on your own risk!
If you are ready with condition, move further -
Click to expand...
Click to collapse
Before moving to root device, must read every single instruction given below as any small mistake can lead to fail to achieve root or may brick the device.
A. Unlocking Bootloader
This is a basic step to root device. Go to settings - about phone - Software Information - tap multiple times on "Build number" - This will open developer option.
Now in settings at the end, you will have new option "Developer options" - look for OEM unlocking - Enable it.
(PS : If you don't see this option then you may need to wait up to 7 days or more to appear or may be on some operator you will get it never. Without this option you can not root your device, sorry!).
How to get OEM Unlock option back?
1. Open the Settings app. Tap on General Management → Date and time.
2. Use the toggle button to disable Automatic date and time.
3. Set date option will be enabled now. Tap on it, and set the date to about 10-20 days earlier.
4. Enable developer options.
4.a Go to your device Settings.
4.b Select ‘About phone’ » tap seven times on ‘Build number’.
└ This will enable Developer options under Settings.
4.c Go back to Settings » scroll down to the bottom and you’ll see Developer options menu.
5. Open developer options (in the Settings app itself), and find the option called ‘Auto update system‘. Use the toggle button to disable it.
6. Now, go back to the main screen of Setting, and then tap on Software update.
7. Disable the option ‘Download updates automatically‘.
8. Tap on ‘Download updates manually‘ option, but it will give you an error because of the wrong date, so it’s fine.
9. Restart the device.
10. Go to Settings > Developer options. The OEM unlock option should be enabled now.
Once you have enable OEM unlock option, switch off your device and reboot to download mode.
To put device in download mode - Press Volume Up & then Press Volume Down (Keep holding both) and connect device to PC with USB cable
When device start to download mode, long press volume up to unlock the bootloader. This will wipe your data and automatically reboot
Now let finish setup and again enable developer options (as said above), and confirm that the OEM unlocking option exists and grayed out!
If it is not then you can not root device!
Once you see this option and greyed out, you are ready to flash custom binary and root your device.2. setup the phone by skipping the wizard.
B. Disabling Android Verified Boot
1. Reboot to DOWNLOAD mode.
2. Download Odin 3.14.4 or newer and make sure Samsung USB drivers are installed.
3. Open Odin and put the vbmeta_disabled.tar into USERDATA slot and click "Start"
4. Your device will reboot but it will not boot into system as vbmeta signature has changed.
5. Your device will reboot into RECOVERY mode automatically and prompt "You have to reset your device to factory settings". Use "Volume Up" or "Volume Down" button to move and "Power" button to select. Confirm and reset the device to factory settings.
6. This is the last time the data on the device has to be cleared. Afterwards, if you don't re-lock bootloader or re-enable the Android Verified Boot, you will not lose your data. Be aware, a stock firmware package contains a Android Verified Boot Metadata Image (vbmeta.img) with verifications enabled. You will need to flash the vbmeta_disable image (put into USERDATA slot) along with the stock firmware (use BL, AP, CP, CSC slots) to make sure AVB is not re-enabled and the data is preserved.
C. Flashing TWRP/Magisk
link
Important :
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
(Powering up normally) → (System with NO Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(OEM Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Actual recovery)
Thanks and credit
For more details read Installation guide by @topjohnwu from Here.
All credit and thanks go to @topjohnwu for magisk & guide.
@dr.ketan for this guide from Here
@jesec for rooting guide Here
@ianmacd for multidisabler from here
Me
reserved.
Hi
Thanks for putting out the details guide!
I followed the steps carefully but got stuck at step 12 - the device boots to download mode and says: "error verifying vbmeta image..."
Luckily I was able to flash it back to stock - but the magisk_patched.tar looks faulty (I copied it using adb) so no root for me
Any ideas?
dani3ltony said:
Hi
Thanks for putting out the details guide!
I followed the steps carefully but got stuck at step 12 - the device boots to download mode and says: "error verifying vbmeta image..."
Luckily I was able to flash it back to stock - but the magisk_patched.tar looks faulty (I copied it using adb) so no root for me
Any ideas?
Click to expand...
Click to collapse
Unplug USB and replug it then make sure the size of tar file almost the same as origin.
for step 6, can we transfer the file via SD card?
afaneh92 said:
Unplug USB and replug it then make sure the size of tar file almost the same as origin.
Click to expand...
Click to collapse
Hi
I triple did it, but no luck
s_ryan said:
for step 6, can we transfer the file via SD card?
Click to expand...
Click to collapse
Sure.
dani3ltony said:
Hi
I triple did it, but no luck
Click to expand...
Click to collapse
Flash AP file only for some reason the BL tar include vbmeta.img but you can patch it too.
I also hit the same problem that soft-brick my phone.. just to confirm, the AP.md5 file u said to use, its name is this? AP_A105GDXU2ASE3_CL15918313_QB23932289_REV00_user_low_ship_meta_OS9.tar
afaneh92 said:
Sure.
Flash AP file only for some reason the BL tar include vbmeta.img but you can patch it too.
Click to expand...
Click to collapse
s_ryan said:
I also hit the same problem that soft-brick my phone.. just to confirm, the AP.md5 file u said to use, its name is this? AP_A105GDXU2ASE3_CL15918313_QB23932289_REV00_user_low_ship_meta_OS9.tar
Click to expand...
Click to collapse
yes
will try to make patched tar for all bootloaders when I got some free time.
Guide updated with more details
Hey dude,
Thanks for the update, I have a problem with step 7
7) Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (BL_[device_model_sw_ver].tar.md5).
I followed but magisk says No Boot image found, process error, installation failed
afaneh92 said:
Guide updated with more details
Click to expand...
Click to collapse
s_ryan said:
Hey dude,
Thanks for the update, I have a problem with step 7
7) Open Magisk Manager - Magisk (first one) - Install - select to "Select and Patch file" - Navigate file you have copied to device (BL_[device_model_sw_ver].tar.md5).
I followed but magisk says No Boot image found, process error, installation failed
Click to expand...
Click to collapse
My bad I didnt test this, the BL file contain vbmeta.img and need to be patched. Will try to find better solution.
You can flash stock BL file only then reboot again to bootloader and flash the rest files.
I see.. no worries.. I tried to flash the patched ap file with the stock bl, it soft brinked my phone the last time I did it.. anyway, I will wait for your workaround..
Appreciate your help!
s_ryan said:
I see.. no worries.. I tried to flash the patched ap file with the stock bl, it soft brinked my phone the last time I did it.. anyway, I will wait for your workaround..
Appreciate your help!
Click to expand...
Click to collapse
Can you replace vbmeta.img from patched AP with BL using 7zip.
remove md5 extension from BL file.
Guide updated and added flash TWRP instructions
afaneh92 said:
2.Download A10_multidisabler-*-1.41.zip from here and copy to Ext Storage (Because once you flash TWRP, Int storage will not be readable)
Click to expand...
Click to collapse
I think it would be helpful to users if there were a single multi-disabler for all Samsung devices. To that end, I've incorporated your changes for the A10 into my multidisabler and attached a test version to this posting.
Will you please test it? If it works for you, I'll issue a new release.
ianmacd said:
I think it would be helpful to users if there were a single multi-disabler for all Samsung devices. To that end, I've incorporated your changes for the A10 into my multidisabler and attached a test version to this posting.
Will you please test it? If it works for you, I'll issue a new release.
Click to expand...
Click to collapse
Thanks for the update, I was thinking to make pull request with changes. After make sure every thing is working as it should.
afaneh92 said:
Thanks for the update, I was thinking to make pull request with changes. After make sure every thing is working as it should.
Click to expand...
Click to collapse
Thanks. In your case, it's easier now if you just verify that the script I attached is working, since I've already integrated the changes you made in your clone.
Anyone who wants multidisabler support for a new device, however, can either send me a pull request against the latest code, or run the following script on a live, rooted device:
Code:
#!/bin/sh
getprop ro.boot.bootloader
echo --
ls -l /vendor/etc/init/pa_daemon*.rc /vendor/etc/fstab.exynos*
echo --
cat /vendor/etc/fstab.exynos*
echo --
su -c cat /init.rc
Hi dude..
I tried it.. unfortunately I still have problems.. here are some of the problems
1) my 7zip does not allow me to mod the BL files within the md5 extension, so I extracted them out and replaced the file manually then zip it to Tar.. (the VBmeta file is only 1kb) is that right?
2) after flashing via odin, I did a reboot, I encountered a VBMEta error, "Error verifying vbmeta image" Verification_disabled bit is (cant see it, block by the camera module)
In the end, i restored the firmware and got everything back.
s_ryan said:
Hi dude..
I tried it.. unfortunately I still have problems.. here are some of the problems
1) my 7zip does not allow me to mod the BL files within the md5 extension, so I extracted them out and replaced the file manually then zip it to Tar.. (the VBmeta file is only 1kb) is that right?
2) after flashing via odin, I did a reboot, I encountered a VBMEta error, "Error verifying vbmeta image" Verification_disabled bit is (cant see it, block by the camera module)
In the end, i restored the firmware and got everything back.
Click to expand...
Click to collapse
Try using this vbmeta.img (inside the tar file). It worked for me on the A20 with similar error. This file normally seems to be a checksum checker and if it doesn't match what the phone wants to see it gives you that error. But this file was modified to essentially be blank so there is nothing to give the phone an error.
READ EVERYTHING CAREFULLY!
1.Your phone warranty will be void after this tutorial!
2.Any small mistake and your phone is bricked/bootlooped!
3.All of your data will be lost so back it up somewhere
Click to expand...
Click to collapse
(Fixed the tutorial my bad.)
Click to expand...
Click to collapse
Hey Guys Im Back! Thank you for the support and how it blew up. I have tested this on Android 10 UI 2.0 and it works better then ever!
Also installed lineage os : https://forum.xda-developers.com/galaxy-a10/development/rom-lineage-os-a10-a105f-t4078093
So i tried using afaneh92's tutorial which will be linked here : https://forum.xda-developers.com/galaxy-a10/how-to/magisk-root-galaxy-a10-series-t3963822
Which lead to me bootlooping or softbricking and my storage was reduced from 32 gb to 16Gb so i decided to work on my own method!
Credits go to afaneh92 for the Twrp!
BEFORE YOU START YOU SHOULD HAVE
1.Samsung Drivers installed
2.Odin Installed
3.7zip Installed
4.A data transfer cable
5.A Proper working brain
If you have all of those lets start!
A: Phone settings
1.Go in settings>about phone>software information>build number tap that 5 times until it says "You are a developer now" then you will have Developer options unlocked
2.Then go in developer functions and find OEM unlocking tick that on scroll down until you see Usb Debugging and tick that also Disable Auto Updates option
B: Download TWRP and 2 other important files
1.Dial *#1234# and it will show the AP and some others, focus on AP paste it on google and get the download for it
2.After downloaded move the AP to your download folder in your android device
3.You will get a magisk_patched.tar after its been offically converted
4.Get the twrp for a10
Download the twrp file here : https://mega.nz/#!OU1WhSDZ!vQz5K1wpqBhg0hCD59aziaHPxFlUsT_2WG8SgT8p6iY
5.After you got everything open the .tar archive and extract vbmeta.img, boot.img and you should already have recovery.img on your Desktop
6.Grab all the 3 .img files and archive them into a .tar using 7zip, Now continue to step C,
C :Unlocking The Bootloader and Getting Into Download Mode (THE PART WHERE YOU RESET YOUR PHONE)
1.Turn Off your phone
1.2.Put your data cable into your PC(dont connect your phone to it yet)
1.3.Hold Volume Up and Down then insert the cable into your phone
1.4.When you see a bluescreen let go
1.5.Hold vol up until you see another screen then let go for 1 second and hold vol up again
2.Your device will reset itself and reboot
2.1.After the device has booted in into the setup take the cable out after Turn off your phone
2.2.Hold Vol Up and Down again and connect the cable
2.3.Let go when a blue screen appears then press vol up until you are in download mode
D: Flashing TWRP
1.Open Odin
2.Press on AP then find Desktop.tar and press open
3.Press start and let it do its thing
4.After your Phone has rebooted you oficially have TWRP installed
5.If you want to know hoe to root go to step E
E: Installing Magisk
Since magisk is counted as the best rooting option rn i will be using it in this tutorial(Sorry supersu fans)
1.Install Magisk Manager
2.Press on Install (first one) then press install again and after that press Install Zip Only
3.Then go into Twrp by doing the steps below
3.1.Turn off your device
3.2.Hold vol up and power button untill you see TWRP logo
4.Press install
4.1.Find magisk-v20.4(20400).zip
4.2Swipe right on the bottom to flash it then press reboot system now.
5.Now you have TWRP,Root and Magisk Congratulations!
What happens if something goes wrong.
1.SV Error Device 1 library 0 - You installed the wrong firmware look for the right firmware.To check go in recovery mode and look at the A105XXXXXX and then look for a download. Remider AP->AP BL->BL CP->CP HOME_CSC->CSC
2.vbmeta.img error - you have the wrong vbmeta.img file. Redownload the original firmware and take out the right vbmeta.img next time you try flashing. Reminder AP->AP BL->BL CP->CP HOME_CSC->CSC
3.A blue screen telling you to use samsung switch emergency update. That wont work so just flash the original firmware and try flashing twrp again.
4.When i try to boot in it gets me into TWRP - Thats just because that your data is corrupted and to fix it while in TWRP mode press wipe then swipe after its done press Reboot To System. That should be a fix
5.My internal storage is just full of weird numbers and I can't download anything on it! Go in TWRP then wipe,press advanced wipe, click on internal storage and data, swipe. That should fix the error
6.Boootlooping or Bricked! Installed corrupted firmware or the recovery was f-ed up. Then install the right firmware and redo the steps!
If you have issues during the process send it in the comment ill try to respond as fast as i can!
i notice thread title says exynos only.. u do know they are all exynos including a102u and a102u1 right?
Oh. Alright thanks for telling me.
Press on app? I have nothing in odin saying that, do you mean ap?
Edit: guess not....i'm bricked, stuck on galaxy logo, device not recognized by pc, holoding power button wont force reboot, nothing lol.
Edit2: can force reboot holding volume down and power but instantly stuck on logo again, cannot power off or enter download, nothing...bricked. Followed this guide to the letter. I assumed when you said app in odin you meant ap since there is no app button. My bootloader unlocked then I went to flash in odin the tar i made with patched boot and vbmeta, along with recovery linked. I used matching firmware to what my A10 has also. Would not mind if i could get back into download mode, but that looks impossible now.
Edit3: Managed to get download mode but had to be so quick...hopefully I can reflash stock now.
Cupcake 1.5 said:
Press on app? I have nothing in odin saying that, do you mean ap?
Edit: guess not....i'm bricked, stuck on galaxy logo, device not recognized by pc, holoding power button wont force reboot, nothing lol.
Edit2: can force reboot holding volume down and power but instantly stuck on logo again, cannot power off or enter download, nothing...bricked. Followed this guide to the letter. I assumed when you said app in odin you meant ap since there is no app button. My bootloader unlocked then I went to flash in odin the tar i made with patched boot and vbmeta, along with recovery linked. I used matching firmware to what my A10 has also. Would not mind if i could get back into download mode, but that looks impossible now.
Edit3: Managed to get download mode but had to be so quick...hopefully I can reflash stock now.
Click to expand...
Click to collapse
Im sorry for that and yes i meant AP.
If you wanted to reboot you had to hold vol up vol down and power at the same time and you sure that you unlocked the bootloader and used the right firmware?
Also tell me the AP and from which source have you downloaded it :laugh:
cmz6996 said:
Im sorry for that and yes i meant AP.
If you wanted to reboot you had to hold vol up vol down and power at the same time and you sure that you unlocked the bootloader and used the right firmware?
Also tell me the AP and from which source have you downloaded it :laugh:
Click to expand...
Click to collapse
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.
Cupcake 1.5 said:
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.
Click to expand...
Click to collapse
Oh! Im happy to hear that!
Cupcake 1.5 said:
All sorted now, back on stock with twrp and root It was a schoolboy error by me, the firmware downloaded was corrupted lol.
Click to expand...
Click to collapse
Could you also tell me from where have you downloaded the corrupted firmware so i can warn the others?
cmz6996 said:
Could you also tell me from where have you downloaded the corrupted firmware so i can warn the others?
Click to expand...
Click to collapse
The corruption was my side, I was using a download manager, but when I downloaded through chrome it was all good. As I said, schoolboy error on my part for not checking md5. I used sammobile site for the firmware.
Cupcake 1.5 said:
The corruption was my side, I was using a download manager, but when I downloaded through chrome it was all good. As I said, schoolboy error on my part for not checking md5. I used sammobile site for the firmware.
Click to expand...
Click to collapse
Alr thanks.
Can you upload it to Mediafire? Mega marks a "temporal error"...
Kyua said:
Can you upload it to Mediafire? Mega marks a "temporal error"...
Click to expand...
Click to collapse
At me it works?
Works on a105m?
Axeggus said:
Works on a105m?
Click to expand...
Click to collapse
Yes
i receive message that i running samsumg not official firmware after odin install recovery.tar
not work
cmz6996 said:
So i tried using afaneh92's tutorial which will be linked here : https://forum.xda-developers.com/galaxy-a10/how-to/magisk-root-galaxy-a10-series-t3963822
Which lead to me bootlooping or softbricking and my storage was reduced from 32 gb to 16Gb so i decided to work on my own method!
Credits go to afaneh92 for the Twrp!
BEFORE YOU START YOU SHOULD HAVE
1.Samsung Drivers installed
2.Odin Installed
3.7zip Installed
4.A data transfer cable
5.A Proper working brain
If you have all of those lets start!
A: Phone settings
1.Go in settings>about phone>software information>build number tap that 5 times until it says "You are a developer now" then you will have Developer options unlocked
2.Then go in developer functions and find OEM unlocking tick that on scroll down until you see Usb Debugging and tick that also Disable Auto Updates option
B: Download Your firmware and TWRP
1.Go in your calls app and dial *#1234# Then You will receive some details about your AP, CP etc. look at the AP then download the firmware by searching it on google and (download it from sites like sammobile etc)
2.After you got your firmware connect your device to your pc after its connected send the entire firmware to the device in the Downloads folder
2.1. Install Magisk Manager
3.After you're in magisk manager press on install (first one) then press install again then press Select and Patch a File
3.1.Chose the firmware you saved on the Downloads folder
3.2.After you tap on it it should've already started modifying it
4.After it finished go back to your pc and move the magisk_patched.tar back to your desktop (It should be located in Downloads)
5.From the magisk_patched.tar extract boot.img and vbmeta.img to your desktop
5.1.Download the twrp file here : https://mega.nz/#!OU1WhSDZ!vQz5K1wpqBhg0hCD59aziaHPxFlUsT_2WG8SgT8p6iY
5.2.After recovery.img(TWRP) has been downloaded move it to your desktop
5.3.Select all those three items(vbmeta.img,recovery.img,boot.img) right click then Find 7Zip then press add to archive
5.4.Rename the Archive name to recovery.tar and make sure the archive format is .tar
6.After the Archive has been downloaded follow the steps in C
C :Unlocking The Bootloader and Getting Into Download Mode (THE PART WHERE YOU RESET YOUR PHONE)
1.Turn Off your phone
1.2.Put your data cable into your PC(dont connect your phone to it yet)
1.3.Hold Volume Up and Down then insert the cable into your phone
1.4.When you see a bluescreen let go
1.5.Hold vol up until you see another screen then let go for 1 second and hold vol up again
2.Your device will reset itself and reboot
2.1.After the device has booted in into the setup take the cable out after Turn off your phone
2.2.Hold Vol Up and Down again and connect the cable
2.3.Let go when a blue screen appears then press vol up until you are in download mode
D: Flashing TWRP
1.Open Odin
2.Press on AP then find recovery.tar and press open
3.Press start and let it do its thing
4.After your Phone has rebooted you oficially have TWRP installed
5.If you want to know hoe to root go to step E
E: Installing Magisk
Since magisk is counted as the best rooting option rn i will be using it in this tutorial(Sorry supersu fans)
1.Install Magisk Manager
2.Press on Install (first one) then press install again and after that press Install Zip Only
3.Then go into Twrp by doing the steps below
3.1.Turn off your device
3.2.Hold vol up and power button untill you see TWRP logo
4.Press install
4.1.Find magisk-v20.4(20400).zip
4.2Swipe right on the bottom to flash it then press reboot system now.
5.Now you have TWRP,Root and Magisk Congratulations!
What happens if something goes wrong.
1.SV Error Device 1 library 0 - You installed the wrong firmware look for the right firmware.To check go in recovery mode and look at the A105XXXXXX and then look for a download. Remider AP->AP BL->BL CP->CP HOME_CSC->CSC
2.vbmeta.img error - you have the wrong vbmeta.img file. Redownload the original firmware and take out the right vbmeta.img next time you try flashing. Reminder AP->AP BL->BL CP->CP HOME_CSC->CSC
3.A blue screen telling you to use samsung switch emergency update. That wont work so just flash the original firmware and try flashing twrp again.
4.When i try to boot in it gets me into TWRP - Thats just because that your data is corrupted and to fix it while in TWRP mode press wipe then swipe after its done press Reboot To System. That should be a fix
5.My internal storage is just full of weird numbers and I can't download anything on it! Go in TWRP then wipe,press advanced wipe, click on internal storage and data, swipe. That should fix the error
6.Boootlooping or Bricked! Installed corrupted firmware or the recovery was f-ed up. Then install the right firmware and redo the steps!
If you have issues during the process send it in the comment ill try to respond as fast as i can!
Click to expand...
Click to collapse
hi guy... very good guide but it not work for my galaxy a10 ....i only have unlock the bootloader... if i try to get patched recovery ... it not work.... i have device blocked black screen for samsung software... or i cant go recovery mode it say me a error of vbmeta)
andrea2o18 said:
hi guy... very good guide but it not work for my galaxy a10 ....i only have unlock the bootloader... if i try to get patched recovery ... it not work.... i have device blocked black screen for samsung software... or i cant go recovery mode it say me a error of vbmeta)
Click to expand...
Click to collapse
You installed the wrong fir.ware check your right firmware.
BlueFolks said:
i receive message that i running samsumg not official firmware after odin install recovery.tar
Click to expand...
Click to collapse
Be cause you modified the firmware ignore that message
have you fixed the storage reduced to 16gb problem?
I have a Samsung galaxy sm-a10. I've tried everything here, even combination files. The error I ALWAYS get is 'failed flashing ROM... OEM lock'
Of course I have unlocked OEM in developer options, but still I get this error in the bootloader.
Any ideas?
Assalom-o-Alaikum!
How to Root and Flash TWRP on Samsung Galaxy A51 One UI 2.5 Android 10 CTJ1 Build number- Android security patch level: 1 October 2020. It may be work for SM-A515F, SM-A515F/DSN, SM-A515F/DS, SM-A515F/DST, SM-A515F/DSM, SM-A515F/N, SM-A515U, SM-A515U1, SM-A515W, PLEASE LET ME KNOW IF IT WORKED. This TWRP version is 3.5.0_10-1 developed and brought to you by [email protected] senior developer. You need installed TWRP for rooting or installing custom rom. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
Downloads
Enable Developer Options: go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Enable OEM unlock and USB debugging options ( Settings -> Developer options )
Make sure the bootloader are unlocked.
Download and Extract ODIN v3.13.1 from https://odindownload.com/SamsungOdin/
Download and Install Samsung Mobile Phone Drivers
Download Latest Magisk and Magisk Manager
Download twrp-a51-3.5.0_10-1_ianmacd.tar
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Flashing TWRP on Galaxy A51 CTJ1 firmware Android 10 Q :
Make sure the bootloader are unlocked, OEM unlock option is grey out
Enter Download Mode : Turn Power Off. Press and hold Volume Up + Volume Down key together, while pressing these keys, connect the phone to computer, then press volume up once.
Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
Flashing twrp-a51-3.5.0_10-1_ianmacd.tar as AP in ODIN, then click start.
Magisk is now successfully flashed to your device! Several steps before you can properly use the device.
DO NOT SKIP THIS STEP! Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until TWRP Recovery Mode Appears.
Select Install – select Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip Swipe to confirm Flash
Select Reboot to Recovery
Select Wipe -> Format data, type ‘yes’ and confirm
Select Reboot to System
Setup the phone, Done!
Rooting Instructions
Enter TWRP recovery : Turn Power Off. Press and hold Volume Up key + Power Key, When SAMSUNG logo appears release Power Key only, keep pressing Volume Up key until TWRP recovery appears.
Install Magisk Magisk-v21.2.zip or latest
Select Reboot to System
Connect the Phone to Internet
Open Magisk Manager ( If you can not see it, just wait for a moment)
Done! You can use Root Checker to check it, Enjoy!
If something goes wrong and you want to unroot it, just flash the ROM to make it works again.
Notes / Warning!
Use at your own risk, I’m not responsible for bricking your device.
Using the incorrect file may brick your device.
If your target device has a custom firmware flash counter, Rooting will trigger it. If you’re lucky, Triangle Away has support for your device and can be used to reset the counter.
If you have a KNOX-enabled device, Rooting will trip the KNOX WARRANTY VOID status !
If your device storage is encrypted, Rooting will wipe your data !
If you have locked bootloaders, flashing one of these will probably brick your device – with the exception of Nexus devices, which will usually automatically “OEM unlock” and wipe your data !
Make sure to backup your important data before root it.
Video Link:
Credit:
1. @ianmacd
2. @redymedan
Mohd Masab said:
Assalom-o-Alaikum!
How to Root and Flash TWRP on Samsung Galaxy A51 One UI 2.5 Android 10 CTJ1 Build number- Android security patch level: 1 October 2020. It may be work for SM-A515F, SM-A515F/DSN, SM-A515F/DS, SM-A515F/DST, SM-A515F/DSM, SM-A515F/N, SM-A515U, SM-A515U1, SM-A515W, PLEASE LET ME KNOW IF IT WORKED. This TWRP version is 3.5.0_10-1 developed and brought to you by [email protected] senior developer. You need installed TWRP for rooting or installing custom rom. Use it at your own risk! Follow the instructions carefully and Make sure to backup all your important data!
Downloads
Enable Developer Options: go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Enable OEM unlock and USB debugging options ( Settings -> Developer options )
Make sure the bootloader are unlocked.
Download and Extract ODIN v3.13.1 from https://odindownload.com/SamsungOdin/
Download and Install Samsung Mobile Phone Drivers
Download Latest Magisk and Magisk Manager
Download twrp-a51-3.5.0_10-1_ianmacd.tar
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Flashing TWRP on Galaxy A51 CTJ1 firmware Android 10 Q :
Make sure the bootloader are unlocked, OEM unlock option is grey out
Enter Download Mode : Turn Power Off. Press and hold Volume Up + Volume Down key together, while pressing these keys, connect the phone to computer, then press volume up once.
Open ODIN, IMPORTANT!: Uncheck “Auto Reboot” in Options!
Flashing twrp-a51-3.5.0_10-1_ianmacd.tar as AP in ODIN, then click start.
Magisk is now successfully flashed to your device! Several steps before you can properly use the device.
DO NOT SKIP THIS STEP! Press and hold Volume Down + Power Key, when the screen blank quickly press and hold Volume Up + Power key, when Samsung Logo appears release Power key only, keep pressing Volume Up key until TWRP Recovery Mode Appears.
Select Install – select Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip Swipe to confirm Flash
Select Reboot to Recovery
Select Wipe -> Format data, type ‘yes’ and confirm
Select Reboot to System
Setup the phone, Done!
Rooting Instructions
Enter TWRP recovery : Turn Power Off. Press and hold Volume Up key + Power Key, When SAMSUNG logo appears release Power Key only, keep pressing Volume Up key until TWRP recovery appears.
Install Magisk Magisk-v21.2.zip or latest
Select Reboot to System
Connect the Phone to Internet
Open Magisk Manager ( If you can not see it, just wait for a moment)
Done! You can use Root Checker to check it, Enjoy!
If something goes wrong and you want to unroot it, just flash the ROM to make it works again.
Notes / Warning!
Use at your own risk, I’m not responsible for bricking your device.
Using the incorrect file may brick your device.
If your target device has a custom firmware flash counter, Rooting will trigger it. If you’re lucky, Triangle Away has support for your device and can be used to reset the counter.
If you have a KNOX-enabled device, Rooting will trip the KNOX WARRANTY VOID status !
If your device storage is encrypted, Rooting will wipe your data !
If you have locked bootloaders, flashing one of these will probably brick your device – with the exception of Nexus devices, which will usually automatically “OEM unlock” and wipe your data !
Make sure to backup your important data before root it.
Credit:
1. [email protected]
2. Recovery-Mode
Click to expand...
Click to collapse
Keep up to making the next tutorial on Galaxy A51
Hello
Mohd Masab
It's my first Samsung .I had 4-5 Sony ,easy to root ,a Doogee S90 (NEVER BUY THAT !).
Is your method safe ,have U seen bad effects ,what fonctions did U lost ?
Bye .
Fred
Okay, so I completed the whole process, here are my observations:
The method provided above almost works. The problem is, that everytime you reboot to system when you are not rooted, TWRP will encrypt your files. So the solution is, that you have to format data and then install dm_verity and Magisk after each other, without a reboot! After that, you can boot to your system and set up your phone.
hargitomi said:
Okay, so I completed the whole process, here are my observations:
The method provided above almost works. The problem is, that everytime you reboot to system when you are not rooted, TWRP will encrypt your files. So the solution is, that you have to format data and then install dm_verity and Magisk after each other, without a reboot! After that, you can boot to your system and set up your phone.
Click to expand...
Click to collapse
I did what you said but still encrypts after reboot. Latest Magisk.
Hi, I am having problems with internal storage, I can not create folders and there are applications that I can not download, any solution?
Could someone tell me if it is compatible with the November update CTK1?
I have managed to root the phone, you can install everything and configure it, but after turning off the phone, I can't start it does bootloop, and it returns to the prompt "The phone is not running Smasung official software ..." never finishes starting? What do you recommend me to do?
020221
I reloaded the original rom and did the procedure again, taking into account the clarification of installing install dm_verity and Magisk after each other, without a reboot, and everything went well!
Hello abraxasboot !
So,for you ,the only problem was that U had to flash the files one after the other without rebooting ?
No other problem since that ?
Is the phone reacting well ?
Where did U find the official rom ?
Thanks and have a good day !
It worked for me but i can't access themes and other system apps
Is there any solution to access themes on rooted a51
Everything working well for me, thanks !
For ameer419 ,maybe try to flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip after EACH other thing U flash in TWRP ...
Good luck !
Hello everybody !
Bootloop til this morning ,maybe my fault :I erased system apps such as Facebook ,Youtube ...nothing very important .
I tried to start the procedure at the begining ,it doesn't work ...
Any idea from anyone ?
Thanks .
fleafred said:
Hello abraxasboot !
So,for you ,the only problem was that U had to flash the files one after the other without rebooting ?
No other problem since that ?
Is the phone reacting well ?
Where did U find the official rom ?
Thanks and have a good day !
Click to expand...
Click to collapse
How are you fleafred, https://samfrew.com/es/model/SM-A515F/ here you will find the original rom. I did the procedure again and had no more problems.
Cool ,I couldn't find it!
Just have to wait for 9h now ...
Thanks a lot ,abraxasboot ,I'll tell u.
Have a nice day .
It worked !
Ouf !Thanks a lot ...
I could re-install Magisk ,Xposed ...
I'd have like to know what I desinstalled to do that ...
Have a nice day .
Thank you very much, brother. You did the perfect way
== important ==
I was unable to flash and reboot into TWRP recovery after applying the official Samsung update from March, which updates Android from 10 to 11. Reboot into recovery would not work and I would always end in a boot loop.
I had to downgrade to Samsung's official Android 10 and used the binaries from January for that: https://samfrew.com/es/model/SM-A515F
After that, flashed TWRP again and was able to boot into recovery right away as it should be
If I follow the steps and flash twrp-a51-3.5.0_10-1_ianmacd.tar file using Odin I get an message:
'Only official release binaries are allowed to be flashed (RECOVERY)
The phone was recently purchased from Samsung official store, and has android 10 official firmware from feb 1st installed
Any clue please?
hey guys i used a lyf wind 1 to flash lineage os using twrp ..... so i wiped the previous os and unknowingly flashed another unsupported version of twrp ...when entering to recovery menu its all blank .... now i have no os and recovery ...... i couldnt flash stock rom because my device is not recognised as qualcomm port .............
pls any help ????
I have a working 11R twrp and all the DRM passers mejestics etc. to run.. you can boot the os after that that is the standard Samsung OS. np u can install LINAGE os 18.1 Andys march release, the Mejestics meaning u can patch root without Needing to part the orignal Firm and copy boot.img over. etc
Here is Link With GSI as Well and 2.5 GUI Twrp working and UI3.0
Google Drive: Sign-in
antuanix46 said:
If I follow the steps and flash twrp-a51-3.5.0_10-1_ianmacd.tar file using Odin I get an message:
'Only official release binaries are allowed to be flashed (RECOVERY)
The phone was recently purchased from Samsung official store, and has android 10 official firmware from feb 1st installed
Any clue please?
Click to expand...
Click to collapse
All good in the end, I needed to install samsung's firmware in odin first
Thank you for the good work
I am not responsible for any damage to your device, when you root you lose the Warranty
This guide collects A107F development info, but with the files ported to the A107M.
Thanks to the Galaxy A10s Development team for the original files.
You need to be on Android 10, if you are on android 11, there are tutorials to downgrade.
[BootLoader Unlock]
- Backup all your media, this process will delete your internal media including music and photos
- Go to developer settings and enable [OEM Unlock]
- Reboot to download mode (Turn off, press VOL- & VOL+ and connect the USB)
- When prompted, press and hold VOL + to enter bootloader unlock mode
- Press VOL + to confirm you want to unlock bootloader, this will wipe your data
- If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
- Go through the initial setup. Skip through all the steps since data will be wiped again later when we flash TWRP and magisk
- Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. This step is MANDATORY
- Perfect! Your bootloader now accepts unofficial images in download mode.
[Twrp Install]
At this point, you will need to install Odin on your PC.
Bootloader unlocked is OBLIGATORY.
On your MicroSD, put the "A10s-encryption-disabler.zip" file.
Boot to download mode, load "VBMeta" file in AP and "TWRP Ported to A107M" file in BL
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL+, VOL - and POWER buttons at the same time
- With the USB connected, and after the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and POWER button at the same time to boot to TWRP Recovery
NOTE: TWRP on this phone is not perfect, after booting to it, the screen will remain black after the Samsung logo disappears, simply wait 10 seconds and press the power button 2 times to have acces to it.
- After booting to TWRP successfully, go to WIPE in TWRP
- At the bottom, you should see an option to FORMAT DATA. After you select it, you will be asked to type "yes" in your keyboard. If you do not see this, you probably selected the wrong option.
- After formatting data, flash the "A10s-encryption-disabler.zip" with TWRP. This is done to avoid future bootloops.
- Optional, flash "Magisk.zip" if you want to keep on Stock ROM with root.
- After doing this, boot back to system and you are done
- Wait patiently for the device to boot for the first time
[Custom ROMs Install]
Bootloader unlocked and TWRP isntalled are OBLIGATORY.
Most of the GSI ROMs of this forum works fine on this device.
Only download a64 ROMs, do not confuse with ARM64.
On your MicroSD, put the ROM image.
- Boot to TWRP
- Go to Wipe > Advanced
- Wipe ONLY the System partition
- Go to Install
- At the bottom, select option "Install Image"
- Search for your GSI. It should be something that ends in .img. If it ends in .xz instead, you need to extract the image first
- Optional, if you want Root, flash the "Magisk.zip" file
- Go to recovery main menu
- Go to Reboot
- Reboot to Recovery
- After that, go to Wipe and perform a Factory Reset
- Reboot to System and enjoy!
[Downloads]
>Everything you will need<
I had a problem in Odin an "RQT-CLOSE" error occurred
Lukas203 said:
I had a problem in Odin an "RQT-CLOSE" error occurred
Click to expand...
Click to collapse
I GOT THE SAME THING WHATS HAPPENNING?
Worked perfectly on a107m with binary 6
Alexander_SlowD said:
Worked perfectly on a107m with binary 6
Click to expand...
Click to collapse
If it worked for you, what procedure did you follow? What rom did you use for bit 6? what tools did you use?
It worked for me at first time I see TWRP menu but I didnt followed the instructions correctly , I've tried to do it by myself after that , then I got a unnoficial bootloader error and RQT_CLOSE error when trying to do the Odin process again .
Any working solution are welcome and I will be thankfully , please !
Luciannus said:
It worked for me at first time I see TWRP menu but I didnt followed the instructions correctly , I've tried to do it by myself after that , then I got a unnoficial bootloader error and RQT_CLOSE error when trying to do the Odin process again .
Any working solution are welcome and I will be thankfully , please !
Click to expand...
Click to collapse
The TWRP is slready working for me , now I trying the Magisk part , I did this on Android 11 binary 6 trough A107MUBS6CWA3_ZTO firmware ...