yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab S2 Android Development] busdonic:
---------- Post added at 03:17 PM ---------- Previous post was at 03:14 PM ----------

[/COLOR]

Hi ashyx, I honestly don't remember, as it was some time ago, but I'm up to try the patch again. Thanks for the hint.
[Galaxy Tab S2 Android Development] ivanox1972:
or tell me here what to do. I like that idea to flash without efs and get imei 0. Maybe can be restored later...

Thanks in advance, i we unbrick it , it is dream scenario [MENTION=4899305]ashyx[/MENTION]
[Galaxy Tab S2 Android Development] ashyx:
Did you try any of the above?
[Galaxy Tab S2 Android Development] ivanox1972:
Not yet, I wait your suggestion. I'm a little afraid. To not brick totally
[Galaxy Tab S2 Android Development] ashyx:
Non of what I've suggested could brick your device.
[Galaxy Tab S2 Android Development] ivanox1972:
Ok. So please, give me some schedule hiw to proceed.

Thanks
[Galaxy Tab S2 Android Development] ashyx:
Back up your Efs partition to sd card first with twrp. Then delete the EFS folder. Format your Data partition using the FORMAT DATA button.

Reboot and wait 10 mins at least.
[Galaxy Tab S2 Android Development] ivanox1972:
On which rom with which twrp?

Sorry if stupid question.
[Galaxy Tab S2 Android Development] ashyx:
TWRP here and stock firmware.
[Galaxy Tab S2 Android Development] ivanox1972:
So ok, 819 twrp and system.ing only? Or some other partitions?
[Galaxy Tab S2 Android Development] ashyx:
After doing the procedure above just flash the whole stock firmware with odin.
[Galaxy Tab S2 Android Development] ivanox1972:
So. Now I am on t813 twrp and t813 lineage... BL is 819 but it can't boot

1. Install twrp 819

2. Install system. img of stock 819 extracted?

3.?

4.?

Please, give me steps...

Thanks for help, should I need to say that, but it is unclear...
[Galaxy Tab S2 Android Development] ashyx:
Flash the WHOLE stock firmware with ODIN. Why are you flashing half baked custom roms? :eek:
[Galaxy Tab S2 Android Development] ivanox1972:
But, remember, my problem is that odin stock can't go....

Look my first post
[Galaxy Tab S2 Android Development] RagingHarry:
So I guess this was you first post after that you soft bricked your device?

I've seen you talking about efs troubles and ashyx directed you what to do incase of efs.

I've used one more drastic option to restore my device, but my problem didn't include efs, but for me the last option was using a pit file in Odin to reformat the whole device and set it up pure clean, in that process you risk a lot, but the T819 gets reset to full stock with clean partitions.

The risk that remains is what will it do for efs, that I can't tell you (efs where the first backups I made when I got this samsmuck device) as ashyx thinks/says they should rebuild but uncertain about the result after rebuilding and the imei.

If you want to go drastic and risky pm me.

If the quote wasn't the 1st post, please provide an url to it.
[Galaxy Tab S2 Android Development] ashyx:
Yes, but you haven't followed the instructions I gave you BEFORE installing the stock firmware.

Also as [MENTION=4427484]RagingHarry[/MENTION] stated, you could try repartitionung the device with the PIT file.
[Galaxy Tab S2 Android Development] RagingHarry:
But the latter isn't without risk ;)
[Galaxy Tab S2 Android Development] ashyx:
Minimal on an already non booting device.
[Galaxy Tab S2 Android Development] RagingHarry:
As long as he can enter to the bootloader....

There is much that can be fixed without fastboot as long you have a proper pit file ;)

Has been like that as I met my Galaxy S1, samsmuck is hard to fully brick, but they make it harder to do emergency resets with their own software, forgot the names that fast but on the latest I discovered that the emergency recovery is stripped out.

That is also when I really needed to search for the pit, used it several times since then, still can't refuse to experiment, and sometimes you need to run drastic matter (within Dutch warrenty that allows root and other stuff, and needed to take that) chance to get it back or fully brick.

As my signature says ORD
[Galaxy Tab S2 Android Development] KarlDroid:
Hi, I'm not a complete noob but I am stuck (the phone won't boot).

I have sm-t719.

Boots to recovery and boots to download mode. No problems.

I have tried flashing lightning ROM 6.0.1 which in TWRP says it's successful, but it doens't boot the image (even after leaving it for 30 minutes).

I have tried flashing back to stock using ODIN 3.10.7 but it failed. Also when I try making a back up in TWRP it also fails and does auto reboot.

