Develop Bugs

[SOLVED]What happen if I flash ROM using the not recommended recovery?

Hi there.
As the above title says, what happen if I do so?
I do not have recovery version 2.5.1.3 in my ROM Manager anymore(I have no idea know why). Also do not have 3.0.2.5.
The only recovery I have is 2.5.1.4, 3.0.0.5, 3.0.0.6 and 3.0.2.4. Plus I am unable to flash 2.5.1.4 version(it pops up an error)

Some have no issues, but some have experienced issues when trying to restore cwm backups.
Have a look in the LeeDrOiD 2.2.3 thread a few days ago. I have posted methods to manually flash it via a tool or adb commands. I have also provided dl links as well.
Sent from my Desire HD using XDA App

Hi Upintheair
Thanks for the reply. Erm.. do you remember the exact date you post that in LeeDroid's thread? The thread is overloading. I cannot find them. =(

From Index of /cm/recoveries Download recovery-clockwork-2.5.1.3-ace.img
Try one of these 2 tools, instructions are on the threads;
1. Thread: [TOOL][All devices & OS] Fastboot Commander [v.1.1]
Download: Fastboot Commander v1.1
2. Thread: Android Flasher
Download: [UTILITY] Android Flasher(Recovery,splash1,Radio,HBOOT,bootanim)[V1.7.4]
OR
Manually through ADB:
1. Place the image in where fastboot.exe is located.
2. Connect phone to PC with Bootloader FASTBOOT USB
3. Using commands "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img", then "fastboot reboot", recovery

3. Using commands "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img", then "fastboot reboot", recovery
Click to expand...
Click to collapse
I tried many threads and find no answer to my question.
On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.
1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.
2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?
It flashed cwm perfectly. But I am not shure about flashing radios and stuff.
Thanks for the links to the Leedroid cwm version
Sent from my DHD using XDA App

kgulruh said:
I tried many threads and find no answer to my question.
On my ubuntu I installed adb and can't remember about fastboot.exe whether it was installed by default or I downloaded it. And know I lost it - deleted accidentally.
1.My ques is where can I find it I mean fastboot? I reconfigured my adb back but there is no fastboot.
2. Can I use fastboot-linux from CWM 3.0.2.8 Installer instead?
It flashed cwm perfectly. But I am not shure about flashing radios and stuff.
Thanks for the links to the Leedroid cwm version
Sent from my DHD using XDA App
Click to expand...
Click to collapse
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........
Edit: I would advise flashing through a battery only powered notebook, don't want a power surge or cut 1/2 way through a flash . Also ensure notebook & phone batteries have near full charge.
Fastboot Commander v1.1 is compatabe with Linux, there is instruction how to install the tool in the Dev's thread. It has everything you need in the zip, and no need for the adb / fastboot commands in CMD.
...............The first result Mr. Google gave me with the search string "download fastboot.exe" Choice of platforms; Windoes, Mac, Linux
Once extracted, just copy the files into your SDK folder where adb.exe is located (maybe tools or platform-tools........)
To make sure fastboot is working ok, boot phone into FASTBOOT, connect to PC & it will change to FASTBOOT USB. Open up CMD and navigate (cd\......) to the folder where adb & fastboot.exe is now located. Now type "fastboot devices", if connected & communicating correctly using Fastboot commands -> HTxxxxxxxxx, giving the device serial number.
If you want to use CMD:
Place image inside SDK folder where fastboot & adb.exe are located.
Rename it to radio.img (unless you like to type the whole name again)
CMD type: " fastboot flash radio radio.img", then
"fastboot reboot"
I am not too sure about Linux PCs, always been Windows until Android.

It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...
this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..

SERGI.3210 said:
It is strange that CWM is not available to update TO 3.0.2.6 in ROM MANAGER...
this version is compatible with leedroid. you must to have installed ROM manager ver.4.1.0.0 from the android market..
Click to expand...
Click to collapse
You'll have to post that question to the ROM Manager Koush.
If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img
OR
CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"

Thanks UpInTheAir
I'll try it later tonight. Guess I will try to manually flash them.
It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?
I just recalled I read it somewhere last time when I was learning how to flash new radio. x)

superstick1 said:
It is exactly how we flash radio using the radio flash tool but this time change the "radio" to "recovery"?? this time im suppose to use back the same tool right?
Click to expand...
Click to collapse
If you are referring to the "tool" as in the CMD (Command Prompt)?
If this is what you mean, the answer is Yes & Yes.
Most of the tools, some examples & links I've given, just save you time, not having to use the adb or fastboot commands, cd\ (navigate) to the location of adb.exe or fastboot.exe in the SDK folder etc. These tools can also do a lot more, particularly Fastboot Commander which can be run on Windows or Linux.

