Database Develop

[RECOVERY][ROOT][TWRP 3.0.2-0]Galaxy A8 sm-a800i - Exynos5433 -UPDATE 5/4/2016

Unofficial original release -TWRP recovery for the SM-A800I, Exynos5433
UPDATE 5/4/2016: TWRP 3.0.2-0 released
SEANDROID warning fix.
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
TWRP is now v3.0.2-0
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
UPDATE: 12/3/2016
New feature available in TWRP 3.0.0-0 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory images from the official firmware can now be flashed with TWRP instead of ODIN. I have extended this feature to include BOOT, RECOVERY, SYSTEM, CACHE, HIDDEN and RADIO(MODEM) partitions.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
NOTE: To flash the modem, first it needs to be renamed to modem.bin.img
F2FS support added.
Internal SUPERSU root option removed. This is to prevent boot loops on 5.11/6.0 devices
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
twrp_3.0.2-0_sm-a800i
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the SuperSU zip below with TWRP.
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS OR YOU WILL BOOT LOOP, ONLY USE THE FILE BELOW:
http://download.chainfire.eu/1019/SuperSU/SR2-SuperSU-v2.79-SR2-20170103215521.zip
GUIDE
https://boycracked.com/2016/04/23/h...2-0-root-samsung-galaxy-a8-sm-a800i-sm-a800f/
DEVICE TREE: github.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Credits: Me, Teamwin and my tester - abhinavparasher
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.

Rooted/Custom recovery installed successfully
Please refer to the attachments.

are you flash a800f????

davod84 said:
are you flash a800f????
Click to expand...
Click to collapse
This version is only for sm-A800i. Do not flash it on any other model.
Do NOT flash it on A800F

does it work with a800iz ? i will try it now
edit : no , it's not working , it's get restart but no root, recovery working but its stick at bootloop

A . S said:
does it work with a800iz ? i will try it now
edit : no , it's not working , it's get restart but no root, recovery working but its stick at bootloop
Click to expand...
Click to collapse
You let supersu root your device which is why you have bootloop. ONLY use the file provided for root.

ashyx said:
You let supersu root your device which is why you have bootloop. ONLY use the file provided for root.
Click to expand...
Click to collapse
Your right ; my device is rooted now
Just do not twrp install supersu!
Sent from my SM-N910C using Tapatalk

Hello Everyone!. i experienced an issue with my rooting process. Now its stuck at the Samsung Galaxy A8 Logo with Red caption on top that says. Custom Binary Blocked by FRP lock. i tried flashing twrp that i downloaded from this thread but it failed with an error on my phone that says. Custom Binary(RECOVERY) Bloced by FRP Lock. I need your guidance, please help me.

ashyx said:
You let supersu root your device which is why you have bootloop. ONLY use the file provided for root.
Click to expand...
Click to collapse
Hi,
I sent you a DM. Coukd you take a look at it??
Thanks in advance.
Sent from my SM-A700F using XDA Free mobile app

rissered said:
Hello Everyone!. i experienced an issue with my rooting process. Now its stuck at the Samsung Galaxy A8 Logo with Red caption on top that says. Custom Binary Blocked by FRP lock. i tried flashing twrp that i downloaded from this thread but it failed with an error on my phone that says. Custom Binary(RECOVERY) Bloced by FRP Lock. I need your guidance, please help me.
Click to expand...
Click to collapse
u need to enable usb debugging & oem unlock from devlper option on phone setting first before start flash root file with odin..
Sent from my SM-A800I using Tapatalk

ryez88 said:
u need to enable usb debugging & oem unlock from devlper option on phone setting first before start flash root file with odin..
Click to expand...
Click to collapse
Yeah. That's what I did wrong. I turned the OEM Unlock off after a successful root. that was yesterday, but today after restarting my phone the frp lock triggered.
---------- Post added at 03:06 PM ---------- Previous post was at 03:01 PM ----------
I guess what i need to do is to download the firmware from sammobile. when i go there i only see China and HongKong as country choices. my country isnt there and my fone says its from Vietnam.

