Database Users

Can't select options in Clockwork Recovery 1.7.3

Oops.
So I got 'Rom Manager' from the app store thinking it would simplify my rom flashing tendencies. I loaded the Clockwork Recovery on last night, did a backup and tried to flash Damage1.0 over 0.99.
Now DC1 is freezing on the nexus startup screen and when I boot into Clockwork, I can't select any of the options; I have to remove the battery.
Can anyone help?

There is alwaready a thread about this

Um... where? Sorry if this is a repost.

JMadr said:
Um... where? Sorry if this is a repost.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=648762

Got it.
But can anyone suggest anything for my specific case? I'm entirely dead in the water here.

JMadr said:
Got it.
But can anyone suggest anything for my specific case? I'm entirely dead in the water here.
Click to expand...
Click to collapse
when you're in recovery you still have access to the flash_image functionality. So all you really have to do is get the old recovery img and put it on the root of your sd card. then just do
Code:
flash_image recovery /sdcard/recovery-whatever-heroc.img
and that should put an old recovery on for you, then you will be able to flash other roms as much as you want. have fun

I appreciate the reply. I'm not quite sure what you mean though. I can't mount my phone because I can't boot - so I can't put any files I don't have onto the memory card. Also, how would I input that code if my computer can't see that I have my device connected?
Sorry, if my questions are annoying. This is the first time I've ever had a problem with any of this stuff. Help would be greatly appreciated... I really cant afford a new phone right now.

JMadr said:
I appreciate the reply. I'm not quite sure what you mean though. I can't mount my phone because I can't boot - so I can't put any files I don't have onto the memory card. Also, how would I input that code if my computer can't see that I have my device connected?
Sorry, if my questions are annoying. This is the first time I've ever had a problem with any of this stuff. Help would be greatly appreciated... I really cant afford a new phone right now.
Click to expand...
Click to collapse
adb wont even read it? if you do "adb devices"? ( in recovery mode )

you need to download the android sdk
http://developer.android.com/sdk/index.html
then you can run the command
adb shell
which will give you a command line on the phone.
If you don't have the old recovery on there then you can run something like
adb push fileOnYourComputer /sdcard/whateverName.img

if he flashed the clockwork recovery he has to have the android sdk for adb

venumx said:
if he flashed the clockwork recovery he has to have the android sdk for adb
Click to expand...
Click to collapse
It looks like you can flash it from the app
http://forum.xda-developers.com/showthread.php?t=639153
This is the problem with apps like that and automated processes for rooting. When the phone goes BOOM we need to go back to basics to explain things.

I downloaded the SKD, but I really have no idea what to do at this point. I'm trying to use terminal to execute commands, but nothing is coming back. What am I doing wrong?
Would anyone mind PMing me a walkthrough for pushing files/flashing updates via OSX? I would really appreciate anyone's help.

unzip it
open up a terminal
cd into wherever you unzipped it into
Code:
cd tools/
./adb devices
if you see your phone then you can do all the command we have been telling you
push the old recovery onto the phone
Code:
./adb push fileONComputer /sdcard/NAME.img
go into the phone
Code:
./adb shell
and run the flash
Code:
flash_image recovery /sdcard/NAME.img

centran said:
It looks like you can flash it from the app
http://forum.xda-developers.com/showthread.php?t=639153
This is the problem with apps like that and automated processes for rooting. When the phone goes BOOM we need to go back to basics to explain things.
Click to expand...
Click to collapse
yeah i agree automatic programs that do this for people hurt them more than they help them haha, the automatic ones should just be a convenience to those who know what they're doing !!

Problem solved! Another victory for y'all at XDA. Thanks a bunch to all that helped.

Cant flash another recovery image!!!

It used to work along time ago, this is my new refurb that i rooted a few days ago, im on the 1.5.2 recovery image and im trying to flash the new 1.6 but i dont what the crap im doing wrong. i keep getting error messages i used to be able to do this in 10 seconds. i already have the image on the root of my card can anyone help.
Plus those bastards sent me a refurb that has dead pixels that are white in the blk screen wtf sprint, thats pure whack customer service.
EDIT: problem solved, i was trying this whole time to flash another recovery inside recovery, i actually left the phone on and pushed the recovery lol no more ghanja.

