Develop Bugs

[Q] Odin fail, bricked?

I attempted to return my phone to stock via Odin, I used the T-Mobile ROM and I have a Telus phone, stupid I know. The Odin attempt failed.
I then tried with the Telus version and Odin just gave me a quick run through, didn't flash, I hit the reset button, tried again, same thing.
I closed Odin in desperation, restarted it and tried to flash the Telus version, it is now stuck here:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T989DTLKJ3_T989DTLKJ3_T989DTLKJ3_HOME.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..
I followed the guide, I do have the correct ROM, the phone is still in recovery and I know if I attempt a restart it will likely hard brick, can I save this???

Just re-run it until it completes. keep trying, sometimes it takes a few tries to go through

xcrazydx said:
Just re-run it until it completes. keep trying, sometimes it takes a few tries to go through
Click to expand...
Click to collapse
+ 1
Sent from my SGH-T989 using xda premium

I ended up unplugging the phone, shutting down Odin and reinstalling Samsung drivers. Plugged the phone back in and it installed, phone is all good now.

[Q] SGH-T999

So... a guy brings me a Galaxy S3 SHG-T999 and says it won't boot up..gets stuck on the Galaxy Boot Logo Screen.
The phone will not go into recovery mode,
PC will not charge the phone while plugged in.
PC does not recognize the phone when at boot up screen.
When plugged in not booted, a gray battery Icon appears and disappears.
The phone will go into download mode
When in download mode the Text shows that everything is still stock and no binary has been downloaded.
All correct drivers installed
I have tried using Kies and Odin to flash using the Stock Rom
Kies see the device but fails, Odin sees the device and reads the file but fails to write
in Odin I have Reboot checked F Reset checked
Is there anything I can do to get the phone to boot from an SD card so that I can reset the phone and reflash to stock ROM?

If Odin Failed while the phone was in download mode, please post the Odin log.

Odin Log
Perseus71 said:
If Odin Failed while the phone was in download mode, please post the Odin log.
Click to expand...
Click to collapse
This is my Odin log
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_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..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

Second Odin Log Fail
I tried a different Stock rom and did not get a fail but it also did nothing at all
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)

Something's wonky here. Did you check the .PIT checkbox ?

[Q] Need Help! Screen discolored in ROM flash

Hi guys,
PLEASE HELP!
I have been reading a lot on XDA. I have been working on putting together a custom Samsung galaxy tablet 3 7.0 for a in dash car install. Everything was going well, I had even designed a custom interface that I was going to post when done. That was until I tried to flash autodroid 1.2 ROM like an idiot (http://forum.xda-developers.com/showthread.php?t=2789993)
History: sucessfully rooted phone,
running Clockworkmod for T217s,
Backup was run in both Titanium Backup pro and Clockwork before flash
Symptoms: Autodroid flash was shown as successful.
Upon restart the tablet went to the Samsung Galaxy Tab boot screen then stopped.
There is a brown discoloration all over the screen with black edges and the boot logo slowly faded out.
Plugged in or not the screen will not change.
None of the buttons will work.
Cannot power on or off to reach download mode.
Tried 1 soft brick solution: Run odin 1.7 with original firmwear .tar file in PDA, and P1_add_hidden in PIT
Being that I cannot enter download mode ID:Com shows yellow with 0:[COM8]
Odin 1.7 cannot move past:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T217SVPUBNK1_T217SSPTBNK1_T217SVPUBNK1_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..
Please let me know what I can do to fix this? Is this even a soft brick as suspected, I have no idea what a brick is even like? Any bit of help is appreciated. Thank you!

Samsung S4 Mini GT I9195 Wont Turn on??

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 ?

Accidentally deleted OS, cant flash Stock OS via ODIN

Hi
Yesterday i installed TWRP on my Tab S4 Wi-Fi and accidentally deleted the OS.
I tried to flash it via Odin but it immediately fails.
I have switched USB cables, FW-Versions, Odin Versions and even the PC.
Odin Log:
<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..
<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.1301)..
<ID:0/006> File analysis..
<ID:0/006> Total Binary size: 6291 M
<ID:0/006> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)

I'm having the same issue
Also unable to install ROM via TWRP, it fails and force reboots a few seconds in

DouJinFlip said:
I'm having the same issue
Also unable to install ROM via TWRP, it fails and force reboots a few seconds in
Click to expand...
Click to collapse
I get this error even when I try to go to download mode to flash via ODIN
"Security error: this device has been flashed with unauthorized software & is locked."

r3flux said:
I get this error even when I try to go to download mode to flash via ODIN
"Security error: this device has been flashed with unauthorized software & is locked."
Click to expand...
Click to collapse
I had the same issue on my Tab S4, tried all combinations of buttons and somehow it booted to download mode.

I can get to Download mode by first rebooting into TWRP recovery, but the issue I've been having is that Odin fails to flash anything to the tablet. I've tried multiple stock ROMs and no Boot, AP, or CSC file succeeds to load.

DouJinFlip said:
Odin fails to flash anything to the tablet.
Click to expand...
Click to collapse
Make sure you have all the USB drivers installed and working. If it's not that, then try using a different version of Odin and TWRP. You will have to find the right combination between Odin and TWRP. I remember I had to do this when flashing my Samsung Note.
Also, did you make sure Developer Options > OEM Unlocking is enabled to unlock the bootloader? And that you signed out from your Google/Samsung account? When you first connect to Odin it tells you that you should do this, otherwise it will trip FRP.