rissered said:
Yeah. That's what I did wrong. I turned the OEM Unlock off after a successful root. that was yesterday, but today after restarting my phone the frp lock triggered.
---------- Post added at 03:06 PM ---------- Previous post was at 03:01 PM ----------
I guess what i need to do is to download the firmware from sammobile. when i go there i only see China and HongKong as country choices. my country isnt there and my fone says its from Vietnam.
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/download/59917/A800IXXU1AOJ1_A800IOLB1AOJ1_XXV/

Hi @ashyx. i downloaded the firmware file that i need, while extracting it is giving me a WinRar error that the file is corrupted. I know the downloaded completed properly because i was checking the whole time.
Additionally i believe i do need the latest Samsung USB Drivers that will work for my phone. I can't find it here.
Any tips would be great. and again, thanks a lot for the help

rissered said:
Hi @ashyx. i downloaded the firmware file that i need, while extracting it is giving me a WinRar error that the file is corrupted. I know the downloaded completed properly because i was checking the whole time.
Additionally i believe i do need the latest Samsung USB Drivers that will work for my phone. I can't find it here.
Any tips would be great. and again, thanks a lot for the help
Click to expand...
Click to collapse
Was the file in .rar/.zip format or did it end in .tar/.tar.md5?
Also, usb drivers can be found on samsungs official website for your country.
Most of the times, usb drivers do not need to be downloaded seperately if you are using an updated windows system.
Plug in your phone in download mode and start up odin. If the "com port" turns green, your phone is detected successfully.

Thanks for replying @abhinavparasher it was in zip file but when i extract it its in tar.md5. even when the error stating that the file is corrupted appears the whole extraction process still completes itself. and i already downloaded the USB driver and hope this works

rissered said:
Hi @ashyx. i downloaded the firmware file that i need, while extracting it is giving me a WinRar error that the file is corrupted. I know the downloaded completed properly because i was checking the whole time.
Additionally i believe i do need the latest Samsung USB Drivers that will work for my phone. I can't find it here.
Any tips would be great. and again, thanks a lot for the help
Click to expand...
Click to collapse
Use 7zip to extract it not Winrar.
If it says corrupted again then the download is not complete.
USB driver: http://developer.samsung.com/technical-doc/view.do?v=T000000117
Also you say your phone is made in Vietnam.
Samsung manufacturer their devices in Vietnam and Korea so that doesn't mean that's the firmware you need.
If you are from the Philippines then download the firmware for the Philippines.
www.sammobile.com/firmwares/database/SM-A800I
There is an app called Samsung phone info that will tell you everything you need to know about your device.

@ashyx thanks! i pre downloaded the Stock Firmware from the Philippines. i chose Openline since it is indeed openline. That is also the file that says it is corrupted when i try to extract it. I am downloading 7zip right now. I'll update you as soon as i get somewhere with this.
I would lie to try the Samsung app you're talking about but right now the only thing happening to my phone is go to logo screen then turn off again.

hi i flashed the twrp .do i flash supersu with odin? my phone:a800i/5.1.1

mohannad22 said:
hi i flashed the twrp .do i flash supersu with odin? my phone:a800i/5.1.1
Click to expand...
Click to collapse
TWRP.
Sent from my HTC One_M8 using XDA Free mobile app

https://github.com/ashyx/TWRP_Samsung_Galaxy_a8hplte/pulls
Please accept those changes

[TWRP][J5 Pro 2017] twrp recovery j5 pro 2017

Unofficial release -TWRP recovery for the Galaxy SM-J530F, Exynos7870
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this version just tested in J5 pro 2017 (android 7).
use latest kernel source from opensource.samsung.com
device tree : github
mtp not work in linux.
Instructions:
Flash with ODIN 3.10.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD:
http://www.mediafire.com/file/qpxypf08usashe4/twrp_v3.1.1_SM-J530F.tar
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/app...2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
http://www.mediafire.com/file/ln38z3q9c6iz3ny/patched-boot.tar

