Hi,
I have a S3 mini I8190L, i rooted and install rom manager which worked for a while then bricked the phone... now when i tried to turn it on it shows me the blank screen that you can see in the picture, anyway the phone does goes to download mode but when i tried to root again with odin the process fails. does anyone knows if there is something i can do with this??
Thanks.
Try to flash stock recovery in odin, then a prerooted or stock odin firmware.
When things like this happen, always try to go back to stock.
onidroc said:
Hi,
I have a S3 mini I8190L, i rooted and install rom manager which worked for a while then bricked the phone... now when i tried to turn it on it shows me the blank screen that you can see in the picture, anyway the phone does goes to download mode but when i tried to root again with odin the process fails. does anyone knows if there is something i can do with this??
Thanks.
Click to expand...
Click to collapse
hi
write this file with odin on the bootloader and fix problem
lauri_ylonen said:
hi
write this file with odin on the bootloader and fix problem
Click to expand...
Click to collapse
How will a efs.img to bootloader for i9300 fix this problem on a i8190L?
Sounds like a hardbrick to me..
onidroc said:
Hi,
I have a S3 mini I8190L, i rooted and install rom manager which worked for a while then bricked the phone... now when i tried to turn it on it shows me the blank screen that you can see in the picture, anyway the phone does goes to download mode but when i tried to root again with odin the process fails. does anyone knows if there is something i can do with this??
Thanks.
Click to expand...
Click to collapse
What error does odin give
AssToast said:
What error does odin give
Click to expand...
Click to collapse
It just says that the process has failed...
onidroc said:
It just says that the process has failed...
Click to expand...
Click to collapse
What version of odin you use?
Sent through time and space from my s3mini/CM10.1
tys0n said:
What version of odin you use?
Sent through time and space from my s3mini/CM10.1
Click to expand...
Click to collapse
i've tried 1.8 and 3.07 with the same result
onidroc said:
i've tried 1.8 and 3.07 with the same result
Click to expand...
Click to collapse
Try with View attachment 2279292
If it fails, paste the log here.
tys0n said:
Try with View attachment 2279292
If it fails, paste the log here.
Click to expand...
Click to collapse
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8190_stock-recovery.tar.md5 is valid.
<OSM> HOME_I8190LUBALJA_I8190LUWAALJ4.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> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
onidroc said:
Hi,
I have a S3 mini I8190L, i rooted and install rom manager which worked for a while then bricked the phone... now when i tried to turn it on it shows me the blank screen that you can see in the picture, anyway the phone does goes to download mode but when i tried to root again with odin the process fails. does anyone knows if there is something i can do with this??
Thanks.
Click to expand...
Click to collapse
you have my same problem, can only be solved ponendo file PIT of this phone and ok everything
http://forum.xda-developers.com/showthread.php?t=2456256.
ok we only require that file to solve our problem. :cyclops:
onidroc said:
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I8190_stock-recovery.tar.md5 is valid.
<OSM> HOME_I8190LUBALJA_I8190LUWAALJ4.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> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
you have a problem with setting up the connection:
kill all process of kies via task manager
change usb cable
change usb port
uninstall, re-install driver
change pc
samersh72 said:
you have a problem with setting up the connection:
kill all process of kies via task manager
change usb cable
change usb port
uninstall, re-install driver
change pc
Click to expand...
Click to collapse
Yes, I was about to say the same. There's a problem with connection.
pepetico1 said:
you have my same problem, can only be solved ponendo file PIT of this phone and ok everything
http://forum.xda-developers.com/showthread.php?t=2456256.
ok we only require that file to solve our problem. :cyclops:
Click to expand...
Click to collapse
... i've looking that file for the latin american version but it seems to be nowhere.....
samersh72 said:
you have a problem with setting up the connection:
kill all process of kies via task manager
change usb cable
change usb port
uninstall, re-install driver
change pc
Click to expand...
Click to collapse
i've done all same result.....
onidroc said:
... i've looking that file for the latin american version but it seems to be nowhere.....
Click to expand...
Click to collapse
I think it's same for all i8190's. goldenxx.pit
Sent through time and space from my s3mini/CM10.1
tys0n said:
I think it's same for all i8190's. goldenxx.pit
Sent through time and space from my s3mini/CM10.1
Click to expand...
Click to collapse
i've tried with that one with no improvement
Related
Hi,
I own Samsung Galaxy S Plus. I've been using GIGABREAD+ ROM but since I want my warranty back I tried to restore stock ROM but failed so far. First I tried flashing stock ROM directly, using Odin but it displayed "<1> big partition size!!" and than "<1> something.bin download.." and for a few hours nothing happened. Then i restored my phone and tried Broodrom rc5 but same thing happens :"<1> big partition size!!" and "<1> partition.bin download.." taking forever. Do you know how to solve this problem?
P.S sorry if topic already appeared but couldn't find it. sorry for my english too.
You have to put the repartition flag on Odin.
But use with carefully, you need a ROm that support repartition.
Otherwise you risk brick your device
casaprocida said:
You have to put the repartition flag on Odin.
But use with carefully, you need a ROm that support repartition.
Otherwise you risk brick your device
Click to expand...
Click to collapse
Thanks, but how do I do that?
Try This HERE
EwOkie said:
Try This HERE
Click to expand...
Click to collapse
Thank you. Please correct me if I'm wrong. I am supposed to download older version of Odin, since 4.43 doesn't have PIT option, and then use it with PIT to repartition and flash with stock ROM?
1.85 ODIN is fine thats what i use Check my signature on How To to Flash with ODIN
Yeah Odin 1.85, 512 pit file, repartition checked, and flash gingerbread jw4 would do nicely.
You will also have to flash dbdata.rfs as PDA in Odin after the rom if you get 'can't mount' rfs error.<<<< Actually, you probably won't need that because you're still GB-based.
Then just reboot and profit.
Sent from my GT-I9000 using Tapatalk 2
Okay, one more question before I start. In a package of stock rom i downloaded there is a file called "APBOOT_I9001XXKQ6_CL980980_REV00_user_low_ship_ONLY.tar.md5". As I understand it's bootloader files. Am I supposed to falsh this too?
knuckles1978 said:
Yeah Odin 1.85, 512 pit file, repartition checked, and flash gingerbread jw4 would do nicely.
You will also have to flash dbdata.rfs as PDA in Odin after the rom if you get 'can't mount' rfs error.<<<< Actually, you probably won't need that because you're still GB-based.
Then just reboot and profit.
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
amkxxx said:
Okay, one more question before I start. In a package of stock rom i downloaded there is a file called "APBOOT_I9001XXKQ6_CL980980_REV00_user_low_ship_ONLY.tar.md5". As I understand it's bootloader files. Am I supposed to falsh this too?
Click to expand...
Click to collapse
Try it without the bootloader first. Unnecessarily flashing a bootloader is better avoided. I have a gt-i9000, not a 9001 and I've not had a bootloader included with a ROM before, but I know to only flash bootloaders when you have to, or you can end up in a world of hurt.
Sent from my Nexus 7 using Tapatalk HD
I tried flashing but nothing happened, and I mean nothing. phone is as it was. here's odins output:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SMD_PDA_I9001XXKQ6_CL980980_REV00_user_low_ship_EMMC.smd.md5 is valid.
<OSM> SMD_MODEM_I9001XXKPK_CL977162_REV00_user_low_ship_EMMC.smd.md5 is valid.
<OSM> SMD_CSC_GT-I9001-CSC-SERKP7_EMMC.smd.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..
<OSM> All threads completed. (succeed 0 / failed 1)
amkxxx said:
I tried flashing but nothing happened, and I mean nothing. phone is as it was. here's odins output:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SMD_PDA_I9001XXKQ6_CL980980_REV00_user_low_ship_EMMC.smd.md5 is valid.
<OSM> SMD_MODEM_I9001XXKPK_CL977162_REV00_user_low_ship_EMMC.smd.md5 is valid.
<OSM> SMD_CSC_GT-I9001-CSC-SERKP7_EMMC.smd.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..
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Like I said, I have a gti9000, not a 9001, so your flashing files are a bit different, but if I were you I'd try downloading a different stock firmware, could be a dodgy download, seen that plenty of times.
Sent from my Nexus 7 using Tapatalk HD
Solved
I used same rom but witch odin 4.43 and somehow it worked, even though it displayed "big partition!" error. So I'm back on stock. Thaks for all your help!
I was wandering if anyone could create a backup from from the firmware that I will provide, since I can´t load my phone using Odin 4.07 because it will crash and close on my PC, so all I need is to someone to load it into their Ace, use CWM to create a backup rom, and load it here so I can just use my CWM and load it into my phone?
Here´s the firmware, if any one would like to help me recover my phone to it´s original fw, since this wasn´t in Samfirmware.
http://www.hotfile.com/dl/184799313/0a34cc8/S5830MWHLK2_S5830MICELK1_ICE.zip.html
Mike02x said:
I was wandering if anyone could create a backup from from the firmware that I will provide, since I can´t load my phone using Odin 4.07 because it will crash and close on my PC, so all I need is to someone to load it into their Ace, use CWM to create a backup rom, and load it here so I can just use my CWM and load it into my phone?
Here´s the firmware, if any one would like to help me recover my phone to it´s original fw, since this wasn´t in Samfirmware.
http://www.hotfile.com/dl/184799313/0a34cc8/S5830MWHLK2_S5830MICELK1_ICE.zip.html
Click to expand...
Click to collapse
LOL!!! ODIN 4.07 WHAAT???
Did you try using Odin 4.38????
Viper The Ripper said:
LOL!!! ODIN 4.07 WHAAT???
Did you try using Odin 4.38????
Click to expand...
Click to collapse
My bad, I meant Odin 4.38 and also Odin 3.07.
flashing other device nandroid backup can cause problem try using odin in some other pc
Mike02x said:
My bad, I meant Odin 4.38 and also Odin 3.07.
Click to expand...
Click to collapse
Unistall kies and samsung drivers, reboot your PC and install the lastest driver update then try again
You can flash a custom rom too via recovery
manoj94 said:
flashing other device nandroid backup can cause problem try using odin in some other pc
Click to expand...
Click to collapse
Thanks!
Will try in another device!
Also this is what happens, when I try to use Odin3 v1.85
Code:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830MWHLK2_S5830MICELK1_S5830MWHLK1_HOME.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..
And it just hangs in there forever!
Thanks!
Mike02x said:
Thanks!
Will try in another device!
Also this is what happens, when I try to use Odin3 v1.85
Code:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830MWHLK2_S5830MICELK1_S5830MWHLK1_HOME.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..
And it just hangs in there forever!
Thanks!
Click to expand...
Click to collapse
... Is your phone model GT-S5830? or GT-S5830M?? Beacuse I think you are flashing an incorrect firmware or .ops file or whatever related with your device model so check out carefully
Viper The Ripper said:
... Is your phone model GT-S5830? or GT-S5830M?? Beacuse I think you are flashing an incorrect firmware or .ops file or whatever related with your device model so check out carefully
Click to expand...
Click to collapse
GTS5830
Mike02x said:
GTS5830
Click to expand...
Click to collapse
So that's what I was saying you, this firmware (S5830MWHLK2_S5830MICELK1_ICE.zip) is a GT-S5830M firmware!! Please go to sammobile and download a correct firmware!!
Mike02x said:
Thanks!
Will try in another device!
Also this is what happens, when I try to use Odin3 v1.85
Code:
<ID:0/010> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> S5830MWHLK2_S5830MICELK1_S5830MWHLK1_HOME.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..
And it just hangs in there forever!
Thanks!
Click to expand...
Click to collapse
here s detailed instruction with files http://yagyagaire.blogspot.in/2012/03/upgrading-galaxy-ace-to-s5830ddkq8.html#.Ub00ClyVhw0
manoj94 said:
here s detailed instruction with files http://yagyagaire.blogspot.in/2012/03/upgrading-galaxy-ace-to-s5830ddkq8.html#.Ub00ClyVhw0
Click to expand...
Click to collapse
Well, I think we've a great tutorial HERE so...
Good day all, and I apologize for having my first post require help, but ive been playing with this thing for hours and hours to no prevail.
This is where i stand:
Rooted my phone using this guide: http://forum.xda-developers.com/showthread.php?p=43182804
Was on the train playing with game killer then chainfire: https://play.google.com/store/apps/details?id=eu.chainfire.cf3d&hl=en
The phone shut off and on reboot it was stuck on the AT&T logo.
Did some reading and tried to do recovery, wipe data and cache and that didnt work.
Accessed download mode for the first time today and now i cant go into recovery mode any longer.
Can no longer get to the AT&T logo, just "GALAXY S4 ACTIVE" then it shuts off.
Downloaded Odin and tried to use this as firmware:http://www.androidfilehost.com/?fid=23011596498370871
fail:
<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/004> Odin v.3 engine (ID:4)..
<ID:0/004> One Click Downloader Mode
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
Not sure where to go here, phone may still be rooted but im not sure due to reset.
Any help would be amazing at this point.
vq35s14 said:
Good day all, and I apologize for having my first post require help, but ive been playing with this thing for hours and hours to no prevail.
This is where i stand:
Rooted my phone using this guide: http://forum.xda-developers.com/showthread.php?p=43182804
Was on the train playing with game killer then chainfire: https://play.google.com/store/apps/details?id=eu.chainfire.cf3d&hl=en
The phone shut off and on reboot it was stuck on the AT&T logo.
Did some reading and tried to do recovery, wipe data and cache and that didnt work.
Accessed download mode for the first time today and now i cant go into recovery mode any longer.
Can no longer get to the AT&T logo, just "GALAXY S4 ACTIVE" then it shuts off.
Downloaded Odin and tried to use this as firmware:http://www.androidfilehost.com/?fid=23011596498370871
fail:
<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/004> Odin v.3 engine (ID:4)..
<ID:0/004> One Click Downloader Mode
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004>
<OSM> All threads completed. (succeed 0 / failed 1)
Not sure where to go here, phone may still be rooted but im not sure due to reset.
Any help would be amazing at this point.
Click to expand...
Click to collapse
Try a different USB port, different cable, and drivers. If none of that works try a different computer
If download mode works you should be able to get it back
I've gotten to the point, after letting it charge for awhile, where i can now get back into recovery mode and i can get to the AT&T logo.
Any Idea of what i should do next?
vq35s14 said:
I've gotten to the point, after letting it charge for awhile, where i can now get back into recovery mode and i can get to the AT&T logo.
Any Idea of what i should do next?
Click to expand...
Click to collapse
Flash Odin....
You can try a factory reset but I recommend Odin. Follow what I said before
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
Chainfire 3d is not compatible with jb
Read carefully the link u provided
Is compatible with froyo and gingerbread only
joshuadjohnson22 said:
Flash Odin....
You can try a factory reset but I recommend Odin. Follow what I said before
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
Click to expand...
Click to collapse
+1. Make sure you have the proper USB drivers installed. An Odin flash is your best bet.
Sent from my SAMSUNG-SGH-I537 using Tapatalk 4
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
The phone shows " Firmware upgrade issue encountered an issue. Please select recovery mode in Kies & try again". I cant go to recovery mode ie. vol up+home+power. THings I have tried:
1. with Kies the device isnt recognised. I have updated the driver as well.
2. with odin every thing fails... flashing "all samsung recovery.tar", flashing stock jelly bean, flashing .pit file
I have googled for days and tried many things but isnt working. Need help
Where and why the stock firmware flashing is going wrong?
nokiamodeln91 said:
Where and why the stock firmware flashing is going wrong?
Click to expand...
Click to collapse
Hello,
Now the odin is not even recognising the device, Before it couldnt perforn the NAND write.
Start fresh... Remove battery and let the phone rest for couple of minutes.. Then try again.. Just go ahead and flash a stock rom. And check where it fails.
nokiamodeln91 said:
Start fresh... Remove battery and let the phone rest for couple of minutes.. Then try again.. Just go ahead and flash a stock rom. And check where it fails.
Click to expand...
Click to collapse
I had done what you've suggested. It dint work. The message in the odin3 v3.04 when trying to flash stock jellybean was
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N7000XXLSZ_N7000OXALSZ_906407_REV02_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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
loveandroider said:
I had done what you've suggested. It dint work. The message in the odin3 v3.04 when trying to flash stock jellybean was
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_N7000XXLSZ_N7000OXALSZ_906407_REV02_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> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Where did you download this file from? SAMmobile?
Try redownloading the file, it may be corrupted during download.
AutumQueen92 said:
Where did you download this file from? SAMmobile?
Try redownloading the file, it may be corrupted during download.
Click to expand...
Click to collapse
Hello. I can say that the file isnt corrupt because I have flash that ROM a numerous time before. But until the last time when I was flashing custom rom night owl lollypop version, it stuck in boot loop and then when I tried to flash that , it dint work. Now I cant even go to recovery mode.
loveandroider said:
Hello. I can say that the file isnt corrupt because I have flash that ROM a numerous time before. But until the last time when I was flashing custom rom night owl lollypop version, it stuck in boot loop and then when I tried to flash that , it dint work. Now I cant even go to recovery mode.
Click to expand...
Click to collapse
As the log say "<ID:0/003> SetupConnection.." and not move ahead.. there is some connection problem with Phone and PC... Could be a driver problem.. or Kies might be running in the background...
There is no writing of data what so ever.
I tried in another laptop and it worked. My mobile was dead for weeks and its back to life. But I had samsung driver. I dint have Kies installed. dont know was the problem in connection. Anyways thanks to nokiamodeln91 and AutumQueen92 :good: