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
Related
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.
was trying to flash cm10 onto my one x from this website:
pocketnow title "Jelly Bean on the HTC One X with CyanogenMod 10 (Video)"
ended up getting stuck one #8 because i assume "Shift+right click in the browser window" means do that in the android sdk program. now my one x wont be able to boot because on my pc it wont work but im now try to attempt at it with my mac. any suggestions on how i can boot it up? even it i do volume down+power button or volume up+down+power button it restarts but stops at the boot logo. your help is greatly appreciated, thanks.
Did you flash the boot.img?
Sent from my HTC One X using xda app-developers app
Shift + Right Click is usually done in Fastboot folder (for me) then click "open command prompt here" to use fastboot commands
Marc199 said:
Did you flash the boot.img?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
that was the next step in the guide but some im not sure how... its my first time flashing on the one x
Can you use fastboot commands with your phone?
If so then extract the boot.img from the rom you want to use, and copy it to the fastboot folder, then right click and open command prompt in the folder and enter the command fastboot flash boot boot.img
craftycarper1 said:
Shift + Right Click is usually done in Fastboot folder (for me) then click "open command prompt here" to use fastboot commands
Click to expand...
Click to collapse
alright thanks ill try that out but the only problem is that i cant seem connect my phone to the computer now as it cant seem to find it. i can enter fastboot mode and all that aswell as cwm. I'll prob just bring it to a cell shop nearby to get their help.
LittleBigTit said:
alright thanks ill try that out but the only problem is that i cant seem connect my phone to the computer now as it cant seem to find it. i can enter fastboot mode and all that aswell as cwm. I'll prob just bring it to a cell shop nearby to get their help.
Click to expand...
Click to collapse
Does it show Fastboot USB on the phone screen when you connect the USB cable to the computer?
craftycarper1 said:
Does it show Fastboot USB on the phone screen when you connect the USB cable to the computer?
Click to expand...
Click to collapse
yes it shows up as red when it says "FASTBOOT USB". damn this 5min per post is annoying
Sounds like everything should work, have you extracted the boot.img from the rom?
place it in the fastboot folder on your computer, then shft+ right click and open command prompt and you should be good to go from there with flashing the boot.img
LittleBigTit said:
yes it shows up as red when it says "FASTBOOT USB". damn this 5min per post is annoying
Click to expand...
Click to collapse
In that state try typing fastboot devices
You should something like HTxxxxxxxxxx fastboot
If the response is blank then you may not have the correct drivers installed for your phone. There are a number of ways to get the drivers; one way is to install PDAnet http://junefabrics.com/android/download.php
You don't even have to complete the whole install, just go until the driver is installed. In any case you can uninstall PDAnet and it will leave the drivers on your system.
When fastboot is finally able to recognize your phone then you can flash the boot.img by doing fastboot flash boot boot.img
(this assumes that boot.img is the actual name of the file, it should be unless you renamed it or downloaded it from somewhere)
is fastboot just a folder i create with the boot.img inside of it?
LittleBigTit said:
is fastboot just a folder i create with the boot.img inside of it?
Click to expand...
Click to collapse
No, fastboot is a tool within the Android SDK. You used it when you unlocked your bootloader.
i bought this phone off another guy who had it rooted and loaded
where is the fastboot folder located in android sdk manager?
Download this file http://www.mediafire.com/?50baad8rykng2j0
Create a folder on your C: drive called fastboot and extract the .zip into the fastboot folder
craftycarper1 said:
Download this file http://www.mediafire.com/?50baad8rykng2j0
Create a folder on your C: drive called fastboot and extract the .zip into the fastboot folder
Click to expand...
Click to collapse
alright ill try that out thanks
ended up bringing my phone to the cell shop. I know its an easy fix but cant seem to find that folder.. they said it was a 50/50 chance and will charge me $80 if they can get it to work...think it was a good idea?
Not really. Seems the only thing your phone needed to boot was the boot.img. That would have been done in a couple minutes. As already said here: you simply need to put the android sdk on your c: drive, put the boot.img in that folder, go into bootloader and connect your device with your pc, it should say fastboot USB, open command prompt, go to the direction of your sdk folder and use the fastboot command to flash the boot.img. It should then boot.
Sent from my HTC One X using xda app-developers app
LittleBigTit said:
ended up bringing my phone to the cell shop. I know its an easy fix but cant seem to find that folder.. they said it was a 50/50 chance and will charge me $80 if they can get it to work...think it was a good idea?
Click to expand...
Click to collapse
Sounds like they haven't got a clue what they're doing.
Should have just done it yourself, it's really not difficult.
hmm okay i might just go back tmr and get it my phone back.. thanks. I'll let you know if I succeed or not
I have google apps in a .zip, but no way to access them. My recovery won't load. It's stuck on "checking SD card update..."
How do I fix this or have I turned my phone into a paperweight?
ashleynicholson said:
I have google apps in a .zip, but no way to access them. My recovery won't load. It's stuck on "checking SD card update..."
How do I fix this or have I turned my phone into a paperweight?
Click to expand...
Click to collapse
try other custom recovery.
robchongke said:
try other custom recovery.
Click to expand...
Click to collapse
I have no idea how to do that.
ashleynicholson said:
I have no idea how to do that.
Click to expand...
Click to collapse
are you on sense 5 already? you have to flash it via fastboot comman in CMD.
robchongke said:
are you on sense 5 already? you have to flash it via fastboot comman in CMD.
Click to expand...
Click to collapse
I've been running CM for several months, I've never had Sense 5. I installed the new CM Nightly, and it wouldn't boot, so I had to factory reset my phone and flash an old version of CM. It booted, but the Gapps didn't install. Now when I go back into my recovery (Clockwork), it won't load properly.
ashleynicholson said:
I've been running CM for several months, I've never had Sense 5. I installed the new CM Nightly, and it wouldn't boot, so I had to factory reset my phone and flash an old version of CM. It booted, but the Gapps didn't install. Now when I go back into my recovery (Clockwork), it won't load properly.
Click to expand...
Click to collapse
download any custom recovery here. http://forum.xda-developers.com/showthread.php?t=1832891
put the recovery in your fastboot folder
rename it to recovery.img
enter this command one at a time
fastboot flash recovery recovery.img
fastboot erase cache
then reboot your phone to recovery
robchongke said:
download any custom recovery here. http://forum.xda-developers.com/showthread.php?t=1832891
put the recovery in your fastboot folder
rename it to recovery.img
enter this command one at a time
fastboot flash recovery recovery.img
fastboot erase cache
then reboot your phone to recovery
Click to expand...
Click to collapse
Is that the windows version?
ashleynicholson said:
Is that the windows version?
Click to expand...
Click to collapse
yes. I'm using windows 7
robchongke said:
yes. I'm using windows 7
Click to expand...
Click to collapse
Ok. Does it matter that I'm using a different computer than the one I used originally?
How exactly do I do this, does my phone need to be on or off or what's the story?
Thanks very much.
ashleynicholson said:
Ok. Does it matter that I'm using a different computer than the one I used originally?
How exactly do I do this, does my phone need to be on or off or what's the story?
Thanks very much.
Click to expand...
Click to collapse
phone must be in bootloader and you need fastboot files. how come your phone is on CM10 yet you don't know this fastboot thing?
robchongke said:
phone must be in bootloader and you need fastboot files. how come your phone is on CM10 yet you don't know this fastboot thing?
Click to expand...
Click to collapse
I had great trouble doing it the last time. It took me several hours and I came close to bricking it a few times. I'm pretty technologically incapable. It's my bootloader thing that won't load anyway, so that's no use to me.
Is there any chance you could be a saint and compile together detailed instructions for me? If not, no worries, but I'm a bit of an idiot.
ashleynicholson said:
I had great trouble doing it the last time. It took me several hours and I came close to bricking it a few times. I'm pretty technologically incapable. It's my bootloader thing that won't load anyway, so that's no use to me.
Is there any chance you could be a saint and compile together detailed instructions for me? If not, no worries, but I'm a bit of an idiot.
Click to expand...
Click to collapse
if you dont have htc driver installed in your computer just download and install htc sync manager.
i only use fastboot. here is the file. http://www.mediafire.com/download/q2540u4g3v6qqd7/Fastboot.zip
extract the fastboot zip file and put it in your desktop.
put your downloaded custom recovery inside the fastboot folder. rename it to recovery.img
boot your phone into bootloader press power button+volume down. dont release until you see this.
https://www.google.com.ph/search?q=bootloader+htc+one+x&client=firefox-a&hs=UrW&rls=org.mozilla:en-USfficial&source=lnms&tbm=isch&sa=X&ei=JGZcUuDFEsaoiAf6rYCABA&ved=0CAkQ_AUoAQ&biw=1262&bih=645#facrc=_&imgdii=_&imgrc=OCSTXEIwH8T3jM%3A%3BHGXrRqPSLDR5xM%3Bhttp%253A%252F%252Fcdn2.ubergizmo.com%252Fwp-content%252Fuploads%252F2012%252F05%252Fone-x-boot.jpg%3Bhttp%253A%252F%252Fwww.ubergizmo.com%252F2012%252F05%252Fatt-htc-one-x-bootloader-unofficially-unlocked%252F%3B640%3B459
now in your pc navigate to start>run then type cmd
one you're in command prompt. navigate to where your fastboot folder is. like this C:\Users\ashleynicholson\desktop\fastboot>
you can now enter these two commands. one at a time
fastboot flash recovery recovery.img
fastboot erase cache
you now have custom recovery. reboot your phone.
robchongke said:
if you dont have htc driver installed in your computer just download and install htc sync manager.
i only use fastboot. here is the file. http://www.mediafire.com/download/q2540u4g3v6qqd7/Fastboot.zip
extract the fastboot zip file and put it in your desktop.
put your downloaded custom recovery inside the fastboot folder. rename it to recovery.img
boot your phone into bootloader press power button+volume down. dont release until you see this.
https://www.google.com.ph/search?q=...x-bootloader-unofficially-unlocked%2F;640;459
now in your pc navigate to start>run then type cmd
one you're in command prompt. navigate to where your fastboot folder is. like this C:\Users\ashleynicholson\desktop\fastboot>
you can now enter these two commands. one at a time
fastboot flash recovery recovery.img
fastboot erase cache
you now have custom recovery. reboot your phone.
Click to expand...
Click to collapse
If you hold shift and right click in side the fastboot folder, it will open a cmd window in that location.
To navigate in cmd you use the CD command
E.g
CD C:\\ will take you to the root of C drive.
CD C:\\fastboot will take you to the folder "fastboot" and so on.
Sent from my HTC One X using xda app-developers app
Ok, I've figured out what I was doing wrong. I had my phone plugged into the USB while trying to load the bootloader, and of course that wouldn't work. All is well now, thanks very much.
Sent from my HTC One X using xda app-developers app
Hi everyone,
So I'm kind of new to flashing ROMs but I pretty much got it and flashed a couple of them the last couple of weeks.
Today I flashed the GPE ROM and everything was going smooth, installed successfully but then, the device won't boot up - it just showed me black sceen.
After a few minutes of non responding I forced shut down and went into fastboot, then hit recovery. I have CWM custom recovery. The device showed me the boot animation of the GPE for some reason and then won't go into recovery but showed me "type password to decrypt storage" for some reason. I couldn't go into recovery no matter what I did. Then somehow the device rebooted as usual and now it's on and running but tons of bugs and force stopping apps. IM TRYING TO GO INTO CWM RECOVERY BUT WHENEVER I CHOOSE THAT OPTION IT SIMPLY REBOOTS AGAIN.
HOW CAN I GO INTO RECOVERY AGAIN AND RESTORE MY NANDROID BACKUP? OR DO ANYTHING IN ORDER TO GET A DIFFERENT ROM?
The PC IS NOT RECOGNIZING THE DEVICE, CANT TRANSFER FILES OR RUN FASTBOOT COMMANDS!
THANKS IN ADVANCE! PLEASE HELP!! THE PHONE IS NOT FUNCTIONAL NOW
Nimi.
You don't need to type in caps to make your message more urgent. We'll still help you if don't use the caps lock.
fastboot erase cache, and re-install CWM with fastboot.
redpoint73 said:
You don't need to type in caps to make your message more urgent. We'll still help you if don't use the caps lock.
fastboot erase cache, and re-install CWM with fastboot.
Click to expand...
Click to collapse
Hey buddy,
You're right, im just anxious! As I said on the previous message, the device is not recognized on the pc so I cant seem to be able to run any kind of commands or transfer files! Any ideas? Any hard resets or stuff like that? Again, the phone is running but seems to have NO recovery at all!
Thanks!
nimrodiny said:
You're right, im just anxious! As I said on the previous message, the device is not recognized on the pc so I cant seem to be able to run any kind of commands or transfer files! Any ideas?
Click to expand...
Click to collapse
Was it able to connect to your PC before this issue started?
redpoint73 said:
Was it able to connect to your PC before this issue started?
Click to expand...
Click to collapse
OK, So I am able to recognize the device on PC and run commands but maybe im doing somehting wrong.
Can you please walk me through the exact commands I have to type in the right order? From A to Z.
THANKS!
Edit: CMD error says: "C:\Users\NIMI>fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img
error: cannot load 'openrecovery-twrp-2.7.0.2-m8.img'"
1) Make sure you have fastboot connectivity. Connect the phone in fastboot mode, and type the command: fastboot devices
2) Place the desired recovery .img in the folder where you have fastboot.exe located. Usually, the most updated version of your recovery is best.
3) In Command Prompt, change directory to your fastboot folder. I have no idea where you setup that up. But it will be something like: cd foldername
4) fastboot erase cache
5) fastboot flash recovery recovery.img
Where recovery.img is the filename of your desired recovery.
redpoint73 said:
1) Make sure you have fastboot connectivity. Connect the phone in fastboot mode, and type the command: fastboot devices
2) Place the desired recovery .img in the folder where you have fastboot.exe located. Usually, the most updated version of your recovery is best.
3) In Command Prompt, change directory to your fastboot folder. I have no idea where you setup that up. But it will be something like: cd foldername
4) fastboot erase cache
5) fastboot flash recovery recovery.img
Where recovery.img is the filename of your desired recovery.
Click to expand...
Click to collapse
Oh my goodness, It worked! Thank you so much my dear friend!!!
Saved my life pretty much.
Nimi
nimrodiny said:
Oh my goodness, It worked! Thank you so much my dear friend!!!
Click to expand...
Click to collapse
There's a button for that.
And you're very welcome. Happy to help!
Hi, i played around with my new OP3, and i wanted to root it. Since i'm noob at rooting, it went wrong. (i did it with twrp)
So first it just went in to bootloop, then i was still able to get to rcovery and stuff, but i followed a guide to fix bootloop, and that ****ed it even more up. The guide i followedet told me to use "OnePlus3_Unbrick_Tool"
After using "OnePlus3_Unbrick_Tool", i now cant even go into recovery anymore, the only thing i can do is go to bootloader, but when i'm in bootloader now, it wont connect proberly, so that i can use "flash twrp", so that i can use twrp recovery.
Also when i try to boot it, it because of "OnePlus3_Unbrick_Tool" goes into something, where it says "md5 checksum failed", and then restarts and does it again and again.....
I hope it's not bricked forever, pls help ))
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
bonham1988 said:
have you tried re-flashing the stock or twrp recovery adb sideload command?
Click to expand...
Click to collapse
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Godeske said:
And how do you say I do that? I have tried using the "tool all in one", where you han flash both stock and twrp, but it doesnt seem to do anything, when i press them (and the device is in bootloader)
Click to expand...
Click to collapse
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
bonham1988 said:
Just boot into bootloader mode and through command prompt check if your phone is detected by typing fastboot devices. If its detected then you flash a new recovery again. Forget the toolkit, just look for instructions on how to install a custom recovery.
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Godeske said:
Okay i've tried that now, and it wont allow me unlock my bootloader from command prompt, and i cant do the flash while it's locked.. what to do?
Click to expand...
Click to collapse
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Godeske said:
When im in fastboot mode in the bootloader, i can only find it in "device manager" as "marshall london device -> marshall london bootloader interface"
Click to expand...
Click to collapse
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
ghostofcain said:
Might seem a silly question but what phone are you using? If it is a OnePlus3 have you installed the correct drivers?
Click to expand...
Click to collapse
Pretty sure i have, but i have booked a session with oneplus costumer service now, so that they do it for me live lololol
bonham1988 said:
have you tried re-flashing the stock or twrp recovery with adb sideload command?
if not give it a shot, it might work.
Click to expand...
Click to collapse
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
gavintoronto2016 said:
Hey bonham,
The same thing happened to me but when I try to sideload it says I need 1.0.32 or higher to sideload this device
What should I do?
Click to expand...
Click to collapse
Adb version is outdated. Just download the latest ones.
Sent from my OnePlus3 using XDA Labs
Hey guys, if there are some of you, who knows a lot about this, would you like to answer this comment? Idk maybe we could use teamviewer to help me or something
simthadim said:
In fastboot mode, did you manage to find your device on the computer? On Linux this is "sudo fastboot devices", on Windows it should be roughly similar.
Click to expand...
Click to collapse
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Godeske said:
Ohh i think i understand your question. YEs in command prompt I am able to find the device, it is connected.
(do you know a lot about this, maybe you could teamview me to help?))
Click to expand...
Click to collapse
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Thank you, but i have not enabled "allow oem unlocking" in the developer settings when the phone worked, so i get a error message "FAILED (remote: oem unloc is not allowed)
What to do to unlock it then?
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
jaganmohans said:
Bro, download 3.2.4 oos rom zip file from official link. Its around 1.3 GB. Just connect ur OP3 to computer. It will detect as MTP device.Im my computer it was in the name of RAIN Transfer the zip file to internal storage. Wipe cache. And select install option in TWRP and select the zip file u pushed and flash it. Best of luck..
Click to expand...
Click to collapse
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
simthadim said:
Hey!
I'm not the expert but I have played with my 1+3 enough to have some knowledge.
First of all, do not use "all in one tools", those do not put you in control.
Cool, so fastboot is detected, though you can't get into the recovery?
Step 1) make sure you have the latest version of "fastboot" and "adb" (Android Debug Bridge) and unlock the bootloader. This tread should be helpfull: http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
You need to do this, because otherwise we will not be able to proceed (i.e. the phone is to be 'unlocked' for what we are about to do).
Step 2) If you are ready than let's flash a new recovery (TWRP):
This is also step 2 in the thread mentioned above. Very important: "Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead Unplug Your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed."
So once you have flashed a new recovery using fastboot, than you should reboot your phone into the new recovery!
step 3)
Once in the new recovery (TWRP) go to advanced and to ADB sideload. Make sure your computer detects your device with the command "adb devices" and flash a new ROM. Just for simplicity use the official OOS 3.2.4.
This should do the trick. Before you go and try make sure you understand EVERYTHING I have written. Let me know if you have questions.
Click to expand...
Click to collapse
Hey i have the same problem but this fix does not work for me.
So I have the bootloader unlocked and I can enter the bootload and my computer detects my device which is nice.
when I flash twrp on my phone trough CMD it doesnt work, my PC tells me that everything is okay but my phone will not boot into twrp and instead it will give me weird errors.
---------- Post added at 03:31 PM ---------- Previous post was at 02:56 PM ----------
this fix worked for me,
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english
Godeske said:
Bro, if just it were that simple, but it's not.. It doesn't find the phone in my computer...
Click to expand...
Click to collapse
Hmm bad try installing all op3 drivers and see whether phone is detected or not. I was in the same situation previously. Pushing zip through adp terminal is painful process. I got device offline first,after solving that i got service not recognized issue. For solving that usb debugging needs to be enabled i stuck in that step.
can you enter recovery trough fastboot mode? I.e. if you are in fastboot mode you van use the volume keys to select recovery.
100% sure you can't enter recovery?
you can try Fast and pro's option. let us know!