Database Info

[Q] HTC Sensation bootloop

Hello xda,
a friend of mine just gave me his HTC Sensation because it isnt running quite a while. The problem is that i haven't had a HTC device ever and I don't really know what to do and what information you need to help me so I'd be happy if u just tell me what information you need and I will try to get them for you.
The Information I got so far is:
- if I want to boot it, it stays at the HTC Logo
- CWM starts with some errors but you can't perform a wipe (just turns off)
- Bootloader starts as well but you can't perform wipe either, nor flash new CWM
- If i connect it with the computer while in fastboot it changes to "fastboot usb" but adb cannot find the device, though i installed first the drivers, lateron htc sync. Windows just calls it "myhtc"
bootloader says:
"PYRAMID PVT SHIP S-OFF RL
HBOOT . 1.27.1100
RADIO - 11.22.3594.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34"
So what should I try to do or what information will you need.
I would be very happy if u can help me

fnstGoliath said:
Hello xda,
a friend of mine just gave me his HTC Sensation because it isnt running quite a while. The problem is that i haven't had a HTC device ever and I don't really know what to do and what information you need to help me so I'd be happy if u just tell me what information you need and I will try to get them for you.
The Information I got so far is:
- if I want to boot it, it stays at the HTC Logo
- CWM starts with some errors but you can't perform a wipe (just turns off)
- Bootloader starts as well but you can't perform wipe either, nor flash new CWM
- If i connect it with the computer while in fastboot it changes to "fastboot usb" but adb cannot find the device, though i installed first the drivers, lateron htc sync. Windows just calls it "myhtc"
bootloader says:
"PYRAMID PVT SHIP S-OFF RL
HBOOT . 1.27.1100
RADIO - 11.22.3594.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34"
So what should I try to do or what information will you need.
I would be very happy if u can help me
Click to expand...
Click to collapse
Hi,
Go HERE
Install 4 EXT recovery,using one of the 3 methods available.(probably third)
Then,try to install ARHD ROM.(same guide)
No need to change the firmware.

So I just tried to flash 4 EXT Recovery but it doesn't work..
It finds the zip, ask me whether i want to start the update, i press vol up and "Update is in progres.." appears but nothing more, I'm waiting since 5 minutes and will probably have to power off the phone now.. the same happened when i tried to install cwm so theres something wrong with the bootloader?
What can I do now?

fnstGoliath said:
So I just tried to flash 4 EXT Recovery but it doesn't work..
It finds the zip, ask me whether i want to start the update, i press vol up and "Update is in progres.." appears but nothing more, I'm waiting since 5 minutes and will probably have to power off the phone now.. the same happened when i tried to install cwm so theres something wrong with the bootloader?
What can I do now?
Click to expand...
Click to collapse
Hi,
Maybe you should run a RUU.
Look HERE

I also thought about this but as I said adb doesn't find the device.
Since I never ran a RUU, can I still flash or do I have to get adb to run with the device.
Anyway, I cannot read out the CID of the device so if it is possible, which RUU should I flash?
Thanks for your help

fnstGoliath said:
I also thought about this but as I said adb doesn't find the device.
Since I never ran a RUU, can I still flash or do I have to get adb to run with the device.
Anyway, I cannot read out the CID of the device so if it is possible, which RUU should I flash?
Thanks for your help
Click to expand...
Click to collapse
Hi,
Try installing these windows 7 & 8 drivers (assuming you have a windows 7 or 8 machine)
Reboot your PC and see if your phone is recognized in ADB.
You are s-off,so you do not have to match it 100%
Just get a RUU that is close to your region or carrier.
If you get the wrong one,it is not a problem.
It will just give you an error.
Then,just try another.
)

Well I just installed those drivers but same result as before..
Windows says "MyHTC" and after i write "adb devices" into the cmd window it says "daemon not running. starting it on port 5037. daemon started succesfully. List of devices attached." and the next time i write adb devices it just says "List of devices attached".
Bootloader still says Fastboot USB.
So maybe there's something wrong with my adb?
Well can i flash RUU without adb finding my device or cant I?

fnstGoliath said:
Well I just installed those drivers but same result as before..
Windows says "MyHTC" and after i write "adb devices" into the cmd window it says "daemon not running. starting it on port 5037. daemon started succesfully. List of devices attached." and the next time i write adb devices it just says "List of devices attached".
Bootloader still says Fastboot USB.
So maybe there's something wrong with my adb?
Well can i flash RUU without adb finding my device or cant I?
Click to expand...
Click to collapse
Hi,
Not sure what is happening with your ADB.
Look HERE for help.
In order to run a RUU ,you need to put the bootloader into fastboot,and plug in the USB.
It should show what yours is showing.
So, it should work.

After "List of devices attached" there is no device shown, I didn't leave anything adb shows, so this is still right? Usually it always shows my device ^^
So my adb is probably not running right or it is about my phone
So my next step should be adb showing my device and therefore reinstall android sdk, java, stuff until it might show the phone
or just do something with the phone?
I still think that i cannot run a ruu without any device shown? Didnt really get an answer on this question I guess or I didnt realize it

fnstGoliath said:
After "List of devices attached" there is no device shown, I didn't leave anything adb shows, so this is still right? Usually it always shows my device ^^
So my adb is probably not running right or it is about my phone
So my next step should be adb showing my device and therefore reinstall android sdk, java, stuff until it might show the phone
or just do something with the phone?
I still think that i cannot run a ruu without any device shown? Didnt really get an answer on this question I guess or I didnt realize it
Click to expand...
Click to collapse
Hi,
Just run the RUU.
It will only show error if it does not work.
No big deal,and no damage done.
Just try another one.

if you enable usb debugging might help too

Well.. I just started "RUU_Pyramid_HTC_Europe_1.50.401.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223042_signed" and everything went fine until installation, no errors at all. Now the installer is stuck at "restarting bootloader" (or something equal, the installation is german) and the phone didnt do anything at all. It's now 15 minutes since the installation started so I probably will try another one but isn't it weird that ther is no error at all?
What should I do if the next RUU does exactly the same?
*edit:
just seeing page 2. How should I enable usb debugging without booting the phone?
*edit2:
second RUU: Same thing, no error but it didnt go further then "Restarting bootloader".
What to do now?

Any further Ideas what I could try?
Puuuush

fnstGoliath said:
Any further Ideas what I could try?
Puuuush
Click to expand...
Click to collapse
Put phone into bootloader then connect to pc and run the RUU
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

The phone was in fastboot usb while running the ruu for sure ..

fnstGoliath said:
The phone was in fastboot usb while running the ruu for sure ..
Click to expand...
Click to collapse
Hi,
Try running a RUU with the same radio (11.22) that you have installed.
You will not damage the phone.
It is not always an exact science with RUU.
Sometimes it is just trial and error.

So it is often that there is no error at all?
I just thought flashing wrong RUU will cause an error and not stopping at restarting bootloader. And anyway the bootloader seems pretty broken since it is not flashing anything at all ^^
Still i gonna try it

fnstGoliath said:
So it is often that there is no error at all?
I just thought flashing wrong RUU will cause an error and not stopping at restarting bootloader. And anyway the bootloader seems pretty broken since it is not flashing anything at all ^^
Still i gonna try it
Click to expand...
Click to collapse
Hi,
Probably ,the only thing that will fix your problem is a RUU.
So,keep trying different ones until it works.

I finally managed to find the phone via adb! I think that's a great step.
The biggest problem is that I lose any contact to the phone when i reboot it into bootloader.
I can just boot the phone into recovery and use any other adb function but as soon as I boot it into bootloader I can't do anything anymore.
That's why I cannot use any fastboot commands to flash a zip, neither run a RUU completely i guess.
So I think that i need any rom to either flash via recovery or just via PC not using fastboot/bootloader at all.
Are there any possibilities for me now?

fnstGoliath said:
I finally managed to find the phone via adb! I think that's a great step.
The biggest problem is that I lose any contact to the phone when i reboot it into bootloader.
I can just boot the phone into recovery and use any other adb function but as soon as I boot it into bootloader I can't do anything anymore.
That's why I cannot use any fastboot commands to flash a zip, neither run a RUU completely i guess.
So I think that i need any rom to either flash via recovery or just via PC not using fastboot/bootloader at all.
Are there any possibilities for me now?
Click to expand...
Click to collapse
Hi,
Plug your phone into the PC.
Go to device manager,and where it says MyHTC,right click and update driver.
Browse to the windows 7 & 8 drivers I gave you earlier.
Update,unplug phone ,and reboot PC.
Get a RUU that shows 3.32 or 3.33 in the title,and matches your region
Pull your battery.
Put it back in,and hold volume down and power button together.
Scroll to fastboot.
Plug in usb and run RUU from the PC

[Q] lg p920 bricked - erased bootloader

After installing cyanogenmod 10 nightly with cwm my battery began to act weird - it showed 0% charge and the phone turned off as soon as i plugged the charger off. I've read that this can be caused by CWM and that i have to install Amon Ra recovery in order to fix it. However, i wasn't able to enter fastboot mode, so i've decided to write the img directly using from adb shell
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/amonrarecovery.img
reboot recovery
(yes, now i understand that it is dumb, but i wanted to do it faster, without reading all tutorials).
it gave me the error that it cannot write there.
after that the phone won't turn on or enter recovery/download/fastboot mode. the only signs of life - omap 4430 usb device blinking in the device manager(i've installed the required drivers).
as far as i understand - if i'll be able to enter fastboot mode - i'll be able to flash normal bootloader back and install any rom.
But there's no LGE CDMA usb serial port showing in device manager, no matter what pc, cable or key combination(volume up, volume up+power, etc) i use. - it was the same even before i've erased bootloader.
besides when i use wkpark's omap4boot - i get error 121 on the second stage responce (i've tried the EMU version - still no luck)
seems that using OMAPflash is my only option now, but i can't seem to find examples of it's usage. One guy on this forum said that he revived p920 by dumping the firmware from a working p920 and then flashing it back on his device starting from 0000 memory address. maybe someone could upload his or stock firmware obtained this way?
i've tried using LG mobile support tool but it seems not to be able to detect the device (tried holding vol up)
maybe you guys can advice me something else?
PS this is a NOT FOR SALE device, if that changes something
thanks in advance.

Tried to install AmonRa recovery on my phone. No change, still no charging.
Sent from my LG-P920 using xda premium

alexisrozkov said:
After installing cyanogenmod 10 nightly with cwm my battery began to act weird - it showed 0% charge and the phone turned off as soon as i plugged the charger off. I've read that this can be caused by CWM and that i have to install Amon Ra recovery in order to fix it. However, i wasn't able to enter fastboot mode, so i've decided to write the img directly using from adb shell
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/amonrarecovery.img
reboot recovery
(yes, now i understand that it is dumb, but i wanted to do it faster, without reading all tutorials).
it gave me the error that it cannot write there.
after that the phone won't turn on or enter recovery/download/fastboot mode. the only signs of life - omap 4430 usb device blinking in the device manager(i've installed the required drivers).
as far as i understand - if i'll be able to enter fastboot mode - i'll be able to flash normal bootloader back and install any rom.
But there's no LGE CDMA usb serial port showing in device manager, no matter what pc, cable or key combination(volume up, volume up+power, etc) i use. - it was the same even before i've erased bootloader.
besides when i use wkpark's omap4boot - i get error 121 on the second stage responce (i've tried the EMU version - still no luck)
seems that using OMAPflash is my only option now, but i can't seem to find examples of it's usage. One guy on this forum said that he revived p920 by dumping the firmware from a working p920 and then flashing it back on his device starting from 0000 memory address. maybe someone could upload his or stock firmware obtained this way?
i've tried using LG mobile support tool but it seems not to be able to detect the device (tried holding vol up)
maybe you guys can advice me something else?
PS this is a NOT FOR SALE device, if that changes something
thanks in advance.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?p=44532338&nocache=1
Make sure you did this
If the LG COSMO appears in device manager install driver for her by select update driver then select browse my computer for driver {install driver Manual} and select Install driver from "inside folder have drivers"(omap4boot-for_optimus-v1.22 modified by XcachorroX®\usb_drv_windows) then try again step 2 flash fastboot

