Database Develop

Help i bricked my samsung (Video)

Help i bricked my samsung note.
when i go at the recovery i cant format emj or data or emmc i got error
i get this error
E:failed to mount /data (invalid argument) ECopy_log_data cant mount /data
i try odin programm with stock firmware and he stack at samsung icon!
sorry for bad english
video in a while ... help me please i want to unbrick my phone

Here is my video guys help me pleaseee .... dont avoid me
youtube.com/watch?v=8WBdO4RdkqQ add W W W

what ROM you had before this happened?
Was phone rooted?
if yes was it on stock kernel?
what you were doing when this happened?
and where is video link?

Valium10 said:
what ROM you had before this happened?
Was phone rooted?
if yes was it on stock kernel?
what you were doing when this happened?
and where is video link?
Click to expand...
Click to collapse
It was stock Rom i install from cmw SU and i root the phone
i try to install cricskelo rom
its stuck at samsung icon and nothing else!
Here is the video - > 8WBdO4RdkqQ at youtube

so??

Did you use CWM.zip? Or how did you root your stock Rom?

yes i install cmw ! and after this i install criskelo rom

rooy said:
yes i install cmw ! and after this i install criskelo rom
Click to expand...
Click to collapse
One more try and read what I write:
Did you use a file "cwm.zip" to install cwm (there is no cmw)?
Your answers should be precise - help is more easy then

ThaiDai said:
One more try and read what I write:
Did you use a file "cwm.zip" to install cwm (there is no cmw)?
Your answers should be precise - help is more easy then
Click to expand...
Click to collapse
Yes i use CWM.ZIP to install cwm

