I don't understand why this is so difficult just for this 1 phone. it's killing me to have a galaxy note 2 hat doesn't work and I have to use my galaxy note 1. is there a program I can use to extract the pit file? because I'm pretty sure that I have the stock wind ROM but when I used it I still got the boot loop.
I don't understand why this is so difficult just for this 1 phone. it's killing me to have a galaxy note 2 hat doesn't work and I have to use my galaxy note 1. is there a program I can use to extract the pit file? because I'm pretty sure that I have the stock wind ROM but when I used it I still got the boot loop.
I have the exact same problem, however flashing the T-Mo modem did not solve the bootloops. It will not make it past the boot animation.
Hey guys.... are you still having this issue? I have actually solved my issue and never been so happy to use my phone!
Hey guys.... are you still having this issue? I have actually solved my issue and never been so happy to use my phone!
How did you solve this
Sent from my SGH-T889V using Tapatalk 2
I'm sorry I've been away... still in need of some help?
Sent from my SGH-T889V using xda app-developers app
Sent from my SGH-T889V using xda app-developers app
Yes please, I still need help. Samsung has returned my phone and they said warranty is void because of the custom ROM flashing.
Long story short, I lost my IMEI and baseband due to flashing a incompatible kernel.
NV item reader writer will not read my phone even in diag mode, saying no answer.
No luck on imei reinjection.
Need help.
If you have any suggestions please share with me, much appreciated.
Ashwill, one thing you could try is writing the m9kefs1, 2 and 3 partitions with the files hkfan uploaded in this thread from CWM or TWRP.
COM ports-wise, what do you see in Device Manager? (trying to make sure your setup looks OK to start with)
COM ports-wise, what do you see in Device Manager? (trying to make sure your setup looks OK to start with)
In the NV Item Reader/Writer port chooser I see something like Samsung Serial Port, I can choose it and connect to it, but unable to read. After it goes through all the ports, it will stop and say Failed... No Answer From the Phone
Thank you for your link above, I've asked you about how to connect to the phone using the NV item reader/writer and you gave me suggestions. The reason I didn't continue asking questions after that was because I sent my phone to this useless Samsung authorized repair center in Toronto for 5 weeks and came back as is. They basically spent 5 weeks determining my phone has been flashed with custom firmware and decided to void my warranty.
So now I have my phone back and I'll keep trying to repair it; I actually gave it to a repair store to try to repair with a cost of $70 CAD and they will not charge anything if they fail.
Thank you very much for sharing this useful information, I believe a lot of people will find it very useful.
However, as I mentioned before, I could not get my phone to connect through QPST, NV Item Reader/Writer, any software like that does not have recognize my phone. I know that if I can get it to connect, everything is just solved.
I wonder whether it would matter if I flashed the i317M modem instead of the T889 tmo modem. Also when I googled no answer from phone from those software I saw couple threads talking about it was the problem of the devices, so who knows, I might just have ****ty luck.
nah don't even think about it!!
before you connect your note to qpst; did you dial *#7284# to acces the qualcom settings anf select RNDIS + DM + MODEM
then on qpst configuration select your port
Last edited:
Ashwill, just double checking: did you make sure Kies wasn't running anything in the background? That software and its dependent background services are known repeat offenders when it comes to interfering with Odin or QPST.
Consider trying on another computer, one where you install only the Samsung drivers (extracted from the Kies installer if necessary) along with QPST/QXDM and NV_reader_writer.
If you're with Robellusfivirkoo, you might as well flash the I317M modem. Contrary to the (current, LTE update pending) T-Mobile USA T889 modem, or the T889V one, it has LTE enabled once you combine it with the proper NV settings; not unlike the AWS mod people have been doing the other way around. If on the other hand you're with Wind, Mobilicity or Videotron, I wouldn't bother with the extra steps.
Consider trying on another computer, one where you install only the Samsung drivers (extracted from the Kies installer if necessary) along with QPST/QXDM and NV_reader_writer.
If you're with Robellusfivirkoo, you might as well flash the I317M modem. Contrary to the (current, LTE update pending) T-Mobile USA T889 modem, or the T889V one, it has LTE enabled once you combine it with the proper NV settings; not unlike the AWS mod people have been doing the other way around. If on the other hand you're with Wind, Mobilicity or Videotron, I wouldn't bother with the extra steps.
I did everything I could, all steps, everything and nothing works, thanks again man.
I have T889V like you do, and because I'm stuck in bootloop I need to flash an other modem to make it boot into the system. So I flashed the i317M modem but in your case you flashed the T889 modem. That's what I'm wondering, not that I haven't tried flashing a different modem before.
---------- Post added at 10:36 PM ---------- Previous post was at 10:32 PM ----------
It is a brand new Windows 8, and I have tried on Windows XP, Vista, 7 32/64 bits with/without Kies. And when I flashed the i317M modem the first time, I enabled LTE on my T889V on my Fido carrier. So everything is working pretty well before I flashed the kernel for 7105.
The last chance I have is to try flashing the T889 modem instead of the i317M one and the efs partition file in your link. I saw an add on Toronto kijiji that someone is able to fix that so I'm asking him about it too.
Saw I had a similar issue and this is what I did to resolve. First off i am not expert but again trying to help. I flashed a T889 modem via TWRP and after that all heck broke loose, bootloop. I then used TWRP to wipe all data factory reset and still it would not work. Trying to Use Odin to write back stock ROM in my case failed, getting stuck on Nand Write Flash. At the end of my rope I used Odin to flash Stock Recovery back. Again Odin failed. So I booted into recovery and did a full wipe of everything cache included. At that point Odin worked and I was able to write back a stock Rom. However my IMEI and is Null / Null so I am still screwed. I was told I would need a NSPro Box to fix it but I really do not want to spend the money. Problem is I cannot get the phone Utilites to show even though I have followed all the threads I can find on how to. Anyway not sure it will work in your case but just sharing and hope it helps anyone out there in the same situ... Man T mobile phones are a pain in the side!!!!
Last edited:
Similar threads
