[T-Mobile Samsung Galaxy Note II] garbageslot:
Sixth Method. Addendum

NOTE: Please also refer to "Sixth Method" post #15 located earlier in this thread. Both posts are critical to understanding the complete solution.

Prior to attempting to read and write to the device, place the device in the proper ADB mode.

1. Disconnect USB cable from phone.

2. Go to Menu->Settings->Developer options.

3. Turn on "USB Debugging" option.

4. When prompt appears press "Yes".

5. Go to dial window.

6. Enter "*#7284#" number.

7. Set "UART" radio button to "PDA" value.

8. Set "USB" radio button to "PDA" value.

9. Go to "Qualcomm USB Settings".

10. Select "DM+MODEM+ADB".

11. Press Home button.

12. Go to dial window.

13. Enter "*#9090#" number.

14. Select "DM/UM over HS-USB".

15. Restart phone.

Now, attempt to write to the device using nv_reader_writer tool.

Did this resolve the problem?

What does your IMEI state currently?

1. Go to dial window.

2. Enter "*#06#" number.

~~

Alternative software?

Again, I was quite detailed about the software that I employed in the past within this thread; however, if I must decide, I would go with the EFS Professional software. The link to the latest version is here. Use the Qualcomm NV Tools.

http://xdaforums.com/galaxy-s2/orig-development/tool-updated-09-06-14-efs-professional-t1308546

~~

In my case, I am also currently using android version 4.3 on my SGH-T889 device. LIKE YOU, I am getting the exact same communication error for the NV_items_reader_writer software stating "Failed..Phone does not answer" and the EFS Professional Qualcomm NV Tools disconnects abruptly.

Since I originally performed the Sixth Method solution, what has changed?

Firstly, the Samsung drivers that I was originally using have definitely been updated. Since "NV-items reader_writer v1.0" software has not come out with a newer version, the current drivers and the older software might not be communicating correctly. However, the EFS Professional is up-to-date. So, if drivers were really the culprit, the EFS Professional would function. However, in fact, this scenario is not the case. The real reason: my guess is that the later OS releases have new security measures preventing the successful interface between these 'home brew' software solutions and the device.

Secondly, I have upgraded my device to 4.3 android version. My original successful write was NOT at 4.1.2 but further downgraded by the Craigslist guy. I am not certain exactly what version and build to which he downgraded. I would begin by trying the following:

Build: T889UVALJ1. Version 4.1.1

You can find three build variations of the 4.1.1 stock ROM at the following link:

http://xdaforums.com/showthread.php?t=2102380

This difference in build and android version could be the reason for our communication error, owing again to these presumed added security-measures in the later releases.

GAMEPLAN

You should downgrade and retrace the steps that I originally performed when I had a successful read/write-- if anything, just to narrow the myriad of troubleshooting possibilities. In fact, for some reason, the older versions of the android OS provided access to parts of the service menu like unlocking-phone functions that the new versions now prevent. The best indicator that you are on the right path if the device displays a NULL IMEI, which is an excellent sign that your device is ready finally to be written (I elaborate below).

UPDATE

Everything that is included in the Sixth Method and the Six Method Addendum are true. In spite of everything, some users, like myself included, were not able to write to the device. However, I now think that I have finally reconciled what the Craigslist guy exactly performed, which does not require "the box" to which I repeatedly alluded.

If after everything your device still will not write using a text-based method with software like "NV-items reader_writer v1.0" or "Qualcomm NV Tools," you should perform an update using the EFS Professional software. Specifically, click on the Restore Tab and restore a backup archive. This action employs a binary file. This procedure will most likely recreate the event that the Craigslist guy performed on my device. Here is the catch: get this backup binary-file from a working SGH T889 device. How? Using the Backup Tab of the EFS Professional software, you can create this binary file. After this restore procedure, you will finally be at a point, at the very least, where I was when after the Craigslist guy failed to write to my device. The successful solution is definitely not linear, but you now have all the information to construct a winning procedure by employing these Six-Method and the Six-Method-Addendum elements. Good luck!

PROLOGUE

After everything, the folks who advertise on the likes of Craigslist and Ebay offering specialized services to repair a corrupt IMEI are misleading. In my search for a solution, I was told that my device had embedded security-chips that prevented me from performing the write, which was untrue. Moreover, other people claimed to have an external box that interfaced in such a way to perform this write, which was also untrue in part. Meanwhile I wondered why some people offered this write-service remotely, while others demanded that I send them my device. Everything appeared suspect!

In the end, I realized that the Craigslist guy made a simple binary-restore to my device, replacing the EFS partition, which contains the NV Backup and IMEI information. When he performed this one-partition restore, this action 'confused' my device lending an IMEI of "0/00" or "0/0," which was a good indicator that the device could finally now be written. Coupled then with a full text-based NV Backup restore, the device was updated in a stable state providing complete functionality.

Ultimately, these would-be techies are opportunists who don't really understand what is going on within the device. Personally, I wouldn't even go so far as to give them the moniker of 'hackers'; because anyone can fix their device by following a simple step-by-step recipe i.e. monkey see, monkey do.