Related
I figured I would post this fix here in case anyone else ran into this problem. This is assuming you did not change the folder names and let Clockworkmod create them. I haven't had it happen until today, but it's not a nice message to see when you are trying to do a restore.
Code:
Checking MD5 sums...
MD5 mismatch!
To fix this problem use the code below. Substitute the final folder name for the backup you need to fix.
Code:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
When that finishes, re-run the restore and everything should be fine.
NOTE: As rpearl stated, there could be something really wrong with your nandroid, so use this tutorial as a learning experience and not a fix-all. In my case, everything was fine after restoring. However, that may not always be the case. Do this with caution.
I had a md5 mismatch and was freaking out. Turned out that the folder name for my backup couldn't have spaces in it...
This also works for anyone that wants a to make a 100% stock image but keep recovery.
just replace the boot.img and system.img with the ones from the RUU and recalc.
i just got this problem. do i need the "#" for each command?
Any idea what causes this? Is it just the folder name with spaces?
zeke1988 said:
i just got this problem. do i need the "#" for each command?
Click to expand...
Click to collapse
No the # simply means you are logged in as root or Su
If its showing $ then you may need to type /system/bin/Su
I believe or could be /system/lib/su I'm still pretty new to Linux / Android
Sent from my ADR6300 using Tapatalk
s197 said:
Any idea what causes this? Is it just the folder name with spaces?
Click to expand...
Click to collapse
Spaces aren't allowed but it could also be caused by corrupted data or sometimes even simply renaming the folder
Sent from my ADR6300 using Tapatalk
Be warned: If the nandroid was legit broken, then this will restore it *anyways* and your system won't boot / will have weird errors / whatever was wrong with the nandroid will be wrong with your system now.
Obviously you can just restore a previous nandroid if that happens.
i did this and still cant fix the md5. making me to use the older backup
For n00bs could you elaborate on this post, i'm having the same problem.
"To fix this problem use the code below"
I know this is through cmd, but what needs to be where when i'm typing exactly that in (changing the folder name etc) what screen do I need to be on. If it was more detailed, and thank you so far because this is the only post on the net, it could be very useful!
jinkzuk said:
For n00bs could you elaborate on this post, i'm having the same problem.
"To fix this problem use the code below"
I know this is through cmd, but what needs to be where when i'm typing exactly that in (changing the folder name etc) what screen do I need to be on. If it was more detailed, and thank you so far because this is the only post on the net, it could be very useful!
Click to expand...
Click to collapse
If you're messing with nandroid backups by now, we'd hope you would know how to get adb shell started.
So basically you start up adb shell in a command prompt on your computer, this connects to your phone, then you follow those commands following "adb shell"
A brief overview of getting to the adb commands >> http://forum.xda-developers.com/showthread.php?t=709220
permission denied error
I'm using windows 7 CMD to connect to my hero for resolving this md5 mismatch issue.
But when i type in the last command, which is -
md5sum *img > nandroid.md5
it gives me an error -
md5sum: permission denied
I tried running the cmd as administrator also but I dont know in windows how to do a 'SU' like in ubuntu.
can you please give a tip what to do ?
Sean.
Ok wow you guys rock thanks this works great.
THANK YOU!!!!!!!!!!!!!
I had this happen to me today... I woulda had to spend a crapload of time getting things all set up on my phone if I hadn't found this thread. It was my fault, I changed the name of the Nandroid backup folder... I had no idea you couldn't do this.... went to restore and BOOM MD5 mismatch.... noooooooooooo.
Thank you again OP for posting this you really saved my day today.
Jacked up Dell Streak/ US ver. build 6601 MD5 Checksum error
After screwing up my brand new Streak, I turned to XDA and MoDaCo to fix my screw-ups. Read this and did that, and nothing would work. The buttons would flash the Dell logo would come up and freeze. So here is another solution that worked for me Step by step.
Installed the fast boot using Windows 7 64 bit I downloaded Fastboot and followed there instructions. Not sure what it did for me, but I did it.
Now as the phone was, I was unable to do any kind manipulation of the SD card. I tool the micro SD card and put it into an SD adapter and added the files via my lap top. See instructions here
Technically you don't need to worry about flashing cache.img and data.img but i performed this backup after a factory reset so your not taking any of my personal info/data
fasboot didn't work for me for so i restored with nandroid
Nandroid
+Create a folder named "Clockworkmod" on your storage card
+In that folder create a folder named "backup"
+Create a folder in "backup" named whatever you want and place boot.img, system.img, cache.img, data.img, recovery.img and nandroid.md5 in that folder.
+Flash Clockworkmod Recovery
2.5.0.1 didnt work on mine but 1.8.1.7 did :/
+Enter clockworkmod recovery
-Power on device while holding both volume keys, then select "2. Software upgrade via Update.pkd on SD Card"
Now you should be in ClockworkMod Recovery
-Scroll down to nandroid using the volume keys and press the camera button to select it
-Select Restore and choose your folder (the one you placed in the backup folder)
thanks fone_fanatic 28th August 2010, 03:14 AM
DO NOT PUT ANY SPACES IN YOUR FILE STRUCTURE. I did and it gave me an "MD5 Check Sum Error" took the space out and bam it worked.
Rebooted the phone and so far every thing works. GPS, WiFi etc and no dam flashing lights or self reboots or O2 stuff Hope this helps ya....Good luck you will need it.
Ihtfp69 to the rescue again!
Man, I can never repay you for how much you've helped me out and saved my bacon! Other dev's, take note, this is an exemplary developer here and his SkyRaider rom is beyond compare!
seansin said:
I'm using windows 7 CMD to connect to my hero for resolving this md5 mismatch issue.
But when i type in the last command, which is -
md5sum *img > nandroid.md5
it gives me an error -
md5sum: permission denied
I tried running the cmd as administrator also but I dont know in windows how to do a 'SU' like in ubuntu.
can you please give a tip what to do ?
Sean.
Click to expand...
Click to collapse
I do not have ABD on my Win 7 machine so I had to use CMD as well. I too received an error, however mine basically said that md5sum was not a recognized command. Not sure where you got md5sum for your win 7 machine, but I got mine at the following website... (fourmilab.ch/md5/) and this one worked just fine. Unzip and copy md5.exe to the system32 folder.
If you are still working through this... good luck. Hopefully it can be helpful to someone else either way. --Josh
OMG ihtfp69!! You're a life-saver!
cscimmia said:
I do not have ABD on my Win 7 machine so I had to use CMD as well. I too received an error, however mine basically said that md5sum was not a recognized command. Not sure where you got md5sum for your win 7 machine, but I got mine at the following website... (fourmilab.ch/md5/) and this one worked just fine. Unzip and copy md5.exe to the system32 folder.
If you are still working through this... good luck. Hopefully it can be helpful to someone else either way. --Josh
Click to expand...
Click to collapse
Hmmm...I just used md5sum from the phone's shell. No need to get anything for Windows.
hey i tried the steps you guys gave buy i get
# cd /sdcard/clockworkmod/backup/2010-10-30.08.23.53
cd: can't cd to /sdcard/clockworkmod/backup/2010-10-30.08.23.53
this is what i did.
I opened terminal in OSX and typed "adb shell" after that i typed "cd /sdcard/clockworkmod/backup/2010-10-30.08.23.53" but it didnt work.
anyone know what i did wrong??
i also did "adb devices" in terminal and it detects my device. i check the su on my sgs and i see my computer, it sees it as unknown.
Alright, I faced this problem a few days backed, and when I did my research I found that a lot of people face this problem, or once in a while at least:
When you try to do a nandroid restore you see this:
Error: run ' nandroid- mobile. sh restore ' via console!
So you try to do it via adb (aka console) and you get this:
Error: unable to mount /sdcard, aborting
Frustrating right! You have messed up your phone while tweaking and thought you had the upper hand because you did a back-up.. but now you are dealing with this..
Here's the solution I gathered from web:
1. Check that you have USB de-bugging on under the development settings of your phone
2. Check that you have your sdcard partitioned to at least ext3.
3. Check that you did not rename your nandroid folder, nandroid's content to anything fanciful.
4. Check that you have enough power on your phone, at least 30 percent to be safe. Low power will disable the ability to do a restore in some cases.
Well if you don't have the above:
1. Go enable USB de-bugging under settings>manage applications>development>USB Debugging>activate.
2. Transfer whatever content you have on sdcard to somewhere safe. Then do a proper partitioning via the recovery, upgrade it from ext2 to ext3. Repair the ext in case there are some errors. After this, transfer all contents back.
3. Please rename all folders back to their original name, and don't rename them ever again.
4. Charge your phone with AC supply, and wait till it is at least 30 percent and try to do a restore again via recovery, if not, do step 1 - 3.
Trying to do a restore:
1. Do it via recovery, if everything is fine, it should go smoothly, and you got your upper hand back!
2. If you like to see words running in strings, doing via console is possible too!
-
"quoted from and credit to Slug from android forums"
Open a command prompt window (Start-All Programs-Accessories-Command Prompt)
Type cd/ and hit <enter>
Enter cd adb
Now enter adb devices and it should show "000000000000 recovery"
If so, enter adb shell and you should see the prompt change to #. You're now running as su (root)!
Enter nandroid-mobile.sh --restore. You'll see instructions about "Using G1 keyboard..." disregard and hit <enter>.
After a brief search, the default (most recent) backup found will be displayed along with any others located. If the default choice isn't the one you want to restore, you'll have to enter the full path to the correct one as displayed in the list. You can use the Edit...Mark... function from the command prompt window menu to simplify this, though. Put the cursor at the beginning of the required line, hold <shift> and highlight the test using the arrow keys. <Enter> copies to the clipboard, and Edit... Paste... places it wherever the cursor is placed.
Once you have the correct backup referenced, hit <enter> and you should see the script work its magic.
When Restore done is displayed you can reboot the handset from the recovery menu.
Alright you have got your restore back! Feedback or anymore tips to this problem are welcome! Thank you for your time.
JokerAce
so if we renamed the nandroid backup to something we will remember more easily, and that the problem, what do we do?
edit: how do we know what the original name of the backup was called.
Hi, did you get a Md5 mismatched or something? Please be clear with your problem. If it's a mismatch problem, make sure your rename'd folder has NO Space in the name.
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.
I am not a developer or even smart. I poked around until I found something that worked for me. Use at your own risk.
I rooted and installed CM 7.0.2 in the past and was pretty happy. When 7.1.0 came out I took the leap. Everything was great except for GPS. GPS did not connect at all. Nothing I did could bring it back other than going back to stock rom. After much frustration and fighting I have it working.
Many people said to make changes to the /system/etc/gps.conf. The problem I had was S-ON was preventing it and nothing I could find explained a work-around. Sorry if I missed it.
I am going to explain what I did to get it going.
Phone details:
- My phone is rooted and CM7.1 installed.
- S-ON
- GPS don't work (even after 30 minutes of waiting)
- Clockwork is on sdcard as update.zip (not permanent)
- Phone is connected to the computer (with adb installed and working)
Proceedure:
1. Unzip the gps.conf.zip file (attached) to the root of your sdcard
2. Turn off the phone
3. Press and hold the volume down and then press the power button
4. Choose "recovery" from the menu and press power (phone will reboot into recovery)
5. Press and hold volume up and press the power button (this may take a few seconds)
6. Choose "Apply sdcard:update.zip" and press power button (assumes clockworkmod is on the sdcard and named update.zip)
7. Choose "mounts and storage" and click the bottom middle button (trackball)
8. While mount /system is selected press the trackball. (sinkinglow suggested that you might need to mount /sdcard as well)
9. Switch to the computer now
10. At a command prompt (DOS) in the folder where adb.exe is located type "adb shell"
11. Type "cd /system/etc" (if you cant get in then you did not mount /system properly)
12. Type "cp /sdcard/gps.conf ."
13. Switch back to the phone.
14. Click the trackball again to unmount /system.
15. Click the back arrow (bottom right)
16. Choose "reboot system now"
Once the phone is back up, you should be all good.
GPS fix htc espresso
Is there anyway that you could maybe post a youtube video on how to do this, or send me a pm.I will give you my contact info.Maybe you could walk me through it.
ok im stuck at (12. Type "cp /sdcard/gps.conf .") i get this in cmd prompt :
C:\Users\Ryan>adb shell
~ # cd /system/etc
cd /system/etc
/system/etc # cp /sdcard/gps.conf
cp /sdcard/gps.conf
BusyBox v1.16.2androidminimal (2010-03-28 22:34:51 EDT) multi-call binary.
Usage: cp [OPTIONS] SOURCE DEST
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY
Options:
-a Same as -dpR
-R,-r Recurse
-d,-P Preserve symlinks (default if -R)
-L Follow all symlinks
-H Follow symlinks on command line
-p Preserve file attributes if possible
-f Force overwrite
-i Prompt before overwrite
-l,-s Create (sym)links
/system/etc #
then step 13/14 (14. Click the trackball again to unmount /system.) says on phone Error unmounting SYSTEM:!
confused on where to go in cmd prompt i think theres a step missing
Try this
Instead of "cp /sdcard/gps.conf", use :
"cp /sdcard/gps.conf /system/etc"
Worked for me and GPS locks within 15 seconds now.
boss2688 said:
ok im stuck at (12. Type "cp /sdcard/gps.conf .") i get this in cmd prompt :
C:\Users\Ryan>adb shell
~ # cd /system/etc
cd /system/etc
/system/etc # cp /sdcard/gps.conf
cp /sdcard/gps.conf
BusyBox v1.16.2androidminimal (2010-03-28 22:34:51 EDT) multi-call binary.
Usage: cp [OPTIONS] SOURCE DEST
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY
Options:
-a Same as -dpR
-R,-r Recurse
-d,-P Preserve symlinks (default if -R)
-L Follow all symlinks
-H Follow symlinks on command line
-p Preserve file attributes if possible
-f Force overwrite
-i Prompt before overwrite
-l,-s Create (sym)links
/system/etc #
then step 13/14 (14. Click the trackball again to unmount /system.) says on phone Error unmounting SYSTEM:!
confused on where to go in cmd prompt i think theres a step missing
Click to expand...
Click to collapse
Step 12 issue
I think what is being missed it the "." at the end of that comand. The "." is the second argument of the "cp" command and "." means the folder i'm currently in.
If you leave it out you are not telling the cp command where to put the file.
Sorry if I abandoned this post. It sat for weeks with no responses so I quit visiting. Hope it helped you guys out.
Is there anyway that you could post a youtube video on this process.I am missing something
---------- Post added at 05:18 PM ---------- Previous post was at 05:12 PM ----------
Maybe you could send me a pm.Then I could give you my contact info.we could go from there.I just really want to use cm7, but this GPS nonsense is keeping me from doing this.
Assumptions
I made a list of assumptions at the top of the post.
- My phone is rooted and CM7.1 installed.
- S-ON (not required but if you have S-OFF you don't need these instructions)
- GPS don't work (even after 30 minutes of waiting)
- Clockwork is on sdcard as update.zip (not permanent because of S-ON)
- Phone is connected to the computer (with adb installed and working)
So you must have already rooted and installed clockwork as well as CM7. You must have the clockwork (update.zip) in the root of your sdcard. you must have ADB working on your computer and working with your phone (shows in devices list). If you have those then it should be following the steps. I am not currently using my slide and do not have equipment or and account to post videos so that would be difficult. if you can tell me where you get stuck I might be able to help.
Like mentioned before I really don't know what I'm doing. I just tried TONS of stuff till I got a feel for things and found a combination that worked for me.
If you are having issues with rooting or installing CM7 or clockwork then that is beyond this tutorial and there is lots of info out there for that.
My phone is rooted and flashing CM7.1.0 (from CM 6.1.1) is simple.
1.) I can never get "adb shell" to "take to" (for lack of better words) the cmd prompt.I always an error message.Maybe I dont have adb installed and/or running right on my PC and/or phone any help would be awesome.
step # 10 is where I get stopped (in my tracks).
My phone is rooted and flashing CM7.1.0 (from CM 6.1.1) is simple.
1.) I can never get "adb shell" to "take to" (for lack of better words) the cmd prompt.I always an error message.Maybe I dont have adb installed and/or running right on my PC and/or phone any help would be awesome.
step # 10 is where I get stopped (in my tracks).
captorofxxx said:
My phone is rooted and flashing CM7.1.0 (from CM 6.1.1) is simple.
1.) I can never get "adb shell" to "take to" (for lack of better words) the cmd prompt.I always an error message.Maybe I dont have adb installed and/or running right on my PC and/or phone any help would be awesome.
step # 10 is where I get stopped (in my tracks).
Click to expand...
Click to collapse
Try this out before you begin. http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Simply start from where it says Windows and you should be good to go.
Did this fix just a moment ago and it worked like a charm. Thanks reiter01
I wish someone would post a video or give (intricate-no detail left out) instructions on how to do this.I video would be the ticket.If I could follow someone or watch someone do it........
I wish someone would post a video or give (intricate-no detail left out) instructions on how to do this.I video would be the ticket.If I could follow someone or watch someone do it........
reiter01 said:
I think what is being missed it the "." at the end of that comand. The "." is the second argument of the "cp" command and "." means the folder i'm currently in.
If you leave it out you are not telling the cp command where to put the file.
Sorry if I abandoned this post. It sat for weeks with no responses so I quit visiting. Hope it helped you guys out.
Click to expand...
Click to collapse
yeah i think that was the problem i didnt see the ''." there and sorry if im being noob with adb i was never any good with cmd prompt, i prefer a GUI
ADB issues
There are countless posts and article about getting adb working. I use a Mac so it's never an issue for me. If you haven't already installed the USB drivers for your specific phone the first time you hook up then you will have issues. Windows will choose a generic driver that ADB can't use. You need to find instructions on removing the generic driver and install the right one.
I'm really glad some had had success with my little tutorial. I am sure there has to be easier ways but it's the best I could come up with.
Worked great
This worked great for me, my GPS now locks on within seconds. One note to add, I had to mount /system and /sdcard. Thank you for this fix.
GUIless
@boss2688: I agree with having a GUI when available. I have no phone programming skills and so I didn't try that. I am not sure if it would work anyway because the S_ON would be in place blocking by the time the GUI shows up. On the other hand, I am sure that someone could make a zip with scripts etc to do what I am doing manually. I tried and failed to make a zip. I wanted to have it work just like you install google apps from clockwork.
@sinkinglow: Not sure why you would have to mount /sdcard. It should be mounted already at that point (I think). I no longer use my slide so I can't go back and test. Thanks for the tip. I will see if I can figure out how to edit the original post and add that as a possible step.
reiter01 said:
@boss2688: I agree with having a GUI when available. I have no phone programming skills and so I didn't try that. I am not sure if it would work anyway because the S_ON would be in place blocking by the time the GUI shows up. On the other hand, I am sure that someone could make a zip with scripts etc to do what I am doing manually. I tried and failed to make a zip. I wanted to have it work just like you install google apps from clockwork.
@sinkinglow: Not sure why you would have to mount /sdcard. It should be mounted already at that point (I think). I no longer use my slide so I can't go back and test. Thanks for the tip. I will see if I can figure out how to edit the original post and add that as a possible step.
Click to expand...
Click to collapse
a much easier way if you don't have experience with ADB would be to use Android Commander. Please see http://androidcommander.com/ (of course you would still need to mount the system from clockwork if you don't have S-OFF) hopefully this helps for those still having issues.
CM7 1 MyTouch Slide GPS fix
Im going up on the 26th, and was hoping to try this slide then bop over to Gothics. Im going to get to the slide and then make the call as to how safe it seems....Backup plan is any other thing time permitting from that spot. Thats how I roll
* I have to run USBDeview.exe and delete everything sometimes. I think the devices get confused etc..
* I also have to use "Vista_x86" drivers as none of them work for me ..in XP SP3
Code:
C:\usb\ANDROID\Vista_x86\androidusb.cat
C:\usb\ANDROID\Vista_x86\androidusb.INF
C:\usb\ANDROID\Vista_x86\androidusb.sys
C:\usb\ANDROID\Vista_x86\htcrndis.cat
C:\usb\ANDROID\Vista_x86\htcrndis.inf
C:\usb\ANDROID\Vista_x86\WdfCoInstaller01007.dll
[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