Related
Somehow I let my ritual of deleting my messages get away from me and now I have an inbox with over 2k messages...and I can delete none of them. Anytime I try my app (both the stock one and handcent) lock up and become non responsive.
Any advice?
So, I got impatient and did a data wipe (i backed up first). It obiviously got rid of my messages. But I decided that I don't like losing everything else, so I tried to restore my backup. No go. It returns something about needing to run it in the console?
The more advice I could get at this point, the better...
I have a fix for this that I helped brock do. I knew I should have made it public. lol. One day too late! I'll post it here in a little bit.
Edit:
So yea I too have noticed that when trying to delete large threads (500+ texts) it will typically FC. Sometimes if I click "wait" enough it will eventually delete, however 1000+ threads never seem to go. This work around will wipe ALL of your threads, however it's much better than wiping your entire phone. The best advice I guess would be to just clear them out every 250 texts or so.
These instructions are for windows. If you have mac or linux then you'll just need to change the parts about pulling the db from the phone.
Code:
mkdir c:\temp
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db c:\temp (this will backup the database to your computer at c:\temp, just in case)
adb remount
adb shell
rm /data/data/com.android.providers.telephony/databases/mmssms.db
reboot
Let me know if you have any problems. Maybe I should add this is a fix in my apps installer program, just like clearing the cache.
Flip, you are a wizard! Thank you!
hello ive got exactly the same problem i have atleast 5k messages in on thread and cant delete them i dont understand what to do with that code you have put up flipzmode can you shed some light on it for me please .
Connect your phone via USB.
Bring up command prompt (or terminal if in osx or Linux)
Change directory to where you're adb is and then input flip's commands.
nvm got it wewt~
and adding this to app installer would be hot~
Permission Denied
I am Getting a "permission Denied" after i Type in the command, "adb pull /data/data/com.android.providers.telephony/databases/mmssms.db c:\temp"..... phone is rooted and i did verify that the phone is pulling up in the bridge... Any help is greatly appreciated
i had to do this: (just put in w/e drive your adb is on if it isnt a H~ more then likely a C drive)
cd H:\android-sdk-windows\tools
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db H:\temp (this will backup the database to your computer at H:\temp, just in case)
adb remount
adb shell
rm /data/data/com.android.providers.telephony/databases/mmssms.db
reboot
all this is complete jiberish to me im not very compouter literate with these codes etc been trying for ages to figure it out and delete these messages its really doing my head in now
cant delete sum msgs how n where do i put that code so i can delete msgs over +1000
sprint hero messages
still cannot get this to work, i have changed the dir to F but i still get errors that says adb is not a rec. internal or ext command
plz help
I had the same problem (about 1600 messages for one contact) I set the phone's display to never turn off so it wouldn't go to "sleep" then I clicked delete on the thread and walked away for about 15 minutes and it eventually deleted. It seemed like the screen turning off and going to the lock screen is what was making the messaging app unresponsive.
riotkid976 said:
Connect your phone via USB.
Bring up command prompt (or terminal if in osx or Linux)
Change directory to where you're adb is and then input flip's commands.
Click to expand...
Click to collapse
What is "Abd"? It is not recognizable in my command prompt!! Please help!!! Thanks!!
I'm adding this in to my kitchen so it can be done with the click of a button. I'll post here when it's released.
Fresh is Sick
Thanks Fresh i definitely that was the easiest way to delete the threads and it worked great. Can't wait for the next best thing you put out there!
SOO glad I found this thread. My girlfriend doesn't even have this phone but this thread has solved her issue with her mms.apk force closing. This needs to be pinned or something.
I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
This is the exact path I had used in the past, even following the .txt instructions that have worked for me in the past.
Yes in am in debugging, charge only, partition mount showing "unmount /system" like it has in the past. Does this have anything to do with what packages I updated when I was messing with SDK emulator?
duckredbeard said:
I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
This is the exact path I had used in the past, even following the .txt instructions that have worked for me in the past.
Yes in am in debugging, charge only, partition mount showing "unmount /system" like it has in the past. Does this have anything to do with what packages I updated when I was messing with SDK emulator?
Click to expand...
Click to collapse
Go into the directory and see if there is a file called adb in there...if it's not check the other folders like tools or something like that i'm at work so i don't know the exact name of the directories...
duckredbeard said:
I did a few things the other day in SDK, messing around with emulators. Now I can't get adb to work.
I keep getting this:
c:\AndroidSDK>adb
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
This is a PC error message stating that the file adb.exe is no longer in the AndroidSDK directory. As zervic mentioned, check and see if the file adb.exe is in that directory.
We're onto something...there is no adb in the AndroidSDK folder. So where do I get this adb? I did the SDK so long ago, like 5 months. Don't remember a thing about it and consider myself lucky that I got it going back then, piecing together youtube videos and several forums.
duckredbeard said:
We're onto something...there is no adb in the AndroidSDK folder. So where do I get this adb? I did the SDK so long ago, like 5 months. Don't remember a thing about it and consider myself lucky that I got it going back then, piecing together youtube videos and several forums.
Click to expand...
Click to collapse
Just reinstall (or unzip if I remember right) the Android SDK into that directory
I started the "update all" in the "installed packages" window. If that doesn't fix it, I shall follow your advice.
Edit: The "update all" didn't fix it.
I found the .zip and extracted it to my c:\AndroidSDK folder, but still a nogo. I also tried copying adb.exe straight to the AndroidSDK folder, still a nogo.
Anything else to try?
When I copied adb.exe to the tools folder and tried adb in cmd prompt, I got "This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem"
Are they telling me to uninstall SDK and start over? Like I said, I was lucky to get it going the first time!
Smack myself in the head while I Edit: Found the AdbWinApi.dll in the zip and copied it to the tools folder. Adb runs now and recognizes my device. Later I will find out if I can rm some stock apps from my wife's new phone.
Thanks for your help in this matter.
duckredbeard said:
I found the .zip and extracted it to my c:\AndroidSDK folder, but still a nogo. I also tried copying adb.exe straight to the AndroidSDK folder, still a nogo.
Anything else to try?
When I copied adb.exe to the tools folder and tried adb in cmd prompt, I got "This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem"
Are they telling me to uninstall SDK and start over? Like I said, I was lucky to get it going the first time!
Smack myself in the head while I Edit: Found the AdbWinApi.dll in the zip and copied it to the tools folder. Adb runs now and recognizes my device. Later I will find out if I can rm some stock apps from my wife's new phone.
Thanks for your help in this matter.
Click to expand...
Click to collapse
Just so you know that may be a little unstable. It may be worth your while to check the "platform-tools" folder and see if adb is in there, i believe that's where it is by default and it also may be worth your while to run adb from that folder instead of where you jerry rigged it to run. But, on the other hand, it may work the way you have it. You never know. Just figured I'd throw that out there.
While rooting my Nook Color, I came across a recommendation for a free app in the market called adbWireless.
It's AWESOME! No need to use USB or worry about drivers, just install the app, push the big huge button and then type the adb command it shows you to connect to your device. Worked absolutely perfectly on my Nook... haven't tried it on my Aria, but next time I need to ADB something on it, you can bet I will!
did anyone check their tools directory?
ie: C:\android-sdk-windows\tools
LOL
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.
Hello all,
I have 5.0.1 stock rooted, with few mods.
So I wanted to backup all my storage because I haven't done it in a while and because 5.1 is coming so just in case something goes wrong I would still have backup.
But, here is the problem:
I don't use MTP because its slow and cuts off all the time(It's not the cable, I tried using other cables same cutting off)
So for a while I have been using adb pull command to pull files with:
adb pull /sdcard/ C:\Backup
or
adb pull /storage/sdcard0/ C:\Backup
All good for now, started to pull but I realized it's not pulling everything, it's just pulling my music, .mp3 files.
So I saw that, but didn't wanted to stop it I let it do it's work.
After 30-40 min cmd window just closed and it didn't pull whole music folder. So I tried it again, same thing, but the windows didn't close and it didn't even said: x files pulled. x files skipped.
I tried copy files using MTP and copy-paste to my backup folder, but it was just stuck on Calculating copying time and that window just closed and it didn't copy my storage, just a few folders.
Anybody know solution?
Bump
zEr0Punk said:
Hello all,
I have 5.0.1 stock rooted, with few mods.
So I wanted to backup all my storage because I haven't done it in a while and because 5.1 is coming so just in case something goes wrong I would still have backup.
But, here is the problem:
I don't use MTP because its slow and cuts off all the time(It's not the cable, I tried using other cables same cutting off)
So for a while I have been using adb pull command to pull files with:
adb pull /sdcard/ C:\Backup
or
adb pull /storage/sdcard0/ C:\Backup
All good for now, started to pull but I realized it's not pulling everything, it's just pulling my music, .mp3 files.
So I saw that, but didn't wanted to stop it I let it do it's work.
After 30-40 min cmd window just closed and it didn't pull whole music folder. So I tried it again, same thing, but the windows didn't close and it didn't even said: x files pulled. x files skipped.
I tried copy files using MTP and copy-paste to my backup folder, but it was just stuck on Calculating copying time and that window just closed and it didn't copy my storage, just a few folders.
Anybody know solution?
Click to expand...
Click to collapse
I hear so many reports that MTP file transfers are unreliable.
I guess I am just a lucky dog or maybe it's because I usually MPT from TWRP instead of Android,
but I've never experienced a single file transfer failure. Push or pull.
If your having issues with ADB pull command not working correctly. Maybe that would explain MPT failures too?
I'd suggest re-doing your ADB drivers if you are certain its not your cable or USB ports.
I FIXED IT I saw some music tracks with weird lettering in it, like: ã€â…
And I renamed it, and it copied the whole storage to my pc
I don't know why it didn't had issues before, because that song has been long time on my N4.
Am just glad I fixed the problem
[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