Flash new recovery to Wildfire the Easy Way - Wildfire Android Development

I found this after searching around for ages on a way to upgrade the recovery on my Wildfire/Buzz, all the friggin fastboot methods weren't working. This worked straight away, no errors, no problems.
Flash a New Recovery Image
1. Find the recovery image you want and MAKE SURE IT IS FOR YOUR PHONE (should say in where you download it what phone it is for)
2. Rename the filename of the recovery image EXACTLY as it is written to recovery.img
3. Put the recovery image file on the SD card (not in any folders)
4. Download Android Terminal Emulator from the Market (there are a few different terminals in the Market some have an onscreen keyboard and some don’t experiment till you get one, also hold down Menu in some of them to bring up the onscreen keyboard if you don’t see it)
5. Open the Terminal program and type the following (with hitting enter at the end of each line):
su (press enter)
(at this stage it will ask you for superuser permission to access your core system. Allow the access)
su (press enter)
flash_image recovery /sdcard/recovery.img
6. Phone should pause for a second and then show you a new blank line. Turn it off and back on by holding down Home and Power to ensure it flashed correctly. Done.

Error
flash_image: not found
Sdcard is fat (not fat32). Any idea.
Sent from my HTC Wildfire using XDA App

EDIT - Sorry, Wrong method, here's the correct one:
First, make sure you have the latest Android SDK, then:
Connect the device to your computer
Copy recovery.img to the root of your SD card
Open term on your computer and run: adb root adb remount
Flashing the custom recovery adb shell flash_image recovery /sdcard/recovery.img
Reboot into recovery to make sure the process was successful.
Sec:
http://wiki.cyanogenmod.com/wiki/RE-recovery-img

3xeno, your method is the same as yusuo's.
he directly use console on android to send command "flash_image recovery /sdcard/recovery.img" after become root ("su")
pro: no need for PC, con: hard typing on the device
you ask adb to execute on the device the command "flash_image recovery /sdcard/recovery.img".
pro: single command with a real keyboard; con: need for PC and cable

fastboot works only with s-off,if you don t have s-off it will not work .-. (or if you don t have the right files)
anyway this metod didn t work for me
fastboot is the best and more simple than this,anyway is there a metod to flash recovery from the phone?

ilgimmy said:
3xeno, your method is the same as yusuo's.
he directly use console on android to send command "flash_image recovery /sdcard/recovery.img" after become root ("su")
pro: no need for PC, con: hard typing on the device
you ask adb to execute on the device the command "flash_image recovery /sdcard/recovery.img".
pro: single command with a real keyboard; con: need for PC and cable
Click to expand...
Click to collapse
I know, but the method on the handset itself didn't work for him. Hence, just suggested the alternative of the same technique as in the OP

My phone has alpharevx s-off. I thought there was no need of pc and everything can be done from phone itself. But still it didn't work for me. Same error.
If there was a need of pc terminal, maybe the 1st post needs to be clear.
Sent from my HTC Wildfire using XDA App

After a bit more reading, it seems "flash_image" must be present in /system/bin for it to work.
More details here:
http://forum.xda-developers.com/showthread.php?t=1146566
Std Disclaimer - I have not tested any of these, so I don't know if they will work or not.

3xeno said:
After a bit more reading, it seems "flash_image" must be present in /system/bin for it to work.
More details here:
http://forum.xda-developers.com/showthread.php?t=1146566
Std Disclaimer - I have not tested any of these, so I don't know if they will work or not.
Click to expand...
Click to collapse
Yes. Now I can confirm that it works when there is "flash_image" (a file with no extension) is present in the path /system/bin/. Also the permissions of flash_image needs to be executable. Just flashed the recovery partition .
Download flash_image from the link given by 3xeno. The OP needs to be updated.
Sent from my HTC Wildfire using XDA App

i use this command since age... it's the only method that works on my buzz

Related

[GUIDE] ADB, Fastboot, and Nandroid for Noobs

Hello All!
After much frustration with setting up ADB i finally got it working. Everyone said its simple and takes minimal knowledge but when things dont work, nothing really worked. Anyways after 2 hours of research trying to get ADB to work i finally got it all working and wanted to share my knowledge to anyone else that needed help.
This Guide is for windows only. If you are using Mac OS X please go here: ADB For Dummies
If you are using Linux please go here: [HOW-TO]Set up Android SDK/ADB/Fastboot on Ubuntu Linux
Like My Guide(s)? Donate
--------------------------------------------------------------------------
Things you need:
Android SDK - Download
Winrar - Download (32bit) Download (64bit)
Windows PC
USB Cable
A Rooted HTC Dream (Google G1)
--------------------------------------------------------------------------
Setting up the Android SDK
Download the file from above
Unzip to your desktop
Take the "android-sdk-windows" folder and move it to the root of your hard drive (C:\)
Right click on My Computer and click properties
Select the Advanced Tab or Advanced System Setting (Vista/Windows 7)
Select Environment Variables...
Press New
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\platform-tools
Now,
1. Run SDK Manager.exe located in the android-sdk-windows folder
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Preparing your phone for ADB
Go to Settings on your phone
Select Applications
Select Development
Make sure 'USB Debugging' is checked
--------------------------------------------------------------------------
Installing Drivers
Plug in your phone through USB and DO NOT MOUNT IT!!!!!
Your computer should see a new device and try to install Android 1.0 driver (If it doesnt, scroll down to the "Im not getting a notification of Android ADB when i plug in my USB" section)
Let it load
Once it cant find them select "Install drivers from my pc"
The drivers you need are in the Android SDK 1.5r2 folder (C:\android-sdk-windows\usb_driver)
Depending on your OS pick x86 or amd64
You ADB Android Device should now be installed! Good Job
For Android SDK 1.5r7+
1. Run SDK Manager.exe
2. If it gives you an error go to settings and click on "Force http//....."
3. Select all options and let it download and install
If you cant get the setup to work, Download the USB-DRIVERS folder - HERE (Windows XP/Vista/Windows 7)
--------------------------------------------------------------------------
Check if your phone is detected by ADB
Open up Command Prompt (Go to run, type in cmd, press enter)
Type in
Code:
cd C:\android-sdk-windows\platform-tools === Press Enter
adb devices === You should see your device listed
adb shell === you should see # in the next line
Now you are all set to run adb commands
Note: for a list of commands type in 'adb' in cmd
CONGRATS YOU NOW HAVE ADB FULLY RUNNING!
--------------------------------------------------------------------------
Droid Explorer by Camalot
Droid Explorer is a Windows software that will download, install, and setup the android SDK for you all in under a minute so you are ready to go. I use this on a daily basis. This amazing piece of software has tons of plugins and a built in file explorer for all your files on your phone! All you gotta do is download, install, and go!
Download Droid Explorer - Here
Install the program, and let it setup the SDK files for you
Connect your phone
Enjoy!
--------------------------------------------------------------------------
"Im not getting a notification of Android ADB when i plug in my USB"
Why: Your computer has detected your phone but as a protable device and as a storage device.
Fix: This took me a lot of research and time to figure out so this is what your are going to do.
First download USBDeview - Here
Unzip it
Run USBDeview.exe as Administrator
You will see all drivers being used on your computer
Highlight and Uninstall all drivers with the description have HTC Android (Should be 3 of them)
Right Click on the driver and press uninstall
Once done, Unplug your phone and plug it back in
You should now get the notification of the ADB device
Follow the steps above to install the drivers
--------------------------------------------------------------------------
When Typing just adb in cmd you will get whats called a "usage doc" which gives you a lits of commands that you can use:
Code:
-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> <local> - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] <file> - push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb root - restarts adb with root permissions
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PDP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be u
pdated.
- If it is "system" or "data", only the corresponding partition
is updated.
--------------------------------------------------------------------------
Commands that you should know
adb push - Insert file to phone such as Stock.apk to /data/app_s
Code:
adb push <pathtofile.apk> <file system location> - Example: adb push c:\app.apk /data/app
adb pull - Remove file from phone such as Stock.apk from /data/app_s
Code:
adb pull <pathtofile.apk> <path where you want to save it>- Example: adb pull /data/app/Stock.apk C:\
adb install - Install app to phone
Code:
adb install <path to file> - Example: adb install c:/apps/apps2sd.apk
adb uninstall - Uninstall app from phone
Code:
adb uninstall <name of application> - Example: adb uninstall linda.apk
For more ADB Commands go - Here
--------------------------------------------------------------------------
Thats it for ADB! Congrats and if you have any questions please ask me or if anything is missing or not correct please tell me. I got all of this from research and personal experience.
[GUIDE] Fastboot for Noobs
Fastboot
Like My Guide(s)? Donate
Things you need:
New SPL - Download
New Radio - Download
Your Current ROM - CyanogenMod 3.6
SD Card Reader
Rooted G1 Phone
Computer
USB Cable
Patience
---------------------------------------------------------------------------------------
Install Radio FIRST
Download the Radio Update
Rename it to update.zip
Remove your SD Card from your phone and place it in your SD Card Reader
Put the update.zip at the root of your SDcard (root = not in any folder)
Insert your sdcard back into the phone
Turn off your phone (Hold power and press Power Off)
Hold the Home button and then press the power button (Keep holding power)
You will now enter recovery
Open up your keyboard and press Alt-S
Let it finish the update
When done reboot by pressing Home and Back
You should be able to access your Home screen (If its stuck on the Google G1 screen dont panic, just remove your battery for now)
---------------------------------------------------------------------------------------
Installing the new SPL
Note: To update you must have a PVT board. To Check go into fastboot (Power and Camera and check)
Take your SD Card out again and plug it into the pc
Remove the update.zip that you put in there
Download your current Rom or any other ROM that you want. I suggest CyanogenMod 3.6
Download the SPL Update
Rename the SPL Update to update.zip
Remove your SD Card from your phone and place it in your SD Card Reader
Put the update.zip at the root of your SDcard (root = not in any folder)
Insert your sdcard back into the phone
Turn off your phone (Hold power and press Power Off) or put your battery back in and turn it on
Hold the Home button and then press the power button (Keep holding power)
You will now enter recovery
Open up your keyboard and press Alt-S
Let it finish the update
Now it will reboot on its own back to recovery
Reboot again by pressing Home + Back
Your phone will be stuck on the T-Mobile G1 Screen (Again DONT FREAK)
Remove the battery from your phone
Remove your SD Card and plug it back into your computer
Take the ROM that you downloaded and rename it update.zip
Remove the update.zip that was on your SD Card and put this new one it
Put the battery back into your phone
Enter recovery (Home + Power)
Press Alt+s to update
Let it finish
Press Home + Back to reboot
Thats it! You now have your new SPL and Radio
---------------------------------------------------------------------------------------
Getting into Fastboot
Turn off your phone
Hold the back button and keep holding it while turning your phone back on
You should see 3 Android guys on skateboards
You should now be in Fastboot mode!
---------------------------------------------------------------------------------------
Setting up fastboot to work with your computer
Plug your phone in to your computer through USB
You should get a popup that your computer found the ADB Device for fastboot
When it asks you for drivers, make sure u select the option to locate the drivers from your computer yourself
Since you already have your Android 1.5r2 SDK installed, the drivers are in the same place where the ADB drivers are
C:\android-sdk-windows-1.5_r2\usb_driver
Make sure you choose the correct folder depending on your OS
Press ok to install the drivers
Fastboot should now be up and running
---------------------------------------------------------------------------------------
Make sure Fastboot is working
Open up Command Prompt
type the following
Code:
cd C:\android-sdk-windows-1.5_r2\tools === Press Enter
fastboot devices === Press enter, your device should be listed
fastboot shell === You should see a # in the next line
type fastboot and press enter for general commands
---------------------------------------------------------------------------------------
When Typing just fastboot in cmd you will get whats called a "usage doc" which gives you a lits of commands that you can use:
Code:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
For more fastboot Commands go - Here
---------------------------------------------------------------------------------------
Congrats! You now have Fastboot and ADB up and running!!!
----------------------------------------------------------------------------
Disclamer: I am not liable to any damage that happens to your phone. This is just a guide which you have chosen to follow, so please do not blame me for any damaged phones or bricks.
Nandroid Backup and Restore
Whats is a Nandroid Backup?
Like My Guide(s)? Donate
Nandroid Backup is a tool allowing all rooted g1 users to create a full system backup and restore which, when flashing and testing different roms can be very useful.
----------------------------------------------------------------------------
What You Will Need
A Rooted G1 phone, I suggest with the latest SPL (Guide above to install latest Radio and SPL)
Cyanogen's Pimped Out Recovery Image 1.4 - Download (IMG)
An SD Card with 100mb of free space
A Computer
SD Card reader or USB Cable
----------------------------------------------------------------------------
Installing the New Recovery Image
Download the recovery image from above, you will want the Download (IMG) download
Place the cm-recovery-1.4.img file in the root of your SD Card (Root = not in any folder)
Go back to your phone (Dont forget to unmount)
Open terminal and type in the following
Code:
su (wait for a screen to popup and press "allow")
flash_image recovery /sdcard/cm-recovery-1.4.img
If you have problems with a "no space on device" error, try using fastboot and erasing first:
Code:
fastboot erase recovery
fastboot flash recovery cm-recovery-1.4.img
----------------------------------------------------------------------------
Creating a Backup using Nandroid 2.1
Boot up your phone in recovery (Turn off, then turn on while holding Home button)
You will now see your new Cyanogen 1.3.1 + JF recovery screen (YAY!!! )
Scroll down to "nandroid v2.1 backup" and press on it to create your Backup
Let it work, it should take a minute or so
Once its done, your backup is complete and is saved on your sdcard in the "nandroid" folder
Recovering to Your Nandroid Backup
Option 1 (Without a Computer)
Note: This recovery will only recover your latest nandroid backup (the one with the newest timestamp)
Make sure u made a backup and its in the nandroid folder on your sdcard
Boot up your phone in recovery (Turn off, then turn on while holding Home button)
Scroll down to "restore latest backup" and press on it
Let it work
Once its done reboot your phone and you backup will now be restored!
Option 2 (With a computer)
Note: With this option, you can use any nandroid backup that you have made, not just the latest one
1) First go in to your tools folder where you put your SDK 1.5r2 (C:\android-sdk-windows-1.5_r2\tools as reference)
2) Take the files adb.exe fastboot.exe and AdbWinApi.dll (found here - http://sharebee.com/16a06ebb) and place them in C:\WINDOWS\system32
3) Download the Nandroid Backup and Restore GUI made by Markazeh - Here
Extract the folder to your desktop or where ever you can easily find it (I put mine in the SDK folder for easy access)
4) You will need 4 files: Boot.img, System.img , Data.img, and Recovery.img
Place those 4 files in the same folder as the Nandroid Recovery GUI folder you just extracted in step 3
5) Boot your phone into fastboot mode (Turn off the G1 and turn on while holding the BACK button. If you have an older SPL then hold the CAMERA button and press POWER)
6) Once in fastboot (you should see a white screen with three androids on skateboards) plug your phone to your computer via USB. You might have to press the BACK key to turn it into FASTBOOT mode, or follow the on screen prompts.
NOTE: If you dont have the drivers installed please look one post above to setup fastboot
7) Open NANDROID_Recovery_GUI.exe, everything on the left hand side should be "found!"
8) Choose an option from the right to Restore All, Restore all except Recovery, or Restore Data Only. Let the program do its thing.
Once its done you can reboot and all your info from your backup should be restored!
----------------------------------------------------------------------------
Congrats! You now Backed up your phone and will/have restored it!
----------------------------------------------------------------------------
Disclamer: I am not liable to any damage that happens to your phone. This is just a guide which you have chosen to follow, so please do not blame me for any damaged phones or bricks.
Credit:
Haykuro
Cyanogen
JacHero
NeoBlade
Markazeh
makethetick
XDA Community for your support and help
If i have forgot anyone, i am sorry, please tell me and i will add you
Excellent Guide bro. Although I have no need for it, still A++. Might want to include how to do a nandroid restore just a suggestion!
[EDIT]: I think this guide is worthy of a sticky! What do you guys think? ^^
You are the man!!!
Short simple and to the point!!!
0nly if all the guides were like this...
Thanks man!
not sure if this is the right spot or not but ever since I flashed from cy36 to 361 I keep losing my adb connection I have to g1s and while I'm working on one the other one isn't even connected to the computer so I just flashed the hero theme on one and plugged it in usb and tried to do the clock switcher didn't work so I go do a cmd and do an adb devices and there's nothing listed then I do an adb shell and it says error device not found but the computer sees it and the adb driver is loaded along with the mass storage driver and haven't had any problems until now.
PlatinumMOTO said:
not sure if this is the right spot or not but ever since I flashed from cy36 to 361 I keep losing my adb connection I have to g1s and while I'm working on one the other one isn't even connected to the computer so I just flashed the hero theme on one and plugged it in usb and tried to do the clock switcher didn't work so I go do a cmd and do an adb devices and there's nothing listed then I do an adb shell and it says error device not found but the computer sees it and the adb driver is loaded along with the mass storage driver and haven't had any problems until now.
Click to expand...
Click to collapse
You might want to try reinstalling the drivers and the USB Storage devices. That fixed it for me
Did you follow the "Preparing your phone for ADB" steps? and do ^ that suggestion first. lol
Mikey1022 said:
Did you follow the "Preparing your phone for ADB" steps? and do ^ that suggestion first. lol
Click to expand...
Click to collapse
yes I did I've had adb since sdk 1.0 and never had a problem like I said I actually have 1.0 and 1.5 on my computer so that when I root or re root other g1s I do adb but I noticed adb only works on it's version if I had a 1.5 g1 then the 1.0 won't work and same with the other way but that's not the problem I think I found it it's the clock switcher with 361 of Cyan because now I deleted it and restarted and it works just fine and I just tried to do the clock switcher and now it doesn't recognize either g1 again.
push apk via abd while in recovery mode?
Is it possible to use ADB to push apk files to the phone when the phone is in recovery mode? I tried and it didn't work (the files I was trying to replace weren't overwritten), and I'm wondering if it's because I did something wrong, or if it just doesn't work. I have adb working fine otherwise, have used it a bunch, including to push files while the phone was booted normally.
Specifically, I want to push the calendar.apk and calendarprovider.apk (I like the 1x4 calendar widget better than the 2x2). I want to do this in recovery mode so that the calendar isn't running when the file gets overwritten. I keep having calendar problems after pushing the 1x4 widget, and I think the problems are due to the calendar being active when the file gets replaced.
ADB Commands...
First I would like to say I think the guide is great. Though I don't have a lot of use for it, but I have some suggestions to make:
1. List some ADB commands and what they do, specifically how to use them, and what you would use them for. This forum has taught me so much about my phone and linux, but sometimes it was a slow learning process. Working the ADB push/pull feature was confusing when I first started using it.
2. Nandroid Back-ups. I still don't think I am using it correctly. I know there is a guide, but it still seems confusing. Maybe dumb it down a little.
3. Maybe more information on fastboot. I'm not sure exactly what it is or does, seems like just another version of recovery terminal, which from everything I have learned so far, if you can't get to your recovery terminal, you probably won't be able to get to your fastboot either.
ccunningham83 said:
Maybe more information on fastboot. I'm not sure exactly what it is or does, seems like just another version of recovery terminal, which from everything I have learned so far, if you can't get to your recovery terminal, you probably won't be able to get to your fastboot either.
Click to expand...
Click to collapse
Actually, you can access fastboot from the bootloader, so it's available even if the recovery console isn't.
heldc said:
Is it possible to use ADB to push apk files to the phone when the phone is in recovery mode? I tried and it didn't work (the files I was trying to replace weren't overwritten), and I'm wondering if it's because I did something wrong, or if it just doesn't work. I have adb working fine otherwise, have used it a bunch, including to push files while the phone was booted normally.
Specifically, I want to push the calendar.apk and calendarprovider.apk (I like the 1x4 calendar widget better than the 2x2). I want to do this in recovery mode so that the calendar isn't running when the file gets overwritten. I keep having calendar problems after pushing the 1x4 widget, and I think the problems are due to the calendar being active when the file gets replaced.
Click to expand...
Click to collapse
In recovery, nothing is mounted. So in order to push and overwrite the calender and calenderproviders, you have to do this in recovery/adb shell
mount /system/app
After that, You should be able to push the files + overwrite them =]. QQ why do you want to do this inrecovery and not when the phone is turned on and fully functional?o_o
but how many times is bootloader available when recovery console isn't? I understand they are different, but from everything I have seen, if you can get one, you can get the other and if you can't get one, you cant get the other either.
ccunningham83 said:
First I would like to say I think the guide is great. Though I don't have a lot of use for it, but I have some suggestions to make:
1. List some ADB commands and what they do, specifically how to use them, and what you would use them for. This forum has taught me so much about my phone and linux, but sometimes it was a slow learning process. Working the ADB push/pull feature was confusing when I first started using it.
2. Nandroid Back-ups. I still don't think I am using it correctly. I know there is a guide, but it still seems confusing. Maybe dumb it down a little.
3. Maybe more information on fastboot. I'm not sure exactly what it is or does, seems like just another version of recovery terminal, which from everything I have learned so far, if you can't get to your recovery terminal, you probably won't be able to get to your fastboot either.
Click to expand...
Click to collapse
If you type "adb" in terminal you get a whole list of the options and what they do Also what part of nandroid backup don't you understand? Its just booting into recovery and alt+b. I assume you mean nandroid restores right? Drop me a PM maybe I can help you
ccunningham83 said:
but how many times is bootloader available when recovery console isn't? I understand they are different, but from everything I have seen, if you can get one, you can get the other and if you can't get one, you cant get the other either.
Click to expand...
Click to collapse
Its because the boot loader is dependent on the SPL and if you flash the "Danger" SPL which is basically the only one that causes problems, then you have a chance of bricking your phone. In that case, brick = no bootloader no recovery
ccunningham83 said:
but how many times is bootloader available when recovery console isn't? I understand they are different, but from everything I have seen, if you can get one, you can get the other and if you can't get one, you cant get the other either.
Click to expand...
Click to collapse
Well, actually, I recently had just this happen. My fiance got a g1, and somehow in flashing it for him, it ended up without a working recovery console. It wouldn't flash the recovery image from within the OS, so I had to use fastboot to flash the recovery image. So, it's quite possible to have a bootloader and no recovery console.
alritewhadeva said:
In recovery, nothing is mounted. So in order to push and overwrite the calender and calenderproviders, you have to do this in recovery/adb shell
mount /system/app
After that, You should be able to push the files + overwrite them =]. QQ why do you want to do this inrecovery and not when the phone is turned on and fully functional?o_o
Click to expand...
Click to collapse
Ah ha, that's likely the problem, thanks!
Like I said, I want to overwrite a system app, the calendar. Every time I've done this with the phone "fully functional", the app ends up constantly force closing. I suspect this might be due to corruption from overwriting the app while it's running. I'm hoping that if I replace the app when the OS isn't on, the replacement app will work properly.
No problem You could also try replacing the calender app in a ROM and resigin it and then flash it. Have you tried rebooting after replacing the Calender app when the phone is I quote from myself " fully functional "?

how to flash recovery?

im trying to flash godspeed recovery but im a newb so of course i dont know how. it says to flash from recovery and type whatever but it doesnt do anything. someone suggested using rom manager to flash it but that didnt work. how can i flash a new recovery? i have asked twice in the godspeed recovery thread but noone answered so i figured i'd try here. any help would be greatly appreciated. thanks!
Someone help, ima newb!!! Lol
Sent from my HERO200 using XDA App
Have you read through Darch's post on how to flash this recovery? Just click on the link in my sig for this particular thread. This is not directly flashable from the sd card. You need to flash it via adb
edit* You have read the thread, do you know how to flash via adb?
Based on your signature, I'm going to assume you are already rooted.
My first question is do you have the Android SDK installed on your computer? My Next question is have you already placed the recovery image on your SD Card (if you are using apps2sd you will want to place it on the FAT partition, but do not place it in any folders)
If you can answer yes two both question above, then go ahead conncect your phone to your computer with the cable and run the sdk in a command window or terminal window (depends on if you are using Windows or Linux) and type the following:
adb shell
flash_image recovery /sdcard/nameofrecovery.img (changing the "nameofrecovery.img" to the name of the image file on your sdcard)
If you run into any problems or if you don't know how to install the sdk post back and I will give you an alternative method to try.
Yes to everything. I tried typing that from recovery and while in the phone with usb debugging on and charge only. It just kept giving me errors.
Sent from my HERO200 using XDA App
cp0020 said:
Yes to everything. I tried typing that from recovery and while in the phone with usb debugging on and charge only. It just kept giving me errors.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Change from charge only to sync and it should work. Make sure ur in the sdk/tools folder and type adb remount before u type in the adb shell command
If you are still having trouble, you may want to just grab from the market a neat little program called Gscript (paid version) or Gscript Lite (adware) and create a script to flash the recovery image.
Once you install it on your phone the steps are:
Start GScript
Click on the phone's Menu Key and select Add Script
Give your script an easily identifiable name
Make sure there is a check mark in the Needs SU? box
then you can type in the command to flash recovery which would be:
flash_image recovery /sdcard/"nameofimagefile" (changing the name to whatever the name of the recovery image you stored on you sd card is)
then click on save.
The script should now appear in the list of availble scripts - just click it to run it. If SuperUser Permissions pops up requesting permission click on allow and you should see message at the bottom that the window will close in 19 seconds.
To verify if this worked for you go ahead and manually reboot into recovery mode - Power off the phone, then press and hold the home key while pressing and releasing the power button.
Let me know how you make out with this.

