Related
Hey guys I have a stock G1 that was given to me and I can't access the wifi settings thus I cannot sign in. I believe I have the latest update. Anyone know a way around this?
http://forum.xda-developers.com/showthread.php?t=452316
B-man007 said:
http://forum.xda-developers.com/showthread.php?t=452316
Click to expand...
Click to collapse
Does not work with the very latest AOSP update : (
cars1106 said:
Does not work with the very latest AOSP update : (
Click to expand...
Click to collapse
You need to root your phone.....Read the stickys at the top of this section to learn how
It has been rooted before. then I unrooted it gave it to someone to use, it got updated and I don't have a sim with data and now I can't do anything with it. I guess I will have to downgrade via SD stick somehow through the recovery menu and try and run the exploit again.
if your one of those one-click rooters....your out of luck
you will have to root the old fashion way.....hint: RC29 DREAIMG.nbh
B-man007 said:
if your one of those one-click rooters....your out of luck
you will have to root the old fashion way.....hint: RC29 DREAIMG.nbh
Click to expand...
Click to collapse
Yup, I had the same issue, downgrade to RC29, then follow this:
**Originally Posted by dizzydevil111**
please make sure you have rc29 or lower by typer (enter)reboot(enter)
if the phone reboots then you have rc 29 or lower.
if not, follow this guide to downgrade to rc29
2. Mount your SD card in Windows and reformat it as FAT32. The HTC
bootloader won't be able to see the RC29 (or RC7) image otherwise. Make
sure you back up all your files first!
3. Download the appropriate image (RC29 for USA or RC7 for UK) from
http://koushikdutta.blurryfox.com/G1/DREAIMG-RC29.zip or
http://koushikdutta.blurryfox.com/G1/DREAIMG-RC7.zip . This is a DOWNGRADE
to the Android version that contains a root shell bug (this exploit just
seems too easy). I got these files from the forum thread
http://forum.xda-developers.com/showthread.php?t=442480 .
4. Extract the DREAIMG.nbh file from the downloaded zip archive and copy it
to your SD card (again, for me, this had to be formatted as FAT32, not just
regular FAT which is the default). Don't put it in a folder, just stick it
directly on there.
5. Disconnect the SD card the right way (eject, unmount, or otherwise tell
your OS you are unplugging it) to make sure the data gets written. If you
used an SD card reader, put the SD card back in your phone.
6. Make sure your phone has a full battery, then turn it off. Turn it back
on by holding down the CAMERA and POWER buttons. This should get you into
the HTC bootloader (the funky red, green, and blue screen).
7. If everything was done correctly, the bootloader will detect the image.
You'll be taken to a different screen that asks you to press the POWER
button to install the image. Do this, but beware, you will lose all your
saved data on your phone (with the exception of things that are synced with
Google's servers, like contacts, calendar, Gmail, etc.).
8. Wait for the update to complete. The progress bar will fill up, then
all the steps will say OK beside them, and finally, it will ask you to press
the "action key" (I think this means click the trackball). DO NOT do
anything until you see this message. The progress bar needs to DISAPPEAR,
not just fill up.
9. You now have the stock RC29 installed. Take out the battery, put it
back in, and turn on your phone. It should ask you to activate your Google
account again -
once you have this done type on the phone again (enter)setprop persist.service.adb.enable 1(enter)
your pc should now pick this up as an android adb device
point it to the correct drivers found in the file called androidusbwindows
once that installs, extract the adb file anywhere on your pc. (best place is root directory)
open up a dos command prompt and type (cd ..<enter>)
then type (cd ..<enter>)
then type adbshell
should look like this thereafter
$
referring to the dollar sign
then copy the following line into your dos command prompt and press enter
(am start -a android.intent.action.MAIN -n com.android.settings/.Settings)
please make sure that you copy the contents of adbwin.zip in your ROOT FOLDER or else you will be going through hell
voila you should be able to access wifi
pm me if it worked for you
The purpose of this document is to clarify a few basics about HTC Android Phones and basic commands to interface with the phones. Think of this as a beginner's guides to the Android device from a non-traditional user's point of view. I'll keep it simple and plain as much as I can for the new users. I'll also try to keep all the technical aspects true as much as I can while keeping it simple.
Before you go on, please read this and understand the basic concepts and how and why following commands are being used. Do not follow anyone's instructions/tutorials/guides without prior basic understanding of what each command do. I do want to believe it's humans visiting this forum and not lemmings. If you do not understand, feel free to ask here. I will or someone else also knowledgeable will answer your questions. DO NOT QUOTE THIS AS A WHOLE. My pet peeves and a complete waste of screen space.
Sometime, depending on your OS, command names may change (e.g: mouse / mouse.exe / mouse-linux / mouse-mac). For general purpose, we'll use mouse instead of an OS specific commands in this instructions.
So to repeat myself, if you understood the concepts of the commands, and you are on a linux system and someone's guide says touch index.php, you will automatically type touch-linux or whatever the name of your executable is on your system.
We shall assume you know how to install needed drivers and where to get android sdk and put the sdk binaries (executables) in the system path. If we need to expend this let me know and I'll expend this here.
Further, if I get any parts wrong, PM me and I'll get those parts corrected.
Android Partition, SPL etc.
Partitions:
Followings are a list of partitions on your android phone.
misc - misc partition -
recovery - Recovery Partition - This is where the original HTC recovery or Amon Ra's recovery or any other Recovery would go. Basically if you reboot into recovery it'll boot from here.
boot - This is your boot partition
system - This is where all your system information (ROM resides)
cache - cache (When you factory reset the phone, this area is wiped)
userdata - user data (like your login, your user settings etc) When you factory reset the phone, this area is wiped)
So, if you replace the recovery image, you are pretty much set for updates provided here at XDA. Note: By replacing your recovery image, you may not be able to have OTA updates.
ROM images will normally replace boot and system images at the same time and often time, userdata and cache too; reseting the phone completely.
SPL/Bootloader/Radio/Bricking Phones:
SPL / Bootloader is like BIOS on a computer. At least I think of it that way. SPL can be updated! SPL comes as either Security-On of Security-Off (S-ON/S-OFF).
Note: It is my understanding that radio will boot first, followed by other systems. So it is IMPORTANT that your radio image/version will work with your SPL image/version. This is the one and only reason for phones being bricked. You can not brick your phone by flashing a ROM or Boot image or recovery image. Once you flash the wrong radio for the SPL, the only known method of recovery is to send the phone back into HTC for repair.
How do I know the phone is bricked? A bricked phone can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked phone via adb or fastboot. You can only see one screen on the phone and it will be the first splash screen.
Commands:
adb - Android Debug Bridge - One of the two things you'll need to know if you ever want to do anything non-conventional on your android based phone.
List of commands that can be used by adb can be prompted by typing adb at the system shell (command prompt or terminal)
Notable adb commands:
adb devices - If you don't know anything, this is the ONE thing you have to know.
adb devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
adb reboot (bootloader|recovery)
adb reboot - this will reboot your phone normally.
adb reboot bootloader - this will reboot your phone back into the bootloader (white screen with the android on wheels)
adb reboot recovery - this will reboot your phone back into recovery console (either default or amon_ra's recovery).
adb shell - this will shell into the phone and you can now explore the phone. Remember phone's native backend os is linux so know your linux commands.
adb remount - remounts the system partition on the phone so you can you read/write to it.
adb push xxx yyy - will push xxx file from computer into yyy location/file on phone (needs rooted access)
adb pull xxx yyy - will pull xxx file from phone into yyy location/file on computer (needs rooted access)
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Notable fastboot commands:
fastboot devices - If you don't know anything, this is the ONE thing you have to know.
fastboot devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
fastboot reboot - this will reboot your phone normally
fastboot oem unlock - this will unlock your bootloader - NOTE THIS WILL VOID YOUR NEXUS ONE WARRANTY
fastboot erase XXX - Will erase the partition XXX (such as userdata, cache) - mainly used for resetting phone and clearing userdata / factory settings.
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image.
e.g: fastboot flash system system_update.img will flash/update your system partition with an image called system_update
If anyone needs me to dig deep into using anything else, please PM me. I'll add it on here. Hopefully this will help all newbies about the basic commands and what they do.
FAQs (UPDATED Feb 09, 2010)
Q: One question about the Android SDK. Do I need it to flash my N1 or just to program new apps? Where can I get it?
A: Android SDK is not entirely needed to flash the N1. However, there are tools in there that you need. Adb / Fastboot etc. Although they can be downloaded by themselves, the windows version of the SDK also have the Drivers that are needed for android devices for USB connection. So, it is recommended to get it. You can get it from developer.android.com
Q:I have never experienced anything like this when I did a hard-spl on my winmo phone. Radio versions are included with SPL's, right?
A: Official packages from HTC did come with nbh packaging, meaning it is a all in one upgrader that will update Radio, ROM, System etc, it is very much common for active development area here at XDA to get the radio or SPL or ROM separately and independently of one another. And as such, you will most likely flash them seperately (who wants to wait 6-8 months). Also, since this phone is released by google, HTC will most likely not update any major Radios. However, it is very likely that we will be hacking in Radio updates or any other "updates" from HTC from their new device - HTC Bravo.
Q: Is there a guide for snow leopard? I'm kind of stuck.
A: I personally ran android SDK and aforementioned executable on both MAC OS 10.5 and 10.6. Like I posted, the commands and the executable names may be slightly different. I may call adb and you may find it as adb-mac. I am not going to write 3 separate documents for 3 separate OSes. You have to know that adb=adb-mac (on your mac), adb-linux (for linux) etc. And yes the above guide will work universally.
Q: Can i replace the splash image..?? (unlocking related)
A: As of the above date (next to the FAQ) no you can not. Issue is probably a few folds. One of them is that splash1.img is not going in due to security lock. Remember, you unlocked the phone. HTC will not like it. Anyhow, I like the current quad color X. If you are thinking of getting rid of the lock logo, good luck. Even if you can get rid of it, you will still have to overcome the pink text that says ***UNLOCKED*** on your bootloader.
Q: Can you run Windows Mobile on Android Phones?
A: With enough resources given, sure. Will it ever happen? No. Why? Windows mobile compiler and builder cost $. As a matter of fact, as of version 5, it was going to cost me $75 per device. That's one of the reasons why handset makers went to Android open platform. Android is free and universal so as long as you use certain chipsets and certain items, you are good to go. Can it ever be ported? Sure. With right amount of time and money anything can be done. But at this point, it's cheaper for you to go buy a windows mobile smartphone.
Q: How do I know the phone is bricked?
A: You can not brick a phone unless you are flashing Radio/SPL packages. Make sure if you are doing that, you follow directions VERY CAREFULLY. A bricked phone can not boot into bootloader, recovery, or into normal operation modes. You can not connect to a bricked phone via adb or fastboot. You can only see one screen on the phone and it will be the first splash screen.
Q: I have installed the Android SDK however, i cannot seem to get the laptop to detect the nexus. What have i left out?
A: Most common item that people forget to enable is USB Debugging. Settings => Applications => Development => USB debugging [checked]
Q: I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
A: You still have the stock (shipping) recovery. If you want a different recovery (Amon RA's), download it, the from fastboot, run fastboot flash recovery downloaded_recovery.img
Q: Which step of the rooting / recovery procedure does it give root?
A: Root and Recovery are two totally different things. Recovery is a partition that contain recovery information. Stock recovery is what allows OTA updates etc. Normally it will search for update.zip in the root folder of the SD card. Amon_RA's Recovery or any other recovery images are there to enhance the traditional stock recovery. Amon Ra's Recovery for example, contains thing such as ability to update from different zip files, and backup/restore of your data/system.
Rooting is not done by recovery but is a kernel level access (simply put) that will give root or "SU". It is done by patching the boot partition of the your android device.
Q: What are the differences, advantages, disadvantages of the different ROM's?
A: They are all different. Some have some features, some are plain stock, some are made for bleeding edge kernel etc. You'll have to try them out and figure out yourself. I may make a chart of what they are (see the bottom at my signature - wiki) but with too many android devices, I will need some major help. One person alone will not have total knowledge of all the ROM releases. There are just way too many devices and ROMs.
Q: Which ROM will allow OTA updates?
A: Stock ROM WITH Stock Recovery.
Q: If the phone is SIM/carrier unlocked and you root do you have to SIM unlock again?
A: SIM/Carrier unlock has nothing to do with rooting your phone. You can still have root and still be carrier locked. Nexus One comes carrier unlocked from factory.
Q: How much space is there for apps? is using the sd card really necessary? (on Nexus One)
A: Search google? The phone has 512MB or space. That SHOULD be more than enough for you. If not, you have some serious issues. I do not believe you will not App2SD for Nexus One. Google did say during the release conference that they will update Android/N1 so that apps can be run/installed to SD but that requires some system and security changes (mainly to prevent pirated software - Yes if I write something, I deserve to get paid for it).
Q: When you do "flash zip from sdcard" or "fastboot flash image" does this merge and overwrite the files in to the partition?
A: When you update a software (via recovery), software my be merged. However, if you fastboot flash, just like the word flash says, it will flash and overwrite the partition.
Q: Which partition does "flash zip from sdcard" affect?
A: Depends on what you are flashing. It could be any or all of the partitions such as SPL, Boot, System, Recovery, Radio. You should study first before randomly flashing things.
sorry, got it!
blakestimac said:
i apologize if this is the wrong place for this but, but i have adb setup perfectly, but fastboot is not recognized at all. could i have missed something?
Click to expand...
Click to collapse
I need your system info.
What os are you running? where did you get fastboot? what are you trying to do?
Don't forget fastboot boot for testing images. My most used command
I still have no idea how to use or setup adb i have downloaded the sdk and used fastboot and superboot to root my phone and am currently running the cm 5.0 beta 2 rom and want to learn how to use adb so i can enable the ram. Thanks, Joe
really a noob question here.....it wa easier with Hero.
i have installed the Android SDK
however, i cannot seem to get the laptop to detect the nexus.
what have i left out?
wishmaker738 said:
really a noob question here.....it wa easier with Hero.
i have installed the Android SDK
however, i cannot seem to get the laptop to detect the nexus.
what have i left out?
Click to expand...
Click to collapse
Check the FAQ.
dylanfan424 said:
I still have no idea how to use or setup adb i have downloaded the sdk and used fastboot and superboot to root my phone and am currently running the cm 5.0 beta 2 rom and want to learn how to use adb so i can enable the ram. Thanks, Joe
Click to expand...
Click to collapse
Ok. I need to know what you actually did. I am not understanding what you are trying to do.
Can't run adb commands - device not found
Thanks for the info. I am having an issue with running adb commands. My phone is rooted via superboot and I tested it with Nexus Torch which works. Now I am trying to install the new kernel so I can run the wireless tether app... but I can't get any of the adb commands to recognize the phone. I boot the phone by holding the trackball and power button. I am in USB debugging mode. When I run fastboot devices, the phone serial number shows up. When I run adb devices, it says no device detected. And when I try to run any other adb commands they do not work, even though fastboot commands work. Any ideas? Thanks.
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
dylanfan424 said:
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
Click to expand...
Click to collapse
I'm a noob so can't offer much help...but I would make sure the usb drivers are installed if you're using windows....this probably should have happened when you installed the sdk, but you can also install it through the device manager and point it to the folder where the usb drivers are located. Also make sure the phone is in USB debugging mode. also you may need to reboot your pc. Make sure you have setup running when you run the adb commands. you need to be in the same directory as the adb file, or in the case of the superboot pack you need to type "adb-windows" not just "adb". you may also need to put .exe, ie adb-windows.exe.
pwnvds said:
Thanks for the info. I am having an issue with running adb commands. My phone is rooted via superboot and I tested it with Nexus Torch which works. Now I am trying to install the new kernel so I can run the wireless tether app... but I can't get any of the adb commands to recognize the phone. I boot the phone by holding the trackball and power button. I am in USB debugging mode. When I run fastboot devices, the phone serial number shows up. When I run adb devices, it says no device detected. And when I try to run any other adb commands they do not work, even though fastboot commands work. Any ideas? Thanks.
Click to expand...
Click to collapse
You run fastboot from the white screen. Android on non-white screen. It's one or the other. It's ADB or Fastboot (depending on the mode of the phone).
dylanfan424 said:
Sorry i was pretty vague before i down loaded the sdk and also installed the adb setup file included with the superboot pack but just have no idea how to get it to work and add things through adb. I tried typing adb commands into comand line with the phone connected to the computer but nothing happend. just said not recognised command so i just basically need a rundown of how to setup adb.
Click to expand...
Click to collapse
Is the directory where ADB/fastboot (SDK) is installled in your system path?
I am guessing it's not. If it was, just by typing adb alone (without commands), it'll give you a list of commands. Click here if you want to know how to change your system path to include a particular folder.
We're now in the age of nintendo pilots and point and click OS that no one knows how to use command lines and system paths anymore.
recovery
I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
umplarry said:
I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
Click to expand...
Click to collapse
Answered in FAQ area.
seraph1024 said:
Answered in FAQ area.
Click to expand...
Click to collapse
I tried that before I posted. I searched the FAQ again. Maybe I am a complete DA, but still can't find answer. I don't mind searching, it will help me to learn, but could you point me in the right direction in FAQ?
umplarry said:
I tried that before I posted. I searched the FAQ again. Maybe I am a complete DA, but still can't find answer. I don't mind searching, it will help me to learn, but could you point me in the right direction in FAQ?
Click to expand...
Click to collapse
Q: I have rooted n1. when I go to recovery to do backup, I get the triangle with the little green android guy, but phone is stuck there. I have to remove battery to reboot phone. What have I done wrong?
A: You still have the stock (shipping) recovery. If you want a different recovery (Amon RA's), download it, the from fastboot, run fastboot flash recovery downloaded_recovery.img
Click to expand...
Click to collapse
There you go.
seraph1024 said:
There you go.
[/B]
Click to expand...
Click to collapse
Thanks for your help
seraph1024 said:
There you go.
[/B]
Click to expand...
Click to collapse
I had it downloaded, just had not flashed it
I've been looking all over, but I probably need to check the HTC Dream forum or something.
How do I install a custom ROM? I know you have to adb push update.zip somewhere, but I can't find any info about this. Please help.
I'm Fairly savvy with computes and technology this has me at hump
what i have
Usb coard
Sd Card
G1 Phone
Windows 7
Q.A) how do i know what model stock version i have on my G1? ( I AM stuck at the google activation screen, so i can't go in and check
B. I downloaded everything i need to, Drivers and on my device manager i see ADB device and it shows HTC Dream
C. My SD Card is not showing up or is grayed out almost as if the g1 is not even reconginzing it.
I really can't do anything as far as rooting without a sd card, so how do i make my phone reconginze it?
U have to activate it I think to be able to mount your sdcard to the computer or to get the info for your phone so start there. Then I beloved holding volume down and power will get u the info. When u plug your phone in u have to pull down from top of phone and click mount to get SD on computer
Sent from my Chromatic Magic using XDA App
damn, i live 4 hours from the nearest T-mobile store
U don't have a sim card with them I take it? Or a friend who does. Lol
Sent from my Chromatic Magic using XDA App
freshkid87 said:
damn, i live 4 hours from the nearest T-mobile store
Click to expand...
Click to collapse
Call them or go on the web and order an activation kit, they'll mail it to you.
alright man im help you out get passed that jus follow these instructions
But what you can do is check your hboot and what bored you have!
power down and hold camera buttong and press power
keep it held down till you see 3 tri colors, and make sure your hboot is not 1.33.005 or something along those lines
if its at 0.005.00 something then you can use the Dreaimg and go down and then use these instructions to get passed it then do the telnet root, and from there follow root instructions
if you have white screen with 3 skateboarding androids and hboot 1.33.2005 then you have (death SPL) but im sure your still on stock hboot and all but you can check what bored you have and grab the right Dreaimg for your phone
First, You must have either RC29 or earlier, or modded RC30. It won't work with official RC30, sorry. If you don't know for sure what version you have, but you know you haven't installed a modified RC30 build, then the easiest way to check is to reboot the phone, and once it starts up and is showing the "click the android to begin" screen, or the "no sim card" screen, then type the following on the phone keyboard
<enter>reboot<enter>
If it reboots, then you have RC29 or ealier. Otherwise you have RC30.
Second, you must have adb installed on your computer, and have the USB drivers installed, or at least ready to install when it asks for the driver when you connect the G1. See this page for details on how to get adb working: http://code.google.com/android/intro...devicehardware
Third, you must have a wifi network that you can connect to.
There are too many possibilities to write specific step-by-step instructions for every case. So I will give an overview of the process instead. If someone else wants to write some specific instructions, that would be welcome
-----------
When you start up the phone without a sim card, it goes into a locked screen that says "no sim card found", and you can't even get into the registration app. So the first step is to get around that screen. You have to connect to your phone with adb shell and get root access, and then type the following command:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "INSERT INTO system (name, value) VALUES ('device_provisioned', 1);"
And then reboot the phone. When it starts up again it will go into the registration screen instead of the locked "no sim card" screen.
This assumes that you have the sqlite3 binary on your phone. This binary is provided in RC30 v1.2. Alternatively, you could manually copy the binary to your phone with adb push, or put it on the sdcard and copy it to your phone. I can post a copy of just the sqlite3 binary if needed.
-----------
The second step is to enable and configure wifi, so that the registration process can connect to the google servers. In an adb shell session, type the following command:
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
This doesn't have to have root access to work. It works fine with the "shell" user that adb on non-modded phones runs as.
That command will bring up the settings page on your phone. From there, you can enable wifi and connect to your wifi network, and then proceed with registration as per normal
Click to expand...
Click to collapse
Turkeys' ULTIMATE Guide to Rooting v42.1.2
Note: It does not work on 2.2.1 Wildfire's (i.e. - Any bought after Feb - March 2011)
Like this guide? Hit the thanks button at the bottom left of this post
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
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
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...
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...
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!
A2SD
Note: It has come to my attention that doing this with ROM Manager doesn't work most of the time. If you have problems please partition your card another way. (I recommend GParted - There is a Live CD if you don't have Linux)
First, we need to partition your SD card with ROM Manager. This will wipe all the data on your SD card so please backup before continuing.
1) Open ROM Manager (Download it from the Market if you don't have it - Although you will need the Market Mod to show all apps) and press Menu > Manually Override Recovery **Not sure exactly what it says, pls could someone help me out here** Then scroll down to Partition SD Card. Choose the ext size you want for your apps to be installed on, then tap 0 for swap size, then tap OK to reboot into recovery and start partitioning!
Note: While it's partitioning it will show a picture of an Android. You can press (Power?) to see what it's actually doing and if there's any errors.
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 Buzz. Now, you need to recall what version of Android you were on before you rooted. 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 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 good measure.
I'm sure this will help many people. Should be sticky'd
HCDR.Jacob said:
I'm sure this will help many people. Should be sticky'd
Click to expand...
Click to collapse
Good Idea!!!
For the rru you need to click on the windows mobile section and select buzz NOT bravo
Added A2SD guides, misc fix & unroot guide. Bump to v42.1.2
Many Thanks,
Helps loads confirm my thinking after a couple of days reading, I just have to grow some balls n take the plunge
My main concern is my WF is a UK Voda PAYG which I believe is locked n I'm unsure whether I should get n unlock code before doing anything.
I did read in a Desire thread that updating a stock rom without a sim could unlock, but haven't seen any other refs to unlocking WF other than code.
Note: Unroot section still refers to Desire Bravo not WF Buzz
Thanks agin
PanGalactic said:
Many Thanks,
Helps loads confirm my thinking after a couple of days reading, I just have to grow some balls n take the plunge
My main concern is my WF is a UK Voda PAYG which I believe is locked n I'm unsure whether I should get n unlock code before doing anything.
I did read in a Desire thread that updating a stock rom without a sim could unlock, but haven't seen any other refs to unlocking WF other than code.
Note: Unroot section still refers to Desire Bravo not WF Buzz
Thanks agin
Click to expand...
Click to collapse
You shouldn't need to unlock or anything.
Thanks, I'll change that bit now
42turkeys said:
You shouldn't need to unlock or anything.
Thanks, I'll change that bit now
Click to expand...
Click to collapse
And buzz is under windows mobile for some reason
The guide really great....but the shipped rom website don't have RUU for Buzz
coltrain said:
The guide really great....but the shipped rom website don't have RUU for Buzz
Click to expand...
Click to collapse
Look under windows mobile - who put it there? Those files do work.
This thread still not stickied?
Piece of art already. Should be stickied for sure.
I thought a bit about 'reporting' the thread to make a mod notice it but it said specifically what report was to be used for , so i didn't do it , i guess we'll have to bump it up so it gets stickied. Great post !!
AlphaRev X Beta is now available for Wildfire/Buzz users stuck on 2.2.1 with HBOOT 1.01.0001 and above. This will make your Wildfire/Buzz s-off and give you the ability to get root. Follow this excellent guide http://forum.xda-developers.com/showthread.php?t=1130881
If you have downgraded to a 2.1 rom and want to get back to official 2.2 rom to use Alpharev X Beta or have HBOOT 1.01.0002 and want official 2.2 with HBOOT 1.01.0001 to use Alpharev X Beta follow this excellent guide http://forum.xda-developers.com/showthread.php?t=1132028
Thanks to all who made this method possible and to those who developed the tools used etc.... This is not my work just trying to simplify it.
I accept no responsability if you brake your phone
Will NOT downgrade the HBOOT but useful if you need to go back to stock 2.1 rom.
Right Here we go:-
Downloads you will need:
Android SDK:- http://developer.android.com/sdk/index.html Google search for a guide to setting this up and read the guide carefully so you know how to use adb.
HTC Sync:- http://www.htc.com/uk/SupportDownload.aspx?p_id=316&cat=3&dl_id=1073 Basically for the drivers to use adb as these are included with htc sync you no longer have to install drivers from sdk to use adb.
HEX Editor:- http://mh-nexus.de/en/downloads.php?product=HxD I suggest you find a guide on making a GOLD CARD as you will need a GOLD CARD any way, this will get you ready and use to using the hex editor later in this guide.
Super One Click:- http://forum.xda-developers.com/showpost.php?p=10452428&postcount=43 Download un zip it and save to pc.
Flash_Image:- http://www.android-hilfe.de/attachm...-how-rebrand-o2-desire-fertig-flash_image.zip un zip and save somewhere on your pc you will remember.
A 2.1 rom RUU to downgrade to:- http://shipped-roms.com/index.php?category=android&model=Buzz Choose the one that best suits you WWE=Unbranded or chose one for your provider/carrier, download and save to ur pc.
Now your have set up the Android SDK you know what ADB is and how to use it (hopefully), you have created a GOLD CARD, you have installed HTC Sync, you have downloaded the 2.1 RUU.exe you want to downgrade to, you have downloaded Super One Click 1.5.5 and un zipped it and save it to ur pc and you have dowloaded the Flash_Image and un zipped it and place on ur pc.
Ready Here We Go:
Step1 - Open Super One Click and press SHELL ROOT it will run its commands and will give you temp root. You will see rooted at the bottom when its done. Try again if it says FAILED it may take a couple of attempts. ( Make sure you have adb working ) and (make sure usb debugging is ticked on your phone and unknown sources tho im not sure if unknown sources needs to be ticked, mine was and that when you plug your phone it the pc via the usb cable you select charge only on the phone)
step2 - open a cmd (command Prompt) on your pc and type adb shell (if you installed the android sdk and read about how to get to adb shell you will have no problem) (for me i type cd C:/android-sdk-windows/platform-tools and hit enter, the type adb shell. (if you see a $ try shell root in super one click again, if you see # your good to go).
step3 - copy the mtd0 file to sdcard.
(in cmd type) cat /dev/mtd/mtd0 > /sdcard/misc.img
step4 - move the misc.img to your pc and use the hex editor to edit it. (run HxD as administrator click extras, open disk image and select your misc.img you just got from your sd card).
step5 - go to 11th row down, you will find current version number at
the end of that row.
step6 - Change it to 1.25.405.1 if you want to use "Ruu_Buzz_HTC_WWE_1.25.405.1", the press file and save. (change the numbers to match the 2.1 RUU you are going to downgrade to (common sense) ok)
step7 - copy the flash_image (the one you downloaded at the start of this guide) and misc.img back to your sdcard.
step8 - (in cmd type) cat /sdcard/flash_image > /data/flash_image
step9 - (in cmd input) chmod 755 /data/flash_image
step10 - (in cmd input) /data/flash_image misc /sdcard/misc.img
Now you can flash offical android 2.1 RUU rom you downloaded earlier (don't forget to make gold card).
Now your on Android 2.1 but your HBOOT is still version 1.01.0001, so Unrevoked still wont work. So still no full root as yet.
Once again not my work just trying to keep everything simple and in one place, ALL THANKS TO ORIGINAL DEVS AND GUIDE CREATERS. BUY THEM A BEER.
Thanks for making this clear, then i wont have to explain it in details
Notice Adb is included in the SuperOneClick directory
Birthe88 said:
Thanks for making this clear, then i wont have to explain it in details
Notice Adb is included in the SuperOneClick directory
Click to expand...
Click to collapse
Yip lol. Ive been asked so many times on how to do this because i posted on a thread that i done it, so i thought i would try and give a step by step brake down of how to do it lol. i wrote it all out the other night went to submit the thread and it wiped cos i got signed out while typing it up (gutted lol) so here it is, hope its clear enough for every one.
Tried it but keeps saying waiting for device and then loops
elinho said:
Tried it but keeps saying waiting for device and then loops
Click to expand...
Click to collapse
Just updated link to super one click download that i used should work now also have usb debugging and unknown sources tick on your phone as i did whilst using super one click.
elinho said:
Tried it but keeps saying waiting for device and then loops
Click to expand...
Click to collapse
my phone got this loop, too
i even tried in fastbat and recoevry mode...
edit:
just try another usb port, not at an hub
Can someone confirm this and create a video tutorail of this?
thanks in advance.
MarkPower said:
Can someone confirm this and create a video tutorail of this?
thanks in advance.
Click to expand...
Click to collapse
Confirmed - make sure to have proper drivers, adb working, put phone in charge only usb mode + usb debugging
This How To works but its useless hboot cant flashed.
For clockwork-recovery is a flashed hboot needed to get Nandroid.
save your time and wait for unrevoked update
PS: find a way to zip a edited orginal rom with changed hboot or find a way to take of the siganture verification this is the way to get full root
INET.exe said:
This How To works but its useless hboot cant flashed.
For clockwork-recovery is a flashed hboot needed to get Nandroid.
save your time and wait for unrevoked update
PS: find a way to zip a edited orginal rom with changed hboot or find a way to take of the siganture verification this is the way to get full root
Click to expand...
Click to collapse
Its not useless if you need to flash back to a 2.1 rom for any reason, which is why i made the guide because i was asked by a few people who did not like the 2.2 update or were experiencing problems on 2.2 that they were not on 2.1...
Will superoneclick allow you to do temproot so you can use root apps
Sent from my GT-P1000 using XDA App
brilldoctor said:
Will superoneclick allow you to do temproot so you can use root apps
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
It gives you temp root so you can downgrade to a lower rom but I couldnt get it to work with titanium or get su permission in terminal app on the phone! have not really tested past the downgrading stage yet will update if I get any more info.
dj_destruction said:
Its not useless if you need to flash back to a 2.1 rom for any reason, which is why i made the guide because i was asked by a few people who did not like the 2.2 update or were experiencing problems on 2.2 that they were not on 2.1...
Click to expand...
Click to collapse
2.2 is more stable and use less of ram and the radio reception is better for most providers.
superoneklick cant give the access for root apps its shell root not file system root
I read somwhere a technique that involved fooling a RUU installer to apply an older rom by replacing some file(s) with older one(s).
I too am stuck with 2.2 and hope to see an easy way to set my phone free
Sent from my weak Wildfire, can't wait to trade in for HD2.
try this>>>>>
open the ruu setup and do not click on and let it open, look in the temp directory of your windows user, according to the extracted files of the setups and replace try something there maybe it will work, I have not tried it yet because most processed rom . zip files stop at the signature and the md5 check.
As if I wan to downgrade my wildfire in order to root . does it downgrade work ? Because u said tat "Will not downgrade the HBOOT" . Newbie here.. dont flame me~ thx..
wait for an other way to root. Downgrading the rom to 2.1 dont give a possible way to root because it will still have the new hboot. The unrevoked team say weeks a go that they are working on it but i guess still without succes. Just wait a read the forums.
I have extracted the 2.2.1 firmware and the rom.zip file within it!
--------------------------------------------------------------------------------
Hi i am unable to post in Dev area, I have managed to extract the .exe from the 2.2.1 to revel all the files including the rom.zip file to which the hboot file is in there.
Do you think we can change the hboot file and fake it to think its 1.01.001 when infact is a hboot file that can be rooted.
I am kind of new to the android platform but not to linux. My device came with 2.2.1 pre installed. This is just a idea weather it will work i don't know.
Could you post this question in the forum that you posted asking the same question with the words that i have managed to extract everything. Thanks
this was a pm sent to me, i am just posting it incase any one can answer
dj_destruction said:
I have extracted the 2.2.1 firmware and the rom.zip file within it!
--------------------------------------------------------------------------------
Hi i am unable to post in Dev area, I have managed to extract the .exe from the 2.2.1 to revel all the files including the rom.zip file to which the hboot file is in there.
Do you think we can change the hboot file and fake it to think its 1.01.001 when infact is a hboot file that can be rooted.
I am kind of new to the android platform but not to linux. My device came with 2.2.1 pre installed. This is just a idea weather it will work i don't know.
Could you post this question in the forum that you posted asking the same question with the words that i have managed to extract everything. Thanks
this was a pm sent to me, i am just posting it incase any one can answer
Click to expand...
Click to collapse
nice idea. I have tried to replace hboot img.zip with a clockworkmod once,but signature failure came up. I will try also your way although i don't know much.hopefully a solution will be released SOON.
beastaki23 said:
nice idea. I have tried to replace hboot img.zip with a clockworkmod once,but signature failure came up. I will try also your way although i don't know much.hopefully a solution will be released SOON.
Click to expand...
Click to collapse
Nice try. And if you test with the img.zip from the older official RRU?
Sent from my HTC Wildfire using XDA App