Database Develop

**CLOSED**[ROM] [Samsung GT-S5570] Vanilla ROM S5570XWKC1 (Froyo) + Added Features

Re-released flashable zip version for those people who are stuck at Froyo because of modem issues
Features:
Modified CWM to support Froyo. Credits to tj_style for porting CWM on Galaxy Mini ==> http://forum.xda-developers.com/showthread.php?t=1167750
Uses tj_style's overclock kernel ==> http://forum.xda-developers.com/showpost.php?p=12880870&postcount=39
All partitions @ Ext4
Pre-rooted
Deodex
Bootanimation
init.d support (running custom scripts during boot)
cifs and tun modules
Darktremor Apps2SD 2.7.5.3 Beta 03
Removed startup sound
Changed default language to English
Added some live wallpapers
TouchWiz replaced with zeam
Pre-installed apps: OpenVPNSettings (inlcuding binary), Screenoffandlock, and CifsManager
Others
FLASHING DISCLAIMER APPLIES!
Should anything go wrong, please make sure you have a backup of your firmware from samfirmware.com or use CheckFus http://forum.xda-developers.com/showthread.php?t=1032437
How to install from stock firmware:
This procedure assumes that you are still using Froyo so there is no need to flash any firmware
1. Download attached ClockworkMod (CWM) Recovery for Froyo. Flash as 'One Pacakge' using Odin
2. Download S5570XWKC1_MOD_ROM.zip and save it on the root your SD card ==> http://www.multiupload.com/0INURR5M72
3. Turn off phone. Go into recovery mode by pressing and holding the Home + Power buttons. Release buttons when you see the Samsung logo
4. Once you are in recovery mode you will get lot of options on screen. In recovery mode touchscreen does not work, so use the Volume button to toggle through options, Home button to select option or confirm action, and Power or Back button to go back to the previous menu.
5. Select 'wipe data / reset'. Confirm action
6. Select 'install zip from sd > 'choose zip from sdcard' > file in Step 2. Confirm action
7. Go back to previous menu and select 'reboot system now'
Done!
Stock theme
{
"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"
}
Quadrant (600MHz)
Quadrant (overclocked)

thanks for this rom really like it) i have just 1 tiny problem :-s when i press home and select task manager it force stops :| this is the only thing that bother me

I can't recreate your issue. Does it happen all the time or in just some cases?

Thank you Parasmi!!! You rock!!! Already downloading and I'll give it a try tomorrow!!!

does the dark font in menu exist in this release too?
if not i'm going to install it

trance89 said:
does the dark font in menu exist in this release too?
if not i'm going to install it
Click to expand...
Click to collapse
No because this is stock theme.
Please note this is a Froyo ROM. If you are coming from Gingerbread, you need to flash a Froyo firmware first using Odin.

parasmi said:
I can't recreate your issue. Does it happen all the time or in just some cases?
Click to expand...
Click to collapse
all the time. you know? when i press menu it pops up recent apps and under the task manager.when i press on task manager phone vibrates and i got the "force close " message.same if i press the task manager from menu :-?

Great work Parasmi.
It's just one thing that I will ask you to consider : some apps that you included in the zip package. For instance, AFAIK Root Explorer is only available as paid version only. How could you manage to include it in your ROM ? I hate to see this great ROM turned into a warez ROM. And secondly, SetCPU, though it's free for xda-dev members, its' developer explicitly asked ROM Developers not to include SetCPU. You can see his post here :
SetCPU for Root Users [2.2.4] Undervolting and more 07/07/2011
Or I'll just quote part of his OP here :
coolbho3000 said:
ROM developers: Please do not include SetCPU in your ROM. I appreciate the work you're doing, but link to this thread instead, and I'd really appreciate it if you mention that SetCPU is available on the Android Market.
SetCPU is a CPU speed tweaking application for Android. More specifically, it allows control of certain aspects of the Linux cpufreq driver, allowing for overclocking, underclocking, or tweaking speeds and settings on many Android devices. It will work with most if not all rooted Android 1.5/1.6/2.0/2.1/2.2/2.3/3.0/3.1 builds on most devices.
The program is free here for XDA members. It costs 1.99 on the Android Market and available for purchase on the Amazon Appstore for users in the US.
QR code (please donate by buying it on the market ):
Click to expand...
Click to collapse
Cheers

