yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Q&A, Help & Troubleshooting] ilegales:
i am on my main pc right now

i have downloaded the SDK manager and installed the Android SDK platform tools and Google USB driver

nothing happens when i plug the nexus into the PC

do i need to actually manually install these drivers or they are already installed when i ran the SDK manager...

the nexus shows as unknown device right now
[Nexus 7 Q&A, Help & Troubleshooting] Lar5:
Try to install WugFresh's toolkit. http://www.wugfresh.com/

Follow the driver installation guide and make sure thet the previous drivers is removed.

Choose the recomended driver.

If you can start your device in fastboot mode (bootloader) it should be salvageable.

If you use Windows 8, getting a working driver can be quite a struggle.
[Nexus 7 Q&A, Help & Troubleshooting] ilegales:
it was wugfresh toolkit that i was using

so i uninstalled all drivers and installed the drivers from his toolkit

sadly the usb device is still not recognised
[Nexus 7 Q&A, Help & Troubleshooting] minhpro9xhp:
well, i searched google and they said there was one way to fix hard brick nexus 7. It is using "JIG usb". If somebody used "JIG usb" please reply me.
[Nexus 7 Q&A, Help & Troubleshooting] BernardWibbles:
I think I'm having the same problem as you, but I am still able to get into bootloader mode. It may take up to around 20 seconds holding the volume down and power button to get back into bootloader mode. In fastboot bootloader, going into recovery freezes (freezes on the "Teamwin" screen), "start" freezes on the "Google" screen with padlock unlocked. Used Wug's to try to go back to factory setting (but to 4.3 instead of 4.2.2), failed to write 'bootloader' and device never boots back up when it says "waiting for device". Then tried using Nexus 7 toolkit (not Wug's) to lock it back up and now I can't unlock again...same thing..."waiting for device" and device never boots back up.
[Nexus 7 Q&A, Help & Troubleshooting] kabivn:
any update for this problem?

any update for this problem?

i try alot of solution but nothing change

i saw N7 can connect to APX with correct Driver however we can do anything

i try connect power about 8 h but nothing change

:( what the F *K with OTA update ........
[Upgrading, Modifying and Unlocking] ramnkc:
Hi,

Does anyone know how to disable rom version to display during device start up? It always showed at the splash screen each time i soft reset my device.

And btw, is there anyway to enable sound during boot up as well?

Coz i do recall when the first time i start the device i did here a sound... but now no more..

pls help !
[T-Mobile Samsung Galaxy Note II] erica_renee:
when you first bought the phone and put in your t-mobile S I M card in it..

what happened .

are you sure its not a blocked imei phone.

this seems to be going around...

are you trying to use it on t- mobile ..

please post the original issue not just want you done to try and fix it..
[T-Mobile Samsung Galaxy Note II] garbageslot:
Thank you for the reply.

This problem stinks.

I don't have a tmobile sim card. The phone is for Tmobile and I hope to use the phone on T-mobile's MVNO (mobile network virtual operator) SimpleMobile, a carrier that piggybacks on the Tmobile carrier. I have Simplemobile SIM card, which the device does not recognize. The network in the "About Phone" in Settings is listed as Unknown. I think that the phone is locked, but I thought that this issue is exclusive of my present dilemma.

So, what is preventing me from writing an update to the device? There are a couple of good Qulalcomm

tools on the market like DFS CDMA ver. 4.7.0.2 and Qualcomm NV Tools, but both of which

fail to restore the IMEI. Is this a CDMA vs GSM tool interface issue?

Where is the IMEI stored on the device? My efs/imei folder only has one file: "mps_code.dat"

(I guess NV_DATA.BIN file is not present for LTE users.)

Thanks again, in any case.:confused:
[T-Mobile Samsung Galaxy Note II] Darkshado:
If I were you, I'd try writing the T889 NV backup from the AWS mod thread with QPST or QXDM. Then finish off with the IMEI using EFS Professional.

As you've noticed, no NV_DATA.BIN for our devices. The /efs partition isn't enough of a backup to fix things.

Information applicable to the N7100 is going to be useless here since it has an Intel baseband, as opposed to the LTE variants which run on a Qualcomm chip.
[T-Mobile Samsung Galaxy Note II] garbageslot:
Thank you Dark Shado[w].

Fifth Method:

I used QPST configuration to establish a serial connection. Using one of the software's client applications called

QPST Software Download, I made a backup of NV Memory Files and then used a hex editor

to locate the IMEI number (offset 00001700 --fyi) and made the repair. However, when I attempted to restore the

file using QPST Software Download, the software failed to update the device. Take note that the software indicated the memory restore worked. However, again, I'm not sure what is preventing me from writing to the device.

Every editor or tool that I have used to interface with the device successfully reads the device but does not write.

In the Qualcomm USB Settings, I have chosen either "RNDIS + DM + Modem" or "DM + MODEM + ADB" settings.

I also try to make sure that "USB Debugging" is checked in "Developer options" in Settings. (This

setting appears to toggle depending on which USB serial setting is chosen.)

I began messing around again with EFS Professional. The problem with this approach is that the backup file is stored in the form of an image file. Unfortunately, I can't edit the image to repair the IMEI with a hex editor.

Previously the backup file was in the form of a bin or text format making the process of editing easy.

I also confirmed indeed that the address location of the efs folder including the IMEI is recorded in /dev/block/mmcblk0p3 for Galaxy Note II LTE variants.

Any other ideas? Is there any other toolkits that might be easier to work with?
[T-Mobile Samsung Galaxy Note II] G7Baker:
Hey since you already odin 4.1.1 go ahead and unlock your phone using the free unlock method. Than try using your simple mobile sim again.
[T-Mobile Samsung Galaxy Note II] garbageslot:
Hi G7Baker. Thank you for the reply.

I was not able to unlock the device using the *#197328640# approach.

The device is missing the "Press [4] NW LOCK NV DATA INITIALLIZ"

I read elsewhere that I needed to downgrade the device to 4.1.1 and this option

would reappear in the menu settings. Specifically, if I downgraded the modem from

4.1.2 to 4.1.1, this option would again appear. In my case, the option is still missing.

I figured that I would just focus on my corrupt IMEI before addressing the locking issue...but if you any ideas,

i am open. :eek:
[T-Mobile Samsung Galaxy Note II] Darkshado:
I'll be blunt: you haven't listened to anything I've said.

Use the .qcn file from the AWS mod thread. Not yours hex-edited to contain your IMEI. You NV items are already messed up.

Toggling USB Debugging might undo the "RNDIS + DM + Modem" setting.

Use EFS Professional to

type in

(not copy-paste, it's a quirk in the UI) your IMEI, then write it. Make sure you've got the latest version, and that you're using the Qualcomm tools. Or hex-edit the file from the AWS mod thread since you're capable of doing so.

Ditch this "toolkit" mindset and get their actual components, latest versions, straight from the devs. You'll be able to check for issues in their respective threads as well.

Good luck,

Darkshado
[T-Mobile Samsung Galaxy Note II] garbageslot:
Thank you Darkshado[w] for the advise.

Game plan

qcn generic file (binary format) --> modify imei in qcn generic file --> EFS Professional-Qualcomm (fourth tab) to apply Restore

Darkshado[w], I'm looking at the EFS Professional -- Qualcomm tab (fourth tab). Just to be clear, this tab has a

"Qualcomm NV Tools" button, to which I don't proceed. This tab has also a set of "NV Backup" and "NV Restore" functions. These functions are supported for US variants only. (The T-mobile T889 has a Qualcomm chipset Gobi MDM9215, making the device eligible, right? or I guess these tools are meant only for Sprint and Verizon variants only) These tools, I believe, are where you would like me to use to make my restoration possible.

Just to be clear, this Restore/Backup receives a binary file, opposed to "Qualcomm NV Tools" that receive a text file.

However, when I click on "NV Backup" or "NV Restore," the phone immediately reboots.

On the same page the following disclaimer is written "If these functions are not supported your phone will just reboot." My device rebooted and I can't use this approach for the moment.

---

I was searching the AWS thread to which you alluded.

On December 28, 2012, I saw that you posted a full NV backup, IMEI removed, at the following thread:

http://50.23.216.69/showthread.php?t=2068041&page=2

I downloaded your attachment and modified the TEXT file to include my repaired IMEI for the T889 and then used

EFS Profressional via "Qualcomm NV Tools" to restore to my device.

I made sure that the device was set for a USB serial connection,

since "Qualcomm NV Tools" would not make the SPC connection otherwise.

The restore procedure completed without any errors, but the device was not successfully written to...again.

---

I also downloaded the ATT_I317_AWSMOD_dumimei.qcn file from the thread. Using QPST via their client application "Software Download" I attempted to make the restoration.

I attempted the restoration twice using "RNDIS + DM + Modem" and "DM + Modem + ADB" settings. In the phone utility menu, UART was always set to "PDA" and USB was set to "PDA" as well. In both cases, the device was not written. The software indicated that the restoration was successful when in fact this case was untrue.

--

On the EFS Professional version2.0.062, I was able to generate backup files using the backup option located on the second tab.

For this backup option, I selected "International LTE Variants" for the "Device Filter." The software

generated one tar.gz file; however, when extracted, a efs.img file and four other bin files are revealed. Unfortunately, the image file of efs contains my corrupted IMEI, which I'm not sure how to edit. I tried to use Hex Workshop Hex Editor to edit the file but can't find the IMEI in this type of file. Alternatively,

is there a generic backup tar.gz of SGH-T889 that I can try to restore?

--

What are your thoughts? Please advise.
[T-Mobile Samsung Galaxy Note II] garbageslot:
I later downgraded the firmware from T889UVALK8 to T889UVALJ1 of 4.1.1. The NW LOCK NV DATA INITIALLIZ

finally appeared and was able to unlock the device successfully. Awesome!

However, I'm still trying to figure why my NV Memory Block refuses to be written. Please share your input!
[T-Mobile Samsung Galaxy Note II] garbageslot:
No solution ... yet.

I tried deleting the efs folder and then I went back through all the methods that I have discussed

really to determine if and when the device was being written. Trying to restore the efs folder from a backup

copy, my findings seem conclusive.

I found that the ONLY solution that replaced my efs folders was EFS Professional--Restore (third tab).

In my case, I'm just restoring my corrupt NV memory backup back onto the device, but this approach can

work for me. In all other methods that I employed, the device and software indicated that a successful update was

made but these cases are untrue; the device is not updated.

Where does this leave me? If I am going to flash my device using this restore feature of EFS Professional(third tab),

I need to flash a modified efs.img that is corrected for my corrupted imei.

Does anyone have a solution out there for the SGH-T889?
[T-Mobile Samsung Galaxy Note II] garbageslot:
I learned today that someone claimed that this SGH-T889 device has a hardware security measure in place. The device has a chip that has the IMEI that is write/no-rewrite (eMMC?); therefore, successful service combines both a hardware and software approach. My "deep throat" operative also said that the IMEI for this particular device appears in five different places within the NV Memory block, making the repair not so trivial.

Can anyone confirm this statement? I can't find anywhere where this statement is validated.
[T-Mobile Samsung Galaxy Note II] rail205:
I would have to call bulls..t on that, I lost my imei flashing a tmobile modem to get lte and was able to rewrite my imei and get it working. Took me 2 days and lots of messing around but finally worked.

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

You can try this link has some valuable info and links.
[T-Mobile Samsung Galaxy Note II] garbageslot:
Thank you Rail205 for your reply. Reviewing the thread that you sent,

I'm still not sure how I should proceed.

I was comparing my device allocation using the df command on the android emulation terminal .

# df

My partition allocations are consistent with jravi and darkshado[w] on the first page of the thread,

so I'm wary if I flash with an updated PIT file that this approach will make a difference.

My device is reading the correct internal storage for example.

To reiterate, if the block allocations are the same, can I assume that using a new T889V pit file

on my device the T889 will make no difference?

Currently, my device is now unlocked, rooted with a 4.1.2 OS.

The device has radio service.

Unlike everyone else who has been successful e.g. Darkshado[w] who has successfully

written an editable hex file or text file (depending on the method employed), my

device remains unmodified when performing approaches of this kind.

The only method that appears to work for me is flashing an image file

using EFS Professional (third tab).

This dilemma is the chicken / egg conundrum, how do I flash the device with the corrected img file

when I don't have a copy of an img file with the corrected imei with which to flash? Otherwise, considering

a no-img file approach, I could try to make the partitions writable (fyi I have used Root Explorer already to modify

the permissions of /dev/block, /efs and /factory before attempting an update -- you guessed it, no luck.)

Anyone, any thoughts? Anyone?:(
[T-Mobile Samsung Galaxy Note II] Jerry D:
I'm glad you fixed it man!..you went through Hell fixing your phone.

I ALWAYS read and follow these "bad IMEI" threads to learn something "just in case" and I must say that your case it's the most complex (for me anyways) I've ever read.

Cheers to you!
[T-Mobile Samsung Galaxy Note II] walydiesel:
New link to file please

Hello! I'm facing the same issue with my T889, could you please re-post the file from darkshadow's post?

Thank you!
[T-Mobile Samsung Galaxy Note II] garbageslot:
NV Backup Blank-IMEI Template File

Thank you WalyDiesel for the follow up.

The administrators of this site appear to have made the original link outdated since I started this thread..

Please internally message me your email and I will send you the NV Backup Blank-IMEI template file.

(The file exceeded the attachment limits for this thread.)

You still need to edit decimal address 00550

to your specific IMEI number. Upon doing so,

write the entire file to your T889 device.

Good luck! -- You are in the home stretch. :)
[T-Mobile Samsung Galaxy Note II] walydiesel:
Ok! I sent you my email inbox.

Thank you!
[T-Mobile Samsung Galaxy Note II] walydiesel:
I'm back!

Unfortunately, the past two days I tried, But I can't write back the file to phone using nv_reader_writer tool. I can't even read from phone. It keeps saying "Failed, phone does not answer". :confused:

I read on a thread that it could be because my chip is not Qualcomm. In fact my chip is Exynos. Is it the problem? :confused: Is there another tool that I could use? Thank you. :) :D

P.S: I'm running stock android 4.3. I also tried stock 4.1.2. Same result :( and Service mode just leads me to a black screen with Serviceode written on top.
[T-Mobile Samsung Galaxy Note II] baabafadil:
Changed IMEI with unstable network

Hello Garbageslot. Thnx 4 d post. Mine is GNII SGH-T889, OS 4.3, Base Band T889UVUCMK7. My IMEI is different from the original. I tried clean flashing stock rom, flashed the modem. The network now appears but its very unstable as its on & off most of the time. Could it be because the imei is still different, so how do i solve that?
[T-Mobile Samsung Galaxy Note II] garbageslot:
You appear to be in good shape because you have successfully been able to write to your device. With this said, you just need to update the NV Build. Upon doing so, you should be able to resolve these spotty network issues. Send me your email (private message) and I am happy to send you the generic-template file in reply. You just need to modify the file with your IMEI and then proceed with the update. Thanks!
[T-Mobile Samsung Galaxy Note II] Gladhatter:
Sure would you be so kind to send me the file also? I am trying to learn something about IMEI and related issues and how it all works. gladhatterhatcompany@gmail com . I thank you in advance.
[T-Mobile Samsung Galaxy Note II] baabafadil:
How do i update that NV Build?

Hullo. I sent u my email but u forgot 2 send me the file, am still stuck. How do i update that NV Build?
[T-Mobile Samsung Galaxy Note II] garbageslot:
My apologies.

I will send the file now.

Thanks.
[T-Mobile Samsung Galaxy Note II] baabafadil:
Puzzled...!!!

i have failed to trace d exact imei 4 my fon which is cozing its network 2b very unstable..... Imei.info web shows the imei number indicated by my dialer is for ITEL fon, then the one [MENTION=600147]THE[/MENTION] fon sticker is for a Galaxy Note 2 N7100. So where is the correct one 4 my fon coz both r incorrect..... what do u suggest.........?
[T-Mobile Samsung Galaxy Note II] garbageslot:
The general methodology presented in Post #15 and Post #21 will work for your phone.

However, you need to translate the steps for a CDMA phone.

My understanding is that iTel piggybacks on the Sprint Network.

Start by trying to find firmware by the carrier to downgrade the phone

to make the necessary changes. In general: downgrade, modify and upgrade.

Again, search the forum for your phone using the Sprint carrier and the right firmware to start.

I should emphasize that my success was possible because I exploited a weakness in the 4.1.1 firmware. I did not utilize any hacking software per se. Goodluck.
[T-Mobile Samsung Galaxy Note II] Gladhatter:
Do you feel like you would not have been successful with 5.xx firm?
[T-Mobile Samsung Galaxy Note II] garbageslot:
Honestly, the scope of my expertise was finding one working solution.

I do not know if higher versions of the firmware would be successful.

However, my gut would say no, at least employing this exact methodology.
[T-Mobile Samsung Galaxy Note II] baabafadil:
Can't 4get those times with my Note 2 network issue, I appreciated a lot from Garbageslot as he helped me write back my imei thou it wasnt an easy task.

Still that year after I repaired the imei & network was still sporty, I took it to a Samsung technician who ended up completely damaging the screen, up to now I have it kept coz of the expensive screen.....ooooops

Anyway after some time I got a Note 3 Sm-n900v which am loving up to now with Lineage 14.1 (Nougat) at the moment.
[Galaxy Tab 2 General] tonyking:
Hello Everyone

We got Something New Here

Model: GT-P3100

Country: France

Version: Android 4.2.2

Changelist: 1198223

Build date: Mon, 29 Jul 2013 02:17:49 +0000

Product Code: XEF

PDA: P3100XXDMG6

CSC: P3100OXADMG6

MODEM: P3100XXDMF2

:laugh: :D

Waiting For Dev To Take Action on it :highfive:

Download It from here - http://www.hotfile.com/dl/237237887/c372f0b/P3100XXDMG6_P3100OXADMG6_XEF.zip.html
[Galaxy Tab 2 General] Narciso Neto:
What's new?
[Galaxy Tab 2 General] Dhiraj:
Is it flashable through Odin ?
[Galaxy Tab 2 General] tonyking:
yes it is but i will suggest you to wait some dev are deodexding and rooting it we will have a flashable zip :good:
[Galaxy Tab 2 General] tonyking:
well actually dont no yet but might be a good feature we gona have wait other dev to deodexed and rooted it then it will be clear to us :D
[Galaxy Tab 2 General] DarkStryder:
Can i flash hotfile on my p3110?

sent from galaxy tab 2 running android 4.3.0
[Galaxy Tab 2 General] tonyking:
No i will suggest you not to flash through odin it might be risky just wait for devs and let them to introduce us with deodexed and rooted rom they can give better option to flash or not to flash on your device or might be with phone remover :o
[Galaxy Tab 2 General] DarkStryder:
Yeah i thought as much. Maybe it mess with bootloader and stuff thats bad

sent from galaxy tab 2 running android 4.3.0
[Galaxy Tab 2 General] tonyking:
Yes boatloader can mess at this time or might be new partition or pit file can kill your device as i heard that new firmware with odin has pit repartition files also so better wait for a while :rolleyes:
[Galaxy Tab 2 General] DarkStryder:
Yes, if there are new pit files it could mess my tab up nicely:D:D repartition? Maybe we can finally move apps 2 sd :p:D:p:D:eek::eek::eek:

sent from galaxy tab 2 running android 4.3.0
[Galaxy Tab 2 General] DarkStryder:
Here are the changes! That are new in 4.2.2
[Galaxy Tab 2 General] Looklearner:
Good news to see galaxy tab 2 7 with much awaited update JB 4.2.2 :D

Its a huge step to leap ahead all custom roms will take all awesomeness from it as base in the next time :D

We're lucky & glad for 4.2.2
[Galaxy Tab 2 General] Looklearner:
I flash this Official JB 4.2.2 on my p3100 with odin but after reboot it stucks at boot any help to make it open desktop

---------- Post added at 09:38 PM ---------- Previous post was at 09:31 PM ----------

Pls help me can i downgrade back to JB 4.1.2 now with odin ?
[Galaxy Tab 2 General] DarkStryder:
Yes u can

sent from galaxy tab 2 running android 4.3.0
[Galaxy Tab 2 General] Narciso Neto:
Sammobile says that people outside France MAY have to wipe data to make ROM boot up... :)
[Galaxy Tab 2 General] Looklearner:
after flashing with odin i set off my gtab2 then i reboot in recovery

i wipe factory data / reset

i wipe partition cache

i reboot sys then i can open to desktop of JB 4.2.2 :laugh:
[Galaxy Tab 2 General] tonyt3rry:
im just waiting for it to hit the uk save all the messing about
[Galaxy Tab 2 General] tonyking:
Not even a single thanks for this thread :(

come on guys :rolleyes:
[Galaxy Tab 2 General] Looklearner:
Yes bro keep waiting, i hope Samsung will out the updates far sooner for uk & worldwide :)
[Galaxy Tab 2 General] Dhiraj:
After many discussion ,I have decided to flash original firmware ,this one. Thanks to info provider. I was in stock 4.1.2 without root or custom cwm . For backup I used philz cwm . I hard from different thread that data,cache clean are required after flash through Odin . But although I am from outside France ,but I succefully booted after flash . No cache partition clean or factory reset . Nice ROM .Thanks to all who helped me .

Sent from my GT-P3100
[Galaxy Tab 2 General] ketut.kumajaya:
Dirty flash over stock 4.1.2 without data lost :victory: Even the water ripple lock screen still exists but AdAway app gone :confused:
[Galaxy Tab 2 General] tonyking:
Gr8 but after that did u tried full wipe and ripple lock screen exist after wipe and one more thing did you have status bar transparent in lock screen after dirty flash :confused:
[Galaxy Tab 2 General] T3ER:
But how about perfomance? Has it got better or is it better than those cm and other custom 4.2.2 roms? Cm and others are too laggy for me. On 4.1.2 no lag and on cm too much lag on gaming.
[Galaxy Tab 2 General] Dhiraj:
If you need performance improvement , then wait for custom karnel support for it.

send from GT P3100/ Android 4.2.2
[Galaxy Tab 2 General] tonyt3rry:
Any news on UK rom
[Galaxy Tab 2 General] babujnik:
i found that "blackhawk's NEXT kernel 1.8" is supporting stock 4.2.2 but havent tested yet:

http://xdaforums.com/showthread.php?t=2285366
[Galaxy Tab 2 General] Dhiraj:
It has sound problem.

send from GT P3100/ Android 4.2.2
[Galaxy Tab 2 General] tonyking:
i m using stock 4.2.2 kernel modded by [MENTION=1434892]ketut[/MENTION] with Overclock Support and now my tab is working fast and smooth :D