Team Win Recovery Project
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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 doing this to your device
* 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.
*/
Disclaimer:
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox TZ Features. It can't be reset in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
- If you like my work please hit the "Thanks" button to support me. You're also free to donate me via my donation link here in XDA.
Installation:
- Download Odin3 v3.13.1, Samsung USB Drivers, latest TWRP's tar for your variant, latest no-verity-opt-encrypt zip and copy all of them to your internal storage.
- Go to Settings App, Developer Options and enable OEM Unlock (If you don't see Developer Setings, go into About phone>Software info and tap "Build number" 10 times to show Developer Options menu).
- Do a backup of all your important data and files in your phone.
- Shutdown the phone. Once it's off, Power it On in Download Mode (Press and hold Vol DOWN and Power buttons together )
- Open Odin3, go in Option section and untick "Auto-reboot". Once that click the "AP" button and select the TWRP tar you downloaded before, then press the "Start" button.
- Once Odin3 finished to flash the recovery (you should see a "PASS" message), force reboot your phone (Press and hold Power and Vol - buttons together) and once the screen is off, press and hold Power and Vol + buttons together to boot in TWRP.
- Once TWRP is booted you first need to decrypt your /data partition. To do so touch Wipe>Format Data and follow the instructions in screen.
- Once it finished go back at the home screen and touch Reboot>Recovery. TWRP should be able to mount your data partition. Now flash the no-verity-opt-encrypt zip you downloaded before (touch Install and select each zip to flash it)
- You're now able to reboot to your OS without re-encrypting /data partition .
Download:
TWRP 3.3.0 (taking down due to a bug, will fix and upload asap)
TWRP 3.2.3
Previous Builds:
TWRP 3.2.2
TWRP 3.2.1
TWRP3.2.0
Bugs:
Cannot mount External SD Card in TWRP
Changelog:
17 April, 2019 (TWRP 3.3.0)
Updated to TWRP 3.3.0.
Read full changelog over here and here.
Credits:
- Samsung Open Source Centre for kernel source code
- TeamWin for their awesome recovery
Awesome work bro thanks for Ur efforts, can you plzz try to fix that bug :fingers-crossed:
Wth ? Ss show that the version is 3.0.0 !
I need this recovery in the formats. img, please don't have a computer[emoji120]
al.iraq said:
I need this recovery in the formats. img, please don't have a computer[emoji120]
Click to expand...
Click to collapse
Root explorer to extract the tar or zarchive
Sent from my Samsung SM-G955F using XDA Labs
Demicro said:
Root explorer to extract the tar or zarchive
Sent from my Samsung SM-G955F using XDA Labs
Click to expand...
Click to collapse
Thank you very much sir, I forgot this. Now remember it thanks again[emoji257]
I can't seem to get the interface to navigate any of the partitions or data directories.
If I move the supersu zip to the phone, I can't find it at all, if I try to mount an sd card, it mounts the wrong file contents somehow.
Something is wonky with the disks
does support SM G610Y?
Working fine.
TWRP 3.2.1
CHANGELOGS
-F2FS support
-Updated TWRP to 3.2.1
DarkLord1731 said:
Team Win Recovery Project 3.2.1
HOW TO INSTALL
Install via ODIN in AP section
OR
If you have TWRP already installed you can extract the downloaded tar and install via recovery(INSTALL -> Select Image -> Flash)
Click to expand...
Click to collapse
But to install by Odin is not it necessary that the file be MD5? How can I get a MD5 file to a first install?
Kherham said:
But to install by Odin is not it necessary that the file be MD5? How can I get a MD5 file to a first install?
Click to expand...
Click to collapse
No it isn't necessary, you can install tar files
DarkLord1731 said:
No it isn't necessary, you can install tar files
Click to expand...
Click to collapse
Am asking because I tried many times install it by Odin with a .tar file and didn't worked. Will put this one in my card for another try.
Thank you very much.
Can I flash on G610L
can you suggest me how to flash or install on this TWRP since it didnt recognize my internal and external memory :<. Tried to use USB cabble but no result too.
i need some help i install the twrp and make it work but when i am try to see any file from sd card or any i cant so i cant install this rom. SdCard Looks empty but its not
i install this recovery in samsung j7 prime odin showing succesfully install but when i try to boot into recovery it is directly boot into stock recovery. help me
no-verity-opt-encrypt.zip
Sir I was wondering on how can I install this zip "! (no-verity-opt-encrypt.zip)
I installed the recovery and it worked fine for me " thanks for that "!:laugh::good:
---------- Post added at 12:32 PM ---------- Previous post was at 12:28 PM ----------
Baqir2 said:
i install this recovery in samsung j7 prime odin showing succesfully install but when i try to boot into recovery it is directly boot into stock recovery. help me
Click to expand...
Click to collapse
Sir I installed this and working fine"!
what I did is I installed it and test to see if its working and no its not and after
I installed it again and tick the auto reboot on odin
and patch it then press and hold the combo for going into download even tho in it and after or immediately the screen goes black press the combo for going into recovery and wolla enjoy I hope this helps "!
sometimes it helps reading the instrucyions carefully "! ???
Deleted
For ppl having trouble to mount internal memory follow these steps:
You have to first Flash TWRP Recovery From Odin
Then on TWRP go to Advance>Wipe And Press Format Data And Type Yes
Then your Internal storage will be able to mount while connected to the PC
And you can now drag zips to flash on your Internal memory via PC
Running perfect on my G610Y
Related
Code:
#include
/*
* Your warranty is now void.
*
* 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 ROM
* 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 RECOVERY WILL TRIP YOUR KNOX COUNTER ..AND UR WARRANTY WILL BE VOID
THIS RECOVERY IS ONLY FOR THE 3G VARIANT (SM-N750) RUNNING KITKAT (4.4.2)
Philz recoveryorignal thread here
Why CWM ? Why not a pre-rooted firmware which will not void warranty?
Ans : CWM has many more functionality than stock recovery ! Rooting means to playing around with your device.If some thing goes wrong it you have to flash the whole firmware again instead,backup your ROM through CWM and if something goes wrong restore your backup AS SIMPLE AS THAT !
All you have to do is follow my instructions :
STEP 1 :
-Download and setup ADB drivers for your device
can be found here Drivers !
STEP 2 :
-Download the recovery from ---> Link
-Download odin 3 Link
-Turn of your device and go to odin mode [ Vol down + power + home button (all at the same time) ] release it when you see Note Neo logo
-Press vol up to confirm
STEP 3 :
-Now that you are in odin mode connect your device via usb cable !
-Now open Odin3 3.09 that you have downloaded.
-If there is a pop-up like Installing ADB drivers let it get finished it is usually updates !!!!
-Make sure the COM : xx (xx is usb port number it can be any number so dont worry about it,just verify COM is lit up)
-Select the recovery (Link in STEP 2) ! Now select AP and browse to where you have .tar file and select it
MAKE SURE U UNTICK THE AUTO-REBOOT BUTTON
-Click Start
ONCE IT SAYS PASS ...REMOVE THE BATTERY ...THEN RE-INSERT THE BATTERY AND BOOT INTO RECOVERY USING VOL UP + HOME + POWER BUTTON
HOW TO ROOT THE DEVICE :
-Download SuperSu (obviously the latest one) from here ------> Click here !
-Copy that to internal sd card
-Power off your device and press vol up + power + home button (all at once)
-Select install zip from sdcard --->choose zip from sdcard ---> scroll down and flash UPDATE-SuperSU-v2.xx.zip
Done ! And you are ready to go
BUGS
YOU TELL ME [/SIZE]
NOTE : IF ANY OPTION DOESNT WORK FOR U ... TURN OFF UR PHONE AND THEN BOOT INTO RECOVERY
SOURCES
DEVICE TREE
KERNEL(PREBUILT ... THANX TO SAMSUNG ... AVAILABLE IN THE DEVICE TREE)
CREDITS
@k2wl
philz3759
@sgatechwork
CHANGELOG
Code:
[B][COLOR="Red"]BUILD 4[/COLOR][/B]
-FIXED FORMAT , WIPE CACHE AND BACKUP AND RESTORE
[B][COLOR="Red"]BUILD 3[/COLOR][/B]
-EXTERNAL SD CARD FIXED - BIG THANX TO @sgatechwork FOR THE MOUNTS
- BACKUP AND RESTORE WORKING
[B][COLOR="Red"]BUILD 2[/COLOR][/B]
-WIPE CACHE FIXED ( BACKUP OF CACHE STILL NOT WORKING)
-A BIG THANX TO @sgatechwork FOR TESTING
[COLOR="Red"][B]BUILD 1[/B][/COLOR]
INITIAL BUILD
Finaly I'm able to root my phone. Thanks a lot
thanks bro for your effort and finally some development for note 3 neo....
but what does the bug in external sd card mean??
does the phone not read the card or something else??because sd card is very important to me...
-HellRaiser- said:
thanks bro for your effort and finally some development for note 3 neo....
but what does the bug in external sd card mean??
does the phone not read the card or something else??because sd card is very important to me...
Click to expand...
Click to collapse
it doesnt read the external sd card ... but internal works properly ... and dont try wipe cache it bootloops ... external sd card will be fixed soon
by not reading external card you mean the recovery cant read it only or the phone cant read it at all while using....if otherwise then i should better wait for a fixed bulid....and does this mean samsung released the kitkat kernal sources???
if yes then once this recovery is fixed then maybe we can make a custom kernal....what do you say OP about that?
-HellRaiser- said:
then i should better wait for a fixed bulid....and does this mean samsung released the kitkat kernal sources???
if yes then once this recovery is fixed then maybe we can make a custom kernal....what do you say OP about that?
Click to expand...
Click to collapse
samsung hasnt released the source code yet ... it takes time after the kk update ..say abt 3-5 weeks .. i hv emailed them .... this uses a prebuilt kernel
U CAN USE THE RECOVERY IF U WANT TO FLASH SUPERSU .. THAT WORKS FINE
rutvikrvr said:
samsung hasnt released the source code yet ... it takes time after the kk update ..say abt 3-5 weeks .. i hv emailed them .... this uses a prebuilt kernel
U CAN USE THE RECOVERY IF U WANT TO FLASH SUPERSU .. THAT WORKS FINE
Click to expand...
Click to collapse
by not reading external card you mean the recovery cant read it only or the phone cant read it at all while using in normal mode....
-HellRaiser- said:
by not reading external card you mean the recovery cant read it only or the phone cant read it at all while using in normal mode....
Click to expand...
Click to collapse
lol ...obviously only the recovery cant read it ......
in the rom it works
rutvikrvr said:
lol ...obviously only the recovery cant read it ......
in the rom it works
Click to expand...
Click to collapse
thanks bro....will try tomm....and yeah good work man....
Ive flashed and SD card isn't detected only in recovery and root works all well after flashing supersu .
{
"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"
}
Finally....
Is backup & restore working properly????????
KSKHH said:
Finally....
Is backup & restore working properly????????
Click to expand...
Click to collapse
Pl try ... But don't backup cache ..or restore it
rutvikrvr said:
Pl try ... But don't backup cache ..or restore it
Click to expand...
Click to collapse
Hi OP first thanks a lot for your time to develop this.
Tell me one thing...suppose the situation come some time when I face bootloop due to lot of unnecessary R&D with the phone. At that moment if I restore then will it give me the option to untick Cache. Becoz I did not find it in my S3.
Till now I was using TWRP in Note 3 Neo, however due to Kitkat TWRP gone where there was a option to untick.
EDIT: Ok I see there is a custom backup option...Thanks.
try to find advance restore
Yipppppppeeeeyyyyyyyyyyyyyyy.. Got rooted after update.. Thanks
priyansh17 said:
Yipppppppeeeeyyyyyyyyyyyyyyy.. Got rooted after update.. Thanks
Click to expand...
Click to collapse
Do hit thanx button
Done
Restoration not working..
I have not taken backup of Cache nor restoring it.
KSKHH said:
Restoration not working..
I have not taken backup of Cache nor restoring it.
Click to expand...
Click to collapse
added to known issues
BUILD 2 IS UP
-WIPE CACHE FIXED ... (BACKUP OF CACHE STILL NOT WORKING)
DOWNLOAD LINK IN OP
{
"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"
}
Code:
#include "twrp30.cpp"
/*
* Your warranty is now void.
*
* 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.
*/
Warning! Flashing custom recovery will trip your Knox!
Works:
Install ZIP
Backup
Restore
File Manager
Terminal
Mounting Partitions
OTG
MTP and Sideload(works not always)
Known Bugs:
MTP and Sideload will not works if u have SM-A300H;
When press Reboot system it just turns phone off, u need to turn it on manually
Warning! I'm not the developer, but if you have questions, you cann ask here
Developer: Mygalaxya
Download:
Google Drive
Mirror: Mega
Thanks!!! Testing in A300M. It works on A300M , but does not start the system recovery loop
Enviado desde mi SM-A300M mediante Tapatalk
thanks a lot @Intel777chanel and @mygalaxya
Edict works perfectamente en el A300M reinstalling the original firmware.
Enviado desde mi SM-A300M mediante Tapatalk
hi,
thank's a lot dudes, works on A300FU
and now we have finally the working MTP mode we need for cm12.1 roms
excellent work :highfive:
update : with this version i can't flash any .zip ( customroms ) ( stop install with error 7 ) and the second bug is it's not boot from recovery into recovery again over the restart menue . all other important funtions are testet and works on my device perfect ...please fix it, it's a very very nice recovery
best regards :good:
So just to be sure, are you sure it won't brick my phone if I flash this recovery on A300FU?
It's not stated if its for all versions or I'm mising something.
Marecki_ said:
So just to be sure, are you sure it won't brick my phone if I flash this recovery on A300FU?
Click to expand...
Click to collapse
i am using it right now. and it is incredibly flexible, especially if you mess things up ...
feels smoother too
Can I flash on top of 2.8.7.0?
Yes you can.
OP, i am having a bit of a problem, i can't get out of Recovery. I rebooted to recovery to show it to a friend, and whatever i do, it will boot in recovery only.
Rebooting "system" boots back to recovery, and powering off in TWRP powers off normally, but it'll boot again in TWRP. Even if i restart from Download mode, same issue.
The thing is, i didnt touch nor flash anything, i know for sure the system is well.
@Intel777chanel @mygalaxya any clue?
EDIT: twrp 2.8.7.0 fixes it (temporarely )
i just read 3.0.0-1 and 3.0.0-2 is out already for a few devices...?
PlutoDelic said:
Yes you can.
OP, i am having a bit of a problem, i can't get out of Recovery. I rebooted to recovery to show it to a friend, and whatever i do, it will boot in recovery only.
Rebooting "system" boots back to recovery, and powering off in TWRP powers off normally, but it'll boot again in TWRP. Even if i restart from Download mode, same issue.
The thing is, i didnt touch nor flash anything, i know for sure the system is well.
@Intel777chanel @mygalaxya any clue?
Click to expand...
Click to collapse
Hi, have you tried to flash it using Flashify ? After flashing TWRP, don't try to reboot the phone, just turn it off and then turn it on. It should boot to system normally.
mygalaxya said:
Hi, have you tried to flash it using Flashify ? After flashing TWRP, don't try to reboot the phone, just turn it off and then turn it on. It should boot to system normally.
Click to expand...
Click to collapse
You mean Flashfire right? I previously used Mobile ODIN/Flashfire, but i saw no need to use it after i strictly used Custom Recoveries.
PS, even with the Power Off feature, when i start the phone, it went to Recovery again.
Google shows One Plus One users having a very similar issue...it definitely isn't a soft brick as flashing TWRP 2 and restarting works fine.
please let me know if i can help in any way
PlutoDelic said:
You mean Flashfire right? I previously used Mobile ODIN/Flashfire, but i saw no need to use it after i strictly used Custom Recoveries.
PS, even with the Power Off feature, when i start the phone, it went to Recovery again.
Google shows One Plus One users having a very similar issue...it definitely isn't a soft brick as flashing TWRP 2 and restarting works fine.
please let me know if i can help in any way
Click to expand...
Click to collapse
No, I don't mean Flashfire, I mean Flashify (search on Play Store), you have to download it and flash the TWRP using it. Once it is flashed, power off your phone, go to download mode and then restart completely the phone. If you did this, all should work fine.
Works if using odin on top of twrp2?
First of all thank you @Intel777chanel and @mygalaxya
Duke2010 said:
with this version i can't flash any .zip ( customroms ) ( stop install with error 7 ) and the second bug is it's not boot from recovery into recovery again over the restart menue
Click to expand...
Click to collapse
Confirm both and Reboot to System turns also device off, (Reboot -> Download & Reboot -> Power Off is working) also MTP is not woking at my A300FU
Installed over Flashify at CM12.1 and at Stock Rom via Odin3 (PC) with same result. Backup and Restore works fine
Installing zip file ´/external_sd/A3 System/cm-12.1-20160119-UNOFFICIAL-a3ultexx.zip´
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
This package is for device: a3ulte,a3ultexx,SM-A300FU; this device is .
Updater process ended with ERROR: 7
Error installing zip file ´/external_sd/A3 System/cm-12.1-20160119-UNOFFICIAL-a3ultexx.zip´
Updating partiton details...
...done
[/COLOR]
Jonny_Hood said:
First of all thank you @Intel777chanel and @mygalaxya
Confirm both and Reboot to System turns also device off, (Reboot -> Download & Reboot -> Power Off is working) also MTP is not woking at my A300FU
Installed over Flashify at CM12.1 and at Stock Rom via Odin3 (PC) with same result. Backup and Restore works fine
Installing zip file ´/external_sd/A3 System/cm-12.1-20160119-UNOFFICIAL-a3ultexx.zip´
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
This package is for device: a3ulte,a3ultexx,SM-A300FU; this device is .
Updater process ended with ERROR: 7
Error installing zip file ´/external_sd/A3 System/cm-12.1-20160119-UNOFFICIAL-a3ultexx.zip´
Updating partiton details...
...done
Click to expand...
Click to collapse
the dev have forgotten the name of device
Jonny_Hood said:
First of all thank you @Intel777chanel and @mygalaxya
Confirm both and Reboot to System turns also device off, (Reboot -> Download & Reboot -> Power Off is working) also MTP is not woking at my A300FU
Installed over Flashify at CM12.1 and at Stock Rom via Odin3 (PC) with same result. Backup and Restore works fine
Installing zip file ´/external_sd/A3 System/cm-12.1-20160119-UNOFFICIAL-a3ultexx.zip´
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
This package is for device: a3ulte,a3ultexx,SM-A300FU; this device is .
Updater process ended with ERROR: 7
Error installing zip file ´/external_sd/A3 System/cm-12.1-20160119-UNOFFICIAL-a3ultexx.zip´
Updating partiton details...
...done
Click to expand...
Click to collapse
Hi, this new TWRP 3.0 uses different mount points than 2.8.7.0, on the build you are trying to flash it uses old mount points. The developer you made the ROM must now use the mount ext4 "dev/block/bootdevice/by-name/system" on META-INF, otherwise you will not be able to flash the ROM. I will update all my builds to support this new mount points.
Thanks again here you are @mygalaxya ! Regards.
Testing this for A300Y model now after flashing successfully with the old version of TWRP recovery and will report back soon.
nowheel said:
[/COLOR]
the dev have forgotten the name of device
Click to expand...
Click to collapse
It seems so.
mygalaxya said:
Hi, this new TWRP 3.0 uses different mount points than 2.8.7.0, on the build you are trying to flash it uses old mount points. The developer you made the ROM must now use the mount ext4 "dev/block/bootdevice/by-name/system" on META-INF, otherwise you will not be able to flash the ROM. I will update all my builds to support this new mount points.
Click to expand...
Click to collapse
Whether recovery mounts partitions by name or by block device should make no difference to a rom install as the Installer script takes care of correctly mounting the partitions.
Most installer scripts unmount the partitions first anyway then remount.
If it doesn't work then the Installer script is at fault.
However according to that error twrp doesn't have the right device name in its build properties to match the rom device name.
Either the device name needs changing in the twrp 'default.prop' - ro.product.device=a3ulte or just remove the 'assert' lines in the rom installer script.
Perfect recovery and I can confirm its working on A300Y but must be flashed via Odin as apps couldn't flash it for some reason.. thanks @mygalaxya
{
"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"
}
Unofficial TWRP 3.3.0 For J5 2017Disclaimer
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.
Special features:
Code:
- built from Pie kernel source
- built in full 64bit mode
- updated TWRP source to 3.3
- Full F2FS Support
- fully compatible with all Oreo roms
Downloads:
J530x - Latest Release
Instructions:
Odin
Download Odin v3.13.1
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
Optional - Download and flash no-verity-opt-encrypt-6.0 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
J530x device tree - https://github.com/omnirom/android_bootable_recovery
Credits:
@corsicanu
@Dyneteve
@yshalsager
@TwrpBuilder
XDA:DevDB Information
TWRP_J530, Tool/Utility for the Samsung Galaxy J5
Contributors
ananjaser1211, corsicanu
Source Code: https://github.com/ananjaser1211/android_device_samsung_jxy17lte
Version Information
Status: Stable
Current Stable Version: V2.0
Stable Release Date: 2019-04-17
Created 2017-12-31
Last Updated 2019-04-17
Reserved
Reserved
Reserved
New year gift
Great work
Keep it up
J5 users are lucky
Good job ?
thanx so much
good job bro
Does it work on J530G?
--Encyrption---
Now you need to disable samsung encryption otherwise you will have a bad time
Format Data partition using FORMAT DATA button under Wipe options. (Note: This will wipe the internal storage)
Flash Latest MAGISK Version OR Any J530 Custom Kernel (To disable DM-Verity/encryption)
Magisk : Official Thread
Reboot and setup your Phone.
Happy flashing !
Click to expand...
Click to collapse
i have root form Magisk befor and old TWRP
and Just only update TWRP in Odin and work fine
lordeBacalhau said:
Does it work on J530G?
Click to expand...
Click to collapse
No it should not work. i ill compile J530G version in a day or two.
Will there be firmware, adapted for J530FM ????
work fine in j530f
thnks
For More support.
If you want TWRP for specific J530x Model, please post its stock boot.img (either from stock firmware from samobile) or figure a way to back it up.
Works fine. Tnx
help
hi attached compressed zip boot file, J530GM 1 sim 16 gb
thanks for the support.
VxBlazter said:
Click to expand...
Click to collapse
only j530F
armando-martin said:
hi attached compressed zip boot file, J530GM 1 sim 16 gb
thanks for the support.
Click to expand...
Click to collapse
Awesome :good:
J530G/GM
J530G : https://github.com/ananjaser1211/android_device_samsung_j5y17lte/releases/tag/J530G
J530GM : https://github.com/ananjaser1211/android_device_samsung_j5y17lte/releases/tag/J530GM
This is for J530G/GM.
This is Untested since i dont own that variant, so please mention weather it worked or not.
G and GM can probably be installed on either device
the version for J530GM is installed and it does not start twrp starts the phone,
the version for J530G is installed if it starts twrp and it works MTP does not mount data, mount system, and does not detect internal memory of the phone.
my phone version J530GM
armando-martin said:
the version for J530GM is installed and it does not start twrp starts the phone,
the version for J530G is installed if it starts twrp and it works MTP does not mount data, mount system, and does not detect internal memory of the phone.
my phone version J530GM
Click to expand...
Click to collapse
You need to wipe internal storage and flash Magisk most probably
{
"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"
}
Official TWRP 3.6.1-* For Galaxy A5/A7 (2017)Only for exynos variants - A520F (Europe, Global Single-SIM); A520F/DS (Global Dual-SIM); A520K/L/S (South Korea); A520W (Canada), A720F (Global Single-SIM); A720F/DS (Global Dual-SIM); A720S (South Korea)
Disclaimer
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.
Features:
Code:
- built from Pie kernel source
- built from android-9.0 recovery sources
- built in full 64 mode
- fully compatible with Android 8.*/9.0/10.0
Downloads:
A5 2017 - https://twrp.me/samsung/samsunggalaxya52017.html
A7 2017 - https://twrp.me/samsung/samsunggalaxya72017.html
Instructions:
Odin
Download latest Odin zip from downloads.corsicanu.ro/samsung
Download and install Samsung Drivers (if you have them installed you can skip this step)
Go to settings/Developer options and enable OEM unlock (If you don't see developer settings, go into Settings/About phone/Software info and tap "Build number" 10 times to show Developer options menu)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
After booting in TWRP download and flash no-verity-opt-encrypt-6.1 zip to disable data partition encryption
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
A5 2017 Device tree - https://github.com/TeamWin/android_device_samsung_a5y17lte
A7 2017 Device tree - https://github.com/TeamWin/android_device_samsung_a7y17lte
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal7880/tree/android-9.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, jesec, geiti94, dyneteve, testers, donors and anyone else involved in making this possible
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Latest Magisk stable or canary
FAQ / Further reading
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware.
Q: I get "Failed to mount /preload message", what to do?
A: From wipe menu select Advanced Wipe, select preload partition to be wiped and reboot recovery.
Q: Why do i need to format data partition?
A: Because old rom encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Thanks
like!
bootloop
Immediately after installing my phone went on bootloop and restart continuously.
Please help me:crying::crying:
e.ahangari said:
Immediately after installing my phone went on bootloop and restart continuously.
Please help me:crying::crying:
Click to expand...
Click to collapse
What device and what method of flashing did you used?
a7, when installing Odin, bootlooр
bootloop
corsicanu said:
What device and what method of flashing did you used?
Click to expand...
Click to collapse
A720F oreo stock rom - I wanted to update from twrp_3.1.0-1 to 3.2.2
cant flash in a7 2017 (a720f)using odin
on my a7 bootloop too, flash via twrp. flash through odin previous version helps
A520F, zip downloaded and flashed in TWRP, It's perfect, no problem (bootloop) at this time!
Thank you corsicanu.
Well done.
Works great for me, flashed .img in TWRP,A520F.
Ok, turned out that A7 twrp was broken, fixed that and also tested properly, meanwhile switched from TwrpBuilder repo to my own repo and moved mega downloads to github releases.
New builds will be up soon, beside mentioned, there are no changes.
Enjoy it!
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases
Thanks
corsicanu said:
Ok, turned out that A7 twrp was broken, fixed that and also tested properly, meanwhile switched from TwrpBuilder repo to my own repo and moved mega downloads to github releases.
New builds will be up soon, beside mentioned, there are no changes.
Enjoy it!
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases
Click to expand...
Click to collapse
Thanks a lot.
Its now fixed and work properly.:highfive::highfive::highfive:
Thanks
A7y17lte
is anyone installed root succesfully?
corsicanu said:
Ok, turned out that A7 twrp was broken, fixed that and also tested properly, meanwhile switched from TwrpBuilder repo to my own repo and moved mega downloads to github releases.
New builds will be up soon, beside mentioned, there are no changes.
Enjoy it!
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases
Click to expand...
Click to collapse
I'm about to receive a new A5 2017 and update it to official OREO right out of the box.
After having updated, there's the TWRP step and I just wanted to know of I have to also flash the usual encription thing (opt verity or something like that) I have almost always flashed after a fresh twrp install.
Works fine for me so far... I will test with the official fw to know if the /data is decrypted. We appreciate the work corsicanu. :good:
@edit
For me, everything works fine! including support for all languages.
A7y17lte
corsicanu said:
Unofficial TWRP 3.2.2-0 For A5 / A7 2017Disclaimer
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.
Special features:
Code:
- built from Oreo kernel source
- built in full 64 mode
- updated TWRP source
- fully compatible with all Oreo roms
Downloads:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte/releases
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte/releases
Instructions:
Odin
Download Odin v3.13.1
Download and install Samsung Drivers (if you have them installed you can skip this step)
Download TWRP_*.tar
Switch off the phone
Use Home+Volume Down+Power to enter Download Mode and connect the device to usb
Open Odin and untick autoreboot in "options" tab. Also make sure that your device is detected
Put TWRP_*.tar.md5 file into AP tab
Click Start
When Odin shows "PASS", take your device in hands, disconnect the usb cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the downoad mode disappears
At the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to forcefully enter TWRP
If it didn`t worked, redo the steps from #1 more careful this time.
TWRP
Download TWRP_*.zip, push it into phone storage and flash it as normal zip in your current recovery.
Download TWRP_*.img, push it into phone storage, choose install image in your current recovery, navigate to downloaded *.img file, select it, select to flash as recovery.
If for any reason you fail to install TWRP multiple times/different methods, make sure you check this thread
Sources:
A520x - https://github.com/corsicanu/android_device_samsung_a5y17lte
A720x - https://github.com/corsicanu/android_device_samsung_a7y17lte
Kernel - https://github.com/corsicanu/twrp_android_kernel_samsung_universal7880
Credits:
@Dyneteve
@TwrpBuilder
Click to expand...
Click to collapse
is anyone installed root succesfully?
Hey,
I have a problem and I don't know how to fix it, cuz I never had that.
I've installed TWRP successfully and I can start it normally, but TWRP don't have access to any Files in Internal Storage.
I installed TWRP on A520F (with Firmware DBT, Android 8.0)
Kind regards,
DasNuddel // Charles
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
Odin
- Odin3 v3.10.5
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy Note 10.1
How to flash TWRP with Odin
1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down simultaneously. When the warning screen appears, release all buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP".
3. Disable auto reboot in Odin and press start.
4. You can then boot directly into TWRP by pressing the Power and Volume Up simultaneously. Release all buttons as soon as you see the boot screen ("Samsung Galaxy Note 10.1").
How to flash TWRP within a previous version of TWRP
1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power and Volume UP simultaneously. Release all buttons when the boot screen appears ("Samsung Galaxy Note 10.1").
2. In TWRP, tap "Install" then "Install Image".
3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.
4. Select the "Recovery" radio button.
5. Move the slider to the right to flash the TWRP image.
6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.
Bugs
- You tell me!
Credits
TWRP Team and all people who worked / are working on the exynos 4 devices.
Sources
- n8000 repository
- n8010 repository
- n8020 repository
- TWRP repository
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my spare time and every donation keeps me motivated.
donate
XDA: DevDB Information
TWRP 3.6.0_9-X, ROM for the Samsung Galaxy Note 10.1
Contributors
@html6405
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-1
Stable Release Date: 2021-02-14
Created 2021-02-14
Last Updated 2021-10-12
Hey after updating to this recovery I noticed when I went to wipe my /data partition it would end up wiping my internal storage even though I did not select the internal storage. Just wanted to let you know about this bug I encountered.
CurbThePain said:
Hey after updating to this recovery I noticed when I went to wipe my /data partition it would end up wiping my internal storage even though I did not select the internal storage. Just wanted to let you know about this bug I encountered.
Click to expand...
Click to collapse
What have you exactly done? If you choose wipe /data, then it should also wipe your internal memory (this is mounted in data/media).
But if you made a factory reset, then the internal memory shouldn't be deleted.
html6405 said:
What have you exactly done? If you choose wipe /data, then it should also wipe your internal memory (this is mounted in data/media/0).
But if you made a factory reset, then the internal memory shouldn't be deleted.
Click to expand...
Click to collapse
Well previously using TWRP 3.3.1 I would do the advanced wipe and only select the /data partition not the internal storage. Then it would say "wiping /data without wiping internal storage". But if I did the same thing in TWRP 3.5.0 it would say "wiping /data and internal storage". I stopped using the basic factory reset many years ago because it always wiped my internal storage. But I will give it a shot and let you know if that works for formatting just the /data partition.
CurbThePain said:
factory reset many years ago because it always wiped my internal storage.
Click to expand...
Click to collapse
This was a faulty behaviour, because the factory reset should wipe only /data withoult /data/media.
Off topic, but it seems like emojis need to be disabled in the 1st post.
TWRP 3.5.1_9-0 is now ready to download , if you should find any bugs, let me know.
got an error
"Size of image is larger than target device"
device N8013 twrp version 3.4.0-0
running Slim 7
noobody168 said:
got an error
"Size of image is larger than target device"
device N8013 twrp version 3.4.0-0
running Slim 7
Click to expand...
Click to collapse
Thanks for testing it,
I will check on this later, maybe something went wrong in the conversion,
I will fix this and we will receive a new build.
All image sizes are fixed,
new builds are up!
html6405 said:
Все размеры изображений фиксированные,
новые постройки построены!
Click to expand...
Click to collapse
Alas, the image size is too large, not flash, n8000 (2021-03-22 09:05:36 build)
html6405 said:
Thanks for testing it,
I will check on this later, maybe something went wrong in the conversion,
I will fix this and we will receive a new build.
Click to expand...
Click to collapse
Works fine with with revised version now, thank you very much
SteelK said:
Alas, the image size is too large, not flash, n8000 (2021-03-22 09:05:36 build)
Click to expand...
Click to collapse
Are you sure? I've tested it, I will check on this later.
Yes, I'm sure I tried the latest version from TWRP site for N8000
Now I've tested the files again from both servers, and it is working in my case.
The file size is lower then our border size.
Is there any option to find out the size of the recovery partition?
Im used https://dl.twrp.me/n8000/twrp-3.5.1_9-0-n8000.img.html
How is this possible ...
The image from the tar archive was installed, but the image from the img link was not.
md5 are the same.
SteelK said:
Is there any option to find out the size of the recovery partition?
Im used https://dl.twrp.me/n8000/twrp-3.5.1_9-0-n8000.img.html
How is this possible ...
The image from the tar archive was installed, but the image from the img link was not.
md5 are the same.
Click to expand...
Click to collapse
I have no idea, actually if the md5 is the same, it must work.
SteelK said:
recovery partition?
Click to expand...
Click to collapse
Yes, but they are equal for all of us.
I seem to have lost access to my microSD in recovery..? I updated from the microSD and on reboot the card was corruptred in LOS18...I was able to fix and recover on my computer and am able to see it again in Android, but still won't mount in recovery. Any ideas?
xtoad said:
I seem to have lost access to my microSD in recovery..? I updated from the microSD and on reboot the card was corruptred in LOS18...I was able to fix and recover on my computer and am able to see it again in Android, but still won't mount in recovery. Any ideas?
Click to expand...
Click to collapse
Which file system are you using?
I had to sort out some things, TWRP needs much more space now.
html6405 said:
Which file system are you using?
I had to sort out some things, TWRP needs much more space now.
Click to expand...
Click to collapse
I believe it is ext4. Or whatever the default is. I have not changed it on my own.