SELINUX is permissive, FRP is 0. The kernel is showing charge light which means kernel is implemented within image?

The boot patcher works but I am not 100% sure how to implement successful.

Is there something in the dependency tree that needs to be corrected?

I also have a stock sm-t719 that is currently working fine. Any way to make full image (nandroid backup) and flash that through TWRP? would that work?

I have tried to make a backup in TWRP but it always fails.

I have tried full wipe, all partitions, and reformatted system even tried changing the file partition format (cache, internal storage, data etc).

Any thoughts?

I need to install either stock 6.0.1 or custom lineage 6.0.1 for this device (LTE version) because the app I need to run only works in SDK 23. I will consider a chroot container in the future but I need this fixed!
[Galaxy Tab S2 Android Development] jhill110:
Yes, if both devices are the same you can restore a backup from the one that works to the other.

Are you sure the TAR file you are flashing is not corrupt?

Here's what I'd do...

I would try the nandroid backup first after formating data and wiping the other partitions. Forget about the patch and rooting and permissive kernel. Just try to get the device to boot first.

If that doesn't work...

Next I'd try downloading the tar again and check the md5. I use Odin 3.12.3. If that doesn't work the egg heads around here may offer (better?) other advice.

Good luck.

P. S.

What is it you did just before this started?
[Galaxy Tab S2 Android Development] KarlDroid:
Hi, Thank you for the tip. I have downloaded stock from sam mobile 6.0.1 and will try to flash in odin when I have some more charge in the battery.

The phone was given to me in this state. I was told that the phone had Nougat originally upgraded OTA and then was attempted to downgrade but the flashing was wrong ROM, and it wouldn't boot fully.

I just did TWRP and then tried to Flash custom 6.0.1 Lightning ROM and was told the partition was encrypted so did full wipe etc and now here I am.

I did think that maybe the Lightning ROM was corrupt but I downloaded twice to the same result. Funnily after the flash it sometimes said boot no OS installed!

I Dunno haha.

---------- Post added at 06:23 AM ---------- Previous post was at 05:25 AM ----------

Update:

Downloaded stock 6.0.1 from Sammobile. MD5 check seems OK.

Download mode (added) Unzipped the md5 tar file, in AP (Odin v3.10.7 selected tar).

Start = SW REV Check Fail : [aboot] Fused 2 > Binary 1

Am I using wrong Odin or wrong Firmware? FRP Lock = OFF

I am stumped.

---------- Post added at 06:54 AM ---------- Previous post was at 06:23 AM ----------

OKay:

So I am no longer a N00B but, you see I didn't know that the bootloader upgrades OTA and that to downgrade is a significant chore with Samsung, unless custom ROM and SU root is installed, that said, I am hoping the Nougat ROM will flash in ODIN. I am not too hopeful alas, given the amount of hours I spent on this project.

Will update because I think it is of semi use. :)
[Galaxy Tab S2 Android Development] ashyx:
All you need to do is install the correct firmware. You're attempting to downgrade the bootloader to revision 1. Not possible.

Download a revision 2 firmware and it should install just fine.
[Galaxy Tab S2 Android Development] jhill110:
Start = SW REV Check Fail : [aboot] Fused 2 > Binary 1

Means you're trying to flash a version with an older bootloader

It's possible on some Samsung devices to flash an older bootloader but you'd have to find someone with the skills to extract the older and make a flashable file. I have used this method for moving back and forth from lollipop to marshmallow roms so I know it works.

You'll either have to flash the latest rom or find somebody.

Here's a thread by Freeza with bootloaders for this purpose although for a different device. You could ask him if it's feasible for this device.

If you want to talk about this anymore with me take it to PM. We're hijacking this thread. ?
[Galaxy Tab S2 Android Development] ashyx:
Nope. Not possible to downgrade a revision 2 bootloader to revision 1.

Only way to downgrade from one OS to another is if the firmware revision is the same or higher or just flash the AP part without the bootloader.
[Galaxy Tab S2 Android Development] KarlDroid:
Update (Last one) Sorry for all the nonsense.

Successfully flashed in ODIN stock ROM. Booted the kernel and went into Stock Recovery and sailed 'no command' reflashed TWRP cleared cache and davlik rebooted (left it for 30 minutes = Samsung OS screen but no OS)

Booted TWRP again clear cache davlik = same result.

Tried wipe internal storage, data etc = cannot mount (/data no such device) unable to mount storage.

Factory reset (remove encryption) reflashed Stock ROM completed in ODIN = same result.

