Unofficial release -TWRP recovery for the Galaxy A3 - SM-A310F/FD/Y/M Exynos7580
UPDATE 14/4/2016: TWRP 3.0.2-0 released. TWRP build updated to 3.0.2-1
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
Seandroid warning fix.
New feature available in TWRP 3.0.0-x 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
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.
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.
twrp_3.0.2-1_sm-a310
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
To Root:
Flash the file below with TWRP:
DO NOT LET TWRP ROOT YOUR DEVICE IF IT ASKS. USE ONLY THE FILE BELOW:
http://download.chainfire.eu/969/SuperSU/
DEVICE TREE: soon
Guide
http://www.theandroidsoul.com/galaxy-a3-2016-twrp-recovery-89527/
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.
Credits: Me, Teamwin and my testers - nhthiencp
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
.
xmodgames
yes rooted. but xmodgames not working on sm-a310f
yareodigiy said:
yes rooted. but xmodgames not working on sm-a310f
Click to expand...
Click to collapse
try use supersu 2.45
chandarakk said:
try use supersu 2.45
Click to expand...
Click to collapse
No, don't it will brick your device.
ashyx said:
No, don't it will brick your device.
Click to expand...
Click to collapse
thanks. do you have a suggestion for xmod work ?
yareodigiy said:
thanks. do you have a suggestion for xmod work ?
Click to expand...
Click to collapse
Sorry I don't really play games, what's the issue?
Removed
alexax66 said:
I added samsung signature into recovery.img and repacked TWRP 3.0.0-0: https://drive.google.com/file/d/0B6vI9V6s4jvbRUtIZDRhb0ZjWlU/view?usp=sharing
Now label "recovery is not seandroid enforcing" will not appear when you start recovery mode.
I think that for those who don't install TWRP yet it is possible will not trip knox after installing this modded TWRP
Test it and report us.
Good luck!
Click to expand...
Click to collapse
Can you please not modify the work of others without getting permission first.
I would have got around to doing this myself, but it wasn't high on my priority list as its just a warning.
It will still trip knox regardless.
ashyx said:
Can you please not modify the work of others without getting permission first.
I would have got around to doing this myself, but it wasn't high on my priority list as its just a warning.
It will still trip knox regardless.
Click to expand...
Click to collapse
ОК!
does anyone tried to install xposed frameworks? if you did, which one should i install?
It's works perfectly, fast and stable so far
Thanks for your hard work and time
I'm using a310f from PLUS GSM in Poland, 16GB.
Custom recovery, root and xposed are working on this phone
Sorry for my English
stuck in download-screen
i'm stuck in the flashing of twrp using your files.
after booting the device into the download-mode, selecting the twrp-tar-file into the AP-slot of odin and pressing "Start!", odin prints:
<ID:0/015> Added!!
<ID:0/015> Odin engine v(ID:3.1100)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> recovery.img
<ID:0/015> NAND Write Start!!
<ID:0/015> RQT_CLOSE !!
<ID:0/015> RES OK !!
<ID:0/015> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
but the device is still in the download-mode and the small progress-bar stopped a few pixels before the end...
[see the picture]
{
"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"
}
fook42 said:
i'm stuck in the flashing of twrp using your files.
after booting the device into the download-mode, selecting the twrp-tar-file into the AP-slot of odin and pressing "Start!", odin prints:
but the device is still in the download-mode and the small progress-bar stopped a few pixels before the end...
[see the picture]
Click to expand...
Click to collapse
Nothing is stuck, you haven't followed the instructions in the OP.
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.
Click to expand...
Click to collapse
ashyx said:
Nothing is stuck, you haven't followed the instructions in the OP.
Click to expand...
Click to collapse
you're right ..
i thought there should be more "feedback" on the device that tells me, the flashing was successfully finished.
"after flashing" means, when ODIN states the process is done, it is done.
UPDATE 14/4/2016: TWRP 3.0.2-1 released.
hi guys
thanks for your great rec
i have a problem , in voice calls the other side suddenly dont hear my voice but i do i after few second again the voice comes and go
its very annoying on voice calls for me , is this about radio? if yes where can i found mine? A310F Asia Iran
thanks all waiting for your help
I get a "failed" thread, seems like Odin doesn't connect properly to my phone.
* plug in the phone with usb cable
* downloaded the Samsung USB driver (SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.25.0-retail.exe)
* opened odin
* unchecked auto-reboot
* loaded the twrp file to AP
=> fail
Attached photo:
Any ideas?
ulfmais said:
I get a "failed" thread, seems like Odin doesn't connect properly to my phone.
* plug in the phone with usb cable
* downloaded the Samsung USB driver (SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.25.0-retail.exe)
* opened odin
* unchecked auto-reboot
* loaded the twrp file to AP
=> fail
Attached photo:
Any ideas?
Click to expand...
Click to collapse
You need to put the device in download mode first. Also make sure OEM unlock is enabled and FRP lock is off.
ashyx said:
You need to put the device in download mode first. Also make sure OEM unlock is enabled and FRP lock is off.
Click to expand...
Click to collapse
Cheers @ashyx :good:
Confirmed working like a charm for my new A3 2016 (bought in Norway)
Now I can uninstall all the crap bloatware
(f**k you Samsung for bundling all sorts of crap that I can't remove, even as the owner of the device)
Great work, thanks a lot!
Is the build configuration open source? Is it possible to build it by myself? Can you give me a link to the sources?
Thanks, regards
Related
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
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)?
TWRP 3.3.0 For A3 2017
{
"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"
}
Disclaimer
Code:
/*
* Your warranty will be VOID after installing a custom recovery.
*
* Get notified yourself that I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this recovery
* before flashing it!
* YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device,
* I will laugh at you.
*/
This is for A3 2017 only
Download
• TWRP Unoffiicial for a3 2017 : host.mcfy.fr
• TWRP Offiicial for a3 2017 : twrp.me
Instructions
• With Odin : download the .tar file and flash on AP case of Odin
• With Twrp : download the .img file on your phone and flash it throw the older twrp by the image installation menu
Credits and sources
• @TwrpBuilder Our team check our project ! twrp buider
• source : https://github.com/TwrpBuilder/android_device_a3y17lte
Changelog
Code:
- 5th March 2018 : Initial build : TWRP 3.2.1-0
- 10th March 2018 : Fixed ODIN ZIP format
- 26th June 2018 : TWRP is now official
- 8th august : TWRP 3.2.3
- 18th Aprile 2019 : TWRP 3.3.0
what is difference between this version and https://forum.xda-developers.com/sa...elopment/recovery-galaxy-a3-sm-a320f-t3562302 this version of twrp?
EVILWAR83 said:
what is difference between this version and https://forum.xda-developers.com/sa...elopment/recovery-galaxy-a3-sm-a320f-t3562302 this version of twrp?
Click to expand...
Click to collapse
This one is up to dated, and can flash oreo zip, my lineage 15.1 zip's were edited to can be flashed on the older twrp
THANK YOU
McFy, amazing contribution!
i got a new a3 (2017 sm-a320f) and wanted to flash twrp. since there is [no official release][1], i came across your unofficial release, which is the most up to date i could find.
i am on a macos box, still trying to figure out what is the safest and easiest way to flash the bootloader ([odin is only compatible with windows][2]) and whether i should unlock the bootloader... but once i do, i am definitely going to give your build a try and report back.
searching the net i couldn't find how one contributes his code to the twrp upstream. could you please share any details you have on it as i would be happy to see your code changes being pushed to the twrp upstream for others to enjoy it.
Code:
[1]: https://teamw.in/Devices/Samsung/
[2]: https://samsungodin.com/
vwtc6yc8e said:
McFy, amazing contribution!
i got a new a3 (2017 sm-a320f) and wanted to flash twrp. since there is [no official release][1], i came across your unofficial release, which is the most up to date i could find.
i am on a macos box, still trying to figure out what is the safest and easiest way to flash the bootloader ([odin is only compatible with windows][2]) and whether i should unlock the bootloader... but once i do, i am definitely going to give your build a try and report back.
searching the net i couldn't find how one contributes his code to the twrp upstream. could you please share any details you have on it as i would be happy to see your code changes being pushed to the twrp upstream for others to enjoy it.
Click to expand...
Click to collapse
I would at your place look at jodin3 for mac, after having installed it, it will be the same than for the windows users, tick AP box select twrp and hit flash, think to disable OEM on developper settings
McFy said:
I would at your place look at jodin3 for mac, after having installed it, it will be the same than for the windows users, tick AP box select twrp and hit flash, think to disable OEM on developper settings
Click to expand...
Click to collapse
thank you for the reply!
from what i understood, jodin3 has issues flashing "large" files and no one provided any quantification to what is "large" so i thought i better use [heimdall][1].
if you worked with jodin3 and you were able to flash twrp, i will head and do that.
@McFy, could you please relate to my question on how can we merge your code changes into twrp code base?
[1]: https://glassechidna.com.au/heimdall/
vwtc6yc8e said:
thank you for the reply!
from what i understood, jodin3 has issues flashing "large" files and no one provided any quantification to what is "large" so i thought i better use [heimdall][1].
if you worked with jodin3 and you were able to flash twrp, i will head and do that.
@McFy, could you please relate to my question on how can we merge your code changes into twrp code base?
[1]: https://glassechidna.com.au/heimdall/
Click to expand...
Click to collapse
Maybe, but twrp is not a large file, large file would be a rom, what do you mean by merging my change to twrp code base ?, I didn't edited source code twrp, just build it for a3 2017
For me Odin gets stuck at: NAND Write Start!!
Complete log:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1101)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery_a3y17lte-050318.img
<ID:0/006> NAND Write Start!!
Click to expand...
Click to collapse
When I use my existing TWRP, it doesn't see the image file (.img and .tar, both do not work). What am I doing wrong?
UPDATE:
Oh my bad, I found out in TWRP I have to press "Install image" to actually see the image file.
xtracter360 said:
For me Odin gets stuck at: NAND Write Start!!
Complete log:
When I use my existing TWRP, it doesn't see the image file (.img and .tar, both do not work). What am I doing wrong?
UPDATE:
Oh my bad, I found out in TWRP I have to press "Install image" to actually see the image file.
Click to expand...
Click to collapse
And you have to flash the .tar file in Odin. It seems you tried the .img file.
McFy said:
Maybe, but twrp is not a large file, large file would be a rom
Click to expand...
Click to collapse
in case something goes wrong, i wanted to be able to flash stock recovery.
the stock firmware (rom) that i have in hand, does not contain a recovery image, at least that is what it seems to a samsung device newbie like me. these the files that i do have within the firmware archive:
Code:
AP_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship_meta.tar.md5
BL_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship.tar.md5
CP_A320FXXU2BQG4_CL589129_QB6977370_SIGNED.tar.md5
CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
HOME_CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
so if there is no way to only flash the stock recovery, i am afraid of bricking the phone...
@McFy: i am sure you could shed the light on the matter - what is the best way (if there is such) to flash only the stock recovery?
vwtc6yc8e said:
in case something goes wrong, i wanted to be able to flash stock recovery.
the stock firmware (rom) that i have in hand, does not contain a recovery image, at least that is what it seems to a samsung device newbie like me. these the files that i do have within the firmware archive:
Code:
AP_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship_meta.tar.md5
BL_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship.tar.md5
CP_A320FXXU2BQG4_CL589129_QB6977370_SIGNED.tar.md5
CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
HOME_CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
so if there is no way to only flash the stock recovery, i am afraid of bricking the phone...
@McFy: i am sure you could shed the light on the matter - what is the best way (if there is such) to flash only the stock recovery?
Click to expand...
Click to collapse
https://desktop.firmware.mobi/device:141/firmware:15535 there you can download latest stock recovery
Pat750 said:
And you have to flash the .tar file in Odin. It seems you tried the .img file.
Click to expand...
Click to collapse
Nope I selected the .tar file (btw: you can't pick an .img file in Odin). The log is .img because I think Odin extracted it.
vwtc6yc8e said:
in case something goes wrong, i wanted to be able to flash stock recovery.
the stock firmware (rom) that i have in hand, does not contain a recovery image, at least that is what it seems to a samsung device newbie like me. these the files that i do have within the firmware archive:
Code:
AP_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship_meta.tar.md5
BL_A320FXXU2BQI3_CL11883096_QB15086315_REV00_user_low_ship.tar.md5
CP_A320FXXU2BQG4_CL589129_QB6977370_SIGNED.tar.md5
CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
HOME_CSC_OJV_A320FOJV2BQI3_CL12328718_QB15071626_REV00_user_low_ship.tar.md5
so if there is no way to only flash the stock recovery, i am afraid of bricking the phone...
@McFy: i am sure you could shed the light on the matter - what is the best way (if there is such) to flash only the stock recovery?
Click to expand...
Click to collapse
Yes it's possible. you can extract the recovery.img from AP package and either flash as img in twrp or tar it and use odin. Samsung are pretty safe from hardbrick, you will everytime have access to the download mode
McFy said:
Yes it's possible. you can extract the recovery.img from AP package and either flash as img in twrp or tar it and use odin.
Click to expand...
Click to collapse
the recover.img file is indeed within the ap package.
if flashing twrp fails and i have to flash the stock recovery, clearly i won't be able to use twrp to do so
@McFy: thank you for answering so many questions. deeply appreciated.
McFy said:
tar it and use odin.
Click to expand...
Click to collapse
i see that the files have the tar.md5 file extension and not only tar.
(1) where is the md5 digest?
(2) why is it names like that?
(3) can i just only tar the recovery.img and i am done?
vwtc6yc8e said:
the recover.img file is indeed within the ap package.
if flashing twrp fails and i have to flash the stock recovery, clearly i won't be able to use twrp to do so
@McFy: thank you for answering so many questions. deeply appreciated.
i see that the files have the tar.md5 file extension and not only tar.
(1) where is the md5 digest?
(2) why is it names like that?
(3) can i just only tar the recovery.img and i am done?
Click to expand...
Click to collapse
md5 doesn't matter, you can still extract it as a tar archive, then you will get the recovery.img,
trust me it will not happen
in the developer options i've enabled usb debugging and oem unlock.
i installed samsung usb drivers and adb. using
Code:
adb devices
i was able to detect my device.
using oding v3.13.1 i tried to flash twrp but i got the following error:
Code:
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1301)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 19 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> NAND Write Start!!
<ID:0/004> SingleDownload.
<ID:0/004> recovery_a3y17lte-050318.img
<ID:0/004> Complete(Write) operation failed.
tried again on a different usb port, and got a different error:
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 19 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> recovery_a3y17lte-050318.img
<ID:0/005> Unassigned file
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
could someone please shed the light on the issue?
this is what i did in order to flash it:
1. flashed twrp 3.1.1-1
2. then using twrp, i flashed the twrp img (not tar) file
now i have twrp ver 3.2.1 running.
i am unsure how the image was compiled even when i looked at the code, but i was unable to read the /data partition which was encrypted.
i had to decrypt it in order to be able to flash magisk.
@McFy:
1. is it possible to check\get the complication flag from adb or twrp itself?
2. can you please also share what are the flags that you used to compile it? (see all my links above)
3. if the TW_INCLUDE_CRYPTO is set to false in your build, could you kindly include it in your next build if you make one?
vwtc6yc8e said:
i am unsure how the image was compiled even when i looked at the code, but i was unable to read the /data partition which was encrypted.
i had to decrypt it in order to be able to flash magisk.
@McFy:
1. is it possible to check\get the complication flag from adb or twrp itself?
2. can you please also share what are the flags that you used to compile it? (see all my links above)
3. if the TW_INCLUDE_CRYPTO is set to false in your build, could you kindly include it in your next build if you make one?
Click to expand...
Click to collapse
1. I think it's impossible
2. You can look at them on sources
3. It's yet set in true
McFy said:
3. It's yet set in true
Click to expand...
Click to collapse
didn't understand you. do you set the value to true when you compiled?
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?
Hello Guyz any solution for rooting our beloved A600FN with android 10 ?
Thx in advance
All our hope are on you @corsicanu
If you want root on stock rom and don't want custom rom you can use magisk's patching firmware feature.
Zeflay said:
If you want root on stock rom and don't want custom rom you can use magisk's patching firmware feature.
Click to expand...
Click to collapse
Without custom recovery?
Show me how you do that, dude!!!
For me we need twrp for a600fn on Android 10... Then we can root...
Envoyé de mon POCO F1 en utilisant Tapatalk
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
I found it!!! And it's so simple....
Basically, it's without custom recovery
0/ Unlock your Bootloader
1/ Download your stock rom android 10 from Sammobile or Frija (On your PC)
2/ Transfer the AP file in your phone
3/ Patch it with Magisk manager
4/ Copy back the pached file (tar extension) to your PC
5/ Reboot in Download mode
6/ Flash your phone via Odin, replacing the original AP file by the patched one
7/ reboot to stock recovery and factory format
8/ reboot system and enjoy your rooted Samsung phone!!!
Read carefully
Mastakony said:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
I found it!!! And it's so simple....
Basically, it's without custom recovery
0/ Unlock your Bootloader
1/ Download your stock rom android 10 from Sammobile or Frija (On your PC)
2/ Transfer the AP file in your phone
3/ Patch it with Magisk manager
4/ Copy back the pached file (tar extension) to your PC
5/ Reboot in Download mode
6/ Flash your phone via Odin, replacing the original AP file by the patched one
7/ reboot to stock recovery and factory format
8/ reboot system and enjoy your rooted Samsung phone!!!
Read carefully
Click to expand...
Click to collapse
Yes, but don't forget you didn't flash RMM bypass. So you can easily get KG prenormal state.
Zeflay said:
Yes, but don't forget you didn't flash RMM bypass. So you can easily get KG prenormal state.
Click to expand...
Click to collapse
I'm ok with that.
I just wanted to Root my device.
I don't want to flash custom binaries so it's cool...
No enough dev on this phone so no custom roms for me...
Root is enough
Mastakony said:
I'm ok with that.
I just wanted to Root my device.
I don't want to flash custom binaries so it's cool...
No enough dev on this phone so no custom roms for me...
Root is enough
Click to expand...
Click to collapse
Is gaming still smooth on your device on android 10 just like android 9?
Curcepogi said:
Is gaming still smooth on your device on android 10 just like android 9?
Click to expand...
Click to collapse
I don't know, dude.
This phone is really not designed for gaming (IMO)
I use it as my secondary phone...
My pocoF1 for gaming
Rooting ok but?
I rooting with metod of the 2 or 3 post is ok but I want copy frida in system/bin but is not possible
Is only read
With root explorer (superuser) change in r/w
launch command copy
And the phone reboot
Why?
Help and sorry for my English ?
Where can we get this file (Download your stock rom android 10 from Sammobile or Frija)
Sammobile
---------- Post added at 10:58 PM ---------- Previous post was at 10:32 PM ----------
The last stock rom
Mastakony said:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
I found it!!! And it's so simple....
Basically, it's without custom recovery
0/ Unlock your Bootloader
1/ Download your stock rom android 10 from Sammobile or Frija (On your PC)
2/ Transfer the AP file in your phone
3/ Patch it with Magisk manager
4/ Copy back the pached file (tar extension) to your PC
5/ Reboot in Download mode
6/ Flash your phone via Odin, replacing the original AP file by the patched one
7/ reboot to stock recovery and factory format
8/ reboot system and enjoy your rooted Samsung phone!!!
Read carefully
Click to expand...
Click to collapse
Hi, can you still use samsung account, and fingerprint payment features ?
Thanks in advance.
Samsung account works
Fingerprint too
Don't use paiement features but it should work it you use the good tricks (when rooted)
Envoyé de mon POCO F1 en utilisant Tapatalk
Thanks so much.
It works fine on A605FN too.
Hello, i have a A600FN with Android 10.
First i make OEM-Unlock, so it make a Factory Reset.
I Install the new Firmware from SamMobile with Odin.
After this, i install MagiskManager and Patch the AP from the Firmware.
So i try install the Magisk-Patched.Tar but it failed in Odin
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 4760 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start!!
<ID:0/005> SingleDownload.
<ID:0/005> system.img
<ID:0/005> vendor.img
<ID:0/005> userdata.img
<ID:0/005> boot.img
<ID:0/005> RQT_CLOSE !!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I test this with the Boot.img from the AP to, same Error.
Right the now the OEM-Unlock Option is disappeared too. (Yes WiFi is on and i test it to with the 8 days back)
I root lot of more Devices. But this one trigger me.
Mastakony said:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
I found it!!! And it's so simple....
Basically, it's without custom recovery
0/ Unlock your Bootloader
1/ Download your stock rom android 10 from Sammobile or Frija (On your PC)
2/ Transfer the AP file in your phone
3/ Patch it with Magisk manager
4/ Copy back the pached file (tar extension) to your PC
5/ Reboot in Download mode
6/ Flash your phone via Odin, replacing the original AP file by the patched one
7/ reboot to stock recovery and factory format
8/ reboot system and enjoy your rooted Samsung phone!!!
Read carefully
Click to expand...
Click to collapse
Confirmed working Magisk on Android 10 using this method on SM-A605G - A605GDXU6CTC9 XID. Thanks! :good:
Hey! Thanks so much for sharing this info with all the XDA community, all those of us who own an a600fn will be forever grateful, me in front line haha I rooted my phone with this method, but I immediately had this problem:
Booted to the system, everything working just fine, root apps working great, but I installed the BusyBox magisk module and it all went down hill. The phone would not boot properly, only on safe mode, and I had to reinstall the firmware with the root AP file all over again. I installed another magisk module, but it was the same thing: It went on a bootloop, or just wouldn't boot at all, only on safe mode, so I've concluded that is not possible to use them on this phone by rooting this way, meaning no magisk modules for me, since I've already upgraded to android 10 and I can't go back to Pie's bootloader or so I've heard. Im i being overly dramatic? Is there a solution for this? Is it because we can't flash the RMM state file without TWRP wich is not available for this phone with this android version?
btw I'm like super fan of all of you who work so hard in pro of making our phones better, there's no enough (insert anything good or that you just love in here) in the world to thank you all. Have a great day!
I hope for your answer
I'll write here because I didn't want to open e new thread.
I wanted to root the Galaxy A+ for my girl. I activated OEM unlock and did the following reset. Then I flashed twrp via Odin and the suggested files in addition. Unfortunately I ran into a bootloop, showing the black android screen with yellow writing in the upper left corner "warranty bit: kernel". The screen appears, gets black, reapperars and so on. Next I tried to flash the latest firmware via odin without success, read a lot about the odin flashing procedure. I think I might use the csc file without the "home" as fourth file, besides the usual bl, ap and cp. But when I choose this csc file, odin gets force closed. I can only use csc_home. The flashing process is very fast and says "success", but leads me into bootloop again. I tried booting into twrp after flashing and wiping cache and other things (lot of attempts) with same result.
If anybody has an idea I'll be very thankful.
no_means_no said:
I'll write here because I didn't want to open e new thread.
I wanted to root the Galaxy A+ for my girl. I activated OEM unlock and did the following reset. Then I flashed twrp via Odin and the suggested files in addition. Unfortunately I ran into a bootloop, showing the black android screen with yellow writing in the upper left corner "warranty bit: kernel". The screen appears, gets black, reapperars and so on. Next I tried to flash the latest firmware via odin without success, read a lot about the odin flashing procedure. I think I might use the csc file without the "home" as fourth file, besides the usual bl, ap and cp. But when I choose this csc file, odin gets force closed. I can only use csc_home. The flashing process is very fast and says "success", but leads me into bootloop again. I tried booting into twrp after flashing and wiping cache and other things (lot of attempts) with same result.
If anybody has an idea I'll be very thankful.
Click to expand...
Click to collapse
Dude, is TWRP. Uninstall it. I ran into the same problem. That recovery just isn't compatible with the bootloader of android 10 for this phone, and it will never boot if it's on your A6. It's all Samsung's fault, hahahaha
Hope I helped you!
no_means_no said:
I'll write here because I didn't want to open e new thread.
I wanted to root the Galaxy A+ for my girl. I activated OEM unlock and did the following reset. Then I flashed twrp via Odin and the suggested files in addition. Unfortunately I ran into a bootloop, showing the black android screen with yellow writing in the upper left corner "warranty bit: kernel". The screen appears, gets black, reapperars and so on. Next I tried to flash the latest firmware via odin without success, read a lot about the odin flashing procedure. I think I might use the csc file without the "home" as fourth file, besides the usual bl, ap and cp. But when I choose this csc file, odin gets force closed. I can only use csc_home. The flashing process is very fast and says "success", but leads me into bootloop again. I tried booting into twrp after flashing and wiping cache and other things (lot of attempts) with same result.
If anybody has an idea I'll be very thankful.
Click to expand...
Click to collapse
You can have root without recovery tho