distan7 said:
Great work Parasmi.
It's just one thing that I will ask you to consider : some apps that you included in the zip package. For instance, AFAIK Root Explorer is only available as paid version only. How could you manage to include it in your ROM ? I hate to see this great ROM turned into a warez ROM. And secondly, SetCPU, though it's free for xda-dev members, its' developer explicitly asked ROM Developers not to include SetCPU. You can see his post here :
SetCPU for Root Users [2.2.4] Undervolting and more 07/07/2011
Or I'll just quote part of his OP here :
Cheers
Click to expand...
Click to collapse
Thank you for the reminder. I'm having seconds thought about them actually. I'll remove them and re-upload a new file

adistf said:
all the time. you know? when i press menu it pops up recent apps and under the task manager.when i press on task manager phone vibrates and i got the "force close " message.same if i press the task manager from menu :-?
Click to expand...
Click to collapse
Not happening to me. Try launching task manager via applications, let's see how it goes

I get E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
when I do wipe data / reset
after that I still go ahead and flash rom zip but it then says
E: Error in /sdcard/S5570XWKC1_MOD_ROM.zip (Status 0)
Installation aborted.
and if I reboot it's stuck at Galaxy mini screen
Any ideas?
I'll have to flash my backup

splattx_x said:
I get E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
when I do wipe data / reset
Click to expand...
Click to collapse
Does you SD have a 2nd partition?
after that I still go ahead and flash rom zip but it then says
E: Error in /sdcard/S5570XWKC1_MOD_ROM.zip (Status 0)
Installation aborted.
and if I reboot it's stuck at Galaxy mini screen
Any ideas?
I'll have to flash my backup
Click to expand...
Click to collapse
Im not sure abour this one. Can you check if the zip file is not corrupted?

parasmi said:
Does you SD have a 2nd partition?
Click to expand...
Click to collapse
No, I only have one partition in FAT format.
parasmi said:
Im not sure abour this one. Can you check if the zip file is not corrupted?
Click to expand...
Click to collapse
I tried once, failed. Then I deleted the file from SDcard, copied it again but it failed again with same error... I was able to extract the zip correctly so I don't think the file is corrupt. Perhaps Latin and European devices are more different than we thought.

splattx_x said:
No, I only have one partition in FAT format.
I tried once, failed. Then I deleted the file from SDcard, copied it again but it failed again with same error... I was able to extract the zip correctly so I don't think the file is corrupt. Perhaps Latin and European devices are more different than we thought.
Click to expand...
Click to collapse
Hhmmm....Let's take this offline. Sent you PM

Hi,
Does this ROM work with my phone?
PDA: S5570XWKC7
PHONE: S5570XXB1
CSC: S5570XXKC3
System information shows me exactly the same version number, except Build is FROYO.XWKC7 compared to FROYO.XWKC1

the same happen with me plz edit ur scrpit and thanks

splattx_x said:
I get E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p2
when I do wipe data / reset
after that I still go ahead and flash rom zip but it then says
E: Error in /sdcard/S5570XWKC1_MOD_ROM.zip (Status 0)
Installation aborted.
and if I reboot it's stuck at Galaxy mini screen
Any ideas?
I'll have to flash my backup
Click to expand...
Click to collapse
Hey are u trying to do it with rom manager?
Sent from my GT-S5570 using xda premium

debsattam said:
Hey are u trying to do it with rom manager?
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
was trying with CWM. Anyway I was able to upgrade to Gingerbread and then flashed new EmanoN rom based on gingerbread and everything went ok.
Thanks for the help anyway!

what are the modem issues? because i think i face modem issues but i cannot find a thread where somebody has issues like mine

This is an outdated thread. Please go HERE instead

[RECOVERY] HighOnAndroid v1 Unofficial ClockworkMod Recovery Touch 6.0.1.1