I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(
This is what I do
1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"
2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
and it pops up that error. =/

superstick1 said:
I just try it and it says "error: cannot load 'recovery-clockwork-2.5.1.3-ace.img" =(
This is what I do
1) Firstly when i was at the cmd window.. I type "adb reboot bootloader"
2) Then "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
and it pops up that error. =/
Click to expand...
Click to collapse
Ensure Fastboot is OFF & USB debugging ON in phone settings
When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
Did you test Fastboot communication by command "fastboot devices"?
Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Edit: I see your signature is ENG S-off?, double check in HBOOT Bootloader. If the above still doesn't work, try the Fastboot Commander Tool, maybe your making a typo somewhere........

1. Ensure Fastboot is OFF & USB debugging ON in phone settings
Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^
2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
How do I check this? =/
3. Did you test Fastboot communication by command "fastboot devices"?
Same as the above. How do I check this?
4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Yes. Checked.
5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Tried. Did not work. Same error coming out.
I try flashing other recovery such as 3.0.2.6 but still the same error.

superstick1 said:
1. Ensure Fastboot is OFF & USB debugging ON in phone settings
Erm Im not sure about this, but I thought if we want to do anything such as flashing recovery we need to have Fastboot ON? Just to double confirm first before I do anything. ^^
2. When in FASTBOOT, does it say FASTBOOT USB when phone is connected?
How do I check this? =/
3. Did you test Fastboot communication by command "fastboot devices"?
Same as the above. How do I check this?
4. Make sure the recovery image is copied to the SDK folder where fastboot.exe & adb.exe is located.
Yes. Checked.
5. Make sure the name is exact. You could also rename it to recovery.img , and the change the command to "fastboot flash recovery recovery.img" (NO "quotes")
Tried. Did not work. Same error coming out.
I try flashing other recovery such as 3.0.2.6 but still the same error.
Click to expand...
Click to collapse
1. Mine works fine with usb debugging on & fastboot off.
2. Power off phone. HOLD volume down (don't release) & press power button once. Phone will boot into HBOOT, you will see FASTBOOT. Connect to pc with usb cable. Wait a few seconds and HBOOT will change to FASTBOOT USB.
3. Use Cmd (command prompt) in Windows. Pc to navigate to the sdk tools or platform tools folder (where fastboot.exe is located). Now type "fastboot devices", if you are communicating in fastboot, you will get HTxxxxxx (device serial number), and can now proceed with "fastboot flash recovery recovery.img"
If it doesn't work, you have not setup properly, or typo, I would suggest using fastboot commander tool.
Sent from my Desire HD using XDA App

I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.
I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.
Anyway thanks a lot ya.

UpInTheAir said:
You'll have to post that question to the ROM Manager Koush.
If you require a CWM Recovery version not listed in ROM Manager, flash through the methods I posted above. Links to Index of /cm/recoveries is there as well as xxxxxxx2.5.1.3-ace.img
OR
CMD: "fastboot flash recovery recovery-clockwork-2.5.1.3-ace.img"
Click to expand...
Click to collapse
i know, and I understand you, only I say that there are CWM's versions you very validate for flash apart from the recommended ones that work perfectly, I am flashing with the current one (leedroid, coredroid, hd rev ..) and it me works to the perfection and the nandroid also.
Certainly .... which is the meaning of "koush"???

superstick1 said:
I got my device number of HT0CCRX00128. Guess I've followed the steps you gave me correctly. Lol. But still the same results, error in flashing the recovery.
I will try that fastboot commander tool later tomorrow. It's getting late here and have to wake up early for work. Plus I havent read that thread properly yet. Lol.
Anyway thanks a lot ya.
Click to expand...
Click to collapse
Here are two zip files: Recovery 3.0.2.8 & 2.5.1.3.
3.0.2.8 doesn't show in ROM Manager, but version shows when boot into CWM Recovery, so no worries.
Reference Thread: [RELEASE][25/04/2011] ClockworkMod Recovery 3.0.2.8
I downloaded 3.0.2.8 from the above thread, extracted replaced the 3.0.2.8 image with 2.5.1.3 image (renamed recovery.img), and zipped again to upload.
View attachment Recovery_Ace_v2.5.1.3.zip
View attachment Recovery_Ace_v3.0.2.8.zip
Installation:
1. Power off your DHD
2. Put it in bootloader mode; Power+Vol down and select Fastboot from menu.
3. Plug-in the USB cable. (FASTBOOT USB)
4. Extract xxxx.zip
5. Double click on install-recovery-windows.bat if you're using windows, execute install-recovery-linux.sh if you're on linux or install-recovery-mac.sh if MacOSX.
6. Done! The device will be automatically rebooted.
7. If the version doesn't show in ROM Manager, reboot into recovery to check version actually installed.
I tested the windows commands and worked perfect Linux should too!!
I do recommend you read up a bit yourself on adb & fastboot commands, and if you aren't able to do that, use the flashing tools provided by the various Devs, thanks to them, life is much easier.

Thanks UpInTheAir!
I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.
Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?
Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? Its getting complex. =/

UpInTheAir said:
Warning: Flashing wrong radios or incorrectly can result in a BRICK !!! Your own risk..........
Click to expand...
Click to collapse
Thanks a lot man, used the one in cwm 3.0.2.8 update tool "fastboot-linux" and it works perfectly just need to rename it for consistency.
For me typing in linux is better then knowing nothing in windows

superstick1 said:
Thanks UpInTheAir!
I actually managed to get 2.5.1.3 installed and now I can continue flashing ROMs! Lol.
Erm why wouldnt recovery version show in the ROM Manager? My ROM Manager still shows it is 3.0.0.6 but in the recovery it shows as 2.5.1.3. Thats pretty weird isnt it?
Oops. I am trying to flash ARHD now, but halfway through it "stuck" in recovery and says: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. please open ROM Manager to report the issue.
What happen here? Its getting complex. =/
Click to expand...
Click to collapse
I always boot into CWM Recovery menu to flash, and not through ROM Manager (wherever possible).
Try that way.

Mac OS X Fastboot Mode <Waiting for Device>

Hi, I am trying to Re-Lock my Galaxy Nexus GSM version, I've downloaded the SDK files (adb-mac and fastboot-mac) and all the image files and I am trying to execute the following commands:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
With the phone in normal mode I connect the USB cable to the computer, start Terminal windows and run the first command, "./adb-mac reboot bootloader" and the phone will boot into the "Fastboot Mode", then I try to execute "./fastboot-mac devices" to make sure the phone is connected and properly detected and I get nothing.
If I try to execute "./fastboot-mac flash bootloader bootloader-toro-primekk15.img" I get the message <waiting for device> and it will stay there forever.
Do you know what might be the problem ?, is there other method to do this ?, go back to Stock ROM and Re-Lock the device ?, thanks

i use windows but i also get problems when i didnt had a break after the flash parts/ update parts

brosenz said:
Hi, I am trying to Re-Lock my Galaxy Nexus GSM version, I've downloaded the SDK files (adb-mac and fastboot-mac) and all the image files and I am trying to execute the following commands:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
With the phone in normal mode I connect the USB cable to the computer, start Terminal windows and run the first command, "./adb-mac reboot bootloader" and the phone will boot into the "Fastboot Mode", then I try to execute "./fastboot-mac devices" to make sure the phone is connected and properly detected and I get nothing.
If I try to execute "./fastboot-mac flash bootloader bootloader-toro-primekk15.img" I get the message <waiting for device> and it will stay there forever.
Do you know what might be the problem ?, is there other method to do this ?, go back to Stock ROM and Re-Lock the device ?, thanks
Click to expand...
Click to collapse
I know nothing about using Macs but have you installed the device drivers? As you are getting no serial number returned when using fastboot devices im guessing not.
Mark.
On a side note please do not post questions in the Development Forums as that is not the place for them.
Thanks.

The device is being detected while running in normal mode, meaning I do have the drivers, the problem is when I go into FASTBOOT MODE, I can no longer see the phone

Craiq said:
i use windows but i also get problems when i didnt had a break after the flash parts/ update parts
Click to expand...
Click to collapse
But for the simple command ./fastboot-mac devices should work and it's not

in bootloader mode u need other drivers
but dont know how to install them on mac

First thing, make sure your fastboot file is executable
from the folder containing fastboot-mac:
chmod a+x fastboot-mac
You do not need further drivers on a mac. Just make sure you are using the correct fast boot and have all of the images in the same folder. Try using a different USB port. I renamed my fastboot file to fastboot and copied it into usr/local/bin folder so it can be accessed without the ./ ...Hope this helps...I actually just got done restoring mine because its gotta go back to the store because the internal storage is all sorts of jacked up...Since you clearly have a mac, have you had any issues using android file transfer?

dhemke17 said:
First thing, make sure your fastboot file is executable
from the folder containing fastboot-mac:
chmod a+x fastboot-mac
You do not need further drivers on a mac. Just make sure you are using the correct fast boot and have all of the images in the same folder. Try using a different USB port. I renamed my fastboot file to fastboot and copied it into usr/local/bin folder so it can be accessed without the ./ ...Hope this helps...I actually just got done restoring mine because its gotta go back to the store because the internal storage is all sorts of jacked up...Since you clearly have a mac, have you had any issues using android file transfer?
Click to expand...
Click to collapse
I just checked and Fastboot is executable, as a matter of fact it's running, the problem is that the phone cannot be seen from the FASTBOOT mode, and I can see from the phone screen that IT IS in Fastboot Mode, it says in RED letters "FASTBOOT MODE"

brosenz said:
I just checked and Fastboot is executable, as a matter of fact it's running, the problem is that the phone cannot be seen from the FASTBOOT mode, and I can see from the phone screen that IT IS in Fastboot Mode, it says in RED letters "FASTBOOT MODE"
Click to expand...
Click to collapse
Well reboot your phone. Once up, try and boot into boot loader the manual way by powering off the device, holding both vol + and -, and press power... then try your fastboot commands. Are you rooted or no?

dhemke17 said:
Well reboot your phone. Once up, try and boot into boot loader the manual way by powering off the device, holding both vol + and -, and press power... then try your fastboot commands. Are you rooted or no?
Click to expand...
Click to collapse
I've done that, going into FASTBOOT MODE manually and the same result. Yes I am rooted.

I just want to go back to stock and re-lock the phone, is there other way to accomplish that ?
NOTE: I've tried Mac and PC (Galaxy Nexus Root Toolkit 1.3), different USB cables, different USB ports, reinstalled all the drivers on the Windows computer, NOTHING, the phone it's not being detected in FASTBOOT MODE.
Is it possible to go back to stock and re-lock from the Recovery Mode ?, I have ClockWorkMode 5.5.0.2 installed and working fine.

You can flash a Stock Rom via cwm but you can only relock the phone via fastboot mode.
Has this problem only surfaced recently?
You say that you are rooted and have cwm flashed so how did you do that?
Do you have another usb cable that you can try?
Mark.

mskip said:
You can flash a Stock Rom via cwm but you can only relock the phone via fastboot mode.
Has this problem only surfaced recently?
You say that you are rooted and have cwm flashed so how did you do that?
Do you have another usb cable that you can try?
Mark.
Click to expand...
Click to collapse
I used FASTBOOT to unlock and Root, no problem at all, use the phone for 10 days and them decided to go back to Stock and Re-Lock. If I connect the phone in normal operating mode to the computer it will be recognized and I can see the phone from the computer connected via USB, so the cabe, port on the phone and port on the computer are OK. I've tried different computer (Mac and PC), different OS (Mac OS X and Windows 7), different USB cable, different USB port.

Just make sure USB debugging is on...try getting on a PC and running the ODIN file from someone was kind enough to post us...to get into odin mode, just hold up while the phone is off and hit power. You need the drivers installed and the latest version of ODIN on your desktop as well.

dhemke17 said:
Just make sure USB debugging is on...try getting on a PC and running the ODIN file from someone was kind enough to post us...to get into odin mode, just hold up while the phone is off and hit power. You need the drivers installed and the latest version of ODIN on your desktop as well.
Click to expand...
Click to collapse
I have Odin3 V1.85 installed in the PC, what I have to do with it ?, thanks

brosenz said:
I have Odin3 V1.85 installed in the PC, what I have to do with it ?, thanks
Click to expand...
Click to collapse
Plug your phone in and then turn it off...download the odin file from xda...not sure who posted it...it will be a 7z file...inside there are two separate .tar files. Extract these from the .7z file but do not fully unzip them. Place the one without LTE in the name in PDA and the one with LTE in phone, turn your phone on while holding vol -... there is a box that turns yellow in odin once your phone is connected. then check your screen against the one posted where you get the odin full restore file from and verify it matches, then flash it...

dhemke17 said:
Plug your phone in and then turn it off...download the odin file from xda...not sure who posted it...it will be a 7z file...inside there are two separate .tar files. Extract these from the .7z file but do not fully unzip them. Place the one without LTE in the name in PDA and the one with LTE in phone, turn your phone on while holding vol +... there is a box that turns yellow in odin once your phone is connected. then check your screen against the one posted where you get the odin full restore file from and verify it matches, then flash it...
Click to expand...
Click to collapse
I do not know why but Vol + does not work in my phone

brosenz said:
I do not know why but Vol + does not work in my phone
Click to expand...
Click to collapse
My bad lol...down...volume down

I made a video on how to root and unroot the nexus s 4g using a Mac and also works with galaxy nexus. Just follow the video but make sure the files u are flashing are for your phone and not a ns4g. Here's the link
https://www.youtube.com/watch?v=mIWEM8zBnTM&feature=youtube_gdata_player if u have questions u can pm me.
Sent from my Galaxy Nexus using xda premium

Esteway.619 said:
I made a video on how to root and unroot the nexus s 4g using a Mac and also works with galaxy nexus. Just follow the video but make sure the files u are flashing are for your phone and not a ns4g. Here's the link
https://www.youtube.com/watch?v=mIWEM8zBnTM&feature=youtube_gdata_player if u have questions u can pm me.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I just used your video to unroot my galaxy nexus 4.0.4 thanks a lot!

[Q] Soft-bricked my HOX, solutions exhausted

Hi guys,
Just wanted to put it out there that I'm totally new at this rooting, custom ROM thing, and I got excited which led me to fail the number ONE rule of backing-up your phone!
Anyways, here's the situation
- Rooted my HTC One X
- Tried to install a custom ROM (IceCold Jelly)
- Phone went into bootloop, after the pink unicorn screen
Some facts
- I can get into the bootloader
- When I plug the phone into the PC, PC makes a sound, but it does not recognize the phone at all
- PC detects a "fastboot" device, but no phone
- went through a few "How to save a soft-bricked" phone tutorial to no avail
- fastboot cmd stuff don't work
- i have boot.img, fastboot.exe etc all on my pc
- drivers and htc sync up to date
I'm sorry if its been answered, but in the bunch of threads I've looked at, everything revolves around being able to use the CMD and the PC actually detecting the phone. Couldn't find any way of fixing my phone, as I said above, the PC doesn't register that theres anything connected to it.
I'd appreciate some help, its been a couple of days, and having no phone is really really hurting!
I'm really really new at this, so I apologize in advance if I don't really understand the terminologies used!
Thanks in advance!

What is the output when you run "fastboot devices" from cmd with your HOX connected in fastboot mode?

Michealtbh said:
What is the output when you run "fastboot devices" from cmd with your HOX connected in fastboot mode?
Click to expand...
Click to collapse
when i type fastboot devices, it comes up as a serial number then fastboot
but when i type adb devices, nothing

appasionata said:
when i type fastboot devices, it comes up as a serial number then fastboot
but when i type adb devices, nothing
Click to expand...
Click to collapse
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.

Michealtbh said:
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.
Click to expand...
Click to collapse
I tried flashing it, the result on the cmd said something about not recognizable internal or external command

appasionata said:
I tried flashing it, the result on the cmd said something about not recognizable internal or external command
Click to expand...
Click to collapse
Are you sure you're typing it correctly? If "fastboot devices" works then those commands should also work.
Try just "fastboot erase cache", without quotation marks of course

Michealtbh said:
That's good, fastboot works.
Flash the boot.img from the rom you're trying to flash by putting it into your fastboot folder and running "fastboot flash boot boot.img" then "fastboot erase cache". Then boot into recovery and perform a full wipe then reflash the rom.
Click to expand...
Click to collapse
Michealtbh said:
Are you sure you're typing it correctly? If "fastboot devices" works then those commands should also work.
Try just "fastboot erase cache", without quotation marks of course
Click to expand...
Click to collapse
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks

appasionata said:
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks
Click to expand...
Click to collapse
Go to the folder with boot.img and fast boot exe, hold shift and press right mouse button on this folder. Than choose run cmd here (or smthng like this, I don't know how it called in English). Than type commands
Sent from my HTC One X using xda app-developers app

If you'd like a hand, I could help you do it remotely via TeamViewer.

appasionata said:
Yeah ofcourse typing the exact same things.
Alright lets clear things up,
where should the fastboot folder be? and I type "fastboot flash boot boot.img" right after i type cmd into the windows search bar. Is there anywhereI should be running the cmd from? like the directory of the cmd?
also what boot.img file should it be? custom rom?
Thanks
Click to expand...
Click to collapse
You should be running the fastboot commands from the folder your fastboot file is in. Either open a command prompt and cd to your fastboot folder, or navigate to the folder in Windows Explorer and open a command prompt there by holding shift and right clicking and choosing "open command window here".
Your fastboot folder should be in your Android SDK, probably in the root of your C drive. It could be somewhere else though depending on how you set up fastboot and adb in the first place.
The boot.img you want to flash is the one inside the rom.zip you want to flash, this goes for all roms.

Michealtbh said:
You should be running the fastboot commands from the folder your fastboot file is in. Either open a command prompt and cd to your fastboot folder, or navigate to the folder in Windows Explorer and open a command prompt there by holding shift and right clicking and choosing "open command window here".
Your fastboot folder should be in your Android SDK, probably in the root of your C drive. It could be somewhere else though depending on how you set up fastboot and adb in the first place.
The boot.img you want to flash is the one inside the rom.zip you want to flash, this goes for all roms.
Click to expand...
Click to collapse
Thanks for the help guys, I'll keep trying and will let you guys know. I think the root of the problem is that I'm inputting the fastboot commands right as I enter the cmd prompt from the windows search bar.
Will keep you guys posted, thanks for the help so far. Don't have my phone on me this minute as its with my friend whos trying to fix it too, will get it back in the morning!

Alright,
I've tried it now, and now theres a different problem. When I try to get into recovery from the bootloader, a picture of a htc device and red triangle and exclamation mark appears. And the custom rom load screen no longer appears. PC still does not recognize the phone.

Are u installed custom recovery ? Are u unlocked your device via hrc dev website?
Sent from my HTC One X using xda premium

incident said:
Are u installed custom recovery ? Are u unlocked your device via hrc dev website?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I'm not sure.
How do I install a custom recovery at this point? and how do I unlock my device via htc site. If you're talking about unlocked with operator, then yes, its an unlocked phone.
As far as I've read into this issue, I think the problem is that maybe installed the stock recovery but from a different RUU?

appasionata said:
I'm not sure.
How do I install a custom recovery at this point? and how do I unlock my device via htc site. If you're talking about unlocked with operator, then yes, its an unlocked phone.
As far as I've read into this issue, I think the problem is that maybe installed the stock recovery but from a different RUU?
Click to expand...
Click to collapse
I think he means that have you unlocked your bootloader via the htcdev.com website?
Sent from my HTC One X using xda premium

OP's first post states that he tried to install a rom, so his bootloader must be unlocked and a custom recovery must have been installed at some point.
@OP - all you have to do is download a custom recovery (CWM or TWRP) then flash it using "fastboot flash recovery nameofrecovery.img", then follow the steps previously explained to you in this thread.

Problem is though he says he rooted HOX he has no idea about unlocking bootloader at HTC Dev? So when he says he's rooted did he unlock the bootloader? He mentions he has an "operator" unlocked phone, and I think this is where he's getting confused. Otherwise suggesting further flashing will make a bad problem worse.
Also it sounds like he's trying to run CMD from start menu. He needs to run it from from where the fastboot file is located, or at least "point" to it in CMD.
---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------
If you can get into bootloader as you stated have you tried a factory reset?

appasionata, my offer of helping you do it remotely still stands. As long as your there to plug in and handle the handset, I'm pretty sure (95%~) that we can recovery your handset.

andyharney said:
appasionata, my offer of helping you do it remotely still stands. As long as your there to plug in and handle the handset, I'm pretty sure (95%~) that we can recovery your handset.
Click to expand...
Click to collapse
Thanks, I really appreciate it, I think I might have to resort to this. How do we go about it? shall we talk about it via PM? I'm pretty busy this whole week, so we can do it on the weekends?

Looks like you have a stock recovery, try to install the correct RUU (stock ROM for your phone, manuals, can be found in a sticky post of the ROMs thread). So first get back to stock, then start over and read the f**king manuals very carefully. no offence.
If you don't know what you are doing, please don't start at all.
Manuals: http://forum.xda-developers.com/showthread.php?t=1832891
Sent from my HTC One X using xda premium

[Q] Arc S, fastboot stuck at " sending 'boot' "

Hi,
I have wanted to try CM10 for some time, and unlocked my Arc S for the first time today. I followed the guides at freexperiaproject, so it seems that I was able to unlock the bootloader successfully. After it was unlocked I rebooted and all my user data was reset (as expected).
I downloaded "FXP150-cm-10-20121208-UNOFFICIAL-anzu" from rapidgator and "gapps-jb-20121011-signed" wich I found at the cyanogenmod wiki. I put both the zip files in the root of my SD card. When I try running "fastboot flash boot boot.img" it says "sending 'boot' <5616 KB>...", but nothing more happens. I let it stay for several minutes and I have to push Control+C to abort it. I also extracted "boot.img" to the platform-tools folder under android-sdk.
In the SDK Manager I have installed "Android SDK Tools", "Android SDK Platform-tools" and "Google USB Driver".
Am I doing something wrong? Is there anything more I should do before running fastboot? Sorry if I have missed a basic step here.
Espen

First, copy the file .img to the fastboot folder, if the file system.img means you have to run the command with the command: fastboot> fastboot flash system system.img, if the file userdata.img means that the command should be fastboot> fastboot flash userdata userdata.img .if the file xxxxboot.img mean form the command fastboot> fastboot flash boot xxxxboot.img
Iam using google translate.so,I hope I helped you and I hope you understand
Sent from my LT18i

The file from the zip file is called "boot.img". I have copied it to the fastboot folder, and I am running "fastboot flash boot boot.img", as the "how to-" says.

Reinstall drivers
Sent from my LT15i using xda premium

espenta said:
Hi,
I have wanted to try CM10 for some time, and unlocked my Arc S for the first time today. I followed the guides at freexperiaproject, so it seems that I was able to unlock the bootloader successfully. After it was unlocked I rebooted and all my user data was reset (as expected).
I downloaded "FXP150-cm-10-20121208-UNOFFICIAL-anzu" from rapidgator and "gapps-jb-20121011-signed" wich I found at the cyanogenmod wiki. I put both the zip files in the root of my SD card. When I try running "fastboot flash boot boot.img" it says "sending 'boot' <5616 KB>...", but nothing more happens. I let it stay for several minutes and I have to push Control+C to abort it. I also extracted "boot.img" to the platform-tools folder under android-sdk.
In the SDK Manager I have installed "Android SDK Tools", "Android SDK Platform-tools" and "Google USB Driver".
Am I doing something wrong? Is there anything more I should do before running fastboot? Sorry if I have missed a basic step here.
Espen
Click to expand...
Click to collapse
did you make the phone enter fastboot mode?
you should run "fastboot devices" to see.

Thanks for the replies!
I tried on a different computer this morning, and here it worked immediately. Not sure what was wrong on the other one, because I installed the same SDK packages and USB driver. Installing ROM at the moment.
[Edit]: Everything seems to be working fine. Very happy with CM10 at the moment

dewa999 said:
First, copy the file .img to the fastboot folder, if the file system.img means you have to run the command with the command: fastboot> fastboot flash system system.img, if the file userdata.img means that the command should be fastboot> fastboot flash userdata userdata.img .if the file xxxxboot.img mean form the command fastboot> fastboot flash boot xxxxboot.img
Iam using google translate.so,I hope I helped you and I hope you understand
Sent from my LT18i
Click to expand...
Click to collapse
I just tried to install cm 10 on Arc S mobile...
It's bootloader is unlocked & rooted...
but when I try to connect it in flashboot mode & In flashtool Press "Reboot into fastboot mode (via ADB) ,
It show error that "This action needs a connected device in ADB mode"
what I have to do to flash boot.img ?
I attached 2 screenshots of connecting & error....
device is connected in flashmode , I also attached blue noti. LED pic which on when connect...
How I connect device & flash boot.img ???
Can I flash that kernel directly by clicking "select kernel to flash" ?
& Why it is showing ADB error when I click "reboot into fastboot mode (via ADB) ??
In advance thank you...

Tech-G.ONE said:
I just tried to install cm 10 on Arc S mobile...
It's bootloader is unlocked & rooted...
but when I try to connect it in flashboot mode & In flashtool Press "Reboot into fastboot mode (via ADB) ,
It show error that "This action needs a connected device in ADB mode"
what I have to do to flash boot.img ?
I attached 2 screenshots of connecting & error....
device is connected in flashmode , I also attached blue noti. LED pic which on when connect...
How I connect device & flash boot.img ???
Can I flash that kernel directly by clicking "select kernel to flash" ?
& Why it is showing ADB error when I click "reboot into fastboot mode (via ADB) ??
In advance thank you...
Click to expand...
Click to collapse
You already asked for help in another topic, why here again?

Someguyfromhell said:
You already asked for help in another topic, why here again?
Click to expand...
Click to collapse
sorry bro....
But my main question is remain....
Why It is showing ADB error... I tried on two laptops, but result is same...
so I thought any one know the exact reason behind it.
ok I will try to flash kernel directly....

Tech-G.ONE said:
sorry bro....
But my main question is remain....
Why It is showing ADB error... I tried on two laptops, but result is same...
so I thought any one know the exact reason behind it.
ok I will try to flash kernel directly....
Click to expand...
Click to collapse
i dont like flashing kernel by flashtool, as far i done several 2011 devices the best method allways was over adb:good: & it pretty easy.
download android sdk & open the exe. leave all like it is (only may make sure google usb drivers are checked) & press on install.
after install place the boot.img here: ...\sdk\platform-tools
2. connect device into fastboot mode (blue led)
3.click in a empty space in the folder. now HOLD SHIFT & right click, choose ''open command line window here'' (<-- or sth like that sorry my setup is german)
4. enter 'fastboot devices' --> your device should be recognized as a bunch of numbers.
5. flash kernel by entering ''fastboot flash boot boot.img'' it tells you all done.
6. ''fastboot reboot''
7. enjoy new kernel

TWRP installed but no OS. Udev problem?

Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
Code:
I: cannot find file /sys/class/android_usb/android0/idProduct
I: cannot find file /sys/class/android_usb/android0/idVendor
When is in appear/disappear loop:
Code:
I:[MTP]Mtpserver::run fd: 20
E:[MTP] request read returned -1, errno: 5 , exiting MtpServer::run loop
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things

Shugui said:
Hi guys!
After years playing around with android roms and devices it looks that i probably brick a device for first time.
I'll try to be brief, but if you need more info it will be a pleasure give it to you.
Now my MI6 have recovery cofface 3.1.1.-0 installed but no os. I can reboot on bootload with keys. The problem is that im unable to push a zip into the device. Commands "adb devices" and "fastboot devices" return no devices founded.
a) OTG: Recovery doesnt allow me to mount USB-OTG. I enter in Mount and when i click over USB-OTG it highlighted but the checkbox still empty.
b)Plug into pc: The phone appears and disappears each second. Tried multiples wires.
Udev not found warning shows up when I click in the device before it disappears.
c) ADB sideload: not working, cause i cant reach MI6 from PC.
I add some stuff i see in logs and could be interesting:
When i use sideload:
When is in appear/disappear loop:
I tried to recover it from Windows and Linux even from FWUL liveiso but all same results.
Any idea is appreciated, thanks a lot!
PD: Excuse my English Besides not having a good level, I'm tired of being all day trying things
Click to expand...
Click to collapse
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.

