Database Develop

[Q] Help Restoring my HTC ONE back to stock.

I bought a used htc one for at&t and it was running 4.1.2. So I tried OTA and it downloaded the s/w, installed it and upon reboot - went straight to something called teamwin recovery (?) screen. I have to chose reboot button to boot the phone back. So I realized it was rooted and am very new to this whole root thing. I wanted to ota upgrade so I googled and stumbled on the following link with too many other links. Since the following link seemed easy, I tried following:
http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
But at the step 4 I get the following:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S--ON RH
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, how can i get it back to stock rom?
I read a lot of threads here for this very topic but each one takes talks different steps and am concerned being a noob with all these steps that I might brick my phone.
Can somebody please help me with the steps to get back to stock. I apologize if this was already covered in one of the many articles. Thanks.

jsknair said:
I bought a used htc one for at&t and it was running 4.1.2. So I tried OTA and it downloaded the s/w, installed it and upon reboot - went straight to something called teamwin recovery (?) screen. I have to chose reboot button to boot the phone back. So I realized it was rooted and am very new to this whole root thing. I wanted to ota upgrade so I googled and stumbled on the following link with too many other links. Since the following link seemed easy, I tried following:
http://htc-one.wonderhowto.com/how-...actory-settings-for-warranty-repairs-0149204/
But at the step 4 I get the following:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S--ON RH
Now, how can i get it back to stock rom?
I read a lot of threads here for this very topic but each one takes talks different steps and am concerned being a noob with all these steps that I might brick my phone.
Can somebody please help me with the steps to get back to stock. I apologize if this was already covered in one of the many articles. Thanks.
Click to expand...
Click to collapse
this should be simple ..do you have a windows PC ? if so what OS version if windows 7 continue, if windows 8.1 just gather the files below and post your answer.
Download this >> http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
and unzip the fastboot.zip below to your desktop
https://www.dropbox.com/s/0wzwt8843zx27nh/Fastboot.zip
from the fastboot folder you just made do shift+right click / command prompt here. now in the command window paste this
fastboot oem lock
you just relocked the bootloader ...now run the RUU file you downloaded above and your phone will be back to Stock.

Thank you very much for the quick reply.
I already downloaded the RUU RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2 as mentioned in the previous link. Should I not use that instead use the one provided by you above?
Just wanted to make sure the steps:
- enable usb debugging on phone
- connect my phone to usb of my windows 7 (with the phone powered on or powered off?)
- from windows 7 command prompt " fastboot oem lock "
- run the RUU file
Please confirm.

jsknair said:
Thank you very much for the quick reply.
I already downloaded the RUU RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2 as mentioned in the previous link. Should I not use that instead use the one provided by you above?
Just wanted to make sure the steps:
- enable usb debugging on phone
- connect my phone to usb of my windows 7 (with the phone powered on or powered off?)
- from windows 7 command prompt " fastboot oem lock "
- run the RUU file
Please confirm.
Click to expand...
Click to collapse
1.26.502.12 is over a year old
flash the one i posted for you it's android 4.3
connect phone to usb when in the bootloader / fastboot usb

Thanks again
I am downloading the RUU.
Do I have to follow the below to do the fastboot?
http://forums.androidcentral.com/ht...restore-back-locked-one-screen-acting-up.html
Reboot your phone to bootloader (power+volume down) and choose fastboot. Plug in your phone and it will change to fastboot USB. Open a command prompt within the fastboot folder and type the following:
fastboot oem lock
The same link I pasted above says to use fastboot oem relock if it is s-on?
"fastboot oem lock" only works if your device is S-OFF and I am assuming yours isn't which is why it didn't work.
Can you please confirm?

jsknair said:
Thanks again
I am downloading the RUU.
Do I have to follow the below to do the fastboot?
http://forums.androidcentral.com/ht...restore-back-locked-one-screen-acting-up.html
Reboot your phone to bootloader (power+volume down) and choose fastboot. Plug in your phone and it will change to fastboot USB. Open a command prompt within the fastboot folder and type the following:
fastboot oem lock
The same link I pasted above says to use fastboot oem relock if it is s-on?
"fastboot oem lock" only works if your device is S-OFF and I am assuming yours isn't which is why it didn't work.
Can you please confirm?
Click to expand...
Click to collapse
which ever works just relock the bootloader and run the RUU