{
"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"
}
I've put together an unofficial ClockworkMod Recovery 6.0.1.1 until Koush adds to ROM Manager, tested working for all features except SD card mount. Working on the latter at the moment.
UPDATE: This recovery does work for both GT-N8000 (3g version) and GT-N8013 (wifi version), just confirmed. (8/16/2012)
Notes:
v1 - Touchscreen is a bit if when you have to scroll, please use the volume buttons for scrolling otherwise you may get accidental presses.
Changelog:
v1 - Everything working except SD card mount. You can backup/restore/ROM to internal or external SD card and other CWM features functional.
Flash this in ODIN or Heimdall:
Download HighOnAndroid v1 ClockworkMod Recovery 6.0.1.1
Also, here's stock recovery you can flash in ODIN or Heimdall to revert (and get OTA updates):
http://downloadandroidrom.com/file/GalaxyNote10.1/recovery/N8000_StockRecovery.tar
Credits:
Of course to Koush! I used his builder then hacked graphics.c + other files to make it work.

reserved
reserved

Amazing! Can't wait to get my hands on my Note
Sent from my SCH-I535

Way to go buddy!

You built it off builder.ClockworkMod.com, didn't you?
Sent from my GT-P1000

cdesai said:
You built it off builder.ClockworkMod.com, didn't you?
Sent from my GT-P1000
Click to expand...
Click to collapse
I did initially but had to hack it to make it work.

zedomax said:
I did initially but had to hack it to make it work.
Click to expand...
Click to collapse
Hey Zedo! Check your PM !

I noticed it does not actually backup system.img on my device, nor did any of my attempts from the clockworkmod builder site either. It says it, but skips over in reality. This will be important to fix if indeed it is not backing it up...
EDIT: Nevermind... I guess the system.img was hiding from me

Where can I find the backup? From my Tab 10.1 I was used to find it in clockworkmod on the sdcard...

akxak said:
Where can I find the backup? From my Tab 10.1 I was used to find it in clockworkmod on the sdcard...
Click to expand...
Click to collapse
It's in your clockworkmod/backup directory. Now, with the new CWM, it stores backups as pieces of files under clockworkmod/blobs directory. This saves a ton of time when doing multiple backups as "blobs" store bits of your filesystem so when doing similar backups, it's not going to backup everything again.
Make sure you copy the whole clockworkmod folder to hard disk for moving though due to this new blobs feature. Your backup folder sizes might be much smaller because of this blobs thingee.

zedomax said:
I used his builder then hacked graphics.c
Click to expand...
Click to collapse
???
Please tutorial graphics.c ...Thanks by Notonlyeyes

I tried flashing with odin following the procedure on the video and with heimdall also, but when I boot in the recovery there is the stock one...both odin and heimdall say the flash is successful and the binary count increases...I also of course tried downloading the recovery again...any suggestions?

gol-D said:
I tried flashing with odin following the procedure on the video and with heimdall also, but when I boot in the recovery there is the stock one...both odin and heimdall say the flash is successful and the binary count increases...I also of course tried downloading the recovery again...any suggestions?
Click to expand...
Click to collapse
Did you do:
Code:
heimdall flash --recovery recovery.img

