Hey guys,
I tried to install a Custom ROM on my Samsung Galaxy Note 3, but it failed pretty hard. After trying to reboot and gest stuck in a boot loop I now get several error messages in recovery mode:
Code:
# MANUAL MODE #
-- Applied the CSC-code : DBT
Successfully applied multi-CSC.
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
I also downloaded a Stock ROM from Sammobile, but it could not be installed via ODIN, I just got another "Fail"-Message. Here's the log:
Code:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005ZSUGOH3_N9005OZSGOH3_N9005ZSUGOH3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> cache.img.ext4
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What can I do to get back a running device? I would be fine with flashing another ROM and loosing data.. Just want a working device!
Lol...
Sent from my Galaxy Note8 using XDA Labs
= try fix the failed to mount cache issue, you have to go to recovery menu and mount system and then clear cache again. It will fix the issue.
how did you got out of this loop? would appreciate a fast reply
READ thread
JJEgan said:
READ thread
Click to expand...
Click to collapse
I cant go to my recovery either. I have a Samsung Tab A 10.5
Bootloader/download mode can only be acessed via recovery mode in this particular device and not by volume down and power key.
My issue is almost this same, but these lines keeps recurring before the tab finally runs out of battery. Same thing happens when I plug in the device. Not even the charging animation comes up.
I dont really know what's the issue :/
Issue is you are in the wrong forum this is NOTE 3 not tab .Not a clue as to what a Tab requires .
JJEgan said:
Issue is you are in the wrong forum this is NOTE 3 not tab .Not a clue as to what a Tab requires .
Click to expand...
Click to collapse
Appreciate your replies, but I searched everywhere this is the closest to my error, so I thought why not. Anyways, samsung care seems only the option as of now.
Did you fix this?
Related
I have problem in my P1000L
I make flash but error in screen tablet
<ID:0/087> Odin v.3 engine (ID:87)..
<ID:0/087> File analysis..
<ID:0/087> SetupConnection..
<ID:0/087> Initialzation..
<ID:0/087> Set PIT file..
<ID:0/087> DO NOT TURN OFF TARGET!!
<ID:0/087> Get PIT for mapping..
<ID:0/087> Firmware update start..
<ID:0/087> zImage
<ID:0/087> Sbl.bin
<ID:0/087> param.lfs
<ID:0/087> modem.bin
<ID:0/087> factoryfs.rfs
<ID:0/087> dbdata.rfs
<ID:0/087> cache.rfs
<ID:0/087> boot.bin
<ID:0/087> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/087> Removed!!
<ID:0/094> Added!!
csc : deleting /system/csc
csc : done.
Successfully installed packpage.
Updating filesystem...
E:failed to mount /efs (invalid argument)
E:discard_filesystem_for_rfs:Can't mount /efs
--wiping cache...
Formatting /cache...
Cache wipe failed.
--Updating applications...
E:failed to mount /preload (No such file or direcotry)
E:install_application_for_customer:Can´t mount /preload
your storage not prepared yet, please use UI menu for format and reboot actions.
copy application failed
Appling Multi-CSC...
E:failed to mount /efs (invalid argument)
E:multi_csc: Can´t mount /efs
What problem?:
turca said:
I have problem in my P1000L
I make flash but error in screen tablet
<ID:0/087> Odin v.3 engine (ID:87)..
<ID:0/087> File analysis..
<ID:0/087> SetupConnection..
<ID:0/087> Initialzation..
<ID:0/087> Set PIT file..
<ID:0/087> DO NOT TURN OFF TARGET!!
<ID:0/087> Get PIT for mapping..
<ID:0/087> Firmware update start..
<ID:0/087> zImage
<ID:0/087> Sbl.bin
<ID:0/087> param.lfs
<ID:0/087> modem.bin
<ID:0/087> factoryfs.rfs
<ID:0/087> dbdata.rfs
<ID:0/087> cache.rfs
<ID:0/087> boot.bin
<ID:0/087> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/087> Removed!!
<ID:0/094> Added!!
csc : deleting /system/csc
csc : done.
Successfully installed packpage.
Updating filesystem...
E:failed to mount /efs (invalid argument)
E:discard_filesystem_for_rfs:Can't mount /efs
--wiping cache...
Formatting /cache...
Cache wipe failed.
--Updating applications...
E:failed to mount /preload (No such file or direcotry)
E:install_application_for_customer:Can´t mount /preload
your storage not prepared yet, please use UI menu for format and reboot actions.
copy application failed
Appling Multi-CSC...
E:failed to mount /efs (invalid argument)
E:multi_csc: Can´t mount /efs
What problem?:
Click to expand...
Click to collapse
There solution to this problem
Which rom did you flash? Which options did you check in Odin?
Sent from my GT-P1000L using XDA
Dear Gentlemen,
Good afternoon.
I have received a GT-S5360 phone which is stuck in a bootloop and I am trying to solve the problem.
I have tried most of the solutions I was able to find here in xda but I did not succeed.
The status of the device:
1- It has the stock ROM and Kernel (untouched, unrooted).
2- I can access the recovery mode and the download mode without any problem.
3- The PC and the ODIN can recognize the device.
4- I am having the proper ODIN driver on my PC.
5- I do not have kies installed on my PC.
6- I am using win7 Pro 32-bit.
7- Antivirus and Firewall were disabled completely during flashing.
Solutions I have tried:
1- Wipe Cache: completed successfully - but did not solve the problem.
2- Wipe data / factory reset: Completed successfully: did not solve the problem.
3- Trying to install a custom ROM from SD card through recovery mode: I have got the following error message:
E: Error in /tmp/sideload/package.zip (status 2). Installation aborted.
The after pressing "reboot", I have got the following before the device reboots:
Format failed on /dev/stl11
Formatting /cache...
e:format_volume: rfs format failed on /dev/stl10
Cache wipe complte.
E: failed to mount /data (Invalid argument)
E:copy_log_files_to_data:: can't mount /dataRebooting
4- Downloaded the ODIN Stock Galaxy Y S5360 flashable firmware packages from Doky73 thread here ..
the flashing completed successfully using ODIN but the problem remains the same (infinite bootloop).
5- Downloaded a single-file stock ROM from Samsung forums (sammobile.com) (.tar.md5) and flashed it successully using ODIN but it did not solve the problem.
6- Downloaded the suitable .pit package and repeated step 4 and 5 but with re-partition selected and the .pit file added it gives me "fail". please find below the message for the status:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_JPLG1.tar.md5 is valid.
<OSM> MODEM_S5360_XXLF3.tar.md5 is valid.
<OSM> CSC_S5360_OJPLG1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> param.lfs
<ID:0/003> system.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried to change the USB cable, and used another PC, but it did not work.
I have repeated the above ODIN flashing using odin v1.83, v1.85, and using v3.7 but it did not work in any.
do you have any ideas guys?
Appreciating your kind support.
whyomax said:
Dear Gentlemen,
Good afternoon.
I have received a GT-S5360 phone which is stuck in a bootloop and I am trying to solve the problem.
I have tried most of the solutions I was able to find here in xda but I did not succeed.
The status of the device:
1- It has the stock ROM and Kernel (untouched, unrooted).
2- I can access the recovery mode and the download mode without any problem.
3- The PC and the ODIN can recognize the device.
4- I am having the proper ODIN driver on my PC.
5- I do not have kies installed on my PC.
6- I am using win7 Pro 32-bit.
7- Antivirus and Firewall were disabled completely during flashing.
Solutions I have tried:
1- Wipe Cache: completed successfully - but did not solve the problem.
2- Wipe data / factory reset: Completed successfully: did not solve the problem.
3- Trying to install a custom ROM from SD card through recovery mode: I have got the following error message:
E: Error in /tmp/sideload/package.zip (status 2). Installation aborted.
The after pressing "reboot", I have got the following before the device reboots:
Format failed on /dev/stl11
Formatting /cache...
e:format_volume: rfs format failed on /dev/stl10
Cache wipe complte.
E: failed to mount /data (Invalid argument)
E:copy_log_files_to_data:: can't mount /dataRebooting
4- Downloaded the ODIN Stock Galaxy Y S5360 flashable firmware packages from Doky73 thread here ..
the flashing completed successfully using ODIN but the problem remains the same (infinite bootloop).
5- Downloaded a single-file stock ROM from Samsung forums (sammobile.com) (.tar.md5) and flashed it successully using ODIN but it did not solve the problem.
6- Downloaded the suitable .pit package and repeated step 4 and 5 but with re-partition selected and the .pit file added it gives me "fail". please find below the message for the status:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S5360_JPLG1.tar.md5 is valid.
<OSM> MODEM_S5360_XXLF3.tar.md5 is valid.
<OSM> CSC_S5360_OJPLG1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> param.lfs
<ID:0/003> system.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried to change the USB cable, and used another PC, but it did not work.
I have repeated the above ODIN flashing using odin v1.83, v1.85, and using v3.7 but it did not work in any.
do you have any ideas guys?
Appreciating your kind support.
Click to expand...
Click to collapse
flash through odin a firmware with pit and bootloader.
download it from http://d-h.st/PF5
press thanks if i helped
Thanks my friend.
I have solved the problem by using a rear USB port in a desktop PC.
All the best
hello. Such problems are also afoot in samsung galaxy y me, what's the solution, you can correct phone back, please let me know, thank
blackbeard said:
flash through odin a firmware with pit and bootloader.
download it from
press thanks if i helped
Click to expand...
Click to collapse
Many Thanks blackbeard. This solved my problem....
please update the download link sir.....:crying:
blackbeard said:
flash through odin a firmware with pit and bootloader.
download it from
press thanks if i helped
Click to expand...
Click to collapse
thanks bro, it solve the /data mount problem.
but now my smartphone continously restarting when it open an apps.
i was reinstall using custom rom via recovery mode, but still keep restarting
are you know why?
Just Asking
I want to ask which category each file is placed. Sorry because I am just a beginner at this. Thanks.
Arkonite said:
I want to ask which category each file is placed. Sorry because I am just a beginner at this. Thanks.
Click to expand...
Click to collapse
If you are taking about flashing stock rom via odin read my firmware thread - Link in signature
+1
blackbeard said:
flash through odin a firmware with pit and bootloader.
download it from http://d-h.st/PF5
press thanks if i helped
Click to expand...
Click to collapse
THIS IS IT! Solved in an eye blink! I had always thought that the repartitioning option in Odin was satanic or something, but well, as soon as I entered the PIT file, repartition got checked itself. I clicked start, and voila. Phone's good as new.
---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
juicided said:
thanks bro, it solve the /data mount problem.
but now my smartphone continously restarting when it open an apps.
i was reinstall using custom rom via recovery mode, but still keep restarting
are you know why?
Click to expand...
Click to collapse
You need to flash stock ROM using Odin, again.
Hi guys,
I was running MH8 and attempted root in order to install the Google Edition ROM but now I can't get into my phone at all. I have tried flashing the original MH8 ROM with odin and it fails. It appears it's having issues mounting /system. I can get into download mode and I can flash philz and I've tried formatting all partitions but it's still not working. This is the code from Odin:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> persdata.img.ext4
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have also tried flashing using a PIT file from here with the stock ROM and this is the code that odin returns:
Code:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> sbl3.mbn
<ID:0/006> rpm.mbn
<ID:0/006> aboot.mbn
<ID:0/006> tz.mbn
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> persdata.img.ext4
<ID:0/006> system.img.ext4
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help me!!! I'm desperate to get my phone working again... Many thanks in advance!!
I have loaded TWRP... When I try a factory reset it comes up with this error: E:Unable to mount '/system'
Is there some way of reloading /system?
Try this link.
http://m.ibtimes.co.uk/samsung-galaxys4-gti9500-gti9505-unbrick-softbrick-hardbrick-469557.html
Method three helped me personally.
Verstuurd van mijn GT-I9505 met Tapatalk
r2go said:
Try this link.
http://m.ibtimes.co.uk/samsung-galaxys4-gti9500-gti9505-unbrick-softbrick-hardbrick-469557.html
Method three helped me personally.
Verstuurd van mijn GT-I9505 met Tapatalk
Click to expand...
Click to collapse
Thanks for your help... I fixed it by formatting system a few times then I was able to mount it... phew!
All you had to do was boot into stock recovery after flashing MH8 and perform a factory reset. Easy
Sent from my GT-I9505 using XDA Premium HD app
MH8 has know security mate ;;;;
you cant switch to some other ROMs or downgrade (STUCK)
reflash MH8 firmware and do a wipe from RECOVERY(STOCK)
hope it works
I know MH8 has some new security... I was able to flash the Google Edition from TWRP recovery but now I wan't to go back to stock.
Unfortunately, when I try and flash stock Mh8 from odin, I'm back to the issue of odin failing at the system.img.ext4
Have you guys got any other suggestions? This is driving me crazy!
arnob_xperia said:
MH8 has know security mate ;;;;
you cant switch to some other ROMs or downgrade (STUCK)
reflash MH8 firmware and do a wipe from RECOVERY(STOCK)
hope it works
Click to expand...
Click to collapse
Same issue in odin... I don't understand why it's failing
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I flashed the MH8 kernel successfully and was able to boot into the stock recovery but it shows the following error messages under the recovery menu selection:
E:failed to mount /system (Invalid argument)
# MANUAL MODE #
-- Applying Multi-CSC...
E:failed to mount /system (Invalid argument)
can't mount '/system' (Invalid argument)
E:failed to mount /system (Invalid argument)
I am completely lost and have no idea what to do... I'm now trying to download DBT-I9505XXUDMH5-20130905095145.zip and will try flashing that...
Does anyone know of faster links to download the stock roms?
gyrex said:
I flashed the MH8 kernel successfully and was able to boot into the stock recovery but it shows the following error messages under the recovery menu selection:
E:failed to mount /system (Invalid argument)
# MANUAL MODE #
-- Applying Multi-CSC...
E:failed to mount /system (Invalid argument)
can't mount '/system' (Invalid argument)
E:failed to mount /system (Invalid argument)
I am completely lost and have no idea what to do... I'm now trying to download DBT-I9505XXUDMH5-20130905095145.zip and will try flashing that...
Does anyone know of faster links to download the stock roms?
Click to expand...
Click to collapse
go to recovery.. wipe everthing including /system
then flash firmware
I've tried this but still no joy...
arnob_xperia said:
go to recovery.. wipe everthing including /system
then flash firmware
Click to expand...
Click to collapse
I have tried using a PIT file and that doesn't work either. Do I need an updated PIT file for MH8?
Code:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/005> Added!!
<ID:0/005> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> persdata.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Ok, I'm seriously at my wits end now and I'm willing to try anything. What does NAND erase do? Is there something drastic I can do?
OK, I think I've figured out what was wrong.
I was previously attempting to use odin on my macbook with vmware fusion. Previously, this had worked flawlessly previously and I never had an issue.
I installed bootcamp and Windows 7 x64 and attempted to flash with odin and it's worked. I have no idea what's changed because as I said, vmware fusion worked perfectly previously. I don't know if this has something to do with KNOX or not? Very strange but I'm just so relieved that I've finally got my phone back after probably 36+ hours of troubleshooting...
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUDMH5_I9505OXADMH5_I9505XXUDMH5_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
Im in download mode when odin failed.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It says do not turn off target !!
It it safe to turn it off in this case and solve the problem?
Yea, it already failed, it's safe to unplug
*Detection* said:
Yea, it already failed, it's safe to unplug
Click to expand...
Click to collapse
Safe to reboot as well?
xs34 said:
Safe to reboot as well?
Click to expand...
Click to collapse
Yea, safe to use your phone as normal
ODIN failed, so it made no changes to your phone
Thank you for your fast reply. I have now succesfully finished my work
For those with the same problem with odin, please reboot like I did and disable reactivation lock (if thats a proper translate). You can find it under security, close to the setting find my device
<id:0/004> fail!
Hi Everyone!
This is my 1st post in any fourms ever. I always get solutions by searching, but i guess am umable to find a correct solution for this . Am hoping if someone could re-direct me to fix my phone.
Issue:
My screen is stuck on the boot screen ( Galaxy Note 2 N7100 - screen). It doesnt go further.
Background:
I was using Diamond ROM for quite a long time. I have no clue, last night i was talking to someone and later i kept my phone in pocket and since then its stuck on that screen. I am not sure what happened or what caused it
I am using Philz Recovery, but when am booting to it
it has the below Error:
PhilX Touch 6.26.6
Clockworkmod v6.0.4.8
E:Could not mount /data to setup /data/media path!
E:Can't mount /cache/recovery/command
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
I Tried everything possible (restarted may times, tried to wipe off the cache - it was not wiping)
Then i thought to reinstall PhilZ.
WHen i went to the download recovery on my phone and connected to odin v3.09 (which i used last time when installing custom ROM and it worked) phone is getting added.
But when i select AP to the PhilZ recovery file (philz_touch_6.26.6-n7100.tar.md5) and click on Start it is giving me error and it failed
Error:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.26.6-n7100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Someone Please Help me
Heya, so after a failed attempt to root my Samsung Galaxy S5 Verizon (G00V) I soft-bricked it. I have been following a lot of guides on the internet but, so far they haven't worked (I don't know if I didn't have the right software or if I wasn't doing it correctly). I still have access to recovery mode and my PC can detect it. I already have Odin and Samsung USB drivers. If I try to install the stock ROM on Odin I get this:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Next I tried installing the software over SD card from recovery mode, but got this:
Supported API: 3
#MANUAL MODE#
-- Appling Multi-CSC...
Applied the CSC-code : VZW
Successfully applied multi-CSC.
-- Install /sdcard/G900VVRU1BOA8_G900VVZW1BOA8_G900VVRU1BOA8_HOME.tar.md5
Finding update package...
Opening update package...
E:failed to map file
Installation aborted.
Please help!
ThatDemonDavid said:
Heya, so after a failed attempt to root my Samsung Galaxy S5 Verizon (G00V) I soft-bricked it. I have been following a lot of guides on the internet but, so far they haven't worked (I don't know if I didn't have the right software or if I wasn't doing it correctly). I still have access to recovery mode and my PC can detect it. I already have Odin and Samsung USB drivers. If I try to install the stock ROM on Odin I get this:
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Next I tried installing the software over SD card from recovery mode, but got this:
Supported API: 3
#MANUAL MODE#
-- Appling Multi-CSC...
Applied the CSC-code : VZW
Successfully applied multi-CSC.
-- Install /sdcard/G900VVRU1BOA8_G900VVZW1BOA8_G900VVRU1BOA8_HOME.tar.md5
Finding update package...
Opening update package...
E:failed to map file
Installation aborted.
Please help!
Click to expand...
Click to collapse
Use this method Jrkruse ok3 root on XDA developers under s5 verizon section here is the link
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370/page1
You might be able to get bootloader unlock also if you have a Samsung 15 Emmc
Go to this thread
http://forum.xda-developers.com/ver...nlocking-galaxys-s5-bootloader-t3337909/page1
Sent from my SM-G900V using Tapatalk
[email protected] said:
Use this method Jrkruse ok3 root on XDA developers under s5 verizon section here is the link
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370/page1
You might be able to get bootloader unlock also if you have a Samsung 15 Emmc
Go to this thread
http://forum.xda-developers.com/ver...nlocking-galaxys-s5-bootloader-t3337909/page1
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
That didn't help. My phone is still soft-bricked.
To undo soft brick in Odin flash firmware you are currently on
this shouldnt cause any data loss
download firmware from sammobile . Com
to check which firmware you are on boot into recovery and look at what it tells you this is your firmware you are currently on
[email protected] said:
To undo soft brick in Odin flash firmware you are currently on
this shouldnt cause any data loss
download firmware from sammobile . Com
to check which firmware you are on boot into recovery and look at what it tells you this is your firmware you are currently on
Click to expand...
Click to collapse
'
Thank you so much!!! :good: