Database Info

[Q] Nexus 5 bricked and USB cable not working

I bricked my Nexus 5 by installing the kernal from touchcontrol.
I can get into recovery mode.
I can not mount the USB storage or access any of my phones files
I've tried installing ADB drivers but that didn't help.
Anyone know what I should do to fix this?

BleachFan21 said:
I bricked my Nexus 5 by installing the kernal from touchcontrol.
I can get into recovery mode.
I can not mount the USB storage or access any of my phones files
I've tried installing ADB drivers but that didn't help.
Anyone know what I should do to fix this?
Click to expand...
Click to collapse
Download the stock kernel zip from here https://www.androidfilehost.com/?fid=23269279319202404 and place it in the fastboot folder. Then reboot in recovery and choose adb sideload. Open cmd and type : adb sideload namekernel.zip and press enter and that should do it, then reboot.

gee2012 said:
Download the stock kernel zip from here and place it in the fastboot folder. Then reboot in recovery and choose adb sideload. Open cmd and type : adb sideload namekernel.zip and press enter and that should do it, then reboot.
Click to expand...
Click to collapse
How do I place it in the fastboot folder?

BleachFan21 said:
How do I place it in the fastboot folder?
Click to expand...
Click to collapse
Copy it to the android-sdk/platform-tools

gee2012 said:
Copy it to the android-sdk/platform-tools
Click to expand...
Click to collapse
Is that a type of program? USB isn't working on my phone as even though it makes the connecting sound when I plug it in it's not appearing on the explorer

BleachFan21 said:
Is that a type of program? USB isn't working on my phone as even though it makes the connecting sound when I plug it in it's not appearing on the explorer
Click to expand...
Click to collapse
Sorry, you`re right. Well without usb you can`t do anything. Have you made a nandroid backup to restore in recovery?

gee2012 said:
Sorry, you`re right. Well without usb you can`t do anything. Have you made a nandroid backup to restore in recovery?
Click to expand...
Click to collapse
no

BleachFan21 said:
no
Click to expand...
Click to collapse
Well then there is nothing i can tell that can help you mate, good luck

Hello,
When the phone is in recovery mode, the file explorer won't show up with your nexus files... The fact that a sound is coming proves that the phone is being detected...
If you have setup a working adb environment you can follow what @gee2012 has said and sideload the kernel and flash it... If you haven't then download the android sdk and make sure you have downloaded the usb_driver package as well...

BleachFan21 said:
no
Click to expand...
Click to collapse
First, don't yet think your phone it's bricked. The actual solution is to get the proper driver on the computer. Remember that nexus 5 does not have Sdcard and there's not way to mount to the computer via recovery. Only ADB PUSH and ADB SIDELOAD will put a Rom into your phone.
You have to check on device manager to see the status of the driver. if t shows as Nexus 5, you will have to update the driver to and adb compatible one. If it says ADB........ then, you are good to go
EDIT: @vin4yak, one day I'll go to ninja school too

1.) If your device is actually bricked then a USB cable will do you absolutely no good. Fixing a "bricked" device is something that will need to be JTAG'd for it to work again. I think you might be mistaken about what a bricked device is. Its pretty hard to brick a nexus device so I highly doubt you're device is bricked.
2.) You have to get into fastboot mode. Just search for how to do so. Then you can flash the stock img's through fastboot and you'll be back in business. I have no clue about what drivers you'll need for your setup as I haven't run windows in 9 years or so. Just get the drivers, fastboot, and get your nexus back.

Why don't you just flash a boot.img from the stock rom? Or going back to stock?
You cannot mount sdcard to the pc in recovery. You have to use adb push or adb sideload.
To make adb work in recovery you need naked usb drivers 0.73.
Then you can adb sideload a rom, or push a rom to /sdcard.
Anyway download my attachment, put your phone to fastboot mode and double click on flash.bat then report me back

Check out this thread. If you can boot into recovery, then you should be able to boot into fastboot and restore your N5 back to stock.
http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
Sent from my Nexus 5 using Tapatalk

[Q] HTC One X (ATT) No OS

