Related
[GUIDE] Turkeys' Ultimate Guide to Root Desire v42.1.1 "Misc Errors are History"
Turkeys' ULTIMATE Guide to Rooting v42.1.1
Before You Start
This is a new type of guide, an experiment if you like. The whole point is to get you with a fully functioning, rooted phone. But also to teach you something. Each step first tells you what you're going to do before you do it. By the end not only should you have a rooted phone but you will hopefully have priceless knowlege of how Android works.
Enjoy.
Need Help?
If at any point during this guide you need help, something's gone wrong or you need some extra clarification. Hit the help button.
The help button will link you to the #rootmydroid IRC help chat channel, where you can ask questions or get walked through the whole thing if you really need to. We have experts on hand to help you out.
PLEASE NOTE: At peak times our experts may be busy so please be patient.
So, Mr. Turkeys, what have you got for us today?
Root Guide
Post 1 - Intro
Post 2 - UnrEVOked (Rooting)
Post 3 - Flashing a ROM
Post 4 - Flashing a new Radio
Other Guides
Unroot (Adding Now)
A2SD
More Coming Soon... Stay tuned!
So, click a link to the guide you want and get cracking, enjoy!
Donate
Should you feel the crazy need to donate to me you can do so below
GBP
EUR
USD
Root Guide - Pt. 1 - Info
So, you wanna root?
Rooting is not easy like some people make it out to be. All these 1 click Noob-Proof tools can actually go wrong. And they do.
But lets get this clear, IT'S ALMOST impossible to brick. I'd put the odds on about a 99.9% chance you will not brick beyond repair. However, things probably will go wrong, which is why you will need to follow the instructions very carefully.
Pre-Root Info
I want to make sure the rooting process goes well for as many as you as possible, so get ready to read lots of information that will turn you from a Noob into a lean, mean rooting machine.
And for those of you who like to slack off and think "I cba to read all that crap", I've made it so you have to answer a question to get the download links. Aren't I nice. Seriously though, it really will be a lot easier for you if you read all of this, you will thank me for it one day.
Pro users who know what HBOOT is, how to flash a ROM and can use ADB can safely skip this step
Android Glossary
This page is probably the most valuble bit of information you will ever need during your rooted life. Behold, the VillainROM Android Glossary. (Cheers Pulser )
http://bit.ly/9HtICk
Read it. Read it ALL. No questions asking for these terms will be tolerated in this thread and you will be teased so much you will want to die. So please, read it carefully.
Downloads
Now, for the bit you've been dreading. 2 downloads. 2 questions. One answer will link you to the download. The other two will link you to a humorous fail picture. (And for all you sneaky cheaters out there, I've bit.ly'd the links. Take that.)
Question 1 - UnrEVOked download
What do you use to flash a ROM?
A) UnrEVOked
B) ADB
C) Recovery
Question 2 - Other Stuff Download (We may ask you to use this on the help channel)
What is a RUU?
A) A tool to root your phone
B) A tool to return your phone to 'stock' (unroot)
C) A tool to flash a ROM
You can also get countless lulz from adding a + to the end of those links and comparing the wrong answers to the correct ones. Yes people really don't read the information.
OK, I've talked enough now, let's get down to business...
Root Guide - Pt. 2 - UnrEVOked
So, hopefully you now know all the terms, which makes my life a lot easier as I don't have to explain everything. Let's begin.
Root Guide - Pt. 2 - UnrEVOked
1) Ensure you have downloaded and extracted the first download in the above post to somewhere you can remember and access easily. For the purpose of this guide, I will refer to that folder as the 'Root Pack'.
Next, we are going to prepare the UnrEVOked program to run. If you are a Windows user, this means installing the drivers, if you use Linux or Mac you just have to run the app as mentioned later. We have to install HTC Sync to get adb drivers and we have to uninstall it again as it interferes with UnrEVOked. The drivers however remain which is why you need to install it.
2) (Windows Only) If you have not already, download HTC Sync and install it. Then uninstall HTC Sync as well as any other software that may interfere such as doubletwist. Next, follow this guide to set up the hacked HBOOT drivers. Make sure you reboot your PC after doing this.
Next, we need to prepare your phone. We will make sure USB Debugging is on as UnrEVOked needs this to send adb commands to the phone. We also need to enable Unknown Sources so that UnrEVOked can push busybox and SuperUser Permissions apps to the phone.
3) With your phone go to Settings > Connect to PC > Default connection type > Charge Only and untick Ask Me. Then go to Settings > Applications > Development > Make sure USB Debugging is ticked. Then go back to Applications and make sure Unknown Sources is ticked.
Next, we're going to run UnrEVOked. What it does is reboot into HBOOT mode, and use an exploit to gain a temporary NAND unlock. Then it uses fastboot to flash a recovery image, and then pushes the su files required for root.
4) WINDOWS USERS: Right click on the 'unrevoked.exe' file (Or something similar) in the Root Pack and click 'Run as Admin' (Not required for XP)
LINUX USERS: Right click the 'ClickHereToRoot.sh' file and UnrEVOked will start. (Make sure you chmod 755'd it first)
MAC USERS:
mattbeef said:
Unrevoked, if your a mac user like myself then drag the app inside the dmg to the desktop and run it from there. Most mac users are lazy and will try to run it from the dmg.
Click to expand...
Click to collapse
GETTING A MISC RELATED ERROR? See post eight.
Your phone should now reboot and then congratulations! Your phone is rooted. However, the root that UnrEVOked gives you is basic. No ROMs or good stuff. So you must read on to the next post to flash a custom ROM...
Root Guide - Pt. 3 - Flashing Your First ROM
Now you've rooted, let's flash a ROM. We will backup all your apps then flash a ROM then restore your apps. Ready?
Pt. 3 - Flashing Your First ROM
**NOTE: You can repeat Pt. 3 every time you want to flash a new ROM or update
Next we're going to download and use Titanium Backup to backup all your apps as we will have to wipe your phone to install the ROM. You can use the same method if you ever want to backup/restore in the future too.
1) Download & Install Titanium Backup from the market. Open it and hit the 'Problems' button to download busybox, a suite of commands for rooted phones.
Then hit menu then batch, and tap the button next to Backup All User Apps + System Data. Let it complete before moving on to the next step.
Next we're going to reboot into recovery mode to flash the ROM. You can use this if you ever need to get into recovery in the future.
2) Turn your phone off and turn it on again holding POWER + VOL DOWN to enter HBOOT mode. Wait a few seconds while it checks for images before using the VOLUME KEYS to scroll and POWER to select Recovery. Your phone will now vibrate and reboot into recovery mode!
Next we're going to do a full backup of your phone using Nandroid. This will backup the entire state of your phone in case you ever
want to go back. You should really do this every time you flash a new ROM.
3) Use the TRACKBALL to scroll down to where it says Backup or Nandroid or Backup / Restore. Then select Backup and wait for it to finish.
Now we need to wipe your phone. Whenever you flash a different ROM you should Always do this, when you are updating the ROM you should check on the release thread for information.
4) If you are not on the Main Menu in recovery, hit back a couple of times to get there. Then, use the TRACKBALL to navigate down to 'Wipe Data / Factory Reset' and accept the scary warning to wipe your phone.
Now we can flash the ROM! Ensure you have downloaded a ROM and it is on the root (Not in any folders) of your SD card. The flashing process may take a few minutes.
5) From the Main Menu, scroll down to and select Install zip from SD Card and then select Choose zip from SD Card then select where you put your ROM and wait for it to complete. Then, select Reboot System Now to reboot into your shiny new ROM!
Your phone will now reboot, it may take a while to reboot as it's rebuilding the Dalvik Cache. If it still doesn't boot up after 10mins, pull the battery and consult the ROM thread for troubleshooting.
Now we're going to restore that Titanium Backup you made before starting Pt. 3. It will restore all your apps back but not system data. (ie Settings) You can use Titanium Backup any time you want to backup/restore your phone.
6) Download & Install Titanium Backup again and tap Menu Button > Batch > Restore Missing apps + data. It should prompt you to reinstall every app again.
--------
Congratulations, you have qualified with a rooted phone from the Turkeh Root School!
(Unless you're reading this without having actually done any of this guide)
So, go off and ask questions, answer questions, and contribute to the community! We'd also really appreciate it if you could hang out in the help channel to help other people trying to root too.
Thanks for rooting! You can also follow some of the other guides to install all apps on the SD card, Unroot & S-OFF
Pt. 4 - Flashing a New Radio
Flashing a Radio
The radio is the lowest part of your phone. (ie It's the very first thing that loads when you turn your phone on.
Most ROMs will have a required radio version, but most will agree that it's best to be on the latest as they often improve battery life etc.
You can downgrade your radio and you can find your radio version by going to Settings > About Phone > Software Information > Baseband Version.
Your ROM should tell you on it's thread what the recommended radio version is, so download it, transfer it to the root of your SD card as you did in Pt. 3 then follow this.
Now we're going to reboot into recovery mode as we did in Pt. 3 to flash the new radio. There is also an app on the market called 'Quick Boot' which you can use to quickly get into recovery. The next step will assume you have this.
1) Open Quick Bootand tap Recovery then tap Allow on the SuperUser permissions prompt.
Note: The SuperUser Permissions app will prompt you whenever an app is requesting to use root. You should look over which app is requesting this before you allow it.
Next, we need to flash the radio. You do this exactly the same way as you flash a ROM, which you did in Pt. 3.
2) Use the same method you flashed the new ROM in Pt. 3 to flash the radio. You do not need to Nandroid backup or wipe to do this, just flash the zip.
Note: Your phone may reboot a couple of times and will show a picture of the Android Robot while it is flashing the radio. It has NOT crashed, it is flashing it. DO NOT pull the battery, it will reboot when it is done.
Your new radio has now flashed!
Apps2SD
A2SD
First, we need to get S-OFF to flash Amon-RA Recovery. You can use clockworkmod/ROM Manager to do this although it is very error prone so don't!
Now, I'll be honest, I really cba to write and provide support for people S-OFFing, so I'll link to someone elses instead.
But you can still post on this thread with questions, post there if the S-OFF doesn't work.
S Me OFF!
Download the AmonRA recovery image here before continuing. (Make sure you save it in the adb folder inside. the other stuff file below)
1) Make sure USB Debugging is on and make sure you downloaded the 'Other Stuff' file in post 2 and have extracted it to somewhere you can get to easily. (I always reccommend C:\root)
Next we need to flash Amon RA recovery. We will do this via the command line using fastboot. Your phone needs to be in booted Android mode for this next step.
2) Open a command prompt (Start > Run > cmd) and type the following: (you will need to replace some bits if you extracted the other stuff file to a different location.
Code:
cd \
cd root
cd adb
adb-windows reboot bootloader *let your phone reboot into fastboot before continuing*
fastboot-windows flash recovery what-you-called-amonra-recovery.img
fastboot-windows reboot
Next we are going to reboot into your newly flashed recovery image and repartition your SD card. This will format your SD card so please BACKUP your SD Card before continuing.
3) Open the Quick Boot app you downloaded in Pt. 4 and tap Recovery to reboot into recovery mode. Once you are in Recovery scroll down to and select Partition SD Card then select Partition SD. Now use the TRACKBALL to scroll up and down until you get the partition size you want and press trackball to continue. Now select 0 swap unless your ROM supports it and you know what it is. Then set the rest of the SD Card to FAT32 and press the TRACKBALL followed by the HOME BUTTON to confirm and start partitioning!
Note: If you want to use an ext3 or ext4 partition and your ROM supports it, select the SD:ext2 to ext3 option to upgrade to ext3 and the other one to upgrade to ext4. However, I would advise against doing this as you will wear out your SD Card faster.
Now, you need to check the ROM thread for info. Most ROMs activate it automatically when it detects an ext partition on your phone. On some others you need to flash a special update.zip. If you are unsure hit the help button on post 1 and we'll help you out.
Congratulations, you now have Apps2SD! Exactly what you will have (dalvik2sd etc) will vary between ROMs.
Unroot
These RUU programs that you use to unroot are Windows only, but fortunatley I wrote a tool for Linux called OpenRUU so you can flash them on there. If you are a Mac user, take a moment to ask yourself 'Why am I using a Steve Jobs product?' as there is no way for you to run the RUUs.
First, we are going to identify what RUU you need to download and flash then download it. (Bravo is the codename for Desire, all RUUs use this name)
1) Go to shipped-roms.com, click on the Android Robot then click on Bravo. Now, you need to recall what version of Android you were on before you rooted. If you were on 2.1, you need to choose one of the RUUs which say 1.21.xxx.x. If you were on FroYo, you need to choose one that says 2.xx.xxx.x. If you had a carrier supplied device you should also get the one that is applicable, but if you are unsure or your carrier is not listed go for one that says WWE. (World Wide English - All Languages) Or come on our IRC channel for advice.
Note: HTC Sync must be installed before continuing. The next step will also wipe all your apps + settings!
Next we're going to run the RUU, this should take around 5-10mins. DO NOT touch your phone during the flashing process!
2) Double click on the RUU file you downloaded in step 1, read the readme, and click to start the flashing process.
After it's done! Your phone now should be completley back to stock status!
If you get an error during the flashing process, try again and then come on our IRC help channel for assistance if it persists.
Fixing the annoying unrEVOked misc errors
Fixing the Annoying unrEVOked Backup CID Missing errors
NEW, EASY METHOD
I managed to find unrEVOked 3.2. If you want to use that as a fast-track then that's fine, but please read the following carefully:
Code:
[B]DISCLAIMER:[/B]
Please be aware that this build was pulled from unrevoked.com because it was not safe.
USE AT YOUR OWN RISK!
If it ****s up and you point the finger at me, I will laugh at you.
This is only for 'Backup CID Missing' errors. if you use this on any other type of misc error it might brick.
Download. Run in replace of unrEVOked 3.21 in the standard guide.
You can still use the old, misc editing guide below:
(Guide edited from http://home.kennynet.co.uk/~kenny/bcid-fix.txt to be more noob-friendly)
This fixes:
Backup CID Missing
Unfortunately, because a couple of people corrupted their misc partitions during the testing of unrEVOked 3.2, they brought in a load of stupid, annoying safety features that included checking the misc partition on your phone.
/rant
What is misc?
Misc is a partition on your phone. It holds various switches and stuff, such as your:
Official HTC ROM Version
Your CID (Which tells the phone what carrier/region your phone is)
However, sometimes, the CID is not in misc or your misc is corrupted. This process will add in the CID to misc and reflash misc. (which may fix other misc related errors but probably wont)
Warning! Misc is quite an important part of your phone. If it gets severely corrupted you may loose USB access. Me or anyone on our IRC help channel take no responsibility if you **** up somehow.
This guide is designed for Windoze, Linux users use common sense adapting the instructions and can use a Linux hex editor like ghex. (Works just the same)
Please ensure you have downloaded the other stuff file on the second post before continuing and have extracted it to C:\root.
First, we need to use adb to grab misc off your phone. We will get temporary root then grab misc.
1) Open a command prompt on your computer by going to Start > Run and typing cmd then pressing enter. Now type the following pressing enter on each line. (Make sure your phone is connected and you have the drivers installed.)
Code:
cd \
cd root\adb
adb-windows devices <---- Make sure it finds your phone before continuing
adb-windows shell <----- You should see a $
$ /system/__unrevoked_su <---- Getting temp root
# cat /dev/mtd/mtd0 > /sdcard/misc.img <---- Copying misc to your SD Card
# getprop ro.cid <----- This is your CID. Remember what this says, it should say something like HTC_000 or 1111111 if you have a goldcard
# exit
adb-windows pull /sdcard/misc.img misc.img <---- Getting the misc we copied before
You should now have a file called misc.img in the C:\root\adb folder.
Now come on to the IRC help channel here. We will stick the CID into the misc.img so you can carry on as it really is complicated. You can also post here if nobody is avalible and I will sort it ASAP.
(If you've done hex editing before, all you do is put the CID you got above in at position 0 then add a 00 at the end so the hex string looks something like "48 54 43 5F 5F 30 30 31 00")
Make sure you save the file that we give you back to C:\root\adb overwriting the original misc.img file.
Next we're going to push misc back on to the phone using a similar method to step 1. Have open a command prompt and cd to the correct directory as in step 1 before proceeding.
2) Type the following in the command prompt:
Code:
adb push misc.img /sdcard/new-misc.img <---- Pushing misc back to your SD card
adb-windows shell
$ /system/__unrevoked_su <---- getting temp root again
# /data/local/flash_image misc /sdcard/new-misc.img <---- Using flash_image to flash the new misc
# exit
Now rerun unrEVOked and everything should be as shiny as the plastic Samsung use to make their phones.
Click to expand...
Click to collapse
Reserved for when I think of some awesome idea I just have to put here. #2
just say WOW! really Great!
Please don't forget radio info.
What a super great guide I really appreciate it, I think we all will
Nice one turkey, I just want to hug you so hard!
{
"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"
}
gascanieto said:
Please don't forget radio info.
Click to expand...
Click to collapse
Whoops forgot that, I'll add it in now
EDIT: Added quickly from an old guide, rewrite soon
Brilliant post
Really Really useful for nooblits
Great, easy guide. wish I had this when I rooted my desire ages ago.
There needs to be more stuff written in plain english - like this guide.
Very easy to read. I'm sure it will find its way into the sticky threads soon enough!
V42 beta....hehe
Anyway, good work! I love it.
Josh.
Can I make a suggestion and ask for a quick guide on updating your recovery image? I have clockwork recovery mod from the first unrevoked tool and thought ROM Manager updated it (it says I am using 2.5.0.7) however whenever I flash a ROM it always says I am on 2.5.0.1. Not sure on how to update it and if I should rather apply the rule if it aint broke dont fix it .
Real nice, one flaw: you use volume keys to navigate in Clockwork (which is default for unrevoked) and trackball in amonra IIRC
Sent from my HDfied HTC Desire
Actually, Clockwork uses the trackball too
Sent from my HTC Desire using XDA App
The purpose of this guide is to walk you through the process of rooting your phone running 2.3.3 ONLY! I will do the best I can to make this as painless as possible and help you achieve your goals of S-Off.
***THIS THREAD IS ONLY FOR OBTAINING S-OFF, OBTAINING ROOT, AND INSTALLING CLOCKWORK MOD RECOVERY! ANY QUESTION REGARDING INSTALLING ROMS DO NOT BELONG HERE AND WILL NOT BE ANSWERED! ONLY ISSUES REGARDING ROOT WILL BE ANSWERED BY MYSELF OR OTHER MEMBERS.***
What you will need: (** = File is attached to OP)
Windows XP or higher (Thats all I have, someone else with MAC and/or Linux will need to assist and I can add it to the OP)
http://revolutionary.io/ .:UPDATE:. PRE4 now available
This site is where you will download the rooting tools and obtain a beta key. When you click on the download button for your OS, make sure you view the box that pops up requesting your OS version, phone model, HBoot version, and phone serial number. Without doing this you cannot root your phone so do it or you are screwed. There are two ways to get your phone serial number: 1) Remove the battery and look at the white sticker or 2) On your phone, go to Settings -> About Phone -> Phone Identity and under Device Serial Number you will see it. After you receive your code COPY AND PASTE it onto a word document or notepad because there are times when you will get confused with the font type from the Revolutionary site. Example, in my beta key, the lower case L looks exactly like the capital I and it threw me off. Also, the key IS case sensitive so keep that in mind.
If running windows, you will need these drivers:
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
If running Linux, reports show that you do not need any drivers.
If running Mac OS, I currently do not know so someone please let me know and I will update.
http://goo-inside.me/superuser/su-2.3.6.3-efgh-signed.zip **
This file is required to obtain ROOT AFTER you have S-Off.
http://forum.xda-developers.com/attachment.php?attachmentid=630611&stc=1&d=1308537076 (WINDOWS) **
http://forum.xda-developers.com/attachment.php?attachmentid=630611&stc=1&d=1308537076 (LINUX) **
http://dl.dropbox.com/u/33327355/cwm-4.0.1.4-vivow.img **
These two items are in case Revolutionary tool fails to install CWM on your phone OR if you want to do this offline at another location. Fastboot and abd tool is the software that will take the img file of CWM and flash it onto your phone after S-OFF is obtained.
Prepping your Phone:
Turn off FAST BOOT in the settings located: SETTINGS -> POWER
Turn on Unknown Sources: SETTINGS -> APPLICATIONS
Turn on USB Debugging: SETTINGS -> APPLICATIONTS -> DEVELOPMENT
Installing Root:
1 - First, install the HTC drivers on your computer. It is a very simple step and you should have no issues doing this at all. Also look at your installed programs list and confirm HTC Sync is not installed. This will stop your device from being detected by Revolutionary to other problems when rooting.
2 - Extract the Fastboot and ABD zip file onto the root of your local disk drive (ex. C:\android-win-tools )
3 - Copy/Cut and Paste the CWM img file into the Fastboot and ABD folder (ex. C:\android-win-tools\cwm-4.0.1.4-vivow.img) Doing this will prep your PC to flash CWM in the event the Revolutionary tool does not download and install it.
4 - Place phone in "Disk Drive" mode then Copy/Cut and Paste the root su zip file (do not extract it) onto the root of your SDCard on your phone (ex. x:\su-2.3.6.3-efgh-signed.zip )
5 - Place phone in "Charge Only" mode. A lot ot people run into issues and not realize this was not selected.
6 - Run the Revolutionary file now that everything is set to go.
7 - You will get a prompt to enter your beta code. This is the code you received when you downloaded the revolutionary file and entered the information to obtain the beta key.
8 - Sit back and WAIT while the application does what is needed. This process will take anywhere from 3 to 5minutes so be PATIENT.
9 - Upon completion, you will get a prompt to install CWM. Say yes here! Once done skip to step 10.
9a - If the revolutionary app crashes or fails to download/install, leave your phone in the state it is (HBoot mode and should say "Fastboot USB". Open a command prompt in windows (Start - Run - type CMD).
9b - If you did exactly as told, type "CD.." until you see "C:\"
9c - Type the following:
CD android-win-tools
fastboot flash recovery cwm-4.0.1.4-vivow.img
9d - This process takes about 30sec max. Almost done!!!
10 - On your phone, back track to the main menu of HBoot using the volume keys and Power button and select recovery (2nd Option). In a few seconds your will be in CWM.
11 - As long as you copied the signed zip file to the root of your sdcard, perform the following:
"Install Zip From SDCard" (5th Option)
"Choose Zip From SDCard" (2nd Option)
Select the root/su zip file (su-2.3.6.3-efgh-signed.zip)
Choose Yes and wait.
Back track to main menu and reboot
12 - Give yourself a pat on the back for paying attention and have a cookie!
I am typing this on my tablet/phone/pc so if an error exists, please let me know right away and I will update the OP. Again, questions here are ONLY for rooting. Anything else...kick yourself in the head, do a real search, and post if needed.
Support:
http://unrevoked.com/rootwiki/doku.php/public/revolutionary
Common Q&A for their recovery tool
irc.freenode.net channel #revolutionary
IRC Support Channel
Special thanks to:
XDA-Developers - You guys rock!!!
AlphaRev and unrevoked (Revolutionary) - You have made many dreams come true!!! DONATE to them if you can peeps.
http://forum.xda-developers.com/showthread.php?t=1122694 - attn1 - his How to guide on manually installing CWM.
Nice guide bro.
Sent from my Incredible Sensation using XDA App
The Incredible 2 or VIVO is not an option in the Beta key?
kyrumo71 said:
The Incredible 2 or VIVO is not an option in the Beta key?
Click to expand...
Click to collapse
The incredible 2 is definitely an option when obtaining a beta key. Unless you are refering to something else?
rivera82falcon said:
The incredible 2 is definitely an option when obtaining a beta key. Unless you are refering to something else?
Click to expand...
Click to collapse
My bad, my work computer is crappy, the 2 does not show up on my browser lol
NICE, this thread should be sticky.
On a side note, make sure you have your phone connected to wifi or 3G if you want the revolutionary tool to download and install the CWM automatically. If not then you would have to flash the CWM manually per the instruction from OP.
kyrumo71 said:
My bad, my work computer is crappy, the 2 does not show up on my browser lol
Click to expand...
Click to collapse
I went to the site just now and HTC DROID Incredible 2 is the 6th option down in the device list. If it still doesn't show up, test another pc or try it on your phone. All you need is the key anyways.
Sent from my A500 using XDA Premium App
Thanks for this guide...
Sent from my DROID using XDA App
Awesome thanks but question. my computer keeps saying usb device not recognized every like 5 seconds when my phone is connected and in bootloader. Is that suppose to be like that?
Darkpsych0 said:
Awesome thanks but question. my computer keeps saying usb device not recognized every like 5 seconds when my phone is connected and in bootloader. Is that suppose to be like that?
Click to expand...
Click to collapse
I will say it is okay as this happens to my PC as well. The files still transfer and CWM flashes through fastboot as well.
Sent from my A500 using XDA Premium App
Mmk. I downloaded ROM Manager but everytime i start it up it says "You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su/" or "system/xbin/su"
I have the file on the root of the sdcard and im pretty sure i rooted it with revolutionary and installed CWM as well.
Ok... Dumb question... where do we find the fastboot and adb zips to install on the C drive??
I have gotten thru step 8 and failed whentrying to install CWM. I manually installed it with step 9 and it said finished. Step 10 says to select recovery but it is not listed. I rebooted to see if that would work but it didnt. Where did I go wrong?
EDIT: Actually it did work just was trying to hard. Thanks for the great instructions.
@ Darkpsycho0
try installing busybox from the market and give it a try again.
@PacerguyDon
The links are in the OP.
It's next to the one that has the img file as well. There is only one zip file and it contains both items in it.
@Flightmed
Power down, and get back into HBoot. You will see the following options:
Fastboot
Recovery
Factory Reset
Simlock
Hboot Usb
Image CRC
The second option (Recovery) is what you want.
EDIT: Glad you got it working!!!
Sent from my A500 using XDA Premium App
Got it... thanks, Found it a few minutes after posting
PacerguyDon said:
Got it... thanks, Found it a few minutes after posting
Click to expand...
Click to collapse
It happens...we get so excited that we tend to overlook the obvious. Kind of like my wife...I love her to death and I love to make love to her but I overlooked the obvious that she is also crazy. Oh well...
Sent from my A500 using XDA Premium App
Busybox said "Root not found! The su binary was not found on your phone." -_____-
Thinking about it and looking back...I didn't complete the instructions on applying root. I apologize to you and everyone else.
When you have CWM installed, open it up through recovery. Next, as long as you copied the signed zip file to the root of your sdcard, select "Install Zip From SDCard" (5th Option).
Select "Choose Zip from SDCard" (2nd Option)
Select the zip file (su-2.3.6.3-efgh-signed.zip)
Choose Yes and wait. Once done, reboot and you should be good!
Again, I apologize. I will update main post asap!
Sent from my A500 using XDA Premium App
That worked.. no more error thanks. I was about to throw my phone across the room especially since while i was waiting for replies I was trying to just install new themes but can't get Astros to work with the apk files correctly. -_- (still can't)
I'm already rooted via 2.2 but this is a great guide for the truly n00b.
Should be seeing lots of new members posting in the development section soon ;!)
Alright, so, I guess I'm not the only person having issues with the current versions of ICS, which is kinda comforting. If you can't update your SU binary in an ICS rom because your SU app tell you you're not S-Off, that means the bootloader partition was somehow damaged and forgot you're S-Off, so here's a detailed guide of what I did to get my phone up and running again.
This is also a great guide to help fix any stability problems your phone is having in general.
If you just need to unroot to send the phone back to Verizon or to sell it to someone, stop after step 17 and reading everything after it, but before step 18.
***WARNING***
If you do not follow these directions perfectly, you have a chance of damaging your phone. Part of this process involves flashing hboot manually through ADB, which is dangerous. PLEASE PAY SPECIFIC ATTENTION TO THAT SECTION OF THIS GUIDE. If you don't, your phone is going to be a very depressing paperweight.
IF AT ANY TIME YOUR PHONE TRIES TO ACCEPT AN OTA YOU NEED TO DENY IT! Because of how the Revolutionary Team's S-Off Tool works, we need to be in Froyo to flash hboot manually. An OTA will only get in the way!
Make sure your phone has a decent amount of battery (More than 50%) and keep it plugged in whenever you boot to hboot to be safe. If your phone powers off or dies when flashing a PG32IMG.zip, BAD BAD BAD things will happen!
I am also not responsible for anything that happens to your phone. If you're rooted and S-Off, you already know the dangers, so be smart!
Before I get started though, I have some people to credit, as their tools are used in this guide.
Thanks to:
notluK for his Unroot Guide on Android Central. Pretty much all of this guide is a direct kang/plagiarization from him, with minor changes due to file hosting fiascos.
CLSShortFuse for his SuperOneClick tool
The Revolutionary Team for their S-Off Tool
The unrEVOked Team for hosting the HTC Fastboot drivers
I think that's it... now, for your bacon.
NOTE: I do not have the original md5 sums for these files, so don't ask. Just download over a reliable connection (NOT ON YOUR PHONE!).
Pre-Requisites:
HTC Fastboot Drivers
Android SDK
Froyo (2.2.1) PG32IMG.zip
Gingerbread (2.3.3) PG32IMG.zip
Super SU ZIP from here
And a significant amount of time and patience
Okay... here goes. Please make sure to keep all of the above files on your PC to be safe. They are always good to have in case your phone goes screwy.
1. Download and install the Android SDK, install the HTC drivers and then reboot your PC. (If your SDK is fully functional and you already have the Fastboot drivers installed, just skip this step.)
2. Put the Froyo RUU zip on the root of your SD card and rename it to PG32IMG.zip (if Windows is hiding your file extensions, don't add the .zip to the end).
3. Boot your phone into the Bootloader (Vol Down + Power while off)
4. Press Vol Up to accept the update
5. Reboot phone when done (It may power off to a black screen instead of actually rebooting. Don't panic, just turn the phone on like you normally would ) When it's done booting, delete the PG32IMG.zip from the SD.
6. Check your OS version under Menu>Settings>About Phone>Software Information. Verify your OS version as 2.2.1.
7. Enable USB Debugging under Menu>Settings>Applications>Development
8. Plug in your phone and run the SuperOneClick root tool. When it asks if you want Busybox installed, say Yes. This is important, as you will need Busybox to verify the md5 of the hboot image you are about to flash to your phone manually.
9. Reboot your phone
10. Find the Froyo PG32IMG.zip on your computer and find the hboot_0.97.0000_336906.nb0 file inside. Extract it and put it in the platform-tools folder of your SDK.
11. Make sure your phone is still plugged in and then open your Command Prompt/Terminal and cd to your SDK's platform-tools folder, and follow the adb commands below, with your phone still plugged in, of course!
EXAMPLE: This is where mine is, yours may be different, so check!
Code:
cd C:\android\platform-tools\
Once that's done, continue:
Code:
adb devices (make sure ADB sees your phone if not, this is an appropriate time to ask for help :))
adb root
adb remount
adb push hboot_0.97.0000_336906.nb0 /data/local/
STOP HERE! If you're a dummy and didn't install Busybox with your SuperOneClick, download a Busybox Installer app from the Market and install it to /system/xbin/.
12. Now, do:
Code:
adb shell
su
/system/xbin/busybox md5sum /data/local/hboot_0.97.0000_336906.nb0
If your answer is not affe3dc9abe9d3a8c8bb3ba0ee5176ac, stop now and reboot your phone, then start over again at step 11.
***WARNING***
If you skip this step, you're a big, dumb idiot. This next step involves flashing something to what is probably the most important partition on your phone. If you mess this up, no one can help you, and your phone is permanent brick.
13. If the md5sums match, continue:
Code:
adb shell dd if=/data/local/hboot_0.97.0000_336906.nb0 of=/dev/block/mmcblk0p18
14. Verify the partition's md5sum to be extra-safe. If it's not exactly the same as the original md5 above, DO NOT REBOOT YOUR PHONE! Just start at step 11 again.
Code:
adb shell /system/xbin/busybox md5sum /dev/block/mmcblk0p18
15. Go into your Settings and disable Fast Boot (I don't remember where this is on the 2.2.1 firmware, so look around until you find it). Now, put the 2.3.3 PG32IMG.zip on the root of your SD and boot into hboot like you did before (Vol Down + Power while off).
16. Press Vol Up to accept the update.
17. Reboot into GB when done.
***WARNING***
If you accept the 2.3.4 OTA before going S-Off, you will have no way of reverting and back and re-rooting, SO DON'T DO IT!
The above may not be true, but I'm pretty sure it is, so PLEASE, for your own good, DON'T ACCEPT THE OTA!
If you needed to unroot to send the phone back to Verizon/wherever you got it from, or to sell it, this is the place to stop. If you're selling the phone to someone and they know what rooting is, they'll thank you for not updating to 2.3.4.
18. Run Revolutionary like you did before and accept the installation of ClockworkMod recovery (It'll be an old version, but that's okay).
19. Put the SuperUser zip from earlier on your SD and flash it like normal. (Backup first if you want to have a backup of factory stock unrooted)
20. Profit!
At this point, your phone is now at root 2.3.3 stock and S-Off again! Update your ClockworkMod recovery (or use 4ext, which I like a lot), make a backup (PLEASE, MAKE A BACKUP!) and then flash the rom of your choice, probably an ICS one.
Feel free to update your radio and stuff too. Things should be working much better than before.
And, to be safe, never OC past 1.3ghz. You shouldn't ever need to anyway, and it can break things, which means you'll have to do this all over again. Overclocking too high and my phone overheating is how I got into this situation in the first place, so I'm not just blowing hot air here. (Haha, get it? )
If anybody has any questions (please, don't bombard me with them ), feel free to post here and I'll do my best to respond in a helpful and timely manner.
If this helped you, click the "Thanks" button, or I'ma find you!
Happy flashing!
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
ballisticn8 said:
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
Click to expand...
Click to collapse
I'm glad this is useful! I have all the RUU files saved on my pc too, so if the links do go bad at some point, I still have them and can re-upload.
RegnierD said:
I'm glad this is useful! I have all the RUU files saved on my pc too, so if the links do go bad at some point, I still have them and can re-upload.
Click to expand...
Click to collapse
Links are definitely bad. Any chance you still have the files?
I found the Froyo RUU, but I still need the latest Gingerbread RUU.
This helps a lot thanks
Reg, could update the links for the Froyo and GB RUU's? Thanks!
I'll post new links sometime today, guys.
RegnierD said:
I'll post new links sometime today, guys.
Click to expand...
Click to collapse
Thanks you!!
the RUU files can be found here:
http://goo-inside.me/vivow/ruu
Does anyone have the 2.3.3 stock kernel? I tried another and now wifi won't enable
nevermind!... lol
my phone isn't charging (read that many users have had problems with the charging port on this phone), i just unrooted and s-off'ed. i'm on froyo now. should i download 2.3.3? where can i get it and would that be enough to get a new phone under warranty? or do i need to have the latest OTA 2.3.4? thanks in advance and i apologize for all the questions
ballisticn8 said:
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
Click to expand...
Click to collapse
Now stickied
If I helped, give thanks, if you please.
........Death before dishonor........
hokieputter said:
the RUU files can be found here:
http://goo-inside.me/vivow/ruu
Click to expand...
Click to collapse
which one should i download if i just want the stock 2.3.3 so that i can return my phone for warranty? thanks.
The links are bad. I need the two PG32IMG files... My phone is not fairing well =/
S-On
Where in the guide should I stop if i want to go from s-off back to s-on so i can get a replacement phone?
smayer85 said:
Where in the guide should I stop if i want to go from s-off back to s-on so i can get a replacement phone?
Click to expand...
Click to collapse
RegnierD said:
17. Reboot into GB when done.
***WARNING***
If you accept the 2.3.4 OTA before going S-Off, you will have no way of reverting and back and re-rooting, SO DON'T DO IT!
The above may not be true, but I'm pretty sure it is, so PLEASE, for your own good, DON'T ACCEPT THE OTA!
If you needed to unroot to send the phone back to Verizon/wherever you got it from, or to sell it, this is the place to stop. If you're selling the phone to someone and they know what rooting is, they'll thank you for not updating to 2.3.4.
Click to expand...
Click to collapse
Reading helps.
I cannot get android SDK to install, it says "Java SE Development Kit (JDK) not found. Error: Failed to find Java version for 'C:\Windows\system32\java.exe': [2] The system cannot find the file specified." I have went and tried to install the java it says to but that won't work either. Should I uninstall any java I have installed and try then? My phone bootloops everytime i restart causing me to factory reset it so I need to get a replacement. Thank you.
Edit: Got the java to install after deleting and also have android SDK installing all the stuff now.
New issue, sorry for so many questions im kind of a noob, but when i try to adb root it says something about not able to in production. Does it affect me that my sdk folder in on a seperate HDD from c:\? I'm gonna try to redo it now and hopefully have this working this afternoon. Also, cmd will not let me cd to my SDK folder.
Mount error
When I enter the remount command an error is returned stating: adb remount failed: unknown error: 0
Anyone have any ideas how to resolve this?
Thanks
First off I'd like to preface this by saying that I love having an Android & I am so grateful for the devs out there that put in endless hours of work for the community.
I am a n00b, but have successfully flashed ROMs on various devices... moto backflip, triumph, nook color...
I currently have an HTC Wildfire S on VMUSA.
Here are other stats:
MARVELC PVT SHIP S-OFF RL
HBOOT-1.06.000
MICROP-0354
RADIO-0.94.00.0824
AUG 15 2011,22:34:38
CWM v5.0.2.8
32gb SD CARD [FAT32/EXT-2 VIA MINI PARTITION TOOL ON WIN7]
MAC OSX LION
WINDOWS 7 [VIA PARALLELS]
Attempted the following:
wipe data/factory reset in CWM
wipe dalvik cache
ran SuperWipeMarvelcEdition.zip (completed successfully)
then tried to install "simonsense3.5v.2.zip" and the following happens:
"--Installing: /sdcard/ROMs/simonsense3.5v2.zip
Finding update package...
Opening update package... (it will either hang here or...)
Installing update..." (it will hang here and then reboot itself into CWM recovery)
I tried flashing simon's v.1 of this ROM a few weeks ago and gave up because I couldn't get it to work and it took me many tries to get it back to the stock ROM. I tried searching on the forums for any issues like mine but haven't found any, and I tried all of the recommendations I could find.
Please let me know if you need any additional information!
Thanks so much!!
You may want to try just redownload the zip file (if you haven't already.)
Also, how did you get S-OFF? Was it Goldcard method or did you receive the phone as S-OFF?
And finally, thank you for detailed information about your phone, computer, and the steps you have tried to fix the issue. It makes troubleshooting much easier!
kalaker said:
You may want to try just redownload the zip file (if you haven't already.)
Also, how did you get S-OFF? Was it Goldcard method or did you receive the phone as S-OFF?
And finally, thank you for detailed information about your phone, computer, and the steps you have tried to fix the issue. It makes troubleshooting much easier!
Click to expand...
Click to collapse
I haven't tried re-downloading it, I will do that right now. 9:23PM redownloaded and flashed another copy...still hangs at "opening update package..."
I used the Goldcard method from this thread: (google: 452087-tutorials-roms-team-marvelusc-everything-you-need it won't let me post a link because i'm new to the forum)
and you're welcome! I appreciate the time that experienced users take to help out people like me and want to make it as quick & painless as possible!
EDIT: i attached a zip of the recovery.log from CWM from one of the first times I tried to flash the ROM...don't know if it helps.[/COLOR]
heatherelane said:
I haven't tried re-downloading it, I will do that right now. I used the Goldcard method from this thread: (google: 452087-tutorials-roms-team-marvelusc-everything-you-need it won't let me post a link because i'm new to the forum)
and you're welcome! I appreciate the time that experienced users take to help out people like me and want to make it as quick & painless as possible!
EDIT: i attached a zip of the recovery.log from CWM from one of the first times I tried to flash the ROM...don't know if it helps.[/COLOR]
Click to expand...
Click to collapse
Thank you for that link. And if you would, just post back on how the re-download goes. Personally, I didn't see anything in the recovery.log, but maybe a more experienced user would.
kalaker said:
Thank you for that link. And if you would, just post back on how the re-download goes. Personally, I didn't see anything in the recovery.log, but maybe a more experienced user would.
Click to expand...
Click to collapse
still hangs at "Opening update package..."
Are you downloading from your computer then putting it on your SD then flashing or are you using ROM Manager?
Have you tried any other ROMs? Try flashing CM7 (make a backup in Recovery first).
CM7 Link
kalaker said:
Are you downloading from your computer then putting it on your SD then flashing or are you using ROM Manager?
Have you tried any other ROMs? Try flashing CM7 (make a backup in Recovery first).
I first downloaded on my phone and flashed using ROM manager, but this time I downloaded from computer and transferred to SD card using a usb sdcard reader.
downloaded CM7 now. I had CM7 on my Triumph, is this build ok for daily use?
Click to expand...
Click to collapse
heatherelane said:
I first downloaded on my phone and flashed using ROM manager, but this time I downloaded from computer and transferred to SD card using a usb sdcard reader.
downloaded CM7 now. I had CM7 on my Triumph, is this build ok for daily use?
Click to expand...
Click to collapse
This build is pretty good. It has some MMS and WiFi issues, but until Sense 3.5, this was the only ROM I'd use. In fact, I'm using it right now. You'll need to flash the gapps package from Recovery if you do CM7 (which I'm sure you know, since you had CM7 before.)
kalaker said:
This build is pretty good. It has some MMS and WiFi issues, but until Sense 3.5, this was the only ROM I'd use. In fact, I'm using it right now. You'll need to flash the gapps package from Recovery if you do CM7 (which I'm sure you know, since you had CM7 before.)
Click to expand...
Click to collapse
awesome, I might just stick with this. I don't use MMS anyway...what wifi issues are there? I barely get any service in my apartment so I am usually on wifi here.
heatherelane said:
awesome, I might just stick with this. I don't use MMS anyway...what wifi issues are there? I barely get any service in my apartment so I am usually on wifi here.
Click to expand...
Click to collapse
I actually haven't had many Wi-Fi issues, but they've been reported. The thread can be found here. Usually I'll lose WiFi if the phone has been locked for awhile. A quick fix I'll do is Settings>Wireless & Networks>WiFi. Then I'll toggle it off then on and it'll work fine.
Did it flash or have you tried yet?
kalaker said:
I actually haven't had many Wi-Fi issues, but they've been reported. The thread can be found here. Usually I'll lose WiFi if the phone has been locked for awhile. A quick fix I'll do is Settings>Wireless & Networks>WiFi. Then I'll toggle it off then on and it'll work fine.
Did it flash or have you tried yet?
Click to expand...
Click to collapse
just downloaded, flashing now. it's currently on "Installing update..."
latest gapps is still 20110828?
heatherelane said:
just downloaded, flashing now. it's currently on "Installing update..."
latest gapps is still 20110828?
Click to expand...
Click to collapse
Hopefully it works! And yes, 20110828 is still the latest. If you need the download link:
http://goo.im/gapps/gapps-gb-20110828-signed.zip
kalaker said:
I actually haven't had many Wi-Fi issues, but they've been reported. The thread can be found here. Usually I'll lose WiFi if the phone has been locked for awhile. A quick fix I'll do is Settings>Wireless & Networks>WiFi. Then I'll toggle it off then on and it'll work fine.
Did it flash or have you tried yet?
Click to expand...
Click to collapse
it restarts in the middle of installing should I try a newer version of CWM? I'm on 5.0.2.8.
heatherelane said:
it restarts in the middle of installing should I try a newer version of CWM? I'm on 5.0.2.8.
Click to expand...
Click to collapse
What happens if you just reboot the phone? Is it the previous ROM or does it fail to boot?
5.0.2.8 is the latest official version for the Marvelc. I am using a not-so-stable touch recovery koush made before realizing Marvelc is mdpi.
kalaker said:
What happens if you just reboot the phone? Is it the previous ROM or does it fail to boot?
5.0.2.8 is the latest official version for the Marvelc. I am using a not-so-stable touch recovery koush made before realizing Marvelc is mdpi.
Click to expand...
Click to collapse
It fails to boot . tried again and now it's hanging at "Opening update package..."
Alright, let's try redownloading the recovery (http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvelc.zip). Then re-flashing the recovery.
Download that file.
Power off phone.
Reboot to HBOOT (Power + Vol. Down)
Choose Fastboot
Open Terminal/Command Prompt
Code:
fastboot flash recovery <path-to-file>
Where, of course, <path-to-file> is the actual path and don't actually put the angle brackets.
kalaker said:
Alright, let's try redownloading the recovery (http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.8-marvelc.zip). Then re-flashing the recovery.
Download that file.
Power off phone.
Reboot to HBOOT (Power + Vol. Down)
Choose Fastboot
Open Terminal/Command Prompt
Code:
fastboot flash recovery <path-to-file>
Where, of course, <path-to-file> is the actual path and don't actually put the angle brackets.
Click to expand...
Click to collapse
>< sorry...can you back up a few steps...I think I need to install your scripts first from your signature?
If you do not have ADB and Fastboot installed on your computer, then yes, you will need to run those scripts.
Simply open Terminal (they're Mac- and Linux-only) and drag and drop the "ADB Install Mac.sh" into the window. Then hit enter.
Edit: Do the following ONLY if you get a permssion error.
If it says something about permission denied, type
Code:
chmod 755 <path-to-directory>/*
chmod 755 <path-to-directory>/*.*
Note, do not do the file, but the directory their in. For example, if they're on your desktop, do "chmod 755 ~/Desktop/Android/*".
I had problems with koush recovery. So I've stuck with alquez unofficial recovery. No problems at all and I do a ton of flashing. It's better imho
Sent from my HTC_A510c using XDA App
kalaker said:
If you do not have ADB and Fastboot installed on your computer, then yes, you will need to run those scripts.
Simply open Terminal (they're Mac- and Linux-only) and drag and drop the "ADB Install Mac.sh" into the window. Then hit enter.
Edit: Do the following ONLY if you get a permssion error.
If it says something about permission denied, type
Code:
chmod 755 <path-to-directory>/*
chmod 755 <path-to-directory>/*.*
Note, do not do the file, but the directory their in. For example, if they're on your desktop, do "chmod 755 ~/Desktop/Android/*".
Click to expand...
Click to collapse
ok it installed no problem, no permissions error. but now I get this error...
hlane$ fastboot flash recovery /Users/hlane/Downloads/recovery-clockwork-5.0.2.8-marvelc.zip
sending 'recovery' (2014 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
WARNING!
I'm no dev, just someone, that knows linux.
If you follow this path, you do it on your own. I'm not responsible for bricked devices, lost data or whatsoever, including the future the past and the present.
Click to expand...
Click to collapse
There are three ways for you, to make an md5 sum of the img files, the good and the bad one and also the quoted one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
cd /sdcard/clockworkmod/backup/{recovery_timestamped_directory} <- this is from your backup, so you need to fill in appropirate data
md5sum *img > nandroid.md5
Click to expand...
Click to collapse
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
.android_secure.vfat.tar
boot.img
data.ext4.tar
{nandroid.md5}
recovery.img
system.ext4.tar
Click to expand...
Click to collapse
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
Three (the quoted one)
Also on the 2nd page you will find an alternative solution for the problem which can help you if you have got busybox installed on your device.
The solution resembles the One type of fix, so with quotes here's the one (thanx for Meeshka for it).
Meeshka said:
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
Click to expand...
Click to collapse
If I helped, don't hesitate to push the Thanks button.
Thanks... a very useful guide. Bookmarked
WORKED!!! Tho I'm from a different device the first (adb) method saved my AOKP backup!!! Daysaver I'd say!!
I keep getting "md5sum: not found"
Put this in the general android section as it works across most devices. ..
Sent from my One V
Nevell said:
I keep getting "md5sum: not found"
Click to expand...
Click to collapse
if you send me the 2 img files i can create an appropirate md5 image of them, but send the one you did, so I can guess what the problem is.
send them to the email of my usr here, or in pm. and mainly, the md5 image has the name "nandroid.md5" like small caption all the way, even the md5? If it is there where it must, it must work, ad absurd it will be "wrong checksum error", but that is another version.
General android section has this, I have learned this from there, but it had only 1st option, and was "discovered" when cwm had generated wrong md5s, the V, in the V the problem is a tad bit different, but the solution is the same.
I fixed it in adb
Sent from my SPH-L710 using xda premium
Nevell said:
I fixed it in adb
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Can you explain what did you do to fix md5sum: not found error??
please i need it!
thatsgamer said:
Can you explain what did you do to fix md5sum: not found error??
please i need it!
Click to expand...
Click to collapse
Just created an md5sum manualy from the img files with the name of nandroid.md5, because on the V the recovery doesn't creates them because of cache mount problem.
The recovery process will end in an error message, because cache cannot be recovered, but the main thing will be recovered this way.
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
haky1988 said:
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
Click to expand...
Click to collapse
See : http://forum.xda-developers.com/showpost.php?p=32248108&postcount=7
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
CWM showing different versions
-Delete-
maranello69 said:
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
Click to expand...
Click to collapse
You do know that the first method is exactly like the one you linked right?
Aside that, I'm happy that the community could help you out
Loir can u help me. I can't locate the boot.img inside the downloads for cyanogen mod u provided. Forgive me but can you post a directory to this kernel file? Tks
Sent from my HTC Desire X using xda app-developers app
Thank you so much. You saved my phone.
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
no * 's
Ken-Shi_Kun said:
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
There are two ways for you, to make an md5 sum of the img files, the good and the bad one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
If I helped, don't hesitate to push the Thanks button.
Click to expand...
Click to collapse
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Beastben13 said:
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Click to expand...
Click to collapse
I have done the thing with a legacy tcmd, so there is a probability, that they have modified the md5sum algorithm, so if you don't se the stars don't panic. (also it should do the trick even with stars in the file, but wanted to be sure at the time I wrote the post)
plz provide touch recovery for karbon a9+ plz and ther is bugs in cwm recovery 5.0.2.8 plz