[GUIDE] Unlock LS980 ZVD (KK 4.4.2) [UPDATED 8/10/14] - Sprint LG G2

Ok I successfully unlocked ZVD (KitKat 4.4.2) and thought I should share my steps in case anyone else was having the same issues as me which was mostly the systemui and home processes crashing on a loop.
First insert the SIM card you would like to use in the LS980. Then download and flash the stock firmware LS980ZVC_12.zip with the LG Tool -> http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware
Download the ZVD update - > http://www.mediafire.com/download/s5dqwo1cbe68ckb/LS980ZVC_12-LS980ZVD_19_update.zip (Do not flash this OTA update from a rooted rom or custom recovery!)
After flashing ZVC, set the phone to charge only and enable USB debugging by becoming a developer. Go to About Phone->Software Information and keep clicking "Build number" until it says you are a developer. Then go back to the main settings and you will now see "Developer options" and can enable USB debugging in there.
After enabling USB debugging choose charge only and when the RSA Key fingerprint window pops up make sure you check "Always allow from this computer" and then click OK.
Next using the ADB tools, reboot into recovery mode to apply the ZVD update.
Code:
adb reboot recovery
Select "apply update from ADB" with the volume buttons then press the power button. Wait 5 seconds then enter the following command.
Code:
adb sideload path_to_file/LS980ZVC_12-LS980ZVD_19_update.zip
After the update finishes select "reboot system now".
Next turn on airplane mode and root the phone using IO Root -> http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Next install SuperSU and BusyBox. Make sure you open SuperSu to update the SU binary and open BusyBox and install the busybox files.
*OPTIONAL INSTALL TWRP*
Next use ADB to install AutoRec -> http://forum.xda-developers.com/showthread.php?t=2715496.
Code:
adb install path_to_file\LS980_AutoRec.apk
Open AutoRec and flash the new patched kernel and recovery and then reboot. If you get white lines after rebooting, read the warning the OP has posted for the fix. I suggest here you take the time to make a backup and copy the EFS to your computer just in case.
*knock code feature will no longer work
*flash this kernel to enable knock code again and much more - > http://forum.xda-developers.com/showthread.php?t=2725023
*OPTIONAL END*
Now using ADB again, enter the following commands.
Code:
adb pull /system/build.prop
adb shell
su
After entering "su" check your phone to grant SuperUser permission to ADB. Aftering granting su to ADB, exit adb shell.
Code:
exit
exit
Next using Total Commander and the files from here -> http://forum.xda-developers.com/showthread.php?t=2655133 copy all the contents of the "carrier" folder to your phones "/carrier/" directory and choose "overwrite all". I like to delete the "legal.db" first this way I know the copy was successful when I see the new file listed. Do not delete any other files before copying the files over since we want to keep the file and folder permissions and owners of the originals. If Total Commander fails to copy the files over to the phone then you can use a root explorer app to do so.
Now edit the build.prop that you pulled from the phone with a program like Notepad++ since it will save the file for use with linux and not windows. Do not edit the build.prop or copy it back to the phone with any apps on the phone, this is what was causing the crashes for me.
Change the following lines
Code:
ro.carrier=unknown
ro.build.target_operator=SPR
persist.service.crash.enable=0
ro.telephony.default_network=10
telephony.lteOnCdmaDevice=1
to
Code:
ro.carrier=spr
ro.build.target_operator=spr
persist.service.crash.enable=1
ro.telephony.default_network=0
telephony.lteOnCdmaDevice=0
*ro.carrier and ro.build.target_operator can bet set to "TMO", "ATT", or "spr".
*"TMO" and "ATT" do not correctly display the signal strength in the status bar.
Save the build.prop and use ADB to push it to the sdcard.
Code:
adb push build.prop /sdcard/
Now here is where we have to manually mount the system partition as RW and copy the build.prop over since all the root explorer apps seem to also cause the crashing issue.
Code:
adb shell
su
mount -o remount,rw /system
cp /sdcard/build.prop /system/
mount -o remount,ro /system
reboot
After the phone reboots it should be unlocked. Verify with Radio Switcher that your preferred network type is "WCDMA preferred", if not then change it to "WCDMA preferred". Now add your APN using Tweakker APN INTERNET MMS. If your APN doesn't stick, delete /data/data/com.android.providers.telephony/databases/telephony.db and reboot then add your APN again.
*To remove Bloatware add ".bak" to the following system applications names located in /system/app/ and /system/priv-app/ folders.
Activation.apk
OmaDmclient.apk
SPR_Skyfire_Observer.apk
SPR_Skyfire_Toolbar.apk
SprintExtensionProvider.apk
SprintID.apk
SprintTouch.apk
Vtt-Sprint.apk
xtra_t_app.apk
Zone-Sprint.apk
WIFIOffloader.apk
Click to expand...
Click to collapse
*To fix the issue of the com.android.phone process crashing when you don't dial a 1 in front of the number edit the /data/data/com.android.providers.settings/databases/settings.db file with a SQLlite editor and change in the "system" table "assist_dial" and "assist_dial_init_db_check" to "0". If you don't see those 2 rows then you can add them instead.
Code:
adb shell
su
cp /data/data/com.android.providers.settings/databases/settings.db /sdcard/settings.db
exit
exit
adb pull /sdcard/settings.db
sqlite3 settings.db
UPDATE system SET value='0' WHERE name='assist_dial';
UPDATE system SET value='0' WHERE name='assist_dial_init_db_check';
.exit
adb push settings.db /sdcard/
adb shell
su
cp /sdcard/settings.db /data/data/com.android.providers.settings/databases/settings.db
chown system:system /data/data/com.android.providers.settings/databases/settings.db
reboot
*To disable OTA updates and notifications rename the following files
/etc/security/otacerts.zip
/system/app/LGFOTA.apk
Click to expand...
Click to collapse
to
/etc/security/otacerts.zip.bak
/system/app/LGFOTA.apk.bak
Click to expand...
Click to collapse
*To replace the Sprint boot/shutdown animations and sounds with the LG default ones download these files -> https://www.mediafire.com/folder/cmb6jn7z7osmf/LG_G2_Boot_Animation
copy and overwrite the following files to /system/media/
bootanimation_sprint.zip
shutdownanimation_sprint.zip
Click to expand...
Click to collapse
copy and overwrite the following files to /system/media/audio/ui/
PowerOff_Sprint.ogg
PowerOn_Sprint.ogg
Click to expand...
Click to collapse
*LG G3 Theme for G2 -> https://play.google.com/store/apps/details?id=com.lge.launcher2.theme.rocketg3&hl=en
Thanks to all those people who contributed to this. :victory:

Thanks for the guide, working find for me and LS980, mms msg not working, propably i have error on APN settings, and signal bar min or max signal is 1 bar only....

MakisPgr said:
Thanks for the guide, working find for me and LS980, mms msg not working, propably i have error on APN settings, and signal bar min or max signal is 1 bar only....
Click to expand...
Click to collapse
Info and fix about the 1 signal bar bug is located in the guide above. Your mms issue is most likely a APN mistake. Make sure your data is working.
Sent from my LG-LS980 using XDA Premium 4 mobile app

This method worked on my ATT sim card I dont need to dial a 1 in front of #. but didnt work on my Lycamobile simcard and pageplus. still need to dial 1 infront of nuber.
thanks.
来自我的 LG-LS980 上的 Tapatalk

Can you attach a logcat of it crashing when you dial please
Sent from my LG-LS980 using XDA Premium 4 mobile app

jsergio123 said:
Info and fix about the 1 signal bar bug is located in the guide above. Your mms issue is most likely a APN mistake. Make sure your data is working.
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes you are right about 1 bar signal, didn't notice, and i fix my mistake settings on APN and mms now works perfectly ... Thank you very much

jsergio123 said:
Can you attach a logcat of it crashing when you dial please
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
sorry, I dont know where is it.

ahqiu said:
sorry, I dont know where is it.
Click to expand...
Click to collapse
adb logcat > logcat.txt
Sent from my LG-LS980 using XDA Premium 4 mobile app