clsA said:
which ever works just relock the bootloader and run the RUU
Click to expand...
Click to collapse
Thanks. I was able to install the RUU you have provided. But the problem is, the camera is all PINK now. It was taking wonderful pictures before but now it's all PINK/PURPLE now. Is there a way I can fix it?

jsknair said:
Thanks. I was able to install the RUU you have provided. But the problem is, the camera is all PINK now. It was taking wonderful pictures before but now it's all PINK/PURPLE now. Is there a way I can fix it?
Click to expand...
Click to collapse
I am still not able to OTA upgrade to kitkat after 48hrs. The bootloader now says relocked. Can I simply enter into fastboot and use the following RUU to get Kitkat?
http://forum.xda-developers.com/showthread.php?t=2428276
Thanks.

My phone is currently running 4.3 with bootloader in 'relocked' state. I am still not getting the OTA update to 4.4 and all my attempts to RUU update to 4.4 fails with htc_fastboot.exe has stopped working error. I will continue to do some more research to get there as the camera is useless in 4.3 at this point. Thanks for all your help and we can close this thread.

Fastboot oem lock only relocks the bootloader. You would have been better downloading and flashing revone to s off and LOCK the bootloader
Can you post a fastboot getvar all please removing imei and serial no?
Sent from my HTC One using xda app-developers app

[Q][H] HTC one Bricked? Wrong recovery image?

Hi All,
I just unlocked the bootloader on my m7 (at&t) and I was following this two guides http://www.android.gs/how-to-install-twrp-recovery-for-the-htc-one/ and http://www.androidegis.com/how-to/how-to-install-twrp-recovery-for-htc-one/ for installing TWRP.
I downloaded the file which is pointed in both tutorials from http://d-h.st/3ST and copied boot.img as indicated to fastboot folder and then ran "fastboot flash recovery boot.img" fom the CMD console. I rebooted the phone, selected recovery and it's stuck in Entering recovery. I guess boot.img is not the correct image.
I also noticed a flag "Tampered" on the top of the boot loader.
Hope you can help me, many thanks in advance,
Nicolas
Edit: It's not rooted, it was the next step to do.
Edit2: I tried once again holding the power button + VolumeUP and the phone is back to life. I wonder if the .img that I loaded is not the correct one. Could you advise and tell me what are the next steps to follow now?
Cheers

Nikouy said:
Hi All,
I just unlocked the bootloader on my m7 (at&t) and I was following this two guides http://www.android.gs/how-to-install-twrp-recovery-for-the-htc-one/ and http://www.androidegis.com/how-to/how-to-install-twrp-recovery-for-htc-one/.
I downloaded the file which is pointed in both tutorials from http://d-h.st/3ST and copies boot.img as suggested to fastboot folder and then ran "fastboot flash recovery boot.img" fom the CMD console. I rebooted the phone, selected recovery and it's stuck in Entering recovery. I guess boot.img is not the correct image.
I also noticed a flag "Tampered" on the top of the boot loader.
Hope you can help me, many thanks in advance,
Nicolas
Click to expand...
Click to collapse
Download this file http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img and rename it recovery.img and place it in your fastboot folder. Boot the phone to the bootloader and connect fastbootusb
Then in the command window type
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Then try entering recovery again.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Download this file http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img and rename it recovery.img and place it in your fastboot folder. Boot the phone to the bootloader and connect fastbootusb
Then in the command window type
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Then try entering recovery again.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
It's not even been recognized by fastboot now when I plug it to the computer. No output for "fastboot devices"
This is what I see on the screen:
TEMPERED
UNLOCKED
m7_UL PVT SHIP S-ON BH
HBOOT-1.44.0000
RADIO-A417.3550.20
OpenDSP-v31.120.274.0617
eMMC-Boot
Jul 5 2013.....
HBOOT
Fastboot
Recovery
Factory Reset
Simlock
Image crc
Show barcode
Click to expand...
Click to collapse

Nikouy said:
It's not even been recognized by fastboot now when I plug it to the computer. No output for "fastboot devices"
This is what I see on the screen:
Click to expand...
Click to collapse
Does it still show correctly in your pcs device manager. Sound like drivers need to be re-installed see 2)Q in this faq post to fix your drivers. http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2 If there installed correctly and you still have this error. Make sure you command line is opened at your fastboot folder.

