My S3 remains in Logo Screen. So i tried in recovery mode the option "wipe data/factory reset" and "wipe cache partitions". After reboot, the phone still hangs on Logo screen. In recovery mode i see this errors:
e:failed to mount /system (invalid argument)
e:failed to mount /efs (invalid argument)
so i tried to flash the phone with odin. I am from switzerland and took 1-part firmware AUT-I9300XXEMB1. The phone is recognized by ODIN. The drivers are also installed. Choose "Auto Reboot" and "F.Reset Time". But i get this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXEMB1_I9300AUTEMA1_I9300XXEMB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried with a 3-part firmware with a pit file and option "Re-Partition". Same Problem. Breaks after "Get PIT for mapping". The phone has never been rootet and the usb is not in debug-mode.
Can someone tell me what i am doing wrong? Thanks a lot.
Reads to me as you have damaged the partition .
a pit file and option "Re-Partition">>> why on earth you did that as its the quickest way to brick
By the looks of it
His nand was already dead before he did it ...
Turn it to service center
Sent From My Galaxy S III Using XDA Premium 4
So there is no possibility to fix? only service? i have no warranty.
i also tought that the problem is the partition, so i chose the option "Re-Partition" with a pit file (i read pit file is nessecary for Re-Partition).
i never tried to flash the phone. The Loop on Samsung Logo starts after a update made by phone.
Ask Samsung if it is covered under the 24 months warranty .
Do not mention that you have played about with PIT .
the errors in recover mode
e:failed to mount /system (invalid argument)
e:failed to mount /efs (invalid argument)
have been shown before i played around with the pit.
Is it possible that the partition have been demaged during the update process made by the phone?
As said in post
>>>
By the looks of it
His nand was already dead before he did it ...<<<
If it was not already dead then you killed it .,
i think odin never starts writting anything on the device.
when i go in downloading mode i see:
custom binary download : no
current binary: Samsung official
system status : official
so everthing is official.
it always stoped at
<ID:0/004> Get PIT for mapping..
and didnt start writting.
i checked now warranty status and i have still warranty .....
its not my phone, and the owner told me there was no warranty.
So i loose 4 hours of my life trying to flash
Its possible the previous owner voided warranty. Worth sending in though. Previous owner may just be wrong
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
Related
I have a Samsung Galaxy Player 5.0 US Model YP-G70. I flashed to a newer version of CWM touch recovery 6.0.4.4. Upon completing the flash the screen confirmed that the flash was successful. I then rebooted my Samsung Galaxy Player. Then it entered the boot loop mode being me to the samsung logo and straight into the CWM Recovery and it displayed this error
"
E:Can't mount /cache/recovery/log E:Can't open /cache/recovery/log E:Can't mount /cache/recovery/last_log E:Can't open /cache/recovery/last_log
"
I then tried to to wipe cache partition, wipe dalvik cache none of that worked for me I got the same error as before that popped up on my screen, even after I rebooted the device I still get the error message.
So I did a data/factory reset. It didn't work and I got the error "E:Can't mount /cache/recovery/log E:Can't open /cache/recovery/log E:Can't mount /cache/recovery/last_log E:Can't open /cache/recovery/last_log" It doesn't let me restore my nandroid backup or let me update using files/zip from my internal sd card but my external sd card work.
I used odin two times (each time using the same files) and flashed the stock rom, the stock kernel, and the stock pit file and it doesn't successfully completed the task.
This is the message I received
This is version odin3 v1.82
"
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ueki8_min.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> factoryfs.rfs
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
"
This is odin3 v3.07
"
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ueki8_min.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> __Xmit Write fail
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
"
I believe my internal sd card can't be mounted or isn't mounted? Or my CWM recovery is corrupted resulting in this consist reboot taking me back into recovery each time with this error. Can anyone brings together ideas or advice on how to fix this problem? (Device can't be powered off completely by power off option on cwm recovery or by manually pressing the power off button located on the top right hand side of the device., my device will power off for a second and turn back on by itself and reboot me back into the loop which takes to back into CWM recovery menu with the error listed above. Also the download mode screen is off by a couple of inches meaning it's kinda misplaced on the screen) Any Fixes / Update / Patches / Recovery / Mods to solve this error?
I'm trying to figure out how to get cwm on to my 5.0 could you link to any threads?
marcdman4000 said:
I'm trying to figure out how to get cwm on to my 5.0 could you link to any threads?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1445840
When I turn on my Samsung Galaxy Ace GT-S5830i, it gets stuck at "Samsung GALAXY Ace GT-S5830i" intro logo, whatever. It won't load, it can just stay like that until the battery goes off.
I'm able to start the Recovery Mode luckily using "Home Button + Volume up + Power Button", but it shows this code:
Code:
-- Appling Multi-CSC --
E:failed to mount /system (Inval
id argument)
E:failed to mount /system (Inval
id argument)
Tried to format /system, doesn't work, neither with ClockworkMod Recovery (every possible versions), it shows this:
Code:
Formatting /system...
Error mounting /system!
Skipping format...
Done.
Also, I tried with Odin3 v1.84/v1.87, and still it won't work. I applied all good, but when I connect my phone to my computer using the USB cable, and it shows it normally, but when I "Start" the process, it read everything valid and it gets stuck at:
Code:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
This is the full log of Odin3:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.md5 is valid.
<OSM> PDA_S5830IXXLA4_REV00.tar.md5 is valid.
<OSM> MODEM_S5830iXXLA2_REV00.tar.md5 is valid.
<OSM> GT-S5830i-MULTI-CSC-OXXLA2.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..
When I turn off the phone or unplug the USB cable it shows:
Code:
^^ ...
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I tried with multiple USB cables, same thing happening.
Also, one more thing. When I try to format and mount /data and /cache, both ends successfully.
Format /data log:
Code:
Formatting /data...
Done.
Format /cache log:
Code:
Formatting /cache...
Done.
So I'm asking for help. Is there any possibility to repair my phone MYSELF? Is there a way to successfully format and mount /system? What should I do? If there are ways to solve this problem, and by that I need to download needed files, please send the link!
Please response ASAP!
Thank you!
crazytebrexxx said:
When I turn on my Samsung Galaxy Ace GT-S5830i, it gets stuck at "Samsung GALAXY Ace GT-S5830i" intro logo, whatever. It won't load, it can just stay like that until the battery goes off.
I'm able to start the Recovery Mode luckily using "Home Button + Volume up + Power Button", but it shows this code:
Code:
-- Appling Multi-CSC --
E:failed to mount /system (Inval
id argument)
E:failed to mount /system (Inval
id argument)
Tried to format /system, doesn't work, neither with ClockworkMod Recovery (every possible versions), it shows this:
Code:
Formatting /system...
Error mounting /system!
Skipping format...
Done.
Also, I tried with Odin3 v1.84/v1.87, and still it won't work. I applied all good, but when I connect my phone to my computer using the USB cable, and it shows it normally, but when I "Start" the process, it read everything valid and it gets stuck at:
Code:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
This is the full log of Odin3:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> DefaultCalDataWithBoot_S5830iXXLB1_REV00.tar.md5 is valid.
<OSM> PDA_S5830IXXLA4_REV00.tar.md5 is valid.
<OSM> MODEM_S5830iXXLA2_REV00.tar.md5 is valid.
<OSM> GT-S5830i-MULTI-CSC-OXXLA2.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..
When I turn off the phone or unplug the USB cable it shows:
Code:
^^ ...
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
I tried with multiple USB cables, same thing happening.
Also, one more thing. When I try to format and mount /data and /cache, both ends successfully.
Format /data log:
Code:
Formatting /data...
Done.
Format /cache log:
Code:
Formatting /cache...
Done.
So I'm asking for help. Is there any possibility to repair my phone MYSELF? Is there a way to successfully format and mount /system? What should I do? If there are ways to solve this problem, and by that I need to download needed files, please send the link!
Please response ASAP!
Thank you!
Click to expand...
Click to collapse
Search for Multiformator Tool and Flash it thorough CWM and choose RFS then do wipe data/cache in CWM then try to flash Stock via Odin .
Hi there guys...I've stumbled onto a problem that I can't fix myself, hence some of your help/expertise is required.
Here's what has happened sofar...
Yesterday a family member of mine lost her phone and asked me for my old SGS3 which was lying around the house.
So after factory resetting the device I gave the phone to her...but then the device got an OTA update...but after update, when the device went to reboot itself, the droid laid dead with a red triangle.
Note: the device was not rooted and was running Touchwiz etc...
Upon reboot, the device got stuck at the Samsung Galaxy SIII - GT-I9300 logo
Then she brought the device back to me and after some searching the web, it seemed that the diagnosis was that the software/firmware may have gotten corrupted.
I followed the TUT (link: here) using ODIN 3.10 , I flashed the International version of 4.3 on my device.
I got the I9300XXUGNJ2_I9300MSTGNJ1_MST file from Sammobile and it worked like a charm...all is well, so I thought.
Today when she turned the phone on in the morning, (she turns it off at night)...the device got stuck at the same place.
But now, even the TUT with ODIN isn't helping...now the whole thing is stuck at SetupConnection.
I have tried the cable, updating the samsung usb drivers, switching the USB ports (not using any USB hub),
making sure that I run the program in admin mode and that there's no ext card connected to the device...but to no avail.
When I hard reset the device I get the following error while the droid lays dead
Code:
E: failed to mount /cache (No such file or directory)
...etc...
Wiping the data/factory reset etc isn't helping either...as it still gives me similar E: failed error.
Rebooting the system gets me back to the stuck Samsung Galaxy SIII - GT-I9300 logo.
Plugging the device with the USB cable to the computer doesn't get me to the ext sd card etc either.
Any ideas?? Help is greatly appreciated.
*UPDATE*
After persisting to follow the TUT mentioned above, finally it went through ODIN and was shown as "PASS"
But when the device reboots after that, the "E: failed to mount error" persists...and I'm back to square one.
contactmsd said:
*UPDATE*
After persisting to follow the TUT mentioned above, finally it went through ODIN and was shown as "PASS"
But when the device reboots after that, the "E: failed to mount error" persists...and I'm back to square one.
Click to expand...
Click to collapse
Sounds like partitions maybe corrupt try the resuce firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << follow instructions exactly as it containes a pit file there are two versions and i think the pit file is in the 4.1.2 version.If this does not work then i think it would probably be a service repair.
tallman43 said:
Sounds like partitions maybe corrupt try the resuce firmware here >> http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6 << follow instructions exactly as it containes a pit file there are two versions and i think the pit file is in the 4.1.2 version.If this does not work then i think it would probably be a service repair.
Click to expand...
Click to collapse
OK...
First try..gave me the following error in ODIN.
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_user_low_ship.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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Then I tried again, after changing the port.
This time I got the following error.
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_user_low_ship.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> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> sboot.bin
<ID:0/007> NAND Write Start!!
<ID:0/007> tz.img
<ID:0/007> param.bin
<ID:0/007> sboot.bin
<ID:0/007> param.bin
<ID:0/007> tz.img
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img
<ID:0/007> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
*Sigh*
Emmc chip is corrupt/damaged. Try reading the dead boot restore thread in general forum, but doubtful if worth repairing.
^^above, I was using the 4.1.2 firmware which I got from the thread that @tallman43 mentioned.
But as you can see I got the errors shown above.
Then I tried the same using the 4.3 firmware also from that thread but it had no *.pit file.
In that thread on page 41 though, @k-semler added the *.pit file that he used.
But that resulted in ODIN getting stuck at the .pit thing.
After renaming that *.pit file to mx.pit it worked...
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXAGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> param.bin
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Completed..
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
BUT after rebooting, the issue remains though.
I'm still stuck at the Samsung Galaxy SIII - GT-I9300 logo
Factory reset in recovery, check for mounting errors.
boomboomer said:
Factory reset in recovery, check for mounting errors.
Click to expand...
Click to collapse
E: failed to mount /cache (No such file or directory) etc...list goes on...
I got some suggestions trying installing Philz Touch Recovery...
So here's what I did...
1. I flashed Philz Touch Recovery using ODIN
It was a pass...and I was able to boot into Philz Recovery.
2. Then I tried installing a Custom ROM (PA) through SD Card.
At first I was getting an error, after checking it seemed that I couldn't access the SD Card.
Then I got myself a new SD card, formatted it to fat32 and transferred the zip files onto it.
3. Installing the Custom ROM (PA)
At first I was getting a Status 7 error.
After editing the updater-script as shown on xda forums..the error went away.
BUT now the installation just aborts and I get the following on my screen.
Code:
Installing: /storage/sdcard1/pa_i9300-4,41-20140705.zip
E: Can't mount /cache/recovery/last_install
E: failed to open last_install: File exists
Finding update package...
Opening update package...
Installing update...
Installation aborted.
press any key to continue.
Note: I also tried with different ROMs (CM11) but same result as above.
Why can't it mount the /cache folder? Could it be a chmod issue??
The error in full from my first post is the following...
Code:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
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
If it's corrupted then why is it listing only that folder and not other folders as well?
Help is really needed and is greatly appreciated guys/gals.
[SOLVED]
I finally got it working...my issue has been resolved.
For those who are interested, this is how I fixed the problem.
I went and got myself:
- stock *.pit file for the SGS3 GT-I9300 16GB variant.
- stock bootloader for SGS3 GT-I9300
- stock Firmware from my Region (Single File variant)
Step 1
Flash the stock *.pit file using ODIN with the following settings ticked on:
- auto reboot
- re-partition
- f.reset time
- Nand erase all
Note: IF for some reason it doesn't work, re-try and it should pass (I myself had to try 3 times).
Step 2
Flash Philz Touch Recovery using ODIN with the following settings ticked on:
- auto reboot
- f.reset time
Note: IF for some reason it doesn't work, re-try and it should pass.
Step 3
Take a Mirco SD card (format if needed, make sure you format it in fat32). Transfer the stock bootloader zip (no need to extract the .zip file) on it and insert the card in your phone.
Step 4
Press Vol.Up+Power+Menu button and keep pressing it until you see the Samsung Galaxy SIII GT-I9300 logo, then release the buttons and the Philz Recovery will boot.
Install the bootloader zip using the "Install from sdcard" option in Philz Touch Recovery.
Step 5
Reboot to recovery and wipe cache and factory reset.
Go to download screen (ODIN MODE).
Step 6
Flash the stock firmware using ODIN with only the following settings ticked on:
- auto reboot
-f.reset time
Note: IF for some reason it doesn't work, re-try and it should pass (I myself had to try 2 times).
Step 7
If all of this is done...then go to Recovery mode (you'll notice that it's no longer the Philz Touch Recovery. No problem, in the current Recovery mode:
- wipe cache
- factory reset
and reboot the device.
This should resolve the problem and your device will work once again.
No cellular due to wrong/fake imei
^^The above did fix my previous problem but I did encounter a new one.
I had a wrong/fake IMEI ("0049..."), which caused that I had no cell reception and couldn't use the phone to call or send/receive sms etc...
I googled a lot and I tried some of the TUT on the web, but nothing helped.
Until I found a thread on the xda that said one could try to flash a newer stock ROM (don't know the exact thread).
So I went ahead and checked the version I was on...luckily it was 4.0.4
I then downloaded a newer stock ROM 4.3 for my region.
And flashed that using ODIN...
and voila...when I checked the IMEI code again, it was back to the original one.
Files that I used to resolve my issues.
I've been asked which .pit file or which ROM etc...did I use to resolve my problem.
So here it is...but do keep in mind, these files may have worked for me but I can't guarantee that they'll work for you too.
Note: therefor use these at your own risk...I'm not responsible for any problems that you may encounter.
Philz Touch Recovery:
I got the "philz_touch_6.12.8-i9300.tar.md5" file from: here
Stock ROM:
I got the stock ROM (single file) "I9300XXUGNJ2_I9300PHNGNJ1_PHN.zip" from: here
That's the: GT-I9300 Netherlands 2014 November 4.3 I9300XXUGNJ2 I9300PHNGNJ1
The stock *.pit file and the stock bootloader that I used, are attached to this post.
The exact steps that I took are in this post: here
Note: Don't forget to backup your EFS, search on xda for how to do that etc...
Best of luck...
Hi,
I've been having some trouble restoring my SCH-I605 to functionality after a nice surprise bricking yesterday.
-------------------------------------------------------------------------------------------------------------------
History of Incident:
-------------------------------------------------------------------------------------------------------------------
A few months back I managed to get a successful on my Note 2 after quite a bit of work. Everything was great, and I managed to do all of the modifications I wanted on the stock firmware.
Last night I decided it would be a good idea to make a backup of my current setup in preparation for potential tinkering. I installed Clockworkmod's Rom Manager and Recovery apps. In one of them I clicked something like "Fix Permissions" which requested root access and completed successfully. Following this, the phone requested a restart.
Post restart, I received the standard "verizon has ruined your day" message as follows: "System software not authorized by Verizon Wireless has been found on your phone. Please turn off your phone and go to the nearest Verizon Wireless store for help."
-------------------------------------------------------------------------------------------------------------------
I researched the topic and found this thread:
http://forum.xda-developers.com/showthread.php?t=2040264
I have tried each of the firmware downloads including the alternates here, along with a variety of others from similar threads claiming to be stock images or stock rooted.
-------------------------------------------------------------------------------------------------------------------
Throughout this process I have managed to get the ODIN Mode Prompt to read:
-------------------------------------------------------------------------------------------------------------------
ODIN MODE
PRODUCT NAME: SCH-I605
CURRENT BINARY: CUSTOM
CURRENT STATUS: CUSTOM
RP SWREV: A3
And
ODIN MODE
PRODUCT NAME: SCH-I605
CURRENT BINARY: SAMSUNG OFFICIAL
CURRENT STATUS: CUSTOM
RP SWREV: A3
-------------------------------------------------------------------------------------------------------------------
Typical failures during and post flash included:
-------------------------------------------------------------------------------------------------------------------
SW REV. CHECK FAIL. DEVICE: 3 BINARY 2
ODIN v3.07 Readout
...
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
-------------------------------------------------------------------------------------------------------------------
SW REV. Invalid magic string.
ODIN v3.07 Readout
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> modem.bin
<ID:0/004> param.bin
<ID:0/004> recovery.img
<ID:0/004> sboot.bin
<ID:0/004> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
-------------------------------------------------------------------------------------------------------------------
The second error yields the interesting result of changing the Binary from CUSTOM to SAMSUNG OFFICIAL and replaces the verizon message with the following:
"Firmware upgrade encountered an issue . Please select recovery mode in Kies & try again."
Kies will not connect to the device in this state or ODIN mode, but it does try.
When the Verizon message is present, the usb connection has no activity and thus yields no connection in Kies.
-------------------------------------------------------------------------------------------------------------------
I have attempted making some other .tars with the TAR_MD5_PACKAGER but these pacakges yielded similar results. I can remove the sboot.bin file from the package and get it to install, but the same verizon message comes up. I have tried on multiple ODIN versions and two computers with no change in results.
Any thoughts on what to do now? I have included all the information I think is pertinent. If you need more I can provide it.
Thanks,
Donkey545
I have managed to get the device to boot past either of the error messages by flashing the OTA 4.4.2 Rom I605VRUFND7_I605VZWFND7_VZW.
-------------------------------------------------------------------------------------------------------------------
I found that rom here
(Cant post URLs Because I am a new member)
androidfilehost /?fid=24052804347837519
-------------------------------------------------------------------------------------------------------------------
The system is hanging at the Verizon logo now, but the fact that it is no longer stuck at the error message is promising. I will attempt so more things to get the system to work..
-------------------------------------------------------------------------------------------------------------------
EDIT:
-------------------------------------------------------------------------------------------------------------------
- Booting in Safe Mode does not remedy the issue.
- Booting into recovery now works!
- Wiping the cache yields no results
-------------------------------------------------------------------------------------------------------------------
Recovery mode information:
-------------------------------------------------------------------------------------------------------------------
Android system recover <3e>
KOT49H. I605VRUFND7
--------------------------------------------------
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : VZW
Successfully applied multi-CSC.
E: failed to mount /data (Invalid argument)
can't mount '/data' (Invalid argument)
E: failed to mount /data/log/recovery_log.txt
-------------------------------------------------------------------------------------------------------------------
I will now attempt a factory reset. I was trying to avoid this, but I probably lost all of my data anyway.
-------------------------------------------------------------------------------------------------------------------
EDIT 2:
-------------------------------------------------------------------------------------------------------------------
The factory reset has successfully un-bricked my phone! I suspect that I will no longer have root, and I definitely lost all of my data. I will confirm these results shortly.
A few days back I was trying to flash stock firmware on my S6 edge and Odin failed in between of the flashing since then My phone started showing a blue screen which basically said to use smart switch emergency software recovery but when I open smart switch It says Unsupported Device So I cannot use smart switch on my phone. Yesterday I flashed PIT file Now I do not have that error screen But my phone can only go in download mode and stock recovery. When I try to flash Stock firmware from Odin It gets stuck
Log of Odin
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
I cannot flash twrp aswell Odin says
<ID:0/005> 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/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
So I cannot Use Odin
When I go into stock recovery it says
Supported API: 3
dm-verity verification failed. . .
E: failed to mount /system (Invalid argument)
If I choose Apply Update from ADB or Apply Update from SD card It says
Update from external storage is disabled.
If I wipe data/factory reset it says
-- Wiping data. . .
Formatting /data. . .
Formatting /cache. . .
Formatting /sbfs. . .
-- Set factory reset done. . .
-- Copying media files. . .
E: failed to mount/ system (Invalid argument)
Can't mount '/system' , rc = '-1' (Invalid argument)
Data wipe complete.
Can someone please help me? Thank you.
raaahimaaa said:
A few days back I was trying to flash stock firmware on my S6 edge and Odin failed in between of the flashing since then My phone started showing a blue screen which basically said to use smart switch emergency software recovery but when I open smart switch It says Unsupported Device So I cannot use smart switch on my phone. Yesterday I flashed PIT file Now I do not have that error screen But my phone can only go in download mode and stock recovery. When I try to flash Stock firmware from Odin It gets stuck
Log of Odin
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
I cannot flash twrp aswell Odin says
<ID:0/005> 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/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
So I cannot Use Odin
When I go into stock recovery it says
Supported API: 3
dm-verity verification failed. . .
E: failed to mount /system (Invalid argument)
If I choose Apply Update from ADB or Apply Update from SD card It says
Update from external storage is disabled.
If I wipe data/factory reset it says
-- Wiping data. . .
Formatting /data. . .
Formatting /cache. . .
Formatting /sbfs. . .
-- Set factory reset done. . .
-- Copying media files. . .
E: failed to mount/ system (Invalid argument)
Can't mount '/system' , rc = '-1' (Invalid argument)
Data wipe complete.
Can someone please help me? Thank you.
Click to expand...
Click to collapse
Flash a firmware again with pit file. Make sure you are using the correct pit file as each model and region needs a certain pit file.
callumbr1 said:
Flash a firmware again with pit file. Make sure you are using the correct pit file as each model and region needs a certain pit file.
Click to expand...
Click to collapse
I did. Its stuck. it says
<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> Added!!
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
And on the top it says "Set partitiion" on a white background.
If I just flash the PIT it says this,
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
On a side note, I bought this phone second hand on the back of the phone theres a 16 digit Imei if i remove the last digit and search it on an IMEI checker it says my model number is G925A where as when the phone worked it showed G925F I have tried Flashing Att pit but that doesnt work. Is there something I should know about a 16 digit imei?
Did you fix the issue because i got this message too and can't find a solution.
Mr.Januzi said:
Did you fix the issue because i got this message too and can't find a solution.
Click to expand...
Click to collapse
were you able to figure out the issue yet? i am having the same exact problem on my s7.
I sent it to a local phone repair shop and they fixed it, try to find the combination file(if you know how to use it) and i personally think after the combination file is flashed, you will be able to flash the stock firmware again with no issues.
I DID NOT TRY THIS METHOD, but i think it would work.
I personally would try it. It's up to you.
Kind regards,
Mr.Januzi said:
I sent it to a local phone repair shop and they fixed it, try to find the combination file(if you know how to use it) and i personally think after the combination file is flashed, you will be able to flash the stock firmware again with no issues.
I DID NOT TRY THIS METHOD, but i think it would work.
I personally would try it. It's up to you.
Kind regards,
Click to expand...
Click to collapse
I am more of a Moto user... Combination file.. the AP/BP/CR/CSC? How do I know which are the proper files for my device?
PM me your firmware specs that you see on recovery and I believe we can make this work.