PIT file needed for GT-N5120 16GB - Galaxy Note 8.0 (Tablet) Q&A, Help & Troubleshooti

Hi there,
I'm trying to flash a stock UK firmware (N5120XXDOD1_N5120BTUDOD1_N5120XXDNH3_HOME.tar.md5) for my GT-N5120 LTE 16GB with Odin, but I'm having problems getting it to work. Odin Log reports two different problems:
[1]
<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 engine v(ID:3.1205)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
[2]
<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 engine v(ID:3.1205)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I've spent hours trawling the net for a suitable Pit file, but I can't find one. I understand that you can make your own using something like Pit Magic, but I don't know what I'm doing with it.
A little background on the problem with my Note 8. Yesterday the tablet was plugged into the charger and switched on but wasn't in use. I noticed it reboot for no reason but then it wouldn't load any further than the logo / model number screen. I rebooted it, pulled the battery and tried just about everything else to get it to work. Finally I resorted to trying to restore the firmware via Kies. The process started but failed. Now I have no firmware and I can only get as far as the Download screen.
Additionally, the screen flickers constantly and sometimes only has flickering black and white lines. I suspect that something more serious is wrong with it, but I'd still like to see if I can fix it before I trash it.
Could anyone point me to a suitable Pit file or could extract one from their GT-N5120?
Appreciate any help, thanks.

BUMP
Still looking for a PIT file for my GT-N5120 16GB. I must have PIT files for nearly every Samsung model to date, all except a 16GB version for this device.. I've got an 8GB version that won't flash. I've probably got every version of Odin released in the wild.
I've got Samsung Full Firmware Maker, PIT Magic, PIT Viewer, various recoveries and stock firmwares.. most of which are a bit over my head at this time. All I need is one little file.
I can still boot into Download Mode, I've made a 300k ohm USB jig so I can boot into Factory Mode, but I still can't flash firmware as repartition fails on every PIT I've tried. The only thing I haven't tried is a 16GB PIT file, and if that fails, I'm left with a few other unbrick options before I concede to the fact that it's dead and has a NAND failure.
Anyone willing and able to extract a 16GB PIT file from their GT-N5120 16GB?
Cheers, Chris.

I have a N5110 16gb, so I likely cannot help. But how would one extract a PIT file, because that might be useful to have, because I was afraid I'd mess mine up flashing ROMs for N5100, but it seemed to be fine, I was able to odin 5110 stock without issue.

Related

[Q] Bricked GT-N7100, is the my problem hardware or software?

Good day, guys! Sorry if my first post is related to a problem. I'm pretty new to Android so please bear with me...
So I woke up this morning and my Note 2 won't completely boot, it goes as far as "Samsung Galaxy Note II GT-N7100" screen and just completely gets stuck. I tried to charge it but it just shows the empty battery icon. I left it charging overnight so I don't exactly know what happened. My phone is completely stock, rooted it before then un-rooted later. No custom ROM, no custom recovery etc.
I tried to boot to Recovery Mode but it won't let me. Luckily it can boot to Download Mode. I figured I would flash it to stock ROM since I was still at 4.1.1 maybe I would just update to 4.1.2. I downloaded the firmware from sammobile.com and used Odin but it fails every time with this message:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_N7100XXDLJ2_422394_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/015> Odin v.3 engine (ID:15)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Get PIT for mapping..
<ID:0/015>
<ID:0/015> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/015> Removed!!
Can someone point out the problem to me? I've read around that this is probably SDS but I'm still hoping that it's not. I bought my phone from another country so taking it back would be a little difficult.
Any help appreciated. Thank you!

[Q] Stuck in boot loop, nothing I try works. Is my phone a lost cause?

Model: SGH-T999V (Wind Mobile)
Firmware Rom: Cyanogenmod 10.1.3 (IIRC, might have been 10.1.2)
So, last night I plugged my phone in to my computer to charge. I walked away to do some other things, and when I came back a few minutes later I found it rebooting, or at least trying to. It seemed to be stuck in a loop. It would vibrate and show the Samsung logo, and then show the model logo (in my case "Samsung Galaxy SIII" with the cyanogenmod logo on the bottom half of the screen). After this, it would vibrate twice with around a two second delay between each vibration. Then it would show the Samsung logo, the model logo, and vibrate twice again, repeating indefinitely. The only thing that stops the loop is pulling the battery.
At this point I'm thinking that there's a problem with the battery. I kept it plugged in to my computer for a little while while it tried to boot, hoping that it just needed to be charged. After this didn't work, I tried charging it with a portable battery pack I had and used a different cable. Still nothing. Then, I found a spare battery that I had and replaced the one I had been using. That didn't work either, the phone continued doing the same boot loop.
I don't believe that the problem is a faulty power button, since it doesn't start trying to boot until I either plug it in to charge or I press the power button myself. I can't seem to enter recovery mode. Whenever I try, it shows the initial Samsung logo screen with "Recovery Booting...." in small blue text in the top left corner of the screen, but then proceeds to reboot again.
I am, however, able to enter download mode. I decided to try and flash my stock firmware, hoping that would fix the problem. I put my phone in download mode, opened odin, and it seemed to recognize my phone. I loaded the .md5 file and hit start, but almost immediately it showed 'FAIL'. This is what it said in the message box:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_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..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
At this point I have no idea what else I can do. I hope it's not a hardware failure, but it's starting to look like that's the case. Is there anything else I can try, or is my phone just dead? And, if it is dead, does anyone know the exact cause?
CM is your rom, not your firmware. The firmware is what we generally refer to as everything but system, kernel and recovery. Do you know what your current firmware build is?
Are you certain you downloaded the Wind version of the firmware?
I could be wrong but from the Odin output it looks like you have pre 4.3 firmware. If so, try using any other build and see if it flashes.
Judging from the symptoms you described, it is possible you could be looking at a hardware failure. Possibly the SoC, but more likely the memory. If you cant get Odin to flash anything the possibility of this becomes greater.
Try other firmware with Odin. Try with and without re-partition checked. (This will wipe all your data)
Try flashing TWRP via Odin. If that makes recovery work you may then be able to factory reset and flash a rom again.
Try different usb cables and ports. Try another computer as well if nothing else is helping.
Beyond all of that, im not sure theres gonna be much you can do.
Argh, I always seem to get ROM and firmware mixed up. Anyway, If I'm understanding this correctly I'm pretty sure that my firmware was 4.2.2. I definitely downloaded the wind version of my stock firmware. I also found on my computer 4.0 firmware that I'd downloaded a couple years ago. I tried flashing that with odin and got the same result. Then I tried it with re-partition checked and it failed again with this:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_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..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Can't open the specified file. (Line: 1949)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I guess that's that then. Luckily I had backed up all my photos last week on a whim.
Out of curiosity, did you use a PIT file when repartitioning, or did it use the one in the device? Whichever it is, try the other as well. I believe the pit files are in the General section.
I used the PIT file on my device when I first tried to repartition. I downloaded the PIT file that you were talking about and tried again:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNF1_T999VYVLFNF1_T999VVLUFNF1_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..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Write)
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Did you try flashing recovery only? And does odin see the devices COM port in the top left?
Did you try different ports and cables?
Odin does see the COM port. I just tried flashing TWRP and odin said that it passed, but I'm still not able to boot into recovery mode. I have tried using another port but I don't have another cable on me.
Well if it said it passed the recovery flash, the cable and port are probably ok.
Im not really sure there is much else you can do tbh. Its sounding more like a hardware problem at this point.
Sorry I dont have anything better to tell you, but if I think of anything else you could try ill let you know.

