Database Develop

[SOLVED FREE] URGENT Help before SERVICE [SOLVED FREE]

Hi, I tried to flash something in odin and my pc stopped usb connection, and now my phone can enter only in download mode.
When I try to flash something odin says write error. I searched on the internet and I saw that it might be an flash lock.
But I dont selected it in odin. I called samsung, and they recommended me a service. And it will be repaired for 28 USD . Can someone help me? As I helped others, now I need your help!
I will sent it to service in 3 days! Also, the repair is not free, because I dont reset binary counter....now is custom (5)

use 3 file rom file

Try wit Secure PIT file

Antox97 said:
Try wit Secure PIT file
Click to expand...
Click to collapse
amir_n71 said:
use 3 file rom file
Click to expand...
Click to collapse
Sorry but no one solution is working. I whink that I can't recover my photos from internal sdcard.
On phone appears: ,,odin transaction fail,, when I am connecting it....and on pc ,,write fail,,
What TO DO???!!!

All depends on what file the USB connection stopped.
If it was fat.bin, then it's pretty much dead.

MrMateczko said:
All depends on what file the USB connection stopped.
If it was fat.bin, then it's pretty much dead.
Click to expand...
Click to collapse
It says write error on any file. I don't know why, I never checked flash lock.
Also 1 click unbrick for samsung devices in not running on my pc.
(flash progress won't start)
-----2 days until service

Odin messages
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S6500DBGMK1_S6500DXXMK1_S6500DXECML1_HOME.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> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)

MaDaLiNoSt said:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S6500DBGMK1_S6500DXXMK1_S6500DXECML1_HOME.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> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I've NEVER seen that before It stop almost imediately Before flashing anything .. My Mini 2 stops in "Fat.Bin" .. Thats all .. did it showed any message at your phone ?? like "Secure Check Fail Id:0x95" ??

I never seen it too! I think that you must send your device into assistance, I'm really sorry

PHOTOS
Ezzam_Itachi said:
I've NEVER seen that before ... Did it showed any message at your phone ?? like "Secure Check Fail Id:0x95" ??
Click to expand...
Click to collapse
Now you can see how my phone is looking:
I see firmware error on power and recovery mode.
When I connect the usb cable in phone, I get error!
What to do??!! Next morning, tomorrow I will send it into service :crying:

Happy again
Hi, and thank you for all your feedbacks (posts). Now I recovered my phone with some pc softwares and everything is ok :victory:
Odin Log:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S6500DBGMK1_S6500DXXMK1_S6500DXECML1_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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> system.img.ext4
<ID:0/003> NAND Write Start!!
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> fat.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> appsbl
<ID:0/003> oemsbl
<ID:0/003> partition.bin
<ID:0/003> qcsbl.mbn
<ID:0/003> qcsblhd_cfgdata.mbn
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
PC Screenshot:
Note: Next time when someone will have connecting issues with phone, is easy to post here and I will give help !
Do not create a new thread, because there are too many threads based same error. (eg. recovery ramdump or not working)

Owh, now I remember that writings.. For that I have sent my device into service :/
When your device are coming back, don't flash any firmware! If you have a NFC model, you must flash a NFC model like XXLD2!

Waw !! You made it !! :victory: okay now I need your help ... How did you do that ?? I oftenly flash my phone with odin .. Unfortunately, It never .. NEVER pass the flash ..It always failed .. Maybe with your solution I can get this done .. Thanks for your help !!