see the # symbol when you enter teh shell? that means you have root already and su isn't necessary. Also try unplugging then plugging back in, the phone from the usb. The file not found error probably means that the sd card is mounted. do an ls from /sdcard to make sure

Also try "adb mount" over "mount -a".

DISABLE usb debugging.
i know, its the little things we overlook. i just did this last night and forgot to disable it.

i did and its still not working.........i dont understand, let me upload another pic. and i already tried adb mount and fastboot still no luck

i kept getting these errors what i did and found easiest with no errors is save the recovery in the sd card. download terminal emulator then in terminal emulator su then enter
then type flash_image recovery /sdcard/nameofimage.img
someone please make sure my prompts are right as i hadn't done it in awhile.

I am trying to do the exact same thing and getting the exact same errors. The file is definitely on the sd card, I am typing the name correct, and USB debugging is off.
Anyone have any other ideas or ways to update to the newest recovery image?

Maitiu said:
I am trying to do the exact same thing and getting the exact same errors. The file is definitely on the sd card, I am typing the name correct, and USB debugging is off.
Anyone have any other ideas or ways to update to the newest recovery image?
Click to expand...
Click to collapse
hahaha dude it used to work perfectly, i been trying and trying for the past couple of hours. (scratching head)

Demoyo23 said:
hahaha dude it used to work perfectly, i been trying and trying for the past couple of hours. (scratching head)
Click to expand...
Click to collapse
you try using the terminal emulator method directly on the phone? only way i can get to work and works everytime.

I'm working on that now, but I tried that a few days ago and got different errors, I'll post what the specific error was when I get there in a few minutes. For some reason Superuser Permissions is force closing right now.
Yeah even from the terminal emulator, I get a "not found" error.

I just updated today from RA1.5.2 to RA1.6.2. I used the Recovery Flasher to update to the newer version as that is what I had originally used to get 1.5.2 installed.
These were original instructions from theunlockr .com:
7. Save both the Recovery-RA-HEROC-v1.5.2.img and the FlashRec.apk to your computer, then copy them both to your SD card (do NOT put them inside any folders on the SD card, just put them on the SD card itself).
8. Unplug the phone from the computer once they are downloaded to the SD card.
8. Goto the Market and download Linda File Manager or any file manager program if you do not already have one.
9. Open the file manager and goto SDCard and then find the FlashRec apk file and click it. If asked tell it to use Package Installer to open it. It should automatically install the apk.
10. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
11. Once done, click on the empty text box in the FlashRec program and type (again remember we have replaced the recovery image from the one in the video so type what is written here, NOT what is written in the video!):
/sdcard/recovery-RA-heroc-v1.5.2.img
Then click on the Flash Custom RecoveryImage button and wait for it to finish.

Just barely.

That's still not working flashrec won't back up it keeps saying failed. And it won't flash a custom img. This refurb is cursed I had no problem doing it all on my original.
-------------------------------------
Sent via the XDA Tapatalk App

Demoyo23 said:
It used to work along time ago, this is my new refurb that i rooted a few days ago, im on the 1.5.2 recovery image and im trying to flash the new 1.6 but i dont what the crap im doing wrong. i keep getting error messages i used to be able to do this in 10 seconds. i already have the image on the root of my card can anyone help.
Plus those bastards sent me a refurb that has dead pixels that are white in the blk screen wtf sprint, thats pure whack customer service..
Click to expand...
Click to collapse
Type 'adb devices' in... Whenever I see the '/' before the '#' it means that it isn't recognizing my phone.

Just do it through adb. I did mine through adb the 1st, 2nd and 3rd time. After looking at the dirwctiona, I think it might be easier and should work.
-------------------------------------
Sent via the XDA Tapatalk App

Make sure the phone is connected as charge only, once it is type
ls /sdcard
AND PASTE THE RESULTS HERE
It sounds like you don't have the sdcard mounted or if you do you may be typing the file wrong compared to what is on the sdcard.
Don't panic, this had nothing to do worth the phone being refurbished, it is only a simple file not found error that once you fun that command can easily be solved.

liquidtenmillion said:
Make sure the phone is connected as charge only, once it is type
ls /sdcard
AND PASTE THE RESULTS HERE
It sounds like you don't have the sdcard mounted or if you do you may be typing the file wrong compared to what is on the sdcard.
Don't panic, this had nothing to do worth the phone being refurbished, it is only a simple file not found error that once you fun that command can easily be solved.
Click to expand...
Click to collapse
it keeps telling me permission denied lol

Type in
"adb shell" then
"ls /sdcard"
Without the quotes exactly as I typed them one at a time and paste the results.

dirkydirk23 said:
i did and its still not working.........i dont understand, let me upload another pic. and i already tried adb mount and fastboot still no luck
Click to expand...
Click to collapse
did you try fastboot boot recovery [dir on your computer]

Do a search for adb shell recovery. It should tell you how to do it. You are going to have to mount the system before doing anything else...and also change the recovery image to something Like recovery.ing as it is easier to type and less likely to be mis-typed
-------------------------------------
Sent via the XDA Tapatalk App

[Q] Bricked? can't mount sdcard

build: RA-dream-v1.7.0
E:Can't mount /dev/block/mmcblk0p1 (or dev/block/mmblk0)
(No such file or directory)
E:Can't mount SDCARD
Boots RA-dream-v1.7.0 and fastboot just in good work
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
So can't flash any new roms...
is the phone bricked?
Really need some help here i'm stuck

I'd really like to see if this correctable with my JTAG solution. PM sent. Others who see this, I've corrected partition bricks on the Galaxy S phones several times with JTAG.

Most likely only the sdcard is broken. Did you try to read it with your PC? As long as you can boot your phone, it's not a brick.
Sent from my Gingerbread on Dream using XDA App

yeah dood ur phone is fine sounds like ur sd card crashed...

At now，I have changed many TF cards，the problem it is！
Below the RA-dream-v1.7.0，link to PC， use USB-MS toggle ；can read or write the TF card.

acmilanajax said:
At now，I have changed many TF cards，the problem it is！
Below the RA-dream-v1.7.0，link to PC， use USB-MS toggle ；can read or write the TF card.
Click to expand...
Click to collapse
so what does that mean? can you transfer files through the usb-ms toggle? or can you at least plug your sd into your comp? and will it read it? try to re partition...

Restore 2 default

Or go to recovery

ldrifta said:
so what does that mean? can you transfer files through the usb-ms toggle? or can you at least plug your sd into your comp? and will it read it? try to re partition...
Click to expand...
Click to collapse
TF card in G1，not in my computer；in my computer also write and read it， re patition I have tried ，but can‘t flash in G1

acmilanajax said:
TF card in G1，not in my computer；in my computer also write and read it， re patition I have tried ，but can‘t flash in G1
Click to expand...
Click to collapse
what is a tf card? do you mean sd card? have you tried to re partition your sd card in recovery mode? or maybe try re formatting to FAT32 on your computer..

ldrifta said:
what is a tf card? do you mean sd card? have you tried to re partition your sd card in recovery mode? or maybe try re formatting to FAT32 on your computer..
Click to expand...
Click to collapse
YES, all what you say ，I try it ，but can't flash G1，also.

This is probably a messed up misc partition unless there is permanent damage to the sdcard reader. Either way jtag is overboard (either is not needed or won't help)
Try to get us you kernel's command line in recovery run the following on your computer with your phone attached via USB:
'adb shell cat /proc/cmdline'
delete or '*' out your serial number and post the rest of that string here unmodified.

I have the same problem..
this is the command output:
Code:
board_trout.disable_uart3=1 board_trout.usb_h2w_sw=1 board_trout.disable_sdcard=
1 smisize=64 androidboot.baseband=2.22.27.08 androidboot.cid=T-MOB101 androidbo
ot.carrier=TMD androidboot.keycaps=qwertz androidboot.mode=recovery_manual andro
idboot.serialno=************ androidboot.bootloader=1.33.0013d no_console_suspen
d=1 console=null mtdparts=msm_nand:[email protected](misc),[email protected]
0(recovery),[email protected](boot),[email protected](system),[email protected]
40000(cache),[email protected](userdata)
Do I have to downgrade and root my phone again?

ThauExodus said:
Code:
board_trout.disable_uart3=1 board_trout.usb_h2w_sw=1 board_trout.disable_sdcard=
1 smisize=64 androidboot.baseband=2.22.27.08 androidboot.cid=T-MOB101 androidbo
ot.carrier=TMD androidboot.keycaps=qwertz androidboot.mode=recovery_manual andro
idboot.serialno=************ androidboot.bootloader=1.33.0013d no_console_suspen
d=1 console=null mtdparts=msm_nand:[email protected](misc),[email protected]
0(recovery),[email protected](boot),[email protected](system),[email protected]
40000(cache),[email protected](userdata)
Do I have to downgrade and root my phone again?
Click to expand...
Click to collapse
Prob not:
The problem is: board_trout.disable_sdcard=
1
This is determined usually by the SPL based on the misc data, so let's fix misc
The below has a misc image for a dream device with CID T-MOB101 (as shown in the cmdline I'm replying to, its best if you have a device with another cid to use a hex editor to update the misc.img to match.
1) download the following and place in a directory on your computer to be used via adb:
misc_tmob101.img
erase_image
2) boot recovery
3) run the following adb commands to push the files to the phones ram
Code:
adb push misc_tmob101.img /tmp/misc.new.img
adb push erase_image /tmp/erase_image
4) run 'adb shell' and at the prompt run the following:
Code:
chmod 0755 /tmp/erase_image
/tmp/erase_image misc
flash_image misc /tmp/misc.new.img
sync
5) reboot the phone normally and see if the problem remains.

