Related
Hey, I am trying to successfully get a new ROM, and in all the forums and such I have read tell me that with the Desire Z/G2 I need to flash the newest ClockWorkMod recovery. So i have downloaded a couple different recovery .img files.
Now when i use Emulator, i put in;
su
flash_image recovery /sdcard/recoveryname.img
and it says
flash_image: not found
I dont understand why ROM Manager doesnt give the newest recovery file as an option.
Can anyone help me in this situation?
Thanks
mobilemidget said:
Hey, I am trying to successfully get a new ROM, and in all the forums and such I have read tell me that with the Desire Z/G2 I need to flash the newest ClockWorkMod recovery. So i have downloaded a couple different recovery .img files.
Now when i use Emulator, i put in;
su
flash_image recovery /sdcard/recoveryname.img
and it says
flash_image: not found
I dont understand why ROM Manager doesnt give the newest recovery file as an option.
Can anyone help me in this situation?
Thanks
Click to expand...
Click to collapse
Did u delete the name on the recoveryname.img upon flashing??
Sent from my HTC Vision using XDA App
Download Root Explorer and navigate to /system/bin
Make sure /system is mounted in r/w then take this attached file, unzip it, and place it inside of /system/bin
Go back into terminal and try that command again.
ok so I installed root manager, and put the flash_image.zip in the system/bit, and tried it again with the terminal emulator, but i still have no results, it says after the pause when you plress enter after the flash_image prompt, your supposed to reboot the phone and it should start with the new recovery, but when i open ROM manager it staill shows V 2.5.... If i did somthing wrong i cant figure it out., Please help.
Thanks
http://www.youtube.com/watch?v=w4QViSam2og&feature=youtube_gdata_player
Follow these instructions. You can't go wrong. Make sure you back out of the app and go back in. It sets the cursor to the correct posistion. All you have to do is put the .img in the root of your sd. Hope this helps, it did for me.
Sent from my HTC Vision using XDA App
wait, so why aren't you just flashing the recovery through ROM manager? Are you trying to install CWR 3.0+?
yes I am trying to flash cwm 3.0, and it is not an option with ROM manager. I will try the Youtube instructions. Thanks
Ok so I tried the instructions with the Youtube video, and when i do the cmd promt in Terminal i get this;
Cant open device: "/dev/block/mmcblk0"
error in reading mbr!
failed with error: -1
I have the recovery.img file (not zip) on the sd card, I used root mamnager to put it in the bin file within system. but the instructions on the video say to use astro and it doesnt give an option to go as deep as root manager.
Thanks
Yes unzip it but make sure its in the root of your sd. That means not folders at all. That's the command that he is making in the video. I don't think you can flash cwm 3.0 in rom manager, only revert back to earlier recoveries, for froyo roms.
Sent from my HTC Vision using XDA App
Make sure the file is named what your commanding it to be. Make sure its recovery.img no caps.
Sent from my HTC Vision using XDA App
OK so I am trying this too. I am putting the recovery image directly to the root of my sd and I can see that it's there. But in TE, I put in the commands and it tells me
flash_image: not found
It's there!!!! I can see it when I have my phone connected. What am I doing wrong?
Edit: I am running stock rooted. Does this have something to do with it?
Rooted running a stock rom? Honestly I can't tell you all I know is I'm running custom rom. If I had to guess I would say it doesn't. All I can say is I had issues until I watched the video, sorry I can't help more. Only thing I would say to do is wipe everything you did and try redoing it.
Sent from my HTC Vision using XDA App
I can say you should only have one .img in your sd to not confuse it. I'm pretty sure you can use command prompt on your pc if you have access to one.
Sent from my HTC Vision using XDA App
Ok, I think I am getting somewhere, I was searching my sdcard on my computer, and I realised that the root of my sdcard is not called "sdcard" so in the command i was doing it wrong, It is called "HTC DESIRE" so i did it in Emulator and it worked i rebooted my phone in recovery and I am now rocking the new ClockworkMod Recovery 3.0.0.5...
Thanks all for the help, Hope what i discovered helps someone else.
Wait, Wait, Wait... I just screwed it up again... I went into ROM Manager after I successfully flashed 3.0.0.5. and it was not showing that in ROM Manager, so I tapped on flash latest recovery, and damnit... it replaced all my hard work with the 2.5 recovery... I have tried to repeat the flash process a few times with 3.0, and i have not been successful... Help... I dont know what to do now!!!
Instead of flashing the recovery in rom manager, after you've inputted the
su
# flash_image recovery sdcard/recovery.img
you can just type in after it
# reboot recovery
and it will reboot you into CWM 3.0. Be sure to perform a nandroid backup under 2.2 first and when you want to go back to a froyo rom, you'll have to flash the 2.5 recovery image again.
Yes, you will not see it in rom manager. Just reboot into the recovery and if you see orange and cwm 3.0 your good. Just repeat the steps.
Sent from my HTC Vision using XDA App
mobilemidget said:
Hey, I am trying to successfully get a new ROM, and in all the forums and such I have read tell me that with the Desire Z/G2 I need to flash the newest ClockWorkMod recovery. So i have downloaded a couple different recovery .img files.
Now when i use Emulator, i put in;
su
flash_image recovery /sdcard/recoveryname.img
and it says
flash_image: not found
I dont understand why ROM Manager doesnt give the newest recovery file as an option.
Can anyone help me in this situation?
Thanks
Click to expand...
Click to collapse
"flash_image: not found" means that you do not have the 'flash_image' binary installed. Follow the guide here to get 'flash_image' installed on your device (the 'flash_image' binary is attached).
As for why ROM Manager not giving the newest recovery as an option, ROM Manger isn't fully compatible with the latest recovery as it just came out. The latest recovery (I'm assuming you're referring to v3.x) is only for Gingerbread based ROM's, if you're trying to install a Froyo based ROM then you should be using recovery version 2.x.
OriginalGabriel said:
"flash_image: not found" means that you do not have the 'flash_image' binary installed. Follow the guide here to get 'flash_image' installed on your device (the 'flash_image' binary is attached).
Click to expand...
Click to collapse
I will try this tonight, thank you. I haven't run into this in any of the tutorials I've read though. I appreciate it.
Hey everyone I found a site that shows me how to flash CWM 3.0 through ROM Manager,
http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-3-using-rom-manager/
However, it is not working for me, if anyone has been successful in doing it this way please let me know cause evrything i try this i still am left with CWM 2.5. I really want to try the new Cyanagen nightly ROM, but i need to have 3.0... I had it once when i was doing it through terminal, however stupid me went back into rom manager and ruined what i did, and could not redo it... i am getting frustrated.
Please Help me.
Thanks
Not applicable
Delete this thread
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Let me answer myself.
I don't think the latest rom 2.3.4 is compatible with the clockwork you supplied. So I have to flash my phone back to GRH78. I downloaded the stock ROM from the internet. and then push all the images file into /sdcard/clockworkmod/backup/2010.xxx.
Next, I restore the image in clockwork menu.
after restore, reboot the phone, now I am back in business.
When the phone is boot, i lost the root again, so i went to modaco.com and get Paul's package. run it, restart, I got the root.
Finally, go to market place and get ROM Manager, install the clockwordmod. and I have a 'proper' phone.
although I don't have the least rom, at least i got a working phone that is rooted.
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
I have the same problem. How did you handle it?
Wow, why risk messing up your phone with flashing a boot.img when you can just rename /etc/install-recovery.sh to something like /etc/install-recovery.bak?
Here's one way to rename (courtesy of Matridom). Another is to use Root Explorer.
Matridom said:
The new update applies the install-recovery.sh script into our phones (not there previously.
Boot into the bootloader
flash CWM
select recovery from the bootloader (DO NOT reboot the phone)
apply the su binary
boot into the OS and test root
make sure busybox is properly installed
run ADB shell
then:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
Boot back into the bootloader and re-flash CWM, should stay permanent now.l had applied the SU binary at the same time as the OTA update, then renamed the installer script and flashed back CWM.
Click to expand...
Click to collapse
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
same here someone please help ?
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
Hi Bante, I am sorry for the inconvenience. I have revert back the CWM Recovery to 3.0.2.4. You can download it at the link above, and try it again
I hope that the problem you mention wont persist anymore
zero383 said:
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am sorry but not all people can successfully use Command Prompt to do so.
I cant use command prompt, as it says "Image cant be loaded".
So I had to use this method.
I search around the forum and seen this as a quite common problem,
so I decided to share it
Hope you understand.
Anyway, thanks for your method too Cheers
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
16vMK1 said:
same here someone please help ?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
Wow people like to make things complicated. Why install an entire rom to get ride of a script?
if you can flash cwm, you should have some basic understanding of fastboot, adb and the search options in the forums. the answers are all there already.
Sent from my Nexus S
No disrespect, I agree flashing recoverys should only be done after you understand how to use the tools to do it. there is no reason someone who is going to mod systems on their nexus shouldn't be able to use fastboot and adb properly. all the right drivers are in the sdk.
Sent from my Nexus S 4G using Tapatalk
nxt said:
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Click to expand...
Click to collapse
This is what I did.
I rooted my NS, which had 2.3.3
Used phone with stock 2.3.3 until I figured out which ROM I want to flash.
Before I flashed any ROM, did a Nandroid Backup through CWM.
Used the ROM for a few days, but when I saw that official update is ready for download for i9020A, did do a restore from the Nandroid backup I created.
Updated from 2.3.3 to 2.3.4, phone works fantastic, video chat also works great.
After update when I tried using any of the apps required SU permission, they didn't work. I tried installing a couple of .apk files, couldn't either install it or after installation it didn't work.
Thought let me try wiping my phone clean and start all over again, may be I will use a custom ROM again, downloaded ROM, went to ROM Manager to reboot into recovery, nothing happens.
Tried booting into Recovery option manually by pressing Volume Up and Power button, nothing happens but the Bot with an Arrow appears on screen.
So, I thought I will follow this procedure to reflash CWM to my phone and get it going. I was able to use the command FastBoot once, and suceeded pushing .img file to my phone but now whenever I try using the commands from my computer, this error message appears : "This application has failed to start becasue AdbWinApi.dll was not found. Re-installing the application may fix this problem."
Why this error message if I have the sdk on my computer already through which I was once able to push .img file without any troubles?
Can anyone tell me what would be a possible solution?
Also, how can I fix this problem and get ClockWorkMod Recovery installed on my NS again?
How can I get stock recovery image on my phone if I want start all over again from scratch?
Thx a million.
Edit ::: I found the answer as to how to how to install CWM again. Thx anyways.
Other question still remains a puzzle... why am I not able to install certain programs or if did manage to install, can't run them?
I ran your method and I think I'm stuck at some step...
My phone now default boots into CWM 3.0.2.4
Recovery boots to a newer recovery I flashed.
How do I get my phone to default boot into the OS again?
Edit: nevermind, just downloaded the full 2.3.4 rom, extracted and flashed the original boot.img.
dreamsforgotten said:
All the right drivers are in the sdk.
Click to expand...
Click to collapse
After installing the sdk and a platform, I have adb, but where is fastboot?
I was getting the same error as "Image cant be loaded". after hours of struggling I found that It's only because I was not in the same directory as the img file. silly eh?
hi,did you repaiar your phone,i have try everything but it just keep going in clockwork mode,if i than pres reboot now in clockworkmode it stays on google padlock
i realy need phone if you can help or someone else,than ....
just tried this method of window7 (thanks for the work) with cwm 3.0.2.4, but got the same result like the others in this thread: cant boot the android 2.3.4, the system is always booting into the cwm, no way out.
I don't think this tool works as it should.
:-(
EDIT:
I didn't realize that window7's tool would install the cwm into the boot-partition instead of the recovery-partition.
To get my boot partition back I downloaded the 2.3.4 firmware image from http://forum.xda-developers.com/showthread.php?t=1056062 and extracted the boot.img from the zip.
with "fastboot flash boot boot.img" I restored my orginal boot partition an can boot into android again.
(fastboot is part of the android sdk)
Hello there. I bought a S5368 (Chinese) device, and want to root it, but it doesnt have recovery (probably they disabled it), and cant root with SuperOneClick or Gingerbreak. It is running 2.3.6. So I tried to open an update file, and it seems it is in FAT16. Is this true? I opened it with UltraISO and attached the su and busybox to the system/bin, make a tar from that file, and flash it using ODIN, but stucks at aprox. 10% of the flash. Any ideas I can use to flash that package or root it? Thanks!
EDIT 1: I managed to get it working - soft of. Mounted using linux and works, BUT, I cant get superuser to work. Any app that needs root, it gets automatically denied. If I enter using the shell, it says: granted, but it exits right away
aby ideas?
Hello,
I plan to install a custom rom, and for that I followed all the tutorials on the web without success.
Using Acer recovery install, whatever the chosen recovery I get the error "recovery verified failed", and flashing the stock 4.03 recovery I have bugdroid lying.
Using AfterOta, it freezes at step 3/5 and Blackthund3r, it stuck stage two..
I have a bootloader and ICS 4.0.3 OTA maj.
If someone has an idea, I'd be grateful
Thanks !
babysugar said:
Hello,
I plan to install a custom rom, and for that I followed all the tutorials on the web without success.
Using Acer recovery install, whatever the chosen recovery I get the error "recovery verified failed", and flashing the stock 4.03 recovery I have bugdroid lying.
Using AfterOta, it freezes at step 3/5 and Blackthund3r, it stuck stage two..
I have a bootloader and ICS 4.0.3 OTA maj.
If someone has an idea, I'd be grateful
Thanks !
Click to expand...
Click to collapse
Rooted?
Yes? use AcerRI to install any recovery.
Download thor200240/digetx CWM 1.7.3.zip here
Copy zip to SD card
Reboot to recover.
Install from zip file > Choose file from SD Card
Select the zip and install.
Reboot to recover if u see CWM 1.7.3 ur set.
Full Backup
Save your cpuid (In your CWM folder on your sd card inside the backup files u just made. Should be a text file named uid.txt or cpuid.txt.)
Copy any compatible rom onto your SD card
Wipe data, cache and dalvik
Flash your rom the same way u installed the .zip file.
Thank you for your response.
Yes, I'm rooted and I already tried Acer Recovery Install without success...
I get "recovery verified failed" (in red)...
tried all the recoveries in ARI?
use adb to install the zip then.
shadowmikeshadow said:
tried all the recoveries in ARI?
use adb to install the zip then.
Click to expand...
Click to collapse
I tried all the recovery... And I don't know how to use adb :s can you quickly explain ?
use the platformer tool link below to use adb so u dont need sdk.
Follow instructions on platformer tool download page to set up your adb
open command prompt and navigate to your platformer
cmd commands:
view available directories: dir
change directory: cd (cd desktop (forward directory example) / cd .. (up directory example))
Use this guide to install with adb
cwm: here
platformer: here
Ok, I'll try later because I can't now and I tell you !
Thanks !!
make sure your rooted too, that could be causing the issue with ari..
download root checker from play store its free
shadowmikeshadow said:
make sure your rooted too, that could be causing the issue with ari..
download root checker from play store its free
Click to expand...
Click to collapse
I already checked, I'm rooted
Having the same issue.
I will also look into adb tool because I'm in the same boat. I did pretty much the same thing and am also stuck with the same error message and can't access the Recovery mode.
shadowmikeshadow said:
make sure your rooted too, that could be causing the issue with ari..
download root checker from play store its free
Click to expand...
Click to collapse
I don't understand.
I put the recovery on sdcard with adb, and next ? How should I install it ?
Follow this guide here
but use the recovery from the zip in earlier post.
I tried to root my Nexus 6P and now I'm stuck. It won't finish booting. I followed instructions found on the web. I unlocked bootloader with no problem. I copied the latest SuperSU file to the phone. I installed TWRP recovery. However, I could not find the SuperSU file when using TWRP. Nevertheless, when I went to exit, TWRP asked if I wanted to instal SuperSU. I recall reading somewhere that it will install the wrong version of SuperSU (not the one for 6.0.1). Somehow I must have hit the wrong selection because it installed it anyway. Now I have an infinite loop.
I have tried to factory reset with TWRP. That fails. I downloaded the 6.0.1 images files from Google. I tried to run flash-all.bat, but that doesn't work. I have pushed images and ZIPs to the /sdcard/ folder with ADB. ADB recognizes the device, but fastboot does not (when connected to my laptop) (which is why flash-all doesn't work). I have tried to install the images/zips with TWRP. However, I always get "failed" messages. I get messages that partitions won't load.
Stupidly, I do not have a nandroid backup (yes, I know, a dumb move).
Any suggestions on what to try next? I'm at my wit's end with this. I've searched the web all morning and found all kinds of helpful info, but I can't find anything to get me past this point. I am perfectly willing to wipe it all out and start over again if I could just force it to do that. I just bought it so I suppose I could return it (I think there's a 30-day return policy), but Google might not like it if it comes back in this state, I suppose. I had an AT&T Galaxy Note 5 for half a day but found out, after the fact, that I can't root it.
Thanks for any help or suggestions.
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
jaidev.s said:
Why did you follow instructions found on "Web" when u have the beautiful guide by our @Heisenberg? Read this thread. Instead of running flash - all. Bat file, follow the instructions in this guide. http://forum.xda-developers.com/showthread.php?t=3206928
Click to expand...
Click to collapse
I saw that post. I wish I had followed it. However, the instructions are very similar to what I tried, although not exact. Where I went wrong is letting TWRP install SuperSU for me. I didn't mean to but when I touched the phone it installed it (of course, I hit something, but I don't know what). Fastboot does not recognize the phone in recovery. I can follow Heisenberg's instructions to get back to stock IF fastboot would recognize the phone. ADB recognizes the phone. Would it be possible to use ADB Sideload instead? How can I force fastboot to recognize the phone? If I could do that, I would be able to flash images back to the phone. Thanks!
U should try fastboot in bootloader / download mode instead of recovery mode..
OK, two comments: Duh (as I slap my head) and Bless You! That worked. I'm back to stock. At least the phone works now. I'll try again to root following Heinsenberg's instructions! Thanks. Where do I sent the beer money?
jaidev.s said:
U should try fastboot in bootloader / download mode instead of recovery mode..
Click to expand...
Click to collapse
Well, I'm back to a stock phone, anyway. Flashing SuperSU per Heinsenberg's instructions did not give me root. Oh well. I'll keep trying. It did install and it did reboot just fine. However, root checker says I have no root and Titanium Backup won't run, either. Thanks.