Hello forum,
I am interested in creating a recovery PDA file that I can flash for odin of my Samsung Galaxy Player 5. Could someone go about telling me how it could be done? Thanks in advance.
Jisrest said:
Hello forum,
I am interested in creating a recovery PDA file that I can flash for odin of my Samsung Galaxy Player 5. Could someone go about telling me how it could be done? Thanks in advance.
Click to expand...
Click to collapse
Your mean is you want to backup data in your device？
I think you can use an application named Titanium Backup.
I have no authority to send links.You can search it on the Internet.:silly:
Jisrest said:
Hello forum,
I am interested in creating a recovery PDA file that I can flash for odin of my Samsung Galaxy Player 5. Could someone go about telling me how it could be done? Thanks in advance.
Click to expand...
Click to collapse
On device as root
Code:
dd if=/dev/block/mmcblk0p13 of=/sdcard/factoryfs.rfs
dd if=/dev/block/mmcblk0p11 of=/sdcard/zImage
On pc, put those two files (from /sdcard) in a tar archive.
Would the terminal Emulator do this correctly?
Jisrest said:
Would the terminal Emulator do this correctly?
Click to expand...
Click to collapse
Yes, as long as you run su to give you root access.
Thanks! I will try in a few to see how this goes.
Would this save my account information, WiFi passwords, etc?
Jisrest said:
Thanks! I will try in a few to see how this goes.
Would this save my account information, WiFi passwords, etc?
Click to expand...
Click to collapse
No. That just saves your rom and kernel. For backup purposes, you will need mmcblk0p10 (efs - your wifi and bluetooth addresses), mmcblk0p14 (dbdata), and mmcblk0p16 (/data). mmcblk0p17 is your media/downloads/whatnot, but obviously you cannot copy it into itself. I just don't know the appropriate names for an Odin tar.
And in case you were wondering, partition 1 is an extended partition holding everything else, 2-4 are not used, 5-9 are for the bootloaders, 12 is a backup kernel, and 15 is cache.
You're really helpful and insightful, thank you for your time!
Last question, sorry for being a novice. But.. once I am done with the terminal Emulator, save it as a tar.md5 file and it'll be flashable on odin?
Jisrest said:
You're really helpful and insightful, thank you for your time!
Last question, sorry for being a novice. But.. once I am done with the terminal Emulator, save it as a tar.md5 file and it'll be flashable on odin?
Click to expand...
Click to collapse
No problem.
You will need to transfer the two files to your computer, and use a tool like 7-zip to add them to a tar archive. The tar file's name should not end in .md5, or Odin will expect it to have extra data that isn't there.
I get a failure whenever I attempt to flash with Odin.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Removed!!
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factory.rfs
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Jisrest said:
I get a failure whenever I attempt to flash with Odin.
Click to expand...
Click to collapse
It should be factoryfs.rfs.
7-Zip is renaming it.
Tried for a third time, and got this error..
Code:
<ID:0/008> Added!!
<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> factoryfs.rfs
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Maybe it's that I don't have PARAM, SBL, and BOOT?
Doing further testing I believe its my player acting up.
Jisrest said:
Tried for a third time, and got this error..
Code:
<ID:0/008> Added!!
<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> factoryfs.rfs
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Maybe it's that I don't have PARAM, SBL, and BOOT?
Doing further testing I believe its my player acting up.
Click to expand...
Click to collapse
I'm not sure what your issue is -it seems right- but I hope you still get it to work.
Thank you.. but im giving up. I guess im not meant for this.
My phone has gone into emergency recover and I've tried to recover it by flashing it with both "Odin" and the samsung "SimpleUpgradeTool" but it has failed everytime I've tried it.
I have the SCH-530 from US Cellular and am unsure on what to try next.
Any and all help is greatly appreciated.
The following is the ouput message from Odin ---
Code:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
mdahlke said:
My phone has gone into emergency recover and I've tried to recover it by flashing it with both "Odin" and the samsung "SimpleUpgradeTool" but it has failed everytime I've tried it.
I have the SCH-530 from US Cellular and am unsure on what to try next.
Any and all help is greatly appreciated.
The following is the ouput message from Odin ---
Code:
Odin v.3 engine (ID:3)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
recovery.img
NAND Write Start!!
cache.img
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
While flashing with odin make sure ur kies is completly closed or from kies tools, preferences, uncheck option open kies while phone connects restart and try should work
Sent from my GT-I9500 using xda premium
I have the SCH-530 from US Cellular and am unsure on what to try next. Wrong forum its not I9300 . Firmware / mods from here will brick your phone . jje
I downloaded the stock firmware from this thread: http://forum.xda-developers.com/showthread.php?t=2357200
I checked the md5 and it matched up perfectly, so no corrupt download.
I am in Download Mode on my Galaxy S4 SCH-i545 and I have Odin3 v3.07. I placed the extracted .zip file (which is a .tar.md5 file) into the PDA slot in Odin, placed a checkmark in it and clicked start.
I get the following message:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am currently stuck on the yellow exclamation screen on my device and desperately need help as I want to return the device. I have searched the forums and on google but what I have found hasn't helped me.
Thanks for any help!
I really need help and am sorry for replying to myself; however, I have tried everything I have found and nothing has worked. I can only get into download mode and to the yellow exclamation. Odin is failing and nothing shows up in Kies Emergency Recovery.
Don't worry, we can figure this out. Read through the entire thread you posted, the last post in that thread states that the guy was stuck on the yellow exclamation as well, but was relieved for some reason or another. You may find your answer there, and if not, private message that person to ask how they got around it.
What build do you have? MDK or ME7? The link you have is for ME7. If you need MDK, here are two different stock versions.
Why are you flashing this is the big question? Is the screen broken or something?
Hi guys,
I have a problem with my S2 (i9100)...I don't understand how it's possibile, but my phone suddenly it has fallen in bootloop, after unaffected reboot. (I wasn't using it).
So I have tried the instructions at bootloop in this thread http://forum.xda-developers.com/galaxy-s2/development-derivatives/kernel-t2291756
After the wipe of dalvik cache and cache I wasn't able to enter into recovery mode but only in download mode and thus I have tried to flash philz kernel but ODIN failed the flash
And now in ODIN i can't flash anymore but it's stuck in "NAND write start".
Please can someone help me? Thanks!
My Device: GT-i9100
ROM: WizzedKAT v. 3.3
KERNEL: Apolo 4.14 Regular
You need to go back to stock, not another custom kernel. Get a stock rom from Samfirmware, and find Hopper8's 'Odin troubleshooting' thread stickied in General - go through the troubleshooting stuff in a methodical manner until you get a successful flash.
There's a chance this might not fix the problem on its own & you still might need to do a factory reset after the flash. If even that doesn't fix the problem, flash the 3 part firmware linked in the thread, which will wipe your phone of whatever is causing bootloop hopefully.
Once you're back at stock you can re-root your phone & restore a nandroid or reinstall custom rom/whatever.
Thanks for reply!
I'm trying to flash a stock ROM (this: I9100XWLSW_I9100XXMS3_I9100ITVLS2_HOME.tar.md5) but ODIN failed the flash.
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9100XWLSW_I9100XXMS3_I9100ITVLS2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Instead flashed 3 part firmware, ODIN stuck in data.img or failed
ODIN v.1.85
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> data.img
ODIN v.3.09
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> data.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried different versions of ODIN and 2 different cable and computer (whit one yesterday I flashed s3 mini without problems)
It's possibile that emmc may be corrupted?
(Sorry for my bad English :S)
Possibly, but you essentially have two choices here:-
1) Keep trying the stuff in that thread over & over I.E all of it (not just a few things), as many times as you need to. There is nothing that can be suggested in these situations which isn't in that thread, it's 'the bible' for this sort of problem. Perseverance always fixes these when they're recoverable (and most are).
2) Give up & pay for a motherboard replacement or a new phone.
I know what I'd be doing if I was in your situation.
HELP-mE?
• my gt-i8730 hard brick [qhsusb_dload]
• i am SEND SDCARD debrick.img and put on my sdcard, then...
flashing PIT file on odin, occored this error
Quote:
ODIN:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
PHP:
PHONE:
BOOT RECOVERY MODE
CHECK BOOT PARTITTONS. .
COPY FROM T-FLASH. .
FLASH READ FAILURE
ODIN MODE
PRODUCT NAME: GT-I8730
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: NONE
QUALCOMM SECUREBOOT: ENABLE
SECURE CHECK FAIL: PIT
ERROR: There is no pit binary.
sorry and thanks, i am brazil and noob.
and sorry posted outside the area, but I'm desperate and nobody helps me.
Duplicate of [HELP-ME] MY GT-i8730 HARD BRICKED QHSUSB_DLOAD
Closed.