Danny201281 said:
Does it still show correctly in your pcs device manager. Sound like drivers need to be re-installed see 2)Q in this faq post to fix your drivers. http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2 If there installed correctly and you still have this error. Make sure you command line is opened at your fastboot folder.
Click to expand...
Click to collapse
I've been playing around with drives, uninstalling, installing, etc but no joy yet. The driver which can't be installed is HTC MTP Device but the FAQ you pointed me does not cover this one.

Nikouy said:
I've been playing around with drives, uninstalling, installing, etc but no joy yet. The driver which can't be installed is HTC MTP Device but the FAQ you pointed me does not cover this one.
Click to expand...
Click to collapse
The MTP driver is not required by fastboot, does your device show as My HTC in device manger.
Are you sure you have your command prompt using your fastboot folder as the working folder?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
The MTP driver is not required by fastboot, does your device show as My HTC in device manger.
Are you sure you have your command prompt using your fastboot folder as the working folder?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Yes Danny,
C:\Users\snicolas\Desktop\Fastboot>fastboot devices
C:\Users\snicolas\Desktop\Fastboot>fastboot devices
Click to expand...
Click to collapse
Now all drives look good but it's still not being recognized by fastboot. See image below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The phone is even being recognized by HTC Sync Manager

Nikouy said:
Yes Danny,
Now all drives look good but it's still not being recognized by fastboot. See image below
The phone is even being recognized by HTC Sync Manager
Click to expand...
Click to collapse
Try a different cable if you've got one or a different usb port. also make sure your bootloader is in "fastbootusb" mode and not "hboot" mode.
---------- Post added at 01:55 AM ---------- Previous post was at 01:51 AM ----------
@Nikouy if you have HTC sync manger running close it. Right click on the small icon by your clock an select exit.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
Try a different cable if you've got one or a different usb port. also make sure your bootloader is in "fastbootusb" mode and not "hboot" mode.
---------- Post added at 01:55 AM ---------- Previous post was at 01:51 AM ----------
@Nikouy if you have HTC sync manger running close it. Right click on the small icon by your clock an select exit.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
Got it working, will update shortly.
Thanks for the quickly updates. Will deploy the img you pointed me before.
---
Successfully loaded. I am able to boot into recovery now. Phone rooted.
Multiple things happened here:
1) Drivers issues
2) The cable I initially used two unlock the bootloader isn't working anymore with fastboot.
Edit: should I set S-ON to OFF?

Nikouy said:
Got it working, will update shortly.
Thanks for the quickly updates. Will deploy the img you pointed me before.
---
Successfully loaded. I am able to boot into recovery now. Phone rooted.
Multiple things happened here:
1) Drivers issues
2) The cable I initially used two unlock the bootloader isn't working anymore with fastboot.
Edit: should I set S-ON to OFF?
Click to expand...
Click to collapse
Nice to know you got it sorted. :good:
It's always better to be s-off, but I would spend some time getting to know the device first.
If you flash something wrong with s-off, you could brick your phone.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

[Q] TWRP 2.5.0.0 Unresponsive

Hello,
I while ago I decided to root my HTC to get some extra stuff. I used a guide on youtube that seemed to be reasonably well made and followed everystep of the process. But before I could root it I had to unlock the bootloader and install TWRP recovery. I got the latest version and proceeded to the next step, where I encountered my problem. After flashing the recovery everything seemed to be well except that my phone wasn't actually rooted. I decided to redo some of the last steps. This is where things get a bit tricky. I have done this quite a while ago (maybe 3-4 months) and don't exactly remember the steps that I repeated but I think I've also flashed TWRP a second time, as well as some other steps. And when it came to the part where I needed to use the recovery I found out that the recovery doesn't work. I can't press anything on the screen, I can however press the lock button and lock the device but when the *slide to unlock* appears it stops working again. I was running out of time and decided to leave it for another time but time has passed and I never really got the time to tinker with it any more since university started and I'm more busy then ever. This has left me with no ability to root or even update my phone.
This brings me to today, when I restored my phone completely forgetting what has happened. It got back to Android 4.1 and I can't do anything about it.
I hope to sort this out and finally root the phone. But even getting rid of TWRP to the original recovery so I could just update my phone would be very helpfull.
Thank you very much.