just putting my 2 cents in, this TWRP does not work with J530Y, it installs and boots to system after being installed but trying to reboot when you enter causes a boot loop incase any 1 comes across this and has the same model as me, my only complaint is the, debug? text in the terminal, but thats just a small gripe of mine

work in j530f duos 2GB RAM? no pro version?

twrp working fine.But when i rebooted i lost root.Super su not found installed .Should i reflash super su and boot image
---------- Post added at 10:36 AM ---------- Previous post was at 10:35 AM ----------
akaluptos21 said:
work in j530f duos 2GB RAM? no pro version?
Click to expand...
Click to collapse
i installed on pro version.2017 sm530f/fd version

work fine thks

and now?
any custom rom for j530f?

akaluptos21 said:
and now?
any custom rom for j530f?
Click to expand...
Click to collapse
Recovery came out yesterday and you already expect a rom to be ready ?? lol

what would happen if I flashed this on a frp locked SM-J530F? I assume that the OEM Unlocking is disabled, is it worth a shot or is it just a waste of time?

Can't moun data on SM-J530F (J5 2017) (non Pro)
Dont forget Point 2.(Format Data)
Now boot.img is taking a long time to flash. Trying to flash it in AP slot of Odin.
There is not an option in TWRP to install image.

Adlbert said:
There is not an option in TWRP to install image.
Click to expand...
Click to collapse
I dont understand, TWRP dont see boot patch file. In odin i cannot do anything

davidescion said:
what would happen if I flashed this on a frp locked SM-J530F? I assume that the OEM Unlocking is disabled, is it worth a shot or is it just a waste of time?
Click to expand...
Click to collapse
Waste of time

CeloxX said:
I dont understand, TWRP dont see boot patch file. In odin i cannot do anything
Click to expand...
Click to collapse
Mine could not see it as well. Maybe you should convert .tar to .img? After some research i found out TWRP can't flash .tar.
Although, recovery works fine without patching boot.

i did the same but end up well.Its working !!.Mine was both OEM and FRP locked .i did clean install of stock rom and disabled oem lock and installed twrp and rooted aswell.
---------- Post added at 05:30 AM ---------- Previous post was at 05:29 AM ----------
davidescion said:
what would happen if I flashed this on a frp locked SM-J530F? I assume that the OEM Unlocking is disabled, is it worth a shot or is it just a waste of time?
Click to expand...
Click to collapse
Adlbert said:
Mine could not see it as well. Maybe you should convert .tar to .img? After some research i found out TWRP can't flash .tar.
Although, recovery works fine without patching boot.
Click to expand...
Click to collapse
if u unzip that patch u would get .img and use that in twrp .

served in j5 Pro Sm-J530G?

FerXray13 said:
served in j5 Pro Sm-J530G?
Click to expand...
Click to collapse
check the model of the device according to the year

I root mine J530F yesterday and install twrp afterwords. It's working, but no 2/3/4G network anymore after flashing one of both.
Not possible to install boot image from twrp app. Also sound problems and brightness troubles.
I am going back to stock rom and wait for a while for a better later version.

Great news! :good:
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
bockywocky said:
I root mine J530F yesterday and install twrp afterwords. It's working, but no 2/3/4G network anymore after flashing one of both.
Not possible to install boot image from twrp app. Also sound problems and brightness troubles.
I am going back to stock rom and wait for a while for a better later version.
Click to expand...
Click to collapse
I think you have to do the inverse process. Flash twrp and after supersu

Oke I start from scratch again...
Flashed the stok ROM first.
Enable OEM and USB debugging
Flashed TWRP twrp_v3.1.1_SM-J530F with Odin3 v3.12.7 and disable Auto Reboot option.
Important: Reboot my phone holding Vol down, Home button, Power button AND when vibrate, Imminently pushed Vol up, Home button, Power button to go directly into TWRP.
Install Magisk-v14.0 (it fails, but just do it instead of installing SuperSU)
Boot my phone and restore al my apps from the play store include root checker. It has already root acces now
Install MagiskManager-v5.3.0.apk and dowload inside this app Magisk-v14.0.zip and choose Update (recommended)
With MagiskManager you are now able to disable root checking apps like SnapChat from root access. So my Snapchat is still working now
Hope this will help you.
If so than let me know with :good:
Bocky Wocky

