Database Info

Getting Galaxy Ace GT-5839i back to stock

I tried putting on the jellyblast rom for the GT-5830i onto this phone (I heard they have the same hardware) but unfortunately it did not go so well and now the phone hangs at the Galaxy Ace logo screen. So now the problem is getting the stock firmware back onto the phone - I have downloaded the Vodafone stock firmware for the phone (UK) from sammobile.com and tried to flash it with Odin.
I have tried with Odin v1.85 and v1.87 although they both fail:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5839iBULK1_S5839iVODLE1_S5839iBULK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> BcmCP.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am using the totoro_0623 pit file as per this thread: http://forum.xda-developers.com/showthread.php?t=1811196 and then just using the PDA file. I check the Re-Partition, Auto Reboot and F. Reset Time boxes when I attempt this.
I found another method also using Kies through "Firmware upgrade and initialization" - I add "GT-S5839i" as the model name (which it accepts) and my S/N but then it complains that "the model information that you have entered cannot be verified; the device initialization cannot proceed".
I am at a loss as to what to do now, tried using the back ports on my desktop and the supplied USB cable to no avail. Any help would be greatly appreciated!
Additionally, in recovery it mentions that it fails to mount /system, and rfs format fails when wiping data and cache whilst in recovery.

ornottin are
With a different cable it gets to the modem part of the flashing then bsod's my computer with pfn_list_corrupt (happened twice in a row at the same point). What is going on here?

Problem solved, google "Galaxy Ace S5830i Flasher& PIT file 100%work" if you have the same issues as me.

[Q] Having trouble upgrading from 2.3.6 to 4.1.2

I have an ATT Samsung SGH-i727 running 2.3.6.
I tried to update it to 4.1.2 stock ATT with Kies, but Kies did not work; it said it could not contact the upgrade server.
So I downloaded Odin 1.85, downloaded ATT stock 4.1.2, and selected the ROM with the PDA button and pressed start. Auto reboot and Reset time were checked.
An hour or two passed and Odin was hanging on system.img.ext4. It never completed. I rebooted, and now it is stuck in "Firmware upgrade encountered an issue. Please selecte recovery mode in Kies and try again."
I tried starting over in Odin, but it says that the write operation failed when it gets to system.img.ext4.
Any guidance on how to get this working?
Thanks!
P.S. Here is the full log from Odin after trying again:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> amss.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> boot.img
<ID:0/004> cache.img.ext4
<ID:0/004> mdm.bin
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

Re-download the Odin file. It's probably a bad download. Check it's md5 after downloading.

go through the troubleshooting section here [HOWTO] NEWB GUIDES To: | RESTORE TO STOCK
note: in your log this line
"<OSM> KIES_HOME_I727UCMC1_I727ATTMC1_844945_REV02_user_l ow_ship.tar.md5 is valid"
there is a space between "l" and "o" in the word "low", did you edit the file name b4 using odin or is the space there because of the copy/paste to the post.
if I had to guess it would be driver issues since odin confirmed the md5 was ok, but go through the trouble shooting section from above link

Also a trick I've learned with Odin, instead of just double clicking to open, right click and select run as administrator. haven't had a hang on it since using this method. Maybe that will help.

Fixed
Redownloaded firmware using link in troubleshooting guide and updated successfully. Thanks.

Galaxy Tab 2 p5100 no adb in download mode

Hi guys,
as the title said i got a problem with running my tab2 in download mode.
when i run the device in dl mode my pc (win 7) shows it as samsung modem, and if i start in recovery mode it shows as adb device.
odin can find the device anyway but failed on any flash process.
when i run in dl mode i get several outpot from the console on the device:
Odin download mode (protocol2.1)
Reason: Force Key
Secue Mode: Secure
Check Signature: Check
Custom Binary Downloads: no (0counts)
Current Binary: Samsung official
waiting usb cable...
connected press the start of odin3!!
so device is seen in odin i choose the .md5 and get following odin output:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-espresso10rf-espresso10rfxx-gtp5100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
after this my tab dl screen tells me following:
fail to download 8/sos data:2569... and so on
tegra_nand_write Error to download partition_odin err0xffffffff
after this i have to do a factory reset with recovery mode to get the tab working again because it want to connect to kies and make a force restore
i already flashed several mobile phones so i think i know what i have to do but with this tab... im just confused
i already tried to setup several drivers manually, tried pc´s with kies and pc´s which never had kies installed before...same issue
I tried several .md5 files
so my question is now... what am i doing wrong? how can i get the adb driver working in download mode not in recovery
hope someone can help me

