Database Develop

[Q] Samsung Galaxy S: Black Screen after Flash

I have a SGS with firmware I9000XWJG5 and Root. I tried to do a Speed fix, but afterwards it was slower so i tried to flash the phone with the I9000XWJG5 firmware again.
After the flash, the phone rebooted and i came to the recovery menu. There the phone wrote:
update media, please wait
and in the next lines:
E: Can't mount /dev/block/st110
(invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Now when i try do start the phone, i get a black screen after the bright S
What i have tried: Flash agein with and without re-partition and Factory Reset
Has anybody an idea what i can do?
and sorry for my bad english

bump. can anyone help with this topic..
i am having some problem..
help us guys
thanks
Fixed... use odin 512

Thread moved in Galaxy S I9000 General.

I can definately help with this one, as I worked through it last night...
I found that if you're trying to flash the JG5 rom (as mentioned in Modaco's thread) with the 513 Pit file, then you'll get the black screen of despair!! For some reason the two combination of the two don't work.
However, if you do a google search for Odin PIT 512, then download this file
You will be able to download the 512 PIT file instead. Now use this in Odin3 to flash the JG5 rom and you should have no further issues....it worked for me.
I also discovered that Samsung have just released a later firmware, so I just flashed this one on top of the JG5 one...I have a nicely running phone now.
Hope this helps...it did me!
Mike

Mine was completely knackered. Couldn't get to recovery either. Flashed Modaco's MCR R3, after the JG5 flash, using all the files in the JG5 download. Working a treat...
Cheers,
BS...