aleks945 said:
Hello,
I while ago I decided to root my HTC to get some extra stuff. I used a guide on youtube that seemed to be reasonably well made and followed everystep of the process. But before I could root it I had to unlock the bootloader and install TWRP recovery. I got the latest version and proceeded to the next step, where I encountered my problem. After flashing the recovery everything seemed to be well except that my phone wasn't actually rooted. I decided to redo some of the last steps. This is where things get a bit tricky. I have done this quite a while ago (maybe 3-4 months) and don't exactly remember the steps that I repeated but I think I've also flashed TWRP a second time, as well as some other steps. And when it came to the part where I needed to use the recovery I found out that the recovery doesn't work. I can't press anything on the screen, I can however press the lock button and lock the device but when the *slide to unlock* appears it stops working again. I was running out of time and decided to leave it for another time but time has passed and I never really got the time to tinker with it any more since university started and I'm more busy then ever. This has left me with no ability to root or even update my phone.
This brings me to today, when I restored my phone completely forgetting what has happened. It got back to Android 4.1 and I can't do anything about it.
I hope to sort this out and finally root the phone. But even getting rid of TWRP to the original recovery so I could just update my phone would be very helpfull.
Thank you very much.
Click to expand...
Click to collapse
The background information is helpful but you have given us nothing to go on.
Post a fastboot getvar all except remove the imei and serialno?
What are you trying to accomplish? Return to Stock? S-OFF?

majmoz said:
The background information is helpful but you have given us nothing to go on.
Post a fastboot getvar all except remove the imei and serialno?
What are you trying to accomplish? Return to Stock? S-OFF?
Click to expand...
Click to collapse
Tell me what background information do you need and I'll get everything.
The goal is to get a working recovery, which ever one it would be I don't really care. I just want to be able to update the firmware.

reboot into the bootloader. flash the latest twrp for your device using fastboot flash recovery recoverynamehere.zip
profit

jdgreat4 said:
reboot into the bootloader. flash the latest twrp for your device using fastboot flash recovery recoverynamehere.zip
profit
Click to expand...
Click to collapse
If you could give me a more detailed guide I would toatally do that, because I'm pretty noobish when it comes to this kind of stuff.

aleks945 said:
Tell me what background information do you need and I'll get everything.
The goal is to get a working recovery, which ever one it would be I don't really care. I just want to be able to update the firmware.
Click to expand...
Click to collapse
like he said before, post the output of "fastboot getvar all" except your IMEI and SERIALNO
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
aleks945 said:
If you could give me a more detailed guide I would toatally do that, because I'm pretty noobish when it comes to this kind of stuff.
Click to expand...
Click to collapse
do you have adb and fastboot on your computer?
Do you have HTC drivers installed?

alray said:
like he said before, post the output of "fastboot getvar all" except your IMEI and SERIALNO
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
do you have adb and fastboot on your computer?
Do you have HTC drivers installed?
Click to expand...
Click to collapse
I don't know what adb is, sorry. And no I don't, I had to do everything on my friend's laptop because it didn't seem to work on my machine (W8.1 compared to his W7).
Edit. But I do have acces to it pretty much all the time.

aleks945 said:
I don't know what adb is, sorry. And no I don't, I had to do everything on my friend's laptop because it didn't seem to work on my machine (W8.1 compared to his W7).
Click to expand...
Click to collapse
yes better to use windows 7
go ahead and download adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790
download and install HTC sync from here: http://www.htc.com/us/support/software/htc-sync-manager.aspx
Once installed, uninstall HTC sync but keep the drivers installed
post back when done

alray said:
yes better to use windows 7
go ahead and download adb and fastboot from here: http://forum.xda-developers.com/showthread.php?t=2317790
download and install HTC sync from here: http://www.htc.com/us/support/software/htc-sync-manager.aspx
Once installed, uninstall HTC sync but keep the drivers installed
post back when done
Click to expand...
Click to collapse
The downloads are complete, just waiting on the instalation. The computer is quite old and slow unfortunatelly.
Thank you again
EDIT. Everything is done.

aleks945 said:
The downloads are complete, just waiting on the instalation. The computer is quite old and slow unfortunatelly.
Thank you again
EDIT. Everything is done.
Click to expand...
Click to collapse
ok so connect your phone with he usb cable to the computer, reboot it in bootloader mode (hold power and vol -). in bootloader select "fastboot"
then lauch the adb command prompt and type "fastboot getvar all". post the output here but edit out the imei and serialno before.