There is still no clean return-to-stock package available for the N8013: Could someone who has installed this recovery and NOT rooted their device or made any other modifications to /system please go into recovery, change the backup format to tar (it's in the backup/restore menu), and do a backup? Then please post system.ext4.tar
That will get us a stock unmodified system (including proper permissions and such), which can then be rooted and flashed in Odin to get stock unmodified kernel/recovery images. Unlike the N8000, the N8013 does not yet have a stock image available anywhere.

Zedomax......greatstuff...root access on the N8010 no problem at all
....................................................................................................
Entropy512
Will try to do this now... But it'll be N8010.
Ive got the file for the N8010 on my desktop, but XDA isnt letting me upload the file keeps failing - any thoughts?
Dc
Sent from my GT-N8010 using Tapatalk 2

Entropy512 said:
There is still no clean return-to-stock package available for the N8013: Could someone who has installed this recovery and NOT rooted their device or made any other modifications to /system please go into recovery, change the backup format to tar (it's in the backup/restore menu), and do a backup? Then please post system.ext4.tar
That will get us a stock unmodified system (including proper permissions and such), which can then be rooted and flashed in Odin to get stock unmodified kernel/recovery images. Unlike the N8000, the N8013 does not yet have a stock image available anywhere.
Click to expand...
Click to collapse
Just use this bud:
http://stockroms.net/file/GalaxyNote10.1/rooted/N8013/StockROMs.net-GT-N8013RootInjectedSystem.zip
And remove /system/xbin/su and /system/app/Superuser.apk
Other than those two files, it's completely stock I pulled off my stock N8013.
I could reupload it but it would be the exact same thing as removing the two files.

zedomax said:
Just use this bud:
http://stockroms.net/file/GalaxyNote10.1/rooted/N8013/StockROMs.net-GT-N8013RootInjectedSystem.zip
And remove /system/xbin/su and /system/app/Superuser.apk
Other than those two files, it's completely stock I pulled off my stock N8013.
I could reupload it but it would be the exact same thing as removing the two files.
Click to expand...
Click to collapse
That does the trick. So far I only saw your N8000 dump. .tar would be preferable due to permissions issues, but that issue is fixable with a little bit of time.
I did the same thing with I777... Right now the only RTS packages I have are rooted ones since it's so easy to remove. I really should reupload 100% clean packages (I used to have them, and then the MegaUpload fiasco killed ALL the damn mirrors and I haven't gotten around to reuploading...)
Edit: Oh, it's a zipped-up .tar - misleading, I usually name those either .tar.7z (using 7-zip to compress) or just .tar.gz or .tar.bz2 (standard compressed tarballs)

Entropy512 said:
That does the trick. So far I only saw your N8000 dump. .tar would be preferable due to permissions issues, but that issue is fixable with a little bit of time.
I did the same thing with I777... Right now the only RTS packages I have are rooted ones since it's so easy to remove. I really should reupload 100% clean packages (I used to have them, and then the MegaUpload fiasco killed ALL the damn mirrors and I haven't gotten around to reuploading...)
Edit: Oh, it's a zipped-up .tar - misleading, I usually name those either .tar.7z (using 7-zip to compress) or just .tar.gz or .tar.bz2 (standard compressed tarballs)
Click to expand...
Click to collapse
Well, I am just waiting for samfirmware to upload some official images, rather enjoy some of my note 10.1 first for awhile, it's pretty fascinating device, I've never used a tablet for a long time before getting this one, makes my life more productive. Yeah, what's up with Megaupload, that move by feds should have been illegal.

I have a few questions about root and I was hoping someone could help. I am fairly new to rooting. I have a galaxy nexus that i use CWM Recovery and have root. I need to root my Note but I am not familiar with the binary counter (all is a little different than the nexus was). If I Flash this CWM recovery and root after will the binary counter increase? is the only way to prevent binary counter to inject root? (all CWM will cause it to increase?)
I know i am a noob but any insight would be greatly appreciated!
Thanks guys!

greenzkool said:
I have a few questions about root and I was hoping someone could help. I am fairly new to rooting. I have a galaxy nexus that i use CWM Recovery and have root. I need to root my Note but I am not familiar with the binary counter (all is a little different than the nexus was). If I Flash this CWM recovery and root after will the binary counter increase? is the only way to prevent binary counter to inject root? (all CWM will cause it to increase?)
I know i am a noob but any insight would be greatly appreciated!
Thanks guys!
Click to expand...
Click to collapse
Flashing a recovery or kernel image in Odin will cause the binary counter to increase.
Flashing it using dd or Mobile Odin from a rooted system will not make it increase.
So the "safest" way to root is currently to flash that root-injected system image linked a few posts above, as it's fully unrootable and won't trigger the counter.
I have visitors most of this weekend so won't be able to do much work - once I get my kernel source tree properly set up I'm going to work on getting TriangleAway working on this device.

[4.4.2][ROOT] SGP311 + SGP312 stripped

