So I was attempting to flash the CWM6 safe kernel to upgrade to CM9 beta 1 on my girlfriend's phone. The kernel flash didn't go well and the phone was stuck at the splash screen. I'm attempting to ODIN FH13 via One Click. ODIN sees the phone, and the process starts...but always fails at:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012>
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas/help?
Thanks in advance.
Nevermind...it all the of the sudden felt like working after 3 attempts.
Hello all
I've got a S4 mini here which I'm hoping I can use to upgrade from my old S2.. Problem is.. it doesn't turn on, charge, or anything. If i plug it into a Windows 10 machine I get a sound from Windows 10 saying the USB device has been connected but nothing from the S4 mini itself.
I'm just curious what i can do to get this thing running as its a really nice little phone and seems a nice upgrade from an S2.
I'm fairly technical and I have used tools such as Odin and such to root older Android phones but I thought I would seek advice here before trying anything as It has been awhile!
I look forward to any replys
Regards,
Jason
Ok some progress...
I've been running it inside an XP virtual machine as Windows 10 hates Odin and other tools. Anyway, Virtualbox does notice the device and names it "Qualcomm CDMA Technologies MSM QHSUSB_DLOAD" Is this some form of basic boot loader or recovery or?? I'm unsure myself and I hope maybe someone can tell me what Virtualbox is actually seeing and hopefully it's showing life to a point where i can reflash the device or at least get it running to a certain degree.
Also I've noticed if i say press and hold the power button in Windows 10 the USB disconnect sound with occur swiftly followed by a reconnect sound. Same applies for VOL Down + PWR + Home botton. I've tried running Odin which see's nothing on the COM port. My S2 shows up right away but the S4 mini shows nothing.
I think at this point it's worth mentioning this phone has come from an ex office environment so a failed custom ROM flash or anything is unlikely but of course whatever the case may be its certainly not well... I guess it's not completely dead as it's connecting as a USB device. Can anyone please advise me on how to get this re flashed/fixed or even just tell me what's actually going on here? As this is a bit bound me.
:good:
Ok so I've made some progress...
I added some files to a micro SD card (from the debrick.img) I used win32imager to write to the card and put it in and tried powering it up which has now made the phone vibrate twice and then turn on to a basic "BOOT RECOVERY MODE" screen in plain text.
It also says the following:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS. .
BOOT RECOVERY
WRITE 139008 sectors
ddi : mmc_read failed
ODIN MODE
PRODUCT NAME: GT-i9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANT VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION: Enable
Now if i load up Odin i can see it on COM5. At this stage I've downloaded a stock firmware from sammobile and I'm ready to load it. I tried it and it requested a PIT file so i found the correct one for my phone and it still wouldn't work. So i looked around on here for answers and found a guide someone had made. Downloaded the "kit" he had which has the following files:
BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
I've added all these where they should go, tried to run it and i get a red FAIL sign above ID:COM along with this error log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone please help me from here as I'm really not sure what is wrong? I've got it from a black screen which would do absolutely zero to doing something at least but I could really use a hand now... please? anyone?
By the way I'm using Odin3 v3.07 which i know isn't the latest but it is said to be the one to use for my S4 mini, could it be that a need the latest version?!
Help please. :good:
dreamscape440 said:
Ok so I've made some progress...
I added some files to a micro SD card (from the debrick.img) I used win32imager to write to the card and put it in and tried powering it up which has now made the phone vibrate twice and then turn on to a basic "BOOT RECOVERY MODE" screen in plain text.
It also says the following:
BOOT RECOVERY MODE
CHECK BOOT PARTITIONS. .
BOOT RECOVERY
WRITE 139008 sectors
ddi : mmc_read failed
ODIN MODE
PRODUCT NAME: GT-i9195
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANT VOID: 0x0
CSB-CONFIG-LSB: 0x30
BOOTLOADER RP SWREV: 2
WRITE PROTECTION: Enable
Now if i load up Odin i can see it on COM5. At this stage I've downloaded a stock firmware from sammobile and I'm ready to load it. I tried it and it requested a PIT file so i found the correct one for my phone and it still wouldn't work. So i looked around on here for answers and found a guide someone had made. Downloaded the "kit" he had which has the following files:
BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5
I've added all these where they should go, tried to run it and i get a red FAIL sign above ID:COM along with this error log:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.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> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone please help me from here as I'm really not sure what is wrong? I've got it from a black screen which would do absolutely zero to doing something at least but I could really use a hand now... please? anyone?
By the way I'm using Odin3 v3.07 which i know isn't the latest but it is said to be the one to use for my S4 mini, could it be that a need the latest version?!
Help please. :good:
Click to expand...
Click to collapse
Have you found the solution dreamscape440 ?
Hi Guys ,
When I connect my phone just vibrate so my last solution is to root it .so below my issues :
-Using Odin3 v1.85 ,I got that :
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery-clockwork-6.0.5.1-serranoltexx.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Using other Odin versions ,I got :
Stuck on initialization .
Also be informed I tried with different usb port ,different cables.
Odin 1.85 sounds old, I user Odin 3,09 that I downloaded from xda (see link below) to install custom recovery (TWRP) now but I have run clockwork earlier on my s4 mini (GT-i9195) and it works fine.
Odin 3.09 - http://forum.xda-developers.com/showthread.php?t=2353876
linol said:
Odin 1.85 sounds old, I user Odin 3,09 that I downloaded from xda (see link below) to install custom recovery (TWRP) now but I have run clockwork earlier on my s4 mini (GT-i9195) and it works fine.
Odin 3.09 - http://forum.xda-developers.com/showthread.php?t=2353876
Click to expand...
Click to collapse
When I plug my phone just vibrate and nothing happen after. when I want to power it also vibrate and nothing on screen .but I can enter on odin mode >
What's could be ? I need your support .
Thanks in advance
How about you plug your USB cable directly at the backside of CPU incase of desktop pc. and also Turn off AntiVirus and kill kies in task manager if its running.
But before doing any of that try connecting your phone to kies. and check if it can be connected. if not install the drivers.
thanks for your but didn't help ,below what I got :
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
You can try flash emergency firmware from Samsung kies. Never tested but maybe can bring back to life your phone.
kies can't detect my mobile
Have you installed the Samsung drivers?
Yes,installed
bingozingo said:
Yes,installed
Click to expand...
Click to collapse
Looks like your eMMC is dead.
How can I confirm that ?
bingozingo said:
How can I confirm that ?
Click to expand...
Click to collapse
IMO, the only way is to look for a full restore image of your device.
Keywords to use in your search are: i9195xxucnh5, rev01, low_user_ship, tar.md5
The full restore image is the one used by Kies to initialise the devise to its factory state. It can be a single file or, in most cases, 4 files (BOOTLOADER, AP, CP and CSC).
It contain the PIT file, necessary to re-partition the entire eMMc, and every image for each new created partition.
If you find that image, or a member can provide it, there are good chances that your phone come back to life.
If Odin fails to flash the image and says "can't re-repartition", then your are good to look for another chipset.
Sorry, i can't help you with links.
pls ,have you the steps to do that ?,also did you have the full name of the all files that can help for search .
pls help
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_I9195XXUBML4_2340422_REV01_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_I9195OXABML4_2340422_REV01_user_low_ship_MULTI_CERT.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..
I wanna be crazy .
Can you note exactly what is written on the Download Mode screen ?
Downloading
Do not turn off target!!
bingozingo said:
Downloading
Do not turn off target!!
Click to expand...
Click to collapse
No, i mean what is written in the upper left corner.
Odin Mode
product name : GT-I9195
Current Binary : samsung official
system status : official
Knox kernel lock : 0x0
knox warranty void : 0x0
csb-config-lsb : 0x30
bootloader ap swrev : 2
write protection : enable
bingozingo said:
Odin Mode
product name : GT-I9195
Current Binary : samsung official
system status : official
Knox kernel lock : 0x0
knox warranty void : 0x0
csb-config-lsb : 0x30
bootloader ap swrev : 2
write protection : enable
Click to expand...
Click to collapse
Nothing strange here...
Your bootloader can see the content of system partition.
Can you access stock recovery (Power Button+Volume Up) ?
If you can, do a factory reset then reboot.
When I want to enter on recovery mode( power+volume up ) ,it's just vibrate .nothing on screen
My phone restarted the other day on its own and then was stuck on the "Samsung Galaxy SIII" splash screen. No luck with soft resets and I tried to boot into recovery mode but was greeted with a "Recovery Booting..." text followed by a dead Android with a red caution symbol floating above it.
I am able to boot into download mode. I downloaded Odin 3.07 and multiple stock ROMs (https://forum.xda-developers.com/sho....php?t=1949687) since I wasn't sure which one. No luck writing any of the ROMs. Here is the log from Odin:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUEOH1_T999TMBEOH1_T999UVUEOH1_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried Kies 3 but it seems that version isn't compatible with this phone. I was unable to get Kies 2 to install on two different PCs.
Any thoughts or ideas for anything else to try? Thanks!
Greetings, I'm attempting to stock firmware my samsung galaxy s7 sm_g930a.
The problem arrose when I accidentally loaded the root file (theunlockr, I can't give the url due to the youth of this account) into the BL section in Odin. I tried loading a stock firmware from samsung/at-t and I get the the following message.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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/006> Odin engine v(ID:3.1101)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The phone is still able to load to download and boot options but the boot screen itself just loops. Comes on, stays for 2-3 seconds then blacks then comes back for 2-3 then blacks again. I have tried clearing the data, clearing the cache, kies says it isn't compatible, tried swapping ports, the only other option i need to try after posting this is trying a alternate usb cable. I have tried both odin3 v3.11 and Odin3 V3.12.
The download screen on the phone at the top left corner reads Odin Mode (high speed)
product name: SM-G930A
Current binary: Samsung Official
System Status: Official
FRP lock: on
Warranty Void: 0x0
Qualcomm secureboot: enable
AP swrev: B4(2, 1, 1, 1, 1)K1 S3
Secure Download: Enable
wrong thread
just realized this is the wrong thread apologies