alray said:
ok so connect your phone with he usb cable to the computer, reboot it in bootloader mode (hold power and vol -). in bootloader select "fastboot"
then lauch the adb command prompt and type "fastboot getvar all". post the output here but edit out the imei and serialno before.
Click to expand...
Click to collapse
Here it is.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Link since image seems to be really tiny.
http://i.imgur.com/9cZZRA9.jpg

aleks945 said:
Here it is.
Link since image seems to be really tiny.
http://i.imgur.com/9cZZRA9.jpg
Click to expand...
Click to collapse
you can flash twrp 2.6.3.3
download the file and save it in the same folder where you have installed minimal adb and fastboot
then open the command prompt and with the phone in bootloader/fastboot mode enter these commands:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
What do you want to achieve then? Custom rooted rom? stock rooted rom (latest version)? or you simply what to root the rom you currently have?

alray said:
you can flash twrp 2.6.3.3
download the file and save it in the same folder where you have installed minimal adb and fastboot
then open the command prompt and with the phone in bootloader/fastboot mode enter these commands:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
What do you want to achieve then? Custom rooted rom? stock rooted rom (latest version)? or you simply what to root the rom you currently have?
Click to expand...
Click to collapse
Latest stock rooted ram would be the final goal.

aleks945 said:
Latest stock rooted ram would be the final goal.
Click to expand...
Click to collapse
you can flash this rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
its the stock rom for 6.09.401.5

alray said:
you can flash this rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.5_odexed.zip
its the stock rom for 6.09.401.5
Click to expand...
Click to collapse
Doesn't my phone have to be rooted to be able to instal another rom?

aleks945 said:
Doesn't my phone have to be rooted to be able to instal another rom?
Click to expand...
Click to collapse
no just flash the rom from twrp recovery then you can root it if you want.

Windows 8.1 x64 ADB Drivers?

I have installed HTC BMP USB Driver v1.0.5375 and HTC Drivers v4.5.0.001. I also have Android SDK and Google USB Drivers. And I have installed these drivers from this thread; http://forum.xda-developers.com/showthread.php?t=2232799&highlight=driver+win7
So my fastboot works just fine. fastboot devices command returns my serial number. The problem is adb just not working.
This is how it looks;
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Anyone?

kuzeykutupdayisi said:
Anyone?
Click to expand...
Click to collapse
so when trying "adb devices" your phone is booted in android with usb debug enabled
or booted in custom recovery?

alray said:
so when trying "adb devices" your phone is booted in android with usb debug enabled
or booted in custom recovery?
Click to expand...
Click to collapse
It's booted in the hboot fastboot usb. I need it to be in bootloader to lock my bootloader. I'm going to return my device for warranty.
EDIT: Alright when booted to android it sees my device but it says offline? Can't enter any command because of it?

kuzeykutupdayisi said:
It's booted in the hboot fastboot usb. I need it to be in bootloader to lock my bootloader. I'm going to return my device for warranty.
Click to expand...
Click to collapse
you can't use ADB from the bootloader hence why there is no output when doing "adb devices".
ADB can only be used from a booted os with usb debug enabled or from a custom recovery
in bootloader mode, you can only use FASTBOOT
---------- Post added at 11:10 AM ---------- Previous post was at 11:08 AM ----------
if you are going to return your phone back to stock for warranty purpose then follow nkk71's guide linked in my signature.

alray said:
you can't use ADB from the bootloader hence why there is no output when doing "adb devices".
ADB can only be used from a booted os with usb debug enabled or from a custom recovery
in bootloader mode, you can only use FASTBOOT
Click to expand...
Click to collapse
As I stated in my upper comment when I'm booted at the OS it sees my device but it says offline? Can't issue any commands.

kuzeykutupdayisi said:
As I stated in my upper comment when I'm booted at the OS it sees my device but it says offline? Can't issue any commands.
Click to expand...
Click to collapse
what is the output of "adb version" ?

alray said:
what is the output of "adb version" ?
Click to expand...
Click to collapse
Now it's like this. It works when it's in OS but when it is in recovery it still does not work. Which is where the most I need it.