KK 10.5.A.0.230 UPDATE SGP311 to 4.4.2 FR / SGP312 to 4.4.2 VMo UK + ROOT
{
"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"
}
If you are on rooted Tablet Z SGP311/312 4.1/4.2/4.3 you can update to this latest version following the guide, just download 4.4 update and start with point 10. ​
Requirements:
1. Flashtool 0.9.15+ (download)
2. XZDualRecovery 2.7.123 or newer.
3.1. Back to 4.1.2 and Rooting or
3.2. Rooted Android 4.3 10.4.B.0.569 or newer
4.1 Tablet Z SGP311[/URL])​
How to update:
1. if you're in non-rooted 4.3, non-rooted 4.2, etc., flash SGP31X 4.1.2 FTF using FlashTool and root
Xperia TabZ Android 4.1 FTF
TabZ 4.1 ROOT - How to
2. Select Debugging on from the Settings Menu
3. Select Unknown Sources under Security Menu in Settings
4. Download 4.4 .zip and stripped.ftf:
Google Drive:
SGP311 :
working 4.4 root for SGP311 in General Discussion > http://forum.xda-developers.com/showthread.php?t=2767847
SGP312:
RAR file (ZIP+FTF)
RAR MD5: EAFBA854DC7408250050356BF882BA95
this zip and ftf work without errors ​5. Put 'SGP3XX_4.4.flashable.zip' on (the external) SDcard1;
6. Put 'SGP3XX_4.4.ftf' inside the Flashtool/firmwares folder;
7. Download XZDualRecovery (latest Version is TabZ-lockeddualrecovery2.7.123.beta.installer.zip), and unzip
http://nut.xperia-files.com/​8. connect your tablet and install the XZ Dualrecovery folder Install.bat file
9. Select the Option as SuperUser (2), it will copy all the stuffs and reboot and start in Philz Recovery.
For clean 4.4 installation with root click "Clean to Install a New ROM" in Wipe Data/Factory Reset
10. Flash 'SGP3XX_4.4.flashable.zip' in Philz,
11.. do not reboot but go back to the main menu, then go to Power->Power off
12. Flash everything in 'SGP3XX_4.4.stripped.ftf';
13. Reboot to system without clearing (dalvik-/)cache.
14. Connect your tablet and once again install the newest XZDualRecovery, Tablet will reboot into Recovery, now just click 'system reboot'
​
If works hit "thanks" button
!!! Create a backup of your TabZ in CWM or TWRP and don't forget to backup the contents of 'SDCard0';!!!
!!! Please read the instructions clearly and flash.!!!
!!! Its your Tablet and I will not responsible for any brick/failures on your Device.!!!​

Thankx Dude. Could you make a 312 version? :good:

Jonfensu said:
Thankx Dude. Could you make a 312 version? :good:
Click to expand...
Click to collapse
tomorrow send me ftf file

ryany67 said:
tomorrow send me ftf file
Click to expand...
Click to collapse
I am uploading (3H remaining) to Mega the VMo UK_IE version :good:
PS. Could you release the Fix for Settings lag+Deodexed for 311/312?
EDIT. Here you go
https://mega.co.nz/#!F9Fi3SRT!QiEzU1RooEeV6pZ9DwHdX7fMhu-vlkBqFCJBe_wV0R8

I've tried to flash and followed the instructions to the letter.
I got an error (code 7) while flashing "SGP311_4.4.flashable.zip" in recovery.
Despite the error, I continued the installation process and could get the system working fine, except I have no root access.

gustavo.rocha said:
I've tried to flash and followed the instructions to the letter.
I got an error (code 7) while flashing "SGP311_4.4.flashable.zip" in recovery.
Despite the error, I continued the installation process and could get the system working fine, except I have no root access.
Click to expand...
Click to collapse
what tablet model and rom do you have? rooted stock 4.1 - 4.3 for SGP311?

can i put the file on the internal sd-card? don't have an external one, yet.
Sent from my GT-I9100 using Tapatalk

if i'm on 4.3 rooted should I start from pt2 or do i need to follow a different procedure?

Can't download .zip file from Google drive-download limits (too many users downloaded...) Please a mirror..
Thanks!

Riekr said:
if i'm on 4.3 rooted should I start from pt2 or do i need to follow a different procedure?
Click to expand...
Click to collapse
download ftf and zip and start with no.10.

Someone please upload this to a mirror.
Thank you.

finally a clear guide to root sp311 non rooted, i`ll follow it and hopefully i`ll manage to root my Z having KK rooted.
i assume strating from 4.3 not rooted doesn`t matter with FW versiion is been running on it (ie the last release of 4.3)

Pls anyone,upload SP311 .zip file to some mirrors-it's impossible to download it from google drive (too many downloads)...
Thanks!

ValVK said:
Pls anyone,upload SP311 .zip file to some mirrors-it's impossible to download it from google drive (too many downloads)...
Thanks!
Click to expand...
Click to collapse
Create your own google account and copy my file into your google drive. Then you can, without limit, everything download.
Sorry but on megaupload i dont have any account and free hostings are too slowly to up- and download smthng

Thanks for the tip! I have a Google drive account,but i can't copy that .zip file to my account...
Or i'm a blind man with my 4 eyes -i don't see,how i can do it...Can you pls point me to that???
Thanks for help!!!

ValVK said:
Thanks for the tip! I have a Google drive account,but i can't copy that .zip file to my account...
Or i'm a blind man with my 4 eyes -i don't see,how i can do it...Can you pls point me to that???
Thanks for help!!!
Click to expand...
Click to collapse
Hmmm... Im not at home now, im on tablet. Ill do it later^_^

Maybe you have a md5 sum for that .zip file? I think i got it done,but would be nice to be sure,if .zip file is intact.
Thank you!

gustavo.rocha said:
I've tried to flash and followed the instructions to the letter.
I got an error (code 7) while flashing "SGP311_4.4.flashable.zip" in recovery.
Despite the error, I continued the installation process and could get the system working fine, except I have no root access.
Click to expand...
Click to collapse
I have the same problem

As i was reading on xda,that error code 7 mostly is related on version Flashtool or recovery.
It must me exactly as p.1 and 2 in OP.

Same error for me flashing SGP312 with the latest TabZ-lockeddualrecovery2.7.123-BETA.flashable.zip from NuT.
Fails on set_perm for me
Hangs now at sony name on boot...

[RECOVERY][on7xelte] TWRP 3.3.0 for Galaxy J7 Prime

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

[GUIDE][SM-T510] Unlock/Root - Tab A 10.1 (Android 10)

This are exactly the steps I did to root this device.
Pre-requisites
. Odin 3.14.4
. Latest MagiskManager(Im using 8.0.2)
. bootloader unlocked
. Firmware that matches the version installed on your device.
. Lz4 extractor : https://github.com/lz4/lz4/releases
. TAR.MD5_PACKAGER
First at all, remember to unlock T510 bootloader
The firmware which is based is this : SM-T510_1_20200702122203_r4oibm2ll7_fac.zip
. Extract AP_T510XXU3BTFN_CL19000394_QB32592397_REV02_user_low_ship_meta_OS10.tar.md5
. Extract boot.img from .tar.md5
. lz4.exe -d boot.img.lz4
boot.img
. Copy MagiskManager-v8.0.2.apk to your tablet and Run it.
- Magisk > Install > Recovery Mode Selected > Next > Method > Select and Patch a File > boot.img > LET'S GO > "All done!"
File called : magisk_pached.img
. Copy to PC
- copy magisk_patched.img boot.img
copy boot.img to TAR_MD5_PACKAGER\parts\
. TAR.MD5_PACKAGER.bat > "1" > boot.img > "Y" > "2" > "1" > "Y" > "4"
in TAR_MD5_PACKAGER\packaged\ : boot.img.tar.md5
. Run Odin
Plug USB > should say "Added!!"
. Volume Up and Power until you get into recovery menu > reboot to bootloader
- Connect USB
- Run ODIN
. In Odin : AP > boot.img.tar.md5
Options > Delect "Auto Reboot"
Click Start . Make sure the operation succeeds.
Unplug your device and reboot.
. Ask for Factory data reset > Factory Reset
. Reboot System now
. Volume Up + Vol down + Power
. Setup WiFi
. Install and run MagiskManager-v8.0.2.apk
. Tablet will ask Reboot System now
Click to expand...
Click to collapse

Great! I somewhat did the same method for rooting/twrp installing. I was on latest Android 10 build(September patch perhaps). I download the latest firmware and unzipped it then I further extracted AP_T510XXX......... .tar.md5 using zarchiver which have me AP_T510XXX........ .tar. Instead of extracting boot image I patched the whole thing with megisk and flashed it from AP from ODIN. When tablet booted installed megisk manager apk and saw that tablet was rooted.
You can further flash TWRP image using flashify but then stock ROM may not boot. Anyway moving further if you want to flash GSI, first flash Lineage or Nexus Rom and then A64b GSIs can be flashed.

Thanks both! i will take a look when i am at home, i tried to patch AP_T510XXX......... .tar.md5 with magisk but i didnt extract it before and it hold on boot, i try to extract first like @Mrigendra10 then patch it and then odin...

i like the guide but the wording need some improvement newer members to understand it clearly just my 2 cents thanks for guide.

Help me out here, I did everything correctly and installed it with Odin, it was a success, but when I installed magisk on my tablet again, nothing new happened, didn't ask me to reboot and I tried an app that requires root but said I wasn't rooted. Help please.

Used a root checker, says a super user app was found, that being Magisk. says root unavailable and no su binary .

Hi, just to be sure
Odin > Options > Delect
means 'Deselect' and not 'Select'?
Thx!

cera33 said:
Hi, just to be sure
Odin > Options > Delect
means 'Deselect' and not 'Select'?
Thx!
Click to expand...
Click to collapse
Yes, it does

I was able to complete everything step by step and used a root checker and it states "Root access is not properly installed on this device. Any idea what may have gone wrong? Do I just start over and try again?

same here. can not root SM510. tried linegae, nexus and stock from. any video root with magisk with rambus on and saftety net passed?

Same..

Hey, just some notes to clear up any confusion about Magisk on the T510. The tablet doesn't have a ramdisk available for boot, so Magisk must be installed to the recovery partition. Below is a screenshot of Magisk Manager data from my own tablet:
{
"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"
}
And per the Magisk installation instructions:
Pay special attention to the Ramdisk info. If the result is Yes, congratulations, your device is perfect for installing Magisk! However, if the result is No this means your device’s boot partition does NOT include ramdisk. This means you will have to go through some extra steps to make Magisk work properly.
If your device does not have boot ramdisk, read the Magisk in Recovery section after installing. The information in that section is VERY important!
If you are using a Samsung device and the SAR result is Yes, please check its own section.
If you are using a Huawei device and the SAR result is Yes, please check its own section.
Click to expand...
Click to collapse
In order to boot into system with active Magisk, one has to essentially boot into recovery. From the Magisk in Recovery section (Bixby button references can be ignored):
If your device does not have ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk.
When Magisk is installed in your recovery, you CANNOT use custom recoveries to install/upgrade Magisk! The only way to install/upgrade Magisk is through the Magisk app. It will be aware of your device state and install to the correct partition and reboot into the correct mode.
Since Magisk now hijacks the recovery of the device, there is a mechanism to let you actually boot into recovery mode when needed: it is determined by how long you press the recovery key combo.
Each device has its own key combo to boot into recovery, as an example for Galaxy S10 it is (Power + Bixby + Volume Up). A quick Google search should easily get you this info of your device. As soon as you press the combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. If you decide to boot into actual recovery mode, continue to press volume up until you see the recovery screen.
After installing Magisk in recovery (starting from power off):
(Power up normally) → (System with NO Magisk)
(Recovery Key Combo) → (Splash screen) → (Release all buttons) → (System with Magisk)
(Recovery Key Combo) → (Splash screen) → (Keep pressing volume up) → (Recovery Mode)
Click to expand...
Click to collapse
I can understand now why John Wu was spitting nails mad when Google switched to dynamic partitions with system-as-root: it completely effs up the architecture for rooting with Magisk.
I don't know why Google and manufacturers persist in making it messy to nigh-impossible for end users--who desire to do so--to have full control of their own devices. Stupid. Just stupid. Usunoro...
On the positive side, I hope this helps everyone trying to root their T510 tablets, and explains the weirdness people may have encountered.
(P.S. Since hardware attestation is used on the T510, SafetyNet won't pass, no matter what. There aren't any modules that can address this, given that hardware is being used for the evaluation. Another baka change! Also, I'm sticking with Pie since I can't stand Scoped Storage. Can't. Stand. It.)
Fur and Purrs --
--
King Cheetah

wolfyj1 said:
I was able to complete everything step by step and used a root checker and it states "Root access is not properly installed on this device. Any idea what may have gone wrong? Do I just start over and try again?
Click to expand...
Click to collapse