I just recently got a HTC dream from Rogers with 1.5. The build number is 1.89.631.1 146733 CL#94714 release-keys. I have tried different methods and they have not worked.
Using this method...
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Rogers_Dream_911_Patched
I could not get past 8. Type in the following commands:
adb push recovery.img /data/local.
I have the new android-sdk program so correct me if i am wrong but I believe the adb is in the platform-tools dir and I should be using that as my path and putting the recovery.img into that dir as well.
This is so frustrating, someone please help me. Thank you.
I haven't done it in a while so I will see what I can remember.
What error or message do you get when you do
adb push recovery.img /data/local
I get an error saying "cannot stat 'recovery.img' : No such file or directory
Maybe I am putting recovery.img in the wrong directory? Its currently in
C:\android-sdk-windows\platform-tools
just fully qualify the location of your recovery (and make sure it is actually called recovery.img) to ensure that it can find it
adb push C:\android-sdk-windows\platform-tools\recovery.img /data/local
Related
Hey, question for anyone who has what I feel is a mistake and used the RUU_Hero_C_Sprint_2.20.651.1_signed_test. Since I have done this I can find no way to get back to the recovery screen to load any custom roms. Several have said that since this is a test it is still rooted but there is no indication that this is true. Any help would be appreciated. Best site should be call Romipedia.
install a recovery image on it. It IS rooted. All Rooted means is you can get access to the linux commandprompt as the all powerful root user. Without a recovery image, you can't load other ROMS.http://forum.xda-developers.com/showthread.php?t=561124
I have loaded a recovery image on the sd card... When I go to power up holding the down volume and power key I get a picture of the device with a triangle and ! on the screen. I have tried everything but I can't even get into recovery mode.
You are missing a few steps. You need to flash the recovery image on your SD. However, the required command "flash_image" is missing in the 2.1 RUU leak. So....
You need to get hold of the "flash_image" executable, move it into the phone's /system/bin folder, and then flash the recovery image using the adb shell from your computer.
This worked for me:
http://forum.androidcentral.com/htc...pair-your-bootloader-after-using-2-1-ruu.html
I get the following when I try to push the flash_image to the phone... cannot stat flash_image : no file or directory found.. I need just a little more help... any would be appreciated.
markus123 said:
I get the following when I try to push the flash_image to the phone... cannot stat flash_image : no file or directory found.. I need just a little more help... any would be appreciated.
Click to expand...
Click to collapse
Make sure that the "flash_image" executable file is in the same directory of the "adb" executable - usually "c:\Android-sdk/tools" if you are just following the posted instructions.
You can use the Windows explorer's search function to see where you downloaded "flash_image".
2.1 ruu.exe left you without flash_image on your phone. You need to copy flash_image to /system/bin/flash_image.
I am attaching flash_image.zip (not really a zip). Copy the file I attach to your sdk root directory and use the commands below to push and rename it:
Code:
adb remount
adb push flash_image.zip /system/bin/flash_image
This will allow you to follow the standard guide on flashing a recovery image.
Hi,
By my mistake i delete recovery file in system directory, and now my phone doesnt start up only wait at galaxy S logo.
What can i do?
what rom was you running.
what if the full directory of the file you deleted.
As you can push it back with adb if someone else has it.
I had froyo2.2, and directory was: system/bin/ recovery
i want to change it with diferent recovery file but i see now that file was only deleted and not replaced xD
so i am without recovery option and phone doesnt start.
I can go to download mode.
denesch said:
I had froyo2.2, and directory was: system/bin/ recovery
i want to change it with diferent recovery file but i see now that file was only deleted and not replaced xD
so i am without recovery option and phone doesnt start.
I can go to download mode.
Click to expand...
Click to collapse
if you still have the recovery file you wanted to put there.
plug your phone into the computer and try
adb devices if something pops up your in luck
move the recovery file to your tools folder (in the sdk)
then use
adb push recovery /system/bin/
i have file on phone under Download folder. how can i get it and how can i copy back file.
my phone is detected by computer and i can acess it with odin.
denesch said:
i have file on phone under Download folder. how can i get it and how can i copy back file.
my phone is detected by computer and i can acess it with odin.
Click to expand...
Click to collapse
To copy a file or directory (recursively) from the emulator or device, use:
adb pull <remote> <local>
To copy a file or directory (recursively) to the emulator or device, use:
adb push <local> <remote>
example:
adb push foo.txt /sdcard/foo.txt
ttf said:
To copy a file or directory (recursively) from the emulator or device, use:
adb pull <remote> <local>
To copy a file or directory (recursively) to the emulator or device, use:
adb push <local> <remote>
example:
adb push foo.txt /sdcard/foo.txt
Click to expand...
Click to collapse
Sry but i am noob here
when i try to connect with adb says that no device found
but odin works fine.
ok we SOLVED with new firmware.
CLOSE thread.
And big thx to iammodo
I've flashed multiple ROMs before but this is the first time I'm experiencing this issue. I download the .zip I want to my PC, connect my HTC One to my computer and copy the file to the root of the SD. I boot into recovery but the .zip doesn't show up.
Has anyone has this problem before?
Thanks for the help in advance.
Maybe is in another folder.
With adb, try to use the command:
Code:
adb push name_rom.zip /data/media/
and check if you can see the zip, if not, try
Code:
adb push name_rom.zip /sdcard/
p.s. The rom will be in the same folder of adb
Hey guys, any help you could give me with my problem would be great. Basically, i tried to flash cyanogenmod 11 unofficial on my d959 g flex and it didn't work. unfortunately, i had created backups with twrp recovery, but had cwm on at the time and no cwm backup. I try to send the stock 1.5gb zip over with adb push or adb sideload, but neither is ever successful(stops after 1gb). basically need a way to flash a twrp.zip in cwm to restore my phone recovery to twrp, then I can restore my phone using my twrp backup. Any ideas? I've got the twrp.img file that the Freedom flex app downloaded before, and found a recoveryinstaller.zip that i have put it in and have thought about flashing that to my phone, but don't want to brick it further.
I lost where you replied to what I said about the otg cable but you're halfway right.
Try this.
Download Flash_img. and extract it from the zip file to a location on your computer. We extracted it to the main C drive (not in any folder) and will use that in the next steps.
Copy the recovery image for your phone to a convenient location on your computer, preferably with a short path. We will be placing it on the C Drive directly (not in any folder) and using that in the next steps.
Note: The recovery image should have .img extension. If it is in a zip file, extract the .img file from it.
Enable USB debugging mode on your device from Menu > Settings > Applications > Development.
Connect your device to your computer via USB.
Open a Command Prompt window on your computer and enter the following commands:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
This will first transfer flash_image and recovery.img to your phone. Then it will copy flash_image to the /system/bin folder of your Android device and make it executable. Finally, it will flash the custom recovery image to your device using flash_image.
Note that we used c:\flash_image and c:\recovery.img in the first two lines as we had these files extracted at the root of our C drive. If you extracted the files elsewhere, use the appropriate paths and if your recovery image has a different name, use the appropriate name.
Reboot your device once the process is finished and you’re done. You may exit adb and the Command Prompt window on your computer by entering ‘exit’ twice.
Here is the "bumped" twrp.img
https://docs.google.com/file/d/0B2OabWtEBQcpVjZGb2ppT083OGs/edit?usp=docslist_api
Here is the flash.img that you need to extract on your PC
https://docs.google.com/file/d/0B2OabWtEBQcpcmowamtnUVY1YU0/edit?usp=docslist_api
---------- Post added at 12:13 PM ---------- Previous post was at 12:10 PM ----------
If you can get into download mode try opening cmd and
Fastboot flash recovery " then drag and drop the twrp.img that I just posted the link for here with out the quotations". It doesn't matter what you name it in this case. This is the easiest way to me.
I have an xt1060 that i'm trying to flash twrp onto.. I have adb and fastboot (mfastboot as well). When trying to flash twrp from philz touch i get error:
(bootloader) Variable not supported!
target max-download-size: 768MB
error: cannot load 'recovery.img': No error
Anyone know what the heck i've done wrong?
What command are you using to flash? Do you have the filename right? Are you in the proper directory or referencing the proper location of the recovery image?
Sent from my Moto X
imnuts said:
What command are you using to flash? Do you have the filename right? Are you in the proper directory or referencing the proper location of the recovery image?
Sent from my Moto X
Click to expand...
Click to collapse
1 & 2) (from bootloader scren) mfastboot flash recovery recovery.img (i've renamed my file believing that could have been the problem)
Also i've tried twrp 2.7, 2.8, and philz touch just to see if it was the file or a mfastboot problem. They all result in the same message.
3) My files are placed in my adb folder.
Is your bootloader unlocked?
Sent from my Moto X
Yes sir it is.
http://android.stackexchange.com/qu...error-cannot-load-recovery-clockwork-no-error
that is, make sure your command prompt path is the fastboot folder, or use the full path name for the recovery file.
easy shortcut fix: create a shortcut to cmd.exe in windows, then right click it and choose properties, then set start from box to be your fastboot/adb folder
note that this is basically what imnuts asked you initially but you must have misunderstood:
Are you in the proper directory or referencing the proper location of the
recovery image?
Click to expand...
Click to collapse
Sorry for misunderstanding. I'm opening cmd from the adb and fastboot folder. This is also where my recovery img is. Edited environmental variable path to minimal adb and fastboot folder as well.
Still, folder referencing issues seem to be the most likely source of the problem. Here's another example of the exact same issue. Try what the guy did, which was to create a new folder, move everything to that folder, then run command prompt from that folder, and try mfastboot flash again.
http://forum.xda-developers.com/moto-x/moto-x-qa/fastboot-flash-error-t2808229/page2
You can also try running command as administrator, see if that helps. But again, make sure of the path.
I tried twice now with the new folder.. once, opening cmd from within the folder and once cd to file path. I got the same result.
Stupid me
I apologize to all of you who have been helping me figure out my flashing problems. I just managed to flash TWRP. My issue was when i renamed the twrp file to "recovery.img" the computer also attributed the file extension so what i was actually trying to flash appeared to the computer as (recovery.img.img)! Sorry again fellas. I found out by looking at the properties of the recovery.img and I saw my error.