I didn't see any threads with this model
I'm on NOUGAT. Official build stock. Simple root same as always,
1. Developer options - own unlock
2 Download mode - flash TWRP 3.2.1
3. TWRP recovery - flash Magisk 16
Profit!
SM- T817
Btw u can flash unbranded FW XAS variant for Sprint, or 817R4 for all other carriershttps://updato.com/firmware-archive-select-model?record=6923350DAEEC11E7963AFA163EE8F90B
@beatbreakee Does it work for the AT&T (T817A) too?
And by the flash you mean, is it through Odin? I'm so scared that if i flash the wrong TWRP, it will get brick (because as long as i know, T817 is different with T817A)
---------- Post added at 04:01 PM ---------- Previous post was at 03:55 PM ----------
beatbreakee said:
I'm on NOUGAT. Official build stock. Simple root same as always,
1. Developer options - own unlock
2 Download mode - flash TWRP 3.2.1
3. TWRP recovery - flash Magisk 16
Profit!
SM- T817
Btw u can flash unbranded FW XAS variant for Sprint, or 817R4 for all other carriershttps://updato.com/firmware-archive-select-model?record=6923350DAEEC11E7963AFA163EE8F90B
Click to expand...
Click to collapse
And by the Own unlock, is that a typo? Was it OEM unlock?
And can i also flash T817's ROM ((such as Lineage) to T817A?
Thanks so much before! I'm hoping for your answer
Yes .. sorry it took so long I must have notifications turned off. And yes I meant OEM UNLOCK. (Autocorrect must have gotten me). And yes use Odin to flash TWRP, then use TWRP to flash Magisk. Here's what I have .. mine is an SM-T817P but this TWRP will work for all the 817 models, here's a link from Team Win website.
https://dl.twrp.me/gts210velte/twrp-3.2.1-0-gts210velte.img.tar.html
And then just Flash MAGISK 16.0 from here.
http://tiny.cc/latestmagisk
I take no credit for creation or discovery of these files. I had help from a few developers here when I needed it regarding my tab. I'm sure u will be fine, just make sure you double check 3 things.
1. Make sure OEM unlock is turned on in developer options
2. Make sure you flash the TWRP using Odin 3.07 (I used)
3. Uncheck AUTO REBOOT in Odin options. (This is important because on initial reboot you have to reboot into recovery 1st, otherwise the stock Rom will erase TWRP and go back to stock.)
MAKE SURE WHEN U FINISH THE TWRP FLASH, THAT YOU DO A HARD REBOOT, AND BOOT INTO RECOVERY AT LEAST 1 TIME BEFORE YOU LET YOUR STOCK ROM RUN. THIS WILL ENSURE TWRP STAYS INSTALLED.
Take care
beatbreakee said:
Yes .. sorry it took so long I must have notifications turned off. And yes I meant OEM UNLOCK. (Autocorrect must have gotten me). And yes use Odin to flash TWRP, then use TWRP to flash Magisk. Here's what I have .. mine is an SM-T817P but this TWRP will work for all the 817 models, here's a link from Team Win website.
https://dl.twrp.me/gts210velte/twrp-3.2.1-0-gts210velte.img.tar.html
And then just Flash MAGISK 16.0 from here.
http://tiny.cc/latestmagisk
I take no credit for creation or discovery of these files. I had help from a few developers here when I needed it regarding my tab. I'm sure u will be fine, just make sure you double check 3 things.
1. Make sure OEM unlock is turned on in developer options
2. Make sure you flash the TWRP using Odin 3.07 (I used)
3. Uncheck AUTO REBOOT in Odin options. (This is important because on initial reboot you have to reboot into recovery 1st, otherwise the stock Rom will erase TWRP and go back to stock.)
MAKE SURE WHEN U FINISH THE TWRP FLASH, THAT YOU DO A HARD REBOOT, AND BOOT INTO RECOVERY AT LEAST 1 TIME BEFORE YOU LET YOUR STOCK ROM RUN. THIS WILL ENSURE TWRP STAYS INSTALLED.
Take care
Click to expand...
Click to collapse
Wow man, thanks so much! I was so confuse about this TWRP thing. I'm not sure if will the TWRP for T817 works for T817A, P, etc. and vice versa. I'm really appreciated your help
i need efs and cert file for t817p.
pls mate, i need efs and cert file for t817p. pls i need it ugently for imei repair or does anyone have any way to repair imei on t817p sprint 3600000000000
Related
DISCLAIMER : You are solely responsible for what you do with this information.
Last Update: Jan.29 (2017)
••••••••••••••••••••••
Custom Recovery
••••••••••••••••••••••
Thanks to @jackeagle for these
TWRP Builds (these ARE compatible)
I used FlashFire to flash the recovery (must be rooted)
See second post for help with Odin.
•••••••••••
Backups
•••••••••••
Notice: THESE ARE TWRP BACKUPS!!
A factory reset will be necessary prior to the restore, or best before it.
Further help in post 2
This debloated (with SuperSU) backup is the latest I have uploaded and it's only around 622mb
A debloated without root version is also abailable.
**by debloated I have removed a bunch of stock Samsung/Google and other applications.
This old 2gb backup has SuperSU and AppOps pre-installed(forgot to remove, has all stock apps)
These other stock partitions include the stock recovery.
I am currently unable (no PC) to produce a flashable zip, if you know what you are doing you can make use of these other files.
This phone needs:
- A permissive kernel
- a deodexed version of this ROM (for xposed)
- cm12/13
- etc etc
If you found this post helpful please hit thank you and leave feedback
Helpful Info:
TWRP NOT RECOGNIZING THE BACKUP???
Stay calm, here's what you do:
zenful said:
∆∆∆make sure to put the files for the these backups in a folder on root of your SD card called TWRP/BACKUPS/<device ID>/BACKUPS/ in order for TWRP to recognize the backups on your device. If you don't know your device ID, just use TWRP and make a backup of whats currently on your device to get the folder with that device ID than place the backup in that location.
Click to expand...
Click to collapse
How to Flash TWRP recovery using Odin said:
Download Odin 3.12.3
Unzip the Odin 3.12.3 .zip file and run/open Odin3 v3.12.3.exe file from the extracted files on your PC.
Make sure you’ve downloaded a Odin flashable TWRP recovery .tar file compatible for your device.
(If applicable) Enable OEM unlock:
Go to Settings » About phone » and tap Build number seven times to enable Developer options.
Go back to main Settings page, scroll to bottom and select Developer options from there.
Under Developer options, look for Enable OEM unlock checkbox/toggle and enable it.
Boot your device into Download mode:
Switch off your device.
Press and hold “Home + Power + Volume down” buttons for a few seconds until you see a warning screen.
Press Volume Up on the warning screen to accept it and boot into Download mode.
Once your device is in download mode, connect it to the PC with a USB cable. The Odin window on PC should detect the device and show an “Added!!” message.
Now click on the AP tab on Odin window and select the TWRP recovery .tar file that you downloaded for your device.
└ Note: DON’T play with any other options on the screen. You’re only required to connect your device and select the TWRP recovery .tar file in the AP tab.
Click the Start button on Odin and wait for it to finish the process. Once it has finished successfully, you’ll see a pass message on the Odin screen.
Your device will automatically reboot when Odin is done flashing. You can then disconnect your device.
How to boot into TWRP recovery on a Samsung Galaxy device
Switch off your device.
Press and hold “Home + Power + Volume Up” buttons for a few seconds and as soon as you see your device’ logo on-screen, release three buttons altogether. Your device will boot into TWRP recovery.
source
source
Click to expand...
Click to collapse
Anybody find out about custom recoveries on the SM-978L?
Well I don't know if this helps, but my brother soft bricked his phone while trying to put a custom boot-animation on his phone. I figured out how to fix it by flashing https://download.chainfire.eu/719/CF-Root/CF-Auto-Root/CF-Auto-Root-e5lte-e5lteub-sme500m.zip using odin 3.09. After i flashed it and reset his device it booted back up like normal, and he had root. Just for ****s and giggles i decided to try to flash http://forum.xda-developers.com/gal...ment/recovery-twrp-samsung-galaxy-e5-t3283089. When i tried to reboot into recovery it told me that the seandroid was enforcing. My question is if we flash http://forum.xda-developers.com/gal...nel-permissive-lollipop-stock-kernel-t3387015 will we be able to use this custom recovery. I know it is not built for this specific device, but i was wondering if they were close enough for it to work. Just to afraid to flash it and brick his device with no backup images available.
bndnrd321 said:
Well I don't know if this helps, but my brother soft bricked his phone while trying to put a custom boot-animation on his phone. I figured out how to fix it by flashing https://download.chainfire.eu/719/CF-Root/CF-Auto-Root/CF-Auto-Root-e5lte-e5lteub-sme500m.zip using odin 3.09. After i flashed it and reset his device it booted back up like normal, and he had root. Just for ****s and giggles i decided to try to flash http://forum.xda-developers.com/gal...ment/recovery-twrp-samsung-galaxy-e5-t3283089. When i tried to reboot into recovery it told me that the seandroid was enforcing. My question is if we flash http://forum.xda-developers.com/gal...nel-permissive-lollipop-stock-kernel-t3387015 will we be able to use this custom recovery. I know it is not built for this specific device, but i was wondering if they were close enough for it to work. Just to afraid to flash it and brick his device with no backup images available.
Click to expand...
Click to collapse
Did you ever gather up enough courage to try? It would seem like it should work. I might try it myself, but I cant afford to buy another one if it fails.
JoeSchmo2840 said:
Did you ever gather up enough courage to try? It would seem like it should work. I might try it myself, but I cant afford to buy another one if it fails.
Click to expand...
Click to collapse
I'm the brother bndnrd was referring to.... at this time we haven't tried it but we are almost sure that this straight talk (tracphone) version is the same as the one mentioned. Just like everyone else though I just don't have $200 to test it if it were to fail.
My stupidity in not setting perms right on the boot animation is what caused the soft brick in the first place and apparently.. what ever he did.... was able to boot the phone back up bypassing perms.
If I can pay off a few bills early enough I will set aside some cash and try the build we think will work but that will be at least a month away.
If TWRP actually works after that permissive kernel is installed, we can finally get a stock nandroid backup. That would take the fear away from testing that custom cyanogen build.
JoeSchmo2840 said:
If TWRP actually works after that permissive kernel is installed, we can finally get a stock nandroid backup. That would take the fear away from testing that custom cyanogen build.
Click to expand...
Click to collapse
I ended up making a nandroid backup of this phone and the only thing I couldn't make a backup of was the boot and recovery for it.
You can find out all the partitions you need to use dd with to start a backup by doing
ls -al /dev/block/bootdevice/by-name
Click to expand...
Click to collapse
If I had the resources for a computer I would have uploaded a copy of my stock image, I'll see what I can do about getting one up. Also saw this tool that I thought may be useful for getting a flashable image.
tool-mmcblk0-extractor
Anyways, until next time x.x
Just wanted to post this and see if anyone has theirs different.
Also if someone could decompile the boot.img (I have a link to mine I can send) I'll work on a passive kernel for us.
допоможіть! потрібна прошивка для мого sm-s978l 4g
Took and wiped the system and data. now loaded only Samsung logo and TWRP 3.0.2
Or maybe someone has a backup of SM-S978L 4G?
oleksandr.lutsyk said:
Took and wiped the system and data. now loaded only Samsung logo and TWRP 3.0.2
Or maybe someone has a backup of SM-S978L 4G?
Click to expand...
Click to collapse
What do you need a backup of? I haven't uploaded data or system partitions yet but I have the rest.
Also, you successfully got TWRP 3.0.2 working? If so please share the details on how please
[via Tapatalk]
Help! Need firmware for my SM-S978L [5.0.2] Straight Talk's E5
Took and wiped the system and data. now loaded only Samsung logo and tvrp
Or maybe someone has a backup of SM-S978L [5.0.2] Straight Talk's E5?
---------- Post added at 10:22 PM ---------- Previous post was at 10:19 PM ----------
I need backup or firmware....
---------- Post added at 10:49 PM ---------- Previous post was at 10:22 PM ----------
zenful said:
What do you need a backup of? I haven't uploaded data or system partitions yet but I have the rest.
Also, you successfully got TWRP 3.0.2 working? If so please share the details on how please
[via Tapatalk]
Click to expand...
Click to collapse
androiding. how/how-to-install-twrp-recovery-using-odin/
If you do this it will be possible. Make a backup for me)
updated main post, will try uploading backup by tonight
zenful backup request
zenful said:
UPDATED dec 8 2016
#############
TWRP thanks to user @jackeagle for providing us with some TWRP builds for the E5.
Jackeagle TWRP build (I believe he has updated versions but this is the one I KNOW works for this phone)
https://www.androidfilehost.com/?fid=24052804347821291
Other builds
http://forum.xda-developers.com/showpost.php?p=62973386&postcount=2
http://androiding.how/galaxy-e5-twrp-recovery/
http://androiding.how/how-to-install-twrp-recovery-using-odin/
####
You can also use FlashFire to flash the recovery as well (must have root first)
Have fun guys!
#edit dec11.2016
Have a twrp backup of the /system partition and a dump of the other partitions as well, just get up with me on here.
Click to expand...
Click to collapse
Hello, I currently have the twrp running but for some reason google play services has stopped working has blocked me our of many of my apps and functions on the phone. The only backup I have at all has this occurring may I please use your backup and partitions so I can have a working phone for the upcoming holiday.
El_Ogan said:
Hello, I currently have the twrp running but for some reason google play services has stopped working has blocked me our of many of my apps and functions on the phone. The only backup I have at all has this occurring may I please use your backup and partitions so I can have a working phone for the upcoming holiday.
Click to expand...
Click to collapse
Hey @El_Ogan check your inbox, or the first post to this thread for the link. Hope it helps, happy holidays
??/
zenful said:
Hey @El_Ogan check your inbox, or the first post to this thread for the link. Hope it helps, happy holidays
Click to expand...
Click to collapse
i have this phone and twrp works but nothing eles is this a complet back up i can just restore from twrp or is there something eles i am in need of to get this phoe working its a sm-s978l but shows e500h when i plug it in to my computer ??? so i am really confused
bullfrog83 said:
i have this phone and twrp works but nothing eles is this a complet back up i can just restore from twrp or is there something eles i am in need of to get this phoe working its a sm-s978l but shows e500h when i plug it in to my computer ??? so i am really confused
Click to expand...
Click to collapse
Hey no worries and yes it's just a full backup from TWRP just stupid in the sdcard and navigate to TWRP's restore section and it should auto find it. Any other files needed I'll also have, but this a bit a flashable zip or flashable via Odin, and
I imagine Odin says that after you flashed TWRP right? If so that's because that's what the TWRP was made for so it seems like Odin checked the recovery.
If it said that BEFORE you flashed it, that's very intriguing and helpful to me
thank you very much i really like this phone maybe ill be able to use it again havent went back to odin since i put twrp on the phone but when i plug into my computer it says e500h in window on my computer when in twrp on the phone used to say sm-s978l so im not sure just the way it is introduced by windows
bullfrog83 said:
i have this phone and twrp works but nothing eles is this a complet back up i can just restore from twrp or is there something eles i am in need of to get this phoe working its a sm-s978l but shows e500h when i plug it in to my computer ??? so i am really confused
Click to expand...
Click to collapse
bullfrog83 said:
thank you very much i really like this phone maybe ill be able to use it again havent went back to odin since i put twrp on the phone but when i plug into my computer it says e500h in window on my computer when in twrp on the phone used to say sm-s978l so im not sure just the way it is introduced by windows
Click to expand...
Click to collapse
I feel ya just let me know if you need any more help and goodluck
Hi all.
I have the 935F International on it's way to me, delivering in the next day or so
By all accounts the 935F is already unlocked. To prepare, I have already downloaded Odin 3.11.1, CF's root file, TWRP twrp-3.0.2-2-hero2lte tar, and a custom ROM and bootloader/modem files.
I'm not a noob to flashing, just newish to Samsung.
What is the best way to start? Boot into stock, enable bootloader unlock on developer options, run Odin and flash TWRP, then CF's root file? Also, I want to run unencrypted - format data using advanced wipe 'yes' method?
The ROM states it sets root on installation. Do I then need to flash CF's root file?
Further, how are bootloader/modem tar files flashed? Is it as simple as selecting BL for bootloader, although I don't see anything for the modem??
Finally, what is the actual order of all this? I'm thinking: TWRP first, Format internal data second, CF root third, ROM flash from TWRP fourth, reboot to download mode from TWRP and then flash modem/bootloader last. Then reboot all together to set the phone up?
Thanks and any help is appreciated
1. Update to latest firmware
2. CF-Autoroot
3. TWRP
4. Flash no-verity-opt-encrypt.zip, wipe data.
5. Reboot recovery, mount system.
6. Wipe all except internal and external sd.
7. Flash your ROM
dynospectrum said:
1. Update to latest firmware
2. CF-Autoroot
3. TWRP
4. Flash no-verity-opt-encrypt.zip, wipe data.
5. Reboot recovery, mount system.
6. Wipe all except internal and external sd.
7. Flash your ROM
Click to expand...
Click to collapse
Thanks for the info :good:
When you say update to latest firmware this is Bootloader and Modem yes?
Steps 2 & 4 - just having done a little more research, are these outdated now?; as TWRP (latest) now fixes encryption and the ROM will inject (for a better term ) SuperSU when installing it? Or will this still need to be done irrespective of using the latest version of TWRP and ROM?
Cheers and thanks :good:
If you're not new to rooting and custom roms, pretty much all you need is to unlock OEM in Dev Options in Settings, Restart the device and hold Vol Down+Home+Power to get into Download Mode and press Up at the blue screen. Plug in your USB to your phone and run the tool on your PC.
Once Rooted, its business as usual. You don't need a guide to install TWRP, just install the Flashify app and let it do it for you, and then have no-verity-opt-encrypt.zip handy to flash. I know no-verity-opt-encrypt.zip is essential if you flash TWRP through ODIN, but not 100% sure if you should if you flashed TWRP through Flashify, I always flash no-verity-opt-encrypt.zip regardless so I unno.
Also if you find yourself in a semi-bricked situation where you can't figure out your problem, as long as you have Download Mode, you'll always have a way to get back to a working device. Samsung Smart Switch for Windows has an Emergency Mode that will revert your device back to Factory Conditions.
peteri8706 said:
Thanks for the info :good:
When you say update to latest firmware this is Bootloader and Modem yes?
Steps 2 & 4 - just having done a little more research, are these outdated now?; as TWRP (latest) now fixes encryption and the ROM will inject (for a better term ) SuperSU when installing it? Or will this still need to be done irrespective of using the latest version of TWRP and ROM?
Cheers and thanks :good:
Click to expand...
Click to collapse
I've been doing things this way since day 1 with no problems. My advice would be to do it the same way. I can assure you a solid install ;]
Yes, firmware is bootloader & modem. Great thread for this is here http://forum.xda-developers.com/s7-edge/how-to/official-stock-firmware-update-odin-t3335065
To change ROM to Global, i do the steps until i unlock the device, i use XiaoMiFlash to flash the last global ROM
and it's work fine
but I note that there is a choice in XiaoMiFlash 'clean all and lock', so i think it's better to lock the device again whit the global ROM to make to my data more safe,
than i flash it again with XiaoMiFlash and choose 'clean all and lock',
after that my "Redmi Note 7" is not working and give me the following screen(attached)-This MIUI version can't be installed on this device-:
so what can i do now to make my mobile work again, please advise.
Thanks.
SOVIETTION said:
To change ROM to Global, i do the steps until i unlock the device, i use XiaoMiFlash to flash the last global ROM
and it's work fine
but I note that there is a choice in XiaoMiFlash 'clean all and lock', so i think it's better to lock the device again whit the global ROM to make to my data more safe,
than i flash it again with XiaoMiFlash and choose 'clean all and lock',
after that my "Redmi Note 7" is not working and give me the following screen(attached)-This MIUI version can't be installed on this device-:
so what can i do now to make my mobile work again, please advise.
Thanks.
Click to expand...
Click to collapse
Man: 1 ) u must unlock already your bootloader using Miunlock tool, and try to flash already global rom not locking this time.
2) If the problem persist, u can install a custom recovery (like TWRP and there are many tutorials on it). Once it done, u must disable force encryption downloading the file in this thread
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
So, connect your device on your pc in recovery mode (TWRP), transfer the disableforceencript.zip on internal storage, click install button, and flash it. Reboot and enjoy.
Hope i helped u.
i can't use Miunlock tool, because now there is no account on my mobile so i can't login Miunlock tool with any account, also the not boot, it just boot to recovery mode or fastboot
SOVIETTION said:
i can't use Miunlock tool, because now there is no account on my mobile so i can't login Miunlock tool with any account, also the not boot, it just boot to recovery mode or fastboot
Click to expand...
Click to collapse
Man, i told u in a previous post, install a custom recovery like TWRP searching follow a guide. Once the devices will be in recovery mode (TWRP) flash this.zip (the latest MIUI Global) putting it into internal storage
https://www.xda-developers.com/xiao...s-incoming-call-floating-window-game-booster/
After u must flash the file that i linked u in previous post (disable dm verity force encrypt), and all will works.
MOD EDIT: QUOTE REMOVED
IGNORE THIS MAN! He only wants your money! You can unbrick on your own!
You can follow this guide to make your phone work again.
https://forum.xda-developers.com/redmi-note-7/how-to/guide-steps-to-unbrick-redmi-note-7-t3922543
I've bricked my phone recently too and made a post on my findings.
https://forum.xda-developers.com/showpost.php?p=80017795&postcount=12
Don't lose hope!
LionHeart90 said:
Man: 1 ) u must unlock already your bootloader using Miunlock tool, and try to flash already global rom not locking this time.
2) If the problem persist, u can install a custom recovery (like TWRP and there are many tutorials on it). Once it done, u must disable force encryption downloading the file in this thread
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
So, connect your device on your pc in recovery mode (TWRP), transfer the disableforceencript.zip on internal storage, click install button, and flash it. Reboot and enjoy.
Hope i helped u.
Click to expand...
Click to collapse
Just a suggestion. If he decides to install OrangeFox recovery, it already has the option to toggle Disable Force Encryption built-in.
Hope he gets the phone working again...
How?!
LionHeart90 said:
Man, i told u in a previous post, install a custom recovery like TWRP searching follow a guide. Once the devices will be in recovery mode (TWRP) flash this.zip (the latest MIUI Global) putting it into internal storage
https://www.xda-developers.com/xiao...s-incoming-call-floating-window-game-booster/
After u must flash the file that i linked u in previous post (disable dm verity force encrypt), and all will works.
Click to expand...
Click to collapse
How can he install custom recovery with a locked boot loader?!
I've seen people here struggling with rooting j701f a.k.a J7 Nxt. I always got bootloop when installed TWRP and flashed Magisk, so little trick here is installing custom kernel; i am using Helios kernel 3.1 and it works perfectly. (Select wifi driver new with android pie when installing, first option).
Technically it should work on J7 Nxt /Neo /Core. Tested in J7 Nxt 701F, DDU6CSF1 Stock firmware OneUI 1.1 Indian Variant.
Procedure from start.
Given:
You're running on Pie.
OEM Unlock option enabled in developers Option.
Get Odin - https://odindownload.com/SamsungOdin/
Get TWRP - https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Get Helios Kernel https://forum.xda-developers.com/ga...70/kernel-heliospie-kernel-3-1-j701x-t3941438
Start Odin and untick auto reboot option.
Select Boot.tar file in BL
Select Recovery.tar file in AP
Flash.
Unplug phone.
Remove battery.
Put it back.
Hold Volume up (+) then Home then Power button for 20-30seconds
Press Power button.
Press power button again.
You'll see TWRP recovery 3.1.1 , say thanks to GhaithSYR
Swipe to modify system.
Format data, Type yes (Beware it'll erase all data and factory reset except SD card.
Flash Kernel.
Reboot.
Update Magisk.
You can update your TWRP to 3.2.1 : https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Credits:
@GhaithSYR for TWRP
@JaskaranSM and @@ananjaser1211 for Helios Kernel
@topjonhuw For Magisk
@lzzy12 for TWRP 3.2.1 Image
Also hit Thanks to respective threads linked above.
PM for Queries. Bit busy so posting it short, will update Detailed guide soon.
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
RECOVERING:
If you mess up and device is not working there is very easy way to get stock rom back. No need to panic at all.
Go to Sammobile.com get your Stock Rom.
Flash via Odin.
Done.
xperia ray said:
I've seen people here struggling with rooting j701f a.k.a J7 Nxt. I always got bootloop when installed TWRP and flashed Magisk, so little trick here is installing custom kernel; i am using Helios kernel 3.1 and it works perfectly. (Select wifi driver new with android pie when installing, first option).
Technically it should work on J7 Nxt /Neo /Core. Tested in J7 Nxt 701F, DDU6CSF1 Stock firmware OneUI 1.1 Indian Variant.
Procedure from start.
Given:
You're running on Pie.
OEM Unlock option enabled in developers Option.
Get Odin - https://odindownload.com/SamsungOdin/
Get TWRP - https://forum.xda-developers.com/ga...-j701f-core-nxt-exynos-7870/recovery-t3693009
Get Helios Kernel https://forum.xda-developers.com/ga...70/kernel-heliospie-kernel-3-1-j701x-t3941438
Start Odin and untick auto reboot option.
Select Boot.tar file in BL
Select Recovery.tar file in AP
Flash.
Unplug phone.
Remove battery.
Put it back.
Hold Volume up (+) then Home then Power button for 20-30seconds
Press Power button.
Press power button again.
You'll see TWRP recovery 3.1.1 , say thanks to GhaithSYR
Swipe to modify system.
Format data, Type yes (Beware it'll erase all data and factory reset except SD card.
Flash Kernel.
Reboot.
Update Magisk.
You can update your TWRP to 3.2.1 : https://forum.xda-developers.com/ga...-exynos-7870/stable-twrp-3-2-1-j701f-t3742401
Credits:
@GhaithSYR for TWRP
@JaskaranSM and @@ananjaser1211 for Helios Kernel
@topjonhuw For Magisk
@lzzy12 for TWRP 3.2.1 Image
Also hit Thanks to respective threads linked above.
PM for Queries. Bit busy so posting it short, will update Detailed guide soon.
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
RECOVERING:
If you mess up and device is not working there is very easy way to get stock rom back. No need to panic at all.
Go to Sammobile.com get your Stock Rom.
Flash via Odin.
Done.
Click to expand...
Click to collapse
I have a Samsung J7 CORE sm-j701f and on Pie version
my problem is after flashing twrp via odin "only official binaries are allowed to be flashed(recovery)" pop up in download mode.
my phone is OEM unlocked and can u help me fix this?, I cant root my phone if i cant fix this thing. Help will be appreciated, thank you.
Anlle said:
I have a Samsung J7 CORE sm-j701f and on Pie version
my problem is after flashing twrp via odin "only official binaries are allowed to be flashed(recovery)" pop up in download mode.
my phone is OEM unlocked and can u help me fix this?, I cant root my phone if i cant fix this thing. Help will be appreciated, thank you.
Click to expand...
Click to collapse
It means phone is not OEM unlocked flash older firmware and check. It's been long i rooted this phone, currently not using it I don't remember exactly what I did to get rid of this msg - unofficial binary.
But i remember changing date back to few months and enabling allow OEM unlock.
There is another guide of rooting including a tool phoenix something. Search Xda it exits here. All I can say is keep fighting i tried a lot time and at the end it worked, I even used custom kernel Helios and rooted properly with magisk.
xperia ray said:
It means phone is not OEM unlocked flash older firmware and check. It's been long i rooted this phone, currently not using it I don't remember exactly what I did to get rid of this msg - unofficial binary.
But i remember changing date back to few months and enabling allow OEM unlock.
There is another guide of rooting including a tool phoenix something. Search Xda it exits here. All I can say is keep fighting i tried a lot time and at the end it worked, I even used custom kernel Helios and rooted properly with magisk.
Click to expand...
Click to collapse
Thank you, I will try until my phone is rooted. best of luck of me hehehe.
Anlle said:
Thank you, I will try until my phone is rooted. best of luck of me hehehe.
Click to expand...
Click to collapse
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/gal...j7nxt-t3974337
xperia ray said:
NOTE:
for OEM Unlock option enabled ( I used miraclebox EE activation, but not sure it got it on with it or it was by default, See reference guide)
Reference Guide, credits @Jukmisael : https://forum.xda-developers.com/ga...e-nxt-exynos-7870/install-twrp-j7nxt-t3974337
Click to expand...
Click to collapse
Thanks
According to the photos shown, you need to use MiracleBox, as it is prenormal
Try using this tutorial
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
You don’t unzip the .tar files. Keep them as is.
secretwolf98 said:
You don’t unzip the .tar files. Keep them as is.
Click to expand...
Click to collapse
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
fountainb234 said:
I don't get a .tar file until I unzip the folder; I get a filed with .tar.md5
Click to expand...
Click to collapse
Just rename the file cutting off the .md5.
is it possible to downgrade from sk5 to sk1? you cannot upgrade to a later version, and I know downgrading can have reverse effects on the tablet. I have same tablet I would like to know. if I flash sk1 is there a way to fix it if it bricks?
Magendanz said:
My recommendation would be to first upgrade to T510XXS2ASK1 of the OEM firmware, since that's the latest version for which Samsung has published kernel source. Use the latest release of Odin and install BL, AP and HOME_CSC. After this, unlock the bootloader and prevent VaultKeeper from relocking it by always enabling Debugger Options while connected to the Internet after a factory wipe.
From there, you could just install TWRP, install the latest MultiDisabler, and live with the Samsung firmware. You could even install Magisk to root. However, I prefer a clean Google OS without all the OEM bloatware, so I'd recommend installing the latest Nexus Stock (which includes TWRP and the custom kernel that disables Knox boot security features). Again, use Odin and install it to AP and do a factory wipe in TWRP because file-based encryption is still unsupported on these custom ROMs.
You could install LineageOS instead, but I haven't yet updated that for T510XXS2ASK1. I've just been busy and Andy hasn't been releasing any new LineageOS 16 GSIs. We're also pretty close to releasing a LineageOS 17 build.
Click to expand...
Click to collapse
fountainb234 said:
Hey guys, this is my first post. I just bought a Samsung SM-T510 and would like to unlock all the features. I'm currently trying to follow multiple guides on how to do so. To my understanding, my best bet is lineageOs 16. I've been following https://forum.xda-developers.com/gal...-16-0-t3987317 alongside with https://forum.xda-developers.com/gal...howto-t3989361 and I'm pretty confused on the method order i need to follow. What I mean is do I install rom first, TWRP, Magisk etc.?
More guides ive been following:
https://forum.xda-developers.com/gal...-10-1-t3934805
https://forum.xda-developers.com/app...mless-t3473445
https://topjohnwu.github.io/Magisk/i...system-as-root
I see posts saying I need and don't need Multidisabler so I'm confused on what I actually need: https://forum.xda-developers.com/gal...ption-t3963020
Another one: https://forum.xda-developers.com/gal...ption-t3919714
https://forum.xda-developers.com/gal...eries-t3918699
I have so many tabs open currently; I know I'm missing a few important ones.
So given all that info, i think i have all the software to do this between kernels, rom, twrp, odin, magisk, multi disabler? and i think thats all.
My sm-t510 build number is T510XXU2ASK5, looking through the lineage rom guide, I click the link https://samfrew.com/model/SM-T510/ and i see different versions. I'm honestly completely confused about this file and how I'm going to use it. I understand it to be the stock rom? as in factory software? With TWRP too, the numbers don't match my current build number leaving me very confused.
Do I need to downgrade my build number (i don't know if it's even a thing just asking)?
I think i can do everything relatively easy once I have an understanding of what to do first (order of things) and the specific files for the specific steps. When I'm reading these guides, I honestly have no idea which download goes for what. For ex. going back to https://forum.xda-developers.com/gal...-16-0-t3987317 like what do I need to download, the build number listed in notes regarding kernel or go to the download section right below and use that? Or both and if both, how do I use them separately for there a specific purpose? I cannot find anything that makes me feel comfortable rooting/custom rom on my device. Not comfortable in terms of I don't know what I'm doing exactly. I have put days of reading into this and still, I cannot figure out how to do this. I would really appreciate it if someone could help me. This is stressing me out and I would like to get this done before Monday due to me having some serious surgery. The reason being; I won't be as fresh on everything I've read recently.
I'm sorry if this post is choppy and all over the place. I'm just exhausted and clueless at this point. If I left any info out in order for someone to help me please let me know so I can provide it.
EDIT: The TWRP file ends in build number SK1, the file lineage-16.0-20191019-UNOFFICIAL-T510XXU2ASI4.tar.md5 doesn't match the TWRP file as well as my current build number; which ends in SK5. So nothing is matching the 3 last characters in my build number across all guides besides the samfrew link.
Also, I keep seeing i need a .tar TWRP file for recovery (?) but when I unzip both files are .img (named boot/recovery)
Click to expand...
Click to collapse
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
framC0 said:
without reading answers i can say that im with YOU! Im almost 3 days to root my T510! We must RAMDISK YES in Magisk but to do that we need to extract recovery.img (https://www.droidwin.com/install-magisk-in-recovery-root-android/) from stock original ROM T510OXM5CUJ1 and Im stucked at the part NORAMDISK trying to patch recovery.img with Magisk Manager (with recovery mode checked) but i only get the "waiting for device in ADB" and I conect disconect USB C and nothing...Still NO RAMDISK...
I used 3 different ROMS but no lucky and tried with firmware CUJ1 but no lucky again. Without "NORAMDISK: YES" no root...stucked. But i saw a T510 with OrangeFOX!
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
framC0 said:
Wow i will try this today and will post feedback. Are you on Android 11? Thank You!
UPDATE: So...flashed with T510XXU5CUL1...
From OEM stock firmware:
Unlock bootloader -> done
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin --> twrp-3.6.0_11-2-T510XXU5CUL1-20220218.tar ---> this put the tablet into emergency mode... had to do again "Hold Vol Up & Vol Down buttons during restart to enter Download mode" and reflash it again. stucked at this point. cant flash TWRP with that! Maybe this TWRP file its for Android 11.2 and im on 11?
Click to expand...
Click to collapse
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
lewmur said:
You don't need to flash TWRP if you flash https://forum.xda-developers.com/t/...k-for-2019-galaxy-tab-a-10-1-sm-t510.4234889/ TWRP is built into this ROM. After installing stock CUL1, did you boot it, connect to wifi, skip the rest of setup and then enable Dev mode before rebooting to download and flashing from Odin?
edit: Don't attempt to download from the regular download link. Use the link under Build archives that says Android File Host and scroll down till you find the CUL1 md5 file.
Click to expand...
Click to collapse
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
EDIT: i dont have OEM unlock option in DEV but its unlocked, i checked when in downloaded mode it says "lock device and..." so its unlocked.
framC0 said:
AH! So donwloaded Nexus_Stock_CR_T510XXU5CUL1-20220219.tar and put into AP in Odin... and FAIL. Error: "Only official released binaries are allowed". Before i flashed with T510XXU5CUL1 didnt conect wifi and enabled usb debug.
Click to expand...
Click to collapse
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
lewmur said:
You must connect wifi and enable Dev mode before flashing. If, after flashing CUL1, you went through the regular setup routine and put in a Google Account, you must also enable OEM in Dev options.
Click to expand...
Click to collapse
YES!!!!!! YOU ARE THE BEST!!!! Done! It booted directly to TWRP!!! THANK YOU!!!! So now will flash Magisk with twrp right? Alawys rooted my devices but this 510 wow...never saw a thing like this
Edit: The fight continues - So i did wipe and format data in TWRP and reboot system and im IN. Installed Magisk 23.0.apk and noticed that im still with "RAMDISK: no"... Searching how to do next to root! Im very near of the goal!!!! Finally! Big thanks to lewmur!
lewmur said:
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file. You can flash the Nexus ROM without first flashing anything else but the latest CUL1 (not CUJ1) stock ROM. Nexus includes both TWRP and gapps. The only time you have to patch things to get Magisk installed is when you are trying to root a stock ROM instead of a custom ROM. Custom ROMs always to the patching for you.
Click to expand...
Click to collapse
I just finished flashing the latest Nexus ROM and rooted it with Magisk merely by flashing the Magisk zip file.
Click to expand...
Click to collapse
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
EDIT: Since an older version dont know witch, Magisk Manager and Magisk are joined in apk so i just flashed Magisk 23.0.apk in TWRP...rooted!!! DONE!!!! FINALLY
framC0 said:
Sorry just one more question im very near. I will flash this Magisk (magisk_patched-24300_tkk90.img) in TWRP or Odin? And is this file from https://forum.xda-developers.com/t/...019-galaxy-tab-a-10-1-sm-t510.4234889/page-18 ?
My brain will explode few days in a row to get it rooted
Click to expand...
Click to collapse
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
lewmur said:
Download latest Magisk from https://magiskapp.com/zip/ and flash with TWRP.
Click to expand...
Click to collapse
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
framC0 said:
Thank you!! Im facing a problem when connect USB to PC...sometime tablet restarts and sometimes dont appear on PC even in device manager. Did you got this also? Not very important because i will access via FTP. Just to learn...thanks!
Click to expand...
Click to collapse
USB cables are notorious for being flaky. Sometimes it helps to just turn the cable over and plug it back in. I always keep several on hand so that if I have connection problems I can try another cable.