[Q] Need help installing a recovery image

I have a Sprint HTC Hero which until yesterday had never been rooted. Software version was 2.31.651.7. I'm trying to install CM6 using these instructions.
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Sprint_Hero_with_Android_2.1
I have rolled it back to 2.27.651.5, as suggested in the above article and I used the universal root method, which seems to have worked. Then when I started the Flashing Radio step I realized that they left out how to install a custom recovery image. I searched and found these instructions:
http://forum.xda-developers.com/showpost.php?p=4898505
After figuring out what adb and fastboot are, I was able to run 'adb devices' which shows:
List of devices attached
HT99RHF03843 device
I then ran 'adb shell reboot bootloader' which gave me the screen with the three androids riding skateboards. Info from that screen:
HERC XC SHIP S-ON
HBOOT-1.47.0000 (HERO20000)
MICORP-0110
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27
Mar 1 2010,16:02:39
When I try to run 'fastboot boot recovery-RA-heroc-v1.6.2.img' I get:
downloading 'boot.img'... FAILED (remote: not allow)
This is were I'm stuck. 'fastboot devices' shows:
HT99RHF03843 fastboot
I've tried searching and most of what I found is over a year old and says something about a perfect SPL, but I gotta believe there is some way around this. I do believe the root worked because I can do an 'adb shell' then 'su' and I get the # prompt. If I can't get a custom image on I'm just going to buy a new phone so I'm willing to risk bricking the phone to get this to work. If anyone knows a way around this I would greatly appreciate some assistance. Thanks.
-Iz-
1. I think you have the latest radio - might not need to flash a new one.
2. About flashing recovery, it's pretty easy -
a. Download the recovery image you want and put it on the SD card (not in any folder)
b. Goto ADB shell and run following commands:
- "flash_image recovery </sdcard/image name>" without quotes and "<>" - replacing image name with the actual file name with extension that you saved to the SD card
- reboot recovery
I am assuming once rooted, you can get to adb shell from your computer.
Let me know if you have further questions.
Thanks for the suggestion here is where I'm at now.
adb shell puts me at the $ prompt, when I type 'flash_image recovery recovery-RA-heroc-v1.6.2.img' from there I get 'flash_image: permission denied'. I also get that if I type gibberish for example if I type 'djherjn' i get 'djherjn: permission denied'. If I use 'su' to get to a # prompt, then run the command I get 'flash_image: not found', If I type gibberish at the # prompt I get 'djherjn: not found'. So it looks like it does not recognize the command flash_image. I checked path using 'echo $PATH' on both prompts it returns '/sbin:/system/sbin:/system/bin:/system/xbin'. Odd thing is there is no /system/sbin directory and flash_image is not located in any other directory. I'm starting to think the phone isn't really rooted. But when I run the universal root again it says phone is already rooted.
You are missing some words on the flashing I think...try this instead.
Connect your USB from the phone to PC choose Charge only.
Now open up Command Prompt(CMD) and type adb shell. Then just to be safe type SU...if SuperUser asks for permission on your phone, give it permission. Should give a # sign instead of $.
Then type ---- flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
You forgot the /sdcard/ from what I read from your post.
With the device set to charge only, adb does not see it. I've been having to set it to HTC Sync, just tried again to make sure. I'm still getting 'flash_image: not found' when I type the command 'flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img' from the # prompt. I also tried 'cd sdcard' and then 'flash_image recovery recovery-RA-heroc-v1.6.2.img' still same error. 'ls sdcard' does show the image in that directory and I'm using copy and paste to avoid typos. I'm still thinking it is complaining that there is no flash_image command. I'm going to re-flash it with the HTC software and start over just in case I screwed something up.
I had the same problem.
Before you go ahead with flashing HTC software, try the ROM manager app from the market. You could flash the ClockWorkMod recovery from ROM manager.
If that does not work, don't waste any more time - go the RUU route (preferbaly using the 2.27.651.5 release) and root using: http://forum.xda-developers.com/showthread.php?t=694572.
I just went through a bunch of issues with recovery/backup/restore and such, so consider this fresh advice ;-).
izard said:
With the device set to charge only, adb does not see it. I've been having to set it to HTC Sync, just tried again to make sure. I'm still getting 'flash_image: not found' when I type the command 'flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img' from the # prompt. I also tried 'cd sdcard' and then 'flash_image recovery recovery-RA-heroc-v1.6.2.img' still same error. 'ls sdcard' does show the image in that directory and I'm using copy and paste to avoid typos. I'm still thinking it is complaining that there is no flash_image command. I'm going to re-flash it with the HTC software and start over just in case I screwed something up.
Click to expand...
Click to collapse
EDIT: Andy beat me to it!
If you want Amon-Ra you have to choose Flash Alternate Recovery.
Finally got it! I used the ROM manger app. I swear last night when I was considering it, I only saw the paid version. That was so much easier then what I was doing. Thanks everyone for your help. It is highly appreciated.
-Iz-