Samsung Galaxy S4 Mini GT-I9195

So, my friend updated their S4 Mini GT-I9195 to Android version 4.4.2 Kitkat. The phone shut down twice after the update and is no longer able to boot up. So they gave me it to see what I can do. I've tried going to Odin mode, Recovery. But none of it works. I've also tried using QPST, but I'm unable to find .hex or .mbn file for it. So I tried the one for the required MSM8930 chipset. Sadly, the QPST cannot connect to my phone. Is there anything else I could do to revive it without having to JTAG it or something? Please help.
EDIT: I've managed to run it in Odin mode by using debrick.img flash into SD Card, however.. after trying to flash recovery. Odin returns:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/010> Odin engine v(ID:3.1100)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010>
<ID:0/010> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Any ideas?

S4 mini gt-i9192 stuck at donwload mode

Hi there,
I have run into this problem with my cellphone (S4 Mini gt-i9192). After it discharged, i connected it on the charger. My device failed to boot and got stuck at download mode ("Could not do normal boot" and mmc read fail). I've tried some procedures i found on the internet:
- flashing some original ROMs with and without PIT file
- hard reset
- wipe cache data
- boot thorugh recovery
The results vary, but I never got it a pass on Odin. Without a PIT file Odin displays "There is no PIT partition" and with PIT file, is displays:
<ID:0/005> 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/005> Odin engine v(ID:3.1101)..
<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> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Auto reboot and F. Reset Time are enabled with or without PIT file and Re-partition is only enabled with a PIT file. So, nothing out of usual for this part.
I also remark that I have never rooted it. I realize I should keep downloading stock ROMs and hope for a flash that works because there might a problem with my mmc, but maybe someone knows another procedure to recommend me. I appreciate all feedback and thank for it in advance. ALso, tell me if I didn't provide any info that could help solve this problem.

Can't flash stock firmware after Lineage 14.1

This morning I flashed Lineage 14.1 and there were no errors. But it got stuck at the Samsung logo during reboot. I waited about 15 minutes. I could not figure out how to fix it so I decided to flash the stock firmware using Odin. It passed but also got stuck at the same screen during reboot. Then I did a hard system recovery but still could not boot past the Samsung logo. After that I install Samsung Kies 3, but it said the phone is no longer supported. Then I tried Kies 2.6 but it said the phone SGH-M919 does not support initialization. Now I can't get to the system recovery screen anymore. It would say there is an issue with the firmware update and try again in Kies. I cannot flash the stock firmware in Odin anymore either. It would fail with a complete write error. I don't know what else to try. Please help me.
Did you confirm the phone's model # in download mode?
You tried different USB cables, different USB ports, and different versions of Odin?
What was the exact Odin error?
Yes, the model is correct SGH-M919. I've tried Odin 3.0.7 and 3.10.6. I used Odin 3.0.7 to root and install TWRP recovery using the same original Samsung USB cable. So the cable and port should be OK. I tried it again this morning and noticed it took a long time after the message "Get PIT for mapping.."
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_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..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried it again using a different USB port and this time it failed right away. I didn't see the line "Get PIT for mapping" this time. Here are the messages in Odin.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUFOK3_M919TMBFOK3_M919UVUFOK3_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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I was using the USB ports at the front of the PC and none of them worked. I tried one port at the back and it worked. Thank you very much. I never thought this would make a difference because I use the ports in the front all the time with my other iPhones, iPads, USB memory sticks and never had a problem. I lost all my data on the phone but that's OK. I would not dare to install custom ROM again. It looked so easy in youtube videos. Thanks again.
Glad you got it working. I always use the ports at the back of my desktop because I find it more reliable than the front case ports.

Categories

Resources