HasH_BrowN
Android Expert
I need a backup of the stock Data Done Right ZV5 boot.img.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Yes, it was that from the day I got it back in March (if remembered correct)Is yours 00:90:4C:C5:12:38?
Maybe. There are probably some similarities. Engineers at LG/Qualcomm aren't going to make each new device completely unique and independent.Could a /misc partition from another device work? Say an LG Volt? I'm suppose to get in the mail today. If so I can pull it from that, being NIB (new in box). OR is there too many differences in makeup?
View WCNSS_qcom_wlan_nv.bin in a hex editor. The value of MAC address starts at offset 0xA. There are 4 addresses, but it seems only Intf0MacAddress is used (one wifi adapter, I guess). NV items are probably values stored in the NV ram. If you google, you can read discussions about people accessing NV items to tweak settings. So it's possible the MAC (and other device specific data like IMEI) are stored in NVRAM, but I don't know how those values are used and accessed.WCNSS_qcom_wlan_nv.bin - which line, there are 26?
Also how do I view properly?
Here is WCNSS_qcom_cfg.iniWhat are NV items line 40
I was talking about this code block:My /system/etc/init.zetaw.wifi.sh has 106 lines. 2 blank lines at end, with no reference anywhere leading to a MAC address. Only thing mentioned was restart and something with bluetooth.
# Populate the writable driver configuration file
#if [ ! -e /data/misc/wifi/WCNSS_qcom_cfg.ini ]; then
rm /data/misc/wifi/WCNSS_qcom_cfg.ini
cp /system/etc/wifi/WCNSS_qcom_cfg.ini \
/data/misc/wifi/WCNSS_qcom_cfg.ini
chown system:wifi /data/misc/wifi/WCNSS_qcom_cfg.ini
chmod 660 /data/misc/wifi/WCNSS_qcom_cfg.ini
#fi
rm /data/misc/wifi/WCNSS_qcom_wlan_nv.bin
cp /system/etc/wifi/WCNSS_qcom_wlan_nv.bin \
/data/misc/wifi/WCNSS_qcom_wlan_nv.bin
chown system:wifi /data/misc/wifi/WCNSS_qcom_wlan_nv.bin
chmod 660 /data/misc/wifi/WCNSS_qcom_wlan_nv.bin
# The property below is used in Qcom SDK for softap to determine
# the wifi driver config file
setprop wlan.driver.config /data/misc/wifi/WCNSS_qcom_cfg.ini
rm /etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin
ln -s /data/misc/wifi/WCNSS_qcom_wlan_nv.bin \
/etc/firmware/wlan/prima/WCNSS_qcom_wlan_nv.bin
rm /etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
ln -s /data/misc/wifi/WCNSS_qcom_cfg.ini \
/etc/firmware/wlan/prima/WCNSS_qcom_cfg.ini
The middle one is just a symlink to the first one. The third one (in /system) is the default I was talking about. The same one for everyone. The first one (in /data) should be the configured one containing device-specific data.WCNSS_qcom_wlan_nv.bin is found at 3 locations. View attachment 95051
All with different dates and middle one a different size
So it's possible data in /misc come from somewhere else, and we can put things back, so to speak, to fix the problem. In my "misc" image, I've found MEID, wifi MAC, and another MAC-address-like byte sequence. If I treat that byte sequence as a MAC address, its vendor id would also be LG. Maybe that's the MAC used for cellular data?misc
Tiny partition used by recovery to stash some information away about what it's doing in case the device is restarted while the OTA package is being applied.
Do I read the byte sequence with a hex reader/editor? I don't normally mess with type of stuff, but this is interesting.So it's possible data in /misc come from somewhere else, and we can put things back, so to speak, to fix the problem. In my "misc" image, I've found MEID, wifi MAC, and another MAC-address-like byte sequence. If I treat that byte sequence as a MAC address, its vendor id would also be LG. Maybe that's the MAC used for cellular data?
Yes. The wifi MAC is at offset 0x3000. The bluetooth MAC (duh, so that's what it was, not cellular data; I forgot about BT) is at 0x4000. MEID is at 0x6800 as a text string.Do I read the byte sequence with a hex reader/editor? I don't normally mess with type of stuff, but this is interesting.
But did it fix/correct a MAC address issue? That's the main issue/concern. My wifes DDR VM's Tribute reverted to a default Android MAC address.I have a DDR LG volt from verizon.... i effed my phone up REAL good!
First thing to do is use a TWRP to wipe out ALL the memory partitions....
Then I used LG Flash tool and flashed the zv3 .tot
Boot it up, connect to wifi.
Let it do HFA, PRL and Profile update
Use LG one click root and root the device.
Install Link2SD and ES File explorer.
Get copies of the "ItsOnDashboard.apk" (a.k.a the default app "Virgin Mobile"), "ItsOnService.apk" and "ItsOnSprintProxy.apk" - I have backups of each if you need them.
Goto ES File Explorer and in the menu on the bottom, click Enable Root and Show Hidden. Then copy those 3 .apk files to the folder "app" located here: Device/carrier/itson/app
Use Link2SD to convert them to system apps. Reboot.
Install and Run the new System Apps.
Connected to Wifi: -LOGIN to your new Virign Mobile icon, Check for Updates, ect. Let that catch up. Then use your ##72786# -> The process should cycle HFA; PRL; Profile, again, just let it run.
Check your status after that.
If still not working, Shut off Wifi, Shut off Data and use ##DATA#
It will probably not let you Diasble "ItsOn" so "Disable eHRPD" instead. Let it reboot. Keep the wifi and data off.... Give it about 10 Minutes and Enable the eHRPD you disabled, and then after reboot, keep wifi off, and Turn on Data.
I have not had the DDR firmware on my Volt since day one. I never had any major problems at first, then the custom roms took it wonkers and i only had TALK and TEXT and wifi. LTE /3G were unable to reach the device. This was how i how i got it fixed.
You may have to throw a ##MSL" - Reset in there after, but thats if all that fails.