Need efs from a T889 - T-Mobile Samsung Galaxy Note II

I've thoroughly trashed my efs & nv items. Long story but basically, I went into dialer menu #*9090#, picked option #3 and, thinking I had multiple backups of everything, picked yes. Dumb? Yes.
My backups were on a hard drive that I'd replaced with an SSD and got lost during that replacement. I hadn't backed up the backups - only had the single copy now lost.
Phone will boot but now shows unknown baseband, borked IMEI. I can get into download mode and have TWRP recovery installed. WIFI works, I can easily get stuff on/off the device & access an ADB shell. It's rooted/stock UVALJ1.
I did find one backup, made using QPST (.qcn file), but in trying on two different PCs & a 32bit WinXP VM I cannot get the phone recognized by QPST (drivers installed, finds port, but "No phone".)
If someone can give me a TWRP backup of their efs I *think* that may get me fixed. I know that may contain your IMEI & if it fixes me but contains the wrong IMEI, that's fairly easy to fix, assuming all the posts on fixing that issue are accurate. I'm not trying to steal an IMEI, I'm trying to make my Note 2 usable as a phone again.
Sent from my Nexus 7 using Tapatalk

LanceDiamond said:
I've thoroughly trashed my efs & nv items. Long story but basically, I went into dialer menu #*9090#, picked option #3 and, thinking I had multiple backups of everything, picked yes. Dumb? Yes.
My backups were on a hard drive that I'd replaced with an SSD and got lost during that replacement. I hadn't backed up the backups - only had the single copy now lost.
Phone will boot but now shows unknown baseband, borked IMEI. I can get into download mode and have TWRP recovery installed. WIFI works, I can easily get stuff on/off the device & access an ADB shell. It's rooted/stock UVALJ1.
I did find one backup, made using QPST (.qcn file), but in trying on two different PCs & a 32bit WinXP VM I cannot get the phone recognized by QPST (drivers installed, finds port, but "No phone".)
If someone can give me a TWRP backup of their efs I *think* that may get me fixed. I know that may contain your IMEI & if it fixes me but contains the wrong IMEI, that's fairly easy to fix, assuming all the posts on fixing that issue are accurate. I'm not trying to steal an IMEI, I'm trying to make my Note 2 usable as a phone again.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Flashing EFS from another device is not going to work.
Try to recover the IMEI using KIES emergency recovery. http://forum.xda-developers.com/showthread.php?t=2261153
If this still does not work try flashing the UVALJ1 modem.

ciphercodes said:
Flashing EFS from another device is not going to work.
Try to recover the IMEI using KIES emergency recovery. http://forum.xda-developers.com/showthread.php?t=2261153
If this still does not work try flashing the UVALJ1 modem.
Click to expand...
Click to collapse
Can't seem to get KIES to connect - the most definitive result I got was a device not supported by KIES message after uninstalling/reinstalling drivers, making sure the phone is in the right mode etc. For the most part KIES just sits at connecting forever. This is the case with both the Note 2 and a Samsung Galaxy S4. KIES isn't exactly inspiring confidence it can magically restore my entire efs & all NV items...
Just to clarify, I can access recovery just fine - I can use Odin to flash to whatever albeit the bootloader is 4.3/Knox locked. I can flash modems, ROMS, etc and access ADB shell or whatever else I'd need to do with ADB. Can't seem to get KIES to work and as I understand it what you're telling me to do in KIES won't actually restore efs, it just resets it to a stock state and lets efs rebuild - assuming the NV items are still there, which they are not. I really hope I'm wrong and I'll have to come back here once I get KIES sorted out and tell you how silly I was for not believing you in the first place!
I did re-flash the modem using TWRP, no change there.
Here's the text of the warning I foolishly ignored:
Warning: Must read below guide
All Communication between AP/CP-
will be disconnected!
To return to normal mode,you
must download efs12.tar file!
All NV data will be erased!
Really want to use RmNET?
Click to expand...
Click to collapse
This was in the ServiceMode menu accessed with dialer code *#9090# but now there isn't a menu there - just a blank screen that says ServiceMode at the top. Dialer code *#0011# produces the same result - no menu where there used to be one, just blank screen/ServiceMode. Based on that warning, this isn't something I expect KIES to fix - but as I said, I hope I'm wrong about that...