Updated the OP for latest ZVD update from Sprint.
Added SQLite instructions.
Also confirmed working myself.

Updated the OP to include the files and instructions to replace the sprint boot/shutdown animations and sounds

Do you know if I would be able to install a custom rom after this? Also, I had the issue before with cloudys rom that would cause app force closing and restarts, should I expect the same this way?
Thanks a bunch

If you want to use a custom asop rom don't follow my guide instead just follow this guide after flashing your rom of choice.
http://forum.xda-developers.com/showthread.php?t=2827043

@jergio123
Do you think this would work to unlock additional bands on the Sprint LGG2 LS980 for T-Mobile USA?
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269

I guess the only way to find out would be to attempt it. I only quickly looked through the thread but good find.

Is there suppose to be a custom folder inside the carrier folder I copied over to root directory? After rebooting my device I've notice this custom folder that's not inside the original carrier folder I extracted ?

There should be a "cust" folder, I'm not sure if that is the folder you're referring to.

Will cloudys g3 ROM work with this unlock method?

I'm pretty sure cloudys rom is already unlocked and only requires you to change the radio with radio switcher and add your APN

Don't work
Hello, i can't unlock with this method. In the end, when i turn on the phone unlocked, the phone give me an error and always appear "com.android.phone".
I don't understand this part:
"Now edit the build.prop that you pulled from the phone with a program like Notepad++ since it will save the file for use with linux and not windows. Do not edit the build.prop or copy it back to the phone with any apps on the phone, this is what was causing the crashes for me."
I need edit "built.prop" or not? How?
I'm using the phone in Portugal (gsm carrier), i need to do this part?
Sorry but i really confused.
Thank you

Follow the guide step by step, I don't know how much clearer I can make it.
If you're getting process crashes then you must either restore the system partition from backup or start fresh by re-flashing with the LG tool.

Related

[GUIDE] enable trackball/pad wake on the latest MIUI builds again

