Database Users

[Q] Accessing Clockworkmod in /sdcard

Greetings.
I am trying to install Cyanogenmod 7.0.2 on my HTC Tattoo (still has 1.6). This is the first time I've done this.
I am following the Cyanogenmod wiki page that shows you the whole process of rooting+flashing a new rom (since this is my first post I am unable to post outside links in this thread).
In the "Installing Clockworkmod Recovery" section, I get the following error when trying to flash the image:
flash_image: not found
I listed the files in /sdcard and saw that it was completely empty.
Can anyone tell me what I missed?
I copied the Clockworkmod image file to the root directory by connecting my phone to my PC through USB (USB Debugging was on) and copying the file there.
Please let me know how to solve this.
Thank you.

I was able to solve my problem and proceed with the attempt to flash Clockworkmod. Now I'm getting another error though:
error writing recovery: No space left on device
I have plenty of space in the SD Card (~2GB), but I'm assuming the problem is with the phone's internal memory. I don't know what I can delete.
Any thoughts?
Thank you.

Hi
Ok so i see you have that kind of problems...
I done it this way.
Downloaded Rom Manager->Downloaded Superuser
Then in ROM MANAGER i clicked an option "Flash Clockwork Mod Recovery"..
After that my phone had Clockwork and i completed the procedure to Flash CM7...
Hope this will help you..

CROpipe said:
Hi
Ok so i see you have that kind of problems...
I done it this way.
Downloaded Rom Manager->Downloaded Superuser
Then in ROM MANAGER i clicked an option "Flash Clockwork Mod Recovery"..
After that my phone had Clockwork and i completed the procedure to Flash CM7...
Hope this will help you..
Click to expand...
Click to collapse
Hi,
Thanks for your reply.
I tried to do as you said and installed both Rom Manager and Superuser. But now I have other issues...
1. On Superuser, it says there is a newer version of su and to update. I accept and get the following error:
An error occurred and su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your binary.
2. So, I decided to ignore the update of su and just move on to Rom Manager. Here, I get an error like "su was not found in /system/bin". Well, su is in "/data/local/bin", as per the cyanogen wiki to root the phone. After this, any attempt to flash Clockworkmod fails.
3. To try to make it so Rom Manager has everything it needs, I followed the wiki again, but this time I tried to move the su file to /system/bin. I got the following error:
failed on './su' - Cross-device link
Any ideas?
Thanks in advance!

Hmm, i had the same problem when i was trying to Flash CM7...
Your phone is not rooted...
I know its very frustrating but no worries!
1.Download program from this thread ->http://forum.xda-developers.com/showthread.php?t=761507... you'll see the program in attachemnts and dl the first one.
2.Paste it in your's SD card , install it (use ASTRO MANAGER, to find the program)
3.Open the program and root the phone with 1 click
4. Then Superuser will ask you to allow it and click yes, and go to ROM MANAGER.
5.You will have to allow the Superuser here too.. Do it.
6.Flash Clockwork Mod recovery, and reboot into recoverymod.
7.Flash your Rom , flash Gapps(Google applications)
8.Enjoy

Thank you CROpipe!
Your instructions worked! I now have CM7 installed on my HTC Tattoo!
Here are the issues I found though:
1. When I was trying to download the ROM using ROM Manager, the list of ROMs was empty. Maybe it's because I was not using the Premium version...? I ended up downloading the ROM from the forum, copying it to the SD card and installing it that way.
2. I tried also to install GApps through Rom Manager. I was afterwards able to set up my google account, but I still had to manually download GMail, Google Maps, ... I'm not sure if this is actually how it's supposed to go... :-/
Anyway, thanks again for the help.

Yap that is quite allright Congrats on your new ROM ))

Updating HBOOT 08x to 1.01.000 on HTC Wildfire (including Rooting & S-OFF)

