Develop Bugs

can not mount system in read-write mode using adb without recovery mode

I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.

maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop

ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:

THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.

error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?

jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?

i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help

ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help

dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]

[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 ?

[GUIDE]Swap Internal Memory to External & Vice Versa

The Xperia M sure packs a lot in such a small device, but then, does it pack enough internal memory to install a huge number of applications? It does not. With just a little over 2 GB, it is very cumbersome to find that you cannot download data for large games. This guide aims to resolve that issue. Although it is not very user friendly at the moment (it requires you to type a few lines on the phone), I will get back to creating a script that you can execute this weekend.
Note: This guide requires you to be rooted. For rooting, you can follow this guide.
Step 1: Setting up stuff
Find and download a suitable file explorer that allows you to modify and browse system files. I recommend Root Explorer. (Optional)
Download and install Terminal Explorer from the Google Play Store.
Download and install Script Manager from the Google Play Store. (Optional)
Step 2: Walking the path
Open Terminal Emulator and type in
Code:
su
Your root manager should request you for permission. Grant the app superuser permission.
Type in
Code:
vold
Press enter
Type in
Code:
mount -t vfat -o umask:0000,uid=1000,gid=1023 /dev/block/vold/179:33 /storage/sdcard0
Press enter.
Type in
Code:
mount -o bind /data/media /storage/sdcard1
Press enter.
Click to expand...
Click to collapse
And, that's it! You're almost done. Go to Settings > Storage and check the internal and external storage to see that they have been mounted. You can now install huge games and enjoy them on your M. This is a temporary workaround until this weekend as I will write a script to automate this once my exams are over. If anyone else wants to do it, they're welcome to!
Note: You will have to type this again every time you reboot the device. A bit cumbersome, but I hope you can hold on till the weekend.
Credits:
 @darz
 @raw235
 @mattiadj
 @Ace King 34

not work in FW XM Dual
how to swap internal and external in FW XMD ?

@gadgetroid , will it work in Xperia M Dual 4.2 ?

It Worked!!!
gadgetroid said:
The Xperia M sure packs a lot in such a small device, but then, does it pack enough internal memory to install a huge number of applications? It does not. With just a little over 2 GB, it is very cumbersome to find that you cannot download data for large games. This guide aims to resolve that issue. Although it is not very user friendly at the moment (it requires you to type a few lines on the phone), I will get back to creating a script that you can execute this weekend.
Note: This guide requires you to be rooted. For rooting, you can follow this guide.
And, that's it! You're almost done. Go to Settings > Storage and check the internal and external storage to see that they have been mounted. You can now install huge games and enjoy them on your M. This is a temporary workaround until this weekend as I will write a script to automate this once my exams are over. If anyone else wants to do it, they're welcome to!
Note: You will have to type this again every time you reboot the device. A bit cumbersome, but I hope you can hold on till the weekend.
Credits:
@darz
@raw235
@mattiadj
@Ace King 34
Click to expand...
Click to collapse
Worked for me
13 GB internal storage

aerialus said:
not work in FW XM Dual
how to swap internal and external in FW XMD ?
Click to expand...
Click to collapse
I will need your help for that. If you can use ADB and pull these files for me and zip and upload here, it would certainly be very helpful.
Pull the folder "/dev/block/vold"
Open Terminal Emulator that you downloaded and run these scripts
Code:
cat /proc/partitions > partitions
Press enter
Code:
mount > mount
Then, on the computer, open a command prompt window (or terminal on Linux) and type in
Code:
adb pull /partitions
Code:
adb pull /mount
Put these two files in the zip along with the vold folder and post them here. I will look into it and provide you the guide.
jereMarfil24 said:
@gadgetroid , will it work in Xperia M Dual 4.2 ?
Click to expand...
Click to collapse
Since it runs 4.2, I can't be very sure, as Sony may have changed device names. Once the above user submits the files, I will look into it and post the guide.

gadgetroid said:
I will need your help for that. If you can use ADB and pull these files for me and zip and upload here, it would certainly be very helpful.
Pull the folder "/dev/block/vold"
Open Terminal Emulator that you downloaded and run these scripts
Code:
cat /proc/partitions > partitions
Press enter
Click to expand...
Click to collapse
i never use ADB ,, but i will try,,
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?

Did u written su above?
Sent from my C1904 using Tapatalk 4

aerialus said:
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?
Click to expand...
Click to collapse
Perhaps you aren't rooted. That is why the script in the OP didn't work for you either.
When you type in su in the terminal, do you get any prompt on your phone?
Or perhaps it could be that you haven't rooted the device completely. You need busybox for making any operations on the ~/ partition.

gadgetroid said:
Perhaps you aren't rooted. That is why the script in the OP didn't work for you either.
When you type in su in the terminal, do you get any prompt on your phone?
Or perhaps it could be that you haven't rooted the device completely. You need busybox for making any operations on the ~/ partition.
Click to expand...
Click to collapse
my device is already rooted and have Busybox installed,,
please look at my attachment

aerialus said:
my device is already rooted and have Busybox installed,,
please look at my attachment
Click to expand...
Click to collapse
Have you used root fixer? As mentioned by the OP of the root thread? If you have ES File Explorer, just try mounting the system partition as r/w over there. If it reboots immediately, then you aren't rooted properly yet.

aerialus said:
i never use ADB ,, but i will try,,
when i do
Code:
cat /proc/partitions > partitions
in terminal emulator, the result is "can't create partitions: read only file system"
what is my fault?
Click to expand...
Click to collapse
If I understand right the command will create the files "partitions" and "mount" directly into the root path that's why it claims "r/o file system"
try
Code:
cat /proc/partitions > [COLOR="Red"]/sdcard/[/COLOR]partitions
and pull it on your computer then with
Code:
adb pull [COLOR="red"]/sdcard/[/COLOR]partitions
same with "mount"
this should create those files into the sdcard which is not read only.

gadgetroid said:
Have you used root fixer? As mentioned by the OP of the root thread? If you have ES File Explorer, just try mounting the system partition as r/w over there. If it reboots immediately, then you aren't rooted properly yet.
Click to expand...
Click to collapse
in XM Dual no need use rootfixer anymore,,
just root with tools and success full root,,
magicw said:
If I understand right the command will create the files "partitions" and "mount" directly into the root path that's why it claims "r/o file system"
try
Code:
cat /proc/partitions > [COLOR="Red"]/sdcard/[/COLOR]partitions
and pull it on your computer then with
Code:
adb pull [COLOR="red"]/sdcard/[/COLOR]partitions
same with "mount"
this should create those files into the sdcard which is not read only.
Click to expand...
Click to collapse
ok i will try :fingers-crossed:

Yes. That is exactly what it does. It works if you put in sdcard

Script
I have created a script for this. If OP gives me permission i can publish it.

pull partitions and mounts success,,
but when i try to pull folder "/dev/block/vold"
the result is " 0 files pulled, 0 files skipped"
see my attachment

icoolguy1995 said:
I have created a script for this. If OP gives me permission i can publish it.
Click to expand...
Click to collapse
Sure, go ahead. Publish it. Are you sure its working? Cause when I created a script, it used to give me errors. That is why I posted this huge tutorial.

gadgetroid said:
Sure, go ahead. Publish it. Are you sure its working? Cause when I created a script, it used to give me errors. That is why I posted this huge tutorial.
Click to expand...
Click to collapse
I have attached the script in attachments.
STEPS TO EXECUTE
1) Download script
2) place it in SD card and open any Explorer in which you can change permissions.
3) Go where you have placed script and change its permission (Thick all the boxes)
4) Execute it.
But it will last till a reboot only
Simple Way
1) Download script manager from play store
2) Execute script with it and tick the boot,su option and tick it is executable.
Your memory is swapped

