Database Users

Problems :-( Un mounted SDCARD

I´m pretty new into Android stuff
But I have a HTC Magic 32 B Vodafonebranded
Everything turned out fine,
rooted and played with it using different Rom's
Using Amon's 1.2.1G Recovery img
Something went wrong, dont know when.
At the moment I´m in this state:
No installed ROM up and running.
FASTBOOT
Able to Start it in Fastboot (Back+Power)
From here it is NOT possible to
use Fastboot to load Recovery IMG from PC.
(Get black screen trying to fastboot a recovery.img)
Possible to use flash-command
but i get "signature-check fail" when trying to flash images.
RECOVERY-Mode (Home+Power)
Able to start in Recovery-mode
but I can not use options in menu
due to SDCard is not mounted
This SDCard problem makes it impossible to restore Backup
it is also impossible to use Option Update from menu
cause it checks for SDCard.
Can anyone help me get my Phone up and running again ?
Could it be possible to upload system.img+boot.img ..
to other location in phone and use adb Flashing
to restore those img´s ?
thx in advance
rgds Eurocrypt

Retarded question I know but, have you pulled your battey? Then try to get into recovery on reboot?

Yes for sure,
the battery has been in and out lots of times
during my struggling.
I can boot directly into recovery,
but no access to SDCard from there.

what recovery do you run? if you have 1 click root w/ cyan 1.4 there is no way to mount sd from recovery.
If that is the case do you have a sd adapter? if so place a ROM to the root of your Sd you should be able to flash in recovery from there.

I have RAv 1.2.1G as Recovery img
Problem is Unmounted SDCard,
trying menus to Update or Restore Backup
gives me error msg's
"Cant find E:..... (SDCard)
If I only could get my SDCard mounted, I probably can
Update with a new Rom or restore a Backup.

So you cant mount SD from RA from recovery?

In sd adapter ferormat card.

Card is running perfectly well in my Girlfriends Magic
Also tried another Card in my Magic, but No Go :-(

post your phone stats

SAPPHIRE PVT 32B ENG S-ON G
HBOOT-1.33.2004 (SAPP10000)
CPLD-10
RADIO-2.22.19.26I
Apr 9 2009,23:29:17
When I Loaded HBOOT-1.33.2004 into it,
I think it was ENG S-OFF G
but not 100% sure

Eurocrypt said:
I have RAv 1.2.1G as Recovery img
Problem is Unmounted SDCard,
trying menus to Update or Restore Backup
gives me error msg's
"Cant find E:..... (SDCard)
If I only could get my SDCard mounted, I probably can
Update with a new Rom or restore a Backup.
Click to expand...
Click to collapse
This is a really dumb question but..... is it your comp or phone telling you that error. I have never seen my phone refer to my SD as the E drive.
Sorry is all the small questions a bothering you. Its a little more difficult for me to diagnoise problems online, if I can physically see the phone thing go alot fast.

The error was from Phone in Recovery mode
trying to Restore from menu.
I finally succeeded in flashing old Backup img´s
using
adb flash_image ..bla.bla.bla
And now for sure, Phone is Bricked, dead, completely Black
will send it to Vodafone service-center and keep my thumbs crossed
hoping they will return a new or at least a working one.
Thank You very much for spending your time trying to help me.

Fastboot> Recovery dosen't find *.img file on SD card

Hi Guys!
I am trying to root my nexus, unlocked it, installed the right usb drivers, I can see the phone and everything looks right.
Downloaded Superboot for ERE27 with himem enabled and ran this. no problem.
I put the img file on the SD card and when I boot the phone in Fastboot / Recovery it does not find and img files on the SD card.
I tried 2 different cards and also different img files.
When I do this I get first the message no images found than I see the droid with a triangle and a ! in it. - Have to pull the battery.
Ideas anyone?
Thanks

What are you trying to do?
1) you had to unlock the bootloader which enables you to install a new recovery image (which is needed to allow you to install new roms)
2) you had to apply the recovery image Amon RA via a command prompt and a batch file if you use Windows. The phone's USB connection needs to be in development mode and once the batch file executes and successfully finishes you need to reboot the phone.
3) you restart the phone into bootloader mode, use the volume rocker to select the recovery console. If you end up with an andriod and exclamation symbol the Amon RA recovery file was not installed.
4) the new recovery console allows you to clean the SD card. Install roms from the SD card and some other commands. The Roms for the Andriod are in ZIP format and do not need to be unziped. In other words all you need to copy to the SD card is the full ZIP file (approx 75MB) and install that directly from the recovery console.
If your android stays in the booting sequence which is shown as the X with flying little pixels, it's most likely because you did not wipe the device clean first. That item is in the recovery console as well.
Hope this helps. I am just as new to this as you are.

You didn't unzip them did you?