Hi guys
I just updated my HTC Wildfire from HBOOT version 08… to 1.01.0001 and I ran into many problems on the way. I’m just writing this guide to help out any other people that are in the same situation as me and don’t want to be searching Google for half a day finding solutions to every tiny problem. Please note this worked for me but I cannot guarantee it will work for you so follow this tutorial at your own risk!
Step 1: Find the RUU that has HBOOT 1.01.0001
I used RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe which you can find here.
And more specifically the download link is here (Credits to 3xeno for the RUU list and uploads).
Step 2: Extract the rom.zip from the RUU
There are many ways of extracting rom.zip the method I used is:
1. Run the RUU installer.
2. Go to your windows temporary folder.
3. Search for rom.zip
Another method that will definitely work and you can be sure you have the correct zip file is given here.
Step 3: Create a goldcard (easy way)
I found that flashing the above RUU was impossible without a goldcard and after lots of searching I found a link for downloading the GoldCardTool - a software that automates most of what you have to do and saves you lots of time.
Note: You need to format your SD card so backup anything important and then go to
Settings -> Storage -> Unmount SD Card
Then hit Erase SD card.
Now you are ready to create a Goldcard.
You can download the software here and follow the instructions in the readme file, they are very straight forward.
Step 4: Prepare the ROM for flashing
Rename rom.zip to PC49IMG.zip and place it on your SD card (in the root folder of your SD card ie. No folder within the SD card).
Now reboot your phone into the bootloader. Mine always starts with FASTBOOT in focus and I have to press the power button over BOOTLOADER to get it to scan the SD card for PC49IMG.zip. Once it finds the zip file it will open and parse the file and then ask you if you’d like to update. Press volume up to confirm then DON’T TOUCH ANYTHING.
Once the update is complete reboot the bootloader and make sure the HBOOT is 1.01.0001. Once that is confirmed you can boot into Android.
Step 5: Use AlphaRevx to get S-OFF and Clockwork recovery
Before you use AlphaRevx you will need to make sure you have the correct drivers.
Download the HTC Fastboot drivers which you can get here.
Also download Superuser which you will use later from here and copy this onto your SD card when you find the time!
(Credits for the links go to the guys at unrevoked for their wiki)
Now it’s time to get the Revolutionary software.
Go to http://revolutionary.io/ and download Revolutionary.
Now plug in your phone and make sure USB debugging is on, if it is not then go to Settings -> Applications -> Development and Enable USB debugging.
Now extract and run the Revolutionary software. It should open a command prompt and it will walk you through the installation, the serial number that you give in the website is given in the command prompt (it is not the same as the serial number on the back of your battery!). If you find an error right from the start it probably means you don’t have ADB drivers – Google sdk can help you out with that one. At the end of the installation it gives you the option to download and install Clockwork recovery mod – say yes (Y) to this option!
Step 6: Rooting your phone
Now that Revolutionary is complete you can reboot your phone into Clockwork Recovery. Select install application from zip file. Choose to select the zip file and then find the Superuser zip file that you download earlier (Superuser-3.0.7-efgh-signed.zip) and install it. If you forgot to put it on DON’T reboot your phone just go to the main menu of Clockwork Recovery. Go to mounts/partitions (I can’t remember the exact name) and at the bottom it says “mount SD card”. Select that and copy the file over to the SD card and then flash it using the directions given above.
Step 7: Flashing a custom ROM (or Fix for if your phone stops on boot screen)
You can either stop at Step 6 or continue to this step and flash a custom ROM.
To do this boot into Clockwork Recovery and do the following:
1. Wipe data
2. Clear cache
3. Clear Dalvik cache in advanced menu
I found that after I flashed a ROM without doing the above 3 steps it got stuck on the boot screen so please do the above 3 steps!
Now flash the ROM by choosing to install from a zip file. Reboot and you’re done!
I updated to Cyanogen mod 2.3.7 and I just want to throw in that Radio_13.55.55.24H_3.35.20.10.zip worked for me !
I really hope this tutorial helped. I just did it with my phone and it’s working well so I wanted to share what I did. Credits go out to everyone that put up tutorials on how to solve problems and all the download links and especially to the guys that wrote Revolutionary – it is an amazing software keep up the good work !
Cheers guys
Kerren