blacksoul93 said:
I have a SGS with firmware I9000XWJG5 and Root. I tried to do a Speed fix, but afterwards it was slower so i tried to flash the phone with the I9000XWJG5 firmware again.
After the flash, the phone rebooted and i came to the recovery menu. There the phone wrote:
update media, please wait
and in the next lines:
E: Can't mount /dev/block/st110
(invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
copy default media content failed.
Now when i try do start the phone, i get a black screen after the bright S
What i have tried: Flash agein with and without re-partition and Factory Reset
Has anybody an idea what i can do?
and sorry for my bad english
Click to expand...
Click to collapse
hello, i got the same problem. trying to reflash with I9000XXJPY 2.2.1 and the 512 pit, but still the same problem.

ash969 said:
hello, i got the same problem. trying to reflash with I9000XXJPY 2.2.1 and the 512 pit, but still the same problem.
Click to expand...
Click to collapse
Same here.
I tried JS3 and going back to JP6....and always the same result.
I'm obviously missing something. Maybe my 512.PIT is corrupted. I get the black screen and the same /dev/block.st110 errors in recovery.

i beleive you need to have a CSC file also for the odin flash.
i sorted mine like this:
Downloaded some JP2 odin files [used this as this was the only one on Samsung-firmwares that had all 3 PDA, Modem and CSC Files. flashed this using a .512 pit in odin. - this allowed the phone to boot normally.
connected to Kies and using reg hack [set to XEU] managed to update to JPY.
the following the Darky guide, flashed the CF Root kernel, installed the ROM Manager from the market, using the recovery mode installed the update.zip file for clockworkMod.
Formatted everything in ClockworkMod
Factory Reset in ClockworkMod
Installed Darky ROM V8.0 Wipe

thanks for your find !
Rumble6059 said:
i beleive you need to have a CSC file also for the odin flash.
i sorted mine like this:
Downloaded some JP2 odin files [used this as this was the only one on Samsung-firmwares that had all 3 PDA, Modem and CSC Files. flashed this using a .512 pit in odin. - this allowed the phone to boot normally.
connected to Kies and using reg hack [set to XEU] managed to update to JPY.
the following the Darky guide, flashed the CF Root kernel, installed the ROM Manager from the market, using the recovery mode installed the update.zip file for clockworkMod.
Formatted everything in ClockworkMod
Factory Reset in ClockworkMod
Installed Darky ROM V8.0 Wipe
Click to expand...
Click to collapse
thanks mate ! after a huge scare sorted mine with this firmware as well, this after I tried several other newer firmware packages from samfirmware and was ,slowly but surely ,starting to lose hope ...
for some reason this particular firmware JP2 seems to fix this problem
cheers and thanks again for your find !

fix for black screen after flash with no recover or download mode working.
Hey All.
So like the subject says, you flash and then your phone restarts or whatever, and then you get the normal galaxy s startup, with the sound and the visuals, but then that's it. Henceforth you are greeted with the two lights (if its a Bell Vibrant) from your options and back keys.
To fix it use the attached file. Its called ADB or something - I just know it works. It was a fix for the galaxy s phones that didnt have the recovery/download mode stock.
so here is how it goes:
1. download adb to your desktop and unpack it (if its in winrar or zip or whatever) to a file folder named adb.
2. open a command prompt.
3. type "cd" and then the address of the "adb" folder. so for example it should be in C:\Users\your user name\Desktop\adb. where "your user name" is your user name a duh.
4. plug in your galaxy s via usb.
5. type "adb reboot download" in the command prompt. copy it using your mouse as well.
6. turn on your phone.
7. press enter in the command prompt, then keep copying and pasting and pressing enter until you see the download screen on your phone. each time you press enter it says device not connected or something but just keep trying.
the article i read:
can't post it but the thread is called "How to get the 3 button recovery mode working"
Credit to Goots from samsung galaxy s forums. Go Goots!

[Q] Problems!

I root my SGS with Z4 root. i change recovery 3e to 2e and there i make some mistake. can´t start droid anymore. It goes Dl and Rec -modes but i can´t flash (install)any roms (firms) with Odin.
It always sais at:
E:Can´t mount /dev/block/st110
(invalid argument)
E:copy_dbdate_media:Can´t mount DBDATA:
Our storage not prepared yet. please use UI menu for format and reboot actions.
copy default media content failed.
How can i get rom back in phone? :F

in recovery mode - mount sdcard
push cwm recovery as update.zip and also something like one of darkys roms as a zip.
then unmount sdcard. then run the update.zip from recovery to reboot to cwm (may have to be done twice)
then from cwm recovery install zip from sdcard (rom file)

I have recovery 3e in it now. Can´t do much with it. :F
cwm?
using update.zip. it says cant find path...
cant mount.. bla bla bla.
having gray hairs.. :F
if u have some good ideas i´m glad to hear.

Flash a speedmod kernel to get 2e back, flash with odin from download mode. then flash a stock rom with a dbdata file inside the .tar file, flash it with odin also. Not all stock roms have the dbdata so you need to check a few of them. Just right click them once downloaded and open.... Dont extract...once you confirm the file has the dbdata flash it...once your phone boots flash any rom on top that you like.
Sent from my GT-I9000 using XDA App

jm1 from samfirmware should have everything required to get back up and running

I get now that clockwork reco 2.5.1.0 working. Thanks about that!
need more adwise
cant find stock roms with dbdata.
Can i just flash some rom (custom rom) with odin?
still having gray hairs.. :F

cilli said:
I root my SGS with Z4 root. i change recovery 3e to 2e and there i make some mistake. can´t start droid anymore. It goes Dl and Rec -modes but i can´t flash (install)any roms (firms) with Odin.
It always sais at:
E:Can´t mount /dev/block/st110
(invalid argument)
E:copy_dbdate_media:Can´t mount DBDATA:
Our storage not prepared yet. please use UI menu for format and reboot actions.
copy default media content failed.
How can i get rom back in phone? :F
Click to expand...
Click to collapse
You need to flash a firmware package with separate pda, modem and csc like JPU and then flash to updated firmware.

Intratech said:
You need to flash a firmware package with separate pda, modem and csc like JPU and then flash to updated firmware.
Click to expand...
Click to collapse
you can flash a stock rom with them all integrated and do not need the seprate pda, csc or modem. I had this exact issue and had to flash original 2.1 to get it going. i'm on a bell phone and my specific version was UGJH2 which had the dbdata included. download the original stock 2.1 and check, get from samfirmware or from here: (make sure you get your specific ROM though, i'm not sure which one that is for you)
http://forum.xda-developers.com/showthread.php?t=846913
You are looking for dbdata.rfs

ITS ALIVE!! ITS ALIVE!!
Thanks all of u!!
But so now i have to update it to 2.2.
Can i do that with Kies?

That is my suggestion, although you know what to do now if it goes bad. it's pretty hard to mess up the phone by flashing unless you unplug it in the middle of the flash.

[Q] EFS Mounting Problem

Hi,
I'm a newbee around here and I would really appreciate if someone could help me on this.
My GT-I9070 was fully functional till yesterday. I've been running CM10.2. Yesterday I tried to change the Kernal to Co-Core 8.2. I deeply regret doing that because I didn't had enough knowledge on how to change kernals. What I did was copied the Co-Core zip file to sdcard and applied it via CWM. After that, my phone restarted and it was stuck on the CM boot screen. I got mad and flashed the phone to stock 4.1.2 using ODIN. Then the setup wizard showed up and it kept on crashing giving me toasts, "gapps not working" and "setup wizard has unfortunately stopped".
I then went to stock recovery mode and the log said,
E:failed to mount /efs (No such file or directory)
E:failed to mount efs (Invalid argument)
Applying Multi CSC..
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs Multi csc applied failed
I searched on n number of threads here in XDA about this problem and read in one thread that IMEI could've corrupted.
Then using ODIN, I flashed my mob to stock GB 2.3.6 with DDLD4 baseband. Then everything worked perfect. Phone booted up and was working perfect. But then I tried to update the phone to 4.1.2 via KIES, the KIES said "This phone can't be upgraded".
I again flashed 4.1.2 using ODIN, again it said gapps and setup wizard unfortunately stopped. I tried installing CM10.1, CM10.2, MIUI but in all cases, it got stuck on the bootscreen of each ROM. I flashed back to stock GB again and phone is working perfect now. When I go to "about phone", IMEI is showing with no error. It is the same IMEI which the phone had when it was bought. But when I go into recovery mode, it still says "/efs can't be mount". What could be the possible reason for this? How I can I fix this? Is there anyway for me to install the CM ROM again and successfully keep it up and running?

arjunkdas said:
Hi,
I'm a newbee around here and I would really appreciate if someone could help me on this.
My GT-I9070 was fully functional till yesterday. I've been running CM10.2. Yesterday I tried to change the Kernal to Co-Core 8.2. I deeply regret doing that because I didn't had enough knowledge on how to change kernals. What I did was copied the Co-Core zip file to sdcard and applied it via CWM. After that, my phone restarted and it was stuck on the CM boot screen. I got mad and flashed the phone to stock 4.1.2 using ODIN. Then the setup wizard showed up and it kept on crashing giving me toasts, "gapps not working" and "setup wizard has unfortunately stopped".
I then went to stock recovery mode and the log said,
E:failed to mount /efs (No such file or directory)
E:failed to mount efs (Invalid argument)
Applying Multi CSC..
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs Multi csc applied failed
I searched on n number of threads here in XDA about this problem and read in one thread that IMEI could've corrupted.
Then using ODIN, I flashed my mob to stock GB 2.3.6 with DDLD4 baseband. Then everything worked perfect. Phone booted up and was working perfect. But then I tried to update the phone to 4.1.2 via KIES, the KIES said "This phone can't be upgraded".
I again flashed 4.1.2 using ODIN, again it said gapps and setup wizard unfortunately stopped. I tried installing CM10.1, CM10.2, MIUI but in all cases, it got stuck on the bootscreen of each ROM. I flashed back to stock GB again and phone is working perfect now. When I go to "about phone", IMEI is showing with no error. It is the same IMEI which the phone had when it was bought. But when I go into recovery mode, it still says "/efs can't be mount". What could be the possible reason for this? How I can I fix this? Is there anyway for me to install the CM ROM again and successfully keep it up and running?
Click to expand...
Click to collapse
Hi, did you try to flash other firmware?
Flash a new one and try to wipe data/factory reset.

YES, I DID
eduds said:
Hi, did you try to flash other firmware?
Flash a new one and try to wipe data/factory reset.
Click to expand...
Click to collapse
Yes, I mentioned, I tried to flash, CM10.1, CM 10.2 and MIUI also..I also did factory reset and wipe cache. But all of em was stuck on the bootscreen of the respective firmwares. :crying:

arjunkdas said:
Yes, I mentioned, I tried to flash, CM10.1, CM 10.2 and MIUI also..I also did factory reset and wipe cache. But all of em was stuck on the bootscreen of the respective firmwares. :crying:
Click to expand...
Click to collapse
No, I'm talking about original firmwares, not custom ROMs.

DDXL1 and DDLD4
eduds said:
No, I'm talking about original firmwares, not custom ROMs.
Click to expand...
Click to collapse
I flashed both of these baseband versions of GB..and DDULP8 baseband of JB..you want me to try flash more baseband versions?

did u solve it ?
arjunkdas
Click to expand...
Click to collapse

NO
amr diab said:
did u solve it ?
Click to expand...
Click to collapse
Not yet..I've been using GB for the past two months. Tried almost everything that I could find in xda. I'm afraid to go to Samsung SVC because I doubt they won't give me warranty for this problem. Do you have any solution?

arjunkdas said:
Not yet..I've been using GB for the past two months. Tried almost everything that I could find in xda. I'm afraid to go to Samsung SVC because I doubt they won't give me warranty for this problem. Do you have any solution?
Click to expand...
Click to collapse
i have the same problem
and i'm on GB too
i'm still searching every where
check this
http://forum.xda-developers.com/showthread.php?t=2506256&page=2
i will try and if it is solved i will tell u

amr diab said:
i have the same problem
and i'm on GB too
i'm still searching every where
check this
http://forum.xda-developers.com/showthread.php?t=2506256&page=2
i will try and if it is solved i will tell u
Click to expand...
Click to collapse
Ok man! I'm also on it!

arjunkdas said:
Hi,
I'm a newbee around here and I would really appreciate if someone could help me on this.
My GT-I9070 was fully functional till yesterday. I've been running CM10.2. Yesterday I tried to change the Kernal to Co-Core 8.2. I deeply regret doing that because I didn't had enough knowledge on how to change kernals. What I did was copied the Co-Core zip file to sdcard and applied it via CWM. After that, my phone restarted and it was stuck on the CM boot screen. I got mad and flashed the phone to stock 4.1.2 using ODIN. Then the setup wizard showed up and it kept on crashing giving me toasts, "gapps not working" and "setup wizard has unfortunately stopped".
I then went to stock recovery mode and the log said,
E:failed to mount /efs (No such file or directory)
E:failed to mount efs (Invalid argument)
Applying Multi CSC..
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs Multi csc applied failed
I searched on n number of threads here in XDA about this problem and read in one thread that IMEI could've corrupted.
Then using ODIN, I flashed my mob to stock GB 2.3.6 with DDLD4 baseband. Then everything worked perfect. Phone booted up and was working perfect. But then I tried to update the phone to 4.1.2 via KIES, the KIES said "This phone can't be upgraded".
I again flashed 4.1.2 using ODIN, again it said gapps and setup wizard unfortunately stopped. I tried installing CM10.1, CM10.2, MIUI but in all cases, it got stuck on the bootscreen of each ROM. I flashed back to stock GB again and phone is working perfect now. When I go to "about phone", IMEI is showing with no error. It is the same IMEI which the phone had when it was bought. But when I go into recovery mode, it still says "/efs can't be mount". What could be the possible reason for this? How I can I fix this? Is there anyway for me to install the CM ROM again and successfully keep it up and running?
Click to expand...
Click to collapse
i got that problem too. you should flash your .pit file and check repartition in odin.
this solved my problem.

Patlcs said:
i got that problem too. you should flash your .pit file and check repartition in odin.
this solved my problem.
Click to expand...
Click to collapse
Are you saying I have to flash pit file alone? Or do a full flash of GB with repartition checked?
While flashing JB, I didn't used any pit file. Just used the .tar file which was selected under PDA of ODIN.
Any idea if checking repartition while flashing JB would work?
I'm currently running GB 2.3.6 baseband version DXLD1. And I've got 2 pit files one for 8GB which I got from the DXLD1 package I downloaded and one 16 GB which I downloaded separately.

arjunkdas said:
Are you saying I have to flash pit file alone? Or do a full flash of GB with repartition checked?
While flashing JB, I didn't used any pit file. Just used the .tar file which was selected under PDA of ODIN.
Any idea if checking repartition while flashing JB would work?
I'm currently running GB 2.3.6 baseband version DXLD1. And I've got 2 pit files one for 8GB which I got from the DXLD1 package I downloaded and one 16 GB which I downloaded separately.
Click to expand...
Click to collapse
No... you should flash pit file with the .tar.md5 file.
repartition will work on either GB or JB.
if you have the 8gb version you should use the 8gb .pit file and use the 16 gb .pit file if you have the 16gb version.

http://forum.xda-developers.com/showthread.php?t=2353293
check this man
it is worked for me !!!!!!!!!!!!!!

NO Backup EFS
amr diab said:
http://forum.xda-developers.com/showthread.php?t=2353293
check this man
it is worked for me !!!!!!!!!!!!!!
Click to expand...
Click to collapse
solution in that thread says you need to have an EFS backup. And I dont have it. And in next post, that guy said his restored IMEI is corrupted. Did u checked yours??!

Doubts
Patlcs said:
No... you should flash pit file with the .tar.md5 file.
repartition will work on either GB or JB.
if you have the 8gb version you should use the 8gb .pit file and use the 16 gb .pit file if you have the 16gb version.
Click to expand...
Click to collapse
My phone is the 16 GB version. I'm having some weird doubts. I beg your pardon if I'm asking noob questions but I need to know them.
Ok, so here's how I flashed JB 4.1.2
In the JB package I downloaded, ther was only .tar file and nothing else. The baseband version is DDULP8. So everytime I flashed JB, I did with .tar file alone and no pit file.
Now, whenever I flashed back to GB 2.3.6, I flashed by selecting three files in the DXLD1 download package. PDA file, CSC file and an 8GB pit file. I flashed with these files at the first place and the phone boots up, works well. But the internal storage is shown as 3.91 GB. To solve this, I downloaded a separate 16GB pit file and flashed the phone by just selecting the 16GB pit file. After I rebooted my phone, it shows 11.1 GB internal storage.
My doubt is, do I need to select the 16GB pit file and check repartition while flashing JB 4.1.2?
Or just check repartition and flash with .tar file alone?!

Didn't solved
Patlcs said:
i got that problem too. you should flash your .pit file and check repartition in odin.
this solved my problem.
Click to expand...
Click to collapse
tried it..didnt solve the problem!

arjunkdas said:
solution in that thread says you need to have an EFS backup. And I dont have it. And in next post, that guy said his restored IMEI is corrupted. Did u checked yours??!
Click to expand...
Click to collapse
i didn't have any backup and the imei is ok
just try it from 1-10
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.

amr diab said:
i didn't have any backup and the imei is ok
just try it from 1-10
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Click to expand...
Click to collapse
Tried! Still getting steup wizard stopped message!

arjunkdas said:
tried it..didnt solve the problem!
Click to expand...
Click to collapse
try to flash .pit file alone

Patlcs said:
try to flash .pit file alone
Click to expand...
Click to collapse
tried that too!

Note 4 N910F 5.1.1 COH4 firmware available

Latest firmware: http://live.samsung-updates.com/det..._4_Snapdragon/SM-N910F/HTS/N910FXXU1COH4.html
Haven't seen it on Sammobile yet (their downloads are much faster) Camera2 Api? Probably not. Downloading now. Also liveblog downloads always fail for me....

download speeds with samsung firmware downloader are much faster, the file is available!!

SamFirm_v0.3.3 http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
FAIL! size is too big

How do you flash it?

bsaidmalta said:
How do you flash it?
Click to expand...
Click to collapse
With Odin

MMarkkk said:
SamFirm_v0.3.3 http://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
FAIL! size is too big
Click to expand...
Click to collapse
EXCELLENT! Didn't know about this program. DL at 4Mbit!

guide to how to avoid the odin error when flashing: http://forum.xda-developers.com/note-4/general/n910f-how-to-create-odin-flashable-5-1-t3189143

TML1504 said:
guide to how to avoid the odin error when flashing: http://forum.xda-developers.com/note-4/general/n910f-how-to-create-odin-flashable-5-1-t3189143
Click to expand...
Click to collapse
waiting for upload

Downloaded and Odin'ed but I got fail!
It doesn't seem to give the size error, besides I've flashed many different regions on my 910F without a hitch in the past.

Check out post up and see guide.

Tried to follow this guide couldn't do it, driving me mad, wont find the directory some want to help noob, i flash before said file to big

TML1504 said:
guide to how to avoid the odin error when flashing: http://forum.xda-developers.com/note-4/general/n910f-how-to-create-odin-flashable-5-1-t3189143
Click to expand...
Click to collapse
Thanks :good::good::good::good::good:

uspsilencer said:
Tried to follow this guide couldn't do it, driving me mad, wont find the directory some want to help noob, i flash before said file to big
Click to expand...
Click to collapse
what exactly is your problem with my guide? if you want you can ask me questions there...
I will try to help!

gave up wouldn't find the directory om my c drive were i had it, flash stock firmware back on, wait for actual tar i can flash with odin

uspsilencer said:
gave up wouldn't find the directory om my c drive were i had it, flash stock firmware back on, wait for actual tar i can flash with odin
Click to expand...
Click to collapse
put the extracted firmware files into c:\odin
delete hidden.img and cache.img
then the command in cygwin to change to that directory would be
cd /cydrive/c/odin
then enter the re-tar command as described in my guide and flash the n910f.tar file with odin! this will work 100%!

Sorry guys.. can i flash N910FXXU1COH4 HUI (h3g italy) on my no branded note?

I uploaded to Mega the tar file without error Too Big. Just flash with odin.
https://mega.nz/#!kF9lQICD!tj20KRkglMOArvu-RyJ_WXLvThGhqyQBdFAtNXD5X88

Kristjan P said:
I uploaded to Mega the tar file without error Too Big. Just flash with odin.
https://mega.nz/#!kF9lQICD!tj20KRkglMOArvu-RyJ_WXLvThGhqyQBdFAtNXD5X88
Click to expand...
Click to collapse
U da real MVP
Sent from my SM-N910F using Tapatalk

3.3 go it's very crazy O_O

Ok finally got through the change directory, created the tar as described and flashed it with Odin. Stuck in bootloop. Tried installing twrp recovery, either failed with odin or when trying to boot into recovery it automatically went into download mode.
Flashed my regions stock rom through kies emergency recovery. Boots up fine, works fine. Next flashed the 5.1.1 Tar image. Same problem, endless booting sequence (gets up to home page and then reboots).
Anyone have some suggestions?

Repairing the A6 after installing unsuitable recovery.tar

#1# I have a Samsung A6 Tab [SM-T580 Series] and unfortunately i installed a wrong custom recovery with Odin, because i forgot looking and the number.
Afterwards my Tab bricked. Download mode is still operational!
#2# The best advice i could find afterwards was to install a stock rom.
However i can't find either the correct stock rom or the correct twrp.tar.
#3# The problem arrived after i renamed twrp.tar to recovery.tar, because flashing or installing by first trying didn't work.
The XDA-Link to supported devices shows me only TWRP for A 10.1, A 9.7 and A8. That's why i am in a state of desperation.
My Questions so far are: Would replacing recovery.tar with the correct custom recovery or the original recovery by using Odin unbrick the Tab?
If not, where i may find the correct stock rom?

dontdropme said:
#1# I have a Samsung A6 Tab [SM-T580 Series] and unfortunately i installed a wrong 10.1, A 9.7 and A8. That's why i am in a state of desperation.
My Questions so far are: Would replacing recovery.tar with the correct custom recovery or the original recovery by using Odin unbrick the Tab?
If not, where i may find the correct stock rom?
Click to expand...
Click to collapse
flashing stock mostly solve problems. i don't know what you type during searching, but when i googling "SM-T580" there r so many sites provide your firmware (sammobile, samsung-firmware.org). From MM (6) until android 7 and 7.1 available and you unable to find it?
top brand like sams*ng it is not hard to find any firmware or whatever related to i think

Thanks for answering, you are right. Sammobile has the firmware i need. I found it. However, i still would like to know if an official TWRP exists for my device, just for the future, if i would need the possibility to backup or restore files.

dontdropme said:
Thanks for answering, you are right. Sammobile has the firmware i need. I found it. However, i still would like to know if an official TWRP exists for my device, just for the future, if i would need the possibility to backup or restore files.
Click to expand...
Click to collapse
go here and check if your device TWRP officially supported.
https://twrpbuilder.github.io/downloads/twrp/ and/or https://twrp.me/Devices/

Before flashing Stock Rom i extracted revocery.img from AP and converted it to recovery.tar without compressing and tried to solve the problem this way, re-flashing original recovery, but it failed.
So i tried it again and installed the newest version of Odin and in the second try i flashed AP, BL, and CSC.
Odin allows me to pass the full flashing process with no error.
But after the reset the tablet stucks in a loop of system updating and stops at 32%.
Notes in the download mode are "FRP-unlock: off" and "System: Custom" changed to "System: Offical. "
The red line "Recovery is not seandroid enforcing" vanished.
However it still says "Recovery: Custom" in the download mode and this shouldn't be possible after flashing Stock Rom.
At this moment the following errors appear.
No Support SINGLE_SKU
Supported API: 3
E: failed to mount/efs (invalid argument)
dm-verity error...
E: failed to mount /cache (invalid argument)
E: Can't mount /cache/recovery/last_kernel_manual
E: Can't open /cache/recovery/last_kernel_manual
E: failed to mount /cache (invalid argument)
E: Can't mount /cache/recovery/last_locale
Does this mean the partitions are damaged?
The only advices i found on google were, to flash with re-partitioning and to find the pit file. But i am afraid this would make it worse. Should i go to a repair service center or is it possible to still fix it?

If you download the stock firmware and flash the whole rom via odin and look in i believe is ap or csc.tar you should find the pit file extract it via 7zip or other alternative and load it with the pit selector in odin and reflash stock rom including the bl,ap,cp,csc and you should have a fully booting A6
Sent from my [device_name] using XDA-Developers Legacy app

Ok, i found the pit-file in CSC, but a CP file doesn't exist for SMT-580 Wi-Fi as far as i know.
I assume that i need to flash with re-partitioning and that i need to get sure the pit-file is for a 16 GB device.
But will this really solve my "[invalid argument]-issue"???

dontdropme said:
Ok, i found the pit-file in CSC, but a CP file doesn't exist for SMT-580 Wi-Fi as far as i know.
I assume that i need to flash with re-partitioning and that i need to get sure the pit-file is for a 16 GB device.
But will this really solve my "[invalid argument]-issue"???
Click to expand...
Click to collapse
yes theoretically it should solve all your issues and you should be able to reboot the device

allenjthomsen said:
yes theoretically it should solve all your issues and you should be able to reboot the device
Click to expand...
Click to collapse
Ok, flashing with Odin works, showing me no error, but i am still stucked in a bootloop. If i try to get in to the recovery mode it tells me, that it installs the update.
It does that, until it reaches 32%. I have tried flashing the stockrom with re-partitioning and the pit-file. Didn't work. Next thing i tried was to start Odin as Admin and with a newer version of the firmware. Didn't work. What changed is that "Current Binary: Custom" to "Current Binary: Samsung Official".
System Status is still: "Custom".
It still refuses to mount the system or to get to 100%, so that i could see the recovery mode with all it's options.
Could it be, that the CPU or the Memory is damaged?

Try to flash twrp then wipe factory data eeset and format data then flash stock again and see if that helps you boot to stock
Sent from my [device_name] using XDA-Developers Legacy app