adb shows my device is offline. I reinstalled the drivers and updated the sdk.
The only way my cpu will detect it is if it in recovery, It wont detect at fastboot or hboot. Im stuck at the green htc screen. My device wont boot up. Im trying to push system.img.
can any1 help
Do you have debug enabled in settings > applications?
Sent from my T-Mobile G2 using Tapatalk
as long as you can see it in recovery you can push system.img, but if you are looking to flash it you need to use the fastboot binary(sorry no link) and use fastboot flash system system.img
@g_grey
I understand what you are trying to say. But his phone is listed as offline in recovery mode. How would he go about on getting adb to recognize his phone. It would his phone id but after that it would say offline. And where do you find these binaries?
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
binaries are found with google(pretty sure it's somewhere in with the other android dev stuff), then just put the binary with your adb binary(sdk/tools) and if it is being seen as offline then the recovery he is using doesn't support adb in which case not really sure.
@OP
if you have clockwork installed i believe there is an option to mount sdcard as you would from the os, then it should appear as a drive on your comp and you can copy files over.
why are you trying to push system.img? what end result are you aiming for?
Thanks I found it right after I posted. His problem is he's stuck at htc screen and s-on so might push system.img and/or userdata.img. can't do anything else. Tried to flash PC10img but says older version yadda yadda. Any suggestions.
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
use the recover from semi brick thread then, didn't know he was with s-on at this point(doh!)
@g_grey
That's what I say. Just downloaded the fastboot binary and hopefully we get some progress
Phone: T-Mobile G2/Vision Rooted
Rom: Latest Cyanogen
Recovery: CWM waiting for Amon_RA
Same problem
did you come up with a solution? I can get into recovery mode. tried appling and update.zip for both the original and latest version. I have tried factory reset. I can get the serial number with adb devices but it says offline. I had found a solution where I could put the PC10IMG.zip but it says its an older version. but I found via 14344-how-to-fix-a-bricked-g2-or-root-new-g2s-with-kernel-fix pm cyanogenmod that I could push a new misc.img which would get ride of that error message. but I have to be able to use the adb push and/or adb shell.
Related
I've been reading up about what to do after I tried to "factory reset" my phone and then was stuck at the htc start up soon, which kept looping.
I've been trying to load recovery.img during fastboot (back+power) and then to apply update.zip during recovery (home+power).
However, the problem is that during fastboot, the device isn't recognized (when I go to adb devices on command prompt, no device is listed). I know that my drivers are good bc the device is found when I start up in the recovery mode. I tried to skip the part where I load recovery.img (since when I try to do that, it tells me that it can't be loaded), and to go straight to apply update.zip, but then the phone tells me that update.zip is either bad or can't be mounted.
I have a Rogers Magic (32A). I am a complete newbie, so any help would be greatly appreciated. I should also say that before I tried to do the factor reset, the phone was on the hero rom loaded by a previous user.
try this:
boot in recovery:
fastboot boot recovery.img
then, push update.zip on your sd card ( need a good rom in the tools folder on your computer)
adb shell mount /sdcard
adb push update.zip /sdcard
and apply update.zip with the recovery menu.
thanks for your reply, but it didn't work:
first, it said "cannot load recovery.img"
and then when I tried to mount, it said "mount: mounting dev/block/mmcblk0p1 on /sdcard failed: Device or resource busy"
replace recovery to correct path to your recovery image. (your phone mut be in fastboot mode power with back button pressed)
ex:
fastboot boot c:\sdk\tools\recovery-RAv1.2.1G.img
then your phone must boot on recovery and you could push update.zip
thanks so much. I figued it out - just a simple problem of the update.zip file being corrupt.
pato17 said:
thanks so much. I figued it out - just a simple problem of the update.zip file being corrupt.
Click to expand...
Click to collapse
i am having the same issues.
any help?
beastmods said:
i am having the same issues.
any help?
Click to expand...
Click to collapse
What exactly have you tried to do?
Sent from my HTC Magic using XDA App
Hi. My magic is having the same issues. Although I believe it is my own doing. I was going to create a gold card and I flashed the sappimg.zip, I can boot the phone into fastboot but it us not seen, when I run the fast boot command it just says waiting on device..
I can boot the phone up normally but it does not want to connect to the market our link my gmail account to it..
All to jailbreak... Any ideas?
Edit....
I must have had a poor internet connection last night. I have got the market working.
Sent from my GT-I9000 using Tapatalk
I am having the same problem.
I have a 32b on vodafone uk.
all the device adb drivers have installed fine. I have tried this on both my laptop and desktop (win 7) and when the phone is turned on - it shows fine under adb devices.
When i boot to fastboot, the phone doesnt show, and therefore i cannot load a custom rom.
Trying to root the phone I have so far used the goldcard method to downgrade to get back to 1.5, if i try to flash the recovery img from the phone (using flash rec) then when i boot to recovery (home+power) it hangs on the vodafone screen - this is why i wont to flash from fastboot.
any ideas?
Thanks
phone rooted?
FlashRec is out of date, I'm pretty sure. Is your phone rooted already, or are you at stock?
I flashed with the latest cyanogen on a 32A in CM's recovery image, i had the patch for the kernel (take it from 32B to 32A) but i didnt get to apply it yet.
when i rebooted my phone it hangs on the Rogers screen, i can get to fastboot and recovery mode (stock recovery mode). I made a nandroid backup (before the flash) but i cant get to it from the recovery mode menu, and when i connect the fastboot usb, my sd card doesnt show up on my computer. so i cant run the fastboot command to load the recovery image...
is there anything i can do?
some more information:
when i go into recovery mode, the "removable disk" shows up in my computer, but clicking on it just says "please insert a disc into drive..." which leads me to believe it is not mounted, any way to do this from recovery?
It'll never boot when you haven't installed the 32A patch.
And that means that you'll never be able to mount the SD card to have it show up in Windows. You can use adb to push the update.zip file to your SD card while in Recovery mode.
(You'll need the Android SDK installed for this)
Start up your phone in Recovery mode using the Power+Home buttons.
Once in recovery, wait for Windows to detect the phone (about 30 seconds).
Copy the 32A patch to your Android SDK tools folder, then run:
Code:
adb push <filename for your 32A patch>.zip /sdcard/update.zip
This will push your 32A patch to your SD card as update.zip.
Then apply update.zip through your Recovery environment.
A note to you... Before running the adb push, try running:
Code:
adb shell
mount /sdcard
exit
adb push <filename for your 32A patch>.zip /sdcard/update.zip
This will make sure that your SD card is properly mounted before copying the file to it.
To check that the file is there before trying to update, run this from your Command Prompt.
Code:
adb shell
cd /sdcard
ls | grep update.zip
You should see update.zip listed there.
After you've applied the 32A patch zip file through your Recovery environment, reboot your phone.
Should work now...
If you haven't installed the Amon_RA Recovery yet, it would be a good idea. It lets you save and update zip file to the root of your SD card without renaming it to update.zip first. You can apply any update zip file as an update.
thanks for the reply,
when i type adb shell i get:
"error: device not found"
typing adb devices also yields that the device is not listed
but windows does make the noise notifying that a device is connected, and the Removable disc still comes up in my computer
when i go into Device Manager, under disc drives it shows up as
HTC Android Phone Usb Device when the phone is in recovery
and if this makes any difference, press home+power again and look at the options in recovery the bottom says "E:Can't open /cache/recovery/command"
it worked in fastboot/recovery before, but that was when i had USB debugging selected and before i flashed CM i wiped. could this be the reason why im not able to access the phone with adb in recovery/fastboot?
for some reason i was able to fastboot into cm's recovery image and then the device was listed in adb, i followed your instructions and applied the patch, the phone booted up!
thank you!!!!! phew, that was a close one
zeotrope said:
for some reason i was able to fastboot into cm's recovery image and then the device was listed in adb, i followed your instructions and applied the patch, the phone booted up!
thank you!!!!! phew, that was a close one
Click to expand...
Click to collapse
The CM recovery works great but without a hardware keyboard it's not entirely functional.
I'd recommend flashing Amon_Ra recovery and using that. Read the directions carefully though. Make sure you use the right one for your phone.
got amon-ra's recovery permanently flashed on there, thanks again for your help
Hello all,
I have been using the super one click method to root my HTC Magic Saphhire 32A.
It works well so far albeit need to alter some SU files in the program. Running of terminal emulator with the command prompt SU confirmed that I have the superuser rights.
Now the problem is whenever I use ROM manager to reboot in recovery, the phone restart, HTC logo shows, then the next screen I see is a big asterisk and a phone image, after this I pressed Home + power, the screen manage to switch to Android system recovery utility, BUT with only 3 options:
1) Reboot system now
2) Apply sdcard:update.zip
3) Wipe data/factory reset
And in the end of the screen, there is one line highlighted in red: E: can’t open /cache/recovery/command
After the phone been rebooted, I switched off the phone. And Pressed vol - with power button, same issue happen too with the asterisk sign shows on the screen. After unrooting it, the phone recovery mode are back to normal with the 3 androids in skates appear on the screen.
Have anyone face the same problem? Any ways to sort this out? I am planning to back up my stock ROM, and wanted to try out some cyanogenmod ROM. I tried Googled and read lots of forum post but left without a solution. Any helps are appreciated! Cheers!
p/s: I am a noob in Android OS. XD
I have the legend and these is a process of booting the recovery from there as update.zip. have you tried renaming the ROM update.zip and flashing it from there?
Sent from my HTC Legend using XDA App
I fiddled with the ROm manger setting by choosing "delete recovery prior to flashing", and now it makes it worse.
I selected "reboot in recovery" in ROM manager and the phone reboot, but just stuck at the HTC start up screen.
I plugged in the phone while trying another recovery reboot, and it still stuck at the HTC screen, but with a red line on the top saying "fastboot USB". Gosh I think i am going no way with this...
E:Can’t open /cache/recovery/command
Same fault here mytouch 3g unlocked at&t 32b downgraded too cupcake and tried
getting E:Can’t open /cache/recovery/command
home and power button down still cant get you in recovery? you cant flash any other working rom?
32b myTouch 3g 2.2.1
Cyanogen Nightly 271
Hboot - 1.33.0006
Radio - 2.22.19.26i
Kernel - 2.6.35.9
ADW 1.3.3
ClockworkMod Recovery
Slideit keyboard
Did you flash custom recovery with ROM manager? Or you just rooted the phone with 1 click method?
Sorry for the late reply. I am just back from overseas business trips. I used Clockmod ROM Manager and did a backup, tried reboot in recovery, and the phone rebooted itself but stuck at the HTC logo now.
I can confirm that the phone is rooted with super user permission.
The reason being the phone didn't manage to get into recovery mode might be due to the missing recovery.img in the phone. Pushing the img file to phone through Clockmod didn't work apparently, so I tried command prompt from PC fastboot flash recovery c:\recoveryxyz.img. It failed too with an error remote failed.
I tried using the terminal emulator in the phone and tried pushing the recovery image again and it didn't happen too. Can some one please help? Cheers!
Download ROM manager and you have option that says install custom recovery it will install Clockwork, and you have flash alternative recovery it installs amon ra's recovery i prefer most
Will try it tonight and revert for the result. Cheers!
I have tried flashing alternate ROM through ROM manager and for once it managed to boot into recovery mode. BUT the device hang right after that, I can't select any of the options and have to pull the battery out to force shutdown.
I tried using fastboot flash recovery *.img remotely through my PC while the phone is in fastboot USB mode, and my command prompt stated FAILED (remote: not allow)
Urgh, I think I might have missed something here... Could some one please help? Cheers!
p/s: my objective is to upgrade my stock ROM android 1.5 to cyanogen ROM. Cheers!
I don't know whether this info helps but here goes:
phone info:
sapphire pvt 32A ship s-on H
Hboot- 1.76.0007 (SAPP10000)
CPLD - 12
RADIO - 6.35.07.29
AUG 4 2009
callmeneotheone said:
I have tried flashing alternate ROM through ROM manager and for once it managed to boot into recovery mode. BUT the device hang right after that, I can't select any of the options and have to pull the battery out to force shutdown.
I tried using fastboot flash recovery *.img remotely through my PC while the phone is in fastboot USB mode, and my command prompt stated FAILED (remote: not allow)
Urgh, I think I might have missed something here... Could some one please help? Cheers!
p/s: my objective is to upgrade my stock ROM android 1.5 to cyanogen ROM. Cheers!
Click to expand...
Click to collapse
OK here is the thing did you chose right model of your phone? HTC magic is 32A and mytouch and something else is for 32B you maybe flashed the wrong one?
Thanks WoblyGoblin for taking your time to help. Yes, I have selected the correct phone model. I chose HTC Magic.
Did you install the recovery?
Sent from my HTC Magic using XDA App
I am stuck in trying to install recovery img into the phone. can't boot in recovery mode, tried ROM manager and remote push of recovery img into the phone.
Please refer to the previous post for more info. Cheers!
Ok here is the solution for you use this guide but download this apk and this recovery.
If you dont have 1.5 android but 1.6 download Terminal emulator from market and when you start it type first:
su
flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img
Hello mate,
i just tried the method and I am stuck at FlashRec backup recovery image step.
I clicked on backup recovery image, but there is a command prompt that says:" backup FAILED: Could not run command.
FYI, I am running on Android 1.5. On the edge of giving up rooting and loading a custom ROM now and without a MARKET apps on the phone.
callmeneotheone said:
Hello mate,
i just tried the method and I am stuck at FlashRec backup recovery image step.
I clicked on backup recovery image, but there is a command prompt that says:" backup FAILED: Could not run command.
FYI, I am running on Android 1.5. On the edge of giving up rooting and loading a custom ROM now and without a MARKET apps on the phone.
Click to expand...
Click to collapse
Did you try terminal emulator app?
And commands that i gave you?
yes mate, have tried flash_image recovery command from the terminal app and tries to restart in recovery without any result.
I have did a few research and read up and found out that I am stuck with the south east asia Magic model without the google based support, with no market apps and it is perfected SPL.
Quite upset by it. LOL!
callmeneotheone said:
yes mate, have tried flash_image recovery command from the terminal app and tries to restart in recovery without any result.
I have did a few research and read up and found out that I am stuck with the south east asia Magic model without the google based support, with no market apps and it is perfected SPL.
Quite upset by it. LOL!
Click to expand...
Click to collapse
Try this
It seems I bricked my Desire Z. That'll teach me for messing with custom roms
I only get the bootloader (the white screen with coloured text). Everything I do from there either does nothing or just goes to a white screen with a green HTC logo and then hangs.
I tried flashing Cyanogenmod by renaming the zip pc10img.zip, this failed. I tried installing an official G2 rom from the SD, this also failed. When I turn the thing on I get a green HTC logo, when I try to go to recovery it's the same story.
Can anyone help me get my phone back to life?
When you get in to recovery are you getting any error messages?
Have you tried restoring a nandroid backup or trying a different sd card?
And re-naming a rom to PC10IMG.zip will never work
I don't get an error message, it just hangs at the HTC logo. Same when I reboot the phone.
I don't have a backup since the last time I tried using one, it didn't work. Besides, I don't have Clockwork so I wouldn't be able to restore it even if I had one
Neko Koneko said:
I don't get an error message, it just hangs at the HTC logo. Same when I reboot the phone.
I don't have a backup since the last time I tried using one, it didn't work. Besides, I don't have Clockwork so I wouldn't be able to restore it even if I had one
Click to expand...
Click to collapse
You cant get in to clockwork. have you tried using adb?
Not yet. Is it possible to flash a rom or even just clockwork through adb?
I'm sorry for being such a n00b about this, I'm just not that experienced yet with android devices. Used to change roms on my WinMo device all the time but Android's... quite different
If you have the ENG Hboot you can flash the recovery from fastboot....
If you have the sdk set up on your computer do the command (after putting the clockwork recovery in your sdk folder):
fastboot flash recovery recovery.img
then go to the recovery, wipe and flash
I now have the issue that ADB won't see the phone. The phone says HBOOT USB PLUG so it knows it's connected through USB, it shows up in my device manager but ADB won't recognise it. Any suggestions?
adb won't work in hboot/fastboot mode, you need to get the fastboot executable.
It might be in your tools folder for adb.
You can make sure its working by running 'fastboot devices'
-Nipqer
Nipqer said:
adb won't work in hboot/fastboot mode, you need to get the fastboot executable.
It might be in your tools folder for adb.
You can make sure its working by running 'fastboot devices'
-Nipqer
Click to expand...
Click to collapse
Thanks! Fastboot detects the device Now I can try to fix stuff.
It worked! I managed to install Clockwork Recovery using Fastboot and after that installing Cyanogenmod was a piece of cake Thanks you guys!
The most important thing I learned from playing with roms is how to read the manual. Be careful out there.
Sent from my HTC Vision using XDA Premium App
Ahem, guys, where can I find fastboot executable? I checked everywhere in the android-sdk directory but I can't find it. I even updated to the latest SDK tools, and yet fastboot is still MIA.
Always and I mean ALWAYS create backups of your working roms, I cannot stress this enough.
You can copy files onto your sdcard using adb then force boot into cwm. Thank goodness for adb
Sent from Space using Tapatalk Pro
I'm putting this in General because this is my first time I've actually posted on XDA and I hope someone will move it to wherever it needs to be.
I've rooted my Nexus S a long time back when it was new, originally had some trouble with fastboot hanging on "waiting for device" I want to say trying PDANet fixed my problem then. I'm not foreign to the flashing/rooting process. And I know this is a long post but If you can please read it all it would be appreciated.
My Story:
>ICS was released and while Google said Nexus S would get an official update I saw some on XDA that were promising ports.
>I downloaded We Scream for Ice Cream Beta 9 and installed through Rom Manager
>About a month later I'm fed up with all the force closes and missing features the thread didn't inform me on and went to find another ICS Port.
>Downloaded and about to install through Rom Manager I'm informed that I need Clockwork (strange because I already have it) so within Rom Manager I flashed a new one.
>Install via SD Card and my phone reboots and then instead of loading recovery and doing its stuff I wait at the Bootloader screen. I try entering recovery myself and my phone restarts and again I'm at the bootloader screen.
>At the very bottom of the screen in gray lettering it says Fastboot FAILEDcommand
(As of now it displays the Google Logo with the unlock icon and hangs)
>At this point I decide I' going to flash over clockworkmod myself via adb. This should be the magic formula: via addictive tips (new user, can't include hyperlinks)
Code:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
>Adb gives me an error similar to won't link after the mount/remount command. Also trying to cp the flash image to bin fails to work.
>I boot my phone, open Total Commander and try to copy the flash image myself to the bin folder in my root and it fails
(As of now I get error: device not found)
Then i think alright, maybe it's my drivers. I tried several different drivers from different tutorials because perhaps they are different in some slight way. >Whenever I try a new driver I can pick "adb Composite" "bootloader" or vanilla "adb interface".
>My device appears as "Android Phone" as the first entry in the Device Manager and the icon is a monitor with a small PCB chip in the corner.
>When the divers are completely uninstalled it appears in Other Devices with a yellow exclamation point.
>My understanding is that while it will automatiaclly grab the driver for USB mode, I have to force it to install the bootloader driver for when my phone is in the bootloader screen.
>And USB Debugging has been checked for everything I've done.
>Now i try to use PDANet, first I uninstall the drivers and install PDANet. Message appears saying there is already an Android Driver installed, I choose reinstall, select Samsung, pop says are you sure you want this driver, publisher cannot be confirmed? I click yes, I beleive that happens twice, it installs and then runs. It installed the vanilla "adb interface" driver.
(This is where I'm at now, the Fastboot FAILEDcommand is also gone.)
So now I'm like well there's fastboot, let me see if it recognizes it.
>Fastboot devices: nothing appears
>fastboot flash recovery recovery.img : it hangs on waiting for device.
>Same goes for other commands like OEM unlock.
All the while ROm Manager insists I have clockwork recovery verison 5.x - only it wont load and none of my PC options are recognizing the phone. So I can't flash over a different recovery image, and there;s nothing under alternate recovery in Rom Manager.
And the strangest of them all which may be Rom Manager's problem is that Super User FCs as soon as I try running it. Rom Manager states Super User gives it power at the end of the clockwork recovery flash, however, still says it's successful.
Before this entire thing my phone tried to OTA update to 2.6.7 for Google Wallet and where it would normally respond I got the Android Guy with a box and a yellow exclamation. This is also what I got when I first had some problems rooting months back before I flashed over images and roms. I figured it wouldn't update because it needed the stock recovery image and wasn't compatible updating with clockwork mod (however i think my phone has updated before with this method.)
I wouldn't mind rolling back to my stock deodexed version of Gingerbread at this point because the ROM I have now for ICS NFC and Bluetooth wont work among a slew of problems. And NFC was the major update in 2.6.7 in regards of tap to share and Wallet.
So I either need ADB and Fastboot to recognize my device to try reflashing clockwork and an Entirely new ROM remotely (if that's possible) or get clockwork mod on my phone to open.
More Details
Also when I load the recovery image and it loops back into the bootloader I get the message up top saying I don't have a boot image or recovery image. yet my phone still boots fine.
I really want my phone to work %100 again, can anyone help me?
I didn't read all you wrote, but if you're having trouble getting adb or fastbook to work correctly just use ROM Manager. Even if it says you have it installed, do it a few times. You can also go into settings and check off the format or erase recovery option before flashing.
It will eventually work. Just keep trying it.
Thanks
I know I've read things where flashing several times gets it to work. But I'm wondering if because SuperUser force closes without opening it's unable to give RomManager the permissions needed to complete the flash.
I've tried a few times ever once in a while. Still waiting, but adb will recognize my phone on my guest login but still no fastboot.
What rom you on? Have you tried going into app manager and then clearing data for superuser? Try that and then reflash the recovery a few times from rom manager.
If you're using CM9 alpha 11 or any of the builds by Koush, and superuser FC's from fresh flash. Clear the data, use root explorer or another app that has root access (it will prompt you for root access even if superuser UI won't open) then you can go into /system/app/ and delete or rename superuser.apk.
Once that is done, get the latest one from the market. Soon as it installs, clear the old data from the previous one by using app manager again. Then your superuser app should be working normally.
What's your phone model? (I guess it's I9020T)
When you boot into bootloader, does the fastboot devices command see the device properly?
You should use fastboot to flash your recovery. You probably have driver issues. Check the rooting guide at nexusshacks.com.
Sent from my Nexus S using XDA App
Fixed
Thanks to everyone and heir suggestions.
Eventually I downloaded another set of Fastboot and ADB registered with my phone and I was able to flash a new ClockworkRecoveryMod.
My only explanation is that the two tools where in the same folder this time - that was the only part that was different.
However ROM manager will still tell me I do not have Clockwork on my phone and when it 'flashed' it over it actually breaks my recovery partition all over again.
Thank god for ADB and Fastboot.