bockywocky said:
Oke I start from scratch again...
Flashed the stok ROM first.
Enable OEM and USB debugging
Flashed TWRP twrp_v3.1.1_SM-J530F with Odin3 v3.12.7 and disable Auto Reboot option.
Important: Reboot my phone holding Vol down, Home button, Power button AND when vibrate, Imminently pushed Vol up, Home button, Power button to go directly into TWRP.
Install Magisk-v14.0 (it fails, but just do it instead of installing SuperSU)
Boot my phone and restore al my apps from the play store include root checker. It has already root acces now
Install MagiskManager-v5.3.0.apk and dowload inside this app Magisk-v14.0.zip and choose Update (recommended)
With MagiskManager you are now able to disable root checking apps like SnapChat from root access. So my Snapchat is still working now
Hope this will help you.
If so than let me know with :good:
Bocky Wocky
Click to expand...
Click to collapse
Hey
Do you Wipe Data before u Flash The Stock rom

Do I have to install on J5 2017 (no PRO)?

help rooting device with oreo 8.1

Hello,
I have this phone (infinix note 4 x572) running oreo 8.1 , build number :X572-H5312CE-O-180531V117
I wish to root it but after a while of searching i'm overly confused and frustrated..
can you please guide me through rooting it?
thanks alot

btw, does local update help in any way ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

All the info and installation instructions you need can be found in the release thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And if you encounter problems along the way, take a look at the troubleshooting guide.
https://www.didgeridoohan.com/magisk/Magisk
If you have further questions after that, make sure to be specific about what you need help with. "Guide me through it" is a bit too general and is already covered in the links above.

Didgeridoohan said:
All the info and installation instructions you need can be found in the release thread:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
And if you encounter problems along the way, take a look at the troubleshooting guide.
https://www.didgeridoohan.com/magisk/Magisk
If you have further questions after that, make sure to be specific about what you need help with. "Guide me through it" is a bit too general and is already covered in the links above.
Click to expand...
Click to collapse
thanks, the first prerequisite is the stock boot.img,, i tried backing it up using miracle box but encountered the 'unstable port' problem, what other possible ways i could extract the boot.img from my phone ?

and btw, i remember asking a guy somewhere and he told me that magisk won't root my device, is that true considering it's a less-known manufacturer ?

yazansayed said:
thanks, the first prerequisite is the stock boot.img,, i tried backing it up using miracle box but encountered the 'unstable port' problem, what other possible ways i could extract the boot.img from my phone ?
Click to expand...
Click to collapse
I'd try the TWRP route instead. I found this thread after about 2 minutes of searching on XDA (search words "infinix note 4 x572"):
https://forum.xda-developers.com/android/general/infinix-one-support-root-twrp-firmware-t3695803
It's a really good idea to use the XDA search, because it often works quite good.
If you want to keep the stock recovery on your device, you can actually just boot the TWRP image instead of flashing it. In that case, the command used in that thread:
Code:
fastboot flash recovery recovery.img
should be changed to:
Code:
fastboot boot recovery recovery.img
If that doesn't work, you can actually make quite easily make a backup of your boot image in TWRP and then patch that file in the Manager, to see if that works better.
If things don't work out in TWRP, make sure to provide the recovery log.
---------- Post added at 20:35 ---------- Previous post was at 20:32 ----------
yazansayed said:
and btw, i remember asking a guy somewhere and he told me that magisk won't root my device, is that true considering it's a less-known manufacturer ?
Click to expand...
Click to collapse
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...

