Database Users

how to disable light sensor in stock rom

this light sensor is really pissing me off , is there any way to shut it off , i'v found a way that is telling me to chmod 777 the patch file after installing it manually but idon't know what chmod 777 is and how to do this please help me

Is stock eclair there isn't a GUI option to disable it.
About chmod 777, I haven't done it yet... but I guess you have to adb shell something.
To know how to use those commands, just have a click on the search button...

maveloth said:
Is stock eclair there isn't a GUI option to disable it.
About chmod 777, I haven't done it yet... but I guess you have to adb shell something.
To know how to use those commands, just have a click on the search button...
Click to expand...
Click to collapse
i searched and found nothing please help it's pissing me off for real !! se u suck i bought this phone because of it's design but their software update service sux !

I have found what you were looking for [just search in devs forum].
Here it is an explaining link:
http://forum.xda-developers.com/showthread.php?t=888232

maveloth said:
I have found what you were looking for [just search in devs forum].
Here it is an explaining link:
http://forum.xda-developers.com/showthread.php?t=888232
Click to expand...
Click to collapse
thanks i found this thread before but i can't apply this method because i don't know how to chmod777 the file so i can't get this to work ? can you try it and then tell me how to exactly do it please , thanks again m8

First thing, you have to learn how to adb shell.
But you have to make everything ok before using it.
So, let's see how it has to be done..
Download the .zip file posted on the other thread [linked above].
Using root explorer, just copy and paste the content of the .zip file under the /etc/ path of the phone.
After you have done this, let's adb shell.
1. Download this file: http://db.tt/cq44S4v
2. Extract the adb.zip file to C:\adb [there will be a folder named "adb" within the C:\ path, with 3 files within it].
3. On your phone, click Settings > Applications > Development, and make sure USB Debugging is on.
4. Plug your phone into your computer via USB cable [it needs to be on]. It should say installing drivers if your phone is plugged for the first time and you are using Windows.
4.1 You'd better install the drivers which comes with X8 software [PC Companion], or just google for them.
5. After it installs the drivers, go to the Start menu and type "cmd" into the search bar to open the command prompt.
6. Type the following into the command prompt window [hitting enter at the end of every line]:
Code:
cd\
cd adb
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set.
After all this procedure, you can finally "chmod" your files.
Always from the CMD, type this:
Code:
adb shell
You should see a "#" on the left. That's good.
Now enter the path with the file to chmod:
Code:
cd /etc
Then finally chmod it:
Code:
su chmod 777 hw_config.sh
You're done.
Hope this helps.

maveloth said:
First thing, you have to learn how to adb shell.
But you have to make everything ok before using it.
So, let's see how it has to be done..
Download the .zip file posted on the other thread [linked above].
Using root explorer, just copy and paste the content of the .zip file under the /etc/ path of the phone.
After you have done this, let's adb shell.
1. Download this file: http://db.tt/cq44S4v
2. Extract the adb.zip file to C:\adb [there will be a folder named "adb" within the C:\ path, with 3 files within it].
3. On your phone, click Settings > Applications > Development, and make sure USB Debugging is on.
4. Plug your phone into your computer via USB cable [it needs to be on]. It should say installing drivers if your phone is plugged for the first time and you are using Windows.
4.1 You'd better install the drivers which comes with X8 software [PC Companion], or just google for them.
5. After it installs the drivers, go to the Start menu and type "cmd" into the search bar to open the command prompt.
6. Type the following into the command prompt window [hitting enter at the end of every line]:
Code:
cd\
cd adb
adb devices
You should see a serial number pop up, it’s the serial number of your phone. This means you are all set.
After all this procedure, you can finally "chmod" your files.
Always from the CMD, type this:
Code:
adb shell
You should see a "#" on the left. That's good.
Now enter the path with the file to chmod:
Code:
cd /etc
Then finally chmod it:
Code:
su chmod 777 hw_config.sh
You're done.
Hope this helps.
Click to expand...
Click to collapse
lol it's freaking hard , thanks for your help m8 i appreciate it is there any easier way?

Have you tried installing Spare Parts from the market. I know it has light sensor tweak option plus has tons of other useful tweaks and monitors.
Sent from my I7500 using Tapatalk

Master Darko said:
Have you tried installing Spare Parts from the market. I know it has light sensor tweak option plus has tons of other useful tweaks and monitors.
Sent from my I7500 using Tapatalk
Click to expand...
Click to collapse
tried it still no use , the sensor is still working !!

Trying to root but can't get ADB working

I've finally decided to try to root my G2 but can't get past the ADB setup. I downloaded the SDK, but when I open the manager and try to install platform tools it goes through the motions and then tells me nothing was installed. When I open a command prompt and type "ADB devices" it doesn't recognize anything. What am I doing wrong??
EDIT: specifically, when I try to install platform-tools it tells me it couldn't create a directory and nothing was installed.

66 people have read this and nobody has any suggestions to help?

i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....

I have a problem after rebooting my PC: <Java not found...> Reinstalling doesn't help, adding environment variables too. Any idea?

Just root using the rage/visionary method. No adb needed and very easy to do. Here is the linkhttp://forum.xda-developers.com/showthread.php?t=834228
Sent from my SilverBullet 'HTCDesireZ running CM7'

juvanni said:
i think you miss the 1st procedure....
you must have the unknown resources and the usb debbuging enabled.....
then you can proceed to your super one click rooting.....
Click to expand...
Click to collapse
I don't understand? I'm trying to root following the recommended wiki instructions, and I haven't been able to get adb to work so I haven't gotten past that step.

Are you running windows x64? Cause the android installer has issues detecting java on x64 systems.
When it says 'Can't find java' or whatever the error is, click back, then next again, it should find it the second time around. Well thats what happened for me anyway.
-Nipqer

If you're on froyo just use the app z4 root or universal androot
You can also use superoneclick root 2.11
Its very easy and it only take about 3 minutes
Stewie just said that!

I appreciate the help so far, but my problem is I have gingerbread and everything I've read requires froyo for root, and the only way I've read to downgrade uses ADB, so any non-ADB rooting method still won't work for me. I've followed the "ADB for dummies" thread and the other instruction thread and everything seems fine, but when I type in the first command for the downgrading it says adb isn't a recognized command. Am I in the wrong command prompt? I feel like its probably something really dumb I'm doing or not doing but for the life of me I can't figure it out.

Navigate to the folder adb is in.
Hold shift, right click in the folder (make sure nothing is selected)
select 'Open command window here' (or something along those lines)
Adb should work.
-Nipqer

OK, so I'm definitely in the right folder, I read and followed ADB for Dummies thread. Trying to follow this direction:
"Run the following command to verify the exploit has access to what it needs. (Only the first line is the command. The second line should be the result returned if all goes well.)
Code:
$ adb shell cat /dev/msm_rotator
/dev/msm_rotator: invalid length"
When I type that in, should there be spaces between the "adb" and "shell"? Should there be a space after the command prompt and before "adb"? I've tried several variations of it and it keeps telling me "adb is not recognized as an internal or external operable program or batch file."

ok you need to run the command from the folder with adb.exe in it, type it as adb<space>shell<space>cat<space>/dev/msm_rotator
If you are getting an error search for adb.exe and once found try the command again from this folder,if as you say you are in the right folder then I think you will have to reinstall adb as I just ran the command in the form above and it works so if you still get an error then something has gone wrong with the install
P.S Another way to make sure that adb is working and recognises your phone is to type adb devices, if your phone is attached and recognised then it will return a number

Thank you! I had to uninstall and reinstall the package, I don't know what was wrong but it seems to be working now. Also, I knew I was probably doing something stupid, and I was. I wasn't in the platform-tools directory for my command prompt, I was in the TOOLs directory. Just so I'm clear, every command I type into the terminal should be in the Platform-tools directory, correct?
Now, assuming I can follow all the other directions with no problems, once I get to the downgrade pushing steps, I will lose all my current settings, right? It will be a fresh froyo 2.2 like it came to me originally? Other than using Appbrain to back up my current apps, how else should I make a backup?
Final question, do I need to follow the temp root directions and push the downgrade all at one time? Or can I do the temp root and come back at a later time to push the downgrade?

First problem solved then!
Yes but follow this Step 4
Now we need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone).
On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to your Path "c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !)if you want to.
Once done you can use ADB from the command prompt in ANY folder,very handy IMO.
If I was you I would set aside enough time and see it through,no point to temp rooting alone.
Get Titanium backup from the market an absolute essential app with this you can backup,upload to dropbox(Another essential app) uninstall apps and a host of other useful tools.
Read the guide first as well,good luck.