Long story short, I had an issue with my HTC One X that I received from a friend. It would load up and then immediately restart about 15 seconds after getting to lock screen. I was just stuck in a boot loop.
So I decided to flash a new rom onto the phone, but neither I nor my friend had created a backup so now my OS is wiped.
I can boot into recovery mode, though. I'm not sure what the first screen is called, but it's the one with the skating androids. It tells me:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse
When I enter into recovery, it appears that I have TWRP v2.3.1.0.
In here, I cannot install any roms. They appear to fail. Installing says:
Zip Install Complete
Updating partition details...
Running boot script...
Finished running boot script.
Installing '/sdcard/pac.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip '/sdcard/pac.zip'
Updating partition details...
Click to expand...
Click to collapse
Failed
Click to expand...
Click to collapse
I had read somewhere that I need to upgrade my TWRP in order to properly install roms, but at the current moment, running adb devices in a command prompt pointed at my adt bundle folder does not work. It just has a blank list.
Attached is a photo with what I think are the most relevant things I've downloaded/installed so far.
It does look like I can connect my phone to the computer via Mount USB Storage, but sideloader does not work since adb devices is blank.
Any thoughts?

kpxexpress said:
Long story short, I had an issue with my HTC One X that I received from a friend. It would load up and then immediately restart about 15 seconds after getting to lock screen. I was just stuck in a boot loop.
So I decided to flash a new rom onto the phone, but neither I nor my friend had created a backup so now my OS is wiped.
I can boot into recovery mode, though. I'm not sure what the first screen is called, but it's the one with the skating androids. It tells me:
When I enter into recovery, it appears that I have TWRP v2.3.1.0.
In here, I cannot install any roms. They appear to fail. Installing says:
I had read somewhere that I need to upgrade my TWRP in order to properly install roms, but at the current moment, running adb devices in a command prompt pointed at my adt bundle folder does not work. It just has a blank list.
Attached is a photo with what I think are the most relevant things I've downloaded/installed so far.
It does look like I can connect my phone to the computer via Mount USB Storage, but sideloader does not work since adb devices is blank.
Any thoughts?
Click to expand...
Click to collapse
The first screen with the skating Androids is your bootloader, FYI. Adb commands aren't used for flashing a recovery, fastboot commands are used. You do indeed need to update TWRP, the version you currently have installed isn't compatible with any current ROMs. Click the guide link in my signature, there are instructions on anything you need to do there.
Transmitted via Bacon

timmaaa said:
The first screen with the skating Androids is your bootloader, FYI. Adb commands aren't used for flashing a recovery, fastboot commands are used. You do indeed need to update TWRP, the version you currently have installed isn't compatible with any current ROMs. Click the guide link in my signature, there are instructions on anything you need to do there.
Transmitted via Bacon
Click to expand...
Click to collapse
I think I have my phone on Fastboot right now. I have the white screen that has FASTBOOT USB written on it with
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWERDOWN
Click to expand...
Click to collapse
underneath the control options. I've attached a picture below.
I Shift + Right Clicked to open command prompt in the folder with fastboot.exe and my recoveryfilename.img file.
In the command prompt, I enter in the command
Code:
fastboot flash recovery "recoveryfilename.img"
and it just stays on
Code:
< waiting for device >
I still can't figure out how to update my TWRP without an OS.

kpxexpress said:
I think I have my phone on Fastboot right now. I have the white screen that has FASTBOOT USB written on it with
underneath the control options. I've attached a picture below.
I Shift + Right Clicked to open command prompt in the folder with fastboot.exe and my recoveryfilename.img file.
In the command prompt, I enter in the command
Code:
fastboot flash recovery "recoveryfilename.img"
and it just stays on
Code:
< waiting for device >
I still can't figure out how to update my TWRP without an OS.
Click to expand...
Click to collapse
What OS are you running on your PC? Did adb/fastboot work at any point?

timmaaa said:
What OS are you running on your PC? Did adb/fastboot work at any point?
Click to expand...
Click to collapse
I'm running Windows 8.1 Pro. ADB worked once. I was able to get it to detect in recovery. ADB Devices would give me the customary string of numbers followed by "RECOVERY" and then I rebooted the phone for some reason and it stopped working. Oh, during that time I was also able to move stuff to the phone via ADB Sideload, but I would get pretty much the same errors when installing, which I later found out was because my TWRP was too old. I can't seem to get it to connect via ADB/Fastboot anymore. I can, however mount via TWRP.