Didgeridoohan said:
I'd try the TWRP route instead. I found this thread after about 2 minutes of searching on XDA (search words "infinix note 4 x572"):
https://forum.xda-developers.com/android/general/infinix-one-support-root-twrp-firmware-t3695803
It's a really good idea to use the XDA search, because it often works quite good.
If you want to keep the stock recovery on your device, you can actually just boot the TWRP image instead of flashing it. In that case, the command used in that thread:
Code:
fastboot flash recovery recovery.img
should be changed to:
Code:
fastboot boot recovery recovery.img
If that doesn't work, you can actually make quite easily make a backup of your boot image in TWRP and then patch that file in the Manager, to see if that works better.
If things don't work out in TWRP, make sure to provide the recovery log.
---------- Post added at 20:35 ---------- Previous post was at 20:32 ----------
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...
Click to expand...
Click to collapse
thanks alot for the quick responses, i will try it and reply as fast as possible

okay, i downloaded the twrp recovery image for Note 4, flashed it using Fastboot method successfully,
the problem is when i try to boot into the twrp recovery mode, i tried holding the power menu+ vol.down buttons, it sends me into a black screen with "factory mode" upwards in yellow, no button is working.
i then tried
Code:
adb reboot recovery
the phone reboots and says "No command" under a red triangle.
i then tried to flash the twrp img using sp flash tools, and flashed it successfully but the same errors occur, i can't seem to be able to boot into recovery mode.

i looked up for a solution for the "no command" problem, here's one:
I faced the same problem with nexus 6p. It works when you root immediately after flashing the TWRP. Keep the superSU file in the storage. Get into bootloader. Flash TWRP via fastboot. Without restarting anything, just press volume up/down buttons while in the bootloader to select recovery. TWRP will open. Flash the SuperSU.zip. Then restart the system. Next time, if you open recovery, you won't get the "no command". If you don't flash SuperSU and you try to open recovery later, you will get the "No command".
Click to expand...
Click to collapse
what i understood is that i shouldn't reboot my device using "fastboot reboot" , he says i should get into recovery mode directly without restarting, idk how to do that since there are no option for it on the screen, i just have
Code:
=> FASTBOOT mode...
on the screen !

Didgeridoohan said:
It's very possible... It depends on how stock the Manufacturer has kept Android on your device, what chipset the device has, and so on...
Click to expand...
Click to collapse
unfortunately i never used the sp flash tool before, so i tried flashing a stock rom but the device is now dead with "dram failed" error, i'll try fixing this first

It's tricky trying to help with a device you don't have...
Did you manage to boot to recovery? Usually you use the volume buttons to select the options and then the power button to confirm. You could also just use the fastboot boot option command I wrote earlier. It'll boot straight into TWRP.
There are a few threads for your device around, so if you need help specific to your device, that's the place to go...

everything is fine now,, fixed the device by flashing a rom named (X572-H5312CE-O-180203V55) then used magisk app to patch the included boot.img, flashed the patched boot.img using sp flash tool,, and everything is working fine now,,,
thanks alot

the twrp from the post you provided is for an older firmware, this is why i couldn't get into recovery after i flashed the provided twrp img,, there is no available twrp for the oreo version of the firmware, but i requested one from twrp builder project,, thanks alot, i've learnt alot in the last 24 hours

yazansayed said:
everything is fine now,, fixed the device by flashing a rom named (X572-H5312CE-O-180203V55) then used magisk app to patch the included boot.img, flashed the patched boot.img using sp flash tool,, and everything is working fine now,,,
thanks alot
Click to expand...
Click to collapse
could you upload the boot.img pls (the stock and the patched if possible )

[RECOVERY][ROOT]TWRP 3.2.3-1 Galaxy A7 2018/A750

