Related
MAJOR Update 7/13/2010 15:48 PDT
Go to http://forum.xda-developers.com/showthread.php?t=724741 for the newer, confirmed root method
The following method is now outdated
Added optional instructions to flash Amon_RA's recovery image
Removed unnecessary steps (old step 6 and 7) because downloading the SDK folder in Step 2 already contains those files
Added .wav file of Tereg's cadence in the timing step
Added commands to Amon_RA's recovery image step
Added list of reported successes
Step 4 (Re-run SDK Setup) has been eliminated
Added 20th reported success with a new condition to try to test
Added YouTube video of user Dradien doing the count in the timing step
Added note in timing step about how long to wait after you see /!\ before you start the step over
Rearranged steps 2 and 3 since installing the USB driver after downloading Tereg's SDK folder might overwrite the modded .inf file
Added TODO note to at some point include instructions at various steps for other OS's where needed.
Tereg's testing has eliminated some extra steps, removed step 6 (the driver step), removed step 8 (maintaining a clean sd card, booting the phone back up, setting charge only, turning phone off), removed steps going into recovery where card DOES NOT HAVE TO BE IN when booting into FASTBOOT, therefore the timing step going from FASTBOOT to HBOOT has been removed.
Note about RUU OTA = Leak v3
More successes added with the new "60 partition" method explained by user anoek here: (http://forum.xda-developers.com/showpost.php?p=7089301&postcount=970)
Added 2 successes where both did not run loop.bat
Please note this process is experimental at best. While we have reported a number of successes, it has not been consistent and the success rate seems to be very low or non-existent for a number of users. We are doing the best we can to replicate this process in a more reliable way, and to continue testing for easier ways to achieve this.
**TODO**
Clarify/expand steps that need instructions based on user's OS
List of reported successes
If you find other people with reported successes, there are duplicates listed, or specific information needs to be added for an individual's case, please let Tereg or myself know.
1. Dc_striker (http://forum.xda-developers.com/showpost.php?p=6927162&postcount=1)
2. Hairson (http://forum.xda-developers.com/showpost.php?p=6942651&postcount=186)
3. tereg
4. a-wilcoxj (andirc) Also rooted another phone for another XDA member using his SD card
5. lame eris (http://forum.xda-developers.com/showpost.php?p=6974393&postcount=209)
6. kzoodroid (http://forum.xda-developers.com/showpost.php?p=6975283&postcount=225 and http://forum.xda-developers.com/showpost.php?p=6975440&postcount=228) Also rooted another phone for another person using his SD card
7. RKLamb2 (http://forum.xda-developers.com/showthread.php?p=6972493#post6972493)
8. Dradien (http://forum.xda-developers.com/showpost.php?p=6980387&postcount=318 and http://forum.xda-developers.com/showpost.php?p=6980491&postcount=320)
9. graphitedv (http://forum.xda-developers.com/showpost.php?p=6981435&postcount=334 http://forum.xda-developers.com/showpost.php?p=7011890&postcount=598) - Rooted a second phone, rooted using a Mac running 10.5.8 and the 2GB PNY card
10. djblade17 (http://forum.xda-developers.com/showpost.php?p=6981578&postcount=336) - Win 7 64 bit
11. xtreme3737 (http://forum.xda-developers.com/showpost.php?p=6985257&postcount=365)
12. reethewhat (http://forum.xda-developers.com/showpost.php?p=6987179&postcount=389) - Win7 64 bit
13. largerlager (http://forum.xda-developers.com/showpost.php?p=6988950&postcount=399)
14. Austinjs0102 (http://forum.xda-developers.com/showpost.php?p=6989397&postcount=405) - Windows XP SP3, 2GB PNY card
15. HaRdC0r3 (http://forum.xda-developers.com/showpost.php?p=6963059&postcount=457)
16. varkie (androidforums) (http://androidforums.com/htc-droid-eris/109901-how-many-successfully-went-leak-root.html#post1023198) - PNY 2GB National Geographic SD card
17. Pimpshit420 (http://forum.xda-developers.com/showpost.php?p=6990916&postcount=426)
18. rcharris (http://forum.xda-developers.com/showpost.php?p=6991694&postcount=437) -- Rooted using OS X. Originally tried in WinXP, switched to Mac OS X and got it rooted.
19. bpenney1 (http://forum.xda-developers.com/showpost.php?p=6993850&postcount=448) Had PNY card
20. davinci27 (http://forum.xda-developers.com/showpost.php?p=6996272&postcount=468 and http://forum.xda-developers.com/showpost.php?p=6996996&postcount=472)
21. Jdog94, on page 71, used airplane mode.
(http://forum.xda-developers.com/showpost.php?p=7034130&postcount=733)
22. NAA_Silent (androidforums) http://androidforums.com/htc-droid-eris/109865-leak-root-has-been-found-4.html#post1065772 -- "I tried about 30 times on my work machine running XP while using my Polaroid 16 gig card. I was not successful. Last night I tried again on my Win 7 64 laptop using the factory 8 gig card that came with my Eris. After about 5 attempts I hit the jackpot. I left the loop running instead of ctl+c after each attempt."
23. lostpilot28 (http://forum.xda-developers.com/showpost.php?p=7103114&postcount=1009 and http://forum.xda-developers.com/showpost.php?p=7113530&postcount=1038) - "I flashed the 60partitions.img file to my PNY 2GB SD card and did exactly as he said."
24. igot3ballz (http://forum.xda-developers.com/showpost.php?p=7104474&postcount=1013)
25. listyb01 (http://forum.xda-developers.com/showpost.php?p=7106183&postcount=1017)
26. homewmt (http://forum.xda-developers.com/showpost.php?p=7106822&postcount=1019) - Used anoek's dd image of 60 partition sd card
27. szgtr (http://forum.xda-developers.com/showpost.php?p=7122616&postcount=1055) - Used 4GB RiDATA card
28. lil_dez (http://forum.xda-developers.com/showpost.php?p=7142521&postcount=1087) - Did not run loop.bat
29. Nickboxer7 (http://forum.xda-developers.com/showpost.php?p=7143847&postcount=1088) - Did not run loop.bat
NEW thing to test "The last time I got /!\, I left the phone in the /!\ and popped the card out tand then right back in. Still had /!\ on the screen, but suddenly the device showed up in the loop." Also disable wifi, 3g, gps, bluetooth, and enable airplane mode.
Applications
-->Development-->and check the box titled "USB Debugging"
Video Tutorial by ECLIPS3 & Tereg
http://vimeo.com/album/250913
Prerequisites
Here is a dd image of teregs sdcard in a 7zip archive
http://www.multiupload.com/OT7SH4XNBP
1.Get the Java JDK
For the Java JDK go to http://java.sun.com/javase/downloads/index.jsp
Install Java Platform, Standard Edition, JDK 6 Update 20
2. Downloading Android SDK and running SDK_Setup
Go to http://developer.android.com/sdk/index.html and download the sdk for the platform you are using. Extract the folder contained in the .zip file to the C: drive. (In Windows's case, that would be C:\android-sdk-windows\).
Run SDK_Setup.exe from inside the android-sdk-windows folder.
*Note: you may get a prompt saying that it can't download the repository.xml*
To fix that error close the warning box and click on "Settings" on the left hand side and then check the box that says "Force Https://... sources to be fetched using http://"
Go to Available Packages, the list should now be populated, expand the list by clicking the little + next to https://dl-ssl.google.com/...
*Note: it is not necessary to download the SDK Platforms
Check the box marked "USB Driver Package" at the very bottom of the list
Click Install selected on the lower right corner of the window.
Click the Accept All Radio button on the lower right window that was brought up, and then click the Install button on the lower right corner.
To make sure you are on the right track you should now see in the list of installed packages two total packages:
Android SDK Tools, revision 6
USB Driver package, revision 3
3. Overwrite the android-sdk-windows folder with all the files you need
**TODO** (Include instructions for Mac and Linux SDK downloads)
Here you can download Tereg's complete SDK with all the files used http://www.multiupload.com/01Q1UXGLOF
Unzip the folder to C:
In our setup we have extracted the Android SDK to C:\android-sdk-windows
Root Process
Tereg's analysis has shown that RUU OTA = 2.1 Leak v3. If you have Leak v3 on your phone, then you probably do not have to do this step.
4. Flash the RUU OTA Update
Go to: http://shipped-roms.com/shipped/Des...WWE_2.36.605.1_release_signed_with_driver.exe and download the RUU OTA executable.
WARNING: THIS WILL WIPE YOUR PHONE. IF YOU HAVE ROOT YOU WILL LOSE ROOT. BACKUP THE CONTENTS OF YOUR SD CARD AND APPS YOU HAVE INSTALLED BEFORE YOU CONTINUE WITH THIS STEP.
If you need to backup the content of your SD Card, mount your phones SD card as a disk drive, open the drive within My Computer, and copy/paste all folders into a new folder. Copy the contents somewhere safe, we are not responsible for any lost data.
In addition to backing up your SD card, you should find a way to back up your phone (apps, settings, etc) using any method available (like MyBackup or Astro File Manager, etc). You will have a stock, wiped phone when you are finished with this step.
Execute the .exe and go through the wizard process.
5. Make sure USB Debugging is turned on on the phone
From the Home screen, press the Menu button -> Settings. Tap Applications -> Tap Development -> Make sure that USB Debugging is CHECKED.
Open a command prompt by going to Start -> Run. Type cmd in the text box, click OK.
If using Linux, open a terminal prompt and change your working directory to the android SDK tools folder and execute the "adb devices" command.
Execute these commands
Code:
cd \
If you don't see
Code:
C:\>
then type and execute
Code:
c:
Execute the following commands
Code:
cd android-sdk-windows
cd tools
adb devices
If you see the following
Code:
List of devices attached
HTxxxxxxxxxx device
where xxxxxxxxxx is some alphanumeric value, then you have done this step successfully.
Note: Old Step 6: Updating drivers for devices has been tested as unnecessary
6. Mounting the SD Card as a Disk Drive and formatting
Mount the SD card as a disk drive from within the phone. To do this, drag the notification bar down and tap the Ongoing notification (either Charge Only or HTC Sync) section. Tap the Disk Drive option (Mount as disk drive), and tap Done.
If you don't still have Computer Management open, click the "Start" button on your computer, RIGHT click on "My Computer", click "Manage", then Click "Disk Management" which is under "Storage" on the left pane and you will see all your drives.
Find your SD Card in the lower half of the right-hand pane. If you do not see your SD card, go to the Action menu and select "Refresh". If you bought the SD Card listed here, the size of the partition is 1.83 GB. Right click on this partition, and select "Format...", and click the "Yes" button that you are sure you want to do this.
Make the volume label blank, pick FAT32 as the file system, and select the allocation unit size 4096
DO NOT do a quick format.
Click the format button on the bottom right corner, then click OK to confirm the format.
Let it format, DO NOT eject the card while formatting.
When the format is complete, power off the phone.
Note: Old Step 8: Maintaining a clean SD card has been tested as unnecessary
7. Booting into recovery (the timing step)
.wav file of Tereg doing the count in this step: http://www.multiupload.com/IRL99EH394
NEW: Dradien has uploaded a video doing the count - http://www.youtube.com/watch?v=2bRl2ul7GdA
Note: The SD card does not have to be in. It can be out before you boot into FASTBOOT. Therefore, you do not need to press down on the SD card while in FASTBOOT, press Vol Down, then remove the SD card.
Make sure that the SD card is OUT before you begin this step.
Boot into FASTBOOT mode by pressing and holding the Send+Power buttons.
Go into HBOOT by pressing the Vol Down button.
NOTE: Running the loop is just for convenience purposes. It is not mandatory for this method to work.
Start -> Run -> type cmd in the box, click ok.
In the command prompt type
Code:
cd C:\android-sdk-windows\tools
Type
Code:
loop
and press enter
Position your right hand over the sd card and the left hand over the Volume Up button. As soon as you press Volume Up, starting counting "1-1000, 2-1000, 3-1000, 4-1000", which in Tereg's case took approximately 2.5-3.5 seconds. As soon as you finish counting, press the SD card into the phone.
Watch the command prompt. If it works it should display
List of devices attached
HTxxxxxxxxxx recovery
over and over again where xxxxxxxxxx is some alphanumeric value
If this succeeded you can stop the loop by pressing Ctrl+C
Important Note: After you see the /!\, you will need to wait for several seconds before you restart this step. You will need to wait for Device Manager to stop flickering before you pull the battery. Wait at least 10-15 seconds after you see the /!\ icon before you start this step over.
If this did not succeed, make sure that Device Manager is not flickering, then pull the battery to turn off the phone. Stop the loop in the command prompt by pressing Ctrl+C, and repeat this step again starting with the phone off.
8. Pushing files in recovery, and getting #
Next on the phone press Volume UP + Power at the same time, which will bring up a menu in Recovery.
Then select "Apply sdcard:update.zip"
THIS STEP WILL FAIL, don't worry, we expect it to.
Once the update has failed we need to go back to our command prompt (the one we stopped the loop in) and type
Code:
adb push ota.zip /sdcard/update.zip
and press enter, then type
Code:
adb push root.zip /sdcard
and press enter.
After each command, ensure there is no error message after executing the command.
The status for success will be something like
Code:
xxx KB/S (x bytes in xxxx.xxxs)
At the next prompt, type this command but DO NOT execute it yet.
Code:
adb push update.zip /sdcard
This is another timing step. You will need to scroll down to "Apply sdcard:update.zip", and press the Power button then look for a very faint, dim progress bar near the bottom of the screen. The progress bar will be green.
AS SOON AS YOU LOCATE THIS PROGRESS BAR, you need to execute the command you typed.
If successful you should see the Clockwork Mod Recovery along the top of the phone.
Go to the Partitions menu on your phone by rolling the trackball down and pressing the trackball to select it.
Then select "mount /system" once.
Scroll down to +++++Go Back+++++ and select it.
Scroll and select "Install zip from sd card". Then, scroll and select "Choose zip from sdcard", then scroll and select "root.zip"
Once this is done, select Reboot System from the menu, and let it boot normally.
After the phone comes back up to Sense UI, in the command prompt execute this command
Code:
adb install Superuser.apk
Again, you should see something like:
Code:
xxx KB/s (x bytes in xxx.xxxs)
pkg: /data/local/tmp/Superuser.apk
Success
underneath the command where x is some number
Once this step is done, make sure the phone is unlocked, awake and not asleep.
Type
Code:
adb shell
then type
Code:
su
You will get a prompt on the phone from superuser asking for permission. Allow this.
the $ symbol will change to #, which indicates you have root.
[Optional] Step 11. Flashing Amon_RA's recovery image
This step is optional. Follow these steps if you would like to flash Amon_RA's recovery image after you have achieved a root prompt.
Open the command prompt and change your working directory to C:\android-sdk-windows\tools exactly as you did in Step 12.
Execute these commands (Note: When you see $ or #, that does NOT mean you type $ or # respectively in the command. It means that is the prompt you should see at the time you are executing these commands.
If you extracted the android-sdk-tools folder in Step 3, you have all the files you need for this step.
Code:
adb shell
$ su
#mount -o rw,remount /dev/block/mtdblock3 /system
# exit
$ exit
adb push recovery.img /sdcard
adb push flash_image /data/local
adb shell
$ su
# chmod 755 /data/local/flash_image
# /data/local/flash_image recovery /sdcard/recovery.img
# reboot recovery
If you do these commands, you should be able to see Amon_RA's recovery.
At the bottom of the screen it should say "Build: RA-eris-v1.6.2", and you should have the following menu options.
Code:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Other
- Power off
Note: If you are getting Permission Denied errors while doing any of these steps and you still have Clockwork's Recovery partition installed, user Dradien has reported success with the "Fix Permissions" function within Clockwork's Recovery main menu. Dradien reported that that function took about 5 minutes and afterwards was able to flash Amon_RA's recovery image.
Afterward
One thing to note, there is a step we did not do that Slide Root method did which is install a full root.zip that allows you complete root access when you execute an "adb shell ..." command.
i.e. if you run adb shell as the following example command prompt
Code:
C:\>adb shell
you will see a $ prompt, not a # prompt.
Therefore, any commands you are executing (at least for the moment) that require root access (like to flash Amon RA's recovery for instance):
Code:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
you will need to do this in the following manner
Code:
adb shell
$su
#mount -o rw,remount /dev/block/mtdblock3 /system
So, if you are getting permission denied errors from a regular command prompt while executing commands (adb shell mount..., adb flash_image..., etc) that require root access, you will most likely need to drop into shell manually, su into root, then cut off the first part of the command, put the rest of the command into the prompt and execute it.
Example:
adb shell mount -o rw,remount /dev/block/mtdblock3 /system
becomes
mount -o rw,remount /dev/block/mtdblock3 /system
Look at other tutorials on how to flash roms, if you have any questions pm me (Captainkrtek) or join us on irc.andirc.net #droideris & #leakroot and ask for any of the opers or Tereg for help.
Below are pictures and tools Tereg used, and how he oriented the phone and positioned his hands and screwdriver over the Vol Down/Vol Up buttons with left hand and over the SD card with the right hand during the SD card timing steps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well written, thank you for writing this guide.
Also, the easiest way to get on irc is to go to http://chat.andirc.net/ and make a nick.
char561 said:
Also, the easiest way to get on irc is to go to http://chat.andirc.net/ and make a nick.
Click to expand...
Click to collapse
Join #leakroot to discuss it
Congrats Tereg, and CaptainKrtek. Tereg your crazy to flash RUU, thank you for trying again and proving
I should note, just remembered, I had Wi-Fi, Mobile Network and GPS all turned off during the entirety of this process.
Wow yeah great guide, people report your success with it and stuff. I'm trying it soon.
Sent from my Eris using XDA App
Great guide hopefully more people start getting root using this method, I currently have root (s-0ff) may try and root the brother in laws phone now he has leakv3. Welcome to the party leakers.
I feel completely crazy for unrooting (and that process is now done), but that's kind of where my mind is. I really want this process to be repeatable.
Hey where is the modified Inf file?
jvward said:
Hey where is the modified Inf file?
Click to expand...
Click to collapse
oops my fault, uploading now! thanks!
EDIT: In the tutorial now
ok so, i t may be a bit early, but once we are rooted from this method, can we unroot using the standard unroot method, or does nobody know that yet?
jrhoades858 said:
ok so, i t may be a bit early, but once we are rooted from this method, can we unroot using the standard unroot method, or does nobody know that yet?
Click to expand...
Click to collapse
Yes i believe you can, tereg just unrooted his phone to try this method again
Awesome! Trying in about an hour. Thank you!
Sent from my Eris using XDA App
trying right now, and yea i deleted all the adk and everyhting to start fresh =P so when i got the the part to download modded.inf i was like where the link but i remembered i didnt delete my downloads folder so i still had tht file =D haha
edit: O and fat32 with no quick format is taking forever!!!
Is there any chance this will work with the stock Eris microSD? I would prefer not to go out and buy a new one but if I absolutely have to I will today.
To unroot once you do this all you have to do is use the ruu that is posted here and that will set it back to exactly how it was.
zigzackattack said:
Is there any chance this will work with the stock Eris microSD? I would prefer not to go out and buy a new one but if I absolutely have to I will today.
Click to expand...
Click to collapse
There is a slight chance though pretty much no. Everyone who has tried it with the stock card has failed so your best bet is to go buy a $12 card
Yea I also am wondering if the stock 8 GB on Eris will work. Please let us know or test it out leakers.
MyFixofAndroid said:
Yea I also am wondering if the stock 8 GB on Eris will work. Please let us know or test it out leakers.
Click to expand...
Click to collapse
I do not believe it will. Everyone who has tried has failed.
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.
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
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!