icoolguy1995 said:
I have attached the script in attachments.
STEPS TO EXECUTE
1) Download script
2) place it in SD card and open any Explorer in which you can change permissions.
3) Go where you have placed script and change its permission (Thick all the boxes)
4) Execute it.
But it will last till a reboot only
Simple Way
1) Download script manager from play store
2) Execute script with it and tick the boot,su option and tick it is executable.
Your memory is swapped
Click to expand...
Click to collapse
I'll add it to the op soon. BTW, if you place the script in /data folder and set it to rw-r--r--, it will be easier. That way, the script won't be in the wrong drive after it's been switched.

No it will not work unless all the options are ticked on permission setting.

icoolguy1995 said:
No it will not work unless all the options are ticked on permission setting.
Click to expand...
Click to collapse
It works for me with rw-r--r--
This message was brought to you by my Sony Xperia M (C1905), using the XDA app.

[GUIDE] Unlock LS980 ZVD (KK 4.4.2) [UPDATED 8/10/14]

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.

Replacing Boot Animation Without Rooting

Can someone check if this method works to replace stock bootanimation without rooting the device?
Disclaimer: I am not responsible for bricking device or bootloop. Also, note that modifying /system will break OTA update. So, please try it at your own risk.
1. Download any bootanimation and make sure to change the name to bootanimation only. You can get it from here. Link: https://forum.xda-developers.com/android/themes/alienware-t3721978 (Credit goes to @mauam)
2. Go to device settings/Developers option and turn on USB debugging
3. Make sure you have ADB tool installed properly in your computer.
4. Connect your device to the computer using the USB cable.
5. Now open ADB tool folder and paste the bootanimation zip file here.
6. On the same ADB folder, press shift+right click and open command box.
7. Type: adb shell mount /system
8. Now type: adb push bootanimation.zip /system/media
9. Type: adb shell umount /system
10. Type: adb shell reboot
I am not sure if it will work for Mi A1 (I can't test as I no longer have an Mi A1), but it works perfectly on my Nokia 7plus.

Rowdyy Ronnie said:
Can someone check if this method works to replace stock bootanimation without rooting the device?
Disclaimer: I am not responsible for bricking device or bootloop. Also, note that modifying /system will break OTA update. So, please try it at your own risk.
1. Download any bootanimation and make sure to change the name to bootanimation only. You can get it from here. Link: https://forum.xda-developers.com/android/themes/alienware-t3721978 (Credit goes to @mauam)
2. Go to device settings/Developers option and turn on USB debugging
3. Make sure you have ADB tool installed properly in your computer.
4. Connect your device to the computer using the USB cable.
5. Now open ADB tool folder and paste the bootanimation zip file here.
6. On the same ADB folder, press shift+right click and open command box.
7. Type: adb shell mount /system
8. Now type: adb push bootanimation.zip /system/media
9. Type: adb shell umount /system
10. Type: adb shell reboot
I am not sure if it will work for Mi A1 (I can't test as I no longer have an Mi A1), but it works perfectly on my Nokia 7plus.
Click to expand...
Click to collapse
Yes, I habe tried it now and it works, the bootanimation is in the system/media folder, why wouldn't ot work? Lol

Haxomen said:
Yes, I habe tried it now and it works, the bootanimation is in the system/media folder, why wouldn't ot work? Lol
Click to expand...
Click to collapse
Because you can't modify system files without root

jigs4wkiller said:
Because you can't modify system files without root
Click to expand...
Click to collapse
I am not rooted and it worked, how?

jigs4wkiller said:
Because you can't modify system files without root
Click to expand...
Click to collapse
That's why we are mounting the system partition to push the bootanimation.zip into /system/media

Haxomen said:
I am not rooted and it worked, how?
Click to expand...
Click to collapse
have you unlocked bootloader?

I haven't tried it and I will not try it.
But if you can push it into the system and It doesn't work, try setting correct permissions for the files after pushing it.

Rowdyy Ronnie said:
That's why we are mounting the system partition to push the bootanimation.zip into /system/media
Click to expand...
Click to collapse
Yes I know but when you try to override other files it will not work that's why I'm a bit confused.