Messed up my Nexus 4 :(

Guys i have a problem...
I wantes to delete all data on my N4 and start again with a fresh device, My phone is rooted and i had an custom rom installed, i deleted all data pictures and everything else, after that i also formated the sd card, cache etc etc and thats where it went wrong Now i can go into cwm but nothing more... when i reboot i see the black screen with google on it and after that nothing happens...
How can i solve this problem? I hope that i didnt bricked my phone

should still be able to mount usb storage in cmw, that or push files using adb, if you can get into recovery then you can always get your device back

I just helped a user with the same problem yesterday.
Here's the link with steps how to push a rom to your phone with adb: http://forum.xda-developers.com/showthread.php?t=2137976

can you get into fastboot? if you can then all you have to do is follow this thread:
http://forum.xda-developers.com/showthread.php?t=2010312

coffmad said:
should still be able to mount usb storage in cmw, that or push files using adb, if you can get into recovery then you can always get your device back
Click to expand...
Click to collapse
No, you can't mount USB in recovery. The Nexus 4 does not use UMS.

Ok thanks for the fast reply, im gonna try to push a rom with adb.

''I know you don't have a rom on your phone. This is how you can push one to your phone.
You must be booted in recovery
Put the rom in the same directory on your PC where you have adb.exe
Open up the command prompt from that directory. (hold shift and right click--then choose open command window here)
Then type the command-- adb push nameofrom.zip /sdcard/
The file with push to your phone and then your can select it and flash it from recovery''.
I see this in another thread, Where can i find adb.exe? Im terrible with computers...

Adb is part of of the platform tools for android. Since you unlocked and flashed a custom rom you should have it on your computer.
If you need it, it is located as an attachment at the bottom of this post: http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1

I got the attachment, its called platform tools v16, i dragged and dropped an rom in that platform tools file and after that i dont know what to do...
''Open up the command prompt from that directory. (hold shift and right click--then choose open command window here)
Then type the command-- adb push nameofrom.zip /sdcard/''
This is what i dont understand.

Mr Djoegoe said:
I got the attachment, its called platform tools v16, i dragged and dropped an rom in that platform tools file and after that i dont know what to do...
''Open up the command prompt from that directory. (hold shift and right click--then choose open command window here)
Then type the command-- adb push nameofrom.zip /sdcard/''
This is what i dont understand.
Click to expand...
Click to collapse
Extract the files in that .zip into a folder and name it something like "Android."
Move the Rom.zip into that folder as well.
Then do the shift and right click and open the command window pointed to that directory. (as I explained above)
Make sure its connected properly and there isn't a driver issue by typing the command: adb devices. If it returns your serial number you are good to go. (If not, you need to install the correct drivers, which are linked in Section A of the post I linked earlier.)
Then type the command. adb push nameofRom.zip /sdcard/

When i type adb devices i can see my serial number and recovery after it.. when i type ''adb push nameofRom.zip /sdcard/ '' i get a message cannot stat 'nameofRom.zip' No such file or directory
What am i doing wrong?
Edit: hahahaha i see what i do wrong nameofRom.zip

Are you actually typing "nameofrom.zip" ?
Sent from my Nexus 4 using xda app-developers app

Mr Djoegoe said:
When i type adb devices i can see my serial number and recovery after it.. when i type ''adb push nameofRom.zip /sdcard/ '' i get a message cannot stat 'nameofRom.zip' No such file or directory
What am i doing wrong?
Click to expand...
Click to collapse
You replace "nameofRom" with the name of your ROM your trying to push

moses992 said:
Are you actually typing "nameofrom.zip" ?
Click to expand...
Click to collapse
hahaha Yes!
@El Daddy: Thanks for your help Im gonna donate a bottle of wine :good:

Mr Djoegoe said:
hahaha Yes!
@El Daddy: Thanks for your help Im gonna donate a bottle of wine :good:
Click to expand...
Click to collapse
Thanks for that. Unneeded, but very appreciated!
Sent from my Nexus 7 using Tapatalk HD

You certainly haven't bricked it. The fact you can get to recovery means, you can get to fastboot. Simply open fastboot and reflash stock and be more careful next time

[Q] How to push file using TWRP adb sideload and Nexus 4 Toolkits

Hi everybody
Today I've just messed up my phone by deleting all TWRP backups as well as ROM zip files on my N4 (haven't found out why i did it, hell!)
Now after wipe my current rom, I've totally in the middle of "NoRom"
I have TWRP, and Nexus 4 Toolkits installed on my PC. I think all drivers are installed correctly as well, since I used them to unlock bootloader and root my N4 before.
But i just cannot figure out how to "ADB sideload" zip file to my device in order to flash a new rom.
So please guild me to do this. Many thanks
Note: I read on TWRP page and they say that I have to enable adb sideload in TWRP on my N4 (of which i've done), then "From the command line, type adb sideload /path/to/rom.zip". From that point I cannot understand. How and where could I open the command line?
(sounds noobie but since downloading that Toolkits, I've got rid of pure ADB things, so now I don't have the sdk)
Thank you.

Lol, getting rid of ADB especially when you have a nexus was a bad idea. You need ADB, so you also need the SDK (although you *might* find only adb.exe and associated files here on XDA, which should be sufficient for this particular process, but I still recommend the SDK as it is quite handy).
Once you set up the SDK on your pc, go to the folder which has adb.exe, and open a command prompt there. That's the command line you need to use for adb sideload. From there, you can simply type adb sideload file_name.zip, which will place the file_name.zip on your sdcard.
Edit: Forgot to mention this. I never used toolkits and advise using the manual method which will teach you a lot and is more comfortable to use once you get the hang of it, believe me.
Sent from my Nexus 4 using Tapatalk 4 Beta

Spiralzz said:
Lol, getting rid of ADB especially when you have a nexus was a bad idea. You need ADB, so you also need the SDK (although you *might* find only adb.exe and associated files here on XDA, which should be sufficient for this particular process, but I still recommend the SDK as it is quite handy).
Once you set up the SDK on your pc, go to the folder which has adb.exe, and open a command prompt there. That's the command line you need to use for adb sideload. From there, you can simply type adb sideload file_name.zip, which will place the file_name.zip on your sdcard.
Edit: Forgot to mention this. I never used toolkits and advise using the manual method which will teach you a lot and is more comfortable to use once you get the hang of it, believe me.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
OK thank you, i'll try it
Back to the past when i got G1, i was familiar with sdk and adb thing. But as time passing by, i'm getting lazier and lazier lol, so i've almost forgotten those useful stuffs, just use some 1-click tools like the toolkits.

Help
Spiralzz said:
Lol, getting rid of ADB especially when you have a nexus was a bad idea. You need ADB, so you also need the SDK (although you *might* find only adb.exe and associated files here on XDA, which should be sufficient for this particular process, but I still recommend the SDK as it is quite handy).
Once you set up the SDK on your pc, go to the folder which has adb.exe, and open a command prompt there. That's the command line you need to use for adb sideload. From there, you can simply type adb sideload file_name.zip, which will place the file_name.zip on your sdcard.
Edit: Forgot to mention this. I never used toolkits and advise using the manual method which will teach you a lot and is more comfortable to use once you get the hang of it, believe me.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried sideload on my nexus 4 but it gives me this error...
"failed to write data 'protocol fault (no status)"
I have been trying to sideload cm 10.2 since my phone is stuck on the google boot logo...any ideas as to how to solve this problem?
Cheers beforehand!

close "adb.exe" in task manager

Help please. I've done the same thing as the OP. I do not know what to do next.
I am unable to mount the phone. I click on "Mount" from TWRP's main screen and nothing registers on my computer.
Under Advanced I am able to click on ADB Sideload but then the adb commands do not work to sideload a rom. I am able to use the command adb devices and that returns a response. I have also tried the adb push command to move the rom onto the phone with no response.
What should I do next?

Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app

Alex240188 said:
Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks that worked.

Alex240188 said:
Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hey bro it says device not found. what do i do?
---------- Post added at 09:46 PM ---------- Previous post was at 09:43 PM ----------
Alex240188 said:
Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have clockworkmod recovery v6.0.1.9 it didnt work for me it said device not found
---------- Post added at 10:37 PM ---------- Previous post was at 09:46 PM ----------
Alex240188 said:
Standard adb functions work on the main menu of twrp
Here is the easiest method.
On your pc go to your toolkit directory
Find the folder that has adb.exe in it
Copy your new Rom to this directory and rename it rom.zip (for simplicity)
Hold shift and right click on a blank bit of the folder
In the pop-up menu there should now be an option saying "open command prompt here" or something similar.
Boot your phone into twrp and plug it into your pc
On your pc's new command prompt screen type
adb push rom.zip /sdcard
Once it has completed you can install the rom as normal on your phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Hey Thank i got it working, but one thing i cant understand is i got in a boot loop cause install cm10.1.3 RC2 coming from cm 10.2 nightly version, i also flased gapp 4.2.2 assuming the rom was 4.2.2 that why. is this correct? i wanna go to cm10.1.3 RC2 current on 10.2 nightly how can i do this? which gapps should i install?

Do you have adb drivers installed?
What happens when you type
adb devices
In the command prompt
You should get the serial number of your phone, then next to it it should say recovery
If you have nothing listed then you have an issue with the drivers on your computer
Sent from my Nexus 4 using xda app-developers app

Hi,
I moved from slimbean build 8 (4.2.2) to Slimbean 5 (4.3)
After a couple of reboot the phone stucks an google screen, I tried to reflash the rom from twpr but nothing chaged.
If I try to sideload small files (like supersu) it works, with rom.zip files not..
I have "* failed to write data 'protocol fault (no status)' *" after some seconds.
If I try to use sideload from twpr home (2.6.0.0) adb doesn't work,
adb devices
List of devices attached
0076a0288a8c04be recovery

Cwm
Is it possible to do the same with Cwm instead of twrp? If so, how? Also, i have both twrp and cwm according to rom manager. How?

Thanks your a life saver!
Alex240188 said:
Do you have adb drivers installed?
What happens when you type
adb devices
In the command prompt
You should get the serial number of your phone, then next to it it should say recovery
If you have nothing listed then you have an issue with the drivers on your computer
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse

HElp
Hi guys,
I had the same problem while trying to install a new rom and i got into a bootloop stuff.
I tried what its say before on this thread but my phone can't be found. what can i do ?
Excuse my english i'm French.
Thx for your help if somebody can help me.

i run adb push rom.zip /sdcard but it tells me: cannot stat 'rom.zip': No such file or directory
I know that my drivers are installed and i can see my device when i run adb devices. Thank you for any help i can get.

Jens_Karlsson said:
i run adb push rom.zip /sdcard but it tells me: cannot stat 'rom.zip': No such file or directory
I know that my drivers are installed and i can see my device when i run adb devices. Thank you for any help i can get.
Click to expand...
Click to collapse
being a noob at all of this, I am getting nowhere..... all I did so far was install android sdk. and put phone into sideload....
when I did adb push rom.zip /sdcard and it did some things?
then I do adb devices (in the cmd line of windows) and it gave me my serial number.... but what now?
I see nothing on the phone to load/install?
also: I type this: adb push rom.zip /sdcard
it says error closed.

Even i have been caught up with this same problem , and i found this thread which was pretty helpful
HTML:
http://forum.xda-developers.com/showthread.php?t=2318497
that saved my day !!

I have the same problem
I have the same issues. When i type adb devices in command prompt, I get
List of devices attached
(there are nothing under it) what should i to ? Help me please

Install http://koush.com/post/universal-adb-driver
Report back if still having issues.

help!!!!!
I get this but now what???
C:\adb> adb push rom.zip /sdcard
_
Nothing more and in my phones sd its the rom but failed when i tried to install it

[Solved!] G2 Soft Brick due to Incompatible Bootanimation.zip (Thx karandpr!)

[Original post has been removed, and replaced with the following updated information]
Hi there fellow G2 users! Unfortunately, I have made a foolish mistake and now I badly need your mighty super-brains over here at XDA to help me out!
Let me start out by saying I have an LG G2 VS980 (3aa) on Lollipop 5.0.2
Now all I wanted to do was change the boring boot animation that displays on startup with one that was more neato. So I did a simple google search and found a guide which instructed me on how to do so. It had me install a "one click root" APK file, and then install it and run it - which apparently rooted my phone and gave me access to my system folder. I then went into my /system/media/ folder and renamed the original bootanimation.zip (to bootanimation-og.zip) and replaced it with a new bootanimation.zip. Everything was perfectly fine until I rebooted my phone a few hours later. It was then that I discovered that I had accidentally used a bootanimation.zip for another phone, and it was not compatible with mine! Total face palm, I know!
So now when I power up my phone, it quickly flashes that (bad/incompatible) image before going straight to a blank screen that does not allow me to do anything. Not good at all, guys! So after doing TONS of hunting around on google and a couple other forums, I still have not been able to fix it. At first, nothing was working. However, after several hours of fiddling around with things, I have finally managed to get ADB to recognize my device again! So I have made a little bit a progress.
After getting ADB to work, I did something which was suggested on a guide I found on Google - which was to use ADB to "pull" the bad file from the system folder. So I went into the command prompt and issued the "pull /system/media/bootanimation.zip" command, and it worked, sort of, I think? It ended up pulling everything out of my /system/media/audio folder, as well as the bootanimation.zip, bootanimation-og.zip, and shutdownanimation.zip files - and placed them into a folder called "bootanimation.zip" inside my ADB folder. Unfortunately, after trying to reboot my phone, it did not solve the problem. The same blank screen happens.
So then, following another guide which recommended I try "pushing" the original bootanimation.zip back into my system folder, I tried just that. I opened the command prompt and issued the "adb shell" command, followed by the "su" command - and this is where I get stuck. It shows me the #root access, but it does not allow me to type anything. I assume this is because SU is trying to display the "permission? option" on my phone - but I cannot ACCEPT it because of my blank screen issue.
I also tried booting into TWRP without installing it (using the method listed in THIS guide under "Installing TWRP"). After placing the "recovery.img" into my ADB folder and trying the "adb reboot bootloader" command, followed by the "fastboot boot recovery.img" command - it simply gets stuck saying <Waiting for device>.
So here I am, completely bamboozled. A couple of people and/or pages I have visited have suggested that I just flash back to stock using KDZ, but I have a couple of concerns regarding that. First, when I go to the "LG G2 : Go Back to Stock" guide here on XDA, it says I have to flash the same firmware that I had been using previously. When I go to the link provided to download the firmware, under the Verizon folder there are only 2 firmwares listed: "Verizon VS98024A_11.kdz" and "Verizon VS98027A_05.kdz" - neither of which are the firmware my phone was using, which was "VS9803AA" - So I am unsure if I would even be able to use this method? And second, I was really hoping I would be able to fix this without losing my data, so I would REALLY like to be 100% sure that there are no other solutions to my issue before I resort to reverting back to stock.
So this is where I hope you guys and your brilliant minds can swoop in and save me from my troubles! Is there ANYTHING I can do to save my phone, by replacing that stupid incompatible bootanimation.zip file with the original one - without wiping back to stock? If any of you are able to help me, I would be sooooo forever grateful! I will patiently await your responses. Thank you guys SO much in advance for any help you may be able to provide.
Much appreciative,
Terri (Psy)
(A very special thanks to @KennyG123 and @karandpr for the help they have attempted to provide thus far!)

PsyintZ said:
Hi guys!
I have made a serious mistake, and I feel so stupid! I was wondering if any of you awesome people at XDA would be able to save me.
I have an LG G2 vs980 Lollipop 5.0.2
So, all I wanted to do was change my startup screen to get rid of that boring LG logo and replace it with something neater. I went over to Google and found a guide on how to do this, and followed the steps 1 by 1. Everything actually worked out perfectly, but it wasn't until after I was locked out of my phone that I realized that I had used a startup image that was not compatible with my LG G2! (Total face palm!). Now, whenever I power my phone, it flashes that "neat" image that I replaced the stock one with - before the screen goes completely blank and I cannot do anything at all. That's not good!
So my question is this - Is there a way I can access my system folder without having access to my phone? I know EXACTLY what file I need to remove/edit to solve this problem! In fact, that is what is frustrating me the most. It's not some random error message out of the blue that I know nothing about. I know exactly what the problem is, I just don't know if I have access to the solution. I just really hope I don't have to wipe everything back to stock all because of a lousy startup image.
Is there a way to access the system folder on my phone so I can remove the bad file and replace it with the stock image so I can get my phone working again? If anybody can help me figure out the best method to solve this issue, I would be forever grateful! Thank you guys so much in advance!
Much appreciative,
Terri (Psyintz)
Click to expand...
Click to collapse
If you are rooted you should be able to swap the files using ADB
http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Good luck!

KennyG123 said:
If you are rooted you should be able to swap the files using ADB
http://www.droidviews.com/push-pull-files-android-using-adb-commands/
Good luck!
Click to expand...
Click to collapse
The problem with guides like this is they all have that step that says "First, you must enable USB Debugging" - which requires USB access to my phone to do. Granted, it is already enabled because I had to enable it during the process of changing out my startup image - but that makes me think it needs access to a connected device in order to work properly. And I cannot connect to my device when it locks up before booting. Whenever I try to utilize an adb command, it returns the message "error: device (null) not found."
So, I guess my question is - is it still possible to use commands like these when my phone cannot boot up and give USB access to adb?

I am beginning to lose faith in there being an option to solve this problem without just performing a factory reset, and losing all of my data. If I were to take this route, can I just use my phone's built-in option? By holding the correct keys, and then choosing to wipe all my data and return to stock?

PsyintZ said:
The problem with guides like this is they all have that step that says "First, you must enable USB Debugging" - which requires USB access to my phone to do. Granted, it is already enabled because I had to enable it during the process of changing out my startup image - but that makes me think it needs access to a connected device in order to work properly. And I cannot connect to my device when it locks up before booting. Whenever I try to utilize an adb command, it returns the message "error: device (null) not found."
So, I guess my question is - is it still possible to use commands like these when my phone cannot boot up and give USB access to adb?
Click to expand...
Click to collapse
If your screen is blank it is difficult to see if the phone is asking permission to allow the USB connection. That is most likely the problem. If you have a custom recovery on your phone you may be able to flash a ROM of the same Android version and not lose your data.

KennyG123 said:
If your screen is blank it is difficult to see if the phone is asking permission to allow the USB connection. That is most likely the problem. If you have a custom recovery on your phone you may be able to flash a ROM of the same Android version and not lose your data.
Click to expand...
Click to collapse
I'm pretty sure I do not have a custom recovery thing installed. I do not remember installing one. I simply installed a "one click root" thing via an APK file, and once that was installed, I went into my /system/media folder and renamed my bootanimation.zip file to boonanimation.zip.backup, and then put in the new (bad/incompatible) bootanimation.zip file. Those were the only steps I performed. Since it appears I will not be able to use ADB to "pull" this bad file out, and most likely will have to wipe everything and go back to stock - can I just use the built in "factory reset" option that came with my phone (by holding the volume up + power keys at the same time)? Will this just wipe everything and put my phone back to how it was when it was brand new?
Very sorry to bug you guys with all of this. I feel like such a goofball. I just wish I could get everything back to normal
Thank you guys very much for your help. I really appreciate you taking the time to help me out.

Making Progress?
Okay guys. I think I may have some good news. After a LOT of fiddling around, I managed to get ADB to see my device! When I use the "adb devices" command, it finally returns my phone's address. That's the good news.
The bad news is, upon the suggestion of a forum member, I attempted to use the "adb pull /system/media/bootanimation.zip" command to try and yank the bad file out of my system folder. It ended up pulling the entire /system/media/audio folder (and all files contained within), as well as bootanimation.zip, bootanimation.zip.backup (the original file that I turned into a backup), and shutdownanimation.zip. All of those files are now sitting in my adb folder (waiting to be put back in their spots if I can ever get back on my phone). The problem is, it didn't solve the problem. When I power on the phone, it still quickly flashes the incompatible image before going to the same blank screen.
So, I think I have made some progress. But unfortunately, the pull command did not solve the problem. Now that ADB is able to see my device, is there more that I can do? What would you guys recommend I do next in order to try and solve this issue?

Type the following commands
adb shell
$ bootanimation stop
OR
adb shell
$ su
# rm /system/media/bootanimation.zip
#mv /system/media/bootanimation.zip.backup bootanimation.zip
This might work if shell has root privileges only though ...

karandpr said:
Type the following commands
adb shell
$ bootanimation stop
OR
adb shell
$ su
# rm /system/media/bootanimation.zip
#mv /system/media/bootanimation.zip.backup bootanimation.zip
This might work if shell has root privileges only though ...
Click to expand...
Click to collapse
Hi karandpr! Thanks for your help! Unfortunately, no luck yet.
I can get into the "adb shell" just fine. However, when I type "bootanimation stop" it returns "/system/bin/sh: bootanimation: not found." And when I issue the "su" command, it puts me into the root access thing where it says "[email protected]:/ #" - but then I am unable to type anything here. I am presuming this is because it is probably asking my phone for SU Permission, only I am not able to Accept it because of my blank screen.
I'm stumped again! I do feel like I'm getting closer to fixing it, though. I just hope these aren't.... false hopes.

PsyintZ said:
Hi karandpr! Thanks for your help! Unfortunately, no luck yet.
I can get into the "adb shell" just fine. However, when I type "bootanimation stop" it returns "/system/bin/sh: bootanimation: not found." And when I issue the "su" command, it puts me into the root access thing where it says "[email protected]:/ #" - but then I am unable to type anything here. I am presuming this is because it is probably asking my phone for SU Permission, only I am not able to Accept it because of my blank screen.
I'm stumped again!
Click to expand...
Click to collapse
Do you have monitor.bat in the adb folder ?
You can see your device connected.
use the screen capture option and see if the screen is replicated on your device.
can you try this command .
adb push bootanimation.zip.backup /system/media/bootanimation.zip
also while you can use adb pull to pull all your user data ...

karandpr said:
Do you have monitor.bat in the adb folder ?
You can see your device connected.
use the screen capture option and see if the screen is replicated on your device.
can you try this command .
adb push bootanimation.zip.backup /system/media/bootanimation.zip
also while you can use adb pull to pull all your user data ...
Click to expand...
Click to collapse
I do not see monitor.bat in the adb folder.
And when I try the push command, I get "failed to copy 'bootanimation.zip' to '/system/media/bootanimation.zip': Read-only file system" - and I think I remember encounting this on another guide as well. The problem lies when trying to use the adb shell and the "su" command to mount the system drive as read+write. I get to the point where I have root access, but an unable to type the mount command because I think it is asking my phone for SU permission, and I am unable to grant it permission. Ugh! So close yet so far - and still so frustrating! You are awesome for taking the time to help me, though! Is there some way I can credit you to show my appreciation?

PsyintZ said:
I do not see monitor.bat in the adb folder.
And when I try the push command, I get "failed to copy 'bootanimation.zip' to '/system/media/bootanimation.zip': Read-only file system" - and I think I remember encounting this on another guide as well. The problem lies when trying to use the adb shell and the "su" command to mount the system drive as read+write. I get to the point where I have root access, but an unable to type the mount command because I think it is asking my phone for SU permission, and I am unable to grant it permission. Ugh! So close yet so far - and still so frustrating! You are awesome for taking the time to help me, though! Is there some way I can credit you to show my appreciation?
Click to expand...
Click to collapse
Get the full android tools from here.
https://dl.google.com/android/repository/tools_r25.2.3-windows.zip
monitor.bat should be in tools folder after you extract them.
Quick question: Does your adb work again if you reboot phone ?
if your adb works after a reboot then can you run this command and see if screen lights up
adb shell stop

karandpr said:
Get the full android tools from here.
https://dl.google.com/android/repository/tools_r25.2.3-windows.zip
monitor.bat should be in tools folder after you extract them.
Quick question: Does your adb work again if you reboot phone ?
if your adb works after a reboot then can you run this command and see if screen lights up
adb shell stop
Click to expand...
Click to collapse
Okay, I am downloading those tools and will install them shortly. I'm not sure if I understand what you mean by "work again if I reboot my phone?" Could you be a little bit more specific for my newbie mind? I apologize for sucking at this! Lol

PsyintZ said:
Okay, I am downloading those tools and will install them shortly. I'm not sure if I understand what you mean by "work again if I reboot my phone?" Could you be a little bit more specific for my newbie mind? I apologize for sucking at this! Lol
Click to expand...
Click to collapse
Lets say your adb is working now.
You remove the battery and start the phone again.
Will you be still able to access adb or not ?

karandpr said:
Lets say your adb is working now.
You remove the battery and start the phone again.
Will you be still able to access adb or not ?
Click to expand...
Click to collapse
Yeah, I believe so. For example: I power it on and let it flash the incompatible image resulting in the blank screen. Then I perform an "adb devices" check and it returns my Phone ID. Then I hold power down until the phone resets, and displays the bad image again resulting in a blank screen. I then perform another "adb devices" check and it still returns my Phone ID. If that is what you were checking for, then yes, it appears to continue working after a reboot.
Also - my download of those tools is complete. I have unzipped the Tools folder to my desktop. Would it be okay to copy the entire contents over to my adb directory? Or is that a bad idea?

PsyintZ said:
Yeah, I believe so. For example: I power it on and let it flash the incompatible image resulting in the blank screen. Then I perform an "adb devices" check and it returns my Phone ID. Then I hold power down until the phone resets, and displays the bad image again resulting in a blank screen. I then perform another "adb devices" check and it still returns my Phone ID. If that is what you were checking for, then yes, it appears to continue working after a reboot.
Also - my download of those tools is complete. I have unzipped the Tools folder to my desktop. Would it be okay to copy the entire contents over to my adb directory? Or is that a bad idea?
Click to expand...
Click to collapse
Open that folder in desktop
the go to tools folder and you will see monitor.bat
Just run it
on a side note
run
adb shell stop
and see what happens

karandpr said:
Open that folder in desktop
the go to tools folder and you will see monitor.bat
Just run it
on a side note
run
adb shell stop
and see what happens
Click to expand...
Click to collapse
Alright. When I run "Monitor.bat" it pops up a window asking me to "Provide the path to the Android SDK" - What shall I enter here?
And regarding the "adb shell stop" command - when should I enter that? Just right now, while it's sitting on the blank screen?

PsyintZ said:
Alright. When I run "Monitor.bat" it pops up a window asking me to "Provide the path to the Android SDK" - What shall I enter here?
And regarding the "adb shell stop" command - when should I enter that? Just right now, while it's sitting on the blank screen?
Click to expand...
Click to collapse
yes right now when sitting on blank screen ...
The path to android sdk is path to desktop where you extracted the folder ...

karandpr said:
yes right now when sitting on blank screen ...
The path to android sdk is path to desktop where you extracted the folder ...
Click to expand...
Click to collapse
Okay. After running the "adb shell stop" command - it appeared that nothing happened. It just went back to the standard "C:\adb>" line.
And after pointing Monitor to my desktop/tools folder, it said that wasn't a valid path. So I searched my computer for "sdk" and it found a folder with that label in Users/AppData/Local/Android/sdk - so I pointed it to that. After doing this, it ran and showed my device in the column to the left, but at the bottom it said it could not connect, and kept trying saying "Attempt 1 (Failed)... Attempt 2 (Failed).. etc..." - so I closed it, and then closed all of my other windows (including my ADB command prompt) in case any of those would be causing a conflict. And now upon re-opening it, it longer lists my device in that column on the left. Just my luck - I already broke it.

PsyintZ said:
Okay. After running the "adb shell stop" command - it appeared that nothing happened. It just went back to the standard "C:\adb>" line.
And after pointing Monitor to my desktop/tools folder, it said that wasn't a valid path. So I searched my computer for "sdk" and it found a folder with that label in Users/AppData/Local/Android/sdk - so I pointed it to that. After doing this, it ran and showed my device in the column to the left, but at the bottom it said it could not connect, and kept trying saying "Attempt 1 (Failed)... Attempt 2 (Failed).. etc..." - so I closed it, and then closed all of my other windows (including my ADB command prompt) in case any of those would be causing a conflict. And now upon re-opening it, it longer lists my device in that column on the left. Just my luck - I already broke it.
Click to expand...
Click to collapse
Try rebooting phone ....
If you get android shell again
do
adb shell
$ stop
$ start