kpxexpress said:
I'm running Windows 8.1 Pro. ADB worked once. I was able to get it to detect in recovery. ADB Devices would give me the customary string of numbers followed by "RECOVERY" and then I rebooted the phone for some reason and it stopped working. Oh, during that time I was also able to move stuff to the phone via ADB Sideload, but I would get pretty much the same errors when installing, which I later found out was because my TWRP was too old. I can't seem to get it to connect via ADB/Fastboot anymore. I can, however mount via TWRP.
Click to expand...
Click to collapse
There's your problem. Windows 8.1 isn't compatible with fastboot. You'll need to get access to a PC with a lower version of Windows so you can update TWRP.

timmaaa said:
There's your problem. Windows 8.1 isn't compatible with fastboot. You'll need to get access to a PC with a lower version of Windows so you can update TWRP.
Click to expand...
Click to collapse
Oh, really? Will 8 or 7 work?
I used a Windows 7 laptop and was able to update my TWRP to v2.7.0.8!
Seem to still be unable to detect devices via adb devices command.
Ok. Had to update my drivers.
I'm following your instructions on How To Install A ROM with TWRP Recovery, and now my issue is that it is saying
Code:
error flashing zip '/sdcard/pac.zip'
I've included a picture below.

kpxexpress said:
Oh, really? Will 8 or 7 work?
I used a Windows 7 laptop and was able to update my TWRP to v2.7.0.8!
Seem to still be unable to detect devices via adb devices command.
Ok. Had to update my drivers.
I'm following your instructions on How To Install A ROM with TWRP Recovery, and now my issue is that it is saying
Code:
error flashing zip '/sdcard/pac.zip'
I've included a picture below.
Click to expand...
Click to collapse
You're gonna need to get s-off so you can update your firmware. In order to get s-off you'll need to flash the Kickdroid ROM. Once you've flashed Kickdroid you can go to the Rumrunner s-off site and get s-off. Then follow the instructions in my guide thread to update your firmware.

timmaaa said:
You're gonna need to get s-off so you can update your firmware. In order to get s-off you'll need to flash the Kickdroid ROM. Once you've flashed Kickdroid you can go to the Rumrunner s-off site and get s-off. Then follow the instructions in my guide thread to update your firmware.
Click to expand...
Click to collapse
Alright, so I managed to get the Kickdroid ROM working! So right now I at least have a working phone that I can use! Thanks a TON for getting me this far.
Rumrunnner seems to not be working right for me. I'm in ADB recovery and can confirm an ADB connection, but it's still displaying
Code:
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on? Drivers?)
But it's a start. I'll have to make sure I'm following all instructions carefully.

[Q] Deleted my OS! | OnePlus One

Today was the worst day ever. I rooted my phone, and it worked perfectly until today. What happened was that when I updated the Google Play Services, I lost connection anything Google related (No connection) I factory reset my phone 4 times, wiped the internal storage, and it still said that I couldn't connect to the Play Store (E.X Could not establish a reliable connection). So I went into recovery and went to Advanced Wipe, and without knowing so, I deleted my OS! Im so stupid..
I FORGOT I WASN'T AN IT...
For the past two days I've been trying to get back the OS (33R). Heres what I've done
1. Downloaded the XNPH33R OS from their website and tried to install it (says NO MD5 Verification)
2. Tried doing everything about resetting OS.
3. HUGEST PROBLEM : Whenever I try and do (e.g adb sideload <rom.>.zip, or flashing) It just says Error: Device not found
4. Downloaded ADB from the Android Debug Bridge, all of my cmd commands return the same thing.
3. Also a huge problem: When I try to flash, it says (device not unlocked) and then I unlock the bootloader (Im guessing what that is will unlock it) and then I go back to the Recovery and do it again on CMD, it repeats it.
ANY SUGGESTIONS?
(If you need more information I will gladly give it to you)

BlaHBlaH525 said:
Today was the worst day ever. I rooted my phone, and it worked perfectly until today. What happened was that when I updated the Google Play Services, I lost connection anything Google related (No connection) I factory reset my phone 4 times, wiped the internal storage, and it still said that I couldn't connect to the Play Store (E.X Could not establish a reliable connection). So I went into recovery and went to Advanced Wipe, and without knowing so, I deleted my OS! Im so stupid..
I FORGOT I WASN'T AN IT...
For the past two days I've been trying to get back the OS (33R). Heres what I've done
1. Downloaded the XNPH33R OS from their website and tried to install it (says NO MD5 Verification)
2. Tried doing everything about resetting OS.
3. HUGEST PROBLEM : Whenever I try and do (e.g adb sideload <rom.>.zip, or flashing) It just says Error: Device not found
4. Downloaded ADB from the Android Debug Bridge, all of my cmd commands return the same thing.
3. Also a huge problem: When I try to flash, it says (device not unlocked) and then I unlock the bootloader (Im guessing what that is will unlock it) and then I go back to the Recovery and do it again on CMD, it repeats it.
ANY SUGGESTIONS?
(If you need more information I will gladly give it to you)
Click to expand...
Click to collapse
Could you post the fastboot and adb commands and results you get from executing them in CMD?

