Repairing the A6 after installing unsuitable recovery.tar - Samsung Galaxy A6 Questions & Answers

#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

Related

[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] Odin stuck on "data.img" i can not flash a firmware and Note Semi Died (Help)

[Q] Odin stuck on "data.img" i can not flash a firmware and Note Semi Died (Help)
Hi Guys,
I hope someone can help me, I accidentally interrupted a factory resect and from this moment I can not flash with Odin .. in detail ....
I can do:
1a I can successfully flash a firmware with Odin with only one file
2a I can successfully flash a kernel with Odin
3a I can go to recovery, any, either Samsung or CWM 3E recovery if i flash to CF-Root Kernel
4a I recorey files from flash, cooked and kernels.
I can not do:
1b I can not flash with success with Odin firrmware with more file and Pit, Odin stuck on "data.img"
2b I can not restore a backup nandroid, because I get I get the following errors:
Error while restoring / date!
E: Can not open / chace / recovery / log
E: Can not open / chace / recovery / log
E: Can not open / chace / recovery / last _log
E: Can not open / chace / recovery / last _log
3b I can not load the system, i can not turn on the Notes, only sometimes into Boot loop and other time stuck on written "Notes Galaxy Samsung GT-N7000"
Other problems:
- If I make the point 1a after the phone sometimes goes directly into Boot loop, other time go to 3E Samsung recovery and I get the following errors:
"And: failed to mount / data (Unknown error: 0)"
"E: install_application_for_customer: Can not mount / data"
"Your storage not prepared yet. Please use UI menus for format and reboot actions."
"copy application failed"
Even doing a full wipe, restarting the Notes, remain on "Notes Samsung Galaxy GT-N7000"
- If I make the point 4a flashing cooked, the flash apparently successfully, but at reboot Note stuck on written "Notes Galaxy Samsung GT-N7000"
I'm desperate, I do not know what else to do to revive my Note...
I hope someone can help me...
Really Thanks
Ps. Sorry for my bad English
Try this,
download abyssnote 3.9 kernal and put it on external sdcard somehow (maybe by taking the sd card out and using a card reader.
boot into recovery, flash the abyss note kernal, go to advanced in recovery and reboot recovery,
now try restoring the nandroid backup u have.
See if this helps..
Edit: or you can download a stock firmware in .tar format, put it in PDA(in odin) see if it flashes successfully,
you can use the firmware in this post, download the three files from mirror 2 and read instruction to join them, and flash it in Odin PC
http://forum.xda-developers.com/showpost.php?p=18981227&postcount=4
Hi dead-angel
thanks for your answer and for your help..
i had flash abyss 3.9 (RedPill Recovery) and after i make restore of nandroid backup but nothing of good..
the restore was interrupted and i get this error:
Error while restoring / date!
E: Error in / chace / recovery / log
(read-Only file system)
i wanna also try your second suggestion, but some link are not available
anyway i have just tryed so many time to flash with odin I can successfully flash a firmware with Odin with only one file the phone sometimes goes directly into Boot loop, other time go to 3E Samsung recovery and I get the following errors:
"And: failed to mount / data (Unknown error: 0)"
"E: install_application_for_customer: Can not mount / data"
"Your storage not prepared yet. Please use UI menus for format and reboot actions."
"copy application failed"
Even doing a full wipe, restarting the Notes, remain on "Notes Samsung Galaxy
GT-N7000"
while I can not flash a firmware with success with Odin and more file and Pit, Odin stuck on "data.img"
frustrating situation
Your Welcome
Try the mediafire links from that second suggestion, Im sure they work, and that shows up as single file in Odin, It should flash if single file fashing works in your PC odin
If mediafire is blocked in your country or by your ISP, try any Proxy bypass site to access the mediafire.
Best of luck mate
Ok, thanks Again Angel
im downloading the file, but are so slow, over 2 hour to get it, i wait
i dont understood this step:
- Tool to join them, run the following file and locate the .001 file.
sorry but English sometime for me is difficult
can you explain me better what i must to do?
Thanks
I m pm you same file, u need not to join
Edit : sent you
Sent from my GT-N7000 using xda premium
Download Tool to join from that post and rest is explained in the attached image
This is xda
Believe how someone caring
Sent from my GT-N7000 using xda premium
Really really really thanks dead-angel & dr.ketan for yours help and your kindness
i make it , but nothing , the phone stuck on written "Notes Galaxy Samsung GT-N7000" and go in Loop on it, dont load boot animation and also do not load a system
As you said now u can enter recovery, so did u wipe cache n qipe off data?
Sent from my GT-N7000 using xda premium
now im in recovery and i making wipe data but is stuck strangely on "Formatting data" do not go ahead
i dont know now what i must to do
this problem was coming when i interrupted a data factory reset, i think cant interrupted another time it
Keep patience.
at least leave it for 15-20 min
Sent from my GT-N7000 using xda premium
ok, i wait
but it so strange, never i get stuck on "formatting data"for all tihis time, have passed more than 20 minute.....
EDIT: ok, now is finished, i repeat another time and was more fast, but when i tryed to reboot the Note is stuck on written "Notes Galaxy Samsung GT-N7000" and go in Loop on it
but i see one good thing, maybe..
now i do not get error when i go in 3Erecovery Samsung, before I received this error:
"And: failed to mount / data (Unknown error: 0)"
"E: install_application_for_customer: Can not mount / data"
"Your storage not prepared yet. Please use UI menus for format and reboot actions."
"copy application failed"
but now i get any error, all seems good but do not load the boot animation and do not load the system
bro, i having the same problem with u, want to check with u. want to check with you is your problem fixed?
tanoxxx said:
ok, i wait
but it so strange, never i get stuck on "formatting data"for all tihis time, have passed more than 20 minute.....
EDIT: ok, now is finished, i repeat another time and was more fast, but when i tryed to reboot the Note is stuck on written "Notes Galaxy Samsung GT-N7000" and go in Loop on it
but i see one good thing, maybe..
now i do not get error when i go in 3Erecovery Samsung, before I received this error:
"And: failed to mount / data (Unknown error: 0)"
"E: install_application_for_customer: Can not mount / data"
"Your storage not prepared yet. Please use UI menus for format and reboot actions."
"copy application failed"
but now i get any error, all seems good but do not load the boot animation and do not load the system
Click to expand...
Click to collapse
Hi chris85e
im sad to see you with my same problem
untill now no Fix
reflash the bootloader see my signature then flash rom in odin
hi antiguangenius
Thanks for your answer
i must put it in PDA like is write in your guide or i must to put it in bootloader section?
EDTI: Guys sorry but i finished my daily thanks i will make it
Really thanks Guys for your help and answers
Having same problem...
Don't know what to do...
tanoxxx said:
hi antiguangenius
i must put it in PDA like is write in your guide or i must to put it in bootloader section?
Click to expand...
Click to collapse
Nothing
i had tryed put bootloader in PDA and after i flashed with odin a firwmare stock with one file, flash successfully, but after the Note stuck on written "Notes Galaxy Samsung GT-N7000" and go in Loop on it
while if i flash with Odin firrmware with more file and Pit, Odin stuck always on "data.img"
Hello everyone
I am having a similar problem: I wanted to downgrade my Note to stock GB because I lost root on an ICS leak. I have done this successfully before but today pc odin suddenly hangs in the middle of flashing the factoryfs.img of a stock kernel (I used this one but tried others as well: N7000XXKJ4_N7000VD2KJ1_N7000XXKJ4_HOME.tar.md5).
Because of this I can now only boot the phone into download mode. I have also tried to use a pit file (as you can see in the screenshot, where I used this file: Q1_20110914_16GB.pit), because I thought the partitions might have been corrupted or changed by the ICS ROM but this didn't help either.
Do you have experienced this before? What else could I try?
Thanks a lot for any help
suxi
Edit: I have tried this (quote below)from a different post and odin still hangs after the first 1mm of factoryfs.img flashing
http://hotfile.com/dl/141060546/b0c7...1_OXA.rar.html
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.m d5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
Click to expand...
Click to collapse

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

No booting at all!

I tryed to flash the modem file cause my wifi wasnt working, and I must have done something wrong cause I cannot boot anything anymore get stock to firmware upgrade encountered! Im on 4.4.2 and I got a sgh-i537 active. I got this to flash with odin SGH-I537UCUCNE3_v4.4.2_ATT_ALL but It doesnt work, I tried 2400258.cfg changed it to update.zip and it doesnt work either! I dont know what to do now! I got a back up with TWRP but how can I use it? I can upload with odin the Bl file and CP file but the AP and CSC doesnt work! After that I get the samsung logo with a black screen after that! Cant get into recovery mode now!
Choquette said:
I tryed to flash the modem file cause my wifi wasnt working, and I must have done something wrong cause I cannot boot anything anymore get stock to firmware upgrade encountered! Im on 4.4.2 and I got a sgh-i537 active. I got this to flash with odin SGH-I537UCUCNE3_v4.4.2_ATT_ALL but It doesnt work, I tried 2400258.cfg changed it to update.zip and it doesnt work either! I dont know what to do now! I got a back up with TWRP but how can I use it? I can upload with odin the Bl file and CP file but the AP and CSC doesnt work! After that I get the samsung logo with a black screen after that! Cant get into recovery mode now!
Click to expand...
Click to collapse
Any help?
help me please!
Choquette said:
help me please!
Click to expand...
Click to collapse
It sounds like you have a bad download. I would redownload it, made sure the MD5's match, and try again.
Devo7v said:
It sounds like you have a bad download. I would redownload it, made sure the MD5's match, and try again.
Click to expand...
Click to collapse
I can flash the BL file (BL_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5) the CP file (CP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5) and the CSC file (CSC_ATT_I537ATTCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5)
When I'm trying to flash the CSC file after I flashed the BL and CP it always fails. After that I reboot the phone and I can flash the CSC file!
but not the AP file (AP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5) Why? WHen I flash the CSC file I can get into recovery mode but it looks like it tries to install a package cause at the bottom tof the screen it got an install message like this
-- Installing package...
E:failed to mount /system (invalid argument)
E:int main(int, char**) :: can't mount /systemE:failed to mo
unt /system (invalid argument)
Choquette said:
I can flash the BL file (BL_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5) the CP file (CP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5) and the CSC file (CSC_ATT_I537ATTCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5)
When I'm trying to flash the CSC file after I flashed the BL and CP it always fails. After that I reboot the phone and I can flash the CSC file!
but not the AP file (AP_I537UCUCNE3_987011_REV06_user_low_ship_MULTI_CERT.tar.md5) Why? WHen I flash the CSC file I can get into recovery mode but it looks like it tries to install a package cause at the bottom tof the screen it got an install message like this
-- Installing package...
E:failed to mount /system (invalid argument)
E:int main(int, char**) :: can't mount /systemE:failed to mo
unt /system (invalid argument)
Click to expand...
Click to collapse
Does the MD5 of the file you downloaded match the MD5 posted in the thread?
Are you using the usb cable that came with the phone?
What version of Odin are you using? Have you tried using a different version of Odin?
Are you flashing the files individually or ask at once?
Devo7v said:
Does the MD5 of the file you downloaded match the MD5 posted in the thread? Yes It all matches
Are you using the usb cable that came with the phone? Yes
What version of Odin are you using? Odin3 v3.07 Have you tried using a different version of Odin? Yes 3.09
Are you flashing the files individually or ask at once?
Click to expand...
Click to collapse
Tried both
Now when I try to flash via my mini sd I get this message
Installing update...
file_getprop: failed to stat ''/system/build.prop'' : No such file or directory
E:Error in /tmp/sideload/package.zip
(status 7)
I had a backup in TWRP but I dunnot know how to use it since I cannot pass the splash screen or the Recovery mode when I successfully flash the CSC file!
Choquette said:
Now when I try to flash via my mini sd I get this message
Installing update...
file_getprop: failed to stat ''/system/build.prop'' : No such file or directory
E:Error in /tmp/sideload/package.zip
(status 7)
I had a backup in TWRP but I dunnot know how to use it since I cannot pass the splash screen or the Recovery mode when I successfully flash the CSC file!
Click to expand...
Click to collapse
You're not going to be able to flash this through stock recovery, it is an Odin package. I honestly don't know what else to do.
Open Odin, load all 4 files and hit run. If it fails, post the Odin log. I'll see if I can find anything.
Devo7v said:
You're not going to be able to flash this through stock recovery, it is an Odin package. I honestly don't know what else to do.
Open Odin, load all 4 files and hit run. If it fails, post the Odin log. I'll see if I can find anything.
Click to expand...
Click to collapse
Well Thank you! Dont know why but I tried all 4 files this time again and it worked! lol Thanks again!

(Help) Note 5 stock in restore mode loop. Odin passes

Hello,
I have been trying to fix a friends t-mobile phone (note 5), he got it from ebaya, dumb i know. It seems like it was rooted because it wouldn't make calls and had super user. I loaded the official latest software via odin and only made it worse, wont even load to OS now.
I have loaded several SWs to try and restore (using odin)
these are the SWs i tried
N920TUVU1AOGE_N920TTMB1AOGE_N920TUVU1AOGE_HOME.tar (.CM fail) original note 5 tmobile sw.
N920TUVU1BOH4_N920TTMB1BOH4_N920TUVU1BOH4_HOME.tar (.CM fail) revision, still official.
N920TUVU2DPD1_N920TTMB2DPD1_N920TUVU2DPD1_HOME.tar (pass) latest official
Odin gives me a consistent pass with official N920TUVU2DPD1_N920TTMB2DPD1_N920TUVU2DPD1_HOME software
It keeps rebooting into recovery mode,
Tried doing a wipe from recovery mode. Error - (Failed to mount /preload (no such file or directory)
Every time the device loads into recovery mode it shows error...
"dm-verity verification failed...
need to check drk first..."
I dont know what to do, knox shows 0x0
used different PCs
different cords
different odins
i must have installed it a dozen times, i even removed the cache file and re packaged the .tar any help would be fantastic.
westsidekino said:
Hello,
I have been trying to fix a friends t-mobile phone (note 5), he got it from ebaya, dumb i know. It seems like it was rooted because it wouldn't make calls and had super user. I loaded the official latest software via odin and only made it worse, wont even load to OS now.
I have loaded several SWs to try and restore (using odin)
these are the SWs i tried
N920TUVU1AOGE_N920TTMB1AOGE_N920TUVU1AOGE_HOME.tar (.CM fail) original note 5 tmobile sw.
N920TUVU1BOH4_N920TTMB1BOH4_N920TUVU1BOH4_HOME.tar (.CM fail) revision, still official.
N920TUVU2DPD1_N920TTMB2DPD1_N920TUVU2DPD1_HOME.tar (pass) latest official
Odin gives me a consistent pass with official N920TUVU2DPD1_N920TTMB2DPD1_N920TUVU2DPD1_HOME software
It keeps rebooting into recovery mode,
Tried doing a wipe from recovery mode. Error - (Failed to mount /preload (no such file or directory)
Every time the device loads into recovery mode it shows error...
"dm-verity verification failed...
need to check drk first..."
I dont know what to do, knox shows 0x0
used different PCs
different cords
different odins
i must have installed it a dozen times, i even removed the cache file and re packaged the .tar any help would be fantastic.
Click to expand...
Click to collapse
Maybe try using the PIT file to do repartitioning of the partitions? Which recovery is on it?
MrMike2182 said:
Maybe try using the PIT file to do repartitioning of the partitions? Which recovery is on it?
Click to expand...
Click to collapse
I can try that, can you recommend a tutorial on how to do it for the note 5?
westsidekino said:
I can try that, can you recommend a tutorial on how to do it for the note 5?
Click to expand...
Click to collapse
Since you said it was already rooted, why don't you go to the T-Mobile thread download and flash one of the Roms and kernels they have instead of trying to flash stock?

Categories

Resources