NickTheSickDick said:
That recovery is ancient. Just use fastboot to flash a stock rom with miflash. Then flash latest twrp.
Click to expand...
Click to collapse
Commands "adb devices" and "fastboot devices" return no devices founded.
Click to expand...
Click to collapse
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Have you tried different machine to do adb devices/ fastboot devices?

ArcOnFire said:
This is the first roadblock for him.
if fastboot devices can't detect his device, then any fastboot command to flash a partition is also invalid.
Click to expand...
Click to collapse
You right
ArcOnFire said:
Have you tried different machine to do adb devices/ fastboot devices?
Click to expand...
Click to collapse
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.

Shugui said:
You right
Yes, linux and windows. And drivers are OK cause it worked before.
I think when i wiped system the device got corrupted someway. Now if i plug it into debian machine the computer detect the phone one sec., then dissapear other second, appear again... and so on.
My idea was to flash new recovery from otg but recovery didnt mount the device. Im researching for some way to mount it manually but at the moment not success.
Click to expand...
Click to collapse
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.

mArIuS% said:
I'm assuming it's a driver error. Few years ago i had a mtk smartphone and somehow i managed to hard brick it, PC recognize it just for 2 or 3 seconds and that was because fastboot drivers didn't installed so i had to install it manually from device manager, for mtk drivers name was preload 89xx (driver must be for specific motherboard model number), i opened device manager, boot phone in fastboot mode, connect it to pc and on the short time wen the PC recognize the phone i hited right click and choose update driver manually, i believe it could be possible to do the same thing with mi 6, i don't know if there are separate drivers for fastboot mode to be able to install them.
Click to expand...
Click to collapse
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back

Shugui said:
I'll try this when i have a bit more time. Right now i dont have all the time i desire. Too much work and university stuff
Thank you all.
I'll be back
Click to expand...
Click to collapse
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess

Fahrilubis said:
Guys i need ur help please, i cant boot into twrp from fastboot
My step is
My step is go to fastboot > instal mi driver in device manager then adb interface coming > open adb folder > put twrp into adb folder > change name twrp file into recovery then use this command > fastboot flash recovery recovery.img then succes and fastboot boot recovery.img but just stuck on mi logo for 30minutes i guess
Click to expand...
Click to collapse
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure

Shugui said:
fastboot devices
fastboot flash recovery twrp.img
fastboot flash boot twrp.img
fastboot reboot
i think u forgot the third command. Anyway check the info, im not 100% sure
Click to expand...
Click to collapse
Thx brother solv