kuzeykutupdayisi said:
(...)but when it is in recovery it still does not work. Which is where the most I need it.
Click to expand...
Click to collapse
so "adb reboot-bootloader" bring you back in recovery? strange, I thought "adb reboot bootloader" should bring the phone back in bootloader mode where only FASTBOOT can be used.
"adb reboot recovery" will reboot the phone in recovery mode.
so in the os use:
adb devices
in recovery mode use:
adb devices
in bootloader mode use:
fastboot devices
---------- Post added at 12:30 PM ---------- Previous post was at 12:28 PM ----------
btw there is a newer verison of adb. You should update your sdk.

alray said:
so "adb reboot-bootloader" bring you back in recovery? strange, I thought "adb reboot bootloader" should bring the phone back in bootloader mode where only FASTBOOT can be used.
"adb reboot recovery" will reboot the phone in recovery mode.
so in the os use:
adb devices
in recovery mode use:
adb devices
in bootloader mode use:
fastboot devices
---------- Post added at 12:30 PM ---------- Previous post was at 12:28 PM ----------
btw there is a newer verison of adb. You should update your sdk.
Click to expand...
Click to collapse
No it brought back me to fastboot usb, I manually entered the recovery. And it didn't work there. I have Ubuntu 14.4 on VirtualBox. Adb works in recovery there but only this time the code that is required to lock the bootloader does not work. Gives an error. I don't know what to do in here.

kuzeykutupdayisi said:
No it brought back me to fastboot usb, I manually entered the recovery. And it didn't work there. I have Ubuntu 14.4 on VirtualBox. Adb works in recovery there but only this time the code that is required to lock the bootloader does not work. Gives an error. I don't know what to do in here.
Click to expand...
Click to collapse
you could use the bootloader reset tool instead
https://www.androidfilehost.com/?fid=23329332407580570
flash this in recovery and choose the option needed to lock the bootloader

alray said:
you could use the bootloader reset tool instead
https://www.androidfilehost.com/?fid=23329332407580570
flash this in recovery and choose the option needed to lock the bootloader
Click to expand...
Click to collapse
Welp, my efforts was in vain. Thank you it worked!

Deleted OS//No Drivers//OTG Don't work

Hello.
I wanted to flash CM12.1 to friends One(M7) but while flashing I have some kind of error.
I removed OS .. there is just TWRP 2.5.0.0 which seems don't recognize OTG USB.
Drivers for ADB or Fastboot while I'm in bootloader seems don't work I have windows 10 and only 3.0 USB Ports.
So now is there TWRP without nothing and I don't know what to do.. I have only 2 days for fix it.
//EDIT// It was unlocked and rooted so I just wanted to flash ROM like in others phones but like I'm reading more and more forums with HTC it's quite difficult and I'm not sure if everything is as it should be. Whats is S-ON/OFF?? What is RUU and how I know if "my" One is the right for which I can flash ROM. (But theses questions aren't important)
I see lot of theard with same problem but I can't find any real solution. I hope someone help me :fingers-crossed:

What happens when you type "fsstboot devices" in bootloader menu?

donkeykong1 said:
What happens when you type "fsstboot devices" in bootloader menu?
Click to expand...
Click to collapse
Typo, should be "fastboot devices".

in ur devices no os??? maybe can't flash because corrupt emmc..,.. sory for bad english

Fastboot devices don't show nothing
How to fix corrupt emmc? Without os or possibility connection with pc

dasti555 said:
Fastboot devices don't show nothing
How to fix corrupt emmc? Without os or possibility connection with pc
Click to expand...
Click to collapse
Hard to suggest much without knowing specifics of the phone but I think we are a long way from assuming the emmc is corrupt.
Try this link to get your drivers working, then give us the output of "fastboot getvar all"
http://forum.xda-developers.com/showthread.php?t=2317790

if ur device can bootloader it's means u can repair emmc maybe
I have experienced 0gb on my EMMC , but can bootloader ,it can repair EMMC with emmcblkp.zip , but I forgot his link
sory for bad in english