A very thorough guide and many people will benefit from this.
This is nearly exactly the same routine I followed from a guide which I can't remember where from now lol and very grateful help from 3xeno (yoda) but I don't think I did anything with alpharevx though and also I just flashed my cm7 nandroid after revolutionary to gain my superuser and I'm sure the serial part WAS my serial on phone but can't remember exactly.
Anyway my point is that after reading through your post it brought back the memory of the satisfaction of successfully s-offing my phone. great work.
"sent from me2u"

Cool!
Haha thanks man glad I could bring back memories
When it comes to the serial number I'm not completely sure, I had generated a code from the serial on the back of my battery and that didn't work. I then read the serial from command prompt and it seemed a lot shorter (also I got a code that worked ).
Maybe I made a mistake originally but all I know is that you don't have to rip your battery out to get the serial number - they give it to you anyway .
Thanks very much for the reply!

Ah yes that sounds familiar now.
"sent from me2u"

[Q] please help me unbrick my nook color!

hello,i'm a fresh man as a nook colorer,but someday,i made a mistake and deleted the boot file of NC,it's out of work,so i reviewed xda to find solutions,finaly i read the thread"forum.xda-developers.com/showthread.php?t=1448186",image the file"Update-Encore-CM9-DualbootSD-02012012.zip",nc start from sdcard,it works!even so it doesn't smooth.so i want to find another way,i was enlightened by the thread"http://forum.xda-developers.com/showthread.php?t=919353",after downloading the file "Boot","System","factory.zip", according to description,l get this output:
install the factory.zip ,the screan show :
installing:/sdcard/factory.zip
finding update packect...
opening update packect...
installing packect...
assert failed:getprop("ro.product.device")=="zoom2"||"zoom2"
E:Error in /sdcard/factory.zip
(status 7)
installation aborted
when i following the instruction to copy system.img,it says:
adb shell
# dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
dd if=/sdcard/system.img of=/dev/block/mmcblk0p5
dd:write '/dev/block/mmcblk0p5':no space left on devices
499353+0 records in
499352+0 records out
2556688224 bytes <243.8MB> copied ,22.483246 seconds,10.8MB/S
and i got a backup rom image(SN.img) from my friend ,and excute the instruction:"adb push /sdcard/SN.img of=/dev/block/mmcblk0p2",it also tell that :no space left on devices
how can i unbrick my NC?
i realy need your help !
the attchment is the pic of debuging the NC
thanks a lot
my email[email protected]

Here is one way of doing it. This will take you all the way back to unrooted stock and you can start over.
http://forum.xda-developers.com/showthread.php?t=1461172

it still out of work
Harrybub said:
Here is one way of doing it. This will take you all the way back to unrooted stock and you can start over.
http://forum.xda-developers.com/showthread.php?t=1461172
Click to expand...
Click to collapse
first at all ,i must thank you for your answer,Harrybub,but my NC had tried the "8 times reboot" ,i followed you advices and do it again ,but the screen say:install failed.i just don't understand how can i delete the original boot flie which should be forbiden by NC , now ,i think the only way to fix my NC is entering the CWM and flash these file :boot.img ,system.img,factory.zip into NC's correspondence part via usb ADB ,in a other word ,rebulid all the flie of NC.do you have any sugestions ,please let me konw! thank
by the way ,do you ever see someone have the same problem?

I'm missing something very important..right?