i resurrected lg p920 not for sale con omap4boot 1.25 option emu
http://www.youtube.com/watch?v=dHZ_RJCyrxk&feature=youtu.be

Praise be he did it. And I wholeheartedly and apologize for my frustration.

[Q] Rooting Issues

Hello,
So I'm trying to unlock and root my tf700t now that my warranty is expired and hope for an ASUS update is diminishing. I downloaded the unlock app from the website and went through the procedure. It took a few weeks and several emails with ASUS support but I think it is unlocked. The reason I say I think its unlocked is whenever I reboot the device, I don't get the message that says its unlocked. The unlock app however says the device is unlocked. So is my device unlocked?
I operated under the assumption that it was and tried to install the twrp recovery using the minimal adb and fastboot exe file. My tablet is recognized by my PC and I put the tablet in fastboot. The error I get when I do that is a writing error. It says writing recovery.... FAILED <remote: <INVALID STATE>>. Does this mean that I am not unlocked or did I do something incorrectly? Any help would be appreciated. I've been working on this for a few weeks and really want to get it moving.

Never heard that before..... If your bootlaoder is unlocked it should say so when you boot up.
Did you run the tool again?
If in doubt call Asus support and check if they have it as unlocked in their database.
But my guess is, since the recovery flash did not take, it's not.

berndblb said:
Never heard that before..... If your bootlaoder is unlocked it should say so when you boot up.
Did you run the tool again?
If in doubt call Asus support and check if they have it as unlocked in their database.
But my guess is, since the recovery flash did not take, it's not.
Click to expand...
Click to collapse
They contacted me today and told me that it is unlocked. Everytime I run the tool, It says the device is unlocked. When I do the power + Vol down, I get the three icons ( RCK, Wipe data, and an android). Ill try applying the recovery again later tonight.

Jkeeper18 said:
They contacted me today and told me that it is unlocked. Everytime I run the tool, It says the device is unlocked. When I do the power + Vol down, I get the three icons ( RCK, Wipe data, and an android). Ill try applying the recovery again later tonight.
Click to expand...
Click to collapse
Sounds like you are all set. You run fast boot from a pc when connected over USB and on that screen with 3 icons If it fails you have a driver issue.

sbdags said:
Sounds like you are all set. You run fast boot from a pc when connected over USB and on that screen with 3 icons If it fails you have a driver issue.
Click to expand...
Click to collapse
I attached a picture of the message I get from the minimal ADB tool. I'm also using the universal Drivers ( the ASUS Fastboot Interface). I tried the ASUS Android Bootloader Interface as well.

Jkeeper18 said:
I attached a picture of the message I get from the minimal ADB tool. I'm also using the universal Drivers ( the ASUS Fastboot Interface). I tried the ASUS Android Bootloader Interface as well.
Click to expand...
Click to collapse
I suspect your bootloader ist not unlocked.
Post a screen shot of when you issue the command 'fastboot devices' please.

berndblb said:
I suspect your bootloader ist not unlocked.
Post a screen shot of when you issue the command 'fastboot devices' please.
Click to expand...
Click to collapse
It says waiting for device. It stayed that way until i manually put it into fastboot. I've attached a screen shot of what it looks like when i did that. If my tablet isnt unlocked, how would I get it unlocked then? The unlock app ( both version) says the device is unlocked.

I am in the same boat - they think it is unlocked but it is not
The Asus v7 and v8 bootloaders both say "device is unlocked" but the fastbook info shows that it is not. I do not see any unlock inormation after the boot process starts. Also , the unlocker did not automatically restart my tablet. It also asked for my google credentials the first 5 times until the unlock said it worked. Now it does not ask that, it just says that it is unlocked. When I try to fastboot install the TWRP rom, it fails.
(remote - invalid state)
I called Asus and they have my tabler listed as unlocked. They are opening a case so that I can prove that it is unlocked.Then hopfully if they reset that setting, I can re-unlock it...
I was following this thread:
http://forum.xda-developers.com/showthread.php?t=2571542
Is there any work around? Please help!
I want TWRP and CM 10.2 on this slow TF700T tablet.
Thanks!

