ive been trying to fix this issue on my own for the past 5 hours but just cant so i'm going to try to get help from you lovely people at XDA.
so i tried to unlock my bootloader using CASUAL and it soft bricked my phone failing half way through. now when i try to boot into the OS, it says theres been a fireware problem, reset using kies.
so kies is not compatible with verizon note 2's, awesome, i know.
so i try to use ODIN to flash a stock rom in download mode. and ODIN will not recognize my phone in download mode. ive tried every driver package under the sea and nothing seems to work. and on top of that, when ODIN used to work, it kept failing at boot.bin files and would fail.
so i cant get ODIN to recognize my phone any more, but my computer does, and the files i try to download all fail at the boot.bin file.
any help would be great, i know i can get this phone fixed its just very frustrating at the moment.
for those wondering, i fixed this issue by using another windows computer to find my phone via odin,
then just flashed the PIT file, nothing in the PDA section.
phew. trial and error.
where did you get PIT file?
bryannh said:
for those wondering, i fixed this issue by using another windows computer to find my phone via odin,
then just flashed the PIT file, nothing in the PDA section.
phew. trial and error.
Click to expand...
Click to collapse
Where did you get the PIT file??
Related
Hi, I started out with a stock tmobile s3 and tried to root it for the first time today, I followed this video
http://www.youtube.com/watch?v=mndQZqom3Ac
which asked me to use this cf-root 6.4
http://forum.xda-developers.com/showthread.php?t=1695238
when I hit start on that .tar file under odin, it failed stating "complete (write)operation failed)
since then, my device would boot with error "firmware upgrade encountered an issue" nothing else would happen.
I tried to go into recovery mode again and this time when I tried to retry the odin tar install, it would give me a new fail of cannot open com3
When I tried to use kies, it would just forever try to connect and never connect. so I couldnt do anything there.
What can I do? I would preferably try to retain all my saved data.
I also suspect my usb port might be faulty, sometimes need to press it in firmly to make the usb mass storage to work properly.
Thanks in advance
What is your Current android version ?
Perseus71 said:
What is your Current android version ?
Click to expand...
Click to collapse
i really didnt note which version i have... noob mistake i kmow. i think it is 4.2...is there any way i can check?
Ok, I totally messed up when I first attempted this. The .tar I used was for an international s3 and I have a tmobile us version!. the OP of the thread says it may even brick my phone if I attempt this on a non international version.
competely my fault, but what should I do to fix this and save my phone?
I cannot connect to kies, reinstalled the drivers and it still wont connect. just gets stuck in "connecting"
The odin now doesnt load a tar because it says "cannot open com3 "
EDIT:
fixed it, odin was not working due to kies running in the background and I finally was able to flash the correct chainfire for my phone
Glad its sorted out. I assume no issues now ?
My phone was working fine today until I took it out of my pocket and it was stuck at the Tmobile Note 2 screen. I tried multiple times to restart it and no go. Tried to go into my TWRP recovery and it appears there is no recovery.
I tried Odin tonight with the rooted stock file on here and keep getting no pit mapping. I tried with a pit file I found and it just gets stuck. From what I'm reading through google, it appears to maybe be a hardware problem. Does anyone have anything I can try? Phone was running Octos Rom with no problem for months.
robl45 said:
My phone was working fine today until I took it out of my pocket and it was stuck at the Tmobile Note 2 screen. I tried multiple times to restart it and no go. Tried to go into my TWRP recovery and it appears there is no recovery.
I tried Odin tonight with the rooted stock file on here and keep getting no pit mapping. I tried with a pit file I found and it just gets stuck. From what I'm reading through google, it appears to maybe be a hardware problem. Does anyone have anything I can try? Phone was running Octos Rom with no problem for months.
Click to expand...
Click to collapse
See if you can Odin just a recovery image and then try to boot to recovery. I think I have a few different recovery .tar files for T889 if you can't find online. You may also want to try a different cable if you continue to get errors connecting.
EdKeys said:
See if you can Odin just a recovery image and then try to boot to recovery. I think I have a few different recovery .tar files for T889 if you can't find online. You may also want to try a different cable if you continue to get errors connecting.
Click to expand...
Click to collapse
I actually did try that, tried stock recovery and TWRP, both say no pit for mapping. using the tar from sammobile I did get it to start downloading one time, it went for like 45 minutes and then finally said failed at probably 3/4 along based on the bar graph that was showing on the phone. That worked after I switched USB ports on the computer although I think that was just a fluke as I tried again after it failed and kept getting the same message of no pit for mapping.
robl45 said:
I actually did try that, tried stock recovery and TWRP, both say no pit for mapping. using the tar from sammobile I did get it to start downloading one time, it went for like 45 minutes and then finally said failed at probably 3/4 along based on the bar graph that was showing on the phone. That worked after I switched USB ports on the computer although I think that was just a fluke as I tried again after it failed and kept getting the same message of no pit for mapping.
Click to expand...
Click to collapse
How old is your battery? This may sound crazy, but I thought my phone was toast several months ago but when I changed to a backup battery that I had all was fine. Also, try restarting your computer after you change USB ports. It may help to get Odin working properly. I have a copy of a CWM recovery that's worked for me to get me out of some similar issues. You can download it from my Dropbox here:
https://www.dropbox.com/s/qx45bapmroh8k0b/Note2-CWM-6.0.4.3-SGH-T889.tar?dl=0
Hope that works. Good luck!
Hi everyone. This is the first time ive posted anything on here. I will try to fully describe my problem that i really need help to fix.
My wife got my old Note 2 is rooted and she got my
Dad's old unrooted Note 2. After deciding that she didnt want a rooted phone she decided to use my father's unrooted phone. Due to apps updating and the internal memory getting full she ingored the warning message not really realising the outcome. The phone eventually shut itself down and is stuck on the Samsung logo (boot loop). So i gave her my old rooted phone back because she said that it just died. The same happened to the rooted phone too.
I asked before what she did and i was told nothing it just died. So i had nothing to go on. It wasn't until a week later when I tried to sort the problem out she said the System Memory was getting full and a message came up warning of this. So now I believe the problem is that the on board memory has got full and the phone seized. Much like what happens to a PC when the main hard drive gets full!
When i attempt to boot the phone up the Samsung logo show and stays on, never booting up. This happens with both phones. When i hold the Home key, Power button and Up volume switch. The phone loads the first Part of the boot up and at the moment it goes to the system screen it goes blank for a split second and back to the start of the boot. No matter how many times i try it fails. So I can't Factory reset or erase anything because i can get to it that screen.
So I try something else. I press the Home button, Power button and the Down on the volume to access the Download mode. This works fine. So i used Odin to try to put Rom onto the phone hoping this will solve the problem. Both phones connects to Odin alright and I can set up ready to load a rom onto it, however when i press start on Odmin to do its job everthing starts ok but then it goes red with a Failed error message. This happens when i try this on both phones, I seem to be stuck no knowing what to do. I have tried using all the ports on my laptop (window 7) and that makes no difference. The same happens on both devices.
I think i need to clear the memory somehow but have no idea how to do it when i can only access Download mode. I would be very grateful for any help on this but if all else fail I will try to build up static on a ballon and see if putting the near will wipe the memory, lol. Only joking. Im desperate to sort this out.
Any ideas?
Try to flash newest rom via odin using pit file.
What is the Odin error message? What file fails to flash? Is Odin able to pick up the partition information from the phone?
audit13 said:
What is the Odin error message? What file fails to flash? Is Odin able to pick up the partition information from the phone?
Click to expand...
Click to collapse
Hi audit13's Avatar. Thanks for your reply.
The file i downloaded from samsung. The offical rom N7100XXUFNL1
Below is what shows in the measage window.
<OSM>N7100XXUFN1_N7100EURFNG1_N7100XXUFNG1
<OSM>Chaecking MD5 finished successfully..
<OSM>Leave CS..
<ID:0/005>Odin v.3 engine (ID:5)..
<ID:0/005>File analysis..
<ID:0/005>SetupConnection..
<ID:0/005>Initialzation..
<ID:0/005>Set PIT file
<ID:0/005>DO NOT TURN OFF TARGET!!
<ID:0/005>Can't open the specific file.. (Line: 1876)
<OSM>All threads completed. (Succeed 0 / failed 1)
I dont understand the 3rd question... how do u check that?
zett89 said:
Try to flash newest rom via odin using pit file.
Click to expand...
Click to collapse
Thanks for your reply. Not sure how to that?
You're using the latest rom from sammobile.com? If you are, you're unzipping it to have a tar.md5 file? Looks like you may not need a pit file as Odin is able to read the pit information from the phone.
audit13 said:
You're using the latest rom from sammobile.com? If you are, you're unzipping it to have a tar.md5 file? Looks like you may not need a pit file as Odin is able to read the pit information from the phone.
Click to expand...
Click to collapse
What should i do then. Could you walk through it as im a bit of a novice...
You may not need a pit file as Odin looks like it can read the information from the phone. Try flashing the stock ROM from Sammobile.com.
If the ROM doesn't flash, try different USB cables and USB ports.
download newer version of Odin HERE
and uncheck repartition.
yaro666 said:
download newer version of Odin HERE
and uncheck repartition.
Click to expand...
Click to collapse
Will do. I will keep you posted...
Hi,
I recently got a SM-T210 from a friend to repair. The description given was that their kids factory reset the unit and won't boot anymore. First the tablet had the death sleep issue which is a easy fix. But after that the tablet simply continues to show the "Samsung GALAXY TAB3" boot screen and never finishes booting.
As I'm known with Odin I simply downloaded the original firmware from sammobile for this tablet and took the firmware version for the Netherlands as that's where I live. There are 2 4.4.2 versions available and downloaded them both. When using Odin 3.09 and higher I simply cannot install the firmware, but on Odin 3.07 it can. Although it installs the tablet still fails to boot properly and hangs at the tab logo as described earlier.
With Odin 3.09 or higher I'm not even able to install the firmware as it says that there is no PIT file and NAND flash write fails. I've found 2 PIT files for this tablet on the forums and even with the use of these PIT files it still errors with the same issue and installation seems impossible with these versions of Odin.
I've also tried installing TWRP recovery but that won't boot either. When booting the tablet with volume key up it shows the Andriod icon with the spinnng "intestines" and alot of red error messages show not able to find /system and /data. My guess is that this is pretty bad, but that is what I want to fix with the stock firmwares and/or the PIT files (LT02.pit and T210(R).pit).
I'm currently out of ideas to revive this tablet and almost start thinking that it's completely dead, but before throwing it in the garbage bin I'm wondering if anybody here is able to help me further with this issue.
If you think you miss critical information, let me know so I can supply it!
Any help is greatly appreciated and thanked for!
langerak said:
Hi,
I recently got a SM-T210 from a friend to repair. The description given was that their kids factory reset the unit and won't boot anymore. First the tablet had the death sleep issue which is a easy fix. But after that the tablet simply continues to show the "Samsung GALAXY TAB3" boot screen and never finishes booting.
As I'm known with Odin I simply downloaded the original firmware from sammobile for this tablet and took the firmware version for the Netherlands as that's where I live. There are 2 4.4.2 versions available and downloaded them both. When using Odin 3.09 and higher I simply cannot install the firmware, but on Odin 3.07 it can. Although it installs the tablet still fails to boot properly and hangs at the tab logo as described earlier.
With Odin 3.09 or higher I'm not even able to install the firmware as it says that there is no PIT file and NAND flash write fails. I've found 2 PIT files for this tablet on the forums and even with the use of these PIT files it still errors with the same issue and installation seems impossible with these versions of Odin.
I've also tried installing TWRP recovery but that won't boot either. When booting the tablet with volume key up it shows the Andriod icon with the spinnng "intestines" and alot of red error messages show not able to find /system and /data. My guess is that this is pretty bad, but that is what I want to fix with the stock firmwares and/or the PIT files (LT02.pit and T210(R).pit).
I'm currently out of ideas to revive this tablet and almost start thinking that it's completely dead, but before throwing it in the garbage bin I'm wondering if anybody here is able to help me further with this issue.
If you think you miss critical information, let me know so I can supply it!
Any help is greatly appreciated and thanked for!
Click to expand...
Click to collapse
Nothing to loose so i should give it one more try with Kies. I remember that years ago i had a problem with a samsung phone and even Odin wasn't helping me. I did it with Kies then which fixed it. No garantuees though.
Droidphilev said:
Nothing to loose so i should give it one more try with Kies. I remember that years ago i had a problem with a samsung phone and even Odin wasn't helping me. I did it with Kies then which fixed it. No garantuees though.
Click to expand...
Click to collapse
Thanks, I've tried it with Kies but it won't even recognize the tablet. When I put it in Download mode and connect it to my computer the Kies welcome screen keeps switching every 2 seconds to the connecting screen, back to the welcome screen and keeps on going like that.
Any ideas left?
langerak said:
Thanks, I've tried it with Kies but it won't even recognize the tablet. When I put it in Download mode and connect it to my computer the Kies welcome screen keeps switching every 2 seconds to the connecting screen, back to the welcome screen and keeps on going like that.
Any ideas left?
Click to expand...
Click to collapse
Except for correct drivers etc etc not really, no.
I am facing same problem.
My Tab 3 (Sm-T210) has gone too.
Now I can't restore it.
I have downloaded Stock ROM from sammobile.org,
but I can't extract this properly.
It always says that "files are corrupted".
I am also going to be hopeless as like as you.
Recently my phone (A520F) started rebboting itself, i didnt think much of it until one day i left it charging and i came back to seeing my phone on Download Mode. I tried getting out of it but it brings me right back to it. When i charge it, download mode. When i turn it on, download mode. I believe the ROM got damaged or something inside. I tried flashing it with odin using the Home CSC so i wouldn't lose important data, but when i tried to start it a error came saying that there was no PIT Partition.
Is there a way to install the PIT Partition without formatting my device? Because i heard you needed to. Or anyway i can get my data out? It's been a week since i cant access my data and im pretty worried.
Sorry if this isnt the right place to ask, first time ever using this platform.
Do you have a PIT file selected in the Odin from the stock ROM?
LR7875 said:
Do you have a PIT file selected in the Odin from the stock ROM?
Click to expand...
Click to collapse
Sorry for the late reply.
I do not have a PIT file selected, because im afraid that if i do select the PIT File correctly, and it flashes, it will format my device. I heard it somewhere, though i dont remember where.
I do have one ready for use.