You're trying to root with superboot. Great, but the recovery is not capable of flashing .img files, only .zip updates and roms and such. .img files have to be flashed using fastboot, not recovery, and are flashed from the connected computer.
If you read the superboot instructions from wherever you got the file, you'll see that you have to put the .img in the same directory ON YOUR COMPUTER as fastboot, connect via USB, boot the phone into fastboot, then enter the appropriate command line on the computer to flash the file.
If you've done that, then you are officially DONE with the rooting process.
Also, make damn sure that the superboot version matches the software version on your phone. They're both ERE27, right?
I'm not sure what anosis's post is talking about, but that looks more like the process for installing a custom rom (ie cyanogenmod), than rooting.
To root your phone, you DO NOT need Amon-RA's recovery. You only need that if you want to install custom roms, etc. It wont hurt to have it, as it includes many more functions than the stock recovery, but just to root, you don't need it.
Summary:
If you flashed the superboot.img from your computer via fastboot, your phone is rooted. Done.
You don't need to do anything in the recovery at all for rooting. Only for installing update.zips and custom rom.zips.

Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.

Daboxk said:
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Click to expand...
Click to collapse
It looks like the time when you were locking-unlocking the bootloader, you messed up the recovery. Since your phone can get into bootloader menu, I think you can get out of this issue.
Here is what I would do.
1. Unlock the bootloader.
2. flash clockworkmod recovery using fastboot USB.
3. Download recovery-RA-passion-v2.2.1.img, put it in C:\fastboot\
4. Shut down your phone. Then start your Nexus One in Fastboot mode by holding down the Trackball and press the Power button.
5. Connect your phone to your computer. Open a Command Prompt (Start -> All Programs -> Accessories -> Command Prompt), and run the following commands:
cd C:\fastboot
fastboot devices
fastboot flash recovery recovery-RA-passion-v2.2.1.img
now see if you can get into recovery. If you can, just flash a custom rom using install zip from sd card option in the recovery

I didn't read all the replies but fastboot reads from your PC's disk not the sdcard, unless you are running it through shell or something?

[solved] Force install of hercimg.zip