Little Flashing TUT
Ezzam_Itachi said:
How did you do that?
Click to expand...
Click to collapse
Download mini 2 firmware from SamMobile
Click to expand...
Click to collapse
Simply enter the model number of your device in the search box and a list of latest firmwares will come up. To download a firmware, you will need to be logged in to your SamMobile account using your username and password.
Click to expand...
Click to collapse
Demo Firmware list:
Disclaimer
SamMobile & me are not responsible if you brick or damage your device by using the files available on SamMobile Firmware Portal. You are doing all at your own risk! Proceed only if you are 100% sure that you know what you are doing.
Click to expand...
Click to collapse
Download and install compatible Kies from Samsung
Select Kies 2.6 for devices launched before September 2013
Click to expand...
Click to collapse
Now lastest drivers should be installed via kies application.
Download and install Odin3 from internet.
Click to expand...
Click to collapse
Now boot phone in download mode via an key combination: Volume down + home + power
If your device is not recognized, or windows failed istalling drivers (CDC or other driver)
use Zadig to force reinstall drive. Zadig can be found in heimdall unbrick pack for windows.
Click to expand...
Click to collapse
An alternative of Zadig is Microsoft Device manager. Select uninstall device from app menu, and then move usb cable to another port.
This solution might not solve your problem.
Click to expand...
Click to collapse
Good luck with flashing!
About you fat.bin error:
-Download another compatible rom
-That's it! : )

Amazing! Congratulations

Antox97 said:
Amazing! Congratulations
Click to expand...
Click to collapse
Thanks :laugh:

Thanks !!

Ezzam_Itachi said:
Thanks !!
Click to expand...
Click to collapse
No problem
Sent from my GT-S6500D using Tapatalk 2

[Q] Hard Bricked my s3 mini gti8190

Well i hard bricked my phone I think? I tryed to use the s5 styled rom stock Virginty V14 and I updated to the latest version of the baseband anr6 or something because that was in the rom setup while in twrp 2.7.1.0, I was on a pacman 4.4.4 custom rom before that, and I think it changed my normal bootlogo screen to i890t? instead of i890. I cannot boot into recovery anymore, ive tryed flashing over cyanogenmod 11 from novafusion, but nothing, ive tryed to flash recoverys, and nothing just a bootloop, this is the first time i've ever had this problem and I was just wondering how I fix it and if it can be fixed, I can still get into odin mode if theres a file or anything for download to fix this? I'm not sure why it did this, just need my phone back asap, any help would be appreciated

As you can get Odin to work, install original firmware from sammobile
http://www.sammobile.com/firmwares/
Sent from my GT-I8190N running SlimKat

Already tryed that, no luck, tryed to change the param folder too idk what to do

look here.
Put battery out and in.
Download laFleur ROM, boot into download-mode and flash it.
After that, flash custom recovery like TWRP from Android-Andi.
After that flash any custom ROM you like.
HTH

tryed it man, no luck again, like after i flashed that param.sfl file, it started to like show like a kind of broken screen kinda thing everytime i try to boot my phone up or boot into recovery, obviously the buttons still work, I really need to have a talk to the dev but since i cant post on the thread I was hoping someone could ask for me? edit: I think my download mode isnt working either because it says all this
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I8190XXAMA2_809600_REV00_user_low_ship.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_QXE_I8190QXEAMA1_20130109.163004_REV00_user_low_ship.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> STE_boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> STE_boot1.img
<ID:0/003> STE_boot2.img
<ID:0/003> ipl.bin
<ID:0/003> modem.bin
<ID:0/003> ssgtest.img
<ID:0/003> normal.bin
<ID:0/003> normal2.bin
<ID:0/003> param.lfs
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
-------------------<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)--------------------- <-- this line shows up after the phone reboots, and it just keeps in a bootloop after its all flashed and then like a minute or two later these lines show up, but my phones not even connected, just a constant ugly screen bootloop... help.

So it seems I was flashing the wrong region country firmware its working again thanks was hard to find the new Zealand firmware haha, now my first splash boot is still like a TV do I flash the param.LFS file for gt-i8190t model and will I have to fresh install the stock firmware again?

imvyzel said:
So it seems I was flashing the wrong region country firmware its working again thanks was hard to find the new Zealand firmware haha, now my first splash boot is still like a TV do I flash the param.LFS file for gt-i8190t model and will I have to fresh install the stock firmware again?
Click to expand...
Click to collapse
So instead of getting the Gt-I8190 and samsung boot image and animation you have some buzz image like a tv, do this go to novafusion .pl I can't post links yet <.< s3 Mini--> Extras --> Original Boot logo download the correct one for your device, you have to install this via TWRP it should fix it

