Database Info

[GUIDE] How To Update Your Samsung Epic 4G to Official "EB13" Android 2.2.1

Thanks to BriefMobile.com For Full Instructions!
- The full instructions are located here!
Instructions: Update "EB13" Android 2.2.1 for Epic 4G (Easy)
Note: If you already have "DI18" stock ROM on your phone already, skip to "Step 11"
Download Samsung_Mobile_Driver_V1.3.800_For_SPH-d700_Epic_4G.zip
Unzip the file and install the driver
Download Odin3+v1.61andepic.pit.zip
Unzip the file and open up "Odin3+v1.61.exe"
Put your phone into "Download Mode"
- Pull out battery
- Put in battery
- Push and hold "1" on your keyboard
- Power on device while holding "1"
Plug your Epic 4G into the computer
Download SPH-D700-DI18-8Gb-REL.tar.md5
Place the file in the "PDA" slot
Start flashing
- This will reset your phone to default settings
You now have stock DI18 Android 2.1 back on your Epic! Feels good right?
Download update.zip
Move the file to your SD card on the Epic 4G
- Plug in device
- Select "Mass Storage"
- Drag the "update.zip" into root of your SD card
Boot your device into "Recovery Mode"
- Pull out battery
- Put in battery
- Push and hold the combination of the Volume Down Button, the Camera Button, and the Power Button
Select "apply sdcard:update.zip" from the "Recovery Mode"
- The "Home" soft key is the select key.
Once again, here is the new update file: update.zip
Alternative Method (Easier)
Download Samsung_Mobile_Driver_V1.3.800_For_SPH-d700_Epic_4G.zip
Unzip the file and install the driver
Download Odin3+v1.61andepic.pit.zip
Unzip the file and open up "Odin3+v1.61.exe"
Put your phone into "Download Mode"
- Pull out battery
- Put in battery
- Push and hold "1" on your keyboard
- Power on device while holding "1"
Plug your Epic 4G into the computer
Download SPH-D700-EB13-8Gb-REL.tar.md5
Place the file in the "PDA" slot
Start flashing
- This will reset your phone to default settings
Congratulations! You now have "EB13" Android 2.2.1 on your Samsung Epic 4G by Sprint!
Once again, here is the new ROM: SPH-D700-EB13-8Gb-REL.tar.md5
Last Resort (Easiest)
Download Epic4G_FroyoUpgrade_EB13_Tool.exe
Install the file
Run "SWUpgrade for SPH-D700"
Follow Directions
Congratulations! You now have "EB13" Android 2.2.1 on your Samsung Epic 4G by Sprint!
Once again here is the Epic4G_FroyoUpgrade_EB13_Tool.exe
For Developers Only
- Use one.click.root.exploitv2.5.5.zip to root your Samsung Epic 4G
- Source for ROM: SPH-D700_Froyo_update_EB13.tar.gz

big ups to whosdaman as always!!!

I will have the full .tar shortly for everyone and I new list of updates

Does this also work for us on EXT4 roms?

drizek said:
Does this also work for us on EXT4 roms?
Click to expand...
Click to collapse
no...you need complete stock di18

Great guide whosdaman.
Update.zip download links lead straight to your blog.
Mirror for update.zip http://www.multiupload.com/K1MHLS6SNX

globalninja said:
no...you need complete stock di18
Click to expand...
Click to collapse
Ya, but the first 8 steps will flash DI18 even if you are using EXT4, right?

drizek said:
Ya, but the first 8 steps will flash DI18 even if you are using EXT4, right?
Click to expand...
Click to collapse
Correct. You will go back to RFS with DI18

So once we do all this and we reinstall CWM3, which if i recall automatically converts your file system to EXT4, we will have EB13 with CWM3 and EXT4 all nice and easy, correct?

NYYFan325 said:
So once we do all this and we reinstall CWM3, which if i recall automatically converts your file system to EXT4, we will have EB13 with CWM3 and EXT4 all nice and easy, correct?
Click to expand...
Click to collapse
You will have a file system with EXT4, you still need a kernel that supports it. I assume that Samsung hasn't suddenly added EXT4 support.

Crap forgot about the kernel... well that just **** on my parade

Will this work for those with stock + root/CWM recovery or will this work only with stock recovery?

PythonFanTN said:
Will this work for those with stock + root/CWM recovery or will this work only with stock recovery?
Click to expand...
Click to collapse
It works with the recovery

does this update zip contain new kernel and modem?

It appears that one click 2.5.5 rooter works with this. Just sayin.

ericizzy1 said:
does this update zip contain new kernel and modem?
Click to expand...
Click to collapse
The update.zip is just like getting an ota from sprint but you have to be stock. It has everything you need
Sent from my SPH-D700 using XDA App

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D700-DI18-8Gb-REL.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..
Is what I get when trying to flash DI18. It has been stuck on that last bit for a while now. You are supposed to select a PIT file, right? and the options I had checked was only Auto Reboot.
Edit: nevermind. Ran it again, worked this time.

Sooo....... Why not just Odin the EB13 tar rather than Odin DI18 then run update.zip?

SubnetMask said:
Sooo....... Why not just Odin the EB13 tar rather than Odin DI18 then run update.zip?
Click to expand...
Click to collapse
That's worth getting banned over
Sent from my SPH-D700 using XDA App

Im a bit confused. Can i use this if im rooted? if yes will it make me lose root?

[SAMSUNG GALAXY S3 TOOLKIT V9] Drivers, Backup, Root, CWM, BusyBox + MORE [VZN]