I very carefully followed the "newb" thread.
I've installed 2.08 HardSPL, an d MagLDR v113 and my phone has the 12 option menu.
However when I go to click "DAF.exe" (in admin mode, win7 64bit) it just gives me an error.
-----------
Error Description: Config load failed.
Info: .\RSPL\RSPL.cpp (725)
Error Description: CONFIG: can't open config file
Info: .\RSPL\RSPL.cpp (304)
----------
Now I see the sentence below...in multiple places..like I should know what this is..but I think I'm missing something very important
Run DAF.exe (Right Click and Run As Administrator if you have Vista or Windows 7) in the folder you extracted the image to and follow the intructions on your pc to start flashing
Click to expand...
Click to collapse
What IMAGE is this referring to??
I have a feeling I'm supposed to do something when running DA.exe..it tells me 'readme.txt not found' on the 3rd page so I must be missing this image.
Is this something really stupid I'm missing? This is a new process for me (although I flashed this HD2 a zillion times with Windows ROMs in the past) and clearly I'm supposed to have put MaglDR inside of another folder with something else??
I downloaded the NexusHD2-JellyBean-CM10_V1.3a ROM but there's no image file or anything..help!!

You missed writing a descriptive title
Can I have a look at that "newb" guide of yours?
Also, from there you can just download the "HD2 Toolkit" and install the recovery from there.

thanks! I was using this guide:
http://forum.xda-developers.com/showthread.php?t=893948
I am looking for the toolkit now.

If you're having problems with the toolkit, you can follow this guide starting from step #7. Don't forget to read the important notice at the top should you choose to follow it.
Good luck.

this suddenly got a whole lot more complicated...
i thought once i had HARDSPL 2.08, the 2.15.50.14 radio and MAGLDR v113, I could just double-click a ROM image or something.

nyvram1 said:
this suddenly got a whole lot more complicated...
i thought once i had HARDSPL 2.08, the 2.15.50.14 radio and MAGLDR v113, I could just double-click a ROM image or something.
Click to expand...
Click to collapse
Once you have all of that, you need to flash CWM recovery and then the ROM. It's a lot easier than you would think, provided that you read everything properly. Just follow the guide in my sig (a more updated version of the guide you linked) and you'll be fine.

thanks! i just flashed to the 'stock' LEO ROM..i see..the DAF.exe is generally in the directory w/ the image you download..but I'm guessing that process is old.
I will read your guide and see about getting CWM and a newer ROM now that i know it has a 'base' ROM and is talking to the PC ok.
THank you so much! I just want to put a stable version of JB on here and see if this phone still has some life left..its been in a drawer for months.

THANK YOU!!!! i'm running the NexusHD2 jellybean ROM now as well!! that was easy.
PS i also have a nexus 4 so we have similar phone setups.
the HD2 lasted until i got my nexus back in november.

nyvram1 said:
I very carefully followed the "newb" thread.
I've installed 2.08 HardSPL, an d MagLDR v113 and my phone has the 12 option menu.
However when I go to click "DAF.exe" (in admin mode, win7 64bit) it just gives me an error.
-----------
Error Description: Config load failed.
Info: .\RSPL\RSPL.cpp (725)
Error Description: CONFIG: can't open config file
Info: .\RSPL\RSPL.cpp (304)
----------
Now I see the sentence below...in multiple places..like I should know what this is..but I think I'm missing something very important
What IMAGE is this referring to??
I have a feeling I'm supposed to do something when running DA.exe..it tells me 'readme.txt not found' on the 3rd page so I must be missing this image.
Is this something really stupid I'm missing? This is a new process for me (although I flashed this HD2 a zillion times with Windows ROMs in the past) and clearly I'm supposed to have put MaglDR inside of another folder with something else??
I downloaded the NexusHD2-JellyBean-CM10_V1.3a ROM but there's no image file or anything..help!!
Click to expand...
Click to collapse
Is there a file called FLASH.CFG in the folder where DAF.EXE is located? You may have to create one - there should be at least a sample file included.
If you need a sample file downloads this one but be sure to modify it to suit the ROM you want to install.
flash.cfg - 134 bytes
---
I used to be indecisive. Now I'm not sure... (via Tapatalk)

Flashing Now Fails

I've been flashing N7 with no issues as recently as over the weekend. Today I tried to flash a new ROM and it failed. Tried a second, different ROM, same result. Do not know what I did. Any thoughts?

Error log would help greatly.

How do I get/generate the log? Haven't had to do it before.
Thanks,
Paul