Tried KIES on another PC with same result - that was 2.x KIES.
I used Odin 3.09 to flash to T-Mobile stock rooted 4.3 from this thread: http://forum.xda-developers.com/showthread.php?t=1975560
Switching to KIES 3 got KIES talking to the phone. It says I'm on the current version of the firmware (because I am - it's what I just flashed with Odin.) If I go into Tools/Emergency nothing is listed. If I go into the second choice and enter the model number with the phone plugged in, it tells me it doesn't support firmware initialization. If I do it without the phone plugged in, it works and accepts the serial number from the phone. If I plug the phone in right after I've gotten past this point, KIES winds up going off into never never land a bit later after it tells me everything is going to be wiped and the phone will be put back to its initial state (which does sound somewhat promising.)
Its spawning this AdminDelegator process which seems to just be sitting doing nothing and the KIES window is shaded. I can close it but that's about the only interaction possible with it in this state - none of the menus work and it seems like it's waiting on something to be clicked maybe in the AdminDelegator process but that process has no window anyplace.
It's possible there is something useful buried in KIES but it's a horrible piece of software. They seem to be authoring it on at best 32bit Windows 7 and that's a stretch, I suspect they're still targeting 32bit XP. I'm on x64 Windows 8.1. I could rant much more but I'll leave it at that.
I'm going to keep working with it and see if I can get around how they've written it or I might just stick it in a 32bit XP VM and see if it's happy back in 2005, software-wise. <G>
I may wind up giving up and just getting another phone - I've already read up some on my options and the funny thing is, I still want a Note 2 - they can be had for more reasonable $ now than a year ago anyway...

LanceDiamond said:
Tried KIES on another PC with same result - that was 2.x KIES.
I used Odin 3.09 to flash to T-Mobile stock rooted 4.3 from this thread: http://forum.xda-developers.com/showthread.php?t=1975560
Click to expand...
Click to collapse
Did you verify the IMEI after this flash ?

ciphercodes said:
Did you verify the IMEI after this flash ?
Click to expand...
Click to collapse
Short answer: IMEI & baseband same as before the flash - both are "Unknown".
Prior to my messing with the dialer menu, everything was fine. I'd used Odin or TWRP recovery to flash a variety of different ROMs the last of which was the 4.3 we're talking about here and it was working. I'd used it for several days. Everything but screen mirroring worked without any problem and I had service - I read up on the screen mirroring problem and it sounded like getting the device to show "Official" might help so I tried to reset my flash counter which I did not do before going to 4.3. Flash counter wouldn't reset so I decided to go back as far as I could on modem/ROM and see if I could reset flash counter then. (I know my Knox flag is not fixable - I was just trying to change the flash counter.)
Using TWRP, I installed UVALJ1 modem & associated ROM, leaving the 4.3 Knox locked bootloader in place to see if that'd work. It did, it booted and I had service. I was actually playing with the menus to see if the old dialer code free unlock menu settings still seemed to work because someone had posted about needing to unlock - looked like the menus were still there for doing an unlock. In messing with the menus I picked the option that messed everything up and since doing that, no matter what I flash, IMEI & baseband are unknown.
Unless KIES rebuilds the entire radio - which it very well might based on it needing the correct model and then wanting a valid serial # - I think I need an efs restore to get the phone communicating with anything now.
One thing I just now did - using the free NV Items Reader Writer from this thread: http://forum.xda-developers.com/showthread.php?t=1804117
On my Note 2 configured as "DM+Modem+ADB" in Qualcomm USB settings (the only of several dialer menus I know of that still actually exists & seems to work), I can see the modem & port in device manager. But the app cannot communicate with the phone. If I change nothing, unplug the Note 2, plug in my Galaxy S4 in "DM+Modem+ADB" mode, I see modem & ports pop up in device manager and now the app can communicate with the phone.
I'm afraid, based on the text of that warning and searching for what "AP" and "CP" are, that the phone isn't going to be able to communicate with much of anything until it gets its efs fixed. This test where I just swap phones seems to be comfirming that this phone isn't responding like it should. Basically my modem & the rest of the phone are disconnected right now - at least that's my understanding. If the modem really is disconnected then obviously trying to do something to fix it via the modem is never going to work. The KIES may work - if I can ever get it sorted out. Haven't yet tried it in a VM might do that right now...
Edit:
Got KIES3 & drivers working in Windows XP SP3 VM. KIES connects to phone but if I pick Tools/Firmware Upgrade with the phone connected it just says "SGH-T889 does not support initializing" and my only choice is "OK". If I go Tools/Firmware without the phone plugged in, I can enter the model # and then it asks for serial #. If I plug the phone in at the point it goes all the way to where it says it's downloading firmware and then same result as on Windows 8 - an AdminDelegator process gets started, KIES gets sort of dimmed like it's waiting on something and nothing ever happens. If I never connect the phone KIES goes through the downloading process then gets an error with options to send a message or cancel - no information about what the message is, what the error is - just I can send it, it won't contain personal information or I can cancel.

Related

