Database Develop

[Q] SGS GA i9010 - need help getting it work again

hi,
sorry for my english, i'm from germany^^
i need your help:
i tried to flash my with odin3 v1.70 to I9010XXJL1, but i failed
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9010XXJL1-REV00-ALL-low-CL752194.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
my phone doesn't start anymore - just a picture looking like this:
[phone]..
{
"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"
}
..[cpu]
thanks in advance for helping

leertaste90 said:
hi,
sorry for my english, i'm from germany^^
i need your help:
i tried to flash my with odin3 v1.70 to I9010XXJL1, but i failed
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9010XXJL1-REV00-ALL-low-CL752194.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
my phone doesn't start anymore - just a picture looking like this:
[phone]..
..[cpu]
thanks in advance for helping
Click to expand...
Click to collapse
You bricked your phone. You are going to need to go to download mode and use odin again. And from personal experience, using that i9010xxjl1 rom, it is a hit or miss, just gotta keep trying. I got it to work after flashing it a second time. You might need a Jig to get into download mode.

hmm... i got a new problem. maybe, the firmware is crap?
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Set PIT file..
<ID:0/009> DO NOT TURN OFF TARGET!!
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> boot.bin
<ID:0/009> Sbl.bin
Click to expand...
Click to collapse
i got a little pice of that downloadbar on my phone screen, but it doesn't move odin does nothing, when Sbl.bin is getting downloaded to the phone.
is there an other firmware i could try?

Okay, ehhh tell me where you got the file and what you put into odin okay ) I'll help as best as I can. Worst case scenario would be flashing a different rom. And what phone do you have? Just tell me everything so I can understand and fix your problem (if I can).

=)
i got the firmware I9010XXJL1 from samfirmware.com/WEBPROTECT-i9010.htm.
i've a samsung galaxy s giorgio armani (gt-i9010).
i tried it with odin v1.0, v1.3 and v1.7... none of them worked
inside the rar file:
I9010XXJL1-REV00-ALL-low-CL752194.tar.md5
MODEM_I9010XXJK9_REV_00_CL737172_SIGNED.tar.md5
my pit-file:
s1_odin_20100512.pit
i tried it several times that way:
img6.imagebanana.com/img/0f1379it/odin.jpg (can't include external links)
thank you =)

Try rebooting your PC, use a different usb port, etc. I had same thing happen to me before. Rebooting fixed my problem.

worked!
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9010XXJL1-REV00-ALL-low-CL752194.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Set PIT file..
<ID:0/010> DO NOT TURN OFF TARGET!!
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> boot.bin
<ID:0/010> Sbl.bin
<ID:0/010> param.lfs
<ID:0/010> factoryfs.rfs
<ID:0/010> cache.rfs
<ID:0/010> zImage
<ID:0/010> Removed!!
<ID:0/010> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
but the next problem^^
on the android system recovery <3e>:
[...]
update media. please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata:media:Can't mount DBDATA:
your storage not prepared yet. please use UI me nu for format and reboot actions.
copy default media content failed.
Click to expand...
Click to collapse
what to do now?

Next problem??
Is this when you turn on the phone??? Usually it'll give you options on what to do as well...

yes,
my phone starts, galaxy intro plays, after finishing i get a black screen and it vibrates several times...
i did in 3e:
wipe date/factory reset
wipe chace partition
but it didn't helped.

Any more options? there should be more, I remember when I flashed this rom I was able to ignore that 3e warning and the phone would be back to normal.

yes:
reboot system now
apply sdcard:update.zip
wipe date/factory reset
wipe chace partition
format internal sd-card
when i start my phone, it doesn't work... it just vibrates^^

Do you already tried the reboot option then? I was afraid of that.... The part where your phone just vibrates.
Sent from my SAMSUNG-SGH-I897 using XDA App

yes, doesn't work any other ideas?

I have an idea, but first, can you still get into download mode? If yes, I can still help you ^^
Sent from my SAMSUNG-SGH-I897 using XDA App

yes, i can get into download mode