YAY! THANK YOU.. now I have to look for a new paper weight..xD

Zte open c 2.1

This is the latest 2.1 for ZTE OPEN C, to install download extract to /sdcard/clockworkmod/backup use .50 recovery to install by choosing restore, navigate to /sdcard/clockworkmod/backup/new_2.1 then let .50 recovery restore 2.1, reboot and enjoy 2.1
in recovery mode
backup and restore > restore from /external_sd > new_2.1 > yes restore
https://drive.google.com/folderview?id=0B_6NtXCtTLkHeGgzcDVwWnZWR2c&usp=sharing
my roms use stock kernel, comes from Open_C_upgrade_Tool: http://alturl.com/2bpns

vampirefo said:
This is the latest 2.1 for ZTE OPEN C, to install download extract to /sdcard/clockworkmod/backup use .50 recovery to install by choosing restore, navigate to /sdcard/clockworkmod/backup/new_2.1 then let .50 recovery restore 2.1, reboot and enjoy 2.1
in recovery mode
backup and restore > restore from /external_sd > new_2.1 > yes restore
https://drive.google.com/folderview?id=0B_6NtXCtTLkHeGgzcDVwWnZWR2c&usp=sharing
Click to expand...
Click to collapse
Thank you so much vampirefo, I am loving this build so far!

KUPOinyourWINDOW said:
Thank you so much vampirefo, I am loving this build so far!
Click to expand...
Click to collapse
This is the best build of Firefox OS I have ever used, omg. I don't know what it's like for you, but I can't find many bugs.

thanks man
overall i like it
the only negative is when unstick App Transition, opening/closing app/setting becomes very slow (in 1.4 i did unstick to make it faster/smooth)

2.1 works well, however 1.4 is more refined, closer to being released, Once 2.1 gets closer to being released it will be the preferred firefox version.

vampirefo said:
..in recovery mode
backup and restore > restore from /external_sd > new_2.1 > yes restore
Click to expand...
Click to collapse
It can't find the folder.
Unmounted and mounted the external_sd didn't help.
What's going wrong?

Thanks for the build!
But could you please explain how to use .50 recovery?
I am trying to flash it to my open c with:
adb push cw_recovery_50.img /sdcard/cwm.img
But I get:
failed to copy 'cw_recovery_50.img' to '/sdcard/cwm.img': Read-only file system

YemSalat said:
Thanks for the build!
But could you please explain how to use .50 recovery?
I am trying to flash it to my open c with:
adb push cw_recovery_50.img /sdcard/cwm.img
But I get:
failed to copy 'cw_recovery_50.img' to '/sdcard/cwm.img': Read-only file system
Click to expand...
Click to collapse
You don't have to adb push the recovery to sdcard, use fastboot to boot recovery.
fastboot boot cw_recovery_50.img
or to install recovery
fastboot flash recovery cw_recovery_50.img

happyass**** said:
It can't find the folder.
Unmounted and mounted the external_sd didn't help.
What's going wrong?
Click to expand...
Click to collapse
do you have a micro sdcard installed? did you extract the backup in correct place?

