Related
last night i flashed an update of clockwork mod through rom manager. i then went to do a back-up of my current rom. the phone re-booted to the fastboot mode and now says no boot or recovery img. when i scroll to recovery and click it, the phone reboots right back into the bootloader. i am trying to flash a new recovery through adb but i cant get anything to connect. when i do "adb devices" in the command prompt i get the daemon started and list of devices but there are no devices listed. "fastboot devices" does nothing either. i have the android sdk loaded onto c:\ and the drivers seem to be installed correctly. when i rooted the phone i used a different pc that i dont have access to now. i also used pdanet for the drivers so i have never had the google drivers set up correctly. i type fastboot flash recovery recovery.img and it says "cannot load recovery.img" i have downloaded the recovery-clockwork3.0.0.5-crespo.img to the "tools" folder and renamed it "recovery.img"
i have tried to explain everything i have done so far but i am sure there are some steps i have missed. i read some on odin and downloaded it but i am even more lost trying to figure that out. i really need some help here and i would appreciate anything i can get
when you're in bootloader, you're supposed to use "fastboot"
you cant flash a recovery using adb.
go into bootloader mode
fastboot devices
... if your device doesn't show up, then your drivers are not properly set up.. uninstall them and look for the sticky and reinstall your drivers using those set of instructions; assure your SDK is updated to support 2.3.X
when you get your device to appear in fastboot devices.
download clockwork recovery 3.0.2.5 (3.0.2.4 is buggy) or 3.0.0.5; 3.0.2.5 is found in dev forums; rename it to recovery.img
put it in /sdk/tools/
fastboot flash recovery recovery.img
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
tohg2 said:
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
Click to expand...
Click to collapse
if your device is unable to GET into bootloader mode... that wont get you anywhere.
when you plug your phone into the computer with the USB.. does that USB sound pop up? if it doesnt.. then its bricked.
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
when i plug the usb in i dont hear a sound. the phone will only boot into "fastboot mode".
when i do fast boot devices i see "38328e03afbf00ec fastboot"
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
bootloader mode is for fastboot. you wont be using ADB to recover your device.
you unzip the file. it should be like: clockwork-recovery-version..blah blah blah.img
rename it to "recovery.img" assure that your "fastboot" appears as "fastboot.exe" and not just "fastboot." if it is "fastboot" you need to go into folder options and show extensions otherwise you'll be trying to flash "recovery.img.img" and SDK wont recognize it
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
Make sure you are typing the full file path, for example on my setup its "fastboot flash recovery c:\android\tools\recovery.img"
Sent from my Nexus S using XDA App
file extensions are being shown and it is named recovery.img. still saying cannot load "recovery.img" i have tried several recovery downloads from different sources. as for file size of the img its 3,988kb sound right? i tried fastboot oem lock and unlock and everything worked fine. is there another recovery img i can try. maybe a stock recovery or somehting?
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
tohg2 said:
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
Click to expand...
Click to collapse
cd C:\program files (x86)\android-sdk\tools\
fastboot flash recovery recovery.img
is what you want to do.
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
tohg2 said:
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
Click to expand...
Click to collapse
Odin is last resort. If fastboot devices shows your phone you will be able to flash recovery. Reinstall phone drivers and get fastboot to work. Then get back to trying to flash recovery. I really think it is some small mistake. Did you exctract the zip of recovery and copy the .img file?
The error you were getting means the appropriate file was not found in the file path you specified, so its not a phone error.
Sent from my Nexus S using XDA App
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
tohg2 said:
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
Click to expand...
Click to collapse
Cool! Glad you got it, good job!
Sent from my Nexus S using XDA App
Please help, I'm having the exact the same problem
I know, I shouldn't have play around with my phone since I don't know much about rooting the device.
My phone booted into Andriod logo with an unlocked, I have successful downloaded
clockwork recovery 3.0.2.5 and rename it to recover.img
I ran following command
fastboot flash recovery recovery.img and it was successful..
I tired to reboot my phone after that as normal but I'm still getting the same screen which only showing the Android Logo with an unlocked lock.
I'm not sure what I am suppose to do after need to get my phone to work again, any help would be appreciated.
Thank you,
I`m trying to flash new recovery,but i can`t write in sdk tool command line=(
I have to type fastboot flash recovery recovery.img but I can`t(offcourse I start my device in fastboot protocol)
where to write and in which folder I have to put `recovery.img`
sorry for my noob question
I found anything what I want, but now it says that device not found
Put the recovery image in the same folder as fastboot
Sent from my Nexus S using XDA App
but
were is mine fastboot?
I have to flash only recovery
upd
I found anything what I want, but now it says that device not found
Fastboot is either in the tools folder. Go read the quides on how to use fastboot/adb root restore etc. You clearly are currently over your head. All the info is here on the forums the stickies.
ok
but what about error : devices not found ?
I`ve tryed to change usb ports,re-installing drivers what to do?
TechnoManiac97 said:
ok
but what about error : devices not found ?
I`ve tryed to change usb ports,re-installing drivers what to do?
Click to expand...
Click to collapse
Make sure that usb debugging is checked off in settings.
You have two threads and you're just confusing your self.
First you can't flash recovery with just adb without root.
In order to flash a recover you need to use fastboot. The device itself needs to be in fastboot mode/protocol or whatever it is called. It also needs to be unlocked which yours is not.
So forget adb for now. Get the device to show up with the command fastboot devices. Then unlock ( will wipe everything) . Device will reboot. Put it back in fastboot and flash recovery.
My xoom is rooted
I tried using revolutionary to root the phone and its worked for my phone and about 4 others ive done. but this peticular phone i came across it will read it, give me a code but tell me that i inputted the.wrong code and close. i did this a few times same.result. so i went to htc.com and unlocked the bootloader and i when i try to install the custom recovery the rough the bootllader it tells me.the phone is not recognized after it picks up the file and opens it. what the #$%$# is going on? lol
Chances are you've made a typo somewhere with Revo, and with unlocking via HTC you have to manually flash CWM to be able to flash a ROM
i tried like ten times and it keeps telling me key is incorrect.
i feel doing it manuelly is the only way to go. since the bootloader is unlocked i downloaded the recovery and saved it to the root. i turned on the phone to the bootllader, it reads it, and it says device not recognized. is their a .img file i can use instead? and what are the adb commands so i can flash it that way?
There are threads covering adb on here, and just Googling it will give you what you want to know as well.
What version of Revolution are you using? Could be an older one which has a different beta key than the current v0.4
adb way is manually
make sure you have sdk and adb/fastboot set up in your environment, its lot faster that way
once you have that, put the phone in fastboot
and type
fastboot flash recovery (drag the recovery.img in command window) and press enter and it will flash new recovery
HHHHHHHHEEEEEECCCCCKKK YYYYEEEESSSS!!!!
Thanks bro!!!!
I put the reocevery into c:/android
Ran cmd
fastboot flash recovery recovery.img
perfect
thx again!!!
Welcome and happy Rom flashing
[email protected] said:
i tried like ten times and it keeps telling me key is incorrect.
i feel doing it manuelly is the only way to go. since the bootloader is unlocked i downloaded the recovery and saved it to the root. i turned on the phone to the bootllader, it reads it, and it says device not recognized. is their a .img file i can use instead? and what are the adb commands so i can flash it that way?
Click to expand...
Click to collapse
Copy/paste the key to notepad then copy/paste from notepad to revolutionary then it will work.
Tried various possible solutions and still can't get past the Google logo. Installed adb and Samsung driver but when executing commands such as "abd remount" or "adb push file.zip \sdcard\" in cmd I get an error saying "device not found".
Does anyone know how I could resolve this issue?
I tried clearing the cache and wiping the data from the phone, and even heating the phone with a hair dryer. I'd very much appreciate any help.
looks like you still be able to get in reovery ? if so , then nothing you should worry , just flash a new ROM
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
nodstuff said:
Do you mean like a boot image or a recovery image?
If so then you need to put phone in fastboot mode, hold volume up and power til it comes up on screen, then on command prompt on your computer type in fastboot flash recovery xxxxxxx.img (xxxxx is the name of the file like cwm5.0.2.0.img or whatever)
That should give you a working recovery to flash roms from.
Is your boot loader unlocked?
If you wanna mount then just go to mounts and storage and mount USB storage and it will show up on your computer!
Click to expand...
Click to collapse
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
leeroy88 said:
Thanks for your reply, seems to be hanging on waiting for device. Fastboot appears to be locked and it just hangs on "waiting for device" when I enter the command fastboot oem unlock... Not sure where to go from here.
Click to expand...
Click to collapse
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
leeroy88 said:
It was a recovery image file by the way. Tried fastboot flash recovery xxxxx.img like you had said but same problem...
Click to expand...
Click to collapse
Hmmm try going to cmd prompt and typing in adb devices, if you get nothing then your adb isn't set up properly and you need to go into setting and change the path on your computer.
I know the details are sketchy but gimme a min and I will find you a link
---------- Post added at 03:05 AM ---------- Previous post was at 03:00 AM ----------
http://forum.xda-developers.com/showthread.php?t=1161776
Find the Android sdk folder in your computer, move it to the root of C.
I don't think adb is where this guide says it is, there is a read me in the folder where it was saying it has moved to the platform tools folder.
So anyway find the path to the file and put it where the guide says and you should be on the ball.
Forget adb. You need to use fastboot.
Open a command prompt in the directory with fastboot or cd into it.
Put phone in fastboot mode.
On the command prompt type fastboot devices.
You will see your serial number. If you don't recheck and make sure you did everything. Sdk PDA drivers if need be etc.
Fastboot flash recovery custom recovery img name.img
Boot into recovery
Mounts and storage.
Mount SD card
Put a rom for you device on there.
Unmount
Wipe everything but sdcard from recovery.
Flash the rom by going to install zip from SD card......
Okay still stuck trying to connect to my phone. I haven't been able to get my serial number show when typing fastboot devices in cmd. adb is set up and seems to be working but the list of devices is blank when I type in adb devices. The phone was put into fastboot mode both times. I get <waiting for device> when I try
fastboot flash recovery clockwork-5.0.2-crespo.img
I think the bootloader may be locked as it does say LOCKED under lock state, which is probably the reason why I can't get the recovery image to work. I couldn't install PDANet as it wanted to connect to my phone while in debugging mode at the end of the installation. Would it be possible that fastboot oem unlock won't work with without having PDANet installed? I'd really appreciate any further help on this topic.
You need the drivers.
albundy2010 said:
You need the drivers.
Click to expand...
Click to collapse
I have the Google USB driver package installed from SDK Manager. I had tried to install some other Samsung driver found on another post but it wouldn't install.
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
leeroy88 said:
Turns out drivers weren't fully installed, managed to get PDANet installed and could connect to the phone with fastboot devices. Serial number was displayed in cmd. Only problems lies with unlocking the bootloader. fastboot oem unlock fails giving an error: too many links. Anyone have a solution to this?
Click to expand...
Click to collapse
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
ismailham said:
Did you try booting into bootloader in the first place? Volume up+Power
Then you can use fastboot. Forget PDAnet. Just install SDK and ADB
Use this:
http://forum.xda-developers.com/showthread.php?t=1007782
Click to expand...
Click to collapse
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
leeroy88 said:
Yeah I was in bootloader at the time, but I noticed that the Lock-State said locked. So I figured I must first use fastboot oem unlock. If I was to try flash with a stock recovery image would I still need to unlock the bootloader? Like I said I was able to use fastboot devices and get my phones serial number to show up, so I think SDK and ADB is properly installed, path set correctly etc.
Click to expand...
Click to collapse
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
nodstuff said:
I don't think you need to unlock the boot loader to flash a recovery image.
I may be wrong but I remember someone saying that once. I had mine unlocked before I had the chance to try it out. What happens when you type in fastboot oem unlock?
Click to expand...
Click to collapse
After typing fastboot oem unlock I get three dots ...
Pretty much straight away it fails and says something about "too many links".
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
kvaju said:
Did you do all the steps from here http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ ?
Click to expand...
Click to collapse
Thanks for your reply, I followed the steps just now and got the exact same error. Before I was trying fastboot oem unlock while in platform-tools but this time I had downloaded the nexussrootICS.zip file, and extracted it to the root of C. I tried fastboot devices and my serial shows up and after fastboot oem unlock I get "status read failed: too many links."
The only difference I seem to have is that in my device manager I have Android Device > ADB Interface, as opposed to SAMSUNG Android Device > ADB Interface.
Not a big difference but that's all I can think of.
the same issue for me. is there any working solution for that?
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
GnubbyaBush said:
I recently had success in recovering from this issue.
Here is the link, read the last comment
http://forum.xda-developers.com/showthread.php?t=1894147
Click to expand...
Click to collapse
Thanks! I'll try to do this fancy dancing
i just got my one x today, unlocked bootloader, rooted, i followed the intructions at onexroot and was sucsessful, i dont know exactly what recovery it is, its file is called openrecovery-twrp-2.1.7-evita.img, anyways flashed sucsesfully and everything then i went to install a button mod, i cant find where i got it, anyways it said sucsessful, but when it booted it hangs at the one x screen, i was an idiot and failed to make a bake up, i clicked factory reset in recovery hoping to remove the bad file, no good, i downloaded a custom rom, but i cant put it on the sd because it wont mount, i get
* verifying filesystems...
* verifying partition sizes...
E:unable to mount /sdcard
E:unable to open ums lunfile: (no such file or directory)
please help im freaking out, what can i do to fix it
First turn off ur mobile ( hold down power button until it turns off)..then hold down power and volume down together... is it getting into the bootloader??
since u rooted and installed a custom recovery u must have used 'fastboot.exe' somewhere....did u ???
i have fast boot exe on my computer, im new to this but i dont think i can get it into adb shell, i tried, maybe did it wrong, sd wont mount and no backup like an idiot, and yes i can get into bootlaoder and recovery, thank you so much for quick response
after some fiddleing i can get it into fastboot and it makes the detected sound on the computer but adb still doesnt recogized it, it says no device found
There wil be no adb in fastboot....and i guess it is better to download a RUU(ROM upgrade utility)... its just a exe file...I guess downloading it and running it wil flash the stock ROM in ur phone and there wil be no problem i guess...
ive installed htc sync and am downloading the ruu, if its a earlier version does that matter? im not sure but i think it was at 1.85, or 1.75, the one i found is 1.73, and once downloaded what do i do, total noob, sorry, thanks again
I guess the RUU must be of same version.... Its better if u find the exact version..i am also a noob..so not sure about different version.. btw where did u search for RUU??
http://forum.xda-developers.com/wik...ashing_a_RUU_to_completely_restore_your_phone
http://forum.xda-developers.com/showthread.php?t=1543604
i typed the first command and its stuck at waiting for device???
Yo man dont freak out youre Phone is perfectly fine here take a detailed look at this link http://forum.xda-developers.com/wiki/HTC_One_X
And after that if you still can`t do anything go to youre specificc htc one x thread from the forum and post there those guys will help you faster and fail proof
I had a desire z and i remember that first you must boot the phone in download mode and then the ruu will find it anyway i wish you luck
it wont go into download mode
by first command which command do u denote?? and wat do u mean by download mode??
"fastboot getvar version-main"
somewhere in the myriad of xda threads ive read it said ruu required you to be in download mode, interstingly enough fast boot works on my mac partition, but not my windows, possibly an issue with windows 8 but idk
Possibly HBOOT driver issue oly....phone is in 'usb fastboot' oly right??? and does 'fastboot devices' list ur device??
it goes into fastboot usb, if i click bootloader it says hboot, but when i do adb it says device not found, i dont know where fastboot devices is listed
Phone should be displaying 'fastboot usb'.... Then oly fastboot.exe wil work.....and adb wont work both in 'fastboot usb' and 'hboot'....when in 'fastboot usb' ...in computer type the command 'fastboot devices'....does it list the devices??
it lists a serial number
note that all the drivers and files i have come from htc sync or onexroot.coms bootloader unlock and root pages
then fastboot mode is working fine...what recovery,kernel and ROM are u in...sometimes the problem u stated might occur due to kernel and ROM mismatch...For recovery i would recomend you to install ClockworkMod Recovery....
could you point me to one that works, ive tried 2 supposed cwm recovieries and they both hung at at the legal disclaimer, twrp is the only one that loads
may i know how r u installing the cwm recoveries??? and were u able to run "fastboot getvar version-main" ??