rooy said:
Yes i use CWM.ZIP to install cwm
Click to expand...
Click to collapse
Okay. Then we can assume you hard bricked your device.
To confirm this (or not) please download a stock Rom (Dr. Ketan's thread or sammobile.com) - it's not so important what you choose, but should be for your country.
Install this Rom with PC Odin on your device.
And have a look at the messages: if it stops at factoryfs.img the it's bricked.

ThaiDai said:
Okay. Then we can assume you hard bricked your device.
To confirm this (or not) please download a stock Rom (Dr. Ketan's thread or sammobile.com) - it's not so important what you choose, but should be for your country.
Install this Rom with PC Odin on your device.
And have a look at the messages: if it stops at factoryfs.img the it's bricked.
Click to expand...
Click to collapse
i try to install with odin stock rom and doesnt stop at factorufs.img it finish and succefully complete . but now it stucks at samsung galaxy note gt-n7000 at boot!
and now new problem at stock cmw . When it boot at stock cmw i got a messenge
Deleting Cryption Neta Data.
#Manual Mode#
--Updating application...
Successfully updated application.
--Appling Multi-CSC...
Installing Multi CSC
Cant access to '/system/csc/EUR/system/'.
Succesfully applied multi-CSC.

rooy said:
i try to install with odin stock rom and doesnt stop at factorufs.img it finish and succefully complete . but now it stucks at samsung galaxy note gt-n7000 at boot!
and now new problem at stock cmw . When it boot at stock cmw i got a messenge
Deleting Cryption Neta Data.
#Manual Mode#
--Updating application...
Successfully updated application.
--Appling Multi-CSC...
Installing Multi CSC
Cant access to '/system/csc/EUR/system/'.
Succesfully applied multi-CSC.
Click to expand...
Click to collapse
Download a different Rom, check MD5 and install it with PC Odin - you should make sure that you have condition that is exactly defined.
I will not answer or search for solutions if this isn't clear, sorry.

ThaiDai said:
Download a different Rom, check MD5 and install it with PC Odin - you should make sure that you have condition that is exactly defined.
I will not answer or search for solutions if this isn't clear, sorry.
Click to expand...
Click to collapse
Where i can find roms for odin ? i dont know -.-

AW: Help i bricked my samsung (Video)
http://forum.xda-developers.com/showthread.php?p=20963707
Sent from my GT-N7000 using xda app-developers app

all its ok but it stucks at boot in samsung icon ?

can't access to /system/scs/eur/system new messenge at recovery mode..

JB Update /efs & baseband problem

Hello to all.
Yesterday I upgraded to JB, everything was fine until I got the idea how to reset the counter by odin terminal emulator.
I rebooted and then came back the wizard and it was in Russian, if I tried to do it crashed.
I tried to reflash but to no avail, same problem.
I went back to GB and I noticed that the phone, even if during the installation gave error mounting efs, could call and surf the 3g.
I find myself with the phone that works but the baseband is displayed as "xxxx" and I can not upgrade to JB or return the usual mistakes.
What has happened? how to fix this?
thanks in advance

http://forum.xda-developers.com/showthread.php?t=2121398

R_a_z_v_a_n said:
http://forum.xda-developers.com/showthread.php?t=2121398
Click to expand...
Click to collapse
I saw that post but does not solve the problem.
If I put JB crashes on startup wizard

Odin terminal emulator? What did you do exactly?
Odin is a PC software, Terminal Emulator is for Android and their functions are different
Sent from my GT-I9070 using xda app-developers app

Here is a tutorial to fix this if you have a backup, this is for Galaxy Ace 2 but applies to this phone too even the partitons are the same: http://forum.xda-developers.com/showthread.php?t=2145464
You will need a backup from /modemfs folder or modemfs partition, if you don't have backups ask someone to make it for you.
Don't use backups from different models (i9070 vs. i9070p).
And the best if the other phone is from the same region/network like yours.
"If I put JB crashes on startup wizard"
Have you selected the pit file and repartition in odin when you flashed JB firmware (with ace 2 we have this issue only if we tried to flash without repartitioning) ?

frapeti said:
Odin terminal emulator? What did you do exactly?
Odin is a PC software, Terminal Emulator is for Android and their functions are different
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
Google has mistranslated =(
Szaby59 said:
Here is a tutorial to fix this if you have a backup, this is for Galaxy Ace 2 but applies to this phone too even the partitons are the same: http://forum.xda-developers.com/showthread.php?t=2145464
You will need a backup from /modemfs folder or modemfs partition, if you don't have backups ask someone to make it for you.
Don't use backups from different models (i9070 vs. i9070p).
And the best if the other phone is from the same region/network like yours.
"If I put JB crashes on startup wizard"
Have you selected the pit file and repartition in odin when you flashed JB firmware ?
Click to expand...
Click to collapse
Unfortunately everyone has upgraded to JB and nobody has to give the modem GB.
They gave me the modem JB, can I use it?
The pit file with the rom JB was not included ... I did the repartitioning.

Not modem, modemfs, and it doesn't matter if the backup is from JB/GB but your phone is on GB/JB
I suggest to flash back first to a GB rom and if everything works try JB. (There is a "How to Go back to GB" thread)
Without PIT don't repartition the device, just follow the flashing instructions.

Szaby59 said:
Not modem, modemfs, and it doesn't matter if the backup is from JB/GB but your phone is on GB/JB
I suggest to flash back first to a GB rom and if everything works try JB. (There is a "How to Go back to GB" thread)
Without PIT don't repartition the device, just follow the flashing instructions.
Click to expand...
Click to collapse
Before I put the modemfs JB on GB, it worked perfectly, then I put the stock rom and I recovered the true baseband =)
NOW
If I try to flash jb or any other rom:
--Copyng media file:
E:Failed to mount /efs (Invalid argument)
--Appling multi csc
e: failed to mount /efs (Invalid argument)
e: multi_csc:Can't mount /efs
How can i fix it?

I have the same problem after an update with ODIN in PDA mode with a JB ROM from Russia. There is no baseband (displayed as Unknown) and no sinal. Tryed to put the old GB rom but it did not help.

evolution_x said:
I have the same problem after an update with ODIN in PDA mode with a JB ROM from Russia. There is no baseband (displayed as Unknown) and no sinal. Tryed to put the old GB rom but it did not help.
Click to expand...
Click to collapse
You happen to have solved?
I can use the phone with GB, but I always have the problem with the update.

evolution_x said:
I have the same problem after an update with ODIN in PDA mode with a JB ROM from Russia. There is no baseband (displayed as Unknown) and no sinal. Tryed to put the old GB rom but it did not help.
Click to expand...
Click to collapse
KiraHack said:
You happen to have solved?
I can use the phone with GB, but I always have the problem with the update.
Click to expand...
Click to collapse
Can either of you post a full system log in normal boot and recovery? Please include logcat and dmesg..
I do not respond to tech support via PM

No, my phone still does not work.

evolution_x said:
No, my phone still does not work.
Click to expand...
Click to collapse
If you can boot, you can make a log. Search "how to do logcat". And dmesg too.

shut_down said:
If you can boot, you can make a log. Search "how to do logcat". And dmesg too.
Click to expand...
Click to collapse
Ok, I will also try that.

Одг: JB Update /efs & baseband problem
evolution_x said:
Ok, I will also try that.
Click to expand...
Click to collapse
That is not solution. That is way to give developers idea what is going on with yor phone, and maybe help you.
Sent from Galaxy S Advance

shut_down said:
That is not solution. That is way to give developers idea what is going on with yor phone, and maybe help you.
Sent from Galaxy S Advance
Click to expand...
Click to collapse
I know but I am saying that I will try to make a logcat. I have installed aLogCat but it logs only the current operations, how can I log the boot ? or what log do you need?

here is a log file, I don't know if it contains what you need?

evolution_x said:
here is a log file, I don't know if it contains what you need?
Click to expand...
Click to collapse
I do not know to read it. Someone expirienced will tell you. Try with ADB logcat, open cmd, connect usb reboot phone and type
Code:
adb logcat > c:\logcat.txt
Wait some time when it boots, and you should get longer log. After some time just close cmd and open that file to see if it is bigger (it will be on your C drive named logcat.txt). Then attach it here.

shut_down said:
I do not know to read it. Someone expirienced will tell you. Try with ADB logcat, open cmd, connect usb reboot phone and type
Code:
adb logcat > c:\logcat.txt
Wait some time when it boots, and you should get longer log. After some time just close cmd and open that file to see if it is bigger (it will be on your C drive named logcat.txt). Then attach it here.
Click to expand...
Click to collapse
I think it's the same result with adb logcat > file, as with the aLogCat

Одг: JB Update /efs & baseband problem
evolution_x said:
I think it's the same result with adb logcat > file, as with the aLogCat
Click to expand...
Click to collapse
You did on boot? Not just from system, because it will not show much when nothing is happening. Put cable in phone, prepare command, reboot phone and tap enter on command in cmd when reboot starts.
Sent from Galaxy S Advance

[Q] Imei lost

hey guys i was using mu I9000 like i used to then i tried to use my second sim card i insert it i started the phone suddenly i was going in no network no data i removed and insert back the sim card nothing changes even with the old one and nothing is changed i diald the *#06# the emei was 00499***** i google it to find how to restore my emei i found a site that gives a code *2787...... or something like that and nothing changes just the emei became blank with no numbers on the screen i tryed to flash several times with odin and the stcok jvu firmware and i am always runing with the blank emei no after i flash the jvu stockrom i get a red message after flashing with odin done it says """" E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
E:check_selective_file:Can't mount /efs '''
and i also gone under root folder i found that the efs folder is empty i tried to upload my saved efs folder it says not enough space .... i tried with the efs backup pro it says can't mount .... please XDA's help me to resolve this f**** prob waiting for your help guys thnx a lot

i had the same problem , but i solved it by :
flash stock firmware via odin
root
flash CM9
flash JB rom
i don't know if that would work with you
good luck

well would you like please to give me links ??? please help and pressed the thnx button

choose a 2.3.6 firmware from this thread
http://forum.xda-developers.com/showthread.php?t=1102881
flash it via odin , root your build by chosing the right cf-root from this thread
http://forum.xda-developers.com/showthread.php?t=788108
if you have flashed for exemple JVU , you have to choose the right cf-root file ( for JVU build )
then flash cm 9 via recovery , download from here
http://get.cm/get/3Fb
then flash any costum rom you want from development section
good luck

The Tox said:
choose a 2.3.6 firmware from this thread
http://forum.xda-developers.com/showthread.php?t=1102881
flash it via odin , root your build by chosing the right cf-root from this thread
http://forum.xda-developers.com/showthread.php?t=788108
if you have flashed for exemple JVU , you have to choose the right cf-root file ( for JVU build )
then flash cm 9 via recovery , download from here
http://get.cm/get/3Fb
then flash any costum rom you want from development section
good luck
Click to expand...
Click to collapse
thank you so much downloading i'l give it a try and i'll let you know if it helps or not hope it will

please XDA's i'm getting this error STATUS7 installation aborted here is the log :
-- Installing: /sdcard/cm-9.1.0-galaxysmtd_2.zip
finding update package...
opening update package ...
installing update...
assert failed: run_program("/tmp/updater.sh")==0
E: error in /sdcard/cm-9.1.0-galaxysmtd_2.zip
(status 7)
installation aborted.
-------------------------- please help -----------------------

[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!

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