abde27 said:
Could you post the fastboot and adb commands and results you get from executing them in CMD?
Click to expand...
Click to collapse
I've been struggling the hole day long with the same problem.
Maybe you could read my thread. : )
Link

abde27 said:
Could you post the fastboot and adb commands and results you get from executing them in CMD?
Click to expand...
Click to collapse
CMD
cd C:\Users\xxxx\Desktop\android-sdk-windows\platform-tools
adb sideload ROM33R.zip <When the ADB sideload is on>
<Output>
* daemon not running. Starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Maybe I should try installing ADB drivers?

BlaHBlaH525 said:
CMD
cd C:\Users\xxxx\Desktop\android-sdk-windows\platform-tools
adb sideload ROM33R.zip <When the ADB sideload is on>
<Output>
* daemon not running. Starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
Maybe I should try installing ADB drivers?
Click to expand...
Click to collapse
Go into Device Manager, and make sure your OPO is listed as under ADB Interface while the OPO is in bootloader mode. If it's not there then yes install or reinstall the adb driver but make sure you don't have any other devices with a triangle next to it as that may be your OPO.

abde27 said:
Go into Device Manager, and make sure your OPO is listed as under ADB Interface while the OPO is in bootloader mode. If it's not there then yes install or reinstall the adb driver but make sure you don't have any other devices with a triangle next to it as that may be your OPO.
Click to expand...
Click to collapse
My phone is listed as
Fastboot Interface (Google USB id)

BlaHBlaH525 said:
My phone is listed as
Fastboot Interface (Google USB id)
Click to expand...
Click to collapse
Does your OPO get listed when you enter "fastboot devices" ? When you had originally rooted and unlocked your OPO had you done it through CMD or a toolkit?

abde27 said:
Does your OPO get listed when you enter "fastboot devices" ? When you had originally rooted and unlocked your OPO had you done it through CMD or a toolkit?
Click to expand...
Click to collapse
Ill give you a screen shot of it being in fastboot mode. I also had rooted and unlocked my phone thru CMD

BlaHBlaH525 said:
Ill give you a screen shot of it being in fastboot mode. I also had rooted and unlocked my phone thru CMD
Click to expand...
Click to collapse
Ok so let me get this straight:
You had originally unlocked your bootloader and rooted through the cmd: "fastboot oem unlock" ?
Did you use this guide by any chance?: http://forum.xda-developers.com/showthread.php?t=2788632
Now you have no installed os and whenever you try to sideload or push stock 33R through adb it gives an error of the device not being found to the adb shell? Or does it complain that the bootloader is unlocked? If the second is happening you might need to reset the unlock and tamper bits,
Sorry if I'm asking something you already stated. I just want to be clear before I recommend anything or try to pull someone who's more experienced in for help.

abde27 said:
Ok so let me get this straight:
You had originally unlocked your bootloader and rooted through the cmd: "fastboot oem unlock" ?
Did you use this guide by any chance?: http://forum.xda-developers.com/showthread.php?t=2788632
Now you have no installed os and whenever you try to sideload or push stock 33R through adb it gives an error of the device not being found to the adb shell? Or does it complain that the bootloader is unlocked? If the second is happening you might need to reset the unlock and tamper bits,
Sorry if I'm asking something you already stated. I just want to be clear before I recommend anything or try to pull someone who's more experienced in for help.
Click to expand...
Click to collapse
Yeah I used that guide. And yes, what you stated is true. But another thing is that when I install the ROM, it says No MD5 file, but when I check the zip file, it says that there is a file called md5sum-fastboot.md5, I think that that is what TWRP is saying.

Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
---------- Post added at 07:13 AM ---------- Previous post was at 07:02 AM ----------
If you can, just push a recovery flashable version of CM11S from here to your phone and flash it with TWRP. No sideload required.
Transmitted via Bacon