Unofficial release -TWRP recovery for the Galaxy A7 2018 - SM-A750F EXYNOS 7885
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.2.3-0 Released
Aug 6, 2018
TWRP 3.2.3-0 is out now for most currently supported devices.
What's new in 3.2.3-0:
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here
Update 25/12/2018
Beta build released.
Current status - (Tested working)
Treble supported
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Hold POWER + VOL DOWN + VOL UP)
2. Load the file below into the AP slot, uncheck AUTO-REBOOT and hit start.
twrp_3.2.3-1_a750_251218
3. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
You should now see TWRP recovery.
4. Flash the RMM bypass zip
https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
5. Reboot to TWRP (Do not boot to the OS yet)
*****OREO ROOT INSTRUCTIONS:*****
NOTE: To mount data it is necessary to first *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
Continue with the instructions below to prevent the data partition becoming re-encrypted.
1. To root I suggest downloading and installing the latest Magisk as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
2. Copy the Magisk zip to a Micro sd card then install with TWRP.
3. Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, @BlackMesa123 for RMM bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

158 views, 20 downloads and not one reply.
Smashing guys. :good:

4. перепрограммируйте обходной zip- архив rmm.можно поподробнее?
Mod edit: English please!
Google translation:
4. reprogram the rmm bypass zip archive. can you be more specific?

Odin shows Failed !! Tried 3 Times ? Had to Flash the Firmare Again.
Help !!

notoriouschyld said:
Odin shows Failed !! Tried 3 Times Had to Flash the Firmare Again.
Help !!
Click to expand...
Click to collapse
Sorry about that, build error on my end. Fixed now.

It will not work on SM-A750FNXXU1ARIC?

Sfuj24 said:
It will not work on SM-A750FNXXU1ARIC?
Click to expand...
Click to collapse
Is that a statement or question?

Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?

powermen27 said:
Hey. Does it work well? I wanted to install myself. but it seems to me that this is not a complete instruction. Does OEM unlock need to be enabled?
Click to expand...
Click to collapse
No matter how complete an instruction is, if you don't bother reading it in the first place it's not going to make any difference.
As clearly posted in the OP:
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
Click to expand...
Click to collapse

sorry

ashyx said:
Sorry about that, build error on my end. Fixed now.
Click to expand...
Click to collapse
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!

notoriouschyld said:
Tried with the new TWRP.img but I'm having a Bootloop on the Samsung Boot Screen.
Help
Take your Time !!
Click to expand...
Click to collapse
Can you tell me which firmware build number you are running and if possible a screen shot of your device screen while booted to download mode?

Stuck in bootloop after flashing twrp
A750FXXU1ARK7

A7whatever said:
Stuck in bootloop after flashing twrp
A750FXXU1ARK7
Click to expand...
Click to collapse
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
https://androidfilehost.com/?fid=11410963190603874542

ashyx said:
Can you try this build, it's built with the kernel from the latest source available - A750FNXXU1ARIC.
Be aware OEM unlock must be enabled and you MUST boot to TWRP immediately after flashing with ODIN. Do not boot to the OS.
In TWRP immediately install Magisk.
Click to expand...
Click to collapse
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number

A7whatever said:
Same bootloop at the Samsung screen
However i use heimdall not odin so I have to unpack the tar file and flash the recovery image. i also use it to flash the stock recovery and it works perfectly
Does using it make a difference?
Edit: my phone is A750FNXXU1ARK2
A750FXXU1ARK7 Was my build number
Click to expand...
Click to collapse
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?

ashyx said:
Can you flash the bootloader from A750FNXXU1ARIC and see if it boots twrp?
Click to expand...
Click to collapse
Flashed the old sboot.bin however got the same bootloop

A7whatever said:
Flashed the old sboot.bin however got the same bootloop
Click to expand...
Click to collapse
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?

ashyx said:
So just to be clear :
Immediately after flashing twrp you are forcing a boot to recovery directly from ODIN?
Click to expand...
Click to collapse
Yes

A7whatever said:
Yes
Click to expand...
Click to collapse
Hmm looks like I'll have to take another look at the twrp config or kernel build.
If I pack the kernel into a boot image would you be willing to test if it boots?

Rooting Problem

I'm using SM-950F, Android 9, and i was trying to root my phone. But whenever i going to downloading mode and trying to fash TWRP but its says only official released binaries are allowed to be flashed samsung (recovery)
Note: OEM was Toggled on.