cassialla said:
Hi guys,
as the title said i got a problem with running my tab2 in download mode.
when i run the device in dl mode my pc (win 7) shows it as samsung modem, and if i start in recovery mode it shows as adb device.
odin can find the device anyway but failed on any flash process.
when i run in dl mode i get several outpot from the console on the device:
Odin download mode (protocol2.1)
Reason: Force Key
Secue Mode: Secure
Check Signature: Check
Custom Binary Downloads: no (0counts)
Current Binary: Samsung official
waiting usb cable...
connected press the start of odin3!!
so device is seen in odin i choose the .md5 and get following odin output:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-espresso10rf-espresso10rfxx-gtp5100.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
after this my tab dl screen tells me following:
fail to download 8/sos data:2569... and so on
tegra_nand_write Error to download partition_odin err0xffffffff
after this i have to do a factory reset with recovery mode to get the tab working again because it want to connect to kies and make a force restore
i already flashed several mobile phones so i think i know what i have to do but with this tab... im just confused
i already tried to setup several drivers manually, tried pc´s with kies and pc´s which never had kies installed before...same issue
I tried several .md5 files
so my question is now... what am i doing wrong? how can i get the adb driver working in download mode not in recovery
hope someone can help me
Click to expand...
Click to collapse
brother i cannot remember but there is a thread here which installs adb on every pc so you can search or try it

[HELP] Odin Fail on GT-P5113 Tab 2 10.1

First off, I have TWO (2) of these guys. Same model number. I flashed 1 successfully. These came from a flea market. The one that upgraded successfully was working. The other one, was labeled "PARTS" and just bootloops.
This one, I am UNABLE TO GET INTO RECOVERY by pressing "PWR+VOL DOWN", unlike the first one. I AM able to get into DOWNLOAD mode and attempt to flash the 4.2.2 update like I did the first one.
The problem is ODIN is throwing a "FAIL!" on this one.
Code:
<ID:0/014> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P5113UEUCMK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/014> Odin engine v(ID:3.1005)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> SingleDownload.
<ID:0/014> boot.img
<ID:0/014> NAND Write Start!!
<ID:0/014> FAIL!
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am using ODIN 3.10. Not sure if there is any way to force a recovery. I don't OWN these, they are a Co-Workers. Just curious if using a PIT file to repartition would be best, or if I need to flash a new bootloader or something. In DOWNLOAD mode, the screen says:
Odin Mode:
Product Name: GT-P5113
Custom Binary Download: No
Current Binary: Samsung_Official
Any help?
Update:
Tried to use a PIT file to restore the partition tables, but all I get is "There is no PIT Partition". I have tried a few PIT files for the 5110/5113 as well as trying to flash it standalone and with said ROM. Not sure if there are any other methods or steps involved.
Any help would be awesome!

[Q] Is Galaxy S5 bricked? mmc_read failed

Galaxy S5 SM-G900F running Lollipop (BOE5) rooted with CF-Auto-root worked fine for about 5 months until few daus back. After device restart it entered download mode with message "Could not normal boot; ddi: mmc_read" failed. It does not boot into recovery either, instead it enters the Download mode with the error messages. Any flashing attempt with Odin stops at "Odin : flash read failure" on the device and the "There is no PIT partition" error on Odin on PC. Is the device really hard bricked and cannot be repaired via Odin or similar?
Things I have tried so far:
-flashing Lollipop and KitKat stock ROMs with Odin
-flashing TWRP and stock recoveries with Odin
-booting with SD with S5 debrick.img (boots into DM with errors)
-flashing PIT file only and PIT file together with stock ROM
-different Odin versions, different USB ports
Odin output when flashing ROMs:
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BOJ1_G900FOXX1BOJ1_G900FXXU1BOJ3_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>
<ID:0/008> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Odin output when flashing PIT:
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> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008>
<ID:0/008> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Unfortunately cannot add picture link wtih DM errors.

DroidTim said:
Galaxy S5 SM-G900F running Lollipop (BOE5) rooted with CF-Auto-root worked fine for about 5 months until few daus back. After device restart it entered download mode with message "Could not normal boot; ddi: mmc_read" failed. It does not boot into recovery either, instead it enters the Download mode with the error messages. Any flashing attempt with Odin stops at "Odin : flash read failure" on the device and the "There is no PIT partition" error on Odin on PC. Is the device really hard bricked and cannot be repaired via Odin or similar?
Things I have tried so far:
-flashing Lollipop and KitKat stock ROMs with Odin
-flashing TWRP and stock recoveries with Odin
-booting with SD with S5 debrick.img (boots into DM with errors)
-flashing PIT file only and PIT file together with stock ROM
-different Odin versions, different USB ports
Odin output when flashing ROMs:
Code:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BOJ1_G900FOXX1BOJ1_G900FXXU1BOJ3_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>
<ID:0/008> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Odin output when flashing PIT:
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> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008>
<ID:0/008> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Unfortunately cannot add picture link wtih DM errors.
Click to expand...
Click to collapse
hey, man. did you ever get this fixed? I'm having the same problem with my G900v

jerkybeef said:
hey, man. did you ever get this fixed? I'm having the same problem with my G900v
Click to expand...
Click to collapse
I have not gotten it fixed. Got another device, the g900f is waiting for repair if that will be applicable.

jerkybeef said:
hey, man. did you ever get this fixed? I'm having the same problem with my G900v
Click to expand...
Click to collapse
Got the device back from repair, looks like they have replaced the internals (board (?) and/or the memory chips; I don't know that much about physical architecture).