1-the rom did not flashed because you are using the wrong recovery version. You need at least 2.7.1.1 to flash Cyanogenmod roms (assuming your phone is a M7_UL variant)
2- Since you are using such an old recovery, it would make sense to me that it was flashed on the phone back in 2013 so maybe the phone never got any Ota updates and the hboot version is still 1.44? If yes you won't be able to get fastboot connectivity using Win8/10, only with win7/linux/OSx. That might be the problem.
3-can you write down all the information you see when in bootloader, with this we should at least be able to confirm what I said above
---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------
bintang456 said:
if ur device can bootloader it's means u can repair emmc maybe
I have experienced 0gb on my EMMC , but can bootloader ,it can repair EMMC with emmcblkp.zip , but I forgot his link
sory for bad in english
Click to expand...
Click to collapse
There is nothing pointing to a bad emmc for now. He is at step 1 (getting the phone detected) and you are talking about a "possible" step 20.... Not saying you're wrong but it's way too early to assume a bad emmc

alray said:
1-the rom did not flashed because you are using the wrong recovery version. You need at least 2.7.1.1 to flash Cyanogenmod roms (assuming your phone is a M7_UL variant)
2- Since you are using such an old recovery, it would make sense to me that it was flashed on the phone back in 2013 so maybe the phone never got any Ota updates and the hboot version is still 1.44? If yes you won't be able to get fastboot connectivity using Win8/10, only with win7/linux/OSx. That might be the problem.
3-can you write down all the information you see when in bootloader, with this we should at least be able to confirm what I said above
---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------
There is nothing pointing to a bad emmc for now. He is at step 1 (getting the phone detected) and you are talking about a "possible" step 20.... Not saying you're wrong but it's way too early to assume a bad emmc
Click to expand...
Click to collapse
One more thought on this phone. Did you also wipe the data partition? If not are you sure that the person that originally installed twrp didn't leave a nandroid backup on the device. Have you looked under restore in twrp? LIkely too simple but worth a shot!!

Yes you are absolutelly right!
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Apr 20 2013, 15:46:23-1
So what should I do now?
I wanted to install today Windows7 but it failed and I ****ed it and I removed my old windows so I must 2 hours searching for new windows. Now I'm finally at Windows10 again.
So.. Maybe Windows7 in virtual box? Anyway one guy have Linux at his computer what can I do now?

sorry for my assume...

dasti555 said:
Yes you are absolutelly right!
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
Apr 20 2013, 15:46:23-1
So what should I do now?
I wanted to install today Windows7 but it failed and I ****ed it and I removed my old windows so I must 2 hours searching for new windows. Now I'm finally at Windows10 again.
So.. Maybe Windows7 in virtual box? Anyway one guy have Linux at his computer what can I do now?
Click to expand...
Click to collapse
Windows 7 in a virtualbox won't work afaik. Better to use a live Ubuntu usb/cd, setup adb and fastboot then you'll be able to update your twrp recovery and flash the rom. Also worth to post a "fastboot getvar all" at the same time. Maybe we could update the firmware easily (depending what the getvar all returns) and fix that connectivity problem at the same time.
Here is aguide how to use Ubuntu without having to install it on your computer: http://forum.xda-developers.com/showthread.php?t=2606577
It was writted for a different purpose so just ignore the steps talking about rumrunner.
---------- Post added at 10:59 AM ---------- Previous post was at 10:57 AM ----------
bintang456 said:
sorry for my assume...
Click to expand...
Click to collapse
No need to be sorry, everyone tries their best, thats what matters :good:
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
Btw here is the reference for the minimum recovery requirement to flash CM:
TWRP recoveries with version greater than or equal to 2.7.0.8 support this fstab change.* If you have a favorite recovery maintainer, encourage them to incorporate "block: by-name" support into their recovery kernels!
Official 2.7.1.0 for m4, m7, m7spr/m7wls, and m7vzw/m7wlv mistakenly did not include the necessary fstab support, so 2.7.1.1 was released for these devices, addressing the issue.
More recent unofficial builds of TWRP can be found at android.cmphys.com. You'll find source code for all these devices linked there as well.
Click to expand...
Click to collapse
https://wiki.cyanogenmod.org/w/HTC_fstab_updates

So what I have to do now is
Connect phone to PC with Ubuntu then write in terminal "fastboot getvar all" and then write here again? Or Just "fastboot flash recovery.img"
Well ... I'm at Ubuntu and when we try "fastboot flash recovery recovery.img" then just waiting for devices .. need i some kind of fastboot drivers for ubuntu or what?
We tried download some kind of" # sudo apt-get install android-tools-adb android-tools-fastboot "
but phone is still not recognized