The logs= errors displayed on the screen provided by the interface you use to flash the rom (recovery, computer...)

Does this help any?
TWRP V2.4.4.0
Updating partition details
E: Unable to open zip file
Error flashing zop
Updating partition details...

do I need to create a partition? Never get more details despite the tease.
Thanks,

First -
Try and download a different (NEWER) TWRP. Re-flash TWRP. Try again
or
Have you tried completely wiping the device? And pushing a ROM from ADB or using a USB OTG and Memory stick?
I had issues with my nexus becoming VERY unstable. Leading to issues.
I completely, and I mean completely, wiped. To the point that all that device basically had was a recovery, and a bootloader.
I proceeded to flash again, BOOM all fixed up.

Is there a new TWRP?
I did a factory restore after wiping everything thing, if that is what you mean?
It was working as expected last week, don't know what I did to screw it up

Boot recovery try the operation, choose advanced then copy log to sdcard. The paste the log results.
sent via electromagnetic radiation.

ibsk8 said:
Boot recovery try the operation, choose advanced then copy log to sdcard. The paste the log results.
sent via electromagnetic radiation.
Click to expand...
Click to collapse
Did this, and it said it copied but I am unable to locate it. It says 0\media\data But that folder structure doesn't exist, at least according to file expert

Will a complete wipe/restore create a partition?

pmgreen said:
Will a complete wipe/restore create a partition?
Click to expand...
Click to collapse
None of the instructions currently found in this forum alters the partitioning of the N7. Not fastboot & not the custom recovery, either.
You are chasing a red herring I think. That message you see is about the recovery performing a scan to check to see if there is a change in file systems (or partitioning of external devices) ... which might have occurred in preceding (custom recovery) operations, but didn't in this particular case.
pmgreen said:
Does this help any?
TWRP V2.4.4.0
Updating partition details
E: Unable to open zip file
Error flashing zop
Updating partition details...
Click to expand...
Click to collapse
Focus your efforts here; it certainly looks like a first-order problem.

bftb0 said:
None of the instructions currently found in this forum alters the partitioning of the N7. Not fastboot & not the custom recovery, either.
You are chasing a red herring I think. That message you see is about the recovery performing a scan to check to see if there is a change in file systems (or partitioning of external devices) ... which might have occurred in preceding (custom recovery) operations, but didn't in this particular case.
Focus your efforts here; it certainly looks like a first-order problem.
Click to expand...
Click to collapse
Think reinstalling TWRP would help? It was working fine so I'm a bit stumped what changed and why

pmgreen said:
Think reinstalling TWRP would help? It was working fine so I'm a bit stumped what changed and why
Click to expand...
Click to collapse
You can also soft-boot a recovery without actually flashing it, e.g.
Code:
fastboot boot custom-recovery.img
I suppose you could then poke around and see if it is having troubles mounting any of the normal partitions (/data, /system, or /cache). Look in the kernel boot log of the recovery (cat /proc/kmsg or "dmesg") to see if anything looks strange, etc.
There have been a couple of reports from folks who developed problems that looked like eMMC flash media errors - loss of partitions, failure to mount /data, et cetera. At the moment though, your symptoms are very generic and non-specific, as in "it doesn't boot".
I suppose you saw no errors at all reported on the screen during that stock-install-via-fastboot procedure?

bftb0 said:
You can also soft-boot a recovery without actually flashing it, e.g.
Code:
fastboot boot custom-recovery.img
I suppose you could then poke around and see if it is having troubles mounting any of the normal partitions (/data, /system, or /cache). Look in the kernel boot log of the recovery (cat /proc/kmsg or "dmesg") to see if anything looks strange, etc.
There have been a couple of reports from folks who developed problems that looked like eMMC flash media errors - loss of partitions, failure to mount /data, et cetera. At the moment though, your symptoms are very generic and non-specific, as in "it doesn't boot".
I suppose you saw no errors at all reported on the screen during that stock-install-via-fastboot procedure?
Click to expand...
Click to collapse
The only error is that it can't open the zip. I've tried downgraded TWRP, then upgrading back. Tried flashing the existing rom.
Nothing has worked. The N7 is functional, just will not allow me to flash

