I need help please, because I can't get my new prestigio 4500T turn on.
I first did the CWM recovery in this site, androidforum.cz/pro-pap4500t-dc-1-2ghz-s-jb-4-1-1-t38976.html
and it was all ok.
But then I wanted to remove the CWM recovery of my phone, because I had some problem updating my phone to the new rom because of it,
and I went to the same program I installed CWM recovery, Smart Phone Flash Tool, and I put the same scatter file I used to install, and instead of clicking on download I clicked Format, and then format whole flash, because it was there that I would take CWM recovery of my phone.
Now I can't turn my phone on, when I connect usb at pc, it connects and disconnects a lot of times. I even tried to do the same steps to download the CWM recovery on my phone but in SP Flash Tool I get this error: BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL (5054)
[HINT]: Please check your load matches to your target which is to be downloaded.
I don't know what to do and please Help me. Thanks
Nobody answers? Please can anybody help me?
ddqgarces said:
I need help please, because I can't get my new prestigio 4500T turn on.
I first did the CWM recovery in this site, androidforum.cz/pro-pap4500t-dc-1-2ghz-s-jb-4-1-1-t38976.html
and it was all ok.
But then I wanted to remove the CWM recovery of my phone, because I had some problem updating my phone to the new rom because of it,
and I went to the same program I installed CWM recovery, Smart Phone Flash Tool, and I put the same scatter file I used to install, and instead of clicking on download I clicked Format, and then format whole flash, because it was there that I would take CWM recovery of my phone.
Now I can't turn my phone on, when I connect usb at pc, it connects and disconnects a lot of times. I even tried to do the same steps to download the CWM recovery on my phone but in SP Flash Tool I get this error: BROM ERROR: S_DL_GET_DRAM_SETTING_FAIL (5054)
[HINT]: Please check your load matches to your target which is to be downloaded.
I don't know what to do and please Help me. Thanks
Click to expand...
Click to collapse
You messed up boot file.Try to find original boot.img here on XDA and try to flash it via PC,or find original stock rom for flashing via SPFlashTool try that
jaskooo said:
You messed up boot file.Try to find original boot.img here on XDA and try to flash it via PC,or find original stock rom for flashing via SPFlashTool try that
Click to expand...
Click to collapse
Thanks for your help, I have a boot.img of the stock rom, I put in the same folder of MT6577_Android_scatter_emmc and CheckSum.ini , but when I try to download via SP flash tool I get this error:
Image Bootimg checksum failed! Checksum reference value (0x5583) in the config.ini file.
Please re-fill correct checksum values in checksum.ini.
I don't know what are the checksum values, can you tell me where i can find these values?
I am getting this DRAM error, because I don't have the correct files to flash in SP flash tool.
Please can you give me all those files needed to put a whole new firmware in y phone, I need the preloader file, and etc.
My phone can't detect preloader, as it did, and I can't boot it, it's like dead, only appears a red light when I connect to pc and a MTk USB Port (COM).
Please help me with the files needed to flash my whole phone in sp flash tool
Need full ROM with scatter file
Hi Guys, I am looking for full ROM including scatter file for PAP4500T. I need it to load all needed (Preloader, MBR, EBR1, UBOOT, BOOTIMG, RECOVERY, SEC_RO, LOGO, EBR2, ANDROID, CACHE, USRDATA) in to the SP Flash Tool. It can be from Stock or any working ROM. If You could provide me Working ROM with all these and with scatter file which will load everithink to the SPflashTool I would really appreciate that.
Thank You in advance.
The phone does not boot - just shows "an error has occurred while updating the device software" screen.
I got this issue due to unsuccesful flashing DOH6 firmware via Odin
"Download mode" is available, "Recovery mode" is not
I triyed to flash firmware again, but, unfortunately, have no success.
When it boot in "download mode" it shows:
"ODIN MODE
PRODUCT NAME: SM-G925T
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FRP LOCK: OFF
Secure Download: Enabled
KNOX WARRANTY VOID: 1 (0x0304)
RP SWREV: B:2 K:2 S:2"
It can only go to download mode when charger or pc is plugged in. Boot loop also only accures when plugged in otherwise no sign of life.
I have tried reflash FW several times with this result:
{
"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"
}
Then tried this method:
originally Posted by samanbabah
Ok everyone. here is the fix for those stuck at Samsung logo after 5.1.1 update thanks to this person "Tuandung.tran". I had to go to a Vietnamese site and download the file that took me 7 hours to download, I had a hard time translating the site since it was in Vietnamese, so now I want to contribute and help others by saving them time with straight forward tutorial on how to fix the problem that they have.
Ok so here it is:
1) download this file and extract it to your PC ==========> https://mega.nz/#!vIEEBQyT!U5AzPE4iR...__4qiFTfkBupp0
2) go to recovery and delete system files and cache
3) go to download mode
4) open Odin on your PC and click AP to add AP_G925TUVU2COF6.tar that you extracted earlier to your PC
5) with Odin still open add BL_G925TUVU2COF6.tar by clicking BL button
6) click start
7) After Odin is finished, it will reboot your phone. just wait a few minutes and you'll be all set.
Here is the result:
Don't know what the "CM" means at the beginning of the last line, it wasn't there before.
Then tried the same without boot img., it started to flash but during flashing system img. failed again.
Without BL and AP everything flashes nicely.
Flashed S6-UniBase_BOG8_v2.tar kernel with no problem, wich made the triangle with the text "an error has occurred while updating the device software" disappear and took me to the samsung powered by android logo, where it loops for several minutes, then goes black.
Flashed g925t_of6_aou_twrp_recovery_v13.tar, but, it gave me the red text "Recovery is not Seandroid Enforcing"
When i flash G925T_Stock_Recovery_ZiDroid.com.tar text disappears, but still can't go to recovery mode.
I still have hope since frp lock is off and there is at least download mode, the phone reacts, still, am kind of stuck here, no idea, how to proceed.
Any help will be greatly appreciated.
Tried this too, with no success:
originally posted by uniphase
If you continue to have boot up problems after flashing any type of newer stock firmware to your phone using Odin and Smart Switch, like I did, you will have to perform something similar to this fix and break up the files in the firmware tarball into the BL and AP tar.md5 files. I split the COF8 firmware from SamMobile and flashed the reconstructed tar.md5 files to the BL and AP sections in Odin, and it worked!
Procedure:
1. Download the latest stock firmware from SanMobile or another source.
2. Rename the filename extension from xxxxx.tar.md5 to xxxxx.tar and open the tar file with WinRAR, 7zip or another utility that can extract tar files.
3. You should see the extracted files below:
- boot.img
- cache.img
- cm.bin
- modem.bin
- recovery.img
- sboot.bin
- system.img
4. Download the attachment in this XDA thread and extract it somewhere.
5. Place the boot.img, system.img, sboot.bin, and cm.bin files in the bin folder, extracted from the attachment in the XDA thread in step 4.
6. Open notepad or another text editor and create this batch file in the same bin folder. Save the filename as convert.bat or whatever you filename you prefer with a .bat extension.
Code:
tar -H ustar -c sboot.bin cm.bin > BL.tar
md5sum -t BL.tar >> BL.tar
mv BL.tar BL.tar.md5
@ECHO off
timeout /t 3 /nobreak @ECHO on
tar -H ustar -c boot.img system.img > AP.tar
md5sum -t AP.tar >> AP.tar
mv AP.tar AP.tar.md5
7. Run the bat file and BL.tar.md5 and AP.tar.md5 will be subsequently created.
8. Open Odin on your PC and click AP to add AP.tar.md5 that was created in Step 7.
9. With Odin still open add BL.tar.md5 by clicking BL button.
10. Click Start.
The phone should be working after the reboot and get past the Samsung Galaxy S6 edge logo!
This method looked very promising, but flashing failed again, just like anything else i've tried so far.
I took the tar files apart and turned out that the two bin files stops flashing immediately, and the system image goes on flashing till a certain point, then flashing fails.
If i leave out these three files, everything goes fine, if any of them is present, flashing fails.
Also tried kies emergency recovery with serial number, but, it went on till 15%, then failed.
Any ideas?
Are you sure it says "RP SWREV: B:2 K:2 S:2" ?
And not "B:3" in there?
It almost sounds like you're on DOI1 firmware, and can't downgrade to DOH6. At least from what I've been seeing elsewhere. Based on all the symptoms, it really, really sounds like you're stuck on DOI1 firmware.
Considering you're pretty much dead-in-the-water at the moment, I might suggest you just download the DOI1 Odin and flash it. If you're not already locked into DOI1 (as mentioned, can't downgrade DOI1 -> older), then you will be after a successful flash/boot.
But hey, if that brings your device back, then so be it, right?
Good luck, friend. I'm still on OH6, so I can't really speak from experience on this one.
Aou said:
Are you sure it says "RP SWREV: B:2 K:2 S:2" ?
And not "B:3" in there?
It almost sounds like you're on DOI1 firmware, and can't downgrade to DOH6. At least from what I've been seeing elsewhere. Based on all the symptoms, it really, really sounds like you're stuck on DOI1 firmware.
Considering you're pretty much dead-in-the-water at the moment, I might suggest you just download the DOI1 Odin and flash it. If you're not already locked into DOI1 (as mentioned, can't downgrade DOI1 -> older), then you will be after a successful flash/boot.
But hey, if that brings your device back, then so be it, right?
Good luck, friend. I'm still on OH6, so I can't really speak from experience on this one.
Click to expand...
Click to collapse
Yea, you are right mate, it is B:3 indeed.
I'm downloading DOI1 as you suggested, gonna flash it and report back.
Really have nothing to loose with a $600 paperweight...
Thanks for your help, i keep up hope and report back soon!
This is probably the main cause of all the "stuck in animation logo" "bootloop" scenarios, downgrading.
Pp.
I have done everything possible to fix this phone. I was sure this was a excellent and sure fix. I pass ODIN ever time and yet still see a blinking logo.
That's Samsung's firmware protection in action, there just improving security on there phones so that stolen phone's can't be re-flashed and activated.
Pp.
pederzen said:
Yea, you are right mate, it is B:3 indeed.
I'm downloading DOI1 as you suggested, gonna flash it and report back.
Really have nothing to loose with a $600 paperweight...
Thanks for your help, i keep up hope and report back soon!
Click to expand...
Click to collapse
I have downloaded and flashed DOI1.
Unfortunately it is no success, though that funky little green line has never got as far as this time...
It also kooks like cm.bin, boot.img, and recovery.img flashes without problem.
It's very promising.
Attempt #1:
Attempt #2:
Attempt #3:
Sometimes process goes almost till the end. It always hangs while system image flashes.
Dodn't understand why it gets stuck at different points though.
After a few more attempts, i decided to try kies recovery again.
I left the PC on for night since the DL of FW is very slow.
It recognised that device needs DOI1 FW.
It failed again and still, leaved me with no recovery number to use for another attempt on another PC, what normally comes up when such a recovering procedure goes down with no success.
ODIN mode sais "Current binary: OFFICIAL" now.
What would be the next move?
Somebody wrote somewhere to install TWRP recovery, try to reboot into and flash a ROM from there.
Frankly, i'm getting out of ideas, i'm no expert in android or linux, at this point all i do is repeating the few methods that i have found so far, in different order wich, apparently gives me no luck.
Maybe some lower level process could wake my little black darling up from her deep sleep?
OMG!!!!View attachment 3502850
Now waiting to see if it boots up...
4 minutes have passed so far...
Well it seems like stuck on the powered by android screen.
26 minutes passed.
OK, flashed again, passed again and still, it is stuck on samsung screen.
This is great progress, i feel like only the last tiny piece is missing from the puzzle...
I wonder how long it can take the phone to boot after a FW reflash.
Anyways i leave it be for the time being, we'll see what happens.
An hour has passed, nothing happens.
Phone is warm feels like it's working on something or maybe only because of charging.
It doesn't seem like a bootloop since the samsung screen is continously on, it doesn't disappeare and come back.
It just stays.
Strange.
I had read in one the threads that one guy in similar kind if situation deleted the cache partition from the tar file, repacked and flashed and it booted up. According to him cache partition was preventing it from booting. May be worth a try..
Sent from my SM-G925T using Tapatalk
Alex9090 said:
I had read in one the threads that one guy in similar kind if situation deleted the cache partition from the tar file, repacked and flashed and it booted up. According to him cache partition was preventing it from booting. May be worth a try..
Sent from my SM-G925T using Tapatalk
Click to expand...
Click to collapse
Sounds like a plan
Give it a shut and report back soon.
Thanks for your help!
PanchoPlanet said:
That's Samsung's firmware protection in action, there just improving security on there phones so that stolen phone's can't be re-flashed and activated.
Pp.
Click to expand...
Click to collapse
Correct me if i'm wrong but if it was Samsung's firmware protection, FRP lock would be ON.
In my case it sais OFF.
Otherwise i agree with you these cases are 95% FW/downgrade related.
@pederzen, that's awesome that you've made progress, but I'm starting to question some things...
Are you sure you've got a good cable, and that it's well-connected to the device? To be sure, maybe snag a different cable, and don't touch it while flashing.
The fact that it's passing the md5 check suggests that the file did not get corrupted upon download, but I'm wonder if something is breaking it while it's flashing? How's your RAM/memory, are you overlocking or anything? Also, you might disable all antivirus/antispyware and disconnect from your network(s)/internet before even opening Odin.
Be sure you've got the correct version of Odin. Last I knew, v3.10.6 was working great for OH6.
Got drivers? Might double-check your device drivers for the device and such. A long shot on this one, because it's usually all-or-nothing.
Maybe just try a different computer if you can.
The fact that it's failing during system partition is the most disturbing thing. I'm doubting that your last "Pass" was actually successful.
@Aou
Tried two computers, several cables still the same.
When flshing hangs, a few seconds pass, unknown USB device sign comes up.
Went to samsung page, DL-ed, installed latest driver.
Now it sais in device manager:
'Device USB\VID_04E8&PID_685D\5&106f75ea&0&4 requires further installation.'
Whether it is connected in Odin mode or in normal mode when the screen with the triangle is on saying that installation went wrong...bla-bla
Checked events after driver installation, it sais:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-UserPnp" Guid="{96F4A050-7E31-453C-88BE-9634F4E02139}" />
<EventID>20001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>7005</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2015-10-12T11:05:28.095021600Z" />
<EventRecordID>7178</EventRecordID>
<Correlation />
<Execution ProcessID="5172" ThreadID="6744" />
<Channel>System</Channel>
<Computer>PUDVAS</Computer>
<Security UserID="S-1-5-18" />
</System>
- <UserData>
- <InstallDeviceID xmlns="http://manifests.microsoft.com/win/2004/08/windows/userpnp">
<DriverName>ssudbus.inf_amd64_6c8cd03f9c562c7a\ssudbus.inf</DriverName>
<DriverVersion>2.11.10.0</DriverVersion>
<DriverProvider>SAMSUNG Electronics Co., Ltd.</DriverProvider>
<DeviceInstanceID>USB\VID_04E8&PID_685D\5&106F75EA&0&4</DeviceInstanceID>
<SetupClass>{36FC9E60-C465-11CF-8056-444553540000}</SetupClass>
<RebootOption>false</RebootOption>
<UpgradeDevice>false</UpgradeDevice>
<IsDriverOEM>true</IsDriverOEM>
<InstallStatus>0x0</InstallStatus>
<DriverDescription>SAMSUNG Mobile USB CDC Composite Device</DriverDescription>
</InstallDeviceID>
</UserData>
</Event>
Maybe those two lines with 'false' at the bottom are supposed to be 'true'.
Might this be the cause of all the problems or, this is normal.
Shall i try to solve this driver issue first?
(If there is an issue at all.)
The rest what you wrote seem to be in working order.
pederzen said:
Correct me if i'm wrong but if it was Samsung's firmware protection, FRP lock would be ON.
In my case it sais OFF.
Otherwise i agree with you these cases are 95% FW/downgrade related.
Click to expand...
Click to collapse
In order to mess with your phone the option should be "on" , that denotes that Samsung's "FRP" with be deactivated and no interference will take place or bricking.
If it's "off" then you run the risk of borking your phone.
Off, no good.
On, ok.
Another thing running Windows 7 on my Asus, my device manager recognises my (stock) phone as a Samsung device.
Pp.
This is what you want in developer options.
Pp.
pederzen said:
@Aou
Tried two computers, several cables still the same.
When flshing hangs, a few seconds pass, unknown USB device sign comes up.
Went to samsung page, DL-ed, installed latest driver.
Now it sais in device manager:
'Device USB\VID_04E8&PID_685D\5&106f75ea&0&4 requires further installation.'
Whether it is connected in Odin mode or in normal mode when the screen with the triangle is on saying that installation went wrong...bla-bla
(snip)
Maybe those two lines with 'false' at the bottom are supposed to be 'true'.
Might this be the cause of all the problems or, this is normal.
Shall i try to solve this driver issue first?
(If there is an issue at all.)
The rest what you wrote seem to be in working order.
Click to expand...
Click to collapse
Well, the fact that you've tried two different computers does narrow things down a tad, except the antivirus/antimalware thing, if you happened to be running the same on both PCs.
As for that specific driver (the CDC one), I've got 2.12.0.0 on my computer, but this is on Win10 at the moment. I could probably check my Win7 installation, but I'm not physically in front of my computer at the moment and can't reboot into Win7 from here.
Usually Samsung Smartswitch (Kies) will force you to get the latest/proper drivers for the device. Do you have the latest version of SmartSwitch?
As for the "false" parts there, that shouldn't matter, I wouldn't think. Odin itself does have an option about rebooting after a successful flash, though.
I believe the behavior you're seeing - where upon an unsuccessful flash you see another device show up - is the device trying to go into some sort of emergency download mode. Like, a more fundamental download mode that Samsung can use to forcefully flash things to the phone to try to revive it. I've had some older Samsung phones do that before upon a bad flash of firmware.
Are you familiar with how to tarball an image for Odin? I'm thinking you might try to re-package only the system.img into a new tarball, and flash that alone. From a CygWin terminal, or in a Linux environment (say hello to VirtualBox and Ubuntu!), you'd do something like this:
Code:
tar -H ustar -c system.img > DOI1_system.tar && md5sum -t DOI1_system.tar >> DOI1_system.tar && mv DOI1_system.tar DOI1_system.tar.md5
Or you could skip the md5 generation and just do:
Code:
tar -H ustar -c system.img > DOI1_system.tar
Of course, the above implies that you extracted the system.img from the Odin package. The .zip file contains the .tar.md5 (of course), and you can use a tool like 7-zip to open that md5'd tarball. You'll probably see warnings/errors about an improper ending to the tarball, but that's because of the md5 hash that's been literally just slapped onto the backside of the tarball. Safe to ignore that.
Let me know if you need me to do this and upload it, but it would take me a little while.
Here is the system.img tar file according to Aou's instructions. You have to unzip it.
System.img
Thank you friends! You guys are wonderful.
I'll give it a shot when i get home this afternoon (EU time)
Let's hope this will give it the final push!
Alex9090 said:
Here is the system.img tar file according to Aou's instructions. You have to unzip it.
System.img
Click to expand...
Click to collapse
Mega requires a key for the download, can you give it please?
Tried 'Don't look back in Anger' but didn' work
Symptoms:
1. Boot loop. GT-N7102 logo comes and the device reboots.
2. Can go to download mode. Model no. GT-N7102 is visible
3. Recovery mode-Android shows up for ~4 seconds and then phone reboots and goes into a boot-loop.
Was running N7102ZCUEOJ1_JB43_deodex_gapps_root_noknox_lite_by _neopunk88 (since March'16), when the phone suddenly decided to go into a boot-loop.
The phone was rooted. I had installed LSpeed the previous night and had set it to run in recommended mode.
What I have tried so far
1. Odin 3.07, 3.09 etc
2. stock recovery flash fails
2. tried to flash N7102ZCUEOJ1_N7102CHNEOJ1_N7102ZCUEML1_HOME.tar.md5 (last stock), but fails
3. After I had exhausted possibilities, tried the following pit files, one at a time, first from here and then here and then here along with the stock ROM. All pit files seem legit and the correct ones, but I have no way to verify. I have tried first without and then with re-partition option selected in Odin. Flash fails.
4. All drivers, USB ports and cable okay as I can flash my wife's S6.
Phone still going into download mode.
Odin fail modes
1. without pit file, while flashing either recovery or stock rom, Odil fails just after sboot.bin at NAND write-start.
2. with pit file and re-partition checked, Odin gets stuck in "get pit file for mapping"
3. with pit file but re-partition unchecked, Odin fails is the same as (1)
4. I have tried setting Odin compatibility to XP but it does not result in anything different. I haven't needed xp compatibility setting this while flashing anything before.
Please could I have some guidance on what options I have left and the files, if I am not using the correct ones?
My belief is that if I can get to the download mode, there has to be way to un-brick the phone..fingers crossed.
Thanks in advance.
UPDATE: Fixed phone by replacing the motherboard from here. Everything working fine now.
still waiting for a response..
@jam_27 It is possible that eMMC got corrupted. (it's a hardware fail)
If I were you I would try to flash TWRP. http://www.twrp.me - For N7100, as it doesn't matter for recovery.
READ: http://forum.xda-developers.com/galaxy-note-2/help/nt7100-wont-boot-wont-charge-recover-t3504290
Thanks, TWRP recovery flash fails at NAND write start.
jam_27 said:
Thanks, TWRP recovery flash fails at NAND write start.
Click to expand...
Click to collapse
Below the JTAG tool report from FoneFunShop UK
eMMC Flash Memory Chip is damaged
===============
= JTAG REPORT =
===============
Open serial port...OK
Connecting to the RIFF Box...OK
Connecting to the dead body...OK
Detected dead body: DETECTED
Set I/O Voltage reads OK, TCK Frequency is OK
Resurrection sequence started.
Establish communication with the phone...OK
Initializing internal hardware configuration...OK
Uploading resurrector data into memory...OK
Starting communication with resurrector...OK
Flashing the dead body...
No Resurrection Data is available for the eMMC Chip with Capacity = 0B
ERROR: Failed use to Resurrection Data for the eMMC Chip with Capacity = 0B
ERROR: Selected FLASH Chip was not initialized by the DCC Loader.
----
I wont be able to replace the emmc chip myself (don't have the correct tools) but should be able to replace the motherboard.
Any other suggestions before I open up the until.
Hi,
So I try to flash TWRP. I tried like 10 differents versions. All version below 3 makes a bootloop when accessing recovery mode, and above 3 are bringing me back to download mode (without the question to accept or not, and without the text at the top left corner of the screen).
I tried with odin under windows (tried with 3.0.7, 3.10.x and I think 3.12 as well), I tried with heimdall under linux also. Here's the output of heimdall:
Code:
[[email protected] ~]# heimdall flash --RECOVERY twrp-3.1.0-1-picassowifi.img --no-reboot
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
censored
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
censored
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading RECOVERY
100%
RECOVERY upload successful
Ending session...
Releasing device interface...
I'm able to go to odin mode by holding down VOL-DOWN + Power (no need to hold the home button) and I go try to go to recovery mode with VOL-UP + Power + Home.
The OS on the tablet is Android 4.4.2 stock rom. I tried to root it but when the OS loads, it does a quick update and root is not working as well.
Anyone else had the same problem than me?
hello
first change the usb cable i don't know but 8/10 it's the solution
back to the origine
install cfautorout ( all needed is in the zip)
then install twrp
regards
Hi I made a post in ressurection remix post in development. I posted a link to everything I used to root my tablet sm-t520. I used cf-autoroot. The best way to flash custom recovery using Odin. Go to official website and download the .Md5 file. Should be called like picassowifi.img.md5 or something similar. Put that in AP slot in Odin and run, that should work. Let me know if you need any other help.
SM-T520
So I just did 5 of these Samsung SM-T520 tablets for work as the 4.4.2 OS’ would not allow us to use some special software for doing digital inspections on Vehicles.
Our software maker said we needed 5.0 and higher so after many hours of trial and error, I found the right process and rom that worked.
For installing TWRP I used Odin, but had similar problem as you. Fix was to go to TWRP website and make sure you download there version for your device but I could only get 3.0.0.0 to work anything above or below caused issues. I also installed micro SD card into units to use as back up and drop all files required to install new rom. I simply just used windows drag and drop or copy and drop feature. I also noticed that while in TWRP and doing backup that if screen saver on tablet activated it would cause a crash and reboot, My fix for this was to go into TWRP screen time out settings and max it out , also even though tedious I would touch screen every 60 second just to make sure counter was reset. I did have one tablet crash after bad rom installation but putting tablet into download mode, running Odin to install TWRP version 3.0.0.0 got me back up and running and allowed me to install better rom. Please note I take no credit for any of this, as many hours of research and testing and trying different things were a combination of other people’s work. That being said I did try the TWRP version 3.0.0.0 on my own without any direction from others as I was just testing things out and got lucky. Hope this helps. If you need more info on exact Rom and files just let me know.
But I will tell you this I did try the Latest versions of Lineage OS "at least 5 versions and was never able to get a stable system, had multiple problems with camera crashing "even with out using it", OS crashing, constant Reboots, Reboot looping and others. All my tablets have been running smooth for 3 weeks no problems at all so far with a different ROM that is base on the 7.1 nougat. I have not given up on Lineage yet just going to wait a bit as it is possible The inspection software I need is not compatible with something in the Lineage OS. Good luck
caution
twrp 3.1.0.0 doesnt work
regards