I think I found an easier way to enable trackball/pad wake again!
1. connect your phone to your pc and open a cmd window
2. execute the following commands:
adb shell
stop
cd /data/data/com.android.providers.settings/databases/
cp settings.db settings.bak
sqlite3 settings.db "insert into system (name,value) values ('trackball_wake_screen',1);"
start
3. thats it, if you want to disable it again do the same again but instead of
sqlite3 settings.db "insert into system (name,value) values ('trackball_wake_screen',1);"
use
sqlite3 settings.db "insert into system (name,value) values ('trackball_wake_screen',0);"
I have found a way to enable trackpad wake on MIUI Roms again! It's a little tricky but it works perfectly.
Things you need:
SQLite Database Browser -> http://sourceforge.net/projects/sqlitebrowser/
Follow these steps exactly:
1. connect your phone to your computer and open a cmd prompt
2. type in the terminal:
Code:
cd %USERPROFILE%\desktop
adb shell stop
adb pull /data/data/com.android.providers.settings/databases/settings.db
3. extract SQLite Database Browser somewhere and start it
4. open your settings.db with SQLite Database Browser (you'll find it on your desktop)
5. Change to "Browse Data" and select the system table
6. add a "New Record"
7. doubleclick the name filed of the new record and write
Code:
trackball_wake_screen
inside. Click Apply Changes!
8. doubleclick the value field of trackball_wake_screen and write
Code:
1
inside. Click Apply Changes!
9. Save the file (maybe you want to make a backup of the original file before this point )
10. last step is to copy the file back to your phone:
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/
adb shell start
Now trackpad wake should work again.
Woukd this only work on miui?
There are quite a few people waiting for this feature on xboarders stock gingerbread rom.
Sent from my Nokia 3210 using XDA Premium App
Can someone try this out on the test ver? I badly need track wake
Sent from my T-Mobile G2 using XDA App
xile6 said:
Can someone try this out on the test ver? I badly need track wake
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I just tried this on my Droid Incredible, and it does work! Thanks!
Worked on my N1, Thankyou
Just wanted to say that I tried this again with the latest MIUI build...and again it works! Thanks!
Sweet worked for my HTC Incredible running MIUI 1.6.24 with Incredikernel 06192011
without adb
Can you do it without using adb, eg. with root explorer on the phone ?
(I am using MIUI on my google N1)
slim_thumb said:
Can you do it without using adb, eg. with root explorer on the phone ?
(I am using MIUI on my google N1)
Click to expand...
Click to collapse
I guess not since android has to be stoped to make this change. (stop command is to shut down android)
But why don't you just enable trackball wake in the settings menu? The Nexus One had always the option for it. The settings app checked the device name and if it wasn't passion (N1) or bravo (Desire) the trackball wake option didn't show up.
So Desire Z (vision) lost trackpad wake. Thats why I was looking for a way to enable it again. But since a few releases this isn't needed anyways.
Sent from my HTC Desire Z using Tapatalk
g4rb4g3 said:
But why don't you just enable trackball wake in the settings menu? The Nexus One had always the option for it.
Click to expand...
Click to collapse
Sorry I looked at the settings menu (under "hardware key setting"), there is no such option.
slim_thumb said:
Sorry I looked at the settings menu (under "hardware key setting"), there is no such option.
Click to expand...
Click to collapse
Goto Settings - System - Button Settings - Trackball wake
I can't belive that this doesn't exist on the Nexus One.
Sent from my HTC Desire Z using Tapatalk
Found it, my bad!
slim_thumb said:
Can you do it without using adb, eg. with root explorer on the phone ?
(I am using MIUI on my google N1)
Click to expand...
Click to collapse
Works with root explorer... Just copy database to sdcard then edit while connected to pc.. Copy back, change permissions, reboot and your set..
You can also just use an sqlite editor app..
Any chance someone could post step by step instructions on how to do this with sqlite editor on the phone?
EDIT:
Scratch that. Figured it out.
Thanks a million! This saved the day. Cant believe its not integrated with miui. Nexus One MIUI
Hi..
when I open cmd and I type adb shell... i get this..
'adb' is not recognized as an internal or external command,
operable program or batch file.
magdiel1975 said:
Hi..
when I open cmd and I type adb shell... i get this..
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
You need to navigate to your sdk / adb folder.
Sent from my Sensation using xda premium
trackpad wake works on latest miui.. I am currently running it? :S
I wonder why people don't use the trackball/pad wake option in the settings menu too....
This was an issue half a year ago but the MIUI team fixed it a few weeks later and since then it works without this.
works for me
g4rb4g3 said:
I have found a way to enable trackpad wake on MIUI Roms again! It's a little tricky but it works perfectly.
Things you need:
SQLite Database Browser -> http://sourceforge.net/projects/sqlitebrowser/
Follow these steps exactly:
1. connect your phone to your computer and open a cmd prompt
2. type in the terminal:
Code:
cd %USERPROFILE%\desktop
adb shell stop
adb pull /data/data/com.android.providers.settings/databases/settings.db
3. extract SQLite Database Browser somewhere and start it
4. open your settings.db with SQLite Database Browser (you'll find it on your desktop)
5. Change to "Browse Data" and select the system table
6. add a "New Record"
7. doubleclick the name filed of the new record and write
Code:
trackball_wake_screen
inside. Click Apply Changes!
8. doubleclick the value field of trackball_wake_screen and write
Code:
1
inside. Click Apply Changes!
9. Save the file (maybe you want to make a backup of the original file before this point )
10. last step is to copy the file back to your phone:
Code:
adb push settings.db /data/data/com.android.providers.settings/databases/
adb shell start
Now trackpad wake should work again.
Click to expand...
Click to collapse
This method worked for me on my HTC Droid Incredible running MIUI 2.11.9. I actually used File Explorer in Android:
1. copied settings.db
2. uploaded it to my PC
3. used SQLite to edit it
4. copied it back to phone
5. backed up settings.db
6. pasted the new file in
Restarted phone and trackball wakes it up now.
Thanks!

[CWMR ZIP] ICS Keyboard backlight fix

First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff.
This also fixes force-close related freezes by setting the default.prop to insecure and debuggable.
manual method
Now with CWM goodness!
DOWNLOAD LH2 file for official ICS RELEASE
Awesome!
does not work for me...
Worked perfect here, that fixes my only serious issue with the ICS rom.
I'm glad i was of some help . My first significant contribution to android. Will have to get back home to test it.
does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing
The_Bizzel said:
does not work for me either. used Root Explorer to take the "lights.n1.so" file from download and overwrote it at /system/lib/hw/lights.n1.so, and rebooted several times, and still got nothing
Click to expand...
Click to collapse
Overwriting the file won't work in my opinion. As these files are part of the boot.img and resides inside the ramdisk. So even if you change something in the ramdisk and then reboot you'll return to the original version.
I guess the only way is to flash the boot.img with the files inbuilt in to the ramdisk. So the boot.img posted by "Nardholio" should work.
Mhh just copying the .so file does not work for me to, even after wiping the caches.
I'm going to try this boot.img thing later this day.
Nardholio said:
First off, I can't take credit for this. ninthsense and etherfish discovered the missing information in the ICS files. There are missing permissions for the keyboard backlight in the boot image, and the actual file that controls lights, /system/lib/hw/lights.n1.so is missing some stuff. To fix it, just copy the version from Gingerbread over the ICS version and reboot. Note this requires root. The attached post contains the file you need and an optional boot.img mod that will fix force-close related freezes and will enable the keyboard light to be controlled by third party utilities.
http://forum.xda-developers.com/showpost.php?p=30591025&postcount=42
Click to expand...
Click to collapse
Didn't work for me at first either after I copied and pasted it. But when I went through and opened up a Terminal on my phone to install everything (I always thought I had to use Ubuntu on my computer for it. I don't know why I never even thought of using a Terminal on my phone to do editing on it and all...) and went through the steps on the link (didn't clear my cache), and it all works. Just a heads up for anyone who might be as slow as I was
Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium
Nardholio said:
Both files are required then I guess. Thanks for letting me know.
Sent from my SGH-I927 using xda premium
Click to expand...
Click to collapse
confirmed working after both files were pushed. warning to others, do not wipe /dev/block/mmcblk0p9 if you have not verified that boot.img is on /sdcard via terminal emulator or adb shell:
Code:
cd /sdcard
ls
goodluck!
Can anyone help me with this via step by step?
I could use a little help as well
Sent from my SGH-I927 using xda app-developers app
Yea, i could use some help too, after re-writing over the existing file didn't work
OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.
Copying the boot.img worked for me
For those who having trouble, look at the Link, posted in the OP
How I did it:
Copy files to sdcard: Use a network enabled file manager or email or drop box (or, or, or) to get boot.img and lights.n1.so to /sdcard
Setup ADB: Google "xda setup adb"
Boot into CWMR: Reboot phone, holding power down (Link: Get CWMR)
Choose in CWMR:
Mounts > Mount sdcard
Mounts > Mound system
Execute Commands on pc
Open Shell/Cmd
Type: adb shell
Type: ls
you should geht a file listening of your root file system
Type: dd if=/dev/zero of=/dev/block/mmcblk0p9
Type: dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
Type: cp /sdcard/lights.n1.so /system/lib/hw/lights.n1.so
Choose in CWMR:
Wipe Cache
Advanced > Wipe dalvik cache
Reboot system
That was the steps as I remember, no guarantee don't brick your device if you do: use one-click-ics-leak-tool and start from scratch
ninthsense said:
OK guys here is the step by step guide :
I'm assuming that you're rooted and are on windows PC :
1. Install root explorer or root browser lite (free) from market. And copy the boot.img and lights.n1.so from keyboard_fix.rar in root of your sdcard(phone).
2. Launch the root explorer and Delete the existing lights.n1.so file from /system/lib/hw (probably you can keep a copy somewhere)
3. Copy the lights.n1.so from your sdcard directory to /system/lib/hw
3. Make sure that the file is presen/copiedt in the directory.
4. Download fastboot.zip file attached to the post and extract it in one of your directory on the pc.
5. Connect your phone through a usb cable and i'm assuming you've the usb drivers for your phone already installed on your pc.
6. Goto command prompt and change to the directory you extracted the zip file into.
7. issue the command "adb shell"
8. You should get a android prompt. Issue the command "su"
9. Issue cd sdcard and then issue "ls". Just to make sure that the boot.img is there.
10. Now issue the following commands:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p9
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p9
11. Reboot and you should get your lights.
Click to expand...
Click to collapse
Worked! thanks abunch man
LuckRocks said:
Worked! thanks abunch man
Click to expand...
Click to collapse
You are welcome. I also did it just before posting the steps and glad that the biggest bug for the leaked ROM is now fixed.
I see that the lights go off very quickly unless you keep pressing something. It's related to "Touch Key Light Duration" under "display" in the settings. But i see only 1.5 seconds which is set currently and 6 seconds. If i change to 6 it's too much.
Does somebody know how to modify this value according to whatever we need ?
Hello ninthsense,
perfect tutorial, keyboard light is working now.
Thanks,
Mister.Knister
Hummm is their gonna b a flashable zip for this ?

Sprint LG-LS980 [Root , Sim Unlock and Custom Recovery] with ZVD Firmware

How to Sprint LG-LS980 [Root , Sim Unlock and Custom Recovery] with ZVD Firmware
If you have the Stock ZVD firmware you may need to follow the below specific methods to Root, Sim Unlock and Setup Custom Recovery
Must have:
1. Stock ROM - ZVD
Root using this instructions in this thread
2. Sim Unlock using instructions in this thread
If you have issues , with files NOT getting copied as per instructions in 2. Then follow the manual copy method.
Once rooted , manually copy over the carrier folder using adb shell commands.
eg :
First copy the carrier folder to /sdcard
adb push carrier /sdcard
adb shell
su
cd carrier
cp -rfv ../sdcard/carrier/* .
The above is manual way of working around the copy issue. For some reason the root explorers dont seem to be providing the right error message due to copy permissions.
3. Custom Recovery : Via Autorec , most other methods will result in : "Secure Booting Error! Cause: boot certification verify"
And then the screen goes black. From here you cant do anything but holding down power and volume down to boot regularly without any problems.
i am sorry I am a complete noob can you tell me step by step how to replace current carrier files for SIM lock? I really need to change my APN settings.
Thanks
sooperbad said:
i am sorry I am a complete noob can you tell me step by step how to replace current carrier files for SIM lock? I really need to change my APN settings.
Thanks
Click to expand...
Click to collapse
Have you tried the step by step instructions here ? http://forum.xda-developers.com/showthread.php?t=2448887
kryptonite said:
Have you tried the step by step instructions here ? http://forum.xda-developers.com/showthread.php?t=2448887
Click to expand...
Click to collapse
I used your ads shell commands to copy carrier files after debugging mode. Here's what I did!!
1) Placed carrier folder into the adb shell folder
2) Shift+right click to open command window here
3) Ran your above mentioned shell command at cmd as they are:
adb push carrier /sdcard
adb shell
su
cd carrier
cp -rfv ../sdcard/carrier/*
Manually copied the apn cml file and changed its permissions. Deleted corresponding files mentioned in the SIMLOCK thread and now MMS is working.
I think that was about right?
Yes thats about right.
Help please
I am trying to unlock my friends sprint ls980 to use on Tmo I am on zvd with affliction rom and I am rooted. However, when i Put tmo sim in I get nothing no signal! any ideas?
edit: I just read sooperbad instructions and doing ok
hi I have one ls980 with zvd. I rooted it with towelroot and installed twrp with autorec app but not able to Sim unlock it. root explorer copy carrier folder and overwrite but after reboot no service with foreign gsm Sim while other ls980 with zvc working fine with my Sim.
I also tried manual command based method as written in first post but still no luck with gsm.
kindly help to resolve this issue.
thanks

Buildprop editor

Hello guys
i konw that it seems that it is a duplicate thread, but im facing a different issue now, i came back to stock (At&t) optimus g pro E980 rom and as i did before i rooted it but to get the network preferred menu in the network settings to change between WCDMA and GSM and LTE i installed the (Buildprop editor) and changed the (ro.build.target_operator) from (ATT) into (OPEN), and i have tried this before and it worked just fine, but now it takes the superuser permission and it reboots but the value (ATT) keeps coming back and the editor doesnt save me new editing, i read many threads and i have installed ES Explorer and change the boot Explorer from the side menu and also gave the (mount R/W) for all the options above, and also it doesnt work and the editor dont save my changes and when i reboots all the old values are coming back,,,,
What can i do?
Setup adb on your pc, then:
- adb root -> give root access to ADB
- adb remount -> remounts system as read-write
- adb pull /system/build.prop -> pulls build.prop from your device to your PC
- find value, change it and save file
- adb push build.prop /system/build.prop -> pushes back file to system
- adb reboot -> reboot to make changes valid
Don't forget to allow both apps and ADB root access in developer options, if you're running something CM based OFC, your phone needs to be rooted for this to work.
Thanks shady but it looks like it is a complicated process specially if i wanna keep switching between the network modes, previously i did it smoothly with the same builtprop editor and i got the preferred network modes menu, but now it is not saving, so there should be a reason for that, i will keep searching and waiting for other members opinion
Thanks again
Well, probably app can't remount filesystem or something goes wrong, take a look at logs. This is the way I prefer to do things - it's easier than typing on the phone and it's error-proof.
Finally i got a logical answer for my issue and it worked just fine
Follow the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1193245
I simply followed the exact instruction for the ES root explorer
Have a nice day
Sent from my LG-E980 using xda Forums PRO

Android 6.0 - SD Card access

Anybody knows how to enable third-party apps to access SD Card? Things that were working under 5.1 are not under 6.0 anymore.
Well, it seems Google is really retarded regarding SD Card access, changing API every other version:
http://stackoverflow.com/questions/32129716/how-does-storage-access-change-on-android-6
Radek Hulán said:
Anybody knows how to enable third-party apps to access SD Card? Things that were working under 5.1 are not under 6.0 anymore.
Click to expand...
Click to collapse
i used the old Kitkat fix for my brief period on 6.0, but i rolled back to 5.1 for the time being, battery drain was too much.. here
Well, not going to root my device to gain basic features such as being able to delete photos Camera app put on SD card.
This is insane.
(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data
Thanks Radek for this!!!
Radek Hulán said:
(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data
Click to expand...
Click to collapse
interesting. i see on some lines there are twrp. so this method can only be used with G4 variants that has twrp? CMIIW
i'd really like to try this on my H818P but there's no TWRP for the variant yet...
Good work mate
Requires root ?
It does not require root, but you must have unlocked bootloader.
Odesláno z mého LG-H815 pomocí Tapatalk
Radek Hulán said:
(connect phone with USB debugging)
adb reboot bootloader
fastboot boot twrp.img
** TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
adb push %USERPROFILE%\build.prop /system/build.prop
adb shell
chmod 644 /system/build.prop
exit
adb reboot
Now you can format SD card as internal storage and use it for data
Click to expand...
Click to collapse
can you explain me what do you mean with
* TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
i dont know it, thanks
Continue working this metod?
Sorry for me bad english xD
[email protected] said:
can you explain me what do you mean with
* TWRP: MOUNT > SYSTEM
** TWRP: Advanced > File > "chmod 775" on system/build.prop
adb pull /system/build.prop %USERPROFILE%
** EDIT FILE, set ro.lge.adoptable_storage=true
i dont know it, thanks
Click to expand...
Click to collapse
Download TWRP for LG G4, run it:
https://twrp.me/devices/lgg4h815.html
In TWRP, select Mount > System, from menu, and continue according to these instructions.
ADB is part of Android SDK tools:
http://developer.android.com/sdk/index.html#Other
I don't know if it is the same problem but I believe it is, so my problem is that I can transfer files from SD to internal but it doesn't work the other way around, I don't want to unlock my bootloader so is there anything else I can do? Thanks
any idea why the G4 is stuck at the Tmobile screen after:
Using the ES root browser and changing the file build.prop manually ( ro.lge.adoptable_storage=true), got the stuck tmobile starts creen
then running the adb commands as per the instructions, then also changing the permission using TWIRP
Nazdar Radku,
the solution is known feature of MM (adopt external storage), but biggest dissadvantage of this, is that you cannot use SD card in other devices anymore - not only in PC using some reader, but not even in other LG-ie your lg g4 broke....no way to get your data back. For some reason LG didnt include this functionality of MM yet. 2nd disadvantage is slowing down your device, as acces, R/W ops are quite slower. And I agree with googles approach to SD card - they want to "protect" users is foolish - you cannot protect stupid people, they should make it as default but keep option for advanced users to access storage as before KK for advanced user as it could be done with KK & LP using that media_rw grp hack.
coolmaster121 said:
any idea why the G4 is stuck at the Tmobile screen after:
Using the ES root browser and changing the file build.prop manually ( ro.lge.adoptable_storage=true), got the stuck tmobile starts creen
then running the adb commands as per the instructions, then also changing the permission using TWIRP
Click to expand...
Click to collapse
I don't think you should ever use a file browser to modify your build.prop. Something about the file being truncated. The modified build.prop ends up being a different size/structure or something along those lines. You should use a dedicated build.prop editor app, or adb commands only. If you had done that chances are you wouldn't have any problems.
IF you have a custom recovery you may be able to restore your original prop file through it in order to get it to boot.
rick09 said:
I don't think you should ever use a file browser to modify your build.prop. Something about the file being truncated. The modified build.prop ends up being a different size/structure or something along those lines. You should use a dedicated build.prop editor app, or adb commands only. If you had done that chances are you wouldn't have any problems.
IF you have a custom recovery you may be able to restore your original prop file through it in order to get it to boot.
Click to expand...
Click to collapse
I resolved the issue by basically booting back in to TWIRP, flashing the stock image again. (didnt loose any files as I didnt do a wipe)
Then ran through the commands from the previous post. But the "set" did not work for me. I then downloaded the build.prop file to the desktop using the "get" command and edited it with wordpad, saved and then sent over the edited file, followed the rest of the permissions and it worked fine then.
Good that you got it figured out but you did it the hard way! All you have to do is download https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Make a backup in the app just in case, then find the entry, make your changes, and reboot. All done on your device.
rick09 said:
Good that you got it figured out but you did it the hard way! All you have to do is download https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Make a backup in the app just in case, then find the entry, make your changes, and reboot. All done on your device.
Click to expand...
Click to collapse
Just tried, it, does not seem to work. it changes the value, says I need to restart, but after restart it goes back to false
Lg G4 SD card as internal storage
Can someone tell me a little more detail on this im new to this and trying to figure it out for myself what software do I need and how to do this to my 2 lg G4's

Categories

Resources