pmgreen said:
The only error is that it can't open the zip. I've tried downgraded TWRP, then upgrading back. Tried flashing the existing rom.
Nothing has worked. The N7 is functional, just will not allow me to flash
Click to expand...
Click to collapse
Well, if the source material can't be opened, then there is nothing to be flashed.
So maybe it is better to call this a "can't open files" problem instead of a "can't flash" problem.
Are there any special characters in the file name ... or spaces? If so, try renaming the file so the name only contains [a-z], [A-Z], [0-9] plus dash, underscore, and dot.
The other thing that can happen is if you drop a file in /data/media/0 as the root user, it will show up under /sdcard, but can't be read by non-privileged users via the /sdcard/ path. I'm not sure what the exact details are here - much less why this would effect the recovery (as you would expect everything to be running as root there) - but you can detect this problem by using a terminal emulator, and looking for differences in ownership or file permission:
Code:
$ su
# cd /data/media/0
# ls -ld *
use chown and chmod as appropriate to fix files as needed

bftb0 said:
Well, if the source material can't be opened, then there is nothing to be flashed.
So maybe it is better to call this a "can't open files" problem instead of a "can't flash" problem.
Are there any special characters in the file name ... or spaces? If so, try renaming the file so the name only contains [a-z], [A-Z], [0-9] plus dash, underscore, and dot.
The other thing that can happen is if you drop a file in /data/media/0 as the root user, it will show up under /sdcard, but can't be read by non-privileged users via the /sdcard/ path. I'm not sure what the exact details are here - much less why this would effect the recovery (as you would expect everything to be running as root there) - but you can detect this problem by using a terminal emulator, and looking for differences in ownership or file permission:
Code:
$ such
# cd /data/media/0
# ls -ld *
use chown and chmod as appropriate to fix files as needed
Click to expand...
Click to collapse
Thanks bftb, you are correct it's a can't open zip. No error than fail and it can't open the zip. It says updating partition but nothing changes
The file names are from the developers, once of which I recently successfully flashed. Tried coping the log to the SD card, but unable to find /data/media/0. Do I need to recreate a partition?

(FYI there was an auto-correct typo in my prior post - "su" not "such". Derp)
pmgreen said:
Do I need to recreate a partition?
Click to expand...
Click to collapse
No. (There is no way to do that with the tools we have anyway)
Unless what you mean by "recreate" is rebuild/reinitialize a filesystem in a partition - that's a possibility.
You need to try and figure out why you can't read files.
As a workaround, you can put files on a USB key (FAT formatted, not NTFS) and using TWRP access them by putting the USB key on the other end of a OTG cable.
Your posts are a bit vague - I can't even tell if you have tried other ROM files, whether you checked them to see if they are the correct size/checksum, etc.

pmgreen said:
Tried coping the log to the SD card, but ...
Click to expand...
Click to collapse
At this point, your best approach is still to follow the initial advice of 'ibsk8'. Look in the log file for any further details about errors that occurred.
The logs are typically in /cache/recovery/ or (while the custom recovery is running) in /tmp
Use "adb pull" to get the log file to your PC and have a look at it. If you can't find anything obvious in there, then cut-n-paste the file to http://pastebin.com and provide the link to us.

bftb0 said:
At this point, your best approach is still to follow the initial advice of 'ibsk8'. Look in the log file for any further details about errors that occurred.
The logs are typically in /cache/recovery/ or (while the custom recovery is running) in /tmp
Use "adb pull" to get the log file to your PC and have a look at it. If you can't find anything obvious in there, then cut-n-paste the file to http://pastebin.com and provide the link to us.
Click to expand...
Click to collapse
I am not familiar using ADB pull. Tried using a root file manager to access the log but don't see.
Greatly appreciate your help, let me know what other info I should paste.
Thanks,