I am wondering in ODIN do I need to specify partition, or maybe do I need the bin file? I am only flashing in AP.

Maybe the device has a hardware issue?

Sorry for hogging the thread! Demoted to N00B again.
[Galaxy Tab S2 Android Development] shev100:
Hello ashyx and everyone. I have same problem. I followed all step in the op but my data partition still unmantable. First of all i flashed twrp for my t819. Then i boot tablet into it and tried to wipe data, but twrp gave me the data's error (it's not mounted). I tried go on and i the tab stuck on boot and i can't reboot it. It reboot when it completly discharge. I tried to refollow all steps, but data's partition still unmountable so i stop the work. I only need to root the tablet. I also tried whit cfautoroot whit different configuration, but there is a problem whit memory so i must restore it. Is there a solution? Thanks in advance who help me
[Galaxy Tab S2 Android Development] RagingHarry:
Wipe data? Or the format data button?

Cause only the last is good! .

Did you try to boot to bootloader and then recovery?
[Galaxy Tab S2 Android Development] IronW:
Following these instructions I was able to root my Tab S2 (T813). I flashed twrp with Odin and was able to boot into twrp recovery. I formatted data but couldn't mount /data. I had to wipe data and them format data again which made / data mountable.

Then I realized I had used another device to download the su and boot image patch, oops. Fortunately I was able to adb push those files to /sdcard and was able to flash them. Reboot took a few minutes but everything worked well.
[Galaxy Tab S2 Android Development] shev100:
Wow what a stupid mistake I've done! The problem was that I wiped data, not format. So there's differences between one and the other, right?

But now I solved my problem and the tab works great with root. Thanks a lot for your help!
[Galaxy Tab S2 Android Development] RagingHarry:
Wipe only removes files from Data, format formats the intire UserData partition which also includes internal storage and that's what is needed to remove the encryption and being able to mount data.
[Galaxy Tab S2 Android Development] ashyx:
I wouldn't mind but it clearly states BUTTON and its not as if you can miss it. :rolleyes:
[Galaxy Tab S2 Android Development] RagingHarry:
As I said in the post before that one... Just missed the word button in the last one
[Galaxy Tab S2 Android Development] ashyx:
Yeah thanks for pointing it out as I'm getting fed up of doing it.

You be amazed how many times someone has posted that they couldn't mount data after 'wiping' the data partition in my TWRP threads.

Honestly it's unreal. :eek:
[Galaxy Tab S2 Android Development] RagingHarry:
Lol I know, have been following this thread long enough to see it passing by quite often ;)
[Galaxy Tab S2 Android Development] rkk89:
I was thinking that if system was gone, I would not be able to boot the system with the recovered bootloader. But actually I did a factory reset after recovering the android bootloader.

I'm waiting for the system to boot... (this time I left the system partition in read only and I wiped data by means of the wipe->format data option).

---------- Post added at 01:28 PM ---------- Previous post was at 12:55 PM ----------

I waited 20 mins and it didn't boot. I noticed some errors while formatting data with twrp in read only mode. This time I'm formatting data with twrp not in read only mode.

So: started tablet in recovery mode, swiped to disable read only, swipe->format data, reboot system
[Galaxy Tab S2 Android Development] ashyx:
You're making things over complicated here.

I suggest you reflash stock, let it boot, reflash twrp, boot to recovery, leave system read only, format data(not wipe, wipe will not work) reboot.

That's all that should be required.

If you still get boot hangs then you may need to flash this with twrp.

https://idlekernel.com/fun-stuff-trust-me/no-verity-opt-encrypt.zip
[Galaxy Tab S2 Android Development] rkk89:
Ok, I followed your instruction and I'm again stuck on waiting for system to boot. When I formatted Data I got this: http://imgbox.com/IJ2q3Y8S

I'll try to get my hands on a sd card to be able to get the boot fix inside the tablet...
[Galaxy Tab S2 Android Development] madsquabbles:
That's what you'd normally get following instructions. Reboot recovery only if you can't access the data partition. The only reason to access the data partition is to be able to flash SU. After you reboot system it's gonna encrypt again after set up.

