Here's one for the genius'
1. I rooted my phone successfully
2. I edited the settings.db file to allow side apps
3. I copied to copy the original settings.db file (that I think I may have corrupted) back and when I restarted my phone, I get a blank screen.... it will not boot into android.
I have a backup of the original settings.db file, but I need to know if there is there a way that I can copy this file back from recovery mode so that I can boot. I do get command line access in through adb, but it will not let me gain su access. Any help would be great.
I would say just hard reset the phone. It'll restore the settings.db back to the factory one.
masterofthebass said:
I would say just hard reset the phone. It'll restore the settings.db back to the factory one.
Click to expand...
Click to collapse
is it possible to do a hard reset without booting into android? I didn't know about that drats!
systoxity said:
is it possible to do a hard reset without booting into android? I didn't know about that drats!
Click to expand...
Click to collapse
I'm fairly sure there's a way to completely reset the phone while in recovery mode. Haven't done it, but I read about it somewhere.
I did a reset, but the phone still goes blank after the Galaxy logo. If I can mount the sdcard in recovery I think I can fix it. But I can't get it mounted.
take it back and ask for a replacement. Use your imagination.
If this fails and you have a brick phone that you cant do anything with, then i personally would try to open it up and see if that internal microsd card can be removed and hooked up to a card reader. Ofc this is very risky, and i am in no way telling you that you should follow in my theoretical footsteps. Be careful and good luck.
Is there a way to mount the internal sdcard. I have adb access in recovery mode, but not root. I have removable sdcard, but it does not seem to access that one from the recovery mode.
Also, I see the drives in "My Computer", but when I click them they ask me to insert a card. Is there a way to manually mount it from the ADB shell?
you have adb access? So when you have it plugged in and you go to cmd and type adb devices, the phone pops up as connected?
Yes... I have shell access, just can't get root or mount anything. I had already rooted the phone before all this began.
Try this.
Boot into recovery and type this into your computer
"adb shell"
"mount /sdcard"
"exit"
"adb push <whateverfile> /<path>/<whateverfile>"
"adb shell"
"umount /sdcard"
"exit"
I haven't tried this on my phone, but it should work. Please post back if you have any problems.
That will fail because /<path>/<whateverfile> isn't readable/writeable by non-root users (aka adbd). It's /dbdata or something like that, if memory serves.
For the record, booting into recovery mode and clearing all user data will NOT restore a working settings.db. I think the OP is SOL, although I'd love to learn that I'm wrong! :-(
Yeah I tried "mount /sdcard" already.... No luck, it just tells me "usage: mount [-r] [-w] [-o options] [-t type] device directory"
I forgot that you can't get root. The only thing i can tell you is to wait for the dump of the original rom whenever that comes out or take it to your ATT store and tell them it broke.
Mostly new to android, but could you create an update.zip which contains a valid dbsettings file and run it using the bootloader (hold down volume buttons and power up)? Would that then install it to the appropriate place?
If you can't recover the settings.db just take it back to the store and tell them the phone just started booting into a black screen. Leave it at that, turn it on for them to show them it does indeed do that. Then they will exchange it for you because it is so soon after the release date. (ask me how I know) :-/. Always check the db file before you copy it over.
centex99 said:
Mostly new to android, but could you create an update.zip which contains a valid dbsettings file and run it using the bootloader (hold down volume buttons and power up)? Would that then install it to the appropriate place?
Click to expand...
Click to collapse
tbae2 said:
If you can't recover the settings.db just take it back to the store and tell them the phone just started booting into a black screen. Leave it at that, turn it on for them to show them it does indeed do that. Then they will exchange it for you because it is so soon after the release date. (ask me how I know) :-/. Always check the db file before you copy it over.
Click to expand...
Click to collapse
both posts +1
If you can access the phone in adb shell, then you might be able to access the recovery console by going to your computer's command line, getting into the SDK tools folder, and typing "adb shell reboot recovery"
Related
My phone keeps booting into recovery mode.
Power on -> Blank -> Reboot -> Recovery
I had the new SPL (the saphire ported one), JF's recovery (i still have it on) and JF1.51.
This happened since i tried to flash the HTC ADP update.zip.
I have tried using the hardSPL, reflashing the saphire SPL, tried flashing back to JF1.5, Rodgers but nothing seems to work
Any ideas?
EDIT: I just checked and it didnt flash the saphireSPL! i dont think adb shell push is copying the update.zip's to the SD card.
EDIT:
SOLUTION:
I was right in that it wasn't copying the updates to the sd card, i borrowed a friends G1, used it to put on the saphireSPL, flashed (and it worked this time), got into fastboot (the hardSPL fastboot didnt seem to work), and restored my nandroid backups! yey! now to try JAC's build
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
ravenge said:
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
Thank you, that'll come in really handy for when i dont have a spare Dream or card reader about!
ravenge said:
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
Oh my god... this (hopefully) has fixed the problem I've had for the past two days - I've spent so long reading every thread on here about the SPL problems, etc. I had a feeling the problem was the update wasn't working correctly, but I had no idea why. (It didn't complain, but just went very quickly - much to quick to be doing a full os upgrade).
Thanks!!!
umm how would i even run that script?cuz i keep bootlooping
Jerzdre said:
umm how would i even run that script?cuz i keep bootlooping
Click to expand...
Click to collapse
On Phone:
Recovery -> ALT+X -> Console
On PC
Command prompt
"cd <directory where you have update.zip>"
"adb shell mount /sdcard"
"adb push update.zip /sdcard/update.zip"
On Phone
Hold 'Home' and then:
On PC:
"adb shell reboot"
ravenge said:
if you want to adb push in recovery, you'll need to mount the sdcard first or it will appear to have transfered, but actually done nothing.
next time, try
Code:
adb shell mount /sdcard
adb push update.zip /sdcard/update.zip
Click to expand...
Click to collapse
but you can abd push to the ext2 portion of the sd card without mounting while in recovery, correct?
i have my phone updated to 2.1 and rooted. Want to overclock it now but not sure what im supposed to do with the kernel-overclock-update-v3.zip. I have the original PB00IMG.zip i updated and rooted my phone with, am i supposed to use it somehow?? New to this would appreciate any help.
Just use this, Flash it and it will make ur life easyier.
http://forum.xda-developers.com/showthread.php?t=685581
so phone will be stock again right? have to re dload apps and sync contacts and **** again right?
hmm... or u can try to flash the kernel-overclock-update-v3.zip to the one you have
be sure to nand backup first
when i put the kernel-overclock-update-v3.zip on the root of the sd card and power up holding the volume down button it doesn't find the kernel-overclock-update-v3.zip and doesn't install it...? in other word how do i flash it, doesn't seem to be working like when i originally flashed and rooted.
did you flash recovery?
duckingzebra said:
when i put the kernel-overclock-update-v3.zip on the root of the sd card and power up holding the volume down button it doesn't find the kernel-overclock-update-v3.zip and doesn't install it...? in other word how do i flash it, doesn't seem to be working like when i originally flashed and rooted.
Click to expand...
Click to collapse
Hey man,
When you rooted did you flash the Amon-Ra recovery image? If so put the update zip on the root of your sd. Power down your handset. hold the volume UP and the power on will bring you to the recovery menu. Here you have options for back up,flash from zip etc...once there you can select whatever rom/update you want to flash. Remember nandroid is your friend always back up. Also as far as apps etc...check out Titanium back up or one of the other free back up apps in market. I hope this helps you out.
volume up + end button = Recovery
ok, im following the steps to III: Flashing a Custom Recovery. and when i get to the step :adb push recovery.img /sdcard it says :cannot start recovery.img: No such file or directory...is the recovery.img also supposed to gon on the root of my sd card? or just the tools folder, cause its there?
yes its suppose to be on the root of the sdcard too
still says cannot stat 'recovery.img': no such fire or directory
am i supposed to replace /sdcard with /J (which is what my phone comes up as in my computer) -tried that still didn't work...
can u link me to the tut u are using?
http://forum.xda-developers.com/showthread.php?t=647707
QUOTE=TopazAaron]
duckingzebra said:
did you see the tutorial i linked? still cant figure it out.
Click to expand...
Click to collapse
ok
put the Recovery image in the tools/ in the sdk
after that plug ur phone into the comp
now being there in cmd navigate to the /tools/ folder
then type or copy and paste
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
adb push recovery.img /sdcard
adb push flash_image /system/bin
adb shell chmod 755 /system/bin/flash_image
adb shell flash_image recovery /sdcard/recovery.img
---
now if you still have issues, let me know, sorry i didnt reply, i got busy with other things.
thanks for ur pm tho[/QUOTE]
ok now instead of saying :cannot start recovery.img: No such file or directory
it says error: device not found, when i open my computer my sdcard in my phone shows up and i can open it...
That is really wierd, try joining the irc u may get more help there
-------------------------------------
Sent via the XDA Tapatalk App
TopazAaron said:
That is really wierd, try joining the irc u may get more help there
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Sorry newser here, irc??
Is your phone actually rooted? To check, turn on your phone, then turn on USB debugging through Settings/Applications/Development/USB debugging. Plug your phone into the computer via the USB cable.
In the run box of your computer, type cmd, then enter.
When the command window shows up, changed you your SDK tools directory. On my system it would be:
cd c:\android-sdk-windows\tools
Then run the following command
adb shell
You're rooted if it comes back with
#
If it comes back with
$
try the typing
SU
if it does not change from $ to # then you might want to try rooting again, and be sure to install the Amon_RA recovery
typing exit multiple times will back you out of adb, and the cmd window.
Hope that helps.
Edit: Of course that works for 2.1 leak 3 users as well.
Easier way for you tho, if you boot to hboot with the send and end buttons, you should see hboot with S off if you're rooted. If it's S On you're not.
I sadly dropped my nexus 4 on hard tiles yesterday face down and the whole front cracked everywhere! The phone still turns on, I can copy internal storage off fine, but since the touchscreen doesn't work anymore I'm having trouble with getting system data off e.g. sms.
I've managed to get non touch CWM installed, made a nandroid, but now I can't copy the damn thing off! ADB gives me unauthorised for every command, and obviously I can't use the phone to authorise my PC. Am I now essentially screwed? Been googling for ages and can't find a way round the fact I can't use ADB or force my phone to authorise my PC without using the screen.
Any other ideas would be massively appreciated. The phone is rooted, CM10.2, and luckily usb debugging is enabled.
Cheers!!
You said you can copy internal storage right? so why not pull the nandroid from /clockworkmod/backup?
Sent from my Nexus 4 using Tapatalk 4
I do not use CWM, but I do use TWRP and it allow me to access to the /data and /sdcard partition just fine, /system is off limit though. I don't know where your nandroid is backed up in, but I assume its in /sdcard.
Try this: Flash TWRP in fastboot mode, then press the volume button either up or down twice, then press Power to access the recovery. Then on the main menu of TWRP, you can do adb commands right away.
I can then simply back up my whole /sdcard partition by: adb pull /sdcard/ C:\backup
Or backup the all the apps data: adb pull /data/data/ C:\backup
Thank you both for the advice. I've tried using adb in recovery, but it says: remote object '/sdcard' is not a file or directory.
If I type adb devices, I get my phone ID along with 'recovery' next to as expected.
Any ideas?
Thanks.
EDIT: Ignore this, just added a / after /sdcard and now its pulling ok. Thanks so much!
I was typing this up before I read your edit:
If you don't know where certain files are, you can type "adb shell" to enter the phone itself, there you can look at the phone directory structure and find where your files are located.
Use the cd and ls commands to navigate in the phone: http://afrodita.rcub.bg.ac.rs/~ivica/nlm/part1/cd_ls.html
Once you're done, type "exit" to get out of adb shell. Then you can use the "adb pull" command to copy the files.
Hi,
So today the front of my Nexus 4 cracked and rendered it completely dysfunctional. The worst part is that there's a screen lock, making it impossible for me to access through Android File Transfer. I was reading that you could use adb and screencast to access the phone and to unlock it, allowing for me to retrieve files. But after installing and running commands, it seemed like I couldn't find a device when I inputted the command 'adb devices'. I know, I searched it up and I think the reason is that usb debugging was not enabled (I don't remember if I did or didn't enable it at all). I've read past threads which explain how to enable it even with a cracked screen but I'm just too confused on how to do it. All this SDK and AVD stuff confuses the heck out of me (I'm fairly new to the whole Android notion) so I practically have the IQ of a 5 year old. My phone is rooted (In which it did wipe the memory so that may be why debugging could be off) and I'm currently flashing Cyanogenmod. Could someone please explain to me how do I enable debugging with a dysfunctional screen like I'm 5? Also, if there were an easier alternative to retrieving/backing up my files that would be nice knowing too because all of this stuff is currently doing my head in.
Thanks!
You can try to access adb from recovery too.
Turn off phone and start by holding VOL-DOWN and POWER together. You will boot into BOOTLOADER mode and there switch to RECOVERY MODE by VOLUME button (2 times press is this mode). If you have installed CyanogenMOD, then you have probably advanced recovery (CWM or TWRP). Now try command "adb devices".
If you haven't CWM or TWRP recovery installed, boot again into BOOTLOADER mode and flash recovery by fastboot.
xjcook said:
You can try to access adb from recovery too.
Turn off phone and start by holding VOL-DOWN and POWER together. You will boot into BOOTLOADER mode and there switch to RECOVERY MODE by VOLUME button (2 times press is this mode). If you have installed CyanogenMOD, then you have probably advanced recovery (CWM or TWRP). Now try command "adb devices".
If you haven't CWM or TWRP recovery installed, boot again into BOOTLOADER mode and flash recovery by fastboot.
Click to expand...
Click to collapse
Thanks for the quick reply,
After I hit advanced recovery and selecting my backup, which option do I press? Do I restore the boot, system, data, cache, or sd-ext?
Also typing in adb devices only lists the recovery device and I don't seem to be able to access it through Android File Transfer, what do I do with the serial number it tells me?
By the way I don't have any backups when I had no screen pattern so wouldn't recovering those areas still give get me locked out?
loolnicetry said:
Thanks for the quick reply,
After I hit advanced recovery and selecting my backup, which option do I press? Do I restore the boot, system, data, cache, or sd-ext?
Also typing in adb devices only lists the recovery device and I don't seem to be able to access it through Android File Transfer, what do I do with the serial number it tells me?
By the way I don't have any backups when I had no screen pattern so wouldn't recovering those areas still give get me locked out?
Click to expand...
Click to collapse
Android File Transfer is not working in recovery mode, but you can pull required files by "adb pull /sdcard/some-file-or-folder/ /to/some/path/on/your-system/". Of course you can pull whole /sdcard/. You can try also adb backup (I didn't try it yet). From recovery you can also make nandroid backup of the system and transfer to computer by adb pull.
In recovery mode you have access to full system (maybe you must mount some partitions), that means you can use magic command "adb shell", to get shell (in shell you can use "ls" for list files, "cd" for change directory) and do what you want. To remove screen lock try some guide from XDA, I've found for example [GUIDE][HOW-TO]Crack android pattern lock! or [EASIEST]Crack Android Pattern/Pin/Password Lockscreen without root.
I hope this will help you.
xjcook said:
Android File Transfer is not working in recovery mode, but you can pull required files by "adb pull /sdcard/some-file-or-folder/ /to/some/path/on/your-system/". Of course you can pull whole /sdcard/. You can try also adb backup (I didn't try it yet). From recovery you can also make nandroid backup of the system and transfer to computer by adb pull.
In recovery mode you have access to full system (maybe you must mount some partitions), that means you can use magic command "adb shell", to get shell (in shell you can use "ls" for list files, "cd" for change directory) and do what you want. To remove screen lock try some guide from XDA, I've found for example [GUIDE][HOW-TO]Crack android pattern lock! or [EASIEST]Crack Android Pattern/Pin/Password Lockscreen without root.
I hope this will help you.
Click to expand...
Click to collapse
I CANNOT THANK YOU ENOUGH! You were easy to understand and got straight to the point which was perfect! On a side note, do you know if there's a way I can extract and save my sms messages and read them on my computer? I know I can take out the .db file but it's complicated to open on a Mac and it's quite an effort. (Considering my phone still has a lock on it)
loolnicetry said:
I CANNOT THANK YOU ENOUGH! You were easy to understand and got straight to the point which was perfect! On a side note, do you know if there's a way I can extract and save my sms messages and read them on my computer? I know I can take out the .db file but it's complicated to open on a Mac and it's quite an effort. (Considering my phone still has a lock on it)
Click to expand...
Click to collapse
I'm really happy that I helped you!
Android is storing messages, contacts in SQLite database, there is not another way to grab these files from recovery. But it's not complicated to extract these files. Download for Mac OS X sqlite-shell-osx-x86-XXX.zip from SQLite Download Page and extract it somewhere.
Then pull messages by
Code:
cd /path/where/is/extracted-sqlite
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db .
Finally you can list your messages by
Code:
./sqlite3 mmssms.db 'select address,body from sms'
If last command is not working try make it executable and repeat previous step
Code:
chmod +x sqlite3
xjcook said:
I'm really happy that I helped you!
Android is storing messages, contacts in SQLite database, there is not another way to grab these files from recovery. But it's not complicated to extract these files. Download for Mac OS X sqlite-shell-osx-x86-XXX.zip from and extract it somewhere.
Then pull messages by
Code:
cd /path/where/is/extracted-sqlite
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db .
Finally you can list your messages by
Code:
./sqlite3 mmssms.db 'select address,body from sms'
If last command is not working try make it executable and repeat previous step
Code:
chmod +x sqlite3
Click to expand...
Click to collapse
For the pulling of the .db file, it says the remote object does not exist, what should I do?
loolnicetry said:
For the pulling of the .db file, it says the remote object does not exist, what should I do?
Click to expand...
Click to collapse
Hmm that is strange, maybe this will help you (especially check first answer): http://stackoverflow.com/questions/12266374/backup-full-sms-mms-contents-via-adb
Sent from my Nexus 4 using Tapatalk
xjcook said:
Hmm that is strange, maybe this will help you (especially check first answer):
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
When I try to enter the $mkdir command it says it's not found. Am I meant to include the $ in the command?
xjcook said:
Hmm that is strange, maybe this will help you (especially check first answer): http://stackoverflow.com/questions/12266374/backup-full-sms-mms-contents-via-adb
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I FIXED IT MYSELF! I'm feeling a bit smart haha, it turns out my system and data wasn't mounted and all I had to do was mount it through cwm. Thanks a lot friend you were a great help, I'd be panicking a substantial amount without you!
[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