Jkeeper18 said:
It says waiting for device. It stayed that way until i manually put it into fastboot. I've attached a screen shot of what it looks like when i did that. If my tablet isnt unlocked, how would I get it unlocked then? The unlock app ( both version) says the device is unlocked.
Click to expand...
Click to collapse
Well you typed fastboot device not fastboot devices.

Did you 2-step verification enabled for Google by any chance?
I think Asus need to update their database so you get another chance ... Good luck
Sent from my XT894 using Tapatalk

berndblb said:
Did you 2-step verification enabled for Google by any chance?
I think Asus need to update their database so you get another chance ... Good luck
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
No, I did not have two-step verification. I hope Asus creates a case and actually looks into it and resets my device's status in their system. It sounds like that is my only option -- a very lengthy and painful one.

I disabled 2 step authentication since it interfered with the app. I would get invalid password errors until I disabled it and then the app worked.
Well you typed fastboot device not fastboot devices.
Click to expand...
Click to collapse
I attached a picture of what happens when I type the command fastboot devices. It looks like my device is not unlocked and Im going to have to contact ASUS. Are there any other tools that would unlock the device?

Jkeeper18 said:
I disabled 2 step authentication since it interfered with the app. I would get invalid password errors until I disabled it and then the app worked.
I attached a picture of what happens when I type the command fastboot devices. It looks like my device is not unlocked and Im going to have to contact ASUS. Are there any other tools that would unlock the device?
Click to expand...
Click to collapse
Are you sure your device gets recognized at all by your computer?
Usually the dialog just stays on "waiting for device" if the computer detects anything attached.
You have the necessary drivers installed?
Check in Device Manager (if you are running Windows) if there is a yellow triangle next to the entry for your tablet.
There is no other way to unlock. The bootloader is encrypted and only Asus has the key.

berndblb said:
Are you sure your device gets recognized at all by your computer?
Usually the dialog just stays on "waiting for device" if the computer detects anything attached.
You have the necessary drivers installed?
Check in Device Manager (if you are running Windows) if there is a yellow triangle next to the entry for your tablet.
There is no other way to unlock. The bootloader is encrypted and only Asus has the key.
Click to expand...
Click to collapse
The device is recognized by the computer. It says waiting for device when i type in "fastboot device" instead of "fastboot devices". Theres no yellow triangle either. I've sent an email to ASUS and I'm waiting on their reply.

Jkeeper18 said:
The device is recognized by the computer. It says waiting for device when i type in "fastboot device" instead of "fastboot devices". Theres no yellow triangle either. I've sent an email to ASUS and I'm waiting on their reply.
Click to expand...
Click to collapse
Fastboot device doesn't do anything.
I think you just need the right drivers. Let me see if I can dig them up from my collection. No point contacting Asus, they won't help you.
Try these, you need to unzip to same folder as fastboot and update device manager when in fastboot.
http://www.androidfilehost.com/?fid=23212708291675384

sbdags said:
Fastboot device doesn't do anything.
I think you just need the right drivers. Let me see if I can dig them up from my collection. No point contacting Asus, they won't help you.
Try these, you need to unzip to same folder as fastboot and update device manager when in fastboot.
http://www.androidfilehost.com/?fid=23212708291675384
Click to expand...
Click to collapse
Sorry Im still new at this. Where is the fastboot folder?

Jkeeper18 said:
Sorry Im still new at this. Where is the fastboot folder?
Click to expand...
Click to collapse
Where ever you are running fast boot from.
You must open a cmd window in the same directory or change to it using the CD command.

sbdags said:
Where ever you are running fast boot from.
You must open a cmd window in the same directory or change to it using the CD command.
Click to expand...
Click to collapse
So I've been trying for the past couple of days to get root and flash a new rom but it doesnt seem to be working. I've contacted ASUS and they said my tablet is unlocked as of December 16th but they will contact Taiwan to see if something is wrong. Do i have any options if they say the same thing? Thanks again for all your help. I appreciate it.