If you can't boot, you may have wiped something you shouldn't have. Grab the stock image and start from scratch.
[Galaxy Tab S2 Android Development] rkk89:
I tried but the tablet is not able to boot :(.
[Galaxy Tab S2 Android Development] ashyx:
You can ignore the red warnings. They are only there because of the encrypted data partition. They will disappear after formatting DATA.

Also the data partition shouldn't re-encrypt as there is no ForceEncrypt flag in the ram disk.

There is dm-verity which is probably why you are having boot issues.

However supersu should patch both.

As I've already stated you do NOT need to format the DATA partition to install supersu.

Get yourself back booting normally again with the stock rom.

Install and boot to twrp. Leave system as read only.

Format the DATA partition then reboot to twrp.

You should now be able to mount data without error.

Copy supersu to your device and install supersu.

Reboot system.
[Galaxy Tab S2 Android Development] madsquabbles:
Is it not supposed to re-encrypt after set up? Mine's done it a couple times as I wanted to test to make sure that it's supposed to happen - I've wiped, formatted and set up three times just to verify that I didn't skip something. Right at the end of set up you get that knox is gonna secure your stuff message. I honestly haven't checked after my last wipe so it may be de-crypted still.
[Galaxy Tab S2 Android Development] ashyx:
Nope shouldn't re-encrypt. No encrypt flag in ramdisk.

I have modified the boot images to remove dm-verity.

Flash with Odin or extract the boot.img and flash with TWRP.

sm-t713_boot_no_verity

sm-t813_boot_no_verity

.
[Galaxy Tab S2 Android Development] rkk89:
I tried that two times, one of them with one of my friend watching me doing it and I still get stuck on the Samsung loading screen. No error appears installing super su. I left the tablet loading for at least an hour. Now I just flashed the other patch you gave me and I'm leaving the tablet loading... I guess I'll leave it there until an autoroot file come out.

Still thanks for your help.
[Galaxy Tab S2 Android Development] madsquabbles:
You could probably do what we've both already said and return to stock....

---------- Post added at 06:30 PM ---------- Previous post was at 06:27 PM ----------

Seems checking on encryption isn't as easy as a Nexus device. I'll have to find how to check if my storage is encrypted later or tomorrow. I do know that twrpl can't access data right now so assumption is that Knox encrypted it after set up. The last message after setting up says Knox is securing your data.
[Galaxy Tab S2 Android Development] Khazaam:
Long Reboot After Root

Hi and thanks for your work on this. I know the first reboot after root and data wipe takes a little while, but my T713 is taking forever.

I've followed everything (I think) perfectly. I am able to get TWRP installed fine and SU installed fine as well.

I did the data wipe and upon reboot, the tablet sits at the flashing logo and never makes it past.

It's running 6.0.1 if that makes a difference.

Am I missing something or am I impatient? :)

Thanks again.
[Galaxy Tab S2 Android Development] ashyx:
Why do you assume that cf-autoroot is any different to flashing supersu with twrp?

They do EXACTLY the same thing. One uses its own recovery, one uses twrp.

They BOTH flash exactly the same files.

If all you want is root then leave the data partition alone. Just keep system read only and flash supersu.

For anyone else having issues. Read post #50.
[Galaxy Tab S2 Android Development] rkk89:
The difference is that with autoroot I cannot mess up :).

I think I've already tried to flash supersu without formatting data (I assume that by flashing you mean to first install twrp with odin and then to install supersu by means of the install command inside twrp) with no availl (It gave me some errors), but tomorrow I'll try again just to be sure.

Also I do am able to recover the tablet but at the moment it is of no use to me without root priviledges. For that I already got a different tab 2 model and succesfully rooted that with autoroot.

---------- Post added at 01:15 AM ---------- Previous post was at 01:11 AM ----------

I think you and I got the same exact problem. I'm trying with the supersu solution tomorrow. Let me know if you discover something.
[Galaxy Tab S2 Android Development] djgade:
For God's sake I didn't format data until now. When I read about this, I think I will wait a bit. Glad that root and xposed is working fine.

I am not so satisfied with the kernel, scrolling in Facebook and Instagram gives some FPS lack. My S6Edge+ does this job very well. But it's getting of topic :)

Gesendet von meinem SM-T813 mit Tapatalk
[Galaxy Tab S2 Android Development] ashyx:
The errors are not related to flashing supersu.

As I've already previously stated ignore the red warnings they are related to encryption and mounting the data partition.
[Galaxy Tab S2 Android Development] ashyx:
Is anyone able to mount the DATA partition in TWRP after formatting?

Also can somone post the recovery log AFTER formatting DATA and rebooting to TWRP.
[Galaxy Tab S2 Android Development] madsquabbles:
I've successfully mounted data after formatting. I even rebooting into recovery after formatting works. After set up is complete though it fails. I'll see if I can reformat and reboot into recovery and interrupt set up at different points to see what happens.

Took a few logs at different stages:

1- after flashing your new boot image

