TLDR: Odin says it flashes recovery successfully, it doesn't seem to be working.
Note 4 was damaged and brought out the S3 for a temp backup phone. I activated it, made some test calls everything worked great. Came back a couple hours later to the phone in download mode with a red error stating it could not normal boot. I attempted to go into recovery, pulled up TWRP 2.6.0.0 with a password prompt but I've never set one. I googled the TWRP issue and there was a problem with Sprint GS3 and TWRP, I loaded up Odin 3.0.9 and attempted to flash a newer version of TWRP as my searching had recommended, Odin flashed, said PASS! and I rebooted but it was still on 2.6.0.0 requesting a password. I pulled up ODIN again, tried CWM/Philz/Stock - same issue still TWRP 2.6.0.0 even though ODIN stated it successfully flashed. Tried a different computer, a different USB cable, same issue. ODIN states that it is successfully flashing but it doesn't seem to take. Then I tried flash stock ROM, got an error in ODIN this time, stating it couldn't write, googled that was told to get a pit file, that can't be written either.
I can't seem to find many people in my situation, was hoping I could get some input before I started buying hardware to try to fix it (JTAG and micro SD/linux solutions).
Odin the full stock ROM then Odin recovery again.
{
"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"
}
bilgerryan said:
Odin the full stock ROM then Odin recovery again.
Click to expand...
Click to collapse
Tried, gives me a PIT error.
toddf2p said:
Tried, gives me a PIT error.
Click to expand...
Click to collapse
What error specifically?
bilgerryan said:
What error specifically?
Click to expand...
Click to collapse
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_L710VPUCMK3_L710SPRCMK3_2034598_REV03_user_low_ship.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..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008>
<ID:0/008> There is no PIT partition.
<ID:0/008> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
toddf2p said:
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_L710VPUCMK3_L710SPRCMK3_2034598_REV03_user_low_ship.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..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008>
<ID:0/008> There is no PIT partition.
<ID:0/008> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You'll have to repartition PIT. I don't have any other information, I know someone with the 32GB model successfully repartitioned his PIT.
Related
I have a Sprint Samsung Galaxy S2 SPH-D710. The phone was running the stock ICS firmware. Yesterday the phone randomly crashed. After crashing I tried rebooting the phone multiple times but it would always hang at the Samsung logo.
I then tried doing a factory reset (Volume-up + power buttons). This at first seemed to work but after restoring and booting all the way up the phone hung again.
Now the phone always hangs at the Samsung logo and I can only enter the odin mode (volumn-down + power buttons).
I have tried restoring the phone using multiple different one-click odin re-flashers. But, although they always completed without errors, when the phone reboots, it still just hangs at he Samsung logo.
Ideas please. Thanks!
Hmm you may have the wrong odin stock files man or maybe hardware failure somewhere?
Sent from my SCH-R760 using XDA Premium 4 mobile app
How can I tell if I have a hardware failure?
I downloaded my odin files from here: rwilco12 . com/downloads.php?dir=Files/Devices/Samsung%20Galaxy%20S2%20%28Sprint%29%20%28SPH-D710%29/Stock%20ROMs
This is a strange thing to happen on stock. I don't believe that its hardware related, if your device bricked for hardware reasons it wouldn't allow you into recovery and try to boot. This sounds more like a corrupted system file. Make sure that your drivers are installed correctly and retry your choice of one clicks. If that doesn't work, I would try using the latest GB27 release, found here. This will wipe out everything on your device, pictures, music, etc..., this kinda sucks, especially if you can't boot to back it up.
Edit - Sorry my two year old hit the mouse before I finished typing.
To continue my post: The above linked one click will reformat your device and install the necessary partitions, essentially giving you a brand new internal drive to work with.
So loaded the GB27 release as you suggested. No joy. The phone still just hangs at the Samsung logo.The odin output is as follows:
<ID:0/004> 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/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> cache.img
<ID:0/004> data.img
<ID:0/004> factoryfs.img
<ID:0/004> modem.bin
<ID:0/004> hidden.img
<ID:0/004> param.lfs
<ID:0/004> recovery.bin
<ID:0/004> Sbl.bin
<ID:0/004> zImage
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Can I assume that since this succeeded that there are no driver issues?
Any other things to try?
Thanks for your help!
Kevlar1234 said:
So loaded the GB27 release as you suggested. No joy. The phone still just hangs at the Samsung logo.The odin output is as follows:
<ID:0/004> 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/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> cache.img
<ID:0/004> data.img
<ID:0/004> factoryfs.img
<ID:0/004> modem.bin
<ID:0/004> hidden.img
<ID:0/004> param.lfs
<ID:0/004> recovery.bin
<ID:0/004> Sbl.bin
<ID:0/004> zImage
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
Can I assume that since this succeeded that there are no driver issues?
Any other things to try?
Thanks for your help!
Click to expand...
Click to collapse
I'm honestly at a loss, never heard of this happening. Not to beat a dead horse, but your sure you have the D710?
Slithering from the nether regions of a twisted mind and tarnished soul
Try this: http://forum.xda-developers.com/showpost.php?p=41320560&postcount=17
Can't guarantee that it'll work but, doesn't hurt to try.
Not sure if this applies to the d710 but I had an evo shift that did that until I removed its sd card. So if you have an sd card in it, take it out and try.
Sent from my SPH-D710 using xda app-developers app
I never had that happen to my Shift lol... But could be worth a shot
{
"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 don't have a SD installed so that can't be it. I'll try out Dypraxxx suggestion this evening and report back.
Thanks for you responses!
Ok, I finally got around to trying Dypraxxx suggestion. No joy.
What is going on?!?
I am having issues using odin to flash anything. I have tried using Samsung drivers old and new and could not successfully flash md5 file using odin. I have previously been successful when 4.3 came out. and im trying to install 4.4.
It has phils touch recovery and mk3 rooted 4.3.
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.6-jfltexx.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> Get PIT for mapping..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
dromango said:
I am having issues using odin to flash anything. I have tried using Samsung drivers old and new and could not successfully flash md5 file using odin. I have previously been successful when 4.3 came out. and im trying to install 4.4.
It has phils touch recovery and mk3 rooted 4.3.
Added!!
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
philz_touch_6.07.6-jfltexx.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:6)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Have you tried different cables and ports on your PC? Those are usually the things that cause problems with 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"
}
I'll try that
windows looking for two drivers
samsung mobile cdc composite device
samsung mobile usb modem
both ready to use.
EDIT: I'll be damned. I was able to flash recovery file after using a different port. I have did this method before. strange.
Dear Guys,
My little brother's N7100 stuck at Galaxy Note II logo, and this is what I've tried to fix it:
Wipe Cache Partition [FAILED]
Wipe Data/Factory Reset [FAILED]
Flashing Recovery by Odin 3.7/3.9 [FAILED]
Flashing Official JB 4.3 ROM by Odin 3.7/3.9 [FAILED]
**** UPDATE ****
Restore Original Stock Partition Table + NAND Erase by Odin 1.85/3.7/3.9 using PIT file [FAILED]
Flashing Bootloader 4.3/4.4 by Odin 3.9 [FAILED]
{
"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"
}
Code:
[B]This is Odin's log when flashing Philz Recovery:[/B]
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.26.6-n7100.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> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
This happens just 1 week after repaired at Samsung Service Center (having failed KitKat upgrade via OTA - Bootloop) and they said must replace the main board. Sadly, the warranty period has run out :crying:
Just want to ask here, is that true it only can be fixed by replace the main board with a new one? Or there's another way to fix it? And why this can happen? I'm afraid, after replace the main board these events recur.
Note: The last ROM is official JB 4.3 without root and don't have any backup (EFS, NAND, etc).
Sadly it's true. But I think it must be the emmc fault. Which year is this phone manufactured?
Sent from my GT-N7100
Sorry for belated reply and thank you. Maybe tomorrow I'll going to replace the main board.
djie said:
Sorry for belated reply and thank you. Maybe tomorrow I'll going to replace the main board.
Click to expand...
Click to collapse
Hello
Did u try flashing a .pit file through ODIN? I recommend you try that before changing the motherboard. If that doesn't work then you have no choice but to spend the money to change the board (or get a new phone!)
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
djie said:
Sorry for belated reply and thank you. Maybe tomorrow I'll going to replace the main board.
Click to expand...
Click to collapse
The guys from the service center surely don't bother to check what is the problem. They just see "ah ok it's not reading anything, change the whole mobo just in case and user will pay us more and it will be easier to do".
These days is hard to find a good tech guy.
Sent from my GT-N7100
Irwenzhao said:
Hello
Did u try flashing a .pit file through ODIN? I recommend you try that before changing the motherboard. If that doesn't work then you have no choice but to spend the money to change the board (or get a new phone!)
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Click to expand...
Click to collapse
Can you give me the guide how to do that? At least the link so I can follow the instructions and get the preparation - the files
I found this guide for SIII: http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367 and this one: http://forum.xda-developers.com/showthread.php?p=33074572#post33074572
djie said:
Can you give me the guide how to do that? At least the link so I can follow the instructions and get the preparation - the files
I found this guide for SIII: http://forum.xda-developers.com/galaxy-s3/help/solved-pit-bricked-dead-problem-gt-t2535367 and this one: http://forum.xda-developers.com/showthread.php?p=33074572#post33074572
Click to expand...
Click to collapse
This should work.
How to restore original stock partition table.
You will need to do this if you want to install stock official firmware.
1 - Download Odin3_v3.07_with_PIT_16GB_GT-N7100.zip and extract it somewhere.
2 - Download any stock ROM from sammobile.com or samsung-updates.com and unzip it.
2 - Open Odin, click "PIT" button and select " PIT_N7100_16GB_20121102.pit"
3 - Click "PDA" and select official ROM that you've downloaded
4 - Click "Start"
5 - After installation, phone will be stuck at bootanimation, don't panic.
6 - Pull out battery, boot to recovery (you can see some mount errors, don't worry)
7 - Select "wipe data/factory reset" in recovery menu
8 - Select "reboot system now"
I'll put the links up in a while.
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Hi Irwenzhao,
Thank's for your guide, I already follow it and use an official 4.3 ROM from Sammobile. And here's the logs:
Code:
[b]From ODIN v3.07[/b]
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUEML3_N7100OLBEML1_N7100XXUEMK1_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> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
[b]It was stuck at Get PIT for mapping..[/b]
[b]From ODIN v3.09[/b]
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUEML3_N7100OLBEML1_N7100XXUEMK1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyway, thanks for your help
djie said:
Hi Irwenzhao,
Thank's for your guide, I already follow it and use an official 4.3 ROM from Sammobile. And here's the logs:
Code:
[b]From ODIN v3.07[/b]
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUEML3_N7100OLBEML1_N7100XXUEMK1_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> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
[b]It was stuck at Get PIT for mapping..[/b]
[b]From ODIN v3.09[/b]
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUEML3_N7100OLBEML1_N7100XXUEMK1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Anyway, thanks for your help
Click to expand...
Click to collapse
0.o try a different cable/port/computer and different versions of ODIN. (Try 1.x versions)
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Irwenzhao said:
0.o try a different cable/port/computer and different versions of ODIN. (Try 1.x versions)
N7105 rocking AOSB with AGNi kernel,
Click "Thanks" if I was of any help!
Click to expand...
Click to collapse
I'm sure that I have no problems with my PC nor the cables But I'm not sure if older Odin will works or support N7100, but I'll try it later.
EDITED:
-------------
Code:
[b]From ODIN v1.85[/b]
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUEML3_N7100OLBEML1_N7100XXUEMK1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Google note2 emmc replace you will see where should be your problem.
Sent from my GT-N7100
Doesn't work. My phone reboots after I select Factory Reset.
Ren Hayashi said:
Doesn't work. My phone reboots after I select Factory Reset.
Click to expand...
Click to collapse
You have same problem with me? Or what? Instead of choosing factory reset via recovery mode, maybe you can try to flashing official ROM that same as your ROM version via Odin.
guys increased the memory of my grand duos looking first tutorial here forum, and happened all right, that now being tried back Stock ROM and when you start the error. and back to the original patition colleagues?
Lucas0Neto said:
guys increased the memory of my grand duos looking first tutorial here forum, and happened all right, that now being tried back Stock ROM and when you start the error. and back to the original patition colleagues?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=55294512&postcount=6
you can't go back to stock unless you reset the partition table
try the link above
to do this tutorial get this error
Yousef Mohamed said:
http://forum.xda-developers.com/showpost.php?p=55294512&postcount=6
you can't go back to stock unless you reset the partition table
try the link above
Click to expand...
Click to collapse
I did the procedure as stated in the tutorial and still continued receiving the error
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9082XXUBMK3_I9082ODDBMJ1_I9082DDUBMK1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<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"
}
Lucas0Neto said:
I did the procedure as stated in the tutorial and still continued receiving the error
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9082XXUBMK3_I9082ODDBMJ1_I9082DDUBMK1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
May be the Baffin.pit file is corrupted , Re-download it and try again
pass me your baffin.pit file
redid the process 2 times with the downloaded file 2 times and still the error could have your baffin.pit file
Did you try to flash the Stock without The pit file then flash the bit file alone and after that flash the stock alone
1. flash the stock
2. Flash the pit
3. Flash the stock again
I know it seems silly but try it
theory or skype whatsapp, could leave here
Yousef Mohamed said:
Did you try to flash the Stock without The pit file then flash the bit file alone and after that flash the stock alone
1. flash the stock
2. Flash the pit
3. Flash the stock again
I know it seems silly but try it
Click to expand...
Click to collapse
I keep getting the same error
That's what happens when I try to go up the system after flashing the rom 2 TIMES
A few weeks ago, my phone was stuck on Samsung Logo. Having read through several threads on the subject, I attempted flashing though Odin but despite following all instructions, my phone is now stuck on a screen that says: "Firmware upgrade encountered an issue. Please select recory mode in Kies & try again." (pic attached).
{
"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"
}
When I press volume up & power & home, I do get to "Downloading ... Do not turn off target" but can't seem to progress beyond this.
I must say, I have only ever attempted one flash before a few years ago and I am not the brightest spark when it comes to understanding what I'm doing even though I am good at following instructions but any help with this would be greatly appreciated and welcomed.
Thanks
Tried Odin again - message I get is:
<ID:0/003> Added!!
<ID:0/003> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SC02EOMALJF_SC02EDCMALJF_SC02EOMALJF_HOME_REV04_user_low_true.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> 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)
<OSM> All threads completed. (succeed 0 / failed 0)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXUFNG4_N7100OLBFNG1_N7100DXUFND2_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> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Are you using the original Samsung USB cable? Have you tried different USB cables, USB ports, ROMs, and operating systems?