INTRODUCING THE SAMSUNG GALAXY S3 UNIFIED TOOLKIT
SUPPORTED MODELS
INTERNATIONAL [GT-I9300] SUPPORT THREAD HERE
AUSTRALIAN MODEL GSM [GT-I9300T]
INTERNATIONAL [GT-I9305/GT-I9305N] SUPPORT THREAD HERE
AUSTRALIAN MODEL LTE [GT-I9305T]
C SPIRE MODEL LTE [SCH-L710]
AT&T US [SGH-I747] SUPPORT THREAD HERE
BELL, ROGERS, SASKTEL, TELUS [SGH-I747M] [SGH-I747M] USE AT&T SUPPORT THREAD
US CELLULAR MODEL LTE [SCH-R530] USE AT&T SUPPORT THREAD
METRO PCS MODEL LTE [SCH-R530M] USE AT&T SUPPORT THREAD
SPRINT US [SPH-L710] SUPPORT THREAD HERE
TMOBILE US [SGH-T999] SUPPORT THREAD HERE
MOBILICITY, VIDEOTRON, WIND [SGH-T999V] USE TMOBILE SUPPORT THREAD
VERIZON US [SCH-I535] SUPPORT THREAD HERE
CHINA ANYCALL CDMA MODEL [SCH-I939] USE GT-I9300 SUPPORT THREAD
Click to expand...
Click to collapse
The Unified Android Toolkit supports a multitude of Nexus and Samsung devices with more devices being added all the time. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.4 [9TH JAN 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn't corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk's to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: As the exe files are not Digitally Signed with a Microsoft Certificate they 'may' get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
Credits: Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NOTHING IS RESTRICTED.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR 'AUTO UPDATES' DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE 'QUICK PICKS' SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.

**FAQ**
Q. Help me I can't find my build in the Model Selection Screen
The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.1).
The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.
If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.
----------------------------------------------------------------------------
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.
----------------------------------------------------------------------------
Q. Why do I need to back up my IMEI/EFS and how do I do it?
There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry). If you have a GT-I9300 GSM Model then you can do this from the Toolkit but if you have an LTE device then it isn't soo easy to do. If you have an LTE device you should go to *THIS* thread by lyriquidperfection and follow the information to save your IMEI/NV Data so that you are covered if anything should happen.
----------------------------------------------------------------------------
Q. Is there currently no way to root the Samsung Galaxy S3 without voiding the warranty?
All methods of rooting will void your warranty in some way as you will have superuser files on your phone that arent supposed to be there. There is a method of rooting your phone without increasing the flash counter which involves flashing a complete rom with root files already added but if anything happens and you need to send it back under warranty you will need to flash a 'proper' Stock Rom back before returning it or your warranty will be void. Flashing a custom kernel or recovery to root will increase the flash counter and also void any warranty. There is currently no method of resetting the flash counter on Snapdragon models but im pretty sure there will be some support for it soon. If you dont want to risk it or you aren't sure then you shouldnt really be flashing your phone and should just leave it alone. Its your choice .
----------------------------------------------------------------------------
Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?
Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.
----------------------------------------------------------------------------
Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
----------------------------------------------------------------------------
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.
----------------------------------------------------------------------------
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
----------------------------------------------------------------------------
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.
----------------------------------------------------------------------------
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
.
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
----------------------------------------------------------------------------
Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit
I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.

**reserved if needed**

\o/ Been waiting for this show up on this device Much appreciated!

I feel so informed already. Even without anything in it
Sent from my SCH-I535 using Tapatalk 2

Getting ahead of ourselves.
I noticed "Reserved for future" follow up posts, which are everywhere, largely go unused. And I ignore it all the time, but right now I'm looking at a blank follow up post that's following a blank post.
;D
** Space reserved for potential future edits **
** Reserved for editing the edits **
Sent from my SCH-I535 using Tapatalk 2

RELEASE OF THE NEW UNIFIED S3 TOOLKIT V7.0.0 [10TH JAN 2013]
ChangeLog:
ToolKit v7.0 (10th January 2013)
+International and Snapdragon Toolkits have been unified into a single Galaxy S3 Toolkit
+Rewritten how the Toolkit works to keep all tasks common to other Toolkits in a seperate executable
+After model is selected the Toolkit will now download ONLY the files needed to cut down on install size
+Seperated all supported devices by model number
+Added support for new S3 variants
+Added support for latest builds on all models
+Updated all cwm and twrp recoverys to the latest version and given each model its matching recovery
+Updated SuperSU files by Chainfire to 0.99
+Added new root methods
+Added flash zip file by sideload function in recovery
+Fixed many functions and made other functions more accessible and easier to understand
+Added Instant Reply donation link to get codes out to people much quicker without waiting for a manual response
+Previous Snapdragon and International Toolkit codes will still work with the new unified version
+Soo many more changes to integration and operation I cant list them all
I have been working on this for over 3 weeks and its finally completed
This new unified S3 Toolkit brings together the International and Snapdragon models under a single Toolkit to make updating and maintenance a lot easier. This new version also is the first of my Toolkits to download the model files as needed to make the intial download smaller and avoid accidentally selecting the wrong models image which could lead to trouble. Please read the 1ST POST again as I have changed some information in it. The Toolkit also has an Information section built in so use it as there is allot of useful stuff in there.
One thing I would like to mention is that all the boot images are pure stock with just the rooting process applied to the insecure images. As some Custom Roms are built with their own kernels you may find that if you have a Custom Rom and flash the Toolkits boot image your device boots fine and will have adb root access but wifi and bluetooth don't work. There is nothing I can do about this because of the change to some Custom Roms but it is very easy to just flash the boot image that is linked to the Rom you are using after you have done what you need to. Everything 'should' work perfectly on Stock Roms.
I have had to make some of the boot image blind as no testers came forward to test. If any of the image do not work to boot your device please do not start screaming and shouting, let me know and I will do my best to fix it as soon as possible. In any case (apart from in custom roms as stated above) the stock boot image will always get your device working again. Because the model specific files are downloaded by the Toolkit, if you need to redownload the boot files because they either didnt download/extract properly or because they had to be fixed then all you have to do is to delete your model folder from the root folder in the Toolkit, restart the Toolkit and select your Model/build and it will force the Toolkit to download the model file again.
Download links in the 1st post.
Enjoy.
Mark.

First I want to say thank you Dev for all of your work on these toolkits. I was happy to donate to unlock the extra features. I'm hoping someone can help me with something though. whenever I try pull the sd contents back to my pc, I get the following... It seems to run through all the commands properly but at the end it says
": No such file or directory
An Error Occurred.
Press any key to return to the Main menu..."
All the other backup features seem to run fine. I haven't had the need to run any of the other features yet. I'll attach a printscreen. Thanks in advance for any help on this!

Trying to root Verizon s3 4.1.1. The device is recognized fine and everything is standard. When I go to root (all in one) I select the correct .tar file but Odin fails. It says "secure check failed" on my phone. No dice there. I've used this in the past on my Sprint S3 and it couldn't have been easier. I'm guessing is something is up with the TAR. I've tried a lot of other options to the same result.
I got similar results when I tried just flashing the recovery option (4). Also I have tried this on multiple computers as well with identical results. I've also re-installed the drivers, tried using "Camera mode" on the usb connection, different root files etc etc to not avail.
ODIN Results:
<ID:0/006> Added!!
<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> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)

big blue said:
First I want to say thank you Dev for all of your work on these toolkits. I was happy to donate to unlock the extra features. I'm hoping someone can help me with something though. whenever I try pull the sd contents back to my pc, I get the following... It seems to run through all the commands properly but at the end it says
": No such file or directory
An Error Occurred.
Press any key to return to the Main menu..."
All the other backup features seem to run fine. I haven't had the need to run any of the other features yet. I'll attach a printscreen. Thanks in advance for any help on this!
Click to expand...
Click to collapse
I have a feeling the filename is too long for windows to handle and so it crashed the procedure. Try deleting the file if it isnt important and it should complete.
Mark.

svinyard said:
Trying to root Verizon s3 4.1.1. The device is recognized fine and everything is standard. When I go to root (all in one) I select the correct .tar file but Odin fails. It says "secure check failed" on my phone. No dice there. I've used this in the past on my Sprint S3 and it couldn't have been easier. I'm guessing is something is up with the TAR. I've tried a lot of other options to the same result.
I got similar results when I tried just flashing the recovery option (4). Also I have tried this on multiple computers as well with identical results. I've also re-installed the drivers, tried using "Camera mode" on the usb connection, different root files etc etc to not avail.
ODIN Results:
<ID:0/006> Added!!
<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> boot.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Have you unlocked the Bootloader as stated at the start for verizon models?
Mark.

SAMSUNG GALAXY S3 TOOLKIT AUTO UPDATE V7.1.0 [22ND JAN 2013] AVAILABLE!!
Changelog:
+Added support for GT-I9300 build XXELLC
+Fixed US variants versions displayed incorrectly in Model Selection screen
+Added GT-I9300 TWRP Recovery 2.3.3.1 image to Toolkit for easy flashing
+Improved CWM NAND Backup script to make it allot more stable and robust
+Added Insecure Kernel detection to sections requiring Insecure Boot Image
+Added 'Pull Folder' to 'Pull Files' section in Main Menu
+Added 'Fix Internal Storage Permissions' to Mods Menu [folder not showing]
+Minor bug fixes and improvements
[Auto Updates are only accessible if you have donated to the Toolkit project, received an activation code and unlocked the donator features. Auto Updates are a much faster and easier way of pushing small updates that would otherwise not be worth doing. I can push a single textual change or add support for a new build without having to go through the whole process of building a full version and uploading a large file. IF you are not able to or do not want to donate to unlock the Auto Update feature (and other donator features) then all the smaller updates are collated and a full build made when I have time or if there are enough updates to warrant it. This is the easiest way to make sure all the Toolkits are as up to date as possible. IF you have any views about this please pm me about them and do not post in the open thread]
Enjoy
Mark.