2- after formatting data

3- after formatting data and reboot recovery

4- after above step but flashing SU

5- after above steps and rebooting system

at the system reboot I get the samsung logo and then it auto reboots after about a minute. at the reboot I quickly put in back into recovery and found that access to /data was gone (this is in log 5).

I may be available for some more testing today based on how busy we are at work. Sucks having to set up my tablet again, but I supposed that's a lot easier than what you're doing ;)

I've flashed SU and TWRP a few times in the last couple days and found it booted pretty quickly. I don't think I've had to wait more than 5 minutes each time (not a exact measurement as I really wasn't watching the time, but it didn't take long at all).
[Galaxy Tab S2 Android Development] ashyx:
Thanks I'll take a look at those. I will be working late tonight though so may not get chance tonight.
[Galaxy Tab S2 Android Development] rkk89:
Thank you, I want to confirm that flashing only super su works fine.

Thanks for all your help!
[Galaxy Tab S2 Android Development] ashyx:
Have investigated this further.

It seems the encryption is being forced in the init.rc. There are many flags and a service which checks if the device is unencrypted and if it is to force encryption.

I have made a couple of modifications. I'm not sure which one will work or if any will work.

These must be flashed with odin or extracted and flashed with twrp.

Flash this one first then immediately FORMAT(not wipe) the data partition and reboot to recovery.

Check whether data can be mounted then try and reboot to system.

sm-t813_no_encryptable_boot

If the one above doesn't work try this one and follow the same instructions as above.

sm-t813_no_init_boot

.
[Galaxy Tab S2 Android Development] BonnyZou:
I have a SM-T713 device.

I've succeed installing the recovery,and format data. But when I connect the device via USB cable with my PC(MTP is enabled), nothing shows up.

So if I need to paste some files that needs to be flash then I had to boot the device, thus encrypted it again.

How to solve this? Didn't got any available SD to use.

Sorry for my poor English. Thanks for your help!
[Galaxy Tab S2 Android Development] ashyx:
Please see the OP for fixing encryption issues.

MTP is working. If MTP is enabled ensure that you have the MTP driver available in device manager when booted to TWRP.

Also in TWRP try disabling MTP then immediately quickly reenable MTP.
[Galaxy Tab S2 Android Development] George M:
I have a problem with twrp that is keeping me from trying any new roms.

My device is:

Tab S2

SM-T813

Currently on 6.0.1

Kernel 3.10.84-7973188

Build number is T813XXU1APF4.stock.odexed.by.pvsgh

I have tried to install the newest TWRP but when I try to go into recovery I just get a black screen with some light flashing across the screen. I cannot get out of it or shut the tablet down. I have to go into download mode to then that allows me to boot into the system again.

I have installed from the TWRP app and also via Odin - same result.

So for my sanity can someone confirm exactly what the TWRP file I should be using? I have been trying this one;

twrp_3.1.0-1_sm_T813_1417 and 1417n.

Thanks for any help

George
[Galaxy Tab S2 Android Development] ashyx:
Maybe try the earlier builds?

Also which bootloader version do you have installed?
[Galaxy Tab S2 Android Development] George M:
Your quite right. It has been a couple of years since I've done anything with the tablet. I am trying to relearn it.

The problem I was having was not with the file I mentioned but with the TWRP 3.2 version. Now I know that is because I need to intstall the 7.0 (Nougat?) rom first - At least I think that is what I need to do.

So can you tell me if this is the process I need to do:

I have TWRP 3.1.0.1 Installed.

I did a backup.

Install stock 7.0

Reroot if neccesary

Install TWRP 3.2

I can then install any of the 7.o custom roms.

Is that correct? And thank you for your time.

George
[Galaxy Tab S2 Android Development] Jaycob2016:
Hi- I have Galaxy Tab S2 SM-T713 Android version 6.01 rooted and I would like to update my Android version to 7.0. Could anyone help me go about doin it. Thank you so much.
[Galaxy Tab S2 Android Development] Jaycob2016:
Never mind, Awesome! I figured it out. Thanks.
[Galaxy Tab S2 Android Development] KarlDroid:
Revision 2 Firmware

Hi all,

Would someone you please (if you are not too busy!!), send a link for a revision 2 firmware for the SM-T719 running android 6.0.1 I don't care about the region?

I am stuck with a revision 2 bootlader on Nougat, and I want to roll back to MM.

Or is there is there anyone who knows the procedure (or a link), for the S2 device, to flash MM Stock ROM without the bootloader that will enable a rollback?

Help me...