timmaaa said:
Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
Click to expand...
Click to collapse
I have not tried, but I was able to view the internal storage and place the ROMs inside /sdcard/

timmaaa said:
Are you able to use adb to push a zip to your internal storage?
Transmitted via Bacon
---------- Post added at 07:13 AM ---------- Previous post was at 07:02 AM ----------
If you can, just push a recovery flashable version of CM11S from here to your phone and flash it with TWRP. No sideload required.
Transmitted via Bacon
Click to expand...
Click to collapse
BlaHBlaH525 said:
I have not tried, but I was able to view the internal storage and place the ROMs inside /sdcard/
Click to expand...
Click to collapse
He is right. If you can actually see the internal storage, you should be able to flash a flashable version of stock 33R from TWRP.
Actually if you are on the latest TWRP you can probably use the MTP functions and copy the file over without having to adb push it.
If you don't have the latest TWRP you can download the .img and flash it via the fastboot command. The latest is 2.8.0.1

abde27 said:
He is right. If you can actually see the internal storage, you should be able to flash a flashable version of stock 33R from TWRP.
Actually if you are on the latest TWRP you can probably use the MTP functions and copy the file over without having to adb push it.
If you don't have the latest TWRP you can download the .img and flash it via the fastboot command. The latest is 2.8.0.1
Click to expand...
Click to collapse
I have the latest version anyways
So, anything else?

Recovery flashable version is the easiest solution.
Transmitted via Bacon

timmaaa said:
Recovery flashable version is the easiest solution.
Transmitted via Bacon
Click to expand...
Click to collapse
Is that what I should do? If so, could you tell me how? Please xD

BlaHBlaH525 said:
Is that what I should do? If so, could you tell me how? Please xD
Click to expand...
Click to collapse
You just flash it like you would flash any ROM, using the install feature in TWRP. Download it from the link I provided before.
Transmitted via Bacon

timmaaa said:
You just flash it like you would flash any ROM, using the install feature in TWRP. Download it from the link I provided before.
Transmitted via Bacon
Click to expand...
Click to collapse
Are these different from the ones I downloaded from the offical CyanogenMOD OnePlus One page? Because when I try to flash it, it says MD5 file not found an then puts an error...

BlaHBlaH525 said:
Are these different from the ones I downloaded from the offical CyanogenMOD OnePlus One page? Because when I try to flash it, it says MD5 file not found an then puts an error...
Click to expand...
Click to collapse
Without you being more specific about exactly which zip you got from the CM site it's impossible to say. What's the filename?
Transmitted via Bacon

timmaaa said:
Without you being more specific about exactly which zip you got from the CM site it's impossible to say. What's the filename?
Transmitted via Bacon
Click to expand...
Click to collapse
The URL is
https://cyngn.com/products/oneplusone/
The name is
cm-11.0-XNPH33R-bacon-signed-fastboot.zip with the MD5 Checksum of 2c5bcbb3230501f2b841b56cac392bcb

Phone stuck on boot animation, won't sideload

I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.

pds6 said:
I unrooted phone to update to Android 5.0.1
Wiped data & cache and tried to reboot but phone won't load past boot animation
I have tried everything I can find online. Phone appears in Device Manager as Android Device, but does not connect to PC when in command prompt.
adb devices shows no devices
when I start phone in fastboot, then recovery mode, I can select to install a file via ADB
when I choose this, and run adb devices in command prompt, it then shows a sideload device
but when I go to load a file, it gives me the same error every time:
E:footer is wrong
E:signature verification failed
Is there anything I can do? Please help! Thanks.
Click to expand...
Click to collapse
What recovery have you got and what file are you sideloading?

All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.

rootSU said:
What recovery have you got and what file are you sideloading?
Click to expand...
Click to collapse
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1

pds6 said:
I'm not sure unfortunately... Is that something I can find out from the Fastboot menu?
I was trying to sideload a factory image 5.0 or 5.0.1
Click to expand...
Click to collapse
You can't sideload a factory image. You must use fastboot.

zagorteney said:
All you have to do is restart the phone in bootloader and make a fresh install of factory image via fastboot.
Click to expand...
Click to collapse
How can I make my Acer read Nexus 5 to install factory image via command prompt?
It comes up in Device Manager, driver seems to be installed fine, as Android Device but does not connect properly (no devices listed in "adb devices")