[Q] Nexus one bricked :( and lost recovery mode

can you help me fix this problem
after wipe all data, cache and anotherthing wipe (it's name very hard to remember ).
I cant use recovery mode, my phone can open fastboot and bootloader, but can't open recovery mode (it's only show a android logo when i press "recovery")
please help me (
I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.
justflikwalk said:
I could be wrong, but you should be able to use adb to push a new recovery on to your phone.
Try plugging your phone thru USB cord to your computer to see if you can run any adb commands. If you can I think you should be able to push a new recovery to your phone.
Click to expand...
Click to collapse
can you show me more, i dont know adb commands, and push new recovery is "recovery clockwork" and "recovery RA". I tried apply them, but it's not work,may be i wrong in some thing, it's the first time i use android phone . throught usb, i have "fastboot usb"
please help me
http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide
but my phone cant connect with PC, atlthough i installed google usb driver.
i might be wrong but cant you just flash a original ruu, than root and reinstall recovery
#1)Go and download yourself a recovery.img file that is compatible with your device and put the image on the root of your SD card (that means on the main directory and not in a folder)
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
#3)Open up your terminal and type in
Code:
su
to gain root access. If you are root the next line should show the
Code:
# symbol
#4)At the next line type in
Code:
flash_image recovery /sdcard/name-of-recovery.img
you will need to replace the code that says name-of-recovery.img with the exact name of the file on your SD card.
#5)Hit enter, wait a few seconds and viola ! you have a recovery again.
Good luck man.
hxq88 said:
but my phone cant connect with PC, atlthough i installed google usb driver.
Click to expand...
Click to collapse
Try the driver from this thread.
It helped me set up my ADB for the N1
http://forum.xda-developers.com/showthread.php?t=613217
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone
hxq88 said:
#2)Make sure you have a terminal emulator application installed from the market on your phone. If you don't...install one now.
you mean install terminal from android market? my phone stop working in android logo screen, i cant do anything in android OS, include enable debugging?
I need restore my recovery mode, and my prolem is Pc cant see phone
Click to expand...
Click to collapse
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?
baseballfanz said:
Did you have ADB working before? Try using the driver from the link I posted.
Have you tried the passimg method?
Click to expand...
Click to collapse
i typed ADB devices on command prompt, it'show
View attachment 763802
and it's my driver after update from your link
View attachment 763803
what is passimg method, is the way rename room.zip => PASSIMG.zip
You did have debugging turn on correct?
Not sure what else to suggest except the passimg method, worth a shot.
Sent from my Transformer TF101 using Tapatalk
And... if you try to install a stock rom? When starts the HBOOT automatically detect the rom and ask to install. One time you've installed the rom, root & install recovery
I think that work because, It happens to me 1 week ago.

[Q] Problem installing Null?

Im following the guide on the unlocker.com. I can root the watch, flash the custom recovery with odin and copy the file over null.zip file.
The trouble i encounter is when trying to enter twrp by selecting recovery.
The android sign comes up with installing update? and then it boots back into the operating system and i have to repair it with my note 3 again? am i doing something wrong or is it just sods law?
Thanks for the help in advance
I had the same problem with mine. You have to enter the following commands after rooting to make the new recovery stick (note, don't put the $ and # symbols in the command) -
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
Full Throttle1 said:
I had the same problem with mine. You have to enter the following commands after rooting to make the new recovery stick (note, don't put the $ and # symbols in the command) -
$ adb shell
$ su
# mount -o rw,remount /dev/block/mmcblk0p20 /system
# rm /system/recovery-from-boot.p
Click to expand...
Click to collapse
Hi is this with the windows command? the rooting method im following is using an impactor.exe to supersu onto the system and then installing supersu on the watch with wondershare mobilego? is this the same as you?
dav08094194 said:
Hi is this with the windows command? the rooting method im following is using an impactor.exe to supersu onto the system and then installing supersu on the watch with wondershare mobilego? is this the same as you?
Click to expand...
Click to collapse
Correct. You do it through the Windows command (after rooting), the same way you flash the new recovery (TWRP) through ADB. So before flashing, type those commands and it'll allow the new recovery to stick without reverting back to the factory Samsung software every time you enter the recovery mode.
Full Throttle1 said:
Correct. You do it through the Windows command (after rooting), the same way you flash the new recovery (TWRP) through ADB. So before flashing, type those commands and it'll allow the new recovery to stick without reverting back to the factory Samsung software every time you enter the recovery mode.
Click to expand...
Click to collapse
Hi jumping in here as appears I am having the same issue. Question the recovery is added through Odin and then the ROM is added through Wondershare directly to the SD card on Gear. Where and how are the commands you typed to be added? Thinking original poster and I are in the same boat. I go to flash recovery and get complete reboot.
ptfd139 said:
Hi jumping in here as appears I am having the same issue. Question the recovery is added through Odin and then the ROM is added through Wondershare directly to the SD card on Gear. Where and how are the commands you typed to be added? Thinking original poster and I are in the same boat. I go to flash recovery and get complete reboot.
Click to expand...
Click to collapse
The correct way of installing null_ would be:
1. Root your Gear
2. Enable ADB in your Gear (Search how to enable)
3. Conenct to PC and install Gear adb drivers
4. Download ADB to your PC, unpack, in explorer go to the adb folder, Hold shift and right click the mouse, choose "Start command prompt here"
5. Run the commands listed in this thread.
6. install TWRP using odin.
7. Move your null_ zip file to Gear storage using wondershare
8. Reboot Gear into Recovery and install your null_ zip.
That should be about it... There is great guides on this forum that explains every step more detailed.
st-tps said:
The correct way of installing null_ would be:
4. Download ADB to your PC, unpack, in explorer go to the adb folder, Hold shift and right click the mouse, choose "Start command prompt here"
5. Run the commands listed in this thread.
That should be about it... There is great guides on this forum that explains every step more detailed.
Click to expand...
Click to collapse
Thats step apepars I am having issue with... is ther detailed explanation how to do? I have ADB on puter but lost once I get to "prompt" part as I've never used this method in any of my previous roots/roms.
ptfd139 said:
Thats step apepars I am having issue with... is ther detailed explanation how to do? I have ADB on puter but lost once I get to "prompt" part as I've never used this method in any of my previous roots/roms.
Click to expand...
Click to collapse
Try the thing I explained:
Hold shift on keyboard and the rightclick anywhere in the folder window. You will get a new alternativ saying something like "Start command prompt here", choose that and a command window shows.
Now copy and paste row one and press enter, row two and so on... You should notice if things go good or bad.

Categories

Resources