hainguyenthao said:
Why u don't paste any screenshot for device in download mode or even write any info it could help us to help you
Click to expand...
Click to collapse
Could you help me with editing the CP file in a Hex editor?
The phone is Samsung N960N. It already has OEM unlock but the KG state is always prenormal.

MrTanz said:
I'm using SM-950F, Android 9, and i was trying to root my phone. But whenever i going to downloading mode and trying to fash TWRP but its says only official released binaries are allowed to be flashed samsung
Note: OEM was Toggled on.
Click to expand...
Click to collapse
On the download mode screen, what does it say next to the KG State? Checking or prenormal?

stonedpsycho said:
On the download mode screen, what does it say next to the KG State? Checking or prenormal?
Click to expand...
Click to collapse
Its checking

MrTanz said:
Its checking
Click to expand...
Click to collapse
It should have flashed ok. What TWRP did you use?
You need to flash stock firmware to be able to get rid of the "only official binary" message, then try rooting again.

stonedpsycho said:
It should have flashed ok. What TWRP did you use?
You need to flash stock firmware to be able to get rid of the "only official binary" message, then try rooting again.
Click to expand...
Click to collapse
I used TWRP 3.1.1.0, 3.2.1.2 & 3.3.1.0

MrTanz said:
I used TWRP 3.1.1.0, 3.2.1.2 & 3.3.1.0
Click to expand...
Click to collapse
Try using the latest TWRP which is 3.4.0.0
https://eu.dl.twrp.me/greatlte/

stonedpsycho said:
Try using the latest TWRP which is 3.4.0.0
https://eu.dl.twrp.me/greatlte/
Click to expand...
Click to collapse
I flashed, still didn’t work

MrTanz said:
I flashed, still didn’t work
Click to expand...
Click to collapse
I don't have a clue then.
Is it possible your phone is made of different variants?

MrTanz said:
I'm using SM-950F, Android 9, and i was trying to root my phone. But whenever i going to downloading mode and trying to fash TWRP but its says only official released binaries are allowed to be flashed samsung (recovery)
Note: OEM was Toggled on.
Click to expand...
Click to collapse
Are you trying to root on stock rom or custom rom??

cheemak said:
Are you trying to root on stock rom or custom rom??
Click to expand...
Click to collapse
On stock rom

stonedpsycho said:
I don't have a clue then.
Is it possible your phone is made of different variants?
Click to expand...
Click to collapse
I'm trying to flash on stock rom! And using global variant

facing same problem ... unable to root and flash custom rom

Have you disable auto reboot in options setting in odin before flashing twrp?

MrTanz said:
On stock rom
Click to expand...
Click to collapse
Can you see success sign in Odin when you flash TWRP?? Can you able to enter TWRP after flashing with odin??

cheemak said:
Can you see success sign in Odin when you flash TWRP?? Can you able to enter TWRP after flashing with odin??
Click to expand...
Click to collapse
The problem is here, when I'm going to flash twrp by odin its says fail and in phone its says only official binarys can be use.

MrTanz said:
The problem is here, when I'm going to flash twrp by odin its says fail and in phone its says only official binarys can be use.
Click to expand...
Click to collapse
That means that the bootloader on your device is locked.

iceepyon said:
That means that the bootloader on your device is locked.
Click to expand...
Click to collapse
How?? My OEM is on from Developer Setting.

iceepyon said:
That means that the bootloader on your device is locked.
Click to expand...
Click to collapse
See
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

MrTanz said:
The problem is here, when I'm going to flash twrp by odin its says fail and in phone its says only official binarys can be use.
Click to expand...
Click to collapse
This case you have to reflash stock firmware and wait 7 days or more for kg state to become normal in download mode.
Then try flashing TWRP again.
There are threads for the kg state issue.
Read this thread.
https://forum.xda-developers.com/galaxy-note-8/how-to/oem-unlock-quick-fix-highly-recommend-t3791984