You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus

rootSU said:
You can't sideload a factory image. You must use fastboot.
Click to expand...
Click to collapse
Oh okay, my bad. Do I have any options to sideload anything, or is there a way to make phone connect for fastboot? Again, it's visible in Device Manager w/drivers, but not in command prompt. Thank you
will try above suggestions and report back

rootSU said:
You use fastboot in bootloader if you want to use factory images.
Read the following 2 threads in general > sticky roll-up
- adb and fastboot
- flashing factory images / save your nexus
Click to expand...
Click to collapse
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."

pds6 said:
After downloading the recommended Driver file from adb and fastboot thread, I unzip it to a folder and attempt to install in Device Manager. I get error saying "the hash for the file is not present in the specified file log..."
Click to expand...
Click to collapse
Win 7?

rootSU said:
Win 7?
Click to expand...
Click to collapse
8.1

pds6 said:
8.1
Click to expand...
Click to collapse
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?

rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Yes uninstalled drivers through Device Manager & did the restart through the settings as outlined there.
Will try to download google usb driver from here http://developer.android.com/sdk/win-usb.html#top
Edit: this driver installed correctly. Device now appears in device manager as Android Bootloader Interface (phone is at Fastboot screen)

rootSU said:
Did you follow the correct windows 8 specific instructions to turn off driver signing etc?
Click to expand...
Click to collapse
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed

pds6 said:
Wow thank you, your thread suggestion was exactly what I needed. I did not know the difference between ADB & Fastboot.
Silly mistake but one that I couldn't solve through several hours of internet searches yesterday. Thanks for your time and insight, have a great day
Nexus 5 fixed
Click to expand...
Click to collapse
No probs. Glad you're sorted.

[Q] How to install custom ROM on stock phone (HBOOT 1.xx/2.xx)

I'm really new to this, and don't want to break my device.
What exact steps do I have to do to root my device, and install a custom rom on it?
Got the HTC One S

rifek4 said:
http://forum.xda-developers.com/wiki/HTC_One_S
http://forum.xda-developers.com/showthread.php?t=2076086
http://forum.xda-developers.com/showthread.php?p=51291053
Links are a little bit older but good. Look at forum General and Development category for more stuff.. You must first do a unlock bootloader, then flash custom recovery (newest unofficial TWRP is best), then you can install new ROM which doesn't need S-OFF/superCID after that flash new kernel for it ROM via fastboot. You must looking some thread's on forum, explore the possibilities, find out what and how you can use... I can't say you everything in one word - I don't have such power
Click to expand...
Click to collapse
I tried all this, but once I get in the bootloader and try to get my "Token ID" or whatever to root it, it just says device not found and that its waiting for device.
Its in USB Debugging mode, and the drivers are fine, its latest drivers and the command to goto bootloader works fine.
Not sure what to do.
I appreciate you taking the time to link me all this though
Just not sure how to do it, I'm probably doing something wrong.
But I got as far as getting to the bootloader.

rifek4 said:
http://forum.xda-developers.com/showthread.php?t=1583427
Try unlock with this thread, not with toolkit. You use newest HTC Drivers? Delete old drivers, install this one then restart PC and try again with above thread.
Click to expand...
Click to collapse
In fastboot menu, got the CMD in right directory, typed the command to get identifier token, says "Waiting For Device..."
Still same issue :/

rifek4 said:
You do reinstall drivers? You see "FASTBOOT USB" text on fastboot menu after connect cable?
Click to expand...
Click to collapse
Says "FASTBOOT" with red highlight.
Then just has instructions, says "BOOTLOADER", Reboot, Reboot Bootloader and Power Down as options.
Also, said that driver you linked isn't compatible with my OS.
I'm on Windows 8.1
Edit: Followed those instructions, went back to repeat and try again. Still did same thing, saying waiting for device.

rifek4 said:
So is not good. After connect USB cable there must be "FASTBOOT USB" text. Check link now, I change URL. If you are on Windows 8.1 install new drivers from right URL (I change now one post before) and look HERE.
Click to expand...
Click to collapse
Says Fastboot USB now.
Going to try it out!