mskip said:
Have you unlocked the Bootloader as stated at the start for verizon models?
Mark.
Click to expand...
Click to collapse
dang it. I swore I wouldn't be the guy that just missed the step talking about this. Yeah I see it in there now.
Now in the verizon instructions, I went to link #1 regarding bootloader info and then to link #2 regarding the process to follow. The link #2 states that it only works for 4.0.4 though and with all the "brick" talk I was hesitant to give it a try. As a note I did select the 4.1.1 option in the toolkit (a2).
Am I missing something or do I need to do something different for a Jelly Bean bootloader unlock? I want to certainly stick with your supported methods.
edit:
In your instructions it references this link (#2) for unlocking the 4.1.1 bootloader: http://forum.xda-developers.com/showpost.php?p=30274025&postcount=317
---------- Post added at 08:03 PM ---------- Previous post was at 07:39 PM ----------
I'm assuming I can just follow the method from this post and should be good to go with Root/Unlock/CWM
http://forum.xda-developers.com/showthread.php?t=2046439
Once that is out of the way I can just backup and flash away right? (I know that is how it has been for everything else but want to be sure I'm not missing something again).
BTW, me skipping over the text that asks me "to read" everything reminded me of this lol:
http://www.southparkstudios.com/clips/382791/can-it-read

svinyard said:
dang it. I swore I wouldn't be the guy that just missed the step talking about this. Yeah I see it in there now.
Now in the verizon instructions, I went to link #1 regarding bootloader info and then to link #2 regarding the process to follow. The link #2 states that it only works for 4.0.4 though and with all the "brick" talk I was hesitant to give it a try. As a note I did select the 4.1.1 option in the toolkit (a2).
Am I missing something or do I need to do something different for a Jelly Bean bootloader unlock? I want to certainly stick with your supported methods.
edit:
In your instructions it references this link (#2) for unlocking the 4.1.1 bootloader: http://forum.xda-developers.com/showpost.php?p=30274025&postcount=317
---------- Post added at 08:03 PM ---------- Previous post was at 07:39 PM ----------
I'm assuming I can just follow the method from this post and should be good to go with Root/Unlock/CWM
http://forum.xda-developers.com/showthread.php?t=2046439
Once that is out of the way I can just backup and flash away right? (I know that is how it has been for everything else but want to be sure I'm not missing something again).
BTW, me skipping over the text that asks me "to read" everything reminded me of this lol:
http://www.southparkstudios.com/clips/382791/can-it-read
Click to expand...
Click to collapse
As far as I know it will work just as well on 4.1.1. Just download the casual app, select root with DebugFSRoot and 'do it', then select 'Flash unsecure Aboot' and 'do it'.
You will then be able to flash anything to your device so be careful and do not accept OTA updates. If you want to flash roms stick with cwm zip versions.
Mark.

It's my first time flashing my VZW s3. How much do i have to donate for the donater features and how do i activate it? I want to put a custom rom on here as well. Does using this utility unlock the bootloader, give me root, and flash a custom recovery? Im sorry for the many questions, I haven't flashed since i had my HTC Sensation.
EDIT:
Do I have to go through this process first http://forum.xda-developers.com/showthread.php?t=2046439? And do I need ODIN images?

tracerman said:
It's my first time flashing my VZW s3. How much do i have to donate for the donater features and how do i activate it? I want to put a custom rom on here as well. Does using this utility unlock the bootloader, give me root, and flash a custom recovery? Im sorry for the many questions, I haven't flashed since i had my HTC Sensation.
EDIT:
Do I have to go through this process first http://forum.xda-developers.com/showthread.php?t=2046439? And do I need ODIN images?
Click to expand...
Click to collapse
EDIT 2:
I went head with that other process and I got everything done.

mskip said:
As far as I know it will work just as well on 4.1.1. Just download the casual app, select root with DebugFSRoot and 'do it', then select 'Flash unsecure Aboot' and 'do it'.
You will then be able to flash anything to your device so be careful and do not accept OTA updates. If you want to flash roms stick with cwm zip versions.
Mark.
Click to expand...
Click to collapse
Thanks for the info. I did end up just following this http://forum.xda-developers.com/showthread.php?t=2046439 and found that it was surprisingly really easy.
As a note, FYI everything I found said that DebugFSRoot doesn't work on 4.1.1 hence I moved away from the method.

I had some drivers installed before I downloaded this so I uninstalled them and installed the drivers that came with the toolkit but my serial is still not showing up...
when i go to device manager, I dont see Samsung Android Phone, I see SAMSUNG MOBILE USB Composite Device - is that right as well? I'm on JRO03C BLK3 if it matters...
thanks in advance!

So can I root using this? I just recieved a replacement S3 and I need to reroot.
Edit: Nevermind, it appears I can not

NightxFall said:
So can I root using this? I just recieved a replacement S3 and I need to reroot.
Edit: Nevermind, it appears I can not
Click to expand...
Click to collapse
If the bootloader has been unlocked (which requires root in the first place) then the Toolkit can update or change the root files.
Blame Verizon not me
Mark.

[GUIDE] Soft Bricked - Solution (Worked for me)

My Samsung Galaxy Note Pro 12.2 WiFi (SM-P900) got soft bricked after following a rooting tutorial i found by googling How to root SM-P900. I think the problem was that i used a too old (or wrong) version of Odin, but im not sure. While i was flashing the auto-root through Odin the screen turn of. After that it showed the "firmware upgrade encountered an issue. please select recovery mode in kies and try again" standard Samsung Message. I tried to reinstall the firmware through kies but with no luck.
[SOLUTION]
1. First I downloaded the correct firmware, from Sammobile. In my case it was Nordic Contries, cause i live in Denmark. Pick the one that suite you!!
2. Then i booted my first NotePro to download mode. It took my some tries, to get it working. First hold the power button. When the "Firmware Upgrade Encountered An Issue..." message turns off, in the same second, release the power button, and now select all three (Power + Volume Down + HomeKey). (You have to release the power button and press it again to make it work (At least for me)
3. Now install the stock firmware and your tablet is now working again.
4. (Optional) If you want to root your device and it didn't work the first time. Make sure you use the same Odin as showed in the tutorial.

invalid ext4 image
madsthines said:
My Samsung Galaxy Note Pro 12.2 WiFi (SM-P900) got soft bricked after following a rooting tutorial i found by googling How to root SM-P900. I think the problem was that i used a too old (or wrong) version of Odin, but im not sure. While i was flashing the auto-root through Odin the screen turn of. After that it showed the "firmware upgrade encountered an issue. please select recovery mode in kies and try again" standard Samsung Message. I tried to reinstall the firmware through kies but with no luck.
[SOLUTION]
1. First I downloaded the correct firmware, from Sammobile. In my case it was Nordic Contries, cause i live in Denmark. Pick the one that suite you!!
2. Then i booted my first NotePro to download mode. It took my some tries, to get it working. First hold the power button. When the "Firmware Upgrade Encountered An Issue..." message turns off, in the same second, release the power button, and now select all three (Power + Volume Down + HomeKey). (You have to release the power button and press it again to make it work (At least for me)
3. Now install the stock firmware and your tablet is now working again.
4. (Optional) If you want to root your device and it didn't work the first time. Make sure you use the same Odin as showed in the tutorial.
Click to expand...
Click to collapse
i AM FACING A PROBLEM HERE, PLEASE HEALP!
First I have download "P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar. md5" for my Galaxy Note Pro 12.2 SM-P905. But unfortunately the file did not work for me and after all the long installation process odin says failed. and the last line on my device is
"ODIN : Invalid ext4 image"
so, after seeing that I thought the downloaded file ("P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar.md5 ") may be corrupted. then I download again another file from sammobile website for my note pro SM-P905 and that is "P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar. md5" but when tried to install by odin after long time same condition happen again. Odin says failed, and my device last line was Invalid ext4 image.
what is the problem?
how to flash SM-P905?
where is the exact proper flash file for my SM-P905?
Please Healp!!!

ornobohornish said:
i AM FACING A PROBLEM HERE, PLEASE HEALP!
First I have download "P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar. md5" for my Galaxy Note Pro 12.2 SM-P905. But unfortunately the file did not work for me and after all the long installation process odin says failed. and the last line on my device is
"ODIN : Invalid ext4 image"
so, after seeing that I thought the downloaded file ("P905XXUANAE_P905OXXANA7_P905XXUANA7_HOME.tar.md5 ") may be corrupted. then I download again another file from sammobile website for my note pro SM-P905 and that is "P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar. md5" but when tried to install by odin after long time same condition happen again. Odin says failed, and my device last line was Invalid ext4 image.
what is the problem?
how to flash SM-P905?
where is the exact proper flash file for my SM-P905?
Please Healp!!!
Click to expand...
Click to collapse
1. You may want to try using:
http://samsung-updates.com/
instead of samfirmware, if you're experiencing corrupted downloads from the latter (but it's not very probable... see pt 3)
2. At the moment I am testing new firmware revision, downloaded from samsung-updates: P905XXUAND1 for NEE region. It flashed fine. Also, for most of the time I have used P905XXUANC3 firmware for DBT region (Germany - even if I am not a German, I do not really care about csc stuff, and I got used to the fact that the newest firmwares were always released for DBT region first on my old "standard" Note 10.1). It was flashing fine, too.
3. The problem seems, however, lie not in the firmware, but in your hardware - or at least in the way it is handled by Odin or drivers. Note that *.tar.md5 archive contain md5 checksum concatenated to the very end of archive. When you're selected firmware file in Odin (in a PDA section), it probably took a longer while before the file appeared as selected - this is because meanwhile Odin is checking the checksum (and for that purpose, he has to read whole 1.5Gig file...). So: If Odin allowed you to flash the tar.md5 file - then it was NOT corrupted, otherwise it won't even be possible to start the process as of file wrong checksum!
4. THere is another possibility - that something bad happened to your pit section (it has been overwritten in result of flashing firmware for a wrong device) and your nand partition table is corrupted, which may probably result in an impossibility of flashing files or impossibility of mounting filesystems... I cannot help then, I have never faced such a problem in practice myself.
5. Pt 4, however, seems to be less possible than pt 3.
- Have you ever flashed any firmware with success?
- what do you mean by "long installation process"? A 10 minutes? An hour? Half-a-day?
- Have you been observing Odin while flashing? It's indicating which partition is being flashed atm - can you tell on which firmware part (system? hidden? cache?) did it fail?
- Try using different version of Odin (an older one, guess 3.07? not sure however - the one which has "PDA" section instead of a single-letter names)
- Try flashing from different PC
- use usb 2.0 port instead of 3.0 ones.
- try using different usb cable (I guess it'll may be the hardest thing to check because the cable seem to be quite unique )

Grateful to you...
esgie said:
1. You may want to try using:
http://samsung-updates.com/
instead of samfirmware, if you're experiencing corrupted downloads from the latter (but it's not very probable... see pt 3)
2. At the moment I am testing new firmware revision, downloaded from samsung-updates: P905XXUAND1 for NEE region. It flashed fine. Also, for most of the time I have used P905XXUANC3 firmware for DBT region (Germany - even if I am not a German, I do not really care about csc stuff, and I got used to the fact that the newest firmwares were always released for DBT region first on my old "standard" Note 10.1). It was flashing fine, too.
3. The problem seems, however, lie not in the firmware, but in your hardware - or at least in the way it is handled by Odin or drivers. Note that *.tar.md5 archive contain md5 checksum concatenated to the very end of archive. When you're selected firmware file in Odin (in a PDA section), it probably took a longer while before the file appeared as selected - this is because meanwhile Odin is checking the checksum (and for that purpose, he has to read whole 1.5Gig file...). So: If Odin allowed you to flash the tar.md5 file - then it was NOT corrupted, otherwise it won't even be possible to start the process as of file wrong checksum!
4. THere is another possibility - that something bad happened to your pit section (it has been overwritten in result of flashing firmware for a wrong device) and your nand partition table is corrupted, which may probably result in an impossibility of flashing files or impossibility of mounting filesystems... I cannot help then, I have never faced such a problem in practice myself.
5. Pt 4, however, seems to be less possible than pt 3.
- Have you ever flashed any firmware with success?
- what do you mean by "long installation process"? A 10 minutes? An hour? Half-a-day?
- Have you been observing Odin while flashing? It's indicating which partition is being flashed atm - can you tell on which firmware part (system? hidden? cache?) did it fail?
- Try using different version of Odin (an older one, guess 3.07? not sure however - the one which has "PDA" section instead of a single-letter names)
- Try flashing from different PC
- use usb 2.0 port instead of 3.0 ones.
- try using different usb cable (I guess it'll may be the hardest thing to check because the cable seem to be quite unique )
Click to expand...
Click to collapse
Dear Sir,
I am so surprised to see that somebody response me for the core of his heart! I am so pleased to realize that some body look at my problem very attentively! sir, thank you!
so,
** I have tried using different usb cable to flash
** I have tried both 3.9 or 3.7 odin
** I have tried different pc to flash
** I have used 2.0 or 3.0 both usb cable
** I have tried both kies3 or previous kies
** I am giving here the whole odin texts which
was shown
"<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P905XXUANC3_P905BTUAND2_P905XXUANA7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl1.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008> aboot.mbn
<ID:0/008> rpm.mbn
<ID:0/008> tz.mbn
<ID:0/008> sdi.mbn
<ID:0/008> NON-HLOS.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img.ext4
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/008> Removed!!
<ID:0/008> Added!!"
** Long installation process means 5-7 minutes! (I think it is normal, sorry)
** yes, I have used all high end android devices and all was rooted, installed cwm recovery, custom room, so I have experience well on android I am not new to play with android operating system. even now I am also using Note 3 with Omega custom rom and working great.
** I am thinking may be the problem is about pit. and I don't know where I will find a .pit file for SM-P905. some how may be the pit of my note pro is corrupted. i don't know actually I am not a developer!
Here all you wanted to know!
Dear Sir please help me to make alive my Galaxy Note Pro!
Please!!!

screen shot!
after the failed flashing operation all the time my devices shows, i am giving a screen shot!

Downloaded 3 Firmware
Already I have downloaded 3 rom, (because I thought the firmware file was corrupted) but by studying your post I know now when ever odin accept any firmware that means the rom file is not corrupted! thanks!
P905XXUANAE_P905DBTANA6_DBT.zip
P905XXUANAE_P905OXXANA7_BTU.zip
P905XXUANC3_P905BTUAND2_BTU.zip
i have download this 3 files!

Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers

mismatch
esgie said:
Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers
Click to expand...
Click to collapse
according to your link there is no file, named "recovery.img" but the file name is "libwfdsm.so"

DAAAAMN wrong link copied.
Wait a sec, I'll upload it in a while. Until then, you may start doing steps 6-8.
EDIT:
Here u go
http://www47.zippyshare.com/v/40021725/file.html
PS: using above method (a similiar one, to be exact...), figured out on my own to be exact, I have managed to unroot and revert to fully-stock state my old Note10.1, which I was not able to flash straight via Odin at all because the port's been broken, so I was able to send it to service center without any worries (at least related to the possibility of detecting the customization by the service) The difference is that you are able to flash files via Odin - except the system - but also that my device was booting at the very beginning, and yours not. Neverthless, with appropriate modifications, it should work on P905 too - or at least explain what's the reason of your issues.
Don't want to worry you, but as of now i am considering physical NAND damage as the most possible cause of the issue... But that's a theory only. Good luck.

problem solved!
esgie said:
DAAAAMN wrong link copied.
Wait a sec, I'll upload it in a while. Until then, you may start doing steps 6-8.
EDIT:
Here u go
http://www47.zippyshare.com/v/40021725/file.html
PS: using above method (a similiar one, to be exact...), I managed to unroot and revert to fully-stock state my old Note10.1, which I was not really able to flash straight via Odin because the port's been broken. The difference is that you are able to flash files via Odin - except the system - but also that my device was booting at the very beginning, and yours not. Neverthless, with appropriate modifications, it should work on P905 too - or at least explain what's the reason of your issues.
Don't want to worry you, but as of now i am considering physical NAND damage as the most possible cause of the issue... But that's a theory only. Good luck.
Click to expand...
Click to collapse
my dear sir, don't know how but my note pro start up automatically. before some minutes on my display "unauthorized operation occur, please restart you device" was showing. so after pressing ok, device tried to restart but it was stuck on recovery mode. so i started my device manually. when I pressed reboot from recovery everything was fine and still now it is working properly!
I don't know is going gone on my device. but is a mystery for me!
one thing, after trying to fix my devices long time my note pro battery was empty and i could not able to charge because it was stuck on download mode. after searching i got a boot image.tar.md5 for SM-P905. and install that Samsung logo appear, and device started charging. and after charge a few, It was start up!
now when I am connecting it with my pc, kies says I need to update my device. but previously my device was updated the latest software. I am giving the screen shot!
what will I do now? just update via kies and star to operate my device normally?

ornobohornish said:
my dear sir, don't know how but my note pro start up automatically. before some minutes on my display "unauthorized operation occur, please restart you device" was showing. so after pressing ok, device tried to restart but it was stuck on recovery mode. so i started my device manually. when I pressed reboot from recovery everything was fine and still now it is working properly!
I don't know is going gone on my device. but is a mystery for me!
one thing, after trying to fix my devices long time my note pro battery was empty and i could not able to charge because it was stuck on download mode. after searching i got a boot image.tar.md5 for SM-P905. and install that Samsung logo appear, and device started charging. and after charge a few, It was start up!
now when I am connecting it with my pc, kies says I need to update my device. but previously my device was updated the latest software. I am giving the screen shot!
what will I do now? just update via kies and star to operate my device normally?
Click to expand...
Click to collapse
Did I understood well that after emptying the battery of the non-working device out and recharging it back again at least a little, the device started to work again? Seems like... eeee...? some voltage circulating through the mainboard was the cause?
Well, I bet it was faulty or somehow corrupted boot.img (as it was the only partition you have flashed between the time the device seemed damaged and time the device started to work again), but I am not sure what really happened.
As to the firmware update question: from the screenshot attached I can see that you are now running XXUNAE firmware. Proposed XXUNC3 is a newer one so in general it is recommended to do the update. However, we cannot be sure anyhow if your device will not react in a same way as before. However, current updates seems to be minor ones (they concentrate on security policies and not on features...) so my recommendation is to leave it alone, at least until some more important update...

ohh nooo! befor reading you reply I was tried to update my device by kies. but same thing happen here. stuck on Invalid ext4 image!

i am so tired
esgie said:
Did I understood well that after emptying the battery of the non-working device out and recharging it back again at least a little, the device started to work again? Seems like... eeee...? some voltage circulating through the mainboard was the cause?
Well, I bet it was faulty or somehow corrupted boot.img (as it was the only partition you have flashed between the time the device seemed damaged and time the device started to work again), but I am not sure what really happened.
As to the firmware update question: from the screenshot attached I can see that you are now running XXUNAE firmware. Proposed XXUNC3 is a newer one so in general it is recommended to do the update. However, we cannot be sure anyhow if your device will not react in a same way as before. However, current updates seems to be minor ones (they concentrate on security policies and not on features...) so my recommendation is to leave it alone, at least until some more important update...
Click to expand...
Click to collapse
emergency firmware recovery start on kies but also stuck on "invalid ext4 image" and my my pc says to go service center! giving two screen shot!

ornobohornish said:
emergency firmware recovery start on kies but also stuck on "invalid ext4 image" and my my pc says to go service center! giving two screen shot!
Click to expand...
Click to collapse
My recommendation: repeat the procedure Ive posted earlier. Well se what happens
It looks like some part of your nand may be physically corrupted... and unwriteable.

before closing my notebook I am just hit the "CF-Auto-Root-viennalte-viennaltexx-smp905.tar" and surprisingly saw after successfully install the root file by Odin, my device start-up again. but problem is "unfortunately Samsung keyboard stopped" sowing. so I have install google stock keyboard and without Samsung keyboard it is running properly. though it is now working properly without samsung keyboard but I am little bit unhappy with my new Note Pro, I have just purchased this 3-6-14 and to day 5-6-14. I can not even look at thish properly because after purchasing it is disturbing! many thanks dear sir!
now I will try again with your instruction!

can not find "simg2img"
esgie said:
Ok, we shall try to flash firmware otherwise, using more advanced method.
Note that if ur knox isn't yet tripped - it WILL trip it, breaking your warranty (in this case it's better to send the device to service center - i suppose something's broken...). If it is tripped, you have nothing to lose...
1. Download:
http://www67.zippyshare.com/v/25492738/file.html
do not rename the file, it should be named recovery.img
2. Using this tool
http://forum.xda-developers.com/showthread.php?t=2446269
convert provided recovery.img to tar.md5 format
3. Flash it with odin (it should take a few sec to finish and it should succeed as recovery seems to flash ok on your device)
4. Enter recovery mode by holding power+home+vol up. Warning should appear about warranty and then custom recovery should appear on screen..
5. Using touch menu seek thru options and thru wipe menu format the system partition, as well as wipe/format data and cache (any errors?). Leave the device for a moment...
6. Simultanously, open one of 2+ gig tar.md5 firmwares (i recommend to choose one which you tried to flash with odin in your last trial) downloaded from sammobile with winrar or 7zip (if error about bad end of file appears ignore it) and extract system.img.ext4 somewhere...
7. Download simg2img from post #19
http://forum.xda-developers.com/showthread.php?t=2191930&page=2
and use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)
8. Copy system.img to root of empty micro sd card (fat32 or exfat formatted). Check if it has been copied correctly. Put the micro sd card into device. Reboot recovery once again
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!!! Also, process may take a LONGER while, like 10 mins, its ok, even if there is no progress indicator. Youll know it finished when keyboard will show back again (any errors here??)
10. Reboot AGAIN to recovery, go to Mounts menu, tick system, data and cache (does tick within system work?)
11. Go to terminal as in pt 9, but this time enter:
restorecon -R /cache
restorecon -R /data
restorecon -R /system
(errors?)
12. Reboot into system and cross yer fingers
Click to expand...
Click to collapse
dear sir,
in your link nowhere i found "simg2img"! I searched all the page number 9 but no where I found "simg2img"!!!
help please
---------- Post added at 10:28 AM ---------- Previous post was at 10:01 AM ----------
able to download simg2img from this link: http://web.djodjo.org/?a=download:android:tools:x86_linux:ext4tools
but how to use it to convert sparse image extracted from firmware tar.md5 (system.img.ext4) to raw image (let's say output file is called system.img)?
how to use simg2img?

Will this work with the SM-P900?
esgie said:
9. Advanced -> terminal/console -> use default directory ( / ), console window should open. Using simple onscreen keyboard input:
dd if=/external_sd/system.img of=/dev/block/mmcblk0p23
Be careful - if ur on P905 the last number should be "23", inputting otherwise may result in unrecoverable hard brick!
Click to expand...
Click to collapse
Hi Esgie.
I'm assuming that most of this would work for the SM-P900 (wifi only) version too? What would I use for the dd command in step 9?
Thanks for your help.
Jo Pop

ornobohornish said:
before closing my notebook I am just hit the "CF-Auto-Root-viennalte-viennaltexx-smp905.tar" and surprisingly saw after successfully install the root file by Odin, my device start-up again. but problem is "unfortunately Samsung keyboard stopped" sowing. so I have install google stock keyboard and without Samsung keyboard it is running properly. though it is now working properly without samsung keyboard but I am little bit unhappy with my new Note Pro, I have just purchased this 3-6-14 and to day 5-6-14. I can not even look at thish properly because after purchasing it is disturbing! many thanks dear sir!
now I will try again with your instruction!
Click to expand...
Click to collapse
I had same problem, install rom from greece. Some roms from sammobile and samsung firmware are giving errors, I have tested polish and british giving "odin: invalid ext4 image" error. After installing greece one everything works flawlessly, samsung keyboard also.

[Q] Unable to ODIN Upgrade from 4.3 to 4.4, instantly gives error msg

Solved
Had to unzip the file.
I'm trying to upgrade from 4.3 NC1 to 4.4 NE1, using the file "I535VRUDNE1_I535VZWDNE1_VZW.zip" from this thread: http://forum.xda-developers.com/showthread.php?t=2795659
- USB debugging is on
- Samsung Drivers installed
- KIES / Verizon programs not installed
- I'm in download mode
- Tried ODIN 3.04, 6, 7, 8.5 and the latest 3.09.
The second I hit the button, it fails 'instantly' with these messages. It doesn't check for md5 or anything, the file is the way I downloaded it (.zip).
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<OSM> All threads completed. (succeed 0 / failed 1)
Any help is greatly appreciated!! I'm out of guesses here. Google comes up all purple now, I've been checking online for similar problems. Anywhere from a different USB cord to a different USB port. No dice.
The device does connect, but it fails instantly - it's like it doesn't even try to flash the stock ROM. COM3 comes up as blue.

Did you unzip the file to a .tar or .tar.md5? Unzip the zip file, then select that file in pda box, it should work. I just did this same exact thing
Sent from my SCH-I535 using Tapatalk

dakota-boy said:
Did you unzip the file to a .tar or .tar.md5? Unzip the zip file, then select that file in pda box, it should work. I just did this same exact thing
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Grrrr. I feel like an idiot. Thank you buddy, flashing now.

[ROOT] How to root SAMSUNG GALAXY CORE 2 (SM-355H)[SuperSu][2015]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[ROOT] How to root and install CWM for SAMSUNG GALAXY CORE 2 (SM-G355H) [Super Su][2015]
This tutorial is about how to root samsung galaxy core 2 with Super Su but not king user.if you were searching for the Super Su app that will be installed after rooting then you have came to right tutorial.ok now lets start
:art-1::
first of all we have to install CWM recovery in our phone to install CWM recovery follow the steps
step-1: Download Odin3-v3.04.zip and CWM_6.0.3-1.zip file,extract both zip files.
step-2: Now connect your phone and make sure debugging mode is enabled from developer option of your phone and then open Odin and click on PDA and select the recovery.tar.md5(it is inside the CWM_6.0.3.zip you will see after you extract the zip) and click on start button.
step-3:It will take little time to complete the process and your phone will reboot. now your phone will be installed will custom recovery mode i.e CWM. now move to :art-2::
(installing CWM recovery mode in you phone is not only the reason to support the rooting using a zip file but it has very useful feature inside it,actually we are installing CWM recovery mode first because the stock reovery mode doesnot supports to root phone to install SuperSu.So to support everything we are installing CWM recovery mode).
:art-2::
Now in this part we will root our phone.so follow the steps.
step-1: download the UPDATE-SuperSU-Pro-v2.46.zip and copy it to your sdcard.
step-2: switch-off your phone and then press volume-up buttom + home buttom + power buttom at once and the phone will turn on with a little red exclamation symbon on top-left side , wait for few seconds after that CWM recover mode will be open and then select install zip > choose zip from sdcard and select UPDATE-SuperSU-Pro-v2.46.zip and reboot your phone.
step-3: congrats!!! your phone is now rooted and SuperSu will be installed
IF ANY PROBLEM ARISES FEEL FREE TO ASK
IF THIS HELPS YOU GIVE ME A THANK

jasbinkarki said:
(installing CWM recovery mode in you phone is not only the reason to support the rooting using a zip file but it has very useful feature inside it,actually we are installing CWM recovery mode first because the stock reovery mode doesnot supports to root phone to install SuperSu.So to support everything we are installing CWM recovery mode).
Click to expand...
Click to collapse
You can also root the phone in stock recovery. Via stock built in binary update and update script. Or you can change the mode via update zip or application uses root access.
If U use binary update shell some process won't be able to finish just because of the SE Linux - ( enforcing,permissive ) , TWRP and latest CWM uses full SElinux

It's not working for me. Please help.
Hi, not sure what I'm doing wrong. Followed the steps you provided. Below is the log of the process. I have a Samsung Galaxy Core 2.
Edit: Realised a difference between yours in the screenshot and mine, your ID:COM = 0:[COM3] and mine is 0:[COM7]. Whether this is relevant or not, I don't know. How to fix it, I don't know.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.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> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in advance for help.
P.S: Sorry in advance if the problem was stupid...

Run for galaxy core 2 duos ?

Does this work for Samsung Core II G355M ?

same happened to me

minor help for newbies
After complete day tiring research on this thread. i found a solution to problem faced by all.
in part 1 after step 1 just switch off your phone and reboot it using power button + volume down + menu button.
then continue it using volume up button.
then connect it to pc.
and complete above procedure from step 2 itself.
it worked for me.
---------- Post added at 09:10 PM ---------- Previous post was at 09:05 PM ----------
ccnh95 said:
Run for galaxy core 2 duos ?
Click to expand...
Click to collapse
Yes it works. i have tested it. go for it. any help needed then ask

The easiest and working root
Download this : http://forum.xda-developers.com/attachment.php?attachmentid=2936385&d=1410667995
Put it on your SD card in your phone
Turn off your phone
Hold VOLUME UP, POWER BUTTON AND START BUTTON at the same time!
A "boot menu" will pop up, and select "Apply update from external storage" and find the file I listed above and select it
Wait...and after a while your phone will be rooted.
Enjoy

Hi,
Just tried the same u did and suffers failure , but u can prevent this by connecting your phone with the downloading mode via Odin( for that u have to do. ( volume down + home + power button ). Now do the same step as u did earlier... U will get pass
To , [unicornsbreakwind ]

jasbinkarki said:
[ROOT] How to root and install CWM for SAMSUNG GALAXY CORE 2 (SM-G355H) [Super Su][2015]
This tutorial is about how to root samsung galaxy core 2 with Super Su but not king user.if you were searching for the Super Su app that will be installed after rooting then you have came to right tutorial.ok now lets start
:art-1::
first of all we have to install CWM recovery in our phone to install CWM recovery follow the steps
step-1: Download Odin3-v3.04.zip and CWM_6.0.3-1.zip file,extract both zip files.
step-2: Now connect your phone and make sure debugging mode is enabled from developer option of your phone and then open Odin and click on PDA and select the recovery.tar.md5(it is inside the CWM_6.0.3.zip you will see after you extract the zip) and click on start button.
step-3:It will take little time to complete the process and your phone will reboot. now your phone will be installed will custom recovery mode i.e CWM. now move to :art-2::
(installing CWM recovery mode in you phone is not only the reason to support the rooting using a zip file but it has very useful feature inside it,actually we are installing CWM recovery mode first because the stock reovery mode doesnot supports to root phone to install SuperSu.So to support everything we are installing CWM recovery mode).
:art-2::
Now in this part we will root our phone.so follow the steps.
step-1: download the UPDATE-SuperSU-Pro-v2.46.zip and copy it to your sdcard.
step-2: switch-off your phone and then press volume-up buttom + home buttom + power buttom at once and the phone will turn on with a little red exclamation symbon on top-left side , wait for few seconds after that CWM recover mode will be open and then select install zip > choose zip from sdcard and select UPDATE-SuperSU-Pro-v2.46.zip and reboot your phone.
step-3: congrats!!! your phone is now rooted and SuperSu will be installed
IF ANY PROBLEM ARISES FEEL FREE TO ASK
IF THIS HELPS YOU GIVE ME A THANK
Click to expand...
Click to collapse
I'm stuck in part 2, second step. When I choose that zip file it gives me this error:
E: Can't open /tmp/sideload/package.zip (STATUS: 255)
Then mobile restarts. But phone is not rooted!!!
I tried kingoroot zip too but it gives the same error.
Help please.
Thanks!

jasbinkarki said:
[ROOT] How to root and install CWM for SAMSUNG GALAXY CORE 2 (SM-G355H) [Super Su][2015]
This tutorial is about how to root samsung galaxy core 2 with Super Su but not king user.if you were searching for the Super Su app that will be installed after rooting then you have came to right tutorial.ok now lets start
:art-1::
first of all we have to install CWM recovery in our phone to install CWM recovery follow the steps
step-1: Download Odin3-v3.04.zip and CWM_6.0.3-1.zip file,extract both zip files.
step-2: Now connect your phone and make sure debugging mode is enabled from developer option of your phone and then open Odin and click on PDA and select the recovery.tar.md5(it is inside the CWM_6.0.3.zip you will see after you extract the zip) and click on start button.
step-3:It will take little time to complete the process and your phone will reboot. now your phone will be installed will custom recovery mode i.e CWM. now move to :art-2::
(installing CWM recovery mode in you phone is not only the reason to support the rooting using a zip file but it has very useful feature inside it,actually we are installing CWM recovery mode first because the stock reovery mode doesnot supports to root phone to install SuperSu.So to support everything we are installing CWM recovery mode).
:art-2::
Now in this part we will root our phone.so follow the steps.
step-1: download the UPDATE-SuperSU-Pro-v2.46.zip and copy it to your sdcard.
step-2: switch-off your phone and then press volume-up buttom + home buttom + power buttom at once and the phone will turn on with a little red exclamation symbon on top-left side , wait for few seconds after that CWM recover mode will be open and then select install zip > choose zip from sdcard and select UPDATE-SuperSU-Pro-v2.46.zip and reboot your phone.
step-3: congrats!!! your phone is now rooted and SuperSu will be installed
IF ANY PROBLEM ARISES FEEL FREE TO ASK
IF THIS HELPS YOU GIVE ME A THANK
Click to expand...
Click to collapse
Thanks for this. I'll be testing it out on my gf's phone this weekend. Hope to extend the battery life and give the phone some much needed new life.

com.android.phone
i have a samsung galaxy core 2 , model: SM-G355H/DS, SSN: -G355H/DSGSMH...it is powered by "android"....currently my phone has prompted me with a message: "Unfortunately, the process com.android.phone has stopped."......how do I activate it to start working again....i cannot access any of the information on the phone.....PLEASE HELP!....

mamadenniec said:
i have a samsung galaxy core 2 , model: SM-G355H/DS, SSN: -G355H/DSGSMH...it is powered by "android"....currently my phone has prompted me with a message: "Unfortunately, the process com.android.phone has stopped."......how do I activate it to start working again....i cannot access any of the information on the phone.....PLEASE HELP!....
Click to expand...
Click to collapse
I recommend u to do a factory reset! Make sure u backup ur data!
Press and hold: vol up+home buttom+power to go into recovery n wipe cache n factory reset this will solve ur problem

There is an easier way to root core 2
I will post soon
---------- Post added at 09:47 PM ---------- Previous post was at 09:44 PM ----------
I have a soution for the rooting problem. U have to do it with Kingroot zip file.
Requirements:
1. Galaxy Core 2
2. Custom or Stock Recovery(which they have lol)
3. Kingroot zip file
REMOVE SPACES FROM THE LINK PLZ
Download Kingroot zip file here in XDA thread: http: //dl-1.va.us .xda-developers. com /2/9/3/6/3/8/5/UPDATE-Kinguser-3.4.0.zip?key=-LqV9wsG96QMaSvqnl7jsg&ts=1462290490
Method:
1. Place the Kingroot zip file in your external SD card
2. Boot into recovery ( Power Down + Home Button + Power)
3. Select "Apply update from sd card" and choose Kingroot zip file
Wait for flashing and CONGRATS your Core 2 is Rooted
LIKE ME IT WILL HELP ME BECOME MORE HELPFUL
TechSTER™
---------- Post added at 09:53 PM ---------- Previous post was at 09:47 PM ----------
I have a soution for the rooting problem. U have to do it with Kingroot zip file.
Requirements:
1. Galaxy Core 2
2. Custom or Stock Recovery(which they have lol)
3. Kingroot zip file
REMOVE SPACES FROM THE LINK PLZ
Download Kingroot zip file here in XDA thread: http: //dl-1.va.us .xda-developers. com /2/9/3/6/3/8/5/UPDATE-Kinguser-3.4.0.zip?key=-LqV9wsG96QMaSvqnl7jsg&ts=1462290490
Method:
1. Place the Kingroot zip file in your external SD card
2. Boot into recovery ( Power Down + Home Button + Power)
3. Select "Apply update from sd card" and choose Kingroot zip file
Wait for flashing and CONGRATS your Core 2 is Rooted
LIKE ME IT WILL HELP ME BECOME MORE HELPFUL
TechSTER™

Unable to root, as when trying SSU, it just reboots with an error, which I cannot even read.

try vroot 100% working if not then change my name
Sent from my SM-G900H using XDA Premium 4 mobile app

FruitNuggets said:
Thanks for this. I'll be testing it out on my gf's phone this weekend. Hope to extend the battery life and give the phone some much needed new life.
Click to expand...
Click to collapse
Please:i need to know how to root my sm-g355h without a pc and external sd card

problem in rooting!
hi
i am a beginner and when i tried rooting my galaxy core 2 phone according to your steps i happened to see these messages..
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.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> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
it says operation failed and succeed 0
what may be the problem
please help me

unicornsbreakwind said:
Hi, not sure what I'm doing wrong. Followed the steps you provided. Below is the log of the process. I have a Samsung Galaxy Core 2.
Edit: Realised a difference between yours in the screenshot and mine, your ID:COM = 0:[COM3] and mine is 0:[COM7]. Whether this is relevant or not, I don't know. How to fix it, I don't know.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.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> Complete(Write) operation failed.
<ID:0/007> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in advance for help.
P.S: Sorry in advance if the problem was stupid...
Click to expand...
Click to collapse
did u people find solution to the above specified problem??

Thanks a lot. My phone was G355HXXU0AOE4 firmware and only your update v2.46 could root it.