Develop Bugs

[HOW TO] Restore your lost IMEI

If your IMEI is corrupted and/or shows 0s this could help you fix it. By using these steps you will not be able to change your IMEI to a different one than your original.
1.You need to be on stock ROM
2.Phone has to be rooted
3.Dial *#7284# on phone's keypad
4.Click Qualcomm USB Settings
5.Select RMNET + DM + MODEM and click ok
6.Download QPST and install it QPST
7.Connect T999 to Windows PC with USB cable (make sure you have all Samsung drivers installed and working)
8. In Windows open Device Manager, go to Ports (COM&LPT) and look up what port your T999 is using
9.Open QPST Configuration program
10.Click Add new port
11. Enter port (for example "COM6") from step 8 to boxes "Port" and "Port Label"
12.Open QPST RF NV Item Manager program
13.From top menu click on Settings then Comport
14. In Comport Configuration window click on drop down menu and select your port from Step 8 then click OK
15. In RF NV Item Manager click on Read Supported NV RF Items (first toolbar button or select it from File menu on the top)
16. Below on left side go to line number 550 and click on it
17. On the right side, check box "Hex" this will display 9 boxes below where you enter your IMEI
18. You enter it in pairs of 2 digits and backwards
Example:
your IMEI is 353024052511214
8 (this number is not part of your IMEI but has to be entered)
3a (first digit of your IMEI ,"a" has to be there also)
35
20
04 (this can be written as just 4 also)
25
15
21
41
19. Click Write NV button
20.You can reboot and disconnect your phone now.
21. On your phone's keypad dial *#7284# go to settings and check MTP + ADB to go back to original state.
Source of info above

[Q] No Wifi broadcasting when in Hotspot mode

I'm having an interesting issue with my AT&T Galaxy Nexus.
At some point, most likely after an update, Wifi tethering stopped working. Because this is a feature I use irregularly, I cannot say for certain when it stopped working. I'm currently using 4.2, but the error persisted into 4.2.1. I know that tethering was working in the past, perhaps in 4.1 or 4.1.2.
The symptom is that when I activate the tethering hotstop, the phone does not turn on the wifi radio (specifically in AP mode). There is no indication of problems on the handset, all of the icons are correct for being in hotspot more, no error message are given. However no other device such as my laptop, Nexus 7, daughters iPod, etc, etc, shows an available wifi network. Tethering and IP forwarding are working because I can correct to the Galaxy Nexus's bluetooth for internet sharing. The problem seems confined to just the Wifi radio.
I did some digging into the logs and discovered the following:
E/hostapd ( 6484): Configuration file: /data/misc/wifi/hostapd.conf
E/hostapd ( 6484): HT (IEEE 802.11n) in 11b mode is not allowed, disabling HT capabilites
I/hostapd ( 6484): rfkill: Cannot open RFKILL control device
E/hostapd ( 6484): nl80211: Failed to set interface wlan0 into AP mode
as well as:
E/hostapd ( 6484): nl80211 driver initialization failed.
All of the log entries for Tethering and TetherController seem correct when I turn off and on the hotspot service.
My /data/misc/wifi/hostapd.conf is pretty basic and has not been hand modified:
interface=wlan0
driver=nl80211
ctrl_interface=/data/misc/wifi/hostapd
ssid=tcgmobile
channel=6
ieee80211n=1
(i have the network open for now during my testing)
The WIFI works fine in normal client mode.
Can anyone shed any light on this? Perhaps there is a driver bug in 4.2?
My next move will be to start wiping and flashing various older ROM versions to try and diagnose this further if no one has any suggestions.
Thanks

mckinleytabor said:
I'm having an interesting issue with my AT&T Galaxy Nexus.
At some point, most likely after an update, Wifi tethering stopped working. Because this is a feature I use irregularly, I cannot say for certain when it stopped working. I'm currently using 4.2, but the error persisted into 4.2.1. I know that tethering was working in the past, perhaps in 4.1 or 4.1.2.
Click to expand...
Click to collapse
I can confirm the issue, seeing the very same behaviour my Nexus S with 4.2.1. It worked with 4.1.1, not sure with 4.1.2
DMESG shows this when trying to enable thetering:
<4>[ 4001.586766] wl_android_wifi_off in
<6>[ 4001.587047] wake disabled for irq 164
<4>[ 4001.587205] wifi_set_power = 0
<4>[ 4001.587275] =========== WLAN placed in RESET ========
<4>[ 4001.601863] dhd_prot_ioctl : bus is down. we have nothing to do
<3>[ 4001.601970] CFG80211-ERROR) wl_cfg80211_change_virtual_iface : WLC_SET_INFRA error (-1)
<4>[ 4001.602190] dhd_prot_ioctl : bus is down. we have nothing to do
<3>[ 4001.602345] CFG80211-ERROR) wl_cfg80211_change_virtual_iface : WLC_SET_INFRA error (-1)
<4>[ 4001.602515]
<4>[ 4001.602518] Dongle Host Driver, version 5.90.195.75
<4>[ 4001.602522] Compiled in drivers/net/wireless/bcmdhd on Sep 10 2012 at 14:10:03
<4>[ 4001.602758] wl_android_wifi_on in
<4>[ 4001.602889] wifi_set_power = 1
<4>[ 4001.808894] =========== WLAN going back to live ========
<4>[ 4001.809548] sdio_reset_comm():
<4>[ 4001.827717] F1 signature read @0x18000000=0x9934329
<4>[ 4001.829946] DHD: dongle ram size is set to 294912(orig 294912)
<4>[ 4001.874294] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
<6>[ 4001.927125] wake enabled for irq 164
<4>[ 4001.928275] wifi_get_mac_addr
<4>[ 4001.931207] Firmware up: op_mode=2, Broadcom Dongle Host Driver mac=02:1a:11:f6:58:92
<3>[ 4001.937722] CFGP2P-ERROR) wl_cfgp2p_supported : wl p2p error -23

the default wireless tether is working fine here, but third party tether apps do not work until updated for 4.2.X. are you using the default wireless tether with security? try leaving the network open.

Fixed... In a mannor of speaking.
Being somewhat inpatient I went ahead and started experimenting with reflashing ROMs on my device. I didn't actually get very far because it worked on my first attempt.
I did a complete factory reset and reflashed the ROM I had on the device to start with. The ROM is located here: http://forum.xda-developers.com/showthread.php?t=1737849
It would seem that the factory reset did the trick. I went back and confirmed the log files and config files on the new flashing and they are essentially identical to the old flashing. Ergo whatever was preventing the driver from loading was not related to my previous post.
I did have to spend a fun 90 minutes reinstalling all of my software and restoring a manual backup of the SD card data but that needs to be done periodically anyways to clear all the stuff I don't use. So all's well that ends well.

simms22 said:
the default wireless tether is working fine here, but third party tether apps do not work until updated for 4.2.X. are you using the default wireless tether with security? try leaving the network open.
Click to expand...
Click to collapse
I tried the default wireless tethering with various options including secure, open, and different permutations of the network SSID.

Request - Is someone willing to share an anonymized QCN/NV partition backup? (Brick)

EDIT: Already got help from someone here. Thanks! "Case is closed now".
Hello everyone,
unfortunately I bricked my Find 7a while trying to expand the 3GB internal storage with Chinese partition layout. And I don't know where it went wrong. :crying:
I already tried the Unbrick tool (Sahara) and restoring the old partition layout several times. And the partition layout recovery worked, but ColorOS says my NV partition is still invalid. It seems this partition got damaged and now my IMEI is gone and I can't use my mobile network anymore.
And sadly I figured out that the normal TWRP doesn't even show the NV/EFS partition to back (only modified TWRP do), so I don't have an backup of those partitions.
One last change would be to take an backup of another phone, anonymizing it by overwriting the IMEI and kindly sending me the copy.
If someone is willing to do so, I'd be very happy so I can reanimate my Find 7 .
I attached a tutorial:
1. Needed software:
Qualcomm QPST Diag drivers
Qualcomm QPST Tool
IMEI converter
Any hex editor, e.g. HxD Editor
2. Start phone in Diag Mode:
-Enable Developer Settings and then "USB-Debugging" on your device
Install the drivers. They are already signed, so no need to disable Windows signature check.
To enable the Diag Port, either under
a) ColorOS:
-Call *#801# and enable "Engineer Mode Toggle"
b) ADB and root access:
ADB commands:
-adb shell (only when accessing the phone with ADB from pc, not necessary when using TWRP adb terminal)
-su
-setprop sys.usb.config diag,adb
Now in the in the device manager you should see a "Qualcomm/Oppo HS-USB MSM Diagnostics 276C (COM y)" device
3. Backup the IMEI/Baseband infos:
Again, we have 2 alternative ways:
a) QFIL
Open QFIL: C:\Program Files (x86)\Qualcomm\QPST\bin\QFIL.exe.
Did QFIL already automatically recognize the Diag Port in the first row?
From the top menu "Tools" choose the entry "QNC Backup Restore". Backup the QNC
b) QPST
Open QPST Configuration: C:\Program Files (x86)\Qualcomm\QPST\bin\QPSTConfig.exe.
Under the tab "Ports" there should be the COM port from the device manager above.
If not, try "Add New Port" and untick “Show Serial and USB/QC Diagnostic ports only” and choose the right COM port and click OK.
If this doesn't help and no device shows up, add the COM-Port manually by typing the following:
Port: COMy (replace x with the number of what the device manager is showing you for the "Qualcomm/Oppo HS-USB MSM Diagnostics 276C (COM y)"
Label: You are free to name this port what you want
Then in QPST Configuation open the top menu entry "Start Clients" and then "Software Download". Select the port of the device in diagnostic mode and press OK.
Choose the “Backup” option tab, click browse, choose your destination and name of your QCN backup, choose the "QPST NV Memory Files (.qcn)" as “Save as type”, NOT the first option as (.xqcn).
Click “Start” and wait for it to finish. This will back up all your phones NV Items and save them to the QCN Backup File.
5. Anonymizing your IMEI:
Open the .qcn file with HEX editor.
Search for your IMEI in HEX format. To do so, use the IMEI converter, enter your IMEI.
[For your own verifcation: An IMEI in HEX always starts with "08" followed by your first IMEI number and an "A". So if you have IMEI 123456789012345 the HEX format would be 08 1A 32 54 76 98 10 32 54.]
Now search for the converted HEX string (or better search for the first four characters 08xA only). Keep in mind to set the search type to "HEX values" not "Text" or anything else.
Replace all numbers after “08” with dummy numbers, so the result will e.g. be: 08 1A 22 33 44 55 66 77 88. Please copy your chosen dummy HEX IMEI, so I know what I am searching for to insert my IMEI then.
Save the file (as another copy, don't replace your original file in ase you will need it some day)
6. Share the anonymized file with me over PN
I thank all of you for your help! :victory:

Hello, I am new here and I would like to know if it is possible that you could share the file that happened to you since I have the same problem after partitioning my cell phone Beforehand thank you very much Sorry for my bad English

hi. had same problem with imei missing in my phone after hard bricking it and partition all mess up but now I done reparing the partition, some error come up says nv partition error. then I find out the imei is missing. please send me the dummy imei to my email. hope I can have my phone back.
- [email protected]

USB Connection Issues?

Hello all;
Recently developed an issue with my S9. It won't connect to the computer over USB!
Unrooted, stock Galaxy S9 Firmware (Pi) with May 2019 security Update installed
Tried 4 USB cables (Original, Aukey USB 3.1, brand new USB 2.0, and brand new USB 3.0)
Tried on two different computers and on Android Auto (2017 VW GTI)
Charges perfectly fine from any computer or charger with any cable
Occasionally connects perfectly fine and will stay connected until I unplug it on either Android Auto or PC, regardless of how I move the device around
When it's wanting to connect, I can also unplug it at the phone end and plug it back in and it works fine.
No apparent correlation with 'how' I plug it in or hold the cable or temperature of the room I'm testing it in.
Connects more often to Windows 10 PC than to Android Auto
Occasionally, switching USB port on computer will make it work without replacing the plug on the phone end
On computer, will often 'Beep-beep' to indicate it connected, but doesn't show up in device manager and ADB won't detect it
When not connected, doesn't show up in ADB or Device manager
When it almost-connects on the computer, it will pop up the 'USB settings' notification and permissions dialogue, but then that disappears
Tried a full reset FROM the Settings menu.
Tried clearing cache
Carefully cleaned the USB C port on the phone with canned air and a soft plastic toothpick- didn't seem very dirty
Looking at Logcat files, I see that it starts to connect and then fail out
Other android phones and iphone work fine on Android Auto and on both computers
Any ideas? Is this most likely a hardware issue? (What Samsung support thinks)
Or is there a deeper hard reset/restore I can do? I tried a factory reset from the recovery menu but that failed saying that it had to be done from inside the OS. (New Pie security feature?)
Here's what I believe to be the relevant logcat file from connection to failure.
Code:
06-05 20:51:08.329 I/[email protected]( 725): partner added
06-05 20:51:08.331 I/[email protected]( 725): uevent received DEVTYPE=typec_partner
06-05 20:51:08.332 I/[email protected]( 725): port0
06-05 20:51:08.335 I/[email protected]( 725): connected:1 canChangeMode:1 canChagedata:0 canChangePower:0
06-05 20:51:08.335 I/UsbPortManager( 1477): ClientCallback: port0
06-05 20:51:08.343 D/UsbPortManager( 1477): addOrUpdatePortLocked()++ : portId=port0, supportedModes=dual, currentMode=ufp, canChangeMode=true, currentPowerRole=sink, canChangePowerRole=false, currentDataRole=device, canChangeDataRole=false
06-05 20:51:08.343 D/UsbPortManager( 1477): addOrUpdatePortLocked() supportedRoleCombinations=272
06-05 20:51:08.344 D/UsbPortManager( 1477): addOrUpdatePortLocked() supportedModes=dual
06-05 20:51:08.344 D/UsbPortManager( 1477): addOrUpdatePortLocked() mPorts DISPOSITION_REMOVED -> DISPOSITION_CHANGED
06-05 20:51:08.344 D/UsbPortManager( 1477): addOrUpdatePortLocked()--
06-05 20:51:08.344 D/UsbPortManager( 1477): mPorts size: 1
06-05 20:51:08.344 I/UsbPortManager( 1477): USB port changed: port=UsbPort{id=port0, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
06-05 20:51:08.345 D/UsbPortManager( 1477): mPorts(0) DISPOSITION_CHANGED -> DISPOSITION_READY
06-05 20:51:08.345 D/UsbPortManager( 1477): updatePortsLocked()--
06-05 20:51:08.348 D/UsbDeviceManager( 1477): received ACTION_USB_PORT_CHANGED
06-05 20:51:08.348 I/UsbDeviceManager( 1477): updateHostState UsbPort{id=port0, supportedModes=dual} status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}
06-05 20:51:08.358 E/BartenderActivityManager( 1477): BarTender: pid : 20445 cached=true abnormal=false kill=false stay=false release=false
06-05 20:51:08.361 E/BartenderActivityManager( 1477): BarTender: pid : 18831 cached=true abnormal=false kill=false stay=false release=false
06-05 20:51:08.362 E/BartenderActivityManager( 1477): BarTender: pid : 20756 cached=true abnormal=false kill=false stay=false release=false
06-05 20:51:08.404 V/UsbDeviceManager( 1477): USB UEVENT: {SUBSYSTEM=android_usb, SEQNUM=6847, ACTION=change, USB_STATE=CONNECTED, DEVPATH=/devices/virtual/android_usb/android0}
06-05 20:51:08.405 I/UsbDeviceManager( 1477): updateState CONNECTED
06-05 20:51:08.405 D/UsbDeviceManager( 1477): handleMessage -> MSG_UPDATE_STATE connected = 1,configured = 0 mCurrentFunctions mtp
06-05 20:51:08.405 D/UsbDeviceManager( 1477): updateUsbNotification(false) : mConnected = true, mConfigured = false, mCurrentFunctions = 4, mHostConnected = false, mSourcePower = false
06-05 20:51:08.406 D/UsbDeviceManager( 1477): id=27, mUsbNotificationId=0, titleRes=17042083
06-05 20:51:08.411 D/ApplicationPolicy( 1477): isStatusBarNotificationAllowedAsUser: packageName = android,userId = -1
06-05 20:51:08.411 D/API test( 1477): getContainerInfo: value is
06-05 20:51:08.411 D/ApplicationPolicy( 1477): isStatusBarNotificationAllowedAsUser: packageName = android,userId = 0
06-05 20:51:08.412 D/API test( 1477): getContainerInfo: value is
06-05 20:51:08.415 D/UsbDeviceManager( 1477): updateUsbNotification : notify id = 27, title = USB for file transfer
06-05 20:51:08.415 D/UsbDeviceManager( 1477): updateUsbStateBroadcastIfNeeded functions 5
06-05 20:51:08.415 D/UsbDeviceManager( 1477): updateUsbStateBroadcastIfNeeded remainingFunctions 5
06-05 20:51:08.416 D/UsbDeviceManager( 1477): broadcasting Intent { act=android.hardware.usb.action.USB_STATE flg=0x31000000 (has extras) } extras: Bundle[{host_connected=false, connected=true, unlocked=true, config_changed=false, adb=true, mtp=true, configured=false}]
06-05 20:51:08.421 V/UsbDeviceManager( 1477): USB UEVENT: {SUBSYSTEM=android_usb, SEQNUM=6848, ACTION=change, USB_STATE=DISCONNECTED, DEVPATH=/devices/virtual/android_usb/android0}
06-05 20:51:08.421 I/UsbDeviceManager( 1477): updateState DISCONNECTED
06-05 20:51:08.429 D/MTPRx (22081): In MtpReceiverandroid.hardware.usb.action.USB_STATE
06-05 20:51:08.430 D/UsbDeviceManager( 1477): sending intent : ACTION_USB_STATE : connected = true, configured = false, mCurrentFunctions = 4, mHostConnected = false, configChanged = false

I am having the same issue. My S9 SM-G960W with latest ROM stopped connecting to my PC. I also noticed that none of my OTG USB drives / cables that I have work anymore. I checked all my PC USB ports and OTG USB drives with my old S6 and my wife's S9 phone and they all connect right away and they recognize the drives with no problems. Cleared the cache. Tried different USB settings on the phone and lots of different cables. The phone just says charging no connection for file transfer. It used to work awhile back because I used the PC to transfer old phone to it and I backed it up a few times. Found the problem when I was going to do my regular backup...

i have a type c otg cable in my car and a usb on my keychain, ill have to grab the otg and give it a whirl. ill post up my results if i can remember to do this

If you dial *#0808# on the dial pad what do you get? Can you change these setting and does it stick? Does your phone recognize if you insert any USB memory stick?

Did you solve your problem yet?

this goes to show what kind of awesome memory i have, but the OTG cable was a go. I was able to read all my files and modify them. Are you still having the same issue?

Not solved. Cannot connect anything to USB and get it to work. Other than charge.

MECH_TECH said:
Not solved. Cannot connect anything to USB and get it to work. Other than charge.
Click to expand...
Click to collapse
have you enabled developer options?

Yes developer options is enabled. USB debugging is on. Default USB is set to file transfer. If I plug in my USB memory stick I get a notification that "USB device connected" then message "charging connected device via USB" and if I tap the notification I see that "USB is controlled by connected device" and cannot change that -it says failed to change.

MECH_TECH said:
Yes developer options is enabled. USB debugging is on. Default USB is set to file transfer. If I plug in my USB memory stick I get a notification that "USB device connected" then message "charging connected device via USB" and if I tap the notification I see that "USB is controlled by connected device" and cannot change that -it says failed to change.
Click to expand...
Click to collapse
might be time to nuke the OS and reflash via Odin. All the time and frustration trying to figure it out might not be worth the time itll take to set your phone back up again

When you say nuke the OS do you mean just flashing the ROM using ODIN to nuke the OS or factory reset then instill ROM with ODIN? Installing ROM with ODIN will not clear the user DATA or SD card contents correct? I have tried booting into recovery and clearing the cache, but that did not do anything.

I don't want to start new thread but similar problem , I can't connect S9 to PC. Did not have any problems until last month. Meanwhile I have done all including changing USB ports and yes I can connect my wife's S9 to PC. Still no luck. Any help will be very much appreciated

b0rken touchscreen

Hi there,
I'm using an old lineageos 18.1 build.
I'm on hols, I just broke my screen, unfortunately it's not only the glass, it's the main touchscreen.
I'm still having access to the recovery and to the booting device with adb, but the device never finishes booting.
It keeps trying to setup the touch input.
08-12 18:23:26.171 10064 10064 I HidlServiceManagement: getService: Trying again for [email protected]::IGloveMode/default...
08-12 18:23:26.173 3960 10428 W libc : Unable to set property "ctl.interface_start" to "[email protected]::IGloveMode/default": error code: 0x20
Click to expand...
Click to collapse
I'd like to use scrcpy from my computer to use the phone.
Any idea how to disable the touch input device init so the phone starts the main services ?

looks like removing vendor.lineage.touch from /etc/vintf/manifest.xml did the trick.
not very convenient to use a phone without a screen, that will do until I get back home