LunarSAF said:
Says "FASTBOOT" with red highlight.
Then just has instructions, says "BOOTLOADER", Reboot, Reboot Bootloader and Power Down as options.
Also, said that driver you linked isn't compatible with my OS.
I'm on Windows 8.1
Edit: Followed those instructions, went back to repeat and try again. Still did same thing, saying waiting for device.
Click to expand...
Click to collapse
Fastboot Win 8.1 fix
Latest official driver
Seems as you already got it

rifek4 said:
So is not good. After connect USB cable there must be "FASTBOOT USB" text. Check link now, I change URL. If you are on Windows 8.1 install new drivers from right URL (I change now link in this post before or they are JUST HERE) and look HERE. You must do fix fastboot for Windows 8.1.
Click to expand...
Click to collapse
Installing that driver now.
Then going to restart PC and reconnect phone, will let you know if it works!

rifek4 said:
Link for fix doesn't work I give him the same version drivers
Click to expand...
Click to collapse
Links fixed

rifek4 said:
After it, do a also fix fastboot for Windows 8.1
Click to expand...
Click to collapse
Sweet, just got the token! Doing the rest of the tutorial!
Believe everything is going to work now
This happened on next step:
c:\fastboot>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Too many links))
finished. total time: 0.000s

rifek4 said:
Good luck!
EDIT:
Try again, reconnect phone etc.
Click to expand...
Click to collapse
Tried reconnecting phone, bootloader says "Fastboot USB" and everything, tried to put it in and still same error.

rifek4 said:
Reboot phone / reboot PC / try again?
P.S.
Sorry for asking again but you do fix for Win 8.1 ?
Click to expand...
Click to collapse
Just rebooted phone, restarted PC and did the Win 8.1 Fix thing.
Still failed D:

LunarSAF said:
Just rebooted phone, restarted PC and did the Win 8.1 Fix thing.
Still failed D:
Click to expand...
Click to collapse
Generate a new unlocktoken
BTW did you uninstall HTC sync?

LS.xD said:
Generate a new unlocktoken
BTW did you uninstall HTC sync?
Click to expand...
Click to collapse
Got it working!
Now, I'm at Step 3.
Issue is, when I go to recovery, it doesn't actually open ClockWorkMod which is the one I installed. http://www.clockworkmod.com/rommanager (6.0.4.8).
It said everything went fine in command prompt, but just boots the device instead of recovery.
Should I try with the Paul one?

LunarSAF said:
Got it working!
Now, I'm at Step 3.
Issue is, when I go to recovery, it doesn't actually open ClockWorkMod which is the one I installed. http://www.clockworkmod.com/rommanager (6.0.4.8).
It said everything went fine in command prompt, but just boots the device instead of recovery.
Should I try with the Paul one?
Click to expand...
Click to collapse
Flash TWRP 2.8.5.0
Recovery can be entered by starting up bootloader mode and select "recovery"

rifek4 said:
Why not unofficial TWRP v2.8.5.5?
Click to expand...
Click to collapse
Missing option to clean sd card. And the developer says "should work, give me feedback". As @LunarSAF just starts modding the phone official should totally do it. At least he shouldn't go for CWM.

Trying to flash TWRP v2.8.5.0
sending 'recovery' is taking forever, and hasn't finished yet.
Will edit post with results once its finished!
Not sure why its taking so long.
Edit: been a while, decided to try and restart it, reconnected phone and new CMD.
Still didn't work.
"fastboot flash recovery twrp.img"
Edit: Nvm just finished.
Going to get into recovery, install SU and see how it goes from there!

Hmm....
I put the TWRP v2.8.5.0 on the device.
Tried to get into Recovery, and it just rebooted device, wouldn't get into recovery.

rifek4 said:
Flash THIS ONE - unofficial TWRP v2.8.5.5.
Click to expand...
Click to collapse
That link doesn't work :/ Found twrp-2.8.5.5-ville.img online though.
Will that work?

rifek4 said:
Link changed. Yes I think. After write unlocktoken you choose right option on display your phone? Vol + & Power button to confirm unlock?
Click to expand...
Click to collapse
Just restarted from write unlocktoken part.
Put it in to flash it and it said it did it successfully, but isn't showing up with anything to confirm.
Confirmed something way earlier when I did it though, so might not have to do it again.
Going to try writing TWRP again and booting into recovery.
Edit: Just did that, tried to go in recovery now and it doesn't work. It just reboots the device. Don't understand why.

rifek4 said:
For me wipe internal storage option work without problems
Click to expand...
Click to collapse
On HBOOT 2.15 the option is totally missing