STRATOS99KINGZ said:
So instead of getting the Gt-I8190 and samsung boot image and animation you have some buzz image like a tv, do this go to novafusion .pl I can't post links yet <.< s3 Mini--> Extras --> Original Boot logo download the correct one for your device, you have to install this via TWRP it should fix it
Click to expand...
Click to collapse
You may have to flash it a couple of times if it doesn't work the first time
Sent from my GT-I8190N running SlimKat

Install the original firmware. If that doesn't work, using Odin install clockworkmod recovery and then install cm11.... Once you install cwm recovery remember to format the media and data!!
Sent from my GT-I8190 using XDA Free mobile app

Loop reboot after the "FIX Ram Management"

Hi
My S6 is in loop reboot after i edit the build.prop... I have the original build.prop on my pc but how to restore it ??? Please help!

master-i said:
Hi
My S6 is in loop reboot after i edit the build.prop... I have the original build.prop on my pc but how to restore it ??? Please help!
Click to expand...
Click to collapse
If you have TWRP installed, you can just ADB the file over. Easy.
If you only rooted and want to preserve your KNOX flag, you need to ODIN back to stock and then re-root. It's not destructive, so it's not nearly as bad as it sounds

I don't have twrp for now but can i Install it on download mode ? I just tried to install it and it stop on Start upload (on odin)

Follow these instructions. Download ODIN from that link too
http://forum.xda-developers.com/tmo...irmware-sm-g920t-firmware-odin-guide-t3077706

Do i lose my data? and where Can I find the [Unified Driver Installer] on step 2?

No you won't lose your data at all, you will lose root, but all you need to do is re-root the phone.
http://developer.samsung.com/technical-doc/view.do?v=T000000117

I think it's easier to flash only the build.prop no? is it possible?
Thanx to help me bro!

No at this point, IMO, this is the easiest way to get you back to where you were. I assume you're on the stock ROM just rooted.

Yes, I were on the stock room just rooted by PingPong. Hope it will not make my phone slower or make it crash more often... :/

Yeah just ODIN back to stock, then re-root using PingPong, it's really not as bad as it sounds. All of your apps and user data including all settings will still be there.

@se1000
Please look this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G920TUVU1AOCG_G920TTMB1AOCG_G920TUVU1AOCG_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> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Have you had your phone in download mode for a while? If so, try rebooting the phone

se1000 said:
Have you had your phone in download mode for a while? If so, try rebooting the phone
Click to expand...
Click to collapse
Of course I just retried again same error... I can't understand because I see the 0:COM3 on Odin...

Are you using the ODIN from the link? I had problems with other versions

se1000 said:
Are you using the ODIN from the link? I had problems with other versions
Click to expand...
Click to collapse
Yes the V3.10

Were you trying to run ADB earlier? Try rebooting the PC

I closed and reopen Ondin on Administrator and now it's blocked with: <ID:0/003> SetupConnection..

Try a different USB cable or different USB port. Seems ODIN can get a bit finicky

I rebooted PC and my Phone and unplugged and still the same
maybe it's because i tried to install twrp?

Shouldn't matter, as long as you're in download mode and ODIN shows light blue it should work

Can't Unroot Note 4 5.1.1 using ODin

For the past couple of days I've been unable to unroot my device using Odin, which I have done many of times on the past. I went to Sammobile and got the latest firmware to flash back to stock, but everytime I attempt to do so the process Fails. USB Debugging is enabled so I don't have a clue what the problem could be. I will list some general information as well as the results of the Odin process below:
Baseband Version: N910TUVUD0K2
Odin process result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1DOK2_N910T3TMB1DOK2_N910T3UVU1DOK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Updated: I've stumbled across a thread here on XDA which has a mirror link to Stock TW Firmware/Bootloader/Modem N910TUVU2DOK2, and after flashing this mirror link using Odin... my phone now is unrooted and back to stock. Many thanks to ShrekOpher for posting the mirror link and here is a link to his post: http://forum.xda-developers.com/note-4-tmobile/development/mirror-stock-tw-t3260858