now i downloaded i9010XXJK9_XXJL1_OXA including:
1. GT-I9010-CSC-MULTI-OXA725151[1].tar.md5
2. I9010XXJL1-REV00-ALL-low-CL752194.tar.md5
3. MODEM_I9010XXJK9_REV_00_CL737172_SIGNED.tar.md5
4. SP6160.axf
where to put these files on odin? the first at CSC, the second at PDA. but last two?

hoooooooooo, it works again! hahah, yeah i like
thank you sooooo much for helping =)

Well I'm glad you got it working. Sorry for the delayed response, I passed out. But reason why you messed up was because of two things. I did the same mistake myself as well when I flashed this rom.
1. When you used Odin, you only use the .pit file if you needed to repartiton and if you have 3 files (Phone/PDA/CSC) Since samfirmware.com was stupid when they released this. They didn't have the third file (CSC) so the only way to flash this rom was to use the 1 file method. You only needed to put the i9010xxjl2 file into the PDA section and simply flash the rom.
(But it looked like you got a different i9010 rom and were able to flash it)
2. When you were in the android 3e directory, that's what the .pit file do and the lack of a CSC file caused the data/cache wipe and partition to do nothing but send your phone into a blank screen.
I guess with this information, I might as well post the guide to flash the i9010 Armani Froyo rom >.<

Leertaste,
where did you download these files and where do they go in odin?
i'm having the same problem as you had..
please let me know

leertaste90 said:
now i downloaded i9010XXJK9_XXJL1_OXA including:
1. GT-I9010-CSC-MULTI-OXA725151[1].tar.md5
2. I9010XXJL1-REV00-ALL-low-CL752194.tar.md5
3. MODEM_I9010XXJK9_REV_00_CL737172_SIGNED.tar.md5
4. SP6160.axf
where to put these files on odin? the first at CSC, the second at PDA. but last two?
Click to expand...
Click to collapse
Where you install the number 4? on Odin?

[Q][HELP]Stuck In Emergency Download Mode Screen

I'm stuck decided to try the latest UK Version of Tizen OS loaded it in Odin 3.09 into the AP Slot pressed start and the damn Odin decided to pop up with a error and close out in Windows, now if I try anything still download mode and reopened Odin 3.07 or 3.09, but it never fully installs I'm in the emergency download kies recovery screen.
Is it possible to install a Odin'ed firmware from here, from what I've learned of the screen/area of recovery, it's the same thing as download mode. I tried the latest Tizen OS again and all it did was sit forever at zImage area of flashing.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> V700XXUCOA2_V700OXACOA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
Or I get this:
<ID:0/016> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> V700XXUCOA2_V700OXACOA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/016> Removed!!
<ID:0/016> Added!!
<ID:0/016> Removed!!
<ID:0/016> Added!!
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/016> Removed!!
<ID:0/016> Added!!
<ID:0/016> Removed!!
<ID:0/016> Added!!
<ID:0/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016> Initialzation..
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> sboot.bin
<ID:0/016> NAND Write Start!!
<ID:0/016> zImage
It just sits there at BOOTLOADER, have to go about getting this far by disconnecting the watch and holding in the power button till it reboots and turns back on to the same screen. Then plug it back up again and press start again in Odin.
I tried on two PC's and this as far as it gets or what all it does.
What can I do to fix this?
{
"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"
}
Don't care if I have to flash JB or TZ, just as long as it's back up and running.

Fixed it had to flash Android MK7 first, now to trying Odin'ing Tizen again

Anddddd zImage gets stuck again... Grrrr

Hi!
I have the same problem... I comes from Null 23 and I want install Tizen
You find the solution for this problem?

Try to flash the tizen NE9 first

Lost galleries, used Dr.Fone for Android and ended up with Odin3

Hi Experts,
Today I lost main DCIM gallery on my Samsung Note 5. I tried to use Dr.Fone application in standard and avanced mode. At the end of the day I didn't manage to retrieve any data. The worst thing is I cannot startup my phone due to "Recovery is not Seandroid Enforcing" error.
I downloaded Singtel Firmware but in Odin3 I get error as follows:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> cm.bin
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
{
"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"
}
Could you please let me know what do I do wrong? By any chance can I recover my phone settings without flashing any data? I still have a hope I will be able to retrieve lost pictures from my gallery.
Thanks and Regards,
KM