mb_guy said:
Typo, should be "fastboot devices".
Click to expand...
Click to collapse
Sorry, big fingers, small keyboard on my phone [emoji20]

dasti555 said:
So what I have to do now is
Connect phone to PC with Ubuntu then write in terminal "fastboot getvar all" and then write here again? Or Just "fastboot flash recovery.img"
Click to expand...
Click to collapse
I'll copy/paste from the guide linked above the step you need only:
(1) a copy of 32bit Ubuntu. NOT 64!! http://www.ubuntu.com/download/desktop
(2) no need to install-boot into it as if trying it (IMAGE 3)
(4) drivers NOT needed
I know others have had zero issues but some of us have had nothing but nightmares. This is who I'm sharing this for.
I hope it helps... Even just one!
Have fun all!
IF BY CHANCE YOU ARE HAVING ISSUES WITH ADB OR FASTBOOT IN UBUNTU SEEING YOUR DEVICE, TYPE sudo BEFORE YOUR COMMANDS. IT WANTS PERMISSION TO ACCEPT YOUR COMMANDS. WHEN YOU TYPE sudo THEN YOUR PASSWORD YOU ARE GRANTING THOSE PERMISSIONS. SOMETIMES THE ISSUE WON'T APPEAR TIL YOU GET INTO FASTBOOT. SO CHECK FIRST BY TYPING IN adb devices WHEN YOU FIRST OPEN THE TERMINAL. IF YOU GET A SERIAL NUMBER YOU SHOULD BE FINE. AFTER YOU GET INTO BOOTLOADER, TYPE fastboot devices IF YOU GET A "no permission" ERROR THEN YOU NEED TO TYPE sudo BEFORE all INSTRUCTIONS. SOME VERSIONS OF LINUX HAVE AN SU TERMINAL. THAT WOULD BE THE BEST TO USE AS IT REQUIRES ROOT/PERMISSION TO EVEN START AND WILL MAINTAIN THOSE PERMISSIONS THROUGHOUT.
UBUNTU STEPS.....
Image 3- Boot into Ubuntu
Image 7- Open Terminal in Ubuntu (Top left gear like symbol, click it and a search bar will appear, start typing terminal, it will appear below the bar, just select it)
Image 8- You need to install adb fastboot these are the instructions you need to type in the terminal you just opened. Type one line at a time and press enter after each. Allow Ubuntu to do it's stuff.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Image 9-12 Shows how the terminal should look as it finds, downloads and install the appropriate files.
Image 13- After the downloads are finish you can check to make sure things were installed correctly. Type “adb” and your screen should look like this
Image 14- Type “fastboot” and this is the information that should appear.
Image 15- To make sure your device is seen type “fastboot devices” and it should show devices with a serial number.
then you can use "fastboot getvar all' and "fastboot flash recovery <file_name>.img"

We made all this now .. fastboot devices command not show nothing just new line which is waiting for command and when we try fastboot flash recovery recovery.img then <waiting for device>
we still dont have drivers or what?

dasti555 said:
We made all this now .. fastboot devices command not show nothing just new line which is waiting for command and when we try fastboot flash recovery recovery.img then <waiting for device>
we still dont have drivers or what?
Click to expand...
Click to collapse
You don't need drivers on linux. Is the phone booted in bootloader and in the fastboot menu? You should see "fastboot usb" in red when in the correct mode to use fastboot commands.
like on this image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

yes it is
its like transfer isnt working but charging is
edit : uh no :/ there is only fastboot in red not fastboot usb I should boot there while I'm connected via cable? // booting there while cable is pluged-in and still only fastboot in red

dasti555 said:
yes it is
its like transfer isnt working but charging is
edit : uh no :/ there is only fastboot in red not fastboot usb I should boot there while I'm connected via cable? // booting there while cable is pluged-in and still only fastboot in red
Click to expand...
Click to collapse
are you using the original usb cable? some cheap cable are only providing power but no data connection. I also just have noticed from your first post that you are using usb 3.0. You have to use a 2.0 port to avoid problems. you should have "fastboot usb" in red when there is a connection as opposed to "fastboot" only if there is none.
bootib there before or after doesnt matter

@alray We are trying it with different PC which have Ubuntu and also Kali Linux as dualboot.
Have only 2.0USB Ports..
I will try different cable.... Nope .. Still only fastboot without USB
My OnePllus One with same cable find but this HTC no :/