Jkeeper18 said:
So I've been trying for the past couple of days to get root and flash a new rom but it doesnt seem to be working. I've contacted ASUS and they said my tablet is unlocked as of December 16th but they will contact Taiwan to see if something is wrong. Do i have any options if they say the same thing? Thanks again for all your help. I appreciate it.
Click to expand...
Click to collapse
I have followed the TF700 forums for the last year pretty extensively and until about 2 weeks ago never read about anyone having this problem: Asus database having you unlocked, but it actually isn't. Since then I think I've read about 4 cases.
My best guess: It's a problem with the v8 Unlock app or the way their servers store/process the information they get from the Unlock Tool.
That you got to a support person willing to contact Taiwan is a big plus already. Other users just ran into a wall of: We do not support unlocking this device.
So stick with the person you contacted already. Take pictures of your boot process (to document that it does NOT say: This device is unlocked) and they always seem to ask for a screen shot of your About Tablet page with your SN number and MAC address.
Persistence seems to be the key. And luck to get someone at Asus willing to help....
There is no other way to unlock the bootloader. So you would be limited to rooting the tablet which would give you more freedom to tweak it and uninstall bloatware, but you still would have to deal with the slow stock rom.... :fingerscrossed:

HTC One Mini (M4_U4) Softbricked, OEM not unlocked, USB debug not enabled, bootloop

Hi all,
My HTC One Mini crashed one month after warranty (Boo!). I can get to the FASTBOOT and BOOTLOADER screen and select options. However, the Factory reset and recovery just cause a vibration and get be back to FASTBOOT menu. The phone is *** LOCKED ***.
After a few false starts on linux and mac machines, I've installed WinDroid Toolkit v3.1 on Windows 7. I have gotten the Token ID and used it to get an Unlock_code.bin via email from the HTC developers website (Cannot link as newb). However, when I follow the instructions in WinDroid it recommends that newer devices require "Enable OEM Unlock" to be set:
I cannot do this now. I continue but when it says a menu will appear on the phone, the menu does not and the phone remains in *** LOCKED *** state. I tried continuing with step 2 "Flashing a TWRP" but it does nothing.
TL;DR Am I screwed with having previously unlocked OEM on my HTC One Mini, now that it is soft-bricked?

I'm not that good at this stuff, but managed to get mine unlocked and a recovery on it via this link
sadly mine still has a problem in that it's now stuck in a boot loop, so don't use Oneclickroot as I did in my post here
hopefully you will get yours to work ok, but when you get to instruction 17 you may find that HTC website is quite fussy with the code you copy/paste
when you copy the Identifier block into Notepad or whatever, ensure you don't get any leading blank spaces before you submit it to HTC.
this excerpt from mine had blank spaces where I have inserted red X's, but it worked with them removed and HTC then emailed me the Unlock_code.bin file
XX<<<< Identifier Token Start >>>>
XX36ADF279412BE14D5002935236B24913
XXetc
XXetc
XX<<<<< Identifier Token End >>>>>
I hope this is of some use mate
---------- Post added at 02:39 PM ---------- Previous post was at 02:26 PM ----------
sorry,
lost the plot on my first reply and forget about the OEM unlock bit ...
to get that OEM unlock bit you would normally
first Enable Developer Modeon your phone by Launching the Settings Application -
Scroll Down and Tap on About Phone(or About Device) - Locate the Build Number Section - Tap on the Build Number Option 7 Times -
Go Back to the Main Settings Page - Scroll Down and Tap on Developer Options and it's found there
but given that you are in is bad a place as me in that we cannot get a bootup, I'm afraid I can't offer any more info,
but it's worth knowing anyway in case you do get booted up