Same issue
I just posted about this same issue a couple of days ago, if you go to my only post ive done so far you can see how we are in the same boat. What were you using before you got to your problem, which custom ROM?

I had this problem on the note edge. What helped me was flashing cwm recovery and wiping everything

Trebor313 said:
For the past couple of days I've been unable to unroot my device using Odin, which I have done many of times on the past. I went to Sammobile and got the latest firmware to flash back to stock, but everytime I attempt to do so the process Fails. USB Debugging is enabled so I don't have a clue what the problem could be. I will list some general information as well as the results of the Odin process below:
Baseband Version: N910TUVUD0K2
Odin process result:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910T3UVU1DOK2_N910T3TMB1DOK2_N910T3UVU1DOK2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks
Click to expand...
Click to collapse
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...

Catfish197621 said:
I just posted about this same issue a couple of days ago, if you go to my only post ive done so far you can see how we are in the same boat. What were you using before you got to your problem, which custom ROM?
Click to expand...
Click to collapse
I'm currently using [DOK2] TEKXodus HYBRID N4 URv7

mdiaz33685 said:
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Click to expand...
Click to collapse
I check and made sure that the reactivation lock was disabled, but it still didn't work. I guess I will keep an eye open to see if this issue can get resolved sometime in the near future

mdiaz33685 said:
make sure u didn't check in settings the reactivation lock,
use twrp, wipe everything except sdcard... then boot into downloader mode, and it should work, I do know the reactivation lock should be the only thing to stop you.
hope that helps...
Click to expand...
Click to collapse
What are the odin settings for doing this install? I can't get it to recognize the file
Nevermind, quick google showed i should extract the file which im not used to doing for roms and use "AP"

waywardfrantz said:
What are the odin settings for doing this install? I can't get it to recognize the file
Nevermind, quick google showed i should extract the file which im not used to doing for roms and use "AP"
Click to expand...
Click to collapse
U have to unziip the firmware and in Odin u need to goto AP and point to the firmware... sometimes i have to remove the extention .md5 after u unzip the firmware depending on which Odin u use...
make sure u have the samsung drivers installed..

mdiaz33685 said:
U have to unziip the firmware and in Odin u need to goto AP and point to the firmware... sometimes i have to remove the extention .md5 after u unzip the firmware depending on which Odin u use...
make sure u have the samsung drivers installed..
Click to expand...
Click to collapse
I can't Odin to stock unless I change the name of the firmware file to .tar. it skips the md5 check I believe.
---------- Post added at 06:17 PM ---------- Previous post was at 06:14 PM ----------
Also go to supersu and do a full unroot before. I'm thinking maybe the supersu backup script could cause issues too

Freezing on the splash screen logo

Hello, I have a big problem with my I9305, which had stock rom 4.4.4 XEO and root. The phone has been resetting on its own from time to time. Now the phone is dead, it freezes on the splash screen logo. Installing new room via Odin and DM doesn't work:
<ID:0/003> 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/003> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
In recovery menu there is message:
failed to mount /cache
Can't mount /cache/recovery/last_recovery
failed to mount /system
end so on...
Click to expand...
Click to collapse
What should I do?

Siadulinho said:
Hello, I have a big problem with my I9305, which had stock rom 4.4.4 XEO and root. The phone has been resetting on its own from time to time. Now the phone is dead, it freezes on the splash screen logo. Installing new room via Odin and DM doesn't work:
In recovery menu there is message:
What should I do?
Click to expand...
Click to collapse
Might be a corrupt nand, if that so, you will need to replace the board...sorry for bad news, maybe other member can have a different opinion.

Any options to make backup of SMS?

Siadulinho said:
Any options to make backup of SMS?
Click to expand...
Click to collapse
I don't think so, a corrupt NAND corrupts it all, i don't think you can boot anything on the phone anymore, however, a user here in XDA was able to use a memory card as a complete NAND and he even flashed a ROM and booted fine,but he was a skilled one, i don't know how he did it.
But he lost all data of course, so even if you did what he did, you won't get your SMSs.