This is my first time messing with the hero, I created a gold card and tried to install the hercimg.zip through hboot. But I am not sure everything installed sucessfully.
I got hboot1.47 and my radio got updated to 2.42.00.03.10
but when I go to flash an recovery image by using
fastboot flash recovery recovery.img
it fails.
I also can't run adb remount
So I am guessing I didn't get root access when installing the RUU.
So is there anyway to force hercimg.zip to get extract and run again?
Everytime I load up hboot now I get the following menu
[vol up] fastboot
[back] simlock
[home recovery
the hercimg will unzip and it will check but it just returns to the menu.
a message flashes right before it goes back to the menu but I am unable to read what it says.
is there anything I can do? I tried searching but I haven't been able to find anything that might work.
As side note my phone still works and it is still on 1.5.

d-shade said:
This is my first time messing with the hero, I created a gold card and tried to install the hercimg.zip through hboot. But I am not sure everything installed sucessfully.
I got hboot1.47 and my radio got updated to 2.42.00.03.10
but when I go to flash an recovery image by using
fastboot flash recovery recovery.img
it fails.
I also can't run adb remount
So I am guessing I didn't get root access when installing the RUU.
So is there anyway to force hercimg.zip to get extract and run again?
Everytime I load up hboot now I get the following menu
[vol up] fastboot
[back] simlock
[home recovery
the hercimg will unzip and it will check but it just returns to the menu.
a message flashes right before it goes back to the menu but I am unable to read what it says.
is there anything I can do? I tried searching but I haven't been able to find anything that might work.
As side note my phone still works and it is still on 1.5.
Click to expand...
Click to collapse
What are you trying to do?

I am trying to root my phone using the leaked sprint ruu the one that came out back in march/april
I have an Alaska DigiTel phone so I couldn't root it using the normal methods
so I was trying to follow the Rooting ALL Non-Sprint CDMA Heros Stuck On 1.5 From Sprint's 2.1 RUU tutorial.
But now I seem to be stuck, my radio and hboot seems to have gotten updated but it looks like everything else didn't as I am still running 1.5 and don't have root access.

I got it to work, after my battery fell out when the white/green htc logo was on my screen and when I went back into hboot it installed fine.
I didn't do anything else other then retrying the things I have been doing.
Format sdcard, recreate gold card. loading hboot
it just worked magically after the batter came out when the phone was booting up.

Evo reboots after updating NVRAM

Hello,
I am on a long journey, trying to flash my EOV to Metro ... a long story for later
Anyway, I ran across a post where someone said to write to the NVRAM from WhiteRabbit's generator: whiterabbit.org/android/
The file uploaded successfully (4 items were changed), but when I tried to reboot the EVO, it vibrates and comes up with the HTC EVO 4G logo, goes blank, and reboots
I have tried re flashing the rom, but it did not help.
I have access to the (power + vol down) menu and all i can do is reflash from the SD card, if I go to recovery, it reboots.
Does anyone have any ideas?
I made backups of my original NVRAM.
The backups were created with CDMA Workshop 2.7. How can I convert these to an image?

I am in the exact same situation. HBOOT is the only thing that loads and fastboot is the only command that works. I have HBOOT 0.93.00.0 installed from the 3.26.651.6 RUU.
The Rom Update Ultility (RUU) uses adb or fastboot commands (if adb is unavailable). After learning the commands the RUU uses I am able to duplicate what it does using a batch file (a script of all the fastboot commands in a text file named *.bat).
I cannot enable debugging (it always reboots/loops after white "HTC EVO 4G" splash screen and ADB will not work. I see no way of entering diagnostic mode (so I can't use QPST).
Recovery does not work. It loads and verifies any PC36IMG.zip file on the SDCARD but never asks do you want to update.
Attempting various other commands with fastboot always results in a Signature Verification Failure of some kind. I've been reading forums, guides, etc. all over but few start of with these limitations when trying to root or flash.
This is all I know so far. Hopefully someone else can add more insight if not a solution.

" x " appears on the screen

Malfunction " x " appears on the screen !! help me what is going on

Haha... you'll need more information than that if you want real help.
Based on the limited information though I suspect your phone is stuck in a bootloop. I'd hook it up to the PC via USB and check the logcat. Probably something screwed up.. Maybe time to restore your latest backup.

Did you flash any ROM if so, did you clean your Dalvic+REgular Cache

If you don't have an Recovery:
- Connect your Micro SD on PC
- Download and insert on SD the stock ROM of your Nexus One
- Power ON your Nexus with Volume Down Pressed.
- Autmotically Restore Nexus (You should say Yes xD)
At this time, you decide if you want to be root and install other ROM

you better just list your setup info before doing anything
locked/unlocked bootloader
rooted/unrooted
which recovery are you using
what rom are you running stock/custom
what were you doing when this happened
a couple safe things you can do in meantime is to pull battery and reinsert and power on
if it goes back to X, pull battery and DO NOT power on. Hold down the pwr button and trackball at same time and see if you can get into recovery
the third is hold down trackball/vol-/power at same time while X is on screen and see if you can get to recovery that way
if you can't get to recovery you will need to fastboot new recovery, assuming you are unlocked
once you get into recovery do a nandroid if you are rooted
and copy it to pc as a secondary backup
it is possible you may need to try the passimg method in wiki
http://forum.xda-developers.com/wiki/Nexus_One/Guides_&_Tutorials#Unroot_.2F_Restore_your_Nexus
also to do fastboot commands you need usb debugging selected on phone--hope it is

Hello, i have a similar problem with my n1
the phone starts and just shows the nexus X - (waited for 15 min. nothing happend)
i can go to the bootloader / fastboot menu with PWR + (Vol-) but i can not go to the recovery mode. -> the phone reboots and get stuck at the X
the phone is rooted
blackrose / hboot 7.35.5017
radio 5.12.00.08
recovery was ext4
i had a german ics miui rom installed and tryed to install the latest ics miui us rom after it didn't booted the miui us rom i turned the phone off and tryed a few hours later to turn it on to reflash the german ics miui rom.
1.)
i tryed to install a new recovery image ->
recovery-clockwork-5.0.2.0-passion &
recovery-RA-passion-v2.2.1
(still get stuck at the X if i try to go to recovery mode)
2.)
i tryed this one with the passimg.zip but nothing happens if i put in the sd card :/
(with nothing i mean the green text show that the sd card is checking for PASSDIAG.zip and PASSIMG.zip but dosn't found it)
i also tryed:
3.)
erased boot
flash boot from passimg.zip (PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_release_signed)
4.)
erased cache
erased userdata
started again with 1.)
5.)
got frustrated and erased system -.-
any ideas?

study it ,thank you
study it ,thank you

Hmm, sorry if its obvious but i have no idea what it could be or what i have to search to find the solution. Would be nice if you could give me a hint. Of course im not asking for a step by step solution. Thank you.
Send from my awesome SE K800i

not sure why you are flashing boot images
do you have a nandroid--copy your sdcard with the nandroid to pc--all of sdcard
are you flashing thru fastboot in command window
did you read my post above on getting to the fastboot screen--can you do that--the one with the 3 androids
pwr/vol-/trackball same time, may take 20-30 seconds
if you can get there, put your recovery image in your fastboot folder on pc, normally tools--assuming you have sdk installed, your phone must have usb debugging checked--I hope
open a command window and change directory to the tools folder or wherever the fastboot.exe file is. Something like:
cd/
cd/ android/android-sdk-windows/tools for me
then on same line type
fastboot devices (it should show your phone H#)
fastboot erase system
fastboot flash recovery recovery.img (or the exact name of the recovery image, checked by right clicking on the img file in your tools folder and looking under properties)
I would use amonra you listed above and check the md5 if possible
hopefully the recovery will flash
if not you can go to the wiki link i posted above and try passimg metthod from there, use correct one. don't add the .zip. Windows will had it automatically.
a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems

rugmankc said:
a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems
Click to expand...
Click to collapse
thank you very much
i already tryed everything else what you wrote but i didn't wiped 3 times... after erasing recovery partition 3 times i was able to flash a new recovery and it started.
Thanks a lot!

Glad that you got it