What I would like to add below is the message on my Samsung Note 5 after Odin3 failed:
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT NAME: SM-N920I
CURRENT BINARY: Custom
SYSTEM STATUS: Official
FRP LOCK: OFF
Secure Download : Enabled
KNOX WARRANTY VOID: 1 (0x0500)
RP SWREV: B:2 K:0 S:0
SW REV. CHECK FAIIL. DEVICE: 2, BINARY: 1
How can I proceed with this case?

So will trip Knox on my Sammy devices ?

Phone broke after unsuccessful flash by odin

I had a fully working Galaxy S3 i9300 and when I got my new phone, it's been in my drawer for a couple of months until my sister needed a temporary phone and I wanted to give this phone to her so I turned it on and it wouldn't load the OS. I charged it to 50%, still nothing.
Then I thought maybe flashing the firmware and then upgrading to a custom ROM would fix whatever the problem is. I searched around and downloaded this ROM:
http://updato.com/firmware-archive-select-model?record=7A9319A15E6411E6B055FA163EE8F90B
The flash failed. I re-tried, and it got stuck. So I restarted the phone. Now it won't respond to any input and when I connect the charger to it, it shows a white screen like the image below:
{
"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"
}
I tried to put it to download mode with no success.
What should I do? is there anything to be done?

Seems to be bricked. Most probably something messed up with boodloader. When you flashed new os did it stop in middle of doing something?

McXred said:
Seems to be bricked. Most probably something messed up with boodloader. When you flashed new os did it stop in middle of doing something?
Click to expand...
Click to collapse
Yes, it was flashing and stopped with an error.
What should I do then? Any solutions?

BTW, I used a program called 300K to go to download mode. The program said that it's on download mode but I have no idea if it's on DL Mode or not. (the screen is still the same) Then connected the phone to Odin and tried to flash again (the screen was the same though).
This is the odin log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9300XXUGPE1_I9300AMNGPF1_I9300BVUGNB2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<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)

Anyone?

alirezanoori said:
Anyone?
Click to expand...
Click to collapse
You have to flash pit file. if you dont want to risk go to gsm shop

McXred said:
You have to flash pit file. if you dont want to risk go to gsm shop
Click to expand...
Click to collapse
I did that (or at least tried to do that) but since the screen doesn't share, I don't know what's going on. However, when I try, odin gets stuck on a message saying "Getting pit" or something similar.

I suggest you to use odin 3.7 for this device. Place the pit file and do repartition. I hope it help.. Good luck.

Boot Loop ODIN stuck at aboot.mbn

For the past 2 years I have been loving my rooted Note 4, always keeping up with the most recent firmware. However, this week I have been having trouble getting out of a bootloop on my SM-N910T.
Last time my phone was broken, KIES was able to help reset it. So this time, I started by trying to use KIES once again. Unfortunately, I got the message "the connected device is not supported by KIES" once it is plugged in. When I try firmware upgrade and initialization in kies, I get the error "SM-N910T" does not support initializing. I get this same error message when I tried using an older version of smartswitch that still allows for initializing.
Since KIES/Smartswitch had failed, I tried downloading the most recent firmware from sammobile and pushing it to the device using ODIN, which I run as an administrator. To do this, I followed the instructions in this video , which asks you to first factory reset and format the system. I did this on my phone using TWRP and even tried wiping the dalvik cache, the system, the data, the internal storage and the cache. I then tried using ODIN to push the firmware while the phone is in download mode. When I plug in the phone, the blue box shows up in odin indicating that the drivers are updated. Despite this, I keep getting stuck on the step called "aboot.mbn". It stays on this step for about an hour before reading "XmitData_Write." After these attempts, the phone no longer
I have tried using an older version of ODIN and even a different version of the firmware. I have also found a .PIT file unique to the phone (here) to re-partition the phone but that failed as well saying it could not be re-partitioned.
Any suggestions would be greatly appreciated!
Picture of ODIN:
{
"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"
}
ODIN Log:
<OSM> N910TUVU2EQI2_N910TTMB2EQI2_N910TUVU2EQI2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> __XmitData_Write
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

i had the same problem i had to use a different usb cable