Baseband Unknown and IMEI Null NOW WORKING

Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/showthread.php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/showthread.php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
I lost my imei again after tinkering, so i went back to this post, followed the procedure and it worked again.
hope this will save somebody's phone also.
I treid to use EFS Pro, but when I push the connect button, it says connection was lost and the program crash and ask me to restart it.
What am I doing wrong?
karlonicolas said:
Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/showthread.php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/showthread.php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
Click to expand...
Click to collapse
So did you solve it without an EFS backup or I misunderstood?
after dialing *#7284#
Miaxus said:
So did you solve it without an EFS backup or I misunderstood?
Click to expand...
Click to collapse
EFS backup is not enough on N7105. The IMEI is stored somewhere else. EFS Pro can backup IMEI from Nvram and restore it.
It is also suppose to write IMEI to the phone, but I never manage to connect it to my phone.
Sent from my GT-I9505 using Tapatalk
Same problem facing but i have this on my GT N7100 ???????
I`m also facing the same problem from few months but in my case it has been repaired by the repairing shop in only 5$ , and they said me that the has done this by some uart tools. But when i gets unrooted by flashing stock or any firmware my note 2`s IMEI gets zero. So i cant stay unrooted and every time I`ve to go back to that repairing shop. So i just wants to know that is this helps to fix this problem permanently . Imeant i just want to stay unrooted after facing all shorts of complications. Plz help
After dialing *#7284#
sora9009 said:
after dialing *#7284#
Click to expand...
Click to collapse
yeah I got the same with you after dialing *#7284#. It shows 2 radio buttons of UART (MODEM, PDA), and 2 radio buttons of USB (MODEM, PDA). How to solve this thing?? I got my IMEI messed up too.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
HIT THANKS IF I HELPED YOU :good:
Device that I'm using right now: Samsung GALAXY Note II International N7100
Firmware: Latest Android 4.3 N7100XXUEMK4 with KNOX Bootloader *NO!!!, somebody please help me remove this idiot BL*
Recovery: CWMR Philz Touch v6
Root: Hell yeah, of course!
One Direction is on XDA-Developers! Note: This 1D XDA account is run by one of official 1D crew, NOT those five singers!
sora9009 said:
after dialing *#7284#
Click to expand...
Click to collapse
there's supposed to be an option "qualcomm USB settings" after hitting *#7284#. have you tried scrolling down. i recall it was below the "save and reset button"
perhaps your chipset is Exynos. i have tried this only for note 2 lte which has qualcomm.
otherwise, you current modem may be different. perhaps you can flash the modem from DMC3 using odin, reboot, and follow the steps again.
the "qualcomm USB settings" should be similar to the one below (i said similar, because the image below is for S4 not Note 2 LTE)
colman1982 said:
I treid to use EFS Pro, but when I push the connect button, it says connection was lost and the program crash and ask me to restart it.
What am I doing wrong?
Click to expand...
Click to collapse
this happened to me also in the process of fixing. i suppose you configured correctly the Qualcomm USB settings, right? using the option with RM***NET...?
What computer OS are you using?
i was able to fix the phone using Windows XP. Also i downloaded all the USB drivers as required in the EFS Pro link.
"Make sure you have Microsoft .NET Framework v4.0 installed on your PC." it also says in the post.
I also turned off Kies. There was also a note to turn off all programs that use ADB.
Good luck!
karlonicolas said:
there's supposed to be an option "qualcomm USB settings" after hitting *#7284#. have you tried scrolling down. i recall it was below the "save and reset button"
perhaps your chipset is Exynos. i have tried this only for note 2 lte which has qualcomm.
otherwise, you current modem may be different. perhaps you can flash the modem from DMC3 using odin, reboot, and follow the steps again.
the "qualcomm USB settings" should be similar to the one below (i said similar, because the image below is for S4 not Note 2 LTE)
Click to expand...
Click to collapse
international n7100 use exynos mate
karlonicolas said:
J
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
Cheers!
Click to expand...
Click to collapse
Hi there. THis is a great post and very informative.
Can you help please, I can not find the above file on sammobile. would you be able to post a link or offer some direction as to where you found it?
thanks in advance
karlonicolas said:
this happened to me also in the process of fixing. i suppose you configured correctly the Qualcomm USB settings, right? using the option with RM***NET...?
What computer OS are you using?
i was able to fix the phone using Windows XP. Also i downloaded all the USB drivers as required in the EFS Pro link.
"Make sure you have Microsoft .NET Framework v4.0 installed on your PC." it also says in the post.
I also turned off Kies. There was also a note to turn off all programs that use ADB.
Good luck!
Click to expand...
Click to collapse
I did configure the Qualcomm USB settings. I use windows 8 64 bit. It crashed with some framework error also. Windows 8 says framework is already installed. I will try next year on my windows 7 64 bit computer.
Sent from my GT-I9505 using Tapatalk
I sent my phone to service and it came back with new mother board and update software to 4.3.
I now manage to make backup with EFS pro on windows 7 64 bit. Just in case.
Sent from my GT-N7105 using Tapatalk
karlonicolas said:
Just sharing my experience in solving this issue. Hopefully it will help solve those who have similar issues.
I flashed a file which messed up my EFS partition. I had a backup and tried to use the available programs to restore my EFS using my backup. None worked. I even brought it to the samsung store, but they said they would change the motherboard and reprogram, and replacement and service would cost more than half the cost of a new N7105. I purchased the phone in another country. The people who had stores to repair phones gave up on my phone. They also offered to replace the motherboard for US$175.00.
My phone was originally under a DMB2 rom (from Singapore I think). I flashed a DMC3 rom, and used this for five months, until i encountered the problem.
I initially gave up and got a note 3. But i could not believe the phone was junk and people in XDA (as I observed) do not seem to give up.
After two weeks, i found the solution below, which brought my phone to working condition.
1. I flashed the stock rom N7105ZHDMI2_N7105ZZHDMI2_TGY from sammobile.
2. I flashed a pit file using Odin. The pit file is found here:
http://forum.xda-developers.com/showthread.php?t=2137008
This restored the baseband. But IMEI was no longer NULL. However, it was still 0.
3. I downloaded and used the EFS Pro from this link:
http://forum.xda-developers.com/showthread.php?t=1308546
Before using EFS Pro, make sure you dial *#7284# and change the setting of Qualcomm USB Settings to
"RMNET + DM + MODEM"
I will not hurt your phone if you do, but EFS Pro will just not work. If you don't do this, the EFS Pro will display "Phone not responding" or something similar.
NOTE: I couldn't find the option with RMNET, but i used the option that also had an "RM*** + DM + MODEM".
After the phone is read, change back the IMEI to what it was originally.
Dial *#7284# again to change back to "MTP+ADB".
It's all working now.
Hope this is able to help someone. Now i have two working versions of Note.
Thanks to the authors of the program i used, and the people who uploaded the files used.
Cheers!
Click to expand...
Click to collapse
Hello, I am on my way to try this, since i dont have a Baseband or IMEI. (started with no service, signal at all on stock, now im custom, still nothing).
But step 1 is that with the recovery, since it wont accept my N7105XXUEMK9_N7105DNFEMK2_DNF.zip ?
ODIN wont see it in download mode. Perhaps its my recovery (Philz ver 6.12. with cwm 6.0.4.7.).??
I'm trying to restore my IMEI but having followed all the steps, I get "IMEI written successfully" but if I re-read the IMEI or look on the phone (even after rebooting) the IMEI has not changed.
Any ideas?
osirls said:
I'm trying to restore my IMEI but having followed all the steps, I get "IMEI written successfully" but if I re-read the IMEI or look on the phone (even after rebooting) the IMEI has not changed.
Any ideas?
Click to expand...
Click to collapse
How did u write ur IMEI? Efs Pro?
I am trying with n5120 from 2 months but no use Imei null
needs newboard I guess
bst dongle useless

[Q] Please help a Noob

OK. I think I've done my due diligence. I've scrubbed the forums for 2 days, I've googled it and I still can't figure out what I'm doing wrong.
Friend gives me this rooted LG OGP. Awsome! Works great! Then AT&T or LG sends an OTA update that bricks it :crying:. Read Aryan1312's sticky thread in this forum and get all pieces together. By now I have the 3.8.1 drivers AND the newest 3.10.1 drivers, LGFlashTool 1.8.1.1023, along with the newest 10P TOT file. I got the Flashtool to stop asking for PW and I think I'm ready to go.
But then . . . Plug my phone in and Device Management doesn't know what to do with phone. Reinstall drivers pack from LG website. Still no dice. Hmm. Phone is in Team Win Recovery Project v2.6.3.0 recovery screen (I guess that's what it's called) and computer doesn't know what to make of it. Hmm.
Maybe I can put it onto a microSD card and copy stuff over to phone? Maybe flash a different ROM through TWRP? Let's try that. I copy files over to the external SD card, put it into the phone, restart phone, hello TWRP, Advanced-File Manager option, WHY CAN'T YOU SEE THE EXTERNAL SDCARD??? Isn't it supposed to be there under /extSD?? It's time to ask for help.
Question: How do I get my Win7 PC to see the phone as a removable drive/external drive/whatever you call it so that I can get this info over?
I know that I have to change Port #'s after Win7 sees the phone. I just can't get there . . . yet.
- What I've tried:
Reinstalled drivers (both versions) and restarted between trying to plug phone in.
Tried installing phone drivers manually. Still doesn't mount as external HD as far as Win7 is concerned.
Called friend to ask his opinion. He doesn't remember and tries to tell me this is why Apple is "better".
Scoured the web to see what to do. Found articles about this same thing happening and all point to Stickied Post on this XDA forum
I did RTFM and am still lost.
---- Sorry for the long post, I just thought that people who wouldn't mind helping would appreciate the extra info.
Drivers
landran said:
OK. I think I've done my due diligence. I've scrubbed the forums for 2 days, I've googled it and I still can't figure out what I'm doing wrong.
Friend gives me this rooted LG OGP. Awsome! Works great! Then AT&T or LG sends an OTA update that bricks it :crying:. Read Aryan1312's sticky thread in this forum and get all pieces together. By now I have the 3.8.1 drivers AND the newest 3.10.1 drivers, LGFlashTool 1.8.1.1023, along with the newest 10P TOT file. I got the Flashtool to stop asking for PW and I think I'm ready to go.
But then . . . Plug my phone in and Device Management doesn't know what to do with phone. Reinstall drivers pack from LG website. Still no dice. Hmm. Phone is in Team Win Recovery Project v2.6.3.0 recovery screen (I guess that's what it's called) and computer doesn't know what to make of it. Hmm.
Maybe I can put it onto a microSD card and copy stuff over to phone? Maybe flash a different ROM through TWRP? Let's try that. I copy files over to the external SD card, put it into the phone, restart phone, hello TWRP, Advanced-File Manager option, WHY CAN'T YOU SEE THE EXTERNAL SDCARD??? Isn't it supposed to be there under /extSD?? It's time to ask for help.
Question: How do I get my Win7 PC to see the phone as a removable drive/external drive/whatever you call it so that I can get this info over?
I know that I have to change Port #'s after Win7 sees the phone. I just can't get there . . . yet.
- What I've tried:
Reinstalled drivers (both versions) and restarted between trying to plug phone in.
Tried installing phone drivers manually. Still doesn't mount as external HD as far as Win7 is concerned.
Called friend to ask his opinion. He doesn't remember and tries to tell me this is why Apple is "better".
Scoured the web to see what to do. Found articles about this same thing happening and all point to Stickied Post on this XDA forum
I did RTFM and am still lost.
---- Sorry for the long post, I just thought that people who wouldn't mind helping would appreciate the extra info.
Click to expand...
Click to collapse
1. Is the first pic with the phone connected to the pc?
2. If yes, have you tried to manually update drivers, while in device manager
3. I know that this is going to sound funny but have you tried a different USB port. The reason I ask is I had the same problem LG Optimus M and the phone was down for a couple of days. I tried everything and was about to call it quits but for some reason when I changed USB port the computer saw the phone and I was back in business. I am not saying that will 100% work but it is worth a try.
TheMighyLoki said:
1. Is the first pic with the phone connected to the pc?
2. If yes, have you tried to manually update drivers, while in device manager
3. I know that this is going to sound funny but have you tried a different USB port. The reason I ask is I had the same problem LG Optimus M and the phone was down for a couple of days. I tried everything and was about to call it quits but for some reason when I changed USB port the computer saw the phone and I was back in business. I am not saying that will 100% work but it is worth a try.
Click to expand...
Click to collapse
Yes I have. I think I did figure it out though. I put the device into "download mode" and my computer could see, and communicate, the phone.
To put my phone into "download mode" I did the following:
I connected the phone to the computer physically with USB cable
I turned phone off.
I pressed BOTH volume buttons and held the power button while phone was attached to computer.
With BOTH volume buttons still pressed, I released the power button.
The phone screen was black with a little dialog box in the middle saying "download mode"
I could then use LGFlash Tools to flash Stock AT&T TOT file back into phone. Took 519 seconds to complete the stock flash.
New problem arises, After flash, I do NOT have any 3G/4G signal. I can use the phone to make and receive phone calls and text messages, but I CANNOT use mobile internet unless I have it connected via wifi.
I installed the Debloated ROM and "tried" to flash 980 Baseband.zip but when I tried to install baseband, CWM gave me a permission error and said install failed. I haven't been able to use mobile internet since. Any help???
-- Again, sorry for the lengthy post. I figured that I might not be the only person who has gone through this. I see a lot of viewers to the thread so I think other people might be having same troubles as me.
landran said:
New problem arises, After flash, I do NOT have any 3G/4G signal. I can use the phone to make and receive phone calls and text messages, but I CANNOT use mobile internet unless I have it connected via wifi.
I installed the Debloated ROM and "tried" to flash 980 Baseband.zip but when I tried to install baseband, CWM gave me a permission error and said install failed. I haven't been able to use mobile internet since. Any help???
-- Again, sorry for the lengthy post. I figured that I might not be the only person who has gone through this. I see a lot of viewers to the thread so I think other people might be having same troubles as me.
Click to expand...
Click to collapse
It sound like you need to manually set the APN. Do a Search for your provider.. ie AT&T T-Mobile the setting is under Network/Tethering & Networks/ Mobile networks/ Access point name/ Hit Menu Button and New APN
You are the MAN / WOMAN!! Thanks for the help. That fixed it.
For posterity and to help another "noob" stuck in my case later (maybe months down the line)
This is what I've done up until now in plain text:
Used LGFlashtool to flash AT&T stock "10k" build
Went into Settings Icon>General>Developer Options>check off "USB Debugging"
Used "E980 Universal Root" from forums to gain Root access (verified with "Root Checker" from Playstore)
Used FreeGee to get TWRP recovery installed (rebooted into recovery with "QuickReboot" from Playstore).
Used TWRP recovery to install "E980 Baseband.zip" from forums
Factory Reset
Setup new phone and input APN settings (located in Settings Icon>Networks>Tethering & Networks>Mobile networks>Access point names>Menu button "New APN"/input carrier values/Menu button "Save")
Now that I know how to get back here, I'm going to scrap the stock ROM and try to do this whole process with a custom ROM. . . and another flash-a-holic is born. The learning journey continues.
Welcome:beer:
*KCCO*2SHAYNEZ*E980*
That is what this forum is for.
I have been helped out a lot from the group and I just thought it was time to pay it back. It is good to hear that you got it up and running. But one last word of advise BACK UP, BACK UP, BACK UP, and when that is done, back up the back up to the computer.

Putting a 100$ bounty for someone to fix my phone (SGH-i317M)

I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.
have you given a look at this thread? http://forum.xda-developers.com/showthread.php?t=2711825 it might give you some ideas to help you out. also did you try flashing a new recovery to see if you could at least get it to boot to that?
dont care about the bounty just trying to toss something out there that may help you
Did you ever try flashing the stock recovery - JUST the stock recovery - through Odin?
If not, grab the recovery.img and make your own tarball for Odin in Linux.
Hopefully that will flash and get you closer.
eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
...
i have access to both windows and ubuntu linux if it makes a difference.
Click to expand...
Click to collapse
Since you mentioned Ubuntu, you can also try using heimdall instead of odin... http://glassechidna.com.au/heimdall/ . Unfortunately, I think it may be a hardware problem?
Since you are willing to pay to have it fixed, if all else fails, you can always send it off to http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-jtag-brick-repair/. It will actually be cheaper than what you are offering to pay ~$40 + shipping
good luck
Thanks all for your help, I've messed around and gotten no closer. I'm beginning to lean on a hardware failure, perhaps from the usb data port either that or the way bootloaders are packaged in kitkat 4.4 is different. which is why initially this thread gave me hope: http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096 but i tried far too many times now to believe I'm going to succeed. In fact, I've gotten confused as to what i tried, in which order, with which rom. I'm basically trying anything and that's a recipe for bricking the phone for good. so i've stopped.
I'll also thank kozmo21 for the link to the repair shop. i was unaware this existed, as a last resort I'll be sending them my phone. If it turns out they are able to repair it, I'll honor my word and give you something for having been part of the solution.
eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.
Click to expand...
Click to collapse
Have you tried going to sammobile and download the newest firmware and only flashing that in odin?
Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app
ShrekOpher said:
Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
More than likely its a bootloader issue my phone did that and all i did was flash the bootloader then it worked again but hes done so much idk what he needs now that's y i said to try a firmware to see if that helps
Download toolkit and select option to push file into phone.
Download a ROM of your choosing, push it into your phone, restart in recovery mode and select file.
Update?
Did you get it fixed? Just my two cents, in case you didnt, I had a similar problem and alll I did to fix it was flash the JediMasterX2 ROM with CWM and everything worked out.

[Q] Need help unbricking

This is practically a cry for help after i searched for hours.
Model: Sm-n910P
Software version : Unknown
Android : 4.4.4
Baseband: Unknown
build: PVPU1ANK2
Stock recovery
(if anything else helps just ask)
Problem first: My note 4 has no network of any kind (wifi doesnt start , doesnt recognize sim card )
When i try attaching a usb cable i get Device is not recognized (checked drivers, cables so its software and it's the mobile)
The only communication with the device is via the SD Card.
Tried flashing a stock 4.4.4 via stock recovery. Nope! It says Update from external card is disabled.
I'm looking for a way to root , or flash anything.
Every thought, suggestion, idea is welcomed.
armandomulla said:
This is practically a cry for help after i searched for hours.
Model: Sm-n910P
Software version : Unknown
Android : 4.4.4
Baseband: Unknown
build: PVPU1ANK2
Stock recovery
(if anything else helps just ask)
Problem first: My note 4 has no network of any kind (wifi doesnt start , doesnt recognize sim card )
When i try attaching a usb cable i get Device is not recognized (checked drivers, cables so its software and it's the mobile)
The only communication with the device is via the SD Card.
Tried flashing a stock 4.4.4 via stock recovery. Nope! It says Update from external card is disabled.
I'm looking for a way to root , or flash anything.
Every thought, suggestion, idea is welcomed.
Click to expand...
Click to collapse
Never been OTA updated to lollipop OE1? That one doesn't allow downgrading to older versions.
Device not recognized with USB in what mode and operation? Security protocols for KitKat and Lollipop are restricted. Device should be recognized in custom recovery or download mode. Did you try Odin? Power down, download mode and flash the NK2 stock tar. If you're still having problems ##786#. Still having issues, try the NIE stock tar. Make sure you power down before flashing stock tars. Link to KitKat tars mentioned above; follow OP, post 1 for instructions.
http://forum.xda-developers.com/showthread.php?p=56853341
For root, you need CF Auto Root for Note 4. You can also try TWRP Manager for custom recovery. It's in Google Play. But you don't have to root to flash in Odin. Samsung KIES is alternate method for restoring factory firmware or updates but some are confused by the serial number request; not recognized. Haven't tried it myself.
Sent from my SM-N910P using Tapatalk
Tx for the reply.
Device is not recognized in neither mode (normal, download or recovery).
I tried ##786# but i dont know my msl and i cant find a wy to get it (im outside the US so the phone is not activated). I tried some "msl reader find my msl" programs but they cant get it. Any1 has some apk that may work in my case?
As for the flashing as I stated all I need is a way to flash stock but i cant get the PC to recognize the phone so im stuck.
EDIT 1 As far as I know never been updated (bought the phone in ebay)
I don't know if there's anything that can be done but get a refund. Sounds like you bought a brick. Was it always a brick?
Did you try another USB port? Try the rear port. If not, try a hard reset: wipe cache and dalvik and factory reset and try to reboot. Long shot would be a hard reset and OB7 update.zip; unless it's completely stock, the update will be rejected. But I'm thinking that can no longer just be placed on external sdcard. That may have to placed on the file system as if the phone downloaded it, itself.
It's safer to hard reset. If not rebooting to normal operation, time to pursue a refund.
Sent from my SM-N910P using Tapatalk
So I was thinking about the situation you're in. I recalled the phone can be unlocked to use internationally on 3G only. Is it unlocked? It would also
need to set your carrier APN/Access points to get data.
If you own the phone, Sprint will give you the MSL number. Sprint can help unlock it and there's also this method but I don't know much about about it. There's also the hard reset method that can be done within settings.
Here's a method that was requested with a pledged bounty. But try Sprint first.
http://forum.xda-developers.com/spr...print-samsung-unlocker-unlock-sprint-t2928250
My initial impression was phone is bricked but not sure if a locked phone's WiFi is bound to regional USA that would cause WiFi connection issues? It's still possible the USB issue is not using a USB 2.0 port or a bad cable. It may not be bricked. Try reinstalling driver and/or another PC.
Sent from my SM-N910P using Tapatalk
Well I tried everything u mentioned , full factory restore, wipe everything. I even tried update from external (since stock has no option for updating from the internal sd) but i get an error (update from external storage is disabled). The phone is practically a brick for the network part but I'm not sure I can return it back in the states as I'm in Europe. Any way i can root via some apk ?
armandomulla said:
Well I tried everything u mentioned , full factory restore, wipe everything. I even tried update from external (since stock has no option for updating from the internal sd) but i get an error (update from external storage is disabled). The phone is practically a brick for the network part but I'm not sure I can return it back in the states as I'm in Europe. Any way i can root via some apk ?
Click to expand...
Click to collapse
I didn't think the root is possible without Odin for either the custom recovery or root.
eBay return practice would be to notify seller of issue. If no response, contact eBay.
Sent from my SM-N910P using Tapatalk
armandomulla said:
Well I tried everything u mentioned , full factory restore, wipe everything. I even tried update from external (since stock has no option for updating from the internal sd) but i get an error (update from external storage is disabled). The phone is practically a brick for the network part but I'm not sure I can return it back in the states as I'm in Europe. Any way i can root via some apk ?
Click to expand...
Click to collapse
Wouldnt the entire phone be soft-bricked (not just the network part) if you did the factory reset and wiped your phone but cant get the cable to recognize your phone on your pc ???
Or is that your current situation?
Well everything but network works. I can install apk's from sdcard, open apps etc. Next thing is the screen just got black and is not giving signs of life (didn't do anything it was charging) so it's going in a repair shop. Thanks everyone for the efforts. Case may be considered closed.
armandomulla said:
Well everything but network works. I can install apk's from sdcard, open apps etc. Next thing is the screen just got black and is not giving signs of life (didn't do anything it was charging) so it's going in a repair shop. Thanks everyone for the efforts. Case may be considered closed.
Click to expand...
Click to collapse
Well, good luck. Hope it works out for you.
As an after thought, have you tried connecting another Samsung phone to the computer?
jhill110 said:
Well, good luck. Hope it works out for you.
As an after thought, have you tried connecting another Samsung phone to the computer?
Click to expand...
Click to collapse
Thanks and yes my other Note 4 connects just fine

Getting DM + Modem + ADB working 5.1.1 ok1

I've successfully unlocked my Note 4 and I'm trying to get it to work with AT&T LTE, now I am following this guide here
http://forum.xda-developers.com/note-4/general/enabling-additional-lte-bands-att-t-t3160864
and I have looked everywhere to try to figure out how to get DM to work on Lollipop with the sm-n910p. A lot of places say to go into recovery and select DM Logging, but that option is not there when I go into the stock recovery for OK1. Does anyone know how to get here?
Thanks!
@ssjgoku24
I'm unlocked also, and use att. And i have tried similar guides here: http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059
And
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
But i couldn't get it to stick. I don't know if it'll work on our device.
Before i continue I must state this is very dangerous and can hardbrick your device. I almost did myself. You have been warned!
Anyhow, use galaxy tools or idone unlock app to access hidden menu, then select 'phone util' and 'usb settings' from there. I've attached pics.
If you attempt, and get it to work please let me know. But like I already stated, this is very risky. Good luck and hope this helps.
Thanks for the info. I did already try doing that, but my computer never recognized the DM. So i was not able to use software. I'll try some more things once i get a chance, and I'll be sure to post results if in successful or not and what i did.
ssjgoku24 said:
Thanks for the info. I did already try doing that, but my computer never recognized the DM. So i was not able to use software. I'll try some more things once i get a chance, and I'll be sure to post results if in successful or not and what i did.
Click to expand...
Click to collapse
Oh. I just remembered, when i tried this(it was a while ago) i used Efs Pro to switch to the right usb setting. Cause if you read all of the guide i used. It states that official roms block us from changing this. I do believe i was using Cm12 on my phone. Then used efs pro to switch phone usb to diagnosis mode (or whatever it is).
Here's link http://forum.xda-developers.com/gal...ol-updated-09-06-14-efs-professional-t1308546
So i was on vacation and finally got around to trying some things out. First using EFS Pro i was able to get my phone to show up as a samsung communication port in device manager. I am not sure if that is correct since in QPST it didn't show up as a diag port, i had to manually add it as COM4 (5 was also there and tested). I was able to see my phone but when i did a software download, it said the system was busy and if i hit "switch to" it would open the start menu, then pop backup. Doing this 3 times would then atart the download. Once the download hit 12% it would error out stating like "could not communicate in diag mode." This leads me to believe the phone is not actually getting set to diag mode. I have also tried to read the phone with another tool in QPST, but it always fails to read.
I tried double checking the settings using *#0808# and making sure dm + modem + adb was activated which it was. I also tried RDNIS + DM + Modem which resulted in the COM port changing to 8 & 9 but gave the same results.
When you tried QPST did you recieve these errors?
Note - I used the stock rooted ok1 rom , firmware, and baseband. I tried pd1 stock rooted rom, firmware, and baseband as well.
I was also using this in a windows 10 vm and tried on a windows 7 vm, since I have a Mac running osx.
ssjgoku24 said:
I've successfully unlocked my Note 4 and I'm trying to get it to work with AT&T LTE, now I am following this guide here
http://forum.xda-developers.com/note-4/general/enabling-additional-lte-bands-att-t-t3160864
and I have looked everywhere to try to figure out how to get DM to work on Lollipop with the sm-n910p. A lot of places say to go into recovery and select DM Logging, but that option is not there when I go into the stock recovery for OK1. Does anyone know how to get here?
Thanks!
Click to expand...
Click to collapse
How did you get it unlocked? I'm having trouble with sprint and wont unlock note 4 its payed off no longer with sprint would like to use it.

Categories

Resources