Hi, i have the same issue, but a little different.
My phone was in a box for like 2 months, and then i decide to turn it on again, and i faced the same problem as the OP, but my One Mini is UNLOCKED, and i can't lock it again because i get an error in ADB. I try to enter on recovery (and flashed three differents recoveries without sucess), and reboot in bootloader, then try to factory reset, and reboot bootloader again. It don't do anything, only turn on when i plug the usb and enter in bootloader but no more than that. i've try to flash a RUU too, but it give me the error 171. i tried too the method with the rubber band pressing the power button to cause a reboot loop and get enough charge to launch the system but nothing, i don't see any results. I'm one step closer to give up, please help, i tried everything and nothing has worked for me. If need more information don't doubt on asking me. I really appreciate any help you can provide.

I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen

carkev said:
I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen
Click to expand...
Click to collapse
i don't need to press vol down and power together, the phone enter in bootloader once you plug the usb cable. it do that alone.
This is what i get
C:\adb>adb devices
List of devices attached
C:\adb>
the phone is recognized by HTC Sync manager but i can't see it in ADB.

a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here

carkev said:
a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
Click to expand...
Click to collapse
Hahaha, i know, i have the replacement here, i'll change it once i solve this problem.
carkev said:
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here
Click to expand...
Click to collapse
2. I will leave you down here exactly what i get when i type "adb devices" (with an attached image)
3. i have installed the latest HTC drivers, and i tried connecting my phone to front an rear usb ports, both of them. No results.
4. Down here i'll leave you an attached image of what i get when i try to install a recovery by typing "fastboot flash recovery recovery.img" (i changed the name to recovery.img of course) and the phone seems installing the recovery in fastboot but it gave me that error in adb and when i try to enter in recovery it reboots on bootloader.

your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here

carkev said:
your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here
Click to expand...
Click to collapse
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers

Little Snevil said:
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers
Click to expand...
Click to collapse
Hello guys, I've been following this thread and I'm having same issue. Adb does not sees my phone.
Fastboot does, but when I run ruu , it disconnects and give error 171
Tried usb 2 instead of 3.nothing.
I also think it's the drivers, but I can't seem to find the correct one for this phone. Any help is appreciated

my phone only starts in bootloader it have s-on and i cant use the toolkit cause usb debugging isnt active
adb writes waiting for device
can anyone help me?

Phone not detected in Fastboot

Long story short converted my phone from TMO to global. Went to relock bootloader but didn't flash the global rom from Oxygen updater and had to MSM back to TMobile. I have all the latest drivers installed and all the latest tools. My pC detects my phone when its booted but when I go into Fastboot I can't send commands to it. ADB Devices runs and says the list but does not show the device number. Sending a command comes back as device not found. If I unplug the phone my pC makes the disconnect sound. There's no sign of my phone in device manager but when I go down to the tool bar I can find Android device attached via USB.
I spent 2 hours already trying to get this to work and I'm out of ideas. I've even googled it and tried everything there. My last thought is to MSM again in hopes that it resets something

Smallsmx3 said:
Long story short converted my phone from TMO to global. Went to relock bootloader but didn't flash the global rom from Oxygen updater and had to MSM back to TMobile. I have all the latest drivers installed and all the latest tools. My pC detects my phone when its booted but when I go into Fastboot I can't send commands to it. ADB Devices runs and says the list but does not show the device number. Sending a command comes back as device not found. If I unplug the phone my pC makes the disconnect sound. There's no sign of my phone in device manager but when I go down to the tool bar I can find Android device attached via USB.
I spent 2 hours already trying to get this to work and I'm out of ideas. I've even googled it and tried everything there. My last thought is to MSM again in hopes that it resets something
Click to expand...
Click to collapse
Update: Looks like I'm good to go. Phone is connected again. B Now when I try to unlock my bootloader I can't flash the unlock token I get an t error cannot load unlock_token.bin

Got it all figured out!

Smallsmx3 said:
Got it all figured out!
Click to expand...
Click to collapse
What did you do for PC to see phone in fastboot mode? I have the same thing where it cannot see in fastboot mode

Arr6 said:
What did you do for PC to see phone in fastboot mode? I have the same thing where it cannot see in fastboot mode
Click to expand...
Click to collapse
Honestly I was typing in adb devices instead of fastboot devices. So I think my computer was detecting it. I did reinstall drivers that I got from the OnePlus site. I made allot of dumb errors