vampirefo said:
do you have a micro sdcard installed? did you extract the backup in correct place?
Click to expand...
Click to collapse
Well I've got an sdcard in it which I used on 1.4. Or do I need to initialize it or do anything in particular? I even did 'format' of the recovery menu..

happyass**** said:
Well I've got an sdcard in it which I used on 1.4. Or do I need to initialize it or do anything in particular? I even did 'format' of the recovery menu..
Click to expand...
Click to collapse
Unless you have used recovery to make a backup, then you need to create all the folders, if you have used recovery to make a backup, folders would have been created except for new_2.1, which is made when you extract 2.1.
if you don't have /clockworkmod/backup folders on your sdcard you need to make them, then in /clockworkmod/backup extract 2.1
in recovery mount external_sd
then post output of
adb shell ls /external_sd/
adb shell ls /external_sd/clockworkmod/backup/

Thanks for the tip!
I managed to get .50 recovery working, but now when I am restoring from external_sd it says:
Error while restoring /system!

YemSalat said:
Thanks for the tip!
I managed to get .50 recovery working, but now when I am restoring from external_sd it says:
Error while restoring /system!
Click to expand...
Click to collapse
That usually means bad download, you may need to redownload 2.1.

vampirefo said:
That usually means bad download, you may need to redownload 2.1.
Click to expand...
Click to collapse
I re-downloaded it and it now falls with hash mismatch for system.ext4.tar.a
I tried formatting the sd card with .50 recovery but it still gives that error.
Is there any way to do the update via fastboot by any chance?

No, your sdcard is bad, if you have room on internal sdcard, make folders and extract 2.1 there.
sent from my kingSing T1 via taptalk

vampirefo said:
No, your sdcard is bad, if you have room on internal sdcard, make folders and extract 2.1 there.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
I just did an adb push to the card:
adb push new_2.1 /sdcard/clockworkmod/backup/new_2.1/
But when I'm in .50 recovery - it does not see the new_2.1 folder. It only sees the one it created earlier when I did a backup.
Any idea what the heck could be wrong? xP

No ideal without looking at your sdcard.
sent from my kingSing T1 via taptalk

vampirefo said:
No ideal without looking at your sdcard.
sent from my kingSing T1 via taptalk
Click to expand...
Click to collapse
Sorry about all the stupid questions, just the last one - can it be done via 'zip install' in recovery by any chance? Or does it have to be through restore?

The version I uploaded is restore only, you could make a zip install if you want, use Google to find info how to build cwm installation zip.
sent from my kingSing T1 via taptalk

Ok, thanks for the help!
I'll post the zip here if I succeed in making one.

Fire HD 8 recovery

So im working on trying to get twrp up on the HD 8 but i need a backup of someones elses recovery. Its located at /dev/block/mmcblk0p7

Update please if you have root, go to adb then type adb shell and then su. after that just run this command dd if=/dev/block/mmcblk0p7 of=/storage/sdcard1/recovery.img, if you want it to go somewhere else then just change the part that says storage/sdcard1(for example if you want it to go to the device storage then just remove the 1) the recovery image should then be on your sd card. please then attach or send the recovery image to me. Thank you

Hi, please find attached the recovery file!

coopmaster said:
Update please if you have root, go to adb then type adb shell and then su. after that just run this command dd if=/dev/block/mmcblk0p7 of=/storage/sdcard1/recovery.img, if you want it to go somewhere else then just change the part that says storage/sdcard1(for example if you want it to go to the device storage then just remove the 1) the recovery image should then be on your sd card. please then attach or send the recovery image to me. Thank you
Click to expand...
Click to collapse
Hi, please find attached the recovery file!

schr01 said:
Hi, please find attached the recovery file!
Click to expand...
Click to collapse
Thank you so much. I needed that so I can compare also because I changed mine and I should have backed it up first.

Any luck on compiling twrp?

madsc13n41s4 said:
Any luck on compiling twrp?
Click to expand...
Click to collapse
would not matter, there is no way to use it
Sent from my KFFOWI using XDA Labs

coopmaster said:
So im working on trying to get twrp up on the HD 8 but i need a backup of someones elses recovery. Its located at /dev/block/mmcblk0p7
Click to expand...
Click to collapse
How die you Figure Out where located?

thebrainkafka said:
How die you Figure Out where located?
Click to expand...
Click to collapse
i think i was following some link i found that explains where the recovery normally is. PM if you want to talk more about it.